10.5.7 GPRS Common information elements
24.0083GPPCore network protocolsMobile radio interface Layer 3 specificationRelease 18Stage 3TS
10.5.7.1 PDP context status
The purpose of the PDP context status information element is to indicate the state of each PDP context which can be identified by NSAPI.
The PDP context status information element is a type 4 information element with 4 octets length.
The PDP context status information element is coded as shown in figure 10.5.148/3GPP TS 24.008 and table 10.5.164/3GPP TS 24.008.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
PDP context status IEI |
octet 1 |
|||||||
|
Length of PDP context status contents |
Octet 2 |
|||||||
|
NSAPI (7) |
NSAPI (6) |
NSAPI (5) |
NSAPI (4) |
NSAPI (3) |
NSAPI (2) |
NSAPI (1) |
NSAPI (0) |
octet 3 |
|
NSAPI (15) |
NSAPI (14) |
NSAPI (13) |
NSAPI (12) |
NSAPI (11) |
NSAPI (10) |
NSAPI (9) |
NSAPI (8) |
octet 4 |
Figure 10.5.148/3GPP TS 24.008 PDP context status information element
Table 10.5.164/3GPP TS 24.008: PDP context status information element
|
NSAPI(x) shall be coded as follows: NSAPI(0) – NSAPI(4): are coded as ‘0’ and shall be treated as spare in this version of the protocol. NSAPI(5) – NSAPI(15): 0 indicates that the SM state of the corresponding PDP context is PDP-INACTIVE. 1 indicates that the SM state of the corresponding PDP context is not PDP-INACTIVE. |
10.5.7.2 Radio priority
The purpose of the radio priority information element is to specify the priority level that the MS shall use at the lower layers for transmission of data related to a PDP context or for mobile originated SMS transmission.
The radio priority information element is coded as shown in figure 10.5.145/3GPP TS 24.008 and table 10.5.161/3GPP TS 24.008.
The radio priority is a type 1 information element.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
Radio priority IEI |
0 spare |
Radio priority level value |
octet 1 |
|||||
Figure 10.5.145/3GPP TS 24.008: Radio priority information element
Table 10.5.161/3GPP TS 24.008: Radio priority information element
|
Radio priority level value (octet 1) Bits 3 2 1 0 0 1 priority level 1 (highest) 0 1 0 priority level 2 0 1 1 priority level 3 1 0 0 priority level 4 (lowest) All other values are interpreted as priority level 4 by this version of the protocol. |
10.5.7.3 GPRS Timer
The purpose of the GPRS timer information element is to specify GPRS specific timer values, e.g. for the READY timer.
The GPRS timer is a type 3 information element with 2 octets length.
The GPRS timer information element is coded as shown in figure 10.5.146/3GPP TS 24.008 and table 10.5.172/3GPP TS 24.008.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|||
|
GPRS Timer IEI |
octet 1 |
|||||||||
|
Unit |
Timer value |
octet 2 |
||||||||
Figure 10.5.146/3GPP TS 24.008: GPRS Timer information element
Table 10.5.172/3GPP TS 24.008: GPRS Timer information element
|
Timer value (octet 2) Bits 5 to 1 represent the binary coded timer value. Bits 6 to 8 defines the timer value unit for the GPRS timer as follows: Bits 8 7 6 0 0 0 value is incremented in multiples of 2 seconds 0 0 1 value is incremented in multiples of 1 minute 0 1 0 value is incremented in multiples of decihours 1 1 1 value indicates that the timer is deactivated. Other values shall be interpreted as multiples of 1 minute in this version of the protocol. |
10.5.7.4 GPRS Timer 2
The purpose of the GPRS timer 2 information element is to specify GPRS specific timer values, e.g. for the timer T3302 or timer T3319.
The GPRS timer 2 is a type 4 information element with 3 octets length.
The GPRS timer 2 information element is coded as shown in figure 10.5.147/3GPP TS 24.008 and table 10.5.163/3GPP TS 24.008.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
GPRS Timer 2 IEI |
octet 1 |
||||||||
|
Length of GPRS Timer 2 contents |
octet 2 |
||||||||
|
GPRS Timer 2 value |
octet 3 |
||||||||
Figure 10.5.147/3GPP TS 24.008: GPRS Timer 2 information element
Table 10.5.163/3GPP TS 24.008: GPRS Timer 2 information element
|
GPRS Timer 2 value is coded as octet 2 of the GPRS timer information element. |
10.5.7.4a GPRS Timer 3
The purpose of the GPRS timer 3 information element is to specify GPRS specific timer values, e.g. for the timer T3396.
The GPRS timer 3 is a type 4 information element with 3 octets length.
The GPRS timer 3 information element is coded as shown in figure 10.5.147a/3GPP TS 24.008 and table 10.5.163a/3GPP TS 24.008.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
||
|
GPRS Timer 3 IEI |
octet 1 |
||||||||
|
Length of GPRS Timer 3 contents |
octet 2 |
||||||||
|
Unit |
Timer value |
octet 3 |
|||||||
Figure 10.5.147a/3GPP TS 24.008: GPRS Timer 3 information element
Table 10.5.163a/3GPP TS 24.008: GPRS Timer 3 information element
|
GPRS Timer 3 value (octet 3) Bits 5 to 1 represent the binary coded timer value. Bits 6 to 8 defines the timer value unit for the GPRS timer as follows: Bits 8 7 6 0 0 0 value is incremented in multiples of 10 minutes 0 0 1 value is incremented in multiples of 1 hour 0 1 0 value is incremented in multiples of 10 hours 0 1 1 value is incremented in multiples of 2 seconds 1 0 0 value is incremented in multiples of 30 seconds 1 0 1 value is incremented in multiples of 1 minute 1 1 0 value is incremented in multiples of 320 hours (NOTE 1) 1 1 1 value indicates that the timer is deactivated (NOTE 2). NOTE 1: This timer value unit is only applicable to the T3312 extended value IE, the T3412 extended value IE (see 3GPP TS 24.301 [120]) and the T3512 value IE (see 3GPP TS 24.501 [167]). If the UE receives the IE in an integrity protected message, then it shall interpret the value as multiples of 320 hours. Otherwise it shall interpret the value as multiples of 1 hour. NOTE 2: This timer value unit is not applicable to the T3412 extended value IE. If this timer value is received, the T3412 extended value IE shall be considered as not included in the message (see 3GPP TS 24.301 [120]). |
10.5.7.5 Radio priority 2
The purpose of the radio priority 2 information element is to specify the priority level that the MS shall use at the lower layers for transmission of mobile originated TOM8 transmission.
The radio priority 2 information element is coded as shown in figure 10.5.7.5-1/3GPP TS 24.008 and table 10.5.7.5-1/3GPP TS 24.008.
The radio priority is a type 1 information element.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
Radio priority 2 IEI |
0 spare |
Radio priority level value |
octet 1 |
|||||
Figure 10.5. 7.5-1/3GPP TS 24.008: Radio priority 2 information element
Table 10.5. 7.5-1/3GPP TS 24.008: Radio priority 2 information element
|
Radio priority level value (octet 1, bits 1-3) |
||||
|
Bits |
||||
|
3 |
2 |
1 |
||
|
0 |
0 |
1 |
priority level 1 (highest) |
|
|
0 |
1 |
0 |
priority level 2 |
|
|
0 |
1 |
1 |
priority level 3 |
|
|
1 |
0 |
0 |
priority level 4 (lowest) |
|
|
All other values are interpreted as priority level 4 by this version of the protocol. |
||||
10.5.7.6 MBMS context status
The purpose of the MBMS context status information element is to indicate the state of each MBMS context which can be identified by an NSAPI.
The MBMS context status information element is a type 4 information element with a minimum length of 2 octets and a maximum length of 18 octets.
The MBMS context status information element is coded as shown in figure 10.5.149/3GPP TS 24.008 and table 10.5.165/3GPP TS 24.008.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
MBMS context status IEI |
octet 1 |
|||||||
|
Length of MBMS context status contents |
octet 2 |
|||||||
|
NSAPI (135) |
NSAPI (134) |
NSAPI (133) |
NSAPI (132) |
NSAPI (131) |
NSAPI (130) |
NSAPI (129) |
NSAPI (128) |
octet 3 |
|
NSAPI (143) |
NSAPI (142) |
NSAPI (141) |
NSAPI (140) |
NSAPI (139) |
NSAPI (138) |
NSAPI (137) |
NSAPI (136) |
octet 4 |
|
NSAPI (255) |
NSAPI (254 |
NSAPI (253) |
NSAPI (252) |
NSAPI (251) |
NSAPI (250) |
NSAPI (249) |
NSAPI (248) |
octet 18 |
Figure 10.5.149/3GPP TS 24.008 MBMS context status information element
Table 10.5.165/3GPP TS 24.008: MBMS context status information element
|
For x = 128 to 255, NSAPI(x) shall be coded as follows: 0 indicates that the SM state of the corresponding MBMS context is PDP-INACTIVE. If octets are not included in the information element, the receiver shall interprete the NSAPI(x) values of these octets as set to 0. |
10.5.7.7 Uplink data status
The purpose of the Uplink data status information element is to indicate to the network which preserved PDP contexts have uplink data pending.
The Uplink data status information element is a type 4 information element with 4 octets length.
The Uplink data status information element is coded as shown in figure 10.5.149/3GPP TS 24.008 and table 10.5.166/3GPP TS 24.008.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
Uplink data status IEI |
octet 1 |
|||||||
|
Length of Uplink data status contents |
octet 2 |
|||||||
|
NSAPI (7) |
NSAPI (6) |
NSAPI (5) |
Spare (0) |
Spare (0) |
Spare (0) |
Spare (0) |
Spare (0) |
octet 3 |
|
NSAPI (15) |
NSAPI (14) |
NSAPI (13) |
NSAPI (12) |
NSAPI (11) |
NSAPI (10) |
NSAPI (9) |
NSAPI (8) |
octet 4 |
Figure 10.5.149A/3GPP TS 24.008 Uplink data status information element
Table 10.5.166/3GPP TS 24.008: Uplink data status information element
NSAPI uplink status (octet 3 and 4)
Octet 3, bits 1 to 5 are all spare and shall be encoded as 0
NSAPI(5) – NSAPI(15) (octets 3 – 4):
0 no uplink data are pending for the preserved PDP context or the PDP context is PDP-INACTIVE or is PDP-ACTIVE with a RAB already established.
1 uplink data are pending for the preserved PDP context.
10.5.7.8 Device properties
The purpose of the Device properties information element is to indicate if the MS is configured for NAS signalling low priority. The network uses the Device properties information element for core-network congestion handling and for charging purposes.
The Device properties information element is coded as shown in figure 10.5.7.8.1/3GPP TS 24.008 and table 10.5.7.8.1/3GPP TS 24.008.
The Device properties is a type 1 information element.
|
8 |
7 |
6 |
5 |
4 |
3 |
2 |
1 |
|
|
Device properties IEI |
0 Spare |
0 Spare |
0 Spare |
Low priority |
octet 1 |
|||
Figure 10.5.7.8.1/3GPP TS 24.008: Device properties information element
Table 10.5.7.8.1/3GPP TS 24.008: Device properties information element
|
Low priority (octet 1) |
||||
|
Bit |
||||
|
1 |
||||
|
0 |
MS is not configured for NAS signalling low priority |
|||
|
1 |
MS is configured for NAS signalling low priority |
|||
|
The value "0" can also be used by an MS configured for NAS signalling low priority for the exception cases specified in subclause 1.8. |
||||
|
Bits 2, 3 and 4 of octet 1 are spare and shall be coded as zero. |
||||