10.5.3 Mobility management information elements

04.083GPPMobile radio interface Layer 3 specificationRelease 1998TS

10.5.3.1 Authentication parameter RAND

The purpose of the Authentication Parameter RAND information element is to provide the mobile station with a non-predictable number to be used to calculate the authentication response signature SRES and the ciphering key Kc.

The Authentication Parameter RAND information element is coded as shown in figure 10.5.75/3GPP TS 04.08 and table 10.5.89/3GPP TS 04.08.

The Authentication Parameter RAND is a type 3 information element with 17 octets length.

8 7 6 5 4 3 2 1

+———————————————–+

│ Authentication parameter RAND IEI │ octet 1

+———————————————–│

│ │

│ RAND value │ octet 2

:

:

│ │ octet 17

│ │

+———————————————–+

Figure 10.5.75/3GPP TS 04.08: Authentication Parameter RAND information element

Table 10.5.89/3GPP TS 04.08: Authentication Parameter RAND information element

+—————————————————–+

│ RAND value (octet 2, 3,… and 17) │

│ The RAND value consists of 128 bits. Bit 8 of octet │

│ 2 is the most significant bit while bit 1 of octet │

│ 17 is the least significant bit. │

+—————————————————–+

10.5.3.2 Authentication parameter SRES

The purpose of the authentication parameter SRES information element is to provide the network with the authentication response signature calculated in the mobile station.

The Authentication Parameter SRES information element is coded as shown in figure 10.5.76/3GPP TS 04.08 and table 10.5.90/3GPP TS 04.08.

The Authentication Parameter SRES is a type 3 information element with 5 octets length.

8 7 6 5 4 3 2 1

+———————————————–+

│ Authentication parameter SRES IEI │ octet 1

+———————————————–│

│ │

│ SRES value │ octet 2

:

:

│ │ octet 5

│ │

+———————————————–+

Figure 10.5.76/3GPP TS 04.08: Authentication Parameter SRES information element

Table 10.5.90/3GPP TS 04.08: Authentication Parameter SRES information element

+——————————————————+

│ SRES value (octet 2, 3, 4 and 5) │

│ The SRES value consists of 32 bits. Bit 8 of octet 2 │

│ is the most significant bit while bit 1 of octet 5 │

│ is the least significant bit. │

+——————————————————+

10.5.3.3 CM service type

The purpose of the CM Service Type information element is to specify which service is requested from the network.

The CM Service Type information element is coded as shown in figure 10.5.77/3GPP TS 04.08 and table 10.5.91/3GPP TS 04.08.

The CM Service Type is a type 1 information element.

8 7 6 5 4 3 2 1

+———————————————–+

│ CM service type IEI │ service type │ octet 1

+———————————————–+

Figure 10.5.77/3GPP TS 04.08: CM Service Type information element

Table 10.5.91/3GPP TS 04.08: CM Service Type information element

+—————————————————–+

│ Service type (octet 1) │

│ Bits │

│ 4 3 2 1 │

│ 0 0 0 1 Mobile originating call establishment │

│ or packet mode connection establishment │

│ 0 0 1 0 Emergency call establishment │

│ 0 1 0 0 Short message service │

│ 1 0 0 0 Supplementary service activation │

│ 1 0 0 1 Voice group call establishment │

│ 1 0 1 0 Voice broadcast call establishment │

│ 1 0 1 1 Location Services │

│ │

│ All other values are reserved. │

+—————————————————–+

10.5.3.4 Identity type

The purpose of the Identity Type information element is to specify which identity is requested.

The Identity Type information element is coded as shown in figure 10.5.78/3GPP TS 04.08 and table 10.5.92/3GPP TS 04.08.

The Identity Type is a type 1 information element .

8 7 6 5 4 3 2 1

+———————————————–+

│ Identity type IEI │ 0 │type of identity │ octet 1

│ │spare│ │

+———————————————–+

Figure 10.5.78/3GPP TS 04.08: Identity Type information element

Table 10.5.92/3GPP TS 04.08: Identity Type information element

+————————————————–+

│ Type of identity (octet 1) │

│ Bits │

│ 3 2 1 │

│ 0 0 1 IMSI │

│ 0 1 0 IMEI │

│ 0 1 1 IMEISV │

│ 1 0 0 TMSI │

│ │

│ All other values are reserved. │

+————————————————–+

10.5.3.5 Location updating type

The purpose of the Location Updating Type information element is to indicate whether a normal updating, a periodic updating or an IMSI attach is wanted. It may also indicate that a follow-on request has been received from the mobile station CM layer.

The Location Updating Type information element is coded as shown in figure 10.5.79/3GPP TS 04.08 and table 10.5.93/3GPP TS 04.08.

The Location Updating Type is a type 1 information element.

8 7 6 5 4 3 2 1

+———————————————–+

│ Location updating │ FOR │ 0 │ LUT │ octet 1

│ type IEI │ │spare│ │

+———————————————–+

Figure 10.5.79/3GPP TS 04.08: Location Updating Type information element

Table 10.5.93/3GPP TS 04.08: Location Updating Type information element

+———————————————–+

│ LUT (octet 1) │

│ Bits │

│ 2 1 │

│ 0 0 Normal location updating │

│ 0 1 Periodic updating │

│ 1 0 IMSI attach │

│ 1 1 Reserved │

│ │

│ FOR (octet 1) │

│ The Follow-On Request bit (FOR) is coded as │

│ follows: │

│ Bit │

│ 4 │

│ 0 No follow-on request pending │

│ 1 Follow-on request pending │

+———————————————–+

10.5.3.5a Network Name

The purpose of this information element is to pass a text string to the mobile station.

The Network Name information element is coded as shown in figure 10.5.80/3GPP TS 04.08 and table 10.5.94/3GPP TS 04.08.

The Network Name is a type 4 information element with a minimum length of 3 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 04.06).

8 7 6 5 4 3 2 1

+———————————————–+

│ │ Network Name IEI │ octet 1

+———————————————–│

│ │

│ Length of Network Name contents │ octet 2

+———————————————–│

│ ext │ coding scheme │Add│ Number of spare │

│ 1 │ │CI │bits in last octet│ octet 3

+———————————————–│

│ │

│ │ octet 4

│ Text String │

│ │

│ │

│ │ octet n

+———————————————–+

Figure 10.5.80/3GPP TS 04.08: Network Name information element

Table 10.5.94/3GPP TS 04.08: Network Name information element

Number of spare bits in last octet (octet 3, bits 1 to 3)

0 0 1 bit 8 is spare and set to "0" in octet n

0 1 0 bits 7 and 8 are spare and set to "0" in octet n

0 1 1 bits 6 to 8(inclusive) are spare and set to "0" in octet n

1 0 0 bits 5 to 8(inclusive) are spare and set to "0" in octet n

1 0 1 bits 4 to 8(inclusive) are spare and set to "0" in octet n

1 1 0 bits 3 to 8(inclusive) are spare and set to "0" in octet n

1 1 1 bits 2 to 8(inclusive) are spare and set to "0" in octet n

0 0 0 this field carries no information about the number of spare bits in octet n

Add CI (octet 3, bit 4)

0 The MS should not add the letters for the Country’s Initials to the text string

1 The MS should add the letters for the Country’s Initials and a separator
(e.g. a space) to the text string

Coding Scheme (octet 3, bits 5-7)

0 0 0 Cell Broadcast data coding scheme defined in 3GPP TS 03.38

0 0 1 UCS2 (16 bit) [72]

0 1 0

to reserved

1 1 1

Text String (octet 4 to octet n, inclusive)
Encoded according to the Coding Scheme defined by octet 3, bits 5-7

10.5.3.6 Reject cause

The purpose of the Reject Cause information element is to indicate the reason why a request from the mobile station is rejected by the network.

The Reject Cause information element is coded as shown in figure 10.5.81/3GPP TS 04.08 and table 10.5.95/3GPP TS 04.08.

The Reject Cause is a type 3 information element with 2 octets length.

8 7 6 5 4 3 2 1

+———————————————–+

│ Reject cause IEI │ octet 1

+———————————————–│

│ │

│ reject cause value │ octet 2

+———————————————–+

Figure 10.5.81/3GPP TS 04.08: Reject Cause information element

Table 10.5.95/3GPP TS 04.08: Reject Cause information element

+——————————————————-+

│ Reject cause value (octet 2) │

│ Bits │

│ 8 7 6 5 4 3 2 1 │

│ 0 0 0 0 0 0 1 0 IMSI unknown in HLR │

│ 0 0 0 0 0 0 1 1 Illegal MS │

│ 0 0 0 0 0 1 0 0 IMSI unknown in VLR │

│ 0 0 0 0 0 1 0 1 IMEI not accepted │

│ 0 0 0 0 0 1 1 0 Illegal ME │

│ 0 0 0 0 1 0 1 1 PLMN not allowed │

│ 0 0 0 0 1 1 0 0 Location Area not allowed │

│ 0 0 0 0 1 1 0 1 Roaming not allowed in this │

│ location area │

│ 0 0 0 1 0 0 0 1 Network failure │

│ 0 0 0 1 0 1 1 0 Congestion │

│ 0 0 1 0 0 0 0 0 Service option not supported │

│ 0 0 1 0 0 0 0 1 Requested service option │

│ not subscribed │

│ 0 0 1 0 0 0 1 0 Service option temporarily │

│ out of order │

│ 0 0 1 0 0 1 1 0 Call cannot be identified │

│ 0 0 1 1 0 0 0 0 } │

│ to } retry upon entry into a new cell │

│ 0 0 1 1 1 1 1 1 } │

│ 0 1 0 1 1 1 1 1 Semantically incorrect message │

│ 0 1 1 0 0 0 0 0 Invalid mandatory information │

│ 0 1 1 0 0 0 0 1 Message type non-existent │

│ or not implemented │

│ 0 1 1 0 0 0 1 0 Message type not compatible with │

│ the protocol state │

│ 0 1 1 0 0 0 1 1 Information element non-existent │

│ or not implemented │

│ 0 1 1 0 0 1 0 0 Conditional IE error │

│ 0 1 1 0 0 1 0 1 Message not compatible with │

│ the protocol state │

│ 0 1 1 0 1 1 1 1 Protocol error, unspecified │

│ │

│ Any other value received by the mobile station │

│ shall be treated as 0010 0010, ‘Service option │

│ temporarily out of order’. Any other value received │

│ by the network shall be treated as 0110 1111, │

│ ‘Protocol error, unspecified’. │

│ │

│ NOTE: The listed reject cause values are defined in │

│ Annex G. │

+——————————————————-+

10.5.3.7 Follow-on Proceed

The purpose of the Follow-on Proceed information element is to indicate that an MM connection may be established on an existing RR connection.

The Follow-on Proceed information element is coded as shown in figure 10.5.82/3GPP TS 04.08.

The Follow-on Proceed is a type 2 information element.

8 7 6 5 4 3 2 1

+———————————————–+

│ Follow-on Proceed IEI │ octet 1

+———————————————–+

Figure 10.5.82/3GPP TS 04.08: Follow-on Proceed information element

10.5.3.8 Time Zone

The purpose of this information element is to encode the offset between universal time and local time in steps of 15 minutes.

The Time Zone information element is coded as shown in figure 10.5.83/3GPP TS 04.08 and table 10.5.96/3GPP TS 04.08.

The Time Zone is a type 3 information element with a length of 2 octets.

8 7 6 5 4 3 2 1

+———————————————–+

│ │ Time Zone IEI │octet 1

+———————————————–│

│ Time Zone │

│ │octet 2

+———————————————–+

Figure 10.5.83/3GPP TS 04.08: Time Zone information element

Table 10.5.96/3GPP TS 04.08: Time Zone information element

+————————————————————–+

│ │

│ Time Zone (octet 2, bits 1-8) │

│This field uses the same format as the Timezone field used in │

│ the TP-Service-Centre-Time-Stamp, which is defined in GSM │

│03.40, and its value shall be set as defined in 3GPP TS 02.42 │

│ . │

+————————————————————–+

10.5.3.9 Time Zone and Time

The purpose of the timezone part of this information element is to encode the offset between universal time and local time in steps of 15 minutes.

The purpose of the time part of this information element is to encode the universal time at which this information element may have been sent by the network.

The Time Zone and Time information element is coded as shown in figure 10.5.84/3GPP TS 04.08 and table 10.5.97/3GPP TS 04.08.

The Time Zone and Time is a type 3 information element with a length of 8 octets.

8 7 6 5 4 3 2 1

+———————————————–+

│ │ Time Zone and Time IEI │octet 1

+———————————————–│

│ Year │

│ │octet 2

+———————————————–│

│ Month │

│ │octet 3

+———————————————–│

│ Day │

│ │octet 4

+———————————————–│

│ Hour │

│ │octet 5

+———————————————–│

│ Minute │

│ │octet 6

+———————————————–│

│ Second │

│ │octet 7

+———————————————–│

│ Time zone │

│ │octet 8

+———————————————–+

Figure 10.5.84/3GPP TS 04.08: Time Zone and Time information element

Table 10.5.97/3GPP TS 04.08: Timezone and Time information element

Year (octet 2, bits 1-8)

This field uses the same format as the Year field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 03.40, and its value shall be set as defined in 3GPP TS 02.42.

Month (octet 3, bits 1-8)

This field uses the same format as the Month field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 03.40, and its value shall be set as defined in 3GPP TS 02.42.

Day (octet 4, bits 1-8)

This field uses the same format as the Day field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 03.40, and its value shall be set as defined in 3GPP TS 02.42.

Hour (octet 5, bits 1-8)

This field uses the same format as the Hour field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 03.40, and its value shall be set as defined in 3GPP TS 02.42.

Minute (octet 6, bits 1-8)

This field uses the same format as the Minute field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 03.40, and its value shall be set as defined in 3GPP TS 02.42.

Second (octet 7, bits 1-8)

This field uses the same format as the Second field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 03.40, and its value shall be set as defined in 3GPP TS 02.42.

Time Zone (octet 8, bits 1-8)

This field uses the same format as the Time Zone field used in the TP-Service-Centre-Time-Stamp, which is defined in 3GPP TS 03.40, and its value shall be set as defined in 3GPP TS 02.42.

NOTE: Due to ambiguities in earlier versions of the protocol specifications, some mobile stations may interpret the received NITZ time as local time. This may result in incorrect time settings in the mobile.

10.5.3.10 CTS permission

The purpose of the CTS permission information element is to indicate that the mobile station is allowed to use GSM-Cordless Telephony System in the Location Area. The CTS permission information element is coded as shown in figure 10.5.84a/3GPP TS 04.08.

The CTS permission is a type 2 information element.

8 7 6 5 4 3 2 1

+———————————————–+

| CTS Permission IEI | octet 1

+———————————————–+

Figure 10.5.84a/3GPP TS 04.08: CTS permission information element

10.5.3.11 LSA Identifier

This element uniquely identifies a LSA.

The LSA Identifier information element is coded as shown in figure 10.68c/3GPP TS 04.08.

The LSA Identifier is a type 4 information element with a length of 2 or 5 octets.

8 7 6 5 4 3 2 1

+———————————————–+

¦ ¦ LSA Identifier IEI ¦octet 1

+———————————————–¦

¦ Length of LSA Identifier contents ¦

¦ ¦octet 2

+———————————————–¦

¦ LSA ID ¦

¦ ¦octet 3

+———————————————–¦

¦ LSA ID cont. ¦

¦ ¦octet 4

+———————————————–¦

¦ LSA ID cont. ¦

¦ ¦octet 5

+———————————————–¦

Figure 10.68c/3GPP TS 04.08: LSA Identifier information element

If the Length = 0, then no LSA ID is included. This is used to indicate that the MS has moved to an area where there is no LSA available for that MS.

Octets 3-5 are coded as specified in 3GPP TS 03.03, ‘Identification of Localised Service Area’. Bit 8 of octet 3 is the most significant bit.