11 General information elements coding
08.183GPPBase Station System (BSS) - Serving GPRS Support Node (SGSN)BSS GPRS ProtocolGeneral Packet Radio Service (GPRS)Release 1999TS
The figures and text in this section describe the Information Elements contents.
11.1 General structure of the information elements
Refer to General Structure Of The Information Elements/3GPP TS 08.16 [16].
11.2 Information element description
Refer to Information Element Description/3GPP TS 08.16 [16].
11.3 Information Element Identifier (IEI)
An Information Element Identifier (IEI) is identified by the same coding in all BSSGP PDUs.
Table 11.1: IEI types
IEI coding | IEI Types |
---|---|
x00 | Alignment Octets |
x01 | Bmax default MS |
x02 | BSS Area Indication |
x03 | Bucket Leak Rate |
x04 | BVCI |
x05 | BVC Bucket Size |
x06 | BVC Measurement |
x07 | Cause |
x08 | Cell Identifier |
x09 | Channel needed |
x0a | DRX Parameters |
x0b | eMLPP-Priority |
x0c | Flush Action |
x0d | IMSI |
x0e | LLC-PDU |
x0f | LLC Frames Discarded |
x10 | Location Area |
x11 | Mobile Id |
x12 | MS Bucket Size |
x13 | MS Radio Access Capability |
x14 | OMC Id |
x15 | PDU In Error |
x16 | PDU Lifetime |
x17 | Priority |
x18 | QoS Profile |
x19 | Radio Cause |
x1a | RA-Cap-UPD-Cause |
x1b | Routeing Area |
x1c | R_default_MS |
x1d | Suspend Reference Number |
x1e | Tag |
x1f | TLLI |
x20 | TMSI |
x21 | Trace Reference |
x22 | Trace Type |
x23 | TransactionId |
x24 | Trigger Id |
x25 | Number of octets affected |
x26 | LSA Identifier List |
x27 | LSA Information |
x28 | Packet Flow Identifier |
x29 | Packet Flow Timer |
x3a | Aggregate BSS QoS Profile (ABQP) |
x3b | Feature Bitmap |
x3c | Bucket_Full Ratio |
x3d | Service UTRAN CCO (Cell Change Order) |
RESERVED | All values not explicitly shown are reserved for future use and shall be treated by the recipient as an unknown IEI |
11.3.1 Alignment octets
The Alignment Octets are used to align a subsequent IEI onto a 32 bit boundary. The element coding is:
Table 11.2: Alignment octets IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator a) | |||||||
octet 3-5 | spare octet |
a) The Length Indicator may indicate that from 0 to 3 spare octets are present.
11.3.2 Bmax default MS
This information element indicates the default bucket size (Bmax) in octets for an MS. The element coding is:
Table 11.3: Bmax default MS IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-4 | Bmax |
The Bmax field is coded as in section 3GPP TS 08.18 BVC Bucket Size/Bmax.
11.3.3 BSS Area Indication
This element is used to indicate that the paging shall be done in all the cells within the BSS. The element coding is:
Table 11.4: BSS Area Indication IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | BSS indicator |
The coding of octet 2 is a binary number indicating the Length of the remaining element.
The coding of octet 3 shall not be specified. The recipient shall ignore the value of this octet.
11.3.4 Bucket Leak Rate (R)
This information element indicates the leak rate (R) to be applied to a flow control bucket. The element coding is:
Table 11.5: Bucket Leak Rate IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | R Value (MSB) | |||||||
octet 4 | R Value (LSB) |
The R field is the binary encoding of the rate information expressed in 100 bits/sec increments, starting from 0 x 100 bits/sec until 65 535 x 100 bits/sec (6 Mbps).
11.3.5 BVC Bucket Size
This information element indicates the maximum bucket size (Bmax) in octets for a BVC. The element coding is:
Table 11.6: BVC Bucket Size IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | Bmax (MSB) | |||||||
octet 4 | Bmax (LSB) |
The Bmax field is the binary encoding of the bucket-size information expressed in 100 octet increments, starting from 0 x 100 octets until 65 535 x 100 octets (6 Mbytes).
11.3.6 BVCI (BSSGP Virtual Connection Identifier)
The BVCI identifies a BVC. The element coding is:
Table 11.7: BVCI IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-4 | Unstructured value |
11.3.7 BVC Measurement
This information element describes average queuing delay for a BVC. The element coding is:
Table 11.8: BVC Measurement IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3,4 | Delay Value (in centi-seconds) |
The Delay Value field is coded as a 16-bit integer value in units of centi-seconds (one hundredth of a second). This coding provides a range of over 10 minutes in increments of 10 msec. As a special case, the hexadecimal value 0xFFFF (decimal 65 535) shall be interpreted as "infinite delay".
11.3.8 Cause
The Cause information element indicates the reason for an exception condition. The element coding is:
Table 11.9: Cause IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | Cause value |
Table 11.10: Cause coding
Cause value | semantics of coding |
Hexadecimal | |
All values not listed below shall be treated as "protocol error – unspecified" | |
x00 | Processor overload |
x01 | Equipment failure |
x02 | Transit network service failure |
x03 | Network service transmission capacity modified from zero kbps to greater than zero kbps |
x04 | Unknown MS |
x05 | BVCI unknown |
x06 | cell traffic congestion |
x07 | SGSN congestion |
x08 | O & M intervention |
x09 | BVCI-blocked |
x0a | PFC create failure |
x20 | Semantically incorrect PDU |
x21 | Invalid mandatory information |
x22 | Missing mandatory IE |
x23 | Missing conditional IE |
x24 | Unexpected conditional IE |
x25 | Conditional IE error |
x26 | PDU not compatible with the protocol state |
x27 | Protocol error – unspecified |
x28 | PDU not compatible with the feature set |
11.3.9 Cell Identifier
This information element uniquely identifies one cell. The element coding is:
Table 11.11: Cell Identifier IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||
octet 1 | IEI | ||||||||
octet 2,2a | Length Indicator | ||||||||
octets 3-8 | Octets 3 to 8 contain the value part (starting with octet 2) of the Routing Area Identification IE defined in 3GPP TS 04.08 [11], not including 3GPP TS 04.08 IEI | ||||||||
octets 9-10 | Octets 9 and 10 contain the value part (starting with octet 2) of the Cell Identity IE defined in 3GPP TS 04.08 [11], not including 3GPP TS 04.08 IEI |
11.3.10 Channel needed
This information element is coded as defined in 3GPP TS 09.18. It is relevant to circuit-switched paging requests. The element coding is:
Table 11.12: Channel needed IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | Rest of element coded as the value part of the Channel Needed PDU defined in 3GPP TS 09.18, not including 3GPP TS 09.18 IEI and 3GPP TS 09.18 length indicator |
11.3.11 DRX Parameters
This information element contains MS specific DRX information. The element coding is:
Table 11.13: DRX Parameters IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-n | Rest of element coded as the value part defined in 3GPP TS 04.08, not including 3GPP TS 04.08 IEI and 3GPP TS 04.08 octet length indicator |
11.3.12 eMLPP-Priority
This element indicates the eMLPP-Priority of a PDU. The element coding is:
Table 11.14: eMLPP-Priority IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | Rest of element coded as the value part of the eMLPP-Priority IE defined in 3GPP TS 08.08, not including 3GPP TS 08.08 IEI and 3GPP TS 08.08 length indicator |
11.3.13 Flush Action
The Flush action information element indicates to the SGSN the action taken by the BSS in response to the flush request. The element coding is:
Table 11.15: Flush Action IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | Action value |
Table 11.16: Action coding
Action value | semantics of coding |
x00 | LLC-PDU(s) deleted |
x01 | LLC-PDU(s) transferred |
All values not explicitly shown are reserved for future use |
11.3.14 IMSI
This information element contains the International Mobile Subscriber Identity. The element coding is:
Table 11.17: IMSI IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-n | Octets 3-n contain an IMSI coded as the value part (starting with octet 3) of the Mobile Identity IE defined in 3GPP TS 04.08, not including 3GPP TS 04.08 IEI and 3GPP TS 04.08 length indicator |
11.3.15 LLC-PDU
This information element contains an LLC-PDU. The element coding is:
Table 11.18: LLC-PDU IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | LLC-PDU (first part) | |||||||
octet n | LLC-PDU (last part) |
11.3.16 LLC Frames Discarded
This element describes the number of LLC frames that have been discarded inside a BSS. The element coding is:
Table 11.19: LLC Frames Discarded IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | Number of frames discarded (in hexadecimal) |
11.3.17 Location Area
This element uniquely identifies one Location Area. The element coding is:
Table 11.20: Location Area IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octets 3-7 | Octets 3 to 7 contain the value part (starting with octet 2) of the Location Area Identification IE defined in 3GPP TS 04.08 [11], not including 3GPP TS 04.08 IEI |
The coding of octet 2 is a binary number indicating the Length of the remaining element.
11.3.18 LSA Identifier List
This information element uniquely identifies LSAs. The element coding is:
Table 11.48: LSA Identifier List IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-? | Rest of element coded as in 3GPP TS 08.08, not including 3GPP TS 08.08 IEI and 3GPP TS 08.08 length indicator |
11.3.19 LSA Information
This information element uniquely identifies LSAs, the priority of each LSA and the access right outside these LSAs. The element coding is:
Table 11.48: LSA Information IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-? | Rest of element coded as in 3GPP TS 08.08, not including 3GPP TS 08.08 IEI and 3GPP TS 08.08 length indicator |
11.3.20 Mobile Id
The element coding is:
Table 11.21: Mobile Id IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-n | Octets 3-n contain either the IMSI, IMEISV or IMEI coded as the value part (starting with octet 3) of the Mobile Identity IE defined in 3GPP TS 04.08, not including 3GPP TS 04.08 IEI and 3GPP TS 04.08 length indcator |
11.3.21 MS Bucket Size
This information element indicates an MS’s bucket size (Bmax). The element coding is:
Table 11.22: MS Bucket Size IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-4 | Bmax |
The Bmax field is coded as in section 3GPP TS 08.18 BVC Bucket Size/Bmax.
11.3.22 MS Radio Access Capability
This information element contains the capabilities of the ME. The element coding is:
Table 11.23: MS Radio Access Capability IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-? | Rest of element coded as the value part defined in GSM 24.008, not including GSM 24.008 IEI and GSM 24.008 octet length indicator. |
11.3.23 OMC Id
The element coding is:
Table 11.24: OMC Id IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-22 | For the OMC identity, see TS 12.20 |
11.3.24 PDU In Error
The element coding is:
Table 11.25: PDU In Error IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-? | Erroneous BSSGP PDU |
11.3.25 PDU Lifetime
This information element describes the PDU Lifetime for a PDU inside the BSS. The element coding is:
Table 11.26: PDU Lifetime IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-4 | Delay Value |
The Delay Value field is coded as in section 3GPP TS 08.18 BVC Measurement/Delay Value.
11.3.26 PDU Type
The first octet of a BSSGP PDU shall contain the PDU type IE. The PDU type IE is one octet long.
Table 11.27: PDU Types
PDU type coding | PDU Types |
---|---|
PDUs between RL and BSSGP SAPs | |
x00 | DL-UNITDATA |
x01 | UL-UNITDATA |
x02 | RA-CAPABILITY |
x03 | PTM-UNITDATA |
PDUs between GMM SAPs | |
x06 | PAGING PS |
x07 | PAGING CS |
x08 | RA-CAPABILITY-UPDATE |
x09 | RA-CAPABILITY-UPDATE-ACK |
x0a | RADIO-STATUS |
x0b | SUSPEND |
x0c | SUSPEND-ACK |
x0d | SUSPEND-NACK |
x0e | RESUME |
x0f | RESUME-ACK |
x10 | RESUME-NACK |
PDUs between NM SAPs | |
x20 | BVC-BLOCK |
x21 | BVC-BLOCK-ACK |
x22 | BVC-RESET |
x23 | BVC-RESET-ACK |
x24 | BVC-UNBLOCK |
x25 | BVC-UNBLOCK-ACK |
x26 | FLOW-CONTROL-BVC |
x27 | FLOW-CONTROL-BVC-ACK |
x28 | FLOW-CONTROL-MS |
x29 | FLOW-CONTROL-MS-ACK |
x2a | FLUSH-LL |
x2b | FLUSH-LL-ACK |
x2c | LLC-DISCARDED |
x40 | SGSN-INVOKE-TRACE |
x41 | STATUS |
0x50 | DOWNLOAD-BSS-PFC |
0x51 | CREATE-BSS-PFC |
0x52 | CREATE-BSS-PFC-ACK |
0x53 | CREATE-BSS-PFC-NACK |
0x54 | MODIFY-BSS-PFC |
0x55 | MODIFY-BSS-PFC-ACK |
0x56 | DELETE-BSS-PFC |
0x57 | DELETE-BSS-PFC-ACK |
RESERVED | all values not explicitly shown are reserved for future use |
11.3.27 Priority
This element indicates the priority of a PDU. The element coding is:
Table 11.28: Priority IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | Rest of element coded as the value part of the Priority IE defined in 3GPP TS 08.08, not including 3GPP TS 08.08 IEI and 3GPP TS 08.08 length indicator |
11.3.28 QoS Profile
This information element describes the QoS Profile associated with a PDU. The element coding is:
Table 11.29: QoS Profile IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||||
octet 1 | IEI | ||||||||||
octet 2,2a | Length Indicator | ||||||||||
octet 3-4 | Peak bit rate provided by the network, coded as the value part in Bucket Leak Rate/R IE/ 3GPP TS 08.18 a) | ||||||||||
octet 5 | SPARE | C/R | T | A | Precedence |
a) The bit rate 0 (zero) shall mean "best effort" in this IE.
"Precedence" is coded as shown below (complying with 3GPP TS 03.60).
Table 11.30: Precedence coding
coding | semantic | |
DL-UNITDATA | UL-UNITDATA | |
000 | High priority | Radio priority 1 |
001 | Normal priority | Radio priority 2 |
010 | Low priority | Radio priority 3 |
011 | Reserved | Radio priority 4 |
100 | Reserved | Radio Priority Unknown |
All values not allocated are reserved. All reserved values shall be interpreted as value 010.
"A-bit" is coded as shown below.
Table 11.31: "A bit" coding
coding | semantic |
0 | Radio interface uses RLC/MAC ARQ functionality |
1 | Radio interface uses RLC/MAC-UNITDATA functionality |
"T-bit" is coded as shown below.
Table 11.32: "T bit" coding
coding | semantic |
0 | The SDU contains signalling (e.g. related to GMM) |
1 | The SDU contains data |
"C/R-bit" is coded as shown below.
Table 11.24: "C/R bit" coding
coding | semantic |
0 | The SDU contains a LLC ACK or SACK command/response frame type |
1 | The SDU does not contain a LLC ACK or SACK command/response frame type |
11.3.29 Radio Cause
This information element indicates the reason for an exception condition on the radio interface. The element coding is:
Table 11.33: Radio Cause IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | Radio Cause value |
Table 11.34: Radio Cause value
Radio cause value | Semantics of coding |
x00 | Radio contact lost with the MS |
x01 | Radio link quality insufficient to continue communication |
x02 | cell-reselection ordered |
All values not explicitly listed are reserved. If received, they shall be handled as "radio contact lost with the MS". |
11.3.30 RA-Cap-UPD-Cause
The RA-Cap-UPD-Cause indicates the success of the RA-CAPABILITY-UPDATE procedure or the reason of the failure. The element coding is:
Table 11.35: RA-Cap-UPD-Cause IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | RA-Cap-UPD Cause value |
Table 11.36: RA-Cap-UPD Cause value
RA-Cap-UPD cause value | semantics of coding |
x00 | OK, RA capability IE present |
x01 | TLLI unknown in SGSN |
x02 | No RA Capabilities or IMSI available for this MS |
All values not explicitly listed are reserved. If received, they shall be handled as "TLLI unknown in SGSN". |
11.3.31 Routeing Area
This element uniquely identifies one routeing area. The element coding is:
Table 11.37: Routeing Area IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octets 3-8 | Octets 3 to 8 contain the value part (starting with octet 2) of the Routing Area Identification IE defined in 3GPP TS 04.08 [11], not including 3GPP TS 04.08 IEI |
The coding of octet 2 is a binary number indicating the Length of the remaining element.
11.3.32 R_default_MS
This information element indicates the default bucket leak rate (R) to be applied to a flow control bucket for an MS. The element coding is:
Table 11.38: R_default_MS IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-4 | R_default_MS value |
The R_default_MS field is coded as in section 3GPP TS 08.18 Bucket Leak Rate /R Value.
11.3.33 Suspend Reference Number
The Suspend Reference Number information element contains an un-formatted reference number for each suspend/resume transaction. The element coding is:
Table 11.39: Suspend Reference Number IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | Suspend Reference Number |
The Suspend Reference Number is an un-formatted 8 bit field.
11.3.34 Tag
This information element is used to correlate request and response PDUs. The element coding is:
Table 11.40: Tag IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | Unstructured value |
11.3.35 Temporary logical link Identity (TLLI)
The element coding is:
Table 11.41: TLLI IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-6 | Rest of element coded as the value part of the TLLI information element in 3GPP TS 04.08, not including 3GPP TS 04.08 IEI. |
11.3.36 Temporary Mobile Subscriber Identity (TMSI)
The element coding is:
Table 11.42: TMSI IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-6 | Rest of element coded as the value part of the TMSI/P-TMSI information element in 3GPP TS 04.08, not including 3GPP TS 04.08 IEI. |
11.3.37 Trace Reference
This element provides a trace reference number allocated by the triggering entity. The element coding is:
Table 11.43: Trace Reference IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-4 | Trace Reference |
11.3.38 Trace Type
This element provides the type of trace information to be recorded. The element coding is:
Table 11.44: Trace Type IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | This is coded as specified in Technical Specification 3GPP TS 12.08. |
11.3.39 TransactionId
This element indicates a particular transaction within a trace. The element coding is:
Table 11.45: Transaction Id IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-4 | Transaction Id |
11.3.40 Trigger Id
This element provides the identity of the entity which initiated the trace. The element coding is:
Table 11.46: Trigger Id IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-22 | Entity Identity ( typically an OMC identity) |
11.3.41 Number of octets affected
This information element indicates, for an MS, the number of octets transferred or deleted by BSS. The element coding is:
Table 11.47: Number of octets affected IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-5 | number of octets transferred or deleted |
The number of octets transferred or deleted by the BSS may be higher than the maximum Bmax value (6 553 500). SGSN shall handle any value higher than 6 553 500 as the value 6 553 500.
11.3.42 Packet Flow Identifier (PFI)
This information element indicates the Packet Flow Identifier for a BSS Packet Flow Context. The element coding is:
Table 11.48: Packet Flow Identifier (PFI) IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2, 2a | Length Indicator | |||||||
octet 3 | Rest of element coded as the value part of the Packet Flow Identifier information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI |
The BSS shall not negotiate BSS PFCs for the following pre-defined PFI values: Best Effort, Signaling, and SMS.
PFIs have local significance to a mobile station. A BSS Packet Flow Context shall be uniquely identified by the PFI along with the IMSI or TLLI within a routeing area.
11.3.42a (void)
11.3.43 Aggregate BSS QoS Profile
This information element indicates the Aggregate BSS QoS Profile (ABQP) for a BSS Packet Flow Context. The ABQP is considered to be a single parameter with multiple data transfer attributes as defined in 3GPP TS 23.107.
The element coding is:
Table 11.49: Aggregate BSS QoS Profile IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3-? | Rest of element coded as the value part of the QoS information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI and length indicator. The shorter 3-byte form of QoS information is not allowed in BSSGP PDUs. |
11.3.44 GPRS Timer
The purpose of the GPRS timer information element is to specify GPRS specific timer values, e.g. the Packet Flow timer.
Table 11.50: GPRS Timer IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |||
octet 1 | GPRS Timer IEI | |||||||||
octet 2,2a | Length Indicator | |||||||||
octet 3 | Unit Value | Timer value |
Timer value: Bits 5 to 1 represent the binary coded timer value.
Unit 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 does not expire.
Other values shall be interpreted as multiples of 1 minute in this version of the protocol.
11.3.45 Feature Bitmap
The Feature bitmapinformation element indicates the optional features supported by the underlying NSE. The element coding is:
Table 11.51: Feature Bitmap IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||
octet 1 | IEI | ||||||||
octet 2,2a | Length Indicator | ||||||||
octet 3 | Spare | CBL | PFC |
Table 11.52: "PFC bit" coding
coding | semantic |
0 | Packet Flow Context Procedures not supported |
1 | Packet Flow Context Procedures supported |
Table 11.53: “CBL bit” coding
coding | semantic |
0 | Current Bucket Level Procedures not supported |
1 | Current Bucket Level Procedures supported |
11.3.46 Bucket Full Ratio
This information element is used to convey the current bucket counter. It is binary encoded as follows: Bcurrent * (100 / Bmax). The element coding is:
Table 11.53: Bucket Full Ratio IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | |
octet 1 | IEI | |||||||
octet 2,2a | Length Indicator | |||||||
octet 3 | Ratio of the bucket that is filled up with data |
The field ranges from zero (00000000) to two hundred and fifty five (11111111). A value of zero means that the bucket is empty. A value of hundred means that the bucket is exactly full, while a value of two hundred and fifty five means that the bucket is at least 2.55 times Bmax
11.3.47 Service UTRAN CCO
The Service UTRAN CCO (Cell Change Order) information element indicates information for Network initiated Cell Change Order to UTRAN, relevant if the procedure is used:
Table 11.53: Service UTRAN CCO IE
8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 | ||
octet 1 | IEI | ||||||||
octet 2,2a | Length Indicator | ||||||||
octet 3 | Spare | Service UTRAN CCO Value part |
Table 11.54: UTRAN CCO Value part coding
coding | Semantic |
000 | Network initiated cell change order procedure to UTRAN should be performed |
001 | Network initiated cell change order procedure to UTRAN should not be performed |
010 | Network initiated cell change order procedure to UTRAN shall not be performed |
Other values | No information available |