## 10.5.1 Common information elements

04.083GPPMobile radio interface Layer 3 specificationRelease 1998TS

#### 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 04.08 and table 10.5.1/3GPP TS 04.08.

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 04.08: Cell Identity information element

Table 10.5.1/3GPP TS 04.08: 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

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 message to the mobile station where it is stored together with the calculated ciphering key Kc.

The Ciphering Key Sequence Number information element is coded as shown in figure 10.5.2/3GPP TS 04.08 and table 10.5.2/3GPP TS 04.08.

The ciphering key sequence number is a type 1 information element.

8 7 6 5 4 3 2 1

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

│ │Ciphering Key │ │ key sequence │ octet 1

│ │Sequence Number │ 0 │ │

│ │ IEI │spare│ │

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

Figure 10.5.2/3GPP TS 04.08: Ciphering Key Sequence Number information element

Table 10.5.2/3GPP TS 04.08: 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 GSM system.

The Location Area Identification information element is coded as shown in figure 10.5.3/3GPP TS 04.08 and table 10.5.3/3GPP TS 04.08.

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 04.08: Location Area Identification information element

Table 10.5.3/3GPP TS 04.08: 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 thevalue from the deleted LAI.In abnormal cases, the MCC stored in the mobilestation can contain elements not in the set{0, 1 … 9}. In such cases the mobile station shouldtransmit the stored values using full hexadecimalencoding. When receiving such an MCC, the networkshall 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 eachadministration 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 mobilestation 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 stationshall transmit the stored values using full hexadecimal encoding. When receiving such an MNC, thenetwork 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 mostsignificant bit and bit 1 of octet 6 the leastsignificant bit.The coding of the location area code is theresponsibility of each administration except thattwo values are used to mark the LAC, and hence theLAI, as deleted. Coding using full hexadecimalrepresentation may be used. The location area codeconsists of 2 octets.If a LAI has to be deleted then all bits of thelocation area code shall be set to one with theexception of the least significant bit which shall beset to zero. If a SIM is inserted in a Mobile Equipmentwith the location area code containing all zeros, thenthe Mobile Equipment shall recognise this LAC as partof 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, the international mobile equipment identity, IMEI or the international mobile equipment identity together with the software version number, IMEISV.

The IMSI shall not exceed 15 digits, the TMSI/P-TMSI is 4 octets long, and the IMEI is composed of 15 digits, the IMEISV is 16 digits (see 3GPP TS 03.03).

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 all other transactions except emergency call establishment, emergency call re-establishment, mobile terminated call establishment, the identification procedure, the GMM identification procedure, the GMM authentication and ciphering procedure and the ciphering mode setting procedure, 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.

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.

2) IMSI: The IMSI shall be used in cases where no TMSI is available.

3) IMEI: The IMEI shall be used in cases where no SIM is available or the SIM 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.

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 04.08 and table 10.5.4/3GPP TS 04.08.

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

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

│ │odd/ │ │

│ Identity digit 1 │even │ Type of identity│ octet 3

│ │indic│ │

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

│ │ │

│ Identity digit p+1 │ Identity digit p │ octet 4*

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

Figure 10.5.4/3GPP TS 04.08: Mobile Identity information element

Table 10.5.4/3GPP TS 04.08: 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 │

│ 0 0 0 No Identity (note) │

│ │

│ 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 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". │

│ │

│ If the mobile identity is the TMSI/P-TMSI then bits 5 │

│ to 8 of octet 3 are coded as "1111" and bit 8 of octet │

│ 4 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. │

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

NOTE: This can be used in the case when a fill paging message without any valid identity has to be sent on the paging subchannel.

#### 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 04.08 and table 10.5.5/3GPP TS 04.08.

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 │ Revision │ ES │ A5/1│ RF power │

│spare│ level │ IND │ │ capability │octet 2

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

Figure 10.5.5/3GPP TS 04.08: Mobile Station Classmark 1 information element

Table 10.5.5/3GPP TS 04.08: Mobile Station Classmark 1 information element

 Revision level (octet 2) Bits 7 6 0 0 Reserved for phase 1 0 1 Used by phase 2 mobile stations All other values are 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 0 "Controlled Early Classmark Sending" option is not implemented in the MS 1 "Controlled Early Classmark Sending" option is implemented in the MS NOTE: 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 value. A5/1 algorithm supported (octet 2, bit 4) 0 encryption algorithm A5/1 available 1 encryption algorithm A5/1 not available RF power capability (octet 2) When the GSM P, E [or R] 900 MHz band is used (for exceptions see 3.4.18): 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 DCS 1800 or PCS 1900 band is used (for exceptions see 3.4.18): Bits 3 2 1 0 0 0 class 1 0 0 1 class 2 0 1 0 class 3 All other values are reserved.

#### 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 04.08, table 10.5.6a/3GPP TS 04.08 and table 10.5.6b/3GPP TS 04.08.

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 │ Revision │ ES │ A5/1│ RF power │

│spare│ level │ IND │ │ capability │ octet 3

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

│ 0 │ PS │ SS Screen.│SM ca│VBS │VGCS │ FC │

│spare│capa.│ Indicator │pabi.│ │ │ │ octet 4

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

│ CM3 │ 0 │LCSVA│ 0 │SoLSA│CMSP │ A5/3│ A5/2│

│ │Spare│ Cap │spare│ │ │ │ │ octet 5

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

Figure 10.5.6/3GPP TS 04.08: Mobile Station Classmark 2 information element

NOTE: 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".

Table 10.5.6a/3GPP TS 04.08: Mobile Station Classmark 2 information element

 Revision level (octet 3) Bits 7 6 0 0 Reserved for phase 1 0 1 Used by phase 2 mobile stationsAll other values are 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 0 "Controlled Early Classmark Sending" option is not implemented in the MS 1 "Controlled Early Classmark Sending" option is implemented in the MSNOTE: 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 value.A5/1 algorithm supported (octet 3, bit 4) 0 encryption algorithm A5/1 available 1 encryption algorithm A5/1 not availableRF Power Capability (Octet 3)When GSM 900 P, E [or R] band is used (for exceptions see 3.4.18): 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 5All other values are reserved.When the DCS 1800 or PCS 1900 band is used (for exceptions see 3.4.18): Bits 3 2 1 0 0 0 class 1 0 0 1 class 2 0 1 0 class 3All other values are reserved.PS capability (pseudo-synchronization capability) (octet 4)Bit 7 0 PS capability not present 1 PS capability presentSS Screening Indicator (octet 4)Bits 6 5 0 0 defined in 3GPP TS 04.80 0 1 defined in 3GPP TS 04.80 1 0 defined in 3GPP TS 04.80 1 1 defined in 3GPP TS 04.80SM capability (MT SMS pt to pt capability) (octet 4) Bit 40 Mobile station does not support mobile terminated point to point SMS1 Mobile station supports mobile terminated point to point SMS

Table 10.5.6b/3GPP TS 04.08: Mobile Station Classmark 2 information element

 VBS notification reception (octet 4)Bit 30 no VBS capability or no notifications wanted1 VBS capability and notifications wantedVGCS notification reception (octet 4)Bit 20 no VGCS capability or no notifications wanted1 VGCS capability and notifications wantedFC Frequency Capability (octet 4)When a GSM 900 band is used (for exceptions see 3.4.18):Bit 10 The MS does not support the E-GSM or R-GSM band (For definition of frequency bands see 3GPP TS 05.05)1 The MS does support the E-GSM or R-GSM (For definition of frequency bands see 3GPP TS 05.05)Note : For mobile station supporting the R-GSM band further information can be found in MS Classmark 3.When the DCS 1800 band is used (for exceptions see 3.4.18):Bit 10 Reserved for future use (for definition of frequency bands see 3GPP TS 05.05)NOTE: This bit conveys no information about support or non support of the E-GSM or R-GSM band when transmitted on a DCS 1800 channel.CM3 (octet 5, bit 8)0 The MS does not support any options that are indicated in CM31 The MS supports options that are indicated in classmark 3 IELCS VA capability (LCS value added location request notification capability) (octet 5,bit 6)0 LCS value added location request notification capability not supported1 LCS value added location request notification capability supportedSoLSA (octet 5, bit 4)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)0 encryption algorithm A5/3 not available1 encryption algorithm A5/3 availableA5/2 algorithm supported (octet 5, bit 1)0 encryption algorithm A5/2 not available1 encryption algorithm A5/2 available

NOTE: Additional mobile station capability information might be obtained by invoking the classmark interrogation procedure.

#### 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 MS Classmark 3 is a type 4 information element with a maximum of 14 octets length.

The value part of a MS Classmark 3 information element is coded as shown in figure 10.5.7/3GPP TS 04.08 and table 10.5.7/3GPP TS 04.08.

NOTE: The 14 octet limit is so that the CLASSMARK CHANGE message will fit in one layer 2 frame.

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 field in the MS Classmark 3.

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 05.02).

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 <Multi Slot Capability>}

<UCS2 treatment: bit>

<Extended Measurement Capability : bit>

{ 0 | 1 <MS measurement capability> }

{ 0 | 1 <MS Positioning Method Capability> }

<spare bit>;

<A5 bits> ::= <A5/7 : bit> <A5/6 : bit> <A5/5 : bit> <A5/4 : bit> ;

<R Support>::=

< R-GSM band Associated Radio Capability : bit(3)>;

<Multi Slot Capability> ::=

<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)>;

Figure 10.5.7/3GPP TS 04.08: Mobile Station Classmark 3 information element

Table 10.5.7/3GPP TS 04.08: Mobile Station Classmark 3 information element

#### 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 04.08 and Table10.5.8/3GPP TS 04.08.

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 04.08: Descriptive Group or Broadcast Call Reference

Table 10.5.8/3GPP TS 04.08: 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 │

│ │

│ SF Service flag (octet 5) │

│ Bit │

│ 5 │

│ 0 VBS (broadcast call reference) │

│ 1 VGCS (group call reference) │

│ │

│ AF Acknowledgement flag (octet 5) │

│ 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 │

│ │

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

#### 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 04.08 and Table10.5.9/3GPP TS 04.08

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 04.08: Group Cipher Key Number

Table 10.5.9/3GPP TS 04.08: 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 04.08 and table 10.5.10/3GPP TS 04.08.

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 │ 0 │ SAPI │ PD │

│spare│spare│ │ │octet 2

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

Figure10.5.10/3GPP TS 04.08: PD and SAPI information element

Table 10.5.1.10/3GPP TS 04.08: 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 sub-clauses 11.2.1 of 04.07.

#### 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 04.08 and table 10.5.11/3GPP TS 04.08.

The Priority Level is a type 1 information element with 1 octet length.

8 7 6 5 4 3 2 1

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

│ │ Priority Level │ 0 │ call priority │

│ │ IEI │spare│ │ octet 1

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

Figure 10.5.11/3GPP TS 04.08: Priority Level

Table 10.5.11/3GPP TS 04.08: 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 │

│ │

│ │

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