12 Information element coding

04.603GPPGeneral Packet Radio Service (GPRS)Mobile Station (MS) - Base Station System (BSS) interfaceRadio Link Control / Medium Access Control (RLC/MAC) protocolRelease 1999TS

12.1 Overview

Information elements used within the context of only one RLC/MAC control message are defined in clause 11. All other information elements are defined within the present sub-clause.

12.2 (void)

12.3 Ack/Nack Description

The Ack/Nack Description information element contains the RLC parameters used to acknowledge or negatively acknowledge a group of RLC data blocks.

Table 12.3.1: Ack/Nack Description information elements

< Ack/Nack Description IE > ::=

< FINAL_ACK_INDICATION : bit (1) >

< STARTING_SEQUENCE_NUMBER : bit (7) >

< RECEIVED_BLOCK_BITMAP : bit (64) > ;

Table 12.3.2: Ack/Nack Description information element details

FINAL_ACK_INDICATION (1 bit field)
This field indicates whether the entire TBF is being acknowledged. If the entire TBF is being acknowledged, the SSN and RBB fields contain no information and shall be ignored.

0 retransmission are requested and the TBF is incomplete
1 no retransmissions are requested and this message indicates acknowledgement of all RLC data in the TBF

STARTING_SEQUENCE_NUMBER (SSN) (7 bit field)
The SSN contains the value of V(R) when this information element was transmitted. This field is encoded as the binary representation of V(R).
Range 0 to 127

RECEIVE_BLOCK_BITMAP (RBB) (64 bit field)
The RBB is a bitmap representing Block Sequence Numbers. The bitmap is indexed relative to SSN as follows:

BSN = (SSN – bit_number) modulo 128, for bit_number = 1 to 64.

The BSN values represented range from (SSN – 1) mod 128 to (SSN – 64) mod 128.

The value of each bit is encoded as:

0 Negative acknowledgement of the RLC data block with BSN = (SSN – bit_number) mod 128
1 Positive acknowledgement of the RLC data block with BSN = (SSN – bit_number) mod 128

Mapping of the bitmap is defined on sub-clause 11.

12.3.1 EGPRS Ack/Nack Description

The Ack/Nack Description information element contains the RLC parameters used to acknowledge or negatively acknowledge a group of RLC data blocks. The number of bits available for the bitmap depends on the inclusion or exclusion of other information elements in the used message.

Table 12.3.1.1: EGPRS Ack/Nack Description information elements

< EGPRS Ack/Nack Description IE > ::=

0 < EGPRS Ack/Nack Description struct > — This IE fills rest of message

| 1 < Length L : bit (8) > — Value part of this IE is of length L

{ < bit (val(Length L)) > & < EGPRS Ack/Nack Description struct > } ;

< EGPRS Ack/Nack Description struct > ::=

< FINAL_ACK_INDICATION : bit (1) >

< BEGINNING_OF_WINDOW : bit (1) >

< END_OF_WINDOW : bit (1) >

< STARTING_SEQUENCE_NUMBER : bit (11) >

{ 0 | 1 < COMPRESSED_BITMAP_LENGTH: bit (7) >

< COMPRESSED_BITMAP_STARTING_COLOR_CODE: bit (1) >

< COMPRESSED_RECEIVED_BLOCK_BITMAP :
bit (val(COMPRESSED_BITMAP_LENGTH)) > }

< UNCOMPRESSED_RECEIVED_BLOCK_BITMAP: bit** > ;

Table 12.3.1.2: Ack/Nack Description information element details

LENGTH L (8 bit field)
Range 15 to 255
This field represents the length of the value part (i.e. the EGPRS Ack/Nack Description struct) of this information element. If this field is not included, this information element fills the remaining part of the message.

FINAL_ACK_INDICATION (1 bit field)
This field indicates whether the entire TBF is being acknowledged. If the entire TBF is being acknowledged, the SSN, CRBB and URBB fields contain no information and shall be ignored.
0 retransmissions are requested and the TBF is incomplete.
1 no retransmissions are requested and this message indicates acknowledgement of all RLC data in the TBF.

BEGINNING_OF_WINDOW (BOW, 1 bit field)
This bit indicates if the Ack/Nack bitmap starts at the beginning of the window.
0 SSN not equal to (V(Q)+1) mod 2048.
1 SSN = (V(Q) +1) mod 2048

END_OF_WINDOW (EOW, 1 bit field)
This bit indicates if the end of the receiver window is included in the bitmap(s).
0 [V(R) – 1] modulo SNS is not included in the bitmap.
1 [V(R) – 1] modulo SNS is included in the bitmap.

STARTING_SEQUENCE_NUMBER (SSN) (11 bit field)
Range 0 to 2047
The SSN indicates the Block Sequence Number of the first RLC block for which the Ack/Nack receipt status is indicated within the bitmap. The SSN is determined using S/P, PBSN and V(Q).

COMPRESSED_BITMAP_LENGTH (Lc) (7 bit field)
Range 0 to 127
This field represents the length of the compressed bitmap. Compression is carried out using T.4 run length coding.

COMPRESSED_BITMAP_STARTING_COLOR_CODE (1 bit field)
This bit indicates if the first code word in the compressed bitmap (i.e., CRBB) represents a run length of ones or a run length of zeros.
0 First code word in CRBB represents run length of zeros.
1 First code word in CRBB represents run length of ones.

COMPRESSED_RECEIVE_BLOCK_BITMAP (CRBB) (Lc bit field)
The CRBB is a compressed bitmap. Compression is carried out starting at SSN using modified T.4 run length coding. The number of bits (Lc) available for Ack/Nack Description depends on the inclusion of other information elements in the used message.

The packing order of the CRBB shall be such that the codeword (or pair of make up/terminating codewords) corresponding to the run including the SSN starts at the most significant bit of the CRBB, and codewords (or pairs of make-up/terminating codewords) corresponding to runs including higher and successively increasing sequence numbers are placed in bits of successively decreasing significance.

NOTE: The URBB is packed in the opposite order.

UNCOMPRESSED_RECEIVE_BLOCK_BITMAP (URBB) (Lu bit field)
The URBB is an uncompressed bitmap, which fills the remainder of this information element upto L bits, where L is the number of bits available for the EGPRS Ack/Nack description struct. The URBB field length, Lu, is determined by:

Lu = L-Lc-23, when the compressed received block bitmap is included, or by
Lu = L-15, when the compressed received block bitmap is not included.:

The bits in URBB, denoted here by index i, are numbered from i=1 (lowest order value) to i=Lu (highest order value). The value of each bit in the bitmap is encoded as following:

0 Negative acknowledgement of the RLC data block with BSN = (ESN_CRBB + i) modulo SNS, and
1 Positive acknowledgement of the RLC data block with BSN = (ESN_CRBB + i) modulo SNS, where

ESN_CRBB is the ending block sequence number of CRBB and, if no CRBB is included, ESN_CRBB = (SSN – 1) modulo SNS.

12.4 ALLOCATION_BITMAP

The ALLOCATION_BITMAP represents uplink radio blocks, each bit representing one radio block or an entire block period. Each bit indicates whether the mobile station is permitted to transmit during the corresponding uplink radio block or radio block period.

Table 12.4.1: ALLOCATION_BITMAP information element details

ALLOCATION_BITMAP (variable length field)
The ALLOCATION_BITMAP represents uplink radio blocks or radio block periods, each bit representing one radio block or an entire radio block.

If the BLOCKS_OR_BLOCK_PERIODS field indicates blocks, the bitmap describes a two dimensional array of radio blocks. The number of columns in the array is variable and is equal to the number of timeslots allocated in the TIMESLOT_ALLOCATION. The array is indexed as follows:

Radio block[x,y]
x = (L – n) / NTS, for n = 0 to L,
y = (L – n) mod NTS for n = 0 to L,

where:
x = block period relative to TBF_STARTING_TIME, range 0 to L / NTS;
y = timeslot number index of the assigned timeslots in the TIMESLOT_BITMAP, range 0 (representing the lowest numbered assigned timeslot) to NTS-1 (representing the highest numbered assigned timeslot);
L = number of bits in the ALLOCATION_BITMAP – 1;
n = bit number index into the ALLOCATION_BITMAP, range 0 to L;
TBF_STARTING_TIME indicates the first block period of the assigned allocation;
NTS = number of timeslots assigned in the TIMESLOT_ALLOCATION, range 1 to 8;
The division operation is integer division;
The modulo operation is integer modulo.

The value of each bit is encoded as:

0 radio block[x,y] is not part of the assigned allocation
1 radio block[x,y] is part of the assigned allocation

If the BLOCKS_OR_BLOCK_PERIODS field indicates block periods, the bitmap describes a one dimensional array of block periods. For each block period indicated as part of the allocation in the bitmap, each of the timeslots indicated in the TIMESLOT_ALLOCATION is assigned as part of the allocation. The array is indexed as follows:

block period[z]
z = n for n = 0 to L,

where:
L = number of bits in the ALLOCATION_BITMAP – 1;
z = block period relative to TBF_STARTING_TIME;
n = bit number index into the ALLOCATION_BITMAP, range 0 to L;
TBF_STARTING_TIME indicates the first block period of the assigned allocation;
NTS = number of timeslots assigned in the TIMESLOT_ALLOCATION, range 1 to 8.

The value of each bit is encoded as:

0 block period[n] is not part of the assigned allocation
1 block period[n] is part of the assigned allocation

NOTE: The relationship between the field mapping within RLC/MAC messages as described in Clause 11 (bit number in range 1 to L + 1) and the ALLOCATION_BITMAP field as defined above (bit number index in range 0 to L) is the following:

RLC/MAC message field [n + 1] = ALLOCATION_BITMAP [n], for n = 0 to L.

Some examples are depicted in Annex H.

12.5 EGPRS

12.5.1 EGPRS Channel Quality Report

EGPRS Channel Quality Report Information Element.

Table 12.5.1.1 : EGPRS Channel Quality Report Information elements

< EGPRS Channel Quality Report > ::=

< EGPRS BEP Link Quality Measurements : < EGPRS BEP Link Quality Measurements IE>>

< C_VALUE : bit (6) >

< EGPRS Timeslot Link Quality Measurements : <EGPRS Timeslot Link Quality Measurements IE >> ;

Table 12.5.1.2 : EGPRS Channel Quality Report Information Elements details

EGPRS BEP Link Quality Measurements IE
This information element is defined in sub-clause 12.5.3. These fields are transferred if the data is available and if the fields would not cause the message to expand beyond one RLC/MAC control block.

EGPRS Timeslot Link Quality Measurements

This information element is defined in sub-clause 12.5.4.

C_VALUE (6 bits)
This field contains the value of the C parameter calculated by the mobile station (see 3GPP TS 05.08). This field is encoded as the binary representation of the C value parameter value defined in 3GPP TS 05.08.
Range 0 to 63

12.5.2 EGPRS Window Size

This information element defines the window size to be used in an EGPRS TBF. The network sets the window size according to the number of timeslots allocated in the direction of the TBF.

Table 12.5.2.1 : EGPRS Window Size Information Elements details

bit
5 4 3 2 1

Value of EGPRS window size

Comment

0 0 0 0 0

64

0 0 0 0 1

96

0 0 0 1 0

128

0 0 0 1 1

160

0 0 1 0 0

192

(maximum window size for a 1 timeslot TBF)

0 0 1 0 1

224

0 0 1 1 0

256

(maximum window size for a 2 timeslot TBF)

0 0 1 1 1

288

0 1 0 0 0

320

0 1 0 0 1

352

0 1 0 1 0

384

(maximum window size for a 3 timeslot TBF)

0 1 0 1 1

416

0 1 1 0 0

448

0 1 1 0 1

480

0 1 1 1 0

512

(maximum window size for a 4 timeslot TBF)

0 1 1 1 1

544

1 0 0 0 0

576

1 0 0 0 1

608

1 0 0 1 0

640

(maximum window size for a 5 timeslot TBF)

1 0 0 1 1

672

1 0 1 0 0

704

1 0 1 0 1

736

1 0 1 1 0

768

(maximum window size for a 6 timeslot TBF)

1 0 1 1 1

800

1 1 0 0 0

832

1 1 0 0 1

864

1 1 0 1 0

896

(maximum window size for a 7 timeslot TBF)

1 1 0 1 1

928

1 1 1 0 0

960

1 1 1 0 1

992

1 1 1 1 0

1024

(maximum window size for an 8 timeslot TBF)

1 1 1 1 1

Reserved

12.5.3 EGPRS BEP Link Quality Measurements IE

The EGPRS BEP Link Quality measurements IE:

Table 12.5.3.1 : EGPRS BEP Link Quality Information elements

<EGPRS BEP Link Quality Measurements IE> ::=

{ 0 | 1 < GMSK_MEAN_BEP : bit (5) >

< GMSK_CV_BEP : bit (3) >}

{ 0 | 1 < 8PSK_MEAN_BEP : bit (5) >

< 8PSK_CV_BEP : bit (3) > };

Table 12.5.3.2 : EGPRS BEP Link Quality Information Elements details

GMSK_MEAN_BEP (5 bit field)
This field contains the mean value of the Bit Error Probability of the channel averaged over all time slots in the TBF for GMSK, refer to 3GPP TS 05.08.

8PSK_MEAN_BEP (5 bit field)
This field contains the mean value of the Bit Error Probability of the channel averaged over all time slots in the TBF for 8 PSK, refer to 3GPP TS 05.08.

GMSK_CV_BEP (3 bit field)
This field contains the variation co-efficient for the Bit Error Probability averaged over all time slots of the TBF for GMSK, refer to 3GPP TS 05.08.

8PSK_CV_BEP (3 bit field)
This field contains the variation co-efficient for the Bit Error Probability averaged over all time slots of the TBF for 8 PSK, refer to 3GPP TS 05.08.

12.5.4 EGPRS Timeslot Link Quality Measurements IE

The EGPRS Timeslot Link Quality measurements IE. Information to be included within this IE is indicated by the LINK_QUALITY_MEASUREMENT_MODE field within the Packet Downlink Assignment and Packet Timeslot Reconfigure messages.

Table 12.5.4.1 : EGPRS Timeslot Link Quality Measurements Information elements

<EGPRS Timeslot Link Quality Measurements IE> ::=

{ 0 | 1< BEP_MEASUREMENTS : BEP Measurement Report Struct >}

{ 0 | 1 < INTERFERENCE_MEASUREMENTS : Interference Measurement Report Struct >};

< BEP Measurement Report Struct > ::=

{ 0 | 1 { 0 <GMSK_MEAN_BEP _TN0 : bit (4) >

| 1 < 8PSK_MEAN_BEP _TN0 : bit (4) >}}

{ 0 | 1 { 0 <GMSK_MEAN_BEP _TN1 : bit (4) >

| 1 < 8PSK_MEAN_BEP _TN1 : bit (4) >}}

{ 0 | 1 { 0 <GMSK_MEAN_BEP _TN2 : bit (4) >

| 1 < 8PSK_MEAN_BEP _TN2 : bit (4) >}}

{ 0 | 1 { 0 <GMSK_MEAN_BEP _TN3 : bit (4) >

| 1 < 8PSK_MEAN_BEP _TN3 : bit (4) >}}

{ 0 | 1 { 0 <GMSK_MEAN_BEP _TN4 : bit (4) >

| 1 < 8PSK_MEAN_BEP _TN4 : bit (4) >}}

{ 0 | 1 { 0 <GMSK_MEAN_BEP _TN5 : bit (4) >

| 1 < 8PSK_MEAN_BEP _TN5 : bit (4) >}}

{ 0 | 1 { 0 <GMSK_MEAN_BEP _TN6 : bit (4) >

| 1 < 8PSK_MEAN_BEP _TN6 : bit (4) >}}

{ 0 | 1 { 0 <GMSK_MEAN_BEP _TN7 : bit (4) >

| 1 < 8PSK_MEAN_BEP _TN7 : bit (4) >} };

< Interference Measurement Report Struct > ::=

{ 0 | 1 < I_LEVEL_TN0 : bit (4) > }

{ 0 | 1 < I_LEVEL_TN1 : bit (4) > }

{ 0 | 1 < I_LEVEL_TN2 : bit (4) > }

{ 0 | 1 < I_LEVEL_TN3 : bit (4) > }

{ 0 | 1 < I_LEVEL_TN4 : bit (4) > }

{ 0 | 1 < I_LEVEL_TN5 : bit (4) > }

{ 0 | 1 < I_LEVEL_TN6 : bit (4) > }

{ 0 | 1 < I_LEVEL_TN7 : bit (4) > };

Table 12.5.4.2 : EGPRS Timeslot Link Quality Measurements Information Elements details

GMSK_MEAN_BEP_TN0 (4 bit field)
GMSK_MEAN_BEP_TN1 (4 bit field)
GMSK_MEAN_BEP_TN2 (4 bit field)
GMSK_MEAN_BEP_TN3 (4 bit field)
GMSK_MEAN_BEP_TN4 (4 bit field)
GMSK_MEAN_BEP_TN5 (4 bit field)
GMSK_MEAN_BEP_TN6 (4 bit field)
GMSK_MEAN_BEP_TN7 (4 bit field)

These fields contain the mean bit errror probability value calculated on timeslots 0 through 7 for GMSK modulation, refer to 3GPP TS 05.08. These fields are transferred only when the mobile station is in packet transfer mode.

8PSK_MEAN_BEP_TN0 (4 bit field)
8PSK_MEAN_BEP_TN1 (4 bit field)
8PSK_MEAN_BEP_TN2 (4 bit field)
8PSK_MEAN_BEP_TN3 (4 bit field)
8PSK_MEAN_BEP_TN4 (4 bit field)
8PSK_MEAN_BEP_TN5 (4 bit field)
8PSK_MEAN_BEP_TN6 (4 bit field)
8PSK_MEAN_BEP_TN7 (4 bit field)

These fields contain the mean bit errror probability value calculated on timeslots 0 through 7 for 8PSK modulation, refer to 3GPP TS 05.08. These fields are transferred only when the mobile station is in packet transfer mode.

I_LEVEL_TN0 (4 bit field)

I_LEVEL_TN1 (4 bit field)

I_LEVEL_TN2 (4 bit field)

I_LEVEL_TN3 (4 bit field)

I_LEVEL_TN4 (4 bit field)

I_LEVEL_TN5 (4 bit field)

I_LEVEL_TN6 (4 bit field)

I_LEVEL_TN7 (4 bit field)

These fields contain the  value calculated on timeslots 0 through 7, respectively. The  value is defined in 3GPP TS 05.08. These fields are encoded relative to C_VALUE as defined for the mapping defined in 3GPP TS 05.08 for interference level (I_LEVEL):

bit

4 3 2 1

0 0 0 0 I_LEVEL 0

0 0 0 1 I_LEVEL 1

1 1 1 0 I_LEVEL 14

1 1 1 1 I_LEVEL 15

12.6 (void)

12.7 Channel Request Description

The Channel Request Description information element is sent by the mobile station to the network to request uplink resources.

Table 12.7.1: Channel Request Description information elements

< Channel Request Description IE > ::=

< PEAK_THROUGHPUT_CLASS : bit (4) >

< RADIO_PRIORITY : bit (2) >

< RLC_MODE : bit (1) >

< LLC_ PDU_TYPE : bit (1) >

< RLC_OCTET_COUNT : bit (16) > ;

Table 12.7.2: Channel Request Description information element details

PEAK_THROUGHPUT_CLASS (4 bit field)
This field indicates the peak throughput class for the PDP context of the LLC PDU that caused the Channel Request Description IE to be transmitted. The field is coded as the binary representation of the Peak Throughput Class specified in 3GPP TS 03.60.
Range: 1 to 9

RADIO_PRIORITY (2 bit field)
This field indicates the Radio Priority of the requested TBF. The field is encoded as the Radio Priority field of the Packet Channel Request (see 11.2.5).

RLC_MODE (1 bit field)
This field indicates the RLC mode of the requested TBF.

0 RLC acknowledged mode
1 RLC unacknowledged mode

LLC_ PDU_TYPE (1 bit field)
This field indicates the type of the first LLC PDU to be transmitted over the requested uplink TBF.

0 LLC PDU is SACK or ACK
1 LLC PDU is not SACK or ACK

RLC_OCTET_COUNT (16 bit field)
The RLC_OCTET_COUNT field indicates the number of RLC data octets, plus the number of RLC data block length octets, that the mobile station wishes to transfer. The value ‘0’ shall be interpreted as a request for an open-ended TBF by the mobile station. All other values shall be interpreted as a request for a close ended TBF.
Range 0 to 65535

12.8 Frequency Parameters

The Frequency Parameters information element defines frequency parameters and a training sequence code (TSC), which may be allocated to a mobile station to define its channel configuration. All timeslots in the channel configuration of the mobile station shall use the same frequency parameters and training sequence code.

NOTE: For COMPACT, for PDTCH/PACCH on primary and secondary carriers that are indicated in EXT_FREQUENCY_LIST by parameter INT_FREQUENCY and in INT_MEAS_CHAN_LIST (see sub-clauses 10.1.5 and 10.2.3.2.2 of 3GPP TS 05.08), the TSCs should be equal to the BCC, as defined in 3GPP TS 03.03, otherwise the accuracy of interference measurement reporting may be compromised.

The frequency parameters may consist of an ARFCN, defining a non-hopping radio frequency channel. The indirect encoding, the direct encoding 1 and the direct encoding 2 defines a hopping radio frequency channel.

Table 12.8.1: Frequency Parameters information elements

< Frequency Parameters IE > ::=

< TSC : bit (3) >

{ 00 < ARFCN : bit (10) >

| 01 < Indirect encoding : < Indirect encoding struct > >

| 10 < Direct encoding 1 : < Direct encoding 1 struct > >

| 11 < Direct encoding 2 : < Direct encoding 2 struct > > } ;

< Indirect encoding struct > ::=

< MAIO : bit (6) >

< MA_NUMBER : bit (4) >

{ 0 | 1 < CHANGE_MARK_1 : bit (2) >

{ 0 | 1 < CHANGE_MARK_2 : bit (2) > } } ;

< Direct encoding 1 struct > ::=

< MAIO : bit (6) >

< GPRS Mobile Allocation : < GPRS Mobile Allocation IE > > ;

< Direct encoding 2 struct > ::=

< MAIO : bit (6) >

< HSN : bit (6) >

< Length of MA Frequency List contents : bit (4) >

< MA Frequency List contents : octet (val(Length of MA Frequency List contents) + 3) > ;

Table 12.8.2: Frequency Parameters information element details

TSC (3 bit field)
This field is the binary representation of the training sequence code, see 3GPP TS 05.02. Range: 0 to 7.

ARFCN (10 bit field)
This field is the binary representation of the absolute radio frequency channel number (ARFCN) defined in 3GPP TS 05.05. Range 0 to 1023.

MAIO (6 bit field)
This field is the binary representation of the mobile allocation index offset (MAIO), see 3GPP TS 05.02. Range 0 to 63.

MA_NUMBER (4 bit field)
This field is the binary reference to a GPRS mobile allocation received in either the PSI2 information, the SI13/PSI13 information or a previous assignment message, see sub-clause 5.5.1.6. Range: 0 to 15.

CHANGE_MARK_1 (2 bit field)
CHANGE_MARK_2 (2 bit field)
These fields are the binary representations of the allowed values for the PSI or SI change mark associated with the GPRS mobile allocation that the MA_NUMBER field refers to. Range: 0 to 3.

GPRS Mobile Allocation (information element)
The GPRS Mobile Allocation information element is defined in sub-clause 12.10a.

HSN (6 bit field)
This field is the binary representation of the hopping sequence number, see 3GPP TS 05.02. Range: 0 to 63.

MA Frequency List contents (variable length octet string)
This variable length octet string is the representation of a set of radio frequency channels defining a GPRS mobile allocation. The encoding of the octet string is defined by the value part of the type 4 information element Frequency List, defined in 3GPP TS 04.08. The allowed formats of the Frequency List information element are the bit map 0, 1024 range, 512 range, 256 range, 128 range and variable bit map formats.

12.8.1 Abnormal cases

If the indirect encoding is used, this information element may contain the CHANGE_MARK_1 and 2 fields. If one of these fields is present, the receiver shall verify the validity of the PSI or SI change mark associated with the GPRS mobile allocation that the MA_NUMBER field refers to, see sub-clause 5.5.1.7. None of the CHANGE_MARK_1 and 2 fields shall be included if the MA_NUMBER refers to a GPRS mobile allocation received in a previous assignment message.

If the receiver detects that an inconsistency is contained in this information element, the information element shall be regarded as invalid. Such inconsistency may be that:

– an invalid PSI or SI change mark is associated with the referred GPRS mobile allocation;

– an CHANGE_MARK_1 or 2 field is included and the MA_NUMBER refers to a GPRS mobile allocation received in a previous assignment message; or

– an undefined MA_NUMBER or an invalid GPRS Mobile Allocation is contained in this information element.

If the inconsistency is due to an invalid PSI or SI change mark associated with the referred GPRS mobile allocation or an undefined MA_NUMBER in the range 0 ñ 14, the mobile station shall initiate a partial acquisition of PBCCH or BCCH information (see 5.5.1.4). It shall then obtain the PSI2 or SI13 information, which is concerned.

12.9 Global Power Control Parameters

The Global Power Control Parameters information element contains parameters the mobile station shall use to determine its TX power level.

Table 12.9.1: Global Power Control Parameters information elements

< Global Power Control Parameters IE > ::=

< ALPHA : bit (4) >

< T_AVG_W : bit (5) >

< T_AVG_T : bit (5) >

< Pb : bit (4) >

< PC_MEAS_CHAN : bit (1) >

< INT_MEAS_CHANNEL_LIST_AVAIL : bit (1) >

< N_AVG_I : bit (4) > ;

Table 12.9.2: Global Power Control Parameters information element details

ALPHA (4 bit field)
This field is the binary representation of the parameter  for MS output power control in units of 0.1, see 3GPP TS 05.08.
Range: 0 to 10. The ALPHA power control parameter field is coded according to the following table:

bit
4 3 2 1
0 0 0 0 α = 0.0
0 0 0 1 α = 0.1
0 0 1 0 α = 0.2
: :
1 0 0 1 α = 0.9
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.

T_AVG_W (5 bit field)
The T_AVG_W parameter is a signal strength filter period for power control in packet idle mode. 2(k/2) / 6 multiframes, k = 0, 1, 2, … 25 (see 3GPP TS 05.08). Values greater than 25 shall be interpreted as 25 by the mobile station.

T_AVG_T (5 bit field)
The T_AVG_T parameter is a signal strength filter period for power control in packet transfer mode. 2(k/2) / 6 multiframes, k = 0,1,2,…,25 (see 3GPP TS 05.08). Values greater than 25 shall be interpreted as 25 by the mobile station.

Pb (4 bit field)
The Pb parameter is a power reduction value used by the BTS on PBCCH blocks, relative to the output power used on BCCH. The field is coded according to the following table:

bit
4 3 2 1
0 0 0 0 Pb = 0 dB
0 0 0 1 Pb = -2 dB
0 0 1 0 Pb = -4 dB
: :
1 1 1 1 Pb = -30 dB

PC_MEAS_CHAN (1 bit field)
The PC_MEAS_CHAN parameter indicates where the mobile station shall measure the received power level on the downlink for the purpose of the uplink power control.

0 downlink measurements for power control shall be made on BCCH
1 downlink measurements for power control shall be made on PDCH

N_AVG_I (4 bit field)
The N_AVG_I parameter is an interfering signal strength filter constant for power control 2(k/2), k=0,1,..,15 (see 3GPP TS 05.08).
Range: 0 to 15

INT_MEAS_CHANNEL_LIST_AVAIL (1 bit field)
Indicates if the optional PSI4 message is broadcast. If broadcast, the PSI4 contains the channel List for interference measurements (INT_MEAS_CHANNEL_LIST).

0 PSI4 message not broadcast
1 PSI4 message broadcast

12.10 Global TFI

The Global TFI (Temporary Flow Identity) information element contains either an uplink TFI or a downlink TFI. The uplink or downlink TFI identifies a single Temporary Block Flow.

Table 12.10.1: Global TFI information elements

< Global TFI IE > ::=

{ 0 < UPLINK_TFI : bit (5) >

| 1 < DOWNLINK_TFI : bit (5) > } ;

Table 12.10.2: Global TFI information element details

UPLINK_TFI (5 bit field)
This field identifies an uplink TBF. This field is coded the same as the TFI field defined in sub-clause 12.15.

DOWNLINK_TFI (5 bit field)
This field identifies a downlink TBF. This field is coded the same as the TFI field defined in sub-clause 12.15.

12.10a GPRS Mobile Allocation

The GPRS Mobile Allocation information element defines a set of radio frequency channels and a hopping sequence number (HSN), which may be allocated to a mobile station to define its channel configuration.

This information element may refer to a reference frequency list, or set of reference frequency lists defined in the PSI2 information. In case there is no such reference included in this information element, it refers to the cell allocation (CA) defined for the cell. The cell allocation is defined in the PSI2 information, if PBCCH is present in the cell, or in the SI1 information (see 3GPP TS 04.08), if PBCCH is not present in the cell.

There are two alternative ways to encode the GPRS mobile allocation, using the MA_BITMAP or the ARFCN index list.

Table 12.10a.1: GPRS Mobile Allocation information elements

< GPRS Mobile Allocation IE > ::=

< HSN : bit (6) >

{ 0 | 1 < RFL number list : < RFL number list struct > > }

{ 0 < MA_LENGTH : bit (6) >

< MA_BITMAP : bit (val(MA_LENGTH) + 1) >

| 1 { 0 | 1 < ARFCN index list : < ARFCN index list struct > > } } ;

< RFL number list struct > ::=

< RFL_NUMBER : bit (4) >

{ 0 | 1 < RFL number list struct > } ;

< ARFCN index list struct > ::=

< ARFCN_INDEX : bit (6) >

{ 0 | 1 < ARFCN index list struct > } ;

Table 12.10a.2: GPRS Mobile Allocation information element details

HSN (6 bit field)
This field is the binary representation of the hopping sequence number, see 3GPP TS 05.02. Range: 0 to 63.

RFL number list (construction)
This construction is a list specifying the referenced set of reference frequency lists for this information element. If the list is not included, this information element refers to the cell allocation defined for the cell.

The number of radio frequency channels included in the referenced set of reference frequency lists or the referenced cell allocation (excluding any duplication of radio frequency channels) is denoted NF. The radio frequency channels shall be arranged by the receiver of this information element in the order of ascending ARFCN, except for ARFCN = 0, if included, which shall be put last. Each radio frequency channel shall then be assigned an ARFCN_INDEX value, ranging from zero, for the first radio frequency channel, to NFñ1, for the last radio frequency channel in the ordered set.

MA_BITMAP (variable length, 1 to 64 bit, field)
This field is a bitmap representing the radio frequency channels belonging to the GPRS mobile allocation. The number of bit positions in MA_BITMAP shall equal NF. The first bit position in MA_BITMAP corresponds to ARFCN_INDEX = NFñ1, the last position corresponds to ARFCN_INDEX = 0. Each bit position is coded:

0 the corresponding radio frequency channel does not belong to the GPRS mobile allocation;
1 the corresponding radio frequency channel belongs to the GPRS mobile allocation.

ARFCN index list (construction)
This construction is a list representing a set of radio frequency channels to be excluded from the definition of the GPRS mobile allocation. The GPRS mobile allocation is defined as consisting of the radio frequency channels included in the referenced set of reference frequency lists or the referenced cell allocation, except those represented by the ARFCN index list. If the list is not included, this information element defines a GPRS mobile allocation consisting of all radio frequency channels included in the referenced set of reference frequency lists or the referenced cell allocation, without exception.

RFL_NUMBER (4 bit field)
This field is the binary reference to a reference frequency list provided in PSI2. Range 0 to 15.

ARFCN_INDEX (6 bit field)
This field is the binary reference to a radio frequency channels in the referenced set of reference frequency lists or the referenced cell allocation. Range: 0 to NFñ1.

12.10a.1 Abnormal cases

If the receiver of this information element detects any inconsistency between the encoding of this information element and the referenced frequency information (i.e., an MA_BITMAP length or an ARFCN_INDEX value out of range, or an undefined RFL_NUMBER value), the information element shall be regarded as invalid.

12.10b (void)

12.10c (void)

12.10d EGPRS Modulation and coding Scheme description

This information element defines the modulation and coding scheme to be used.

Table 12.10d.1: EGPRS MCS information element details

EGPRS modulation and coding scheme information element

bits
4 3 2 1

value

0 0 0 0

MCS-1

0 0 0 1

MCS-2

0 0 1 0

MCS-3

0 0 1 1

MCS-4

0 1 0 0

MCS-5

0 1 0 1

MCS-6

0 1 1 0

MCS-7

0 1 1 1

MCS-8

1 0 0 0

MCS-9

1 0 0 1

MCS-5-7

1 0 1 0

MCS-6-9

12.10e RESEGMENT

The RESEGMENT field defines whether retransmitted uplink RLC data blocks shall be re-segmented or not.

Table 12.10e.1: RESEGMENT information element details

RESEGMENT (1 bit field)
0 Retransmitted RLC data blocks shall not be re-segmented
1 Retransmitted RLC data blocks shall be re-segmented according to commanded MCS

12.11 Packet Request Reference

The purpose of the Packet Request Reference information element is to provide the information field sent in the Packet Channel Request (i.e., the PACKET CHANNEL REQUEST or EGPRS PACKET CHANNEL REQUEST message) and the frame number, FN modulo 42432, in which the Packet Channel Request was received.

Table 12.11.1: Packet Request Reference information elements

< Packet Request Reference IE > ::=
< RANDOM_ACCESS_INFORMATION value : bit (11) >
< FRAME_NUMBER : bit (16) > ;

Table 12.11.2: Packet Request Reference information element details

RANDOM_ACCESS_INFORMATION value (11 bit field)
This is an unformatted 11 bit field. If the mobile station used the 11-bit message format in the Packet Channel Request, all 11 bits of this field are valid. Otherwise, only bits 8 through 1 are valid and bits 11 through 9 shall be set to ‘0’.

bit
11 10 9 8 7 6 5 4 3 2 1
11-bit message format used X X X X X X X X X X X
8-bit message format used 0 0 0 X X X X X X X X

FRAME_NUMBER (16 bit field)
This field is encoded the same as the Starting Time information element defined in 3GPP TS 04.18.

12.12 Packet Timing Advance

The Packet Timing Advance field describes the timing advance mode and timing advance value assigned to the mobile station.

Table 12.12.1: Packet Timing Advance information elements

< Packet Timing Advance IE > ::=

{ 0 | 1 < TIMING_ADVANCE_VALUE : bit (6) > }

{ 0 | 1 < TIMING_ADVANCE_INDEX : bit (4) >

< TIMING_ADVANCE_TIMESLOT_NUMBER : bit (3) > } ;

Table 12.12.2: Packet Timing Advance information element details

TIMING_ADVANCE_VALUE (6 bit field)
If the TIMING_ADVANCE_VALUE field is present, the mobile station shall use the value contained therein after time defined in 3GPP TS 05.10. If the TIMING_ADVANCE_VALUE field is not present the mobile station shall not change its timing advance value. The Timing Advance value field is encoded the same as the Timing Advance value of the Timing Advance information element defined in 3GPP TS 04.08

TIMING_ADVANCE_INDEX (4 bit field)
If the TIMING_ADVANCE_INDEX and TIMING_ADVANCE_TIMESLOT_NUMBER fields are present the mobile station shall begin operation of the Continuous Timing Advance procedure at the point in time denoted by the TBF starting time if present, otherwise after the reaction time specified in 3GPP TS 05.10.. If these two fields are not present the mobile station shall stop operation of the Continuous Timing Advance procedure. This information field is encoded as a binary representation of the Timing Advance Index defined in 3GPP TS 05.02.
Range 0 to 15.

TIMING_ADVANCE_TIMESLOT_NUMBER (3 bit field)
This field indicates the timeslot assigned for Continuous Timing Advance operation on the PTCCH. This field is coded as the binary representation of the timeslot number as defined in 3GPP TS 05.10.
Range 0 to 7

12.12a Global Packet Timing Advance

The Global Packet Timing Advance field describes the timing advance mode and timing advance value assigned to the mobile station for uplink and/or downlink TBF.

Table 12.12a.1: Global Packet Timing Advance information elements

< Global Packet Timing Advance IE > ::=

{ 0 | 1 < TIMING_ADVANCE_VALUE : bit (6) > }

{ 0 | 1 < UPLINK_TIMING_ADVANCE_INDEX : bit (4) >

< UPLINK_TIMING_ADVANCE_TIMESLOT_NUMBER : bit (3) > }

{ 0 | 1 < DOWNLINK_TIMING_ADVANCE_INDEX : bit (4) >

< DOWNLINK_TIMING_ADVANCE_TIMESLOT_NUMBER : bit (3) > }

Table 12.12a.2: Global Packet Timing Advance information element details

TIMING_ADVANCE_VALUE (6 bit field)
If the TIMING_ADVANCE_VALUE field is present, the mobile station shall use the value contained therein after time defined in 3GPP TS 05.10. If the TIMING_ADVANCE_VALUE field is not present the mobile station shall not change its timing advance value. The Timing Advance value field is encoded the same as the Timing Advance value of the Timing Advance information element defined in 3GPP TS 04.08

UPLINK_TIMING_ADVANCE_INDEX (4 bit field)
This field indicates the Timing Advance Index related to Uplink TBF. This information field is encoded as a binary representation of the Timing Advance Index defined in 3GPP TS 05.02.
Range 0 to 15.

UPLINK_TIMING_ADVANCE_TIMESLOT_NUMBER (3 bit field)
This field indicates the timeslot assigned for Continuous Timing Advance operation on the PTCCH related to Uplink TBF. This field is coded as the binary representation of the timeslot number as defined in 3GPP TS 05.10.
Range 0 to 7

DOWNLINK_TIMING_ADVANCE_INDEX (4 bit field)
This field indicates the Timing Advance Index related to Downlink TBF. This information field is encoded as a binary representation of the Timing Advance Index defined in 3GPP TS 05.02.
Range 0 to 15.

DOWNLINK_TIMING_ADVANCE_TIMESLOT_NUMBER (3 bit field)
This field indicates the timeslot assigned for Continuous Timing Advance operation on the PTCCH related to Downlink TBF. This field is coded as the binary representation of the timeslot number as defined in 3GPP TS 05.10.
Range 0 to 7

If Timing Advance Index and Timing Advance Timeslot Number are present for any of the TBFs already existing or to be established with this message, the mobile station shall begin operation of the Continuous Timing Advance procedure at the point in time denoted by the TBF starting time if present, otherwise within the reaction time specified in 3GPP TS 05.10.

If Timing Advance Index and Timing Advance Timeslot Number are not present for any of the TBFs already existing or to be established with this message, the mobile station shall stop operation of the Continuous Timing Advance procedure.

12.12b Packet Extended Timing Advance

The Packet Extended Timing Advance field is a 2 bit field used to support Extended Timing Advance. These two bits represent the two most significant bits of the timing advance value to be applied by the mobile station. The coding of the timing advance value is defined in the Timing Advance IE defined in 3GPP TS 04.18. The mapping of the two bits of the Packet Extended Timing Advance field is defined as follows:

Bit
1 bit 7 of the Timing Advance IE defined in 3GPP TS 04.18
2 bit 8 of the Timing Advance IE defined in 3GPP TS 04.18

The least significant bits of a timing advance value is provided the TIMING_ADVANCE_VALUE field in either a Packet Timing Advance IE (sub-clause 12.12) or a Global Packet Timing Advance IE (sub-clause 12.12a). If the least significant bits of the timing advance value is not provided in the message, then the Packet Extended Timing Advance field shall be ignored.

12.13 Power Control Parameters

The Power Control parameters information element contains parameters the mobile station shall use to determine its TX power level.

Table 12.13.1: Power Control Parameters information elements

< Power Control Parameters IE > ::=

< ALPHA : bit (4) >

{ 0 | 1 < GAMMA_TN0 : bit (5) > }

{ 0 | 1 < GAMMA_TN1 : bit (5) > }

{ 0 | 1 < GAMMA_TN2 : bit (5) > }

{ 0 | 1 < GAMMA_TN3 : bit (5) > }

{ 0 | 1 < GAMMA_TN4 : bit (5) > }

{ 0 | 1 < GAMMA_TN5 : bit (5) > }

{ 0 | 1 < GAMMA_TN6 : bit (5) > }

{ 0 | 1 < GAMMA_TN7 : bit (5) > } ;

Table 12.13.2: Power Control Parameters information element details

ALPHA (4 bit field)
For encoding and description see the Global Power Control Parameters IE.

GAMMA_TN0 (5 bit field)
GAMMA_TN1 (5 bit field)
GAMMA_TN2 (5 bit field)
GAMMA_TN3 (5 bit field)
GAMMA_TN4 (5 bit field)
GAMMA_TN5 (5 bit field)
GAMMA_TN6 (5 bit field)
GAMMA_TN7 (5 bit field)
The GAMMA_TN0..7 fields are the binary representation of the parameter ΓCH for MS output power control in units of 2 dB, see 3GPP TS 05.08. GAMMA_TN0 contains the gamma value for timeslot number 0, GAMMA_TN1 contains the gamma value for timeslot number 1, etc. If this information element is also used to determine the timeslot allocation for an uplink TBF, for each timeslot, the presence of the GAMMA value indicates that the timeslot is assigned, and the absence of the GAMMA value indicates that the timeslot is not assigned (see sub-clause 12.18). The GAMMA_TN0..7 field is coded according to the following table:

bit
5 4 3 2 1
0 0 0 0 0 ΓCH = 0 dB
0 0 0 0 1 ΓCH = 2 dB
: : : :
1 1 1 1 0 ΓCH = 60 dB
1 1 1 1 1 ΓCH = 62 dB

12.14 PRACH Control Parameters

The purpose of the PRACH Control Parameters information element is to provide parameters used to control the PRACH utilization.

Table 12.14.1: PRACH Control Parameters information elements

< PRACH Control Parameters IE > ::=

< ACC_CONTR_CLASS : bit (16) >

< MAX_RETRANS : bit (2) > * 4

< S : bit (4) >

< TX_INT : bit (4) >

{ 0 | 1 < PERSISTENCE_LEVEL : bit (4) > * 4 } ;

Table 12.14.2: PRACH Control Parameters information element details

TX_INT (4 bit field)
Number of slots to spread transmission of the random access. The field is coded according to the following table:

bit
4 3 2 1
0 0 0 0 2slots used to spread transmission
0 0 0 1 3 slots used to spread transmission
0 0 1 0 4 slots used to spread transmission
0 0 1 1 5 slots used to spread transmission
0 1 0 0 6 slots used to spread transmission
0 1 0 1 7 slots used to spread transmission
0 1 1 0 8 slots used to spread transmission
0 1 1 1 9 slots used to spread transmission
1 0 0 0 10 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

S (4 bit field)
S is a parameter used for calculation of the minimum number of slots between two successive Channel request messages. The field is coded according to the following table:

bit
4 3 2 1
0 0 0 0 S = 12
0 0 0 1 S = 15
0 0 1 0 S = 20
0 0 1 1 S = 30
0 1 0 0 S = 41
0 1 0 1 S = 55
0 1 1 0 S = 76
0 1 1 1 S = 109
1 0 0 0 S = 163
1 0 0 1 S = 217
All other values reserved.

MAX_RETRANS (2 bit field for each Radio Priority 1..4)
Indicates for each Radio Priority level 1 to 4 the maximum number of retransmissions allowed. Radio Priority 1 represents the highest priority. The field is coded with two bits per Radio Priority level according to the following table where the first two bits refer to Radio Priority 1, the second two bits to Radio Priority 2, etc.:

bit
2 1
0 0 1 retransmission allowed
0 1 2 retransmissions allowed
1 0 4 retransmissions allowed
1 1 7 retransmissions allowed

PERSISTENCE_LEVEL (4 bit field for each Radio Priority 1..4)
The PERISTENCE_LEVEL field indicates the values of the access persistence level P(i) for each Radio Priority i (i = 1..4) where Radio Priority 1 represents the highest Radio Priority of an LLC PDU to be transmitted.

bits
4 3 2 1
0 0 0 0 persistence level 0
0 0 0 1 persistence level 1
0 0 1 0 persistence level 2
0 0 1 1 persistence level 3
0 1.0.0 persistence level 4
: : :
1 1 1 0 persistence level 14
1 1 1 1 persistence level 16

ACC_CONTR_CLASS ( 16 bit field)
Access Control Class N (bit 1-16) (see octet 3 and 4 of the RACH Control Parameters IE in 3GPP TS 04.08) . For a mobile station with Access Control Class =N access is not barred if the Access Control Class N bit is coded with a ‘0’; N = 0, 1,….9,11,…,15. Bit 11= the EC bit is the Emergency Call Allowed coded as specified in 3GPP TS 04.08.

Bits: 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Class N: 15 14 13 12 11 EC 9 8 7 6 5 4 3 2 1 0

12.15 Temporary Flow Identity (TFI)

The Temporary Flow Identity (TFI) uniquely identifies either a single uplink Temporary Block Flow (TBF) or a single downlink Temporary Block Flow (TBF).

Table 12.15.1: UPLINK_TFI information element details

UPLINK_TFI (5 bit field)
The Temporary Flow Identity field identifies an uplink Temporary Block Flow (TBF). This field is encoded as a binary number.
Range 0 to 31

Table 12.15.2: DOWNLINK_TFI information element details

DOWNLINK_TFI (5 bit field)
The Temporary Flow Identity field identifies a downlink Temporary Block Flow (TBF). This field is encoded as a binary number.
Range 0 to 31

12.16 Temporary Logical Link Identity (TLLI)

The Temporary Logical Link Identity (TLLI) is associated with the GPRS subscriber. TLLI is defined in 3GPP TS 03.03.

Table 12.16.1: TLLI information element details

TLLI (32 bit field)
The TLLI field is encoded as a binary number.
Range 0 to 4294967295

12.17 Temporary Queueing Identifier (TQI)

The Temporary Queueing Identifier (TQI) field identifies a mobile station during the queueing procedure. The contents of this field are operator defined.

Table 12.17.1: TQI information element details

TQI (16 bit field)
The Temporary Queueing Identifier field is an unformatted field.

12.18 TIMESLOT_ALLOCATION

The TIMESLOT_ALLOCATION field indicates the timeslots for use during a TBF or the timeslots carrying a PCCCH.

Table 12.18.1: TIMESLOT_ALLOCATION information element details

TIMESLOT_ALLOCATION (8 bit field)
This information field indicates the timeslots assigned for use during the TBF or the timeslots carrying a PCCCH. Bit 8 indicates the status of timeslot 0, bit 7 indicates the status of timeslot 1, etc. At least one timeslot must be assigned.

0 Timeslot is not assigned
1 Timeslot is assigned

12.19 TS_OVERRIDE

The TS_OVERRIDE field indicates the timeslots whose allocation should be overridden during a TBF.

Table 12.19.1: TS_OVERRIDE information element details

TS_OVERRIDE (8 bit field)
This information field indicates which the timeslots whose allocation should be overridden. The override applies for one repeated allocation. Bit 8 indicates the status of timeslot 0, bit 7 indicates the status of timeslot 1, etc. The MS shall ignore any bit in the TS_OVERRIDE field whose corresponding bit in the previous timeslot allocation for the uplink TBF is set to ‘0’.

0 The mobile shall use the ALLOCATION_BITMAP to determine in which radio blocks it shall transmit on the timeslot during the allocation

1 The mobile shall transmit in all uplink blocks of the timeslot during the allocation

12.20 PAGE_MODE

The PAGE_MODE field controls the action of the mobile station belonging to the paging subgroup corresponding to the paging subchannel.

Table 12.20.1: PAGE_MODE information element details

PAGE_MODE (2 bit field)

bit
2 1 value
0 0 Normal Paging
0 1 Extended Paging
1 0 Paging Reorganization
1 1 Same as before

12.21 Starting Frame Number Description

There are two types of encoding for this IE : Relative Frame Number or Absolute Frame Number.

Table 12.21.1: Starting Frame Number Description information element

< Starting Frame Number Description IE > ::=

{ 0 < Absolute Frame Number Encoding >

| 1 < Relative Frame Number Encoding > } ;

If the mobile station is in packet transfer mode during the block immediately before the starting time and the lowest numbered PDCH assigned to the MS is different immediately before and after the starting time then the mobile station shall be ready to receive or transmit no later than one radio block from the starting time (see 3GPP TS 05.02).

12.21.1 Absolute Frame Number Encoding

In this case, the field is encoded as the 16-bit Starting Time IE defined in 3GPP TS 04.08, and the value of the Starting FN is obtained directly.

If the Starting FN is not aligned to the start of a block period and the mobile station is in packet transfer mode during the TDMA immediately before the Starting FN, then the mobile station shall align the starting time to the next block boundary and continue to use the currently assigned allocation upto the next block boundary.

12.21.2 Relative Frame Number Encoding

In this case, the field indicates the delay, relative to the first TDMA frame (N) of the RLC/MAC block containing the Starting Time field, before the assigned or requested resource becomes valid.

The value of this field is the 13-bit binary representation of the integer k, from which the offset to be applied to N can be derived.

The value of the Starting Frame Number is calculated as follows:

For (k mod 3) equal to:

The value of the Starting Frame Number is:

0 or 1

N + 4 + 4 k + (k div3), N + 5 + 4k + (k div3) (NOTE 1)

2

N + 5 + 4 k + (k div3)

0 ≤ k ≤ 8191

Example :

Starting Frame Number Description (13-bit field)

k = 1 0000000000001 block with first TDMA frame number = N+8 or N+9

k = 2 0000000000010 block with first TDMA frame number = N+13

k = 3 0000000000011 block with first TDMA frame number = N+17 or N+18

NOTE 1: In these cases, only one of the frame numbers N+4+4k+kdiv3 or N+5+4k+kdiv3 is valid, because the other corresponds to an idle frame, depending on the position of the block in the multi-frame.

NOTE 2: The value of (k+1) gives the number of relative blocks. The maximum number of relative blocks is therefore 8192 ; this value was chosen according to the interval of time encoded by the Starting Time IE in 3GPP TS 04.08 (32024 frames).

NOTE 3: The value (k=0) should not be used, so as to leave time for the MS to analyse the message and get ready to receive or transmit.

12.22 (void)

12.23 Cell Identification

The Cell Identification information element is used to uniquely identify the cell.

Table 12.23.1: Cell Identification information element

< Cell Identification IE > ::=

< Location Area Identification IE : octet (5) > — 3GPP TS 04.08

< RAC : bit (8) >

< Cell Identity IE : octet (2) > ; — 3GPP TS 04.08

Table 12.23.2: Cell Identification information element details

Location Area Identity IE (5 octet field)
This field is coded using the V format of the type 3 information element Location Area Identification defined in 3GPP TS 04.08.

RAC (8 bit field)
This field is the binary representation of the Routing Area Code, see 3GPP TS 03.03.

Cell Identity IE (2 octet field)
This field is coded using the V format of the type 3 information element Cell Identity defined in 3GPP TS 04.08.

12.24 GPRS Cell Options

The GPRS Cell Options information element is used to control a set of cell options related to GPRS.

This information element may include a nested Extension Bit information element to allow future extension of cell option parameters.

Table 12.24.1: GPRS Cell Options information element

< GPRS Cell Options IE > ::=

< NMO : bit (2) >

< T3168 : bit (3) >

< T3192 : bit (3) >

< DRX_TIMER_MAX : bit (3) >

< ACCESS_BURST_TYPE : bit >

< CONTROL_ACK_TYPE : bit >

< BS_CV_MAX : bit (4) >

{ 0 | 1 < PAN_DEC : bit (3) >

< PAN_INC : bit (3) >

< PAN_MAX : bit (3) > }

— Optional extension information:

{ 0 | 1 <Extension Length : bit (6)>

< bit (val(Extension Length) + 1)

& { <Extension Information > ! { bit ** = <no string> } } > } ;

< Extension Information> : : =

{ 0 | 1 – EGPRS supported by the cell if the choice bit is set to ‘1’

<EGPRS_PACKET_ CHANNEL_REQUEST : bit>

< BEP_PERIOD : bit (4) > }

<PFC_FEATURE_MODE: bit>

<DTM_SUPPORT: bit>

<BSS_PAGING_COORDINATION: bit>

<spare bit > ** ;

Table 12.24.2: GPRS Cell Options information element details

NMO (2 bit field)
This field is the binary representation of the Network Mode of Operation, see 3GPP TS 03.60:

Bit
2 1
0 0 Network Mode of Operation I
0 1 Network Mode of Operation II
1 0 Network Mode of Operation III
1 1 Reserved.

T3168 (3 bit field)
This field is the binary representation of the timeout value of timer T3168. Range: 0 to 7. The timeout value is given as the binary value plus one in units of 500millisecond.

T3192 (3 bit field)
This field is the binary representation of the timeout value of timer T3192. Range: 0 to 7. The timeout value is given in the following table. In the case of 0 msec, timer is not started and the mobile station follows procedures defined in 9.3.2.5 and 9.3.3.5:

bit
3 2 1
0 0 0 500 msec
0 0 1 1000 msec
0 1 0 1500 msec
0 1 1 0 msec
1 0 0 80 msec
1 0 1 120 msec
1 1 0 160 msec
1 1 1 200 msec

DRX_TIMER_MAX (3 bit field)
This field is the binary representation of the parameter DRX_TIMER_MAX. Range: 0 to 7. The parameter value is given as two taken to the power of the binary value minus one (2 (bv – 1) ) in units of 1 second. The binary value zero indicates the parameter value zero (i.e, the parameter takes the values: 0, 1 s, 2 s, 4 s, .. 64 s.)

ACCESS_BURST_TYPE (1 bit field)
The ACCESS_BURST_TYPE field indicates if the 8 or 11 bit format shall be used in the PACKET CHANNEL REQUEST message, the PTCCH uplink block (3GPP TS 04.04) and in the PACKET CONTROL ACKNOWLEDGMENT message when the format is four access bursts. The field is coded according to the following table:

0 8-bit format shall be used
1 11-bit format shall be used

CONTROL_ACK_TYPE (1 bit field)
This field is the binary representation of the default format of the PACKET CONTROL ACKNOWLEDGMENT message:

0 default format is four access bursts
1 default format is RLC/MAC control block.

BS_CV_MAX (4 bit field)
This field is the binary representation of the parameter BS_CV_MAX. Range: 0 to 15. The value BS_CV_MAX=0 shall be interpreted as value BS_CV_MAX=1 for calculation of T3200 and N3104max values.

PAN_DEC (3 bit field)
This field is the binary representation of the parameter PAN_DEC. If the field in not included, the default value 0 shall be used. Range: 0 to 7.

PAN_INC (3 bit field)
This field is the binary representation of the parameter PAN_INC. If the field in not included, the default value 0 shall be used. Range: 0 to 7.

PAN_MAX (3 bit field)
This field defines the maximum value allowed for counter N3102.

bit
3 2 1
0 0 0 maximum value allowed for counter N3102 is 4
0 0 1 maximum value allowed for counter N3102 is 8
. . .
1 1 1 maximum value allowed for counter N3102 is 32

If the PAN_MAX field in not included, the default value 0 (i.e. N3102 max = 4) shall be used.

EGPRS_PACKET_CHANNEL_REQUEST (1 bit field)

0 EGPRS capable MSs shall use EGPRS PACKET CHANNEL REQUEST message for uplink TBF establishment on the PRACH when there is a PBCCH in the cell or on the RACH when there is no PBCCH in the cell.

1 EGPRS capable MSs shall use two phase packet access with PACKET CHANNEL REQUEST message on the PRACH for uplink TBF establishment when there is a PBCCH in the cell. EGPRS capable MSs shall use two phase packet access with CHANNEL REQUEST message on the RACH when there is no PBCCH in the cell.

BEP_PERIOD (4 bit field)
This field contains the bit error probability (BEP) filter averaging period, refer to 3GPP TS 05.08.

PFC_FEATURE_MODE (1 bit field)
0 The network does not support packet flow context procedures.
1 The network supports packet flow context procedures.

DTM_SUPPORT (1 bit field)
This field indicates whether the cell supports DTM or not. It is coded as follows:
0 The cell does not support DTM procedures.
1 The cell supports DTM procedures.

BSS_PAGING_COORDINATION (1 bit field)
This field indicates the network support of CS paging co-ordination in packet transfer mode during network mode of operation II and III. This field shall be ignored by the mobile station during network mode of operation I. It is coded as follows:
0 The cell does not support Circuit-Switched paging co-ordination
1 The cell supports Circuit-Switched paging co-ordination

12.25 PCCCH Organization Parameters

The PCCCH Organization Parameters information element is used to control the organization of PCCCHs present in the cell. This information element contains general PCCCH organization parameters.

Table 12.25.1: PCCCH Organization Parameters information element

< PCCCH Organization Parameters IE > ::=

< BS_PCC_REL : bit >

< BS_PBCCH_BLKS : bit (2) >

< BS_PAG_BLKS_RES : bit (4) >

< BS_PRACH_BLKS : bit (4) > ;

Table 12.25.2: PCCCH Organization Parameters information element details

BS_PCC_REL (1 bit field)
The BS_PCC_REL field indicates if set = 1 that the last PDCH carrying PCCCH and PBCCH will be released shortly. All mobile stations on PCCCH shall then as soon as this information has been received return to CCCH and there obey the information sent on BCCH as specified in 3GPP TS 04.08. If the field is set = 0, no channel release is pending.

BS_PBCCH_BLKS (2 bit field)
The BS_PBCCH_BLKS field indicates the number of blocks allocated to the PBCCH in the multiframe. The field is coded as the binary representation of BS_PBCCH_BLKS as defined in 3GPP TS 05.02 minus 1.

BS_PAG_BLKS_RES (4 bit field)
The BS_PAG_BLKS_RES field indicates the number of blocks on each PDCH carrying the PCCCH per multiframe where neither PPCH nor PBCCH should appear. The field is coded as the binary representation of BS_PAG_BLKS_RES as defined in 3GPP TS 05.02. Range: 0-12. All other values are reserved and shall be interpreted as the default value 0.

BS_PRACH_BLKS (4 bit field)
The BS_PRACH_BLKS field indicates the number of blocks reserved in a fixed way to the PRACH channel on any PDCH carrying PCCCH (see 3GPP TS 05.02). The field is coded as the binary representation of BS_PRACH_BLKS as defined in 3GPP TS 05.02. Range: 0-12. All other values are reserved and shall be interpreted as no Block reserved for PRACH.

12.26 Extension Bits IE

The Extension Bits information element is used to provide a generalized means for possible future extension within a message. This information element is variable length and contains the length indicator and spare bits.

Table 12.26.1: Extension Bits information element

< Extension Bits IE > ::=

< extension length : bit (6) >

< spare bit (val(extension length)+1) > ;

12.27 Non GPRS Cell Options IE

The Non GPRS Cell Options IE is used to provide mobile stations operating in mode A or B with a repeated subset of BCCH information required for entering dedicated, group receive or group transmit mode.

Table 12.27.1: Non GPRS Cell Options information element

< Non GPRS Cell Options IE > ::=

< ATT : bit > — Attach/Detach allowed

{ 0 | 1 < T3212 : bit (8) > } — Time-out value for periodic update

< NECI : bit > — Half rate support

< PWRC : bit > — Power Control indicator

< DTX : bit (2) > — DTX indicator

< RADIO-LINK-TIMEOUT : bit (4) > — Supervisory timer for RR connection

< BS-AG-BLKS-RES : bit (3) > — number of blocks reserved for access grant

< CCCH-CONF : bit (3) > — physical channel configuration for CCCH

< BS-PA-MFRMS : bit (3) > — number of 51 multiframes between

— transmission of paging messages

< MAX-RETRANS : bit (2) > — maximum number of retransmissions

< TX-INTEGER : bit (4) > — number of slots to spread transmission

< EC : bit > — emergency call allowed

< MS-TXPWR-MAX-CCCH : bit (5) > — maximum Tx power level

Optional extension information:

{ 0 | 1 < Extension Length : bit (6) >

< bit (val(Extension Length) + 1)

& { <Extension Information > ! { bit ** = <no string> } } > } ;

< Extension Information > ::=

< ECSC: bit > — Early Classmark Sending Control

< 3G ECSR > — 3G Early Classmark Sending Restriction

< spare bit > ** ;

Table 12.27.2: Non GPRS Cell Options information element details

For detailed descriptions of all elements see 3GPP TS 04.18
If the optional T3212 parameter is not included, no periodic updating shall be performed.

ECSC (1 bit field)
This field defines the Early Classmark Sending Control.

0 Early Classmark Sending is forbidden
1 Early Classmark Sending is allowed

If the optional ECSC parameter is not included, early classmark sending is allowed. For a detailed description see 3GPP TS 04.18.

3G ECSR (1 bit field)
This field defines the 3G Early Classmark Sending Restriction.

0 Neither UTRAN nor cdma2000 classmark change message shall be sent with the Early Classmark Sending
1 The sending of UTRAN and CDMA2000 Classmark Sending messages is controlled
by the Early Classmark Sending Control parameter

If the optional 3G Early Classmark Sending Restriction parameter is not included, the default value ‘0’ shall be assumed. For a detailed description see 3GPP TS 04.18.

12.28 LSA Parameters

The LSA Parameters information element is used for cell reselection by SoLSA mobile stations. The IE contains a list of LSA_ID(s) corresponding either to the entries in the ‘Add Frequency list struct’ defined in the Packet Cell Change Order message and in Packet Measurement Order message or to the entries in the Neighbour Cell Parameters when used in the packet System Information 3 and 3bis messages. Some entries in the ‘LSA parameters IE’ may be empty. In case there are too few entries in the ‘LSA parameters IE’, empty entries shall be added at the end. In case there are too many entries in the ‘LSA parameters IE’, the last shall be discarded.

Table 12.28.1/3GPP TS 04.60: LSA Parameters information element

< LSA Parameters IE > ::=

< NR_OF_FREQ_OR_CELLS : bit (5) >:
{ < LSA ID information : < LSA ID information struct >> * (val(NR_OF_FREQ_OR_CELLS)) };

< LSA ID information struct > ::=
{ 1 { 0 < LSA_ID : bit (24) >

|1 < ShortLSA_ID : bit (10) >} } ** 0 ;

Table 12.28.2/3GPP TS 04.60: LSA Parameters information element details

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 03.03.

Short LSA_ID (10 bit field)
The purpose of the Short LSA_ID field is to identify a LSA. The LSA ID defined by the Short LSA_ID is a LSA_ID as specified in 3GPP TS 03.03 with bit 0 set to "0" bit 1 to 10 set to the value of the Short LSA_ID field (LSB in bit 1, MSB in bit 10) and bit 11 to 23 set to "0".

12.29 COMPACT reduced MA

Table 12.29.1/3GPP TS 04.60: COMPACT reduced MA information element

< COMPACT reduced MA IE > ::=

<Length of Reduced MA bitmap : bit (7) >

<Reduced MA bitmap : bit( val( Length of Reduced MA bitmap ) ) >

{ 0 | 1 <MAIO_2 : bit(6) >};

Table 12.29.2/3GPP TS 04.60: COMPACT reduced MA information element details

Length of Reduced MA bitmap (7 bit field)
This field is the binary representation of the length (in bits) of the field Reduced MA bitmap.
If set to 0, then no reduced Mobile Allocation is used.
Range 0 to 127.

Reduced MA bitmap (bitmap)
This field gives the reduced Mobile Allocation.
This bitmap uses the list of frequencies given in the current Mobile Allocation, i.e. the Mobile Allocation used by the mobile for the assigned TBF. These radio frequency channels shall be arranged in the order of ascending ARFCN, except for ARFCN = 0, if included, which shall be put last.

The first bit position in the reduced MA bitmap corresponds to the last ARFCN put in the list, the last bit position corresponds to the first ARFCN put in the list. Each bit position is coded:

0 the corresponding radio frequency channel does not belong to the reduced MA;
1 the corresponding radio frequency channel belongs to the reduced MA.

MAIO_2 (6 bit field)
This field is present when a reduced MA is used, indicating more than one frequency.
This parameter is the binary representation of the mobile allocation index offset (MAIO) to be used on blocks using a reduced Mobile Allocation.
Range 0 to 63.

12.30 MS Radio Access Capability 2

The MS Radio Access Capability 2 information element is used to provide the radio part of the network with information concerning radio aspects of the mobile station. The contents may affect the manner in which the network handles the operation of the mobile station.

For the indication of the Access Technology Types the following conditions shall apply (see 3GPP TS 24.008 for the definition of the parameters):

– Among the three Access Technology Types GSM 900-P, GSM 900-E and GSM 900-R only one shall be present.

– Due to shared radio frequency channel numbers between GSM 1800 and GSM 1900, the mobile station should provide the relevant radio access capability for either GSM 1800 band OR GSM 1900 band, not both.

– If the alternative coding by using the Additional access technologies struct is chosen by the mobile station, the mobile station shall indicate its radio access capability for the serving BCCH frequency band in the first included Radio Access Capabilities struct.

– If this information element is sent during a GPRS TBF establishment, the mobile station should indicate as many as possible of its supported Access Technology Types. The maximum number of indicated Access Technology Types depends on the remaining bits left in the RLC/MAC message containing the MS Radio Access Capability 2 IE. The radio access capability for the serving BCCH frequency band shall be part of the indicated technologies, the inclusion of any other radio access capability is a mobile station implementation option.

– If this information element is sent during an EGPRS TBF establishment, the mobile station shall indicate its supported Access Technology Types within the ones that are requested by the network or the access technology of the serving BCCH frequency band, as specified by the relevant procedures.

Table 12.30.1/3GPP TS 04.60: MS Radio Access Capability 2 information element

< MS Radio Access Capability 2 IE > ::=

< MS RA capability : < MS RA capability value part struct > > ;

Table 12.30.2/3GPP TS 04.60: MS Radio Access Capability 2 information element details

MS RA capability
This information element is coded as defined by the MS RA capability value part defined in the MS Radio Access Capability IE defined in 3GPP TS 24.008. When this information element is sent, all spare bits shall be suppressed by the transmitter.