O.4 Information elements
24.0083GPPCore network protocolsMobile radio interface Layer 3 specificationRelease 18Stage 3TS
O.4.1 Personal ME identifier
The purpose of the personal ME identifier is to discriminate between MEs used by the same user (see TS 24.279 [116], subclause 4.2).
NOTE: As the personal ME identifier is generated randomly, it is not guaranteed that it uniquely identifies a specific ME used by the same user.
The personal ME identifier has the form PMI-XXXX, where XXXX is a 4-digit hexadecimal number. Only the hexadecimal number XXXX is coded in the personal ME identifier information element.
The personal ME identifier information element is coded as shown in figure O.2/3GPP TS 24.008 and table O.2/3GPP TS 24.008.
The personal ME identifier is a type 3 information element with 3 octets length.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
Personal ME identifier IEI |
octet 1 |
|||||||
|
ME identifier digit 2 |
ME identifier digit 1 |
octet 2 |
||||||
|
ME identifier digit 4 |
ME identifier digit 3 |
octet 3 |
||||||
Figure O.2/3GPP TS 24.008 Personal ME identifier
Table O.2/3GPP TS 24.008: Personal ME identifier
|
ME identifier digits (octets 2, 3) |
|||||
|
Bits 1 to 4 or bits 5 to 8, respectively, contain the binary encoding of a hexadecimal ME identifier digit. Digit 1 is the leftmost digit in the 4-digit hexadecimal number XXXX. |
|||||
|
Bits |
ME identifier digit value |
||||
|
4 |
3 |
2 |
1 |
Or |
|
|
8 |
7 |
6 |
5 |
||
|
0 |
0 |
0 |
0 |
0 |
|
|
0 |
0 |
0 |
1 |
1 |
|
|
0 |
0 |
1 |
0 |
2 |
|
|
0 |
0 |
1 |
1 |
3 |
|
|
0 |
1 |
0 |
0 |
4 |
|
|
0 |
1 |
0 |
1 |
5 |
|
|
0 |
1 |
1 |
0 |
6 |
|
|
0 |
1 |
1 |
1 |
7 |
|
|
1 |
0 |
0 |
0 |
8 |
|
|
1 |
0 |
0 |
1 |
9 |
|
|
1 |
0 |
1 |
0 |
A |
|
|
1 |
0 |
1 |
1 |
B |
|
|
1 |
1 |
0 |
0 |
C |
|
|
1 |
1 |
0 |
1 |
D |
|
|
1 |
1 |
1 |
0 |
E |
|
|
1 |
1 |
1 |
1 |
F |
|
O.4.2 Radio environment capability
The purpose of the radio environment capability is to provide information about the current radio environment of the MS.
The radio environment capability information element is coded as shown in figure O.3/3GPP TS 24.008 and table O.3/3GPP TS 24.008.
The radio environment capability is a type 1 information element with 1 octet length.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||||||
|
Radio environment capability |
0 spare |
0 spare |
0 Spare |
CS/ |
octet 1 |
|||||||||
Figure O.3/3GPP TS 24.008 Radio environment capability contents
Table O.3/3GPP TS 24.008: Radio environment capability contents
|
CS and PS capability (octet 1, bit 1) |
|||
|
The CS and PS capability indicates whether the MS is in a radio environment that supports simultaneous use of CS and PS services (see 3GPP TS 24.279 [116]). |
|||
|
0 |
simultaneous use of CS and PS services not supported |
||
|
1 |
simultaneous use of CS and PS services supported |
||
|
Bits 2 to 4 of octet 1 are spare and shall be coded as zero. |
|||
O.4.3 UE capability version
The purpose of the UE capability version is to inform the receiving MS that the capability of the sending MS has changed since the last UE capability exchange (see 3GPP TS 24.279 [116]).
The UE capability version information element is coded as shown in figure O.4/3GPP TS 24.008 and table O.4/3GPP TS 24.008.
The UE capability version has the form UCV-XX, where XX is a 2-digit hexadecimal number. Only the hexadecimal number XX is coded in the UE capability version information element.
The UE capability version information element is coded as shown in figure O.4/3GPP TS 24.008 and table O.4/3GPP TS 24.008.
The UE capability version is a type 3 information element with 2 octets length.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
UE capability version IEI |
octet 1 |
|||||||
|
UE capability version digit 2 |
UE capability version digit 1 |
octet 2 |
||||||
Figure O.4/3GPP TS 24.008: UE capability version
Table O.4/3GPP TS 24.008: UE capability version
|
UE capability version digits(octet 2) |
|||||
|
Bits 1 to 4 and bits 5 to 8, respectively, contain the binary encoding of a 2-digit hexadecimal UE capability version. Digit 1 is the leftmost digit. |
|||||
|
Bits |
UE capability version digit value |
||||
|
4 |
3 |
2 |
1 |
Or |
|
|
8 |
7 |
6 |
5 |
||
|
0 |
0 |
0 |
0 |
0 |
|
|
0 |
0 |
0 |
1 |
1 |
|
|
0 |
0 |
1 |
0 |
2 |
|
|
0 |
0 |
1 |
1 |
3 |
|
|
0 |
1 |
0 |
0 |
4 |
|
|
0 |
1 |
0 |
1 |
5 |
|
|
0 |
1 |
1 |
0 |
6 |
|
|
0 |
1 |
1 |
1 |
7 |
|
|
1 |
0 |
0 |
0 |
8 |
|
|
1 |
0 |
0 |
1 |
9 |
|
|
1 |
0 |
1 |
0 |
A |
|
|
1 |
0 |
1 |
1 |
B |
|
|
1 |
1 |
0 |
0 |
C |
|
|
1 |
1 |
0 |
1 |
D |
|
|
1 |
1 |
1 |
0 |
E |
|
|
1 |
1 |
1 |
1 |
F |
|
O.4.4 IM Status
The purpose of the IM Status is to provide information about the IMS capability and registration state of a specific public user identity and it MS.
NOTE: The definition of what is a public user identity can be found in 3GPP TS 23.003 [10].
The IM Status information element is coded as shown in figure O.5/3GPP TS 24.008 and table O.5/3GPP TS 24.008.
The IM Status is a type 1 information element with 1 octet length.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||||||
|
IM Status IEI |
0 Spare |
0 spare |
IM |
octet 1 |
|||||||||
Figure O.5/3GPP TS 24.008 IM Status contents
Table O.5/3GPP TS 24.008: IM Status contents
|
IM Status (octet 1) |
|||
|
Bits |
|||
|
2 |
1 |
||
|
0 |
0 |
MS is not IM subsystem capable |
|
|
0 |
1 |
MS is IM subsystem registered |
|
|
1 |
0 |
MS is IM subsystem capable and willing to register to IM subsystem (NOTE 1) |
|
|
1 |
1 |
MS is IM subsystem capable but will not register to IM subsystem (NOTE 2) |
|
|
Bits 3 to 4 of octet 1 are spare and shall be coded as zero. |
|||
|
NOTE 1: This value indicates that a terminal can be configured to allow IMS registration without user intervention when required, for example when prompted by receiving an IM Status of "MS is IM subsystem registered" or "MS is IM subsystem capable and willing to register to IM subsystem" during establishment of a CS call. NOTE 2: This value indicates that the terminal will not IMS register without user permission. |
|||