This chapter
describes the CDR fields supported by the system for use in PGW-CDRs.
CDR Fields
Access Point Name
Network Identifier
The network
identifier portion of the access point name (APN). This APN is sent
to the S-GW by the MME and is relayed to the P-GW in the EGTP Create
Session Request message.
The APN string may consist
of alphabetic characters (“A...Z”, “a...z”),
digits (“0...9”) and the dash “-”.
APN Selection Mode
An index indicating
how the APN was selected.
The following APN
selection mode indexes are possible:
- 0: MS or network provided
APN, subscription verified
- 1: MS provided APN,
subscription not verified
- 2: Network provided
APN, subscription not verified
Cause for Record
Closing
This field contains
a reason for the closure of the CDR.
Some of the possible
reasons are as follows:
- normalRelease (0):
The PDP context was terminated normally through a PDP context release
(end of context or SGSN change) or a GPRS detach.
- abnormalRelease (4):
The PDP context was abnormally terminated.
- volumeLimit (16): The
PDP context was terminated due to exceeding volume limit.
- timeLimit (17): The
PDP context was terminated due to exceeding time limit.
- servingNodeChange (18):
The PDP context was terminated due to Serving Node Address List
Overflow.
- maxChangeCond (19):
The PDP context was terminated due to exceeding the changed condition
limit.
- managementIntervention
(20): The record was closed due to an O&M request.
- rATChange (22): The
PDP context was terminated due to change in RAT.
- mSTimeZoneChange (23):
The PDP context was terminated due to change in time zone of MS.
- PLMNChange (24): The
PDP context was terminated due to change of PLMN-ID.
- Partial record generation:
A partial CDR was generated for reasons such as the reaching of
data volume or time (duration) limits, or reaching the maximum number
of charging condition changes.
Charging Characteristics
Lists the charging
characteristics applied to the PDP context by the P-GW.
Charging Characteristics
Selection Mode
This field specifies
how the Charging Characteristics were selected.
Supported values:
- servingNodeSupplied (0)
- homeDefault (3)
- roamingDefault (4)
- visitingDefault (5)
-
AAASupplied (6)
-
GWOverride (7)
Note: The values
AAASupplied (6) and GWOverride (7) are only supported in the custom40
GTPP dictionary.
Charging ID
This field contains
a charging identifier, which can be used together with the P-GW
address to identify all records involved in a single bearer context.
The Charging ID is generated by the P-GW during bearer context activation
and is transferred to the context requesting P-GW.
Diagnostics
This field is
included in the CDR when the bearer is released and when the option gtpp attribute diagnostics is
configured.
Duration
This field contains
the duration in seconds for the record. The value is reset for each
new partial CDR.
This value is converted
from the internal representation in milliseconds to an integer value
representing only seconds. The mechanism for this conversion (ceiling,
floor, round-off) can be configured.
Dynamic Address
Flag
This field indicates
that the PDN address has been dynamically allocated for that particular IP
CAN bearer (PDN connection). This field is missing if the address
is static.
List of Service
Data
This list includes
one or more service data containers. Each container is associated
with a service condition change on a service data flow (categorized
per rating group or per combination of the rating group and service
id) within this IP CAN bearer.
Data Service Volume
Block
This is a service
data container. A container is associated with a service condition
change on a service data flow (categorized per rating group or per
combination of the rating group and service id) within this IP CAN
bearer.
A service data container
may include the fields in the following subsections.
Charging Rulebase
Name
The name of
the Rulebase used for charging. This is the group name of charging rules.
Data Volume FBC
Downlink
The number of
octets transmitted during the use of the packet data services in
the downlink direction.
Data Volume FBC
Uplink
The number of
octets received during the use of the packet data services in the
uplink direction.
Failure Handling
Continue
This parameter
is included when the failure handling procedure has been executed
and new containers are opened. This parameter shall be included
in the first and subsequent containers opened after the failure
handling execution.
Local Sequence Number
(LOSDV)
A service data
container sequence number. It starts from 1 and is increased by
1 for each service data container generated within the lifetime
of this IP-CAN bearer.
QoS Information
Negotiated
For an IP-CAN
bearer-specific container, this contains the authorized QoS for
the IP-CAN bearer. The first container for each QCI/ARP
pair includes this field. In following containers this field is present
if the previous change condition is “QoS change”.
The field contains a
sequence of fields which are described in the following subsections:
- qCI [1] Integer
- maxRequestedBandwithUL [2] Integer
Optional
- maxRequestedBandwithDL [3] Integer
Optional
- guaranteedBitrateUL [4] Integer
Optional
- guaranteedBitrateDL [5] Integer
Optional
- aRP [6] Integer
Optional
Allocation and Retention
Priority (ARP)
The ARP contains
information about the priority level (scalar), the pre-emption capability
(flag) and the pre-emption vulnerability (flag). The primary purpose
of ARP is to decide whether a bearer establishment or modification
request can be accepted, or needs to be rejected due to resource
limitations (typically available radio capacity for GBR bearers).
Range: 1-15.
Guaranteed Bit Rate
(GBR) Downlink
The GBR denotes
the downlink bit rate that can be expected to be provided by a GBR
bearer.
Guaranteed Bit Rate
(GBR) Uplink
The GBR denotes
the uplink bit rate that can be expected to be provided by a GBR
bearer.
Maximum Bit Rate
(MBR) Downlink
The MBR limits
the downlink bit rate that can be expected to be provided by a GBR
bearer (for example, excess traffic may get discarded by a rate
shaping function).
Maximum Bit Rate
(MBR) Uplink
The MBR limits
the uplink bit rate that can be expected to be provided by a GBR
bearer.
Quality Class Identifier
(QCI)
A QCI is a scalar
that is used as a reference to access node-specific parameters that
control bearer level packet forwarding treatment (for example, scheduling
weights, admission thresholds, queue management thresholds, link
layer protocol configuration, etc.), and that have been pre-configured
by the operator owning the access node (for example, eNodeB). Value
Range: 1-9.
Rating Group
This is the
service flow identity and must be used for differentiated evaluation
of user’s traffic. This is also known as content-id.
Result Code
This is filled
by OCS on Gy interface.
The following are the
values as per RFC 3588 and 4006 (Other Result Codes not defined
in the RFCs can also be seen in the Result Code field if sent by
OCS):
- DIAMETER_SUCCESS
2001
- DIAMETER_LIMITED_SUCCESS
2002
- DIAMETER_COMMAND_UNSUPPORTED
3001
- DIAMETER_UNABLE_TO_DELIVER
3002
- DIAMETER_REALM_NOT_SERVED
3003
- DIAMETER_TOO_BUSY
3004
- DIAMETER_LOOP_DETECTED
3005
- DIAMETER_REDIRECT_INDICATION
3006
- DIAMETER_APPLICATION_UNSUPPORTED
3007
- DIAMETER_INVALID_HDR_BITS
3008
- DIAMETER_INVALID_AVP_BITS
3009
- DIAMETER_UNKNOWN_PEER
3010
- DIAMETER_AUTHENTICATION_REJECTED
4001
- DIAMETER_OUT_OF_SPACE
4002
- ELECTION_LOST
4003
- DIAMETER_END_USER_SERVICE_DENIED
4010
- DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE
4011
- DIAMETER_CREDIT_LIMIT_REACHED
4012
- DIAMETER_AVP_UNSUPPORTED
5001
- DIAMETER_UNKNOWN_SESSION_ID
5002
- DIAMETER_AUTHORIZATION_REJECTED
5003
- DIAMETER_INVALID_AVP_VALUE
5004
- DIAMETER_MISSING_AVP
5005
- DIAMETER_RESOURCES_EXCEEDED
5006
- DIAMETER_CONTRADICTING_AVPS
5007
- DIAMETER_AVP_NOT_ALLOWED
5008
- DIAMETER_AVP_OCCURS_TOO_MANY_TIMES
5009
- DIAMETER_NO_COMMON_APPLICATION
5010
- DIAMETER_UNSUPPORTED_VERSION
5011
- DIAMETER_UNABLE_TO_COMPLY
5012
- DIAMETER_INVALID_BIT_IN_HEADER
5013
- DIAMETER_INVALID_AVP_LENGTH
5014
- DIAMETER_INVALID_MESSAGE_LENGTH
5015
- DIAMETER_INVALID_AVP_BIT_COMBO
5016
- DIAMETER_NO_COMMON_SECURITY
5017
- DIAMETER_USER_UNKNOWN
5030
- DIAMETER_RATING_FAILED
5031
Service Condition
Change
The reason for
closing the service data container for triggers like SGSN change,
QoS change, RAT change, time and volume triggers, etc.
Bit Setting regarding
TS 32.298:
- qoSChange (0), bearer
modification
- sGSNChange (1), bearer
modification
- sGSNPLMNIDChange (2),
bearer modification
- tariffTimeSwitch (3),
tariff time change
- pDPContextRelease (4),
bearer release
- rATChange (5), bearer
modification
- serviceIdledOut (6),
IP flow idle out, DCCA QHT expiry
- reserved (7), old: QCTexpiry
is no report event
- configurationChange (8),
configuration change
- serviceStop (9), IP flow
termination
- dCCATimeThresholdReached
(10), DCCA quota reauth.
- dCCAVolumeThresholdReached
(11), DCCA quota reauth.
- dCCAServiceSpecificUnitThresholdReached
(12), DCCA quota reauth.
- dCCATimeExhausted (13),
DCCA quota reauth.
- dCCAVolumeExhausted (14),
DCCA quota reauth.
- dCCAValidityTimeout (15),
DCCA quota validate time (QVT expiry)
- reserved (16), reserved
due to no use case, old: return Requested is covered by (17), (18)
- dCCAReauthorisationRequest
(17), DCCA quota reauthorization request by OCS
- dCCAContinueOngoingSession
(18), DCCA failure handling continue IP flow
- dCCARetryAndTerminateOngoingSession
(19), DCCA failure handling terminate IP flow after DCCA retry
- dCCATerminateOngoingSession
(20), DCCA failure handling, terminate IP flow
- cGI-SAIChange (21), bearer
modification
- rAIChange (22), bearer
modification
- dCCAServiceSpecificUnitExhausted
(23), DCCA quota reauthorization
- recordClosure (24), PGW-CDR
closure
- timeLimit (25), intermediate
recording
- volumeLimit (26), intermediate
recording
- serviceSpecificUnitLimit
(27), intermediate recording
- envelopeClosure (28)
- eCGIChange (29), bearer
modification. “ECGI Change”
- tAIChange (30), bearer
modification. “TAI Change”
- userLocationChange (31)
bearer modification. “User Location Change”
Service Identifier
The service
identifier may designate an end user service, a part of an end user
service, or an arbitrarily formed group thereof. This field is only
included if reporting is per combination of the rating group and
service id.
Serving Node Address
(LOSDV)
This field contains
the serving node (for example, SGSN/S-GW) control plane
IP address.
Length
6 or 18 bytes (depending
on v4 or v6 address)
Time of First Usage
The timestamp
for the first IP packet to be transmitted for the service data flow
referred to the current instance of Service Condition Change.
Format
BCD encoded octet string
Time of Last Usage
The timestamp
for the last IP packet to be transmitted for the service data flow
referred to the current instance of Service Condition Change.
Format
BCD encoded octet string
Time of Report
A timestamp
defining the moment when the service data container is closed.
Format
BCD encoded octet string
Time Usage
The difference
in seconds within the range of 0.to.4294967295 between “time
of first usage” and “time of last usage”.
User Location Information
(LOSDVV)
This field indicates
details of where the UE is currently located (SAI, TAI, RAI, CGI,
ECGI or access-specific user location information).
Local Sequence Number
This field contains
a unique sequence number associated with the Node ID field and independent
of the bearer context.
MS Time Zone
The “Time
Zone” IE that the SGSN may provide to the P-GW during the
PDP context activation/modification procedure.
Node ID
This field contains
an identifier string for the node that had generated the CDR.
On the Cisco P-GW, this
Node ID field is a printable string in the format ndddSTRING:
- n: The first digit is
the Sessmgr restart counter having a value between 0 and 7.
- ddd: The number of the
sessmgr instance generating the CDR
- STRING: This is a configured
Node-ID-Suffix having any string between 1 to16 characters, defined
using the gtpp attribute node-id command.
If this node-id-suffix
is not configured, the PGW uses the active-charging service name
as the Node-id-suffix (truncated to 16 characters).
This field is only included
when the option gtpp
attribute local-record-sequence-number is configured.
PDN Connection Id
This field defines
the PDN connection (IP-CAN session) identifier to identify different
records belonging to same PDN connection. This field includes the
Charging Id of the first IP-CAN bearer activated within the PDN
connection. Together with P-GW address, this uniquely identifies
the PDN connection.
PDP PDN Type
-- OCTET 1: PDP Type
Organization
Spare ‘1111’ PDP
Type Organization Value
PDP
Type Organization |
Value |
ETSI |
0 |
IETF |
1 |
Note: In LTE, only
IETF is supported.
-- OCTET 2: PDP/PDN
Type Number
Bits
3 2 1
0 0 1 IPv4
0 1 0 IPv6
0 1 1 IPv4/IPv6
Bits
8-4 of octet are spare and are coded as zero.
P-GW Address
These field
is the serving P-GW IP address for the Control Plane. If both an
IPv4 and an IPv6 address of the P-GW is available, the P-GW shall
include the IPv4 address in the CDR.
Length
6 or 18 bytes (depending
on v4 or v6 address)
P-GW PLMN Identifier
This field is
the P-W PMLN Identifier (Mobile Country Code and Mobile Network Code).
The MCC and MNC are coded
as described for “User Location Info” in TS 29.274 [91].
RAT Type
Holds the value
of RAT Type, as provided to S-GW and P-GW, described in TS 29.274
for eGTP case.
RAT
Types |
Values (Decimal) |
<reserved> |
0 |
UTRAN |
1 |
GERAN |
2 |
WLAN |
3 |
GAN |
4 |
HSPA
Evolution |
5 |
EUTRAN |
6 |
<spare> |
7-255 |
The field is provided
by the SGSN/MME and transferred to the S-GW/P-GW
during the IP-CAN bearer activation/modification.
Record Opening Time
This field contains
the timestamp when a PDP context is activated in PGW or when a subsequent
record is opened after a partial record.
The timestamp is determined
based on the internal timer which has an accuracy of 10ms. Depending
on the configured mechanism (ceiling, floor, or round-off) this field
is translated to only show full seconds.
TimeStamp ::= OCTET
STRING (SIZE(6))
The contents of this
field are a compact form of the UTC Time format containing local
time plus an offset to universal time. Binary coded decimal encoding
is employed for the digits to reduce the storage and transmission
overhead
--
e.g. YYMMDDhhmmssShhmm
--
where
--
YY = Year
00 to 99 BCD
encoded
--
MM = Month
01 to 12 BCD encoded
--
DD = Day
01 to 31 BCD
encoded
--
hh = hour
00 to 23 BCD
encoded
--
mm = minute
00 to 59 BCD encoded
--
ss = second
00 to 59 BCD encoded
--
S = Sign
0 = “+”, “-” ASCII
encoded
--
hh = hour
00 to 23 BCD
encoded
--
mm = minute
00 to 59 BCD
encoded
Format
BCD encoded octet string
Record Sequence
Number
A running sequence
number within the range of 1 to 4294967296 used to link partial
records generated by the P-GW for a specific IP-CAN bearer context
(characterized with the same Charging ID and P-GW address). This
field is not present if the first record is also the final record.
Record Type
This field identifies
the type of the record:
PGW-CDR (pgwPDPRecord)
85 (0x55)
Served IMEISV
This field contains
the International Mobile Equipment Identity (IMEISV) of the equipment served.
The structure of the
IMEI is defined in TS 23.003.
The IMEI is composed
of the following elements:
- Type Allocation Code
(TAC). Its length is 8 digits.
- Serial Number (SNR) is
an individual serial number uniquely identifying each equipment
within each TAC. Its length is 6 digits.
- Software Version Number
(SVN) identifies the software version number of the mobile equipment.
Its length is 2 digits.
If SV is not available,
a filler digit “f” is added after the spare digit
to fill up the last byte. Spare digit: this digit shall be zero,
when transmitted by the MS.
Format
BCD encoded octet string
Served IMSI
The International
Mobile Subscriber Identity (IMSI) of the MS. The IMSI is formatted
in accordance with 3GPP TS 23.003. This will be present if the Anonymous
Access Indicator is FALSE or not supplied.
The IMSI is formatted
in accordance with 3GPP TS 23.003.
Format
BCD encoded octet string
Served MNNAI
This field contains
the Mobile identifier of the served user in Network Access Identifier (NAI)
format based on IMSI, as defined in TS 23.003 [68].
SubscriptionID ::= SET
{
subscriptionIDType
[0] SubscriptionIDType,
subscriptionIDData
[1] UTF8String
}
SubscriptionIDType
::= ENUMERATED
{
END_USER_E164
(0),
END_USER_IMSI
(1),
END_USER_SIP_URI
(2),
END_USER_NAI
(3),
END_USER_PRIVATE
(4)
}
The type will be END_USER_NAI.
For IMSI: 123456789012345
mcc=123 mnc=045
subscriptionIDData is
a string will be
0123456789012345@nai.epc.mnc045.mcc123.3gppnetwork.org
Served MSISDN
The field tracks
the Mobile Station (MS) ISDN number (MSISDN) of the subscriber which is
transparently copied from the Create Session Request message.
The MSISDN is TBCD encoded
as shown in the example below:3GPP TS 23.003 (CCITT Rec. E 213)
ServedMSISDN ::= OCTET
STRING (SIZE(1..9))
subscriber identification
MSISDN
octet 1 : bit 8 (msb):
extension bit
= 1 : no extension
other : not relevant
bit 7..5 : type of number
= 000 : unknown
= 001 : international
number
= 010 : national
significant number
= 011 : network
specific number
= 100 : subscriber
number
= 101 : reserved
= 110 : abbreviated
number
= 111 : reserved
for extension
bit 4..1 : numbering
plan indicator
= 0001: ISDN/Telephony
Numbering Plan (Rec CCITT E.164)
other : not relevant
octet 2..9: <= 16
digits TBCD-String (twisted)
substructure (without
spares or fillers):
1..3 digits - country
code (CC)
(only international number)
3 digits - national destination
code (NDC)
<= 10 digits
- subscriber number (SN)
first and intermediate
octet = 2 digits
last octet = 2
digits or 1 digit + 1 fill digit H'F
As per 3GPP TS 29.274
v 8.11.0, “MSISDN value contains only the actual MSISDN number
(does not contain the ‘nature of address indicator’ octet,
which indicates ‘international number’ as in 3GPP
TS 29.002 [37]) and is encoded as TBCD digits.”
To comply with this,
octet 1 (nature of address indicator) is not added in the encoded
value of MSISDN.
example:
MSISDN: '491720400305'
encoded: H'94 71 02 04
30 50
Format
BCD encoded octet string.
Served PDP PDN Address
This field contains
the IP address for the PDN connection (PDP context, IP-CAN bearer). This
is a network layer address of type IP version 4 (PDN Type is IPv4)
or IP version 6 (PDN Type is IPv6 or IPv4v6). The address for each
Bearer type is allocated either temporarily or permanently (see “Dynamic Address
Flag”). This parameter shall be present except when both
the Bearer type is PPP and dynamic address assignment is used.
Length
The length can vary
based on whether the encoded IP address is IPv4 or IPv6.
Serving Node Address
The serving
node control plane IP address of the S-GW used during this record.
This is a list of IP addresses. If the list overflows with a configured
number of IP addresses, a CDR with “serving node Change” as
cause for record closure will be generated. The serving node addresses
that are listed here are sequentially mapped to the serving node
types listed in the field “Serving node Types”.
Format
Sequence of IPv4 orIPv6
addresses.
Length
6-98 or 18-292 bytes
(depending on IPv4 or IPv6 address; for 1-16 S-GW/SGSN addresses)
Serving Node PLMN
Identifier
This field contains
a serving node (SGSN/S-GW/MME/ePDG/HSGW)
PLMN Identifier (Mobile Country Code and Mobile Network Code).
The MCC and MNC are coded
as described for “Routing Area Identity” in TS
29.060 [75].
Serving Node Type
These fields
contain one or several serving node types in the control plane of
an S-GW or P-GW, which have been connected during the record. The
serving node types listed here are sequentially mapped to the serving
node addresses listed in the field “Serving node Address”.
The possible values
are:
ServingNodeType ::= ENUMERATED
{
sGSN (0),
pMIPSGW (1),
gTPSGW (2),
ePDG (3),
hSGW (4),
mME (5)
}
Format
Sequence of serving
Node Type
Length
3-48; variable length
format (based on number of nodes connected during this period)
Start Time
This field contains
the time when the User IP-CAN session starts at the P-GW, available
in the CDR for the first bearer in an IP-CAN session.
The timestamp is determined
based on the internal timer which has an accuracy of 10ms. Depending
on the configured mechanism this is translated into the timestamp
which only shows the full seconds.
The format is shown
below.
TimeStamp ::= OCTET
STRING (SIZE(6))
The contents of this
field are a compact form of the UTC Time format containing local
time plus an offset to universal time. Binary coded decimal encoding
is employed for the digits to reduce the storage and transmission
overhead
--
e.g. YYMMDDhhmmssShhmm
--
where
--
YY = Year
00 to 99 BCD
encoded
--
MM = Month
01 to 12 BCD encoded
--
DD = Day
01 to 31 BCD
encoded
--
hh = hour
00 to 23 BCD
encoded
--
mm = minute
00 to 59 BCD encoded
--
ss = second
00 to 59 BCD encoded
--
S = Sign
0 = “+”, “-” ASCII
encoded
--
hh = hour
00 to 23 BCD
encoded
--
mm = minute
00 to 59 BCD
encoded
Format
BCD encoded octet string
Stop Time
This field contains
the time when the User IP-CAN session is terminated at the P-GW,
available in the CDR for the last bearer in an IP-CAN session.
The timestamp is determined
based on the internal timer which has an accuracy of 10ms. Depending
on the configured mechanism (ceiling, floor, round-off) this is translated
into the timestamp which only shows the full seconds.
The format is shown
below.
TimeStamp ::= OCTET
STRING (SIZE(6))
The contents of this
field are a compact form of the UTC Time format containing local
time plus an offset to universal time. Binary coded decimal encoding
is employed for the digits to reduce the storage and transmission
overhead
--
e.g. YYMMDDhhmmssShhmm
--
where
--
YY = Year
00 to 99 BCD
encoded
--
MM = Month
01 to 12 BCD encoded
--
DD = Day
01 to 31 BCD
encoded
--
hh = hour
00 to 23 BCD
encoded
--
mm = minute
00 to 59 BCD encoded
--
ss = second
00 to 59 BCD encoded
--
S = Sign
0 = “+”, “-” ASCII
encoded
--
hh = hour
00 to 23 BCD
encoded
--
mm = minute
00 to 59 BCD
encoded
Format
BCD encoded octet string
User Location Information
This field contains
the User Location Information as described in TS 29.274 for eGTP
case (e.g. CGI, SAI, RAI TAI and ECGI).
The field is provided
by the SGSN/MME and transferred to the S-GW/P-GW
during the IP-CAN bearer activation/modification.
User Location Information
contains the location (e.g. CGI/SAI, ECGI/TAI
or RAI) where the UE is located and used during the transfer of
the data volume captured by the container (applicable only to the
SGW-CDR). This is included in the Traffic data container only if
previous container's change condition is “user location
change”. Note the user location information in SGW-CDR
main level contains the location where the UE was when PGW-CDR was opened.
The flags ECGI, TAI,
RAI, SAI and CGI in octet 5 indicate if the corresponding fields
are present in the IE or not. If one of these flags is set to “0”,
the corresponding field is not present at all. The respective identities
are defined in 3GPP TS 23.003.
The following subclauses
specify the coding of the different identities. For each identity,
if an Administration decides to include only two digits in the MNC,
then bits 5 to 8 of octet 7 are coded as “1111”.
CGI field:
The Location Area Code
(LAC) consists of 2 octets. Bit 8 of Octet 9 is the most significant bit
and bit 1 of Octet 10 the least significant bit. The coding of the
location area code is the responsibility of each administration.
Coding using full hexadecimal representation shall be used.
The Cell Identity (CI)
consists of 2 octets. Bit 8 of Octet 11 is the most significant
bit and bit 1 of Octet 12 the least significant bit. The coding
of the cell identity is the responsibility of each administration.
Coding using full hexadecimal representation shall be used.
SAI field:
The Location Area Code
(LAC) consists of 2 octets. Bit 8 of Octet 9 is the most significant bit
and bit 1 of Octet 10 the least significant bit. The coding of the
location area code is the responsibility of each administration.
Coding using full hexadecimal representation shall be used.
The Service Area Code
(SAC) consists of 2 octets. Bit 8 of Octet 11 is the most significant bit
and bit 1 of Octet 12 the least significant bit. The SAC is defined
by the operator.
RAI field:
The Location Area Code
(LAC) consists of 2 octets. Bit 8 of Octet 9 is the most significant bit
and bit 1 of Octet 10 the least significant bit. The coding of the
location area code is the responsibility of each administration.
Coding using full hexadecimal representation shall be used.
The Routing Area Code
(RAC) consists of 2 octets. Only Octet 11 contains the RAC. Octet 12
is coded as all 1's (11111111). The RAC is defined by the operator.
TAI field:
The Tracking Area Code
(TAC) consists of 2 octets. Bit 8 of Octet 9 is the most significant bit
and bit 1 of Octet 10 the least significant bit. The coding of the
tracking area code is the responsibility of each administration.
Coding using full hexadecimal representation shall be used.
ECGI field:
The E-UTRAN Cell Identifier
(ECI) consists of 28 bits. Bit 4 of octet 10 is the most significant
bit and bit 1 of Octet 11 the least significant bit. The coding
of the E-UTRAN cell identifier is the responsibility of each administration.
Coding using full hexadecimal representation shall be used.
Length
Varies based on the
type of identity