9.9.4 EPS Session Management (ESM) information elements

24.3013GPPNon-Access-Stratum (NAS) protocol for Evolved Packet System (EPS)Release 18Stage 3TS

9.9.4.1 Access point name

See clause 10.5.6.1 in 3GPP TS 24.008 [13].

9.9.4.2 APN aggregate maximum bit rate

The purpose of the APN aggregate maximum bit rate information element is to indicate the initial subscribed APN-AMBR when the UE establishes a PDN connection or to indicate the new APN-AMBR if it is changed by the network.

The APN aggregate maximum bit rate information element is coded as shown in figure 9.9.4.2.1 and table 9.9.4.2.1.

The APN aggregate maximum bit rate is a type 4 information element with a minimum length of 4 octets and a maximum length of 8 octets. Octets 5-8 are optional. If octet 5 is included, then octet 6 shall also be included, and octets 7-8 may be included. If octet 7 is included, then octet 8 shall also be included. The length of the APN-AMBR IE can be either 4 octets, 6 octets or 8 octets.

8

7

6

5

4

3

2

1

APN aggregate maximum bit rate IEI

octet 1

Length of APN aggregate maximum bit rate contents

octet 2

APN-AMBR for downlink

octet 3

APN-AMBR for uplink

octet 4

APN-AMBR for downlink (extended)

octet 5*

APN-AMBR for uplink (extended)

octet 6*

APN-AMBR for downlink (extended-2)

octet 7*

APN-AMBR for uplink (extended-2)

octet 8*

Figure 9.9.4.2.1: APN aggregate maximum bit rate information element

Table 9.9.4.2.1: APN aggregate maximum bit rate information element

APN-AMBR for downlink, 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 The APN-AMBR is binary coded in 8 bits, using a granularity of 1 kbps
to giving a range of values from 1 kbps to 63 kbps in 1 kbps increments.
0 0 1 1 1 1 1 1

0 1 0 0 0 0 0 0 The APN-AMBR is 64 kbps + ((the binary coded value in 8 bits –01000000) * 8 kbps)
to giving a range of values from 64 kbps to 568 kbps in 8 kbps increments.
0 1 1 1 1 1 1 1

1 0 0 0 0 0 0 0 The APN-AMBR is 576 kbps + ((the binary coded value in 8 bits –10000000) * 64 kbps)
to giving a range of values from 576 kbps to 8640 kbps in 64 kbps increments.
1 1 1 1 1 1 1 0

1 1 1 1 1 1 1 1 0kbps

If the network wants to indicate an APN-AMBR for downlink higher than 8640 kbps, it shall set octet 3 to "11111110", i.e. 8640 kbps, and shall encode the value for the APN-AMBR in octet 5.

APN-AMBR for uplink, octet 4

Coding is identical to that of APN-AMBR for downlink.

APN-AMBR for downlink (extended), octet 5

Bits

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 0 Use the value indicated by the APN-AMBR for downlink in octet 3.

For all other values: Ignore the value indicated by the APN-AMBR for downlink in octet 3
and use the following value:
0 0 0 0 0 0 0 1 The APN-AMBR is 8600 kbps + ((the binary coded value in 8 bits) * 100 kbps),
to giving a range of values from 8700 kbps to 16000 kbps in 100 kbps increments.
0 1 0 0 1 0 1 0

0 1 0 0 1 0 1 1 The APN-AMBR is 16 Mbps + ((the binary coded value in 8 bits – 01001010) * 1 Mbps),
to giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments.
1 0 1 1 1 0 1 0

1 0 1 1 1 0 1 1 The APN-AMBR is 128 Mbps + ((the binary coded value in 8 bits – 10111010) * 2 Mbps),
to giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments.
1 1 1 1 1 0 1 0

All other values shall be interpreted as ‘1 1 1 1 1 0 1 0’

APN-AMBR for uplink (extended), octet 6

This field is an extension of the APN-AMBR for uplink in octet 4. The coding is identical to that of the APN-AMBR for downlink (extended).

APN-AMBR for downlink (extended-2), octet 7

Bits

8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 Use the value indicated by the APN-AMBR for downlink and APN-AMBR for downlink (extended) in
octets 3 and 5.

0 0 0 0 0 0 0 1 The APN-AMBR is (the binary coded value in 8 bits) * 256 Mbps + (the value indicated by

to the APN-AMBR for downlink and APN-AMBR for downlink (extended) in octets 3 and 5),

1 1 1 1 1 1 1 0 giving a range of 264.64 Mbps to 65280 Mbps.

1 1 1 1 1 1 1 1 This value shall be interpreted as ‘0 0 0 0 0 0 0 0’ in this version of the specification.

If the network wants to indicate an APN-AMBR value for downlink higher than 65280 Mbps, it shall set octet 5 to "11111010" and octet 7 to "11111110", i.e. 65280 Mbps, and shall encode the higher value for the APN-AMBR in the extended APN aggregate maximum bit rate information element specified in clause 9.9.4.29.

APN-AMBR for uplink (extended-2), octet 8

This field is an extension of the APN-AMBR for uplink and APN-AMBR for uplink (extended) in octets 4 and 6. The coding is identical to that of the APN-AMBR for downlink (extended-2).

If the UE or the network wants to indicate an APN-AMBR value for uplink higher than 65280 Mbps, it shall set octet 8 to "11111110", i.e. 65280 Mbps, and shall encode the higher value for the APN-AMBR in the extended APN aggregate maximum bit rate information element specified in clause 9.9.4.29.

9.9.4.2A Connectivity type

See clause 10.5.6.19 in 3GPP TS 24.008 [13].

9.9.4.3 EPS quality of service

The purpose of the EPS quality of service information element is to specify the QoS parameters for an EPS bearer context.

The EPS quality of service information element is coded as shown in figure 9.9.4.3.1 and table 9.9.4.3.1.

The EPS quality of service is a type 4 information element with a minimum length of 3 octets and a maximum length of 15 octets. Octets 4-15 are optional. If octet 4 is included, then octets 5-7 shall also be included, and octets 8-15 may be included. If octet 8 is included, then octets 4-11 shall also be included, and octets 12-15 may be included. If octet 12 is included, then octets 4-15 shall also be included. The length of the EPS QoS IE can be either 3 octets, 7 octets, 11 octets or 15 octets.

Refer to 3GPP TS 23.203 [7] for a detailed description of the QoS Class Identifier (QCI).

8

7

6

5

4

3

2

1

EPS quality of service IEI

octet 1

Length of EPS quality of service contents

octet 2

QCI

octet 3

Maximum bit rate for uplink

octet 4*

Maximum bit rate for downlink

octet 5*

Guaranteed bit rate for uplink

octet 6*

Guaranteed bit rate for downlink

octet 7*

Maximum bit rate for uplink (extended)

octet 8*

Maximum bit rate for downlink (extended)

octet 9*

Guaranteed bit rate for uplink (extended)

octet 10*

Guaranteed bit rate for downlink (extended)

octet 11*

Maximum bit rate for uplink (extended-2)

octet 12*

Maximum bit rate for downlink (extended-2)

octet 13*

Guaranteed bit rate for uplink (extended-2)

octet 14*

Guaranteed bit rate for downlink (extended-2)

octet 15*

Figure 9.9.4.3.1: EPS quality of service information element

Table 9.9.4.3.1: EPS quality of service information element

Quality of Service Class Identifier (QCI), octet 3 (see 3GPP TS 23.203 [7] and 3GPP TS 29.212 [16B])

Bits

8 7 6 5 4 3 2 1

In UE to network direction:

0 0 0 0 0 0 0 0 no QCI requested (NOTE)

In network to UE direction:

0 0 0 0 0 0 0 0 Reserved

In UE to network direction and in network to UE direction:

0 0 0 0 0 0 0 1 QCI 1

0 0 0 0 0 0 1 0 QCI 2

0 0 0 0 0 0 1 1 QCI 3

0 0 0 0 0 1 0 0 QCI 4

0 0 0 0 0 1 0 1 QCI 5

0 0 0 0 0 1 1 0 QCI 6

0 0 0 0 0 1 1 1 QCI 7

0 0 0 0 1 0 0 0 QCI 8

0 0 0 0 1 0 0 1 QCI 9

0 0 0 0 1 0 1 0 QCI 10

0 0 0 0 1 0 1 1

to Spare

0 1 0 0 0 0 0 0

0 1 0 0 0 0 0 1 QCI 65

0 1 0 0 0 0 1 0 QCI 66

0 1 0 0 0 0 1 1 QCI 67

0 1 0 0 0 1 0 0

to Spare

0 1 0 0 0 1 0 0

0 1 0 0 0 1 0 1 QCI 69

0 1 0 0 0 1 1 0 QCI 70

0 1 0 0 0 1 1 1 QCI 71

0 1 0 0 1 0 0 0 QCI 72

0 1 0 0 1 0 0 1 QCI 73

0 1 0 0 1 0 1 0 QCI 74

0 1 0 0 1 0 1 1 QCI 75

0 1 0 0 1 1 0 0 QCI 76

0 1 0 0 1 1 0 0

to Spare

0 1 0 0 1 1 1 0

0 1 0 0 1 1 1 1 QCI 79

0 1 0 1 0 0 0 0 QCI 80

0 1 0 1 0 0 0 1 Spare

0 1 0 1 0 0 1 0 QCI 82

0 1 0 1 0 0 1 1 QCI 83

0 1 0 1 0 1 0 0 QCI 84

0 1 0 1 0 1 0 1 QCI 85

0 1 0 1 0 1 1 0

to Spare

0 1 1 1 1 1 1 1

1 0 0 0 0 0 0 0

to Operator-specific QCIs

1 1 1 1 1 1 1 0

1 1 1 1 1 1 1 1 Reserved

The network shall consider all other values not explicitly defined in this version of the protocol as unsupported.

NOTE: The UE shall use this value, if the information element has presence requirement "M" in a message, but the information element does not serve any useful purpose in the specific procedure for which the message is sent (see clause 6.5.3.2).

QCI values 10-127 were reserved in earlier versions of the protocol.

If the UE receives a QCI value (excluding the reserved QCI values) that it does not understand, the UE shall choose a QCI value from the set of QCI values defined in this version of the protocol (see 3GPP TS 23.203 [7] and 3GPP TS 29.212 [16B]) and associated with:

– GBR bearers if the IE includes a guaranteed bit rate value and a maximum bit rate value; and

– non-GBR bearers if the IE does not include any one of a guaranteed bit rate value or a maximum bit rate value.

The UE shall use this chosen QCI value for internal operations only. The UE shall use the received QCI value in subsequent NAS signalling procedures.

For all non-GBR QCIs, the maximum and guaranteed bit rates shall be ignored.

Maximum bit rate for uplink, octet 4 (see 3GPP TS 23.107 [5])

Bits

8 7 6 5 4 3 2 1

In UE to network direction:
0 0 0 0 0 0 0 0 Subscribed maximum bit rate for uplink

In network to UE direction:
0 0 0 0 0 0 0 0 Reserved

In UE to network direction and in network to UE direction:

0 0 0 0 0 0 0 1 The maximum bit rate is binary coded in 8 bits, using a granularity of 1 kbps
to giving a range of values from 1 kbps to 63 kbps in 1 kbps increments.

0 0 1 1 1 1 1 1

0 1 0 0 0 0 0 0 The maximum bit rate is 64 kbps + ((the binary coded value in 8 bits – 01000000) * 8 kbps)
to giving a range of values from 64 kbps to 568 kbps in 8 kbps increments.

0 1 1 1 1 1 1 1

1 0 0 0 0 0 0 0 The maximum bit rate is 576 kbps + ((the binary coded value in 8 bits – 10000000) * 64 kbps)
to giving a range of values from 576 kbps to 8640 kbps in 64 kbps increments.
1 1 1 1 1 1 1 0

1 1 1 1 1 1 1 1 0kbps

If the sending entity wants to indicate a maximum bit rate for uplink higher than 8640 kbps, it shall set octet 4 to "11111110", i.e. 8640 kbps, and shall encode the value for the maximum bit rate in octet 8.

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

Maximum bit rate for downlink, octet 5 (see 3GPP TS 23.107 [5])

Coding is identical to that of maximum bit rate for uplink.

If the sending entity wants to indicate a maximum bit rate for downlink higher than 8640 kbps, it shall set octet 5 to "11111110", i.e. 8640 kbps, and shall encode the value for the maximum bit rate in octet 9.

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

In this version of the protocol, for messages specified in the present document, the sending entity shall not request 0 kbps for both the maximum bit rate for downlink and the maximum bit rate for uplink at the same time. Any entity receiving a request for 0 kbps in both the maximum bit rate for downlink and the maximum bit rate for uplink shall consider that as a syntactical error (see clause 8 of 3GPP TS 24.008 [13]).

Guaranteed bit rate for uplink, octet 6 (see 3GPP TS 23.107 [5])

Coding is identical to that of maximum bit rate for uplink.

If the sending entity wants to indicate a guaranteed bit rate for uplink higher than 8640 kbps, it shall set octet 6 to "11111110", i.e. 8640 kbps, and shall encode the value for the guaranteed bit rate in octet 10.

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

Guaranteed bit rate for downlink, octet 7 (see 3GPP TS 23.107 [5])

Coding is identical to that of maximum bit rate for uplink.

If the sending entity wants to indicate a guaranteed bit rate for downlink higher than 8640 kbps, it shall set octet 7 to "11111110", i.e. 8640 kbps, and shall encode the value for the guaranteed bit rate in octet 11.

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

Maximum bit rate for uplink (extended), octet 8

Bits
8 7 6 5 4 3 2 1

In UE to network direction and in network to UE direction:
0 0 0 0 0 0 0 0 Use the value indicated by the maximum bit rate for uplink in octet 4.

For all other values: ignore the value indicated by the maximum bit rate for uplink in octet 4
and use the following value:
0 0 0 0 0 0 0 1 The maximum bit rate is 8600 kbps + ((the binary coded value in 8 bits) * 100 kbps),
to giving a range of values from 8700 kbps to 16000 kbps in 100 kbps increments.
0 1 0 0 1 0 1 0

0 1 0 0 1 0 1 1 The maximum bit rate is 16 Mbps + ((the binary coded value in 8 bits – 01001010) * 1 Mbps),
to giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments.
1 0 1 1 1 0 1 0

1 0 1 1 1 0 1 1 The maximum bit rate is 128 Mbps + ((the binary coded value in 8 bits – 10111010) * 2 Mbps),
to giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments.
1 1 1 1 1 0 1 0

If the sending entity wants to indicate a Maximum bit rate for uplink higher than 256 Mbps, it shall set octet 8 to "11111010", i.e. 256 Mbps, and shall encode the value for the Maximum bit rate in octet 12.

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

Maximum bit rate for downlink (extended), octet 9

This field is an extension of the maximum bit rate for downlink in octet 5. The coding is identical to that of the maximum bit rate for uplink (extended).

If the sending entity wants to indicate a Maximum bit rate for downlink higher than 256 Mbps, it shall set octet 9 to "11111010", i.e. 256 Mbps, and shall encode the value for the Maximum bit rate in octet 13.

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

Guaranteed bit rate for uplink (extended), octet 10

Bits
8 7 6 5 4 3 2 1

In UE to network direction and in network to UE direction:

0 0 0 0 0 0 0 0 Use the value indicated by the guaranteed bit rate for uplink in octet 6.

For all other values: ignore the value indicated by the guaranteed bit rate for uplink in octet 6
and use the following value:
0 0 0 0 0 0 0 1 The guaranteed bit rate is 8600 kbps + ((the binary coded value in 8 bits) * 100 kbps),
to giving a range of values from 8700 kbps to 16000 kbps in 100 kbps increments.
0 1 0 0 1 0 1 0

0 1 0 0 1 0 1 1 The guaranteed bit rate is 16 Mbps + ((the binary coded value in 8 bits – 01001010) * 1 Mbps),
to giving a range of values from 17 Mbps to 128 Mbps in 1 Mbps increments.
1 0 1 1 1 0 1 0

1 0 1 1 1 0 1 1 The guaranteed bit rate is 128 Mbps + ((the binary coded value in 8 bits – 10111010) * 2 Mbps),
to giving a range of values from 130 Mbps to 256 Mbps in 2 Mbps increments.
1 1 1 1 1 0 1 0

If the sending entity wants to indicate a Guaranteed bit rate for uplink higher than 256 Mbps, it shall set octet 10 to "11111010", i.e. 256 Mbps, and shall encode the value for the Maximum bit rate in octet 14.

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

Guaranteed bit rate for downlink (extended), octet 11

This field is an extension of the guaranteed bit rate for downlink in octet 7. The coding is identical to that of guaranteed bit rate for uplink (extended).

If the sending entity wants to indicate a Guaranteed bit rate for downlink higher than 256 Mbps, it shall set octet 11 to "11111010", i.e. 256 Mbps, and shall encode the value for the Maximum bit rate in octet 15.

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

Maximum bit rate for uplink (extended-2), octet 12

Bits

8 7 6 5 4 3 2 1

In UE to network direction and in network to UE direction:

0 0 0 0 0 0 0 0 Use the value indicated by the Maximum bit rate for uplink in octet 4 and octet 8.

For all other values: Ignore the value indicated by the Maximum bit rate for uplink in octet 4 and

octet 8 and use the following value:

0 0 0 0 0 0 0 1 The maximum bit rate is 256 Mbps + ((the binary coded value in 8 bits) * 4 Mbps),

0 0 1 1 1 1 0 1 giving a range of values from 260 Mbps to 500 Mbps in 4 Mbps increments.

0 0 1 1 1 1 1 0 The maximum bit rate is 500 Mbps + ((the binary coded value in 8 bits – 00111101) * 10 Mbps),

1 0 1 0 0 0 0 1 giving a range of values from 510 Mbps to 1500 Mbps in 10 Mbps increments.

1 0 1 0 0 0 1 0 The maximum bit rate is 1500 Mbps + ((the binary coded value in 8 bits – 10100001) * 100 Mbps),

1 1 1 1 0 1 1 0 giving a range of values from 1600 Mbps to 10 Gbps in 100 Mbps increments.

If the sending entity wants to indicate a Maximum bit rate for uplink higher than 10 Gbps, it shall set octet 12 to "11110110", i.e. 10 Gbps, and shall encode the value for the maximum bit rate in the Extended quality of service information element specified in clause 9.9.4.30.

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

The UE shall map all other values not explicitly defined onto the maximum value defined in this version of the protocol.

Maximum bit rate for downlink (extended-2), octet 13

This field is an extension of the Maximum bit rate for downlink in octet 9. The coding is identical to that of the Maximum bit rate for uplink (extended-2).

If the sending entity wants to indicate a Maximum bit rate for downlink higher than 10 Gbps, it shall set octet 13 to "11110110", i.e. 10 Gbps, and shall encode the value for the maximum bit rate in the Extended quality of service information element specified in clause 9.9.4.30.

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

The UE shall map all other values not explicitly defined onto the maximum value defined in this version of the protocol.

Guaranteed bit rate for uplink (extended-2), octet 14

Bits

8 7 6 5 4 3 2 1

In UE to network direction and in network to UE direction:

0 0 0 0 0 0 0 0 Use the value indicated by the Guaranteed bit rate for uplink in octet 6 and octet 10.

For all other values: Ignore the value indicated by the Guaranteed bit rate for uplink in octet 6 and

octet 10 and use the following value:

0 0 0 0 0 0 0 1 The guaranteed bit rate is 256 Mbps + ((the binary coded value in 8 bits) * 4 Mbps),

0 0 1 1 1 1 0 1 giving a range of values from 260 Mbps to 500 Mbps in 4 Mbps increments.

0 0 1 1 1 1 1 0 The guaranteed bit rate is 500 Mbps + ((the binary coded value in 8 bits – 00111101) * 10 Mbps),

1 0 1 0 0 0 0 1 giving a range of values from 510 Mbps to 1500 Mbps in 10 Mbps increments.

1 0 1 0 0 0 1 0 The guaranteed bit rate is 1500 Mbps + ((the binary coded value in 8 bits – 10100001) * 100 Mbps),

1 1 1 1 0 1 1 0 giving a range of values from 1600 Mbps to 10 Gbps in 100 Mbps increments.

If the sending entity wants to indicate a Guaranteed bit rate for uplink higher than 10 Gbps, it shall set octet 14 to "11110110", i.e. 10 Gbps, and shall encode the value for the guaranteed bit rate in the Extended quality of service information element specified in clause 9.9.4.30.

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

The UE shall map all other values not explicitly defined onto the maximum value defined in this version of the protocol.

Guaranteed bit rate for downlink (extended-2), octet 15

This field is an extension of the Guaranteed bit rate for downlink in octet 11. The coding is identical to that of the Guaranteed bit rate for uplink (extended-2).

If the sending entity wants to indicate a Guaranteed bit rate for downlink higher than 10 Gbps, it shall set octet 15 to "11110110", i.e. 10 Gbps, and shall encode the value for the guaranteed bit rate in the Extended quality of service information element specified in clause 9.9.4.30.

The network shall map all other values not explicitly defined onto one of the values defined in this version of the protocol. The network shall return a negotiated value which is explicitly defined in this version of the protocol.

The UE shall map all other values not explicitly defined onto the maximum value defined in this version of the protocol.

9.9.4.4 ESM cause

The purpose of the ESM cause information element is to indicate the reason why a session management request is rejected.

The ESM cause information element is coded as shown in figure 9.9.4.4.1 and table 9.9.4.4.1.

The ESM cause is a type 3 information element with 2 octets length.

8

7

6

5

4

3

2

1

ESM cause IEI

octet 1

Cause value

octet 2

Figure 9.9.4.4.1: ESM cause information element

Table 9.9.4.4.1: ESM cause information element

Cause value (octet 2)

Bits

8

7

6

5

4

3

2

1

0

0

0

0

1

0

0

0

Operator Determined Barring

0

0

0

1

1

0

1

0

Insufficient resources

0

0

0

1

1

0

1

1

Missing or unknown APN

0

0

0

1

1

1

0

0

Unknown PDN type

0

0

0

1

1

1

0

1

User authentication or authorization failed

0

0

0

1

1

1

1

0

Request rejected by Serving GW or PDN GW

0

0

0

1

1

1

1

1

Request rejected, unspecified

0

0

1

0

0

0

0

0

Service option not supported

0

0

1

0

0

0

0

1

Requested service option not subscribed

0

0

1

0

0

0

1

0

Service option temporarily out of order

0

0

1

0

0

0

1

1

PTI already in use

0

0

1

0

0

1

0

0

Regular deactivation

0

0

1

0

0

1

0

1

EPS QoS not accepted

0

0

1

0

0

1

1

0

Network failure

0

0

1

0

0

1

1

1

Reactivation requested

0

0

1

0

1

0

0

1

Semantic error in the TFT operation

0

0

1

0

1

0

1

0

Syntactical error in the TFT operation

0

0

1

0

1

0

1

1

Invalid EPS bearer identity

0

0

1

0

1

1

0

0

Semantic errors in packet filter(s)

0

0

1

0

1

1

0

1

Syntactical errors in packet filter(s)

0

0

1

0

1

1

1

0

Unused (see NOTE 2)

0

0

1

0

1

1

1

1

PTI mismatch

0

0

1

1

0

0

0

1

Last PDN disconnection not allowed

0

0

1

1

0

0

1

0

PDN type IPv4 only allowed

0

0

1

1

0

0

1

1

PDN type IPv6 only allowed

0

0

1

1

1

0

0

1

PDN type IPv4v6 only allowed

0

0

1

1

1

0

1

0

PDN type non IP only allowed

0

0

1

1

0

1

0

0

Single address bearers only allowed

0

0

1

1

0

1

0

1

ESM information not received

0

0

1

1

0

1

1

0

PDN connection does not exist

0

0

1

1

0

1

1

1

Multiple PDN connections for a given APN not allowed

0

0

1

1

1

0

0

0

Collision with network initiated request

0

0

1

1

1

0

1

1

Unsupported QCI value

0

0

1

1

1

1

0

0

Bearer handling not supported

0

0

1

1

1

1

0

1

PDN type Ethernet only allowed

0

1

0

0

0

0

0

1

Maximum number of EPS bearers reached

0

1

0

0

0

0

1

0

Requested APN not supported in current RAT and PLMN combination

0

1

0

1

0

0

0

1

Invalid PTI value

0

1

0

1

1

1

1

1

Semantically incorrect message

0

1

1

0

0

0

0

0

Invalid mandatory information

0

1

1

0

0

0

0

1

Message type non-existent or not implemented

0

1

1

0

0

0

1

0

Message type not compatible with the protocol state

0

1

1

0

0

0

1

1

Information element non-existent or not implemented

0

1

1

0

0

1

0

0

Conditional IE error

0

1

1

0

0

1

0

1

Message not compatible with the protocol state

0

1

1

0

1

1

1

1

Protocol error, unspecified

0

1

1

1

0

0

0

0

APN restriction value incompatible with active EPS bearer context

0

1

1

1

0

0

0

1

Multiple accesses to a PDN connection not allowed

Any other value received by the UE shall be treated as 0010 0010, "service option temporarily out of order". Any other value received by the network shall be treated as 0110 1111, "protocol error, unspecified".

NOTE 1: The listed cause values are defined in annex B.

NOTE 2: This value was allocated in earlier versions of this protocol, but there is no situation where this value can be used. If received by the network, it shall be treated as 0110 1111, "protocol error, unspecified".

9.9.4.5 ESM information transfer flag

The purpose of the ESM information transfer flag information element is to indicate whether ESM information, i.e. protocol configuration options or APN or both, is to be transferred security protected.

The ESM information transfer flag information element is coded as shown in figure 9.9.4.5.1 and table 9.9.4.5.1.

The ESM information transfer flag is a type 1 information element.

8

7

6

5

4

3

2

1

ESM information transfer flag IEI

0

0

0

EIT

value

octet 1

spare

Figure 9.9.4.5.1: ESM information transfer flag information element

Table 9.9.4.5.1: ESM information transfer flag information element

EIT (ESM information transfer)

Bit

1

0

security protected ESM information transfer not required

1

security protected ESM information transfer required

9.9.4.6 Linked EPS bearer identity

The purpose of the Linked EPS bearer identity IE is to identify the default bearer that is associated with a dedicated EPS bearer or to identify the EPS bearer (default or dedicated) with which one or more packet filters specified in a traffic flow aggregate are associated.

The Linked EPS bearer identity information element is coded as shown in figure 9.9.4.6.1 and table 9.9.4.6.1.

The Linked EPS bearer identity is a type 1 information element.

8

7

6

5

4

3

2

1

Linked EPS bearer identity IEI

Linked EPS bearer identity value

octet 1

Figure 9.9.4.6.1: Linked EPS bearer identity information element

Table 9.9.4.6.1: Linked EPS bearer identity information element

Linked EPS bearer identity (bits 1-4)

4

3

2

1

0

0

0

0

Reserved

0

0

0

1

EPS bearer identity value 1

0

0

1

0

EPS bearer identity value 2

0

0

1

1

EPS bearer identity value 3

0

1

0

0

EPS bearer identity value 4

0

1

0

1

EPS bearer identity value 5

0

1

1

0

EPS bearer identity value 6

0

1

1

1

EPS bearer identity value 7

1

0

0

0

EPS bearer identity value 8

1

0

0

1

EPS bearer identity value 9

1

0

1

0

EPS bearer identity value 10

1

0

1

1

EPS bearer identity value 11

1

1

0

0

EPS bearer identity value 12

1

1

0

1

EPS bearer identity value 13

1

1

1

0

EPS bearer identity value 14

1

1

1

1

EPS bearer identity value 15

9.9.4.7 LLC service access point identifier

See clause 10.5.6.9 in 3GPP TS 24.008 [13].

9.9.4.7A Notification indicator

The purpose of the Notification indicator information element is to inform the UE about an event which is relevant for the upper layer using an EPS bearer context or having requested a procedure transaction.

The Notification indicator information element is coded as shown in figure 9.9.4.7A.1 and table 9.9.4.7A.1.

The Notification indicator is a type 4 information element with 3 octets length.

8

7

6

5

4

3

2

1

Notification indicator IEI

octet 1

Length of notification indicator contents

octet 2

Notification indicator value

octet 3

Figure 9.9.4.7A.1: Notification indicator information element

Table 9.9.4.7A.1: Notification indicator information element

Notification indicator value (octet 3)

Bits

8

7

6

5

4

3

2

1

0

0

0

0

0

0

0

1

SRVCC handover cancelled, IMS session re-establishment required (see 3GPP TS 23.216 [8])

0

0

0

0

0

0

1

0

to

Unused, shall be ignored if received by the UE

0

1

1

1

1

1

1

1

All other values are reserved.

9.9.4.8 Packet flow identifier

See clause 10.5.6.11 in 3GPP TS 24.008 [13].

9.9.4.9 PDN address

The PDN address information element can assign an IPv4 address to the UE associated with a packet data network and provide the UE with an interface identifier to be used to build the IPv6 link local address.

The PDN address information element is coded as shown in figure 9.9.4.9.1 and table 9.9.4.9.1.

The PDN address is a type 4 information element with minimum length of 7 octets and a maximum length of 15 octets.

8

7

6

5

4

3

2

1

PDN address IEI

octet 1

Length of PDN address contents

octet 2

0

0

0

0

0

PDN type value

octet 3

spare

PDN address information

octet 4

octet 15

Figure 9.9.4.9.1: PDN address information element

Table 9.9.4.9.1: PDN address information element

PDN type value (octet 3)

Bits

3

2

1

0

0

1

IPv4

0

1

0

IPv6

0

1

1

IPv4v6

1

0

1

non IP

1

1

0

Ethernet

All other values are reserved.

Bit 4 to 8 of octet 3 are spare and shall be coded as zero.

PDN address information (octet 4 to 15)

If PDN type value indicates IPv4, the PDN address information in octet 4 to octet 7 contains an IPv4 address. Bit 8 of octet 4 represents the most significant bit of the IPv4 address and bit 1 of octet 7 the least significant bit.

If PDN type value indicates IPv6, the PDN address information in octet 4 to octet 11 contains an IPv6 interface identifier. Bit 8 of octet 4 represents the most significant bit of the IPv6 interface identifier and bit 1 of octet 11 the least significant bit.

If PDN type value indicates IPv4v6, the PDN address information in octet 4 to octet 15 contains an IPv6 interface identifier and an IPv4 address. Bit 8 of octet 4 represents the most significant bit of the IPv6 interface identifier and bit 1 of octet 11 the least significant bit. Bit 8 of octet 12 represents the most significant bit of the IPv4 address and bit 1 of octet 15 the least significant bit.

If PDN type value indicates IPv4 or IPv4v6 and DHCPv4 is to be used to allocate the IPv4 address, the IPv4 address shall be coded as 0.0.0.0.

If PDN type value indicates non IP, the PDN address information in octet 4 to octet 7 are spare and shall be coded as zero.

If PDN type value indicates Ethernet, the PDN address information in octet 4 to octet 7 are spare and shall be coded as zero.

9.9.4.10 PDN type

The purpose of the PDN type information element is to indicate:

– the IP version capability of the IP stack associated with the UE;

– non IP; or

– Ethernet.

The PDN type information element is coded as shown in figure 9.9.4.10.1 and table 9.9.4.10.1.

The PDN type is a type 1 information element.

8

7

6

5

4

3

2

1

PDN type IEI

0

Spare

PDN type value

octet 1

Figure 9.9.4.10.1: PDN type information element

Table 9.9.4.10.1: PDN type information element

PDN type value (octet 1)

Bits

3

2

1

0

0

1

IPv4

0

1

0

IPv6

0

1

1

IPv4v6

1

0

0

unused; shall be interpreted as "IPv6" if received by the network

1

0

1

non IP

1

1

0

Ethernet

All other values are reserved.

Bit 4 of octet 1 is spare and shall be coded as zero.

9.9.4.11 Protocol configuration options

See clause 10.5.6.3 in 3GPP TS 24.008 [13].

9.9.4.12 Quality of service

See clause 10.5.6.5 in 3GPP TS 24.008 [13].

9.9.4.13 Radio priority

See clause 10.5.7.2 in 3GPP TS 24.008 [13].

9.9.4.13A Re-attempt indicator

The purpose of the Re-attempt indicator information element is to indicate a condition under which the UE is allowed, in the current PLMN for the same APN, to re-attempt a session management procedure (see 3GPP TS 24.008 [13]) corresponding to the EPS session management procedure which was rejected by the network.

The Re-attempt indicator information element is coded as shown in figure 9.9.4.13A/3GPP TS 24.301 and table 9.9.4.13A/3GPP TS 24.301.

The Re-attempt indicator is a type 4 information element with a length of 3 octets.

8

7

6

5

4

3

2

1

Reattempt indicator IEI

octet 1

Length of Reattempt indicator contents

octet 2

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

0

Spare

EPLMNC value

RATC value

octet 3

Figure 9.9.4.13A: Re-attempt indicator information element

Table 9.9.4.13A: Re-attempt indicator information element

Re-attempt indicator

RATC (octet 3, bit 1)

0 UE is allowed to re-attempt the procedure in A/Gb mode or Iu mode or N1 mode

1 UE is not allowed to re-attempt the procedure in A/Gb mode or Iu mode or N1 mode

EPLMNC (octet 3, bit 2)

0 UE is allowed to re-attempt the procedure in an equivalent PLMN

1 UE is not allowed to re-attempt the procedure in an equivalent PLMN

Bits 3 to 8 of octet 3 are spare and shall be encoded as zero.

9.9.4.14 Request type

See clause 10.5.6.17 in 3GPP TS 24.008 [13].

9.9.4.15 Traffic flow aggregate description

The purpose of the Traffic flow aggregate description information element is to specify the aggregate of one of more packet filters and their related parameters and operations. The traffic flow aggregate description may contain the aggregate of packet filters for the downlink direction, the uplink direction or packet filters that apply for both directions. The packet filters determine the traffic mapping to EPS bearer contexts. The downlink packet filters shall be applied by the network, and the uplink packet filters shall be applied by the UE. A packet filter that applies for both directions shall be applied by the network as a downlink packet filter and by the UE as an uplink packet filter.

When the traffic flow aggregate description is used in the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure, it is associated to a particular procedure identified by a procedure transaction identity (PTI). Therefore, the UE shall release the traffic flow aggregate description when the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure is completed. The UE shall not include the packet filters of a particular traffic flow aggregate description in any other traffic flow aggregate description when multiple UE requested bearer resource allocation procedures and/or UE requested bearer resource modification procedures are ongoing in parallel.

The Traffic flow aggregate description information element is encoded using the same format as the Traffic flow template (TFT) information element (see clause 10.5.6.12 in 3GPP TS 24.008 [13]). When sending this IE in the BEARER RESOURCE ALLOCATION REQUEST message or the BEARER RESOURCE MODIFICATION REQUEST message, the UE shall set the packet filter identifier values to 0 if the packet filters are newly created; otherwise, the UE shall set the packet filter identifier values from those of already assigned packet filter identifiers of the existing EPS bearer, so that they are unique across all packet filters for the EPS bearer context indicated by the EPS bearer identity IE.

9.9.4.16 Traffic flow template

See clause 10.5.6.12 in 3GPP TS 24.008 [13].

9.9.4.17 Transaction identifier

The purpose of the Transaction identifier information element is to represent the corresponding PDP context in A/Gb mode or Iu mode which is mapped from the EPS bearer context.

The Transaction identifier information element is coded as the Linked TI information element in 3GPP TS 24.008 [13], clause 10.5.6.7.

9.9.4.18 WLAN offload acceptability

See clause 10.5.6.20 in 3GPP TS 24.008 [13].

9.9.4.19 NBIFOM container

See clause 10.5.6.21 in 3GPP TS 24.008 [4].

9.9.4.20 Remote UE context list

The purpose of the Remote UE context list information element is to provide identity and optionally IP address of a remote UE connected to, or disconnected from, a UE acting as a ProSe UE-to-network relay.

The Remote UE context list information element is coded as shown in figure 9.9.4.20.1 and table 9.9.4.20.1.

The Remote UE context list is a type 6 information element with a minimum length of 5 octets and a maximum length of 65538 octets.

8

7

6

5

4

3

2

1

Remote UE context list IEI

octet 1

Length of remote UE context list contents

octet 2 to 3

Number of remote UE contexts

octet 4

Remote UE context 1

octet 5 to a

…

Remote UE context k

octet b

octet m

Figure 9.9.4.20.1: Remote UE context list

Table 9.9.4.20.1: Remote UE context list

Remote UE context (octet 5 etc)

The contents of remote UE context are applicable for one individual UE and are coded as shown in figure 9.9.4.20.2 and table 9.9.4.20.2.

8

7

6

5

4

3

2

1

Length of remote UE context

octet 1

Number of user identities

octet 2

Length of user identity 1

octet 3

User identity 1 digit 1

odd/

even

indic

Type of user identity 1

octet 4

User identity 1 digit p+1

User identity 1 digit p

octet 5*

…

Length of user identity v

octet m

User identity v digit 1

odd/

even

indic

Type of user identity v

octet m+1

User identity v digit p+1

User identity v digit p

octet m+2*

Spare

UPRI4

TPRI4I

Address type

octet j

Address information

octet (j+1)*

octet (j+k)*

UDP port range for IPv4

octet (j+k+1)*

octet (j+k+4)*

TCP port range for IPv4

octet l*

octet (l+3)*

Figure 9.9.4.20.2: Remote UE context

Table 9.9.4.20.2: Remote UE context list information element

Odd/even indication (octet 4)

Bit

4

0

even number of identity digits

1

odd number of identity digits

Type of user identity (octet 4)

Bits

3

2

1

0

0

1

Encrypted IMSI

0

1

0

IMSI

0

1

1

MSISDN

1

0

0

IMEI

1

0

1

IMEISV

All other values are reserved.

Identity digits (octet 4 etc)

For the Encrypted IMSI, this field is coded as a 128-bit string. Bits 5 to 8 of octet 4 are not part of the encrypted IMSI and shall be coded as zero. Bit 8 of octet 5 represents the most significant bit of the encrypted IMSI and bit 1 of octet 21 the least significant bit.

For the IMSI, this field is coded using BCD coding. If the number of identity digits is even then bits 5 to 8 of the last octet shall be filled with an end mark coded as "1111". The format of IMSI is described in 3GPP TS 23.003 [2].

For the MSISDN, this field is coded using BCD coding. The format of MSISDN is described in 3GPP TS 23.003 [2].

For the IMEI, this field is coded using BCD coding. The format of the IMEI is described in 3GPP TS 23.003 [2].

For the IMEISV, this field is coded using BCD coding. Bits 5 to 8 of the last octet shall be filled with an end mark coded as "1111". The format of the IMEISV is described in 3GPP TS 23.003 [2].

Bits 6 to 8 of octet j are spare and shall be coded as zero.

Address type (octet j)

Bits

3

2

1

0

0

0

No IP Info

0

0

1

IPv4

0

1

0

IPv6

All other values are reserved.

TCP port range for IPv4 indicator (TPRI4I) (octet j+1, bits 4)

Bits

4

0

TCP port range for IPv4 absent

1

TCP port range for IPv4 present

If the address type field is not set to "IPv4", the TCP port range for IPv4 indicator bit is set to "TCP port range for IPv4 absent".

UDP port range for IPv4 indicator (TPRI4I) (octet j+1, bits 5)

Bits

5

0

UDP port range for IPv4 absent

1

UDP port range for IPv4 present

If the address type field is not set to "IPv4", the UDP port range for IPv4 indicator bit is set to "UDP port range for IPv4 absent".

Address information (octet j+1 to octet j+k)

If Address type indicates IPv4, the Address information in octet j+1 to octet j+6 contains the IPv4 address and port number. Bit 8 of octet j+1 represents the most significant bit of the IP address and bit 1 of octet j+4 the least significant bit. Bit 8 of octet j+5 represents the most significant bit of the port number and bit 1 of octet j+6 the least significant bit. The port number is a port number from the TCP port range or the UDP port range, assigned to the remote UE in the NAT function of ProSe layer-3 UE-to-network relay.

If Address type indicates IPv6, the Address information in octet j+1 to octet j+8 contains the /64 IPv6 prefix of a remote UE. Bit 8 of octet j+1 represents the most significant bit of the /64 IPv6 prefix and bit 1 of octet j+8 the least significant bit.

If Address type indicates No IP info, the Address information octets are not included.

UDP port range for IPv4 (octet (j+k+1) to octet (j+k+4))

The UDP port range for IPv4 field consists of the lowest UDP port number field followed by the highest UDP port number field, of the UDP port range assigned to the remote UE in the NAT function of ProSe layer-3 UE-to-network relay.

If the UDP port range for IPv4 indicator bit is set to "UDP port range for IPv4 present" then the UDP port range for IPv4 field is present otherwise the UDP port range for IPv4 field is absent.

TCP port range for IPv4 (octet l to octet l+3)

The TCP port range for IPv4 field consists of the lowest TCP port number field followed by highest TCP port number field, of the TCP port range assigned to the remote UE in the NAT function of ProSe layer-3 UE-to-network relay.

If the TCP port range for IPv4 indicator bit is set to "TCP port range for IPv4 present" then the TCP port range for IPv4 field is present otherwise the TCP port range for IPv4 field is absent.

Each port number field is two octets long and bit 8 of first octet of the port number field represents the most significant bit of the port number and bit 1 of second octet of the port number field the least significant bit.

NOTE: In the present release of the specification, providing information for IP protocols other than UDP or TCP is not specified.

9.9.4.21 PKMF address

The purpose of the PKMF address information element is to provide IP address of a ProSe Key Management Function associated with remote UEs connected to or disconnected from a UE acting as a ProSe UE-to-network relay.

The PKMF address information element is coded as shown in figure 9.9.4.21.1 and table 9.9.4.21.1.

The PKMF address is a type 4 information element with a minimum length of 3 octets and a maximum length of 19 octets.

8

7

6

5

4

3

2

1

PKMF address IEI

octet 1

Length of PKMF address contents

octet 2

Spare

Address type

octet 3

Address information

octet 4

octet 4+k

Figure 9.9.4.21.1: PKMF Address

Table 9.9.4.21.1: PKMF Address information element

Bits 4 to 8 of octet 1 are spare and shall be coded as zero.

Address type (octet 1)

Bits

3

2

1

0

0

1

IPv4

0

1

0

IPv6

All other values are reserved.

If Address type indicates IPv4, the Address information in octet 4 to octet 7 contains the IPv4 address. Bit 8 of octet 4 represents the most significant bit of the IP address and bit 1 of octet 7 the least significant bit.

If Address type indicates IPv6, the Address information in octet 4 to octet 19 contains the IPv6 address. Bit 8 of octet 4 represents the most significant bit of the IP address and bit 1 of octet 19 the least significant bit.

9.9.4.22 Header compression configuration

The purpose of the Header compression configuration information element is to negotiate ROHC channel setup parameters specified in IETF RFC 5795 [37] and, optionally, provide additional header compression context setup parameters.

The Header compression configuration information element is coded as shown in figure 9.9.4.22.1 and table 9.9.4.22.1.

The Header compression configuration is a type 4 information element with a minimum length of 5 octets and a maximum length of 257 octets.

The optional Additional header compression parameters container field conveys the additional header compression context setup parameters as specified in 3GPP TS 23.401 [10] in a generic container. This field corresponds to the profile-specific information in the header of the ROHC IR packet type in IETF RFC 5795 [37].

8

7

6

5

4

3

2

1

Header compression configuration IEI

octet 1

Length of Header compression configuration contents

octet 2

Spare

P0x0104

P0x0103

P0x0102

P0x0006

P0x0004

P0x0003

P0x0002

octet 3

MAX_CID

octet 4

octet 5

Additional header compression context setup parameters type

octet 6*

Additional header compression context setup parameters container

octet 7*

octet n*

Figure 9.9.4.22.1: Header compression configuration information element

Table 9.9.4.22.1: Header compression configuration information element

ROHC Profiles (octet 3)

The ROHC Profiles shall indicate which of the ROHC profiles is supported. When a particular bit is set to 1, this indicates that the corresponding profile is supported. The No Compression profile 0x0000 (see IETF RFC 5795 [37]) shall always be supported. When all the bits are set to 0, this indicates that only the No Compression profile 0x0000 is supported.

Profile 0x0002 support indicator (see IETF RFC 3095 [40] and IETF RFC 4815 [42]) (octet 3 bit 1)

0 RoHC profile 0x0002 (UDP/IP) is not supported

1 RoHC profile 0x0002 (UDP/IP) is supported

Profile 0x0003 support indicator (see IETF RFC 3095 [40] and IETF RFC 4815 [42]) (octet 3 bit 2)

0 RoHC profile 0x0003 (ESP/IP) is not supported

1 RoHC profile 0x0003 (ESP/IP) is supported

Profile 0x0004 support indicator (see IETF RFC 3843 [41] and IETF RFC 4815 [42]) (octet 3 bit 3)

0 RoHC profile 0x0004 (IP) is not supported

1 RoHC profile 0x0004 (IP) is supported

Profile 0x0006 support indicator (see IETF RFC 6846 [39]) (octet 3 bit 4)

0 RoHC profile 0x0006 (TCP/IP) is not supported

1 RoHC profile 0x0006 (TCP/IP) is supported

Profile 0x0102 support indicator (see IETF RFC 5225 [43]) (octet 3 bit 5)

0 RoHC profile 0x0102 (UDP/IP) is not supported

1 RoHC profile 0x0102 (UDP/IP) is supported

Profile 0x0103 support indicator (see IETF RFC 5225 [43]) (octet 3 bit 6)

0 RoHC profile 0x0103 (ESP/IP) is not supported

1 RoHC profile 0x0103 (ESP/IP) is supported

Profile 0x0104 support indicator (see IETF RFC 5225 [43]) (octet 3 bit 7)

0 RoHC profile 0x0104 (IP) is not supported

1 RoHC profile 0x0104 (IP) is supported

Bits 8 is spare and shall be set to 0.

MAX_CID (octet 4 and octet 5)

This is the MAX_CID value as specified in 3GPP TS 36.323 [38]. It is encoded in binary coding with a value in the range from 1 to 16383.

Additional header compression context parameters type (octet 6).

The Additional header compression context parameters type octet indicates the profile associated with the profile-specific information in the Additional header compression context parameters container.

Bits

8 7 6 5 4 3 2 1 Type

0 0 0 0 0 0 0 0 0x0000 (No Compression)

0 0 0 0 0 0 0 1 0x0002 (UDP/IP)

0 0 0 0 0 0 1 0 0x0003 (ESP/IP)

0 0 0 0 0 0 1 1 0x0004 (IP)

0 0 0 0 0 1 0 0 0x0006 (TCP/IP)

0 0 0 0 0 1 0 1 0x0102 (UDP/IP)

0 0 0 0 0 1 1 0 0x0103 (ESP/IP)

0 0 0 0 0 1 1 1 0x0104 (IP)

0 0 0 0 1 0 0 0 Other

0 0 0 0 1 0 0 1

to

1 1 1 1 1 1 1 1 Spare

Additional header compression context parameters container (octets 7 to n).

Additional header compression context parameters container carries the profile-specific information (see IETF RFC 5795 [37]). The maximum size is 251 octets.

9.9.4.23 Control plane only indication

The purpose of the Control plane only indication information element is to indicate that a PDN connection is only for control plane CIoT EPS optimization, e.g. the PDN connection is with an SCEF (see 3GPP TS 23.401 [10]).

The Control plane only indication information element is coded as shown in figure 9.9.4.23.1.

The Control plane only indication is a type 1 information element.

8

7

6

5

4

3

2

1

Control plane only indication IEI

0

Spare

0

Spare

0

Spare

CPOI value

octet 1

Figure 9.9.4.23.1: Control plane only indication information element

Table 9.9.4.23.1: Control plane only indication information element

Control plane only indication value (CPOI) (octet 1)

Bit

1

0

reserved

1

PDN connection can be used for control plane CIoT EPS optimization only

The value 0 is reserved. If received, it shall be interpreted as if the Control plane indication IE was not included in the message.

Bits 4 to 2 of octet 1 are spare and shall be all encoded as zero.

9.9.4.24 User data container

This information element is used to encapsulate the user data transferred between the UE and the MME. The User data container information element is coded as shown in figure 9.9.4.24.1 and table 9.9.4.24.1.

The User data container is a type 6 information element.

8

7

6

5

4

3

2

1

User data container IEI

octet 1

Length of User data container contents

octet 2

octet 3

octet 4

User data container contents

octet n

Figure 9.9.4.24.1: User data container information element

Table 9.9.4.24.1: User data container information element

User data container contents (octet 4 to octet n)

These octets include user data to be delivered between UE and MME.

9.9.4.25 Release assistance indication

The purpose of the Release assistance indication IE is to inform the network whether

– no further uplink and no further downlink data transmission is expected; or

– only a single downlink data transmission (e.g. acknowledgement or response to uplink data) and no further uplink data transmission subsequent to the uplink data transmission is expected.

The Release assistance indication information element is coded as shown in figure 9.9.4.25.1 and table 9.9.4.25.1.

The Release assistance indication is a type 1 information element.

8

7

6

5

4

3

2

1

Release assistance indication

IEI

0

Spare

0

Spare

DDX

octet 1

Figure 9.9.4.25.1: Release assistance indication information element

Table 9.9.4.25.1: Release assistance indication information element

Release assistance indication value

Downlink data expected (DDX)

Bits

2

1

0

0

No information regarding DDX is conveyed by the information element. If received it shall be interpreted as ‘neither value "01" nor "10" applies’

0

1

No further uplink and no further downlink data transmission subsequent to the uplink data transmission is expected

1

0

Only a single downlink data transmission and no further uplink data transmission subsequent to the uplink data transmission is expected

1

1

reserved

Bits 3 and 4 of octet 1 are spare and shall be encoded as zero.

9.9.4.26 Extended protocol configuration options

See clause 10.5.6.3A in 3GPP TS 24.008 [13].

9.9.4.27 Header compression configuration status

The purpose of the Header compression configuration status information element is to indicate the status of the Header compression configuration for each EPS bearer using Control plane CIoT EPS optimisation that can be identified by an EPS bearer identity.

The Header compression configuration status information element is a type 4 information element with 4 the length of 4 octets.

8

7

6

5

4

3

2

1

Header compression configuration status IEI

octet 1

Length of Header compression configuration status contents

octet 2

EBI

(7)

EBI

(6)

EBI

(5)

EBI

(4)

EBI

(3)

EBI

(2)

EBI

(1)

EBI

(0)

octet 3

EBI

(15)

EBI

(14)

EBI

(13)

EBI

(12)

EBI

(11)

EBI

(10)

EBI

(9)

EBI

(8)

octet 4

Figure 9.9.4.27.1: Header compression configuration status information element

Table 9.9.4.27.1: Header compression configuration status information element

EBI(x) shall be coded as follows:

EBI(0):

Bit 0 of octet 3 is spare and shall be coded as zero.

EBI(1) – EBI(15):

0 indicates that the header compression configuration for the corresponding EPS bearer is used.

1 indicates that the header compression configuration for the corresponding EPS bearer is not used.

9.9.4.28 Serving PLMN rate control

The purpose of the Serving PLMN rate control information element is to indicate the maximum number of uplink ESM DATA TRANSPORT messages including User data container IEs the UE is allowed to send via a PDN connection per 6 minute interval (see 3GPP TS 23.401 [10]).

The Serving PLMN rate control information element is coded as shown in figure 9.9.4.28.1.

The Serving PLMN rate control is a type 4 information element with 4 octets length.

8

7

6

5

4

3

2

1

Serving PLMN rate control IEI

octet 1

Length of serving PLMN rate control contents

octet 2

Serving PLMN rate control value

octet 3

octet 4

Figure 9.9.4.28.1: Serving PLMN rate control information element

Serving PLMN rate control value (octet 3 to octet 4) is a binary encoded integer indicating the maximum number of uplink ESM DATA TRANSPORT messages including User data container IEs the UE is allowed to send per 6 minute interval. The Serving PLMN rate control value is an integer equal to or higher than 10. The Serving PLMN rate control value FFFFH indicates that the maximum number of uplink ESM DATA TRANSPORT messages including User data container IEs the UE is allowed to send per 6 minute interval is not restricted.

9.9.4.29 Extended APN aggregate maximum bit rate

The purpose of the extended APN aggregate maximum bit rate information element is to indicate the initial subscribed APN-AMBR with a value higher than 65280 Mbps when the UE establishes a PDN connection or to indicate the new APN-AMBR with a value higher than 65280 Mbps if it is changed by the network.

The receiving entity shall ignore the bit rate values which are included in the extended APN aggregate maximum bit rate information element and not higher than 65280 Mbps.

The extended APN aggregate maximum bit rate information element is coded as shown in figure 9.9.4.29.1 and table 9.9.4.29.1.

The extended APN aggregate maximum bit rate is a type 4 information element with a length of 8 octets.

8

7

6

5

4

3

2

1

Extended APN aggregate maximum bit rate IEI

octet 1

Length of extended APN aggregate maximum bit rate contents

octet 2

Unit for extended APN-AMBR for downlink

octet 3

Extended APN-AMBR for downlink

octet 4

Extended APN-AMBR for downlink (continued)

octet 5

Unit for extended APN-AMBR for uplink

octet 6

Extended APN-AMBR for uplink

octet 7

Extended APN-AMBR for uplink (continued)

octet 8

Figure 9.9.4.29.1: Extended APN aggregate maximum bit rate information element

Table 9.9.4.29.1: Extended APN aggregate maximum bit rate information element

Unit for extended APN-AMBR for downlink (octet 3)

0 0 0 0 0 0 0 0 value is not used (see NOTE)

0 0 0 0 0 0 0 1 value is not used (see NOTE)

0 0 0 0 0 0 1 0 value is not used (see NOTE)

0 0 0 0 0 0 1 1 value is incremented in multiples of 4 Mbps

0 0 0 0 0 1 0 0 value is incremented in multiples of 16 Mbps

0 0 0 0 0 1 0 1 value is incremented in multiples of 64 Mbps

0 0 0 0 0 1 1 0 value is incremented in multiples of 256 Mbps

0 0 0 0 0 1 1 1 value is incremented in multiples of 1 Gbps

0 0 0 0 1 0 0 0 value is incremented in multiples of 4 Gbps

0 0 0 0 1 0 0 1 value is incremented in multiples of 16 Gbps

0 0 0 0 1 0 1 0 value is incremented in multiples of 64 Gbps

0 0 0 0 1 0 1 1 value is incremented in multiples of 256 Gbps

0 0 0 0 1 1 0 0 value is incremented in multiples of 1 Tbps

0 0 0 0 1 1 0 1 value is incremented in multiples of 4 Tbps

0 0 0 0 1 1 1 0 value is incremented in multiples of 16 Tbps

0 0 0 0 1 1 1 1 value is incremented in multiples of 64 Tbps

0 0 0 1 0 0 0 0 value is incremented in multiples of 256 Tbps

0 0 0 1 0 0 0 1 value is incremented in multiples of 1 Pbps

0 0 0 1 0 0 1 0 value is incremented in multiples of 4 Pbps

0 0 0 1 0 0 1 1 value is incremented in multiples of 16 Pbps

0 0 0 1 0 1 0 0 value is incremented in multiples of 64 Pbps

0 0 0 1 0 1 0 1 value is incremented in multiples of 256 Pbps

Other values shall be interpreted as multiples of 256 Pbps in this version of the protocol.

Extended APN-AMBR for downlink (octets 4 and 5)

Octets 4 and 5 represent the binary coded value of extended APN-AMBR for downlink in units defined by octet 3

Unit for extended APN-AMBR for uplink (octet 6)

The coding is identical to that of the unit for extended APN-AMBR for downlink (octet 3)

Extended APN-AMBR for uplink (octets 7 and 8)

Octets 7 and 8 represent the binary coded value of extended APN-AMBR for uplink in units defined by octet 6.

NOTE: In this release of the specifications if received it shall be interpreted as value is incremented in multiples of 4 Mbps. In earlier releases of specifications, the interpretation of this value is up to implementation.

9.9.4.30 Extended quality of service

The purpose of the Extended quality of service information element is to indicate for an EPS bearer context the maximum bit rates for uplink and downlink and the guaranteed bit rates for uplink and downlink, if at least one of the bit rates has a value higher than 10 Gbps.

The Extended quality of service information element is coded as shown in figure 9.9.4.30.1 and table 9.9.4.30.1. For uplink and downlink, if the sending entity only has to indicate one bit rate (i.e. with a value higher than 10 Gbps), it shall encode the other bit rate (i.e., with a value smaller or equal to 10 Gbps) as "00000000". The receiving entity shall ignore a bit rate which is included in the extended quality of service information element and has a value smaller or equal to 10 Gbps.

The Extended quality of service is a type 4 information element with a length of 12 octets.

8

7

6

5

4

3

2

1

Extended quality of service IEI

octet 1

Length of Extended quality of service contents

octet 2

Unit for maximum bit rate

octet 3

Maximum bit rate for uplink

octet 4

Maximum bit rate for uplink (continued)

octet 5

Maximum bit rate for downlink

octet 6

Maximum bit rate for downlink (continued)

octet 7

Unit for guaranteed bit rate

octet 8

Guaranteed bit rate for uplink

octet 9

Guaranteed bit rate for uplink (continued)

octet 10

Guaranteed bit rate for downlink

octet 11

Guaranteed bit rate for downlink (continued)

octet 12

Figure 9.9.4.30.1: Extended quality of service information element

Table 9.9.4.30.1: Extended quality of service information element

Unit for maximum bit rate (octet 3)

0 0 0 0 0 0 0 0 value is not used (see NOTE)

0 0 0 0 0 0 0 1 value is incremented in multiples of 200 kbps

0 0 0 0 0 0 1 0 value is incremented in multiples of 1 Mbps

0 0 0 0 0 0 1 1 value is incremented in multiples of 4 Mbps

0 0 0 0 0 1 0 0 value is incremented in multiples of 16 Mbps

0 0 0 0 0 1 0 1 value is incremented in multiples of 64 Mbps

0 0 0 0 0 1 1 0 value is incremented in multiples of 256 Mbps

0 0 0 0 0 1 1 1 value is incremented in multiples of 1 Gbps

0 0 0 0 1 0 0 0 value is incremented in multiples of 4 Gbps

0 0 0 0 1 0 0 1 value is incremented in multiples of 16 Gbps

0 0 0 0 1 0 1 0 value is incremented in multiples of 64 Gbps

0 0 0 0 1 0 1 1 value is incremented in multiples of 256 Gbps

0 0 0 0 1 1 0 0 value is incremented in multiples of 1 Tbps

0 0 0 0 1 1 0 1 value is incremented in multiples of 4 Tbps

0 0 0 0 1 1 1 0 value is incremented in multiples of 16 Tbps

0 0 0 0 1 1 1 1 value is incremented in multiples of 64 Tbps

0 0 0 1 0 0 0 0 value is incremented in multiples of 256 Tbps

0 0 0 1 0 0 0 1 value is incremented in multiples of 1 Pbps

0 0 0 1 0 0 1 0 value is incremented in multiples of 4 Pbps

0 0 0 1 0 0 1 1 value is incremented in multiples of 16 Pbps

0 0 0 1 0 1 0 0 value is incremented in multiples of 64 Pbps

0 0 0 1 0 1 0 1 value is incremented in multiples of 256 Pbps

Other values shall be interpreted as multiples of 256 Pbps in this version of the protocol.

Maximum bit rate for uplink (octets 4 and 5)

Octets 4 and 5 represent the binary coded value of maximum bit rate for uplink in units defined by octet 3.

Maximum bit rate for downlink (octets 6 and 7)

Octets 6 and 7 represent the binary coded value of maximum bit rate for downlink in units defined by octet 3.

Unit for guaranteed bit rate (octet 8)

The coding is identical to that of the unit for maximum bit rate (octet 3).

Guaranteed bit rate for uplink (octets 9 and 10)

Octets 9 and 10 represent the binary coded value of guaranteed bit rate for uplink in units defined by octet 8.

Guaranteed bit rate for downlink (octets 11 and 12)

Octets 11 and 12 represent the binary coded value of guaranteed bit rate for downlink in units defined by octet 8.

NOTE: In this release of the specifications if received it shall be interpreted as value is incremented in multiples of 200 Kbps. In earlier releases of specifications, the interpretation of this value is up to implementation.