10.5.1 Common information elements.
24.0083GPPCore network protocolsMobile radio interface Layer 3 specificationRelease 18Stage 3TS
10.5.1.1 Cell identity
The purpose of the Cell Identity information element is to identify a cell within a location area.
The Cell Identity information element is coded as shown in figure 10.5.1/3GPP TS 24.008 and table 10.5.1/3GPP TS 24.008.
The Cell Identity is a type 3 information element with 3 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Cell Identity IEI |
octet 1 |
|||||||
CI value |
octet 2 |
|||||||
CI value (continued) |
octet 3 |
Figure 10.5.1/3GPP TS 24.008 Cell Identity information element
Table 10.5.1/3GPP TS 24.008: Cell Identity information element
CI value, Cell identity value (octet 2 and 3) In the CI value field bit 8 of octet 2 is the most significant bit and bit 1 of octet 3 the least significant bit. The coding of the cell identity is the responsibility of each administration. Coding using full hexadecimal representation may be used. The cell identity consists of 2 octets. |
10.5.1.2 Ciphering Key Sequence Number
In a GSM authentication challenge, the purpose of the Ciphering Key Sequence Number information element is to make it possible for the network to identify the ciphering key Kc which is stored in the mobile station without invoking the authentication procedure.
The ciphering key sequence number is allocated by the network and sent with the AUTHENTICATION REQUEST or AUTHENTICATION AND CIPHERING REQUEST message to the mobile station where it is stored together with the calculated keys, e.g. Kc, CK, IK, Kc128, Kint.
The Ciphering Key Sequence Number information element is coded as shown in figure 10.5.2/3GPP TS 24.008 and table 10.5.2/3GPP TS 24.008.
In a UMTS authentication challenge, the purpose of the Ciphering Key Sequence Number information element is to make it possible for the network to identify the ciphering key CK and integrity key IK which are stored in the MS without invoking the authentication procedure. CK and IK form a Key Set Identifier (KSI) (see 3GPP TS 33.102 [5a]) which is encoded the same as the CKSN and is therefore included in the CKSN field.
The ciphering key sequence number is a type 1 information element.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Ciphering Key Sequence Number IEI |
0 spare |
key sequence |
octet 1 |
Figure 10.5.2/3GPP TS 24.008 Ciphering Key Sequence Number information element
Table 10.5.2/3GPP TS 24.008: Ciphering Key Sequence Number information element
Key sequence (octet 1) Bits |
|||
3 |
2 |
1 |
|
0 |
0 |
0 |
|
through |
Possible values for the ciphering key |
||
1 |
1 |
0 |
sequence number |
1 |
1 |
1 |
No key is available (MS to network); |
Reserved (network to MS) |
10.5.1.3 Location Area Identification
The purpose of the Location Area Identification information element is to provide an unambiguous identification of location areas within the area covered by the 3GPP system.
The Location Area Identification information element is coded as shown in figure 10.5.3/3GPP TS 24.008 and table 10.5.3/3GPP TS 24.008.
The Location Area Identification is a type 3 information element with 6 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Location Area Identification IEI |
octet 1 |
|||||||
MCC digit 2 |
MCC digit 1 |
octet 2 |
||||||
MNC digit 3 |
MCC digit 3 |
octet 3 |
||||||
MNC digit 2 |
MNC digit 1 |
octet 4 |
||||||
LAC |
octet 5 |
|||||||
LAC (continued) |
octet 6 |
Figure 10.5.3/3GPP TS 24.008 Location Area Identification information element
Table 10.5.3/3GPP TS 24.008: Location Area Identification information element
MCC, Mobile country code (octet 2 and 3) The MCC field is coded as in ITU-T Rec. E212, Annex A. If the LAI is deleted the MCC and MNC shall take the value from the deleted LAI. In abnormal cases, the MCC stored in the mobile station can contain elements not in the set {0, 1 … 9}. In such cases the mobile station should transmit the stored values using full hexadecimal encoding. When receiving such an MCC, the network shall treat the LAI as deleted. MNC, Mobile network code (octet 3 bits 5 to 8, octet 4) The coding of this field is the responsibility of each administration but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. For PCS 1900 for NA, Federal regulation mandates that a 3-digit MNC shall be used. However a network operator may decide to use only two digits in the MNC in the LAI over the radio interface. In this case, bits 5 to 8 of octet 3 shall be coded as "1111". Mobile equipment shall accept LAI coded in such a way. NOTE 1: In earlier versions of this protocol, the possibility to use a one digit MNC in LAI was provided on the radio interface. However as this was not used this possibility has been deleted. NOTE 2: In earlier versions of this protocol, bits 5 to 8 of octet 3 were coded as "1111". Mobile equipment compliant with these earlier versions of the protocol may be unable to understand the 3-digit MNC format of the LAI, and therefore unable to register on a network broadcasting the LAI in this format. In abnormal cases, the MNC stored in the mobile station can have: – digit 1 or 2 not in the set {0, 1 … 9}, or – digit 3 not in the set {0, 1 … 9, F} hex. In such cases the mobile station shall transmit the stored values using full hexadecimal encoding. When receiving such an MNC, the network shall treat the LAI as deleted. The same handling shall apply for the network, if a 3-digit MNC is sent by the mobile station to a network using only a 2-digit MNC. LAC, Location area code (octet 5 and 6) In the LAC field bit 8 of octet 5 is the most significant bit and bit 1 of octet 6 the least significant bit. The coding of the location area code is the responsibility of each administration except that two values are used to mark the LAC, and hence the LAI, as deleted. Coding using full hexadecimal representation may be used. The location area code consists of 2 octets. If a LAI has to be deleted then all bits of the location area code shall be set to one with the exception of the least significant bit which shall be set to zero. If a SIM/USIM is inserted in a Mobile Equipment with the location area code containing all zeros, then the Mobile Equipment shall recognise this LAC as part of a deleted LAI |
10.5.1.4 Mobile Identity
The purpose of the Mobile Identity information element is to provide either the international mobile subscriber identity, IMSI, the temporary mobile subscriber identity, TMSI/P-TMSI/M-TMSI, the international mobile equipment identity, IMEI, the international mobile equipment identity together with the software version number, IMEISV, or the temporary mobile group identity (TMGI), associated with the optional MBMS Session Identity.
The IMSI shall not exceed 15 digits, the TMSI/P-TMSI/M-TMSI is 4 octets long, and the IMEI is composed of 15 digits, the IMEISV is 16 digits (see 3GPP TS 23.003 [10]). The TMGI is at maximum 6 octets long and is defined in subclause 10.5.6.13. The MBMS Session Identity, if included, is 1 octet long (see 3GPP TS 48.018 [86]).
For packet paging the network shall select the mobile identity type with the following priority:
1- P-TMSI: The P-TMSI shall be used if it is available.
2- IMSI: The IMSI shall be used in cases where no P-TMSI is available.
For MBMS (pre-)notification (see 3GPP TS 44.018 [84] and 3GPP TS 44.060 [76]) the network shall select the mobile identity type "TMGI and optional MBMS Session Identity".
NOTE 1: The type of identity "TMGI and optional MBMS Session Identity" is only used by the MBMS (pre‑)notification procedure in of A/Gb mode.
For all other transactions with the following exceptions:
– emergency call establishment, emergency call re-establishment, mobile terminated call establishment, the identification procedure, the GMM identification procedure, the GMM authentication, GPRS attach, routing area updating, and ciphering procedure and the ciphering mode setting procedure; and
– location updating when the MS is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368 [135] or 3GPP TS 31.102 [112] and the selected PLMN is neither the registered PLMN nor in the list of equivalent PLMNs;
the mobile station and the network shall select the mobile identity type with the following priority:
1- TMSI: The TMSI shall be used if it is available.
2- IMSI: The IMSI shall be used in cases where no TMSI is available.
For mobile terminated call establishment the mobile station shall select the same mobile identity type as received from the network in the PAGING REQUEST message. In case of enhanced DTM CS establishment (see 3GPP TS 44.018 [84]) the mobile station shall select the mobile identity type with the following priority in the PAGING RESPONSE message:
1- TMSI: The TMSI shall be used if it is available.
2- IMSI: The IMSI shall be used in cases where no TMSI is available.
For the PAGING RESPONSE message sent as a response to a paging for CS fallback, the MS shall:
– select the TMSI as mobile identity type if the network has, in E-UTRAN,
– paged the MS for CS fallback using the S-TMSI; or
– indicated TMSI in the CS SERVICE NOTIFICATION message (see 3GPP TS 24.301 [120]);
– select the IMSI as mobile identity type if the network has, in E-UTRAN,
– paged the MS for CS fallback using the IMSI; or
– indicated IMSI in the CS SERVICE NOTIFICATION message (see 3GPP TS 24.301 [120]).
For emergency call establishment and re-establishment the mobile station shall select the mobile identity type with the following priority:
1- TMSI: The TMSI shall be used if it is available and if the location update status is UPDATED, and the stored LAI is equal to the one received on the BCCH from the current serving cell.
2- IMSI: The IMSI shall be used in cases where no TMSI is available or TMSI is available but either the update status is different from UPDATED, or the stored LAI is different from the one received on the BCCH from the current serving cell.
3- IMEI: The IMEI shall be used in cases where no SIM/USIM is available or the SIM/USIM is considered as not valid by the mobile station or no IMSI or TMSI is available.
In the identification procedure and in the GMM identification procedure the mobile station shall select the mobile identity type which was requested by the network, if available. If the requested identity is not available, then the mobile station shall indicate the identity type "No Identity".
In the ciphering mode setting procedure and in the GMM authentication and ciphering procedure the mobile shall select the IMEISV.
The Mobile Identity information element is coded as shown in figure 10.5.4/3GPP TS 24.008 and table 10.5.4/3GPP TS 24.008.
The Mobile Identity is a type 4 information element with a minimum length of 3 octet and 11 octets length maximal. Further restriction on the length may be applied, e.g. number plans.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Mobile Identity IEI |
octet 1 |
|||||||
Length of mobile identity contents |
octet 2 |
|||||||
Identity digit 1 |
odd/ even indic |
Type of identity |
octet 3 |
|||||
Identity digit p+1 |
Identity digit p |
octet 4* |
Figure 10.5.4/3GPP TS 24.008 Mobile Identity information element
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Mobile Identity IEI |
octet 1 |
|||||||
Length of Mobile Identity contents |
octet 2 |
|||||||
0 |
0 |
MBMS Sess Id indic |
MCC/MNC indic |
odd/ even indic |
Type of identity |
octet 3 |
||
spare |
||||||||
MBMS Service ID |
octet 4 octet 5 |
|||||||
octet 6 |
||||||||
MCC digit 2 |
MCC digit 1 |
octet 6a* |
||||||
MNC digit 3 |
MCC digit 3 |
octet 6b* |
||||||
MNC digit 2 |
MNC digit 1 |
octet 6c* |
||||||
MBMS Session Identity |
octet 7* |
Figure 10.5.4a/3GPP TS 24.008: Mobile Identity information element for type of identity "TMGI and optional MBMS Session Identity"
Table 10.5.4/3GPP TS 24.008: Mobile Identity information element
Type of identity (octet 3) Bits |
|||
3 |
2 |
1 |
|
0 |
0 |
1 |
IMSI |
0 |
1 |
0 |
IMEI |
0 |
1 |
1 |
IMEISV |
1 |
0 |
0 |
TMSI/P-TMSI/M-TMSI |
1 |
0 |
1 |
TMGI and optional MBMS Session Identity |
0 |
0 |
0 |
No Identity (note 1) |
All other values are reserved. |
|||
Odd/even indication (octet 3) Bit |
|||
4 |
|||
0 |
even number of identity digits and also when the TMSI/P-TMSI or TMGI and optional MBMS Session Identity is used |
||
1 |
odd number of identity digits |
||
Identity digits (octet 3 etc) For the IMSI, IMEI and IMEISV this field is coded using BCD coding. If the number of identity digits is even then bits 5 to 8 of the last octet shall be filled with an end mark coded as "1111". For Type of identity "No Identity", the Identity digit bits shall be encoded with all 0s and the Length of mobile identity contents parameter shall be set to one of the following values: – "1" if the identification procedure is used (see subclause 9.2.11); – "3" if the GMM identification procedure is used (see subclause 9.4.13) – "3" if the EMM identification procedure is used (see 3GPP TS 24.301 [120]) If the mobile identity is the TMSI/P-TMSI/M-TMSI then bits 5 to 8 of octet 3 are coded as "1111" and bit 8 of octet4 is the most significant bit and bit 1 of the last octet the least significant bit. The coding of the TMSI/P-TMSI is left open for each administration. For type of identity "TMGI and optional MBMS Session Identity" the coding of octet 3 etc is as follows: |
|||
MCC/MNC indication (octet 3) Bit |
|||
5 |
|||
0 |
MCC/MNC is not present |
||
1 |
MCC/MNC is present |
||
MBMS Session Identity indication (octet 3) Bit |
|||
6 |
|||
0 |
MBMS Session Identity is not present |
||
1 |
MBMS Session Identity is present |
||
MBMS Service ID (octet 4, 5 and 6) The contents of the MBMS Service ID field are coded as octets 3 to 5 of the Temporary Mobile Group Identity IE in Figure 10.5.154/3GPP TS 24.008. Therefore, bit 8 of octet 4 is the most significant bit and bit 1 of octet 6 the least significant bit. The coding of the MBMS Service ID is the responsibility of each administration. Coding using full hexadecimal representation may be used. The MBMS Service ID consists of 3 octets. |
|||
MCC, Mobile country code (octet 6a, octet 6b bits 1 to 4) The MCC field is coded as in ITU-T Rec. E.212 [46], Annex A. |
|||
MNC, Mobile network code (octet 6b bits 5 to 8, octet 6c) The coding of this field is the responsibility of each administration but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. If a network operator decides to use only two digits in the MNC, bits 5 to 8 of octet 6b shall be coded as "1111". The MCC and MNC digits are coded as octets 6 to 8 of the Temporary Mobile Group Identity IE in Figure 10.5.154/3GPP TS 24.008. |
|||
MBMS Session Identity (octet 7) The MBMS Session Identity field is encoded as the value part of the MBMS Session Identity IE as specified in 3GPP TS 48.018 [86]. |
|||
NOTE 1: This can be used in the case when a fill paging message without any valid identity has to be sent on the paging subchannel and when the requested identity is not available at the mobile station during the identity request procedure. |
10.5.1.5 Mobile Station Classmark 1
The purpose of the Mobile Station Classmark 1 information element is to provide the network with information concerning aspects of high 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.
The Mobile Station Classmark 1 information element is coded as shown in figure 10.5.5/3GPP TS 24.008 and table 10.5.5/3GPP TS 24.008.
The Mobile Station Classmark 1 is a type 3 information element with 2 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Mobile Station Classmark 1 IEI |
octet 1 |
|||||||
0 spare |
Revision level |
ES IND |
A5/1 |
RF power capability |
octet 2 |
Figure 10.5.5/3GPP TS 24.008 Mobile Station Classmark 1 information element
Table 10.5.5/3GPP TS 24.008: Mobile Station Classmark 1 information element
Revision level (octet 2) Bits |
|||||||
7 |
6 |
||||||
0 |
0 |
Reserved for GSM phase 1 |
|||||
0 |
1 |
Used by GSM phase 2 mobile stations |
|||||
1 |
0 |
Used by mobile stations supporting R99 or later versions of the protocol |
|||||
1 |
1 |
Reserved for future use. If the network receives a revision level specified as ‘reserved for future use’, then it shall use the highest revision level supported by the network. |
|||||
ES IND (octet 2, bit 5) "Controlled Early Classmark Sending" option implementation |
|||||||
An MS not supporting A/Gb mode shall set this bit to ‘0’. An MS supporting A/Gb mode shall indicate the associated capability (see table): |
|||||||
0 |
"Controlled Early Classmark Sending" option is not implemented in the MS |
||||||
1 |
"Controlled Early Classmark Sending" option is implemented in the MS |
||||||
NOTE 1: The value of the ES IND gives the implementation in the MS. It’s value is not dependent on the broadcast SI 3 Rest Octet <Early Classmark Sending Control> value. |
|||||||
A5/1 algorithm supported (octet 2, bit4) (Note 2) An MS not supporting A/Gb mode shall set this bit to ‘1’. An MS supporting A/Gb mode shall indicate the associated capability (see table): |
|||||||
0 |
encryption algorithm A5/1 available |
||||||
1 |
encryption algorithm A5/1 not available |
||||||
RF power capability (octet 2) |
|||||||
When GSM 450, GSM 480, GSM 710, GSM 750, T-GSM 810, GSM 850, GSM 900 P, E [or R] band is used (for exceptions see 3GPP TS 44.018 [84]), the MS shall indicate the RF power capability of the band used (see table): When UMTS is used, a single band GSM 450, GSM 480, GSM 710, GSM 750, T-GSM 810, GSM 850, GSM 900 P, E [or R] MS shall indicate the RF power capability corresponding to the (GSM) band it supports (see table). In this case information on which single band is supported is found in classmark 3. |
|||||||
Bits |
|||||||
3 |
2 |
1 |
|||||
0 |
0 |
0 |
class 1 |
||||
0 |
0 |
1 |
class 2 |
||||
0 |
1 |
0 |
class 3 |
||||
0 |
1 |
1 |
class 4 |
||||
1 |
0 |
0 |
class 5 |
||||
All other values are reserved. |
|||||||
When the GSM 1800 or GSM 1900 band is used (for exceptions see 3GPP TS 44.018 [84], sub-clause 3.4.18), the MS shall indicate the RF power capability of the band used (see table): When UMTS is used, a single band GSM 1800 or GSM 1900 MS shall indicate the RF power capability corresponding to the (GSM) band it supports (see table). In this case, information on which single band is supported is found in classmark 3. Bits |
|||||||
3 |
2 |
1 |
|||||
0 |
0 |
0 |
class 1 |
||||
0 |
0 |
1 |
class 2 |
||||
0 |
1 |
0 |
class 3 |
||||
All other values are reserved. |
|||||||
When UMTS is used, an MS not supporting any GSM band or a multiband GSM MS shall code this field as follows (see table): Bits |
|||||||
3 |
2 |
1 |
|||||
1 |
1 |
1 |
RF power capability is irrelevant in this information element. |
||||
All other values are reserved. |
|||||||
NOTE 2: The requirements for the support of the A5 algorithms in the MS are specified in 3GPP TS 43.020 [13]. |
10.5.1.6 Mobile Station Classmark 2
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.
The Mobile Station Classmark 2 information element is coded as shown in figure 10.5.6/3GPP TS 24.008, table 10.5.6a/3GPP TS 24.008 and table 10.5.6b/3GPP TS 24.008.
The Mobile Station Classmark 2 is a type 4 information element with 5 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Mobile station classmark 2 IEI |
octet 1 |
|||||||||
Length of mobile station classmark 2 contents |
octet 2 |
|||||||||
0 spare |
Revision level |
ES IND |
A5/1 |
RF power capability |
octet 3 |
|||||
0 spare |
PS capa. |
SS Screen. Indicator |
SM ca pabi. |
VBS |
VGCS |
FC |
octet 4 |
|||
CM3 |
0 spare |
LCSVA CAP |
UCS2 |
SoLSA |
CMSP |
A5/3 |
A5/2 |
octet 5 |
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".
Figure 10.5.6/3GPP TS 24.008 Mobile Station Classmark 2 information element
Table 10.5.6a/3GPP TS 24.008: Mobile Station Classmark 2 information element |
||||||
---|---|---|---|---|---|---|
Revision level (octet 3) Bits |
||||||
7 |
6 |
|||||
0 |
0 |
Reserved for GSM phase 1 |
||||
0 |
1 |
Used by GSM phase 2 mobile stations |
||||
1 |
0 |
Used by mobile stations supporting R99 or later versions of the protocol |
||||
1 |
1 |
Reserved for future use. If the network receives a revision level specified as ‘reserved for future use’, then it shall use the highest revision level supported by the network. |
||||
ES IND (octet 3, bit 5) "Controlled Early Classmark Sending" option implementation |
||||||
AN MS not supporting A/Gb mode shall set this bit to ‘0’. An MS supporting A/Gb mode shall indicate the associated capability (see table): |
||||||
0 |
"Controlled Early Classmark Sending" option is not implemented in the MS |
|||||
1 |
"Controlled Early Classmark Sending" option is implemented in the MS |
|||||
NOTE 1: The value of the ES IND gives the implementation in the MS. It’s value is not dependent on the broadcast SI 3 Rest Octet <Early Classmark Sending Control> value |
||||||
A5/1 algorithm supported (octet 3, bit 4) (Note 4) An MS not supporting A/Gb mode shall set this bit to ‘1’. An MS supporting A/Gb mode shall indicate the associated capability (see table) |
||||||
0 |
encryption algorithm A5/1 available |
|||||
1 |
encryption algorithm A5/1 not available |
|||||
RF Power Capability (Octet 3) |
||||||
When T-GSM 380, T-GSM 410, GSM 450, GSM 480, GSM 710, GSM 750, T-GSM 810, GSM 850, GSM 900 P, E [or R] band is used (for exceptions see 3GPP TS 44.018 [84]), the MS shall indicate the RF power capability of the band used (see table). When UMTS or E-UTRAN is used, a single band T-GSM 380, T-GSM 410, GSM 450, GSM 480, GSM 710, GSM 750, T-GSM 810, GSM 850, GSM 900 P, E [or R] MS shall indicate the RF power capability corresponding to the (GSM) band it supports (see table). In this case, information on which single band is supported is found in classmark 3. |
||||||
Bits |
||||||
3 |
2 |
1 |
||||
0 |
0 |
0 |
class 1 |
|||
0 |
0 |
1 |
class 2 |
|||
0 |
1 |
0 |
class 3 |
|||
0 |
1 |
1 |
class 4 |
|||
1 |
0 |
0 |
class 5 |
|||
All other values are reserved. |
||||||
When the GSM 1800 or GSM 1900 band is used (for exceptions see 3GPP TS 44.018 [84]) The MS shall indicate the RF power capability of the band used (see table). When UMTS or E-UTRAN is used, a single band GSM 1800 or GSM 1900 MS shall indicate the RF power capability corresponding to the (GSM) band it supports (see table). In this case, information on which single band is supported is found in classmark 3 Bits |
||||||
3 |
2 |
1 |
||||
0 |
0 |
0 |
class 1 |
|||
0 |
0 |
1 |
class 2 |
|||
0 |
1 |
0 |
class 3 |
|||
All other values are reserved. |
||||||
When UMTS or E-UTRAN is used, an MS not supporting any GSM band or a multiband GSM MS shall code this field as follows (see table): |
||||||
Bits |
||||||
3 |
2 |
1 |
||||
1 |
1 |
1 |
RF Power capability is irrelevant in this information element |
|||
All other values are reserved. |
||||||
PS capability (pseudo-synchronization capability) (octet 4) An MS not supporting A/Gb mode shall set this bit to ‘0’. An MS supporting A/Gb mode shall indicate the associated capability (see table): Bit 7 |
||||||
0 |
PS capability not present |
|||||
1 |
PS capability present |
|||||
SS Screening Indicator (octet 4) Bits |
||||||
6 |
5 |
|||||
0 |
0 |
defined in 3GPP TS 24.080 [24] |
||||
0 |
1 |
defined in 3GPP TS 24.080 [24] |
||||
1 |
0 |
defined in 3GPP TS 24.080 [24] |
||||
1 |
1 |
defined in 3GPP TS 24.080 [24] |
||||
SM capability (MT SMS pt to pt capability) (octet 4) Bit 4 |
||||||
0 |
Mobile station does not support mobile terminated point to point SMS |
|||||
1 |
Mobile station supports mobile terminated point to point SMS |
|||||
VBS notification reception (octet 4) An MS not supporting A/Gb mode shall set this bit to ‘0’. An MS supporting A/Gb mode shall indicate the associated capability (see table): Bit 3 |
||||||
0 |
no VBS capability or no notifications wanted |
|||||
1 |
VBS capability and notifications wanted |
|||||
VGCS notification reception (octet 4) An MS not supporting A/Gb mode shall set this bit to ‘0’. An MS supporting A/Gb mode shall indicate the associated capability (see table): Bit 2 |
||||||
0 |
no VGCS capability or no notifications wanted |
|||||
1 |
VGCS capability and notifications wanted |
|||||
FC Frequency Capability (octet 4) When the T-GSM 400, GSM 400, or GSM 700, or T-GSM 810, or GSM 850, or GSM 1800, or GSM 1900 band or UMTS or E-UTRAN is used (for exceptions see 3GPP TS 44.018 [84]), for definitions of frequency band see 3GPP TS 45.005 [33]), this bit shall be sent with the value ‘0’. |
||||||
NOTE 2: This bit conveys no information about support or non support of the E-GSM or R-GSM bands when T-GSM 400, GSM 400, GSM 700, T-GSM 810, GSM 850, GSM 1800, GSM 1900 band or UMTS or E-UTRAN is used. |
||||||
When a GSM 900 band is used (for exceptions see 3GPP TS 44.018 [84]): Bit 1 |
||||||
0 |
The MS does not support the E-GSM or R-GSM band (For definition of frequency bands see 3GPP TS 45.005 [33]) |
|||||
1 |
The MS does support the E-GSM or R-GSM (For definition of frequency bands see 3GPP TS 45.005 [33]) |
|||||
NOTE 3: For mobile station supporting the R-GSM band further information can be found in MS Classmark 3. |
||||||
CM3 (octet 5, bit 8) |
||||||
0 |
The MS does not support any options that are indicated in CM3 |
|||||
1 |
The MS supports options that are indicated in classmark 3 IE |
|||||
LCS VA capability (LCS value added location request notification capability) (octet 5,bit 6) This information field indicates the support of the LCS value added location request notification via CS domain as defined in 3GPP TS 23.271 [105]. |
||||||
0 |
location request notification via CS domain not supported |
|||||
1 |
location request notification via CS domain supported |
|||||
UCS2 treatment (octet 5, bit 5) This information field indicates the likely treatment by the mobile station of UCS2 encoded character strings. For backward compatibility reasons, if this field is not included, the value 0 shall be assumed by the receiver. |
||||||
0 |
the ME has a preference for the default alphabet (defined in 3GPP TS 23.038 [8b]) over UCS2. |
|||||
1 |
the ME has no preference between the use of the default alphabet and the use of UCS2. |
|||||
SoLSA (octet 5, bit 4) An MS not supporting A/Gb mode shall set this bit to ‘0’. An MS supporting A/Gb mode shall indicate the associated capability (see table): |
||||||
0 |
The ME does not support SoLSA. |
|||||
1 |
The ME supports SoLSA. |
|||||
CMSP: CM Service Prompt (octet 5, bit 3) $(CCBS)$ |
||||||
0 |
"Network initiated MO CM connection request" not supported. |
|||||
1 |
"Network initiated MO CM connection request" supported for at least one CM protocol. |
|||||
A5/3 algorithm supported (octet 5, bit 2) (Note 4) An MS not supporting A/Gb mode shall set this bit to ‘0’. An MS supporting A/Gb mode shall indicate the associated capability (see table): |
||||||
0 |
encryption algorithm A5/3 not available |
|||||
1 |
encryption algorithm A5/3 available |
|||||
A5/2 algorithm supported (octet 5, bit 1) (Note 4) The MS shall set this bit to ‘0’. The network shall accept any received value. |
||||||
0 |
encryption algorithm A5/2 not available |
|||||
1 |
Not used. This value was allocated in earlier versions of the protocol. |
|||||
NOTE 4: The requirements for the support of the A5 algorithms in the MS are specified in 3GPP TS 43.020 [13]. |
NOTE 2: Additional mobile station capability information might be obtained by invoking the classmark interrogation procedure when GSM is used.
10.5.1.7 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.
NOTE: The 34 octet limit is so that the CLASSMARK CHANGE message will fit in up to two layer 2 frames.
SEMANTIC RULE: a multiband mobile station shall provide information about all frequency bands it can support. A single band mobile station shall not indicate the band it supports in the Multiband Supported, GSM 400 Bands Supported, GSM 710 Associated Radio Capability, GSM 750 Associated Radio Capability, T-GSM 810 Associated Radio Capability, GSM 850 Associated Radio Capability or GSM 1900 Associated Radio Capability fields in the Mobile Station Classmark 3. Due to shared radio frequency channel numbers between GSM 1800 and GSM 1900, the mobile should indicate support for either GSM 1800 band OR GSM 1900 band.
SEMANTIC RULE: a mobile station shall include the MS Measurement Capability field if the Multi Slot Class field contains a value of 19 or greater (see 3GPP TS 45.002 [32]).
Typically, the number of spare bits at the end is the minimum to reach an octet boundary. The receiver may add any number of bits set to "0" at the end of the received string if needed for correct decoding.
<Classmark 3 Value part> ::= < spare bit > { < Multiband supported : { 000 } > < A5 bits > | < Multiband supported : { 101 | 110 } > < A5 bits > < Associated Radio Capability 2 : bit(4) > < Associated Radio Capability 1 : bit(4) > | < Multiband supported : { 001 | 010 | 100 } > < A5 bits > < spare bit >(4) < Associated Radio Capability 1 : bit(4) > } { 0 | 1 < R Support > } { 0 | 1 < HSCSD Multi Slot Capability > } < UCS2 treatment: bit > < Extended Measurement Capability : bit > { 0 | 1 < MS measurement capability > } { 0 | 1 < MS Positioning Method Capability > } { 0 | 1 < ECSD Multi Slot Capability > } { 0 | 1 < 8-PSK Struct > } { 0 | 1 < GSM 400 Bands Supported : { 01 | 10 | 11 } > < GSM 400 Associated Radio Capability: bit(4) > } { 0 | 1 <GSM 850 Associated Radio Capability : bit(4) > } { 0 | 1 <GSM 1900 Associated Radio Capability : bit(4) > } < UMTS FDD Radio Access Technology Capability : bit > < UMTS 3.84 Mcps TDD Radio Access Technology Capability : bit > < CDMA 2000 Radio Access Technology Capability : bit > { 0 | 1 < DTM GPRS Multi Slot Class : bit(2) > < Single Slot DTM : bit > {0 | 1< DTM EGPRS Multi Slot Class : bit(2) > } } { 0 | 1 < Single Band Support > } — Release 4 starts here. { 0 | 1 <GSM 750 Associated Radio Capability : bit(4)>} < UMTS 1.28 Mcps TDD Radio Access Technology Capability : bit > < GERAN Feature Package 1 : bit > { 0 | 1 < Extended DTM GPRS Multi Slot Class : bit(2) > < Extended DTM EGPRS Multi Slot Class : bit(2) > } { 0 | 1 < High Multislot Capability : bit(2) > } –Release 5 starts here. 0 — The value ‘1’ was allocated in an earlier version of the protocol and shall not be used. < GERAN Feature Package 2 : bit > < GMSK Multislot Power Profile : bit (2) > < 8-PSK Multislot Power Profile : bit (2) > { 0 | 1 < T-GSM 400 Bands Supported : { 01 | 10 | 11 } > — Release 6 starts here. < T-GSM 400 Associated Radio Capability: bit(4) > } 0 — The value ‘1’ was allocated in an earlier version of the protocol and shall not be used. < Downlink Advanced Receiver Performance : bit (2)> < DTM Enhancements Capability : bit > { 0 | 1 < DTM GPRS High Multi Slot Class : bit(3) > < Offset required : bit> { 0 | 1 < DTM EGPRS High Multi Slot Class : bit(3) > } } < Repeated ACCH Capability : bit > { 0 | 1 <GSM 710 Associated Radio Capability : bit(4)>} — Release 7 starts here. { 0 | 1 <T-GSM 810 Associated Radio Capability : bit(4)>} < Ciphering Mode Setting Capability : bit > < Additional Positioning Capabilities : bit > < E-UTRA FDD support : bit > — Release 8 starts here < E-UTRA TDD support : bit > < E-UTRA Measurement and Reporting support : bit > < Priority-based reselection support : bit > < UTRA CSG Cells Reporting : bit > — Release 9 starts here < VAMOS Level : bit(2) > < TIGHTER Capability : bit(2) > — Release 10 starts here < Selective Ciphering of Downlink SACCH : bit > < CS to PS SRVCC from GERAN to UTRA : bit(2) > — Release 11 starts here < CS to PS SRVCC from GERAN to E-UTRA : bit(2)> < GERAN Network Sharing support : bit > < E-UTRA Wideband RSRQ measurements support : bit > < ER Band Support : bit > — Release 12 starts here < UTRA Multiple Frequency Band Indicators support : bit > < E-UTRA Multiple Frequency Band Indicators support: bit > < Extended TSC Set Capability support: bit > < Extended EARFCN value range : bit > — Late addition of a release 11 feature < spare bits > ; < A5 bits > ::= < A5/7 : bit > < A5/6 : bit > < A5/5 : bit > < A5/4 : bit > ; <R Support>::= < R-GSM band Associated Radio Capability : bit(3) > ; < HSCSD Multi Slot Capability > ::= < HSCSD Multi Slot Class : bit(5) > ; < MS Measurement capability > ::= < SMS_VALUE : bit (4) > < SM_VALUE : bit (4) > ; < MS Positioning Method Capability > ::= < MS Positioning Method : bit(5) > ; < ECSD Multi Slot Capability > ::= < ECSD Multi Slot Class : bit(5) > ; < 8-PSK Struct> : := < Modulation Capability : bit > { 0 | 1 < 8-PSK RF Power Capability 1: bit(2) > } { 0 | 1 < 8-PSK RF Power Capability 2: bit(2) > } < Single Band Support > ::= < GSM Band : bit (4) > ; |
Figure 10.5.1.7/3GPP TS 24.008 Mobile Station Classmark 3 information element
Table 10.5.1.7/3GPP TS 24.008: Mobile Station Classmark 3 information element
Multiband Supported (3 bit field) Band 1 supported Bit 1 0 P-GSM not supported 1 P-GSM supported Band 2 supported Bit 2 0 E-GSM or R-GSM not supported 1 E-GSM or R-GSM supported Band 3 supported Bit 3 0 GSM 1800 not supported 1 GSM 1800 supported The indication of support of P-GSM band or E-GSM or R-GSM band is mutually exclusive. When the ‘Band 2 supported’ bit indicates support of E-GSM or R-GSM, the presence of the <R Support> field, see below, indicates if the E-GSM or R-GSM band is supported. In this version of the protocol, the sender indicates in this field either none, one or two of these 3 bands supported. For single band mobile station or a mobile station supporting none of the GSM 900 bands(P-GSM, E-GSM and R-GSM) and GSM 1800 bands, all bits are set to 0. A5/4 0 Encryption algorithm A5/4 not available 1 Encryption algorithm A5/4 available A5/5 0 Encryption algorithm A5/5 not available 1 Encryption algorithm A5/5 available A5/6 0 Encryption algorithm A5/6 not available 1 Encryption algorithm A5/6 available A5/7 0 Encryption algorithm A5/7 not available 1 Encryption algorithm A5/7 available Associated Radio capability 1 and 2 (4 bit fields) If either of P-GSM or E-GSM or R-GSM is supported, the radio capability 1 field indicates the radio capability for P-GSM, E-GSM or R-GSM, and the radio capability 2 field indicates the radio capability for GSM 1800 if supported, and is spare otherwise. If none of P-GSM or E-GSM or R-GSM are supported, the radio capability 1 field indicates the radio capability for GSM 1800, and the radio capability 2 field is spare. The radio capability contains the binary coding of the power class associated with the band indicated in multiband support bits (see 3GPP TS 45.005 [33]). |
(continued…)
Table 10.5.1.7/3GPP TS 24.008 (continued): Mobile Station Classmark 3 information element
R-GSM band Associated Radio Capability (3 bit field) In case where the R-GSM band is supported the R-GSM band associated radio capability field contains the binary coding of the power class associated (see 3GPP TS 45.005 [33]) (regardless of the number of GSM bands supported). A mobile station supporting the R-GSM band shall also when appropriate, (see 10.5.1.6) indicate its support in the ‘FC’ bit in the Mobile Station Classmark 2 information element. NOTE: The coding of the power class for P-GSM, E-GSM, R-GSM and GSM 1800 in radio capability 1 and/or 2 is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements. HSCSD Multi Slot Class (5 bit field) In case the MS supports the use of multiple timeslots for HSCSD then the HSCSD Multi Slot Class field is coded as the binary representation of the multislot class defined in 3GPP TS 45.002 [32]. UCS2 treatment (1 bit field) This information field indicates the likely treatment by the mobile station of UCS2 encoded character strings. If not included, the value 0 shall be assumed by the receiver. 0 the ME has a preference for the default alphabet (defined in 3GPP TS 23.038 [8b]) over UCS2. 1 the ME has no preference between the use of the default alphabet and the use of UCS2. Extended Measurement Capability (1 bit field) This bit indicates whether the mobile station supports ‘Extended Measurements’ or not 0 the MS does not support Extended Measurements 1 the MS supports Extended Measurements SMS_VALUE (Switch-Measure-Switch) (4 bit field) Bits SM_VALUE (Switch-Measure) (4 bit field) Bits MS Positioning Method (5 bit field) MS assisted E-OTD Bit 5 0 MS assisted E-OTD not supported 1 MS assisted E-OTD supported |
Table 10.5.1.7/3GPP TS 24.008 (continued): Mobile Station Classmark 3 information element
MS based E-OTD Bit 4 0 MS based E-OTD not supported 1 MS based E-OTD supported MS assisted GPS Bit 3 0 MS assisted GPS not supported 1 MS assisted GPS supported MS based GPS Bit 2 0 MS based GPS not supported 1 MS based GPS supported MS Conventional GPS Bit 1 0 conventional GPS not supported 1 conventional GPS supported ECSD Multi Slot class (5 bit field) An MS that supports ECSD shall include this field to indicate its ECSD capability. Whether the MS is capable of 8-PSK modulation in uplink is indicated by the value of the Modulation Capability field in the 8-PSK struct. The ECSD Multi Slot Class field is coded as the binary representation of the multislot class defined in 3GPP TS 45.002 [32]. 8-PSK struct The MS shall include the 8-PSK struct if it supports ECSD or DTM EGPRS or both. Modulation Capability The Modulation Capability field indicates the modulation scheme the MS supports in addition to GMSK. 0 8-PSK supported for downlink reception only 1 8-PSK supported for uplink transmission and downlink reception 8-PSK RF Power Capability 1 (2 bit field) If 8-PSK modulation is supported for both uplink and downlink, the 8-PSK RF Power Capability 1 field indicates the radio capability for 8‑PSK modulation in GSM 400, GSM 700, GSM 850 or GSM 900. 8-PSK RF Power Capability 2 (2 bit field) If 8-PSK modulation is supported for both uplink and downlink, the 8-PSK RF Power Capability 2 field indicates the radio capability for 8‑PSK modulation in GSM 1800 or GSM 1900 if supported, and is not included otherwise. The respective 8-PSK RF Power Capability 1 and 8-PSK RF Power Capability 2 fields contain the following coding of the 8‑PSK modulation power class (see 3GPP TS 45.005 [33]): Bits 2 1 0 0 Reserved 0 1 Power class E1 1 0 Power class E2 1 1 Power class E3 |
Table 10.5.1.7/3GPP TS 24.008 (continued): Mobile Station Classmark 3 information element
GSM 400 Bands Supported (2 bit field) See the semantic rule for the sending of this field. Bits GSM 400 Associated Radio Capability (4 bit field) If either GSM 450 or GSM 480 or both is supported, the GSM 400 Associated Radio Capability field indicates the radio capability for GSM 450 and/or GSM 480. The radio capability contains the binary coding of the power class associated with the band indicated in GSM 400 Bands Supported bits (see 3GPP TS 45.005 [33]). NOTE: The coding of the power class for GSM 450 and GSM 480 in GSM 400 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements. GSM 850 Associated Radio Capability (4 bit field) See the semantic rule for the sending of this field. This field indicates whether GSM 850 band is supported and its associated radio capability. The radio capability contains the binary coding of the power class associated with the GSM 850 band (see 3GPP TS 45.005 [33]). Note: the coding of the power class for GSM 850 in GSM 850 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements. GSM 1900 Associated Radio Capability (4 bit field) See the semantic rule for the sending of this field. This field indicates whether GSM 1900 band is supported and its associated radio capability. The radio capability contains the binary coding of the power class associated with the GSM 1900 band (see 3GPP TS 45.005 [33]). Note: the coding of the power class for GSM 1900 in GSM 1900 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements. |
Table 10.5.1.7/3GPP TS 24.008 (continued): Mobile Station Classmark 3 information element
UMTS FDD Radio Access Technology Capability (1 bit field) 0 UMTS FDD not supported UMTS 3.84 Mcps TDD Radio Access Technology Capability (1 bit field) 0 UMTS 3.84 Mcps TDD not supported CDMA 2000 Radio Access Technology Capability (1 bit field) DTM GPRS Multi Slot Class (2 bit field) If a multislot class type 1 MS indicates the support of a DTM GPRS multislot class for which three uplink timeslots can be assigned, the mobile station shall support Extended Dynamic Allocation. This field shall contain one of the following values if the DTM GPRS High Multi Slot Class field is present: – Multislot class 9 if DTM GPRS High Multi Slot Class is set to indicate Class 31/36 or Class 41; – Multislot class 11 if DTM GPRS High Multi Slot Class is set to indicate Classes 32/37, 33/38 or Classes 42, 43, 44. The same multislot capability is applicable also for EGPRS2 if supported. Single Slot DTM (1 bit field) 0 Single Slot DTM not supported An MS indicating support for Extended DTM GPRS multislot class or Extended DTM EGPRS multislot class shall set this bit to ‘1’. The network may ignore the bit in this case. DTM EGPRS Multi Slot Class (2 bit field) If a multislot class type 1 MS indicates the support of a DTM EGPRS multislot class for which three uplink timeslots can be assigned, the mobile station shall support Extended Dynamic Allocation. This field shall contain one of the following values if the DTM EGPRS High Multi Slot Class field is present: – Multislot class 9 if DTM EGPRS High Multi Slot Class is set to indicate Class 31/36 or Class 41; – Multislot class 11 if DTM EGPRS High Multi Slot Class is set to indicate Classes 32/37, 33/38 or Classes 42, 43, 44. Single Band Support This field shall be sent if the mobile station supports UMTS and one and only one GSM band with the exception of R-GSM; this field shall not be sent otherwise GSM Band (4 bit field) Bits 4 3 2 1 0 0 0 0 E-GSM is supported 0 0 0 1 P-GSM is supported 0 0 1 0 GSM 1800 is supported 0 0 1 1 GSM 450 is supported 0 1 0 0 GSM 480 is supported 0 1 0 1 GSM 850 is supported 0 1 1 0 GSM 1900 is supported 0 1 1 1 GSM 750 is supported 1 0 0 0 GSM 710 is supported 1 0 0 1 T-GSM 810 is supported All other values are reserved for future use. NOTE: When this field is received, the associated RF power capability is found in Classmark 1 or 2. GSM 750 Associated Radio Capability (4 bit field) See the semantic rule for the sending of this field. This field indicates whether GSM 750 band is supported and its associated radio capability. The radio capability contains the binary coding of the power class associated with the GSM 750 band (see 3GPP TS 45.005 [33]). NOTE: The coding of the power class for GSM 750 in GSM 750 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements. UMTS 1.28 Mcps TDD Radio Access Technology Capability (1 bit field) 0 UMTS 1.28 Mcps TDD not supported GERAN Feature Package 1 (1 bit field) This field indicates whether the MS supports the GERAN Feature Package 1 (see 3GPP TS 44.060 [76]). It is coded as follows: 0 GERAN feature package 1 not supported. Extended DTM GPRS Multi Slot Class (2 bit field) This field indicates the extended DTM GPRS multislot capabilities of the MS and shall be interpreted in conjunction with the DTM GPRS Multi Slot Class field. It is coded as follows, where ‘DGMSC’ denotes the DTM GPRS Multi Slot Class field: DGMSC Bit 2 1 Bit 2 1 0 0 0 0 Unused. If received, it shall be interpreted as ’01 00’ 0 0 0 1 Unused. If received, it shall be interpreted as ’01 00’ 0 0 1 0 Unused. If received, it shall be interpreted as ’01 00’ 0 0 1 1 Unused. If received, it shall be interpreted as ’01 00’ 0 1 0 0 Multislot class 5 supported 0 1 0 1 Multislot class 6 supported 0 1 1 0 Unused. If received, it shall be interpreted as ’01 00’ 0 1 1 1 Unused. If received, it shall be interpreted as ’01 00’ 1 0 0 0 Multislot class 9 supported 1 0 0 1 Multislot class 10 supported 1 0 1 0 Unused. If received, it shall be interpreted as ’10 00’ 1 0 1 1 Unused. If received, it shall be interpreted as ’10 00’ 1 1 0 0 Multislot class 11 supported 1 1 0 1 Unused. If received, it shall be interpreted as ’11 00’ 1 1 1 0 Unused. If received, it shall be interpreted as ’11 00’ 1 1 1 1 Unused. If received, it shall be interpreted as ’11 00’ The presence of this field indicates that the MS supports combined fullrate and halfrate GPRS channels in the downlink.When this field is not present, the MS supports the multislot class indicated by the DTM GPRS Multi Slot Class field. If this field is included, it shall contain one of the following values if the DTM GPRS High Multi Slot Class field is present: – Multislot class 10 if DTM GPRS High Multi Slot Class is set to indicate Class 31/36 or Class 41; – Multislot class 11 if DTM GPRS High Multi Slot Class is set to indicate Classes 32/37, 33/38 or Classes 42, 43, 44. Extended DTM EGPRS Multi Slot Class (2 bit field) This field is not considered when the DTM EGPRS Multi Slot Class field is not included. This field indicates the extended DTM EGPRS multislot capabilities of the MS and shall be interpreted in conjunction with the DTM EGPRS Multi Slot Class field. This field is coded as the Extended DTM GPRS Multi Slot Class field. The presence of this field indicates that the MS supports combined fullrate and halfrate GPRS channels in the downlink. When this field is not present, the MS supports the multislot class indicated by the DTM EGPRS Multi Slot Class field. If this field is included, it shall contain one of the following values if the DTM EGPRS High Multi Slot Class field is present: – Multislot class 10 if DTM EGPRS High Multi Slot Class is set to indicate Class 31/36 or Class 41; – Multislot class 11 if DTM EGPRS High Multi Slot Class is set to indicate Classes 32/37, 33/38 or Classes 42, 43, 44. High Multislot Capability (2 bit field) This field indicates the support of multislot classes 30 to 45, see 3GPP TS 45.002 [32]. The High Multislot Capability is individually combined with each multislot class field sent by the MS (the possible multislot class fields are: GPRS multislot class, EGPRS multislot class) to extend the related multislot class with the rule described in the MS Radio Access Capability IE. The same capability is applicable also to EGPRS2 if supported. GERAN Feature Package 2 (1 bit field) This field indicates the MS support of the GERAN Feature Package 2. The GERAN Feature Package 2 includes Enhanced Power Control (EPC) (see 3GPP TS 45.008 [34]). 0 GERAN feature package 2 not supported. GMSK Multislot Power Profile (2 bit field) This field indicates the GMSK multislot power capability parameter GMSK_MULTISLOT_POWER_PROFILE as described in 3GPP TS 45.005 [33]. Bits 2 1 0 0 GMSK_MULTISLOT_POWER_PROFILE 0 0 1 GMSK_MULTISLOT_POWER_PROFILE 1 1 0 GMSK_MULTISLOT_POWER_PROFILE 2 1 1 GMSK_MULTISLOT_POWER_PROFILE 3 8-PSK Multislot Power Profile (2 bit field) This field indicates the 8-PSK multislot power capability parameter 8‑PSK_MULTISLOT_POWER_PROFILE as described in 3GPP TS 45.005 [33]. If the MS does not support 8-PSK in the uplink, then it shall set this field to ‘0 0’. Bits 2 1 0 0 8-PSK_MULTISLOT_POWER_PROFILE 0 0 1 8-PSK_MULTISLOT_POWER_PROFILE 1 1 0 8-PSK_MULTISLOT_POWER_PROFILE 2 1 1 8-PSK_MULTISLOT_POWER_PROFILE 3 T-GSM 400 Bands Supported (2 bit field) See the semantic rule for the sending of this field. Bits T-GSM 400 Associated Radio Capability (4 bit field) If either T-GSM 410 or T-GSM 380 or both is supported, the T-GSM 400 Associated Radio Capability field indicates the radio capability for T-GSM 410 and/or T-GSM 380. The radio capability contains the binary coding of the power class associated with the band indicated in T-GSM 400 Bands Supported bits (see 3GPP TS 45.005 [33]). NOTE: The coding of the power class for T-GSM 410 and T-GSM 380 in T-GSM 400 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements. Downlink Advanced Receiver Performance (2 bit field) This field indicates Downlink Advanced Receiver Performance capabilities of the MS (see 3GPP TS 45.005 [33]). Bits 2 1 0 0 Downlink Advanced Receiver Performance not supported 0 1 Downlink Advanced Receiver Performance – phase I supported 1 0 Downlink Advanced Receiver Performance – phase II supported The value ’11’ shall not be used by the MS. If the value ’11’ is received by the network, it shall be interpreted as ’10’. DTM Enhancements Capability (1 bit field) 0 The mobile station does not support enhanced DTM CS establishment and enhanced DTM CS release procedures. DTM GPRS High Multi Slot Class (3 bit field) Bit The presence of this field indicates that the MS supports the DTM extension to high multislot classes. When this field is not present, the MS supports the DTM multislot class indicated by the DTM GPRS Multi Slot Class field. The values ‘0 0 1’, ‘0 1 0’ and ‘0 1 1’ shall be interpreted as indicating DTM GPRS multislot class 36, 37 or 38 respectively if the Offset required field indicates that the offset t0 is required; in all other cases those codepoints shall be interpreted as indicating DTM GPRS multislot class 31, 32 or 33 respectively. Offset required (1 bit field) 0 The mobile station does not require the offset DTM EGPRS High Multi Slot Class (3 bit field) The values ‘0 0 1’, ‘0 1 0’ and ‘0 1 1’ shall be interpreted as indicating DTM EGPRS multislot class 36, 37 or 38 respectively if the Offset required field indicates that the Timing Advance offset t0 is required; in all other cases those codepoints shall be interpreted as indicating DTM EGPRS multislot class 31, 32 or 33 respectively. The same multislot capability is applicable also for EGPRS2 if supported Repeated ACCH Capability (1 bit field) This field indicates whether the MS supports Repeated SACCH and Repeated Downlink FACCH (see 3GPP TS 44.006 [19]). It is coded as follows: 0 The mobile station does not support Repeated SACCH An MS that only supports Repeated Downlink FACCH shall set this bit field to ‘0’. GSM 710 Associated Radio Capability (4 bit field) See the semantic rule for the sending of this field. This field indicates whether GSM 710 band is supported and its associated radio capability. The radio capability contains the binary coding of the power class associated with the GSM 710 band (see 3GPP TS 45.005 [33]). NOTE: The coding of the power class for GSM 710 in GSM 710 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements. T-GSM 810 Associated Radio Capability (4 bit field) See the semantic rule for the sending of this field. This field indicates whether T- GSM 810 band is supported and its associated radio capability. The radio capability contains the binary coding of the power class associated with the T-GSM 810 band (see 3GPP TS 45.005 [33]). NOTE: The coding of the power class for T-GSM 810 in T-GSM 810 Associated Radio Capability is different to that used in the Mobile Station Classmark 1 and Mobile Station Classmark 2 information elements. Ciphering Mode Setting Capability (1 bit field) This field indicates whether the MS supports the Ciphering Mode Setting IE in the DTM ASSIGNMENT COMMAND message (see 3GPP TS 44.018 [84]). It is coded as follows: 0 The mobile station does not support the Ciphering Mode Setting IE in the 1 The mobile station supports the Ciphering Mode Setting IE in the DTM ASSIGNMENT COMMAND Additional Positioning Capabilities (1 bit field) This field indicates whether the mobile station supports additional positioning capabilities which can be retrieved using RRLP. It is coded as follows: 0 The mobile station does not support additional positioning capabilities which can be retrieved using RRLP E-UTRA FDD support (1 bit field) Bit 0 E-UTRA FDD not supported 1 E-UTRA FDD supported E-UTRA TDD support (1 bit field) Bit 0 E-UTRA TDD not supported 1 E-UTRA TDD supported E-UTRA Measurement and Reporting support (1 bit field) This field indicates whether the mobile station supports E-UTRAN neighbouring cell measurements and measurement reporting in dedicated mode and, if the mobile station is DTM capable, also in dual transfer mode. If both "E-UTRA FDD support" and "E-UTRA TDD support" bits are set to ‘0’, this field shall be set to ‘0’. If one of or both "E-UTRA FDD support"and "E-UTRA TDD support" bits are set to ‘1’, this field may be set to ‘0’ or ‘1’. It is coded as follows: Bit 0 E-UTRAN Neighbour Cell measurements and measurement reporting while having an RR connection 1 E-UTRAN Neighbour Cell measurements and measurement reporting while having an RR connection Priority-based reselection support (1 bit field) This field indicates whether the mobile station supports priority-based cell reselection. It is coded as follows: Bit 0 Priority-based cell reselection not supported 1 Priority-based cell reselection supported UTRA CSG Cells Reporting (1 bit field) This field indicates whether the mobile station supports reporting of measurements and routing parameters (see 3GPP TS 44.018 [84]) for UTRAN CSG cells in dedicated mode and, if the mobile station is DTM capable, also in dual transfer mode. This capability shall apply to each UTRA radio access mode supported by the mobile. It is coded as follows: Bit 0 Reporting of UTRAN CSG cells not supported 1 Reporting of UTRAN CSG cells supported VAMOS Level (2 bit field) This field indicates the VAMOS support of the MS and the VAMOS level supported. It is coded as follows: Bits 2 1 0 0 VAMOS not supported 0 1 VAMOS I supported 1 0 VAMOS II supported 1 1 VAMOS III supported. TIGHTER Capability (2 bit field) This field indicates Tightened Link Level Performance support in the MS (see 3GPP TS 45.005 [33]). The tightened performance applies to the traffic channels and signalling channels specified in 3GPP TS 45.005 [33]. The field is coded as follows: Bits 2 1 0 0 TIGHTER not supported Selective Ciphering of Downlink SACCH (1 bit field) This field indicates whether the mobile station supports Selective Ciphering of Downlink SACCH (see 3GPP TS 44.018 [84]). It is coded as follows: Bit 0 Selective Ciphering of Downlink SACCH not supported 1 Selective Ciphering of Downlink SACCH supported CS to PS SRVCC from GERAN to UTRA (2 bit field) This field indicates whether the mobile station supports CS to PS SRVCC to UTRAN. If" UMTS FDD Radio Access Technology Capability" and" UMTS 1.28 Mcps TDD Radio Access Technology Capability" bitsare set to ‘0’ this field shall be set to ’00’. If one or both bits are set to ‘1’ this field may be set to ’01’ or ’10’ or ’11’. It is coded as follows: Bits 2 1 0 0 CS to PS SRVCC from GERAN to U MTS FDD and 1.28 Mcps TDD not supported 0 1 CS to PS SRVCC from GERAN to UMTS FDD supported 1 0 CS to PS SRVCC from GERAN to UMTS 1.28 Mcps TDD supported 1 1 CS to PS SRVCC from GERAN to UMTS FDD and 1.28 Mcps TDD supported CS to PS SRVCC from GERAN to E-UTRA (2 bit field) This field indicates whether the mobile station supports CS to PS SRVCC to E-UTRAN. If both "E-UTRA FDD support" and "E-UTRA TDD support" bits are set to ‘0’, this field shall be set to ’00’. If one or both "E-UTRA FDD support" and "E-UTRA TDD support" bits are set to ‘1’, this field may be set to ’01’ or ’10’ or ’11’. A mobile station not compliant to the UE E-UTRA capability requirements as defined in 3GPP TS 36.306 [153] shall set this field to ’00’. It is coded as follows: Bits 2 1 0 0 CS to PS SRVCC from GERAN to E-UTRA FDD and TDD not supported 0 1 CS to PS SRVCC from GERAN to E-UTRA FDD supported 1 0 CS to PS SRVCC from GERAN to E-UTRA TDD supported 1 1 CS to PS SRVCC from GERAN to E-UTRA FDD and TDD supported GERAN Network Sharing support (1 bit field) This field indicates whether the mobile station supports GERAN network sharing. A mobile station supporting GERAN network sharing shall also support the extended EARFCN value range in GERAN and indicate this in the respective bit. The field is coded as follows: Bit 0 GERAN network sharing not supported 1 GERAN network sharing supported E-UTRA Wideband RSRQ measurements support (1 bit field) This field indicates whether the mobile station supports E-UTRA wideband RSRQ measurements (see 3GPP TS 45.008 [151]). It is coded as follows: Bit 0 E-UTRA wideband RSRQ measurements not supported 1 E-UTRA wideband RSRQ measurements supported ER Band Support (1 bit field) This field indicates whether the mobile station supports ER-GSM band (see 3GPP TS 45.005 [33]). It is coded as follows: Bit 0 ER-GSM not supported 1 ER-GSM supported NOTE: When ER-GSM is supported, the associated RF power capability is found in Mobile Station Classmark 1, Mobile Station Classmark 2 and/or Mobile Station Classmark 3. The ER-GSM band associated radio capability is the same as for the R-GSM band (see R-GSM band Associated Radio Capability). UTRA Multiple Frequency Band Indicators support (1 bit field) This field indicates whether the mobile station supports multiple radio frequency bands in UTRAN (see 3GPP TS 25.331 [23c]) and whether it understands signalling of overlapping UTRA frequency bands (see 3GPP TS 44.018 [84]). It is coded as follows: Bit 0 Multiple Frequency Band Indicators in UTRAN not supported 1 Multiple Frequency Band Indicators in UTRAN supported E-UTRA Multiple Frequency Band Indicators support (1 bit field) This field indicates whether the mobile station supports multiple radio frequency bands in E-UTRAN (see 3GPP TS 36.331 [129]) and whether it understands signalling of overlapping E-UTRA frequency bands (see 3GPP TS 44.018 [84]). It is coded as follows: Bit 0 Multiple Frequency Band Indicators in E-UTRAN not supported 1 Multiple Frequency Band Indicators in E-UTRAN supported Extended TSC Set Capability support (1 bit field) This field indicates whether the mobile station supports the extended TSC sets when operating in the PS or CS domain (see 3GPP TS 45.002 [32]). It is coded as follows: Bit 0 Extended TSC sets not supported 1 Extended TSC sets supported Extended EARFCN value range (1 bit field) This field indicates whether the mobile station supports the extended EARFCN value range in GERAN (see 3GPP TS 44.018 [84]). It is coded as follows: Bit 0 Extended EARFCN value range not supported 1 Extended EARFCN value range supported |
10.5.1.8 Spare Half Octet
This element is used in the description of messages in clause 9 when an odd number of half octet type 1 information elements are used. This element is filled with spare bits set to zero and is placed in bits 5 to 8 of the octet unless otherwise specified.
10.5.1.9 Descriptive group or broadcast call reference
The purpose of the Descriptive Group or Broadcast Call Reference is to provide information describing a voice group or broadcast call. The IE of the Descriptive Group or Broadcast Call Reference is composed of the group or broadcast call reference together with a service flag, an acknowledgement flag, the call priority and the group cipher key number.
The Descriptive Group or Broadcast Call Reference information element is coded as shown in figure 10.5.8/3GPP TS 24.008 and Table10.5.8/3GPP TS 24.008
The Descriptive Group or Broadcast Call Reference is a type 3 information element with 6 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Group or broadcast call reference IEI |
octet 1 |
|||||||
Binary coding of the group or broadcast call reference |
octet 2 |
|||||||
octet 3 |
||||||||
octet 4 |
||||||||
SF |
AF |
call priority |
octet 5 |
|||||
Spare |
||||||||
Ciphering information |
0 |
0 |
0 |
0 |
octet 6 |
Figure 10.5.8/3GPP TS 24.008 Descriptive Group or Broadcast Call Reference
Table 10.5.8/3GPP TS 24.008 Descriptive Group or Broadcast Call Reference
Binary code of the group or broadcast call reference The length of the binary code has 27 bits which is encoded in the octet 2, 3, 4 and Bits 8,7,6 (octet 5). The highest bit of the BC is the bit 8 in the octet 2 and the lowest bit is allocated in the bit 6 in the octet 5. (see also 3GPP TS 23.003 [10]) |
||||
SF Service flag (octet 5) |
||||
Bit |
||||
5 |
||||
0 |
VBS (broadcast call reference) |
|||
1 |
VGCS (group call reference) |
|||
AF Acknowledgement flag (octet 5), network to MS direction: |
||||
Bit |
||||
4 |
||||
0 |
acknowledgement is not required |
|||
1 |
acknowledgement is required |
|||
Call priority (octet 5) |
||||
Bit |
||||
3 |
2 |
1 |
||
0 |
0 |
0 |
no priority applied |
|
0 |
0 |
1 |
call priority level 4 |
|
0 |
1 |
0 |
call priority level 3 |
|
0 |
1 |
1 |
call priority level 2 |
|
1 |
0 |
0 |
call priority level 1 |
|
1 |
0 |
1 |
call priority level 0 |
|
1 |
1 |
0 |
call priority level B |
|
1 |
1 |
1 |
call priority level A |
|
Ciphering information (octet 6) |
||||
Bit |
||||
8 |
7 |
6 |
5 |
|
0 |
0 |
0 |
0 |
no ciphering |
0 |
0 |
0 |
1 |
ciphering with cipher key number 1 |
0 |
0 |
1 |
0 |
ciphering with cipher key number 2 |
0 |
0 |
1 |
1 |
ciphering with cipher key number 3 |
0 |
1 |
0 |
0 |
ciphering with cipher key number 4 |
0 |
1 |
0 |
1 |
ciphering with cipher key number 5 |
0 |
1 |
1 |
0 |
ciphering with cipher key number 6 |
0 |
1 |
1 |
1 |
ciphering with cipher key number 7 |
1 |
0 |
0 |
0 |
ciphering with cipher key number 8 |
1 |
0 |
0 |
1 |
ciphering with cipher key number 9 |
1 |
0 |
1 |
0 |
ciphering with cipher key number A |
1 |
0 |
1 |
1 |
ciphering with cipher key number B |
1 |
1 |
0 |
0 |
ciphering with cipher key number C |
1 |
1 |
0 |
1 |
ciphering with cipher key number D |
1 |
1 |
1 |
0 |
ciphering with cipher key number E |
1 |
1 |
1 |
1 |
ciphering with cipher key number F |
AF Acknowledgement flag (octet 5), MS to network direction: |
||||
Bit 4 is spare and shall be set to "0". |
||||
Call priority (octet 5) |
||||
Bits 1 to 3 are spare and shall be set to "0". |
||||
Ciphering information (octet 6) |
||||
Bits 5 to 8 are spare and shall be set to "0". |
||||
10.5.1.10 Group Cipher Key Number
The purpose of the Group Cipher Key Number is to provide information on the group cipher key to be used for ciphering and deciphering by the mobile station.
The Group Cipher Key Number information element is coded as shown in figure 10.5.9/3GPP TS 24.008 and Table10.5.9/3GPP TS 24.008
The Group Cipher Key Number is a type 1 information element with 1 octet length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Group cipher key number IEI |
Group cipher key number |
Figure 10.5.9/3GPP TS 24.008 Group Cipher Key Number
Table 10.5.9/3GPP TS 24.008 Group Cipher Key Number
Group cipher key number |
||||
Bit |
||||
4 |
3 |
2 |
1 |
|
0 |
0 |
0 |
0 |
spare |
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 |
10.5.1.10a PD and SAPI $(CCBS)$
The purpose of the PD and SAPI information element is to provide information concerning Protocol Discriminators and Service Access Point Identifiers.
The PD and SAPI information element is coded as shown in figure 10.5.10/3GPP TS 24.008 and table 10.5.10/3GPP TS 24.008.
The PD and SAPI is a type 3 information element with 2 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
PD and SAPI IEI |
octet 1 |
|||||||
0 spare |
0 spare |
SAPI |
PD |
octet 2 |
Figure10.5.10/3GPP TS 24.008
PD and SAPI information element
Table 10.5.1.10/3GPP TS 24.008: PD and SAPI information element
SAPI: Service Access Point Identifier (octet 2) |
|||
Bits |
|||
6 |
5 |
||
0 |
0 |
SAPI 0 |
|
0 |
1 |
reserved |
|
1 |
0 |
reserved |
|
1 |
1 |
SAPI 3 |
|
PD: Protocol Discriminator (octet 2) |
|||
bits 4-1 |
|||
Encoded as specified in subclause 11.2.1 of 3GPP TS 24.007 [20]. |
|||
10.5.1.11 Priority Level
The purpose of the Priority Level is to provide information defining the priority level requested or applied. The Priority Level IE may be included in CM_SERVICE_REQUEST, CALL_PROCEEDING and SETUP messages.
The Priority Level information element is coded as shown in figure 10.5.11/3GPP TS 24.008 and table 10.5.11/3GPP TS 24.008.
The Priority Level is a type 1 information element with 1 octet length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Priority Level IEI |
0 spare |
call priority |
octet 1 |
Figure 10.5.11/3GPP TS 24.008 Priority Level
Table 10.5.11/3GPP TS 24.008 Priority Level
Call priority (octet 1) |
|||
Bit |
|||
3 |
2 |
1 |
|
0 |
0 |
0 |
no priority applied |
0 |
0 |
1 |
call priority level 4 |
0 |
1 |
0 |
call priority level 3 |
0 |
1 |
1 |
call priority level 2 |
1 |
0 |
0 |
call priority level 1 |
1 |
0 |
1 |
call priority level 0 |
1 |
1 |
0 |
call priority level B |
1 |
1 |
1 |
call priority level A |
10.5.1.12 Core Network System Information (Iu mode only)
The purpose of the Core Network System Information is to provide the MS with actual parameter settings of system information parameters controlling MM and GMM functionality. The Core Network system information is included in specific information elements within some RRC messages sent to MS, see 3GPP TS 25.331 [23c].
NOTE: These IEs do not have an IEI or a length indicator, because these IEs are never present in any layer 3 messages, Hence these IEs do not conform to the general IE rules defined in 3GPP TS 24.007 [20].
10.5.1.12.1 CN Common GSM-MAP NAS system information
The purpose of the CN Common GSM-MAP NAS system information element is to provide the MS with actual parameter settings of parameters relevant for both MM and GMM functionality. The coding of the information element identifier and length information is defined in the 3GPP TS 25.331 [23c]. Only the coding of the content is in the scope of the present document.
The content of the CN common GSM-MAP NAS system information element is coded as shown in figure 10.5.1.12.1/3GPP TS 24.008 and table 10.5.1.12.1/3GPP TS 24.008.
The length of this element content is two octets. The MS shall ignore any additional octets received.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
LAC |
octet 1 |
|||||||
octet 2 |
Figure 10.5.1.12.1/3GPP TS 24.008 Common system information element
Table 10.5.1.12.1/3GPP TS 24.008: Common system information element
LAC, Location Area Code (2 octet field) |
10.5.1.12.2 CS domain specific system information
The purpose of the CN domain specific GSM-MAP NAS system information element, when used for the CS domain, is to provide the MS with actual parameter settings of parameters relevant only for MM functionality. The coding of the information element identifier and length information is defined in the 3GPP TS 25.331 [23c]. Only the coding of the content is in the scope of the present document.
For CS domain, the content of the CN domain specific GSM-MAP NAS system information element is coded as shown in figure 10.5.1.12.2/3GPP TS 24.008 and table 10.5.1.12.2/3GPP TS 24.008. The length of this element content is two octets. The MS shall ignore any additional octets received.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
T3212 |
octet 1 |
|||||||
Spare |
ATT |
octet 2 |
Figure 10.5.1.12.2/3GPP TS 24.008 CS domain specific system information element
Table 10.5.1.12.2/3GPP TS 24.008: CS domain specific system information element
T3212 timeout value (1 octet field) |
ATT, Attach-detach allowed (1 bit field): |
The bits 2 – 8 of octet 2 are spare and shall be coded all zeros. |
10.5.1.12.3 PS domain specific system information
The purpose of the CN domain specific GSM-MAP NAS system information element, when used for the PS domain, is to provide the MS with actual parameter settings of parameters relevant only for GMM functionality. The coding of the information element identifier and length information is defined in the 3GPP TS 25.331 [23c]. Only the coding of the content is in the scope of the present document.
For PS domain, the content of the CN domain specific GSM-MAP NAS system information element is coded as shown in figure 10.5.1.12.3/3GPP TS 24.008 and table 10.5.1.12.3/3GPP TS 24.008. The length of this element content is two octets. The MS shall ignore any additional octets received.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||||
RAC |
octet 1 |
|||||||||||
Spare |
NMO I |
NMO |
octet 2 |
Figure 10.5.1.12.3/3GPP TS 24.008 PS domain specific system information element
Table 10.5.1.12.3/3GPP TS 24.008: PS domain specific system information element
RAC, Routing Area Code (8 bit field) |
NMO, Network Mode of Operation (1 bit field) |
NMO I, Network Mode of Operation I (1 bit field) |
The bits 3 – 8 of octet 2 are spare and shall be coded all zeros. |
10.5.1.13 PLMN list
The purpose of the PLMN List information element is to provide a list of PLMN codes to the mobile station.
The PLMN List information element is coded as shown in figure 10.5.13/3GPP TS 24.008 and table 10.5.13/3GPP TS 24.008.
The PLMN List is a type 4 information element with a minimum length of 5 octets and a maximum length of 47 octets.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
PLMN List IEI |
octet 1 |
|||||||
Length of PLMN List contents |
octet 2 |
|||||||
MCC digit 2, PLMN 1 |
MCC digit 1, PLMN 1 |
octet 3 |
||||||
MNC digit 3, PLMN 1 |
MCC digit 3, PLMN 1 |
octet 4 |
||||||
MNC digit 2, PLMN 1 |
MNC digit 1, PLMN 1 |
octet 5 |
||||||
MCC digit 2, PLMN 15 |
MCC digit 1, PLMN 15 |
octet 45 |
||||||
MNC digit 3, PLMN 15 |
MCC digit 3, PLMN 15 |
octet 46 |
||||||
MNC digit 2, PLMN 15 |
MNC digit 1, PLMN 15 |
octet 47 |
Figure 10.5.13/3GPP TS 24.008 PLMN List information element
Table 10.5.13/3GPP TS 24.008: PLMN List information element
MCC, Mobile country code (octet 3, octet 4 bits 1 to 4) The MCC field is coded as in ITU-T Rec. E212, Annex A. MNC, Mobile network code (octet 5, octet 4 bits 5 to 8). The coding of this field is the responsibility of each administration but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. For PCS 1900 for NA, Federal regulation mandates that a 3-digit MNC shall be used. However a network operator may decide to use only two digits in the MNC over the radio interface. In this case, bits 5 to 8 of octet 4 shall be coded as "1111". Mobile equipment shall accept MNC coded in such a way. |
10.5.1.14 NAS container for PS HO
The purpose of the NAS container for PS HO information element is to indicate the NAS specific information for the PS handover to A/Gb mode. The NAS container for PS HO information element is included in the PS HO command message, see 3GPP TS 44.060 [76]. The coding of the information element identifier and length information is defined in 3GPP TS 44.060 [76].
The content of the NAS container for PS HO information element is coded as shown in figure 10.5.1.14/3GPP TS 24.008 and table 10.5.1.14/3GPP TS 24.008. The length of this information element is 5 octets. The MS shall ignore any additional octets received.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
0 spare |
0 spare |
0 spare |
old |
0 spare |
Type of ciphering algorithm |
octet 1 |
||
IOV-UI value (High-order octet) |
octet 2 |
|||||||
IOV-UI value (continued) |
octet 3 |
|||||||
IOV-UI value (continued) |
octet 4 |
|||||||
IOV-UI value (Low-order octet) |
octet 5 |
Figure 10.5.1.14/3GPP TS 24.008 NAS container for PS HO information element
Table 10.5.1.14/3GPP TS 24.008: NAS container for PS HO information element
Type of ciphering algorithm (octet 1, bits 1 to 3) |
||||
Bits |
||||
3 |
2 |
1 |
||
0 |
0 |
0 |
ciphering not used |
|
0 |
0 |
1 |
GPRS Encryption Algorithm GEA/1 |
|
0 |
1 |
0 |
GPRS Encryption Algorithm GEA/2 |
|
0 |
1 |
1 |
GPRS Encryption Algorithm GEA/3 |
|
1 |
0 |
0 |
GPRS Encryption Algorithm GEA/4 |
|
1 |
0 |
1 |
GPRS Encryption Algorithm GEA/5 |
|
1 |
1 |
0 |
GPRS Encryption Algorithm GEA/6 |
|
1 |
1 |
1 |
GPRS Encryption Algorithm GEA/7 |
|
Bit 4 of octet 1 is spare and shall be coded as zero. |
||||
old XID (octet 1, bit 5): Bit 5 |
||||
0 The MS shall perform a Reset of LLC and SNDCP without old XID indicator as specified in |
||||
1 The MS shall perform a Reset of LLC and SNDCP with old XID indicator as specified in |
||||
The bits 6 – 8 of octet 1 are spare and shall be coded all zeroes. |
||||
IOV-UI value (octet 2 to 5) |
||||
10.5.1.15 MS network feature support
The purpose of the MS network feature support information element is to indicate support of mobility management parameters during the tracking area updating, location updating, routing area updating, IMSI attach, GPRS attach, and EPS attach procedures.
The MS network feature support information element is coded as shown in figure 10.5.1.15/3GPP TS 24.008 and table 10.5.1.15/3GPP TS 24.008.
The MS network feature support information element is a type 1 information element.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
MS network feature support IEI |
0 Spare |
0 Spare |
0 Spare |
extended periodic timers |
octet 1 |
Figure 10.5.1.15/3GPP TS 24.008: MS network feature support information element
Table 10.5.1.15/3GPP TS 24.008: MS network feature support information element
Extended periodic timers (octet 1) |
|
Bit |
|
1 |
|
0 |
MS does not support the extended periodic timer in this domain |
1 |
MS supports the extended periodic timer in this domain |
The relevant extended periodic timer is T3212 for MM messages, T3312 for GMM messages, and T3412 for EMM messages. |
|
Bits 4, 3 and 2 of octet 1 are spare and shall be coded as zero. |
|