11 General information elements coding

3GPP48.018Base Station System (BSS) - Serving GPRS Support Node (SGSN)BSS GPRS protocol (BSSGP)General Packet Radio Service (GPRS)Release 17TS

The figures and text in this sub-clause describe the Information Elements contents.

11.1 General structure of the information elements

Refer to General Structure Of The Information Elements/3GPP TS 48.016.

11.2 Information element description

Refer to Information Element Description/3GPP TS 48.016.

11.3 Information Element Identifier (IEI)

An Information Element Identifier (IEI) is identified by the same coding in all BSSGP PDUs.

Table 11.3: IEI types

IEI coding
(hexadecimal)

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

GPRS Timer

x3a

Aggregate BSS QoS Profile (ABQP)

x3b

Feature Bitmap

x3c

Bucket_Full Ratio

x3d

Service UTRAN CCO (Cell Change Order)

x3e

NSEI

x3f

RRLP APDU

x40

LCS QoS

x41

LCS Client Type

x42

Requested GPS Assistance Data

x43

Location Type

x44

Location Estimate

x45

Positioning Data

x46

Deciphering Keys

x47

LCS Priority

x48

LCS Cause

x49

LCS Capability

x4a

RRLP Flags

x4b

RIM Application Identity

x4c

RIM Sequence number

x4d

RAN-INFORMATION-REQUEST Application Container

x4e

RAN-INFORMATION Application Container

x4f

RIM PDU Indications

x50

This value is reserved for future use and shall be treated by the recipient as an unknown IEI

x51

This value should not be used, as it has been used in earlier versions of this protocol.

x52

PFC flow control parameters

x53

Global CN-Id

x54

RIM Routing Information

x55

RIM Protocol Version Number

x56

Application Error Container

x57

RAN-INFORMATION-REQUEST RIM Container

x58

RAN-INFORMATION RIM Container

x59

RAN-INFORMATION-APPLICATION-ERROR RIM Container

x5a

RAN-INFORMATION-ACK RIM Container

x5b

RAN-INFORMATION-ERROR RIM Container

x5c

TMGI

x5d

MBMS Session Identity

x5e

MBMS Session Duration

x5f

MBMS Service Area Identity List

x60

MBMS Response

x61

MBMS Routing Area List

x62

MBMS Session Information

x63

MBMS Stop Cause

x64

Source BSS to Target BSS Transparent Container

x65

Target BSS to Source BSS Transparent Container

x66

NAS container for PS Handover

x67

PFCs to be set-up list

x68

List of set-up PFCs

x69

Extended Feature Bitmap

x6a

Source to Target Transparent Container

x6b

Target to Source Transparent Container

x6c

RNC Identifier

x6d

Page Mode

x6e

Container ID

x6f

Global TFI

x70

IMEI

x71

Time to MBMS Data Transfer

x72

MBMS Session Repetition Number

x73

Inter RAT Handover Info

x74

PS Handover Command

x75

PS Handover Indications

x76

SI/PSI Container

x77

Active PFCs List

x78

Velocity Data

x79

DTM Handover Command

x7a

CS Indication

x7b

Requested GANSS Assistance Data

x7c

GANSS Location Type

x7d

GANSS Positioning Data

x7e

Flow Control Granularity

x7f

eNB Identifier

x80

E-UTRAN Inter RAT Handover Info

x81

Subscriber Profile ID for RAT/Frequency priority

x82

Request for Inter RAT Handover Info

x83

Reliable Inter RAT Handover Info

x84

SON Transfer Application Identity

x85

CSG Identifier

x86

TAC

x87

Redirect Attempt Flag

x88

Redirection Indication

x89

Redirection Completed

x8a

Unconfirmed send state variable

x8b

IRAT Measurement Configuration

x8c

SCI

X8d

GGSN/P-GW location

x8e

Selected PLMN ID

x8f

Priority Class Indicator

x90

Source Cell ID

x91

IRAT Measurement Configuration (extended E-ARFCNs)

x92

eDRX Parameters

x93

Time Until Next Paging Occasion

x98

Coverage Class

X99

Paging Attempt Information

X9a

Exception Report Flag

x9b

Old Routing Area Identification

x9c

Attach Indicator

x9d

PLMN Identity

x9e

MME Query

x9f

SGSN Group Identity

xa0

Additional P-TMSI

xa1

UE Usage Type

xa2

Multilateration Timer

xa3

Multilateration Timing Advance

xa4

MS Sync Accuracy

xa5

BTS Reception Accuracy Level

xa6

Timing Advance Request

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.3.1: Alignment octets IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator (note)

octet 3-5

spare octet

NOTE: 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.2: 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 Bmax of BVC Bucket Size, see sub-clause 11.3.5.

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.3.3: 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.3.4: 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)

If the Gigabit Interface feature has not been negotiated, the R field is the binary encoding of the rate information expressed in 100 bits/s increments, starting from 0 x 100 bits/s until 65 535 x 100 bits/s (6 Mbps).

If the Gigabit Interface feature has been negotiated, the R field is the binary encoding of the rate information expressed in increments as defined by the Flow Control Granularity IE.

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.3.5: 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)

If the Gigabit Interface feature has not been negotiated, 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).

If the Gigabit Interface feature has been negotiated, the Bmax field is the binary encoding of the rate information expressed in increments as defined by the Flow Control Granularity IE.

11.3.6 BVCI (BSSGP Virtual Connection Identifier)

The BVCI identifies a BVC. The element coding is:

Table 11.3.6: 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.3.7: 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 ms. 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.3.8.a: Cause IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Cause value

Table 11.3.8.b: Cause coding

Cause value
Hexadecimal

Semantics of coding

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

x0b

PFC preempted

x0c

ABQP no more supported

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

x29

Requested Information not available

x2a

Unknown Destination address

x2b

Unknown RIM Application Identity or RIM application disabled

x2c

Invalid Container Unit Information

x2d

PFC queuing

x2e

PFC created successfully

x2f

T12 expiry

x30

MS under PS Handover treatment

x31

Uplink quality

x32

Uplink strength

x33

Downlink quality

x34

Downlink strength

x35

Distance

x36

Better cell

x37

Traffic

x38

Radio contact lost with MS

x39

MS back on old channel

x3a

T13 expiry

x3b

T14 expiry

x3c

Not all requested PFCs created

x3d

CS cause

x3e

Requested ciphering and/or integrity protection algorithms not supported

x3f

Relocation failure in target system

x40

Directed Retry

x41

Time critical relocation

x42

PS Handover Target not allowed

x43

PS Handover not Supported in Target BSS or Target System

x44

Incoming relocation not supported due to PUESBINE feature

x45

DTM Handover – No CS resource

x46

DTM Handover – PS Allocation failure

x47

DTM Handover – T24 expiry

x48

DTM Handover – Invalid CS Indication IE

x49

DTM Handover – T23 expiry

x4a

DTM Handover – MSC Error

x4b

Invalid CSG cell

x80 to x87

Reserved for further definition of non-critical PS handover cause values

NOTE: If received, cause values x80 to x87 inclusive indicate a non-critical PS Handover (see sub-clause 8a.5).

11.3.9 Cell Identifier

This information element uniquely identifies one cell. The element coding is:

Table 11.3.9: 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 24.008, not including 3GPP TS 24.008 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 24.008, not including 3GPP TS 24.008 IEI

11.3.10 Channel needed

This information element is coded as defined in 3GPP TS 29.018. It is relevant to circuit-switched paging requests. The element coding is:

Table 11.3.10: 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 29.018, not including 3GPP TS 29.018 IEI and 3GPP TS 29.018 length indicator

11.3.11 DRX Parameters

This information element contains MS specific DRX information. The element coding is:

Table 11.3.11: 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 24.008, not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 octet length indicator

11.3.12 eMLPP-Priority

This element indicates the eMLPP-Priority of a PDU. The element coding is:

Table 11.3.12: 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 48.008, not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 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.3.13.a: 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.3.13.b: Action coding

Action value
Hexadecimal

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 (see 3GPP TS 23.003). The element coding is:

Table 11.3.14: 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 of the Mobile Identity IE defined in 3GPP TS 24.008
(NOTE 1)

NOTE 1: The Type of identity field in the Mobile Identity IE shall be ignored by the receiver.

11.3.15 LLC-PDU

This information element contains an LLC-PDU. The element coding is:

Table 11.3.15: 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.3.16: 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.3.17: 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 24.008, not including 3GPP TS 24.008 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.3.18: 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 48.008, not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 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.3.19: 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 48.008, not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 length indicator

11.3.20 Mobile Id

The element coding is:

Table 11.3.20: 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 24.008, not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 length indcator

11.3.21 MS Bucket Size

This information element indicates an MS’s bucket size (Bmax). The element coding is:

Table 11.3.21: 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 Bmax of BVC Bucket Size, see sub-clause 11.3.5.

11.3.22 MS Radio Access Capability

This information element contains the capabilities of the ME. The element coding is:

Table 11.3.22: 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 3GPP TS 24.008, not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 octet length indicator.

11.3.23 OMC Id

The element coding is:

Table 11.3.23: 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 3GPP TS 12.20

11.3.24 PDU In Error

The element coding is:

Table 11.3.24: 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.3.25: 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 Delay Value of BVC Measurement, see sub-clause 11.3.7.

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.3.26: PDU Types

PDU type coding
(Hexadecimal)

PDU Types

PDUs between RL and BSSGP SAPs

x00

DL-UNITDATA

x01

UL-UNITDATA

x02

RA-CAPABILITY

x03

reserved (Note 1)

x04

DL-MBMS-UNITDATA

x05

UL-MBMS-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

x11

PAGING-PS-REJECT

x12

DUMMY-PAGING-PS

x13

DUMMY-PAGING-PS-RESPONSE

x14

MS-REGISTRATION-ENQUIRY

x15

MS-REGISTRATION-ENQUIRY-RESPONSE

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

x2d

FLOW-CONTROL-PFC

x2e

FLOW-CONTROL-PFC-ACK

x40

SGSN-INVOKE-TRACE

x41

STATUS

x42

OVERLOAD

PDUs between PFM SAPs

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

0x58

DELETE-BSS-PFC-REQ

0x59

PS-HANDOVER-REQUIRED

0x5a

PS-HANDOVER-REQUIRED-ACK

0x5b

PS-HANDOVER-REQUIRED-NACK

0x5c

PS-HANDOVER-REQUEST

0x5d

PS-HANDOVER-REQUEST-ACK

0x5e

PS-HANDOVER-REQUEST-NACK

0x91

PS-HANDOVER-COMPLETE

0x92

PS-HANDOVER-CANCEL

0x93

PS-HANDOVER-COMPLETE-ACK

PDUs between LCS SAPs

0x60

PERFORM-LOCATION-REQUEST

0x61

PERFORM-LOCATION-RESPONSE

0x62

PERFORM-LOCATION-ABORT

0x63

POSITION-COMMAND

0x64

POSITION-RESPONSE

PDUs between RIM SAPs

0x70

RAN-INFORMATION

0x71

RAN-INFORMATION-REQUEST

0x72

RAN-INFORMATION-ACK

0x73

RAN-INFORMATION-ERROR

0x74

RAN-INFORMATION-APPLICATION-ERROR

PDUs between MBMS SAPs

0x80

MBMS-SESSION-START-REQUEST

0x81

MBMS-SESSION-START-RESPONSE

0x82

MBMS-SESSION-STOP-REQUEST

0x83

MBMS-SESSION-STOP-RESPONSE

0x84

MBMS-SESSION-UPDATE-REQUEST

0x85

MBMS-SESSION-UPDATE-RESPONSE

RESERVED

all values not explicitly shown are reserved for future use

NOTE 1: This value was allocated in an earlier version of the protocol and shall not be used.

11.3.27 Priority

This element indicates the priority of a PDU. The element coding is:

Table 11.3.27: 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 48.008, not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 length indicator

11.3.28 QoS Profile

This information element describes the QoS Profile associated with a PDU. The element coding is:

Table 11.3.28.a: 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 (note)

octet 5

Peak Bit Rate Granularity

C/R

T

A

Precedence

NOTE: The bit rate 0 (zero) shall mean "best effort" in this IE.

"Peak bit rate" is coded as shown below:

Table 11.3.28.a1: Peak bit rate

8

7

6

5

4

3

2

1

octet 3

Peak bit rate value (MSB)

octet 4

Peak bit rate value (LSB)

If the Gigabit Interface feature has not been negotiated, the "Peak bit rate" field is the binary encoding of the peak bit rate information expressed in 100 bits/s increments, starting from 0 x 100 bits/s until 65 535 x 100 bits/s (6 Mbps).

If the Gigabit Interface feature has been negotiated, the "Peak bit rate" field is the binary encoding of the peak bit rate information expressed in increments as defined by the Peak Bit Rate Granularity field.

"Precedence" is coded as shown below (complying with 3GPP TS 23.060).

Table 11.3.28.b: 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.3.28.c: "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.3.28.d: "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.3.28.e: "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

"Peak Bit Rate Granularity" is coded as shown below.

Table 11.3.28.f: "Peak Bit Rate Granularity" coding

coding

semantic

00

100 bits/s increments

01

1000 bits/s increments

10

10000 bits/s increments

11

100000 bits/s increments

This field provides the granularity to be used for deriving the peak bit rate value if the Gigabit Interface feature is negotiated.

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.3.29.a: 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.3.29.b: Radio Cause value

radio cause value
Hexadecimal

Semantics of coding

x00

Radio contact lost with the MS

x01

Radio link quality insufficient to continue communication

x02

cell-reselection ordered

x03

Cell reselection prepare. See Note below.

x04

Cell reselection failure. See Note below.

All values not explicitly listed are reserved. If received, they shall be handled as "radio contact lost with the MS".

NOTE: In case the Enhanced Radio Status feature has not been negotiated the Radio Cause values in range of x03-x04 should if received be handled as "radio contact lost with the MS". This is in order to be backwards compatible with earlier releases of the standard.

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.3.30.a: 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.3.30.b: RA-Cap-UPD Cause value

RA-Cap-UPD cause value
Hexadecimal

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.3.31: 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 24.008, not including 3GPP TS 24.008 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.3.32: 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 value field is coded as The "R Value" of Bucket Leak Rate, see sub-clause 11.3.4.

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.3.33: 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.3.34: 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.3.35: 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 44.018, not including 3GPP TS 44.018 IEI.

11.3.36 Temporary Mobile Subscriber Identity (TMSI)

The element coding is:

Table 11.3.36: 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 24.008, not including 3GPP TS 24.008 IEI.

11.3.37 Trace Reference

This element provides a trace reference number allocated by the triggering entity. The element coding is:

Table 11.3.37: 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.3.38: 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 32.008.

11.3.39 Transaction Id

This element indicates a particular transaction within a trace. The element coding is:

Table 11.3.39: 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.3.40: 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.3.41: 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.3.42: 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, SMS, and TOM8.

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 or an MBMS Service 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.3.43: 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.3.44: GPRS Timer IE

8

7

6

5

4

3

2

1

octet 1

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 s

0 0 1 value is incremented in multiples of 1 minute

0 1 0 value is incremented in multiples of decihours

0 1 1 value is incremented in multiples of 500 msec

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 bitmap information element indicates the optional features supported by the underlying NSE. The element coding is:

Table 11.3.45.a: Feature Bitmap IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

MBMS

Enhanced Radio Status

PFC-FC

RIM

LCS

INR

CBL

PFC

Table 11.3.45.b: "PFC bit" coding

coding

Semantic

0

Packet Flow Context Procedures not supported

1

Packet Flow Context Procedures supported

Table 11.3.45.c: "CBL bit" coding

coding

Semantic

0

Current Bucket Level Procedures not supported

1

Current Bucket Level Procedures supported

Table 11.3.45.d: "INR bit" coding

coding

Semantic

0

Inter-NSE re-routing not supported

1

Inter-NSE re-routing supported

Table 11.3.45.e: "LCS bit" coding

coding

Semantic

0

LCS Procedures not supported

1

LCS Procedures supported

Table 11.3.45.f: "RIM bit" coding

coding

Semantic

0

RAN Information Management (RIM) procedures not supported

1

RAN Information Management (RIM) procedures supported

Table 11.3.45.g: "PFC-FC" coding

coding

Semantic

0

PFC Flow Control Procedures not supported

1

PFC Flow Control Procedures supported

Table 11.3.45.h: "Enhanced Radio Status" coding

coding

Semantic

0

Enhanced Radio Status Procedures not supported

1

Enhanced Radio Status Procedures supported

Table 11.3.45.i: "MBMS" coding

coding

Semantic

0

MBMS Procedures not supported

1

MBMS 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 x (100 / Bmax). The element coding is:

Table 11.3.46: 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 whether Network initiated Cell Change Order to UTRAN or E-UTRAN or PS Handover to UTRAN or E-UTRAN should be used for the mobile station or not, and it is relevant if at least one of the procedures is used:

Table 11.3.47.a: Service UTRAN CCO IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Spare

Service E-UTRAN CCO Value part

Service UTRAN CCO Value part

Table 11.3.47.b: Service UTRAN CCO Value part coding

coding bits
321

Semantic

000

Network initiated cell change order to UTRAN or PS handover to UTRAN procedure should be performed

001

Network initiated cell change order to UTRAN or PS handover to UTRAN procedure should not be performed

010

Network initiated cell change order to UTRAN or PS handover to UTRAN procedure shall not be performed

111

If received, shall be interpreted as no information available (bits 4-5 valid)

Other values

If received, shall be interpreted as no information available

Table 11.3.47.c: Service E-UTRAN CCO Value part coding

coding bits
54

Semantic

01

Network initiated cell change order to E-UTRAN or PS handover to E-UTRAN procedure should be performed

10

Network initiated cell change order to E-UTRAN or PS handover to E-UTRAN procedure should not be performed

11

Network initiated cell change order to E-UTRAN or PS handover to E-UTRAN procedure shall not be performed

00

If received, shall be interpreted as no information available

11.3.48 NSEI (Network Service Entity Identifier)

The NSEI unambiguously identifies a NSE. The element coding is:

Table 11.3.48: NSEI IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

most significant octet of NSEI

octet 4

least significant octet of NSEI

11.3.49 RRLP APDU

This information element conveys an embedded message associated with a higher level protocol. The element coding is:

Table 11.3.49: RRLP APDU IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3-?

The rest of the information element contains an embedded RRLP message whose content and encoding are defined according to the 3GPP TS 44.031. The RRLP protocol is not octet aligned. Therefore, the unused bits in the last octet are padded with zeroes.

11.3.50 LCS QoS

This information element provides the LCS QoS. The element coding is:

Table 11.3.50: LCS QOS 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 48.008, not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 octet length indicator

11.3.51 LCS Client Type

This information element provides the LCS Client Type. The element coding is:

Table 11.3.51: LCS Client Type 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 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator

11.3.52 Requested GPS Assistance Data

This information element provides the information on which GPS Assistance Data has been requested. The element coding is:

Table 11.3.52: Requested GPS Assistance Data 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 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator

11.3.53 Location Type

This information element provides the Location Type. The element coding is:

Table 11.3.53: Location Type 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 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator

11.3.54 Location Estimate

This information element provides the Location Estimate. The element coding is:

Table 11.3.54: Location Estimate 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 48.008, not including 3GPP TS 48.008 IEI and 3GPP TS 48.008 octet length indicator

11.3.55 Positioning Data

This information element provides Positioning Data. The element coding is:

Table 11.3.55: Positioning Data 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 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator

11.3.56 Deciphering Keys

This information element provides the Deciphering Keys. The element coding is:

Table 11.3.56: Deciphering Keys 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 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator

11.3.57 LCS Priority

This information element provides the data/information on LCS Priority. The element coding is:

Table 11.3.57: LCS Priority 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 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator

11.3.58 LCS Cause

This information element provides the data/information on LCS Cause. The element coding is:

Table 11.3.58: LCS Cause 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 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator

11.3.59 LCS Capability

This information element provides the data/information on LCS Capability. The element coding is:

Table 11.3.59: LCS 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 of the PS LCS Capability IE defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI and length indicator

11.3.60 RRLP Flags

This information element provides control information for the RRLP APDU. The element coding is:

Table 11.3.60: RRLP Flags IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Spare

Flag 1

The fields are coded as follows:

Flag 1 (Octet 3, bit 1):

0 Position Command (BSS to SGSN) or final response (SGSN to BSS);

1 Not a Positioning Command or final response.

Spare These bits shall be ignored by the receiver and set to zero by the sender.

11.3.61 RIM Application Identity

This information element specifies the addressed application within the target BSS node. The element coding is:

Table 11.3.61.a: RIM Application Identity IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

RIM Application Identity

RIM Application Identity is coded as shown below.

Table 11.3.61.b: RIM Application Identity coding

Coding

Semantic

0000 0000

Reserved

0000 0001

Network Assisted Cell Change (NACC)

0000 0010

System Information 3 (SI3)

0000 0011

MBMS data channel

0000 0100

SON Transfer

0000 0101

UTRA System Information (UTRA SI)

0000 0110

Multilateration Timing Advance

0000 0111 – 1111 1111

Reserved

All values not allocated are reserved.

11.3.62 RIM Sequence Number

This information element defines the sequence number allocated to the PDU by the source node. The element coding is:

Table 11.3.62: RIM Sequence Number IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

RIM Sequence Number (Higher order octet)

Octet 4

RIM Sequence Number

Octet 5

RIM Sequence Number

Octet 6

RIM Sequence Number (Lower order octet)

11.3.62a RIM Container

11.3.62a.0 General

The coding of the RIM Container IE value part depends on the value of the PDU type according to the following sub-clauses:

11.3.62a.1 RAN-INFORMATION-REQUEST RIM Container

This information element defines the RIM container used in the RAN-INFORMATION-REQUEST PDU. The element coding is:

Table 11.3.62a.1.a: RAN-INFORMATION-REQUEST RIM Container IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-?

RAN-INFORMATION-REQUEST RIM Container Contents coded as defined in table 11.3.62a.1b

Table 11.3.62a.1.b: RAN-INFORMATION-REQUEST RIM Container Contents

Information Elements

Type / Reference

Presence

Format

Length

RIM Application Identity

RIM Application Identity/11.3.61

M

TLV

3

RIM Sequence Number

RIM Sequence Number/11.3.62

M

TLV

6

RIM PDU Indications

RIM PDU Indications/11.3.65

M

TLV

3

RIM Protocol Version Number

RIM Protocol Version Number/11.3.67

O

TLV

3

Application Container (note 1)

RAN-INFORMATION-REQUEST Application Container/11.3.63.1

C

TLV

4-?

SON Transfer Application Identity (note 2)

SON Transfer Application Identity/11.3.108

C

TLV

3-m

NOTE 1: The presence of the Application Container depends on the value of the RIM Application Identity IE.

NOTE 2: The SON Transfer Application Identity IE shall be present if and only if the RIM Application Identity IE is set to "SON Transfer".

11.3.62a.2 RAN-INFORMATION RIM Container

This information element defines the RIM container used in the RAN-INFORMATION PDU. The element coding is:

Table 11.3.62a.2.a: RAN-INFORMATION RIM Container IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-?

RAN-INFORMATION RIM Container Contents coded as defined in table 11.3.62a.2b

Table 11.3.62a.2.b: RAN-INFORMATION RIM Container Contents

Information Elements

Type / Reference

Presence

Format

Length

RIM Application Identity

RIM Application Identity /11.3.61

M

TLV

3

RIM Sequence Number

RIM Sequence Number /11.3.62

M

TLV

6

RIM PDU Indications

RIM PDU Indications /11.3.65.

M

TLV

3

RIM Protocol Version Number

RIM Protocol Version Number/11.3.67

O

TLV

3

Application Container (NOTE 1)

RAN-INFORMATION Application Container /11.3.63.2

C (Note 1)

TLV

4-?

Application Error Container (NOTE 1)

Application Error Container/11.3.64

C (Note 1)

TLV

n

SON Transfer Application Identity (note 2)

SON Transfer Application Identity/11.3.108

C

TLV

3-m

NOTE 1: The presence of application information depends on the value of the RIM Application Identity IE. If application information is mandatory either the Application Error Container IE or the Application Container IE is present.

NOTE 2: The SON Transfer Application Identity IE shall be present if and only if the RIM Application Identity IE is set to "SON Transfer".

11.3.62a.3 RAN-INFORMATION-ACK RIM Container

This information element defines the RIM container used in the RAN-INFORMATION-ACK PDU. The element coding is:

Table 11.3.62a.3.a: RAN-INFORMATION-ACK RIM Container IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-16

RAN-INFORMATION-ACK RIM Container Contents coded as defined in table 11.3.62a.3b

Table 11.3.62a.3.b: RAN-INFORMATION-ACK RIM Container Contents

Information Elements

Type / Reference

Presence

Format

Length

RIM Application Identity

RIM Application Identity /11.3.61

M

TLV

3

RIM Sequence Number

RIM Sequence Number /11.3.62

M

TLV

6

RIM Protocol Version Number

RIM Protocol Version Number/11.3.67

O

TLV

4

SON Transfer Application Identity (note 1)

SON Transfer Application Identity/11.3.108

C

TLV

3-m

NOTE 1: The SON Transfer Application Identity IE shall be present if and only if the RIM Application Identity IE is set to "SON Transfer".

11.3.62a.4 RAN-INFORMATION-ERROR RIM Container

This information element defines the RIM container used in the RAN-INFORMATION-ERROR PDU. The element coding is:

Table 11.3.62a.4.a: RAN-INFORMATION-ERROR RIM Container IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-?

RAN-INFORMATION-ERROR RIM Container Contents coded as defined in table 11.3.62a.4b

Table 11.3.62a.4.b: RAN-INFORMATION-ERROR RIM Container Contents

Information Elements

Type / Reference

Presence

Format

Length

RIM Application Identity

RIM Application Identity /11.3.61

M

TLV

3

RIM Cause

Cause/11.3.8

M

TLV

3

RIM Protocol Version Number

RIM Protocol Version Number/11.3.67

O

TLV

3

PDU in Error

PDU in Error/11.3.24

M

TLV

3-?

SON Transfer Application Identity (note 1)

SON Transfer Application Identity/11.3.108

C

TLV

3-m

NOTE 1: The SON Transfer Application Identity IE shall be present if and only if the RIM Application Identity IE is set to "SON Transfer".

11.3.62a.5 RAN-INFORMATION-APPLICATION-ERROR RIM Container

This information element defines the RIM container used in the RAN-INFORMATION-APPLICATION-ERROR PDU. The element coding is:

Table 11.3.62a.5.a: RAN-INFORMATION-APPLICATION-ERROR RIM Container IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-?

RAN-INFORMATION-APPLICATION-ERROR RIM Container Contents coded as defined in table 11.3.62a.5b

Table 11.3.62a.5.b: RAN-INFORMATION-APPLICATION-ERROR RIM Container Contents

Information Elements

Type / Reference

Presence

Format

Length

RIM Application Identity

RIM Application Identity /11.3.61

M

TLV

3

RIM Sequence Number

RIM Sequence Number /11.3.62

M

TLV

6

RIM PDU Indications

RIM PDU Indications /11.3.65.

M

TLV

3

RIM Protocol Version Number

RIM Protocol Version Number/11.3.67

O

TLV

3

Application Error Container

Application Error Container/11.3.64

M

TLV

n

SON Transfer Application Identity (note 1)

SON Transfer Application Identity/11.3.108

C

TLV

3-m

NOTE 1: The SON Transfer Application Identity IE shall be present if and only if the RIM Application Identity IE is set to "SON Transfer".

11.3.63 Application Container

11.3.63.1 RAN-INFORMATION-REQUEST Application Container

11.3.63.1.0 General

The coding of the Application Container value part within the RAN-INFORMATION-REQUEST RIM container depends on the value of the RIM Application Identity IE included into the RIM container according to the following sub-clauses.

11.3.63.1.1 RAN-INFORMATION-REQUEST Application Container for the NACC Application

The coding of the Application Container IE within the RAN-INFORMATION-REQUEST RIM container for the NACC application is specified as follows:

Table 11.3.63.1.1: RAN-INFORMATION-REQUEST Application Container coding for NACC

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-10

Reporting Cell Identifier

Reporting Cell Identifier: This field is encoded as the Cell Identifier defined in sub-clause 11.3.9

11.3.63.1.2 RAN-INFORMATION-REQUEST Application Container for the SI3 Application

The coding of the Application Container IE within the RAN-INFORMATION-REQUEST RIM container for the SI3 application is specified as follows:

Table 11.3.63.1.2: RAN-INFORMATION-REQUEST Application Container coding for SI3

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-10

Reporting Cell Identifier

Reporting Cell Identifier: This field is encoded as the Cell Identifier defined in sub-clause 11.3.9

11.3.63.1.3 RAN-INFORMATION-REQUEST Application Container for the MBMS data channel Application

The coding of the Application Container IE within the RAN-INFORMATION-REQUEST RIM container for the MBMS data channel application is specified as follows:

Table 11.3.63.1.3: RAN-INFORMATION-REQUEST Application Container coding for MBMS data channel

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-10

Reporting Cell Identifier

Reporting Cell Identifier: This field is encoded as the Cell Identifier defined in sub-clause 11.3.9

11.3.63.1.4 RAN-INFORMATION-REQUEST Application Container for the SON Transfer Application

The coding of the Application Container IE within the RAN-INFORMATION-REQUEST RIM container for the SON Application is specified as follows:

Table 11.3.63.1.4: RAN-INFORMATION-REQUEST Application Container coding for SON Transfer

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-m

Reporting Cell Identifier

Octet (m+1)-n

SON Transfer Request Container

Reporting Cell Identifier:

– If the request concerns an E-UTRAN cell, this field is encoded as the E-UTRAN CGI IE as defined in 3GPP TS 36.413 [36].

– If the request concerns a UTRAN cell, this field is encoded as the Source Cell Identifier IE (UTRAN Source Cell ID) as defined in 3GPP TS 25.413 [38].

– If the request concerns a GERAN cell, this field is encoded as the Cell Identifier IE defined in sub-clause 11.3.9.

– If the request concerns an eHRPD eAN cell,this field is encoded as the eHRPD Sector ID IE as specified in 3GPP2 C.S0024-B [47].

SON Transfer Request Container: This field is encoded as the SON Transfer Request Container IE as defined in 3GPP TS 36.413 [36].

11.3.63.1.5 RAN-INFORMATION-REQUEST Application Container for the UTRA SI Application

The coding of the Application Container IE within the RAN-INFORMATION-REQUEST RIM container for the UTRA SI application is specified as follows:

Table 11.3.63.1.5: RAN-INFORMATION-REQUEST Application Container coding for UTRA SI

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-m

Reporting Cell Identifier

Reporting Cell Identifier: This field is encoded as the Source Cell Identifier IE (UTRAN Source Cell ID) as defined in 3GPP TS 25.413 [38].

11.3.63.2 RAN-INFORMATION Application Container Unit

11.3.63.2.0 General

The coding of the Application Container value part within the RAN-INFORMATION RIM container depends on the value of the RIM Application Identity IE included into the RIM container according to the following sub-clauses.

11.3.63.2.1 RAN-INFORMATION Application Container for the NACC Application

The coding of the Application Container IE within the RAN-INFORMATION RIM container for the NACC application is specified as follows:

Table 11.3.63.2.1.a: RAN-INFORMATION Application Container coding for NACC

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-10

Reporting Cell Identifier

Octet 11

Number of SI/PSI

Type

Octet 12-n

SI/PSI

Reporting Cell Identifier: This field is encoded as the value part of the Cell Identifier IE defined in sub-clause 11.3.9, not including IEI and Length Indicator.

Type: This field indicates the type of SI/PSI messages provided by the reporting cell. The Type field is coded as shown below:

Table 11.3.63.2.1.b: Type coding

Coding

Semantic

0

SI messages as specified for BCCH (3GPP TS 44.018) follow

1

PSI messages as specified for PBCCH (3GPP TS 44.060) follow

Number of SI/PSI: This field indicates the number of SI/PSI provided by the reporting cell contained in the SI/PSI field. This number may be zero. For system information messages with multiple instances, each instance is counted as one SI/PSI message. The Number of SI/PSI field is coded as shown below:

Table 11.3.63.2.1.c: Number of SI/PSI coding

Coding

Semantic

000 0000

0 "SI/PSI" follows

000 0001

1 "SI/PSI" follow

‘

"

111 1111

127 "SI/PSI" follow

SI/PSI: This field contains a list of either system information or packet system information messages valid for the reporting cell. The number of (packet) system information messages is indicated in the Number of SI/PSI field specified above. Furthermore:

– If the Type field indicates that "SI messages as specified for BCCH (3GPP TS 44.018) follow" then the SI/PSI field contains System Information message instances encoded for BCCH as specified in 3GPP TS 44.018. Each System Information message contains the Message type octet followed by all the IEs composing the message payload. Each message is 21 octets long.

– If the Type field indicates that "PSI messages as specified for PBCCH (3GPP TS 44.060) follow" then the SI/PSI field contains Packet System Information message instances encoded for PBCCH as specified in 3GPP TS 44.060. Each Packet System Information message contains the MESSAGE_TYPE field followed by the PSI message content. Each message is 22 octets long.

11.3.63.2.2 RAN-INFORMATION Application Container for the SI3 Application

The coding of the value part of the Application Container IE within the RAN-INFORMATION RIM container for the SI3 application is specified as follows:

Table 11.3.63.2.2: RAN-INFORMATION Application Container coding for SI3

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-10

Reporting Cell Identifier

Octet 11-31

SI3

Reporting Cell Identifier: The parameter is encoded as the value part of the Cell Identifier IE defined in sub-clause 11.3.9, not including IEI and Length Indicator.

SI3: contains the SYSTEM INFORMATION type 3 message encoded for BCCH as specified in 3GPP TS 44.018. It contains the Message type octet followed by all the IEs composing the message payload. The message is 21 octets long.

11.3.63.2.3 RAN-INFORMATION Application Container for the MBMS data channel Application

The coding of the Application Container IE within the RAN-INFORMATION RIM container for the MBMS data channel application is specified as follows :

Table 11.3.63.2.3.a: RAN-INFORMATION Application Container coding for MBMS data channel

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-10

Reporting Cell Identifier

Octet 11-n

MBMS data channel report

Reporting Cell Identifier: This field is encoded as the value part of the Cell Identifier IE defined in sub-clause 11.3.9, not including IEI and Length Indicator.

MBMS data channel report: This field contains a CSN1 encoded structure coded as shown below:

Table 11.3.63.1.3.b: MBMS data channel report

< MBMS data channel report struct > ::=

{ 1 < MBMS Frequency List : < MBMS Frequency List struct > > } **0

{1

< MBMS p-t-m Frequency Parameters : < MBMS p-t-m Frequency Parameters struct > >

< DOWNLINK_TIMESLOT_ALLOCATION : bit (8) > –default value common to all described bearer Id using this frequency allocation

{ 1

< TMGI : < TMGI IE > > — MBMS service identifier

{ 0 | 1 < MBMS Session Identity: bit(8) > } — session identifier of the particular MBMS service

< Length of MBMS Bearer Identity : bit (3) >

< MBMS Bearer Identity : bit (val (Length of MBMS Bearer Identity)) >

{ 0 | 1 < EGPRS Window Size : < EGPRS Window Size IE >> }

{ 0 | 1 < DOWNLINK_TIMESLOT_ALLOCATION : bit (8) > } — dedicated value for this bearer, overwrites the default value

{ 0 | 1 <TIMESLOT_ALLOCATION_UPLINK_FEEDBACK_CHANNEL : bit (3) > }

{ 0 | 1 < MBMS Radio Bearer Starting Time : < bit (16) > > }

< MBMS In-band Signalling Indicator : < MBMS In-band Signalling Indicator IE >>

{ 0 | 1 < NPM Transfer Time : bit (5) > }

} ** 0 — End of list of MBMS bearer identifiers sharing the same PDCH (frequency parameters)

} ** 0 — End of list of PDCHs for this cell

{ null | 0 bit** = < no string >

| 1 — Rel-7 Additions

{ 1

{ 0 | 1 < USF : bit (3) > –choice bit indicates presence or not of parameters for the MBMS bearer

{ 0 | 1 < MPRACH Control Parameters : < MPRACH Control Parameters IE > > }

}

} ** 0 — End of list of MBMS bearers. The list of MBMS bearers is ordered as described by the loops in the earlier releases part.

}

< padding bits > — to fill the last octet

MBMS Frequency List: This field contains a MBMS Frequency List struct as specified in 3GPP TS 44.060

MBMS p-t-m Frequency Parameters: This field contains a MBMS p-t-m Frequency Parameters struct as specified in 3GPP TS 44.060

DOWNLINK_TIMESLOT_ALLOCATION: This field contains a DOWNLINK_TIMESLOT_ALLOCATION field as specified in 3GPP TS 44.060

TMGI: This field contains a TMGI IE as specified in 3GPP TS 44.060

MBMS Session Identity: This field contains a MBMS Session Identity field as specified in 3GPP TS 44.060

MBMS Bearer Identity: This field contains a MBMS Bearer Identity IE as specified in 3GPP TS 44.060

EGPRS Window Size: This field contains a EGPRS Window Size IE as specified in 3GPP TS 44.060

TIMESLOT_ALLOCATION_UPLINK_FEEDBACK_CHANNEL: This field contains a TIMESLOT_ALLOCATION_UPLINK_FEEDBACK_CHANNEL field as specified in 3GPP TS 44.060

MBMS Radio Bearer Starting Time: This field is encoded as value part of the type 3 information element Starting Time in 3GPP TS 44.018.

MBMS In-band Signalling Indicator: This field contains a MBMS In-band Signalling Indicator IE as specified in 3GPP TS 44.060. NPM Transfer Time: This field contains a NPM Transfer Time IE as specified in 3GPP TS 44.060.USF: This field contains a USF field as specified in 3GPP TS 44.060

MPRACH Control Parameters: This field contains a MPRACH Control Parameters IE as specified in 3GPP TS 44.060.

11.3.63.2.4 RAN-INFORMATION Application Container for the SON Transfer Application

The coding of the Application Container IE within the RAN-INFORMATION RIM container for the SON Transfer Application is specified as follows :

Table 11.3.63.2.4: RAN-INFORMATION Application Container coding for SON Transfer

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Spare

RAT discriminator

Octet 4-m

Reporting Cell Identifier

Octet (m+1)-n

SON Transfer Response Container

The coding of RAT discriminator (bits 4 to 1 of octet 3) is a binary number indicating the RAT of the Reporting Cell Identifier. The RAT discriminator is coded as follows:

Bits

4321

0000 The reporting RAT is GERAN.

0001 The reporting RAT is UTRAN.

0010 The reporting RAT is E-UTRAN.

0011 The reporting RAT is eHRPD eAN

All other values are reserved.

Reporting Cell Identifier:

– If the RAT discriminator field indicates E-UTRAN, this field is encoded as the E-UTRAN CGI IE as defined in 3GPP TS 36.413 [36].

– If the RAT discriminator field indicates UTRAN, this field is encoded as the Source Cell Identifier IE (UTRAN Source Cell ID) as defined in 3GPP TS 25.413 [38].

– If the RAT discriminator field indicates GERAN, this field is encoded as the value part of the Cell Identifier IE defined in sub-clause 11.3.9, not including IEI and Length Indicator.

– If the RAT discriminator field indicates eHRPD, this field is encoded as eHRPD Sector ID IE as defined in 3GPP2 C.S0024-B [47].

SON Transfer Response Container: This field is encoded as the SON Transfer Response Container IE as defined in 3GPP TS 36.413 [36].

11.3.63.2.5 RAN-INFORMATION Application Container for the UTRA SI Application

The coding of the Application Container IE within the RAN-INFORMATION RIM container for the UTRA SI application is specified as follows:

Table 11.3.63.2.5: RAN-INFORMATION Application Container coding for UTRA SI

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-m

Reporting Cell Identifier

Octet (m+1)-n

UTRA SI Container

Reporting Cell Identifier: This field is encoded as the Source Cell Identifier IE (UTRAN Source Cell ID) as defined in 3GPP TS 25.413 [38].

UTRA SI Container: This field contains System Information Container valid for the reporting cell encoded as defined in TS 25.331 [42].

11.3.63.2.6 RAN-INFORMATION Application Container for the Multilateration Timing Advance Application

The coding of the Application Container IE within the RAN-INFORMATION RIM container for the Multilateration Timing Advance application is specified as follows:

Table 11.3.63.2.6: RAN-INFORMATION Application Container coding for Multilateration Timing Advance

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-6

TLLI

Octet 7

MS Sync Accuracy

MTA High

Octet 8

MTA Low

BTS Reception Accuracy Level

High

Octet 9

BTS Reception Accuracy Level

Low

Spare

TLLI: This field is encoded as the value part of the TLLI information element in 3GPP TS 44.018, not including 3GPP TS 44.018 IEI.

Multilateration Timing Advance (MTA): The MTA field is coded according to the value part of the Multilateration Timing Advance information element described in 3GPP TS 49.031 (i.e. not including 3GPP TS 49.031 IEI).

MS Sync Accuracy: The MS Sync Accuracy field is coded according to the value part of the MS Sync Accuracy information element described in 3GPP TS 49.031 (i.e. not including 3GPP TS 49.031 IEI).

BTS Reception Accuracy Level: The BTS Reception Accuracy Level field is coded according to the value part of the BTS Reception Accuracy Level information element described in 3GPP TS 49.031 (i.e. not including 3GPP TS 49.031 IEI).

11.3.64 Application Error Container

11.3.64.1 Application Error Container layout for the NACC application

The coding of the Application Error Container IE for the NACC application is specified as follows:

Table 11.3.64.1.a: Application Error Container coding for NACC

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

NACC Cause

Octet 4-n

Erroneous Application Container including IEI and LI

NACC Cause: This field indicates the cause why the Application Error Container IE is sent. The NACC Cause field is coded as shown below:

Table 11.3.64.1.b: NACC Cause coding

Coding

Semantic

0000 0000

Other unspecified error

0000 0001

Syntax error in the Application Container

0000 0010

Reporting Cell Identifier does not match with the Destination Cell Identifier or with the Source Cell Identifier.

0000 0011

SI/PSI type error

0000 0100

Inconsistent length of a SI/PSI message

0000 0101

Inconsistent set of messages

Other values

reserved

"Other unspecified error": none of the error description below fits with the detected error

"Syntax error in the Application Container": the Application Container IE is syntactically incorrect

"Reporting Cell Identifier does not match with the Destination Cell Identifier or with the Source Cell Identifier": the Reporting Cell Identifier in the Application Container IE does not match with the Destination Cell Identifier IE value (in the case of a RAN-INFORMATION-REQUEST PDU) or with the Source Cell Identifier IE value (in the case of a RAN-INFORMATION PDU) of the RIM PDU

"SI/PSI type error": the Application Container IE contains system information messages instead of packet system information messages or conversely

"Inconsistent length of a SI/PSI message": the length contained in one SI/PSI message does not fit with the content of the message

"Inconsistent set of messages": the status of the change marks reported in the (packet) system information message set is inconsistent

Erroneous Application Container: this field contains the erroneous Application Container IE

11.3.64.2 Application Error Container for the SI3 application

The coding of the Application Error Container IE for the SI3 application is specified as follows:

Table 11.3.64.2.a: Application Error Container coding for SI3

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

SI3 Cause

Octet 4-n

Erroneous Application Container including IEI and LI

SI3 Cause: This field indicates the cause why the Application Error Container IE is sent. The SI3 Cause field is coded as shown below:

Table 11.3.64.2.b: SI3 Cause coding

Coding

Semantic

0000 0000

Other unspecified error

0000 0001

Syntax error in the Application Container

0000 0010

Reporting Cell Identifier does not match with the Destination Cell Identifier or with the Source Cell Identifier.

0000 0011

Inconsistent length of a SI3 message

Other values

Reserved

"Other unspecified error": None of the error description below fits with the detected error;

"Syntax error in the Application Container": the Error Application Container is syntactically incorrect;

"Reporting Cell Id does not match with the Destination Cell Identifier or with the Source Cell Identifier": the Reporting Cell Identifier in the Application Container IE does not match with the Destination Cell Identifier IE value (in the case of a RAN-INFORMATION-REQUEST PDU) or with the Source Cell Identifier IE value (in the case of a RAN-INFORMATION PDU) of the RIM PDU;

"Inconsistent length of a SI3 message": the length contained in the SI3 message does not fit with the content of the message;

Erroneous Application Container: This field contains the erroneous Application Container IE.

11.3.64.3 Application Error Container for the MBMS data channel application

The coding of the Application Error Container IE for the MBMS data channel application is specified as follows:

Table 11.3.64.3.a: Application Error Container coding for MBMS data channnel

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

MBMS data channel Cause

Octet 4-n

Erroneous Application Container including IEI and LI

MBMS data channel Cause: This field indicates the cause why the Application Error Container IE is sent. The MBMS data channel Cause" field is coded as shown below:

Table 11.3.64.3.b: MBMS DATA CHANNEL Cause coding

Coding

Semantic

0000 0000

Other unspecified error

0000 0001

Syntax error in the Application Container

0000 0010

Reporting Cell Identifier does not match with the Destination Cell Identifier or with the Source Cell Identifier.

0000 0011

RAN-INFORMATION/Initial Multiple Report or RAN-INFORMATION/Single Report PDU exceeds the maximum supported length

0000 0100

Inconsistent MBMS data channel description

Other values

reserved

"Other unspecified error": None of the error description below fits with the detected error.

"Syntax error in the Application Container": the Application Container IE is syntactically incorrect.

"Reporting Cell Id does not match with the Destination Cell Identifier or Source Cell Identifier respectively": the Reporting Cell Identifier in the Application Container IE does not match with the Destination Cell Identifier IE value (in the case of a RAN-INFORMATION-REQUEST PDU) or with the Source Cell Identifier IE value (in the case of a RAN-INFORMATION PDU) of the RIM header.

"RAN-INFORMATION/Initial Multiple Report or RAN-INFORMATION/Single Report PDU exceeds the maximum supported length": the RAN-INFORMATION/Initial Multiple Report PDU exceeds the maximum length supported by the system.

"Inconsistent MBMS data channel description": failure in a MBMS data channel description.

Erroneous Application Container: This field contains the erroneous Application Container IE .

11.3.64.4 Application Error Container for the SON Transfer Application

The coding of the Application Error Container IE for the SON Transfer Application is specified as follows:

Table 11.3.64.4: Application Error Container coding for SON Transfer

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-m

SON Transfer Cause

Octet (m+1)- n

Erroneous Application Container including IEI and LI

SON Transfer Cause: This field indicates the cause why the Application Error Container IE is sent. The "SON Transfer Cause" field is encoded as the SON Transfer Cause IE as defined in 3GPP TS 36.413 [36].

11.3.64.5 Application Error Container for the UTRA SI Application

The coding of the Application Error Container IE for the UTRA SI Application is specified as follows:

Table 11.3.64.5.a: Application Error Container coding for UTRA SI

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

UTRA SI Cause

Octet 4-n

Erroneous Application Container including IEI and LI

UTRA SI Cause: This field indicates the cause why the Application Error Container IE is sent. The UTRA SI Cause field is coded as shown below:

Table 11.3.64.5.b: UTRA SI Cause coding

Coding

Semantic

0000 0000

Unspecified

0000 0001

Syntax Error in the Application Container

0000 0010

Inconsistent Reporting Cell Identifier

Other values

Reserved

"Unspecified": Sent when none of the above cause values applies.

"Syntax Error in the Application Container": The Application Container IE is syntactically incorrect.

"Inconsistent Reporting Cell Identifier": The cell identified by Reporting Cell Identifier in the Application Container IE is unknown in the RNC identified by the Destination Cell Identifier IE value in the RAN-INFORMATION-REQUEST PDU.

Erroneous Application Container: This field contains the erroneous Application Container IE.

11.3.64.6 Application Error Container for the Multilateration Timing Advance Application

The coding of the Application Error Container IE for the Multilateration Timing Advance Application is specified as follows:

Table 11.3.64.5.a: Application Error Container coding for Multilateration Timing Advance

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Multilateration Timing Advance Cause

Octet 4-n

Erroneous Application Container including IEI and LI

Multilateration Timing Advance Cause: This field indicates the cause why the Application Error Container IE is sent. The Multilateration Timing Advance Cause field is coded as shown below:

Table 11.3.64.5.b: Multilateration Timing Advance Cause coding

Coding

Semantic

0000 0000

Unspecified error

0000 0001

Syntax Error in the Application Container

Other values

Reserved

"Unspecified": Sent when none of the above cause values applies.

"Syntax Error in the Application Container": The Application Container IE is syntactically incorrect.

Erroneous Application Container: This field contains the erroneous Application Container IE.

11.3.65 RIM PDU Indications

11.3.65.0 General

This information element contains various indications related to a RAN-INFORMATION-REQUEST PDU, RAN-INFORMATION PDU or RAN-INFORMATION-APPLICATION-ERROR PDU.

The element coding is:

Table 11.3.65.a: RIM PDU Indications IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Reserved

PDU Type Extension

ACK

ACK: this field indicates whether the source side is requesting a RAN-INFORMATION-ACK PDU as response to a RAN-INFORMATION or to a RAN-INFORMATION-APPLICATION-ERROR PDU. This field is coded as shown below.

Table 11.3.65.b: ACK coding

Coding

Semantic

0

No ACK requested

1

ACK requested

PDU Type Extension: This field specifies the type extension of the PDU. The defined values depend on the PDU type.

11.3.65.1 RAN-INFORMATION-REQUEST RIM PDU Indications

The ACK field is not used and shall be considered as spare.

The following values of the PDU Type Extension field are defined:

Table 11.3.65.1: RAN-INFORMATION-REQUEST PDU Type Extension coding

Coding

Semantic

000

RAN-INFORMATION-REQUEST/Stop PDU

001

RAN-INFORMATION-REQUEST/Single Report PDU

010

RAN-INFORMATION-REQUEST/Multiple Report PDU

011

Reserved

100

Reserved

101

Reserved

110

Reserved

111

Reserved

11.3.65.2 RAN-INFORMATION RIM PDU Indications

The ACK field is defined as specified in sub-clause 11.3.65.0.

The following values of the PDU Type Extension field are defined:

Table 11.3.65.2: RAN-INFORMATION PDU Type Extension coding

Coding

Semantic

000

RAN-INFORMATION/Stop PDU

001

RAN-INFORMATION/Single Report PDU

010

RAN-INFORMATION/Initial Multiple Report PDU

011

RAN-INFORMATION/Multiple Report PDU

100

RAN-INFORMATION/End PDU

101

Reserved

110

Reserved

111

Reserved

11.3.65.3 RAN-INFORMATION-APPLICATION-ERROR RIM PDU Indications

The ACK field is defined as specified in sub-clause 11.3.65.0.

The PDU Type Extension field is not used and shall be considered as spare.

11.3.66 (void)

11.3.67 RIM Protocol Version Number

This information element defines which version number of the RIM protocol is in use in the PDU. The element coding is:

Table 11.3.67.a: RIM Protocol Version Number IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

RIM Protocol Version Number

RIM Protocol Version Number is coded as follows:

Table 11.3.67.b: RIM Protocol Version Number IE coding

Coding

Semantic

0000 0000

Reserved

0000 0001

Version 1

Other values

Reserved

If this Information Element is omitted the value "Version 1" should be assumed.

11.3.68 PFC Flow Control parameters

This information element contains the flow control parameters for one or more PFC(s) of a certain MS. The element coding is:

Table 11.3.68.a: PFC Flow Control parameters IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Number of PFCs

Octet 4

PFI (1)

Octet 5-6

Bmax_PFC (1)

Octet 7-8

R_PFC (1)

Octet 9

B_PFC (1)

Octet ?

PFI (2)

Octet ?-?

Bmax_PFC (2)

Octet ?-?

R_PFC (2)

Octet ?

B_PFC (2)

"

"

Octet ?

PFI (n)

Octet ?-?

Bmax_PFC (n)

Octet ?-?

R_PFC (n)

Octet ?

B_PFC (n)

Number of PFCs: Number of PFCs for which flow control parameters are provided. For each of those PFCs follows its identifier and the value of the flow control parameters. The "Number of PFCs"parameter is coded as shown below:

Table 11.3.68.b: Number of PFCs

Coding

Semantic

0000 0000

0 PFC

0000 0001

1 PFC

…

…

0000 1011

11 PFCs

0000 1100

Reserved

‘

"

1111 1111

Reserved

PFI: Packet Flow Identifier. Coded as the value part of the Packet Flow Identifier information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI.

Bmax_PFC: Bucket size of the PFC. Coded like the value part of BVC Bucket Size, see sub-clause 11.3.5.

R_PFC: Bucket Leak Rate of the PFC. Coded as the value part of Bucket Leak Rate (R), see sub-clause 11.3.4.

B_PFC: Bucket Full Ratio of the PFC. This field is only present if the Current Bucket Level (CBL) feature is negotiated. Otherwise, the flow control parameters for the next PFC, if any, are provided instead. This field if coded as the value part of the Bucket Full Ratio, see sub-clause 11.3.46.

11.3.69 Global CN-Id

The Global CN-Id consists of a PLMN-Id and a CN-Id, see 3GPP TS 23.003. The value part of the Global CN-Id is coded as defined in 3GPP TS 29.018. The CN-Id is an integer defined by O&M. The element coding is:

Table 11.3.69: Global CN-Id IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3-7

Coded as octets 3 to 7 of the Global CN-Id IE, defined in 3GPP TS 29.018

11.3.70 RIM Routing Information

This information element uniquely identifies either a cell within a GERAN BSS, a UTRAN RNC, an E-UTRAN eNodeB or an eHRPD eAN. The element coding is:

Table 11.3.70: RIM Routing Information IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Spare

RIM Routing Address

discriminator

octet 4-n

RIM Routing Address

The coding of RIM Routing Address discriminator (bits 4 to 1 of octet 3) is a binary number indicating which type of address is provided in octet 4-n. The RIM Routing Address discriminator is coded as follows:

Bits

4321

0000 A Cell Identifier is used to identify a GERAN cell.

0001 An RNC identifier is used to identify a UTRAN RNC.

0010 An eNB identifier is used to identify an E-UTRAN eNodeB or HeNB

0011 An eHRPD Sector ID is used to identify an eHRPD eAN

All other values are reserved.

The coding of octet 4-n depends on the RIM Routing Address discriminator (octet 3) as it is specified below.

RIM Routing Address discriminator = 0000:

The RIM Routing Address field contains a Cell Identifier and is coded as the value part (octet 3 to octet 10) of the Cell Identifier information element specified in sub-clause 11.3.9.

RIM Routing Address discriminator = 0001:

The RIM Routing Address field contains an RNC identifier and is coded as follows:

8

7

6

5

4

3

2

1

Octets 4 to 9 contain the value part (starting with octet 2) of the Routing Area Identification IE defined in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI

octets 4-9

RNC-ID (or Extended RNC-ID)

octet 10

RNC-ID (or Extended RNC-ID) (continued)

octet 11

The octets 10-11 contain the RNC-ID (0..4095) or the Extended RNC-ID (4096..65535) – see 3GPP TS 25.413:

– The least significant bit of RNC-ID is octet 11 bit 1 and most significant bit is octet 10 bit 4. In the octet 10 bits 5-8 are set to "0000".

– The least significant bit of Extended RNC-ID is octet 11 bit 1 and most significant bit is octet 10 bit 8.

RIM Routing Address discriminator = 0010:

The RIM Routing Address field contains an eNB identifier and is coded as follows:

8

7

6

5

4

3

2

1

Octets 4 to 8 contain the value part (starting with octet 2) of the Tracking Area Identity IE defined in 3GPP TS 24.301 [37], not including 3GPP TS 24.301 IEI [37]

octet 4-8

Global eNB ID

octet 9-n

Octets 9-n contain the Global eNB ID (see 3GPP TS 36.413 [36] sub-clause 9.3.4, Global-ENB-ID Sequence) of the eNodeB.

RIM Routing Address discriminator = 0011:

The RIM Routing Address field contains an eHRPD evolved Access Network identifier and is coded as follows:

8

7

6

5

4

3

2

1

eHRPD Sector ID

octet 4-n

Octets 4-n contain the eHRPD Sector ID defined in 3GPP2 C.S0024-B [47].

11.3.71 MBMS Session Identity

The MBMS Session Identity is an identification of the MBMS Session as defined in 3GPP TS 23.246 [32]. The element coding is:

Table 11.3.71: MBMS Session Identity IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

MBMS-Session-Identity AVP encoded as in 3GPP TS 29.061 [31], excluding AVP Header fields as defined in IETF RFC 3588 [33].

11.3.72 MBMS Session Duration

The MBMS Session Duration defines the (remaining) duration of the MBMS Session as defined in 3GPP TS 23.246 [32]. The element coding is:

Table 11.3.72: MBMS Session Duration IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3-m

MBMS-Session-Duration AVP encoded as in 3GPP TS 29.061 [31], excluding AVP Header fields as defined in IETF RFC 3588 [33].

11.3.73 MBMS Service Area Identity List

The MBMS Service Area Identity List identifies the Service Areas Identities for the Service Areas where the MBMS Session shall be active as defined in 3GPP TS 29.061. The element coding is:

Table 11.3.73: MBMS Service Area Identity List IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3 – 514

MBMS-Service-Area AVP encoded as in 3GPP TS 29.061, excluding AVP Header fields (as defined in IETF RFC 3588 [33]).

11.3.74 MBMS Response

The MBMS Response identifies the Cause Values from the BSS regarding MBMS.

Table 11.3.74.a: MBMS Response IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Spare

Spare

Spare

Spare

Cause Value

Table 11.3.74.b: Cause Value

(octet 3)

Bits 8 7 6 5 Spare

Bits

4 3 2 1

0 0 0 0 Acknowledge

0 0 0 1 Acknowledge, initiate data transfer

0 0 1 0 Acknowledge, data transfer initiated from other SGSN

0 0 1 1 Reject – Congestion

0 1 0 0 Reject – None of the listed MBMS Service Areas are supported by BSS

0 1 0 1 Reject – MBMS Service Context is released due to interrupted data flow

0 1 1 0

: Unspecified in this version of the protocol

1 1 1 1

11.3.75 MBMS Routing Area List

The MBMS Routing Area List identifies each Routing Area that contains at least one PMM-IDLE MS that has activated the MBMS bearer service. The list may be empty.

Table 11.3.75.a: MBMS Routing Area List IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Number of Routing Area Identifications

Spare

Spare

Spare

Spare

octet 4 – 11

Routing Area Identification 1

octet 12 – 19

Routing Area Identification 2

octet 20 – 27

Routing Area Identification 3

octet 28 – 35

Routing Area Identification 4

octet 36 – 43

Routing Area Identification 5

octet 44 – 51

Routing Area Identification 6

octet 52 – 59

Routing Area Identification 7

octet 60 – 67

Routing Area Identification 8

octet 68 – 75

Routing Area Identification 9

octet 76 – 83

Routing Area Identification 10

octet 84 – 91

Routing Area Identification 11

octet 92 – 99

Routing Area Identification 12

octet 100 – 107

Routing Area Identification 13

octet 108 – 115

Routing Area Identification 14

Table 11.3.75.b: MBMS Routing Area List information element details

Number of Routing Areas (octet 3)
8 7 6 5
0 0 0 0 Notification shall not be sent to any Routing Areas in the BSS
0 0 0 1 "1" Routing Area Identities
:
:

1 1 1 0 "14" Routing Area Identities
1 1 1 1 Notification shall be sent in all Routing Areas in the BSS

4 3 2 1 (octet 3)
Spare

Routing Area Identification i 7 octets (octet 4, 12, 20, 28, 36, 44, 52, 60, 68, 76, 84, 92, 100 and 108)
The element is coded as the Routing Area Identification information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 length indicator.

11.3.76 MBMS Session Information

The MBMS Session Information carries information about the MBMS Session from the SGSN to the BSS.

Table 11.3.76.a: MBMS Session Information IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Spare

Spare

Spare

Spare

Spare

Spare

Spare

BC/MC

Table 11.3.76.b: MBMS Session Information information element details

BC/MC (octet 3)
This field indicates wheter it is a Broadcast or an Multicast MBMS Session.
Bit
1
0 Broadcast Session
1 Multicast Session

8 7 6 5 4 3 2 (octet 3)
Spare

11.3.77 TMGI (Temporary Mobile Group Identity)

The purpose of TMGI is for group paging in MBMS as defined in 3GPP TS 24.008.

Table 11.3.77: TMGI IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2,2a

Length Indicator

octet 3-8

Rest of element coded as in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI and 3GPP TS 24.008 length indicator.

11.3.78 MBMS Stop Cause

The MBMS Stop Cause identifies the Cause Values for stopping an MBMS Session.

Table 11.3.74.a: MBMS Stop Cause IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Spare

Spare

Spare

Spare

Cause Value

Table 11.3.74.b: Cause Value

(octet 3)

Bits 8 7 6 5 Spare

Bits

4 3 2 1

0 0 0 0 MBMS Session terminated by upstream node

0 0 0 1 MBMS Session terminated by SGSN

0 0 1 0

: Unspecified in this version of the protocol

1 1 1 1

11.3.79 Source BSS to Target BSS Transparent Container

This information element contains the information needed in the Target BSS to execute a PS Handover.

The element coding is:

Table 11.3.79.a: Source BSS to Target BSS Transparent Container coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-?

Source BSS to Target BSS Transparent Container Contents coded as defined in table 11.3.79.b

Table 11.3.79.b: Source BSS to Target BSS Transparent Container Contents

Information Elements

Type / Reference

Presence

Format

Length

MS Radio Access Capability

MS Radio Access Capability/11.3.22

M

TLV

7-?

Inter RAT Handover Info

Inter RAT Handover Info/11.3.94

O (note 1)

TLV

3-?

Page Mode

Page Mode/11.3.88

O (note 2, note 3)

TLV

3

Container ID

Container ID/11.3.89

O (note 2)

TLV

3

Global TFI

Global TFI/11.3.90

O (note 2, note 3)

TLV

3

PS Handover Indications

PS Handover Indications/11.3.95a

O

TLV

3

CS Indication

CS Indication/11.3.98

O (note 3)

TLV

3

E-UTRAN Inter RAT Handover Info

E-UTRAN Inter RAT Handover Info/11.3.104

O (note 1)

TLV

3-?

IRAT Measurement Configuration

IRAT Measurement Configuration/11.3.115

O

(note 4)

TLV

3-?

Source Cell ID

Source Cell ID/11.3.120

O

(note 4, note 5)

TLV

8-?

IRAT Measurement Configuration (extended E-ARFCNs)

IRAT Measurement Configuration (extended E-ARFCNs)/11.3.121

O

(note 4)

TLV

3-?

NOTE1: This information element shall be present if available in the source BSS.

NOTE2: This information element shall be present in case of PS Handover from A/Gb mode.

NOTE3: This information element shall be present in case of DTM Handover from A/Gb mode.

NOTE4: This information element may be present in case of PS Handover from E-UTRAN (see 3GPP TS 36.413 [36])

NOTE 5: This information element shall be present in case either the IRAT Measurement Configuration information element or the IRAT Measurement Configuration (extended E-ARFCNs) information element is present.

11.3.80 Target BSS to Source BSS Transparent Container

This information element contains the information needed in the Source BSS to execute a PS Handover.

The element coding is:

Table 11.3.80.a: Target BSS to Source BSS Transparent Container coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2 2a

Length Indicator

Octet 3-?

Target BSS to Source BSS Transparent Container Contents coded as defined in table 11.3.80.b

Table 11.3.80.b: Target BSS to Source BSS Transparent Container Contents

Information Elements

Type / Reference

Presence

Format

Length

PS Handover Command

PS Handover Command/11.3.95

O (Note 2)

TLV

4-?

SI/PSI Container

SI/PSI Container/11.3.95b

O (Note 1)

TLV

3-?

DTM Handover Command

DTM Handover Command/11.3.97

O (Note 2)

TLV

22-?

NOTE 1: This information element shall be included when requested in the PS-HANDOVER-REQUEST PDU.

NOTE 2: Only one of these information elements shall be included.

11.3.81 NAS container for PS Handover

This information element contains the NAS container for PS Handover. The value part of this IE is to be included in the PS Handover Command message within the Target BSS to Source BSS Transparent Container IE.

The element coding is:

Table 11.3.81: NAS container for PS Handover coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octets 3-?

NAS container for PS HO coded as defined in 3GPP TS 24.008

11.3.82 PFCs to be set-up list

This information element contains the Packet Flow Context parameters for one or more PFC(s), that the SGSN requests the target BSS to set-up.

The element coding is:

Table 11.3.82.a: PFCs to be set-up list IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Number of PFCs

Octet 4-6

PFI (1)

Octet 7-9

PFT (1)

Octet 10-?

ABQP (1)

Octet ?-?

Allocation/Retention Priority (1)

Octet ?-?

T10 (1)

Octet ?-?

PFI (2)

Octet ?-?

PFT (2)

Octet ?-?

ABQP (2)

Octet ?-?

Allocation/Retention Priority (2)

Octet ?-?

T10 (2)

"

"

Octet ?-?

PFI (n)

Octet ?-?

PFT (n)

Octet ?-?

ABQP (n)

Octet ?-?

Allocation/Retention Priority (n)

Octet ?-?

T10 (n)

Number of PFCs: Number of PFCs for which packet flow context parameters are provided. For each of those PFCs follows its identifier and the packet flow context parameters. The "Number of PFCs" parameter is coded as shown below:

Table 11.3.82.b: Number of PFCs

Coding

Semantic

0000 0000

Reserved

0000 0001

1 PFC

…

…

0000 1011

11 PFCs

0000 1100

Reserved

‘

"

1111 1111

Reserved

PFI: Packet Flow Identifier. Coded as the Packet Flow Identifier information element, see sub-clause 11.3.42

PFT: Packet Flow Timer. Coded as the GPRS Timer information element, see sub-clause 11.3.44.

ABQP: Aggregate BSS QoS Profile. Coded as the Aggregate BSS QoS Profile information element, see sub-clause 11.3.43.

Allocation/Retention Priority: Allocation Retention Priority. Coded as the Priority information element, see sub-clause 11.3.27. This information element is optionally included.

T10: T10. Coded as the GPRS Timer information element, see sub-clause 11.3.44. This information element shall be present for a PFC if the Allocation/Retention Priority is present and if queuing is allowed for the PFC.

11.3.83 List of set-up PFCs

This information element contains the Packet Flow Identifiers of the PFCs that were successfully allocated in the target system during a PS handover. The element coding is:

Table 11.3.83.a: List of set-up PFCs IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Number of PFCs

Octet 4

PFI (1)

Octet 5

PFI (2)

"

"

Octet ?

PFI (n)

Number of PFCs: Number of PFCs for which corresponding Packet Flow Identifiers are provided. The "Number of PFCs" parameter is coded as shown below:

Table 11.3.83.b: Number of PFCs

Coding

Semantic

0000 0000

0 PFC

0000 0001

1 PFC

…

…

0000 1011

11 PFCs

0000 1100

Reserved

‘

"

1111 1111

Reserved

PFI: Packet Flow Identifier. Coded as the value part of the Packet Flow Identifier information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI.

11.3.84 Extended Feature Bitmap

The Extended Feature bitmap information element indicates the optional features supported by the underlying NSE. The element coding is:

Table 11.3.84.a: Extended Feature Bitmap IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

MSADCN

eDRX

DCN

EC-GSM-IoT

CS/PS coord

MOCN

Gigabit Interface

PS Handover

Table 11.3.84.b: "PS Handover" coding

coding

Semantic

0

PS Handover not supported

1

PS Handover supported

Table 11.3.84.c: "Gigabit Interface" coding

coding

Semantic

0

Gigabit Interface not supported

1

Gigabit Interface supported

Table 11.3.84.d: "Multi Operator Core Network” coding

coding

Semantic

0

Multi Operator Core Network not supported

1

Multi Operator Core Network supported

Table 11.3.84.e: "CS/PS coordination enhancements” coding

coding

Semantic

0

CS/PS coordination enhancements not supported

1 (note)

CS/PS coordination enhancements supported

Table 11.3.84.f: "EC-GSM-IoT” coding

coding

Semantic

0

EC-GSM-IoT not supported

1

EC-GSM-IoT supported

Table 11.3.84.g: “eDRX” coding

coding

Semantic

0

eDRX is not supported (see Note 1)

1

eDRX is supported

Note 1: A SGSN shall consider a BSS that indicates it does not support eDRX but indicates it supports EC-GSM-IoT as only supporting the lowest eDRX cycle (see 3GPP TS 23.682).

Table 11.3.84.h: "DCN” coding

coding

Semantic

0

Dedicated Core Network not supported

1

Dedicated Core Network supported

Table 11.3.84.i: "MSADCN” coding

coding

Semantic

0

MS assisted Dedicated Core Network selection not supported

1

MS assisted Dedicated Core Network selection supported

NOTE: The CS/PS coordination enhancements bit may only be set to ‘1’ if the Multi Operator Core Network bit is set to ‘1’.

11.3.85 Source to Target Transparent Container

This information element contains the information needed in the target RAN node to execute a inter-RAT PS or DTM Handover.

The element coding is:

Table 11.3.85: Source to Target Transparent Container coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octets 3-?

Source to Target Transparent Container content coded as specified in 3GPP TS 25.413 or 3GPP TS 36.413.

In inter-RAT handovers to Iu mode this IE includes the Source RNC to Target RNC Transparent container. The Source RNC to Target RNC Transparent Container content structure and encoding is defined in relevant RANAP specification 3GPP TS 25.413, excluding RANAP tag.

In inter-RAT handover to E-UTRAN this IE includes the Source eNB to Target eNB Transparent container. The Source eNB to Target eNB Transparent Container content structure and encoding is defined in 3GPP TS 36.413.

11.3.86 Target to Source Transparent Container

This information element contains the information needed in the Source BSS to execute a inter-RAT PS Handover.

The element coding is:

Table 11.3.86: Target to Source Transparent Container coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octets 3-?

Rest of element coded as either a complete Handover to UTRAN Command radio interface message (as defined in 3GPP TS 25.331) or a complete Radio Bearer Reconfiguration radio interface message (as defined in 3GPP TS 44.118) or a HandoverCommand message that consists only of the DL-DCCH-Message including a complete RRCConnectionReconfiguration radio interface message (as defined in 3GPP TS 36.331)

11.3.87 RNC Identifier

This information element contains the identifier of the RNC in case of PS Handover to UTRAN or the Corresponding RNC-ID of the eNB in case of PS handover to E-UTRAN as specified in 3GPP TS 25.413.

The element coding is:

Table 11.3.87: RNC Identifier coding

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 24.008, not including 3GPP TS 24.008 IEI

Octet 9

RNC ID (or Extended RNC-ID or Corresponding RNC-ID)

Octet 10

RNC ID (or Extended RNC-ID or Corresponding RNC-ID) (continued)

RNC ID (or Extended RNC-ID or Corresponding RNC-ID): The octets 9-10 contain the RNC-ID (0..4095) or the Corresponding RNC-ID (0..4095) or the Extended RNC-ID (4096..65535) – see 3GPP TS 25.413:

– The least significant bit of RNC-ID is octet 10 bit 1 and most significant bit is octet 9 bit 4. In the octet 9 bits 5-8 are set to "0000".

– The least significant bit of Extended RNC-ID is octet 10 bit 1 and most significant bit is octet 9 bit 8.

For detailed definition of the RNC-Id see 3GPP TS 23.003.

11.3.88 Page Mode

This information element contains the Page Mode to be used by the MS.

The element coding is:

Table 11.3.88: Page Mode coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Reserved

PAGE_MODE coded as specified in 3GPP TS 44.060

11.3.89 Container ID

This information element contains the identity of the neighbour cell system information container previously sent to the MS.

The element coding is:

Table 11.3.89: Container ID coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Reserved

Container ID coded as specified in 3GPP TS 44.060

11.3.90 Global TFI

This information element contains the TFI of the mobile station’s downlink or uplink TBF.

The element coding is:

Table 11.3.90: Global TFI coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Reserved

Global TFI coded as specified in 3GPP TS 44.060

11.3.91 IMEI

This information element contains the International Mobile Station Equipment Identity (see 3GPP TS 23.003). The element coding is:

Table 11.3.91: IMEI IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3-10

Octets 3-10 contain the IMEI coded as the value part of the Mobile Identity IE defined in 3GPP TS 24.008
(NOTE 1)

NOTE 1: The Type of identity field in the Mobile Identity IE shall be ignored by the receiver.

11.3.92 Time to MBMS Data Transfer

The Time to MBMS Data Transfer denotes the time occurring between the transmission of the MBMS-SESSION-START-REQUEST PDU or the MBMS-SESSION-UPDATE-REQUEST PDU to the BSS and the actual start of the data transfer at the BM-SC.

Table 11.3.92.a: Time to MBMS Data Transfer IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Time to MBMS Data Transfer Value Part

Table 11.3.92.b: Time to MBMS Data Transfer Value Part Coding

Bits

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0 1s

0 0 0 0 0 0 0 1 2s

0 0 0 0 0 0 1 0 3s

:

1 1 1 1 1 1 1 1 256s

11.3.93 MBMS Session Repetition Number

The MBMS Session Repetition Number denotes the repetition number of the MBMS session as defined in 3GPP TS 23.246 [32]. The element coding is:

Table 11.3.93: MBMS Session Repetition Number IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

MBMS-Session-Repetition-Number AVP encoded as in 3GPP TS 29.061 [31], excluding AVP Header fields as defined in IETF RFC 3588 [33].

11.3.94 Inter RAT Handover Info

This information element contains UTRAN related information needed to be transferred to the target RNC during a PS Handover to UTRAN. The element coding is:

Table 11.3.94: Inter RAT Handover Information coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octets 3-?

Inter RAT Handover Information coded as specified in 3GPP Technical Specification 25.331

11.3.95 PS Handover Command

This information element contains the radio interface message to be sent to the mobile station.

The element coding is:

Table 11.3.95: PS Handover Command coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2 2a

Length Indicator

Octet 3-?

Rest of element coded as a complete PS Handover Command radio interface message as defined in 3GPP TS 44.060 (carrying the PS Handover to A/Gb Mode Payload)

11.3.95a PS Handover Indications

The PS Handover Indications information element provides indications related to the PS Handover procedure. The element coding is:

Table 11.3.95a.a: PS Handover Indications IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Spare

DMLC Carriers

SI/PSI

Table 11.3.95a.b: "SI/PSI" coding

coding

Semantic

0

SI/PSI not requested

1

SI/PSI requested

Table 11.3.95a.c: "DLMC Carriers" coding

coding

Semantic

00

2 or 3 carriers currently assigned

01

4 or 5 carriers currently assigned

10

6 or 7 carriers currently assigned

11

8 or more carriers currently assigned

11.3.95b SI/PSI Container

The SI/PSI Container information element provides the (Packet) System Information messages of the GSM target cell that are required by the mobile station for PS Handover. The element coding is:

Table 11.3.95b.a: SI/PSI Container coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Number of SI/PSI

Type

Octet 4-n

SI/PSI

Type: This field indicates the type of the (Packet) System Information messages provided by the target cell. The Type field is coded as shown below:

Table 11.3.95b.b: Type coding

Coding

Semantic

0

SI messages as specified for BCCH (3GPP TS 44.018) follow

1

PSI messages as specified for PBCCH (3GPP TS 44.060) follow

Number of SI/PSI: This field indicates the number of (Packet) System Information messages contained in the SI/PSI field. For (Packet) System Information messages with multiple instances, each instance is counted as one SI/PSI message. The Number of SI/PSI field is coded as shown below:

Table 11.3.95b.c: Number of SI/PSI coding

Coding

Semantic

000 0000

0 "SI/PSI" follows

000 0001

1 "SI/PSI" follow

‘

"

111 1111

127 "SI/PSI" follow

SI/PSI: This field contains either a list of System Information or a list of Packet System Information messages of the GSM target cell that are required by the mobile station for PS Handover as specified in 3GPP TS 44.060. The number of (Packet) System Information messages is indicated in the Number of SI/PSI field specified above. Furthermore:

– If the Type field indicates that "SI messages as specified for BCCH (3GPP TS 44.018) follow" then the SI/PSI field contains the subset of System Information message instances encoded for BCCH as specified in 3GPP TS 44.018. Each System Information message contains the Message type octet followed by all the IEs composing the message payload. Each message is 21 octets long.

– If the Type field indicates that "PSI messages as specified for PBCCH (3GPP TS 44.060) follow" then the SI/PSI field contains the subset of Packet System Information message instances encoded for PBCCH as specified in 3GPP TS 44.060. Each Packet System Information message contains the MESSAGE_TYPE field followed by the PSI message content. Each message is 22 octets long.

11.3.95c Active PFCs List

This information element contains the Packet Flow Identifiers of the PFCs that are active in the source BSS at the time the PS Handover Required message is sent. The element coding is:

Table 11.3.95c.a: Active PFCs List IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Number of PFCs

Octet 4

PFI (1)

Octet 5

PFI (2)

"

"

Octet ?

PFI (n)

Number of PFCs: Number of PFCs for which corresponding Packet Flow Identifiers are provided. The "Number of PFCs" parameter is coded as shown below:

Table 11.3.95c.b: Number of PFCs

Coding

Semantic

0000 0000

Reserved

0000 0001

1 PFC

…

…

0000 1011

11 PFCs

0000 1100

Reserved

‘

"

1111 1111

Reserved

PFI: Packet Flow Identifier. Coded as the value part of the Packet Flow Identifier information element in 3GPP TS 24.008, not including 3GPP TS 24.008 IEI. This IE shall not contain any pre-defined PFIs.

11.3.96 Velocity Data

This is a variable length information element providing an estimate of a velocity data. The element coding is:

Table 11.3.96: Velocity Data IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2

Length indicator

Octet 3

to

Octet n

The rest of the information element contains an octet sequence identical to that for Description of Velocity defined in 3GPP TS 23.032.

11.3.97 DTM Handover Command

This information element contains the radio interface message to be sent to the mobile station.

The element coding is:

Table 11.3.97: DTM Handover Command coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-?

Rest of element coded as a complete DTM Handover Command radio interface message as defined in 3GPP TS 44.060 (carrying the DTM Handover to A/Gb Mode Payload)

11.3.98 CS Indication

This information element indicates to the target BSS that this PS Handover is part of a DTM Handover Procedure.

The element coding is:

Table 11.3.98: CS Indication coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

CS Indication Contents

CS Indication Contents: This identifies a particular handover attempt for this MS. This shall be identical to the PS Indication Contents value in the corresponding PS Indication IE included in the Old BSS to New BSS Information IE (see 3GPP TS 48.008). The choice of the value of this field is implementation specific, with the requirement that consecutive handover attempts for the same mobile station shall not have the same CS Indication Contents value.

11.3.99 Requested GANSS Assistance Data

This information element provides the information on which GANSS Assistance Data has been requested. The element coding is:

Table 11.3.99: Requested GANSS Assistance Data 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 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator

11.3.100 GANSS Location Type

This information element provides the GANSS Location Type. The element coding is:

Table 11.3.53: Location Type 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 3GPP TS 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator

11.3.101 GANSS Positioning Data

This information element provides GANSS Positioning Data. The element coding is:

Table 11.3.55: Positioning Data 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 49.031, not including 3GPP TS 49.031 IEI and 3GPP TS 49.031 octet length indicator

11.3.102 Flow Control Granularity

This information element provides the granularity to be used for deriving the Flow Control parameters values in the BVC Bucket Size IE, the BVC Bucket Leak Rate IE and the PFC flow control parameters IE when the Gigabit Interface feature is negotiated. The element coding is:

Table 11.3.102: Flow Control Granularity IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Reserved

Granularity

Table 11.3.102.a: "Granularity" coding

coding

Semantic

00

100 octets or bits/s increments

01

1000 octets or bits/s increments

10

10000 octets or bits/s increments

11

100000 octets or bits/s increments

11.3.103 eNB Identifier

This information element contains the information required to identify an eNB within a PLMN.

The element coding is:

Table 11.3.103: eNB Identifier coding

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 Tracking Area Identity IE defined in 3GPP TS 24.301 [37], not including 3GPP TS 24.301 IEI [37]

Octet 8-n

Global eNB ID

Octets 8-n contain the Global eNB ID (see 3GPP TS 36.413 [36] sub-clause 9.3.4, Global-ENB-ID Sequence) of the eNodeB.

11.3.104 E-UTRAN Inter RAT Handover Info

This information element contains E-UTRAN related information needed to be transferred to the target eNB during a PS Handover to E-UTRAN. The element coding is:

Table 11.3.104: E-UTRAN Inter RAT Handover Information coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octets 3-?

Formatted and coded according to the UE-EUTRA-Capability IE defined in 3GPP Technical Specification 36.331. The most significant bit of the first octet of the octet string contains bit 8 of the first octet of the IE.

11.3.105 Subscriber Profile ID for RAT/Frequency priority

This information element may be used by the BSS to provide individual priorities (see 3GPP TS 44.060) to mobile stations.

The element coding is:

Table 11.3.105.1: Subscriber Profile ID for RAT/Frequency priority coding

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2

Length Indicator

Octet 3

Octet 3 contains the value part of the Subscriber Profile ID for RAT/Frequency priority IE.

Octet 3 contains a number in binary representation ranging from 0 to 255. The Subscriber Profile ID for RAT/Frequency priority is given by the indicated value +1.

11.3.106 Request for Inter-RAT Handover Info

The Request for Inter RAT Handover Info information element provides the request from the BSS to the SGSN for the Inter RAT Handover Info IE for UTRAN necessary for inter-RAT PS Handover procedure to UTRAN. The element coding is:

Table 11.3.106.a: Request for Inter RAT Handover Info IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Spare

E-UTRAN Inter RAT Handover Info

Req

Inter RAT Handover Info Req

Table 11.3.106.b: "Inter RAT Handover Info Req" coding

Coding

Semantic

0

Inter RAT Handover Info not requested

1

Inter RAT Handover Info requested

Table 11.3.106.c: "E-UTRAN Inter RAT Handover Info Req" coding

coding

Semantic

0

See note

NOTE: The value ‘1’ was allocated in a previous version of the protocol and shall not be used.

11.3.107 Reliable Inter-RAT Handover Info

The Reliable Inter RAT Handover Info information element provides to the target BSS the indication that the source BSS has received the Inter RAT Handover Info for UTRAN from the SGSN in the CREATE-BSS-PFC-PDU or in the PS-HANDOVER-COMPLETE-ACK PDU upon successful completion of PS handover or a PS-HANDOVER-REQUEST PDU with “Reliable Inter RAT Handover Info Indicator” set to “1”. The element coding is:

Table 11.3.107.a: Reliable Inter RAT Handover Info IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Spare

Reliable Inter RAT Handover Info Indicator

Table 11.3.107.b: "Reliable Inter RAT Handover Info Indicator” coding

Coding

Semantic

0

Inter RAT Handover Info not reliable

1

Inter RAT Handover Info reliable

11.3.108 SON Transfer Application Identity

This information element specifies the addressed SON Transfer application within the target BSS node. The element coding is:

Table 11.3.108: SON Transfer Application Identity IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3-m

SON Transfer Application Identity

SON Transfer Application Identity: This field is encoded as the SON Transfer Application Identity IE as defined in 3GPP TS 36.413 [36].

11.3.109 CSG Identifier

The CSG Identifier information element indicates the identifier of the Closed Subscriber Group within the PLMN, as defined in [40], and the cell access mode of the CSG cell as defined in [22], [39]. The element coding is:

Table 11.3.109.a: CSG Identifier IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octets 3-6

Octets 3 to 6 contain the CSG Identity (CSG-ID) of the cell (defined in 3GPP TS 23.003) as reported by the mobile station (see 3GPP TS 44.060). Bits 4 to 8 of octet 6 are spare and set to zero.

octet 7

Spare

Cell Access Mode

Table 11.3.109.b: Cell Access Mode field element details

Cell Access Mode (bit 1 of octet 7)
This field indicates the cell access mode of the cell as reported by the mobile station.
Bit
1
0 CSG cell
1 Hybrid cell

Spare bits are reserved and coded with zeroes.

11.3.110 Tracking Area Code

The TAC information element provides an unambiguous identification of tracking areas needed for routing of the PS handover signalling to the target cell. The element coding is:

Table 11.3.110: TAC IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octets 3-5

Octets 3 to 5 contain the value part (starting with octet 2) of the TAC IE defined in 3GPP TS 24.301.

11.3.111 Redirect Attempt Flag

This information element provides control information for the MOCN, GWCN and for the DCN rerouting procedure. It indicates that the CN shall include in the answer either Redirection Indication IE or Redirection Completed IE.

The element coding is:

Table 11.3.111: Redirect Attempt Flag IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

spare

11.3.112 Redirection Indication

This information element provides control information for the MOCN, GWCN and for the DCN rerouting procedure. It indicates that the CN requests rerouting by the BSS to another CN operator. The Reroute Reject cause is given.

Table 11.3.112: Redirection Indication IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Reroute Reject Cause value

Reroute Reject cause value (octet 3)

Bits

8

7

6

5

4

3

2

1

0

0

0

0

0

0

0

0

Reserved

"

"

0

0

0

0

1

0

1

0

Reserved

0

0

0

0

1

0

1

1

PLMN not allowed (meaning is defined in 3GPP TS 24.008 [11])

0

0

0

0

1

1

0

0

location area not allowed (meaning is defined in 3GPP TS 24.008 [11])

0

0

0

0

1

1

0

1

roaming not allowed in this location area (meaning is defined in 3GPP TS 24.008 [11])

0

0

0

0

1

1

1

0

GPRS services not allowed in this PLMN (meaning is defined in 3GPP TS 24.008 [11])

0

0

0

0

1

1

1

1

no suitable cell in location area (meaning is defined in 3GPP TS 24.008 [11])

0

0

0

1

0

0

0

0

CS/PS domain registration coordination required (meaning defined in 3GPP TS 23.251 [43])

0

0

0

1

0

0

0

1

Network failure (meaning is defined in 3GPP TS 24.008 [11])

0

0

0

1

0

0

1

0

Rerouting to a DCN required

0

0

0

1

0

0

1

1

Reserved

"

"

1

1

1

1

1

1

1

1

Reserved

11.3.113 Redirection Completed

This information element provides control information for the MOCN, GWCN and for the DCN rerouting procedure. It indicates that the reroute procedure is completed.

The element coding is:

Table 11.3.113: Redirection Completed IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

Outcome value

Outcome value (octet 3)

Bits

8

7

6

5

4

3

2

1

0

0

0

0

0

0

0

0

Reserved

0

0

0

0

0

0

0

1

MS is accepted

0

0

0

0

0

0

1

0

MS is not accepted

0

0

0

0

0

0

1

1

MS is already registered

0

0

0

0

0

1

0

0

Reserved

“

“

1

1

1

1

1

1

1

1

Reserved

11.3.114 Unconfirmed send state variable

This IE indicates the value of the Unconfirmed send state variable as defined in 3GPP TS 44.064 [12].

The element coding is:

Table 11.3.114: Unconfirmed send state variable IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2, 2a

Length Indicator

Octet 3

spare

V(U) MSB

Octet 4

V(U)

Octet 2 and bit 1 of octet 3 contain a number in binary representation ranging from 0 to 511. The least significant bit is bit 1 of octet 3, and the most significant bit is bit 1 of octet 2.

11.3.115 IRAT Measurement Configuration

The IRAT Measurement Configuration IE is used to indicate to the BSS which frequency measurement results of the source RAT shall be collected after a successful inter-system handover. The IRAT Measurement Configuration IE is used by the source RAT to specify the E-UTRA frequencies for which the corresponding EARFCN is less than 65535 to be reported back to the source RAT (each of them associated with a measurement bandwidth), the minimum radio quality and the period of time that the measurements should last before triggering a HO Report for unnecessary handover to another RAT.

NOTE 1: HO Report is defined in 3GPP TS 36.413 [36].

NOTE 2: The functionality of Unnecessary IRAT HO is described in 3GPP TS 36.300 [45].

NOTE 3: E-UTRA frequencies corresponding to E-ARFCNs in the value range from 65536 to 262143 shall be indicated using the IRAT Measurement Configuration (extended E-ARFCNs) IE (see subclause 11.3.121); in such a case, E-UTRA frequencies corresponding to E-ARFCNs in the value range from 0 to 65534 (value 65535 is reserved and shall not be used) shall be indicated using the IRAT Measurement Configuration IE.

The element coding is:

Table 11.3.115: IRAT Measurement Configuration IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2

Length Indicator

Octet 3

Spare

REP_QUANT

REPORTING_THRESHOLD

Octet 4

Measurement _Duration

Octets 5-6

E-ARFCN

Octet 7

Spare

Measurement Bandwidth

Octets 8-9

E-ARFCN

Octet 10

Spare

Measurement Bandwidth

“

“

Octets m-(m+1)

E-ARFCN

Octet m+2

Spare

Measurement Bandwidth

REPORTING_THRESHOLD: defines the reporting threshold to be used for measurement results analysis according to REP_QUANT. This threshold is used to compare against the measurement results received from the MS. It is a value between 0 and 63 encoded on 6 bits according to 3GPP TS 45.008 [44] sub-section 8.1.5.4.

REP_QUANT: indicates the measurement quantity for E-UTRAN cells coded as follows: 0=RSRP 1=RSRQ.

Measurement _Duration: defines (in seconds) how long the BSS shall collect the measurements results received from the MS after a successful inter-RAT handover. It is a number in binary representation ranging from 1 to 100.

E- ARFCN: designates a specific E-UTRA frequency for which the target RAT should continue to collect the measurement results received from MS of this frequency. It is coded as a number in binary representation ranging from 0 to 65534 (value 65535 is reserved and shall not be used).

Measurement Bandwidth: defines the measurement bandwidth of the E-UTRA frequency signalled in the two previous octets. It is coded on 3 bits according to 3GPP TS 44.018 [25].

11.3.116 SCI

The SCI information element provides information on the service class of the user data. The element coding is:

Table 11.3.116-1: SCI IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Octet 3 contains the value part (octet 2) of the SCI IE defined in 3GPP TS 29.281 [46].

Octet 3 specifies the Service Class value for LLC PDUs of applications benefitting from specific RRM behaviour.

11.3.117 GGSN/P-GW location

The GGSN/P-GW location information element provides information on the location of the GGSN/P-GW that encoded the SCI. The element coding is:

Table 11.3.117.a: GGSN/P-GW location IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

GGSN/P-GW location

In octet 3, bits 8 to 4 are spare, set to zero by the SGSN and shall be ignored by the BSS. The coding of bits 3 to 1 is specified in Table 11.3.117.b.

Table 11.3.117.b: GGSN/P-GW location coding

Octet 3

Semantic

Bit:

3 2 1

0 0 0

HPLMN

0 0 1

VPLMN

0 1 0

Operator Group GGSN

0 1 1

Unknown

1 0 0 to 1 1 1

For future use (treat as VPLMN)

The conditions under which the SGSN indicates the values defined in Table 11.3.117.b are specified in 3GPP TS 23.060 [7].

11.3.118 Selected PLMN ID

The purpose of the Selected PLMN ID information element is to provide the SGSN with the PLMN ID selected by a mobile station supporting network sharing when network sharing is in use in a cell.

Table 11.3.116: Selected PLMN ID IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

Octet 3

MCC dig 2

MCC dig 1

Octet 4

MNC dig 3

MCC dig 3

Octet 5

MNC dig 2

MNC dig 1

NOTE: The MCC and MNC value field is coded as specified within 3GPP TS 24.008 [11].

11.3.119 Priority Class Indicator

This information element indicates that overload has occurred in the SGSN and traffic for the indicated priority class should be reduced.

Table 11.3.118: Priority Class Indicator IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2

Length Indicator

octet 3

Value part of Priority Class Indicator

The Value part of Priority Class Indicator is coded as a bit string with length of 8. Each bit represents a kind of priority class as specified below. If a bit is set to “1“, the signalling traffic of the respective priority class should be reduced.

Bit (0) = A mobile station configured for "low access priority" as defined in TS 44.060.

Bits (1…7) are spare. The SGSN shall set them to "0 ". The BSS shall ignore them.

11.3.120 Source Cell ID IE

The Source Cell ID IE is used to indicate to the BSS the identification of the source cell, e.g. in the Unnecessary IRAT HO case (see IRAT Measurement Configuration IE description, subclause 11.3.115).

The element coding is:

Table 11.3.120: Source Cell ID IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2

Length Indicator

Octet 3-7

Tracking Area Identity

Octet 8-m

E-UTRAN CGI

Octet(m+1)-n

Global eNB ID

Tracking Area Identity: Octets 3 to 7 contain the value part of the Tracking Area Identity IE defined in 3GPP TS 24.301, not including 3GPP TS 24.301 IEI.

E-UTRAN CGI: Octets 8 – m contain the E-UTRAN CGI (see 3GPP TS 36.413 sub-clause 9.3.4, EUTRAN-CGI Sequence) for the source cell.

Global eNB ID: Octets (m+1)-n contain the Global eNB ID (see 3GPP TS 36.413 sub-clause 9.3.4, Global-ENB-ID Sequence) for the source eNB.

11.3.121 IRAT Measurement Configuration (extended E-ARFCNs)

The IRAT Measurement Configuration (extended E-ARFCNs) IE is used to indicate to the BSS which frequency measurement results of the source RAT shall be collected after a successful inter-system handover. The IRAT Measurement Configuration IE is used by the source RAT to specify the E-UTRA frequencies for which the corresponding E-ARFCN is greater than 65535 to be reported back to the source RAT (each of them associated with a measurement bandwidth), the minimum radio quality and the period of time that the measurements should last before triggering a HO Report for unnecessary handover to another RAT.

NOTE 1: HO Report is defined in 3GPP TS 36.413 [36].

NOTE 2: The functionality of Unnecessary IRAT HO is described in 3GPP TS 36.300 [45].

The element coding is:

Table 11.3.121: IRAT Measurement Configuration (extended E-ARFCN) IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2

Length Indicator

Octet 3

Spare

REP_QUANT

REPORTING_THRESHOLD

Octet 4

Measurement _Duration

Octets 5-6

E-ARFCN

Octet 7

E-ARFCN

Spare

Measurement Bandwidth

Octets 8-9

E-ARFCN

Octet 10

E-ARFCN

Spare

Measurement Bandwidth

“

“

Octets m-(m+1)

E-ARFCN

Octet m+2

E-ARFCN

Spare

Measurement Bandwidth

REPORTING_THRESHOLD: see subclause 11.3.115.

REP_QUANT: see subclause 11.3.115.

Measurement _Duration: see subclause 11.3.115.

E- ARFCN: designates a specific E-UTRA frequency for which the target RAT should continue to collect the measurement results received from MS of this frequency. It is coded as a number in binary representation ranging from 65536 to 262143 in which bit 8 octet m is the most significant bit while bit 7 octet (m+2) is the least significant bit.

Measurement Bandwidth: see subclause 11.3.115.

11.3.122 eDRX Parameters

This information element is used to indicate the eDRX cycle value the BSS is to use for determining the reachability of a MS that has enabled eDRX operation. The element coding is:

Table 11.3.122: eDRX Parameters IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Spare

eDRX Cycle Value

The BSS uses the eDRX cycle value indicated by the eDRX Parameters IE along with the IMSI to determine the nominal paging group of a mobile station (see 3GPP TS 45.002 [48]). The eDRX cycle value is coded as specified within 3GPP TS 24.008 [11]).

11.3.123 Time Until Next Paging Occasion

This information element is used to indicate the time until the next paging occasion for a MS for which the BSS has rejected a PS-PAGING PDU received from the SGSN. The element coding is:

Table 11.3.123: Time Until Next Paging Occasion IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Spare

Minutes

octet 4

Spare

Seconds

The BSS uses information provided by the PAGING-PS PDU to calculate the time until the next paging occasion in minutes and seconds and includes it within this IE.

The “Minutes” field is coded as shown below.

Table 11.3.123.a: "Minutes" coding

coding

semantic

000000

0 minutes

000001

1 minute

000010

2 minutes

000011

3 minutes

….

110100

52 minutes

All other values are reserved.

The “Seconds” field is coded as shown below.

Table 11.3.123.b: "Seconds" coding

coding

semantic

0000 0000

0 seconds

0000 0001

1 second

0000 0010

2 seconds

0000 0011

3 seconds

….

0011 1011

59 seconds

All other values are reserved.

11.3.124 Coverage Class

This information element is used to indicate the uplink and downlink Coverage Class associated with a given MS supporting EC operation. The element coding is:

Table 11.3.124.a: Coverage Class IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

spare

DL Coverage Class

UL Coverage Class

UL Coverage Class: Octet 3, bits 1 to 3, contain the value part of the uplink Coverage Class.
DL Coverage Class: Octet 3, bits 4 to 6, contain the value part of the downlink Coverage Class.

The UL Coverage Class field is coded as shown below:

Table 11.3.124.b: UL Coverage Class field

Coding

Semantic

000

reserved

001

UL Coverage Class 1

010

UL Coverage Class 2

011

UL Coverage Class 3

100

UL Coverage Class 4

101

UL Coverage Class 5

All other values are reserved.

The DL Coverage Class field is coded as shown below:

Table 11.3.124.c: DL Coverage Class field

Coding

Semantic

000

reserved

001

DL Coverage Class 1

010

DL Coverage Class 2

011

DL Coverage Class 3

100

DL Coverage Class 4

All other values are reserved.

Spare bits are reserved and coded with zeroes.

11.3.125 Paging Attempt Information

This information element provides the BSS with paging attempt count and intended number of paging attempts information for a given paging procedure for an MS.
The element coding is:

Table 11.3.125.a: Paging Attempt Information IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

PEI

Intended Number of Paging Attempts

Paging Attempt Count

The Paging Attempt Count field is coded as shown below:

Table 11.3.125.b: Paging Attempt Count field

Coding

Semantic

000

1st paging attempt

001

2nd paging attempt

010

3rd paging attempt

011

4th paging attempt

100

5th paging attempt

101

6th paging attempt

110

7th paging attempt

111

8th paging attempt

The Intended Number of Paging Attempts field is coded as shown below:

Table 11.3.125.c: Intended Number of Paging Attempts field

Coding

Semantic

0000

Information not available

0001

1 page attempt

0010

2 page attempts

0011

3 page attempts

0100

4 page attempts

0101

5 page attempts

0110

6 page attempts

0111

7 page attempts

1000

8 page attempts

All other values are reserved

The PEI (Positioning Event Indicator) field is coded as shown below:

Table 11.3.125.d: "PEI" coding

coding

Semantic

0

Positioning event not triggered

1

Positioning event triggered

11.3.126 Exception Report Flag

This information element is included if the LLC PDU carried within the UL-UNITDATA PDU was sent by the MS using an uplink EC TBF established in response to an EC PACKET CHANNEL REQUEST message or an EC PACKET DOWNLINK ACK/NACK message including a channel request, indicating high priority (i.e. an exception report), see 3GPP TS 44.018 [25] and 3GPP TS 44.060 [22].

The element coding is:

Table 11.3.126a: Exception Report Flag IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

Spare

11.3.127 Old Routing Area Identification

This information element provides the BSS with the Old Routing Area Identification (RAI) as reported by the MS in the intitial Layer 3 message. It is used in MOCN and GWCN configurations for network sharing.

The element coding is:

Table 11.3.127: Old Routing Area Identification 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 24.008, not including 3GPP TS 24.008 IEI

11.3.128 Attach Indicator

This information element provides the BSS with the information of an ongoing GPRS attach for a given mobile station. It is used in MOCN and GWCN configurations for network sharing.

The element coding is:

Table 11.3.128: Attach Indicator IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

spare

11.3.129 PLMN Identity

The purpose of the PLMN Identity information element is to identify a given CN operator. It is used in MOCN and GWCN configurations for network sharing.

The element coding is:

Table 11.3.129: PLMN Identity IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

MCC dig 2

MCC dig 1

octet 4

MNC dig 3

MCC dig 3

octet 5

MNC dig 2

MNC dig 1

The MCC and MNC value fields are coded as specified within 3GPP TS 24.008 [11].

11.3.130 MME Query

This information element provides control information for the MS Registration Enquiry procedure. The purpose of the MME Query IE is to request the SGSN to send a registration information enquiry to each MME that may hold the context for a given MS. It is used in MOCN and GWCN configurations for network sharing.

The element coding is:

Table 11.3.130: MME Query IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2, 2a

Length Indicator

octet 3

spare

11.3.131 SGSN Group Identity

This information element provides the BSS with the DCN related information within the PLMN for identification of CN node as described in 23.401 [49].

The element coding is:

Table 11.3.131.a: SGSN Group Identity IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2

Length Indicator

Octet 3

Choice bits for type of SGSN Group Identity

Octet 4-5

Null-NRI/SGSN Group ID

The Choice bit field is coded as shown below:

Table 11.3.131.b: Choice bits for type of SGSN Group Identity field

Coding

Semantic

00000000

Octets 4-5 contain the Null-NRI

00000001

Octets 4-5 contain the SGSN Group ID

All other values are reserved

Null-NRI: The 10 most significant bits of Octets 4 to 5 contain the Null-NRI, the remaining bits are spare.

SGSN Group ID: Octets 4-5 contain the SGSN Group ID and is coded as specified in 3GPP TS 23.401 [49].

11.3.132 Additional P-TMSI

This information element provides the BSS with the Additional P-TMSI.

The element coding is:

Table 11.3.132: Additional P-TMSI IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2

Length Indicator

Octet 3-6

Additional P-TMSI

Additional P-TMSI: Octets 3-6 contain the Additional P-TMSI, see 3GPP TS 24.008 [11]

11.3.133 UE Usage Type

This information element provides the BSS with the UE Usage Type.

The element coding is:

Table 11.3.133: UE Usage Type IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2

Length Indicator

Octet 3

UE Usage Type

UE Usage Type: Octet 3 contains the UE Usage Type.

11.3.134 DCN-ID

This information element provides the SGSN with the DCN-ID, see 3GPP TS 23.401 [49] and 3GPP TS 44.060 [22].

The element coding is:

Table 11.3.133: DCN-ID IE

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2

Length Indicator

Octet 3

DCN-ID (Octet 1)

Octet 4

DCN-ID (Octet 2)

DCN-ID: Octet 3 and 4 contains the DCN-ID and is coded as the DCN-ID field in 3GPP TS 44.060 [22].

11.3.135 Void

11.3.136 Multilateration Timer

The inclusion of this information element indicates the MTA procedure or MOTD procedure has been triggered and provides the specific timer value used by the BSS for that procedure. The element coding is:

Table 11.3.136: Multilateration Timer IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2

Length Indicator

octet 3

Spare

MPM Timer

The fields are coded as follows:

MPM Timer (bits 1, 2 and 3 of octet 3): This field is coded according to the value part of the of the MPM Timer field defined in 3GPP TS 49.031 [24].

Spare: these bits shall be ignored by the receiver and set to zero by the sender.

11.3.137 Multilateration Timing Advance

This parameter identifies the Multilateration Timing Advance value the BSS determines to be applicable for a MS at the point when it receives a corresponding RLC Data Block containing a page response, a “MS Transmission Offset” parameter and a “MS Sync Accuracy” parameter (see 3GPP TS 44.060 [22]).

Table 11.3.137: Multilateration Timing Advance IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2

Length Indicator

octet 3

spare

MTA Granularity

MTA Low

octet 4

MTA High

The MTA Granularity and MTA fields are coded according to the value parts of the Multilateration Timing Advance information element described in 3GPP TS 49.031 [24] (i.e. not including 3GPP TS 49.031 IEI)

11.3.138 MS Sync Accuracy

This parameter identifies the downlink synchronization accuracy the MS determines to be applicable at the point of sending the RLC Data Block containing a page response, a “MS Transmission Offset” parameter and the “MS Sync Accuracy” parameter (see 3GPP TS 44.060 [22]).

Table 11.3.138: MS Sync Accuracy IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2

Length Indicator

octet 3

spare

MS Sync Accuracy

The MS Sync Accuracy field is coded according to the value part of the MS Sync Accuracy information element described in 3GPP TS 49.031 [24] (i.e. not including 3GPP TS 49.031 IEI).

11.3.139 BTS Reception Accuracy Level

This parameter identifies the BTS Reception Accuracy Level the BSS determines to be applicable at the point when it receives a RLC Data Block containing a page response, a “MS Transmission Offset” parameter and a “MS Sync Accuracy” parameter (see 3GPP TS 44.060 [22]).

Table 11.3.139: BTS Reception Accuracy Level IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2

Length Indicator

octet 3

spare

BTS Reception Accuracy Level

The BTS Reception Accuracy Level field is coded according to the value part of the BTS Reception Accuracy Level information element described in 3GPP TS 49.031 [24] (i.e. not including 3GPP TS 49.031 IEI).

11.3.140 Timing Advance Request (TAR)

This parameter indicates whether or not MS specific timing advance information (“MS Transmission Offset” and “MS Sync Accuracy” parameters – see 3GPP TS 44.060 [22]) needs to be aquired.

Table 11.3.140.1: Timing Advance Request IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2

Length Indicator

octet 3

spare

TAR

The TAR field is coded as shown below and has a value determined by the SMLC when it triggers the Multilateration Timing Advance procedure or the MOTD procedure (see 3GPP TS 49.031 [24]):

Table 11.3.140.2: "TAR" coding

coding

Semantic

0

Timing Advance information not needed

1

Timing Advance information needed

11.3.141 Enhanced Coverage Additional Information

This information element provides the BSS with the Enhanced Coverage Additional Information.

The element coding is:

Table 11.3.141.a: Enhanced Coverage Additional Information

8

7

6

5

4

3

2

1

Octet 1

IEI

Octet 2

Length Indicator

Octet 3

Spare

ECRR

The Enhanced Coverage Restriction Removed (ECRR) field is coded as shown below:

Table 11.3.141.b: ECRR field

Coding

Semantic

0

Restriction on use of enhanced coverage

1

No restriction on use of enhanced coverage

11.3.142 MTA Access Security Required(MTASR)

This parameter indicates SGSN request to MS to provide MTA Signature.

Table 11.3.142.1: MTA Access Security Required IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2

Length Indicator

octet 3

spare

MTASR

The MTASR field is coded as shown below and has a value determined by the SGSN.

Table 11.3.142.2: "MTASR" coding

coding

Semantic

0 0

MTA Access Security not required

0 1

MTA Access Security Method requested

1 0

BSS Duplication Detection method requested

1 1

spare

11.3.143 MTA Sequence

This parameter is provided by BSS to SGSN. The BSS obtains this parameter from SMLC.

Table 11.3.143.1: MTA Sequence IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2

Length Indicator

octet 3

MTA Sequence (octet 1)

octet 4

MTA Sequence (octet 2)

octet 5

MTA Sequence (octet 3)

octet 6

MTA Sequence (octet 4)

octet 7

MTA Sequence (octet 5)

octet n

MTA Sequence (octet n-2)

11.3.144 MTA Signature

This parameter is provided by BSS to SGSN. BSS obtains this parameter from SMLC.

Table 11.3.144.1: MTA Signature IE

8

7

6

5

4

3

2

1

octet 1

IEI

octet 2

Length Indicator

octet 3

MTA Signature (octet 1)

octet 4

MTA Signature (octet 2)

octet 5

MTA Signature (octet 3)

octet 6

MTA Signature (octet 4)