10.5.2 Radio Resource management information elements.
3GPP44.018GSM/EDGE Radio Resource Control (RRC) protocolMobile radio interface Layer 3 specificationRelease 17TS
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 44.006).
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.21a.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 If $(impr-BA-range-handling)$ is supported: $begin |
RANGEi_HIGHER If $(impr-BA-range-handling)$ is not supported: $begin If $(impr-BA-range-handling)$ is supported: $begin 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 shows only a special bit numbering. The different general format is described in table 10.5.2.1b.1.1.
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:
A GSM 900 mobile station which only supports the primary GSM band P-GSM 900 (cf. 3GPP TS 45.005) 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 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 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 |
ORIG |
|
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 |
RFCN |
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 44.006).
< 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 45.008 and 3GPP TS 23.022).
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 45.008 and 3GPP TS 23.022).
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 45.008 and 3GPP TS 23.022).
10.5.2.1d UTRAN Freq List
The UTRAN Freq 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 Freq List information element and an UTRAN Frequency List Description struct (3GPP TS 44.060) are received, the mobile station shall use the one most recently received.
The UTRAN Freq 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 44.006).
< 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.1e Cell selection indicator after release of all TCH and SDCCH IE
This IE indicates on which frequency /cell the cell selection after channel release shall be performed.
The "Cell selection indicator after release of all TCH and SDCCH" information element is coded as shown in figure 10.5.2.1e.1 and tables 10.5.2.1e.1 and 10.5.2.1e.2.
The "Cell selection indicator after release of all TCH and SDCCH" is a type 4 information element with a minimum length of 4 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006).
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Cell selection indicator after release of all TCH and SDCCH IEI |
octet 1 |
|||||||
Length of Cell selection indicator after release of all TCH and SDCCH value part |
octet 2 |
|||||||
Cell selection indicator after release of all TCH and SDCCH value part |
octet 3 – n |
Figure 10.5.2.1e.1: Cell selection indicator after release of all TCH and SDCCH information element
Table 10.5.2.1e.1: Cell selection indicator after release of all TCH and SDCCH value part
<Cell Selection Indicator after release of all TCH and SDCCH value part> ::= { 000 { 1 <GSM Description : <GSM Description struct >} ** 0 | 001 { 1 <UTRAN FDD Description : < UTRAN FDD Description struct >> } ** 0 | 010 { 1 <UTRAN TDD Description : < UTRAN TDD Description struct >> } ** 0 | 011 { 1 <E-UTRAN Description : < E-UTRAN Description struct >> } ** 0 }; |
< GSM Description struct > ::= < Band_Indicator : bit > < ARFCN : bit (10) > < BSIC : bit (6) > ; |
< UTRAN FDD Description struct > ::= { 0 | 1 < Bandwidth_FDD : bit (3) > } < FDD-ARFCN : bit (14) > { 0 | 1 < FDD_Indic0 : bit > |
< UTRAN TDD Description struct > ::= { 0 | 1 < Bandwidth_TDD : bit (3) > } < TDD-ARFCN : bit (14) > { 0 | 1 < TDD_Indic0 : bit > — q(x) defined in table 9.1.54.1 |
< E-UTRAN Description struct > ::= < EARFCN : bit (16) > { 0 | 1 < Measurement Bandwidth : bit (3) > } { 0 | 1 < Not Allowed Cells: < PCID Group IE > > } { 0 | 1 < TARGET_PCID : bit (9) > }; |
Table 10.5.2.1e.2: Cell selection indicator after release of all TCH and SDCCH value part details
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 45.005. |
ARFCN (10 bit field) Range 0 to 1023 |
BSIC (6 bit field) Range 0 to 63 |
UTRAN FDD DESCRIPTION |
UTRAN TDD DESCRIPTION E-UTRAN description For detailed element definitions see the Measurement Information message TARGET_PCID (9 bit field) |
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 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) BCC, BS colour code (octet 2) BCCH ARFCN (octet 2, bits 7 and 8, and octet 3) 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 Options (BCCH) IEI |
octet 1 |
|||||||
DN-IND |
PWRC |
DTX |
RADIO-LINK-TIMEOUT |
octet 2 |
Figure 10.5.2.3.1: Cell Options (BCCH) information element
Table 10.5.2.3.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 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 |
DN-IND, Dynamic ARFCN mapping indicator (octet 2) Note 4 Bit 8 0 Dynamic ARFCN mapping is not used by the PLMN 1 Dynamic ARFCN mapping is used by the PLMN |
NOTE 1: The precise meaning of the PWRC parameter can be found in 3GPP TS 45.008.
NOTE 2: The precise meaning of RADIO-LINK-TIMEOUT parameter can be found in 3GPP TS 45.008.
NOTE 3: The DTX indicator field is not related to the use of downlink discontinuous transmission.
NOTE 4: Dynamic ARFCN mapping is specified in 3GPP TS 45.005.
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 Options (SACCH) 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: (void)
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 45.008.
NOTE 2: The precise meaning of RADIO-LINK-TIMEOUT parameter can be found in 3GPP TS 45.008.
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 45.008 Bits 0 0 0 0 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 45.005 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 45.008. 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 45.008). |
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 (void)
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 S 0 0 0 1 TCH/F + ACCHs S 0 0 1 T TCH/H + ACCHs 0 0 1 T T SDCCH/4 + SACCH/C4 or CBCH (SDCCH/4); TSC Set 1 shall be used 0 1 T T T SDCCH/8 + SACCH/C8 or CBCH (SDCCH/8); TSC Set 1 shall be used The T bits indicate the subchannel number coded in binary. S, TSC set Bit 8 0 TSC Set 1 shall be used 1 TSC Set 2 shall be used All other values are reserved. 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 45.010. 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 45.002 The TSC set for the CS channels is signalled via ‘Channel type and TDMA offset’ field. In case of DTM the PS channels shall use the training sequence with the training sequence code as signalled in the TSC field and always selected from TSC Set 1 regardless of the TSC set signalled in the ‘Channel type and TDMA offset’ field. If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) and the ‘Extended TSC Set’ IE is included in the assignment message the mobile station shall use information provided therein for the CS and PS channels (see sub-clause 10.5.2.82). 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 45.002. Range: 0 to 63. HSN, (octet 4 bit 6 to 1) The HSN field is coded as the binary representation of the hopping sequence numberas defined in 3GPP TS 45.002 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 2 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) 1 1 0 0 0 TCH/F + ACCHs using TSC Set 2 1 1 1 0 T TCH/H + ACCHs using TSC Set 2 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 45.010. 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 45.002 Unless stated otherwise by coding of ‘Channel type and TDMA offset’ IE, TSC Set 1 shall be used. If a mobile station supports the extended TSC sets (see 3GPP TS 45.002 [32]) and the ‘Extended TSC Set’ IE is included in the assignment message the mobile station shall use information provided therein for the CS and PS channels (see sub-clause 10.5.2.82). 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 45.002. 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 45.002 Range 0 to 63. |
10.5.2.5c Channel Description 3
The purpose of the Channel Description 3 information element is to provide a description of a channel which does not specify a TCH.
The Channel Description 3 information element is coded as shown in figure 10.5.2.5c.1. All elements are as specified for the Channel Description IE (see sub-clause 10.5.2.5).
The Channel Description 3 is a type 3 information element with 3 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Channel Description 3 IEI |
octet 1 |
|||||||
H=1-> |
MAIO (high part) |
|||||||
TSC |
— H — |
—————————————————– |
octet 2 |
|||||
ARFCN |
||||||||
0 |
||||||||
H=0-> |
spare |
(high part) |
||||||
MAIO |
HSN |
octet 3 |
||||||
ARFCN (low part) |
Figure 10.5.2.5c.1: Channel Description 3 information element
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 1 1 0 0 0 0 0 1 speech full rate or half rate version 1 in VAMOS mode (Note 3) 0 0 1 0 0 0 0 1 speech full rate or half rate version 2 1 1 0 0 0 0 1 0 speech full rate or half rate version 2 in VAMOS mode (Note 3) 0 1 0 0 0 0 0 1 speech full rate or half rate version 3 1 1 0 0 0 0 1 1 speech full rate or half rate version 3 in VAMOS mode (Note 3) 1 0 0 0 0 0 0 1 speech full rate or half rate version 4 1 0 0 0 0 0 1 0 speech full rate or half rate version 5 1 1 0 0 0 1 0 1 speech full rate or half rate version 5 in VAMOS mode (Note 3) 1 0 0 0 0 0 1 1 speech full rate or half rate version 6 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 0 0 0 1 0 0 0 0 data, 64.0 kbit/s Transparent Data Bearer (Note 2) Other values are reserved for future use. Note 1: The speech versions are also referred as follows (see 3GPP TS 26.103): full rate or half rate version 1: GSM FR or GSM HR full rate or half rate version 2: GSM EFR (half rate version 2 not defined in this version of the protocol) full rate or half rate version 3: FR AMR or HR AMR full rate or half rate version 4: OFR AMR-WB or OHR AMR-WB full rate or half rate version 5: FR AMR-WB (half rate version 5 not defined in this version of the protocol) full rate or half rate version 6: OHR AMR (full rate version 6 not defined in this version of the protocol) Note 2: This code point is only used for channel assignments made in GAN mode. Note 3: This code point is only used for a mobile station that indicates support for VAMOS II or VAMOS III (see 3GPP TS 24.008) |
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 1 1 0 0 0 0 0 1 speech half rate version 1 in VAMOS mode (Note: 2) 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 1 1 0 0 0 0 1 1 speech half rate version 3 in VAMOS mode (Note: 2) 1 0 0 0 0 1 0 1 speech half rate version 4 0 1 0 0 0 1 1 0 speech half rate version 6 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 1: The speech versions are also referred as follows (see 3GPP TS 26.103): half rate version 1: GSM HR half rate version 2: not defined in this version of the protocol half rate version 3: HR AMR half rate version 4: OHR AMR-WB half rate version 6: OHR AMR Note 2: This code point is only used for a mobile station that indicates support for VAMOS II or VAMOS III (see 3GPP TS 24.008). |
10.5.2.7a UTRAN Classmark information element
Only valid for a UTRAN capable mobile station. The UTRAN 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.
The UTRAN 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 44.006).
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 or GERAN IU MODE CLASSMARK CHANGE message. The classmark change procedure is described in sub-clause 3.4.10.
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 000 UTRAN CLASSMARK CHANGE message is requested 111 UTRAN CLASSMARK CHANGE message is not requested. All other values shall not be sent. If received, they shall be interpreted as ‘000’. |
Bit 4: |
Bit 3: |
Bits 2 – 1: spare(0). |
10.5.2.7d GERAN Iu Mode Classmark information element
Only valid for a GERAN Iu mode capable mobile station. The GERAN Iu Mode Classmark information element includes the MS GERAN IU MODE RADIO ACCESS CAPABILTY IE defined in 3GPP TS 44.118.
The GERAN Iu mode Classmark information element is a type 4 information element with a minimum length of 13 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.060).
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
GERAN Iu Mode Classmark IEI |
octet 1 |
|||||||
Length of GERAN Iu Mode Classmark |
octet 2 |
|||||||
GERAN Iu Mode Classmark value part |
octet 3-n |
Figure 10.5.2.7d: GERAN Iu Mode Classmark information element
The value part of the GERAN Iu Mode Classmark information element is the MS GERAN IU MODE RADIO ACCESS CAPABILITY as defined in 3GPP TS 44.118. If the value part of the GERAN Iu Mode Classmark information element has a length which is not an integer number of octets, then the remaining bits in the GERAN Iu Mode Classmark information element shall be padding bits.
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 (void)
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 and MS capabilities relevant to DTM.
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 44.060 { 0 | 1 < PFI : bit (7) > } < Multiple TBF Capability : bit > — Additions in Rel-6 { null | L — Receiver backward compatible with earlier version | H — Additions in Rel-7 { < RLC Non-persistent Mode Capability : bit > < Reduced Latency Capability : bit > < Uplink EGPRS2 : bit(2) > < Downlink EGPRS2 : bit(2) > } { null | L — Receiver backward compatible with earlier version | H — Additions in Rel-9 { < EMST_MS_Capability : bit > } { null | L — Receiver backward compatible with earlier version | H — Additions in Rel-10 { < EMSR_MS_Capability : bit > } { null | L — Receiver backward compatible with earlier version | H — Additions in Rel-11 { < FANR_Capability : bit > } } — End of aditions for Rel-11 } — End of additions for Rel-10 } — End of additions for Rel-9 } — End of additions for Rel-7 < spare padding > ; |
Table 10.5.2.8b.2: Channel Request Description 2 value part details
PACKET_ESTABLISHMENT_CAUSE (2 bit field) Bit |
Channel Request Description (information element) The Channel Request Description information element is defined in 3GPP TS 44.060. |
PFI (7 bit field) |
Multiple TBF Capability (1 bit field) This field is included as the MS Radio Access Capability IE is not present and the Mobile Station Classmark 3 does not contain this information. Bit L Multiple TBF procedures in A/Gb mode not supported H Multiple TBF procedures in A/Gb mode supported |
RLC Non-persistent Mode Capability (1 bit field) This field is included as the MS Radio Access Capability IE is not present and the Mobile Station Classmark 3 does not contain this information. Bit 0 RLC Non-persistent Mode not supported 1 RLC Non-persistent Mode supported |
Reduced Latency Capability (1 bit field) This field indicates whether the mobile station supports Reduced TTI configurations and Fast Ack/Nack Reporting (see 3GPP TS 44.060 [76]) for both EGPRS and, if supported, EGPRS2. Bit 0 The mobile station does not support Reduced TTI configurations and Fast Ack/Nack Reporting 1 The mobile station supports Reduced TTI configurations and Fast Ack/Nack Reporting NOTE: A mobile station supporting both FANR and RTTI in (non DTM) packet transfer mode but whose multislot class does not allow the support of RTTI configurations in dual transfer mode due to a limited number of uplink or downlink timeslots (see 3GPP TS 45.002 [32]) shall support FANR for BTTI configurations in dual transfer mode and set the Reduced Latency Capability field to ‘1’. |
Uplink EGPRS2 (2 bit field) This field indicates whether the mobile station supports EGPRS2-A or EGPRS2-A and EGPRS2-B in the uplink Bit 2 1 0 0 The mobile station does not support either EGPRS2-A or EGPRS2-B in the uplink 0 1 The mobile station supports EGPRS2-A in the uplink 1 0 The mobile station supports both EGPRS2-A and EGPRS2-B in the uplink 1 1 This value is not used in this release/version of the specifications. If received it shall be interpreted as ‘10’ |
Downlink EGPRS2 (2 bit field) This field indicates whether the mobile station supports EGPRS2-A or EGPRS2-A and EGPRS2-B in the downlink Bit 2 1 0 0 The mobile station does not support either EGPRS2-A or EGPRS2-B in the downlink 0 1 The mobile station supports EGPRS2-A in the downlink 1 0 The mobile station supports both EGPRS2-A and EGPRS2-B in the downlink 1 1 This value is not used in this release/version of the specifications. If received it shall be interpreted as ‘10’ |
EMST_MS_Capability (1 bit field) This field indicates whether the mobile station supports the enhanced multiplexing for single TBF. Bit 0 The mobile station does not support EMST 1 The mobile station supports EMST |
EMSR_MS_Capability (1 bit field) This field indicates whether the mobile station supports the enhanced multiplexing for single RLC entity. Bit 0 The mobile station does not support EMSR 1 The mobile station supports EMSR |
FANR Capability (1 bit field) Bit 0 The mobile station does not support Fast Ack/Nack Reporting 1 The mobile station supports Fast Ack/Nack Reporting |
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 |
||||
SI22IND |
CBQ3 |
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. In a cell that supports eDRX this field is subject to special requirements (see 3GPP TS 45.002 [32]). 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 |
SI22IND, SYSTEM INFORMATION TYPE 22 indicator (octet 3) Bit 8 0 SI22 is not broadcast. 1 SI22 is broadcast. |
CBQ3, Cell Bar Qualify 3 (octet 3) Bits 7 6 0 0 Iu mode not supported 0 1 Iu mode capable MSs barred 1 0 Iu mode supported, cell not barred 1 1 Iu mode supported, cell not barred. The network shall not use this value. NOTE: See 3GPP TS 45.008 for information on Cell Bar Qualify 3 |
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 This field is not used by a MS that uses eDRX (see 3GPP TS 45.002 [32]). 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. |
NOTE: The MSC Release bit indicates the version of the MSC specific protocols and is not applicable to access stratum protocols.
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 minimum length of 5 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 |
|
DTM Information Details IEI |
octet 1 |
|||||||
Length of DTM Information Details value part |
octet 2 |
|||||||
DTM Information Details value part |
octet 3-n |
Figure 10.5.2.11a.1: DTM Information Details information element
Table 10.5.2.11a.1: DTM Information Details value part
< DTM Information Details value part > ::= < MAX_LAPDm : bit (3) > < GPRS_MS_TXPWR_MAX_CCH : bit (5) > < Cell identity: bit (16) > { null | L — Receiver backward compatible with earlier version | H — Additions for REL-6 { 0 — MBMS procedures not supported by the cell if the choice bit is set to ‘0’ | 1 — MBMS procedures supported by the cell if the choice bit is set to ‘1’ < DEDICATED_MODE_MBMS_NOTIFICATION_SUPPORT: bit > < MNCI_SUPPORT: bit >} < 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) Range: 0 to 31. |
Cell identity (16 bits field) |
DEDICATED_MODE_MBMS_NOTIFICATION_SUPPORT (1 bit field) |
MNCI_SUPPORT (1 bit field) |
10.5.2.11b Dynamic ARFCN Mapping
The purpose of the Dynamic ARFCN Mapping information element is to provide information on ARFCN mapping to physical frequencies (see 3GPP TS 45.005).
The Dynamic ARFCN Mapping 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 44.060).
Parameters GSM_Band, ARFCN_FIRST, BAND_OFFSET and ARFCN_RANGE are defined in table 10.5.2.37j.
Spare bits in the end of the field are used to fill the last octet.
Table 10.5.2.11b.1: Dynamic ARFCN Mapping content
< Dynamic ARFCN Mapping >::= < LENGTH OF DYNAMIC ARFCN MAPPING : bit (8) > — length of value part in octets < DYNAMIC ARFCN MAPPING Description : { 1 < DYNAMIC ARFCN MAPPING > } ** 0 > < spare bit >** ; |
< DYNAMIC ARFCN MAPPING >::= < GSM_Band : bit (4) > < ARFCN_FIRST : bit (10) > < BAND_OFFSET: bit (10) > < ARFCN_RANGE : bit (7) > ; |
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 45.005).
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 (cf. 3GPP TS 45.005) 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 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 – 2) mod (2048/J – 1) + 1; else — right child INDEX := INDEX – J; N := (N + W(PARENT) +2048/J – 2) 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 INDEX := INDEX – J/2; — left child N := (N + W(PARENT) + 512/J – 2) mod (1024/J – 1) + 1; else — right child INDEX := INDEX – J; N := (N + W(PARENT) +1024/J – 2) mod (1024/J – 1) + 1; end if; J := J/2; end loop; F(K) := N; |
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 – 2) mod (512/J – 1) + 1; else — right child INDEX := INDEX – J; N := (N + W(INDEX) + 512/J – 2) 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 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 – 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 – 2) mod (256/J – 1) + 1; else — right child INDEX := INDEX – J; N := (N + W(INDEX) + 256/J – 2) 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 et, 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) 1 0 0 0 0 TCH/FS + ACCHs (speech codec version 2) 1 0 0 0 1 TCH/AFS + ACCHs (speech codec version 3) 1 0 0 1 T TCH/AHS + ACCHs (speech codec version 3) 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. A mobile station that is not able to recognise the channel type when set to a value that is defined as ‘reserved for future use’ in earlier versions of this specification, may be able to join the group call from the signalling point of view but is not able to decode any speech. |
TN, Timeslot number (octet 3) The TN field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.010. 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 45.002 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 45.002. 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 45.002 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 informationi 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 IE > > < spare bit >**; |
Table 10.5.2.14d.2: GPRS broadcast information value part details
GPRS Cell Options |
GPRS Power Control Parameters |
10.5.2.14e Enhanced DTM CS Release Indication
The purpose of the Enhanced DTM CS Release Indication information element is to indicate whether the mobile station is allowed to enter packet transfer mode or not, when the RR connection is released while in dual transfer mode.
The Enhanced DTM CS Release Indication information element is coded as shown in figure 10.5.2.14e.1 and table 10.5.2.14e.1.
The Enhanced DTM CS Release Indication is a type 1 information element.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Enhanced DTM CS Release Indication |
Spare |
IND |
Octet 1 |
|||||
IEI |
0 |
0 |
0 |
Figure 10.5.2.14e.1: Enhanced DTM CS Release Indication information element
Table 10.5.2.14e.1: Enhanced DTM CS Release Indication information element
The IND field (1 bit) is the binary indication whether the mobile station is allowed to enter packet transfer mode directly after the release of the RR connection: 0 the mobile station is not allowed to continue in packet transfer mode; 1 the mobile station is allowed to continue in packet transfer mode. |
10.5.2.14f Group Channel Description 2
The purpose of the Group Channel Description 2 information element is to provide a description of an allocatable voice group call channel together with its SACCH and the list of the absolute radio frequency channel numbers used in a frequency hopping sequence, in a small fixed length information element.
The Group Channel Description 2 information element is coded as shown in figure 10.5.2.14f.1 and table 10.5.2.14f.1.
The Group Channel Description 2 is a type 4 information element with the value part that has fixed length of 11 octets.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Group Channel Description 2 IEI |
octet 1 |
|||||||
Length of Group Channel Description 2 |
octet 2 |
|||||||
Channel type and TDMA offset |
TN |
octet 3 |
||||||
TSC |
0 |
MAIO (high part) |
octet 4 |
|||||
MAIO |
HSN |
octet 5 |
||||||
Same coding as Frequency Short List 2 (sub-clause 10.5.2.14a) |
octet 6 |
|||||||
octet 13 |
Figure 10.5.2.14f.1: Group Channel Description 2 information element
Table 10.5.2.14f.1: Group Channel Description2 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) 1 0 0 0 0 TCH/FS + ACCHs (speech codec version 2) 1 0 0 0 1 TCH/AFS + ACCHs (speech codec version 3) 1 0 0 1 T TCH/AHS + ACCHs (speech codec version 3) 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. A mobile station that is not able to recognise the channel type when set to a value that is defined as ‘reserved for future use’ in earlier versions of this specification, may be able to join the group call from the signalling point of view but is not able to decode any speech. |
TN, Timeslot number (octet 3) The TN field is coded as the binary representation of the timeslot number as defined in 3GPP TS 45.010. 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 45.002 Range: 0 to 7. |
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 45.002. Range: 0 to 63. |
HSN, (octet 5) The HSN field is coded as the binary representation of the hopping sequence number as defined in 3GPP TS 45.002 Range 0 to 63. |
Octet 6 to octet 13 have the same coding as Frequency Short List 2 (sub-clause 10.5.2.14a) |
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, a frequency parameters, before time or a multiple blocks packet downlink assignment 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 < Compressed_Inter_RAT_HO_INFO_IND > { null | L — Receiver compatible with earlier release | H — Additions in Release 13 < Implicit Reject PS : bit > < PEO_BCCH_CHANGE_MARK : bit (2) > < RCC : bit (3) > } | LH { 00 < EGPRS Packet Uplink Assignment > | 01 < Multiple Blocks Packet Downlink Assignment > | 1 — reserved for future use (however the value 7C for the first octet shall not be used) } { null | L — Receiver compatible with earlier release | H — Additions in Release 13 < Implicit Reject PS : bit > < PEO_BCCH_CHANGE_MARK : bit (2) > < RCC : bit (3) > } | HL < Length of frequency parameters : bit string (6) > < Frequency Parameters, before time > < Compressed_Inter_RAT_HO_INFO_IND > { null | L — Receiver compatible with earlier release | H — Additions in Release 13 < Implicit Reject PS : bit > < PEO_BCCH_CHANGE_MARK : bit (2) > < RCC : bit (3) > } | HH { 00 < Packet Uplink Assignment > | 01 < Packet Downlink Assignment > | 1 < Second Part Packet Assignment > } { null | L — Receiver compatible with earlier release | H — Additions in Release 10 < Implicit Reject CS : bit > < Implicit Reject PS : bit > } { null | L — Receiver compatible with earlier release | H — Additions in Release 13 < PEO_BCCH_CHANGE_MARK : bit (2) > < RCC : bit (3) > } } — Additions for Rel-14 { 0 | 1 < Multilateration Information Request : bit (1) > } — Additions for Release 15 { 0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } <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 — The value ‘1’ was allocated in an earlier version of the protocol and shall not be used. < USF: bit (3) > < USF_GRANULARITY : bit > { 0 | 1 < P0 : bit (4) > < 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) > } { null | L — Receiver compatible with earlier release | H — Additions for Rel-7 { 0 — An uplink BTTI TBF is assigned { 0 — ‘0’ indicates that FANR is not activated | 1 — ‘1’ indicates that FANR is activated { 0 — SSN-based encoding is selected | 1 — Time-based encoding is selected < REPORTED TIMESLOTS : bit (8) > < TSH : bit (2) > } } | 1 — An uplink RTTI TBF is assigned <RTTI USF Mode :_ bit(1)> <PDCH PAIR INDICATION: bit(3) > < Additional_USF : bit (3) >*(1-val(RTTI USF MODE)) { 0 — One PDCH Pair assigned | 1 < USF2 : bit(3)> — Two PDCH Pairs assigned < Additional_USF2 : bit (3) >*(1-val(RTTI USF MODE)) } { 0 — SSN-based encoding is selected | 1 < REPORTED TIMESLOTS : bit (8) > — Time-based encoding is selected < TSH : bit (2) > } } } | 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) > 0 — The value ‘1’ was allocated in an earlier version of the protocol and shall not be used. < PR_MODE : bit (1) > } { null | L — Receiver compatible with earlier release | H — Additions for Rel-6 { 0 | 1 < PFI : bit (7) > } } } ; |
<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 — The value ‘1’ was allocated in an earlier version of the protocol and shall not be used. < USF: bit (3) > < USF_GRANULARITY : bit > { 0 | 1 < P0 : bit (4) > < 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) > 0 — The value ‘1’ was allocated in an earlier version of the protocol and shall not be used. < PR_MODE : bit (1) > } } { null | L — Receiver compatible with earlier release | H — Additions for R99 { 0 | 1 < Extended RA : bit (5) > } } { null | L — Receiver compatible with earlier release | H — Additions for Rel-6 { 0 | 1 < PFI : bit (7) > } } ; |
< 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) > 0 — The value ‘1’ was allocated in an earlier version of the protocol and shall not be used. < PR_MODE : bit (1) > } { null | L — Receiver compatible with earlier release | H — Additions for R99 — indicates EGPRS TBF mode, see 44.060 < EGPRS Window Size : < EGPRS Window Size IE >> < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > { 0 | 1 < BEP_PERIOD2 : bit (4) > } } { null | L — Receiver compatible with earlier release | H — Additions for Rel-6 { 0 | 1 < PFI : bit (7) > } } { null | L — Receiver compatible with earlier release | H — Additions for Rel-7 { 0 | 1 < NPM Transfer Time : bit (5) > } { 0 — A downlink BTTI TBF is assigned { 0 — FANR is not activated for the assigned TBF | 1 — FANR is activated for the assigned TBF < EVENT_BASED_FANR: bit (1) > } | 1 — A downlink RTTI TBF is assigned < EVENT_BASED_FANR: bit (1) > < PDCH PAIR INDICATION: bit(3) > } < Downlink EGPRS Level: < EGPRS Level IE > > } ; |
< 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) > } } ; |
< Multiple Blocks Packet Downlink Assignment > ::= < TBF_STARTING_TIME : bit (16) > < NUMBER_OF_ALLOCATED_BLOCKS : bit (4) > { 0 — Reserved for future use | 1 { 0 — MBMS Assignment (Distribution) < TMGI : < TMGI IE > > { 0 | 1 < MBMS Session Identity : bit (8) > } | 1 — MBMS Assignment (Non-distribution) < TLLI / G-RNTI bit (32) > { 0 | 1 < Length Indicator of MS ID : bit (2) > < MS_ID : bit (val (Length Indicator of MS_ID)+1) > < PACKET_TIMING_ADVANCE : < Packet Timing Advance IE > > { 0 | 1 < ALPHA : bit (4) > { 0 | 1 < GAMMA : bit (5) > } } } } } ; < PEO IMM Cell Group Details struct > ::= — Addition in Rel-15 < PEO IMM Cell Group Identifier : bit (3) > < PEO IMM Change Mark : bit (2) >; |
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 1997.
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 EGPRS PACKET CHANNEL REQUEST message defined in 3GPP TS 44.060. 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 |
The TFI_ASSIGNMENT field (5 bit field) is the binary representation of the Temporary Flow Identity, see 3GPP TS 44.060. Range: 0 to 31. |
The USF field (3 bit field) is the binary representation of the uplink state flag, see 3GPP TS 44.060. Range: 0 to 7. For the case when BTTI USF mode is used for an uplink EGPRS TBF in RTTI configuration, this field indicates the USF to be monitored on the first PDCH of the first corresponding downlink PDCH pair assigned for that TBF. |
The USF2 field (3 bit field) is the binary representation of the uplink state flag, see 3GPP TS 44.060. Range: 0 to 7. This field shall only be used in the case when two PDCH pairs are assigned for an uplink EGPRS TBF in RTTI configuration, and will in such case apply to the second PDCH pair. For the case when BTTI USF mode is used for an uplink EGPRS TBF in RTTI configuration, this field indicates the USF to be monitored on the first PDCH of the second corresponding downlink PDCH pair assigned for that TBF. |
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 44.060: 0 the mobile station shall transmit one RLC/MAC block; |
The CHANNEL_CODING_COMMAND field (2 bit field) indicates the coding scheme to be used for transmission, see 3GPP TS 45.003: 0 0 coding scheme 1, CS-1; |
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 45.008: 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 45.008. |
The TIMING_ADVANCE_INDEX field (4 bit field) is the binary representation of the timing advance index (TAI), see 3GPP TS 45.010 and 3GPP TS 44.004. 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) |
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 44.060. Range: 0 to 31. |
The RLC_MODE field (1 bit field) indicates the RLC mode, see 3GPP TS 44.060: 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 45.010 and 3GPP TS 44.004. 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 (sub-clause 10.5.2.38). |
P0 (4 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 EGPRS PACKET CHANNEL REQUEST message defined in 3GPP TS 44.060. 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 Assignment EGPRS specific fields 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 44.060. |
LINK_QUALITY_MEASUREMENT_MODE (2 bit field) This field is encoded as the LINK_QUALITY_MEASUREMENT_MODE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. |
Access Technology Type Among the three GSM 900 access technology types GSM P, GSM E and GSM R only one shall be requested by the network. |
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) |
Compressed_Inter_RAT_HO_INFO_IND (1 bit field): This information is used for determining whether a dual mode mobile station shall use a compressed version of the INTER RAT HANDOVER INFO message, see 3GPP TS 25.331. |
PFI (7 bit field) |
Number of Allocated Blocks 0 0 0 0 1 radio block reserved for downlink transmission; 0 0 0 1 2 radio blocks reserved for downlink transmission; 0 0 1 0 3 radio blocks reserved for downlink transmission; 0 0 1 1 4 radio blocks reserved for downlink transmission; 0 1 0 0 5 radio blocks reserved for downlink transmission; 0 1 0 1 6 radio blocks reserved for downlink transmission; 0 1 1 0 7 radio blocks reserved for downlink transmission; 0 1 1 1 8 radio blocks reserved for downlink transmission; 1 0 0 0 9 radio blocks reserved for downlink transmission. All other values are reserved for future use. |
TMGI |
MBMS Session Identity (8 bit field) |
MS_ID (1-4 bit field) |
Packet Timing Advance |
ALPHA (4 bit field) |
GAMMA (5 bit field) bit |
NPM Transfer Time (5 bit field) This field contains the NPM Transfer Time limitation in case of RLC non-persistent mode, and is encoded as the NPM Transfer Time IE in 3GPP TS 44.060. |
EVENT_BASED_FANR (1 bit field) This field indicates whether the event-based FANR shall be used for the assigned TBF. The presence of this field means that FANR is activated for the assigned TBF. The coding of this information element is defined in 3GPP TS 44.060. |
RTTI USF Mode (1 bit field) 0 BTTI USF Mode is used |
The Additional USF (3 bit field) is the binary representation of the uplink state flag, see 3GPP TS 44.060. Range: 0 to 7. This field is used only in the case when BTTI USF mode is used for an uplink EGPRS TBF in RTTI configuration and indicates the USF to be monitored on the second PDCH of the first corresponding downlink PDCH pair assigned for that TBF. |
The Additional USF2 (3 bit field) is the binary representation of the uplink state flag, see 3GPP TS 44.060. Range: 0 to 7. This field shall only be used in the case when two PDCH pairs are assigned for an uplink EGPRS TBF in RTTI configuration, and will in such case apply to the second PDCH pair. This field is used only in the case when BTTI USF mode is used for an uplink EGPRS TBF in RTTI configuration and indicates the USF to be monitored on the second PDCH of the second corresponding downlink PDCH pair assigned for that TBF. |
PDCH PAIR INDICATION (3 bit field) This field is the binary encoding of the relative placement of the timeslots constituting the uplink PDCH pair(s) and the corresponding downlink PDCH pair(s) in case of an uplink RTTI assignment, or the downlink PDCH pair(s) and the corresponding uplink PDCH pair(s) in case of a downlink RTTI assignment (see 3GPP TS 44.060). The placement is relative to the TN as indicated in the Packet Channel Description Information Element as described in subclause 10.5.2.25a. In the case the timeslot number indicated by the Packet Channel Description is TN=i, then this field is encoded as follows: bit uplink PDCH pair(s) downlink PDCH pair(s) 1 1 1 not used |
REPORTED TIMESLOTS (8 bit field) The field indicates the timeslots for which feedback is provided by a time-based encoded PAN field and is defined in 3GPP TS 44.060. |
TSH (2 bit field) This field indicates the time-shift between the most recent radio block period for which feedback information is provided and the radio block period when the bitmap is sent and is defined in 3GPP TS 44.060. Downlink EGPRS Level The coding of this information element is defined in 3GPP TS 44.060. Implicit Reject CS (1 bit) 0 An implicit reject is not indicated for the CS domain. 1 An implicit reject is indicated for the CS domain. Implicit Reject PS (1 bit) 0 An implicit reject is not indicated for the PS domain. 1 An implicit reject is indicated for the PS domain. PEO_BCCH_CHANGE_MARK (2 bit) See P1 Rest Octets IE, sub-clause 10.5.2.23. RCC (3 bit) This field contains Radio frequency Colour Code (RCC), and used when determining the 9 bit BSIC (see 3GPP TS 45.003 and 3GPP TS 45.008). It has a value in the range 0 to7. |
Multilateration Information Request (1 bit field) This field indicates whether or not a MS is to include "MS Transmission Offset" and "MS Sync Accuracy" parameters when sending an EGPRS Packet Downlink Ack/Nack Type 2 message (see 3GPP TS 44.060 [76]) or an EGPRS Packet Downlink Ack/Nack Type 3 message (see 3GPP TS 44.060 [76]) during a downlink TBF. This field can be included when the IA Rest Octets or IPA Rest Octets information element is used to assign a downlink TBF to deliver a downlink LLC PDU for which the corresponding DL-UNITDATA PDU indicates timing advance information is needed (see 3GPP TS 48.018). This field is coded as follows: 0 Do not include "MS Transmission Offset" and "MS Sync Accuracy" parameters 1 Include "MS Transmission Offset" and "MS Sync Accuracy" parameters PEO IMM Cell Group Details struct This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). PEO IMM Cell Group Identifier (3 bits) This 3 bit field provides the PEO IMM Cell Group Identifier (see subclause 10.5.2.37b) and is coded as follows: bit 0 0 0 Cell belongs to PEO IMM Cell Group Identity 0 0 0 1 Cell belongs to PEO IMM Cell Group Identity 1 0 1 0 Cell belongs to PEO IMM Cell Group Identity 2 … 1 1 1 Cell belongs to PEO IMM Cell Group Identity 7 PEO IMM Change Mark (2 bits) This 2 bit field identifies the change mark of the PEO IMM Cell Group (see subclause 10.5.2.37b) and is coded as follows: bit 0 0 PEO IMM Change Mark value is 0 0 1 PEO IMM Change Mark value is 1 1 0 PEO IMM Change Mark value is 2 1 1 PEO IMM Change Mark value is 3 |
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) > } { null | L — Receiver compatible with earlier release | H — Additions in Release 13 < RCC : bit (3) > } — Additions in Release 15 {0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } <spare padding> ; < PEO IMM Cell Group Details struct > ::= — Addition in Rel-15 < PEO IMM Cell Group Identifier : bit (3) > < PEO IMM Change Mark : bit (2) >; |
Figure 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 44.060. RCC (3 bit) See sub-clause 10.5.2.16. PEO IMM Cell Group Details struct This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). PEO IMM Cell Group Identifier (3 bits) See sub-clause 10.5.2.16. PEO IMM Change Mark (2 bits) See sub-clause 10.5.2.16. |
10.5.2.18 IAX Rest Octets
The IAX Rest Octets information element is coded according to the syntax specified below and described in table 10.5.2.18.1.
The IAX Rest Octets information element is a type 5 information element with 0-4 octets length.
<IAX Rest Octets> ::= < Compressed_Inter_RAT_HO_INFO_IND : bit > { null | L — Receiver compatible with earlier release | H — Additions in Release 13 < RCC : bit (3) > } — Additions in Release 15 {0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } <spare padding> ; < PEO IMM Cell Group Details struct > ::= — Addition in Rel-15 < PEO IMM Cell Group Identifier : bit (3) > < PEO IMM Change Mark : bit (2) >; |
Figure 10.5.2.18.1: IAX Rest Octets information element
Table 10.5.2.18.1: IAX Rest Octet information element
Compressed_Inter_RAT_HO_INFO_IND (1 bit field): This information is used for determining whether a multi-RAT mobile station shall use a compressed version of the INTER RAT HANDOVER INFO message, see 3GPP TS 25.331. RCC (3 bit) See sub-clause 10.5.2.16. PEO IMM Cell Group Details struct This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). PEO IMM Cell Group Identifier (3 bits) See sub-clause 10.5.2.16. PEO IMM Change Mark (2 bits) See sub-clause 10.5.2.16. |
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 when present) 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 tables 10.5.2.20.0 and 10.5.2.20.1. The field mapping convention defined for RLC/MAC control blocks shall be used (see 3GPP TS 44.060).
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 |
|||||||
Measurement Results Contents |
octets 2-17 |
Figure 10.5.2.20.1: Measurement Results information element
Table 10.5.2.20.0: Measurement Results Contents
< Measurement Results Contents > ::= { < BA_USED : bit (1) > < DTX_USED : bit (1) > < RXLEV_FULL_SERVING_CELL : bit (6) > < 3G_BA_USED : bit (1) > < MEAS_VALID : bit (1) > < RXLEV_SUB_SERVING_CELL : bit (6) > < SI23_BA_USED : bit (1) > < RXQUAL_FULL_SERVING_CELL : bit (3) > < RXQUAL_SUB_SERVING_CELL : bit (3) > { < NO_NCELL_M : { bit (3) := 111 } > 0** — Padding with zeroes } | { < NO_NCELL_M : { bit (3) exclude 111 } > { < NCELL Report : < NCELL Report struct >> } * val (NO_NCELL_M) { null | 0** — Padding with zeroes | 1 < UTRAN_CSG_Measurement_Report : < UTRAN_CSG_Measurement_Report IE > > { null | 0** } — Padding with zeroes } } } & octet (16) ; |
< NCELL Report struct > ::= < RXLEV-NCELL: bit (6) > < BCCH-FREQ-NCELL : bit (5) > < BSIC-NCELL : bit (6) > ; |
Table 10.5.2.20.1: Measurement Results Contents details
BA-USED (1 bit field) |
DTX-USED (1 bit field) Bit 7 |
RXLEV-FULL-SERVING-CELL and RXLEV-SUB-SERVING-CELL (6 bit fields) 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 45.008 to the received signal strength on the serving cell. Range: 0 to 63 |
MEAS-VALID (1 bit field) Bit 7 |
3G-BA-USED (1 bit field) SI23_BA_USED (1 bit field) |
RXQUAL-FULL-SERVING-CELL and RXQUAL-SUB-SERVING-CELL (3 bit fields) CELL fields are coded as the binary representation of the received signal quality on the serving cell. Range: 0 to 7 (See 3GPP TS 45.008) |
NO-NCELL-M (3 bit field) Bits |
NCELL Report |
RXLEV-NCELL i (6 bit field) 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 45.008 to the received signal strength on the i’th neighbouring cell. If the i’th neighbour cell is a 3G cell, the contents of the RXLEV-NCELL field is defined in 3GPP TS 45.008. Range: 0 to 63. |
BCCH_FREQ_NCELL (5 bit field) |
BSIC_NCELL (6 bit field) |
Report on GSM cells: BCCH-FREQ-NCELL i, BCCH carrier of the i’th neighbour cell. 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. 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". 3G cells with indexes above 63 are not reported (6 bits field). If more than 31 (GSM) ARFCN frequencies are included in the BA (list), reporting of 3G cells is not possible with this IE. Range: 0 to 63. |
Report on E-UTRAN cells: If no more than (31 – NUM_E-UTRAN_FREQUENCIES) GSM ARFCN frequencies are included in the BA (list), the BCCH-FREQ-NCELL indices from (31 – NUM_E-UTRAN_FREQUENCIES) to 30 (inclusive) indicate report(s) on E-UTRAN cells. The index BCCH-FREQ-NCELL 30 indicates a report of an E-UTRAN neighbour cell on the first frequency defined in the E-UTRAN Neighbour Cell list, the value 29 indicates a report of an E-UTRAN neighbour cell on the second frequency in the E-UTRAN Neighbour Cell list and so on. NUM_E-UTRAN_FREQUENCIES is defined as the number of separate E-UTRAN frequencies in the E-UTRAN Neighbour Cell list. If the BCCH-FREQ-NCELL index indicates an E-UTRAN frequency, the corresponding ‘BSIC-NCELL’ field in figure 10.5.2.20.1 contains the least significant 6 bits of the physical layer cell identity (see 3GPP TS 36.211) of the E-UTRAN neighbour cell. The corresponding ‘RXLEV-NCELL’ field in figure 10.5.2.20.1 contains the 3 bit measurement value (see 3GPP TS 45.008) in the most significant 3 bits of the field and the most significant 3 bits of the physical layer cell identity in the least significant 3 bits of the field. If more than (31 – NUM_E-UTRAN_FREQUENCIES) GSM ARFCN frequencies are included in the BA (list), reporting of E-UTRAN cells is not possible with this IE. |
BSIC-NCELL i (6 bit field) 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. Range: 0 to 63. |
UTRAN CSG Measurement Report |
10.5.2.20a (void)
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-clauses 9.1.18.1 and 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 speech codec.
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 |
|||||||
Multirate speech version |
NSCB |
ICMI |
spare |
Start mode |
octet 3 |
|||
Parameters for multirate speech |
octet 4 |
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 Multirate speech versions 1 & 2 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: Parameters for multirate speech field
for the Multirate speech versions 1 & 2 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 Multirate speech versions 1 & 2 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 Multirate speech versions 1 & 2 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 0 1 0 Adaptive Multirate speech version 2 Other values reserved NOTE 1: The Adaptive Multirate speech versions are also referred as follows (see 3GPP TS 26.103): Bit 5 NSCB: Noise Suppression Control Bit 0 Noise Suppression can be used (default) 1 Noise Suppression shall be turned off Bit 4 ICMI: Initial Codec Mode Indicator 0 The initial codec mode is defined by the implicit rule provided in 3GPP TS 45.009 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 45.009. When Multirate speech version field indicates Adaptive Multirate speech version 1 or 2 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 45.009; HYSTj (4 bits) is coded as the binary representation of the hysteresis value associated to THRj, as defined in 3GPP TS 45.009. j = 1 corresponds to the lowest value of threshold in dB, j = 2 to the second lowest, j = 3 to the highest value. |
Table 10.5.2.21aa.2: Set of adaptive multirate codec modes field (octet 4)
for the Multirate speech version 1
Bit 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; |
Bit 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; |
Bit 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; |
Bit 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; |
Bit 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; |
Bit 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; |
Bit 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; |
Bit 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; |
Table 10.5.2.21aa.3: Set of adaptive multirate codec modes field (octets 4 & 5)
for the Multirate speech version 2
Bit 8 (Octet 4) 0 spare |
Bit 7 (Octet 4) 0 spare |
Bit 6 (Octet 4) 0 spare |
Bit 5 (Octet 4) 0 23,85 kbit/s codec rate is not part of the subset; 1 23,85 kbit/s codec rate is part of the subset; |
Bit 4 (Octet 4) 0 15,85 kbit/s codec rate is not part of the subset; 1 15,85 kbit/s codec rate is part of the subset; |
Bit 3 (Octet 4) 0 12,65 kbit/s codec rate is not part of the subset; 1 12,65 kbit/s codec rate is part of the subset; |
Bit 2 (Octet 4) 0 8,85 kbit/s codec rate is not part of the subset; 1 8,85 kbit/s codec rate is part of the subset; |
Bit 1 (Octet 4) 0 6,60 kbit/s codec rate is not part of the subset; 1 6,60 kbit/s codec rate is part of the subset; |
10.5.2.21ab Mobile Time Difference on Hyperframe level
A Mobile Time Difference on Hyperframe level 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 on Hyperframe level information element is coded as shown in figure 10.5.2.21ab.1 and table 10.5.2.21ab.1.
The Mobile Time Difference on Hyperframe level information element is a type 4 information element with 7 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Mobile Time Difference on Hyperframe level IEI |
Octet 1 |
|||||||
Length of Mobile Time difference on Hyperframe level contents |
Octet 2 |
|||||||
Mobile Time Difference on Hyperframe level value (high) |
Octet 3 |
|||||||
Mobile Time Difference on Hyperframe level value (contd) |
Octet 4 |
|||||||
Mobile Time Difference on Hyperframe level value (contd) |
Octet 5 |
|||||||
Mobile Time Difference on Hyperframe level value (contd) |
Octet 6 |
|||||||
Mobile Time Difference on Hyperframe level value (low) |
0 |
0 |
0 |
0 |
0 |
0 |
0 |
Octet 7 |
Figure 10.5.2.21ab.1: Mobile Time Difference on Hyperframe level information element
Table 10.5.2.21ab.1: Mobile Time Difference on Hyperframe level information element
Mobile Time Difference on Hyperframe level value (octets 3 to 7) The value is calculated by adding the timing advance value towards the old BTS to the time difference between the start of a hyperframe in the old BTS and the start of the next hyperframe in the new BTS as observed by the mobile station. (See 3GPP TS 45.010). |
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 Type 2: TCH/F + SACCH/M bidirectional Type 3: TCH/F + SACCH/M unidirectional 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 (void)
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 (cf. 3GPP TS 45.005) 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 1: EXT-IND 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. NOTE 2: The network should change the contents of the Neighbour Cell Description information element (FORMAT-ID and/or set of ARFCNs) when changing the ciphering mode from not ciphered to ciphered with algorithm A5/1 (see sub-clause 3.4.7.2). For this purpose, the network may change the set of frequencies, by including ARFCNs not in a frequency band supported by the MS, without changing the BA-IND value, provided the position in the resulting BA(SACCH) of the ARFCNs that are candidates for measurement reporting is not altered. The network should also ensure that different mobiles in the cell receive different sets of ARFCNs when sent encrypted with A5/ |
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 128 124 123 122 format notation 0 X X X bit map 0 1 0 X X 1024 range 1 1 0 0 512 range 1 1 0 1 256 range 1 1 1 0 128 range 1 1 1 1 variable bit map Bits 6 and 7 of Octet 2 Multiband reporting Binary encoding of multiband reporting parameter as specified in 3GPP TS 45.008. 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. NOTE: The network should change the contents of the Neighbour Cell Description 2 information element (FORMAT-ID and/or set of ARFCNs) when changing the ciphering mode from not ciphered to ciphered with algorithm A5/1 (see sub-clause 3.4.7.2). For this purpose, the network may change the set of frequencies, by including ARFCNs not in a frequency band supported by the MS, without changing the BA-IND value, provided the position in the resulting BA(SACCH) of the ARFCNs that are candidates for measurement reporting is not altered. The network should also ensure that different mobiles in the cell receive different sets of ARFCNs when sent encrypted with A5/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(NCH) : bit (2) >} <list of Group Call NCH information> { null | L — Receiver compatible with earlier release | H — Additions in Release 6°: { 0 | 1 < CELL_GLOBAL_COUNT: bit (2) >} < List of Reduced GCR > < List of VSTK_RAND information > } { null | L — Receiver compatible with earlier release | H — Additions in Release 7°: < List of Emergency information > { 0 | 1 < Priority Uplink access : bit(1)> } { 0 | 1 { 0|1 <FR AMR Config:bit(4)> } { 0|1 <HR AMR Config:bit(4)> } } { 0 | 1 < SMS Data Confidentiality Ind : bit(1)> < SMS Guaranteed Privacy Ind : bit(1)> } } <Spare padding>; |
< List of Group Call NCH information > ::= { 0 | 1 < Group Call information > < List of Group Call NCH information > } ; |
< List of Emergency information > ::= { 0 | 1 < Emergency_Ind > < List of Emergency information > } ; If List of Emergency Information is not present in the notification, then the emergency mode is not set for all of the group calls in the List of Group Call NCH information that contain a group channel description. Each Emergency_Ind in the List of Emergency Information is associated with a VGCS/VBS call in the List of Group Call NCH information. The Emergency_Ind at position (i) in the List of Emergency Information is associated with (i)th group call in the List of Group Call NCH information that contains a group channel description. |
NLN(NCH) This field gives the NLN value to be used as specified in sub-clause3.3.3 |
<Group Call information> See sub-clause 9.1.21a |
Segment Id (1 bit) Indicates if this message instance contains the first or second segment of a segmented notification. bit If the notification is not segmented then the Segment Id shall be set to 0. |
CELL_GLOBAL_COUNT (2 bits) This field contains the CELL_GLOBAL_COUNT that is used by the VGCS/VBS ciphering mechanism. The value is incremented by one (modulo 4) each time bit 22 of COUNT ( defined in 3GPP TS 43.020) changes from ‘1’ to ‘0’. |
< List of VSTK_RAND information > ::= { 1 < Segment Id: bit > {0 | 1 < VSTK_RAND: bit (36) >} } **0; Each VSTK_RAND and Segment Id that is in the List of VSTK_RAND Information is associated to a ciphered VGCS/VBS call that is in the List of Group Call NCH information or List of Reduced GCR information. The VSTK_RAND and Segment Id at position (i) in the List of VSTK_RAND Information is associated with (i)th ciphered group call in the combined List of Group Call NCH information and List of Reduced GCR information, where the elements in the List of Group Call NCH information precede the elements in the List of Reduced GCR. |
< List of Reduced GCR > ::= { 1< Reduced GCR: bit (28) >} **0; The Reduced Group Call Reference shall only be used in the second segment of a segmented notification. |
VSTK_RAND (36 bit) The 36-bit value that is used for derivation of a short term key VSTK, as defined in 3GPP TS 43.020. This parameter is only provided when the group call reference is present and the group call is ciphered. |
Reduced GCR (28 bits) This field contains the binary code of the group call reference together with the service flag. It is equivalent to octets 2-4 and bits 5 to 8 of octet 5 of the Reduced Group or Broadcast Call Reference information element (see sub-clause 10.5.2.63) |
Emergency_Ind This field indicates the status of the emergency mode for the group call. 0 Emergency mode not set. 1 Emergency mode set. Each Emergency_Ind that is in the List of Emergency Information is associated to a VGCS/VBS call that is in the List of Group Call NCH information. The Emergency_Ind at position (i) in the List of Emergency Information is associated with (i)th group call in the List of Group Call NCH information that contains a group channel description. |
Priority Uplink Access (1 bit) Indicates the method to be used for priority uplink access related to talker priority and sending of application data. bit When "RACH Access" is indicated, the channel to be used for priority uplink access for talker priority-related requests shall be determined from the UAI parameter in the talker priority status IE (see subclause 10.5.2.64); in the case of the sending of application data the channel to be used shall be determined from the Uplink access IE (see subclause 10.5.2.74). |
FR AMR Config (4 bit) This field indicates the set of AMR codec modes to be used on a group channel using speech full rate version 3. It is coded as the binary representation of the parameter Config-NB-Code of one of the preferred AMR configurations defined in 3GPP TS 28.062 [92] |
HR AMR Config (4 bit) This field indicates the set of AMR codec modes to be used on a group channel using speech half rate version 3. It is coded as the binary representation of the parameter Config-NB-Code of one of the preferred AMR configurations defined in 3GPP TS 28.062 [92]. |
SMS Data Confidentiality Ind (1 bit) This field shall be included if the network supports the transfer of mobile originated point-to-point short messages via the group call channel. The value is provided by the network (see 3GPP TS 43.068). bit 0 SMS data confidentiality not required. 1 SMS data confidentiality required. |
SMS Guaranteed Privacy Ind (1 bit) This field shall be included if the network supports the transfer of mobile originated point-to-point short messages via the group call channel. The value is provided by the network (see 3GPP TS 43.068). bit 0 SMS guaranteed privacy not required. 1 SMS guaranteed privacy required. |
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, notification and packet page indications applied for mobile station identities, MBMS Notifications, a segment of an ETWS Primary Notification message 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(PCH) : 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} > { null | L — Receiver compatible with earlier release | H — Additions in Release 6 : { 0 | 1 { 00 < CELL_GLOBAL_COUNT:bit(2) > | 01 < CELL_GLOBAL_COUNT:bit(2) > < VSTK_RAND : bit (36) > | 10 < Reduced_GCR : bit (28) > < VSTK_RAND : bit (36) > | 11 < CELL_GLOBAL_COUNT:bit(2) > < Reduced_GCR : bit (28) > < VSTK_RAND : bit (36) > } } { 0 | 1 — MBMS parameters included { 0 — MBMS pre-notification I 1 — MBMS notification <MBMS Notification 1 : < MBMS Channel Parameters IE > >} { 0 — MBMS pre-notification I 1 — MBMS notification <MBMS Notification 2 : { 0 | 1 < MBMS Channel Parameters IE > } > } — ‘0’indicates that the same MBMS Channel Parameters as for MBMS Notification 1 apply { 0 | 1 <MBMS Information> } } } { null | L — Receiver compatible with earlier release | H — Additions in Release 7 : { 0 | 1 <AMR Config:bit(4)> } } { null | L — Receiver compatible with earlier release | H — Additions in Release 8 < Priority Uplink Access : bit > { 0 | 1 < ETWS Primary Notification : < ETWS Primary Notification struct > > } } { null | L — Receiver compatible with earlier release | H — Additions in Release 10 < Implicit Reject CS : bit > < Implicit Reject PS : bit > } { null | L — Receiver compatible with earlier release | H — Additions in Release 11 < IPA Support : bit > } { null | L — Receiver compatible with earlier release | H — Additions in Release 13 < PEO_BCCH_CHANGE_MARK : bit (2) > < RCC : bit (3) > } { null | L — Receiver compatible with earlier release | H — Additions in Release 14 < Positioning Event Pending Indicator : bit (2) > < Enhanced Coverage Restriction Indicator : bit (2) > } { null | L — Receiver compatible with earlier release | H — Additions in Release 15 {0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } } < spare padding >; } // — truncation according to sub-clause 8.9 is allowed, bits "L" assumed |
< Priority > ::= < bit (3) >; |
< Group Call information > See sub-clause 9.1.21a |
<MBMS Information> ::= — Pre-notifications < MBMS Sessions List : < MBMS Sessions List IE > > — Notifications: listed per MBMS Channel Parameters — 1) Notifications with same MBMS Channel Parameters as in Notification 1 or Notification 2 { 0 — None | 1 { 0 | 1 } — 0: same MBMS Channel Parameters as Notification 1. — 1: same MBMS Channel Parameters as Notification 2 < MBMS Sessions List : < MBMS Sessions List IE > > } — 2) Notifications with specific MBMS Channels Parameters { 1 < MBMS Channel Parameters : < MBMS Channel Parameters IE > > < MBMS Sessions List : < MBMS Sessions List IE > > } ** 0 ; |
< ETWS Primary Notification struct> ::= {0 — First segment of ETWS Primary Notification, number of segments included < Total No Of Segments For ETWS Primary Notification : bit (4) > | 1 — Not first segment, segment number included < Segment Number : bit (4) > } < PNI: bit (1) > — identifier for segments belonging to one and the same ETWS Primary Notification message < Length Of Segment : bit (7) > — length of segment in bits < ETWS Primary Notification Data : bit (val(Length of segment)) >; < PEO IMM Cell Group Details struct > ::= — Addition in Rel-15 < PEO IMM Cell Group Identifier : bit (3) > < PEO IMM Change Mark : bit (2) >; |
NOTE: 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 NLN status(PCH) Notification List Number status The NLN status indicates the status of the content of the NOTIFICATION/NCH messages for a particular NLN value. A change of the NLN status field indicates a change of information on the NCH which is not related to new calls, as specified in sub-clause 3.3.3. Priority: Priority i relates to Mobile Identity i (i = 1, 2). If Mobile Identity i denotes an MBMS session, the corresponding Priority i field shall be ignored if present. 0 0 0 no priority applied The Packet Page Indication i field relates to Mobile 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; |
Reduced GCR (28 bits) |
VSTK_RAND (36 bits) |
CELL_GLOBAL_COUNT (2 bits) |
The MBMS Notification i structure relates to Mobile Identity i (i = 1, 2) and contains information related to a specific MBMS session. If Mobile Identity i does not denote an MBMS session or is not a TMGI of interest for the mobile station the corresponding MBMS Notification information shall be ignored. |
MBMS Sessions List |
MBMS Channel Parameters |
AMR_Config (4 bits) |
Priority Uplink Access (1 bit) This field indicates the method to be used for priority uplink access related to talker priority and sending of application data. bit When "RACH Access" is indicated, the channel to be used for priority uplink access for talker priority-related requests shall be determined from the UAI parameter in the talker priority status IE (see subclause 10.5.2.64); in the case of the sending of application data the channel to be used shall be determined from the Uplink access IE (see subclause 10.5.2.74). This bit shall be ignored by mobiles which do not support group receive mode. |
Total No Of Segments For ETWS Primary Notification (4 bits) Bits 4 3 2 1 0 0 0 0 reserved 0 0 0 1 one segment 0 0 1 0 two segments . . . 1 1 1 1 fifteen segments |
Segment Number (4 bits) Bits 4 3 2 1 0 0 0 0 reserved 0 0 0 1 reserved 0 0 1 0 second segment 0 0 1 1 third segment . . . 1 1 1 1 fifteenth segment |
PNI, Primary Notification Identifier (1 bit) |
Length Of Segment (7 bits) |
ETWS Primary Notification Data (n*8 bits) |
Implicit Reject CS (1 bit) Implicit Reject PS (1 bit) |
IPA_Support (1 bit) 0 IMMEDIATE PACKET ASSIGNMENT message is not supported PEO_BCCH_CHANGE_MARK (2 bits) This field is incremented every time one or more SI messages have changed. An exception is when EAB is enabled for a given set of PLMNs (see sub-clause 10.5.2.37m) and changes are made only to the EAB Authorization Mask and EAB Subcategory fields corresponding to this set of PLMNs in which case the PEO_BCCH_CHANGE_MARK field is not incremented (i.e. the network shall use the PEO_BCCH_CHANGE_MARK field to indicate when EAB has been enabled/disabled or when the set of PLMNs affected by EAB has changed). It is only used by a MS that has enabled PEO. In order for mobile stations that have negotiated the longest eDRX cycle to detect a change in PEO BCCH CHANGE MARK the network should not increment this field more frequently than three times per 24 hour period. RCC (3 bits) See sub-clause 10.5.2.16. Positioning Event Pending Indicator (2 bit) This field is a 2 bit bitmap indicating whether or not a paging request is sent due to a pending positioning event for the MS identified by the Mobile Identity 1 and Mobile Identity 2 fields. Bit 2 1 x 0 Page not sent for Mobile Identity 1 due to a pending positioning event 0 x Page not sent for Mobile Identity 2 due to a pending positioning event Enhanced Coverage Restriction Indicator (2 bits) See Table 9.1.63.2. PEO IMM Cell Group Details struct This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). PEO IMM Cell Group Identifier (3 bits) See sub-clause 10.5.2.16. PEO IMM Change Mark (2 bits) See sub-clause 10.5.2.16. |
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, MBMS Notification 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(PCH) : bit (2)> <NLN status(PCH) : bit>} {L I H <Priority1 ::= Priority>} {L I H <Priority2 ::= Priority>} {L I H <Priority3 ::= Priority>} < Packet Page Indication 3 : {L | H} > { null | L — Receiver compatible with earlier release | H — Additions in Release 6 : { 0 I 1 — MBMS parameters included { 0 — MBMS pre-notification I 1 — MBMS notification <MBMS Notification 3 : < MBMS Channel Parameters IE > > } { 0 | 1 < MBMS Information > } } } { null | L — Receiver compatible with earlier release | H — Additions in Release 10 < Implicit Reject CS : bit > < Implicit Reject PS : bit > } { null | L — Receiver compatible with earlier release | H — Additions in Release 11 < IPA Support : bit > } { null | L — Receiver compatible with earlier release | H — Additions in Release 13 < PEO_BCCH_CHANGE_MARK : bit (2) > < RCC : bit (3) > } { null | L — Receiver compatible with earlier release | H — Additions in Release 14 < Positioning Event Pending Indicator : bit (3) > < Enhanced Coverage Restriction Indicator : bit (3) > } { null | L — Receiver compatible with earlier release | H — Additions in Release 15 {0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } } } // — truncation according to sub-clause 8.9 is allowed, bits ‘L’ assumed <Priority> ::= <bit(3)>; <MBMS Information> ::= — Pre-notifications < MBMS Sessions List : < MBMS Sessions List IE > > — Notifications: listed per MBMS Channel Parameters — 1) Notifications with same MBMS Channel Parameters as in Notification 3 { 0 — None | 1 — Same MBMS Channel Parameters as Notification 3 < MBMS Sessions List : < MBMS Sessions List IE > > } — 2) Notifications with specific MBMS Channels Parameters { 1 < MBMS Channel Parameters : < MBMS Channel Parameters IE > > < MBMS Sessions List : < MBMS Sessions List IE > > } ** 0 ; < PEO IMM Cell Group Details struct > ::= — Addition in Rel-15 < PEO IMM Cell Group Identifier : bit (3) > < PEO IMM Change Mark : bit (2) >; |
NOTE: 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). If Mobile Identity 3 denotes an MBMS session, the CN3 field shall be ignored if present. NLN(PCH) Notification List Number NLN status(PCH) Notification List Number status See P1 Rest Octets. Priority: Priority i relates to Mobile Identity i (i = 1, 2, 3). If Mobile Identity 3 denotes an MBMS session, the corresponding Priority 3 field shall be ignored if present. 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 3 field relates to Mobile 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; |
The MBMS Notification 3 field relates to Mobile Identity 3 and contains information related to a specific MBMS session. If Mobile Identity 3 does not denote an MBMS session or is not a TMGI of interest for the mobile station the corresponding MBMS Notification information shall be ignored. See Table 10.5.2.23.1: "P1 Rest Octets information element" for the definitions of IEs used for MBMS related information. |
Implicit Reject CS (1 bit) Implicit Reject PS (1 bit) |
IPA_Support (1 bit) PEO_BCCH_CHANGE_MARK (2 bit) See P1 Rest Octets IE, sub-clause 10.5.2.23. RCC (3 bit) See sub-clause 10.5.2.16. Positioning Event Pending Indicator (3 bit) This field is a 3 bit bitmap indicating whether or not a paging request is sent due to a pending positioning event for the MS identified by the Mobile Identity 1, Mobile Identity 2 and Mobile Identity 3 fields. Bit 3 2 1 x x 0 Page not sent for Mobile Identity 1 due to a pending positioning event x 0 x Page not sent for Mobile Identity 2 due to a pending positioning event 0 x x Page not sent for Mobile Identity 3 due to a pending positioning event Enhanced Coverage RestrictionIndicator (3 bits) This field is a 3 bit bitmap indicating whether or not the use of enhanced coverage is restricted for the MS identified by the Mobile Identity 1, Mobile Identity 2 and Mobile Identity 3 fields. Bit 3 2 1 x x 0 Restricted use of enhanced coverage for Mobile Identity 1 x x 1 No restriction on use of enhanced coverage for Mobile Identity 1 x 0 x Restricted use of enhanced coverage for Mobile Identity 2 x 1 x No restriction on use of enhanced coverage for Mobile Identity 2 0 x x Restricted use of enhanced coverage for Mobile Identity 3 1 x x No restriction on use of enhanced coverage for Mobile Identity 3 PEO IMM Cell Group Details struct This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). PEO IMM Cell Group Identifier (3 bits) See sub-clause 10.5.2.16. PEO IMM Change Mark (2 bits) See sub-clause 10.5.2.16. |
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(PCH) : bit (2) > < NLN status(PCH) : bit >} {L I H < Priority1 ::= Priority >} {L I H < Priority2 ::= Priority >} {L I H < Priority3 ::= Priority >} {L I H < Priority4 ::= Priority >} { null | L — Receiver compatible with earlier release | H — Additions in Release 10 < Implicit Reject CS : bit > < Implicit Reject PS : bit > } { null | L — Receiver compatible with earlier release | H — Additions in Release 11 < IPA Support : bit > } { null | L — Receiver compatible with earlier release | H — Additions in Release 13 < PEO_BCCH_CHANGE_MARK : bit (2) > < RCC : bit (3) > } { null | L — Receiver compatible with earlier release | H — Additions in Release 14 < Positioning Event Pending Indicator : bit (4) > < Enhanced Coverage Restriction Indicator : bit (4) > } { null | L — Receiver compatible with earlier release | H — Additions in Release 15 {0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } } < spare padding >; } // — truncation according to sub-clause 8.9 is allowed, bits ‘L’ assumed < Priority > ::= < bit(3) >; < PEO IMM Cell Group Details struct > ::= — Addition in Rel-15 < PEO IMM Cell Group Identifier : bit (3) > < PEO IMM Change Mark : bit (2) >; |
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 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 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(PCH) Notification List Number See P1 Rest Octets |
NLN status(PCH) Notification List Number status See P1 Rest Octets. |
Priority: Priority i relates to Mobile Station Identity i 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 |
Implicit Reject CS (1 bit) Implicit Reject PS (1 bit) |
IPA_Support (1 bit) |
PEO_BCCH_CHANGE_MARK (2 bit) See P1 Rest Octets IE, sub-clause 10.5.2.23. RCC (3 bit) See sub-clause 10.5.2.16. Positioning Event Pending Indicator (4 bit) This field is a 4 bit bitmap indicating whether or not a paging request is sent due to a pending positioning event for the MS identified by the Mobile Identity 1, Mobile Identity 2, Mobile Identity 3 and Mobile Identity 4 fields. Bit 4 3 2 1 x x x 0 Page not sent for Mobile Identity 1 due to a pending positioning event x x 0 x Page not sent for Mobile Identity 2 due to a pending positioning event x 0 x x Page not sent for Mobile Identity 3 due to a pending positioning event 0 x x x Page not sent for Mobile Identity 3 due to a pending positioning event Enhanced Coverage Restriction Indicator (4 bits) This field is a 4 bit bitmap indicating whether or not the use of enhanced coverage is restricted for the MS identified by the Mobile Identity 1, Mobile Identity 2, Mobile Identity 3 and Mobile Identity 4 fields. Bit 4 3 2 1 x x x 0 Restricted use of enhanced coverage for Mobile Identity 1 x x x 1 No restriction on use of enhanced coverage for Mobile Identity1 x x 0 x Restricted use of enhanced coverage for Mobile Identity 2 x x 1 x No restriction on use of enhanced coverage for Mobile Identity2 x 0 x x Restricted use of enhanced coverage for Mobile Identity 3 x 1 x x No restriction on use of enhanced coverage for Mobile Identity3 0 x x x Restricted use of enhanced coverage for Mobile Identity 4 1 x x x No restriction on use of enhanced coverage for Mobile Identity4 PEO IMM Cell Group Details struct This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). PEO IMM Cell Group Identifier (3 bits) See sub-clause 10.5.2.16. PEO IMM Change Mark (2 bits) See sub-clause 10.5.2.16. |
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 45.010. Range: 0 to 7 |
The TSC field (3 bit) is the binary representation of the training sequence code as defined in 3GPP TS 45.002. |
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 44.060. 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 45.002. 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 or to indicate that no Temporary Block Flow is allocated for the case where an IMMEDIATE ASSIGNMENT message is sent in response to an EGPRS MULTILATERATION REQUEST message indicating ‘Access Burst method’ or ‘Extended Access Burst method’ (see sub-clause 3.5.2.1.2 and sub-clause 3.11).
This information element also indicates:
– whether the IMMEDIATE ASSIGNMENT message identifies a mobile station in the IA Rest Octets information elements for the assignment of a downlink TBF; 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, 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 |
NRA |
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) |
Downlink : Downlink TBF assignment to the mobile station identified in the IA Rast Octets IE (octet 1, bit 2) |
TMA : Two-message assignment (octet 1, bit 3) NRA (No Resource Allocated): This field is used to indicate when neither a TBF nor a dedicated resource is allocated by the IMMEDIATE ASSIGNMENT message (octet 1, bit 4). The coding of this field is given by Table 10.5.2.2.25b.2. |
Table 10.5.2.25b.2: Dedicated mode or TBF information element:
T/D, downlink, TMA and NRA fields
NRA |
TMA |
downlink |
T/D |
Description |
---|---|---|---|---|
0 |
0 |
0 |
0 |
This message assigns a dedicated mode resource |
0 |
0 |
1 |
0 |
Not used (Note 1) |
0 |
1 |
0 |
0 |
Not used (Note 1) |
1 |
1 |
0 |
Not used (Note 1) |
|
0 |
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 |
0 |
1 |
1 |
This message assigns a downlink TBF to the mobile station identified in the IA Rest Octets IE |
0 |
1 |
0 |
1 |
This message is the first message of two in a two-message assignment of an uplink TBF |
0 |
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 |
1 |
0 |
0 |
0 |
When the IMMEDIATE ASSIGNMENT message is sent in response to an EGPRS MULTILATERATION REQUEST message indicating ‘Access Burst method’ or ‘Extended Access Burst method’ (see sub-clause 3.5.2.1.2 and sub-clause 3.11) the NRA bit shall be set to ‘1’ thereby indicating that no TBF or dedicated mode resources are allocated by the message. If a TBF is allocated by the IMMEDIATE ASSIGNMENT message then this bit shall be set to ‘0’. |
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 < reserved > — The value ’10’ was allocated in an earlier version of the protocol and shall not be used. | 11 < reserved > — The value ’11’ was allocated in an earlier version of the protocol and shall not be used. | 00 { 0 < Multiple TBF Allocation : Multiple TBF Allocation struct > | 1 < 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) > } { null | 0 bit** = < no string > — Receiver compatible with earlier release | 1 — Additions for Rel-7 { 0 | 1 < RLC_MODE : bit (1) > } — This field may be present in case of single TBF allocation { 1 { 0 | 1< NPM Transfer Time : bit (5) > } }** 0 < Uplink EGPRS Level: < EGPRS Level IE > > { 0 | 1 < Pulse Format: < Pulse Format IE > > } { 0 — ‘0’ indicates that FANR is not activated | 1 — ‘1’ indicates that FANR is activated { 0 — SSN-based encoding is selected | 1 — Time-based encoding is selected < REPORTED TIMESLOTS : bit (8) > < TSH : bit (2) > } } { null | 0 bit** = < no string > — Receiver backward compatible with earlier version | 1 — Additions for REL-8 { 0 | 1 { 1 < Measurement_Control_E-UTRAN : bit(1) > < E-UTRAN_FREQUENCY_INDEX : bit (3) > { 1 < E-UTRAN_FREQUENCY_INDEX : bit (3) > } ** 0 } ** 0 } { 0 | 1 { 1 < Measurement_Control_UTRAN : bit(1) > < UTRAN_FREQUENCY_INDEX : bit (5) > { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 } ** 0 } { null | 0 bit** = < no string > — Receiver backward compatible with earlier version | 1 — Additions for Rel-9 { 0 < EMST_NW_Capability : bit (1) > — EMST is not used | 1 — EMST is used < RLC Entity 2 : <RLC Entity Struct> > { 0 | 1 < RLC Entity 3 : <RLC Entity Struct> > } } { null | 0 bit** = < no string > — Receiver backward compatible with earlier version | 1 — Additions for Rel-10 { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 <spare bit>** } — End of additions for Rel-10 } — End of additions for Rel-9 } — End of additions for Rel-8 } — End of additions for Rel-7 } ; — End of additions for R99 |
< Multiple TBF Allocation struct > ::= < EXTENDED_DYNAMIC_ALLOCATION : bit (1) > { 0 | 1 < P0 : bit (4) > < PR_MODE : bit(1) > } { 0 | 1 < Timeslot description : < Timeslot description struct > > { 1 < Uplink TBF Assignment : < Uplink TBF Assignment struct > > } ** 0 } ; |
< Timeslot description struct > ::= { 0 — without power control params { 0 | 1 < USF_GRANULARITY : bit(1) > } — ‘0’ means TS not assigned { 0 | 1 < USF_GRANULARITY : bit(1) > } { 0 | 1 < USF_GRANULARITY : bit(1) > } { 0 | 1 < USF_GRANULARITY : bit(1) > } { 0 | 1 < USF_GRANULARITY : bit(1) > } { 0 | 1 < USF_GRANULARITY : bit(1) > } { 0 | 1 < USF_GRANULARITY : bit(1) > } { 0 | 1 < USF_GRANULARITY : bit(1) > } | 1 — with power control params < ALPHA : bit (4) > { 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN0 : bit (5) > } { 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN1 : bit (5) > } { 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN2 : bit (5) > } { 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN3 : bit (5) > } { 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN4 : bit (5) > } { 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN5 : bit (5) > } { 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN6 : bit (5) > } { 0 | 1 < USF_GRANULARITY : bit(1) > < GAMMA_TN7 : bit (5) > } } ; |
< Uplink TBF Assignment struct > ::= — Recursive for multiple TBFs < PFI : bit (7) > < RLC_MODE : bit (1) > < UPLINK_TFI_ASSIGNMENT: bit (5) > { 0 | 1 < CHANNEL_CODING_COMMAND : bit (2) > } { 0 | 1 < EGPRS Channel Coding Command : < EGPRS Modulation and Coding Scheme IE > > } { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } { 0 < USF_ALLOCATION : bit (3) > | 1 { 1 < USF Assignment: < USF Assignment struct > > } ** 0 } ; |
< USF Assignment struct > ::= — Recursive for multiple USFs (per TBF) { 0 | 1 < USF_ALLOCATION: bit (3) > } ; — ‘0’ indicates no valid USF for this TS |
<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 — The value ‘1’ was allocated in an earlier version of the protocol and shall not be used. { 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) > } } ; |
< RLC Entity Struct > ::= < UPLINK_TFI_ASSIGNMENT : bit (5) > < RLC_MODE : bit (1) > { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } < PFI : bit (7) >; |
< Additional PFCs struct > ::= < UPLINK_TFI_ASSIGNMENT : bit (5) > { 0 | 1 < NPM Transfer Time : bit (5) > } < PFI : bit (7) >; |
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 |
USF for Timeslot Number 0 (TN0) (3 bit field) |
ALPHA (4 bit field) |
TIMESLOT_NUMBER (3 bit field) |
GAMMA_TN (5 bit field) |
P0 and PR_MODE fields |
Packet Extended Timing Advance (2 bit field) Bit |
PFI (7 bit field) This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 24.008. If EMST is used (see 3GPP TS 44.060), this field contains the PFI parameter identifying the Packet Flow Context related to the RLC entity. If EMSR is supported (see 3GPP TS 44.060), this field contains the PFI parameter identifying a Packet Flow Context supported by a specific RLC entity. |
USF_GRANULARITY (1 bit field) This field indicates the USF granularity to be applied by the mobile station when it is assigned a TBF using Dynamic Allocation, see 3GPP TS 44.060: Bit 0 the mobile station shall transmit one RLC/MAC block; |
Extension and Message escape fields RLC_MODE (1 bit field) |
Uplink EGPRS Level The coding of this information element is as the EGPRS Level IE as defined in 3GPP TS 44.060. A mobile station which does not support EGPRS2 in the uplink shall ignore this IE. NPM Transfer Time (5 bit field) This field contains the NPM Transfer Time limitation for TBF or RLC entity assigned to operate in RLC non-persistent mode, and is encoded as the NPM Transfer Time IE in 3GPP TS 44.060. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode. In case of single TBF allocation there is at most one NPM Transfer Time field. In case of multiple TBF allocation, the list of NPM Transfer Time fields is ordered as described by the loops in the Multiple TBF Allocation struct. |
FANR (1 bit field) This field indicates whether FANR is activated. This information element is defined in 3GPP TS 44.060. |
REPORTED TIMESLOTS (8 bit field) The field indicates the timeslots for which feedback is provided by a time-based encoded PAN field and is defined in 3GPP TS 44.060. |
TSH (2 bit field) This field indicates the time-shift between the most recent radio block period for which feedback information is provided and the radio block period when the bitmap is sent and is defined in 3GPP TS 44.060. |
Pulse Format This information element, if assigned, specified on which radio frequency channel the mobile station shall transmit using the narrow-band pulse option. The information element is defined in 3GPP TS 44.060. |
Measurement_Control_UTRAN (1 bit field) |
EMST_NW_Capability (1 bit field) This field indicated the network’s support of EMST. This information element is defined in 3GPP TS 44.060. |
EMSR Additional PFCs 1 EMSR Additional PFCs 2 EMSR Additional PFCs 3 These information elements are defined in 3GPP TS 44.060. |
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.
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) > 0 — The value ‘1’ was allocated in an earlier version of the protocol and shall not be used. < PR_MODE : bit (1) > } { 0 | 1 < Power Control Parameters : Power Control Parameters IE > } { 0 | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > } 0 — The value ‘1’ was allocated in an earlier version of the protocol and shall not be used. { null — Receiver compatible with earlier release | { 0 | 1 — indicates EGPRS TBF mode, see 3GPP TS 44.060 < EGPRS Window Size : < EGPRS Window Size IE >> < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > } { 0 | 1 < Packet Extended Timing Advance : bit (2) > } { null | 0 bit** = < no string > — Receiver backward compatible | 1 — Additions for REL-6 { 1 < Multiple Downlink TBF Assignment : < Multiple Downlink TBF Assignment struct > > } ** 0 { null | 0 bit** = < no string > — Receiver backward compatible with earlier release | 1 — Additions for REL-7 < FANR: bit (1) > { 1 { 0 | 1< NPM Transfer Time : bit (5) > } < EVENT_BASED_FANR: bit (1) > }** 0 < Downlink EGPRS Level: < EGPRS Level IE > > { null | 0 bit** = < no string > — Receiver backward compatible with earlier version | 1 — Additions for REL-8 { 0 | 1 { 1 < Measurement_Control_E-UTRAN : bit(1) > < E-UTRAN_FREQUENCY_INDEX : bit (3) > { 1 < E-UTRAN_FREQUENCY_INDEX : bit (3) > } ** 0 } ** 0 } { 0 | 1 { 1< Measurement_Control_UTRAN : bit(1) > < UTRAN_FREQUENCY_INDEX : bit (5) > { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 } ** 0 } { null | 0 bit** = < no string > — Receiver backward compatible with earlier version | 1 — Additions for Rel-9 { 0 — EMST is not used | 1 < RLC Entity 2 : < RLC Entity Struct > > { 0 | 1 < RLC Entity 3 : < RLC Entity Struct > > } } { null | 0 bit** = < no string > — Receiver backward compatible with earlier version | 1 — Additions for Rel-10 { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 <spare bit>** } — End of additions for Rel-10 } — End of additions for Rel-9 } — End of additions for Rel-8 } — End of additions for Rel-7 } — End of additions for Rel-6 } ; — End of additions for R99 |
< Multiple Downlink TBF Assignment struct > ::= { 0 | 1 < Uplink Control Timeslot : bit (3) > } < TIMESLOT_ALLOCATION : bit (8) > { 1 < Downlink TBF assignment : < Downlink TBF assignment struct > > } ** 0 ; |
< Downlink TBF assignment struct > :: = < PFI : bit (7) > < RLC_MODE : bit (1) > < DOWNLINK_TFI_ASSIGNMENT : bit (5) > < CONTROL_ACK : bit (1) > { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE >> } ; |
< RLC Entity Struct > ::= < DOWNLINK_TFI_ASSIGNMENT : bit (5) > < RLC_MODE : bit (1) > { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } < PFI : bit (7) >; |
< Additional PFCs struct > ::= < DOWNLINK_TFI_ASSIGNMENT : bit (5) > { 0 | 1 < NPM Transfer Time : bit (5) > } < PFI : bit (7) >; |
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 and PR_MODE fields |
Power Control Parameters IE |
DOWNLINK_TFI_ASSIGNMENT (5 bit field) |
EGPRS Window Size IE |
LINK_QUALITY_MEASUREMENT_MODE (2 bit field) |
Packet Extended Timing Advance (2 bit field) Bit |
Uplink Control Timeslot (3 bit field) This field contains the timeslot number of the timeslot where the uplink PACCH for the MS is located. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. The mobile station shall send all uplink control messages on the PACCH/U on the uplink control timeslot. If the uplink control message relates to a TBF which does not have a valid TFI on the downlink timeslot corresponding to the uplink control timeslot, it shall indicate (one of) the downlink timeslot(s) associated with that downlink TBF in the TIMESLOT_NUMBER field. The combination of downlink TFI and timeslot number enables the network to uniquely identify the TBF referred to in this message. |
PFI (7 bit field) This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 24.008. If EMST is used (see 3GPP TS 44.060), this field contains the PFI parameter identifying the Packet Flow Context related to the RLC entity. If EMSR is supported (see 3GPP TS 44.060), this field contains the PFI parameter identifying a Packet Flow Context supported by a specific RLC entity. |
NPM Transfer Time (5 bit field) This field contains the NPM Transfer Time limitation for TBF or RLC entity assigned to operate in RLC non-persistent mode, and is encoded as the NPM Transfer Time IE in 3GPP TS 44.060. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode. In case of single TBF allocation there is at most one NPM Transfer Time field. In case of multiple TBF allocation, the list of NPM Transfer Time fields is ordered as described by the loops in the Multiple Downlink TBF Assignment struct. |
EVENT_BASED_FANR (1 bit field) This field indicates whether the event-based FANR shall be used for the assigned TBF. This field shall be ignored if FANR is not activated. This information element is defined in 3GPP TS 44.060. In case of single TBF allocation there is at most one EVENT_BASED_FANR field. In case of multiple TBF allocation, the list of EVENT_BASED_FANR fields is ordered as described by the loops in the Multiple Downlink TBF Assignment struct. |
FANR (1 bit field) Downlink EGPRS Level The coding of this information element is defined in 3GPP TS 44.060. |
Measurement_Control_UTRAN (1 bit field) |
EMSR Additional PFCs 1 EMSR Additional PFCs 2 EMSR Additional PFCs 3 These information elements are defined in 3GPP TS 44.060. |
10.5.2.25e RR Packet Downlink Assignment Type 2
The RR Packet Downlink Assignment Type 2 information element is sent by the network to the mobile station to indicate the assigned downlink resources.
The RR Packet Downlink Assignment Type 2 information element is coded as shown in figure 10.5.2.25e.1 and tables 10.5.2.25e.1 and 10.5.2.25e.2.
The RR Packet Downlink Assignment Type 2 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.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
RR Packet Downlink Assignment Type 2 IEI |
octet 1 |
|||||||
Length of RR Packet Downlink Assignment Type 2 value part |
octet 2 |
|||||||
RR Packet Downlink Assignment Type 2 value part |
octet 3 – n |
Figure 10.5.2.25e.1: RR PACKET DOWNLINK ASSIGNMENT TYPE 2 information element
Table 10.5.2.25e.1: RR Packet Downlink ASSIGNMENT TYPE 2 value part
< RR Packet Downlink Assignment Type 2 value part > ::= < RLC_MODE : bit (1) > { 0 | 1 < P0_C1 : bit (4) > < PR_MODE_C1 : bit (1) > { 0 | 1 < P0_C2 : bit (4) > < PR_MODE_C2 : bit (1) > } } { 0 | 1 < Power Control Parameters C1 : < Power Control Parameters IE > > } { 0 | 1 < Power Control Parameters C2 : < Power Control Parameters IE > > } { 0 | 1 < DOWNLINK_TFI_ASSIGNMENT : bit (5) > } < EGPRS Window Size : < EGPRS Window Size IE >> < LINK_QUALITY_MEASUREMENT_MODE : bit (2) > { 0 — BTTI mode < FANR: bit (1) > { 1 < BTTI Multiple Downlink Assignment : < BTTI Multiple Downlink Assignment struct > > } ** 0 | 1 — RTTI mode { 0 — Single Carrier Assignment { 00 — Default PDCH-pair configuration | 01 — Unchanged | 10 — Explicit PDCH pair configuration < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > < UPLINK_PDCH_PAIRS_C1 : bit (8) > ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > — reserved } { 1 < RTTI Multiple Downlink Assignment SC : < RTTI Multiple Downlink Assignment SC struct > > } ** 0 | 1 — Dual Carrier Assignment { 00 — Default PDCH pair configuration | 01 — Unchanged | 10 — Explicit PDCH pair configuration < DOWNLINK_PDCH_PAIRS_C1 : bit (8) > < DOWNLINK_PDCH_PAIRS_C2 : bit (8) > < UPLINK_PDCH_PAIRS_C1 : bit (8) > < UPLINK_PDCH_PAIRS_C2 : bit (8) > ! < PDCH pairs configuration error : { 1 1 } bit (*) = < no string > — reserved } { 1 < RTTI Multiple Downlink Assignment DC : < RTTI Multiple Downlink Assignment DC struct > > } ** 0 } } < Downlink EGPRS Level: < EGPRS Level IE > > { null | 0 bit** = < no string > — Receiver backward compatible with earlier version | 1 — Additions for REL-8 { 0 | 1 { 1 < Measurement_Control_E-UTRAN : bit(1) > < E-UTRAN_FREQUENCY_INDEX : bit (3) > { 1 < E-UTRAN_FREQUENCY_INDEX : bit (3) > } ** 0 } ** 0 } { 0 | 1 { 1< Measurement_Control_UTRAN : bit(1) > < UTRAN_FREQUENCY_INDEX : bit (5) > { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 } ** 0 } { null | 0 bit** = < no string > — Receiver backward compatible with earlier release | 1 — Additions for Rel-99 { 0 — EMST is not used | 1 < RLC Entity 2 : < RLC Entity Struct > > { 0 | 1 < RLC Entity 3 : < RLC Entity Struct > > } } { null | 0 bit** = < no string > — Receiver backward compatible with earlier version | 1 — Additions for Rel-10 { 1 < EMSR Additional PFCs 1 : < Additional PFCs struct > > } ** 0 { 1 < EMSR Additional PFCs 2 : < Additional PFCs struct > > } ** 0 { 1 < EMSR Additional PFCs 3 : < Additional PFCs struct > > } ** 0 { null | 0 bit** = < no string > — Receiver backward compatible with earlier version | 1 — Additions for Rel-11 < EGPRS Packet Downlink Ack/Nack Type 3 Support : bit(1) > <spare bit>** } — End of additions for Rel-11 } — End of additions for Rel-10 } — End of additions for Rel-9 } ; — End of additions for Rel-8 |
< BTTI Multiple Downlink Assignment struct > ::= { 0 | 1 < Uplink Control Timeslot: bit (3) > } { 0 | 1 < TIMESLOT_ALLOCATION_C1 : bit (8) > } { 0 | 1 < TIMESLOT_ALLOCATION_C2 : bit (8) > } { 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; |
< RTTI Multiple Downlink Assignment SC struct > ::= < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_SC : bit (4) > { 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; |
< RTTI Multiple Downlink Assignment DC struct > ::= < RTTI_DOWNLINK_PDCH_PAIR_ASSIGNMENT_DC : bit (8) > { 1 < Downlink TBF assignment : < Downlink TBF assignment 2 struct > > } ** 0 ; |
< Downlink TBF assignment 2 struct > :: = < PFI : bit (7) > < RLC_MODE : bit (1) > < TFI Assignment : bit (5) > < CONTROL_ACK : bit (1) > { 0 | 1 < NPM Transfer Time : bit (5) > } < EVENT_BASED_FANR: bit (1) > { 0 | 1 < Downlink EGPRS Window Size : < EGPRS Window Size IE > > } ; |
< RLC Entity Struct > ::= < DOWNLINK_TFI_ASSIGNMENT : bit (5) > < RLC_MODE : bit (1) > { 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE > > } < PFI : bit (7) >; |
< Additional PFCs struct > ::= < DOWNLINK_TFI_ASSIGNMENT : bit (5) > { 0 | 1 < NPM Transfer Time : bit (5) > } < PFI : bit (7) >; |
Table 10.5.2.25e.2: RR PACKET Downlink ASSIGNMENT TYPe 2
value part details
RLC_MODE (1 bit field) |
TIMESLOT_ALLOCATION_C1, TIMESLOT_ALLOCATION_C2 (8 bit field) |
P0_C1, P0_C2, PR_MODE_C1 and PR_MODE_C2 fields |
Power Control Parameters C1, Power Control Parameters C2 |
DOWNLINK_TFI_ASSIGNMENT (5 bit field) |
EGPRS Window Size IE |
LINK_QUALITY_MEASUREMENT_MODE |
Uplink Control Timeslot (3 bit field) This field contains the timeslot number of the timeslot where the uplink PACCH for the MS is located. It is encoded as the binary representation of the timeslot number as defined in 3GPP TS 45.002. The mobile station shall send all uplink control messages on the PACCH/U on the uplink control timeslot on the same carrier as the CS timeslot. If the uplink control message relates to a TBF which does not have a valid TFI on the downlink timeslot corresponding to the uplink control timeslot, it shall indicate (one of) the downlink timeslot(s) associated with that downlink TBF in the TIMESLOT_NUMBER field. The combination of downlink TFI and timeslot number enables the network to uniquely identify the TBF referred to in this message. |
PFI (7 bit field) This field contains the PFI parameter identifying a Packet Flow Context. The PFI parameter is encoded as the contents of the PFI information element as defined in 3GPP TS 24.008. If EMST is used (see 3GPP TS 44.060), this field contains the PFI parameter identifying the Packet Flow Context related to the RLC entity. If EMSR is supported (see 3GPP TS 44.060), this field contains the PFI parameter identifying a Packet Flow Context supported by a specific RLC entity. |
EVENT_BASED_FANR (1 bit field) This field indicates whether the event-based FANR shall be used for the assigned TBF. This field shall be ignored if FANR is not activated. This information element is defined in 3GPP TS 44.060. |
DOWNLINK_PDCH_PAIRS_C1 These fields indicate the set of timeslots which make up the PDCH pairs. These fields are formatted as defined for the PACKET TIMESLOT RECONFIGURE message in 3GPP TS 44.060. |
FANR (1 bit field) Downlink EGPRS Level The coding of this information element is defined in 3GPP TS 44.060. |
Measurement_Control_UTRAN (1 bit field) |
NPM Transfer Time (5 bit field) This field contains the NPM Transfer Time limitation for TBF or RLC entity assigned to operate in RLC non-persistent mode, and is encoded as the NPM Transfer Time IE in 3GPP TS 44.060. If EMSR is supported this field contains the NPM Transfer Time limitation for a specific Packet Flow Context configured to use RLC non-persistent mode. |
EMSR Additional PFCs 1 EMSR Additional PFCs 2 EMSR Additional PFCs 3 These information elements are defined in 3GPP TS 44.060. |
EGPRS Packet Downlink Ack/Nack Type 3 Support (1 bit field) See 3GPP TS 44.060 (Packet Downlink Assignment message). |
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 1: 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. NOTE 2: This information element is ignored when receieved by a mobile station that has enabled EC operation. An MS that has enabled EC operation only attempts page reception using the EC-PCH where it can detect a paging reorganization condition as a result of re-acquiring EC-SI information (e.g. due to detecting a change in the EC-BCCH CHANGE MARK field sent in the EC-SCH). |
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.An MS supporting network sharing (see 3GPP TS 23.251 [103], 3GPP TS 45.008 [34]) shall use this parameter in the reselection procedure.
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 |
EPC mode |
FPC_EPC |
POWER LEVEL |
|||||
spare |
octet 2 |
Figure 10.5.2.28.1: Power Command information element
Table 10.5.2.28.1: Power Command information element
EPC_mode (octet 2) The EPC mode field (octet 2) indicates whether the assigned channel(s) shall be in enhanced power control (EPC) mode. It is only valid for channels on which EPC may be used. It is coded as follows: Value 0 Channel(s) not in EPC mode 1 Channel(s) in EPC mode |
FPC_EPC (octet 2) The FPC_EPC field (octet 2) has different interpretation depending on the channel mode of the assigned channed(s) and the value of the EPC mode field. If the channel mode is such that fast power control (FPC) may be used, the FPC_EPC field indicates whether Fast Measurement Reporting and Power Control mechanism is used. It is coded as follows: Value 0 FPC not in use 1 FPC in use If the channel mode is such that EPC may be used and the EPC mode field indicates that the channel is in EPC mode, the FPC_EPC field indicates whether EPC shall be used for uplink power control. It is coded as follows: Value 0 EPC not in use for uplink power control 1 EPC in use for uplink power control |
Power level (octet 2) The power level field is coded as the binary Representation of the "power control level", see 3GPP TS 3GPP TS 45.005. This value shall be used by the mobile station According to 3GPP TS 45.008. 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 |
EPC mode |
FPC_EPC |
POWER LEVEL |
|||||
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 0 Sending of Handover access is mandatory 1 Sending of Handover access is optional |
EPC_mode (octet 2) The EPC mode field (octet 2) indicates whether the assigned channel(s) shall be in enhanced power control (EPC) mode. It is only valid for channels on which EPC may be used. It is coded as follows: Value 0 Channel(s) not in EPC mode 1 Channel(s) in EPC mode |
FPC_EPC (octet 2) The FPC_EPC field (octet 2) has different interpretation depending on the channel mode of the assigned channel (s) and the value of the EPC mode field. If the channel mode is such that fast power control (FPC) may be used, the FPC_EPC field indicates whether Fast Measurement Reporting and Power Control mechanism is used. It is coded as follows: Value 0 FPC not in use 1 FPC in use If the channel mode is such that EPC may be used and the EPC mode field indicates that the channel is in EPC mode, the FPC_EPC field indicates whether EPC shall be used for uplink power control. It is coded as follows: Value 0 EPC not in use for uplink power control 1 EPC in use for uplink power control |
Power level (octet 2) The power level field is coded as the binary Representation of the "power control level", see 3GPP TS 3GPP TS 45.005. This value shall be used by the mobile station According to 3GPP TS 45.008. 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 23.022 1 The cell is barred, see 3GPP TS 23.022 |
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) Bit 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) When included in an IMMEDIATE ASSIGNMENT message sent in response to an EGPRS MULTILATERATION REQUEST message indicating ‘RLC Data Block’ method or ‘Page Response for Positioning Event’ (see sub-clause 3.5.2.1.2, sub-clause 3.11 and 3GPP TS 44.060 [76]) this field includes the 8 least significant bits of the corresponding EGPRS MULTILATERATION REQUEST message sent on the RACH (see 3GPP TS 44.060). In this case the Dedicated mode or TBF IE indicates that a Temporary Block Flow (TBF) is assigned by the IMMEDIATE ASSIGNMENT message (see sub-clause 10.5.2.25b). When included in an IMMEDIATE ASSIGNMENT message sent in response to an EGPRS MULTILATERATION REQUEST message indicating the ‘Access Burst’ method or ‘Extended Access Burst’ method this field is ignored. In this case the Dedicated mode or TBF IE indicates that no TBF or dedicated mode resources are assigned by the IMMEDIATE ASSIGNMENT message. T1′ (octet 3) T3 (octet 3 and 4) T2 (octet 4) NOTE 1: The frame number, FN modulo 42432 can be calculated as 51x((T3-T2) mod 26)+T3+51x26xT1′ |
10.5.2.30a Random Reference/ Establishment Cause
The purpose of the Random Reference/ Establishment Cause information element within Priority Uplink Request is to provide the reason for the request and a random reference to correlate a VGCS UPLINK GRANT with the PRIORITY UPLINK REQUEST message sent by a mobile station. It is based on the UPLINK ACCESS message (subclause 9.1.45).
The Random Reference/ Establishment Cause is coded as shown in figure 10.5.2.30a.1 and table 10.5.2.30a.1
The Random Reference/Establishment Cause is a type 3 information element with 1 octet length.
Establishment Cause (octet 1)
This information field indicates the reason for requesting the uplink. This field has a variable length (from 3 bits to 8 bits)
Randon Reference (octet 1)
This is an unformatted field with variable length (from 5 down to 0 bits) indicated bv ‘xxxxx’ in the table below.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Establishment Cause |
Random Reference |
octet 1 |
Figure 10.5.2.30a.1: Random Reference/Establishment Cause information element
Table 10.5.2.30a.1: Random Reference/Establishment Cause information element
Random Reference/ Establishment Cause (octet 1) Bits 8 7 6 5 4 3 2 1 1 1 0 x x x x x reserved 0 0 1 0 0 1 0 1 reserved 1 0 1 x x x x x Privilege subscriber request 1 1 1 x x x x x Emergency subscriber request 0 0 0 x x x x x Reset emergency talker indication other values reserved for future use |
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 0 1 1 Originator or talker leaving group call area 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: SI 1 Rest Octets information element details
BAND_INDICATOR (1 bit) The band indicator for 1800 and 1900 associates the ARFCN channel numbers to the GSM 1800 respectively to the PCN 1900 band, see 3GPP TS 45.005. |
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 45.002) 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 : { null | L — Receiver compatible with earlier release | H — Additions in release R5: { 0 | 1 < 3G Additional Measurement Parameters Description : < 3G Additional 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 |
< 3G Additional Measurement Parameters Description struct > ::= < FDD_Qmin_Offset : bit (3) > — FDD Parameters < FDD_RSCPmin : bit (4) > ; |
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 (no scrambling code and no SC_P_SCG), 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) |
3G Additional Measurement Parameters Description |
10.5.2.33b SI 2quater Rest Octets
The SI 2quater Rest Octets information element contains neighbour cell lists for UTRAN and/or E-UTRAN cells and/or CSG cells. For cell reselection to UTRAN, 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. For cell reselection to E-UTRAN, it is used directly to build the E-UTRAN Neighbour Cell list.
The SI 2quater Rest Octets information element is a type 5 information element with 20 octet length.
Table 10.5.2.33b.1: SI2quater Rest Octets information element
< 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 : { 0 | 1 < NC Measurement Parameters : < NC Measurement Parameters struct >> } { 0 | 1 < extension length : bit (8) > < < bit (val(extension length)+1) > & { < SI2q Extension Information > ! { Ignore: bit ** = <no string> } } > } { 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 : { null | L — Receiver compatible with earlier release | H — Additions in Rel-5: { 0 | 1 < 3G Additional Measurement Parameters Description : { 0 | 1 < 3G ADDITIONAL MEASUREMENT Parameters Description 2 : { null | L — Receiver compatible with earlier release | H — Additions in Rel-6: < 3G_CCN_ACTIVE : bit (1) > { null | L — Receiver compatible with earlier release | H — Additions in Rel-7: { 0 | 1 < 700_REPORTING_OFFSET : bit (3) > { 0 | 1 < 810_REPORTING_OFFSET : bit (3) > { null | L — Receiver compatible with earlier release | H — Additions in Rel-8 { 0 | 1 < Priority and E-UTRAN Parameters Description : < Priority and E-UTRAN Parameters Description struct >> } { 0 | 1 < 3G CSG Description : < 3G CSG Description struct >> } { 0 | 1 < E-UTRAN CSG Description : < E-UTRAN CSG Description struct >> } { null | L — Receiver compatible with earlier release | H — Additions in Rel-9 { 0 | 1 < Enhanced Cell Reselection Parameters Description : < Enhanced Cell Reselection Parameters IE >> } { 0 | 1 < CSG Cells Reporting Description : < CSG Cells Reporting Description struct >> } { null | L — Receiver compatible with earlier release | H — Additions in Rel-10 { 0 | 1 < INIT_PWR_RED : bit (1)> } < NC2_CSG_PCCN_permitted : bit (1) > } { null | L — Receiver compatible with earlier release | H — Additions in Rel-11 { 0 | 1 < Extended EARFCNs Description: < Extended EARFCNs Description struct >> } { 0 | 1 < Extended EARFCNs Description for CSG Cells: < Extended EARFCNs Description for CSG Cells 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 > ::= |
< UTRAN TDD Description struct > : := { 0 | 1 < Bandwidth_TDD : bit (3) } { 1 < Repeated UMTS TDD Neighbour Cells : Repeated UMTS TDD Neighbour Cells struct >> } ** 0 ; |
< Repeated UTRAN TDD Neighbour Cells struct > ::= — The value ‘1’ was used in an earlier version of 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) > { 1 ! < Ignore : bit = < no string >> } — this bit shall be ignored by the receiver — for backward compatibility with earlier releases { 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) > } ; |
< SI2q Extension Information > :: = { 0 | 1 < CCN Support Description : < CCN Support Description struct >> } <spare bit>** ; |
< CCN Support Description struct > ::= < Number_Cells : bit (7) > { CCN_SUPPORTED : bit } * (val(Number_Cells)) ; |
< 3G Additional Measurement Parameters Description struct > ::= < FDD_Qmin_Offset : bit (3) > — FDD information < FDD_RSCPmin : bit (4) > ; |
< 3G Additional Measurement Parameters Description 2 struct > ::= { 0 | 1 < FDD_REPORTING_THRESHOLD_2 : bit (6) > } ; — FDD information |
< Priority and E-UTRAN Parameters Description struct > ::= { 0 | 1 < Serving Cell Priority Parameters Description : < Serving Cell Priority Parameters Description struct >> } { 0 | 1 < 3G Priority Parameters Description : < 3G Priority Parameters Description struct >> } { 0 | 1 < E-UTRAN Parameters Description : < E-UTRAN Parameters Description struct >> } ; |
< Serving Cell Priority Parameters Description struct > ::= < GERAN_PRIORITY : bit(3) > < THRESH_Priority_Search : bit(4) > < THRESH_GSM_low : bit(4) > < H_PRIO : bit(2) > < T_Reselection : bit(2) >; |
< 3G Priority Parameters Description struct > ::= < UTRAN_Start : bit > < UTRAN_Stop : bit > { 0 | 1 < DEFAULT_UTRAN_PRIORITY : bit(3) > < DEFAULT_THRESH_UTRAN: bit(5) > < DEFAULT_UTRAN_QRXLEVMIN: bit(5) > } { 1 < Repeated UTRAN Priority Parameters : < Repeated UTRAN Priority Parameters struct >> } ** 0 ; |
< Repeated UTRAN Priority Parameters struct > ::= { 0 | 1 < UTRAN_PRIORITY : bit(3) > } < THRESH_UTRAN_high : bit(5) > { 0 | 1 < THRESH_UTRAN_low : bit(5) > } { 0 | 1 < UTRAN_QRXLEVMIN: bit(5) > } ; |
< E-UTRAN Parameters Description struct > ::= < E-UTRAN_CCN_ACTIVE : bit > < E-UTRAN_Start : bit > < E-UTRAN_Stop : bit > { 0 | 1 E-UTRAN Measurement Parameters Description : < E-UTRAN Measurement Parameters Description struct >> } { 0 | 1 GPRS E-UTRAN Measurement Parameters Description : < GPRS E-UTRAN Measurement Parameters Description struct >> } { 1 < Repeated E-UTRAN Neighbour Cells : < Repeated E-UTRAN Neighbour Cells struct >> } ** 0 { 1 < Repeated E-UTRAN Not Allowed Cells : < Repeated E-UTRAN Not Allowed Cells struct >> } ** 0 { 1 < Repeated E-UTRAN PCID to TA mapping : < Repeated E-UTRAN PCID to TA mapping struct >> } ** 0 ; |
< E-UTRAN Measurement Parameters Description struct > ::= < Qsearch_C_E-UTRAN_Initial : bit(4) > < E-UTRAN_REP_QUANT : bit > < E-UTRAN_MULTIRAT_REPORTING : bit(2) > { 0 { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD : bit(3) > — FDD 6 bit reporting { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD_2 : bit(6) > } { 0 | 1 < E-UTRAN_FDD_REPORTING_OFFSET : bit(3) > } } { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD : bit(3) > — TDD 6 bit reporting { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD_2 : bit(6) > } { 0 | 1 < E-UTRAN_TDD_REPORTING_OFFSET : bit(3) > } } | 1 { 0 | 1 < E-UTRAN_FDD_MEASUREMENT_REPORT_OFFSET: bit(6) > — FDD 3 bit reporting { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD_2 : bit(6) > } { 0 | 1 < E-UTRAN_FDD_REPORTING_OFFSET : bit(3) > } } { 0 | 1 < E-UTRAN_TDD_MEASUREMENT_REPORT_OFFSET: bit(6) > — TDD 3 bit reporting { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD_2 : bit(6) > } { 0 | 1 < E-UTRAN_TDD_REPORTING_OFFSET : bit(3) > } } < REPORTING_GRANULARITY : bit(1) > } ; |
< GPRS E-UTRAN Measurement Parameters Description struct > ::= < Qsearch_P_E-UTRAN : bit(4) > < E-UTRAN_REP_QUANT : bit > < E-UTRAN_MULTIRAT_REPORTING : bit(2) > { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD : bit(3) > { 0 | 1 < E-UTRAN_FDD_REPORTING_THRESHOLD_2 : bit(6) > } { 0 | 1 < E-UTRAN_FDD_REPORTING_OFFSET : bit(3) > } } { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD : bit(3) > { 0 | 1 < E-UTRAN_TDD_REPORTING_THRESHOLD_2 : bit(6) > } { 0 | 1 < E-UTRAN_TDD_REPORTING_OFFSET : bit(3) > } } ; |
< Repeated E-UTRAN Neighbour Cells struct > ::= { 0 | 1 < Measurement Bandwidth : bit (3) > } } ** 0 { 0 | 1 < E-UTRAN_PRIORITY : bit(3) > } < THRESH_E-UTRAN_high: bit(5) > { 0 | 1 < THRESH_E-UTRAN_low: bit(5) > } { 0 | 1 < E-UTRAN_QRXLEVMIN : bit(5) > }; |
< Repeated E-UTRAN Not Allowed Cells struct > ::= < Not Allowed Cells : < PCID Group IE >> { 1 < E-UTRAN_FREQUENCY_INDEX : bit(3) > } ** 0 ; |
< Repeated E-UTRAN PCID to TA mapping struct > ::= { 1 — each repetition corresponds to a different TA < PCID to TA mapping : < PCID Group IE >> — group of PCIDs belonging to the same TA } ** 0 { 1 < E-UTRAN_FREQUENCY_INDEX : bit(3) > } ** 0 ; |
< 3G CSG Description struct > ::= { 1 < CSG_PSC_SPLIT : < PSC Group IE >> { 1 < UTRAN_FREQUENCY_INDEX : bit (5) > } ** 0 } ** 0 { 1 { 0 < CSG_FDD_UARFCN : bit (14) > | 1 < CSG_TDD_UARFCN : bit (14) > } } ** 0 ; — UTRAN CSG Dedicated Frequencies |
< E-UTRAN CSG Description struct > ::= { 1 < CSG_PCI_SPLIT : <PCID Group IE >> { 1 < E-UTRAN_FREQUENCY_INDEX : bit (3) > } ** 0 } ** 0 { 1 < CSG_EARFCN : bit (16) > } ** 0 ; — E-UTRAN CSG Dedicated Frequencies |
< CSG Cells Reporting Description struct > ::= { 0 | 1 < UTRAN CSG Cells Reporting Description : < UTRAN CSG Cells Reporting Description struct >> } { 0 | 1 < E-UTRAN CSG Cells Reporting Description : <E-UTRAN CSG Cells Reporting Description struct >> } ; |
< UTRAN CSG Cells Reporting Description struct > ::= { 0 | 1 < UTRAN_CSG_FDD_REPORTING_THRESHOLD : bit (3) > < UTRAN_CSG_FDD_REPORTING_THRESHOLD_2 : bit (6) > } { 0 | 1 < UTRAN_CSG_TDD_REPORTING_THRESHOLD : bit (3) > } ; |
< E-UTRAN CSG Cells Reporting Description struct > ::= { 0 | 1 < E-UTRAN_CSG_FDD_REPORTING_THRESHOLD : bit (3) > < E-UTRAN_CSG_FDD_REPORTING_THRESHOLD_2 : bit (6) > } { 0 | 1 < E-UTRAN_CSG_TDD_REPORTING_THRESHOLD : bit (3) > < E-UTRAN_CSG_FDD_REPORTING_THRESHOLD_2 : bit (6) > } ; |
< Extended EARFCNs Description struct > ::= { 1 < EARFCN_extended : bit(18) >} ** 0 ; < Extended EARFCNs Description for CSG Cells struct > ::= { 1 < CSG_EARFCN_extended : bit(18) >} ** 0 ; |
Table 10.5.2.33b.2: SI2quater Rest Octets information element
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 (p bit field) |
|
UTRAN TDD DESCRIPTION TDD_CELL_INFORMATION (q bit field) |
|
UTRAN FDD DESCRIPTION |
|
UTRAN TDD DESCRIPTION |
|
MEASUREMENT PARAMETERS Description |
|
3G MEASUREMENT PARAMETERS Description |
|
GPRS REPORT PRIORITY Description This information is used for GPRS Enhanced (NC) Reporting when the cell has no PBCCH allocated, see 3GPP TS 44.060 sub-clause 5.6.3.5 ("Report Priority Description"). If the GPRS REPORT PRIORITY Description is included in more than one instance of the SI2quater message, the GPRS REPORT PRIORITY Description of the instance with the highest SI2quater_INDEX shall be used. 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 44.060 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 44.060 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 45.008. |
|
GPRS 3G MEASUREMENT PARAMETERS Description This information is used for GPRS 3G neighbour cell measurement when the cell has no PBCCH allocated, see 3GPP TS 44.060 sub-clause 5.6.3.6 ("GPRS Measurement Parameters and GPRS 3G Measurement Parameters"). The fields of this Description are defined in 3GPP TS 45.008. |
|
NC Measurement Parameters struct Information in this structure is used when the cell has no PBCCH allocated, for (NC) measurement reporting. See 3GPP TS 44.060 sub-clause 5.6.1 ("Network Control (NC) measurement reporting"). Coding of the fields is defined in 3GPP TS 44.060, sub-clause 11.2.23 ("PACKET SYSTEM INFORMATION TYPE5"). |
|
CCN Support Description CCN_SUPPORTED bit: This information is used for determining whether the mobile station shall enter CCN mode when re-selecting a cell and CCN is enabled, see 3GPP TS 44.060. If the CCN Support Description is included in more than one instance of the SI2quater message, the CCN Support Description of the instance with the highest SI2quater_INDEX shall be used. The use of these bits is described in sub-clause 3.4.1.2.1.8("’CCN Support description’"). |
|
3G Additional Measurement Parameters Description |
|
3G_CCN_ACTIVE (1 bit field) 0 CCN towards 3G cells is disabled in the cell. |
|
3G Additional Measurement Parameters Description 2 |
|
700_REPORTING_OFFSET (3 bit field) |
|
810_REPORTING_OFFSET (3 bit field) |
|
Serving Cell Priority Parameters |
|
3G Priority Parameters Description UTRAN_Start (1 bit field) DEFAULT_UTRAN_PRIORITY (3 bit field) Any parameter present overwrites any old data held by the mobile station for these parameters. |
|
Repeated UTRAN Priority Parameters UTRAN_FREQUENCY_INDEX (5 bit field) UTRAN_PRIORITY (3 bit field) These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. These values apply to each of the frequencies indexed within this structure. Any parameter present overwrites any old data held by the mobile station for these parameters. |
|
E-UTRAN Parameters Description If E-UTRAN cells or frequencies are included in the neighbour cell list, this information element shall be included in the message. E-UTRAN_CCN_ACTIVE (1 bit field) 0 The broadcast E-UTRAN_CCN_ACTIVE parameter shall apply if available. Otherwise, CCN towards E-UTRAN cells is disabled in the cell. 1 CCN towards E-UTRAN cells is enabled in the cell. E-UTRAN_Start (1 bit field) |
|
E-UTRAN Measurement Parameters Description If the E-UTRAN MeasurementParameters Description is included in more than one instance of the SI2quater message, the E-UTRAN MeasurementParameters Description of the instance with the highest SI2quater_INDEX shall be used. Qsearch_C_E-UTRAN_Initial (4 bit field) If both TDD and FDD frequencies are provided in the Repeated E-UTRAN Neighbour Cells IE and the E-UTRAN reporting thresholds are present for only one mode (i.e. TDD or FDD), then the parameter values for both modes shall be interpreted as having the same values. |
|
GPRS E-UTRAN Measurement Parameters Description If the GPRS E-UTRAN Measurement Parameters Description is included in more than one instance of the SI2quater message, the GPRS E-UTRAN Measurement Parameters Description of the instance with the highest SI2quater_INDEX shall be used. Qsearch_P_E-UTRAN (4 bit field) If both TDD and FDD frequencies are provided in the Repeated E-UTRAN Neighbour Cells IE and the E-UTRAN reporting thresholds are present for only one mode (i.e. TDD or FDD), then the parameter values for both modes shall be interpreted as having the same values. |
|
Repeated E-UTRAN Neighbour Cells If E-UTRAN cells or frequencies are included in the neighbour cell list, this information element shall be included in the message. EARFCN (16 bit field) Measurement Bandwidth (3 bit field) E-UTRAN_PRIORITY (3 bit field) These fields are used for the inter-RAT cell re-selection algorithm based on priority, as defined in 3GPP TS 45.008. These values apply to each of the EARFCN values listed within this structure. |
|
Repeated E-UTRAN Not Allowed Cells struct This structure identifies Not Allowed Cells with zero or more corresponding E-UTRAN frequency indices. If no E-UTRAN_FREQUENCY_INDEX is present, the Not Allowed Cells IE is applicable to all E-UTRAN frequencies specified in the Repeated E-UTRAN Neighbour Cells struct(s). E-UTRAN_FREQUENCY_INDEX (3 bit field) This field is defined in sub-clause 9.1.54. |
|
Not Allowed Cells |
|
PCID to TA mapping This information element is defined as the PCID Group IE described in 3GPP TS 44.060. |
|
3G CSG Description UTRAN_FREQUENCY_INDEX (5 bit field) CSG_FDD_UARFCN (14 bit field) CSG_TDD_UARFCN (14 bit field) |
|
E-UTRAN CSG Description E-UTRAN_FREQUENCY_INDEX (3 bit field) CSG_EARFCN (16 bit field) |
|
CSG_PCI_SPLIT |
|
CSG_PSC_SPLIT This information element identifies one or more primary scrambling code values for UTRAN FDD cells (see 3GPP TS 25.213) or cell parameter values for UTRAN TDD cells (see 3GPP TS 25.223) as being reserved for CSG cells. The range of reserved primary scrambling codes or cell parameters applies to all UTRAN frequencies specified in the list of frequencies. This information element is defined as the PSC Group IE described in 3GPP TS 44.060. |
|
Enhanced Cell Reselection Parameters Description This information element contains parameters for enhanced cell reselection procedures towards E-UTRAN cells, see 3GPP TS 45.008. This information element is defined as the Enhanced Cell Reselection Parameters IE described in 3GPP TS 44.060. |
|
CSG Cells Reporting Description |
|
UTRAN CSG Cells Reporting Description UTRAN_CSG_FDD_REPORTING_THRESHOLD (3 bit field) |
|
E-UTRAN CSG Cells Reporting Description E-UTRAN_CSG_FDD_REPORTING_THRESHOLD (3 bit field) |
|
INIT_PWR_RED (1 bit field) The INIT_PWR_RED field indicates whether or not a mobile station that supports the initial power reduction feature shall apply it as described in 3GPP TS 45.008. If this field is not present, no power reduction shall apply. 0 RACH power reduction, INIT_PWR_RED=10 dB 1 RACH power reduction, INIT_PWR_RED=10 dB. In case of emergency calls, no power reduction shall apply. |
|
NC2_CSG_PCCN_permitted (1 bit field) This field indicates whether a mobile station is permitted to send a PACKET CELL CHANGE NOTIFICATION message while in NC2 mode to report a detected CSG cell or hybrid cell (see 3GPP TS 44.060) |
|
This information element contains one or more EARFCNs with value > 65535. EARFCN_Extended (18 bits field) See table 9.1.54.1 for the definition of the EARFCN_extended field. Extended EARFCNs Description for CSG Cells struct This information element contains one or more E-UTRAN CSG dedicated frequencies with EARFCN value > 65535. The fields of this description are used for inter-RAT cell reselection to E-UTRAN CSG cells as defined in 3GPP TS 45.008. CSG_EARFCN_Extended (18 bits field) |
10.5.2.33c SI 2n Rest Octets
The SI 2n Rest Octets information element contains parameters affecting cell reselection for neighbouring cells.
The SI 2n Rest Octets information element is a type 5 information element with 20 octet length.
Table 10.5.2.33c.1: SI2n Rest Octets information element
< SI2n Rest Octets > ::= < BA_IND : bit (1) > < SI2n_CHANGE_MARK: bit (2) > < SI2n_INDEX : bit (4) > < SI2n_COUNT : bit (4) > < GSM Neighbour Cell Selection parameters : { 1 < GSM Neighbour Cell Selection params struct > } ** 0 > < spare padding > ; |
< GSM Neighbour Cell Selection params struct > ::= < NCELL_LIST_INDEX : bit (6) > { 0 | 1 < BSIC : bit (6) > } { 0 | 1 < CELL_BAR_ACCESS : bit (1) > < SAME_LA_AS_SERVING_CELL : bit (1) > { 0 | 1 < RXLEV_ACCESS_MIN : bit (6) > < MS_TXPWR_MAX_CCH : bit (5) > } { 0 | 1 < CBQ : bit (1) > < TEMPORARY_OFFSET : bit (3) > < PENALTY_TIME : bit (5) > } { 0 | 1 < POWER_OFFSET : bit (2) > } { 0 | 1 < GPRS Support Indicator : < GPRS Support Indicator struct > > } } ; |
<GPRS Support Indicator struct> ::= { 0 — GPRS not supported in the cell | 1 — GPRS supported in the cell < SAME_RA_AS_SERVING_CELL : bit (1) > < SI13_POSITION : bit (1) > } ; |
Table 10.5.2.33c.2: SI2n Rest Octets information element
BA_IND (1 bit), BCCH allocation sequence number indication. |
SI2n_CHANGE_MARK (2 bit field), SI2n Rest Octet Change Mark This parameter is used to indicate to the MS a change of information in the SI2n Rest Octets, as described in sub-clause 3.4.1.2.1.10, ‘GSM Neighbour Cell Selection parameters’. |
SI2n_INDEX (4 bit field) SI2n_COUNT (4 bit field) |
GSM Neighbour Cell Selection params struct General rules for handling neighbour cell parameter default values If the first neighbour cell defined in SI2n with SI2n_INDEX = 0 does not include all the parameter values, the following default values shall be used: RXLEV_ACCESS_MIN : Serving cell RXLEV_ACCESS_MIN POWER_OFFSET 0 dB GPRS Support Indicator (struct not present) : The following neighbour cells defined in the set of SI2n messages use the parameter values of the previous neighbour cell in the set of SI2n messages as their default values. This principle also applies when going from SI2n instance i over to SI2n instance i+1. |
NCELL_LIST_INDEX (6 bit field) This field indicates the index to the GSM Neighbour Cell list to identify the neighbouring cell to which the parameters are given.. BSIC (6 bit field) This optional field is needed to identify the neighbour cell in case the GSM Neighbour Cell list is only a frequency list, see 3GPP TS 44.060 sub-clause 5.6.3.2 SAME_LA_AS_SERVING_CELL (1 bit field) 0 the cell is in different location area as the serving cell SAME_RA_AS_SERVING_CELL (1 bit field) 0 the cell is in different routeing area as the serving cell For the description of the rest of the parameters in the GSM Neighbour Cell Selection params struct, see 3GPP TS 45.008. |
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 > > } <Iu Indicator> — Conditional <System Information 21 Indicator> <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 > ::= < SI2quater_POSITION : bit > ; |
<Iu Indicator> ::= <SI13alt POSITION: bit >; |
<System Information 21 Indicator> ::= L | H < SI21_POSITION : bit > ; |
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 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, CDMA2000 nor GERAN IU MODE CLASSMARK CHANGE message shall be sent with the Early classmark sending H The sending of UTRAN,CDMA2000 and GERAN IU MODE CLASSMARK CHANGE messages are controlled by the Early Classmark Sending Control parameter |
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 |
Iu Indicator |
SI13alt POSITION (1 bit field) The SI13alt POSITION field indicates the minimum schedule for where the SYSTEM INFORMATION TYPE 13alt message is sent on BCCH: 0 SYSTEM INFORMATION TYPE 13alt message is sent on BCCH Norm; |
SYSTEM INFORMATION 21 Indicator L SYSTEM INFORMATION TYPE 21 message is not available SI21_POSITION (1 bit field) 0 SYSTEM INFORMATION TYPE 21 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.35.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 according to sub-clause 8.9 is allowed, bits ‘L’ assumed |
<SI4 Rest Octets_O> ::= { <Optional selection parameters> <Optional Power offset> {L | H < GPRS Indicator >} } // ; — truncation according to sub-clause 8.9 is allowed, bits ‘L’ assumed |
<SI4 Rest Octets_S> ::= {L | H <LSA Parameters>} {L | H <Cell Identity : bit(16)>} {L | H <LSA ID information>} {L | H < CBQ3 : bit (2) > {0 | 1 < SI13alt Position : bit >}} ; |
<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) > < SI13 POSITION : bit > ; |
<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 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) |
CBQ3, Cell Bar Qualify 3 (2 bit field) |
SI13alt Position (1 bit field) The SI13alt Position field indicates the minimum schedule for where the SYSTEM INFORMATION TYPE 13alt message is sent on BCCH. Bit |
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) > } { L | H — MBMS procedures supported by the cell < DEDICATED_MODE_MBMS_NOTIFICATION_SUPPORT: bit > < MNCI_SUPPORT: bit >} { L — Receiver compatible with earlier release | H — Additions in Release 7 : { 0 | 1 <AMR Config:bit(4)> } } { H < Random bit stream : bit **> | L — Extension must be made in expanding the "L" branch with a new structure including a ‘Random bit stream’ } < spare padding >; |
<PCH and NCH info> ::= <Paging channel restructuring> <NLN(SACCH) : bit(2)> {0 I 1 <Call priority : bit (3)>} <NLN status(SACCH) : 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)>: the presence of the NLN(SACCH) field indicates that if an NCH is present, reduced NCH monitoring can be used, and gives the NLN(SACCH) value, to be used as specified in sub-clause 3.3.3. 2. For the <NLN status(SACCH) : bit >: the NLN status indicates the status of the content of the NOTIFICATION/NCH messages for a particular NLN value. A change of the NLN status field indicates a change of information on the NCH which is not related to new calls, as specified in sub-clause 3.3.3. 3. 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 If this parameter has not yet been received by the MS in the serving cell, the MS shall assume the default value of ‘000’ (5 LAPDm frames) |
BAND_INDICATOR (1 bit field) |
GPRS_MS_TXPWR_MAX_CCH (5 bits field) Range: 0 to 31. |
DEDICATED_MODE_MBMS_NOTIFICATION_SUPPORT (1 bit field) |
MNCI_SUPPORT (1 bit field) |
AMR_Config (4 bit field) |
Random bit stream |
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 described in tables 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 asdescribed in tables 10.5.2.35.1 and 10.5.2.35.2.
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 coded as shown in table 10.5.2.37a.1 and table 10.5.2.37a.2.
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) == 0000 > < bcch_type: bit (1) > | < modulus: bit (4) exclude 0000 > < relative_position: < bit (1 + val(modulus)) >> –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 45.002) 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. |
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: 1 0 0 0 0 System Information type 21 |
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 45.002) |
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 tables 10.5.2.37b.1 and 10.5.2.37b.2.
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 44.060 { 0 — PBCCH not present in cell (This shall always be indicated. See sub-clause 1.8) : < 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 44.060 < GPRS Power Control Parameters : GPRS Power Control Parameters IE > | 1 — PBCCH present in cell (This shall never be indicated. See sub-clause 1.8) : < PSI1_REPEAT_PERIOD : bit (4) > < PBCCH Description : PBCCH Description struct > } { null | L — Receiver compatible with earlier release | H — Additions in release 99 : < SGSNR : bit > { null | L — Receiver compatible with earlier release | H — Additions in release Rel-4: < SI_STATUS_IND : bit > { null | L — Receiver compatible with earlier release | H — Additions in release Rel-6: { 0 | 1 < LB_MS_TXPWR_MAX_CCH : bit (5) > } < SI2n_SUPPORT : bit(2) > { — Additions in Rel-11: < SI_CHANGE_ALT > — Additions in Rel-13: { 0 | 1 < PEO_DSC : bit (2) > < RCC : bit (3) > } { 0 | 1 < C1_DELTA_MIN : bit (2) > < C1_DELTA_MAX : bit (3) > } — Additions in Rel-14: { 0 | 1 < MTA_BITMAP : bit (4) > } < MS_ASSISTED_DCN : bit (1) > — Additions in Rel-15: { 0 | 1 < PEO IMM Cell Group Definition : < PEO IMM Cell Group Definition struct >> } — Additions in future releases shall be indicated above this line } // — truncation according to sub-clause 8.9 is allowed, bits "L" assumed } } } } < spare padding > ; |
< PBCCH Description struct > ::= < Pb : bit (4) > < TSC : bit (3) > < TN : bit (3) > { 00 — BCCH carrier | 01 < ARFCN : bit (10) > | 1 < MAIO : bit (6) > } ; < SI_CHANGE_ALT > ::= L | H ; < PEO IMM Cell Group Definition struct > ::= — Addition in Rel-15 < PEO IMM Cell Group Identifier : bit (3) > < PEO IMM Change Mark : bit (2) > < Timeout Read Complete SI : bit (2) > < BCCH Frequency List Bitmap : bit (32) > { 0 | 1 < PEO IMM Cell Group Specific Parameters : < PEO IMM Cell Group Specific Parameters struct >> }; < PEO IMM Cell Group Specific Parameters struct > ::= < Nb_NCELL : bit (4) > { < BSIC : bit (9) > { 0 | 1 < CCCH-CONF_SPECIFIC : bit (2) > } { 0 | 1 < CELL_BAR_ACCESS_SPECIFIC : bit (1) > } } * (val(Nb_NCELL)+1) ; { 0 | 1 < CCCH-CONF_DEFAULT : bit (2) > } { 0 | 1 < CELL_BAR_ACCESS_DEFAULT : bit (1) > }; |
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 44.060: 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 |
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. Range: 0 to 7. The TN field (3 bit) is the binary representation of the timeslot number for the PBCCH. 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 (1 bit field) 0 SGSN is Release ’98 or older |
SI_STATUS_IND (1 bit field) 0 The network does not support the PACKET SI STATUS message; |
LB_MS_TXPWR_MAX_CCH (5 bit field) The LB_MS_TXPWR_MAX_CCH field is coded as the binary representation of the ‘power control level’ in 3GPP TS 45.005 corresponding to the maximum TX power level a mobile station may use when accessing on a packet control channel. This value shall be used by the mobile station according to 3GPP TS 45.008. |
SI2n_SUPPORT (2 bit field) 00 SI2n is not supported |
SI_CHANGE_ALT L A mobile station supporting network sharing should not attempt to re-read the SI2quater message; PEO_DSC (2 bit field) This field provides an intial value for the downlink signalling counter (DSC) used for verifying the ongoing ability of a MS that has enabled eDRX to receive paging messages on the PCH (3GPP TS 45.008). The presence of the PEO_DSC field indicates the serving cell supports PEO. The PEO_DSC field is coded according to the following table: 00 DSC = 4 01 DSC = 6 10 DSC = 8 11 DSC = 10 RCC (3 bit) See sub-clause 10.5.2.16. C1_DELTA_MIN (2 bit field) See sub-clause 9.1.43r. C1_DELTA_MAX (3 bit field) See sub-clause 9.1.43r. MTA_BITMAP (4 bits) Bits x x 1 x MTA Access Burst method supported x 1 x x MTA Extended Access Burst method supported MS_ASSISTED_DCN 0 The network does not support MS assisted Dedicated Core Network selection; All remaining bit positions are reserved. |
PEO IMM Cell Group Definition struct This structure provides identifier, change mark indication as well as common and specific cell parameters of the PEO IMM Cell Group which the serving cell belongs to. Common cell parameters across cells in the same PEO IMM cell group are contained in the PEO IMM Cell Group Definition structure (see below) and further refer to following cell parameters outside the PEO IMM Cell Group Definition structure, if sent for the serving cell in SI2 / SI3 messages (i.e. these parameters broadcasted by the serving cell are interpreted as common parameters of the PEO IMM cell group): Common cell parameters outside the PEO IMM Cell Group Definition structure in SI13: Parameters in Neighbour Cell Description IE (sent in SI2): BCCH Frequency List : octets (16) Parameters in Control Channel Description IE (sent in SI3): CCCH-CONF : bit (3) Parameters in Cell Selection Parameters structure (sent in SI3): CELL_RESELECT_HYSTERESIS : bit (3) RXLEV_ACCESS_MIN : bit (6) MS_TXPWR_MAX_CCH : bit (5) Parameters in RACH Control Parameters structure (sent in SI3): Cell_Bar_Access : bit (1) Parameters in Selection Parameters structure (sent in SI3 rest octets ): CELL_RESELECT_OFFSET : bit (6) Parameters sent in SI13 rest octets: Routing Area Code : bit (8) LB_MS_TXPWR_MAX_CCH : bit (5) C1_DELTA_MIN : bit (2) C1_DELTA_MAX : bit (3) PEO IMM Cell Group Identifier (3 bits) This field is the binary representation of the identity of the PEO IMM cell group. Range: 0 to 7. Bits PEO IMM Change Mark (2 bits) This field is the binary representation of the PEO IMM Change Mark value N indicating the status of the PEO IMM Cell Group description, referring to parameters belonging to the PEO IMM Cell Group Definition struct and to specific parameters sent in SI3 and SI13. Range: 0 to 3. Whenever the value of parameters belonging to the PEO IMM Cell Group description is modified, the PEO IMM Change Mark value N is incremented to (N+1) modulo 4. If only parameters are modified that belong to the PEO IMM Cell Group Definition struct, neither the BCCH CHANGE MARK nor the PEO BCCH CHANGE MARK field shall be incremented by the network. BCCH Frequency List Bitmap (32 bits) |
Timeout Read Complete SI (2 bits) This field indicates the timeout for triggering the acquisition of the complete set of System Information messages in the serving cell, if the last acquisition of the complete set of System Information messages has been performed in a different cell. It is coded as follows. Bits PEO IMM Cell Group Specific Parameters struct This structure provides specific cell parameters of neighbour cells belonging to the same PEO IMM Cell Group as the serving cell. Nb_NCELL (4 bits) Bits BSIC (9 bits) CCCH-CONF_SPECIFIC (2 bits) This field indicates the number of common control channels (CCCHs) that shall be applied for each cell sharing the same PEO IMM Cell Group as the serving cell, if its BSIC is contained in the cell description of the PEO IMM Cell Group Definition struct to indicate specific parameters for that cell. It is coded as the field CCCH-CONF (sent in SI3). It overwrites the default parameter CCCH-CONF_DEFAULT for that cell. CELL_BAR_ACCESS_SPECIFIC (1 bit) This field indicates the cell barring status that shall be applied for each cell sharing the same PEO IMM Cell Group as the serving cell, if its BSIC is contained in the cell description of the PEO IMM Cell Group Definition struct to indicate specific parameters for that cell. It is coded as the field Cell_Bar_Access (sent in SI3). It overwrites the default parameter CELL_BAR_ACCESS_DEFAULT for that cell. CCCH-CONF_DEFAULT (2 bits) This field indicates the number of common control channels (CCCHs) that shall be used by default for all cells sharing the same PEO IMM Cell Group as the serving cell, if their BSIC is not contained in the cell description of the PEO IMM Cell Group Definition struct. It is coded as the field CCCH-CONF (sent in SI3). If this parameter is not broadcasted, the MS shall assume that all cells belonging to the same PEO IMM Cell Group use the same value for this parameter and the value indicated in CCCH-CONF (sent in SI3) applies. CELL_BAR_ACCESS_DEFAULT (1 bit) This field indicates the cell barring status that shall be used by default for all cells sharing the same PEO IMM Cell Group as the serving cell, if their BSIC is not contained in the cell description of the PEO IMM Cell Group Definition struct. It is coded as the field Cell_Bar_Access (sent in SI3). If this parameter is not broadcasted, the MS shall assume that all cells belonging to the same PEO IMM Cell Group use the same value for this parameter and the value indicated in Cell_Bar_Access (sent in SI3) applies. |
NOTE: The SGSN Release bit indicates the version of the SGSN specific protocols and is not applicable to access stratum protocols.
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 45.008. |
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 45.008. |
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.33 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 23.003 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 23.003. |
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 |
TIME_GROUP (2 bit field) The TIME_GROUP defines which time group (see 3GPP TS 45.002) 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 45.008). 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_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 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.37j SI 14 Rest Octets
The SI 14 Rest Octets information element contains information about dynamic ARFCN mapping. It allows to allocate ARFCN values and dynamically map them to physical frequencies, see 3GPP TS 45.005.
The SI 14 Rest Octets information element is a type 5 information element with 16 octet length.
Table 10.5.2.37j.1: SI14 message content
< SI14 Rest Octets > ::= < SI14_INDEX : bit (2) > < SI14_COUNT : bit (2) > < DM_CHANGE_MARK : bit (4) > < DYNAMIC ARFCN MAPPING Description : { 1 < DYNAMIC ARFCN MAPPING > } ** 0 > < spare padding > ; |
< DYNAMIC ARFCN MAPPING >::= < GSM_Band : bit (4) > < BAND_OFFSET : bit (10) > < ARFCN_RANGE : bit (7) > ; |
Table 10.5.2.37j.2: SI14 message information
SI14_INDEX (2 bit field) SI14_COUNT (2 bit field) This field is coded as the binary representation of the SI14_INDEX for the last (highest indexed) individual SI14 message. DM_CHANGE_MARK (4 bit field), Dynamic ARFCN Mapping Change Mark. This parameter is used to indicate to the MS a change of information concerning Dynamic ARFCN Mapping. |
Dynamic ARFCN Mapping parameters description: GSM_Band (4 bit field) Bits 4 – 1 ARFCN_FIRST (10 bit field) This parameter indicates the first ARFCN number for dynamic ARFCN mapping. BAND_OFFSET (10 bit field) This parameter indicates the first carrier, on the band concerned, for dynamic ARFCN mapping. ARFCN_RANGE (7 bit field) This parameter indicates the number of ARFCNs allocated, subsequent to ARFCN_FIRST. The use of the parameters GSM_Band, ARFCN_FIRST, BAND_OFFSET and ARFCN_RANGE is described in 3GPP TS 45.005. If the mobile station receives more than 8 DYNAMIC_ARFCN_MAPPING structures, it shall store at least the 8 first structures in the order of occurrence, starting with the SI14 instance with the lowest index number. NOTE: For important guidelines on Dynamic ARFCN mapping, see Annex "Guidance on the Usage of Dynamic ARFCN Mapping" in 3GPP TS 45.005. |
10.5.2.37k SI 15 Rest Octets
The SI 15 Rest Octets information element contains information about dynamic ARFCN mapping. It allows to allocate ARFCN values and then dynamically map to physical frequencies, see 3GPP TS 45.005.
The SI 15 Rest Octets information element is a type 5 information element with 20 octet length.
Table 10.5.2.37k.1: SI15 message content
< SI15 Rest Octets > ::= < SI15_INDEX : bit (2) > < SI15_COUNT : bit (2) > < DM_CHANGE_MARK : bit (4) > < DYNAMIC ARFCN MAPPING Description : { 1 < DYNAMIC ARFCN MAPPING > } ** 0 > < spare padding > ; |
< DYNAMIC ARFCN MAPPING >::= < GSM_Band : bit (4) > < BAND_OFFSET: bit (10) > < ARFCN_RANGE : bit (7) > ; |
Table 10.5.2.37k.2: SI15 message information
SI15_INDEX (2 bit field) SI15_COUNT (2 bit field) This field is coded as the binary representation of the SI15_INDEX for the last (highest indexed) individual SI15 message. DM_CHANGE_MARK (4 bit field), Dynamic ARFCN Mapping Change Mark. This parameter is used to indicate to the MS a change of information concerning Dynamic ARFCN Mapping. |
Dynamic ARFCN Mapping parameters description These parameters are described in table 10.5.2.37j. |
10.5.2.37l SI 13alt Rest Octets
The SI 13alt Rest Octets information element is coded according to the syntax specified below and described in tables 10.5.2.37l.1 and 10.5.2.37l.2.
The SI 13alt Rest Octets information element is a type 5 information element with 20 octets length.
Table 10.5.2.37l.1: SI 13alt Rest Octets information element content
< SI 13alt Rest Octets > ::= < PBCCH Description : < PBCCH Description 2 struct >> < spare padding > ; |
< PBCCH Description 2 struct > ::= < PSI1_REPEAT_PERIOD : bit (4) > < Pb : bit (4) > < TN : bit (3) > < PBCCH Frequency Description : < Frequency Parameters IE >> ; — Defined in 3GPP TS 44.060 |
Table 10.5.2.37l.2: SI 13alt Rest Octets information element
PSI1_REPEAT_PERIOD (4 bit field) |
Pb (4 bit field) |
TN (3 bit field) |
PBCCH Frequency Description |
10.5.2.37m SI 21 Rest Octets
The SI 21 Rest Octets information element contains Extended Access Barring information.
The SI 21 Rest Octets information element is a type 5 information element with 20 octet length.
Table 10.5.2.37m.1: SI 21 Rest Octets information element
< SI 21 Rest Octets > ::= < SI 21_CHANGE_MARK : bit (2) > < SI 21_INDEX : bit (3) > < SI 21_COUNT : bit (3) > { 0 | 1 < EAB Authorization Mask: bit (10) > < EAB Subcategory : bit (2) > } { — Additions in Release 11 { L | H < Network Sharing EAB Information : < Network Sharing EAB Information struct >> } < spare padding > } // ; — truncation according to sub-clause 8.9 is allowed, bits "L" assumed |
< Network Sharing EAB Information struct > ::= { 0 | 1 < Common PLMN PS EAB Authorization Mask : bit (10) > < Common PLMN PS EAB Subcategory : bit (2) > } < Nb_Additional_PLMNs : bit (2) > { { 0 — The previously listed EAB Authorization Mask/Subcategory apply | 1 — The indicated EAB Authorization Mask/Subcategory apply < Additional EAB Authorization Mask : bit (10) > < Additional EAB Subcategory : bit (2) > } { 0 — Domain-specific access control for EAB not in use | 1 — Domain-specific access control for EAB in use { 0 — The previously listed PS EAB Authorization Mask/Subcategory apply | 1 < PS EAB Authorization Mask : bit (10) > — The indicated PS EAB Authorization Mask/Subcategory apply < PS EAB Subcategory : bit (2) > } } } * (val(Nb_Additional_PLMNs)+1) ; |
Table 10.5.2.37m.2: SI 21 Rest Octets information element
SI 21_CHANGE_MARK (2 bit) |
SI 21_INDEX (3 bits) and SI 21_COUNT (3 bits) |
EAB Authorization Mask (10 bit) This field is a bit map that provides the list of authorized access classes for mobile stations configured for Extended Access Barring. It allows for zero, one or more access classes to be indicated as authorized and is coded as follows: bit x x x x x x x x x 1 Mobile stations configured for EAB and a member of Access Class 0 are barred x x x x x x x x 1 x Mobile stations configured for EAB and a member of Access Class 1 are barred x x x x x x x 1 x x Mobile stations configured for EAB and a member of Access Class 2 are barred ….. 1 x x x x x x x x x Mobile stations configured for EAB and a member of Access Class 9 are barred When network sharing is used, a mobile station supporting network sharing and configured for EAB shall consider this field applicable to the Common PLMN. |
EAB Subcategory (2 bit) This field identifies the targeted subcategory of mobile stations configured for EAB. It is coded as follows: 00 The EAB Authorization mask is applicable to all mobile stations configured for EAB. 01 The EAB Authorization mask is only applicable to mobile stations configured for EAB and neither in their HPLMN nor in a PLMN that is equivalent to it (see TS 22.011). 10 The EAB Authorization mask is only applicable to mobile stations configured for EAB and neither in the PLMN listed as most preferred PLMN of the country where the UE is roaming in the operator-defined PLMN selector list on the SIM/USIM, nor in their HPLMN nor in an PLMN that is equivalent to it (see TS 22.011). All other values are unused. Upon receiving a value it considers to be unused, a mobile station configured for EAB shall ignore it and shall consider itself as not being part of the targeted subcategory. When network sharing is used, a mobile station supporting network sharing and configured for EAB shall consider this field applicable to the Common PLMN. |
Nb_Additional_PLMNs (2 bit) |
Common PLMN PS EAB Authorization Mask (10 bit) and Common PLMN PS EAB Subcategory (2 bit) These fields contain the EAB Authorization Mask/Subcategory applicable to the Common PLMN for the PS domain when domain-specific access control for EAB is used. In the absence of these fields, the mobile station shall consider domain-specific access control for EAB as not used for the Common PLMN. These fields are coded as specified for the EAB Authorization Mask/Subcategory fields. |
Additional EAB Authorization Mask (10 bit) and Additional EAB Subcategory (2 bit) |
PS EAB Authorization Mask (10 bit) and PS EAB Subcategory (2 bit)These fields contain the EAB Authorization Mask/Subcategory applicable in the corresponding Additional PLMN for the PS domain when domain-specific access control for EAB is used. In the absence of these fields and if domain-specific access control is indicated as used for this Additional PLMN, the previously listed PS EAB Authorization Mask/Subcategory fields in this message shall be used instead (see sub-clause 3.8.3), or if no such fields exist, the Common PS EAB Authorization Mask/Subcategory fields shall apply. These fields are coded as specified for the EAB Authorization Mask/Subcategory fields. |
10.5.2.37n SI 22 Rest Octets
The SI 22 Rest Octets information element contains network sharing and domain-specific access control information.
The SI 22 Rest Octets information element is a type 5 information element with 20 octet length.
Table 10.5.2.37n.1: SI 22 Rest Octets information element
< SI 22 Rest Octets > ::= < SI 22_CHANGE_MARK : bit (2) > < SI 22_INDEX : bit (3) > < SI 22_COUNT : bit (3) > { 0 | 1 < Network Sharing Information : < Network Sharing Information struct >> } < spare padding > ; < Network Sharing Information struct > ::= < SI23 Indicator : bit > < Common_PLMN_Allowed : bit > { 0 | 1 < Common_PLMN_PS_ACC : bit(16) > } < Nb_Additional_PLMNs : bit (2) > { { 0 | 1 < MCC : bit (12) > } < MNC : bit (12) > < NCC Permitted : bit (8) > { 0 — The previously listed Access Control Class bitmap applies | 1 — The indicated Access Control Class bitmap applies < Additional_ACC: bit (16) > } { 0 — Domain-specific access control not in use | 1 — Domain specific access control in use { 0 — The previously listed PS Access Control Class bitmap applies | 1 < PS_ACC: bit(16) > } — The indicated PS Access Control Class bitmap applies } } * ( val (Nb_Additional_PLMNs)+1) ; |
Table 10.5.2.37n.2: SI 22 Rest Octets information element
SI 22_CHANGE_MARK (2 bit) |
SI 22_INDEX (3 bits) and SI 22_COUNT (3 bits) |
SI23 Indicator (one bit field) Bit |
Common_PLMN_Allowed (one bit field) Bit |
Common_PLMN_PS_ACC (16 bit field) Bits |
Nb_Additional_PLMNs (2 bit field) Value |
MCC and MNC (24 bit field) This field contains the PLMN ID for each Additional PLMN. If for a given MNC the MCC field is missing, the previously listed MCC in this message shall be used instead (see sub-clause 3.8.3), or if no such exists, the MCC provided as part of the Location Area Identification IE in SI3 and SI4 shall be used instead. The MCC and MNC value field is coded as specified in sub-clause 10.5.3. |
NCC Permitted (8 bit field)The purpose of this field is to provide for each Additional PLMN the list of allowed NCCs on the BCCH carriers to be reported in the MEASUREMENT REPORT message by the mobile station in the cell. The NCC Permitted value field is coded as the value part of the NCC Permitted IE specified in sub-clause 10.5.2.27 |
Additional_ACC (16 bit field) This field contains a bitmap indicating the barring status for access control classes 0 to 15 (AC C0 to AC C15), applicable in the corresponding Additional PLMN. Each AC CN is coded as the AC CN in the RACH Control Parameters IE (see sub-clause 10.5.2.29). In the absence of this field, the previously listed Additional_ACC field in this message shall be used instead (see sub-clause 3.8.3), or if no such field exists, the AC CN in the RACH Control Parameters IE shall apply. If domain-specific access control is used for this Additional PLMN, this field (and absence thereof) applies to CS domain only, otherwise to both CS and PS domains. The Additional_ACC field is coded as follows. Bits |
PS_ACC (16 bit field) This field contains a bitmap indicating the barring status for access control classes 0 to 15 (AC C0 to AC C15), applicable in the corresponding Additional PLMN for the PS domain when domain-specific access control is used. Each AC CN is coded as the AC CN in the RACH Control Parameters IE (see sub-clause 10.5.2.29). In the absence of this field and if domain-specific access control is indicated as used for this Additional PLMN, the previously listed PS_ACC field in this message shall be used instead (see sub-clause 3.8.3), or if no such field exists, the Common_PLMN_PS_ACC field shall apply. The PS_ACC field is coded as follows. Bits |
10.5.2.37o SI 23 Rest Octets
The SI 23 Rest Octets information element contains inter RAT cell reselection information related to network sharing.
The SI 23 Rest Octets information element is a type 5 information element with 20 octet length.
Table 10.5.2.37o.1: SI 23 Rest Octets information element
< SI 23 Rest Octets > ::= < SI 23_BA_IND : bit (1) > < SI 23_CHANGE_MARK : bit (2) > < SI 23_INDEX : bit (3) > < SI 23_COUNT : bit (3) > { 0 | 1 < IRAT Cell Reselection Information : < IRAT Cell Reselection Information struct >> } < spare padding > ; < IRAT Cell Reselection Information struct > ::= { < Priority and UTRAN Parameters Description for the Common PLMN : < Priority and UTRAN Parameters Description struct >> } { < Priority and E-UTRAN Parameters Description for the Common PLMN : < Priority and E-UTRAN Parameters Description struct >> } < Nb_Additional_PLMNs : bit (2) > { < PLMN index : bit (2) > { < Priority and UTRAN Parameters Description : < Priority and UTRAN Parameters Description struct >> } { < Priority and E-UTRAN Parameters Description : < Priority and E-UTRAN Parameters Description struct >> } } * ( val (Nb_Additional_PLMNs)+1) ; |
< Priority and UTRAN Parameters Description struct > ::= { 0 — Inter RAT Cell Reselection information for UTRAN not provided for the corresponding PLMN | 1 { 0 — UTRAN default threshold information not provided for the corresponding PLMN | 1 { 0 | 1 < DEFAULT_UTRAN_PRIORITY : bit(3) > } { 0 | 1 < DEFAULT_THRESH_UTRAN_low : bit(5) > } { 0 | 1 < DEFAULT_UTRAN_QRXLEVMIN : bit(5) > } } { 0 | 1 < UTRAN FDD/TDD Description : < UTRAN FDD/TDD Description struct >> } } ; |
< UTRAN FDD/TDD Description struct > ::= {{ 0 | 1 < Bandwidth_FDD : bit (3) > } | { 0 | 1 < Bandwidth_TDD : bit (3) > }} { 1 < Repeated UTRAN FDD/TDD Neighbour Frequency and Priority : < Repeated UTRAN FDD/TDD Neighbour Frequency and Priority struct >> } ** 0 ; |
< Repeated UTRAN FDD/TDD Neighbour Frequency and Priority struct > ::= { 1 < UTRAN-ARFCN : bit (14) > } ** 0 { 0 | 1 < UTRAN_PRIORITY : bit(3) > } < THRESH_UTRAN_high : bit(5) > { 0 | 1 < THRESH_UTRAN_low : bit(5) > } { 0 | 1 < UTRAN_QRXLEVMIN: bit(5) > } ; |
< Priority and E-UTRAN Parameters Description struct > ::= { 0 — Inter RAT Cell Reselection information for E-UTRAN not provided for the corresponding PLMN | 1 { 0 — E-UTRAN threshold information not provided for the corresponding PLMN | 1 { 0 | 1 < DEFAULT_E-UTRAN_PRIORITY: bit(3) > } { 0 | 1 < DEFAULT_THRESH_E-UTRAN_low: bit(5) > } { 0 | 1 < DEFAULT_E-UTRAN_QRXLEVMIN : bit(5) > } } { 1 < Repeated E-UTRAN Neighbour Frequency and Priority : < Repeated E-UTRAN Neighbour Frequency and Priority struct >> } ** 0 { 1 < Repeated E-UTRAN Not Allowed Cells : < Repeated E-UTRAN Not Allowed Cells struct >> } ** 0 { 1 < Repeated E-UTRAN PCID to TA mapping : < Repeated E-UTRAN PCID to TA mapping struct >> } ** 0 { 0 | 1 < Enhanced Cell Reselection Parameters Description : < Enhanced Cell Reselection Parameters IE >> } } ; |
< Repeated E-UTRAN Neighbour Frequency and Priority struct > ::= { 0 | 1 < Measurement Bandwidth : bit (3) > }} ** 0 { 0 | 1 < E-UTRAN_PRIORITY : bit(3) > } < THRESH_E-UTRAN_high: bit(5) > { 0 | 1 < THRESH_E-UTRAN_low : bit(5) > } { 0 | 1 < E-UTRAN_QRXLEVMIN : bit(5) > }; |
Table 10.5.2.37o.2: SI 23 Rest Octets information element
SI 23_BA_IND (1 bit), 3G BCCH allocation sequence number indication. |
SI 23_CHANGE_MARK (2 bit) |
SI 23_INDEX (3 bits) and SI 23_COUNT (3 bits) |
IRAT Cell Reselection Information: |
Priority and UTRAN Parameters Description for the Common PLMN: |
Priority and E-UTRAN Parameters Description for the Common PLMN: |
Nb_Additional_PLMNs (2 bit) |
PLMN Index (2 bit) Value Priority and UTRAN Parameters Description: Priority and E-UTRAN Parameters Description: |
Priority and UTRAN Parameters Description: DEFAULT_UTRAN_PRIORITY (3 bit) UTRAN_FDD/TDD_Description: Repeated UTRAN FDD/TDD Neighbour Frequency and Priority |
Priority and E-UTRAN Parameters Description: DEFAULT_E-UTRAN_PRIORITY (3 bit) Repeated E-UTRAN Neighbour Frequency and Priority: Repeated E-UTRAN Not Allowed Cells: Repeated E-UTRAN PCID to TA mapping: Enhanced Cell Reselection Parameters Description: |
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 1: The frame number, FN modulo 42432 can be calculated as 51x((T3-T2) mod 26)+T3+51x26xT1′ |
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 seconds. 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 42432 <= 31623, the indicated time is the next time when FN mod 42432 is equal to ST;
if 32024 <= (ST-T) mod 42432 <= 42431, 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:
31624 <= (ST-T) mod 42432 <= 32023.
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 and Mobile Time Difference on Hyperframe level IE shall not be included in the HANDOVER COMPLETE message 1 Mobile Time Difference IE and Mobile Time Difference on Hyperframe level IE shall be included in the HANDOVER COMPLETE message SI: Synchronization indication (octet 1) Bit 2 1 0 0 Non-synchronized 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 45.010.
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.42b VGCS Ciphering Parameters
The VGCS Ciphering parameters information element is a type 4 information element with 3-15 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||||
VGCS Ciphering Parameters IEI |
octet 1 |
|||||||||||
Length of VGCS Ciphering Parameters |
octet 2 |
|||||||||||
Spare |
RAND_IND |
LAC_IND |
CELL_IND |
B22 COUNT |
CELL_GLOBAL_COUNT |
octet 3 |
||||||
Cell Identity |
Octet 4(Optional) |
|||||||||||
Octet 5 |
||||||||||||
Location Area Identification |
Octet m (optional) |
|||||||||||
Octet m+4 |
||||||||||||
VSTK_RAND |
Octet n (Optional) |
|||||||||||
VSTK_RAND |
||||||||||||
VSTK_RAND |
||||||||||||
VSTK_RAND |
||||||||||||
VSTK_RAND |
Spare |
Octet n + 4 (Optional) |
Figure 10.5.2.42b.1: VGCS Ciphering Parameters Information Element
Table 10.5.2.42b.1: VGCS Ciphering Parameters Information Element
CELL_GLOBAL_COUNT (octet 3) B22_COUNT (octet 3) This field contains the value of bit 22 of COUNT (see 3GPP TS43.020) corresponding to the moment when the value of <CELL_GLOBAL_COUNT> was valid. CELL_IND (Octet 3) Bit LAC_IND (Octet 3) Bit RAND_IND (Octet 3) Bit Cell Identity (octets 4 and 5) The purpose of the Cell Identity is to identify a cell within a location area (see sub-clause 10.5.1.1). Location Area Identification (octets m to m+4) The purpose of the Location Area Identification is to provide the identity of the location area. The Location Area Identification is coded as in sub-clause 9.1.40.2. VSTK_RAND (octets n to n+4) The purpose of this field is to provide the VSTK_RAND, as defined in 3GPP TS 43.020. |
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.
11) 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.
12) For <cell reselect hysteresis : bit(3)>: see sub-clause 10.5.2.4.
13) For <ms txpwr max cch : bit(5)>: see sub-clause 10.5.2.4.
14) For <rxlev access min : bit(6)> see sub-clause 10.5.2.4.
15) For <cell reselect offset : bit(6)>: see sub-clause 10.5.2.35.
16) For <temporary offset : bit(3)>: see sub-clause 10.5.2.35.
17) 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). |
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 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 All other cause values shall be treated as 0000 0000 |
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 |
octet 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 44.031)/ LCS 0 0 0 1 ETWS (3GPP TS 23.041) 0 0 1 0 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 |
octet 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 44.006).
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 ETWS ETWS Primary Notification message in 3GPP TS 23.041 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 station when performing handover to UTRAN or CS to PS SRVCC to UTRAN (HSPA). The Handover to UTRAN Command information element contains all information needed by the mobile station when performing handover to UTRAN and part of information needed by the mobile station when performing CS to PS SRVCC to UTRAN (HSPA).
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 (void)
10.5.2.57 Service Support
The Service Support information element provides information about which services the mobile station supports.
The Service Support information element is coded as shown in figure 10.5.2.57.1 and table 10.5.2.57.1.
The Service Support is a type 3 information element with 2 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Service Support IEI |
octet 1 |
|||||||
Spare |
Spare |
Spare |
Spare |
Spare |
Spare |
MBMS Multicast |
MBMS Broadcast |
octet 2 |
Figure 10.5.2.57.1: Service Support information element
Table 10.5.2.57.1: Service Support information element format
Last Segment (octet 2) bit 1 0 mobile station does not require notification of broadcast MBMS services 1 mobile station requires notification of broadcast MBMS services bit 2 0 mobile station does not require notification of multicast MBMS services 1 mobile station requires notification of multicast MBMS services |
10.5.2.58 MBMS p-t-m Channel Description
The MBMS p-t-m Channel Description information element is sent by the network to the mobile station to indicate part of the preassigned resources for an MBMS service (see 3GPP TS 44.060). The remaining part is included in the MBMS Session Parameters List information element (see sub-clause 10.5.2.58a).
The MBMS p-t-m Channel Description information element is coded as shown in figure 10.5.2.58.1 and table 10.5.2.58.1 and table 10.5.2.58.2.
The MBMS p-t-m Channel Description is a type 4 information element with a minimum length of 4 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006).
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
MBMS p-t-m Channel Description IEI |
octet 1 |
|||||||
Length of MBMS p-t-m Channel Description value part |
octet 2 |
|||||||
MBMS p-t-m Channel Description value part |
octet 3 – n |
Figure 10.5.2.58.1: MBMS p-t-m Channel Description information element
Table 10.5.2.58.1: MBMS p-t-m Channel Description value part
< MBMS p-t-m Channel Description value part > ::= < MBMS p-t-m Channel Description : < MBMS p-t-m Channel Description IE > > < spare bit >**; |
Table 10.5.2.58.2: MBMS p-t-m Channel Description value part details
MBMS p-t-m Channel Description |
10.5.2.58a MBMS Session Parameters List
The MBMS Session Parameters List information element is sent by the network to the mobile station to indicate part of the preassigned resources for an MBMS service (see 3GPP TS 44.060). The remaining part is included in the MBMS p-t-m Channel Description information element (see sub-clause 10.5.2.58).
The MBMS Session Parameters List information element is coded as shown in figure 10.5.2.58a.1 and table 10.5.2.58a.1 and table 10.5.2.58a.2.
The MBMS Session Parameters List is a type 4 information element with a minimum length of 4 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006) and except for that given when the information element is included in the MBMS ANNOUNCEMENT message.
If the MBMS Session Parameters List information element is included in the MBMS ANNOUNCEMENT message, its maximum length is equal to 8 octets (if octet 6 is included, then octet 7 shall also be included) and it shall contain one MBMS Bearer Identity, one Estimated Session Duration and may contain one MBMS Radio Bearer Starting Time, one EGPRS Window Size and one NPM Transfer Time.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
MBMS Session Parameters List IEI |
octet 1 |
|||||||
Length of MBMS Session Parameters List value part |
octet 2 |
|||||||
MBMS Session Parameters List value part |
octet 3 – n |
Figure 10.5.2.58a.1: MBMS Session Parameters List information element
Table 10.5.2.58a.1: MBMS Session Parameters List value part
< MBMS Session Parameters List value part > ::= < MBMS Session Parameters List : < MBMS Session Parameters List IE > > < spare bit >**; |
Table 10.5.2.58a.2: MBMS Session Parameters List value part details
MBMS Session Parameters List |
10.5.2.59 Dedicated Service Information
The Dedicated Service Information information element indicates to the mobile station whether any actions shall be performed on the target cell.
The Dedicated Service Information information element is coded as shown in figure 10.5.2.59.1 and table 10.5.2.59.1.
The Dedicated Service Information is a type 3 information element with 2 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||||||
Dedicated Service Information IEI |
octet 1 |
||||||||||||
Spare |
Spare |
Spare |
Spare |
Spare |
Spare |
Spare |
SIS |
octet 2 |
Figure 10.5.2.59.1: Dedicated Service Information information element
Table 10.5.2.59.1: Dedicated Service Information information element format
Last Segment (octet 2) bit 1 0 mobile station shall not perform Service Information Sending procedure on new cell. 1 mobile station shall perform Service Information Sending procedure on new cell. |
10.5.2.60 MPRACH Description
The MPRACH Description information element is sent by the network to the mobile station to indicate that Counting is to be used for MBMS (see 3GPP TS 44.060).
The MPRACH Description information element is coded as shown in figure 10.5.2.60.1 and table 10.5.2.60.1 and table 10.5.2.60.2.
The MPRACH Description 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 44.006).
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
MPRACH description IEI |
octet 1 |
|||||||
Length of MPRACH description value part |
octet 2 |
|||||||
MPRACH description value part |
octet 3 – n |
Figure 10.5.2.60.1: MPRACH description information element
Table 10.5.2.60.1: MPRACH description value part
< MPRACH description value part > ::= < MPRACH description: < MPRACH description IE > > < spare bit >**; |
Table 10.5.2.60.2: MPRACH description value part details
MPRACH description |
10.5.2.61 Restriction Timer
The Restriction Timer information element indicates to the mobile station whether any actions shall be performed on the target cell (see 3GPP TS 44.060).
The Restriction Timer information element is coded as shown in figure 10.5.2.61.1 and table 10.5.2.61.1 and table 10.5.2.61.2.
The Restriction Timer is a type 3 information element with 2 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Restriction Timer IEI |
octet 1 |
|||||||
Restriction Timer value part |
octet 2 |
Figure 10.5.2.61.1: Restriction Timer information element
Table 10.5.2.61.1: Restriction Timer value part
< Restriction Timer value part > ::= < RESTRICTION_TIMER : bit (4) > < spare bit >**; |
Table 10.5.2.61.2: Restriction Timer value part details
RESTRICTION_TIMER Bit |
10.5.2.62 MBMS Session Identity
The MBMS Session Identity information element is passed to the mobile station by the network and allows the mobile station to avoid duplication of reception of MBMS sessions.
The MBMS Session Identity information element is coded as shown in figure 10.5.2.62.1 and table 10.5.2.62.1 and table 10.5.2.62.2.
The MBMS Session Identity is a type 3 information element with 2 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
MBMS Session Identity IEI |
octet 1 |
|||||||
Length of MBMS Session Identity value part |
octet 2 |
|||||||
MBMS Session Identity value part |
octet 3 – n |
Figure 10.5.2.62.1: MBMS Session Identity information element
Table 10.5.2.62.1: MBMS Session Identity value part
< MBMS Session Identity value part > ::= < MBMS_Session_Identity : bit (8) > < spare bit >**; |
Table 10.5.2.62.2: MBMS Session Identity value part details
MBMS_Session_Identity (8 bit field) |
10.5.2.63 Reduced group or broadcast call reference
The purpose of the Reduced Group or Broadcast Call Reference is to provide information describing a voice group or broadcast call. The IE of the Reduced Group or Broadcast Call Reference is composed of the group or broadcast call reference together with a service flag.
The Reduced Group or Broadcast Call Reference information element is coded as shown in figure 10.5.2.63.1 and Table10.5.2.63.1
The Reduced Group or Broadcast Call Reference is a type 3 information element with 5 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Reduced Group or broadcast call reference IEI |
Octet 1 |
|||||||
Binary coding of the group or broadcast call reference |
Octet 2 |
|||||||
Octet 3 |
||||||||
Octet 4 |
||||||||
SF |
SPARE |
Octet 5 |
Figure 10.5.2.63.1 Reduced Group or Broadcast Call Reference
Table 10.5.2.63.1 Reduced Group or Broadcast Call Reference
Binary code of the group or broadcast call reference The length of the binary code has 27 bits which is encoded in the octet 2, 3, 4 and Bits 8,7,6 (octet 5). The highest bit of the BC is the bit 8 in the octet 2 and the lowest bit is allocated in the bit 6 in the octet 5. (see also 3GPP TS 23.003 [10]) |
|||
SF Service flag (octet 5) |
|||
Bit |
|||
5 |
|||
0 |
VBS (broadcast call reference) |
||
1 |
VGCS (group call reference) |
10.5.2.64 Talker Priority status
The Talker Priority Status information element identifies the priority of the current talker, the channel to be used for talker priority-related uplink access requests, and the status of the emergency mode.
The Talker Priority Status information element is coded as shown in figure 10.5.2.64.1 and table 10.5.2.64.1.
The Talker Priority Status IE is a type 4 information element with 3 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Talker Priority Status IEI |
octet 1 |
|||||||||
Length of Talker Priority Status |
octet 2 |
|||||||||
ES |
Spare |
UAI |
Priority |
octet 3 |
Figure 10.5.2.64.1: Talker Priority Status information element
Table 10.5.2.64.1: Talker Priority Status information element format
Priority (octet 3) Bits 3 2 1 0 0 0 Normal Priority 0 0 1 Privileged Priority 0 1 0 Emergency Priority 0 1 1 reserved for future use to 1 1 1 reserved for future use UAI- Uplink Access Indication (octet 3) Bit 4 0 Group Channel 1 RACH Access ES – Emergency Status (octet 3) Bits 8 0 Emergency mode not set 1 Emergency mode set |
10.5.2.65 Talker Identity
The Talker identity information element contains additional information regarding the identity of the talker.
The Talker identity information element is coded as shown in figure 10.5.2.65.1 and table 10.5.2.65.1.
The Talker identity is a type 4 information element with a minimum length of 3 octets and a maximum length of 20 octets.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Talker Identity IEI |
Octet 1 |
|||||||
Length of talker identity contents |
Octet 2 |
|||||||
Spare |
Filler Bits |
Octet 3 |
||||||
Talker Identity field |
Octet 4-20 |
Figure 10.5.2.65.1: Talker identity information element
Table 10.5.2.65.1: Talker identity information element
Filler bits (octet 3, bits 1-3) This field contains the number of unused bits in the last octet of the Talker Identity field. The filler bits are situated in the val(Filler Bits) least significant bits of the last octet of the Talker Identity field. Bits 4 to 8 of octet 3 are spare and shall be encoded as zero. Talker identity field (octets 4, etc.) This field contains the Talker Identity field. Bit 8 of octet 4 contains the most significant bit of the Talker Identity field. |
10.5.2.66 Token
The purpose of the Token information element is for a handshake mechanism between the BSS and the MS to validate Priority Uplink Requests. It is therefore included in the BUSY UPLINK and the PRIORITY UPLINK REQUEST messages.
The Token information element is coded as shown in figure 10.5.2.66.1 and table 10.5.2.66.1.
The Token 2 is a type 3 information element with 5 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Identification Value 2 IEI |
octet 1 |
|||||||
Identification Value |
octet 2 |
|||||||
octet 3 |
||||||||
octet 4 |
||||||||
octet 5 |
Figure 10.5.2.66.1: Token information element
Table 10.5.2.66.1: Token information element
Token (octets 2-5) This is an unformatted 32 bit field. The contents of this field are randomly generated by the BSS. |
10.5.2.67 PS Cause
The purpose of the PS Cause information element is to provide the reason for release of a DTM handover.
The PS Cause information element is coded as shown in Figure 10.5.2.67.1. The use of the PS Cause information element is described in sub-clause 3.7.2.1.
The PS Cause is a type 1 information element.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
PS Cause IEI |
PS cause value |
octet 1 |
Figure 10.5.2.67.1: PS Cause information element
Table 10.5.2.67.1: PS Cause information element
PS cause value (4 bit field) Bit 4 3 2 1 0 0 0 0 DTM multislot capabilities violated 0 0 0 1 No uplink TBF 0 0 1 0 Too many TBFs All remaining PS cause values are reserved |
10.5.2.68 VGCS AMR Configuration
The VGCS AMR Configuration information element identifies the AMR codec modes to be used on a group channel using speech version 3.
The VGCS AMR Configuration information element is coded as shown in figure 10.5.2.67.1 and table 10.5.2.67.1.
The VGCS AMR Configuration IE is a type 4 information element with 3 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
VGCS AMR Configuration IEI |
octet 1 |
|||||||
Length of VGCS AMR Configuration |
octet 2 |
|||||||
AMR Configuration |
Spare |
octet 3 |
Figure 10.5.2.68.1: VGCS AMR Configuration information element
Table 10.5.2.68.1: VGCS AMR Configuration information element
AMR Configuration bit 5-8 (octet 3) This field indicates the set of AMR codec modes to be used. It is coded as the binary representation of the parameter Config-NB-Code of one of the preferred AMR configurations defined in 3GPP TS 28.062 [92]. |
10.5.2.69 Carrier Indication
This information element may be included in the Frequency Redefinition Message to indicate a change on only one carrier.
The Uplink Carrier Indication is a type 1 information element with a length of 1 octet.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Carrier Indication IEI |
Spare |
CI |
octet 1 |
Figure 10.5.2.69.1: Carrier Indication information element
Table 10.5.2.69.1: CARRIER INDICATION information element
CI bit 0 Carrier 1 1 Carrier 2 |
10.5.2.70 SI10bis Rest Octets
Table 10.5.2.70.1: SI10bis Rest Octets
<SI10bis Rest Octets> ::= < SI10bis Sequence : bit (2) > { H <Position in SI5 list : bit(5)> { 0 | 1 < BCCH ARFCN : bit (10) > } { 0 | 1 < BSIC : bit (6) > } < SI10bis Neighbour Cell Info > } ** L <spare padding>; <SI10bis Neighbour Cell Info> ::= < Group Channel Description > { 0 — no additional frequency list is included | 1 { 0 < Frequency Short List : bit (64) > | 1 < Frequency List : <bit string>> } }< CELL_GLOBAL_COUNT : bit (2) > < B22_COUNT : bit > { 0 — all following parameters are same as in current cell | 1 { 0 — talker priority not supported | 1 < Priority Uplink access : bit > } { 0 | 1 { 0 | 1 < FR AMR Config : bit (4) > } { 0 | 1 < HR AMR Config : bit (4) > } } { 0 | 1 < SMS Data Confidentiality Ind : bit (1) > < SMS Guaranteed Privacy Ind : bit (1) >} { 0 | 1 < Max retrans : bit (2) > < Tx-Integer : bit (4) > } }; <bit string> ::= null | bit <bit string> ; |
SI10bis Sequence
This sequence number identifies a consistent set of SI10bis/SI10ter messages.
Position in SI5 list
This is coded as the first frequency field as specified in sub-clause 10.5.2.44
BCCH ARFCN
The BCCH ARFCN number field is coded as the binary representation of the BCCH carrier’s absolute RF channel number.
BSIC
This field is optional and need only to be included to distinguish two cells which have the same BCCH ARFCN value.
Group Channel Description
This is coded as the Group Channel Description field as specified in sub-clause 9.1.21a. If the hopping sequence for the group channel is specified by means of the Frequency List, then neither the Mobile Allocation nor the Frequency Short List shall be included in the Group Channel Description.
Frequency Short List
This field is syntactically and semantically equivalent to octets 1-8 of the Frequency Short List 2 information element. See sub-clause 10.5.2.14a.
Frequency List
This field is syntactically and semantically equivalent to octets 2-n of the Frequency List information element. See sub-clause 10.5.2.13.
CELL_GLOBAL_COUNT, B22_COUNT
These are coded as specified in sub-clause 9.1.21a.
Priority Uplink access, FR AMR Config, HR AMR Config, SMS Data Confidentiality Ind, SMS Guaranteed Privacy Ind
These are coded as specified in sub-clause 10.5.2.22c.
Max retrans, Tx-Integer
These are coded as specified in sub-clause 10.5.2.29.
10.5.2.71 SI10ter Rest Octets
Table 10.5.2.71.1: SI10ter Rest Octets
<SI10ter Rest Octets> ::= < SI10bis Sequence : bit (2) > { 0 <Position in SI5 list : bit(5) > | 1 < BCCH ARFCN : bit (10) > } { 0 | 1 < BSIC : bit (6) > } <NCH Position : bit (5)> — see SI1 rest octets, 44.018 / 10.5.2.32 <spare padding>; |
Position in SI5 list
This is coded as the first frequency field as specified in sub-clause 10.5.2.44
BCCH ARFCN
The BCCH ARFCN number field is coded as the binary representation of the BCCH carrier’s absolute RF channel number.
BSIC
This field is optional and need only to be included to distinguish two cells which have the same BCCH ARFCN value.
SI10bis Sequence
This sequence number identifies a consistent set of SI10bis/SI10ter messages.
10.5.2.72 Application Data
The Application Data element contains application data sent to or by the network .
The Application Data element is a type 3 information element with a length of 10 octets. The contents of the Application Data is implementation-specific:
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Application Data IEI |
octet 1 |
|||||||
Application Data |
octets 2-10 |
Figure 10.5.2.72.1: Application Data information element
10.5.2.73 Data Identity
The Data Identity Element contains Application Indicator, Data Identifier and Distribution Parameter. The Application Indicator is used to identify whether the Application data IE, which is sent together with the Data Identity IE, is an application-specific data or is a confirmation. The Data Identifier is to provide a sequence number of the sending of Application Data. The value of the Data identifier is dependent on the value of the Application Indicator:
– If the Application Indicator indicates sending application data to the network, the data identifier contains a number from the range between 0 and 15 which is generated by the mobile station.
– If the Application Indicator indicates sending confirmation of the reception of the application data, the Data Identifier shall contain the data identifier which was received in the Data Identity IE sent by the previous sender.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Data Identity IEI |
Octet 1 |
||||||||
DP |
DI |
AI |
Octet 2 |
Figure 10.5.2.73.1: Data Identity information element
Table 10.5.2.73.1: Data Identity information element
Application Indicator (1 bit): Bit 1 0 Application-specific data 1 Confirmation of receiving application-specific data Data identifier (4 bit): The data identitification can have 16 values to identify the data sending sequence. Distribution parameter (3 bit): 8 7 6 1 x x data shall be distributed to talkers & listeners x 1 x data shall be distributed to dispatchers x x 1 data shall be distributed to network application |
10.5.2.74 Uplink Access Indication
The Uplink Access Indication is a type 1 information element.
The Uplink Access Indication information element is coded as shown in figure 10.5.2.74.1 and table 10.5.2.74.1.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Uplink Access Indication |
Spare |
UA Ind |
Octet 1 |
Figure 10.5.2.74.1 Uplink Access Indication
Table 10.5.2.74.1: Uplink Access Indication information element
UA Ind (octet 1, bit 1) |
||||
Bit |
||||
1 |
||||
0 |
Uplink access for application-specific data on the group call channel |
|||
1 |
Uplink access for application-specific data on the RACH |
10.5.2.75 Individual priorities
The Individual priorities information element is coded as shown in figure 10.5.2.75.1 and table 10.5.2.75.1.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
Individual priorities IEI |
octet 1 |
|||||||
Length of Individual priorities |
octet 2 |
|||||||
Individual priorities |
octet 3 – n |
Figure 10.5.2.75.1 Individual priorities
Table 10.5.2.75.1: Individual priorities information element
< Individual priorities > ::= { 0 | — delete all stored individual priorities 1 — provide individual priorities < GERAN_PRIORITY : bit(3) > { 0 | 1 < 3G Individual Priority Parameters Description : < 3G Individual Priority Parameters Description struct >> } { 0 | 1 < E-UTRAN Individual Priority Parameters Description : < E-UTRAN Individual Priority Parameters Description struct >> } { 0 | 1 < T3230 timeout value : bit(3) >} { null | L — Receiver compatible with earlier release | H — Additions in Rel-11 { 0 | 1 < E-UTRAN IPP with extended EARFCNs Description : < E-UTRAN IPP with extended EARFCNs Description struct >> } } }; |
< 3G Individual Priority Parameters Description struct > ::= { 0 | 1 < DEFAULT_UTRAN_PRIORITY : bit(3) >} { 1 < Repeated Individual UTRAN Priority Parameters : < Repeated Individual UTRAN Priority Parameters struct >> } ** 0 ; |
< Repeated Individual UTRAN Priority Parameters struct > ::= { 0 { 1 < FDD-ARFCN : bit (14) > } ** 0 | 1 { 1 < TDD-ARFCN : bit (14) > } ** 0 } < UTRAN_PRIORITY : bit(3) > ; |
< E-UTRAN Individual Priority Parameters Description struct > ::= { 0 | 1 < DEFAULT_E-UTRAN_PRIORITY : bit(3) > } { 1 < Repeated Individual E-UTRAN Priority Parameters : < Repeated Individual E-UTRAN Priority Parameters Description struct >> } ** 0 ; |
< Repeated Individual E-UTRAN Priority Parameters Description struct > ::= { 1 < EARFCN : bit (16) > } ** 0 < E-UTRAN_PRIORITY : bit(3) > ; |
< E-UTRAN IPP with extended EARFCNs Description struct > ::= { 0 | 1 < DEFAULT_E-UTRAN_PRIORITY : bit(3) > } { 1 < Repeated Individual E-UTRAN PP with extended EARFCNs : < Repeated Individual E-UTRAN PP with extended EARFCNs Description struct >> } ** 0 ; |
< Repeated Individual E-UTRAN PP with extended EARFCNs Description struct > ::= { 1 < EARFCN_extended : bit (18) > } ** 0 < E-UTRAN_PRIORITY : bit(3) > ; |
Table 10.5.2.75.2: Individual priorities information element details
GERAN_PRIORITY (3 bit field) UTRAN_PRIORITY (3 bit field) E-UTRAN_PRIORITY (3 bit field) These fields are used for the inter-RAT cell re-selection algorithm based on priority information, as defined in 3GPP TS 45.008. DEFAULT_UTRAN_PRIORITY (3 bit field) DEFAULT_E-UTRAN_PRIORITY (3 bit field) The DEFAULT_UTRAN_PRIORITY field is encoded as the UTRAN_PRIORITY field; the DEFAULT_E-UTRAN_PRIORITY field is encoded as the E-UTRAN_PRIORITY field. Any UTRAN frequency contained in the 3G Frequency list and not explicitly listed in any occurrence of the Repeated Individual UTRAN Priority Parameters IE or any E-UTRAN frequency contained in the E-UTRAN Neighbour Cell list and not explicitly listed in any occurrence of neither the Repeated Individual E-UTRAN Priority Parameters IE nor the Repeated Individual E-UTRAN PP with extended EARFCNs IE shall be assigned the corresponding default value. If the Repeated Individual UTRAN Priority Parameters IE is not present, every UTRAN frequency in the 3G Frequency list for the serving cell shall be assigned the default value. If neither the Repeated Individual E-UTRAN Priority Parameters IE nor the Repeated Individual E-UTRAN PP with extended EARFCNs IE are present, every E-UTRAN frequency in the E-UTRAN Neighbour Cell list for the serving cell shall be assigned the default value. |
FDD-ARFCN (14 bit field) TDD-ARFCN (14 bit field) EARFCN (16 bit field) These fields are used to indicate the frequencies for which priorities are provided, see sub-clause 9.1.54. |
T3230 timeout value (3 bit field) The timer uses 3 bits to indicate the time for which the signalled individual priorities are valid: 0 0 0 5 minute timeout; 0 0 1 10 minute timeout; 0 1 0 20 minute timeout; 0 1 1 30 minute timeout; 1 0 0 60 minute timeout; 1 0 1 120 minute timeout; 1 1 0 180 minute timeout; 1 1 1 reserved for future use; if received, it shall be interpreted by the mobile station as ‘110’; If this information element is not present, the mobile station shall consider the signalled individual priorities to be valid until the occurrence of one of the conditions specified in subclause 3.2.3.3 |
E-UTRAN IPP with extended EARFCNs Description This information element shall be included in the message if both the network and the mobile station support extended EARFCNs (see 3GPP TS 24.008); in such a case the E-UTRAN Individual Priority Parameters Description IE shall not be included in the message. DEFAULT E-UTRAN_PRIORITY (3 bit field) E-UTRAN_PRIORITY (3 bit field) See the above description. EARFCN_extended (18 bit field) |
10.5.2.76 Feature Indicator
The purpose of the Feature Indicator information element is to provide the mobile station with feature related indications.
The Feature Indicator information element is coded as shown in figure 10.5.2.76.1 and table 10.5.2.76.1.
The Feature Indicator is a type 1 information element.
4 |
3 |
2 |
1 |
PEO_BCCH_CHANGE_MARK |
CS IR |
PS IR |
Figure 10.5.2.76.1: Feature Indicator information element
Table 10.5.2.76.1: Feature information element
PS IR (PS Domain Implicit Reject) 0 An implicit reject is not indicated for the PS domain. 1 An implicit reject is indicated for the PS domain. CS IR (CS Domain Implicit Reject) 0 An implicit reject is not indicated for the CS domain. 1 An implicit reject is indicated for the CS domain. PEO_BCCH_CHANGE_MARK See P1 Rest Octets IE, sub-clause 10.5.2.23. |
10.5.2.77 (void)
10.5.2.78 IPA Rest Octets
The IPA Rest Octets information element contains spare bits and possibly at leaste one of the IPA Uplink Assignment struct, the IPA Downlink Assignment struct, and the IPA Single Block Uplink Assignment struct. It shall exclude the assignment of packet resources when sent in response to an EGPRS MULTILATERATION REQUEST message indicating the ‘Access Burst method’ or ‘Extended Access Burst method’.
The IPA Rest Octets information element is coded according to the syntax specified below and described in table 10.5.2.78.1.
The IPA Rest Octets information element is a type 5 information element with 19 octets length.
Table 10.5.2.78.1: IPA Rest Octets information element
<IPA Rest Octets> ::= { 0 | 1 < IPA Uplink Assignment struct >} { 0 | 1 < IPA Downlink Assignment struct >} { 0 | 1 < IPA Single Block Uplink Assignment struct >} { null | L — Receiver compatible with earlier release | H — Additions in Release 13 < RCC : bit (3) > } { null | L — Receiver compatible with earlier release | H — Additions in Release 14 { 0 | 1 < Acknowledged Access Request 1 : Acknowldeged Access Request struct > } { 0 | 1 < Acknowledged Access Request 2 : Acknowldeged Access Request struct > } { 0 | 1 < Acknowledged Access Request 3 : Acknowldeged Access Request struct > } { 0 | 1 < Acknowledged Access Request 4 : Acknowldeged Access Request struct > } } { null | L — Receiver compatible with earlier release | H — Additions in Release 15 {0 | 1 < PEO IMM Cell Group Details : < PEO IMM Cell Group Details struct >> } } <spare padding>; <IPA Uplink Assignment struct> : := { 1 < Random Reference : bit (11) > < FN_OFFSET: bit (8) > < GAMMA : bit (5) > < TIMING_ADVANCE_VALUE : bit (6) > < TFI_ASSIGNMENT : bit (5) > < USF: bit (3) > < EGPRS_CHANNEL_CODING_COMMAND : bit (4) > < Radio Access Capabilities Request: bit (1) > } ** 0; –Repeated as many times as necessary, once for each addressed device < TN : bit (3) > { 0 ; —‘0’ indicates that BCCH frequency shall be used | 1 {< Frequency Parameters: Frequency Parameters struct >} } < IPA Downlink Assignment struct> ::= { 1 < TLLI : bit (32) > < TFI_ASSIGNMENT : bit (5) > < GAMMA : bit (5) > { 0 |1 < TIMING_ADVANCE_VALUE : bit (6) > } } ** 0; –Repeated as many times as necessary, limited by the space in the message { 0 | 1 < LINK_QUALITY_MEASUREMENT_MODE: bit (2) > } < RLC_MODE : bit > < TN : bit (3) > { 0 –‘0’ indicates that BCCH frequency shall be used | 1 {< Frequency Parameters: Frequency Parameters struct >} } <IPA Single Block Uplink Assignment struct> ::= { 1 < Random Reference : bit (11) > < FN_OFFSET: bit (8) > < GAMMA : bit (5) > < TIMING_ADVANCE_VALUE : bit (6) > < STARTING_TIME_OFFSET: bit (6) >, } ** 0; –Repeated as many times as necessary, limited by the space in the message < TN : bit (3) > { 0 ; –‘0’ indicates that BCCH frequency shall be used | 1 {< Frequency Parameters: Frequency Parameters struct >} } < Acknowledged Access Request struct > ::= { 00 < Short ID : bit (8) > | 01 < Random ID Low : bit (4) > | 10 < Random ID High : bit (12) > | 11 — Reserved } < PEO IMM Cell Group Details struct > ::= — Addition in Rel-15 < PEO IMM Cell Group Identifier : bit (3) > < PEO IMM Change Mark : bit (2) >; |
Table 10.5.2.78.2: IPA Rest Octets information element details
IPA Uplink Assignment struct The Random Reference field (11 bit field) is the 11 bits of the EGPRS PACKET CHANNEL REQUEST message or the EGPRS MULTILATERATION REQUEST message indicating ‘RLC Data Block method’ or ‘Page Response for Positioning Event’ as defined in 3GPP TS 44.060. The FN_OFFSET field (8 bit field) is a negative offset added to the first FN of this received IMMEDIATEE PACKET ASSIGNEMENT message which indicates the frame number where the MS sending the EGPRS PACKET CHANNEL REQUEST message. Range: – 255to 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 45.008. The GAMMA field is coded according to the following table: bit The TIMING_ADVANCE_VALUE field (6 bit field) is the binary representation of the timing advance in bit periods and encoded the same as the value of the Timing Advance information element defined in sub-clause 10.5.2.40. Range: 0 to 63. The TFI_ASSIGNMENT field (5 bit field) is the binary representation of the Temporary Flow Identity, see 3GPP TS 44.060. Range: 0 to 31. The USF field (3 bit field) is the binary representation of the uplink state flag, see 3GPP TS 44.060. Range: 0 to 7. The EGPRS_CHANNEL_CODING_COMMAND fileld (4 bit field) indicates the channel coding command that the mobile station shall use for any RLC data block regardless a TLLI field contained or not, and is defined in sub-clause 12.10d, 3GPP TS44.060. The Radio Access Capabilities Request field (1 bit field) indicates the request of MS Radio Access Capability by the network for the addressed MSs in this message. 0 MS Radio Access Capability is not requested by the network; 1 MS Radio Access Capability for the BCCH band is requested by the network. The TN field (3 bit field) is the binary representation of the timeslot number as defined in 3GPP TS 45.010. Range: 0 to 7. Frequency Parameters IE This information element is defined in sub-clause 12.8, 3GPP TS44.060. The EGPRS Window Size parameter is not included, and default value 192 shall be used for this parameter. The ALPHA parameter is not included, and default value 0 shall be used for this parameter. The RESEGMENT parameter is not included, and default value 0 shall be used for this parameter. The USF_GRANULARITY parameter is not included, and default value 0 shall be used for this parameter, i.e. the mobile station shall transmit one RLC/MAC block if assigned USF is received. |
IPA Downlink Assignment struct Random Reference, FN_OFFSET, GAMMA, TFI_ASSIGNMENT, TIMING_ADVANCE_VALUE, TN, EGPRS Window Size, ALPHA fields and Frequency Parameters IE These fields are encoded as in IPA Uplink Assignment struct. 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 RLC_MODE field (1 bit field) indicates the RLC mode, see 3GPP TS 44.060: 0 RLC acknowledged mode; 1 RLC unacknowledged mode. LINK_QUALITY_MEASUREMENT_MODE (2 bit field) This field is encoded as the LINK_QUALITY_MEASUREMENT_MODE in the PACKET DOWNLINK ASSIGNMENT message in 3GPP TS 44.060. |
IPA Single Block Uplink Assignment struct Random Reference, FN_OFFSET, GAMMA, TIMING_ADVANCE_VALUE, TN, ALPHA fields and Frequency Parameters IE These fields are encoded as in IPA Uplink Assignment struct. The STARTING_TIME_OFFSET field (6 bit field) is a positive offset added to the first FN of this received IMMEDIATE PACKET ASSIGNMENT message which indicates the start frame number of the assigned single uplink block. Range 0 to 63. RCC (3 bit) See sub-clause 10.5.2.16. The Short ID field (8 bit field) is the 8 bits of the "Short ID" parameter included in an EGPRS MULTILATERATION REQUEST message indicating ‘Access Burst’ method as defined in 3GPP TS 44.060 [76]. The Random ID Low field (4 bit field) is the "Random ID Low" parameter included in an EGPRS MULTILATERATION REQUEST message indicating ‘Extended Access Burst method – part 1’ as defined in 3GPP TS 44.060 [76]. The Random ID High field (12 bit field) is the "Random ID High" parameter included in an EGPRS MULTILATERATION REQUEST message indicating ‘Extended Access Burst method – part 2’ as defined in 3GPP TS 44.060 [76]. Multilateration Information Request (1 bit field) See sub-clause 10.5.2.16. PEO IMM Cell Group Details struct This structure provides identifier and change mark indication of the PEO IMM cell group which the serving cell belongs to for deferred SI acquisition for PEO (see subclause 3.9.4.1). PEO IMM Cell Group Identifier (3 bits) See sub-clause 10.5.2.16. PEO IMM Change Mark (2 bits) See sub-clause 10.5.2.16. |
10.5.2.79 DL-DCCH-Message
The purpose of the DL-DCCH-Message information element is to provide information to the mobile station when performing CS to PS SRVCC to E-UTRAN.
The DL-DCCH-Message IE is a type 4 information element with length 3-n octets.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
DL-DCCH-Message IEI |
octet 1 |
|||||||
Length of DL-DCCH-Message contents |
octet 2 |
|||||||
DL-DCCH-Message value part |
octet 3-n |
Figure 10.5.2.79.1: DL-DCCH-Message information element
The value part of the DL-DCCH-Message IE includes a complete RRCConnectionReconfiguration radio interface message as defined in 3GPP TS 36.331.
10.5.2.80 CN to MS transparent information
This information element is defined as a general container for passing CN specific information transparently through the BSS from the CN to the MS.
The CN to MS transparent information IE is a type 4 information element with length 3-n octets.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
CN to MS transparent information IEI |
octet 1 |
|||||||
Length of CN to MS transparent information contents |
octet 2 |
|||||||
CN to MS transparent information (NOTE 1) |
octet 3-n |
|||||||
NOTE 1: The content of this field is transparent to the BSS and will be determined by whether a CS to PS SRVCC to UTRAN (HSPA) or E-UTRAN is performed. |
Figure 10.5.2.80.1: CN to MS transparent information information element
CN to MS transparent information field is encoded as the CN to MS transparent information IE without the Element identifier as defined in 3GPP TS 48.008.
10.5.2.81 PLMN Index
This information element refers either to the identity of the Common PLMN broadcast in the SYSTEM INFORMATION TYPE 3/4 message or to the identity of an Additional PLMN broadcast in the SYSTEM INFORMATION TYPE 22 message and is coded as in figure 10.5.2.81.1.
The PLMN Index is a type 1 information element.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
PLMN Index IEI |
PLMN Index |
octet 1 |
Figure 10.5.2.81.1 PLMN Index
The PLMN Index is mapped into the Selected PLMN Index field (see 3GPP TS 44.060) as shown in the table 10.5.2.81.1 below.
Table 10.5.2.81.1: Mapping PLMN Index to Selected PLMN Index
PLMN Index bit |
Selected PLMN Index |
0 0 0 1 |
001 – PLMN identity of the Common PLMN broadcast in SYSTEM INFORMATION TYPE 3/4 |
0 0 1 0 |
010 – PLMN identity of the first Additional PLMN in the network sharing information broadcast in SYSTEM INFORMATION TYPE 22 |
0 0 1 1 |
011 – PLMN identity of the second Additional PLMN in the network sharing information broadcast broadcast in SYSTEM INFORMATION TYPE 22 |
0 1 0 0 |
100 – PLMN identity of the third Additional PLMN in the network sharing information broadcast in SYSTEM INFORMATION TYPE 22 |
0 1 0 1 |
101 – PLMN identity of the fourth Additional PLMN in the network sharing information broadcast in SYSTEM INFORMATION TYPE 22 |
0 1 1 0…1 1 1 1 |
Reserved |
10.5.2.82 Extended TSC Set
The purpose of the Extended TSC Set information element is to provide TSC related information for the assigned radio resources (see 3GPP TS 45.002 for the TSC sets applicable to the CS domain and the PS domain).
The Extended TSC Set information element is coded as shown in figure 10.5.2.82.1 and table 10.5.2.82.1.
The Extended TSC Set is a type 3 information element with 2 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
Extended TSC Set IEI |
octet 1 |
|||||||||
Secondary PS Domain TSC Value |
Secondary PS Domain TSC Set |
PrimaryPS Domain TSC Set |
2nd PS Domain TSC Assigned |
CS Domain TSC Set |
octet 2 |
Figure 10.5.2.82.1: Extended TSC Set information element
Table 10.5.2.82.1: Extended TSC Set information element
CS Domain TSC Set (octet 2): Indicates the TSC set to be used for the radio resources assigned for the CS domain and takes precedence over the CS domain TSC set indicated by the Channel Description IE or the Channel Description 2 IE in the assignment message. This field is ignored when no CS domain resources are provided by the assignment message. Bit 1 2 |
0 0 TSC set 1 0 1 TSC set 2 1 0 TSC set 3 1 1 TSC set 4 2nd PS Domain TSC Assigned (octet 2): Indicates whether or not a secondary TSC value is assigned for the downlink of the PS domain. This field is ignored when no PS domain resources are provided by the assignment message. Bit 3 0 A secondary TSC value is not assigned for the PS domain. 1 A secondary TSC value is assigned for the PS domain. The TSC value is indicated by the Secondary PS Domain TSC Value field and the corresponding TSC set is indicated by the Secondary PS Domain TSC Set field. Primary PS Domain TSC Set (octet 2): This field indicates the TSC set corresponding to the TSC value indicated by the Packet Channel Description IE or the Channel Description 3 IE in the assignment message regardless if a secondary TSC value is assigned. This field is used for the assigned uplink and downlink PS resources and is ignored when no PS domain resources are provided by the assignment message. |
Bit 4 |
0 TSC set 1 1 Indicates TSC set 2 for 8PSK, 16QAM and 32QAM modulation. For GMSK modulation it indicates TSC set 3 (which is identical to TSC set 3 used for the CS domain). Secondary PS Domain TSC Set (octet 2): This field indicates the TSC set corresponding to the TSC value indicated by the Secondary PS Domain TSC Value field when a secondary TSC value is assigned for the downlink PS resources. This field is ignored when no PS domain resources are provided by the assignment message. Bit 5 0 TSC set 1 1 Indicates TSC set 2 for 8PSK, 16QAM and 32QAM modulation. For GMSK modulation it indicates TSC set 3 (which is identical to TSC set 3 used for the CS domain). Secondary PS Domain TSC Value (octet 2): Indicates the secondary TSC value assigned for the downlink PS resources and is coded as the binary representation of the Training Sequence code as defined in 3GPP TS 45.002. Its corresponding TSC set is indicated by the Secondary PS Domain TSC Set field. This field is ignored when a secondary TSC value is not assigned for the PS domain or no PS domain resources are provided by the assignment message. Range: 0 to 7. |
10.5.2.83 EC Request Reference
The purpose of the EC Request Reference information element is to indicate the 10 least significant bits of the uplink TDMA frame in which the BSS received an EC PACKET CHANNEL REQUEST message and the 3 random bits contained within that same message.
The EC Request Reference information element is coded according to the syntax specified below and described in table 10.5.2.83.1.
The EC Request Reference is a type 3 information element with 13 bits length.
< EC Request Reference Description > ::= < Last TDMA Frame : bit (10) > < Echoed Random Bits : bit (3) > ; |
Figure 10.5.2.83.1: Request Reference information element
Table 10.5.2.83.1: EC Request Reference information element
Last TDMA Frame (10 bit field) This field identifies the 10 least significant bits of the TDMA frame in which the BSS received the EC PACKET CHANNEL REQUEST message to which the EC IMMEDIATE ASSIGNMENT TYPE 2 message corresponds. |
Echoed Random Bits (3 bit field) This field is set to the value of the 3 bit random field included within the EC PACKET CHANNEL REQUEST message to which the EC IMMEDIATE ASSIGNMENT TYPE 2 message corresponds. |
10.5.2.84 EC Packet Channel Description Type 1
The EC Packet Channel Description Type 1 IE identifies the radio parameters applicable to a mobile station that has enabled EC operation and attempting system access using the RACH (i.e. coverage class 1 has been selected for both the uplink and the downlink).
The EC Packet Channel Description Type 1 information element is coded according to the syntax specified below and described in table 10.5.2.84.1.
The EC Packet Channel Description Type 1 is a type 3 information element with 16 bits length.
< EC Packet Channel Description Type 1 > ::= < QUARTER_HYPERFRAME_INDICATOR : bit (2) > < DL_COVERAGE_CLASS : bit (2) > < UL_COVERAGE_CLASS : bit (2) > < TSC Set : bit (1) > < TSC : bit (3) > < EC_MA_NUMBER : bit (5) > <spare bit : bit (1) >; |
Figure 10.5.2.84.1: EC Packet Channel Description Type 1 information element
Table 10.5.2.84.1: EC Packet Channel Description Type 1 information element
The QUARTER_HYPERFRAME_INDICATOR field (2 bits) indicates the quarter hyperframe in which the last TDMA frame used to send the EC IMMEDIATE ASSIGNMENT TYPE 1 message was sent. The mobile station uses this information to determine the quarter hyperframe in which it last read the EC-SCH INFORMATION message and thereby acquires TDMA frame synchronization (see 3GPP TS 45.002). This field is coded as follows: Bit 2 1 0 0 Quarter Hyperframe 0 0 1 Quarter Hyperframe 1 1 0 Quarter Hyperframe 2 1 1 Quarter Hyperframe 3 |
The DL_COVERAGE_CLASS field (2 bits) indicates the downlink coverage class the mobile station is to use on the assigned packet resources. This field is coded as follows: Bit 2 1 0 0 DL Coverage Class 1 0 1 DL Coverage Class 2 1 0 DL Coverage Class 3 1 1 DL Coverage Class 4 |
The UL_COVERAGE_CLASS field (2 bits) indicates the uplink coverage class the mobile station is to use on the assigned packet resources. This field is coded as follows: Bit 2 1 0 0 UL Coverage Class 1 0 1 UL Coverage Class 2 1 0 UL Coverage Class 3 1 1 UL Coverage Class 4 |
The TSC Set field (1 bit) indicates the TSC set corresponding to the TSC value indicated by the TSC field. This field is used for the assigned uplink and downlink PS resources 0 TSC set 1 1 Indicates TSC set 2 for 8PSK modulation and TSC set 3 for GMSK modulation (which is identical to TSC set 3 used for the CS domain). |
The TSC field (3 bits) is the binary representation of the training sequence code as defined in 3GPP TS 45.002. |
The EC_MA_NUMBER field (5 bits) identifies an EC Mobile Allocation set provided by the EC SYSTEM INFORMATION TYPE 1 message (see sub-clause 9.1.43p). This field is coded as follows: Bit 5 4 3 2 1 0 0 0 0 0 EC Mobile Allocation set 1 0 0 0 0 1 EC Mobile Allocation set 2 0 0 0 1 0 EC Mobile Allocation set 3 . . . 1 1 1 1 1 EC Mobile Allocation set 32 |
10.5.2.85 EC Packet Channel Description Type 2
The EC Packet Channel Description Type 2 IE identifies the radio parameters applicable to a mobile station that has received an EC IMMEDIATE ASSIGNMENT TYPE 2 message or an EC DOWNLINK ASSIGNMENT message on the EC-AGCH.
The EC Packet Channel Description Type 2 information element is coded according to the syntax specified below and described in table 10.5.2.85.1.
The EC Packet Channel Description Type 2 is a type 3 information element with 15 bits length.
< EC Packet Channel Description Type 2 > ::= < QUARTER_HYPERFRAME_INDICATOR : bit (2) > < DL_COVERAGE_CLASS : bit (2) > < UL_COVERAGE_CLASS : bit (2) > < TSC Set : bit (1) > < TSC : bit (3) > < EC_MA_NUMBER : bit (5) > ; |
Figure 10.5.2.85.1: EC Packet Channel Description Type 2 information element
Table 10.5.2.85.1: EC Packet Channel Description Type 2 information element
QUARTER_HYPERFRAME_INDICATOR (2 bit field) This field indicates the quarter hyperframe in which the last TDMA frame used to send the EC IMMEDIATE ASSIGNMENT TYPE 2 message or EC DOWNLINK ASSIGNMENT message was sent. The mobile station uses this information to determine the quarter hyperframe in which it last read the EC-SCH INFORMATION message and thereby acquires TDMA frame synchronization (see 3GPP TS 45.002). This field is coded as described in sub-clause 10.5.2.84. |
DL_COVERAGE_CLASS (2 bit field) This field is described in sub-clause 10.5.2.84. |
UL_COVERAGE_CLASS (2 bit field) This field is described in sub-clause 10.5.2.84. |
TSC Set (1 bit field) This field is described in sub-clause 10.5.2.84. |
TSC (3 bit field) This field is described in sub-clause 10.5.2.84. |
EC_MA_NUMBER (5 bit field) This field is described in sub-clause 10.5.2.84. |
10.5.2.86 EC Fixed Uplink Allocation
The purpose of the EC Fixed Uplink Allocation information element is to indicate the set of one or more pre-allocated uplink radio blocks a mobile station is to use for packet data transmission.
The EC Fixed Uplink Allocation information element is coded according to the EC Fixed Uplink Allocation struct described in sub-clause 9.1.60.
The EC Fixed Uplink Allocation is a type 3 information element with 32 to 112 bits length.
See 3GPP TS 24.008.
10.5.2.87 Request Reference Alt
The purpose of the Request Reference Alt information element is to provide the random access information included within the EGPRS MULTILATERATION REQUEST message (indicating the ‘Access Burst’ method or ‘Extended Access Burst’ method, see sub-clause 3.5.2.1.2 and sub-clause 3.11) and the frame number, FN modulo 42432 in which the EGPRS MULTILATERATION REQUEST message was received.
The Request Reference Alt information element is coded as shown in figure 10.5.2.87.1 and table 10.5.2.87.1.
The Request Reference Alt is a type 3 information element with 5 octets length.
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
Request Reference Alt IEI |
octet 1 |
||||||||
RA (low part) |
RA Type |
spare |
octet 2 |
||||||
RA (high part) |
Octet 3 |
||||||||
T1′ |
T3 |
octet 4 |
|||||||
T3 |
T2 |
octet 5 |
Figure 10.5.2.87.1: Request Reference Alt information element
Table 10.5.2.87.1: Request Reference Alt information element
RA, Random Access Information (octet 2 and octet 3) When included in an IMMEDIATE PACKET ASSIGNMENT message sent in response to an EGPRS MULTILATERATION REQUEST message indicating ‘Extended Access Burst – part 1’ the least significant 4 bits of this field are used and contain the value of the ‘Random ID Low’ field included in the corresponding message. When included in an IMMEDIATE PACKET ASSIGNMENT message sent in response to an EGPRS MULTILATERATION REQUEST message indicating ‘Extended Access Burst – part 2’ all 12 bits of this field are used and contain the value of the ‘Random ID High’ field included in the corresponding message. RA Type, Random Access Type (octet 2) This field indicates the type of access request the IMMEDIATE PACKET ASSIGNMENT message sent in response to. This field is coded as follows: Bits
T1′ (octet 3) T3 (octet 3 and 4) T2 (octet 4) NOTE 1: The frame number, FN modulo 42432 can be calculated as 51x((T3-T2) mod 26)+T3+51x26xT1′ |
10.5.2.88 EC Packet Channel Description Type 3
The EC Packet Channel Description Type 3 IE identifies the radio parameters applicable to a mobile station that has received an EC IMMEDIATE ASSIGNMENT TYPE 4 message on the EC-AGCH.
The EC Packet Channel Description Type 3 information element is coded according to the syntax specified below and described in table 10.5.2.88.1.
The EC Packet Channel Description Type 3 is a type 3 information element with 15 bits length.
< EC Packet Channel Description Type 3 > ::= < QUARTER_HYPERFRAME_INDICATOR : bit (2) > < DL_COVERAGE_CLASS : bit (2) > < UL_COVERAGE_CLASS_EXTENDED : bit (2) > < TSC Set : bit (1) > < TSC : bit (3) > < EC_MA_NUMBER : bit (5) > ; |
Figure 10.5.2.88.1: EC Packet Channel Description Type 3 information element
Table 10.5.2.88.1: EC Packet Channel Description Type 3 information element
QUARTER_HYPERFRAME_INDICATOR (2 bit field) This field is coded as described in sub-clause 10.5.2.85.1. |
DL_COVERAGE_CLASS (2 bit field) This field is described in sub-clause 10.5.2.84. |
UL_COVERAGE_CLASS_EXTENDED (2 bit field) bit 2 1 0 0 UL CC5 0 1 Reserved 1 0 Reserved 1 1 Reserved |
TSC Set (1 bit field) This field is described in sub-clause 10.5.2.84. |
TSC (3 bit field) This field is described in sub-clause 10.5.2.84. |
EC_MA_NUMBER (5 bit field) This field is described in sub-clause 10.5.2.84. |