10.5.2 Radio Resource management information elements.
04.183GPPMobile radio interface Layer 3 specificationRadio Resource Control (RRC) protocolRelease 1999TS
10.5.2.1a BA Range
The purpose of the BA Range information element is to provide the mobile station with ARFCN range information which can be used in the cell selection procedure.
The BA Range information element is coded as shown in figure 10.5.21a.1 and table 10.5.2.1a.1.
The BA Range is a type 4 information element with a minimum length of 6 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 04.06).
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
BA RANGE IEI | octet 1 | |||||||
Length of BA Range contents | octet 2 | |||||||
Number of Ranges | octet 3 | |||||||
RANGE1_LOWER (high part) | octet 4 | |||||||
RANGE1_LOWER | RANGE1_HIGHER | octet 5 | ||||||
RANGE1_HIGHER | RANGE2_LOWER | octet 6 | ||||||
RANGE2_LOWER | RANGE2_HIGHER | octet 7 | ||||||
RANGE2_HIGHER (low part) | octet 8 | |||||||
RANGE3_LOWER (high part) | octet 9 | |||||||
RANGE3_LOWER | RANGE3_HIGHER | octet 10 | ||||||
RANGE3_HIGHER | RANGE4_LOWER | octet 11 | ||||||
RANGE4_LOWER | RANGE4_HIGHER | octet 12 | ||||||
RANGE4_HIGHER (low part) | octet 13 | |||||||
octet n |
Figure 10.5.2.1a.1: BA RANGE information element
Table 10.5.2.1a.1: BA Range information element
Number of Ranges parameter The number of Ranges parameter indicates in binary the number of ranges to be transmitted in the IE. It shall have a minimum value of 1. |
RANGEi_LOWER If $(impr-BA-range-handling)$ is not supported: $begin The RANGEi_LOWER is coded as the binary representation of the ARFCN used as the lower limit of a range of frequencies to be used by the mobile station in cell selection (see 3GPP TS 05.08 and 3GPP TS 03.22) $end If $(impr-BA-range-handling)$ is supported: $begin The RANGEi_LOWER is coded as the binary representation of the ARFCN used as the lower limit of a range of frequencies which could be used by the mobile station in cell selection (see 3GPP TS 05.08 and 3GPP TS 03.22) $end |
RANGEi_HIGHER If $(impr-BA-range-handling)$ is not supported: $begin The RANGEi_HIGHER is coded as the binary representation of the ARFCN used as the higher limit of a range of frequencies to be used by the mobile station in cell selection (see 3GPP TS 05.08 and 3GPP TS 03.22) $end If $(impr-BA-range-handling)$ is supported: $begin The RANGEi HIGHER is coded as the binary representation of the ARFCN used as the higher limit of a range of frequencies which could be used by the mobile station in cell selection (see 3GPP TS 05.08 and 3GPP TS 03.22) $end If the length of the BA range information element is greater than the number of octets required to carry the Number of Ranges given in octet 3, then any unused octets or parts of octets at the end of the IE shall be considered as spare. If $(impr-BA-range-handling)$ is supported: If a mobile station receives range information which has ranges or part of the ranges which are not supported by the mobile station, the mobile station shall take into account those parts of the ranges which it does support. |
10.5.2.1b Cell Channel Description
The purpose of the Cell Channel Description information element is to provide the reference frequency list to be used to decode the mobile allocation information element.
The Cell Channel Description is a type 3 information element with 17 octets length.
There are several formats for the Cell Channel Description information element, distinguished by the "format indicator" subfield. Some formats are frequency bit maps, the others use a special encoding scheme.
NOTE: No more than 64 RF channels should be encoded in the Cell Allocation since this is the maximum number of RF channels which can be referenced in the Mobile Allocation IE.
10.5.2.1b.1 General description
Figure 10.5.2.1b.1.1/04.18 shows only a special bit numbering. The different general format is described in table 10.5.2.1b.1.1/04.18.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Cell Channel Description IEI | octet 1 | |||||||
Bit | Bit | 0 | 0 | Bit | Bit | Bit | Bit | octet 2 |
Bit | Bit | Bit | Bit | Bit | Bit | Bit | Bit | octet 3 |
Bit | Bit | Bit | Bit | Bit | Bit | Bit | Bit | octet 17 |
Figure 10.5.2.1b.1.1: Cell Channel Description information element (general format)
Table 10.5.2.1b.1.1: Cell Channel Description information element, general format
FORMAT-ID, Format Identifier (Bit 128 and next) The different formats are distinguished by the bits of higher number. The possible values are the following: Bit Bit Bit Bit Bit format notation 128 127 124 123 122 0 0 X X X bit map 0 1 0 0 X X 1024 range 1 0 1 0 0 512 range 1 0 1 0 1 256 range 1 0 1 1 0 128 range 1 0 1 1 1 variable bit map All other combinations are reserved for future use. A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (see 3GPP TS 05.05) may consider all values except the value for bit map 0 as reserved. The significance of the remaining bits depends on the FORMAT-ID. The different cases are specified in the next sub-clauses. Mobile stations shall treat all ARFCNs in the set {0, 1, 2 … 1023} as valid ARFCN values even if the mobile station is unable to transmit or receive on that ARFCN. |
10.5.2.1b.2 Bit map 0 format
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Cell Channel Description IEI | octet 1 | |||||||
0 | 0 | 0 | 0 | CA | CA | CA | CA | |
FORMAT-ID | spare | spare | ARFCN | ARFCN | ARFCN | ARFCN | octet 2 | |
CA | CA | CA | CA | CA | CA | CA | CA | octet 3 |
CA | CA | CA | CA | CA | CA | CA | CA | octet 17 |
Figure 10.5.2.1b.2.1: Cell Channel Description information element, bit map 0 format
Table 10.5.2.1b.2.1: Cell channel Description information element, bit map 0 format
CA ARFCN N, Cell Allocation Absolute RF Channel Number N (octet 2 etc.) For a RF channel with ARFCN = N belonging to the cell allocation the CA ARFCN N bit is coded with a "1"; N = 1, 2, .. , 124. For a RF channel with ARFCN = N not belonging to the cell allocation the CA ARFCN N bit is coded with a "0"; N = 1, 2 .. , 124. |
10.5.2.1b.3 Range 1024 format
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Cell Channel Description IEI | octet 1 | |||||||
1 | 0 | 0 | 0 | 0 | ||||
FORMAT-ID | spare | spare | FORMAT-ID | F0 | W(1) | octet 2 | ||
W(1) (low part) | octet 3 | |||||||
W(2) (high part) | octet 4 | |||||||
W(2) | W(3) | octet 5 | ||||||
W(3) | W(4) | octet 6 | ||||||
W(4) | W(5) | octet 7 | ||||||
W(5) | W(6) | octet 8 | ||||||
W(6) | W(7) | octet 9 | ||||||
W(7) | W(8) | octet 10 | ||||||
W(8) | W(9) | octet 11 | ||||||
W(10) | W(11) | octet 12 | ||||||
W(11) | W(12) | octet 13 | ||||||
W(12) (low part) | W(13) (high part) | octet 14 | ||||||
W(13) (low part) | W(14) (high part) | octet 15 | ||||||
W(14) (low part) | W(15) (high part) | octet 16 | ||||||
W(15) | W(16) | octet 17 |
Figure 10.5.2.1b.3.1: Cell Channel Description information element,
1024 range format
Table 10.5.2.1b.3.1: Cell Channel Description information element,
range 1024 format
F0, frequency 0 indicator (octet 2, bit 3): 0 ARFCN 0 is not a member of the set 1 ARFCN 0 is a member of the set W(i), i from 1 to 16 (octet 2 to 17): Each W(i) encodes a non negative integer in binary format. If W(k) is null, W(k+1) to W(16) must be null also. Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The computation formulas are given in sub-clause 10.5.2.13.3. |
10.5.2.1b.4 Range 512 format
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Cell Channel Description IEI | octet 1 | |||||||
1 | 0 | 0 | 0 | 1 | 0 | 0 | ORIG- | |
FORMAT-ID | spare | spare | FORMAT-ID | ARFCN | octet 2 | |||
ORIG-ARFCN (middle part) | octet 3 | |||||||
ORIG- | W(1) | octet 4 | ||||||
W(1) | W(2) | octet 5 | ||||||
W(2) | W(3) | octet 6 | ||||||
W(3) | W(4) | octet 7 | ||||||
W(4) | W(5) | octet 8 | ||||||
W(6) | W(7) | octet 9 | ||||||
W(7) | W(8) | octet 10 | ||||||
W(8) (low part) | W(9) (high part) | octet 11 | ||||||
W(9) | W(10) | octet 12 | ||||||
W(11) | W(12) | octet 13 | ||||||
W(12) (low part) | W(13) (high part) | octet 14 | ||||||
W(13) | W(14) | octet 15 | ||||||
W(15) | W(16) | octet 16 | ||||||
W(16) (low part) | W(17) | octet 17 |
Figure 10.5.2.1b.4.1: Cell Channel Description information element,
512 range format
Table 10.5.2.1b.4.1: Cell Channel Description information element,
range 512 format
ORIG-ARFCN, origin ARFCN (octet 2, 3 and 4) This field encodes the ARFCN of one frequency belonging to the set. This value is also used to decode the rest of the element. W(i), i from 1 to 17 (octet 4 to 17): Each W(i) encodes a non negative integer in binary format. If W(k) is null, W(k+1) to W(17) must be null also. Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The computation formulas are given in sub-clause 10.5.2.13.4. |
10.5.2.1b.5 Range 256 format
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Cell Channel Description IEI | octet 1 | |||||||
1 | 0 | 0 | 0 | 1 | 0 | 1 | ORIG- | |
FORMAT-ID | spare | spare | FORMAT-ID | ARFCN | octet 2 | |||
ORIG-ARFCN (middle part) | octet 3 | |||||||
ORIG- | W(1) | octet 4 | ||||||
W(1) | W(2) | octet 5 | ||||||
W(3) | W(4) | octet 6 | ||||||
W(4) (low part) | W(5) (high part) | octet 7 | ||||||
W(5) (low part) | W(6) (high part) | octet 8 | ||||||
W(6) | W(7) | W(8) | octet 9 | |||||
W(8) (low part) | W(9) (high part) | octet 10 | ||||||
W(9) | W(10) | W(11) | octet 11 | |||||
W(11) (low part) | W(12) | octet 12 | ||||||
W(13) | W(14) (high part) | octet 13 | ||||||
W(14) | W(15) | W(16) | octet 14 | |||||
W(16) | W(17) | W(18) | octet 15 | |||||
W(18) | W(19) | W(20) | octet 16 | |||||
W(20) | W(21) | 0 | octet 17 |
Figure 10.5.2.1b.5.1: Cell Channel Description information element,
range 256 format
Table 10.5.2.1b.5.1: Cell Channel Description information element,
range 256 format
ORIG-ARFCN, origin ARFCN (octet 2, 3 and 4) This field encodes the ARFCN of one frequency belonging to the set. This value is also used to decode the rest of the element. W(i), i from 1 to 21 (octet 4 to 17): Each W(i) encodes a non negative integer in binary format. If W(k) is null, W(k+1) to W(21) must be null also. Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The computation formulas are given in sub-clause 10.5.2.13.5. |
10.5.2.1b.6 Range 128 format
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Cell Channel Description IEI | octet 1 | |||||||
1 | 0 | 0 | 0 | 1 | 1 | 0 | ORIG- | |
FORMAT-ID | spare | spare | FORMAT-ID | ARFCN | octet 2 | |||
ORIG-ARFCN | octet 3 | |||||||
ORIG- | W(1) | octet 4 | ||||||
W(2) | W(3) | octet 5 | ||||||
W(3) (low part) | W(4) (high part) | octet 6 | ||||||
W(4) | W(5) | W(6) | octet 7 | |||||
W(6) (low part) | W(7) | octet 8 | ||||||
W(8) | W(9) | octet 9 | ||||||
W(10) | W(11) | octet 10 | ||||||
W(12) | W(13) | octet 11 | ||||||
W(14) | W(15) | octet 12 | ||||||
W(16) | W(17) | W(18) | octet 13 | |||||
W(18) | W(19) | W(20) | W(21) | octet 14 | ||||
W(21) | W(22) | W(23) | octet 15 | |||||
W(24) | W(25) | W(26) | octet 16 | |||||
W(26) | W(27) | W(28) | 0 | octet 17 |
Figure 10.5.2.1b.6.1/: Cell Channel Description information element,
range 128 format
Table 10.5.2.1b.6.1: Cell Channel Description information element,
range 128 format
ORIG-ARFCN, origin ARFCN (octet 2, 3 and 4) This field encodes the ARFCN of one frequency belonging to the set. This value is also used to decode the rest of the element. W(i), i from 1 to 28 (octet 4 to 17): Each W(i) encodes a non negative integer in binary format. If W(k) is null, W(k+1) to W(28) must be null also. Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The computation formulas are given in sub-clause 10.5.2.13.6. |
10.5.2.1b.7 Variable bit map format
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Cell Channel Description IEI | octet 1 | |||||||
1 | 0 | 0 | 0 | 1 | 1 | 1 | CA | |
FORMAT-ID | spare | spare | FORMAT-ID | ARFCN | octet 2 | |||
ORIG-ARFCN | octet 3 | |||||||
ORIG- | RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | octet 4 |
RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | CA | octet 17 |
Figure 10.5.2.1b.7.1/: Cell Channel Description information element,
variable bit map format
Table 10.5.2.1b.7.1: Cell Channel Description information element,
variable bit map format
ORIG-ARFCN, origin ARFCN (octet 2, 3 and 4) This field encodes the ARFCN of one frequency belonging to the set. This value is also used as origin of the bit map to generate all other frequencies. RRFCN N, relative radio frequency channel number N (octet 4 etc.) For a RF channel with ARFCN = (ORIG-ARFCN + N) mod 1024 belonging to the set, RRFCN N bit is coded with a "1"; N = 1, 2, .. , 111 For a RF channel with ARFCN = (ORIG-ARFCN + N) mod 1024 not belonging to the set, RRFCN N bit is coded with a "0"; N = 1, 2, .. , 111 |
10.5.2.1c BA List Pref
The purpose of the BA List Pref information element is to provide the mobile station with ARFCN information which can be used in the cell selection/reselection procedure.
The BA List Pref is a type 4 information element with a minimum length of 3 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 04.06).
<BA List Pref>::=
<LENGTH OF BA LIST PREF : bit (8)>
{1 <RANGE LIMITS >}**0
{1 <BA FREQ : bit (10)>}**0
<spare padding>;
<RANGE LIMITS>::=
<RANGE LOWER : bit (10)>
<RANGE UPPER : bit (10)>;
The RANGE LOWER is coded as the binary representation of the ARFCN used as the lower limit of a range of frequencies to be used by the mobile station in cell selection and reselection (see 3GPP TS 05.08 and 3GPP TS 03.22).
The RANGE HIGHER is coded as the binary representation of the ARFCN used as the higher limit of a range of frequencies to be used by the mobile station in cell selection and reselection (see 3GPP TS 05.08 and 3GPP TS 03.22).
BA FREQ is coded as the binary representation of the ARFCN indicating a single frequency to be used by the mobile station in cell selection and reselection (see 3GPP TS 05.08 and 3GPP TS 03.22).
10.5.2.1d UTRAN Frequency List
The UTRAN frequency list information element provides the mobile station with a list of UTRAN frequencies used by the network. These frequencies may be used in the cell selection procedure, see 3GPP TS 25.304.
FDD_ARFCN and TDD_ARFCN are defined as the UARFCN in 3GPP TS 25.101 and 3GPP TS 25.102. If both an UTRAN Frequency List information element and an UTRAN Frequency List Description struct (3GPP TS 04.60) are received, the mobile station shall use the one most recently received.
The UTRAN Frequency List is a type 4 information element with a minimum length of 3 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 04.06).
< UTRAN Freq List >::=
< LENGTH OF UTRAN FREQ LIST : bit (8) > — length following in octets
{ 1 < FDD_ARFCN > : bit (14) } ** 0 — FDD frequencies
{ 1 < TDD_ARFCN > : bit (14) } ** 0 — TDD frequencies
<spare bit>**;
Spare bits in the end of the field are used to fill the last octet.
10.5.2.2 Cell Description
The purpose of the Cell Description information element is to provide a minimum description of a cell, e.g. to allow the mobile station to use its pre-knowledge about synchronization.
The Cell Description information element is coded as shown in figure 10.5.2.2.1 and table 10.5.2.2.1.
The Cell Description is a type 3 information element with 3 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Cell Channel Description IEI | octet 1 | |||||||
BCCH ARFCN | NCC | BCC | octet 2 | |||||
BCCH ARFCN (low part) | octet 3 |
Figure 10.5.2.2.1: Cell Description information element
Table 10.5.2.2.1: Cell Description information element
NCC, PLMN colour code (octet 2) The NCC field is coded as the binary representation of the PLMN colour code (see 3GPP TS 23.003). BCC, BS colour code (octet 2) The BCC field is coded as the binary representation of the BS colour code (see 3GPP TS 23.003). BCCH ARFCN (octet 2, bits 7 and 8, and octet 3) The BCCH ARFCN number field is coded as the binary representation of the BCCH carriers absolute RF channel number. Range: 0 to 1023 |
10.5.2.3 Cell Options (BCCH)
The purpose of the Cell Options (BCCH) information element is to provide a variety of information about a cell.
The Cell Options (BCCH) information element is coded as shown in figure 10.5.2.3.1 and table 10.5.2.3a.1.
The Cell Options (BCCH) is a type 3 information element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Cell Channel Description IEI | octet 1 | |||||||
0 | PWRC | DTX | RADIO-LINK-TIMEOUT | octet 2 |
Figure 10.5.2.3.1: Cell Options (BCCH) information element
10.5.2.3a Cell Options (SACCH)
The purpose of the Cell Options (SACCH) information element is to provide a variety of information about a cell.
The Cell Options (SACCH) information element is coded as shown in figure 10.5.2.3a.1 and table 10.5.2.3a.2.
The Cell Options (SACCH) is a type 3 information element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Cell Channel Description IEI | octet 1 | |||||||
DTX | PWRC | DTX | RADIO-LINK-TIMEOUT | octet 2 |
Figure 10.5.2.3a.1: Cell Options (SACCH) information element
Table 10.5.2.3a.1: Cell Options (BCCH) information element
PWRC Power control indicator (octet 2) note 1 bit 7 0 PWRC is not set 1 PWRC is set |
DTX, DTX indicator (octet 2) note 3 Bit 6 5 0 0 The MSs may use uplink discontinuous transmission 0 1 The MSs shall use uplink discontinuous transmission 1 0 The MS shall not use uplink discontinuous transmission |
RADIO-LINK_TIMEOUT (octet 2) note 2 Bits 4 3 2 1 0 0 0 0 4 0 0 0 1 8 0 0 1 0 12 … 1 1 1 0 60 1 1 1 1 64 |
NOTE 1: The precise meaning of the PWRC parameter can be found in 3GPP TS 05.08. NOTE 2: The precise meaning of RADIO-LINK-TIMEOUT parameter can be found in 3GPP TS 05.08. NOTE 3: The DTX indicator field is not related to the use of downlink discontinuous transmission. |
Table 10.5.2.3a.2: Cell Options (SACCH) information element
PWRC Power control indicator (octet 2) note 1 bit 7 0 PWRC is not set 1 PWRC is set |
DTX, DTX indicator (octet 2) note 3 Bit 8 6 5 0 0 0 The MS may use uplink discontinuous transmission on a TCH-F. The MS shall not use uplink discontinuous transmission on TCH-H. 0 0 1 The MS shall use uplink discontinuous transmission on a TCH-F. The MS shall not use uplink discontinuous transmission on TCH-H. 0 1 0 The MS shall not use uplink discontinuous transmission on a TCH-F. The MS shall not use uplink discontinuous transmission on TCH-H. 0 1 1 Note 4: The MS shall use uplink discontinuous transmission on a TCH-F. The MS may use uplink discontinuous transmission on TCH-H. 1 0 0 The MS may use uplink discontinuous transmission on a TCH-F. The MS may use uplink discontinuous transmission on TCH-H. 1 0 1 The MS shall use uplink discontinuous transmission on a TCH-F. The MS shall use uplink discontinuous transmission on TCH-H. 1 1 0 The MS shall not use uplink discontinuous transmission on a TCH-F. The MS shall use uplink discontinuous transmission on TCH-H. 1 1 1 Note 4: The MS may use uplink discontinuous transmission on a TCH-F. The MS shall use uplink discontinuous transmission on TCH-H. |
RADIO-LINK_TIMEOUT (octet 2) note 2 Bits 4 3 2 1 0 0 0 0 4 0 0 0 1 8 0 0 1 0 12 1 1 1 0 60 1 1 1 1 64 |
NOTE 1: The precise meaning of the PWRC parameter can be found in 3GPP TS 05.08. NOTE 2: The precise meaning of RADIO-LINK-TIMEOUT parameter can be found in 3GPP TS 05.08. NOTE 3: The DTX indicator field is not related to the use of downlink discontinuous transmission. NOTE 4: These codes shall not be sent to mobile stations that implement an earlier version of this protocol in which these codes were not defined. |
10.5.2.4 Cell Selection Parameters
The purpose of the Cell Selection Parameters information element is to provide a variety of information about a cell.
The Cell Selection Parameters information element is coded as shown in figure 10.5.2.4.1 and table 10.5.2.4.1.
The Cell Selection Parameters information element is a type 3 information element with 3 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Cell Selection Parameters IEI | octet 1 | |||||||
CELL-RESELECT | MS-TXPWR-MAX-CCH | octet 2 | ||||||
ACS | NECI | RXLEV-ACCESS-MIN | octet 3 |
Figure 10.5.2.4.1: Cell Selection Parameters information element
Table 10.5.2.4.1: Cell Selection Parameters information element
CELL-RESELECT-HYSTERESIS (octet 2) The usage of this information is defined in 3GPP TS 05.08 Bits 8 7 6 0 0 0 0 dB RXLEV hysteresis for LA re-selection 0 0 1 2 dB RXLEV hysteresis for LA re-selection 0 1 0 4 dB RXLEV hysteresis for LA re-selection 0 1 1 6 dB RXLEV hysteresis for LA re-selection 1 0 0 8 dB RXLEV hysteresis for LA re-selection 1 0 1 10 dB RXLEV hysteresis for LA re-selection 1 1 0 12 dB RXLEV hysteresis for LA re-selection 1 1 1 14 dB RXLEV hysteresis for LA re-selection |
MS-TXPWR-MAX-CCH (octet 2) The MS-TXPWR-MAX-CCH field is coded as the binary representation of the "power control level" in 3GPP TS 05.05 corresponding to the maximum TX power level an MS may use when accessing on a Control Channel CCH. This value shall be used by the Mobile Station according to 3GPP TS 05.08. Range: 0 to 31. |
RXLEV-ACCESS-MIN (octet 3) The RXLEV-ACCESS-MIN field is coded as the binary representation of the minimum received signal level at the MS for which it is permitted to access the system. Range: 0 to 63. (See 3GPP TS 05.08). |
ACS, ADDITIONAL RESELECT PARAM IND (octet 3) Bit 8: In System Information type 3 message: 0 System information type 16 and 17 are not broadcast on the BCCH. 1 System information type 16 and 17 are broadcast on the BCCH. A mobile station which does not support System information type 16 and 17 may consider this bit as "0". In System Information type 4 message: 0 The SI 4 rest octets, if present, and SI 7 and SI 8 rest octets, if so indicated in the SI 4 rest octets shall be used to derive the value of PI and possibly C2 parameters and/or other parameters 1 The value of PI and possibly C2 parameters and/or other parameters in a System information type 7 or type 8 message shall be used |
NECI: HALF RATE SUPPORT (octet 3) Bit 7: 0 New establishment causes are not supported 1 New establishment causes are supported |
10.5.2.4a MAC Mode and Channel Coding Requested
The purpose of the MAC Mode and Channel Coding Requested information element is for the mobile station to indicate to the network which channel coding rate the mobile station desires the network to use on the downlink.
The MAC Mode and Channel Coding Requested information element is coded as shown in figure 10.5.2.4a.1 and table 10.5.2.4a.1.
The MAC Mode and Channel Coding Requested is a type 1 information element.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
MAC Mode and | MAC 0 | CS | octet 1 |
Figure 10.5.2.4a.1: MAC Mode and Channel Coding Requested information element
Table 10.5.2.4a.1: MAC Mode and Channel Coding Requested information element
CS: Coding Scheme This field indicates to network the channel coding scheme (see 3GPP TS 05.03) that the network should use on the downlink. The field is encoded according to the following table: bits 2 1 0 0 CS 1 0 1 CS 2 1 0 CS 3 1 1 CS 4 MAC Mode (bits 3-4, octet 1) This field is encoded the same as the MAC_MODE field in the PACKET RESOURCE REQUEST message described in 3GPP TS 04.60. |
10.5.2.5 Channel Description
The purpose of the Channel Description information element is to provide a description of an allocable channel together with its SACCH.
The Channel Description information element is coded as shown in figure 10.5.2.5.1 and table 10.5.2.5.1.
The Channel Description is a type 3 information element with 4 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Channel Description IEI | octet 1 | |||||||
Channel type | TN | octet 2 | ||||||
H=1-> | MAIO (high part) | |||||||
TSC | — H — | —————————————————– | octet 3 | |||||
ARFCN | ||||||||
0 | ||||||||
H=0-> | spare | (high part) | ||||||
MAIO | HSN | octet 4 | ||||||
ARFCN (low part) |
Figure 10.5.2.5.1: Channel Description information element
Table 10.5.2.5.1: Channel Description information element
Channel type and TDMA offset (octet 2) Bits 8 7 6 5 4 0 0 0 0 1 TCH/F + ACCHs 0 0 0 1 T TCH/H + ACCHs 0 0 1 T T SDCCH/4 + SACCH/C4 or CBCH (SDCCH/4) 0 1 T T T SDCCH/8 + SACCH/C8 or CBCH (SDCCH/8) The T bits indicate the subchannel number coded in binary. All other values are reserved. The Channel Type and TDMA offset field shall be ignored and all bits treated as spare when received in a PDCH ASSIGNMENT COMMAND message. The sender set the spare bits to the coding for TCH/F+ACCHs |
TN, Timeslot number (octet 2) The TN field is coded as the binary representation of the timeslot number as defined in 3GPP TS 05.10. Range: 0 to 7. The Timeslot number field shall be ignored and all bits treated as spare when received in a PDCH ASSIGNMENT COMMAND message. The sender sets the spare bits as ‘000’ |
TSC, Training Sequence Code (octet 3) The TSC field is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 05.03 Range: 0 to 7. |
H, Hopping channel (octet 3) Bit 5 0 Single RF channel 1 RF hopping channel NOTE: The value of H affects the semantics of the channel selector field Channel selector (octet 3 and 4) H = "0": The channel selector field consists of the absolute RF channel number Octet 3 Bits 4 3 0 0 Spare |
ARFCN, (octet 3, bits 2 and 1, and octet 4, bits 8 to 1) The ARFCN is coded as the binary representation of the absolute RF channel number Range: 0 to 1023 H = "1": The channel selector field consists of the mobile allocation index offset, MAIO, and the hopping sequence number, HSN. |
MAIO, (octet 3 bit 4 to 1 high part and octet 4 bit 8 to 7 low part) The MAIO field is coded as the binary representation of the mobile allocation index offset as defined in 3GPP TS 05.02. Range: 0 to 63. |
HSN, (octet 4 bit 6 to 1) The HSN field is coded as the binary representation of the hopping sequence number as defined in 3GPP TS 05.02 Range 0 to 63. |
10.5.2.5a Channel Description 2
The purpose of the Channel Description 2 information element is to provide a description of an allocable channel configuration together with its SACCH.
The Channel Description 2 information element is coded as shown in figure 10.5.2.5a.1 and table 10.5.2.5a.1.
The Channel Description 2 is a type 3 information element with 4 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Channel Description IEI | octet 1 | |||||||
Channel type | TN | octet 2 | ||||||
H=1-> | MAIO (high part) | |||||||
TSC | — H — | —————————————————– | octet 3 | |||||
ARFCN | ||||||||
0 | ||||||||
H=0-> | spare | (high part) | ||||||
MAIO | HSN | octet 4 | ||||||
ARFCN (low part) |
Figure 10.5.2.5a.1: Channel Description 2 information element
Table 10.5.2.5a.1: Channel Description 2 information element
Channel type and TDMA offset (octet 2) Bits 8 7 6 5 4 0 0 0 0 0 TCH/F + FACCH/F and SACCH/M at the timeslot indicated by TN, and additional bidirectional or undirectional TCH/Fs and SACCH/Ms according to the multislot allocation information element 0 0 0 0 1 TCH/F + FACCH/F and SACCH/F 0 0 0 1 T TCH/H + ACCHs 0 0 1 T T SDCCH/4 + SACCH/C4 or CBCH (SDCCH/4) 0 1 T T T SDCCH/8 + SACCH/C8 or CBCH (SDCCH/8) The T bits indicate the subchannel number coded in binary. In the description below "n" is the timeslot number indicated by TN. The description is valid only if all the indicated timeslot numbers are in the range 0 to 7. |
1 0 X X X TCH/F + FACCH/F and SACCH/M at the time slot indicated by TN, and additional bidirectional TCH/Fs and SACCH/Ms at other timeslots according to the following: X X X: 0 0 0 no additional timeslots 0 0 1 at timeslot n-1 0 1 0 at timeslot n+1, n-1 0 1 1 at timeslot n+1, n-1 and n-2 1 0 0 at timeslot n+1, n-1, n-2, and n-3 1 0 1 at timeslot n+1, n-1, n-2, n-3 and n-4 1 1 0 at timeslot n+1, n-1, n-2, n-3, n-4 and n-5 1 1 1 at timeslot n+1, n-1, n-2, n-3, n-4, n-5 and n-6 |
1 1 0 0 1 to 1 1 0 1 1 TCH/F + FACCH/F and SACCH/M at the time slot indicated by TN and additional unidirectional TCH/FDs and SACCH/MDs at other timeslots according to the following: 1 1 0 0 1 at timeslot n-1 1 1 0 1 0 at timeslot n+1, n-1 1 1 0 1 1 at timeslot n+1, n-1 and n-2 1 1 1 1 0 TCH/F + FACCH/F and SACCH/M at the time slot indicated by TN and additional bidirectional TCH/F and SACCH/M at timeslot n+1 and unidirectional TCH/FD and SACCH/MD at timeslot n-1 All other values are reserved. |
TN, Timeslot number (octet 2) The TN field is coded as the binary representation of the timeslot number as defined in 3GPP TS 3GPP TS 05.10. Range: 0 to 7. |
TSC, Training Sequence Code (octet 3) The TSC field is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 05.03 Range: 0 to 7. |
H, Hopping channel (octet 3) Bit 5 0 Single RF channel 1 RF hopping channel NOTE: The value of H affects the semantics of the channel selector field. |
Channel selector (octet 3 and 4) H = "0": The channel selector field consists of the absolute RF channel number Octet 3 Bits 4 3 0 0 Spare |
ARFCN, (octet 3, bits 2 and 1, and octet 4, bits 8 to 1) The ARFCN is coded as the binary representation of the absolute RF channel number Range: 0 to 1023 H = "1": The channel selector field consists of the mobile allocation index offset, MAIO, and the hopping sequence number, HSN. |
MAIO, (octet 3 bit 4 to 1 high part and octet 4 bit 8 to 7 low part) The MAIO field is coded as the binary representation of the mobile allocation index offset as defined in 3GPP TS 05.02. Range: 0 to 63. |
HSN, (octet 4 bit 6 to 1) The HSN field is coded as the binary representation of the hopping sequence number as defined in 3GPP TS 05.02 Range 0 to 63. |
10.5.2.6 Channel Mode
The Channel Mode information element gives information of the mode on coding/decoding and transcoding. The exact mode is determined by the contents of this IE and the channel type.
The Channel Mode information element is coded as shown in figure 10.5.2.6.1 and table 10.5.2.6.1.
The Channel Mode is a type 3 information element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Channel Mode IEI | octet 1 | |||||||
Mode | octet 2 |
Figure 10.5.2.6.1: Channel Mode information element
Table 10.5.2.6.1: Channel Mode information element
The mode field is encoded as follows: (octet 2) Bits 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 signalling only 0 0 0 0 0 0 0 1 speech full rate or half rate version 1 0 0 1 0 0 0 0 1 speech full rate or half rate version 2 0 1 0 0 0 0 0 1 speech full rate or half rate version 3 0 1 1 0 0 0 0 1 data, 43.5 kbit/s (downlink)+14.5 kbps (uplink) 0 1 1 0 0 0 1 0 data, 29.0 kbit/s (downlink)+14.5 kbps (uplink) 0 1 1 0 0 1 0 0 data, 43.5 kbit/s (downlink)+29.0 kbps (uplink) 0 1 1 0 0 1 1 1 data, 14.5 kbit/s (downlink)+43.5 kbps (uplink) 0 1 1 0 0 1 0 1 data, 14.5 kbit/s (downlink)+29.0 kbps (uplink) 0 1 1 0 0 1 1 0 data, 29.0 kbit/s (downlink)+43.5 kbps (uplink) 0 0 1 0 0 1 1 1 data, 43.5 kbit/s radio interface rate 0 1 1 0 0 0 1 1 data, 32.0 kbit/s radio interface rate 0 1 0 0 0 0 1 1 data, 29.0 kbit/s radio interface rate 0 0 0 0 1 1 1 1 data, 14.5 kbit/s radio interface rate 0 0 0 0 0 0 1 1 data, 12.0 kbit/s radio interface rate 0 0 0 0 1 0 1 1 data, 6.0 kbit/s radio interface rate 0 0 0 1 0 0 1 1 data, 3.6 kbit/s radio interface rate Other values are reserved for future use. |
NOTE: The speech full rate or half rate version 3 is also referred as the adaptive multi-rate full rate or half rate speech version 1. |
10.5.2.7 Channel Mode 2
The Channel Mode 2 information element gives information of the mode of coding/decoding and transcoding.
The Channel Mode 2 information element is coded as shown in figure 10.5.2.7.1 and table 10.5.2.7.1.
The Channel Mode 2 is a type 3 information element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Channel Mode IEI | octet 1 | |||||||
Mode | octet 2 |
Figure 10.5.2.7.1: Channel Mode 2 information element
Table 10.5.2.7.1: Channel Mode 2 information element
The mode field is encoded as follows: (octet 2) Bits 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 signalling only 0 0 0 0 0 1 0 1 speech half rate version 1 0 0 1 0 0 1 0 1 speech half rate version 2 0 1 0 0 0 1 0 1 speech half rate version 3 0 0 0 0 1 1 1 1 data, 6.0 kbit/s radio interface rate 0 0 0 1 0 1 1 1 data, 3.6 kbit/s radio interface rate Other values are reserved for future use. |
NOTE: The speech half rate version 3 is also referred as the adaptive multi-rate half rate speech version 1. |
10.5.2.7a UTRAN Classmark information element
Only valid for a UTRAN capable mobile station. TheUTRAN Classmark information element includes the INTER RAT HANDOVER INFO (defined in 3GPP TS 25.331) which gives UTRAN related information to the network (target system) for intersystem handover.
TheUTRAN Classmark information element is a type 4 information element with a minimum length of 2 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 04.06).
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
UTRAN Classmark IEI | octet 1 | |||||||
Length of UTRAN Classmark | octet 2 | |||||||
UTRAN Classmark value part | octet 3-n |
Figure 10.5.2.7a: UTRAN Classmark information element
The value part of the UTRAN Classmark information element is the INTER RAT HANDOVER INFO as defined in 3GPP TS 25.331.
10.5.2.7b (void)
10.5.2.7c Classmark Enquiry Mask
The Classmark Enquiry mask defines the information to be returned to the network. The bit mask defines the specific information to be returned, such as UTRAN specific information and/or CDMA2000 capability and/or requests the sending of the CLASSMARK CHANGE message.
The Classmark Enquiry Mask is a type 4 information element with 3 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Classmark Enquiry Mask IEI | octet 1 | |||||||
Length of Classmark Enquiry Mask contents | octet 2 | |||||||
Classmark Enquiry Mask value part | octet 3 |
Figure 10.5.2.7c.1: Classmark Enquiry Mask information element
Table 10.5.2.7c.2: Classmark Enquiry Mask value part.
Bit 8: |
Bits 7-5 All other values shall not be sent. If received, they shall be interpreted as ‘000’. |
Bit 4: |
Bits 3-1: |
10.5.2.8 Channel Needed
The purpose of the Channel Needed information element is to indicate to up to two mobile stations which type of channel is needed (for each mobile station) for the transaction linked to the paging procedure.
The Channel Needed information element is coded as shown in figure 10.5.2.8.1 and table 10.5.2.8.1.
The Channel Needed is a type 1 information element.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Channel Needed | CHANNEL | CHANNEL | octet 1 |
Figure 10.5.2.8.1: Channel Needed information element
Table 10.5.2.8.1: Channel Needed information element
CHANNEL (octet 1) Bits 2/4 1/3 0 0 Any channel. 0 1 SDCCH. 1 0 TCH/F (Full rate). 1 1 TCH/H or TCH/F (Dual rate). If this information element is used for only one mobile station, then the first CHANNEL field is used and the second CHANNEL field is spare. |
10.5.2.8a Channel Request Description
The purpose of the Channel Request Description information element is to indicate to the network the type of requested uplink resources or to indicate the type of paging that is being responded to.
The Channel Request Description information element is coded as shown in figure 10.5.2.8a.1 and table 10.5.2.8a.1.
The Channel Request Description is a type 3 information element with a length of 6 octets.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Channel Request Description IEI | octet 1 | |||||||
0 | 0 | 0 | 0 | 0 | 0 | 0 | ||
=0-> | spare | |||||||
MT/MO | – – – – – – – – – — – – – – – – — – — – – – – – – – – — – – – – – – — – – – – – – – – — – – | octet 2 | ||||||
spare | RLC | LLC | ||||||
=1-> | priority | mode | frame | |||||
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | |
spare | ||||||||
Requested bandwidth (MSB-Value field) | octet 3 | |||||||
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | |
spare | octet 4 | |||||||
Requested bandwidth (LSB-Value field) | ||||||||
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | |
Spare | ||||||||
RLC Octet Count (MSB-Value field) | octet 5 | |||||||
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | |
Spare | octet 6 | |||||||
RLC Octet Count (LSB-Value field) |
Figure 10.5.2.8a.1: Channel Request Description information element
Table 10.5.2.8a.1: Channel Request Description information element details
MT/MO (bit 8, octet 2) 1 Mobile originated (MO) 0 Mobile terminated (MT) |
PRIORITY (bits 3-4, octet 2) When MT/MO indicates MO, this field indicates the priority of the requested TBF bit 4 3 0 0 Priority Level 1 (Highest priority) 0 1 Priority Level 2 1 0 Priority Level 3 1 1 Priority Level 4 (Lower priority) |
RLC_MODE (bit 2, octet 2) When MT/MO indicates MO, this field indicates the RLC mode of the requested TBF. 0 RLC acknowledged mode 1 RLC unacknowledged mode |
LLC_FRAME_TYPE (bit 1, octet 2) When MT/MO indicates MO, this field indicates the type of the first LLC frame to be transmitted over the requested uplink TBF. 0 LLC frame is SACK or NACK 1 LLC frame is not SACK or NACK |
REQUESTED_BANDWIDTH (16 bits field, octets 3 and 4) When MT/MO indicates MO, this field indicates the useful uplink bandwidth requested in bit rate. The bit rate field is the binary encoding of the rate information expressed in 100 bits/s, starting from 0 x 100 bits/s until 65 535 x 100 bits/s. The throughput granted by BSS may be higher to cope with protocol overhead and retransmissions. |
RLC_OCTET_COUNT (16 bits field, octets 5 and 6) When MT/MO indicates MO, this field indicates the number of octets of RLC data the mobile station wishes to transfer: see 3GPP TS 04.60. |
10.5.2.8b Channel Request Description 2
The purpose of the Channel Request Description 2 information element is to indicate to the network the reason of the request to enter dual transfer mode.
The Channel Request Description 2 information element is coded as shown in figure 10.5.2.8b.1 and tables 10.5.2.8b.1 and 10.5.2.8b.2.
The Channel Request Description 2 information element is a type 4 information element with a minimum length of 6 octets. The maximum length of this information element is resulting from the encoding of the value part as specified below.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Channel Request Description 2 IEI | octet 1 | |||||||
Length of Channel Request Description 2 value part | octet 2 | |||||||
Channel Request Description 2 value part | octet 3 – n |
Figure 10.5.2.8b.1: Channel Request Description 2 information element
Table 10.5.2.8b.1: Channel Request Description 2 value part
< Channel Request Description 2 value part > ::= < PACKET_ESTABLISHMENT_CAUSE :bit(2) > < Channel Request Description : Channel Request Description IE > — Defined in 3GPP TS 04.60 { 0 | 1 < PFI : bit (7) > } < spare padding >; |
Table 10.5.2.8b.2: Channel Request Description 2 value part details
PACKET_ESTABLISHMENT_CAUSE (2 bit field) This field indicates the reason for requesting the access. Bit 2 1 0 0 User Data 0 1 Page Response 1 0 Cell Update 1 1 Mobility Management procedure |
Channel Request Description (information element) The Channel Request Description information element is defined in 3GPP TS 04.60. |
PFI (7 bit field) The PFI field is defined in 3GPP TS 04.60. |
10.5.2.9 Cipher Mode Setting
The purpose of the Cipher Mode Setting information element is to indicate whether stream ciphering shall be started or not and if it is to be started, which algorithm to use.
The Cipher Mode Setting information element is coded as shown in figure 10.5.2.9.1 and table 10.5.2.9.1.
The Cipher Mode Setting is a type 1 information element.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Ciph Mod Set IEI | algorithm identifier | SC | octet 1 |
Figure 10.5.2.9.1: Cipher Mode Setting information element
Table 10.5.2.9.1: Cipher Mode Setting information element
algorithm identifier If SC=1 then: bits 4 3 2 0 0 0 cipher with algorithm A5/1 0 0 1 cipher with algorithm A5/2 0 1 0 cipher with algorithm A5/3 0 1 1 cipher with algorithm A5/4 1 0 0 cipher with algorithm A5/5 1 0 1 cipher with algorithm A5/6 1 1 0 cipher with algorithm A5/7 1 1 1 reserved If SC=0 then bits 4, 3 and 2 are spare and set to "0" SC (octet 1) Bit 1 0 No ciphering 1 Start ciphering |
10.5.2.10 Cipher Response
The Cipher Response information element is used by the network to indicate to the mobile station which information the mobile station has to include in the CIPHERING MODE COMPLETE message.
The Cipher Response information element is coded as shown in figure 10.5.2.10.1 and table 10.5.2.10.1.
The Cipher Response is a type 1 information element.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
0 | 0 | 0 | octet 1 | |||||
Cipher Resp. IEI | Spare | CR |
Figure 10.5.2.10.1: Cipher Response information element
Table 10.5.2.10.1: Cipher Response information element
CR Cipher Response (octet 1) Bit 1 0 IMEISV shall not be included 1 IMEISV shall be included |
10.5.2.11 Control Channel Description
The purpose of the Control Channel Description information element is to provide a variety of information about a cell.
The Control Channel Description information element is coded as shown in figure 10.5.2.11.1 and table 10.5.2.11.1.
The Control Channel Description is a type 3 information element with 4 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Control Channel Description IEI | octet 1 | |||||||
MSCR | ATT | BS-AG-BLKS-RES | CCCH-CONF | octet 2 | ||||
0 | 0 | 0 | 0 0 | BS-PA-MFRMS | octet 3 | |||
T 3212 | octet 4 |
Figure 10.5.2.11.1: Control Channel Description information element
Table 10.5.2.11.1: Control Channel Description information element
MSCR, MSC Release (octet 2) Bit 8 0 MSC is Release ’98 or older 1 MSC is Release ’99 onwards |
ATT, Attach-detach allowed (octet 2) Bit 7 0 MSs in the cell are not allowed to apply IMSI attach and detach procedure. 1 MSs in the cell shall apply IMSI attach and detach procedure. BS-AG-BLKS-RES (octet 2) The BS-AG-BLKS-RES field is coded as the binary representation of the number of blocks reserved for access grant. Range 0 to 2 if CCCH-CONF = "001" 0 to 7 for other values of CCCH-CONF All other values are reserved in the first case |
CCCH-CONF (octet 2) bits 3 2 1 0 0 0 1 basic physical channel used for CCCH, not combined with SDCCHs 0 0 1 1 basic physical channel used for CCCH, combined with SDCCHs 0 1 0 2 basic physical channel used for CCCH, not combined with SDCCHs 1 0 0 3 basic physical channel used for CCCH, not combined with SDCCHs 1 1 0 4 basic physical channels used for CCCH, not combined with SDCCHs all other values are reserved |
BS-PA-MFRMS (octet 3) Bits 3 2 1 0 0 0 2 multiframes period for transmission of PAGING REQUEST messages to the same paging subgroup 0 0 1 3 multiframes period for transmission of PAGING REQUEST messages to the same paging subgroup 0 1 0 4 multiframes period for transmission of PAGING REQUEST messages to the same paging subgroup . . 1 1 1 9 multiframes period for transmission of PAGING REQUEST messages to the same paging subgroup NOTE: The number of different paging subchannels on the CCCH is: MAX(1,(3 – BS-AG-BLKS-RES)) * BS-PA-MFRMS if CCCH-CONF = "001" (9 – BS-AG-BLKS-RES) * BS-PA-MFRMS for other values of CCCH-CONF |
T3212 timeout value (octet 4) The T3212 timeout value field is coded as the binary representation of the timeout value for periodic updating in decihours. Range: 1 to 255 The value 0 is used for infinite timeout value i.e. periodic updating shall not be used within the cell. |
10.5.2.11a DTM Information Details
The DTM Information Details Information Element provides the mobile station with relevant GPRS information needed for correct DTM operation. This information element is contained in messages addressed to mobile stations supporting GPRS and DTM.
The DTM Information Details information element is coded as shown in figure 10.5.2.11a.1 and tables 10.5.2.11a.1 and 10.5.2.11a..2.
The DTM Information Details is a type 4 information element with a length of 3 octets.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
DTM Information Details IEI | octet 1 | |||||||
Length of DTM Information Details value part | octet 2 | |||||||
DTM Information Details value part | octet 3 |
Figure 10.5.2.11a.1: DTM Information Details information element
Table 10.5.2.11a.1: DTM Information Detaisl value part element
< DTM Information Details value part > ::= < MAX_LAPDm : bit (3) > < GPRS_MS_TXPWR_MAX_CCH : bit (5) > < Cell identity: bit (16) > < spare bit >**; |
Table 10.5.2.11a.2: DTM Information Details value part details
MAX_LAPDm (3 bit field) |
GPRS_MS_TXPWR_MAX_CCH (5 bits field) The GPRS_MS_TXPWR_MAX_CCH field is coded as the binary representation of the "power control level" in 3GPP TS 05.05 corresponding to the maximum TX power level the MS shall use for packet resources while in dual transfer mode. This value shall be used by the Mobile Station according to 3GPP TS 05.08. Range: 0 to 31. |
Cell identity (16 bits field) The purpose of the Cell Identity is to identify a cell within a routing area area. The Cell Identity is coded as the value part of the Cell Identity IE defined in 3GPP TS 24.008. |
10.5.2.12 Frequency Channel Sequence
The purpose of the Frequency Channel Sequence information element is to provide the absolute radio frequency channel numbers used in the mobile hopping sequence. This information element shall only be used for radio frequency channels in the primary GSM band (see 3GPP TS 05.05).
The Frequency Channel Sequence information element is coded as shown in figure 10.5.2.12.1 and table 10.5.2.12.1.
The Frequency Channel Sequence is a type 3 information element with 10 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Frequency Channel Sequence IEI | octet 1 | |||||||
0 | Lowest ARFCN | octet 2 | ||||||
inc skip of ARFCN 01 | inc skip of ARFCN 02 | octet 3 | ||||||
inc skip of ARFCN 15 | inc skip of ARFCN 16 | octet 10 |
Figure 10.5.2.12.1: Frequency Channel Sequence information element
Table 10.5.2.12.1: Frequency Channel Sequence information element
Lowest ARFCN (octet 2) The lowest ARFCN field is coded as the binary representation of the lowest absolute RF channel number appearing in the sequence of channels used in the frequency hopping. Range: 1 to 124 All other values are reserved. |
Increment skip ARFCN n (octet 3 to 10) The increment skip ARFCN n is coded as the binary representation of the increment of the preceding absolute RF channel number appearing in the sequence of channels used in the frequency hopping: n = 1,…,16. Range: 0 to 15 The value 0 indicates that the increment value is 15 but the concerned channel is not used and the next field, i.e. Increment skip ARFCN n+1 (if present) must be added to the increment to determine the next absolute RF channel number in the sequence of channels used in the frequency hopping. |
10.5.2.13 Frequency List
The purpose of the Frequency List information element is to provide the list of the absolute radio frequency channel numbers used in a frequency hopping sequence.
The Frequency List information element is a type 4 information element.
There are several formats for the Frequency List information element, distinguished by the "format indicator" subfield. Some formats are frequency bit maps, the others use a special encoding scheme.
10.5.2.13.1 General description
Table 10.5.2.13.1.1: Frequency List information element, general format
FORMAT-ID, Format Identifier (part of octet 3) The different formats are distinguished by the FORMAT-ID field. The possible values are the following: Bit Bit Bit Bit Bit format notation 8 7 4 3 2 0 0 X X X bit map 0 1 0 0 X X 1024 range 1 0 1 0 0 512 range 1 0 1 0 1 256 range 1 0 1 1 0 128 range 1 0 1 1 1 variable bit map All other combinations are reserved for future use. A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (see 3GPP TS 05.05) may consider all values except the value for bit map 0 as reserved. The significance of the remaining bits depends on the FORMAT-ID. The different cases are specified in the next sub-clauses. |
10.5.2.13.2 Bit map 0 format
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Frequency List IEI | octet 1 | |||||||
0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | |
Length of frequency list contents | octet 2 | |||||||
0 | 0 | 0 | 0 | |||||
FORMAT-ID | spare | ARFCN | ARFCN | ARFCN | ARFCN | octet 3 | ||
ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | octet 4 |
ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | ARFCN | octet 18 |
Figure 10.5.2.13.2.1: Frequency List information element, bit map 0 format
Table 10.5.2.13.2.1: Frequency List information element, bit map 0 format
ARFCN N, Absolute RF Channel Number N (octet 3 etc.) For a RF channel with ARFCN = N belonging to the frequency list the ARFCN N bit is coded with a "1"; N = 1, 2, .. , 124. For a RF channel with ARFCN = N not belonging to the frequency list the ARFCN N bit is coded with a "0"; N = 1, 2 .. , 124. |
10.5.2.13.3 Range 1024 format
The information element contains a header, and W(1) to W(M) for some M. If, due to octet boundaries, some bits are not used at the end of the last octet, these bits must be set to 0.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Frequency List IEI | octet 1 | |||||||
Length of frequency list contents | octet 2 | |||||||
1 | 0 | 0 | 0 | 0 | ||||
FORMAT-ID | spare | FORMA | F0 | W(1) | octet 3 | |||
W(1) (low part) | octet 4 | |||||||
W(2) to W(3) are on 9 bits, when present W(4) to W(7) are on 8 bits, when present W(8) to W(15) are on 7 bits, when present W(16) to W(31) are on 6 bits, when present W(2k) to W(2(k+1)-1) are on 10-k bits when present and so on |
Figure 10.5.2.13.3.1: Frequency List information element (Range 1024 format)
Table 10.5.2.13.3.1: Frequency List information element, range 1024 format
F0, frequency 0 indicator (octet 3, bit 3): 0 ARFCN 0 is not a member of the set 1 ARFCN 0 is a member of the set W(i), i from 1 to M (octet 3 and next): Each W(i) encodes a non negative integer in binary format. If W(k) is null, W(i) for i>k must be null also. Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The first computation formulas are given hereafter, with the following conventions: Wi denotes W(i); Fi denotes F(i); + indicates the natural integer addition; * indicates the natural integer multiplication; n mod m indicates the remainder of the euclidian division of n by m, ie n smod m indicates the offset remainder of the euclidian division of n by m, ie: 1 (n smod m) m and there exists k such that n = (k*m) + (n smod m); |
F1 = W1 F2 = (W1 – 512 + W2) smod 1023 F3 = (W1 + W3) smod 1023 F4 = (W1 – 512 + (W2 – 256 + W4) smod 511) smod 1023 F5 = (W1 + (W3 – 256 + W5) smod 511) smod 1023 F6 = (W1 – 512 + (W2 + W6) smod 511) smod 1023 F7 = (W1 + (W3 + W7) smod 511) smod 1023 F8 = (W1 – 512 + (W2 – 256 + (W4 – 128 + W8 ) smod 255) smod 511) smod 1023 F9 = (W1 + (W3 – 256 + (W5 – 128 + W9 ) smod 255) smod 511) smod 1023 F10 = (W1 – 512 + (W2 + (W6 – 128 + W10) smod 255) smod 511) smod 1023 F11 = (W1 + (W3 + (W7 – 128 + W11) smod 255) smod 511) smod 1023 F12 = (W1 – 512 + (W2 – 256 + (W4 + W12) smod 255) smod 511) smod 1023 F13 = (W1 + (W3 – 256 + (W5 + W13) smod 255) smod 511) smod 1023 F14 = (W1 – 512 + (W2 + (W6 + W14) smod 255) smod 511) smod 1023 F15 = (W1 + (W3 + (W7 + W15) smod 255) smod 511) smod 1023 F16 = (W1 – 512 + (W2 – 256 + (W4 – 128 + (W8 – 64 + W16) smod 127) smod 255) smod 511) smod 1023 |
More generally, the computation of F(K) can be done with the following program, using ADA language (declarative parts are skipped and should be obvious): INDEX := K; J := GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX); N := W(INDEX); while INDEX>1 loop if 2*INDEX < 3*J then INDEX := INDEX – J/2; — left child N := (N + W(PARENT) – 1024/J – 1) mod (2048/J – 1) + 1; else — right child INDEX := INDEX – J; N := (N + W(PARENT) – 1) mod (2048/J – 1) + 1; end if; J := J/2; end loop; F(K) := N; |
10.5.2.13.4 Range 512 format
The information element contains a header, and W(1) to W(M) for some M. If, due to octet boundaries, some bits are not used at the end of the last octet, these bits must be set to 0.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Frequency List IEI | octet 1 | |||||||
Length of frequency list contents | octet 2 | |||||||
1 | 0 | 0 | 0 | 1 | 0 | 0 | ORIG- | |
FORMAT-ID | spare | spare | FORMAT-ID | ARFCN high | octet 3 | |||
ORIG-ARFCN (middle part) | octet 4 | |||||||
ORIG- | W(1) | octet 5 | ||||||
W(1) | W(2) | octet 6 | ||||||
W(2) to W(3) are on 8 bits, when present W(4) to W(7) are on 7 bits, when present W(8) to W(15) are on 6 bits, when present W(16) to W(31) are on 5 bits, when present W(2k) to W(2(k+1)-1) are on 9-k bits when present and so on |
Figure 10.5.2.13.4.1: Frequency List information element (Range 512 format)
Table 10.5.2.13.4.1: Frequency List information element, range 512 format
ORIG-ARFCN, origin ARFCN (octet 3, 4 and 5) This field encodes the ARFCN of one frequency belonging to the set. This value is also used to decode the rest of the element. |
W(i), i from 1 to M (octet 5 and next): Each W(i) encodes a non negative integer in binary format. If W(k) is null, W(i) for i>k must be null also. |
Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The first computation formulas are given hereafter, with the following conventions: Wi denotes W(i); W0 denotes the value of ORIG-ARFCN Fi denotes F(i); + indicates the natural integer addition; * indicates the natural integer multiplication; n mod m indicates the remainder of the euclidian division of n by m, ie n smod m indicates the offset remainder of the euclidian division of n by m, ie |
F1 = (W0 + W1) mod 1024 F2 = (W0 + (W1 – 256 + W2) smod 511) mod 1024 F3 = (W0 + (W1 + W3) smod 511) mod 1024 F4 = (W0 + (W1 – 256 + (W2 – 128 + W4) smod 255) smod 511) mod 1024 F5 = (W0 + (W1 + (W3 – 128 + W5) smod 255) smod 511) mod 1024 F6 = (W0 + (W1 – 256 + (W2 + W6) smod 255) smod 511) mod 1024 F7 = (W0 + (W1 + (W3 + W7) smod 255) smod 511) mod 1024 F8 = (W0 + (W1 – 256 + (W2 – 128 + (W4 – 64 + W8 ) smod 127) smod 255) smod 511) mod 1024 F9 = (W0 + (W1 + (W3 – 128 + (W5 – 64 + W9 ) smod 127) smod 255) smod 511) mod 1024 F10 = (W0 + (W1 – 256 + (W2 + (W6 – 64 + W10) smod 127) smod 255) smod 511) mod 1024 F11 = (W0 + (W1 + (W3 + (W7 – 64 + W11) smod 127) smod 255) smod 511) mod 1024 F12 = (W0 + (W1 – 256 + (W2 – 128 + (W4 + W12) smod 127) smod 255) smod 511) mod 1024 F13 = (W0 + (W1 + (W3 – 128 + (W5 + W13) smod 127) smod 255) smod 511) mod 1024 F14 = (W0 + (W1 – 256 + (W2 + (W6 + W14) smod 127) smod 255) smod 511) mod 1024 F15 = (W0 + (W1 + (W3 + (W7 + W15) smod 127) smod 255) smod 511) mod 1024 F16 = (W0 + (W1 – 256 + (W2 – 128 + (W4 – 64 + (W8 – 32 + W16) smod 63) smod 127) smod 255) smod 511) mod 1024 F17 = (W0 + (W1 + (W3 – 128 + (W5 – 64 + (W9 – 32 + W17) smod 63) smod 127) smod 255) smod 511) mod 1024 |
More generally, the computation of F(K) can be done with the following program, using ADA language (declarative parts are skipped and should be obvious): INDEX := K; J := GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX); N := W(INDEX); while INDEX>1 loop if 2*INDEX < 3*J then — left child INDEX := INDEX – J/2; N := (N + W(PARENT) – 512/J – 1) mod (1024/J – 1) + 1; else — right child INDEX := INDEX – J; N := (N + W(_INDEX) – 1) mod (1024/J – 1) + 1; end if; J := J/2; end loop; F(K) := (W(0) + N) mod 1024; |
10.5.2.13.5 Range 256 format
The information element contains a header, and W(1) to W(M) for some M. If, due to octet boundaries, some bits are not used at the end of the last octet, these bits must be set to 0.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Frequency List IEI | octet 1 | |||||||
Length of frequency list contents | octet 2 | |||||||
1 | 0 | 0 | 0 | 1 | 0 | 1 | ORIG- | |
FORMAT-ID | spare | spare | FORMAT-ID | ARFCN | octet 3 | |||
ORIG-ARFCN (middle part) | octet 4 | |||||||
ORIG- | W(1) | octet 5 | ||||||
W(1) | W(2) | octet 6 | ||||||
W(2) to W(3) are on 7 bits, when present W(4) to W(7) are on 6 bits, when present W(8) to W(15) are on 5 bits, when present W(16) to W(31) are on 4 bits, when present W(2k) to W(2(k+1)-1) are on 8-k bits when present and so on |
Figure 10.5.2.13.5.1: Frequency List information element (Range 256 format)
Table 10.5.2.13.5.1: Frequency List information element, range 256 format
ORIG-ARFCN, origin ARFCN (octet 3, 4 and 5) This field encodes the ARFCN of one frequency belonging to the set. This value is also used to decode the rest of the element. W(i), i from 1 to M (octet 5 and next): Each W(i) encodes a non negative integer in binary format. If W(k) is null, W(i) for i>k must be null also. Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The first computation formulas are given hereafter, with the following conventions: Wi denotes W(i); W0 denotes the value of ORIG-ARFCN Fi denotes F(i); + indicates the natural integer addition; * indicates the natural integer multiplication; n mod m indicates the remainder of the euclidian division of n by m, ie n smod m indicates the offset remainder of the euclidian division of n by m, ie |
F1 = (W0 + W1) mod 1024 F2 = (W0 + (W1 – 128 + W2) smod 255) mod 1024 F3 = (W0 + (W1 + W3) smod 255) mod 1024 F4 = (W0 + (W1 – 128 + (W2 – 64 + W4) smod 127) smod 255) mod 1024 F5 = (W0 + (W1 + (W3 – 64 + W5) smod 127) smod 255) mod 1024 F6 = (W0 + (W1 – 128 + (W2 + W6) smod 127) smod 255) mod 1024 F7 = (W0 + (W1 + (W3 + W7) smod 127) smod 255) mod 1024 F8 = (W0 + (W1 – 128 + (W2 – 64 + (W4 – 32 + W8 ) smod 63) smod 127) smod 255) mod 1024 F9 = (W0 + (W1 + (W3 – 64 + (W5 – 32 + W9 ) smod 63) smod 127) smod 255) mod 1024 F10 = (W0 + (W1 – 128 + (W2 + (W6 – 32 + W10) smod 63) smod 127) smod 255) mod 1024 F11 = (W0 + (W1 + (W3 + (W7 – 32 + W11) smod 63) smod 127) smod 255) mod 1024 F12 = (W0 + (W1 – 128 + (W2 – 64 + (W4 + W12) smod 63) smod 127) smod 255) mod 1024 F13 = (W0 + (W1 + (W3 – 64 + (W5 + W13) smod 63) smod 127) smod 255) mod 1024 F14 = (W0 + (W1 – 128 + (W2 + (W6 + W14) smod 63) smod 127) smod 255) mod 1024 F15 = (W0 + (W1 + (W3 + (W7 + W15) smod 63) smod 127) smod 255) mod 1024 F16 = (W0 + (W1 – 128 + (W2 – 64 + (W4 – 32 + (W8 – 16 + W16) smod 31) smod 63) smod 127) smod 255) mod 1024 F17 = (W0 + (W1 + (W3 – 64 + (W5 – 32 + (W9 – 16 + W17) smod 31) smod 63) smod 127) smod 255) mod 1024 F18 = (W0 + (W1 – 128 + (W2 + (W6 – 32 + (W10 – 16 + W18) smod 31) smod 63) smod 127) smod 255) mod 1024 F19 = (W0 + (W1 + (W3 + (W7 – 32 + (W11 – 16 + W19) smod 31) smod 63) smod 127) smod 255) mod 1024 F20 = (W0 + (W1 – 128 + (W2 – 64 + (W4 + (W12 – 16 + W20) smod 31) smod 63) smod 127) smod 255) mod 1024 F21 = (W0 + (W1 + (W3 – 64 + (W5 + (W13 – 16 + W21) smod 31) smod 63) smod 127) smod 255) mod 1024 |
More generally, the computation of F(K) can be done with the following program, using ADA language (declarative parts are skipped and should be obvious): INDEX := K; J := GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX); N := W(INDEX); while INDEX>1 loop if 2*INDEX < 3*J then — left child INDEX := INDEX – J/2; N := (N + W(INDEX) – 256/J – 1) mod (512/J – 1) + 1; else — right child INDEX := INDEX – J; N := (N + W(INDEX) – 1) mod (512/J – 1) + 1; end if; J := J/2; end loop; F(K) := (W(0) + N) mod 1024; |
10.5.2.13.6 Range 128 format
The information element contains a header, and W(1) to W(M) for some M. If, due to octet boundaries, some bits are not used at the end of the last octet, these bits must be set to 0.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Frequency List IEI | octet 1 | |||||||
Length of frequency list contents | octet 2 | |||||||
1 | 0 | 0 | 0 | 1 | 1 | 0 | ORIG- | |
FORMAT-ID | spare | spare | FORMAT-ID | ARFCN | octet 3 | |||
ORIG-ARFCN (middle part) | octet 4 | |||||||
ORIG- | W(1) | octet 5 | ||||||
W(2) to W(3) are on 6 bits, when present W(4) to W(7) are on 5 bits, when present W(8) to W(15) are on 4 bits, when present W(16) to W(31) are on 3 bits, when present W(2k) to W(2(k+1)-1) are on 7-k bits when present and so on |
Figure 10.5.2.13.6.1: Frequency List information element (Range 128 format)
Table 10.5.2.13.6.1: Frequency List information element, range 128 format
ORIG-ARFCN, origin ARFCN (octet 3, 4 and 5) This field encodes the ARFCN of one frequency belonging to the set. This value is also used to decode the rest of the element. W(i), i from 1 to M (octet 5 and next): Each W(i) encodes a non negative integer in binary format. If W(k) is null, W(i) for i>k must be null also. Each non null W(k) allows to compute, together with some previous W(i) the ARFCN F(k) of a frequency in the set. The first computation formulas are given hereafter, with the following conventions: Wi denotes W(i); W0 denotes the value of ORIG-ARFCN Fi denotes F(i); + indicates the natural integer addition; * indicates the natural integer multiplication; n mod m indicates the remainder of the euclidiandivision of n by m, ie n smod m indicates the offset remainder of the euclidian division of n by m, ie |
F1 = (W0 + W1) mod 1024 F2 = (W0 + (W1 – 64 + W2) smod 127) mod 1024 F3 = (W0 + (W1 + W3) smod 127) mod 1024 F4 = (W0 + (W1 – 64 + (W2 – 32 + W4) smod 63) smod 127) mod 1024 F5 = (W0 + (W1 + (W3 – 32 + W5) smod 63) smod 127) mod 1024 F6 = (W0 + (W1 – 64 + (W2 + W6) smod 63) smod 127) mod 1024 F7 = (W0 + (W1 + (W3 + W7) smod 63) smod 127) mod 1024 F8 = (W0 + (W1 – 64 + (W2 – 32 + (W4 – 16 + W8 ) smod 31) smod 63) smod 127) mod 1024 F9 = (W0 + (W1 + (W3 – 32 + (W5 – 16 + W9 ) smod 31) smod 63) smod 127) mod 1024 F10 = (W0 + (W1 – 64 + (W2 + (W6 – 16 + W10) smod 31) smod 63) smod 127) mod 1024 F11 = (W0 + (W1 + (W3 + (W7 – 16 + W11) smod 31) smod 63) smod 127) mod 1024 F12 = (W0 + (W1 – 64 + (W2 – 32 + (W4 + W12) smod 31) smod 63) smod 127) mod 1024 F13 = (W0 + (W1 + (W3 – 32 + (W5 + W13) smod 31) smod 63) smod 127) mod 1024 F14 = (W0 + (W1 – 64 + (W2 + (W6 + W14) smod 31) smod 63) smod 127) mod 1024 F15 = (W0 + (W1 + (W3 + (W7 + W15) smod 31) smod 63) smod 127) mod 1024 F16 = (W0 + (W1 – 64 + (W2 – 32 + (W4 – 16 + (W8 – 8 + W16) smod 15) smod 31) smod 63) smod 127) mod 1024 F17 = (W0 + (W1 + (W3 – 32 + (W5 – 16 + (W9 – 8 + W17) smod 15) smod 31) smod 63) smod 127) mod 1024 F18 = (W0 + (W1 – 64 + (W2 + (W6 – 16 + (W10 – 8 + W18) smod 15) smod 31) smod 63) smod 127) mod 1024 F19 = (W0 + (W1 + (W3 + (W7 – 16 + (W11 – 8 + W19) smod 15) smod 31) smod 63) smod 127) mod 1024 F20 = (W0 + (W1 – 64 + (W2 – 32 + (W4 + (W12 – 8 + W20) smod 15) smod 31) smod 63) smod 127) mod 1024 F21 = (W0 + (W1 + (W3 – 32 + (W5 + (W13 – 8 + W21) smod 15) smod 31) smod 63) smod 127) mod 1024 F22 = (W0 + (W1 – 64 + (W2 + (W6 + W(14 – 8 + W22) smod 15) smod 31) smod 63) smod 127) mod 1024 F23 = (W0 + (W1 + (W3 + (W7 + (W15 – 8 + W23) smod 15) smod 31) smod 63) smod 127) mod 1024 F24 = (W0 + (W1 – 64 + (W2 – 32 + (W4 – 16 + (W8 + W24) smod 15) smod 31) smod 63) smod 127) mod 1024 F25 = (W0 + (W1 + (W3 – 32 + (W5 – 16 + (W9 + W25) smod 15) smod 31) smod 63) smod 127) mod 1024 F26 = (W0 + (W1 – 64 + (W2 + (W6 – 16 + (W10 + W26) smod 15) smod 31) smod 63) smod 127) mod 1024 F27 = (W0 + (W1 + (W3 + (W7 – 16 + (W11 + W27) smod 15) smod 31) smod 63) smod 127) mod 1024 F28 = (W0 + (W1 – 64 + (W2 – 32 + (W4 + (W12 + W28 smod 15) smod 31) smod 63) smod 127) mod 1024 F29 = (W0 + (W1 + (W3 – 32 + (W5 + (W13 + W29 smod 15) smod 31) smod 63) smod 127) mod 1024 |
More generally, the computation of F(K) can be done with the following program, using ADA language (declarative parts are skipped and should be obvious): INDEX := K; J := GREATEST_POWER_OF_2_LESSER_OR_EQUAL_TO(INDEX); N := W(INDEX); while INDEX>1 loop if 2*INDEX < 3*J then — left child INDEX := INDEX – J/2; N := (N + W(INDEX) – 128/J – 1) mod (256/J – 1) + 1; else — right child INDEX := INDEX – J; N := (N + W(INDEX) – 1) mod (256/J – 1) + 1; end if; J := J/2; end loop; F(K) := (W(0) + N) mod 1024; |
10.5.2.13.7 Variable bit map format
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Frequency List IEI | octet 1 | |||||||
Length of frequency list contents | octet 2 | |||||||
1 | 0 | 0 | 0 | 1 | 1 | 1 | ORIG- | |
FORMAT-ID | spare | spare | FORMAT-ID | ARFCN | octet 3 | |||
ORIG-ARFCN (middle part) | octet 4 | |||||||
ORIG- | RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | octet 5 |
RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | RRFCN | octet k |
Figure 10.5.2.13.7.1: Frequency List information element, variable bit map format
Table 10.5.2.13.7.1: Frequency List information element, variable bit map format
ORIG-ARFCN, origin ARFCN (octet 3, 4 and 5) This field encodes the ARFCN of one frequency belonging to the set. This value is also used as origin of the bit map to generate all the other frequencies. |
RRFCN N, relative radio frequency channel number N (octet 5 etc.) For a RF channel with ARFCN = (ORIG-ARFCN + N) mod 1024 belonging to the set, RRFCN N bit is coded with a "1"; N = 1, 2, .. , 8M+7 with 1 M 127 For a RF channel with ARFCN = (ORIG-ARFCN + N) mod 1024 not belonging to the set, RRFCN N bit is coded with a "0"; N = 1, 2, .. , 8M+7 with 1 M 127 |
10.5.2.14 Frequency Short List
The purpose of the Frequency Short List information element is to provide the list of the absolute radio frequency channel numbers used in a frequency hopping sequence, in a small fixed length information element to obtain when possible the HANDOVER COMMAND message in a single block.
The Frequency Short List information element is a type 3 information element of 10 octet length.
This element is encoded exactly as the Frequency List information element, except that it has a fixed length instead of a variable length and does not contain a length indicator and that it shall not be encoded in bitmap 0 format.
10.5.2.14a Frequency Short List 2
The purpose of the Frequency Short List 2 information element is to provide the list of the absolute radio frequency channel numbers used in a frequency hopping sequence, in a small fixed length information element to obtain the SYSTEM INFORMATION TYPE 11 and NOTIFICATION FACCH messages in a single block.
The Frequency Short List information element is a type 3 information element of 8 octet length.
This element is encoded exactly as the Frequency List information element, except that it has a fixed length instead of a variable length and does not contain a length indicator and that it shall not be encoded in bitmap 0 format.
10.5.2.14b Group Channel Description
The purpose of the Group Channel Description information element is to provide a description of an allocable voice group call or voice broadcast call channel together with its SACCH and that part of the RF channels belonging to the cell allocation which is used in the mobile hopping sequence if applicable.
The Group Channel Description information element is coded as shown in figure 10.5.2.14b.1 and table 10.5.2.14b.1.
The Group Channel Description is a type 4 information element with 5 to 13 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Group Channel Description IEI | octet 1 | |||||||
Length of Group Channel Description contents | octet 2 | |||||||
Channel type | TN | octet 3 | ||||||
H=1-> | MAIO (high part) | |||||||
TSC | — H — | —————————————————– | octet 4 | |||||
H=0-> | 0 | ARFCN (high part) | ||||||
MAIO | HSN | octet 5 | ||||||
ARFCN (low part) | ||||||||
MA | MA | MA | MA | MA | MA | MA | MA | octet 6 |
MA | MA | MA | MA | MA | MA | MA | MA | octet n+5 |
Figure 10.5.2.14b.1: Group Channel Description information element
Table 10.5.2.14b.1: Group Channel Description information element
Channel type and TDMA offset (octet 3) Bits 8 7 6 5 4 0 0 0 0 1 TCH/FS + ACCHs (speech codec version 1) 0 0 0 1 T TCH/HS + ACCHs (speech codec version 1) 0 0 1 T T SDCCH/4 + SACCH/C4 0 1 T T T SDCCH/8 + SACCH/C8 The T bits indicate the subchannel number coded in binary. All other values are reserved for future use. |
TN, Timeslot number (octet 3) The TN field is coded as the binary representation of the timeslot number as defined in 3GPP TS 05.10. Range: 0 to 7. |
TSC, Training Sequence Code (octet 4) The TSC field is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 05.03 Range: 0 to 7. |
H, Hopping channel (octet 4) Bit 5 0 Single RF channel 1 RF hopping channel NOTE 1: The value of H affects the semantics of the channel selector field. NOTE 2: If H=0, the information element terminates with octet 5. Channel selector (octet 4 and 5) H = "0": The channel selector field consists of the absolute RF channel number Octet 4 Bits 4 3 0 0 Spare |
ARFCN, (octet 4, bits 2 and 1, and octet 5, bits 8 to 1) The ARFCN is coded as the binary representation of the absolute RF channel number Range: 0 to 1023 H = "1": The channel selector field consists of the mobile allocation index offset, MAIO, and the hopping sequence number, HSN. |
MAIO, (octet 4 bit 4 to 1 high part and octet 5 bit 8 to 7 low part) The MAIO field is coded as the binary representation of the mobile allocation index offset as defined in 3GPP TS 05.02. Range: 0 to 63. |
HSN, (octet 5 bit 6 to 1) The HSN field is coded as the binary representation of the hopping sequence number as defined in 3GPP TS 05.02 Range 0 to 63. |
MA C i, Mobile allocation RF channel i (octet 6 etc.), i = 1, 2,…, NF The MA C i bit indicates whether or not the Mobile allocation frequency list includes the i’th frequency in the cell allocation frequency list. In the cell allocation frequency list the absolute RF channel numbers are placed in increasing order of ARFCN, except that ARFCN 0, if included in the set, is put in the last position in the list, For a RF channel belonging to the mobile allocation the MA C i bit is coded with a "1"; i = 1, 2,…, NF. For a RF channel not belonging to the mobile allocation the MA C i bit is coded with a "0"; i = 1, 2,…, NF. If NF mod 8 <> 0 then bits NF to 8n in octet 6 must be coded with a "0" in each. |
10.5.2.14c GPRS Resumption
The purpose of the GPRS Resumption information element is to indicate whether the network has successfully resumed GPRS services or not.
The GPRS Resumption information element is coded as shown in figure 10.5.2.14c.1 and table 10.5.2.14c.1.
The GPRS Resumption is a type 1 information element.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
GPRS resumption | spare | ACK | octet 1 | |||||
IEI | 0 | 0 | 0 |
Figure 10.5.2.14c.1: GPRS Resumption information element
Table 10.5.2.14c.1: GPRS Resumption information element
The ACK field (1 bit) is the binary acknowledge of a successful resumption of GPRS services: 0 resumption of GPRS services not successfully acknowledged; 1 resumption of GPRS services successfully acknowledged. |
10.5.2.14d GPRS broadcast information
The GPRS broadcast information information element provides the mobile station with relevant GPRS information needed for correct DTM operation. This information element is contained in messages addressed to mobile stations supporting GPRS and DTM.
The GPRS broadcast information information element is coded as shown in figure 10.5.2.14d.1 and tables 10.5.2.14d.1 and 10.5.2.14d.2.
The GPRS broadcast information is a type 4 information element with a minimum length of 7 octets. The maximum length of this information element is resulting from the encoding of the value part as specified below.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
GPRS Broadcast Information IEI | octet 1 | |||||||
Length of GPRS Broadcast Information value part | octet 2 | |||||||
GPRS Broadcast Information value part | octet 3 – n |
Figure 10.5.2.14d.1: GPRS Broadcast Information information element
Table 10.5.2.14d.1: GPRS broadcast information value part
< GPRS broadcast information value part > ::= < GPRS Cell Options : < GPRS Cell Options IE > > < GPRS Power Control Parameters : < GPRS Power Control Parameters struct > > < spare bit >**; |
Table 10.5.2.14d.2: GPRS broadcast information value part details
GPRS Cell Options GPRS Power Control Parameters |
10.5.2.15 Handover Reference
The purpose of the Handover Reference information element is to provide a handover reference value used for access identification.
The Handover Reference information element is coded as shown in figure 10.5.2.15.1 and table 10.5.2.15.1.
The Handover Reference is a type 3 information element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Handover Reference IEI | octet 1 | |||||||
Handover reference value | octet 2 |
Figure 10.5.2.15.1: Handover Reference information element
Table 10.5.2.15.1: Handover Reference information element
Handover reference value (octet 2) The handover reference value field is coded using binary representation. Range: 0 to 255. |
10.5.2.16 IA Rest Octets
The IA Rest Octets information element contains spare bits and possibly either a packet uplink assignment construction, a packet downlink assignment construction, a second part packet assignment construction or a frequency parameters, before time construction.
The frequency parameters, before time construction combines a mobile allocation (see sub-clause 10.5.2.21) and a MAIO (see the channel description information element).
The IA Rest Octets information element is coded according to the syntax specified below and described in table 10.5.2.16.1.
The IA Rest Octets information element is a type 5 information element with 0-11 octets length.
<IA Rest Octets> ::= { LL | LH { 00 < EGPRS Packet Uplink Assignment > | 01 — reserved for future use | 1 — reserved for future use (however the value 7C for the first octet shall not be used) } | HL < Length of frequency parameters : bit string (6) > < Frequency Parameters, before time > | HH { 00 < Packet Uplink Assignment > | 01 < Packet Downlink Assignment > | 1 < Second Part Packet Assignment > } } <spare padding> ; |
< EGPRS Packet Uplink Assignment > : := < Extended RA : bit (5) > { 0 | 1 < Access Technologies Request : Access Technologies Request struct > } { 1 < TFI_ASSIGNMENT : bit (5) > < POLLING : bit > { 0 — Dynamic Allocation < USF: bit (3) > < USF_GRANULARITY : bit > { 0 | 1 < P0 : bit (4) > < PR_MODE : bit (1) >} | 1 — Fixed Allocation < ALLOCATION_BITMAP_LENGTH : bit (5) > < ALLOCATION_BITMAP : bit (val(ALLOCATION_BITMAP_LENGTH)) > { 0 | 1 < P0 : bit (4) > < BTS_PWR_CTRL_MODE : bit (1) > < PR_MODE : bit (1) > } } < EGPRS CHANNEL_CODING_COMMAND : < EGPRS Modulation and Coding IE>> < TLLI_BLOCK_CHANNEL_CODING : bit (1) > { 0 | 1 < BEP_PERIOD2 : bit (4) > } < RESEGMENT : bit (1) > < EGPRS Window Size : < EGPRS Window Size IE>> { 0 | 1 < ALPHA : bit (4) >} < GAMMA : bit (5) > { 0 | 1 < TIMING_ADVANCE_INDEX : bit (4) > } { 0 | 1 < TBF_STARTING_TIME : bit (16) > } | 0 — Multi Block Allocation { 0 | 1 < ALPHA : bit (4) > } < GAMMA : bit (5) > < TBF_STARTING_TIME : bit (16) > < NUMBER OF RADIO BLOCKS ALLOCATED : bit (2) > { 0 | 1 < P0 : bit (4) > < BTS_PWR_CTRL_MODE : bit (1) > < PR_MODE : bit (1) > } } ; |
<Access Technologies Request struct> ::= — recursive structure allows any combination of Access technologies <Access Technology Type : bit (4)> { 0 | 1 <Access Technologies Request struct> } ; |
< Packet Uplink Assignment > ::= { 1 < TFI_ASSIGNMENT : bit (5) > < POLLING : bit > { 0 — Dynamic Allocation < USF: bit (3) > < USF_GRANULARITY : bit > { 0 | 1 < P0 : bit (4) > < PR_MODE : bit (1) > } | 1 — Fixed Allocation < ALLOCATION_BITMAP_LENGTH : bit (5) > < ALLOCATION_BITMAP : bit (val(ALLOCATION_BITMAP_LENGTH)) > { 0 | 1 < P0 : bit (4) > < BTS_PWR_CTRL_MODE : bit (1) > < PR_MODE : bit (1) > } } < CHANNEL_CODING_COMMAND : bit (2) > < TLLI_BLOCK_CHANNEL_CODING : bit > { 0 | 1 < ALPHA : bit (4) > } < GAMMA : bit (5) > { 0 | 1 < TIMING_ADVANCE_INDEX : bit (4) > } { 0 | 1 < TBF_STARTING_TIME : bit (16) > } | 0 — Single Block Allocation { 0 | 1 < ALPHA : bit (4) >} < GAMMA : bit (5) > 0 1 — See Note < TBF_STARTING_TIME : bit (16) > { L | H < P0 : bit (4) > < BTS_PWR_CTRL_MODE : bit (1) > < PR_MODE : bit (1) >} } { null | L — Receiver compatible with earlier release | H — Additions for R99 { 0 | 1 < Extended RA : bit (5) > } } ; |
< Packet Downlink Assignment > ::= < TLLI : bit (32) > { 0 | 1 < TFI_ASSIGNMENT : bit (5) > < RLC_MODE : bit > { 0 | 1 < ALPHA : bit (4) > } < GAMMA : bit (5) > < POLLING : bit > < TA_VALID : bit (1) > } { 0 | 1 < TIMING_ADVANCE_INDEX : bit (4) > } { 0 | 1 < TBF_STARTING_TIME : bit (16) > } { 0 | 1 < P0 : bit (4) > < BTS_PWR_CRTL_MODE : bit (1) > < PR_MODE : bit (1) > } { null | L — Receiver compatible with earlier release | H — Additions for R99 — indicates EGPRS TBF mode, see — 3GPP TS 04.60 < EGPRS Window Size : < EGPRS Window Size IE >> < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > { 0 | 1 < BEP_PERIOD2 : bit (4) > } } ; |
< Frequency Parameters, before time > ::= { null — Length of frequency parameters = 0 | 0 0 < MAIO : bit (6) > < Mobile Allocation : octet (val (Length of frequency parameters) – 1) > } ; |
< Second Part Packet Assignment > ::= { null | L — Receiver compatible with earlier release | H — Additions for R99 { 0 | 1 < Extended RA : bit (5) > } } ; |
NOTE: A ‘Timing Advance index’ shall not be allocated at a Single Block allocation. A ‘TBF Starting Time’ shall be allocated at a Single Block allocation. The control bits set to fixed values to specify these requirements in a way compatible with early GPRS mobile stations in release 97. |
Table 10.5.2.16.1: IA Rest Octet information element
Packet Uplink Assignment The Extended RA (5 bit field) is the Extended Random Access information. This is an unformatted 5 bit field, whose content is coded as the 5 least significant bits of the the EGPRS PACKET CHANNEL REQUEST message defined in 3GPP TS 04.60. |
The POLLING field (1 bit field) indicates if the MS is being polled for a PACKET CONTROL ACKNOWLEDGEMENT: 0 no action is required from MS; 1 MS shall send a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink block specified by TBF Starting Time, on the assigned PDCH. |
The TFI_ASSIGNMENT field (5 bit field) is the binary representation of the Temporary Flow Identity, see 3GPP TS 04.60. Range: 0 to 31. |
The USF field (3 bit field) is the binary representation of the uplink state flag, see 3GPP TS 04.60. Range: 0 to 7. |
The USF_GRANULARITY field (1 bit field) indicates the USF granularity to be applied by the mobile station when it is assigned a TBF using Dynamic Allocation, see 3GPP TS 04.60: 0 the mobile station shall transmit one RLC/MAC block; |
The ALLOCATION_BITMAP_LENGTH field (5 bit field) specifies the number of bits in the ALLOCATION_BITMAP. |
The ALLOCATION_BITMAP field (variable length field) represents uplink radio blocks, each bit representing one radio block. Each bit indicates whether the mobile station is permitted to transmit during the corresponding uplink radio block. The bitmap describes a one dimensional array of block periods, indexed as follows: block period[z] z = n for n = 0 to L, where: L = number of bits in the ALLOCATION_BITMAP – 1; z = block period relative to TBF_STARTING_TIME; n = bit number index into the ALLOCATION_BITMAP, range 0 to L; TBF_STARTING_TIME indicates the first block period of the assigned allocation The value of each bit is encoded as: 0 block period[n] is not part of the assigned allocation 1 block period[n] is part of the assigned allocation |
The CHANNEL_CODING_COMMAND field (2 bit field) indicates the coding scheme to be used for transmission, see 3GPP TS 05.03: 0 0 coding scheme 1, CS-1; 0 1 coding scheme 2, CS-2; 1 0 coding scheme 3, CS-3; 1 1 coding scheme 4, CS-4. |
The TLLI_BLOCK_CHANNEL_CODING field (1 bit field) indicates the channel coding to be used for RLC data block comprising TLLI for contention resolution: 0 mobile station shall use CS-1 in GPRS TBF mode or MCS-1 in EGPRS TBF mode; 1 mobile station shall use coding scheme as specified by the corresponding CHANNEL CODING COMMAND or EGPRS CHANNEL CODING COMMAND field. |
The ALPHA field (4 bit field) is the binary representation of the parameter for MS output power control, see 3GPP TS 05.08: 0 0 0 0 = 0.0; 0 0 0 1 = 0.1; : : 1 0 1 0 = 1.0. All other values are reserved in this version of the protocol and shall be interpreted by the mobile station as = 1.0. |
The GAMMA field (5 bit field) is the binary representation of the parameter CH for MS output power control in units of 2 dB, see 3GPP TS 05.08. |
The TIMING_ADVANCE_INDEX field (4 bit field) is the binary representation of the timing advance index (TAI), see 3GPP TS 05.10 and 3GPP TS 04.04. Range: 0 to 15. |
The TBF_STARTING_TIME field (16 bit field) defines a starting time for the packet uplink assignment. The TBF starting time is coded using the same coding as the V format of the type 3 information element Starting Time (10.5.2.38). |
P0 (4 bit field) |
BTS_PWR_CTRL_MODE (1 bit field) |
PR_MODE (1 bit field) |
Packet Downlink Assignment |
The TLLI field (32 bit field) is the binary representation of a TLLI. The coding of TLLI is left open for each administration using the structure specified in 3GPP TS 23.003. |
The TFI_ASSIGNMENT field (5 bit field) is the binary representation of the Temporary Flow Identity, see 3GPP TS 04.60. Range: 0 to 31. |
The RLC_MODE field (1 bit field) indicates the RLC mode, see 3GPP TS 04.60: 0 RLC acknowledged mode; 1 RLC unacknowledged mode. |
The ALPHA field (4 bit field) is the binary representations of the parameters for MS output power control, see Packet Uplink Assignment construction. |
The GAMMA field (5 bit field) is the binary representation of the parameter CH for MS output power control, see Packet Uplink Assignment construction. |
The POLLING field (1 bit field) indicates if the MS is being polled for a PACKET CONTROL ACKNOWLEDGEMENT. 0 no action is required from MS; 1 MS shall send a PACKET CONTROL ACKNOWLEDGEMENT message in the uplink block specified by TBF Starting Time, on the assigned PDCH. |
The TA_VALID field (1 bit field) indicates the validity of the timing advance value given in the Timing Advance IE. 0 the timing advance value is not valid ; 1 the timing advance value is valid. |
The TIMING_ADVANCE_INDEX field (4 bit field) is the binary representation of the timing advance index (TAI), see 3GPP TS 05.10 and 3GPP TS 04.04. Range: 0 to 15. |
The TBF_STARTING_TIME field (16 bit field) defines a starting time for the packet downlink assignment. The TBF starting time is coded using the same coding as the V format of the type 3 information element Starting Time (10.5.2.38). |
P0 (4 bit field) |
BTS_PWR_CTRL_MODE (1 bit field) |
PR_MODE (1 bit field) |
Second Part Packet Assignment The presence of the Second Part Packet Assignment is the indication that this message is the second message of two IMMEDIATE ASSIGNMENT messages in an assignment of an uplink or downlink Temporary Block Flow (TBF). The Extended RA (5 bits) is the Extended Random Access information. This is an unformatted 5 bit field, whose content is coded as the 5 least significant bits of the the EGPRS PACKET CHANNEL REQUEST message defined in 3GPP TS 04.60. The field shall be ignored by the mobile station, if present in a message used in an assignment of a downlink TBF. |
Frequency parameters, before time Length of frequency parameters (6 bit field) |
The MAIO field (6 bit field) is coded as the binary representation of the mobile allocation index offset. Range: 0 to 63. |
The Mobile Allocation field (k octet field (k = Length of frequency parameters –1) contains a bitmap referring to the Cell Channel Description IE in SI 1 message. The length of the bitmap is 8k, where k = ((NF-1) div 8 + 1) and where NF denotes the number of ARFCNs contained in the cell channel description. The different bit positions in the mobile allocation bitmap are assigned indices i = 1 to 8k, starting with i = 8k in the most significant bit position and ending with i = 1 in the least significant bit position. The bit position with index i corresponds to the i’th frequency in the cell channel description arranged in ascending order of ARFCN (except that ARFCN = 0, if included, is put last) and numbered from 1 to NF. Each bit position in the mobile allocation bitmap is coded: 0 RF channel not belonging to mobile allocation; 1 RF channel belonging to mobile allocation. If NF mod 8 <> 0, then bit positions i = NF+1 to 8k shall each be coded with a "0". |
EGPRS Packet Uplink Assignment EGPRS Packet Downlink AssignmentEGPRS specific fieds are detailed here. EGPRS Window Size IE This information element is encoded as the EGPRS window size IE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 04.60. |
LINK_QUALITY_MEASUREMENT_MODE (2 bit field) This field is encoded as the LINK_QUALITY_MEASUREMENT_MODE in the PACKET DOWNLINNK ASSIGNMENT message in 3GPP TS 04.60. |
Access Technology Type |
NUMBER OF RADIO BLOCKS ALLOCATED (2 bit field) 0 0 1 radio block reserved for uplink transmission; 0 1 2 radio blocks reserved for uplink transmission; 1 0 reserved for future use; 1 1 reserved for future use. |
EGPRS Modulation and Coding |
BEP_PERIOD2 (4 bit field) |
RESEGMENT (1 bit field) |
10.5.2.17 IAR Rest Octets
The IAR Rest Octets information element contains spare bits or possibly Extended RA informations.
The IAR Rest Octets information element is a type 5 information element with 3 octets length.
<IAR Rest Octets> ::= { 0 | 1 < Extended RA 1 : bit (5) > } { 0 | 1 < Extended RA 2 : bit (5) > } { 0 | 1 < Extended RA 3 : bit (5) > } { 0 | 1 < Extended RA 4 : bit (5) > } <spare padding> ; |
Figure 10.5.2.17.1: IAR Rest Octets information element
Table 10.5.2.17.1: IAR Rest Octets information element
The Extended RA i (5 bits) is the Extended Random Access information related to the Request Reference i (i within the range 1..4). These are unformatted 5 bit fields, whose contents are coded as the 5 least significant bits of the EGPRS PACKET CHANNEL REQUEST message defined in 3GPP TS 04.60. |
10.5.2.18 IAX Rest Octets
The IAX Rest Octets information element contains only spare bits only. Its purpose is to allow the upward compatible introduction of new information on the AGCH in later phases.
The IAX Rest Octets information element is a type 5 information element with 0-4 octets length.
<IAX Rest Octets> ::= <spare padding> ; |
Figure 10.5.2.18.1: IAX Rest Octets information element
10.5.2.19 L2 Pseudo Length
The L2 Pseudo Length information element indicates the number of octets following it in the message which are to be interpreted in the scope of the phase 1 protocol, i.e. the total number of octets (excluding the Rest Octets) for which T, V, TV, LV, or TLV formatting is used (reference table 11.1/3GPP TS 24.007).
The L2 Pseudo Length information element is the first part of e.g. SYSTEM INFORMATION messages which are mentioned as exceptions in sub-clause 10.1. It occupies the first octet of such messages.
For any of the SYSTEM INFORMATION messages sent on the BCCH, a mobile station should ignore the contents of the L2 Pseudo Length value contained in the L2 Pseudo Length information element. For some specific messages, further requirements are specified in clause 9.
The L2 Pseudo Length Information element is an element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
L2 Pseudo Length IEI | octet 1 | |||||||
L2 Pseudo Length value | 0 | 1 | octet 2 |
Figure 10.5.2.19.1: L2 Pseudo Length information element
Table 10.5.2.19.1: L2 Pseudo Length information element
L2 pseudo length value (octet 2) The coding of the L2 pseudo length value field is the binary representation of the L2 pseudo length of the message in which the L2 pseudo length information element occurs. |
NOTE: Bits 1 and 2 are not spare.
10.5.2.20 Measurement Results
The purpose of the Measurement Results information element is to provide the results of the measurements made by the mobile station on the serving cell and the neighbour cells.
The Measurement Results information element is coded as shown in figure 10.5.2.20.1 and table 10.5.2.20.1.
The Measurement Results is a type 3 information element with 17 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Measurement Results IEI | octet 1 | |||||||
BA- | DTX | RXLEV-FULL-SERVING-CELL | octet 2 | |||||
3G-BA-USED | MEAS- | RXLEV-SUB-SERVING-CELL | octet 3 | |||||
0 | RXQUAL-FULL | RXQUAL-SUB | NO- | octet 4 | ||||
NO-NCELL-M | RXLEV-NCELL 1 | octet 5 | ||||||
BCCH-FREQ-NCELL 1 | BSIC-NCELL 1 | octet 6 | ||||||
BSIC-NCELL 1 | RXLEV-NCELL 2 | octet 7 | ||||||
RXLEV | BCCH-FREQ-NCELL 2 | BSIC-NCELL | octet 8 | |||||
BSIC-NCELL 2 | RXLEV-NCELL 3 | octet 9 | ||||||
RXLEV- (low part) | BCCH-FREQ-NCELL 3 | BSIC- | octet 10 | |||||
BSIC-NCELL 3 | RXLEV-NCELL 4 | octet 11 | ||||||
RXLEV-NCELL 4 | BCCH-FREQ-NCELL 4 | octet 12 | ||||||
BSIC-NCELL 4 | RXLEV-NCELL | octet 13 | ||||||
RXLEV-NCELL 5 | BCCH-FREQ-NCELL 5 | octet 14 | ||||||
BCCH- | BSIC-NCELL 5 | RXLEV | octet 15 | |||||
RXLEV-NCELL 6 | BCCH-FREQ-NCELL 6 | octet 16 | ||||||
BCCH-FREQ- | BSIC-NCELL 6 | octet 17 |
Figure 10.5.2.20.1: Measurement Results information element
Table 10.5.2.20.1: Measurement Results information element details
BA-USED (octet 2), the value of the BA_IND field of the neighbour cell description information element or elements defining the BCCH allocation used for the coding of BCCH-FREQ-NCELL fields. Range 0 to 1. |
DTX-USED (octet 2) This bit indicates whether or not the mobile station used DTX during the previous measurement period. Bit 7 |
RXLEV-FULL-SERVING-CELL and RXLEV-SUB-SERVING-CELL, (octets 2 and 3) Received signal strength on serving cell, measured respectively on all slots and on a subset of slots (see 3GPP TS 05.08) The RXLEV-FULL-SERVING-CELL and RXLEV-SUB-SERVING-CELL fields are coded as the binary representation of a value N. N corresponds according to the mapping defined in 3GPP TS 05.08 to the received signal strength on the serving cell. Range: 0 to 63 |
MEAS-VALID (octet 3) Bit 7 |
3G-BA-USED (octet 3) |
RXQUAL-FULL-SERVING-CELL and RXQUAL-SUB-SERVING-CELL (octet 4) Received signal quality on serving cell, measured respectively on all slots and on a subset of the slots (see 3GPP TS 05.08) CELL fields are coded as the binary representation of the received signal quality on the serving cell. Range: 0 to 7 (See 3GPP TS 05.08) |
NO-NCELL-M, Number of neighbour cell measurements (octets 4 and 5) Bits 1 8 7 0 0 0 No neighbour cell measurement result 0 0 1 1 neighbour cell measurement result 0 1 0 2 neighbour cell measurement results 0 1 1 3 neighbour cell measurement results 1 0 0 4 neighbour cell measurement results 1 0 1 5 neighbour cell measurement results 1 1 0 6 neighbour cell measurement results 1 1 1 Neighbour cell information not available for serving cell |
RXLEV-NCELL i, Result of measurement on the i’th neighbour cell (octet 5, 7, 8, 9, 10, 11, 12, 13, 14, 15 and 16) If the i’th neighbour cell is a GSM cell, the RXLEV-NCELL field is coded as the binary representation of a value N. N corresponds according to the mapping defined in 3GPP TS 05.08 to the received signal strength on the i’th neighbouring cell. See note 1 & 2. If the i’th neighbour cell is a 3G cell, the contents of the RXLEV-NCELL field is defined in 3GPP TS 05.08. Range: 0 to 63. |
Report on GSM cells: BCCH-FREQ-NCELL i, BCCH carrier of the i’th neighbour cell (octet 6, 8,10, 12, 14, 15, 16 and 17). The BCCH-FREQ-NCELL i field is coded as the binary representation of the position, starting with 0, of the i’th neighbour cells BCCH carrier in the BCCH channel list. The BCCH channel list is composed of one or two BCCH channel sub lists, each sub list is derived from the set of frequencies defined by reference neighbour cell description information element or elements. In the latter case the set is the union of the two sets defined by the two neighbour cell description information elements. In each BCCH channel sub list the absolute RF channel numbers are placed in increasing order of ARFCN, except that ARFCN 0, if included in the set, is put in the last position in the sub list. The BCCH channel list consists either of only the sub list derived from the neighbour cell description information element(s) in System Information 2/5 (and possible 2bis/5bis) or of that sub list immediately followed by the sub list derived from the neighbour cell description information element in System Information 2ter/5ter for the case System Information 2ter/5ter is also received. If the set of ARFCNs defined by the reference neighbour cell description information element or elements includes frequencies that the mobile station does not support then these ARFCNs shall be included in the list. The notation 2/5 etc. means that the rules above apply to the neighbour cell description information elements received in System Information 2, 2bis and 2ter and to those received in System Information 5, 5bis and 5ter separately. See note 1 & 2. Range: 0 to 31/30. |
Report on 3G cells: If no more than 31 (GSM) ARFCN frequencies are included in the BA (list), the index BCCH-FREQ-NCELL 31 indicates report(s) on 3G cells. In this case, the corresponding ‘BSIC-NCELL’ field in Figure 10.5.2.20.1 carries the index of the i’th 3G neighbour cell in the 3G Neighbour Cell list defined in sub-clause 3.4.1.2.1.1, "Deriving the 3G Neighbour Cell list from the 3G Neighbour Cell Description". Range: 0 to 63. |
BSIC-NCELL i, Base station identity code of the i’th neighbour cell (octet 6, 7, 8, 9, 10, 11, 13, 15 and 17) For GSM cells, the BSIC-NCELL i field is coded as the binary representation of the base station identity code of the i’th neighbour cell. See note 1 & 2. Range: 0 to 63. NOTE 1: If the field extends over two octets the highest numbered bit of the lowest numbered octet is the most significant and the lowest numbered bit of the highest numbered octet is the least significant. NOTE 2: If NO-NCELL-M < 6 the remaining RXLEV-NCELL i, BS-FREQ-NCELL i and BSIC-NCELL i fields (NO-NCELL-M < i 6) shall be coded with a "0" in each bit. |
10.5.2.20a GPRS Measurement Results
The purpose of the GPRS Measurement Results information element is to provide the results of the GPRS measurements made by the GPRS mobile station on the serving cell.
The GPRS Measurement Results information element is coded as shown in figure 10.5.2.20a.1 and table 10.5.2.20a.1.
The GPRS Measurement Results is a type 3 information element with 3 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
GPRS Measurement Results IEI | octet 1 | |||||||
C_VALUE | RXQUAL | octet 2 | ||||||
RXQ-L | 0 | SIGN_VAR | octet 3 |
Figure 10.5.2.20a.1: GPRS Measurement Results information element
Table 10.5.2.20a.1: GPRS Measurement Results information element
C_VALUE (octet 1), the value of the C parameter calculated by the GPRS mobile station (see 3GPP TS 05.08). This field is encoded as the binary representation of the C parameter value defined in 3GPP TS 05.08. Range 0 to 63. RXQUAL (octets 1 and 2), contains the RXQUAL parameter field calculated by the GPRS mobile station (see 3GPP TS 05.08). This field is encoded as defined in 3GPP TS 05.08. Range 0 to 7. SIGN_VAR (octet 3), contains the signal variance parameter SIGN_VAR calculated by the mobile station (see 3GPP TS 05.08). This field is encoded as defined in 3GPP TS 04.60. |
10.5.2.21 Mobile Allocation
The purpose of the Mobile Allocation information element is to provide that part of the RF channels belonging to the cell allocation (coded with a "1" in the cell channel description information element) which is used in the mobile hopping sequence.
The Mobile Allocation information element is coded as shown in figure 10.5.2.21.1 and table 10.5.2.21.1.
The Mobile Allocation is a type 4 information element with 3 to 10 octets length except for the cases specified in sub-clause 9.1.18.1 and sub-clause 9.1.19.2.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Mobile Allocation IEI | octet 1 | |||||||
Length of mobile allocation contents | octet 2 | |||||||
MA | MA | MA | MA | MA | MA | MA | MA | octet 3 |
MA | MA | MA | MA | MA | MA | MA | MA | octet n+2 |
Figure 10.5.2.21.1: Mobile Allocation information element
Table 10.5.2.21.1: Mobile Allocation information element
MA C i, Mobile allocation RF channel i (octet 3 etc.), i = 1, 2,…, NF The MA C i bit indicates whether or not the Mobile allocation frequency list includes the i’th frequency in the cell allocation frequency list. The cell allocation frequency list is derived from the set of frequencies defined by the reference cell channel description information element. NF denotes the number of frequencies in the cell allocation frequency list. In the cell allocation frequency list the absolute RF channel numbers are placed in increasing order of ARFCN, except that ARFCN 0, if included in the set, is put in the last position in the list, For a RF channel belonging to the mobile allocation the MA C i bit is coded with a "1"; i = 1, 2,…, NF. For a RF channel not belonging to the mobile allocation the MA C i bit is coded with a "0"; i = 1, 2,…, NF. If NF mod 8 <> 0 then bits NF to 8n in octet 3 must be coded with a "0" in each. |
10.5.2.21a Mobile Time Difference
A Mobile Time Difference information element encodes a time related to the synchronization difference between the time bases of two base stations. This type of information is used in conjunction with the HANDOVER COMPLETE message.
The Mobile Time Difference information element is coded as shown in figure 10.5.2.21a.1 and table 10.5.2.21a.1.
The Mobile Time Difference information element is a type 4 information element with 5 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Mobile Time Difference IEI | Octet 1 | |||||||
Length of Mobile Time difference contents | Octet 2 | |||||||
Mobile Time Difference value (high) | Octet 3 | |||||||
Mobile Time Difference value (contd) | Octet 4 | |||||||
Mobile Time Difference value (low) | 0 | 0 | 0 | Octet 5 |
Figure 10.5.2.21a.1: Mobile Time Difference information element
Table 10.5.2.21a.1: Mobile Time Difference information element
Mobile Time Difference value (octet 3, 4 and 5) |
10.5.2.21aa MultiRate configuration
The MultiRate configuration information element gives all parameters related to a multi-rate speechcodec.
The MultiRate configuration information element is coded as shown in figure 10.5.2.21aa.1 and table 10.5.2.21aa.1.
The MultiRate configuration is a type 4 information element with a minimum length of 4 octets and a maximum length of 8 octets.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Multirate speech configuration IEI | octet 1 | |||||||
Length | octet 2 | |||||||
MR version | NSCB | ICMI | spare | Start mode | octet 3 | |||
Parameters for multirate speech | octet 4 . octet n |
Figure 10.5.2.21aa.1: MultiRate configuration information element
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Set of AMR codec modes | octet 4 |
Figure 10.5.2.21aa.2: Parameters for multirate speech field
for the MR version 1 when a set with one codec mode is chosen
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Set of AMR codec modes | octet 4 | |||||||
Spare | ||||||||
0 | 0 | Threshold 1 | octet 5 | |||||
Spare | ||||||||
Hysteresis 1 | 0 | 0 | 0 | 0 | octet 6 |
Figure 10.5.2.21aa.3/3GPP TS 04: Parameters for multirate speech field
for the MR version 1 when a set with two codec modes is chosen
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Set of AMR codec modes | octet 4 | |||||||
Spare | ||||||||
0 | 0 | Threshold 1 | octet 5 | |||||
Hysteresis 1 | Threshold 2 | octet 6 | ||||||
Threshold | Spare | |||||||
2 (cont.) | Hysteresis 2 | 0 | 0 | octet 7 |
Figure 10.5.2.21aa.4: Parameters for multirate speech field
for the MR version 1 when a set of three codec modes is chosen
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Set of AMR codec modes | octet 4 | |||||||
Spare | ||||||||
0 | 0 | Threshold 1 | octet 5 | |||||
Hysteresis 1 | Threshold 2 | octet 6 | ||||||
Threshold | Threshold 3 | |||||||
2 (cont.) | Hysteresis 2 | octet 7 | ||||||
Threshold (3) | Hysteresis 3 | octet 8 |
Figure 10.5.2.21aa.5: Parameters for multirate speech field
for the MR version 1 when a set of four modes is chosen
Table 10.5.2.21aa.1: MultiRate configuration information element
Octet 3 Bits 8 7 6 Multirate speech version 0 0 1 Adaptive Multirate speech version 1 Other values reserved Bit 5 NSCB: Noise Suppression Control Bit 0 Noise Suppression can be used (default) 1 Noise Suppression shall be turned off Bit 4 Initial Codec Mode Indicator 0 The initial codec mode is defined by the implicit rule provided in 3GPP TS 05.09 1 The initial codec mode is defined by the Start Mode field Bit 3 0 Spare Bits 2 1 Start Mode, The initial codec mode is coded as in 3GPP TS 05.09 sub-clause 3.4.1 When Multirate speech version field indicates Adaptive Multirate speech version 1 then the remaining fields are coded as follows: THRj (6 bits), is coded as the binary representation of a value N. N corresponds to the threshold of C/I in dB, as defined in 3GPP TS 05.09; HYSTj (4 bits) is coded as the binary representation of the hysteresis value associated to THRj, as defined in 3GPP TS 05.09. j = 1 corresponds to the lowest value of threshold in dB, j = 2 to the second lowest, j = 3 to the highest value. |
Set of adaptive multirate codec modes field (octet 4) | ||
Bit | Value | |
8 | 0 | 12,2 kbit/s codec rate is not part of the subset; |
1 | 12,2 kbit/s codec rate is part of the subset; | |
7 | 0 | 10,2 kbit/s codec rate is not part of the subset; |
1 | 10,2 kbit/s codec rate is part of the subset; | |
6 | 0 | 7,95 kbit/s codec rate is not part of the subset; |
1 | 7,95 kbit/s codec rate is part of the subset; | |
5 | 0 | 7,40 kbit/s codec rate is not part of the subset; |
1 | 7,40 kbit/s codec rate is part of the subset; | |
4 | 0 | 6,70 kbit/s codec rate is not part of the subset; |
1 | 6,70 kbit/s codec rate is part of the subset; | |
3 | 0 | 5,90 kbit/s codec rate is not part of the subset; |
1 | 5,90 kbit/s codec rate is part of the subset; | |
2 | 0 | 5,15 kbit/s codec rate is not part of the subset; |
1 | 5,15 kbit/s codec rate is part of the subset; | |
1 | 0 | 4,75 kbit/s codec rate is not part of the subset; |
1 | 4,75 kbit/s codec rate is part of the subset; |
10.5.2.21b Multislot Allocation
The purpose of the Multislot Allocation information element is to provide a description of which channels are used in downlink and uplink respectively, in a multislot configuration. It also groups the channels into channel sets, the channel mode for each channel set can be defined by a separate information element.
The Multislot Allocation information element is coded as shown in figure 10.5.2.21b.1 and table 10.5.2.21b.1.
The multislot allocation information element is a type 4 information element with a minimum length of 3 octets and a maximum length of 12 octets.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Multislot alloction IEI | octet 1 | |||||||
Length of the multislot allocation contents | octet 2 | |||||||
0/1 | DA | DA | DA | DA | DA | DA | DA | octet 3 |
1 | UA | UA | UA | UA | UA | UA | UA | octet 3a |
Channel set 1 | octet 4* | |||||||
Channel set 2 | octet 5* | |||||||
. | ||||||||
Channel set 8 | octet 11* |
Figure 10.5.2.21b.1: Multislot Allocation information element
Table 10.5.2.21b.1: Multislot allocation information element
DA 1-7, Downlink assignment (octet 3) Indicates additional downlink channel allocation. If bit DA n is set to "1" this indicates that timeslot TN = (n + TNm)mod8 is assigned. If bit DA n is set to "0" the corresponding timeslot is not assigned. TNm is the timeslot number of the main link. UA 1-7, Uplink assignment (octet 3a) Indicates additional uplink channel allocation. If bit UA n is set to "1" this indicates that timeslot TN = (n + TNm)mod8 is assigned. If bit UA n is set to "0" the corresponding timeslot is not assigned. TNm is the timeslot number of the main link. If octet 3a is not included the timeslots indicated by octet 3 are allocated in both downlink and uplink direction. NOTE 1: Allocation of timeslots only in uplink is FFS. NOTE 2: In combination with the channel description IE, all types of channels can be indicated. The channel carrying the main signalling link (indicated by the channel description IE is of type 1 (see below)), all other channels allocated both in downlink and uplink are of type 2 and channels with allocation in only one direction are of type 3. Type 1: TCH/F + FACCH/F + SACCH/M bidirectional Channel set n (octet 4 to 11 (if included)) If octets 4-11 are omitted, all channels belong to channel set 1. If bit m of Channel set n is set to "1" then timeslot m-1 is included in channel set n. If bit m of Channel set n is set to "0" then timeslot m-1 is not included in channel set n. Each allocated timeslot, including the timeslot carrying the main signalling link, shall be included in one (and only one) channel set. |
10.5.2.21c NC mode
The purpose of the NC mode information element is for the network to inform the mobile station of the NC mode to be implemented on the target cell.
The NC mode information element is coded as shown in figure 10.5.2.21c.1 and table 10.5.2.21c.1.
The NC mode is a type 1 information element.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
0 | 0 | octet 1 | ||||||
NC mode IEI | spare | NC mode |
Figure 10.5.2.21c.1: NC mode information element
Table 10.5.2.21c.1: NC Mode information element
NC mode This field indicates to the mobile the NC mode for the target cell (see 3GPP TS 04.60). The field is encoded according to the following table: bits 2 1 0 0 NC 0 0 1 NC 1 1 0 NC 2 1 1 information on NC mode to be gathered from the target cell |
10.5.2.22 Neighbour Cell Description
The purpose of the Neighbour Cell Description information element is to provide the absolute radio frequency channel numbers of the BCCH carriers to be monitored by the mobile stations in the cell.
The Neighbour Cell Description information element is coded as the Cell Channel Description information element, as specified in sub-clause 10.5.2.1b, with the exception of bits 5 and 6 of octet 2. Figure 10.5.2.22.1 and table 10.5.2.22.1: contains the difference of specifications.
The Neighbour Cell Description information element is a type 3 information element with 17 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Neighbour Cell Description IEI | octet 1 | |||||||
Bit | Bit | EXT- | BA- | Bit | Bit | Bit | Bit | octet 2 |
Bit | Bit | Bit | Bit | Bit | Bit | Bit | Bit | octet 3 |
Bit | Bit | Bit | Bit | Bit | Bit | Bit | Bit | octet 17 |
Figure 10.5.2.22.1: Neighbour Cell Description information element
Table 10.5.2.22.1: Neighbour Cell Description information element
EXT-IND, Extension indication (octet 2, bit 6) If received in System Information 2, 2bis, 5 or 5bis this bit indicates whether the information element carries the complete information of a BCCH channel sub list or whether a complementary information element is sent in another message. A GSM 900 mobile station which only supports the primary GSM band P‑GSM 900 (see 3GPP TS 05.05) may consider this bit as a spare bit and assume that the information element carries the complete BA, see sub-clause 3.2.2.1. NOTE: This indicator is set to 1 in the neighbour cell description information elements in System Information 2 and 2bis and 5 and 5bis respectively when more than one is needed to describe a BCCH channel sub list. Bit 6 0 The information element carries the complete BA 1 The information element carries only a part of the BA BA-IND, BCCH allocation sequence number indication (octet 2). Range 0 to 1 The BA-IND is needed to allow the network to discriminate measurements results related to different BAs (e.g. BA(BCCH) and BA(SACCH)) sent to the MS. |
10.5.2.22a Neighbour Cell Description 2
The purpose of the Neighbour Cell Description 2 information element is to provide the absolute radio frequency channel numbers of the BCCH carriers to be monitored by the mobile stations in the cell.
The Neighbour Cell Description 2 information element is coded as the Cell Channel Description information element, as specified in sub-clause 10.5.2.1b, with the exception of bits 5 to 7 of octet 2. Figure 10.5.2.22a.1 and table 10.5.2.22a.1: contains/ the difference of specifications.
The Neighbour Cell Description 2 information element is a type 3 information element with 17 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Neighbour Cell Description IEI | octet 1 | |||||||
Bit | Multiband | BA- | Bit | Bit | Bit | Bit | octet 2 | |
Bit | Bit | Bit | Bit | Bit | Bit | Bit | Bit | octet 3 |
Bit | Bit | Bit | Bit | Bit | Bit | Bit | Bit | octet 17 |
Figure 10.5.2.22a.1: Neighbour Cell Description 2 information element
Table 10.5.2.22a.1: Neighbour Cell Description 2 information element
Octet 2 bit 8, 4, 3 and 2 FORMAT-ID, Format Identifier (Bit 128 and next) Bit Bit Bit Bit format notation |
Bits 6 and 7 of Octet 2 Multiband reporting Binary encoding of multiband reporting parameter as specified in 3GPP TS 05.08. Range: 0 to 3 |
Bit 5 of octet 2 BA-IND, BCCH allocation sequence number indication. The BA-IND is needed to allow the network to discriminate measurements results related to different BAs (e.g. BA(BCCH) and BA(SACCH)) sent to the MS. Range 0 to 1. |
10.5.2.22b (void)
10.5.2.22c NT/N Rest Octets
The NT/N Rest Octets information element is a type 5 information element with 20 octets length.
NT/N Rest Octets ::= {0 I 1<NLN(PCH) : bit (2)>} <list of Group Call NCH information> <Spare padding>; |
<List of Group Call NCH information> ::= 0 | 1 <Group Call information> <List of Group Call NCH information> ; |
NLN(PCH) This field gives the NLN value to be used as specified in sub-clause 3.3.3 |
<Group Call information> See sub-clause 9.1.21a |
10.5.2.23 P1 Rest Octets
The P1 Rest Octets information element contains information about the status of information on an existing NCH, priority levels and packet page indications applied for mobile station identities and spare bits.
The P1 Rest Octets information element is a type 5 information element with 0-17 octets length.
{ <P1 Rest Octets> ::= {L I H <NLN(PCH) : bit (2)> <NLN status : bit>} {L I H <Priority1 ::= Priority>} {L I H <Priority2 ::= Priority>} {L | H <Group Call information>} < Packet Page Indication 1 : {L | H} > < Packet Page Indication 2 : {L | H} > <spare padding>; } — truncation allowed, bits ‘L’ assumed |
<Priority> ::= <bit (3)>; |
<Group Call information> See sub-clause 9.1.21a |
NOTE 1: The value 17h shall not be used as a value of the first octet when this information element is used in the PAGING REQUEST TYPE 1 message. This will prevent mobile stations misinterpreting this information as the Mobile Identity IEI.
Table 10.5.2.23.1: P1 Rest Octets information element
NLN(PCH) Notification List Number Priority: Priority i relates to Mobile Station Identity i (i = 1, 2) 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 The Packet Page Indication i field relates to Mobile Station Identity i (i = 1, 2) and indicates the kind of paging procedure associated with the mobile station identity. If the identity is not IMSI the Packet Page Indication has no meaning and is ignored. L paging procedure for RR connection establishment; H packet paging procedure. |
10.5.2.24 P2 Rest Octets
The P2 Rest Octets information element contains information on the channel needed by the network and information about the status of information on an existing NCH, priority levels and packet page indications applied for mobile station identities and spare bits.
The P2 Rest Octets information element is a type 5 information element with 1-11 octets length.
{ <P2 Rest Octets> ::= {L I H <CN3: bit (2)>} {L I H <NLN : bit (2)> <NLN status : bit>} {L I H <Priority1 ::= Priority>} {L I H <Priority2 ::= Priority>} {L I H <Priority3 ::= Priority>} < Packet Page Indication 3 : {L | H} > <spare padding>; } — truncation allowed, bits ‘L’ assumed <Priority> ::= <bit(3)>; |
NOTE 1: The value 17h shall not be used as a value of the first octet when this information element is used in the PAGING REQUEST TYPE 2 message. This will prevent mobile stations misinterpreting this information as the Mobile Identity IEI.
Table 10.5.2.24.1: P2 Rest Octets information element
CN3 Channel Needed for Mobile Identity 3 If the CN3 field is not present, the default value is 00 (any channel). NLN Notification List Number Priority: Priority i relates to Mobile Station Identity i (i = 1, 2, 3) 0 0 0 no priority applied The Packet Page Indication 3 field relates to Mobile Station Identity 3 and indicates the kind of paging procedure associated with the mobile station identity. If the identity is not IMSI the Packet Page Indication has no meaning and is ignored. L paging procedure for RR connection establishment; |
10.5.2.25 P3 Rest Octets
The P3 Rest Octets information element contains information on the channel needed by the network and information about the status of information on an existing NCH, priority levels applied for mobile station identities and spare bits. The purpose of the spare bits is to allow the upward compatible introduction of new information on the PCH in later phases.
The P3 Rest Octets information element is a type 5 information element with 3 octets length.
<P3 Rest Octets> ::= {L I H <CN3 : bit (2)> <CN4 : bit (2)>} {L I H <NLN : bit (2)> <NLN status : bit>} {L I H <Priority1 ::= Priority>} {L I H <Priority2 ::= Priority>} {L I H <Priority3 ::= Priority>} {L I H <Priority4 ::= Priority>} <spare padding>; <Priority> ::= <bit(3)>; |
Table 10.5.2.25.1: P3 Rest Octets information element
CN3 Channel Needed for Mobile Identity 3 The values and semantics used in the CN3 field are those of the CHANNEL field of Channel Needed IE (see sub-clause 10.5.2.8). The CN3 field is associated with the Mobile Identity 3 IE of the PAGING REQUEST TYPE 3 message. If the CN3 field is not present, the default value is 00 (any channel) CN4 Channel Needed for Mobile Identity 4 The values and semantics used in the CN43 field are those of the CHANNEL field of Channel Needed IE (see sub-clause 10.5.2.8). The CN4 field is associated with the Mobile Identity 4 IE of the PAGING REQUEST TYPE 3 message. If the CN4 field is not present, the default value is 00 (any channel) NLN Notification List Number See P1 Rest Octets Priority: Priority i relates to Mobile Station Identity i 0 0 0 no priority applied |
10.5.2.25a Packet Channel Description
The purpose of the Packet Channel Description information element is to provide a description of a packet data physical channel (PDCH).
The Packet Channel Description information element is coded according to the syntax specified below and described in table 10.58.
The Packet Channel Description is a type 3 information element with 4 octets length.
< Packet Channel Description > ::= < Channel type : bit (5) > < TN : bit (3) > < TSC : bit (3) > { 0 { 0 < spare bit > < ARFCN : bit (10) > — non-hopping RF channel configuraion | 1 < spare bit > < MAIO : bit (6) > — indirect encoding of hopping RF channel configuration < MA_NUMBER_IND : bit > { 0 < spare bits : bit (2) > | 1 < CHANGE_MARK_1 : bit (2) > } } | 1 < MAIO : bit (6) > — direct encoding of hopping RF channel configuration < HSN : bit (6) > }; |
Table 10.5.2.25a.1: Packet Channel Description information element
The Channel type field (5 bit) shall be ignored by the receiver and all bits treated as spare. For backward compatibility reasons, the sender shall set the spare bits to binary ‘00001’. |
The TN field (3 bit) is the binary representation of the timeslot number as defined in 3GPP TS 05.10. Range: 0 to 7 |
The TSC field (3 bit) is the binary representation of the training sequence code as defined in 3GPP TS 05.02. |
Non-hopping RF channel configuration |
Indirect encoding of hopping RF channel configuration |
The MA_NUMBER_IND field (1 bit) is the binary representation of the MA_NUMBER to use as reference to a GPRS mobile allocation: 0 MA_NUMBER = 14 1 MA_NUMBER = 15 |
The CHANGE_MARK_1 field (2 bit) is the binary representation of the allowed value of the SI change mark associated with the GPRS mobile allocation to which the MA_NUMBER refers. Range: 0 to 3. If the indirect encoding is used, this information element may contain the CHANGE_MARK_1 field. If that is present, the mobile station being assigned the TBF shall verify the validity of the SI change mark associated with the GPRS mobile allocation to which this information element refers, see 3GPP TS 04.60. The CHANGE_MARK_1 field shall not be included in this information element if MA_NUMBER = 15 is used. |
Direct encoding of hopping RF channel configuration The HSN field (6 bit) is the binary representation of the hopping sequence number, see 3GPP TS 05.02. Range: 0 to 63. |
10.5.2.25b Dedicated mode or TBF
The Dedicated mode or TBF information element is used by the network to indicate to the mobile station whether the rest of the message shall be decoded as an IMMEDIATE ASSIGNMENT message allocating a channel in dedicated mode or whether the rest of the message shall be decoded as the allocation of a Temporary Block Flow.
This IE information element also indicates:
– whether the IMMEDIATE ASSIGNMENT message relates to identifies a mobile station in the IA Rest Octets information elements for the assignment of a downlink TBF for a mobile station in packet idle mode; and
– whether the IMMEDIATE ASSIGNMENT message is the first message of two IMMEDIATE ASSIGNMENT messages in a two-message assignment of an uplink or downlink TBF.
The Dedicated mode or TBF information element is coded as shown in Figure 10.5.2.25b.1, and Table 10.5.2.25b.1 and Table 10.5.2.25b.2.
The Dedicated mode or TBF is a type 1 information element.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Dedicated mode | spare | TMA | down- | T/D | octet 1 |
Figure 10.5.2.25b.1: Dedicated mode or TBF information element
Table 10.5.2.25b.1: Dedicated mode or TBF information element
T/D : TBF or dedicated mode (octet 1, bit 1) Bit |
Downlink : Downlink TBF assignment to the mobile station identified in the IA Rast Octets IE in packet idle mode (octet 1, bit 2) Bit |
TMA : Two-message assignment (octet 1, bit 3) Bit |
Table 10.5.2.25b.2: Dedicated mode or TBF information element:
T/D, downlink and TMA fields
TMA | downlink | T/D | Description |
---|---|---|---|
0 | 0 | 0 | This message assigns a dedicated mode resource |
0 | 1 | 0 | Not used (Note 1) |
1 | 0 | 0 | Not used (Note 1) |
1 | 1 | 0 | Not used (Note 1) |
0 | 0 | 1 | This message assigns an uplink TBF or is the second message of two in a two-message assignment of an uplink or downlink TBF |
0 | 1 | 1 | This message assigns a downlink TBF to the mobile station identified in the IA Rest Octets IE |
1 | 0 | 1 | This message is the first message of two in a two-message assignment of an uplink TBF |
1 | 1 | 1 | This message is the first message of two in a two-message assignment of a downlink TBF to the mobile station identified in the IA Rest Octets IE |
NOTE 1: The code point is not used. The behaviour of the mobile station is not defined. The code point should not be used in future versions of the protocol. |
10.5.2.25c RR Packet Uplink Assignment
The RR Packet Uplink Assignment information element is sent by the network to the mobile station to indicate the assigned uplink resources.
The RR Packet Uplink Assignment information element is coded as shown in figure 10.5.2.25c.1 and tables 10.5.2.25c.1 and 10.5.2.25c.2.
The RR Packet Uplink Assignment is a type 4 information element with a minimum length of 4 octets. The maximum length of this information element is resulting from the encoding of the value part as specified below.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
RR Packet Uplink Assignment IEI | octet 1 | |||||||
Length of RR Packet Uplink Assignment value part | octet 2 | |||||||
RR Packet Uplink Assignment value part | octet 3 – n |
Figure 10.5.2.25c.1: RR PACKET UPLINK ASSIGNMENT information element
Table 10.5.2.25c.1: RR Packet UPlink ASSIGNMENT value part
< RR Packet Uplink Assignment value part > ::= < TLLI_BLOCK_CHANNEL_CODING : bit (1) > < Packet Timing Advance : Packet Timing Advance IE > { 01 < Dynamic Allocation : Dynamic Allocation struct > | 10 < Single Block Allocation : Single Block Allocation struct > | 11 < Fixed Allocation : Fixed Allocation struct > | 00 < Extension > } { null — Receiver compatible with earlier release | — Additions for R99 { 0 | 1 < EGPRS_MCS_MODE : bit (4) > < RESEGMENT : bit (1) > < EGPRS Window Size : < EGPRS Window Size IE >> } { 0 | 1 < Packet Extended Timing Advance : bit (2) > } < SPARE_BITS : bit ** > } ; |
< Extension > ::= — Future extension can be done by modifying this structure null ; |
<Dynamic Allocation struct > ::= < Extended Dynamic Allocation : bit(1)> {0 | 1 < P0 : bit (4) > < PR_MODE : bit (1) > } < USF_GRANULARITY : bit (1) > { 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > } { 0 | 1 < RLC_DATA_BLOCKS_GRANTED : bit (8) > } { 0 — Timeslot Allocation { 0 | 1 < USF_TN0 : bit (3) > } { 0 | 1 < USF_TN1 : bit (3) > } { 0 | 1 < USF_TN2 : bit (3) > } { 0 | 1 < USF_TN3 : bit (3) > } { 0 | 1 < USF_TN4 : bit (3) > } { 0 | 1 < USF_TN5 : bit (3) > } { 0 | 1 < USF_TN6 : bit (3) > } { 0 | 1 < USF_TN7 : bit (3) > } | 1 — Timeslot Allocation with Power Control Parameters < ALPHA : bit (4) > { 0 | 1 < USF_TN0 : bit (3) > < GAMMA_TN0 : bit (5) > } { 0 | 1 < USF_TN1 : bit (3) > < GAMMA_TN1 : bit (5) > } 0 | 1 < USF_TN2 : bit (3) > < GAMMA_TN2 : bit (5) > } { 0 | 1 < USF_TN3 : bit (3) > < GAMMA_TN3 : bit (5) > } { 0 | 1 < USF_TN4 : bit (3) > < GAMMA_TN4 : bit (5) > } { 0 | 1 < USF_TN5 : bit (3) > < GAMMA_TN5 : bit (5) > } { 0 | 1 < USF_TN6 : bit (3) > < GAMMA_TN6 : bit (5) > } { 0 | 1 < USF_TN7 : bit (3) > < GAMMA_TN7 : bit (5) > } } ; |
<Single Block Allocation struct > ::= < TIMESLOT_NUMBER : bit (3) > { 0 | 1 < ALPHA : bit (4) > < GAMMA_TN : bit (5) > } { 0 | 1 < P0 : bit (4) > < BTS_PWR_CTRL_MODE : bit (1) > < PR_MODE : bit (1) > } ; |
<Fixed Allocation struct > ::= { 0 | 1 < UPLINK_TFI_ASSIGNMENT : bit (5) > } < FINAL_ALLOCATION : bit (1) > < DOWNLINK_CONTROL_TIMESLOT: bit(3) > { 0 | 1 < P0 : bit (4) > < BTS_PWR_CTRL_MODE : bit (1) > < PR_MODE : bit (1) > } { 0 < TIMESLOT_ALLOCATION : bit (8) > | 1 < Power Control Parameters : Power Control Parameters IE > } < HALF_DUPLEX_MODE : bit (1) > { 0 { 0 — with length of allocation bitmap < BLOCKS_OR_BLOCK_PERIODS : bit (1) > < ALLOCATION_BITMAP_LENGTH : bit (7) > < ALLOCATION_BITMAP : bit (val(ALLOCATION_BITMAP_LENGTH)) > | 1 — without length of Allocation Bitmap (fills remainder of this IE) < ALLOCATION_BITMAP : bit ** > } ! < Message escape : 1 bit (*) = <no string > > } ; |
Table 10.5.2.25c.2: RR Packet UPlink ASSIGNMENT value part details
TIMESLOT_ALLOCATION (8 bit field) |
CHANNEL_CODING_COMMAND (2 bit field) |
EGPRS_MCS_MODE (4 bit field) |
RESEGMENT (1 bit field) |
EGPRS Window Size IE |
TLLI_BLOCK_CHANNEL_CODING (1 bit field) |
Packet Timing Advance IE |
Dynamic Allocation struct |
Extended Dynamic Allocation (1 bit field) |
UPLINK_TFI_ASSIGNMENT (5 bit field) |
Power Control Parameters IE |
RLC_DATA_BLOCKS_GRANTED (8 bit field) |
USF for Timeslot Number 0 (TN0) (3 bit field) |
Single Block Allocation struct |
ALPHA (4 bit field) bits 4 3 2 1 0 0 0 0 a = 0.0 0 0 0 1 a = 0.1 : : : 1 0 0 1 a = 0.9 1 0 1 0 a = 1.0 All other values are reserved in this version of the protocol and shall be interpreted by the mobile station as = 1.0. |
TIMESLOT_NUMBER (3 bit field) |
GAMMA_TN (5 bit field) |
P0, BTS_PWR_CTRL_MODE and PR_MODE fields |
Fixed Allocation struct |
FINAL_ALLOCATION (1 bit field) 0 this allocation is not the last allocation of the TBF |
DOWNLINK_CONTROL_TIMESLOT (3 bit field) This information field indicates the downlink timeslot that mobile station operating in fixed allocation mode shall monitor for downlink PACCH. This field is coded as the binary representation of the timeslot number as defined in 3GPP TS 05.10. |
HALF_DUPLEX_MODE (1 bit field) Bit |
BLOCKS_OR_BLOCK_PERIODS (1 bit field) |
ALLOCATION_BITMAP_LENGTH (7 bit field) |
ALLOCATION_BITMAP (variable length field) |
Packet Extended Timing Advance (2 bit field) Bit |
Extension and Message escape fields |
10.5.2.25d RR Packet Downlink Assignment
The RR Packet Downlink Assignment information element is sent by the network to the mobile station to indicate the assigned downlink resources.
The RR Packet Downlink Assignment information element is coded as shown in figure 10.5.2.25d.1 and tables 10.5.2.25d.1 and 10.5.2.25d.2.
The RR Packet Downlink Assignment is a type 4 information element with a minimum length of 5 octets. The maximum length of this information element is resulting from the encoding of the value part as specified below.
For a mobile station assigned to operate in the fixed allocation MAC mode, the network may assign regularly repeating intervals during which the mobile station shall measure neighbour cell power levels.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
RR Packet Downlink Assignment IEI | octet 1 | |||||||
Length of RR Packet Downlink Assignment value part | octet 2 | |||||||
RR Packet Downlink Assignment value part | octet 3 – n |
Figure 10.5.2.25d.1: RR PACKET DOWNLINK ASSIGNMENT information element
Table 10.5.2.25d.1: RR Packet Downlink ASSIGNMENT value part
< RR Packet Downlink Assignment value part > ::= < MAC_MODE : bit (2) > < RLC_MODE : bit (1) > < TIMESLOT_ALLOCATION : bit (8) > < Packet Timing Advance : Packet Timing Advance IE > { 0 | 1 < P0 : bit (4) > < BTS_PWR_CTRL_MODE : bit(1) > < PR_MODE : bit (1) > } { 0 | 1 < Power Control Parameters : Power Control Parameters IE > } { 0 | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > } { 0 | 1 < MEASUREMENT_STARTING_TIME : bit (16) > < MEASUREMENT_INTERVAL : bit (5) > < MEASUREMENT_BITMAP : bit (8) > } { null — Receiver compatible with earlier release | { 0 | 1– indicates EGPRS TBF mode, see 3GPP TS 04.60 < EGPRS Window Size : < EGPRS Window Size IE >> < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > } { 0 | 1 < Packet Extended Ttiming Advance : bit (2)> } < SPARE_BITS : bit ** > } ; |
Table 10.5.2.25d.2: RR PACKET Downlink ASSIGNMENT
value part details
MAC_MODE (2 bit field) |
RLC_MODE (1 bit field) |
TIMESLOT_ALLOCATION (8 bit field) |
Packet Timing Advance IE |
P0, BTS_PWR_CTRL_MODE and PR_MODE fields |
Power Control Parameters IE |
DOWNLINK_TFI_ASSIGNMENT (5 bit field) |
MEAUREMENT_STARTING_TIME (16 bit field) The frame number shall be aligned to a PDCH block period according to the requirements defined for the ‘Absolute Frame Number Encoding’ in the ‘Starting Time Frame Number Description’ IE defined in 3GPP TS 04.60. |
MEASUREMENT_BITMAP (8 bit field) |
MEASUREMENT_INTERVAL (5 bit field) |
EGPRS Window Size IE |
LINK_QUALITY_MEASUREMENT_MODE (2 bit field) |
Packet Extended Timing Advance (2 bit field) Bit |
10.5.2.26 Page Mode
The purpose of the Page Mode information element is to control the action of the mobile station belonging to the paging subgroup corresponding to the paging subchannel.
The Page Mode information element is coded as shown in figure 10.5.2.26.1 and table 10.5.2.26.1.
The Page Mode is a type 1 information element.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Page Mode IEI | 0 | 0 | PM | octet 1 |
Figure 10.5.2.26.1: Page Mode information element
Table 10.5.2.26.1: Page Mode information element
PM (octet 1) Bits 2 1 0 0 Normal paging. 0 1 Extended paging. 1 0 Paging reorganization. 1 1 Same as before. |
NOTE: The value "same as before" has been defined instead of "reserved" to allow the use of this coding with another meaning in an upwards compatible way in later phases of the GSM system. |
10.5.2.26a (void)
10.5.2.26b (void)
10.5.2.26c (void)
10.5.2.26d (void)
10.5.2.27 NCC Permitted
The purpose of the NCC Permitted information element is to provide a definition of the allowed NCCs on the BCCH carriers to be reported in the MEASUREMENT REPORT message by the mobile stations in the cell.
The NCC Permitted information element is coded as shown in figure 10.5.2.27.1 and table 10.5.2.27.1.
The NCC Permitted is a type 3 information element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
NCC Permitted IEI | octet 1 | |||||||
NCC permitted | octet 2 |
Figure 10.5.2.27.1: NCC Permitted information element
Table 10.5.2.27.1: NCC Permitted information element
NCC permitted (octet 2) The NCC permitted field is coded as a bit map, i.e. bit N is coded with a "0" if the BCCH carrier with NCC = N-1 is not permitted for monitoring and with a "1" if the BCCH carrier with NCC = N-1 is permitted for monitoring; N = 1,2,..,8. |
10.5.2.28 Power Command
The purpose of the Power Command information element is to provide the power level to be used by the mobile station.
The Power Command information element is coded as shown in figure 10.5.2.28.1 and table 10.5.2.28.1.
The Power Command is a type 3 information element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Power Command IEI | octet 1 | |||||||
0 | 0 | FPC | POWER LEVEL | |||||
spare | spare | octet 2 |
Figure 10.5.2.28.1: Power Command information element
Table 10.5.2.28.1: Power Command information element
FPC (octet 2) The FPC field (octet 2) indicates whether Fast Measurement Reporting and Power Control mechanism is used. It is coded as follows: Value 0 FPC not in use Power level (octet 2) The power level field is coded as the binary representation of the "power control level", see 3GPP TS 05.05. This value shall be used by the mobile station according to 3GPP TS 05.08. Range: 0 to 31. |
10.5.2.28a Power Command and access type
The purpose of the Power Command and access type information element is to provide the power level to be used by the mobile station and the indication that the mobile station can avoid the transmission of handover access.
The Power Command and access type information element is coded as shown in figure 10.5.2.28a.1 and table 10.5.2.28a.1.
The Power Command and access type is a type 3 information element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Power Command and Access Type IEI | octet 1 | |||||||
ATC | 0 | FPC | POWER LEVEL | |||||
spare | octet 2 |
Figure 10.5.2.28a.1: Power Command and access type information element
Table 10.5.2.28a.1: Power Command and access type information element
ATC (Access Type Control) (octet 2) bit 8 FPC (octet 2) The FPC field (octet 2) indicates whether Fast Measurement Reporting and Power Control mechanism is used. It is coded as follows: Value 0 FPC not in use Power level (octet 2) The power level field is coded as the binary representation of the "power control level", see 3GPP TS 05.05. This value shall be used by the mobile station according to 3GPP TS 05.08. Range: 0 to 31. |
10.5.2.29 RACH Control Parameters
The purpose of the RACH Control Parameters information element is to provide parameters used to control the RACH utilization. This information element is broadcast to mobile stations in SYSTEM INFORMATION TYPE 1, 2, 2bis, 3, and 4 messages.
The RACH Control Parameters information element is coded as shown in figure 10.5.2.29.1 and table 10.5.2.29.1.
The RACH Control Parameters is a type 3 information element with 4 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
RACH Control Parameters IEI | octet 1 | |||||||
Max retrans | Tx-integer | CELL | RE | octet 2 | ||||
AC | AC | AC | AC | AC | AC | AC | AC | octet 3 |
AC | AC | AC | AC | AC | AC | AC | AC | octet 4 |
Figure 10.5.2.29.1: RACH Control Parameters information element
Table 10.5.2.29.1: RACH Control Parameters information element
Max retrans, Maximum number of retransmissions (octet 2) Bits 8 7 0 0 Maximum 1 retransmission 0 1 Maximum 2 retransmissions 1 0 Maximum 4 retransmissions 1 1 Maximum 7 retransmissions |
Tx-integer, Number of slots to spread transmission (octet 2) Bits 6 5 4 3 0 0 0 0 3 slots used to spread transmission 0 0 0 1 4 slots used to spread transmission 0 0 1 0 5 slots used to spread transmission 0 0 1 1 6 slots used to spread transmission 0 1 0 0 7 slots used to spread transmission 0 1 0 1 8 slots used to spread transmission 0 1 1 0 9 slots used to spread transmission 0 1 1 1 10 slots used to spread transmission 1 0 0 0 11 slots used to spread transmission 1 0 0 1 12 slots used to spread transmission 1 0 1 0 14 slots used to spread transmission 1 0 1 1 16 slots used to spread transmission 1 1 0 0 20 slots used to spread transmission 1 1 0 1 25 slots used to spread transmission 1 1 1 0 32 slots used to spread transmission 1 1 1 1 50 slots used to spread transmission |
CELL_BAR_ACCESS, Cell Barred for Access (octet 2) Bit 2 0 The cell is not barred, see 3GPP TS 03.22 1 The cell is barred, see 3GPP TS 03.22 |
RE, Call reestablishment allowed (octet 2) Bit 1 0 Call Reestablishment allowed in the cell 1 Call Reestablishment not allowed in the cell |
EC Emergency Call allowed (octet 3 bit 3) 3 0 Emergency call allowed in the cell to all MSs 1 Emergency call not allowed in the cell except for the MSs that belong to one of the classes between 11 to 15 |
AC CN, Access Control Class N (octet 3(except bit 3) and octet 4) For a mobile station with AC C = N access is not barred if the AC CN bit is coded with a "0"; N = 0, 1, .. 9,11, .., 15. |
10.5.2.30 Request Reference
The purpose of the Request Reference information element is to provide the random access information used in the channel request and the frame number, FN modulo 42432 in which the channel request was received.
The Request Reference information element is coded as shown in figure 10.5.2.30.1 and table 10.5.2.30.1.
The Request Reference is a type 3 information element with 4 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Request Reference IEI | octet 1 | |||||||
RA | octet 2 | |||||||
T1′ | T3 | octet 3 | ||||||
T3 | T2 | octet 4 |
Figure 10.5.2.30.1: Request Reference information element
Table 10.5.2.30.1: Request Reference information element
RA, Random Access Information (octet 2) This is an unformatted 8 bit field. Typically the contents of this field are coded the same as the CHANNEL REQUEST message shown in Table 9.9, sub-clause 9.1.8 T1′ (octet 2) The T1′ field is coded as the binary representation of (FN div 1326) mod 32. T3 (octet 3 and 4) The T3 field is coded as the binary representation of FN mod 51. Bit 3 of octet 2 is the most significant bit and bit 6 of octet 3 is the least significant bit. T2 (octet 4) The T2 field is coded as the binary representation of FN mod 26. |
NOTE: The frame number, FN modulo 42432 can be calculated as |
10.5.2.31 RR Cause
The purpose of the RR Cause information element is to provide the reason for release or the reason for completion of an assignment or handover.
The RR Cause information element is coded as shown in figure 10.5.2.31.1 and table 10.5.2.31.1.
The RR Cause is a type 3 information element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
RR Cause IEI | octet 1 | |||||||
RR cause value | octet 2 |
Figure 10.5.2.31.1: RR Cause information element
Table 10.5.2.31.1: RR Cause information element
RR cause value (octet 2) Bits 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 Normal event 0 0 0 0 0 0 0 1 Abnormal release, unspecified 0 0 0 0 0 0 1 0 Abnormal release, channel unacceptable 0 0 0 0 0 0 1 1 Abnormal release, timer expired 0 0 0 0 0 1 0 0 Abnormal release, no activity on the radio path 0 0 0 0 0 1 0 1 Preemptive release 0 0 0 0 0 1 1 0 UTRAN configuration unknown 0 0 0 0 1 0 0 0 Handover impossible, timing advance out of range 0 0 0 0 1 0 0 1 Channel mode unacceptable 0 0 0 0 1 0 1 0 Frequency not implemented 0 0 0 0 1 1 0 0 Lower layer failure 0 1 0 0 0 0 0 1 Call already cleared 0 1 0 1 1 1 1 1 Semantically incorrect message 0 1 1 0 0 0 0 0 Invalid mandatory information 0 1 1 0 0 0 0 1 Message type non-existent or not implemented 0 1 1 0 0 0 1 0 Message type not compatible with protocol state 0 1 1 0 0 1 0 0 Conditional IE error 0 1 1 0 0 1 0 1 No cell allocation available 0 1 1 0 1 1 1 1 Protocol error unspecified All other cause values shall be treated as 0000 0000, ‘normal event’ The listed RR cause values are defined in Annex F. |
10.5.2.32 SI 1 Rest Octets
The SI 1 Rest Octets information element contains the position about the NCH and spare bits.
The SI 1 Rest Octets information element is a type 5 information element with 1 octet length.
<SI1 Rest Octets> ::= {L |H <NCH Position : bit (5)> } < Band indicator > <spare padding> ; |
< Band indicator > ::= < BAND_INDICATOR : bit == L > — ARFCN indicates 1800 band | < BAND_INDICATOR : bit == H > ; — ARFCN indicates 1900 band |
Table 10.5.2.32.1a: SI1 Rest Octets information element details
BAND_INDICATOR (1 bit) The band indicator for 1800 and 1900 associates the ARFCN channel numbers to the DCS 1800 respectively to the PCS 1900 band, see 3GPP TS 05.05. |
Table 10.5.2.32.1b: SI 1 Rest Octets information element
NCH Position on the CCCH The values in the NCH Position field indicates the block number of the CCCH block which is used for the first NCH block and the number of blocks used for the NCH. (The block numbering corresponds to table 5 in clause 7 of 3GPP TS 05.02) The absence of the NCH position field indicates that there is no NCH in the cell/on the carrying CCCH slot. The following coding applies if 1 or more basic physical channels are used for CCCH, not combined with SDCCHs. Value No of blocks Number of first block 0 0 0 0 0 1 0 0 0 0 0 1 1 1 0 0 0 1 0 1 2 0 0 0 1 1 1 3 0 0 1 0 0 1 4 0 0 1 0 1 1 5 0 0 1 1 0 1 6 0 0 1 1 1 2 0 0 1 0 0 0 2 1 0 1 0 0 1 2 2 0 1 0 1 0 2 3 0 1 0 1 1 2 4 0 1 1 0 0 2 5 0 1 1 0 1 3 0 0 1 1 1 0 3 1 0 1 1 1 1 3 2 1 0 0 0 0 3 3 1 0 0 0 1 3 4 1 0 0 1 0 4 0 1 0 0 1 1 4 1 1 0 1 0 0 4 2 1 0 1 0 1 4 3 1 0 1 1 0 5 0 1 0 1 1 1 5 1 1 1 0 0 0 5 2 1 1 0 0 1 6 0 1 1 0 1 0 6 1 1 1 0 1 1 7 0 Other values are reserved for future use. A mobile station receiving a reserved value shall behave as if the NCH position was not present. |
In the case the CCCH configuration is not compatible with the NCH position (e.g. CCCH with combined SDCCH and the value different from 00000, 00001 or 00111), the mobile station shall behave as if the NCH Position field was not present.
10.5.2.33 SI 2bis Rest Octets
The SI 2bis Rest Octets information element contains only spare bits. Its purpose is to allow the upward compatible introduction of new information on the BCCH in later phases.
The SI 2bis Rest Octets information element is a type 5 information element with 1 octet length.
Table 10.5.2.33.1: SI 2bis Rest Octets information element
<SI2bis Rest Octets> ::= <spare padding> ; |
10.5.2.33a SI 2ter Rest Octets
SI2ter Rest Octets information element contains optional information on UTRAN cell(s) to be monitored by the mobile in the cell. It is used together with 3G Cell(s) from the SI2quater message to build the 3G Cell Reselection list, see sub-clause 3.4.1.2.1.7. Optionally this information element may in addition include thresholds that the mobile shall use for cell reselection. Information received in this message do not modify the 3G Neighbour Cell list used for reporting and defined in sub-clause 3.4.1.2.1.1.
The SI 2ter Rest Octets information element is a type 5 information element with 4 octets length.
Table 10.5.2.33a.1: SI 2ter Rest Octets information element
<SI2ter Rest Octets> ::= { L | H < SI2ter_MP_CHANGE_MARK : bit(1) > < SI2ter_3G_CHANGE_MARK : bit(1) > < SI2ter_INDEX : bit(3) > < SI2ter_COUNT : bit(3) > { 0 | 1 < UTRAN FDD Description : < UTRAN FDD Description struct > > } { 0 | 1 < UTRAN TDD Description : < UTRAN TDD Description struct > > } { 0 | 1 < 3G MEASUREMENT Parameters Description :< 3G MEASUREMENT Parameters Description struct > > } } <spare padding> ; |
< UTRAN FDD Description struct >::= — 21 bits are available if this structure is present on its own 01 < FDD-ARFCN : bit (14) > — requires 2+14=16 bits — The values ’00’, ’10’ and ’11’ were used in an earlier version — of the protocol and shall not be used. { 0 | 1 < Bandwidth_FDD : bit (3) > } ; |
< UTRAN TDD Description struct >::= — 21 bits are available if this structure is present on its own 01 < TDD-ARFCN : bit (14) > — requires 2+14=16 bits — The values ’00’, ’10’ and ’11’ were used in an earlier version — of the protocol and shall not be used. { 0 | 1 < Bandwidth_TDD : bit (3) > } ; |
< 3G MEASUREMENT Parameters Description struct >::= < Qsearch_I : bit (4) > 0 | 1 < FDD_Qoffset : bit (4) > — FDD Parameters |
Table 10.5.2.33a.2: SI 2ter Rest Octets information element details
SI2ter_MP_CHANGE_MARK (1 bit field), SI2ter Rest Octet Measurement Parameter Change Mark. |
SI2ter_3G_CHANGE_MARK (1 bit field), SI2ter Rest Octet 3G Change Mark. |
SI2ter_INDEX (3 bit field) and SI2ter_COUNT (3 bit field) |
UTRAN FDD Description FDD_ARFCN (14 bit field) |
When a frequency is included with no scrambling code information, this indicates all the scrambling codes. |
Bandwidth_FDD (3 bit field) |
UTRAN TDD Description TDD_ARFCN (14 bit field) |
When a frequency is included with no Cell Parameter information, this indicates all the Cell Parameter values. |
3G Measurement Parameters Description: Bandwidth_TDD (3 bit field) |
10.5.2.33b SI 2quater Rest Octets
The SI 2quater Rest Octets information element contains neighbour cell lists for UTRAN cells. For cell reselection, it is used with the SI 2ter Rest Octets information to build the 3G Cell Reselection list, see sub-clause 3.4.1.2.1.7.
The SI 2quater Rest Octets information element is a type 5 information element with 20 octet length.
Table 10.5.2.33b.1: SI2quater message content
< SI2quater Rest Octets > ::= < BA_IND : bit (1) > < 3G_BA_IND : bit (1) > < MP_CHANGE_MARK : bit (1) > < SI2quater_INDEX : bit (4) > < SI2quater_COUNT : bit (4) > { 0 | 1 < Measurement_Parameters Description : < Measurement Parameters Description struct >> } { 0 | 1 < GPRS_Real Time Difference Description : < GPRS_Real Time Difference Description struct >> } { 0 | 1 < GPRS_BSIC Description : GPRS_BSIC Description struct > } { 0 | 1 < GPRS_REPORT PRIORITY Description : < GPRS_REPORT_PRIORITY Description struct >> } { 0 | 1 < GPRS_MEASUREMENT_Parameters Description : < GPRS_MEASUREMENT Parameters Description struct >> } { 0 | 1 < NC Measurement Parameters : < NC Measurement Parameters struct >> } { 0 | 1 < extension length : bit (8) > < spare bit (val(extension length)+1) > } – used for future extensions of the 2G parameters { 0 | 1 < 3G Neighbour Cell Description : < 3G Neighbour Cell Description struct >> } { 0 | 1 < 3G Measurement Parameters Description : < 3G Measurement Parameters Description struct >> } { 0 | 1 < GPRS_3G_MEASUREMENT Parameters Description : < GPRS_3G MEASUREMENT Parameters Description struct >> } < spare padding > ; |
< 3G Neighbour Cell Description struct > ::= { 0 | 1 < Index_Start_3G : bit (7) } { 0 | 1 < Absolute_Index_Start_EMR : bit (7) } { 0 | 1 < UTRAN FDD Description : UTRAN FDD Description struct >> } { 0 | 1 < UTRAN TDD Description : UTRAN TDD Description struct >> } ; |
< UTRAN FDD Description struct > ::= { 0 | 1 < Bandwidth_FDD : bit (3) } { 1 < Repeated UTRAN FDD Neighbour Cells : Repeated UTRAN FDD Neighbour Cells struct >> } ** 0 ; |
< Repeated UTRAN FDD Neighbour Cells struct > ::= — the protocol and shall not be used. |
< UTRAN TDD Description struct > ::= { 0 | 1 < Bandwidth_TDD : bit (3) } { 1 < Repeated UTRAN TDD Neighbour Cells : Repeated UTRAN TDD Neighbour Cells struct >> } ** 0 ; |
< Repeated UTRAN TDD Neighbour Cells struct > ::= — the protocol and shall not be used. |
<MEASUREMENT PARAMETERS Description Struct > ::= < REPORT_TYPE : bit > |
< 3G MEASUREMENT PARAMETERS Description struct > ::= < Qsearch_I : bit (4) > |
< GPRS Real Time Difference Description struct > ::= { 0 | 1 { 0 | 1 < BA_Index_Start_RTD : bit (5) > } –default value=0 |
< RTD6 Struct > ::= |
< RTD12 Struct > ::= |
< GPRS BSIC Description struct > ::= |
< GPRS REPORT PRIORITY Description struct > ::= |
< GPRS MEASUREMENT PARAMETERS Description struct > ::= { 0 | 1 < 900_REPORTING_OFFSET : bit (3) > { 0 | 1 < 1800_REPORTING_OFFSET : bit (3) > { 0 | 1 < 400_REPORTING_OFFSET : bit (3) > { 0 | 1 < 1900_REPORTING_OFFSET : bit (3) > { 0 | 1 < 850_REPORTING_OFFSET : bit (3) > |
< GPRS 3G MEASUREMENT PARAMETERS Description struct > ::= < Qsearch_P : bit (4) > < 3G_SEARCH_PRIO : bit > { 0 | 1 < FDD_REP_QUANT : bit > — FDD Parameters < FDD_MULTIRAT_REPORTING : bit (2) > } { 0 | 1 < FDD_REPORTING_OFFSET : bit (3) > < FDD_REPORTING_THRESHOLD : bit (3) > } { 0 | 1 < TDD_MULTIRAT_REPORTING : bit (2) > } — TDD Parameters { 0 | 1 < TDD_REPORTING_OFFSET : bit (3) > < TDD_REPORTING_THRESHOLD : bit (3) > } ; |
< NC Measurement Parameters struct > ::= < NETWORK_CONTROL_ORDER : bit (2) > { 0 | 1 < NC_ NON_DRX_PERIOD : bit (3) > < NC_REPORTING_PERIOD_I : bit (3) > < NC_REPORTING_PERIOD_T : bit (3) > } ; |
Table 10.5.2.33b.2: SI2quater message information
BA_IND (1 bit), BCCH allocation sequence number indication. |
3G_BA_IND (1 bit), 3G BCCH allocation sequence number indication. |
MP_CHANGE_MARK (1 bit ) |
SI2quater_INDEX (4 bit field) SI2quater_COUNT (4 bit field) This field is coded as the binary representation of the SI2quater_INDEX for the last (highest indexed) individual SI2quater message. |
3G Neighbour Cell Description: The building of the 3G Neighbour Cell list and the ordering of indices within each Radio Access Technology is described in sub-clause 3.4.1.2.1.1, ‘Deriving the 3G Neighbour Cell list from the 3G Neighbour Cell Description’. |
Index_Start_3G (7 bit) |
Absolute_Index_Start_EMR (7 bit) |
UTRAN FDD DESCRIPTION FDD_CELL_INFORMATION Field (p bit field) If parameter n in table 9.1.54.1a. is equal to 31, this indicates that the corresponding UARFCN shall be included in the 3G Cell Reselection list (see sub-clause 3.4.1.2.1.7); no index shall be allocated in the 3G Neighbour Cell list. |
UTRAN TDD DESCRIPTION If parameter m in table 9.1.54.1b. is equal to 31, this indicates that the corresponding UARFCN shall be included in the 3G Cell Reselection list (see sub-clause 3.4.1.2.1.7); no index shall be allocated in the 3G Neighbour Cell list. |
UTRAN FDD DESCRIPTION |
UTRAN TDD DESCRIPTION |
MEASUREMENT PARAMETERS Description |
3G MEASUREMENT PARAMETERS Description |
GPRS PRIORITY Description REP_PRIORITY bit: This information is used for GPRS Enhanced (NC) Reporting when the cell has no PBCCH allocated, see 3GPP TS 04.60 sub-clause 5.6.3.5 ("Report Priority Description"). The use of these bits is similar to the PRIORITY description, see sub-clause 3.4.1.2.1.5("’Report Priority Description"). |
GPRS BSIC Description This information is used for GPRS Enhanced (NC) Measurement reporting when the cell has no PBCCH allocated, see 3GPP TS 04.60 sub-clause 5.6.3.2 ("Deriving the GSM Neighbour Cell list from the BSICs and frequency list"). The use of this information is similar to the BSIC Description, see sub-clause 3.4.1.2.1.2 ("Deriving the GSM Neighbour Cell list from the BSICs and the BA (list)"). |
GPRS Real Time Difference Description This information is used for GPRS neighbour cell measurement when the cell has no PBCCH allocated, see 3GPP TS 04.60 sub-clause 5.6.3.4 ("GPRS Real Time Differences"). The use of this information is similar to the Real Time Difference Description, see sub-clause 3.4.1.2.1.4 ("Real Time Differences"). |
GPRS MEASUREMENT PARAMETERS Description The fields of this Description are defined in 3GPP TS 05.08. |
3G MEASUREMENT PARAMETERS Description This information is used for GPRS neighbour cell measurement when the cell has no PBCCH allocated, see 3GPP TS 04.60 sub-clause 5.6.3.6 ("GPRS Measurement Parameters and GPRS 3G Measurement Parameters"). The fields of this Description are defined in 3GPP TS 05.08. |
NC Measurement Parameters struct Information in this structure is used when the cell has no PBCCH allocated, for (NC) measurement reporting. See 3GPP TS 04.60 sub-clause 5.6.1 ("Network Control (NC) measurement reporting"). Coding of the fields is defined in 3GPP TS 04.60, sub-clause 11.2.23 ("PACKET SYSTEM INFORMATION TYPE5"). |
10.5.2.34 SI 3 Rest Octets
The SI 3 Rest Octets information element is coded according to the syntax specified below and described in tables 10.5.2.34.1, 10.5.2.34.2 and 10.5.2.35.1 (see sub-clause 10.5.2.35).
The SI 3 Rest Octets information element is a type 5 information element with 4 octets length.
Table 10.5.2.34.1: SI 3 Rest Octets information element
<SI3 Rest Octet> ::= <Optional selection parameters> <Optional Power offset> <System Information 2ter Indicator> <Early Classmark Sending Control> <Scheduling if and where> { L | H <GPRS Indicator> } <3G Early Classmark Sending Restriction> { L | H < SI2quater Indicator : < SI2quater Indicator struct > > } <spare padding> ; |
<Optional Selection Parameters> ::= L | H <Selection Parameters>; |
<Selection Parameters> ::= <CBQ: bit (1)> <CELL_RESELECT_OFFSET: bit (6)> <TEMPORARY_OFFSET: bit (3)> <PENALTY_TIME: bit (5)>; |
<Optional Power Offset> ::= L | H <Power Offset: bit (2)>; |
<System Information 2ter Indicator> ::= L | H; |
<Early Classmark Sending Control> ::= L | H; |
<Scheduling if and where>::= L | H <WHERE: bit (3)>; |
<GPRS Indicator> ::= < RA COLOUR : bit (3) > < SI13 POSITION : bit >; |
<3G Early Classmark Sending Restriction>::= L | H; |
< SI2quater Indicator struct > ::= |
Table 10.5.2.34.2: SI 3 Rest Octets information element details
CBQ, CELL_BAR_QUALIFY (1 bit field) |
CELL_RESELECT_OFFSET (6 bit field) |
TEMPORARY_OFFSET (3 bit field) |
PENALTY_TIME (5 bit field) |
Power Offset (2 bit field) If this parameter is transmitted on a BCCH carrier within the DCS 1800 band, its meaning shall be described below: Value Meaning 0 0 0 dB power offset 0 1 2 dB power offset 1 0 4 dB power offset 1 1 6 dB power offset If this parameter is transmitted on a BCCH carrier outside the DCS 1800 band, then all bit positions shall be treated as spare. |
System Information 2ter Indicator (1 bit field) L SYSTEM INFORMATION TYPE 2ter message is not available |
Early Classmark Sending Control (1 bit field) L Early Classmark Sending is forbidden |
WHERE (3 bit field) If the WHERE field is contained in the information element, this indicates that BCCH scheduling information is sent in SYSTEM INFORMATION TYPE 9 on the BCCH and that SYSTEM INFORMATION TYPE 9 messages are sent in the blocks of the BCCH norm for which ((FN DIV 51) mod (8) = 4 AND (((FN DIV 51) DIV 8) mod (n+1))= 0), where n is the value encoded in binary in WHERE. |
GPRS Indicator |
RA COLOUR (3 bit field) |
SI13_POSITION (1 bit field) 0 SYSTEM INFORMATION TYPE 13 message is sent on BCCH Norm; |
3G Early Classmark Sending Restriction (1 bit field) L Neither UTRAN nor cdma2000 classmark change message shall be sent with the Early classmark sending |
SI2quater Indicator struct The presence of this field indicates that the SI2quater message is broadcast. SI2quater_POSITION (1 bit field) 0 SYSTEM INFORMATION TYPE 2 quater message is sent on BCCH Norm |
10.5.2.35 SI 4 Rest Octets
The SI 4 Rest Octets information element includes parameters which are used by the mobile station for cell selection and reselection purposes. It may also include the POWER OFFSET parameter used by DCS 1800 Class 3 MS.
Its content is described in table 10.5.2.35a.1.
NOTE: In the future evolution of this standard the values 64h and 72h shall not be used as values of the first octet when this information element is used in the SYSTEM INFORMATION TYPE 4 message. This will prevent mobile stations misinterpreting this information as the CBCH IEIs.
The SI 4 Rest Octets information element is a type 5 information element with 0 to 10 octets length.
Table 10.5.2.35.1: SI 4 Rest Octets information element content
<SI4 Rest Octets> ::= { <SI4 Rest Octets_O> {L <Break indicator> | H <SI Rest Octets_S>} <spare padding> } — truncation allowed, bits ‘L’ assumed; |
<SI4 Rest Octets_O> ::= { <Optional selection parameters> <Optional Power offset> {L | H < GPRS Indicator >} } — truncation allowed, bits ‘L’ assumed ; |
<SI4 Rest Octets_S> ::= {L | H <LSA Parameters>} {L | H <Cell Identity : bit(16)>} {L | H <LSA ID information>} ; |
<Break Indicator> : := L | H ; |
<SI7 Rest Octets> ::= <SI4 Rest Octets_O><SI4 Rest Octets_S> |<SI4 Rest Octets_S> ; |
<SI8 Rest Octets> ::= <SI4 Rest Octets_O><SI4 Rest Octets_S> |<SI4 Rest Octets_S> ; |
<Optional Selection Parameters> ::= L | H <Selection Parameters> ; |
<Selection Parameters> ::= <CBQ : bit (1)> <CELL_RESELECT_OFFSET : bit (6)> <TEMPORARY_OFFSET : bit (3)> < PENALTY_TIME : bit (5)> ; |
<Optional Power Offset> ::= L | H <Power Offset : bit(2)> ; |
<GPRS Indicator> ::= < RA COLOUR : bit (3) > |
<LSA Parameters> ::= <PRIO_THR : bit (3)> <LSA_OFFSET : bit (3)> {0 | 1 <MCC : bit (12)> <MNC : bit (12)>} ; |
<LSA ID information> ::= <LSA identity> {0 | 1 <LSA ID information>} ; |
<LSA identity> : := {0 <LSA_ID : bit (24)> |1 <ShortLSA_ID : bit (10)>} ; If "ACS " in the System information type 4 message is set to "1" then the SI 7 and SI 8 rest octets consists of "SI4 Rest Octets_O" and "SI4 Rest Octets_S", otherwise of only "SI4 Rest Octets_S". |
Table 10.5.2.35.2: SI 4 Rest Octets information element details
CBQ, CELL_BAR_QUALIFY (1 bit field) |
CELL_RESELECT_OFFSET (6 bit field) |
TEMPORARY_OFFSET (3 bit field) |
PENALTY_TIME (5 bit field) |
POWER OFFSET (2 bit field) If this parameter is transmitted on a BCCH carrier within the DCS 1800 band, its meaning shall be described below: Value Meaning 0 0 0 dB power offset 0 1 2 dB power offset 1 0 4 dB power offset 1 1 6 dB power offset If this parameter is transmitted on a BCCH carrier outside the DCS 1800 band, then all bit positions shall be treated as spare. |
GPRS Indicator |
RA COLOUR (3 bit field) |
SI13_POSITION (1 bit field) 0 SYSTEM INFORMATION TYPE 13 message is sent on BCCH Norm; |
Break Indicator L Additional parameters are not sent in SYSTEM INFORMATION TYPE 7 and 8. |
PRIO_THR (3 bit field) |
LSA_OFFSET (3 bit field) |
MCC and MNC (24 bit field) |
Cell Identity (16 bit field) |
LSA_ID (24 bit field) |
Short LSA_ID (10 bit field) |
10.5.2.35a SI 6 Rest Octets
The SI 6 Rest Octet information element may contain information concerning the paging, notification channels, VBS and VGCS services of the cell.
The SI 6 Rest Octets information element is a type 5 information element with 7 octets length.
The value part is as shown below:
Table 10.5.2.35a.1: SI 6 Rest Octets information element content
<SI6 rest octets> ::= L I H <PCH and NCH info>} L I H <VBS/VGCS options : bit(2)>} < DTM_support : bit == L > I < DTM_support : bit == H > < RAC : bit (8) > < MAX_LAPDm : bit (3) > } < Band indicator > { L | H < GPRS_MS_TXPWR_MAX_CCH : bit (5) > } <implicit spare >; |
<PCH and NCH info> ::= <Paging channel restructuring> <NLN(SACCH) : bit(2)> {0 I 1 <Call priority : bit (3)>} <NLN status : bit >; |
<paging channel restructuring> ::= 1| — paging channel is restructured 0 — paging channel is not restructured |
<VBS/VGCS options> ::= <inband notifications> <inband pagings>; |
<inband notifications>::= 0| — the network does not provide notification on FACCH so that the mobile should inspect the NCH for notifications 1 — the mobile shall be notified on incoming high priority VBS/VGCS calls through NOTIFICATION/FACCH, the mobile need not to inspect the NCH |
<inband pagings>::= 0| — the network does not provide paging information on FACCH so that the mobile should inspect the PCH for pagings 1 — the mobile shall be notified on incoming high priority point-to-point calls through NOTIFICATION/FACCH, the mobile need not to inspect the PCH |
< Band indicator > ::= < BAND_INDICATOR : bit == L > — ARFCN indicates 1800 band | < BAND_INDICATOR : bit == H > ; — ARFCN indicates 1900 band |
Table 10.5.2.35a.2: SI 6 Rest Octets information element details
Attributes, field contents: 1. For <NLN(SACCH): bit(2)>: see 10.5.2.23. 2. For <call priority>: see 10.5.2.23. Indication of the highest priority associated with VBS/VGCS calls in a cell. |
DTM_support (1 bit field) Bit 0 |
RAC (8 bit field) |
MAX_LAPDm (3 bit field) Bit 2 1 0 |
BAND_INDICATOR (1 bit field) The band indicator for 1800 and 1900 associates the ARFCN channel numbers to the DCS 1800 respectively to the PCS 1900 band, see 3GPP TS 05.05. |
GPRS_MS_TXPWR_MAX_CCH (5 bits field) The GPRS_MS_TXPWR_MAX_CCH field is coded as the binary representation of the "power control level" in 3GPP TS 05.05 corresponding to the maximum TX power level the MS shall use for packet resources while in dual transfer mode. This value shall be used by the Mobile Station according to 3GPP TS 05.08. Range: 0 to 31. |
10.5.2.36 SI 7 Rest Octets
The SI 7 Rest Octets information element includes parameters which are used by the mobile station for cell selection and reselection purposes. It may also include the POWER OFFSET parameter used by a DCS 1800 Class 3 MS.
The SI 7 Rest Octets information element is a type 5 information element with 20 octets length.
The SI 7 Rest Octets information element is coded as the SI 4 Rest Octets. Its contents is described in table 10.5.2.35.1 and 10.5.2.35.2.
10.5.2.37 SI 8 Rest Octets
The SI 8 Rest Octets information element includes parameters which are used by the mobile station for cell selection and reselection purposes. It may also include the POWER OFFSET parameter used by a DCS 1800 Class 3 MS.
The SI 8 Rest Octets information element is a type 5 information element with 20 octets length.
The SI 8 Rest Octets information element is coded as the SI 4 Rest Octets. Its contents is described in table 10.5.2.35a.1 and 10.5.74.
10.5.2.37a SI 9 Rest Octets
The SI 9 Rest Octets information element contains information about scheduling of some or all of the information on the BCCH.
The SI 9 Rest Octets information element is a type 5 information element with 17 octets length.
Table 10.5.2.37a.1: SI 9 Rest Octets information element content
<SI9 rest octets> ::= {L | H <Scheduling info>} <spare padding>; |
<Scheduling info> ::= <Info type> <Positions> {0 | 1 <Scheduling info>}; |
<Info type> ::= 0 <Info_type_4: bit (4)> | 1 0 <Info_type_5: bit (5)> | 1 1 <Info_type_6: bit6)>; |
<Positions> ::= <Position> {0 | 1 <Position>} |
<Position> ::= <Modulus: bit(4)> <Relative_position: <bit>> –length depends on modulus <Bcch_type: bit(1)>; |
Table 10.5.2.37a.2: SI 9 rest octet information element details
Attributes The scheduling info indicates one or more information types (in info type) together with their positions. Here, a position specifies at which relative position P (specified in relative_position) modulo a position modulus M (specified in modulus) messages of the given information type are sent, on the BCCH norm or BCCH ext (see 3GPP TS 05.02) as indicated in bcch_type. Precisely, messages of the given information type are sent in the multiframes for which ((frame number) DIV 51) mod (M)) = P. If the position modulus M equals 0, the information type is not sent. |
Field contents The fields of the SI 9 Rest Octets information element are coded as shown in table 10.5.37a.1. |
Info_type_4_(4 bits) This field contains a binary encoded non-negative integer number assigned to a type of information sent on the BCCH. All values indicate unknown, unnecessary information and are reserved for future use. |
Info_type_5 (5 bits) This field contains a binary encoded non-negative integer number assigned to a type of information sent on the BCCH. All values except those defined below indicate unknown, unnecessary information and are reserved for future use. Info_type_5: 0 0000 System Information type 1 0 0001 System Information type 2 0 0010 System Information type 2bis 0 0011 System Information type 2ter 0 0100 System Information type 3 0 0101 System Information type 4 0 0110 System Information type 7 0 0111 System Information type 8 0 1000 System Information type 9 0 1001 System Information type 13 0 1011 System Information type 16 0 1100 System Information type 17 0 1101 System Information type 18 0 1110 System Information type 19 0 1111 System Information type 20 |
Info_type_6_(6 bits) This field contains a binary encoded non-negative integer number assigned to a type of information sent on the BCCH. All values indicate unknown, unnecessary information and are reserved for future use. |
modulus (4 bits) This field encodes the position modulus, according to the following encoding method. Let N be the integer encoded in binary in the modulus field; the position modulus is then defined as follows : If N=0, the position modulus is 0, |
relative position (0 bits if the non-negative integer n contained in the modulus field is 0; n+1 bits, if the non-negative integer N encoded in the modulus field is > 0. This field contains the N+1 bit binary encoding of a non-negative integer number < 2N+1. |
bcch_type (1 bit) 0 BCCH norm (as defined in 3GPP TS 05.08) |
10.5.2.37b SI 13 Rest Octets
The SI 13 Rest Octets information element is coded according to the syntax specified below and described in table 10.5.2.37b.1.
The SI 13 Rest Octets information element is a type 5 information element with 20 octets length.
Table 10.5.2.37b.1: SI 13 Rest Octets information element content
< SI 13 Rest Octets > ::= { L | H < BCCH_CHANGE_MARK : bit (3) > < SI_CHANGE_FIELD : bit (4) > { 0 | 1 < SI13_CHANGE_MARK : bit (2) > < GPRS Mobile Allocation : GPRS Mobile Allocation IE > } — Defined in 3GPP TS 04.60 { 0 — PBCCH not present in cell : < RAC : bit (8) > < SPGC_CCCH_SUP : bit > < PRIORITY_ACCESS_THR : bit (3) > < NETWORK_CONTROL_ORDER : bit (2) > < GPRS Cell Options : GPRS Cell Options IE > — Defined in 3GPP TS 04.60 < GPRS Power Control Parameters : GPRS Power Control Parameters struct > | 1 — PBCCH present in cell : < PSI1_REPEAT_PERIOD : bit (4) > < PBCCH Description : PBCCH Description struct > } { null | L — Receiver compatible with ealier release | H — Additions in release 99 : < SGSNR : bit > } } < spare padding > ; |
< GPRS Power Control Parameters struct > ::= < ALPHA : bit (4) > < T_AVG_W : bit (5) > < T_AVG_T : bit (5) > < PC_MEAS_CHAN : bit > < N_AVG_I : bit (4) >; |
< PBCCH Description struct > ::= <Pb : bit (4) < TSC : bit (3) > < TN : bit (3) > { 00 — BCCH carrier | 01 < ARFCN : bit (10) > | 1 < MAIO : bit (6) >} ; |
Table 10.5.2.37b.2: SI 13 Rest Octets information element
BCCH_CHANGE_MARK (3 bit field) |
SI_CHANGE_FIELD (4 bit field) 0 Update of unspecified SI message or SI messages; All other values shall be interpreted as ‘update of unknown SI message type’. |
SI13_CHANGE_MARK (2 bit field) |
GPRS Mobile Allocation (information element) |
RAC (8 bit field) |
SPGC_CCCH_SUP (bit field) 0 SPLIT_PG_CYCLE is not supported on CCCH in this cell; |
The PRIORITY_ACCESS_THR field (3 bit) is the binary representation of the parameter PRIORITY_ACCESS_THR: 0 0 0 packet access is not allowed in the cell; |
The NETWORK_CONTROL_ORDER field (2 bit) is the binary representation of the parameter NETWORK_CONTROL_ORDER, see 3GPP TS 04.60: 0 0 NC0: MS controlled cell re-selection, no measurement reporting. |
GPRS Cell Options (information element) |
PSI1_REPEAT_PERIOD (4 bit field) 0000 PSI1 repeat period = 1 multiframe |
GPRS Power Control Parameters struct The ALPHA field (4 bit) is the binary representation of the parameter for MS output power control in units of 0.1, see 3GPP TS 05.08: Range: 0 to 10. Values greater than 10 shall be interpreted as 10 by the mobile station. The T_AVG_W field (5 bit) is the binary representation of the parameter TAVG_W for MS output power control, see 3GPP TS 05.08: Range: 0 to 25. Values greater than 25 shall be interpreted as 25 by the mobile station. The T_AVG_T field (5 bit) is the binary representation of the parameter TAVG_T for MS output power control, see 3GPP TS 05.08: Range: 0 to 25. Values greater than 25 shall be interpreted as 25 by the mobile station. The PC_MEAS_CHAN field (bit) indicates the type of channel which shall be used for downlink measurements for power control: 0 BCCH; The N_AVG_I field (4 bit) is the binary representation of the parameter NAVG_I for MS output power control, see 3GPP TS 05.08: Range: 0 to 15. |
PBCCH Description struct Pb (4bit) (for encoding and description see the Global Power Control Parameters IE) The TSC field (3 bit) is the binary representation of the training sequence code used for PBCCH and PCCCHs. Range: 0 to 7. The TN field (3 bit) is the binary representation of the timeslot number for the PBCCH and the corresponding PCCCH. Range: 0 to 7. The ARFCN field (10 bit) is the binary representation of the absolute RF channel number. Range: 0 to 1023. The MAIO field (6 bit) is the binary representation of the mobile allocation index offset. Range: 0 to 63. SGSNR, SGSN Release (bit field) 0 SGSN is Release ’98 or older |
10.5.2.37c (void)
10.5.2.37d (void)
10.5.2.37e SI 16 Rest Octets
The SI 16 Rest Octets information element includes parameters which are used by the mobile station for cell selection and reselection purposes.
The SI 16 Rest Octets information element is coded according to the syntax specified below. Its contents is described in table 10.5.2.37c.1.
The SI 16 Rest Octets information element is a type 5 information element with 20 octets length.
Table 10.5.2.37e.1: SI 16 Rest Octets information element
<SI16 Rest Octets> ::= {L | H <LSA Parameters>} <spare padding> ; |
<SI17 Rest Octets> ::= < SI16 Rest Octets> ; |
<LSA Parameters> ::= <PRIO_THR : bit (3)> <LSA_OFFSET : bit (3)> {0 | 1 <MCC : bit (12)> <MNC : bit (12)>} <LSA ID information>; |
<LSA ID information> ::= <LSA identity> {0 | 1 <LSA ID information>} ; |
<LSA identity> : := {0 <LSA_ID : bit (24)> |1 <ShortLSA_ID : bit (10)>} ; |
Table 10.5.2.37e.2: SI 16 Rest Octets information element details
PRIO_THR (3 bit field) The PRIO_THR field is a signal threshold used by the mobile station to determine whether prioritised cell re-selection shall apply. The use and coding of this parameters is defined in 3GPP TS 05.08. |
LSA_OFFSET (3 bit field) The LSA_OFFSET field applies an offset for LSA reselection between cells with same LSA priorities. The use and coding of this parameters is defined in 3GPP TS 05.08. |
MCC and MNC (24 bit field) If the escape PLMN is broadcast in SI3 and SI4 the cell is used for SoLSA exclusive access and the MCC and MNC field shall be included. The MS shall then for all purposes use the MCC and MNC values received in the LSA Parameters instead of the ones received in the Location Area information element in SI3 and 4, eg when deriving the PLMN identity, the Location Area Identity and Cell Global Identity broadcast by the cell. The MCC and MNC value field is coded as specified in Figure 10.5.33GPP TS 04.18 and Table 10.5.3. |
LSA_ID (24 bit field) The purpose of the LSA_ID field is to identify a LSA. The LSA ID value field is coded as specified in 3GPP TS 23.003. |
Short LSA_ID (10 bit field) The purpose of the Short LSA_ID field is to identify a LSA. The LSA ID defined by the Short LSA_ID is a LSA_ID as specified in 3GPP TS 03.03 with bit 0 set to "0" bit 1 to 10 set to the value of the Short LSA_ID field (LSB in bit 1, MSB in bit 10) and bit 11 to 23 set to "0". |
10.5.2.37f SI 17 Rest Octets
The SI 17 Rest Octets information element includes parameters, which are used by the mobile station for cell selection and reselection purposes.
The SI 17 Rest Octets information element is a type 5 information element with 20 octets length.
The SI 17 Rest Octets information element is coded as the SI 16 Rest Octets. Its contents is described in tables 10.5.2.37e.1 and 10.5.2.37e.2.
10.5.2.37g SI 19 Rest Octets
The SI 19 Rest Octets information element contains information for cell re-selection to COMPACT channels.
The SI 19 Rest Octets information element is a type 5 information element with 20 octets length.
The value part is coded as shown below.
Table 10.5.2.37g.1: SI 19 Rest Octets information element
< SI 19 Rest Octets > ::= < SI19_CHANGE_MARK : bit (2) > < SI19_INDEX : bit (3) > < SI19_LAST : bit (1) > < COMPACT Neighbour Cell Parameters : < COMPACT Neighbour Cell params struct > > < spare padding >; |
< COMPACT Neighbour Cell params struct > ::= { 1 < START_FREQUENCY : bit (10) > < COMPACT Cell selection params : COMPACT Cell Selection struct > < NR_OF_REMAINING_CELLS : bit (4) > < FREQ_DIFF_LENGTH : bit (3) > { < FREQUENCY_DIFF : bit (n) > < COMPACT Cell Selection struct > > } * val(NR_OF_REMAINING_CELLS } ** 0; |
< COMPACT Cell Selection struct > ::= { 0 <BCC : bit (3)> | 1 <BSIC : bit (6)> } < CELL_BARRED : bit (1) > 0 0 — The values ’01’, ’10’ and ’11’ were allocated in an — earlier version of the protocol and shall not be used. { < LA Different parameters : < LA Different struct > > } { 0 | 1 < MS_TXPWR_MAX_CCH : bit (5) > } { 0 | 1 < RXLEV ACCESS MIN : bit (6) > } { 0 | 1 < CELL_RESELECT_OFFSET : bit (6) > } { 0 | 1 < TEMPORARY_OFFSET: bit (3) < PENALTY_TIME : bit (5) > } { 0 | 1 < TIME_GROUP : bit (2) > } { 0 | 1 < GUAR_CONSTANT_PWR_BLKS : bit (2) >} ; |
< LA Different struct > : := { 0 | 1 < CELL_RESELECT_HYSTERISIS : bit (3) > ; |
Table 10.5.2.37g.2: SI 19 Rest Octets information element details
SI19_CHANGE_MARK (2 bit field) The SI19 change mark field is changed each time information has been updated in any of the SI19 messages. A new value indicates that the mobile station shall re-read the information from all the SI19 messages. The coding of this field is network dependent. Range: 0-3. |
SI19_INDEX (3 bit field) The SI19_INDEX field is used to distinguish individual SI19 messages containing information about different neighbour cells. The field can take the binary representation of the values 0 to n, where n is the index of the last SI19 message. Range: 0-7. |
SI19_LAST (1 bit field) This field is coded as binary one if the SI19_INDEX in this message is the last SI19 message (i.e., it represents the highest SI19_INDEX being broadcast). If the field is coded as binary zero, then this is not the last SI19 message. Range: 0-1. |
START_FREQUENCY (10 bit field) The Start Frequency defines the ARFCN for the BCCH frequency of the first cell in the list. |
FREQ_DIFF_LENGTH (3 bit field) The Freq Diff length field specifies the number of bits to be used for the Frequency diff field in the current Frequency group. The field is coded according to the following table 3 2 1 |
NR_OF_REMAINING_CELLS (4 bit field) This field specifies the remaining number of cells that are defined in the frequency group. For each of them the parameters ‘Frequency diff’ and ‘Cell selection params’ will be repeated. Range 1-16. |
COMPACT Cell Selection params This struct contains information about COMPACT neighbour cells. The first field of the COMPACT Cell Selection struct, BSIC, defines the BSIC of the cell and then comes the field same RA as serving cell. Then follows none, some, or all of the fields MS_TXPWR_MAX_CCH, RXLEV ACCESS MIN, CELL_RESELECT_OFFSET, TEMPORARY_OFFSET, PENALTY_TIME, TIME_GROUP, GUAR_CONSTANT_PWR_BLKS. If fields are omitted, the values for these parameters are the same as for the preceding cell. |
FREQUENCY_DIFF ("Freq Diff length" bit field) The Frequency Diff field specifies the difference in ARFCN to the BCCH carrier in the next cell to be defined. Note that the difference can be zero if two specified cells use the same frequency. |
BSIC (6 bit field) The BSIC field is coded as the "Base Station Identity Code" defined in 3GPP TS 03.03. |
BCC (3 bit field) The BCC is specified by encoding its binary representation; it specifies the BSIC given by that BCC and the NCC of the BSIC specified by the previous occurrence of <BCC : bit(3)> or <BSIC : bit(6)>. |
CELL_BARRED (1 bit field) 0 The cell is not barred |
LA Different parameters If <LA Different struct> contains a < CELL_RESELECT_HYSTERISIS : bit (3)>, this means that the cell is to be considered by the mobile station to belong to a different location area and that for the cell, the cell reselect hysteresis specified in < CELL_RESELECT_HYSTERISIS : bit (3)> applies. If <LA Different struct> doesn’t contain a < CELL_RESELECT_HYSTERISIS : bit (3)>, this means that the cell is to be considered by the mobile station to belong to the same location area. For < CELL_RESELECT_HYSTERISIS : bit (3)>: see 10.5.2.4. For < MS_TXPWR_MAX_CCH : bit (5)>: see 10.5.2.4. For < RXLEV_ACCESS_MIN : bit (6)> see 10.5.2.4. For < CELL_RESELECT_OFFSET : bit (6)>: see 10.5.2.35. For < TEMPORARY_OFFSET : bit (3)>: see 10.5.2.35. For < PENALTY_TIME : bit (5)>: see 10.5.2.35. |
TIME_GROUP (2 bit field) The TIME_GROUP defines which time group (see 3GPP TS 05.02) the cell belongs to Bit |
GUAR_CONSTANT_PWR_BLKS (2 bit field) This field indicates the guaranteed number of constant power blocks in the neighbour cell. These are the blocks that the MS can use to perform neighbour cell measurements (see 3GPP TS 05.08). Note that there may be more CPBCCH blocks or allowed paging blocks in the neighbour cell than what is indicated in this field, but never less. Bit 2 1 Blocks at constant power 0 0 4 0 1 5 1 0 6 1 1 12 (i.e. BS_PAG_BLKS_RES = 0 in that cell) |
10.5.2.37h SI 18 Rest Octets
The SI 18 Rest Octets information element includes parameters for non-GSM networks.
The SI 18 Rest Octets information element is a type 5 information element and is 20 octets long.
Several Non-GSM information containers may be mapped into one instance of this information element, separated by a Non-GSM protocol discriminator. The last Non-GSM information container may be continued in a subsequent instance of this information element.
Table 10.5.2.37h.1: SI 18 Rest Octets information element
< SI 18 Rest Octets > ::= < SI18_CHANGE_MARK : bit (2) > < SI18_INDEX : bit (3) > < SI18_LAST : bit (1) > < spare bit > * 2 < Non-GSM Message : < Non-GSM Message struct > > ** — The Non-GSM Message struct is repeated until: — A) val(NR_OF_CONTAINER_OCTETS) = 0, or — B) the SI message is fully used < spare padding > ; |
< Non-GSM Message struct > ::= < Non-GSM Protocol Discriminator : bit(3) > < NR_OF_CONTAINER_OCTETS : bit(5) > { < CONTAINER : bit(8) > } * (val(NR_OF_CONTAINER_OCTETS)) ; |
Table 10.5.2.37h.2: SI 18 information element details
SI18_CHANGE_MARK (2 bit field) The SI18 change mark field is changed each time information has been updated in any of the SI18 messages. A new value indicates that the mobile station shall update the information from all the SI18 messages. The coding of this field is network dependent. Range: 0-3. |
SI18_INDEX (3 bit field) The SI18_INDEX field is used to distinguish individual SI18 messages. The field can take the binary representation of the values 0 to n, where n is the index of the last SI18 message. Range: 0-7. |
SI18_LAST (1 bit field) This field is coded as binary one if the SI18_INDEX in this message is the last instance of the SI18 messages (i.e., it represents the highest SI18_INDEX being broadcast). Otherwise, this field is coded as binary zero. Range: 0-1. |
Non-SM Protocol Discriminator (3 bit field) bit 3 2 1 0 0 1 TIA/EIA-136 All other values are reserved |
NR_OF_CONTAINER_OCTETS (5 bit field) Bit 5 4 3 2 1 0 0 0 0 0 Zero octets. There are no more NonGSM Messages embedded in this SI message. The Non‑GSM Protocol Discriminator field is spare (i.e., sent as ‘000’, not verified by the receiver). 0 0 0 0 1 CONTAINER length is 1 octet 0 0 0 1 0 CONTAINER length is 2 octets …. through … 1 0 0 1 0 CONTAINER length is 18 octets 1 1 1 1 1 The remaining portion of the SI message instance is used by the associated CONTAINER. The Non‑GSM message continues in a subsequent instance of the SI message, in the next CONTAINER with the same Non‑GSM Protocol Discriminator value as the current one. All other values are reserved. |
CONTAINER (8 bits) The concatenation of one or several CONTAINER octets forms the actual contents, specific to the non-GSM network soliciting the transmission of a SI18 message. |
NOTE: The format of SI 18 Rest Octets when 2 different Non-GSM messages are sent is exemplified below.
Bit | ||||||||
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
SI18 CHANGE MARK | SI18 INDEX | SI18 LAST | Spare bits | Octet 1 | ||||
Non-GSM Protocol Discriminator | NR_OF_CONTAINER_OCTETS | Octet 2 | ||||||
. | . | |||||||
Non-GSM Protocol Discriminator | NR_OF_CONTAINER_OCTETS | Octet M (optional) | ||||||
. | Octet M+1 | |||||||
. | . | |||||||
. . | Octet N-1 | |||||||
Octet N | ||||||||
Spare padding | (if present) |
10.5.2.37i SI 20 Rest Octets
The SI 20 Rest Octets information element includes parameters for non-GSM networks.
The SI 20 Rest Octets information element is a type 5 information element and is 20 octets long.
The SI 20 Rest Octets are defined as the SI 18 Rest Octets, see also sub-clause 10.5.2.37h.
10.5.2.38 Starting Time
The purpose of the Starting Time information element is to provide the start TDMA frame number, FN modulo 42432.
The Starting Time information element is coded as shown in figure 10.5.2.38.1 and table 10.5.2.38.1.
The Starting Time is a type 3 information element with 3 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Starting Time IEI | octet 1 | |||||||
T1′ | T3 | octet 2 | ||||||
T3 | octet 3 |
Figure 10.5.2.38.1: Starting Time information element
Table 10.5.2.38.1: Starting Time information element
T1′ (octet 2) The T1′ field is coded as the binary representation of (FN div 1326) mod 32. T3 (octet 2 and 3) The T3 field is coded as the binary representation of FN mod 51. Bit 3 of octet 2 is the most significant bit and bit 6 of octet 3 is the least significant bit. T2 (octet 3) The T2 field is coded as the binary representation of FN mod 26. |
NOTE: The frame number, FN modulo 42432 can be calculated as |
The starting time and the times mentioned above are with reference to the frame numbering in the concerned cell. They are given in units of frames (around 4.615 ms).
The Starting Time IE can encode only an interval of time of 42 432 frames, that is to say around 195.8 s. To remove any ambiguity, the specification for a reception at time T is that the encoded interval is (T-10808, T+31623). In rigorous terms, if we note ST the starting time:
– if 0 (ST-T) mod 42 432 31 623, the indicated time is the next time when FN mod 42 432 is equal to ST
– if 32 024 (ST-T) mod 42 432 42 431, the indicated time has already elapsed.
The reception time T is not specified here precisely. To allow room for various MS implementations, the limit between the two behaviours above may be anywhere within the interval defined by
– 31 624 (ST-T) mod 42 432 32 023.
10.5.2.39 Synchronization Indication
The purpose of Synchronization Indication information element is to indicate which type of handover is to be performed.
The Synchronization Indication information element is coded as shown in figure 10.5.2.39.1 and table 10.5.2.39.1.
The Synchronization Indication is a type 1 information element.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Synch. Indic. IEI | NCI | ROT | SI | octet 1 |
Figure 10.5.2.39.1: Synchronization Indication information element
Table 10.5.2.39.1: Synchronization Indication information element
ROT: Report Observed Time Difference (Octet1 bit 3) 0 Mobile Time Difference IE shall not be included in the HANDOVER COMPLETE message 1 Mobile Time Difference IE shall be included in the HANDOVER COMPLETE message SI: Synchronization indication (octet 1) Bit 0 1 Synchronized 1 0 Pre-synchronised 1 1 Pseudo-synchronised NCI: Normal cell indication (octet 1, bit 4) 0 Out of range timing advance is ignored 1 Out of range timing advance shall trigger a handover failure procedure. |
10.5.2.40 Timing Advance
The purpose of the Timing Advance information element is to provide the timing advance value.
The Timing Advance information element is coded as shown in figure 10.5.2.40.1 and table 10.5.2.40.1
The Timing Advance is a type 3 information element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Timing Advance IEI | octet 1 | |||||||
Timing advance value | octet 2 |
Figure 10.5.2.40.1: Timing Advance information element
Table 10.5.2.40.1: Timing Advance information element
Timing advance value (octet 2) The coding of the timing advance value field is the binary representation of the timing advance in bit periods; 1 bit period = 48/13 µs. For all the bands except GSM 400, the values 0 – 63 are valid TA values, and bit 7 and bit 8 are set to spare. For GSM 400, the values 0 to 219 are vaild TA values. The remaining values 220 to 255 decimal are reserved. |
10.5.2.41 Time Difference
The purpose of the Time Difference information element is to provide information about the synchronization difference between the time bases of two Base Stations. This type of information element is used in relation with the pseudo-synchronization scheme, see 3GPP TS 05.10.
The Time Difference information element is coded as shown in figure 10.5.2.41.1 and table 10.5.2.41.1.
The Time Difference information element is a type 4 information element with 3 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Time Difference IEI | octet 1 | |||||||
Length of Time Difference contents | octet 2 | |||||||
Time difference value | octet 3 |
Figure 10.5.2.41.1: Time Difference information element
Table 10.5.2.41.1: Time Difference information element
Time Difference value (octet 3) The coding of the time difference value field is the binary representation of time difference in half bit periods, modulo 256 half bit periods; 1/2 bit period = 24/13 µs. |
10.5.2.41a TLLI
The purpose of the TLLI information element is to provide the Temporary Logical Link Identifier.
The TLLI information element is coded as shown in figure 10.5.2.41a.1 and table 10.5.2.41a.1.
The TLLI is a type 3 information element with 5 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
TLLI IEI | octet 1 | |||||||
TLLI value | octet 2 | |||||||
TLLI value (contd) | octet 3 | |||||||
TLLI value (contd) | octet 4 | |||||||
TLLI value (contd) | octet 5 |
Figure 10.5.2.41a.1: TLLI information element
Table 10.5.2.41a.1: TLLI information element
TLLI value (octet 2, 3, 4 and 5) Bit 8 of octet 2 is the most significant bit and bit 1 of octet 5 is the least significant bit. The TLLI is encoded as a binary number with a length of 4 octets. TLLI is defined in 3GPP TS 23.003. |
10.5.2.42 TMSI/P-TMSI
The purpose of the TMSI/P-TMSI information element is to provide the Temporary Mobile Subscriber Identity for paging purposes.
The TMSI/P-TMSI information element is coded as shown in figure 10.5.2.42.1 and table 10.5.2.42.1.
The TMSI/P-TMSI is a type 3 information element with 5 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
TMSI/P-TMSI IEI | octet 1 | |||||||
TMSI/P-TMSI value | octet 2 | |||||||
TMSI/P-TMSI value (contd) | octet 3 | |||||||
TMSI/P-TMSI value (contd) | octet 4 | |||||||
TMSI/P-TMSI value (contd) | octet 5 |
Figure 10.5.2.42.1: TMSI/P-TMSI information element
Table 10.5.2.42.1: TMSI/P-TMSI information element
TMSI/P-TMSI value (octet 2, 3, 4 and 5) The coding of the TMSI/P-TMSI is left open for each administration according to 3GPP TS 23.003. The length is 4 octets. |
NOTE: For purposes other than paging the TMSI/P-TMSI should be provided using the mobile identity
information element.
10.5.2.42a VGCS target mode Indication
The VGCS target mode Indication information element is a type 3 information element with 3 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
VGCS target mode Indic. IEI | octet 1 | |||||||
Length of VGCS target mode Indic. | octet 2 | |||||||
Target mode | Group cipher key number | 1 | 1 | octet 3 |
Figure 10.5.2.42a.1: VGCS target mode Indication information element
Table 10.5.2.42a.1: VGCS target mode information element
Target mode (octet 3) Bit 8 7 0 0 dedicated mode 0 1 group transmit mode Other values are reserved for future use. Group cipher key number (octet 3) Bit 6 5 4 3 0 0 0 0 no ciphering 0 0 0 1 cipher key number 1 0 0 1 0 cipher key number 2 0 0 1 1 cipher key number 3 0 1 0 0 cipher key number 4 0 1 0 1 cipher key number 5 0 1 1 0 cipher key number 6 0 1 1 1 cipher key number 7 1 0 0 0 cipher key number 8 1 0 0 1 cipher key number 9 1 0 1 0 cipher key number A 1 0 1 1 cipher key number B 1 1 0 0 cipher key number C 1 1 0 1 cipher key number D 1 1 1 0 cipher key number E 1 1 1 1 cipher key number F |
10.5.2.43 Wait Indication
The purpose of the Wait Indication information element is to provide the time the mobile station shall wait before attempting another channel request.
The Wait Indication information element is coded as shown in figure 10.5.2.43.1 and table 10.5.2.43.1.
The Wait Indication is a type 3 information element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Wait Indication IEI | octet 1 | |||||||
T3122/T3142 timeout value | octet 2 |
Figure 10.5.2.43.1: Wait Indication information element
Table 10.5.2.43.1: Wait Indication information element
T3122/T3142 timeout value (octet 2) This field is coded as the binary representation of the T3122/T3142 timeout value in seconds. |
NOTE: The timeout value is used for T3122 when received in IMMEDIATE_ASSIGNMENT REJECT message for RR connection establishment. For GPRS MS the timeout value isused for T3142 when received in the IMMEDIATE ASSIGNMENT REJECT or DTM REJECT message for TBF establishment.
10.5.2.44 SI10 rest octets $(ASCI)$
The SI 10 rest octets information element contains information for cell re-selection in group receive mode.
The SI 10 Rest Octets information element is a type 5 information element with 20 octets length.
The value part is coded as shown below.
Table 10.5.2.44.1: SI 10 Rest Octets information element
<SI10 rest octets> ::= <BA ind : bit(1)> <neighbour information> ::= <first frequency: bit(5)> <cell info> <cell info> ::= <bsic : bit(6)> { H <cell parameters> | L }; <cell parameters> ::= <cell barred> | L <further cell info>; <cell barred> ::= H; <further cell info> ::= <la different> <la different> ::= { H <cell reselect hysteresis : bit(3)> | L }; <info field> ::= <next frequency>** L <differential cell info>; <next frequency> ::= H; <differential cell info> ::= { H <BCC : bit(3)> | L <bsic : bit(6)> } <diff cell pars> ::= <cell barred> | L <further diff cell info>; <further diff cell info> ::= <la different> |
Static and dynamic conditions:
1) Information from the last received neighbour cell description in SYSTEM INFORMATION TYPE 5/5bis/5ter is necessary for the mobile station to interpret <neighbour information>. If <BA ind> is different from the last received BA IND value indicated in SYSTEM INFORMATION TYPE 5/5bis/5ter, <neighbour information> cannot be interpreted by the mobile station.
2) If the correspondence between neighbour cell frequencies and sets of pairs (BSIC, cell information) cannot be established following the rules below, or if more than one set of such pairs corresponds to one neighbour cell frequency, the mobile station shall diagnose an imperative message part error.
Attributes, field contents:
1) <cell info> defines a BSIC given by <bsic : bit(6)>. It also defines cell information. If <cell parameters> is contained in <cell info>, this cell information is the cell information given by <cell parameters>; if <cell parameters> is not contained in <cell info>, this cell information is empty.
2) <differential cell info> defines a BSIC given by <bsic : bit(6)> or by <BCC : bit(3)>, see below. It also defines cell information. If <diff cell pars> is contained in <differential cell info>, this cell information is the cell information given by <diff cell pars>; if <diff cell pars> is not contained in <differential cell info>, this cell information is empty.
3) <cell parameters> either indicates a barred cell (by presence of <cell barred>)or specifies cell information given by <further cell info>.
4) Each occurrence of <diff cell pars> either indicates a barred cell (by presence of <cell barred>)or specifies cell information given by <further diff cell info>.
5) <further cell info> specifies cell information given by its components:
– <la different>
– <ms txpwr max cch : bit(5)>
– <rxlev access min : bit(6)>
– <cell reselect offset : bit(6)>
– <temporary offset : bit(3)>
– <penalty time : bit(5)>,
as defined below.
6) For each occurrence of <further diff cell info>, a cell information is defined. This information is given by <la different> and remaining cell information established as follows:
The remaining cell information defined for the first occurrence of <further diff cell info> consists of the cell information given by its actual components plus the cell information specified by <further cell info> corresponding to its missing components.
The remaining cell information defined for a later occurrence of <further diff cell info> consists of the cell information given by its actual components plus the remaining cell information corresponding to its missing components which is defined for the previous occurrence of <further diff cell info>.
Here, the:
"actual components" of an occurrence of <further diff cell info> denotes those parameters among
– <ms txpwr max cch : bit(5)>
– <rxlev access min : bit(6)>
– <cell reselect offset : bit(6)>
– <temporary offset : bit(3)>
– <penalty time : bit(5)>
which are present in that occurrence.
"missing components" of an occurrence of <differential cell info> denote those parameters among
– <ms txpwr max cch : bit(5)>
– <rxlev access min : bit(6)>
– <cell reselect offset : bit(6)>
– <temporary offset : bit(3)>
– <penalty time : bit(5)>
which are not present in that occurrence.
7) Each occurrence of <bsic : bit(6)> specifies a BSIC by encoding its binary representation. <BCC : bit(3)> specifies a BCC by encoding its binary representation; it specifies the BSIC given by that BCC and the NCC of the BSIC specified by the previous occurrence of <BCC : bit(3)> or <bsic : bit(6)>. All occurrences of <bsic: bit(6)> and <BCC : bit(3)> establish a list of BSIC.
8) <first frequency : bit(5)> is the 5 bit binary coding of an integer n with 0 n 31. It specifies a first frequency number n+1.
9) <SI10 rest octets> defines a correspondence between neighbour cell frequencies and sets of pairs (BSIC, cell information) defining the parameters for cell re-selection of any corresponding neighbour cell with BCCH on that frequency and having that BSIC:
Let a(1),…, a(n) be the list of neighbour cell frequencies, in the order determined by the mobile station. Let i be the first frequency number specified by <first frequency : bit(5)> (see above).
The first BSIC and the cell information specified by <cell info> build a pair belonging to the set corresponding to a(i).
If an m-th occurrence of <info field> is present (where m >=2), having established the correspondence of the (m‑1)-th BSIC to a neighbour frequency a(k), the m-th BSIC and following <differential cell info>
– belong to a(k), if <next frequency> is not present in the m-th occurrence of <info field>;
– belong to a((smod(k+t)), if <next frequency> is present exactly t times in the m-th occurrence of <info field>.
Here, for an integer j, smod(j) := ((j-1) mod n) + 1.
10) If <la different> contains a <cell reselect hysteresis : bit(3)>, this means that the cell is to be considered by the mobile station to belong to a different location area and that for the cell, the cell reselect hysteresis specified in <cell reselect hysteresis : bit(3)> applies.
If <la different> doesn’t contain a <cell reselect hysteresis : bit(3)>, this means that the cell is to be considered by the mobile station to belong to the same location area.
11) For <cell reselect hysteresis : bit(3)>: see sub-clause 10.5.2.4.
12) For <ms txpwr max cch : bit(5)>: see sub-clause 10.5.2.4.
13) For <rxlev access min : bit(6)> see sub-clause 10.5.2.4.
14) For <cell reselect offset : bit(6)>: see sub-clause 10.5.2.35.
15) For <temporary offset : bit(3)>: see sub-clause 10.5.2.35.
16) For <penalty time : bit(5)>: see sub-clause 10.5.2.35.
10.5.2.45 EXTENDED MEASUREMENT RESULTS
The purpose of the Extended Measurement Results information element is to provide the results of the measurements made by the mobile station on the carriers specified in the EXTENDED MEASUREMENT ORDER.
The Extended Measurement Results information element is coded as shown in figure 10.5.2.45.1 and table 10.5.2.45.1.
The Extended Measurement Results is a type 3 information element with 17 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Extended Measurement Results IEI | octet 1 | |||||||
SC | DTX | RXLEV carrier 0 | octet 2 | |||||
RXLEV carrier 1 | RXLEV | octet 3 | ||||||
RXLEV carrier 2 | RXLEV carrier 3 | octet 4 | ||||||
RXLEV | RXLEV carrier 4 | octet 5 | ||||||
RXLEV carrier 5 | RXLEV | octet 6 | ||||||
RXLEV carrier 6 | RXLEV carrier 7 | octet 7 | ||||||
RXLEV | RXLEV carrier 8 | octet 8 | ||||||
RXLEV carrier 9 | RXLEV | octet 9 | ||||||
RXLEV carrier 10 | RXLEV carrier 11 | octet 10 | ||||||
RXLEV | RXLEV carrier 12 | octet 11 | ||||||
RXLEV carrier 13 | RXLEV | octet 12 | ||||||
RXLEV carrier 14 | RXLEV carrier 15 | octet 13 | ||||||
RXLEV | RXLEV carrier 16 | octet 14 | ||||||
RXLEV carrier 17 | RXLEV | octet 15 | ||||||
RXLEV carrier 18 | RXLEV carrier 19 | octet 16 | ||||||
RXLEV | RXLEV carrier 20 | octet 17 |
Figure 10.5.2.45.1: Extended Measurement Results information element
Table 10.5.2.45.1: Extended Measurement Results information element details
SC USED (octet 2), indicates the value of the SEQ-CODE in the extended measurement frequency list information element used for defining the list of frequencies reported on. Range: 0 to 1. |
DTX USED (octet 2). Bit 7 |
RXLEV carrier ‘N’ (octets 2 to 17). Range: 0 to 63 If the EXTENDED MEASUREMENT ORDER message contains less than 21 carriers, the fields in the EXTENDED MEASUREMENT REPORT not referring to any specified carrier shall have RXLEV values set to zero. |
10.5.2.46 Extended Measurement Frequency List
The purpose of Extended Measurement Frequency List information element is to provide the absolute radio frequency channel numbers of carriers to measure signal strength on.
The Extended Measurement Frequency List information element is coded as the Cell Channel Description information element, as specified in sub-clause 10.5.2.1b, with the exception of bit 5 of octet 2. Figure 10.5.2.46.1 and table 10.5.2.46.1: contains the difference of specifications.
The Extended Measurement Frequency List information element is a type 3 information element with 17 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Extended Measurement Frequency List IEI | octet 1 | |||||||
Bit | Bit | 0 | SEQ- | Bit | Bit | Bit | Bit | octet 2 |
Bit | Bit | Bit | Bit | Bit | Bit | Bit | Bit | octet 3 |
Bit | Bit | Bit | Bit | Bit | Bit | Bit | Bit | octet 17 |
Figure 10.5.2.46.1: Extended Measurement Frequency List information element
Table 10.5.2.46.1: Extended Measurement Frequency List information element details
SEQ-CODE, Sequence code (octet 2, bit 5). Range 0 to 1. |
10.5.2.47 Suspension Cause
The purpose of the Suspension Cause information element is to provide the reason for the GPRS suspension.
The Suspension Cause information element is coded as shown in figure 10.5.2.47.1 and table 10.5.2.21aa.1.
The Suspension Cause is a type 3 information element with 2 octets length.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Suspension Cause IEI | octet 1 | |||||||
Suspension cause value | octet 2 |
Figure 10.5.2.47.1: Suspension Cause information element
Table 10.5.2.21aa.1: Suspension Cause information element
Suspension cause value (octet 2) Bits 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 Emergency call, mobile originating call or call re-establishment 0 0 0 0 0 0 0 1 Location Area Update 0 0 0 0 0 0 1 0 MO Short message service (note 1) 0 0 0 0 0 0 1 1 Other procedure which can be completed with an SDCCH 0 0 0 0 0 1 0 0 MO Voice broadcast or group call (note 2) 0 0 0 0 0 1 0 1 Mobile terminating CS connection 0 0 0 0 0 1 1 0 DTM not supported in the cell All other cause values shall be treated as 0000 0000 |
NOTE 1: As an option, cause value 0000 0011 may be used for an MO Short message service. NOTE 2: As an option, cause value 0000 0000 may be used for an MO Voice broadcast or group call. |
10.5.2.48 APDU ID
The APDU ID information element identifies the particular protocol and associated application for an APDU.
The APDU ID information element is coded as shown in figure 10.5.2.48.1 and table 10.5.2.48.1.
The APDU ID is a type 1 information element.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
APDU ID IEI | Protocol identifier | oktet 1 |
Figure 10.5.2.48.1: APDU ID information element
Table 10.5.2.48.1: APDU ID information element format
Protocol identifier (octet 1) Bits Protocol / Application 4 3 2 1 0 0 0 0 RRLP (3GPP TS 04.31)/ LCS 0 0 0 1 to reserved for future use 1 1 1 1 |
10.5.2.49 APDU Flags
The APDU Flags information element provides segmentation and control information for an associated APDU.
The APDU Flags information element is coded as shown in figure 10.5.2.49.1 and table 10.5.2.49.1.
The APDU Flags is a type 1 information element.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||
APDU Flags IEI | 0 | C/R | first | last | oktet 1 |
Figure 10.5.2.49.1: APDU Flags information element
Table 10.5.2.49.1: APDU Flags information element format
Last Segment (octet 1) bit 1 0 Last or only segment 1 Not last or only segment First Segment (octet 1) bit 2 0 First or only segment 1 Not first or only segment C/R (octet 1) If last seg. = 0, then: bit 3 0 Command or Final Response 1 Not Command or Final Response If last seg. = 1, then bit 3 is spare and set to 0 |
10.5.2.50 APDU Data
The purpose of the information element is to provide an APDU or APDU segment.
The APDU Data information element is coded as shown in figure 10.5.2.50.1 and table 10.5.2.50.1.
The APDU Data is a type 4 information element with minimum length of 2 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (3GPP TS 04.06).
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
APDU IEI | octet 1 | |||||||
Length of APDU contents | octet 2 | |||||||
APDU Information | octet 3-n |
Figure 10.5.2.50.1: APDU Data information element
Table 10.5.2.50.1: APDU Data information element format
APDU Information (octets 3-n) Contains an APDU message or APDU segment as follows: Protocol ID APDU Message or Segment ———– ——————- RRLP RRLP message in 3GPP TS 04.31 (1) NOTE 1: Messages are segmented on octet boundaries. Zero bits are used, where necessary, to pad out the last segment to an octet boundary. |
10.5.2.51 Handover To UTRAN Command
The purpose of Handover To UTRAN Command information element is to provide information to the mobile of handover to UTRAN.The Handover to UTRAN Command information element contains all information needed by the mobile for handover to UTRAN.
The Handover To UTRAN Command is a type 4 information element with length 3-n octets.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Handover to UTRAN Command IEI | octet 1 | |||||||
Length of Handover to UTRAN Command contents | octet 2 | |||||||
Handover to UTRAN Command value part | Octet 3-n |
Figure 10.5.2.51.1: Handover to UTRAN Command information element
The value part of the Handover To UTRAN Command IE is coded as defined in 3GPP TS 25.331.
10.5.2.52 Handover To cdma2000 Command
The purpose of Handover To cdma2000 Command information element is to provide information to the mobile of handover to cdma2000.The Handover to cdma2000 Command information element contains all information needed by the mobile for handover to cdma2000.
The Handover To cdma2000 Command IE is coded as follows:
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
Handover to cdma2000 Command IEI | octet 1 | |||||||
Length of cdma2000 command contents | octet 2 | |||||||
Handover to cdma2000 Command value part | octet 3-n |
Figure 10.5.2.52.1: Handover to cdma2000 Command information element
The MSG_TYPE of the cdma2000 message used for the intersystem handover shall be included in the first octet of the Handover to cdma2000 value part. It is specified in TIA/EIA/IS-2000-4-A and in TIA/EIA/IS-833. (E.g. MSG_TYPE::= {00010001} if Extended Handoff Direction Message (EHDM) is used, MSG_TYPE::= {00011111} if General Handoff Direction Message is used, etc.). The order of the bits in this octet representing is given by the following example. If MSG_TYPE::={00010001} (EHDM), the bit number 1 of ‘cdma2000 MSG_TYPE IEI’ shall be ‘0’, the bit number 2 shall be ‘0’, etc., and the bit number 8 shall be ‘1’, as illustrated below.
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | bit |
1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 |
The remaining octets in the Handover to cdma2000 value part shall be coded as the payload of the message used for the inter system handover, as specified in TIA/EIA/IS-2000.5-A and in TIA/EIA/IS-833. The bit ordering shall be similar to the case described above. The bit number 1 of ‘cdma2000 message payload’ shall be coded as the first bit of the first record of the message defined in TIA/EIA/IS-2000.5-A and in TIA/EIA/IS-833, reading the records defined in TIA/EIA/IS-2000.5-A and in TIA/EIA/IS-833 from left to right.
The Handover To cdma2000 Command is a type 4 information element with length 4 to n octets.
10.5.2.53 (void)
10.5.2.54 (void)
10.5.2.55 (void)
10.5.2.56 3G Target Cell
The purpose of the 3G Target Cell information element is to indicate to the MS the target 3G Cell.
The 3G Target Cell is a type 4 information element with a minimum length of 3 octets and a maximum length of 6 octets.
If the 3G Target Cell information element contains information on both 3G UTRAN FDD and 3G UTRAN TDD, the information element shall be ignored by the receiver.
Table 10.5.2.56.1: 3G Target Cell information element
< 3G Target Cell >::= < 0 0 0 1 0 0 1 1 > –type < LENGTH OF 3G TARGET CELL : bit (8) > — length following in octets { 0 | 1 < FDD-ARFCN : bit (14) > — 3G UTRAN FDD < Diversity : bit > { 0 | 1 < Bandwidth_FDD : bit (3) > } < SCRAMBLING_CODE : bit (9) > } { 0 | 1 < TDD-ARFCN : bit (14) > — 3G UTRAN TDD < Diversity : bit > { 0 | 1 < Bandwidth_TDD : bit (3) > } < Cell Parameter : bit (7) > < Sync Case : bit > } ; <spare bit>**; |
Parameters in the 3G Target Cell informatin element are defined in the Measurement Information message, sub-clause 9.1.54.