< Extension Information> : : =

{ { — R99 extension:

{ 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 > }

{ — REL‑4 extension:

< CCN_ACTIVE : bit >

< NW_EXT_UTBF : bit > }

{ — REL 6 extension:

< MULTIPLE_TBF_CAPABILITY : bit >

< EXT_UTBF_NODATA : bit >

< DTM_ENHANCEMENTS_CAPABILITY : bit >

{ 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 > } }

{ — Rel-7 extension:

< REDUCED_LATENCY_ACCESS : bit > }

{ — Rel-10 extension:

< NMO_I_ALTERNATE: bit > }

< spare bit > ** } // ; — Extension information may be truncated between released versions of the protocol.

— The receiver shall assume the value zero for any truncated bit.

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 500 ms.

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 ms, the timer is not started and the mobile station shall consider T3192 as immediately expiring and follow procedures defined in sub-clauses 9.3.2.6 and 9.3.3.5:

Bit
3 2 1
0 0 0 500 ms
0 0 1 1000 ms
0 1 0 1500 ms
0 1 1 0 ms
1 0 0 80 ms
1 0 1 120 ms
1 1 0 160 ms
1 1 1 200 ms

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 PS HANDOVER ACCESS message, the PTCCH uplink block (3GPP TS 44.004) 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.

As an exception, a mobile station that has enabled PEO (see 3GPP TS 43.064 [5]) shall always send an EGPRS PACKET CHANNEL REQUEST message with access type ‘PEO One Phase Access Request’ (see Table 11.2.5a.4) on the RACH regardless of the value of this field.

BEP_PERIOD (4 bit field)
This field is applicable in EGPRS TBF mode. For the definition of this field, refer to 3GPP TS 45.008.

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.

CCN_ACTIVE (1 bit field)
This field indicates whether CCN is enabled in the cell or not. It is coded as follows:

0 CCN is disabled in the cell.
1 CCN is enabled in the cell.

NW_EXT_UTBF (1 bit field)
This field indicates whether the network supports the extended uplink TBF mode:

0 The extended uplink TBF mode is not supported by the network.
1 The extended uplink TBF mode is supported by the network.

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 or by a mobile station capable of DTM in a cell supporting DTM procedures, in which cases Circuit-Switched paging coordination in packet transfer mode shall be provided by the network. It is coded as follows:

0 The cell does not support Circuit-Switched paging coordination
1 The cell supports Circuit-Switched paging coordination

MULTIPLE_TBF_CAPABILITY (1 bit field)
This field indicates whether or not the cell supports multiple TBF procedures for A/Gb mode:

0 The cell does not support multiple TBF procedures.
1 The cell supports multiple TBF procedures.

EXT_UTBF_NODATA (1 bit field)
This field indicates whether the mobile station during extended uplink TBF mode may refrain from sending PACKET UPLINK DUMMY CONTROL BLOCK messages when there is no other RLC/MAC block ready to send in an uplink radio block allocated by the network.

0 The mobile station shall send a PACKET UPLINK DUMMY CONTROL BLOCK message when there is no other RLC/MAC block ready to send in an uplink radio block allocated by the network.

1 The mobile station may refrain from sending a PACKET UPLINK DUMMY CONTROL BLOCK message when there is no other RLC/MAC block ready to send in an uplink radio block allocated by the network.

DTM_ENHANCEMENTS_CAPABILITY (1 bit field)
This field indicates whether the cell supports enhanced DTM CS establishment and enhanced DTM CS release or not. It is coded as follows:

0 The cell does not support enhanced DTM CS establishment and enhanced DTM CS release procedures.
1 The cell supports enhanced DTM CS establishment and enhanced DTM CS release procedures.

DEDICATED_MODE_MBMS_NOTIFICATION_SUPPORT (1 bit field)
This field indicates whether the cell supports Dedicated Mode MBMS Notification or not. It is coded as follows:

0 The cell does not support the Dedicated Mode MBMS Notification procedures.
1 The cell supports the Dedicated Mode MBMS Notification procedures.

MNCI_SUPPORT (1 bit field)
This field indicates whether the cell supports the distribution of MBMS NEIGHBOURING CELL INFORMATION messages. It is coded as follows:

0 The cell does not support the distribution of MBMS NEIGHBOURING CELL INFORMATION messages
1 The cell supports the distribution of MBMS NEIGHBOURING CELL INFORMATION messages

REDUCED_LATENCY ACCESS (1 bit field)
This field indicates whether the cell supporting the EGPRS PACKET CHANNEL REQUEST message also supports "One Phase Access Request by Reduced Latency MS", see sub-clause 7.1.2.1.

0 The cell does not support "One Phase Access Request by Reduced Latency MS".
1 The cell supports "One Phase Access Request by Reduced Latency MS".

NMO_I_ALTERNATE (1 bit field)
This field applies only to mobile stations which have the parameter “NMO_I_Behaviour” set to the value of "1" in the NAS configuration Management Object as specified in 3GPP TS 24.368 [50] or in the USIM file NAS_CONFIG as specified in 3GPP TS 31.102 [51] (the USIM file having priority if both parameters exist).

0 The mobile station shall use the Network Mode of Operation indicated in the NMO field.
1 The mobile station shall use Network Mode of Operation I irrespective of the value in the NMO field.