Message

Type value
(Decimal)
Message Reference Initial
0 Reserved 3GPP TS 29.274 [3]
1 Echo Request 3GPP TS 29.274 [3] X
2 Echo Response 3GPP TS 29.274 [3]
3 Version Not Supported Indication 3GPP TS 29.274 [3]
16-Apr Reserved for S101 interface 3GPP TS 29.274 [3]
17-24 Reserved for S121 interface 3GPP TS 29.276 [17]
25 SRVCC PS to CS Request 5.2.2 X
26 SRVCC PS to CS Response 5.2.3
27 SRVCC PS to CS Complete Notification 5.2.4 X
28 SRVCC PS to CS Complete Acknowledge 5.2.5
29 SRVCC PS to CS Cancel Notification 5.2.6 X
30 SRVCC PS to CS Cancel Acknowledge 5.2.7
31 SRVCC CS to PS Request 5.2.8 X
32-239 Reserved for GTPv2 3GPP TS 29.274 [3]
240 SRVCC CS to PS Response 5.2.9
241 SRVCC CS to PS Complete Notification 5.2.10 X
242 SRVCC CS to PS Complete Acknowledge 5.2.11
243 SRVCC CS to PS Cancel Notification 5.2.12 X
244 SRVCC CS to PS Cancel Acknowledge 5.2.13
245 to 247
248-255 Reserved for GTPv2 3GPP TS 29.274 [3]
For future Sv interface use -
Triggered
X
X
MME/SGSN - MSC
X MSC - MME/SGSN
MSC - MME/SGSN
X MME/SGSN - MSC
MME/SGSN - MSC
X MSC - MME/SGSN
X
X
X
Information elements P Condition / Comment
This IE shall be included in the message except for the cases:
The UE is emergency attached and it is UICCless
The UE is emergency attached and the IMSI is not
authenticated
C
This IE shall be included in the message for all types of
emergency calls by the MME and the SGSN.
CO
This IE shall be included for all SRVCC calls if available in the
MME or SGSN (NOTE 2).
This IE shall be included if any one of the applicable flags is set to
1.
The following flags are applicable:
EmInd: this flag shall be sent if this session is for
an emergency call.
ICS: this flag shall be sent to request IMS
Centralized Service support.
VHO: this flag shall be sent if the MME requests
the vSRVCC HO.
This IE specifies the address for control plane Initial message
which is chosen by the source MME/SGSN.
The target MSC Server shall send subsequent control plane Initial
messages related to the GTP tunnel for this UE towards this
address.
This IE specifies the tunnel for control plane message which is
chosen by the source MME/SGSN.
The target MSC Server shall include this TEID in the GTP header
of all control plane messages related to the GTP tunnel for this
UE.
The MME/SGSN shall include C-MSISDN IE in the message
except for the cases:
The UE is emergency attached and it is UICCless
The UE is emergency attached and the IMSI is not
authenticated
The C-MSISDN is defined in 3GPP TS 23.003 [4].
STN-SR C
The MME/SGSN shall include STN-SR IE if this session is not for
an emergency call.
The MME shall include mobile station classmarks, supported
codecs, and CS Security key in MM Context for E-UTRAN
(v)SRVCC.
The derivation of the CS security keys shall follow the procedures
defined 3GPP TS 33.401[7].
The SGSN shall include mobile station classmarks, supported
codecs, and CS Security key in MM Context for UTRAN (HSPA)
SRVCC.
The derivation of the CS security keys shall follow the procedures
defined 3GPP TS 33.102[10].
Source to Target
Transparent Container
M
The MME or SGSN shall include Source to Target Transparent
Container IE
Target RNC ID C
This IE shall be used to identify the target access for (v)SRVCC
handover to UTRAN (NOTE 1).
Target Cell ID C
This IE shall be used to identify the target access for SRVCC
handover to GERAN (NOTE 1).
MM Context for E-
UTRAN (v)SRVCC
C
MM Context for UTRAN
SRVCC
C
MME/SGSN Sv TEID for
Control Plane
M
C-MSISDN C
Sv Flags C
MME/SGSN Sv Address
for Control Plane
M
IMSI C
ME Identity (MEI)
Source SAI CO
The SGSN shall include this IE during a SRVCC Handover from
UTRAN to GERAN and shall set it as per the SAI of the Source
ID IE received from the source RNC (see 3GPP TS 25.413 [9]).
See NOTE 3.
Allocation/Retention
Priority
CO
The MME shall include this IE if (v)SRVCC with priority is
supported and (v)SRVCC is performed for an IMS-based MPS
session (see 3GPP TS 23.216 [2]).
Anchor PLMN ID CO
The MME/SGSN shall include this IE during SRVCC from
UTRAN/E-UTRAN PS to UTRAN/GERAN CS domain
GWCN/MOCN to be used for subsequent SRVCC handover in
the reverse direction as specified in 3GPP TS 23.251 [16].
Private Extension O None
NOTE 3: The Source SAI is sent in BSSMAP Handover Request during a SRVCC Handover from UTRAN to GERAN. A default
SAI configured in the MSC Server enhanced for SRVCC is sent in BSSMAP Handover Request during a SRVCC Handover from
E-UTRAN to GERAN. The default SAI for E-UTRAN should be different from the SAIs used in UTRAN.
NOTE1: Based upon the SRVCC Handover procedure, either Target RNC ID or Target Cell ID shall be present in this message
NOTE2: An MME or SGSN supporting the Sv interface should attempt to get the ME Identity for all SRVCC calls for interception,
charging or Automatic Device Detection in the MSC.
IE Type Ins.
Not Required
Needs Discussion
STN-SR 0
Source to Target
Transparant Container IE
0
Target RNC ID 0
Target Global Cell
ID
0
MM Context for E-UTRAN
(v)SRVCC
0
MM Context for UTRAN
SRVCC
0
TEID-C 0
MSISDN 0
Sv Flags 0
IP-Address 0
IMSI 0
MEI 0
Service Area Identifier 0
ARP 0
PLMN ID 0
Private Extension VS
NOTE 3: The Source SAI is sent in BSSMAP Handover Request during a SRVCC Handover from UTRAN to GERAN. A default
SAI configured in the MSC Server enhanced for SRVCC is sent in BSSMAP Handover Request during a SRVCC Handover from
E-UTRAN to GERAN. The default SAI for E-UTRAN should be different from the SAIs used in UTRAN.
NOTE1: Based upon the SRVCC Handover procedure, either Target RNC ID or Target Cell ID shall be present in this message
NOTE2: An MME or SGSN supporting the Sv interface should attempt to get the ME Identity for all SRVCC calls for interception,
charging or Automatic Device Detection in the MSC.
Information elements P Condition / Comment
Cause M
This IE shall be sent if Cause value differs from "Request
accepted".
MSC Server shall include this information element to indicate the
reason for rejecting SRVCC PS to CS request
MSC Server Sv Address for Control
Plane
O
If the Cause IE contains the value" Request accepted", the
target MSC server may include MSC server Sv Address for
Control Plane IE in SRVCC PS to CS Response message if
target MSC Server decides to use different IP address for the
subsequent communication. The source MME/SGSN shall store
this MSC server address and use it when sending subsequent
control plane messages to this GTP-C tunnel.
MSC Server Sv TEID for Control Plane C
The target MSC server shall include MSC server Sv Tunnel
Endpoint Identifier for Control Plane IE in SRVCC PS to CS
Response message if the Cause IE contains the value "Request
accepted". The source MME/SGSN shall include this TEID-C in
the GTP-C header of all subsequent uplink control plane
messages from the source MME/SGSN to the target MSC
servers.
Target to Source Transparent
Container
C
If the Cause IE contains the value "Request accepted ", this IE
shall be included and shall carry the Target to Source
Transparent Container to be sent within the Handover command
or the Relocation Command towards the source access network.
Private Extension O None
(v)SRVCC rejected Cause CO
IE Type Ins.
Cause 0
IP Address 0
TEID-C 0
Target to Source Transparant
Container IE
0
Private Extension VS
SRVCC Cause 0
Information elements P
Private Extension O
Information elements P
Cause M
Private Extension O
Information elements P
Cancel Cause M
Private Extension O
Information elements P
Cause M
Private Extension O
Sv Flags C
SRVCC PS to CS Complete Notification
SRVCC PS to CS Complete Acknowledge
SRVCC PS to CS Cancel Notification
SRVCC PS to CS Cancel Acknowledge
IMSI C
ME Identity (MEI) C
IMSI C
SRVCC post failure Cause CO
Condition / Comment IE Type Ins.
This IE shall be included in the message except for the
cases:
The UE is emergency attached and it is
UICCless
The UE is emergency attached and the
IMSI is not authenticated
This IE shall be sent if a call is to be released locally in
the MSC Server due to IMS session leg establishment
failure.
The MSC Server shall include this IE to indicate the
nature of the failure (i.e, permanent or temporary)
None Private Extension VS
Condition / Comment IE Type Ins.
None Cause 0
None Private Extension VS
Condition / Comment IE Type Ins.
This IE shall be included in the message except for the
cases:
The UE is emergency attached and it is
UICCless
The UE is emergency attached and the
IMSI is not authenticated
MME/SGSN indicates the reason for Handover
cancellation
SRVCC Cause 0
This IE shall be included in the message for the following
cases:
The UE is emergency attached and it is
UICCless
The UE is emergency attached and the
IMSI is not authenticated
None Private Extension VS
Condition / Comment IE Type Ins.
None Cause 0
This IE shall be included if any one of the applicable flags
is set to 1.
The following flags are applicable:
STI: this flag shall be sent if the MSC
Server has started the IMS session transfer
procedure.
None Private Extension VS
Sv Flags 0
IMSI 0
MEI 0
IMSI 0
SRVCC Cause 0
International Mobile Subscriber Identity (IMSI)
Octets 8 7 6 5 4 3
1
2 to 3
4
5
6

n+4
.
Octets 8 7 6 5 4 3
1
2 to 3
4
5
6 PCE
a(n+1)
a(n+2) to
a(n+3)
a(n+4) Spare Instance
Octets 8 7 6 5 4 3
1
2 to 3
4
5
6
Spec: 29.274
Section : 8
Bits
Type = 51 (decimal)
Length = n
Spare Instance
Session Transfer Number for Single Radio Voice Call Continuity (STN-SR)
Spec: 29.280
Section : 6
Cause
Octets 5 to (n+4) represent the IMSI value in international number format as described in ITU-T Rec E.164 [25], encoded as TBCD digits,
i.e. digits from 0 through 9 are encoded "0000" to "1001". When there is an odd number of digits, bits 8 to 5 of the last octet are encoded
with the filler "1111". The maximum number of digits is 15.
International Mobile Subscriber Identity (IMSI)
Bits
Type = 2 (decimal)
Length = n
Spare Instance
Number digit 4 Number digit 3

Number digit m Number digit m-1
Bits
Type = 1 (decimal)
Length = n
Spare Instance
Number digit 2 Number digit 1
NANPI
Digit 2 Digit 1
Cause value
Spare
Type of the offending IE
Length of the offending IE = 0
Cause is a variable length IE, which may have either of the following two lengths values:
- If n = 2, a = 0 and the Cause IE shall be 6 octets long. Therefore, octets "a(n+1) to a(n+4)" will not be present.
- If n = 6, a = 1 and the Cause IE will be 10 octets long.

n+4
Octets 8 7 6 5 4 3
1
2 to 3
4
5
6 to (n+4)
Octets 8 7 6 5 4 3
1
2 to 3
4
5
6 to (n+4)
When the target network is GERAN, the Transparent container field contains the value part of the Layer 3 Information IE defined in 3GPP
TS 48.008 [8], i.e., octets 3 to n, excluding octet 1 (Element ID) and octet 2 (Length).
When the target network is UTRAN, this container carries the Target RNC to Source RNC Transparent Container IE defined in 3GPP TS
25.413 [9]. The Transparent container field contains a transparent copy of the corresponding ASN.1/PER IE (see subclauses 8.2.2 and 8.48
in 3GPP TS 29.274 [3]).
When the target network is E-UTRAN, the container carries the Target eNB To Source eNB Transparent Container IE defined in 3GPP TS
36.413 [14]. The Transparent container field contains a transparent copy of the corresponding ASN.1/PER IE (see subclauses 8.2.2 and 8.48
in 3GPP TS 29.274 [3]).
The receiver of this Information Element shall ignore the length of the transparent container encoded in octet 5 and shall derive the actual
length of the container from the length encoded in octets 2 to 3 minus 1.
For backward compatibility, the sender of this Information Element shall set the octet 5 to the actual length of the transparent container if
the size of the container is smaller or equal to 255 octets, and to the value "255" otherwise
Length = n
Spare Instance
Length of the Transparent container
Transparent container
Digit m Digit (m-1)
Octet 5 contains the Nature of Address and Numbering Plan Indicator (NANPI) of the "AddressString" ASN.1 type (see 3GPP TS 29.002
[11]). Octets 6 to (n+4) contain the actual STN-SR (digits of an address encoded as a TBCD-STRING as in the "AddressString" ASN.1
type). For an odd number of STN-SR digits, bits 8 to 5 of the last octet are encoded with the filler "1111".
Bits
Source to Target Transparent Container
The Source to Target Transparent Container contains information that shall be transferred transparently by CN entities from the source RAN
to the target RAN.
When the target network is GERAN, the Transparent container field contains the value part of the Old BSS to New BSS Information IE
defined in 3GPP TS 48.008 [8], i.e. octets 3 to n, excluding octet 1 (Element ID) and octet 2 (Length).
The receiver of this Information Element shall ignore the length of the transparent container encoded in octet 5 and shall derive the actual
length of the container from the length encoded in octets 2 to 3 minus 1.
For backward compatibility, the sender of this Information Element shall set the octet 5 to the actual length of the transparent container if
the size of the container is smaller or equal to 255 octets, and to the value "255" otherwise.
Bits
Type = 53 (decimal)
Target to Source Transparent Container
Type = 52 (decimal)
Length = n (decimal)
Spare Instance
Length of the Transparent container
Transparent container
Octets 8 7 6 5 4 3
1
2 to 3
4
5
6 to 21
22 to 37
38
39 to a
b
(b+1) to c
d
(d+1) to
(n+4)
Octets 8 7 6 5 4 3
1
2 to 3
4
5
6 to 21
22 to 37
38 to 45
46
47
48 to a
b
(b+1) to c
d
(d+1) to
(n+4)
Octets 8 7 6 5 4 3
1
2 to 3
SRVCC Cause
MM Context for UTRAN SRVCC
Bits
Type = 56 (decimal)
Length = 1
Length of the Mobile Station Classmark 2
Mobile Station Classmark 2
Length of the Mobile Station Classmark 3
Mobile Station Classmark 3
Length of the Supported Codec List
Supported Codec List
Bits
Type = 55 (decimal)
Length = n
Spare Instance
Spare KSI
CS
Length of the Mobile Station Classmark 2
Mobile Station Classmark 2
Length of the Mobile Station Classmark 3
Mobile Station Classmark 3
Length of the Supported Codec List
Supported Codec List
Spare Instance
Spare eKSI
CK
SRVCC
IK
SRVCC
Bits
Type = 54 (decimal)
Length = n
MM Context for E-UTRAN (v)SRVCC
CK
CS
IK
CS
Kc
CKSN
CS
4
5
Octets 8 7 6 5 4 3
1
2 to 3
4
5 to (n+4)
Octets 8 7 6 5 4 3
1
2 to 3
4
5 to (n+4)
Octets 8 7 6 5 4 3
1
2 to 3
4
5 to 8
9 to (n+4)
Octets 8 7 6 5 4 3
1
2 to 3
4
5 Spare Spare Spare Spare VHO STI
6-(n+4)
Cell ID
Target Global Cell ID
RNC ID
Target RNC ID
Bits
Type = 58 (decimal)
Length = n (decimal)
Spare Instance
SRVCC Cause value
Bits
Type = 57 (decimal)
Length = n (decimal)
Spare Instance
Spare Instance
Bits
Type = 59 (decimal)
Length = n (decimal)
Spare Instance
Tunnel Endpoint Identifier for Control Plane (TEID-C)
These octet(s) is/are present only if explicitly specified
Tunnel Endpoint Identifier for Control Plane (TEID-C)
Bits
Type = 60 (decimal)
Length = n
Spare Instance
These octet(s) is/are present only if explicitly specified
Sv Flags
The following bits within Octet 5 indicate:
- Bit 1 EmInd (Emergency Indicator): This flag is used to indicate the IMS emergency session.
- Bit 2 ICS (IMS Centralized Service): This flag is used to request ICS support.
- Bit 3 STI (Session Transfer Indicator): This flag is used to indicate IMS session transfer has been invoked.
- Bit 4 VHO (vSRVCC flag): This flag is used to indicate that the vSRVCC HO is requested by the MME.
Service Area Identifier
Octets 8 7 6 5 4 3
1
3-Feb
4
5
6
7
8 to 9
10 to 11
12-(n+4)
Octets 8 7 6 5 4 3
1
2 to 3
4
5 to (n+4)
Octets 8 7 6 5 4 3
1
2 to 3
4
5
6

n+4
Bits
Type = 61 (decimal)
Location Area Code (LAC)
Service Area Code (SAC)
These octet(s) is/are present only if explicitly specified
The Location Area Code (LAC) consists of 2 octets. Bit 8 of Octet 8 is the most significant bit and bit 1 of Octet 9 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 10 is the most significant bit and bit 1 of Octet 11 the least significant bit.
The SAC is defined by the operator
Bits
Length = n
Spare Instance
MCC digit 2 MCC digit 1
MNC digit 3 MCC digit 3
MNC digit 2 MNC digit 1
Mobile Equipment (ME) Identity
Mobile Equipment Identity (MEI)
The ME Identity field contains either the IMEI or the IMEISV as defined in clause 6.2 of 3GPP TS 23.003 [2]. It is encoded as specified in
clause 7.7.53 of 3GPP TS 29.060 [4], beginning with octet 4 of Figure 7.7.53.1.
The IMEI(SV) digits are encoded using BCD coding where IMEI is 15 BCD digits and IMEISV is 16 BCD digits. For IMEI, bits 5 to 8 of
the last octet shall be filled with an end mark coded as '1111'
Bits
Type = 76 (decimal)
Length = n
Spare Instance
Number digit 2 Number digit 1
Type = 75 (decimal)
Length = n
Spare Instance
Number digit 4 Number digit 3

Number digit m Number digit m-1
MSISDN
The sending entity copies the value part of the MSISDN into the Value field of the MSISDN IE.
Octets 5 to (n+4) represent the MSISDN value is in international number format as described in ITU-T Rec E.164 [25] and 3GPP TS 29.002
[41]. 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 [41]) and is encoded as TBCD digits, i.e. digits from 0 through 9 are encoded "0000" to
"1001". When there is an odd number of digits, bits 8 to 5 of the last octet are encoded with the filler "1111".
Spec: 29.274
Section : 8
Octets 8 7 6 5 4 3
1
2 to 3
4
5 Spare PCI
6 to (n+4)
Octets 8 7 6 5 4 3
1
2 to 3
4
5 to (n+4)
Octets 8 7 6 5 4 3
1
2 to 3
4
5 to (n+4)
Octets 8 7 6 5 4 3
1
2 to 3
4 to 11
The meaning and value range of the parameters within the ARP are defined in 3GPP TS 29.212 [29]. The bits within the octet 5 are:
- Bit 1 PVI (Pre-emption Vulnerability): See 3GPP TS 29.212[29], clause 5.3.47 Pre-emption-Vulnerability AVP.
- Bit 2 spare
- Bits 3 to 6 PL (Priority Level): See 3GPP TS 29.212[29], clause 5.3.45 ARP-Value AVP. PL encodes each priority level defined for the
ARP-Value AVP as the binary value of the priority level.
- Bit 7 PCI (Pre-emption Capability): See 3GPP TS 29.212[29], clause 5.3.46 Pre-emption-Capability AVP.
- Bit 8 spare.
Bits
The sending entity copies the value part of the MSISDN into the Value field of the MSISDN IE.
Octets 5 to (n+4) represent the MSISDN value is in international number format as described in ITU-T Rec E.164 [25] and 3GPP TS 29.002
[41]. 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 [41]) and is encoded as TBCD digits, i.e. digits from 0 through 9 are encoded "0000" to
"1001". When there is an odd number of digits, bits 8 to 5 of the last octet are encoded with the filler "1111".
Bits
Length = n
Spare Instance
IPv4 or IPv6 Address
IP Address
The Length field may have only two values (4 or 16) that determine if the Value field contains IPv4 or IPv6 address.
Type = 120 (decimal)
Length = n
Spare Instance
PLMN ID
PLMN ID
Octets 5-7 shall contain a non-transparent copy of the " PLMN Identity" parameter in 3GPP TS 36.413
Bits
Type = 74 (decimal)
Type = 155 (decimal)
Length = n
Spare Instance
PL
These octet(s) is/are present only if explicitly specified
Allocation/Retention Priority (ARP)
International Mobile Equipment Identity (and Software Version) (IMEI(SV))
Bits
Type = 154 (Decimal)
Length = 8
IMEI(SV)
The structure of the IMEI and IMEISV are defined in sub clause 6.2 of 3GPP TS 23.003 [2]. The "IMEI(SV)" field shall contain the
IMEISV if it is available. If only the IMEI is available, then the IMEI shall be placed in the IMEI(SV) field and the last semi octet of octet
11 shall be set to "1111". Both IMEI and IMEISV are TBCD encoded. Bits 5 to 8 of octet n+3 (where n represents the octet of the
IMEI(SV) being encoded) encodes digit 2n, bits 1 to 4 of octet n+3 encodes digit 2n-1 (i.e the order of digits is swapped in each octet
compared to the digit order defined in 3GPP TS 23.003 [2]). Digits are packed contiguously with no internal padding
Pre-emption-Vulnerability AVP:
The Pre-emption Vulnerability AVP (AVP code 1048) is of type Enumerated. If it is provided within the QoS-Information AVP, the AVP
defines whether a service data flow can lose the resources assigned to it in order to admit a service data flow with higher priority level. If it
is provided within the Default-EPS-Bearer-QoS AVP, the AVP defines whether the default bearer can lose the resources assigned to it in
order to admit a pre-emption capable bearer with a higher priority level.
The following values are defined:
PRE-EMPTION_VULNERABILITY_ENABLED (0)
This value indicates that the resources assigned to the service data flow or bearer can be pre-empted and allocated to a service data flow or
bearer with a higher priority level. This is the default value applicable if this AVP is not supplied.
PRE-EMPTION_VULNERABILITY_DISABLED (1)
This value indicates that the resources assigned to the service data flow or bearer shall not be pre-empted and allocated to a service data
flow or bearer with a higher priority level.
Priority-Level AVP (All access types):
The Priority-Level AVP (AVP code 1046) is of type Unsigned 32. The AVP is used for deciding whether a bearer establishment or
modification request can be accepted or needs to be rejected in case of resource limitations (typically used for admission control of GBR
traffic). The AVP can also be used to decide which existing bearers to pre-empt during resource limitations. The priority level defines the
relative importance of a resource request.
Values 1 to 15 are defined, with value 1 as the highest level of priority.
Values 1 to 8 should only be assigned for services that are authorized to receive prioritized treatment within an operator domain. Values 9 to
15 may be assigned to resources that are authorized by the home network and thus applicable when a UE is roaming.
Pre-emption-Capability AVP:
The Pre-emption-Capability AVP (AVP code 1047) is of type Enumerated. If it is provided within the QoS-Information AVP, the AVP
defines whether a service data flow can get resources that were already assigned to another service data flow with a lower priority level. If it
is provided within the Default-EPS-Bearer-QoS AVP, the AVP defines whether the default bearer can get resources that were already
assigned to another bearer with a lower priority level.
The following values are defined:
PRE-EMPTION_CAPABILITY_ENABLED (0)
This value indicates that the service data flow or bearer is allowed to get resources that were already assigned to another service data flow
or bearer with a lower priority level.
PRE-EMPTION_CAPABILITY_DISABLED (1)
This value indicates that the service data flow or bearer is not allowed to get resources that were already assigned to another service data
flow or bearer with a lower priority level. This is the default value applicable if this AVP is not supplied
2 1
2 1
BCE CS
2 1
Spec: 29.274
Section : 8
Bits
Type = 51 (decimal)
Length = n
Instance
Session Transfer Number for Single Radio Voice Call Continuity (STN-SR)
Spec: 29.280
Section : 6
Cause
Octets 5 to (n+4) represent the IMSI value in international number format as described in ITU-T Rec E.164 [25], encoded as TBCD digits,
i.e. digits from 0 through 9 are encoded "0000" to "1001". When there is an odd number of digits, bits 8 to 5 of the last octet are encoded
with the filler "1111". The maximum number of digits is 15.
International Mobile Subscriber Identity (IMSI)
Bits
Type = 2 (decimal)
Length = n
Instance
Number digit 3

Number digit m-1

Bits
Type = 1 (decimal)
Length = n
Instance
Number digit 1
NANPI
Digit 1
Cause value
Type of the offending IE
Length of the offending IE = 0
Cause is a variable length IE, which may have either of the following two lengths values:
- If n = 2, a = 0 and the Cause IE shall be 6 octets long. Therefore, octets "a(n+1) to a(n+4)" will not be present.
- If n = 6, a = 1 and the Cause IE will be 10 octets long.
2 1
2 1
When the target network is GERAN, the Transparent container field contains the value part of the Layer 3 Information IE defined in 3GPP
TS 48.008 [8], i.e., octets 3 to n, excluding octet 1 (Element ID) and octet 2 (Length).
When the target network is UTRAN, this container carries the Target RNC to Source RNC Transparent Container IE defined in 3GPP TS
25.413 [9]. The Transparent container field contains a transparent copy of the corresponding ASN.1/PER IE (see subclauses 8.2.2 and 8.48
in 3GPP TS 29.274 [3]).
When the target network is E-UTRAN, the container carries the Target eNB To Source eNB Transparent Container IE defined in 3GPP TS
36.413 [14]. The Transparent container field contains a transparent copy of the corresponding ASN.1/PER IE (see subclauses 8.2.2 and 8.48
in 3GPP TS 29.274 [3]).
The receiver of this Information Element shall ignore the length of the transparent container encoded in octet 5 and shall derive the actual
length of the container from the length encoded in octets 2 to 3 minus 1.
For backward compatibility, the sender of this Information Element shall set the octet 5 to the actual length of the transparent container if
the size of the container is smaller or equal to 255 octets, and to the value "255" otherwise
Length = n
Instance
Length of the Transparent container
Transparent container
Digit (m-1)
Octet 5 contains the Nature of Address and Numbering Plan Indicator (NANPI) of the "AddressString" ASN.1 type (see 3GPP TS 29.002
[11]). Octets 6 to (n+4) contain the actual STN-SR (digits of an address encoded as a TBCD-STRING as in the "AddressString" ASN.1
type). For an odd number of STN-SR digits, bits 8 to 5 of the last octet are encoded with the filler "1111".
Bits
Source to Target Transparent Container
The Source to Target Transparent Container contains information that shall be transferred transparently by CN entities from the source RAN
to the target RAN.
When the target network is GERAN, the Transparent container field contains the value part of the Old BSS to New BSS Information IE
defined in 3GPP TS 48.008 [8], i.e. octets 3 to n, excluding octet 1 (Element ID) and octet 2 (Length).
The receiver of this Information Element shall ignore the length of the transparent container encoded in octet 5 and shall derive the actual
length of the container from the length encoded in octets 2 to 3 minus 1.
For backward compatibility, the sender of this Information Element shall set the octet 5 to the actual length of the transparent container if
the size of the container is smaller or equal to 255 octets, and to the value "255" otherwise.
Bits
Type = 53 (decimal)
Target to Source Transparent Container
Type = 52 (decimal)
Length = n (decimal)
Instance
Length of the Transparent container
Transparent container
8 7 6 5 4
2 1
0 ES
spare IND
0 PS
37 spare capa.
1 0 LCSVA
5 spare CAP
1
34
1
110
total: 189
2 1
2 1
Mobile station classmark 2
REFERENCE:: 24.008: Sec:10.5.1.6 (More detailed Table there)
Element Identifier: 0 0 1 0 0 0 0 0 Mobile Station classmark 3
The purpose of the Mobile Station Classmark 3 information element is to provide the network with information concerning aspects of the
mobile station. The contents might affect the manner in which the network handles the operation of the mobile station. The Mobile Station
Classmark information indicates general mobile station characteristics and it shall therefore, except for fields explicitly indicated, be
independent of the frequency band of the channel it is sent on.
The Mobile Station Classmark 3 is a type 4 information element with a maximum of 34 octets length.
The value part of a Mobile Station Classmark 3 information element is coded as shown in figure 10.5.1.7/3GPP TS 24.008 and table
10.5.1.7/3GPP TS 24.008
SS Screen.
Indicator
SM ca
pabi.
CM3 UCS2 SoLSA
Mobile station classmark 2 IEI
Length of mobile station classmark 2 contents
Revision
level
A5/1
SRVCC Cause
MM Context for UTRAN SRVCC
Bits
Type = 56 (decimal)
Length = 1
Length of the Mobile Station Classmark 2
Mobile Station Classmark 2
Length of the Mobile Station Classmark 3
Mobile Station Classmark 3
Length of the Supported Codec List
Supported Codec List
Bits
Type = 55 (decimal)
Length = n
Instance
KSI
CS
Length of the Mobile Station Classmark 2
Mobile Station Classmark 2
Length of the Mobile Station Classmark 3
Mobile Station Classmark 3
Length of the Supported Codec List
Supported Codec List
Instance
eKSI
CK
SRVCC
IK
SRVCC
Bits
Type = 54 (decimal)
Length = n
MM Context for E-UTRAN (v)SRVCC
No of
Octets
calculated
CK
CS
IK
CS
Kc
CKSN
CS
2 1
2 1
2 1
2 1
ICS EmInd
Cell ID
Target Global Cell ID
RNC ID
Target RNC ID
Bits
Type = 58 (decimal)
Length = n (decimal)
Instance
SRVCC Cause value
Bits
Type = 57 (decimal)
Length = n (decimal)
Instance
Instance
Bits
Type = 59 (decimal)
Length = n (decimal)
Instance
Tunnel Endpoint Identifier for Control Plane (TEID-C)
These octet(s) is/are present only if explicitly specified
Tunnel Endpoint Identifier for Control Plane (TEID-C)
Bits
Type = 60 (decimal)
Length = n
Instance
These octet(s) is/are present only if explicitly specified
Sv Flags
The following bits within Octet 5 indicate:
- Bit 1 EmInd (Emergency Indicator): This flag is used to indicate the IMS emergency session.
- Bit 2 ICS (IMS Centralized Service): This flag is used to request ICS support.
- Bit 3 STI (Session Transfer Indicator): This flag is used to indicate IMS session transfer has been invoked.
- Bit 4 VHO (vSRVCC flag): This flag is used to indicate that the vSRVCC HO is requested by the MME.
Service Area Identifier
2 1
2 1
2 1
Bits
Type = 61 (decimal)
Location Area Code (LAC)
Service Area Code (SAC)
These octet(s) is/are present only if explicitly specified
The Location Area Code (LAC) consists of 2 octets. Bit 8 of Octet 8 is the most significant bit and bit 1 of Octet 9 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 10 is the most significant bit and bit 1 of Octet 11 the least significant bit.
The SAC is defined by the operator
Bits
Length = n
Instance
MCC digit 1
MCC digit 3
MNC digit 1
Mobile Equipment (ME) Identity
Mobile Equipment Identity (MEI)
The ME Identity field contains either the IMEI or the IMEISV as defined in clause 6.2 of 3GPP TS 23.003 [2]. It is encoded as specified in
clause 7.7.53 of 3GPP TS 29.060 [4], beginning with octet 4 of Figure 7.7.53.1.
The IMEI(SV) digits are encoded using BCD coding where IMEI is 15 BCD digits and IMEISV is 16 BCD digits. For IMEI, bits 5 to 8 of
the last octet shall be filled with an end mark coded as '1111'
Bits
Type = 76 (decimal)
Length = n
Instance
Number digit 1
Type = 75 (decimal)
Length = n
Instance
Number digit 3

Number digit m-1

MSISDN
The sending entity copies the value part of the MSISDN into the Value field of the MSISDN IE.
Octets 5 to (n+4) represent the MSISDN value is in international number format as described in ITU-T Rec E.164 [25] and 3GPP TS 29.002
[41]. 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 [41]) and is encoded as TBCD digits, i.e. digits from 0 through 9 are encoded "0000" to
"1001". When there is an odd number of digits, bits 8 to 5 of the last octet are encoded with the filler "1111".
Spec: 29.274
Section : 8
2 1
Spare PVI
2 1
2 1
2 1
The meaning and value range of the parameters within the ARP are defined in 3GPP TS 29.212 [29]. The bits within the octet 5 are:
- Bit 1 PVI (Pre-emption Vulnerability): See 3GPP TS 29.212[29], clause 5.3.47 Pre-emption-Vulnerability AVP.
- Bit 2 spare
- Bits 3 to 6 PL (Priority Level): See 3GPP TS 29.212[29], clause 5.3.45 ARP-Value AVP. PL encodes each priority level defined for the
ARP-Value AVP as the binary value of the priority level.
- Bit 7 PCI (Pre-emption Capability): See 3GPP TS 29.212[29], clause 5.3.46 Pre-emption-Capability AVP.
- Bit 8 spare.
Bits
The sending entity copies the value part of the MSISDN into the Value field of the MSISDN IE.
Octets 5 to (n+4) represent the MSISDN value is in international number format as described in ITU-T Rec E.164 [25] and 3GPP TS 29.002
[41]. 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 [41]) and is encoded as TBCD digits, i.e. digits from 0 through 9 are encoded "0000" to
"1001". When there is an odd number of digits, bits 8 to 5 of the last octet are encoded with the filler "1111".
Bits
Length = n
Instance
IPv4 or IPv6 Address
IP Address
The Length field may have only two values (4 or 16) that determine if the Value field contains IPv4 or IPv6 address.
Type = 120 (decimal)
Length = n
Instance
PLMN ID
PLMN ID
Octets 5-7 shall contain a non-transparent copy of the " PLMN Identity" parameter in 3GPP TS 36.413
Bits
Type = 74 (decimal)
Type = 155 (decimal)
Length = n
Instance
These octet(s) is/are present only if explicitly specified
Allocation/Retention Priority (ARP)
International Mobile Equipment Identity (and Software Version) (IMEI(SV))
Bits
Type = 154 (Decimal)
Length = 8
IMEI(SV)
The structure of the IMEI and IMEISV are defined in sub clause 6.2 of 3GPP TS 23.003 [2]. The "IMEI(SV)" field shall contain the
IMEISV if it is available. If only the IMEI is available, then the IMEI shall be placed in the IMEI(SV) field and the last semi octet of octet
11 shall be set to "1111". Both IMEI and IMEISV are TBCD encoded. Bits 5 to 8 of octet n+3 (where n represents the octet of the
IMEI(SV) being encoded) encodes digit 2n, bits 1 to 4 of octet n+3 encodes digit 2n-1 (i.e the order of digits is swapped in each octet
compared to the digit order defined in 3GPP TS 23.003 [2]). Digits are packed contiguously with no internal padding
Pre-emption-Vulnerability AVP:
The Pre-emption Vulnerability AVP (AVP code 1048) is of type Enumerated. If it is provided within the QoS-Information AVP, the AVP
defines whether a service data flow can lose the resources assigned to it in order to admit a service data flow with higher priority level. If it
is provided within the Default-EPS-Bearer-QoS AVP, the AVP defines whether the default bearer can lose the resources assigned to it in
order to admit a pre-emption capable bearer with a higher priority level.
The following values are defined:
PRE-EMPTION_VULNERABILITY_ENABLED (0)
This value indicates that the resources assigned to the service data flow or bearer can be pre-empted and allocated to a service data flow or
bearer with a higher priority level. This is the default value applicable if this AVP is not supplied.
PRE-EMPTION_VULNERABILITY_DISABLED (1)
This value indicates that the resources assigned to the service data flow or bearer shall not be pre-empted and allocated to a service data
flow or bearer with a higher priority level.
Priority-Level AVP (All access types):
The Priority-Level AVP (AVP code 1046) is of type Unsigned 32. The AVP is used for deciding whether a bearer establishment or
modification request can be accepted or needs to be rejected in case of resource limitations (typically used for admission control of GBR
traffic). The AVP can also be used to decide which existing bearers to pre-empt during resource limitations. The priority level defines the
relative importance of a resource request.
Values 1 to 15 are defined, with value 1 as the highest level of priority.
Values 1 to 8 should only be assigned for services that are authorized to receive prioritized treatment within an operator domain. Values 9 to
15 may be assigned to resources that are authorized by the home network and thus applicable when a UE is roaming.
Pre-emption-Capability AVP:
The Pre-emption-Capability AVP (AVP code 1047) is of type Enumerated. If it is provided within the QoS-Information AVP, the AVP
defines whether a service data flow can get resources that were already assigned to another service data flow with a lower priority level. If it
is provided within the Default-EPS-Bearer-QoS AVP, the AVP defines whether the default bearer can get resources that were already
assigned to another bearer with a lower priority level.
The following values are defined:
PRE-EMPTION_CAPABILITY_ENABLED (0)
This value indicates that the service data flow or bearer is allowed to get resources that were already assigned to another service data flow
or bearer with a lower priority level.
PRE-EMPTION_CAPABILITY_DISABLED (1)
This value indicates that the service data flow or bearer is not allowed to get resources that were already assigned to another service data
flow or bearer with a lower priority level. This is the default value applicable if this AVP is not supplied
1
octet 1
octet 2
octet 3
octet 4
octet 5
The purpose of the Mobile Station Classmark 2 information element is to provide the network with information
concerning aspects of both high and low priority of the mobile station equipment. This affects the manner in which
the network handles the operation of the mobile station. The Mobile Station Classmark information indicates
general mobile station characteristics and it shall therefore, except for fields explicitly indicated, be independent of
the frequency band of the channel it is sent on.
NOTE 1: Owing to backward compatibility problems, bit 8 of octet 4 should not be used unless it is also checked
that the bits 8, 7 and 6 of octet 3 are not "0 0 0".
Mobile station classmark 2
REFERENCE:: 24.008: Sec:10.5.1.6 (More detailed Table there)
Element Identifier: 0 0 1 0 0 0 0 0 Mobile Station classmark 3
The purpose of the Mobile Station Classmark 3 information element is to provide the network with information concerning aspects of the
mobile station. The contents might affect the manner in which the network handles the operation of the mobile station. The Mobile Station
Classmark information indicates general mobile station characteristics and it shall therefore, except for fields explicitly indicated, be
independent of the frequency band of the channel it is sent on.
The Mobile Station Classmark 3 is a type 4 information element with a maximum of 34 octets length.
The value part of a Mobile Station Classmark 3 information element is coded as shown in figure 10.5.1.7/3GPP TS 24.008 and table
10.5.1.7/3GPP TS 24.008
SM ca
pabi.
VBS VGCS FC
SoLSA CMSP A5/3 A5/2
3 2
Mobile station classmark 2 IEI
Length of mobile station classmark 2 contents
A5/1
RF power
capability
8
Codec Bitmap for (SysID x), bits 1 to 8
Codec Bitmap for (SysID x), bits 9 to 16
The Supported Codec List information element is a type 4 information element with a minimum
length of 5 octets and a maximum length of m+3 octets.
RAM: 6 codec of GSM
Each of (2+16) octets
total size: 2 + 18*6 = 110 octets max
Codec Bitmap for (SysID 2), bits 9 to 16
System Identification x (SysID x)
Codec Bitmap for SysID 1, bits 1 to 8
Codec Bitmap for SysID 1, bits 9 to 16
System Identification 2 (SysID 2)
Length Of Bitmap for (SysID 2)
Codec Bitmap for (SysID 2), bits 1 to 8
The purpose of the Mobile Station Classmark 2 information element is to provide the network with information
concerning aspects of both high and low priority of the mobile station equipment. This affects the manner in which
the network handles the operation of the mobile station. The Mobile Station Classmark information indicates
general mobile station characteristics and it shall therefore, except for fields explicitly indicated, be independent of
the frequency band of the channel it is sent on.
NOTE 1: Owing to backward compatibility problems, bit 8 of octet 4 should not be used unless it is also checked
that the bits 8, 7 and 6 of octet 3 are not "0 0 0".
Mobile station classmark 2
REFERENCE:: 24.008: Sec:10.5.1.6 (More detailed Table there)
Supported Codec List IEI
Length Of Supported Codec list
System Identification 1 (SysID 1)
Length Of Bitmap for SysID 1
Length Of Bitmap for (SysID x)
7 6 5 4 3 2 1
octet 1
octet 2
octet 3
octet 5
octet 6
octet j
octet j+2
octet j+3
octet m
octet m+2
octet m+3
octet m+1
Codec Bitmap for (SysID x), bits 1 to 8
Codec Bitmap for (SysID x), bits 9 to 16
The Supported Codec List information element is a type 4 information element with a minimum
length of 5 octets and a maximum length of m+3 octets.
RAM: 6 codec of GSM
Each of (2+16) octets
total size: 2 + 18*6 = 110 octets max
Codec Bitmap for (SysID 2), bits 9 to 16
System Identification x (SysID x)
Supported Codec List
Spec: 24.008
octet 4
Codec Bitmap for SysID 1, bits 1 to 8
Codec Bitmap for SysID 1, bits 9 to 16
System Identification 2 (SysID 2)
Length Of Bitmap for (SysID 2) octet j+1
Codec Bitmap for (SysID 2), bits 1 to 8
Supported Codec List IEI
Length Of Supported Codec list
System Identification 1 (SysID 1)
Length Of Bitmap for SysID 1
Length Of Bitmap for (SysID x)
Binary
Notation
0x00h 0x0000.0000 GSM_FR
0x01h 0x0000.0001 GSM_HR
0x02h 0x0000.0010 GSM_EFR
0x03h 0x0000.0011 (GSM) FR_AMR
0x04h 0x0000.0100 (GSM) HR_AMR
0x05h 0x0000.0101 UMTS_AMR
0x06h 0x0000.0110 UMTS_AMR2
0x07h 0x0000.0111 TDMA_EFR
0x08h 0x0000.1000 PDC_EFR
0x09h 0x0000.1001 (GSM) FR_AMR-WB
0x0Ah 0x0000.1010 UMTS_AMR-WB
0x0Bh 0x0000.1011 OHR_AMR
0x0Ch 0x0000.1100 OFR_AMR-WB
0x0Dh 0x0000.1101 OHR_AMR-WB
0x0Eh 0x0000.1110 Spare, for future use
0x0Fh 0x0000.1111 Codec Extension For AoIP and TFO
0x0001.0000
0x1111.1100
0xFDh 0x1111.1101 CSData For AoIP only
0xFEh 0x1111.1110 MuMe2 For OoBTC only
0xFFh 0x1111.1111 MuMe For OoBTC only
Hexadecim
al Notation
Codec Name Remark
0x10h
0xFCh
Spare, for future use
Up to date the following Code Points are defined:
Spec: 26.103
Cause
value
(decimal)
0
Reserved. Shall not be sent and if received the Cause
shall be treated as an invalid IE
1 Reserved
2 Local Detach
3 Complete Detach
4 RAT changed from 3GPP to Non-3GPP
5 ISR deactivation
6 Error Indication received from RNC/eNodeB/S4-SGSN
7 IMSI Detach Only
8 Reactivation Requested
9 PDN reconnection to this APN disallowed
10 Access changed from Non-3GPP to 3GPP
11 PDN connection inactivity timer expires
12 PGW not responding
13 Network Failure
14 QoS parameter mismatch
15
Spare. This value range shall be used by Cause values
in an initial/request message. See NOTE 5.
16 Request accepted
17 Request accepted partially
18 New PDN type due to network preference.
19 New PDN type due to single address bearer only.
20 to 63
Spare. This value range shall be used by Cause values
in an acceptance response/triggered message
64 Context Not Found
65 Invalid Message Format
66 Version not supported by next peer
67 Invalid length
68 Service not supported
69 Mandatory IE incorrect
70 Mandatory IE missing
71 Shall not be used. See NOTE 2 and NOTE 3.
72 System failure
73 No resources available
74 Semantic error in the TFT operation
75 Syntactic error in the TFT operation
76 Semantic errors in packet filter(s)
77 Syntactic errors in packet filter(s)
78 Missing or unknown APN
Cause
Message Type Meaning
Request / Initial message
Acceptance in a Response /
triggered message. See NOTE 1.
Rejection in a Response / triggered
message. See NOTE 1.
79 Shall not be used. See NOTE 2 and NOTE 3.
80 GRE key not found
81 Relocation failure
82 Denied in RAT
83 Preferred PDN type not supported
84 All dynamic addresses are occupied
85
UE context without TFT already activated. See NOTE
6.
86 Protocol type not supported
87 UE not responding. See NOTE 7.
88 UE refuses
89 Service denied. See NOTE 7.
90 Unable to page UE
91 No memory available
92 User authentication failed
93 APN access denied no subscription
94 Request rejected (reason not specified)
95 P-TMSI Signature mismatch
96 IMSI/IMEI not known
97 Semantic error in the TAD operation
98 Syntactic error in the TAD operation
99 Shall not be used. See NOTE 2 and NOTE 3.
100 Remote peer not responding
101 Collision with network initiated request
102 Unable to page UE due to Suspension
103 Conditional IE missing
104
APN Restriction type Incompatible with currently active
PDN connection
105
Invalid overall length of the triggered response
message and a piggybacked initial message
106 Data forwarding not supported
107 Invalid reply from remote peer
108 Fallback to GTPv1
109 Invalid peer
110
Temporarily rejected due to handover/TAU/RAU
procedure in progress
111 Modifications not limited to S1-U bearers
112
Request rejected for a PMIPv6 reason (see 3GPP TS
29.275 [26]).
113 APN Congestion
114 Bearer handling not supported
115 UE already re-attached. See NOTE 7.
116 Multiple PDN connections for a given APN not allowed
117 Target access restricted for the subscriber
118 Shall not be used. See NOTE 2 and NOTE 3.
119 MME/SGSN refuses due to VPLMN Policy
Rejection in a Response / triggered
message. See NOTE 1.
120 GTP-C Entity Congestion
121 to 239
Spare. For future use in a triggered/response message
See NOTE 4.
Request / Initial message 240 to 255
Spare. For future use in an initial/request message.
See NOTE 5.
Cause value
(decimal)
0
1
2
3
4
5
6
7
8
9
10
11-255
Failure in Radio Interface Procedure
Permanent session leg establishment error
Temporary session leg establishment error
NOTE 2: Subclause 7.7.8 "Semantically incorrect Information Element" specifies quite strict
handling of the reserved values and therefore this table shall not contain any reserved values.
NOTE 3: This value was used in earlier versions of the spec. If received, it shall be interpreted
as unspecified rejection cause. Unspecified/unrecognized rejection cause shall be treated in
the same ways as the cause value 94 "Request rejected (reason not specified)".
NOTE 4: This value is or may be used in the newer versions of the spec. If the receiver cannot
comprehend the value, it shall be interpreted as unspecified rejection cause.
Unspecified/unrecognized rejection cause shall be treated in the same ways as the cause
value 94 "Request rejected (reason not specified)".
NOTE 5: This value is or may be used in the newer versions of the spec. If the receiver cannot
comprehend the value, it shall be interpreted as an unspecified request/initial message cause.
Unspecified/unrecognized cause handling in a request/initial message shall be implementation
dependent (e.g. may be ignored).
NOTE 6: This Cause value is only used over the S4, S5 and S8 interface in the secondary
PDP Context Activation procedure (see 9.2.2.1.1A in 3GPP TS 23.060 [4]).
NOTE 7: This cause value may also be used by a Downlink Data Notification Failure
Indication, which is an initial message.
Rejection in a Response / triggered
message. See NOTE 1.
NOTE 1: The listed cause values for rejection in a response/triggered message can be also
used for request messages if the request message is triggered by a command message.
SRVCC Cause
Spare. This value range is reserved for SRVCC Cause values
Meaning
Reserved. Shall not be sent and if received the Cause shall be
treated as an invalid IE
Unspecified
Handover/Relocation cancelled by source system
Handover /Relocation Failure with Target system
Handover/Relocation Target not allowed
Unknown Target ID
Target Cell not available
No Radio Resources Available in Target Cell
8 7 6 5 4 3 2 1
LEN
3
4
3
19
3 to 8
3
3-n
n
3-n
3
3
5
3-n
4
8 7 6 5 4 3 2 1
The D-RNTI field element shall only be present when a Radio Resource Reserve Handover procedure is applied over the Iur-g interface (see 3GPPTS43.130).
Field Element identifier
Length
0000 0011
0000 0100
0000 0101
0000 1111
0110 1111
1001 0101
Extra information
Octet 2 is a binary indication of the length of the rest of the field element.
Octet 3 is coded as follows:
Last used E-UTRAN PLMN ID
FIELD ELEMENT
cdma2000 Capability Information
Cell Load Information Group
VGCS talker mode
PS Indication
D-RNTI
IRAT Measurement Configuration
Old BSS to New BSS information
The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator
octet and may be set to zero.
The Old BSS to New BSS information elements field is made up of 0 or more Field Elements listed in the table shown
below.
Field elements may occur in any order in the Old BSS to New BSS information elements field.
The construction of the Field Elements allows the receiver to ignore unknown Field Elements.
Due to backward compatibility issues Field Elements in the "Old BSS to New BSS information" may duplicate
information from Information Elements in the HANDOVER REQUEST, when this occurs and the new BSS detects an
inconsistency between this information then the information contained in the "Old BSS to New BSS information" shall
take precedence as long as the coding is understood by the new BSS.
Reception of an erroneous "Old BSS to New BSS information" shall not cause a rejection of the HANDOVER
REQUEST message; the "Old BSS to New BSS information" information element shall be discarded and the handover
resource allocation procedure shall continue.
Extra information
Current Channel Type 2
Target cell radio information
Element identifier
Length
Old BSS to New BSS information elements
0000 0110
0000 0111
0000 1000
0000 1011
0000 1101
1111 1110
Field Element Identifier Coding
0000 0001
0000 0010
GPRS Suspend information
MultiRate configuration information
Dual Transfer Mode information
Inter RAT Handover Info
8 7 6 5 4 3 2 1
UE-prob lcs prec
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
Current Channel type 2
This Field Element contains a description of the channel allocated to the MS.
The channel mode field is coded as follows:
Bit
4321
0000 signalling only
0001 speech (full rate or half rate)
0110 data, 14.5 kbit/s radio interface rate
0011 data, 12.0 kbit/s radio interface rate
0100 data, 6.0 kbit/s radio interface rate
0101 data, 3.6 kbit/s radio interface rate
1111 is reserved
All other values indicate that no information is provided.
Bits 8 to 5 are spare.
Target cell radio information
spare
This field element provides a general flag mechanism that allows the old BSS to indicate to the new BSS flag information.
Bit 8 to 4 are flags that indicate no information.
prec = Pre-emption Recommendation:
0 The old BSS recommends that this allocation request should not cause a pre-emption an existing connection;
1 The old BSS recommends that this allocation request is allowed to preempt an existing connection based on the information
supplied in the Priority information element, if available
In the case the "prec" bit is not present or the Extra Information field element is not present then the new BSS should run pre-
emption as specified by the Priority information element, if available.
In the case where the Priority information element is not present in the request then the "prec" element, if present, shall be ignored.
lcs = Location Services (LCS) information:
0 No ongoing LCS procedure;
1 An ongoing LCS procedure was interrupted by handover. The new BSS may notify the SMLC when the handover is completed.
UE-prob = support of handover to UMTS for this MS:
0 This MS supports handover to UMTS;
1 This MS does not support handover to UMTS
Field Element identifier
Length
Channel mode
Channel field
Field Element identifier
Length
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
7 6 5 4
Dual Transfer Mode information
Spare EGPRS ind
Octet 2 is a binary indication of the length of the rest of the element.
Octet 3 is coded as follows:
Field Element identifier
Length
Length of SRN
Suspend reference number
Field Element identifier
Length
Rest of element coded as in 3GPPTS44.018, not including 3GPPTS44.018 element identifier or
3GPPTS44.018 octet length value
8 3
This Field Element contains the contents of the Gb interface SUSPEND ACK PDU
The coding of the fields are not relevant to 3GPP TS 24.008.
MultiRate configuration Information
This Field Element contains a description of the multi-rate speech codec configuration currently used
RAI
Gb interface SRN IEI
RXLEV-NCELL
Field Element identifier
Length
Gb interface TLLI IEI
Bit 8 to 7 is spare, set to 0
Bit 6 to 1 is the RXLEV-NCELL field.
The RXLEV-NCELL field is coded as the binary representation of a value N. N corresponds according to
the mapping defined in TS. 3GPP TS 45.008 to the received signal strength on the target cell.
GPRS Suspend Information
Length of TLLI
TLLI
Gb interface RAI IEI
Length of RAI
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
Octets 3-n are encoded as Inter RAT Handover Info as defined in 3GPPTS25.331.
cdma2000 Capability Information
Field Element identifier
cdma2000 capability information
Octets 3-n are encoded as octets 3-n of the cdma2000 Classmark Change message defined in 3GPPTS44.018.
Cell Load Information Group
Field Element identifier
Length
Inter RAT Handover Info
Field Element identifier
Length
This Field Element contains information about a mobile in dual transfer mode. This information may be used for the target BSS to allocate the resources for the RR connection
(e.g. TCH/H, TCH in an EGPRS transceiver).
Octet Bit 1 is the dual transfer mode indicator. It indicates whether the MS is in dedicated mode or in dual transfer mode. This bit shall also be used in the case of handover to
GERAN from another RAT to indicate the allocation of resources for the CS and PS domain in the old cell. It is coded as follows:
Bit
1
0 The MS has resources allocated exclusively for the CS domain in the old cell
1 The MS has resources allocated for both the CS and PS domains in the old cell
Bit 2 is the single timeslot operation indicator. It indicates whether the MS has a TCH/H and a PDCH/H; see 3GPP TS 45.002. It is coded as follows:
Bit
2
0 The MS is in multislot operation in the old cell
1 The MS is in single timeslot operation in the old cell
Bit 3 is the EGPRS indicator. It is coded as follows:
Bit
3
0 The MS has no TBF using E-GPRS in the old cell
1 The MS has a TBF using E-GPRS in the old cell
Bits 8 to 4 of octet 3 are spare.
Inter RAT Handover Info
Length
Cell Identifier
Cell Load Information Group elements
This field element contains the load information of the source cell for either the Downlink or the Uplink or both as well
as the source cell identifier the included cell load information corresponds to during a handover procedure.
The Cell Identifier identifies the source cell. The structure and encoding of Cell Identifier is described in sub-clause
3.2.2.17. For a GERAN source cell, Cell identification discriminator = 0000. For a UTRAN source cell, Cell
identification discriminator = 1100.
LEN
8
8
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
8 7 6 5 4 3 2 1
The VGCS talker mode information element contains the RR mode of the VGCS talker and the Group cipher key
number in use on the voice group channel
Octet 3 is coded as follows:
RR mode
Bit
8 7
0 0 dedicated mode (i.e. dedicated channel)
0 1 group transmit mode (i.e. voice group channel)
Other values are reserved for future use.
Length
RR mode Group cipher key number
0
spare
Field Element identifier
Length
This field element contains information about the downlink traffic load of a cell during a handover procedure. It refers
either to the source or target cell depending on the direction of the message containing the Information Element where
this field element is present
Uplink Cell Load Information
Field Element identifier
Element identifier
Cell Load Information
Length
Cell Load Information
This field element contains information about the uplink traffic load of a cell during a handover procedure. It refers
either to the source or target cell depending on the direction of the message containing the Information Element where
this field element is present.
VGCS talker mode
The Cell Load Information Group elements field is made up of zero or more of the field elements listed below.
FIELD ELEMENT
Downlink Cell Load Information
Uplink Cell Load Information
Downlink Cell Load Information
7 6 5 4
REP_QUANT
7 6 4
8 7 6 5 4 3 2 1
Cell Load Information
Field Element identifier
MNC dig 2
This information element provides the BSS with the last used E-UTRAN PLMN used by a CSFB MS before CSFB took place. This information
element can help to redirect the MS back to the last used E-UTRAN PLMN by selecting the suitable dedicated target E-UTRAN frequencies/cells
if applicable.
MNC dig 1
REPORTING_THRESHOLD
IRAT Measurement Configuration
8 3
Field Element identifier
Spare
MNC dig 3
Last used E-UTRAN PLMN ID
MCC dig 3
The IRAT Measurement Configuration IE is used to indicate to the BSS which frequency measurement results of the
source RAT shall be collected after a successful inter-system handover. The IRAT Measurement Configuration IE is
used by the source RAT to specify the E-UTRA frequencies to be reported back to the source RAT (each of them
associated with a measurement bandwidth), the minimum radio quality and the period of time that the measurements
should last before triggering a HO Report for unnecessary handover to another RAT.
NOTE 1: HO Report is defined in 3GPP TS 36.413 [57].
NOTE 2: The functionality of Unnecessary IRAT HO is described in 3GPP TS 36.300 [59].
REPORTING_THRESHOLD: defines the reporting threshold to be used for measurement results analysis according
to REP_QUANT. This threshold is used to compare against the measurement results received from the MS. It is a value
between 0 and 63 encoded on 6 bits according to 3GPP TS 45.008 [58] sub-section 8.1.5.4.
REP_QUANT: indicates the measurement quantity for E-UTRAN cells coded as follows: 0=RSRP 1=RSRQ.
Measurement _Duration: defines (in seconds) how long the BSS shall collect the measurements results received from
the MS after a successful inter-RAT handover. It is a number in binary representation ranging from 1 to 100
E- ARFCN: designates a specific E-UTRA frequency for which the target RAT should continue to collect the
measurement results received from MS of this frequency. It is coded as a number in binary representation ranging from
0 to 65535.
Measurement Bandwidth: defines the measurement bandwidth of the E-UTRA frequency signalled in the two previous
octets. It is coded on 3 bits according to 3GPP TS 44.018 [32].
8 5 3
Element identifier
MCC dig 1 MCC dig 2
Spare Measurement Bandwidth
E-ARFCN
Spare Measurement Bandwidth

E-ARFCN
Spare Measurement Bandwidth
E-ARFCN
Length
Measurement_Duration
Length
Cell Capacity Class Value
Load Value
RT Load Value
NRT Load Information Value
This field element contains the load information of a specific (serving or target) cell for either the Downlink or the Uplink.
Cell Capacity Class Value is the value that classifies the cell capacity with regards to the other cells. It only indicates resources that
are configured for traffic purposes. Cell Capacity Class Value may take binary coded integer values from and including 1 up to and
including 100. Other values shall be considered as an error. Value 1 shall indicate the minimum cell capacity, and 100 shall indicate
the maximum cell capacity. There should be linear relation between cell capacity and Cell Capacity Class Value.
Load Value contains the total cell load relative to the maximum planned load. It is defined as the load percentage of the Cell
Capacity Class. Load Value may take binary coded integer values from and including 0 up to and including 100. Other values shall
be considered as an error. Value 0 shall indicate the minimum load, and 100 shall indicate the maximum load. Load Value should be
measured on a linear scale.
RT Load Value indicates in percents the ratio of the load generated by Real Time traffic relative to the measured Load Value. Real
Time traffic corresponds to the Conversational and Streaming traffic classes. RT Load Value may take binary coded integer values
from and including 0 up to and including 100. Other values shall be considered as no information.
NRT Load Information Value indicates the load situation on the cell for Non Real-Time traffic. Non Real-Time traffic corresponds
to the Interactive and Background traffic classes. NRT Load Information Value may take binary coded integer values from and
including 0 up to and including 3. Other values shall be considered as no information. The values shall be interpreted as:
Value 0: NRT load is low.
Value 1: NRT load is medium.
Value 2: NRT load is high. (Probability to admit a new user is low.)
Value 3: NRT overload. (Probability to admit a new user is low, packets are discarded and the source is recommended to reduce the
data flow.)
octet 1
octet 2
octet 3-n
octet 1
octet 2
octet 3
Personal Review
Not Required
Need Discussion
The D-RNTI field element shall only be present when a Radio Resource Reserve Handover procedure is applied over the Iur-g interface (see 3GPPTS43.130).
The length indicator (octet 2) is a binary number indicating the absolute length of the contents after the length indicator
octet and may be set to zero.
The Old BSS to New BSS information elements field is made up of 0 or more Field Elements listed in the table shown
below.
Field elements may occur in any order in the Old BSS to New BSS information elements field.
The construction of the Field Elements allows the receiver to ignore unknown Field Elements.
Due to backward compatibility issues Field Elements in the "Old BSS to New BSS information" may duplicate
information from Information Elements in the HANDOVER REQUEST, when this occurs and the new BSS detects an
inconsistency between this information then the information contained in the "Old BSS to New BSS information" shall
take precedence as long as the coding is understood by the new BSS.
Reception of an erroneous "Old BSS to New BSS information" shall not cause a rejection of the HANDOVER
REQUEST message; the "Old BSS to New BSS information" information element shall be discarded and the handover
resource allocation procedure shall continue.
octet 3
octet 1
octet 2
octet 3
octet 4
octet 1
octet 2
This Field Element contains a description of the channel allocated to the MS.
The channel mode field is coded as follows:
Bit
4321
0000 signalling only
0001 speech (full rate or half rate)
0110 data, 14.5 kbit/s radio interface rate
0011 data, 12.0 kbit/s radio interface rate
0100 data, 6.0 kbit/s radio interface rate
0101 data, 3.6 kbit/s radio interface rate
1111 is reserved
All other values indicate that no information is provided.
Bits 8 to 5 are spare.
The channel field is coded as follows:
Bit:
4321
0001 SDCCH
1000 1 Full rate TCH
1001 1 Half rate TCH
1010 2 Full Rate TCHs
1011 3 Full Rate TCHs
1100 4 Full Rate TCHs
1101 5 Full Rate TCHs
1110 6 Full Rate TCHs
1111 7 Full Rate TCHs
0100 8 Full Rate TCHs
0000 is reserved
All other values indicate that no information is provided.
Bits 8 to 5 are spare
This field element provides a general flag mechanism that allows the old BSS to indicate to the new BSS flag information.
Bit 8 to 4 are flags that indicate no information.
prec = Pre-emption Recommendation:
0 The old BSS recommends that this allocation request should not cause a pre-emption an existing connection;
1 The old BSS recommends that this allocation request is allowed to preempt an existing connection based on the information
supplied in the Priority information element, if available
In the case the "prec" bit is not present or the Extra Information field element is not present then the new BSS should run pre-
emption as specified by the Priority information element, if available.
In the case where the Priority information element is not present in the request then the "prec" element, if present, shall be ignored.
lcs = Location Services (LCS) information:
0 No ongoing LCS procedure;
1 An ongoing LCS procedure was interrupted by handover. The new BSS may notify the SMLC when the handover is completed.
UE-prob = support of handover to UMTS for this MS:
0 This MS supports handover to UMTS;
1 This MS does not support handover to UMTS
octet 3
octet 3
octet 1
octet 2
octet 3
octet 4
octet 5-5+m
octet 6+m
octet 7+m
octet 7+m-n
octet n+1
octet n+2
octet n+3-p
octet 1
octet 2
octet 3-n
2
octet 3 DTM Ind STO Ind
1
Field Element identifier octet 1
Length octet 2
This Field Element contains the contents of the Gb interface SUSPEND ACK PDU
The coding of the fields are not relevant to 3GPP TS 24.008.
This Field Element contains a description of the multi-rate speech codec configuration currently used
octet 1
octet 2
octet 3-n
octet 1
octet 2
octet 3-n
8 7 6 5 4 3
octet 1
octet 2
octet 3-n
octet (n+1)-
(n+m)
Cell identification
Cell Identifier
The coding of "Cell identification discriminator" (bits 1 to 4 of octet 3) is a binary number indicating if the whole
or a part of Cell Global Identification, CGI, according to 3GPP TS 23.003 is used for cell identification in octet 4-
n. The "Cell identification discriminator" is coded as follows:
0000 The whole Cell Global Identification, CGI, is used to identify the cell.
0001 Location Area Code, LAC, and Cell Identity, CI, is used to identify the cell.
0010 Cell Identity, CI, is used to identify the cell.
0011 No cell is associated with the transaction.
1011 Serving Area Identity, SAI, is used to identify the Serving Area of UE within UTRAN or cdma2000 or to
indicate an E-UTRAN source
The coding of octet 4-n depends on the Cell identification discriminator (octet 3).
Element identifier
Length
Spare
Cell identification
discriminator
Octets 3-n are encoded as octets 3-n of the cdma2000 Classmark Change message defined in 3GPPTS44.018.
This Field Element contains information about a mobile in dual transfer mode. This information may be used for the target BSS to allocate the resources for the RR connection
(e.g. TCH/H, TCH in an EGPRS transceiver).
Octet Bit 1 is the dual transfer mode indicator. It indicates whether the MS is in dedicated mode or in dual transfer mode. This bit shall also be used in the case of handover to
GERAN from another RAT to indicate the allocation of resources for the CS and PS domain in the old cell. It is coded as follows:
Bit
1
0 The MS has resources allocated exclusively for the CS domain in the old cell
1 The MS has resources allocated for both the CS and PS domains in the old cell
Bit 2 is the single timeslot operation indicator. It indicates whether the MS has a TCH/H and a PDCH/H; see 3GPP TS 45.002. It is coded as follows:
Bit
2
0 The MS is in multislot operation in the old cell
1 The MS is in single timeslot operation in the old cell
Bit 3 is the EGPRS indicator. It is coded as follows:
Bit
3
0 The MS has no TBF using E-GPRS in the old cell
1 The MS has a TBF using E-GPRS in the old cell
Bits 8 to 4 of octet 3 are spare.
This field element contains the load information of the source cell for either the Downlink or the Uplink or both as well
as the source cell identifier the included cell load information corresponds to during a handover procedure.
The Cell Identifier identifies the source cell. The structure and encoding of Cell Identifier is described in sub-clause
3.2.2.17. For a GERAN source cell, Cell identification discriminator = 0000. For a UTRAN source cell, Cell
identification discriminator = 1100.
octet 1
octet 2
octet 3-n
octet 1
octet 2
octet 3-n
octet 1
octet 2
The VGCS talker mode information element contains the RR mode of the VGCS talker and the Group cipher key
number in use on the voice group channel
Octet 3 is coded as follows:
RR mode
Bit
8 7
0 0 dedicated mode (i.e. dedicated channel)
0 1 group transmit mode (i.e. voice group channel)
Other values are reserved for future use.
Group cipher key number
Bit
6 5 4 3
0 0 0 0 no ciphering
0 0 0 1 cipher key number 1
0 0 1 0 cipher key number 2
0 0 1 1 cipher key number 3
0 1 0 0 cipher key number 4
0 1 0 1 cipher key number 5
0 1 1 0 cipher key number 6
0 1 1 1 cipher key number 7
1 0 0 0 cipher key number 8
1 0 0 1 cipher key number 9
1 0 1 0 cipher key number A
1 0 1 1 cipher key number B
1 1 0 0 cipher key number C
1 1 0 1 cipher key number D
1 1 1 0 cipher key number E
1 1 1 1 cipher key number F
octet 3
The coding of "Cell identification discriminator" (bits 1 to 4 of octet 3) is a binary number indicating if the whole
or a part of Cell Global Identification, CGI, according to 3GPP TS 23.003 is used for cell identification in octet 4-
n. The "Cell identification discriminator" is coded as follows:
0000 The whole Cell Global Identification, CGI, is used to identify the cell.
0001 Location Area Code, LAC, and Cell Identity, CI, is used to identify the cell.
0010 Cell Identity, CI, is used to identify the cell.
0011 No cell is associated with the transaction.
1011 Serving Area Identity, SAI, is used to identify the Serving Area of UE within UTRAN or cdma2000 or to
indicate an E-UTRAN source
The coding of octet 4-n depends on the Cell identification discriminator (octet 3).
This field element contains information about the downlink traffic load of a cell during a handover procedure. It refers
either to the source or target cell depending on the direction of the message containing the Information Element where
this field element is present
This field element contains information about the uplink traffic load of a cell during a handover procedure. It refers
either to the source or target cell depending on the direction of the message containing the Information Element where
this field element is present.
The Cell Load Information Group elements field is made up of zero or more of the field elements listed below.
2 1
2 1
octet 1
octet 2
octet 3
octet 4
octet 1
This information element provides the BSS with the last used E-UTRAN PLMN used by a CSFB MS before CSFB took place. This information
element can help to redirect the MS back to the last used E-UTRAN PLMN by selecting the suitable dedicated target E-UTRAN frequencies/cells
if applicable.
MNC dig 1
REPORTING_THRESHOLD
Field Element identifier
MCC dig 3
The IRAT Measurement Configuration IE is used to indicate to the BSS which frequency measurement results of the
source RAT shall be collected after a successful inter-system handover. The IRAT Measurement Configuration IE is
used by the source RAT to specify the E-UTRA frequencies to be reported back to the source RAT (each of them
associated with a measurement bandwidth), the minimum radio quality and the period of time that the measurements
should last before triggering a HO Report for unnecessary handover to another RAT.
NOTE 1: HO Report is defined in 3GPP TS 36.413 [57].
NOTE 2: The functionality of Unnecessary IRAT HO is described in 3GPP TS 36.300 [59].
REPORTING_THRESHOLD: defines the reporting threshold to be used for measurement results analysis according
to REP_QUANT. This threshold is used to compare against the measurement results received from the MS. It is a value
between 0 and 63 encoded on 6 bits according to 3GPP TS 45.008 [58] sub-section 8.1.5.4.
REP_QUANT: indicates the measurement quantity for E-UTRAN cells coded as follows: 0=RSRP 1=RSRQ.
Measurement _Duration: defines (in seconds) how long the BSS shall collect the measurements results received from
the MS after a successful inter-RAT handover. It is a number in binary representation ranging from 1 to 100
E- ARFCN: designates a specific E-UTRA frequency for which the target RAT should continue to collect the
measurement results received from MS of this frequency. It is coded as a number in binary representation ranging from
0 to 65535.
Measurement Bandwidth: defines the measurement bandwidth of the E-UTRA frequency signalled in the two previous
octets. It is coded on 3 bits according to 3GPP TS 44.018 [32].
3
Element identifier
MCC dig 1
octet m+2 Measurement Bandwidth
octet 10

E-ARFCN octets m-(m+1)

Measurement Bandwidth

E-ARFCN octets 5-6

octet 7
octets 8-9
Measurement Bandwidth
E-ARFCN
octet 1
Length octet 2
octet 3
Measurement_Duration octet 4
octet 2
octet 3
octet 4
octet 5
octet 6
This field element contains the load information of a specific (serving or target) cell for either the Downlink or the Uplink.
Cell Capacity Class Value is the value that classifies the cell capacity with regards to the other cells. It only indicates resources that
are configured for traffic purposes. Cell Capacity Class Value may take binary coded integer values from and including 1 up to and
including 100. Other values shall be considered as an error. Value 1 shall indicate the minimum cell capacity, and 100 shall indicate
the maximum cell capacity. There should be linear relation between cell capacity and Cell Capacity Class Value.
Load Value contains the total cell load relative to the maximum planned load. It is defined as the load percentage of the Cell
Capacity Class. Load Value may take binary coded integer values from and including 0 up to and including 100. Other values shall
be considered as an error. Value 0 shall indicate the minimum load, and 100 shall indicate the maximum load. Load Value should be
measured on a linear scale.
RT Load Value indicates in percents the ratio of the load generated by Real Time traffic relative to the measured Load Value. Real
Time traffic corresponds to the Conversational and Streaming traffic classes. RT Load Value may take binary coded integer values
from and including 0 up to and including 100. Other values shall be considered as no information.
NRT Load Information Value indicates the load situation on the cell for Non Real-Time traffic. Non Real-Time traffic corresponds
to the Interactive and Background traffic classes. NRT Load Information Value may take binary coded integer values from and
including 0 up to and including 3. Other values shall be considered as no information. The values shall be interpreted as:
Value 0: NRT load is low.
Value 1: NRT load is medium.
Value 2: NRT load is high. (Probability to admit a new user is low.)
Value 3: NRT overload. (Probability to admit a new user is low, packets are discarded and the source is recommended to reduce the
data flow.)
2 1 8 7 6 5 4
octet 1
octet 2
octet 4-n
Coding of Cell Identification for Cell identification discriminator = 0000
MCC dig 2 MCC dig 1
MNC dig 3 MCC dig 3
The octets 4-8 are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification
information element'.
The octet 5 bits 5-8 are filled by '1111' if 2 digit MNC is used.
The octets 9-10 are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'
MNC dig 2 MNC dig 1
LAC
LAC cont.
CI value
CI value cont
octet 3
Cell identification
Cell Identifier
The coding of "Cell identification discriminator" (bits 1 to 4 of octet 3) is a binary number indicating if the whole
or a part of Cell Global Identification, CGI, according to 3GPP TS 23.003 is used for cell identification in octet 4-
n. The "Cell identification discriminator" is coded as follows:
0000 The whole Cell Global Identification, CGI, is used to identify the cell.
0001 Location Area Code, LAC, and Cell Identity, CI, is used to identify the cell.
0010 Cell Identity, CI, is used to identify the cell.
0011 No cell is associated with the transaction.
1011 Serving Area Identity, SAI, is used to identify the Serving Area of UE within UTRAN or cdma2000 or to
indicate an E-UTRAN source
The coding of octet 4-n depends on the Cell identification discriminator (octet 3).
Element identifier
Length
Cell identification
discriminator
The octets 4-8 are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification
information element'.
The octet 5 bits 5-8 are filled by '1111' if 2 digit MNC is used.
The octets 9-10 are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'
The coding of "Cell identification discriminator" (bits 1 to 4 of octet 3) is a binary number indicating if the whole
or a part of Cell Global Identification, CGI, according to 3GPP TS 23.003 is used for cell identification in octet 4-
n. The "Cell identification discriminator" is coded as follows:
0000 The whole Cell Global Identification, CGI, is used to identify the cell.
0001 Location Area Code, LAC, and Cell Identity, CI, is used to identify the cell.
0010 Cell Identity, CI, is used to identify the cell.
0011 No cell is associated with the transaction.
1011 Serving Area Identity, SAI, is used to identify the Serving Area of UE within UTRAN or cdma2000 or to
indicate an E-UTRAN source
The coding of octet 4-n depends on the Cell identification discriminator (octet 3).
3 2 1 8 7 6 5
octet 4
octet 5
octet 6
octet 7
octet 8
octet 9
octet 10 8 7 6 5
Coding of Cell Identification for Cell identification discriminator = 0000
MCC dig 1
MCC dig 3
The octets 4-8 are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification
information element'.
The octet 5 bits 5-8 are filled by '1111' if 2 digit MNC is used.
The octets 9-10 are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'
Coding of Cell Identification for Cell identification discriminator = 0001
LAC
LAC cont.
CI value
CI value cont
Coding of Cell Identification for Cell identification discriminator = 0010
CI value
CI value cont
MNC dig 1
LAC
LAC cont.
CI value
CI value cont
The coding of SAI is defined in 3GPP TS 25.413, without the protocol extension container.
NOTE: A default value of SAI can be defined in the MSC Server enhanced for SRVCC to be used
as identifier of an E-UTRAN source in case of SRVCC.
The octets 4-8 are coded as shown in 3GPP TS 24.008, Table 'Location Area Identification
information element'.
The octet 5 bits 5-8 are filled by '1111' if 2 digit MNC is used.
The octets 9-10 are coded as shown in 3GPP TS 24.008, Table 'Cell Identity information element'
Coding of Cell Identification for Cell identification discriminator = 1011
4 3 2 1
octet 4
octet 5
octet 6
octet 7
4 3 2 1
octet 4
octet 5
Coding of Cell Identification for Cell identification discriminator = 0001
LAC
LAC cont.
CI value
CI value cont
Coding of Cell Identification for Cell identification discriminator = 0010
CI value
CI value cont
The coding of SAI is defined in 3GPP TS 25.413, without the protocol extension container.
NOTE: A default value of SAI can be defined in the MSC Server enhanced for SRVCC to be used
as identifier of an E-UTRAN source in case of SRVCC.
Coding of Cell Identification for Cell identification discriminator = 1011