8

7

6

5

4

3

2

1

8

7

6

5

4

3

2

1

8

7

6

5

4

3

2

1

Configuration protocol (octet 3)
Bits
3 2 1
0 0 0 PPP for use with IP PDP type or IP PDN type (see 3GPP TS 24.301 [120])

All other values are interpreted as PPP in this version of the protocol.

After octet 3, i.e. from octet 4 to octet z, two logical lists are defined:

– the Configuration protocol options list (octets 4 to w), and

– the Additional parameters list (octets w+1 to za).

Configuration protocol options list (octets 4 to w)

The configuration protocol options list contains a variable number of logical units, they may occur in an arbitrary order within the configuration protocol options list.

Each unit is of variable length and consists of a:

– protocol identifier (2 octets);
– the length of the protocol identifier contents of the unit (1 octet); and
– the protocol identifier contents itself (n octets).

The protocol identifier field contains the hexadecimal coding of the configuration protocol identifier. Bit 8 of the first octet of the protocol identifier field contains the most significant bit and bit 1 of the second octet of the protocol identifier field contains the least significant bit.

If the configuration protocol options list contains a protocol identifier that is not supported by the receiving entity the corresponding unit shall be ignored.

The length of the protocol identifier contents field contains the binary coded representation of the length of the protocol identifier contents field of a unit. The first bit in transmission order is the most significant bit.

The protocol identifier contents field of each unit contains information specific to the configuration protocol specified by the protocol identifier.

At least the following protocol identifiers (as defined in RFC 3232 [103]) shall be supported in this version of the protocol:

– C021H (LCP);
– C023H (PAP) (see NOTE 3);
– C223H (CHAP) (see NOTE 3); and
– 8021H (IPCP).

The support of other protocol identifiers is implementation dependent and outside the scope of the present document.

The protocol identifier contents field of each unit corresponds to a "Packet" as defined in RFC 1661 [102] that is stripped off the "Protocol" and the "Padding" octets.

The detailed coding of the protocol identifier contents field is specified in the RFC that is associated with the protocol identifier of that unit: LCP is specified in RFC 1661 [102], PAP is specified in RFC 1334 [179], CHAP is specified in RFC 1994 [180] and IPCP is specified in RFC 1332 [181].

Additional parameters list (octets w+1 to za)

The additional parameters list is included when special parameters and/or requests (associated with a PDP context) need to be transferred between the MS and the network. These parameters and/or requests are not related to a specific configuration protocol (e.g. PPP), and therefore are not encoded as the "Packets" contained in the configuration protocol options list.

The additional parameters list contains a list of special parameters, each one in a separate container. The type of the parameter carried in a container is identified by a specific container identifier. In this version of the protocol, the following container identifiers are specified:

MS to network direction:

– 0001H (P-CSCF IPv6 Address Request);

– 0002H (IM CN Subsystem Signaling Flag);

– 0003H (DNS Server IPv6 Address Request);

– 0004H (Not Supported);

– 0005H (MS Support of Network Requested Bearer Control indicator);

– 0006H (Reserved);

– 0007H (DSMIPv6 Home Agent Address Request);

– 0008H (DSMIPv6 Home Network Prefix Request);

– 0009H (DSMIPv6 IPv4 Home Agent Address Request);

– 000AH (IP address allocation via NAS signalling);

– 000BH (IPv4 address allocation via DHCPv4);

– 000CH (P-CSCF IPv4 Address Request);

– 000DH (DNS Server IPv4 Address Request);

– 000EH (MSISDN Request);

– 000FH (IFOM-Support-Request);

– 0010H (IPv4 Link MTU Request);

– 0011H (MS support of Local address in TFT indicator) (see NOTE 4);

– 0012H (P-CSCF Re-selection support);

– 0013H (NBIFOM request indicator);

– 0014H (NBIFOM mode);

– 0015H (Non-IP Link MTU Request);

– 0016H (APN rate control support indicator);

– 0017H (3GPP PS data off UE status);

– 0018H (Reliable Data Service request indicator);

– 0019H (Additional APN rate control for exception data support indicator);

– 001AH (PDU session ID);

– 001BH (reserved);

– 001CH (Reserved);

– 001DH (Reserved);

– 001EH (Reserved);

– 001FH (Reserved);

– 0020H (Ethernet Frame Payload MTU Request);

– 0021H (Unstructured Link MTU Request);

– 0022H (5GSM cause value);

– 0023H (QoS rules with the length of two octets support indicator);

– 0024H (QoS flow descriptions with the length of two octets support indicator);

– 0025H (Reserved)

– 0026H (Reserved);

– 0027H (ACS information request);

— 0028H (Reserved);

– 0029H (Reserved);

– 002AH (Reserved);

– 002BH (Reserved);

– 0030H (ATSSS request);

– 0031H (DNS server security information indicator);

– 0032H (ECS configuration information provisioning support indicator);

– 0035H (Reserved);

– 0036H (PVS information request);

– 0037H (Reserved);

– 0038H (Reserved);

– 0039H (DNS server security protocol support);

– 003AH (EAS rediscovery support indication);

– 003BH (Reserved);

– 003CH (Reserved);

– 003DH (Reserved);

– 003EH (Reserved);

– 003FH (Reserved);

– 0040H (Reserved);

– 0041H (Service-level-AA container with the length of two octets);

– 0047H (EDC support indicator);

– 0048H (Reserved);

– 0049H (Reserved);

– 004AH (MS support of MAC address range in 5GS indicator);

– 00XXH (SDNAEPC support indicator);

– 00YYH (SDNAEPC EAP message with the length of two octets); and

– FF00H to FFFFH reserved for operator specific use.

Network to MS direction:

– 0001H (P-CSCF IPv6 Address);

– 0002H (IM CN Subsystem Signaling Flag);

– 0003H (DNS Server IPv6 Address);

– 0004H (Policy Control rejection code);

– 0005H (Selected Bearer Control Mode);

– 0006H (Reserved);

– 0007H (DSMIPv6 Home Agent Address) ;

– 0008H (DSMIPv6 Home Network Prefix);

– 0009H (DSMIPv6 IPv4 Home Agent Address);

– 000AH (Reserved);

– 000BH (Reserved);

– 000CH (P-CSCF IPv4 Address);

– 000DH (DNS Server IPv4 Address);

– 000EH (MSISDN);

– 000FH (IFOM-Support);

– 0010H (IPv4 Link MTU);

– 0011H (Network support of Local address in TFT indicator);

– 0012H (Reserved);

– 0013H (NBIFOM accepted indicator);

– 0014H (NBIFOM mode);

– 0015H (Non-IP Link MTU);

– 0016H (APN rate control parameters);

– 0017H (3GPP PS data off support indication);

– 0018H (Reliable Data Service accepted indicator);

– 0019H (Additional APN rate control for exception data parameters);

– 001AH (reserved);

– 001BH (S-NSSAI);

– 001CH (QoS rules);

– 001DH (Session-AMBR);

– 001EH (PDU session address lifetime);

– 001FH (QoS flow descriptions);

– 0020H (Ethernet Frame Payload MTU);

– 0021H (Unstructured Link MTU);

– 0022H (Reserved);

– 0023H (QoS rules with the length of two octets);

– 0024H (QoS flow descriptions with the length of two octets);

– 0025H (Small data rate control parameters);

– 0026H (Additional small data rate control for exception data parameters);

– 0027H (ACS information);

– 0028H (Initial small data rate control parameters);

– 0029H (Initial additional small data rate control for exception data parameters);

– 002AH (Initial APN rate control parameters);

– 002BH (Initial additional APN rate control for exception data parameters);

– 0030H (ATSSS response with the length of two octets);

– 0031H (DNS server security information with length of two octets);

– 0032H (ECS address with the length of two octets);

– 0035H (ECSP identifier);

– 0036H (PVS IPv4 Address);

– 0037H (PVS IPv6 Address);

– 0038H (PVS name);

– 0039H (reserved);

– 003AH (EAS rediscovery indication without indicated impact);

– 003BH (EAS rediscovery indication with impacted EAS IPv4 address range);

– 003CH (EAS rediscovery indication with impacted EAS IPv6 address range);

– 003DH (EAS rediscovery indication with impacted EAS FQDN);

– 003EH (Uplink data not allowed);

– 003FH (Uplink data allowed);

– 0040H (UAS services not allowed indication);

– 0041H (Service-level-AA container with the length of two octets);

– 0047H (Reserved);

– 0048H (EDC usage allowed indicator);

– 0049H (EDC usage required indicator);

– 004AH (Network support of MAC address range in 5GS indicator);

– 0050H (Reserved);

– 0051H (SDNAEPC EAP message with the length of two octets); and

– FF00H to FFFFH reserved for operator specific use.

If the additional parameters list contains a container identifier that is not supported by the receiving entity the corresponding unit shall be ignored.

The container identifier field is encoded as the protocol identifier field and the length of container identifier contents field is encoded as the length of the protocol identifier contents field.

When the container identifier indicates P-CSCF IPv6 Address Request, DNS Server IPv6 Address Request, MSISDN Request or DNS server security information indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. The DNS server security information indicator indicates that the MS supports receiving DNS server security information with length of two octets. When the DNS Server IPv6 Address Request is indicated in N1 mode, the DNS Server IPv6 Address Request indicates that the MS supports handling of the DNS Server IPv6 address(es) received in the PDU session establishment procedure and network-requested PDU session modification procedure(s), if any.

When the container identifier indicates IM CN Subsystem Signaling Flag (see 3GPP TS 24.229 [95]), the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. In Network to MS direction this information may be used by the MS to indicate to the user whether the requested dedicated signalling PDP context was successfully established.

When the container identifier indicates P-CSCF IPv6 Address, the container identifier contents field contains one IPv6 address corresponding to a P-CSCF address (see 3GPP TS 24.229 [95]). This IPv6 address is encoded as a 128-bit address according to IETF RFC 4291 [99]. When there is a need to include more than one P-CSCF IPv6 address, then more logical units with the container identifier indicating P-CSCF IPv6 Address are used. If more than 3 instances of the P‑CSCF IPv6 Address logical unit are received by the MS, then the MS may ignore all but the first 3 instances of the P‑CSCF IPv6 Address logical unit received.

When the container identifier indicates DNS Server IPv6 Address, the container identifier contents field contains one IPv6 DNS server address (see 3GPP TS 27.060 [36a]). This IPv6 address is encoded as a 128-bit address according to IETF RFC 4291 [99]. When there is a need to include more than one DNS Server IPv6 address, then more logical units with the container identifier indicating DNS Server IPv6 Address are used.

When the container identifier indicates Policy Control rejection code, the container identifier contents field contains a Go interface related cause code from the GGSN to the MS (see 3GPP TS 29.207 [100]). The length of container identifier contents indicates a length equal to one. If the container identifier contents field is empty or its actual length is greater than one octet, then it shall be ignored by the receiver.

When the container identifier indicates MS Support of Network Requested Bearer Control indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored.

When the container identifier indicates Selected Bearer Control Mode, the container identifier contents field contains the selected bearer control mode, where ’01H’ indicates that ‘MS only’ mode has been selected and ’02H’ indicates that ‘MS/NW’ mode has been selected. The length of container identifier contents indicates a length equal to one. If the container identifier contents field is empty or its actual length is greater than one octet, then it shall be ignored by the receiver.

When the container identifier indicates DSMIPv6 Home Agent Address Request, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored.

When the container identifier indicates DSMIPv6 Home Network Prefix Request, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored.

When the container identifier indicates DSMIPv6 IPv4 Home Agent Address Request, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored.

When the container identifier indicates DSMIPv6 Home Agent Address, the container identifier contents field contains one IPv6 address corresponding to a DSMIPv6 HA address (see 3GPP TS 24.303 [124] and 3GPP TS 24.327 [125]). This IPv6 address is encoded as a 128-bit address according to IETF RFC 4291 [99].

When the container identifier indicates DSMIPv6 Home Network Prefix, the container identifier contents field contains one IPv6 Home Network Prefix (see 3GPP TS 24.303 [124] and 3GPP TS 24.327 [125]). This IPv6 prefix is encoded as an IPv6 address according to IETF RFC 4291 [99] followed by 8 bits which specifies the prefix length.

When the container identifier indicates DSMIPv6 IPv4 Home Agent Address, the container identifier contents field contains one IPv4 address corresponding to a DSMIPv6 IPv4 Home Agent address (see 3GPP TS 24.303 [124] and 3GPP TS 24.327 [125]).

When the container identifier indicates P-CSCF IPv4 Address Request, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored.

When the container identifier indicates DNS Server IPv4 Address Request, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. When the DNS Server IPv4 Address Request is indicated in N1 mode, the DNS Server IPv4 Address Request indicates that the MS supports handling of the DNS Server IPv4 address(es) received in the PDU session establishment procedure and network-requested PDU session modification procedure(s), if any.

When the container identifier indicates P-CSCF IPv4 Address, the container identifier contents field contains one IPv4 address corresponding to the P-CSCF address to be used. When there is a need to include more than one P‑CSCF IPv4 address, then more logical units with the container identifier indicating P‑CSCF IPv4 Address are used. If more than 3 instances of the P‑CSCF IPv4 Address logical unit are received by the MS, then the MS may ignore all but the first 3 instances of the P‑CSCF IPv4 Address logical unit received.

When the container identifier indicates DNS Server IPv4 Address, the container identifier contents field contains one IPv4 address corresponding to the DNS server address to be used. When there is a need to include more than one DNS Server IPv4 address, then more logical units with the container identifier indicating DNS Server IPv4 Address are used.

P-CSCF IPv4 Address Request, P-CSCF IPv4 Address, DNS Server IPv4 Address Request and DNS Server IPv4 Address are applicable in S1-mode and N1-mode.

When the container identifier indicates IP address allocation via NAS signalling, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored.

When the container identifier indicates IP address allocation via DHCPv4, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored.

When the container identifier indicates MSISDN, the container identifier contents field contains the MSISDN (see 3GPP TS 23.003 [10]) assigned to the MS. Use of the MSISDN provided is defined in subclause 6.4. The content of the MSISDN is coded as the value part of the Called party BCD number information element as specified in subclause 10.5.4.7.

When the container identifier indicates IFOM Support Request (see 3GPP TS 24.303 [124] and 3GPP TS 24.327 [125]), the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored.

When the container identifier indicates IFOM Support, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the Home Agent supports IFOM.

When the container identifier indicates IPv4 Link MTU Request, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored.

When the container identifier indicates IPv4 Link MTU, the length of container identifier contents indicates a length equal to two. The container identifier contents field contains the binary coded representation of the IPv4 link MTU size in octets. Bit 8 of the first octet of the container identifier contents field contains the most significant bit and bit 1 of the second octet of the container identifier contents field contains the least significant bit. If the length of container identifier contents is different from two octets, then it shall be ignored by the receiver.

When the container identifier indicates MS support of Local address in TFT, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS supports Local address in TFTs.

When the container identifier indicates Network support of Local address in TFT, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the network supports Local address in TFTs.

When the container identifier indicates P-CSCF Re-selection support, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This PCO parameter may be present only if a container with P-CSCF IPv4 Address Request or P-CSCF IPv6 Address Request is present. This information indicates that the UE supports P-CSCF re-selection based on procedures specified in 3GPP TS 24.229 [95] subclauses B.2.2.1C, L.2.2.1C, R.2.2.1C, U.2.2.1C and W.2.2.1C.

When the container identifier indicates NBIFOM request indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS requests the NBIFOM usage.

When the container identifier indicates NBIFOM accepted indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the network accepts UE’s request of the NBIFOM usage.

When the container identifier indicates NBIFOM mode, the length of container identifier contents indicates a length equal to one. If the length of container identifier contents indicates length different to one, it shall be ignored. The container identifier contents field containing value 00H indicates the UE-initiated NBIFOM mode. The container identifier contents field containing value 01H indicates the network-initiated NBIFOM mode. The container identifier contents field containing a value other than 00H and other than 01H shall be ignored.

When the container identifier indicates Non-IP Link MTU Request, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS requests link MTU for "non-IP" PDN connection.

When the container identifier indicates Non-IP Link MTU, the length of container identifier contents indicates a length equal to two. The container identifier contents field contains the binary coded representation of the link MTU size for non-IP PDN connection in octets which is at least 128 octets. Bit 8 of the first octet of the container identifier contents field contains the most significant bit and bit 1 of the second octet of the container identifier contents field contains the least significant bit. If the length of container identifier contents is different from two octets, then it shall be ignored by the receiver.

When the container identifier indicates APN rate control support indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS supports APN rate control functionality.

When the container identifier indicates APN rate control parameters, the container identifier contents field contains parameters for APN rate control functionality. The container contents are coded as described in subclause 10.5.6.3.2.

When the container identifier indicates Initial APN data rate control parameters, the container identifier contents field contains status parameters for APN rate control functionality. The container contents are coded as described in subclause 10.5.6.3.8.

When the container identifier indicates 3GPP PS data off UE status, the container identifier contents field contains information of the status of 3GPP PS data off in the UE for a PDN connection where "01H" indicates ’deactivated’ and "02H" indicates ‘activated’. The length of container identifier contents indicates a length equal to one. If the container identifier contents field is empty or its actual length is greater than one octet, then it shall be ignored by the receiver.

When the container identifier indicates 3GPP PS data off support indication, the container identifier contents field is empty. The length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, then it shall be ignored by the receiver.

When the container identifier indicates Reliable Data Service request indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS requests the Reliable Data Service usage as specified in 3GPP TS 24.250 [162].

When the container identifier indicates Reliable Data Service accepted indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the network accepts UE’s request of the Reliable Data Service usage as specified in 3GPP TS 24.250 [162].

When the container identifier indicates Additional APN rate control for exception data support indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS supports additional APN rate control for exception data functionality.

When the container identifier indicates Additional APN rate control for exception data parameters, the container identifier contents field contains parameters for additional APN rate control for exception data functionality. The container contents are coded as described in subclause 10.5.6.3.3.

When the container identifier indicates Initial additional APN rate control for exception data parameters, the container identifier contents field contains status parameters for additional APN rate control for exception data functionality. The container contents are coded as described in subclause 10.5.6.3.9.

When the container identifier indicates PDU session identity, the container identifier contents field contains the PDU session identity assigned by the MS. The encoding of the PDU session identity and its usage are defined in 3GPP TS 24.007 [20].

When the container identifier indicates S-NSSAI, the container identifier contents field contains one S-NSSAI value followed by one PLMN ID that the S-NSSAI relates to. The S-NSSAI value is coded as the value part of S-NSSAI information element as specified in subclause 9.11.2.8 of 3GPP TS 24.501 [167]. The PLMN ID is encoded as the value of the PLMN identity of the CN operator IE in subclause 10.5.5.36. The usage of the S-NSSAI and the associated PLMN ID is defined in 3GPP TS 24.501 [167].

When the container identifier indicates QoS rules, the container identifier contents field contains the QoS rules for the QoS flow corresponding to the EPS bearer of the PDN connection. The QoS rules is coded as the value part of QoS rules information element as specified in subclause 9.11.4.13 of 3GPP TS 24.501 [167]. The usage of the QoS rules is specified in 3GPP TS 24.501 [167].

When the container identifier indicates Session-AMBR, the container identifier contents field contains the Session-AMBR for the PDU session corresponding to the PDN connection. The Session-AMBR is coded as the value part of Session-AMBR information element as specified in subclause 9.11.4.14 of 3GPP TS 24.501 [167]. The usage of the Session-AMBR is specified in 3GPP TS 24.501 [167].

When the container identifier indicates PDU session address lifetime, the length of container identifier contents indicates a length equal to two. The container identifier contents field contains the binary coded representation of how long the network is willing to maintain the PDU session in units of seconds. Bit 8 of the first octet of the container identifier contents field contains the most significant bit and bit 1 of the second octet of the container identifier contents field contains the least significant bit. If the length of container identifier contents is different from two octets, then it shall be ignored by the receiver.

When the container identifier indicates QoS flow descriptions, the container identifier contents field contains the QoS flow descriptions for the QoS flow corresponding to the EPS bearer of the PDN connection. The QoS flow descriptions is coded as the value part of QoS flow descriptions information element as specified in subclause 9.11.4.12 of 3GPP TS 24.501 [167]. The usage of the QoS flow descriptions is specified in 3GPP TS 24.501 [167].

When the container identifier indicates Ethernet Frame Payload MTU Request, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS requests link MTU for an Ethernet PDU session.

When the container identifier indicates Ethernet Frame Payload MTU, the length of container identifier contents indicates a length equal to two. The container identifier contents field contains the binary coded representation of Ethernet frame payload MTU size, i.e. the maximum size of a payload of an Ethernet frame which can be sent via an Ethernet PDU session in octets. Bit 8 of the first octet of the container identifier contents field contains the most significant bit and bit 1 of the second octet of the container identifier contents field contains the least significant bit. If the length of container identifier contents is different from two octets, then it shall be ignored by the receiver.

When the container identifier indicates Unstructured Link MTU Request, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS requests link MTU for an Unstructured PDU session.

When the container identifier indicates Unstructured Link MTU, the length of container identifier contents indicates a length equal to two. The container identifier contents field contains the binary coded representation of unstructured link MTU size, i.e. the maximum size of a message which can be sent via an Unstructured PDU session in octets. Bit 8 of the first octet of the container identifier contents field contains the most significant bit and bit 1 of the second octet of the container identifier contents field contains the least significant bit. If the length of container identifier contents is different from two octets, then it shall be ignored by the receiver.

When the container identifier indicates 5GSM cause value, the container identifier contents field contains a 5GSM cause value. The encoding of the 5GSM cause value and its usage are specified in 3GPP TS 24.501 [167].

When the container identifier indicates QoS rules with the length of two octets support indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. The length of container identifier contents field consists of one octet. This information indicates that the MS supports receiving QoS rules with the length of two octets.

When the container identifier indicates QoS flow descriptions with the length of two octets support indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. The length of container identifier contents field consists of one octet. This information indicates that the MS supports receiving QoS flow descriptions with the length of two octets.

When the container identifier indicates QoS rules with the length of two octets, the container identifier contents field contains the QoS rules for the QoS flow corresponding to the EPS bearer of the PDN connection if the MS has indicated the support of receiving QoS rules with the length of two octets. The QoS rules with the length of two octets is coded as the value part of QoS rules information element as specified in subclause 9.11.4.13 of 3GPP TS 24.501 [167]. The usage of the QoS rules is specified in 3GPP TS 24.501 [167]. See NOTE 2.

When the container identifier indicates QoS flow descriptions with the length of two octets, the container identifier contents field contains the QoS flow descriptions for the QoS flow corresponding to the EPS bearer of the PDN connection if the MS has indicated the support of receiving QoS flow descriptions with the length of two octets. The QoS flow descriptions with the length of two octets is coded as the value part of QoS flow descriptions information element as specified in subclause 9.11.4.12 of 3GPP TS 24.501 [167]. The usage of the QoS flow descriptions is specified in 3GPP TS 24.501 [167]. See NOTE 2.

When the container identifier indicates Small data rate control parameters, the container identifier contents field contains parameters for small data rate control functionality. The container contents are coded as described in subclause 10.5.6.3.4.

When the container identifier indicates Initial small data rate control parameters, the container identifier contents field contains status parameters for small data rate control functionality. The container contents are coded as described in subclause 10.5.6.3.6.

When the container identifier indicates Additional small data rate control for exception data parameters, the container identifier contents field contains parameters for additional small data rate control for exception data functionality. The container contents are coded as described in subclause 10.5.6.3.5.

When the container identifier indicates Initial additional small data rate control for exception data parameters, the container identifier contents field contains status parameters for additional small data rate control for exception data functionality. The container contents are coded as described in subclause 10.5.6.3.7.

When the container identifier indicates ACS information request, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS requests ACS information.

When the container identifier indicates ACS information, the length of container identifier contents indicates non-zero length. The container identifier contents field contains the UTF-8 (see IETF RFC 3629 [168]) coded representation of an ACS URL. Bit 8 of the first octet of the container identifier contents field contains the most significant bit and bit 1 of the last octet of the container identifier contents field contains the least significant bit.

When the container identifier indicates ATSSS request, the container identifier contents field is coded according to 3GPP TS 24.193 [171] subclause 6.1.6.2. The length of container identifier contents field consists of one octet. This information indicates that the MS supports receiving ATSSS response with the length of two octets.

When the container identifier indicates ATSSS response with the length of two octets, the container identifier contents field is coded according to 3GPP TS 24.193 [171] subclause 6.1.6.3. See NOTE 2.

When the container identifier indicates DNS server security information with length of two octets, the container identifier contents field contains one of the parameters: security protocol type, port number, authentication domain name, SPKI pin sets, root certificate, raw public key.

When there is a need to send more than one parameter, then multiple containers with the container identifier indicating DNS server security information with length of two octets are used, each containing one parameter. The first octet of container identifier contents of the DNS server security information with length of two octets contains the type and all octets excluding the first octet of the container identifier contents field of the DNS server security information with length of two octets contain the value part. If the DNS server security information with length of two octets contains security protocol type then the type is set to 00H and the value part is set to 00H if the security protocol type is TLS (see IETF RFC 7858 [172]) and 01H if the security protocol type is DTLS (see IETF RFC 8094 [173]). If the DNS server security information with length of two octets contains port number then the type is set to 01H and the value part to content is set ephemeral port (see IETF RFC 6056 [174]). If the DNS server security information with length of two octets contains authentication domain name then the type is set to 02H and the value part is set authentication domain name (The FQDN shall be encoded as defined in IEFT RFC 1035 [175]). If the DNS server security information with length of two octets contains SPKI pin set then the type is set to 03H and the value part is set SPKI pin set (The SPKI pin set shall be encoded as in DER as specified in X 690.3 [177]). If the DNS server security information with length of two octets contains a root certificate then the type is set to 04H and the value part is set the root certificate (the root certificate is encoded as in DER as specified in X 690 [177]). If the DNS server security information with length of two octets contains raw public key then the type is set to 05H and the value part is set to raw public key (The raw public key shall be encoded as in DER as specified in X 690.3 [177]). See NOTE 2.
If the DNS server security information indicator or the DNS server security protocol support is included by the MS, the network may configure the UE with the DNS server security information. If the MS includes DNS server security information indicator but does not include the DNS server security protocol support, the network may configure the UE with both security protocols TLS and DTLS.

When the container identifier indicates DNS server security protocol support, the container identifier contents field contains the parameter security protocol type. The first octet of container identifier contents of the DNS server security protocol support with length of one octet contains the security protocol type. If the security protocol type is is set to 01H the UE indicates the support of the security protocol TLS (see IETF RFC 7858 [172]) and if it is set to 02H the UE indicates the support of the security protocol DTLS (see IETF RFC 8094 [173]), all other values are spare. When there is a need to send more than one parameter, then multiple containers with the container identifier indicating DNS server security protocol support with length of one octet are used, each containing one parameter.

When the container identifier indicates ECS configuration information provisioning support indicator (related to ECS IPv4 Address, ECS IPv6 Address, ECS FQDN and ECSP identifier), the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS supports to receive ECS address with the length of two octets. The usage of ECS configuration information provisioning support indicator is specified in 3GPP TS 24.501 [167].

When the container identifier indicates ECS address with the length of two octets, the container identifier contents field contains an ECS address and may contain spatial validity condition parameters as specified in subclause 9.11.4.34 of 3GPP TS 24.501 [167], if the MS has indicated ECS configuration information provisioning support indicator. When there is a need to include more than one ECS address, then more logical units with the container identifier indicating ECS address with the length of two octets are used. The usage of ECS address and spatial validity condition is specified in 3GPP TS 24.501 [167].

When the container identifier indicates ECSP identifier, the container identifier contents field contains one ECSP identifier (see 3GPP TS 23.558 [184]). There can be multiple ECSP identifier logical units. Each logical unit shall be considered related to any previous ECS address with length of two octets logical units. If an ECSP identifier logical unit is not following an ECS address with length of two octets logical unit it shall be ignored. The ECSP identifier is encoded as a UTF-8 string. The usage of ECSP identifier is specified in 3GPP TS 24.501 [167].

When the container identifier indicates PVS information request, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS requests PVS information as specified in 3GPP TS 23.501 [166].

When the container identifier indicates PVS IPv4 Address, the container identifier contents field contains parameters for PVS IPv4 Address information. The container contents are coded as described in subclause 10.5.6.3.10d. When there is a need to include more than one PVS IPv4 address, then more logical units with the container identifier indicating PVS IPv4 Address are used.

When the container identifier indicates PVS IPv6 Address, the container identifier contents field contains parameters for PVS IPv6 Address information. The container contents are coded as described in subclause 10.5.6.3.11. When there is a need to include more than one PVS IPv6 address, then more logical units with the container identifier indicating PVS IPv6 Address are used.

When the container identifier indicates PVS name, the container identifier contents field contains parameters for fully qualified domain name information. The container contents are coded as described in subclause 10.5.6.3.12. When there is a need to include more than one PVS name, then more logical units with the container identifier indicating PVS name are used.

When the container identifier indicates EAS rediscovery support indication, either the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero, or the container identifier contents field contains one octet long capability field. If the container identifier contents field is longer than one octet, the octets after the first octet of the container identifier contents shall be ignored by the receiving entity. EAS rediscovery support indication indicates that the sending entity supports handling of the EAS rediscovery indication without indicated impact received in PDU session modifications. Bit 1 of the capability field set to zero indicates that the sending entity does not support handling of the EAS rediscovery indication with impacted EAS IPv4 address range received in PDU session modifications. Bit 1 of the capability field set to one indicates that the sending entity supports handling of the EAS rediscovery indication with impacted EAS IPv4 address range received in PDU session modifications. Bit 2 of the capability field set to zero indicates that the sending entity does not support handling of the EAS rediscovery indication with impacted EAS IPv6 address range received in PDU session modifications. Bit 2 of the capability field set to one indicates that the sending entity supports handling of the EAS rediscovery indication with impacted EAS IPv6 address range received in PDU session modifications. Bit 3 of the capability field set to zero indicates that the sending entity does not support handling of the EAS rediscovery indication with impacted FQDN received in PDU session modifications. Bit 3 of the capability field set to one indicates that the sending entity supports handling of the EAS rediscovery indication with impacted FQDN received in PDU session modifications. Bits 4 to 8 of the capability field shall be set to zero by the sending entity and shall be ignored by the receiving entity. If the container identifier contents field is empty, the receiving entity shall consider that the container identifier contents field with the capability field with value 00H is received. The usage of EAS rediscovery support indication is specified in 3GPP TS 24.501 [167].

When the container identifier indicates EAS rediscovery indication without indicated impact, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. EAS rediscovery indication without indicated impact indicates that all EAS information(s) as specified in 3GPP TS 23.548 [182] need to be refreshed. If the container identifier contents field is not empty, it shall be ignored. The usage of EAS rediscovery indication without indicated impact is specified in 3GPP TS 24.501 [167].

When the container identifier indicates EAS rediscovery indication with impacted EAS IPv4 address range, the container identifier contents field contains binary encoded lowest IPv4 address of the EAS IPv4 address range followed by binary encoded highest IPv4 address of the EAS IPv4 address range, and the length of container identifier contents indicates eight. EAS rediscovery indication with impacted EAS IPv4 address range indicates IPv4 address(es) of EAS information(s) as specified in 3GPP TS 23.548 [182] which needs to be refreshed. When there is a need to include EAS rediscovery indication with more impacted EAS IPv4 address ranges, then more logical units with the container identifier indicating EAS rediscovery indication with impacted EAS IPv4 address range, are used. The usage of EAS rediscovery indication with impacted EAS IPv4 address range is specified in 3GPP TS 24.501 [167].

When the container identifier indicates EAS rediscovery indication with impacted EAS IPv6 address range, the container identifier contents field contains binary encoded lowest IPv6 address of the EAS IPv6 address range followed by binary encoded highest IPv6 address of the EAS IPv6 address range, and the length of container identifier contents indicates thirty two (decimal). EAS rediscovery indication with impacted EAS IPv6 address range indicates IPv6 address(es) of EAS information(s) as specified in 3GPP TS 23.548 [182] which needs to be refreshed. When there is a need to include EAS rediscovery indications with more impacted EAS IPv6 address ranges, then more logical units with the container identifier indicating EAS rediscovery indication with impacted EAS IPv6 address range, are used. The usage of EAS rediscovery indication with impacted EAS IPv6 address range is specified in 3GPP TS 24.501 [167].

When the container identifier indicates EAS rediscovery indication with impacted EAS FQDN, the container identifier contents field contains one EAS FQDN. EAS rediscovery indication with impacted EAS FQDN indicates an FQDN of EAS information as specified in 3GPP TS 23.548 [182] which needs to be refreshed. The FQDN is constructed as specified in subclause 19.4.2 of 3GPP TS 23.003 [10]. When there is a need to include EAS rediscovery indications with more impacted EAS FQDNs, then more logical units with the container identifier indicating EAS rediscovery indication with impacted EAS FQDN are used. The usage of EAS rediscovery indication with impacted EAS FQDN is specified in 3GPP TS 24.501 [167]. See NOTE 5.

When the container identifier indicates Uplink data not allowed (see 3GPP TS 24.301 [120]), the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that uplink user data shall not be sent over EPS bearer context(s) of the PDN connection.

When the container identifier indicates Uplink data allowed (see 3GPP TS 24.301 [120]), the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that uplink user data are allowed over EPS bearer context(s) of the PDN connection.

When the container identifier indicates UAS services not allowed indication, the container identifier contents field is empty and the length of container identifier contents indicates a length equals to zero. The UAS services not allowed indication indicates that the requested UAS services are not allowed by the network. If the container identifier contents field is not empty, it shall be ignored.

When the container identifier indicates service-level-AA container with the length of two octets, the container identifier contents field contains the service-level-AA container. The conditions under which this PCO parameter can be used are specified in 3GPP TS 24.301 [120]. The service-level-AA container is coded as the value part of the service-level-AA container information element as specified in subclause 9.11.2.10 of 3GPP TS 24.501 [167]. See NOTE 2.

When the container identifier indicates EDC support indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS supports EDC as specified in 3GPP TS 23.548 [182]. The usage of EDC support indicator is specified in 3GPP TS 24.501 [167].

When the container identifier indicates EDC usage allowed indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the network allows use of EDC as specified in 3GPP TS 23.548 [182]. The usage of EDC usage allowed indicator is specified in 3GPP TS 24.501 [167].

When the container identifier indicates EDC usage required indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the network requires use of EDC as specified in 3GPP TS 23.548 [182]. The usage of EDC usage required indicator is specified in 3GPP TS 24.501 [167].

When the container identifier indicates MS support of MAC address range in 5GS indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS supports a "destination MAC address range type" packet filter component and a "source MAC address range type" packet filter component specified in 3GPP TS 24.501 [167].

When the container identifier indicates Network support of MAC address range in 5GS indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the network supports a "destination MAC address range type" packet filter component and a "source MAC address range type" packet filter component specified in 3GPP TS 24.501 [167].

When the container identifier indicates SDNAEPC support indicator, the container identifier contents field is empty and the length of container identifier contents indicates a length equal to zero. If the container identifier contents field is not empty, it shall be ignored. This information indicates that the MS supports secondary DN authentication and authorization over EPC as specified in 3GPP TS 24.301 [120].

When the container identifier indicates SDNAEPC EAP message with the length of two octets, the container identifier contents field contains the EAP message used for secondary DN authentication and authorization over EPC if the MS has indicated that it supports secondary DN authentication and authorization over EPC as specified in 3GPP TS 24.301 [120]. The SDNAEPC EAP message is coded as the value part of the EAP message information element as specified in subclause 9.11.2.2 of 3GPP TS 24.501 [167]. See NOTE 2.

When the container identifier indicates operator specific use, the Container contents starts with MCC and MNC of the operator providing the relevant application and can be followed by further application specific information. The coding of MCC and MNC is as in octet 2 to 4 of the Location Area Identification information element in subclause 10.5.1.3.

8

7

6

5

4

3

2

1

Additional exception reports (AER) (octet 1)

8

7

6

5

4

3

2

1

Uplink time unit (octet 1)

8

7

6

5

4

3

2

1

Maximum uplink rate allowed (octet 1 to octet 3) is a binary coded representation of the maximum allowed number of messages the UE is allowed to send before the validity period of the initial small data rate control parameters expires.

8

7

6

5

4

3

2

1

PVS IPv4 Address (octet 1 to octet 4) is a binary coded representation of the IPv4 Address of the PVS.

DNN indicator value (octet 5, bit 1)

Bit

1

0 DNN absent

1 DNN present

If the DNN indicator bit is set to "DNN present", the DNN field is present. If the DNN indicator bit is set to "DNN absent", the DNN field is absent.

S-NSSAI indicator value (octet 5, bit 2)

Bit

2

0 S-NSSAI absent

1 S-NSSAI present

If the S-NSSAI indicator bit is set to " S-NSSAI present", the S-NSSAI field is present. If the S-NSSAI indicator bit is set to " S-NSSAI absent", the S-NSSAI field is absent.

8

7

6

5

4

3

2

1

PVS IPv6 Address (octet 1 to octet 16) is a binary coded representation of the IPv6 Address of the PVS.

8

7

6

5

4

3

2

1

PVS name (octet 1) length indicates the length of the PVS name.

PVS name (octet 2 to m) indicates the FQDN of the PVS which is a fully qualified domain name according to DNS naming conventions (see 3GPP TS 23.003 [10]).

8

7

6

5

4

3

2

1

Extended protocol configuration options contents (octet 4 to octet n); Max value of 65535 octets

8

7

6

5

4

3

2

1

Length of PDP address contents (octet 2)

If the value of octet 2 equals 0000 0010, then:

– No PDP address is included in this information element; and

– If the PDP type is IP, dynamic addressing is applicable.

NOTE: For PPP no address is required in this information element.

PDP type organisation (octet 3)
Bits
4 3 2 1
In MS to network direction :
0 0 0 0 ETSI allocated address
0 0 0 1 IETF allocated address
1 1 1 1 Empty PDP type

All other values are reserved.

In network to MS direction :
0 0 0 0 ETSI allocated address
0 0 0 1 IETF allocated address

All other values are reserved.

If bits 4,3,2,1 of octet 3 are coded 0 0 0 0
PDP type number value (octet 4)
Bits
8 7 6 5 4 3 2 1
0 0 0 0 0 0 0 0 Reserved, used in earlier version of this protocol
0 0 0 0 0 0 0 1 PDP-type PPP
0 0 0 0 0 0 1 0 non IP
All other values are reserved
in this version of the protocol.

If bits 4,3,2,1 of octet 3 are coded 0 0 0 1
PDP type number value (octet 4)
Bits
8 7 6 5 4 3 2 1
0 0 1 0 0 0 0 1 IPv4 address
0 1 0 1 0 1 1 1 IPv6 address
1 0 0 0 1 1 0 1 IPv4v6 address

All other values shall be interpreted as IPv4 address
in this version of the protocol.

In MS to network direction:
If bits 4,3,2,1 of octet 3 are coded 1 1 1 1
PDP type number value (octet 4)
bits 8 to 1 are spare and shall be coded all 0.

Octet 3, bits 8, 7, 6, and 5 are spare and shall be coded all 0.

8

7

6

5

4

3

2

1

8

7

6

5

4

3

2

1

Re-attempt indicator

RATC (octet 3, bit 1)

0 MS is allowed to re-attempt the procedure in S1 mode

1 MS is not allowed to re-attempt the procedure in S1 mode

EPLMNC (octet 3, bit 2)

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

1 MS 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.

8

7

6

5

4

3

2

1

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 0 0 MBMS bearer capabilities insufficient for the service

0 0 0 1 1 0 0 1 LLC or SNDCP failure(A/Gb mode only)
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 PDP address or PDP type
0 0 0 1 1 1 0 1 User authentication failed
0 0 0 1 1 1 1 0 Activation rejected by GGSN, Serving GW or PDN GW

0 0 0 1 1 1 1 1 Activation 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 NSAPI already used (not sent)

0 0 1 0 0 1 0 0 Regular deactivation

0 0 1 0 0 1 0 1 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 0 Feature not supported

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 Unknown PDP context

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 PDP context without TFT already activated

0 0 1 0 1 1 1 1 Multicast group membership time-out

0 0 1 1 0 0 0 0 Request rejected, BCM violation

0 0 1 1 0 0 1 0 PDP type IPv4 only allowed

0 0 1 1 0 0 1 1 PDP type IPv6 only allowed

0 0 1 1 1 0 0 1 PDP type IPv4v6 only allowed

0 0 1 1 1 0 1 0 PDP type non IP only allowed

0 0 1 1 0 1 0 0 Single address bearers only allowed

0 0 1 1 1 0 0 0 Collision with network initiated request

0 0 1 1 1 1 0 0 Bearer handling not supported

0 1 0 0 0 0 0 1 Maximum number of PDP contexts 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 transaction identifier 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 PDP context

0 1 1 1 0 0 0 1 Multiple accesses to a PDN connection not allowed

Any other value received by the mobile station 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: The listed cause values are defined in Annex I

8

7

6

5

4

3

2

1

SM cause 2 value is coded as octet 2 of the SM cause information element.

8

7

6

5

4

3

2

1

8

7

6

5

4

3

2

1

LLC SAPI value (octet 2)

Bit

4 3 2 1

0 0 0 0 LLC SAPI not assigned

0 0 1 1 SAPI 3

0 1 0 1 SAPI 5

1 0 0 1 SAPI 9

1 0 1 1 SAPI 11

All other values are reserved.

8

7

6

5

4

3

2

1

Tear down indicator(TDI) flag (octet 1)

Bit

1

0 tear down not requested

1 tear down requested

8

7

6

5

4

3

2

1

Packet Flow Identifier value (octet 3)

Bits

7 6 5 4 3 2 1

0 0 0 0 0 0 0 Best Effort
0 0 0 0 0 0 1 Signaling
0 0 0 0 0 1 0 SMS

0 0 0 0 0 1 1 TOM8

0 0 0 0 1 0 0 }
to } reserved
0 0 0 0 1 1 1 }

0 0 0 1 0 0 0 }
to } dynamically assigned
1 1 1 1 1 1 1 }

8

7

6

5

4

3

2

1

8

7

6

5

4

3

2

1

8

7

6

5

4

3

2

1

8

7

6

5

4

3

2

1

TFT operation code (octet 3)
Bits
8 7 6

0 0 0 Ignore this IE
0 0 1 Create new TFT

0 1 0 Delete existing TFT

0 1 1 Add packet filters to existing TFT

1 0 0 Replace packet filters in existing TFT

1 0 1 Delete packet filters from existing TFT

1 1 0 No TFT operation

1 1 1 Reserved

The TFT operation code "No TFT operation" shall be used if a parameters list is included but no packet filter list is included in the traffic flow template information element.

The TFT operation code "Ignore this IE" shall be used by the MS if the Traffic flow aggregate 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 3GPP TS 24.301 [120], subclauses 6.5.3.2 and 6.5.4.2). If the TFT operation code indicates "Ignore this IE", the MS shall also set the E bit and the number of packet filters to zero.

If the TFT operation code is set to "Ignore this IE" and the E bit and the number of packet filters to zero, then the network shall ignore the contents of the traffic flow template information element.

E bit (bit 5 of octet 3)

The E bit indicates if a parameters list is included in the TFT IE and it is encoded as follows:

0 parameters list is not included

1 parameters list is included

Number of packet filters (bits 1 to 4 of octet 3)

The number of packet filters contains the binary coding for the number of packet filters in the packet filter list. The number of packet filters field is encoded in bits 4 through 1 of octet 3 where bit 4 is the most significant and bit 1 is the least significant bit. For the "delete existing TFT" operation and for the "no TFT operation", the number of packet filters shall be coded as 0. For all other operations, the number of packet filters shall be greater than 0 and less than or equal to 15.

Packet filter list (octets 4 to z)

The packet filter list contains a variable number of packet filters. For the "delete existing TFT" operation and the "no TFT operation", the packet filter list shall be empty.

For the "delete packet filters from existing TFT" operation, the packet filter list shall contain a variable number of packet filter identifiers. This number shall be derived from the coding of the number of packet filters field in octet 3.

For the "create new TFT", "add packet filters to existing TFT" and "replace packet filters in existing TFT" operations, the packet filter list shall contain a variable number of packet filters. This number shall be derived from the coding of the number of packet filters field in octet 3.

Each packet filter is of variable length and consists of

– a packet filter identifier and direction (1 octet);
– a packet filter evaluation precedence (1 octet);

– the length of the packet filter contents (1 octet); and
– the packet filter contents itself (v octets).

The packet filter identifier field is used to identify each packet filter in a TFT. The least significant 4 bits are used.

The packet filter direction is used to indicate, in bits 5 and 6, for what traffic direction the filter applies:

00 – pre Rel-7 TFT filter
01 – downlink only
10 – uplink only
11 – bidirectional

Bits 8 through 7 are spare bits.

The packet filter evaluation precedence field is used to specify the precedence for the packet filter among all packet filters in all TFTs associated with this PDP address. Higher the value of the packet filter evaluation precedence field, lower the precedence of that packet filter is. The first bit in transmission order is the most significant bit.

The length of the packet filter contents field contains the binary coded representation of the length of the packet filter contents field of a packet filter. The first bit in transmission order is the most significant bit.

The packet filter contents field is of variable size and contains a variable number (at least one) of packet filter components. Each packet filter component shall be encoded as a sequence of a one octet packet filter component type identifier and a fixed length packet filter component value field. The packet filter component type identifier shall be transmitted first.

In each packet filter, there shall not be more than one occurrence of each packet filter component type. Among the "IPv4 local address type" and "IPv6 local address type" packet filter components, only one shall be present in one packet filter. Among the "IPv4 remote address type" and "IPv6 remote address type" packet filter components, only one shall be present in one packet filter. Among the "single local port type" and "local port range type" packet filter components, only one shall be present in one packet filter. Among the "single remote port type" and "remote port range type" packet filter components, only one shall be present in one packet filter. If the "Ethertype type" packet filter component is present in the packet filter and the "Ethertype type" packet filter component value is neither 0800H (for IPv4) nor 86DDH (for IPv6), no IP packet filter component shall be present in the packet filter.

The term "IP packet filter component" refers to "IPv4 remote address type", "IPv4 local address type", "IPv6 remote address/prefix length type", "IPv6 local address/prefix length type", "Protocol identifier/Next header type", "Single local port type", "Local port range type", "Single remote port type", "Remote port range type", "Security parameter index type", "Type of service/Traffic class type" and "Flow label type".

The term local refers to the MS and the term remote refers to an external network entity.

Packet filter component type identifier
Bits
8 7 6 5 4 3 2 1

0 0 0 1 0 0 0 0 IPv4 remote address type
0 0 0 1 0 0 0 1 IPv4 local address type
0 0 1 0 0 0 0 0 IPv6 remote address type
0 0 1 0 0 0 0 1 IPv6 remote address/prefix length type
0 0 1 0 0 0 1 1 IPv6 local address/prefix length type
0 0 1 1 0 0 0 0 Protocol identifier/Next header type
0 1 0 0 0 0 0 0 Single local port type
0 1 0 0 0 0 0 1 Local port range type
0 1 0 1 0 0 0 0 Single remote port type
0 1 0 1 0 0 0 1 Remote port range type
0 1 1 0 0 0 0 0 Security parameter index type
0 1 1 1 0 0 0 0 Type of service/Traffic class type
1 0 0 0 0 0 0 0 Flow label type
1 0 0 0 0 0 0 1 Destination MAC address type
1 0 0 0 0 0 1 0 Source MAC address type
1 0 0 0 0 0 1 1 802.1Q C-TAG VID type
1 0 0 0 0 1 0 0 802.1Q S-TAG VID type
1 0 0 0 0 1 0 1 802.1Q C-TAG PCP/DEI type
1 0 0 0 0 1 1 0 802.1Q S-TAG PCP/DEI type
1 0 0 0 0 1 1 1 Ethertype type

All other values are reserved.

The description and valid combinations of packet filter component type identifiers in a packet filter are defined in 3GPP TS 23.060 [74] subclause 15.3.2.

For "IPv4 remote address type", the packet filter component value field shall be encoded as a sequence of a four octet IPv4 address field and a four octet IPv4 address mask field. The IPv4 address field shall be transmitted first.

For "IPv4 local address type", the packet filter component value field shall be encoded as defined for "IPv4 remote address type".
Both the MS and network indication for support of the Local address in TFTs are required to use this packet filter component.

For "IPv6 remote address type", the packet filter component value field shall be encoded as a sequence of a sixteen octet IPv6 address field and a sixteen octet IPv6 address mask field. The IPv6 address field shall be transmitted first.

For "IPv6 remote address/prefix length type", the packet filter component value field shall be encoded as a sequence of a sixteen octet IPv6 address field and one octet prefix length field. The IPv6 address field shall be transmitted first.
This parameter shall be used, instead of IPv6 remote address type, when both the MS and network indication for support of the Local address in TFT are present.

For "IPv6 local address/prefix length type", the packet filter component value field shall be encoded as defined for "IPv6 remote address /prefix length".

Both the MS and network indication for support of the Local address in TFTs are required to use this packet filter component.

NOTE 1: Local IP address and mask can be used when IPv6 prefix delegation is used (see 3GPP TS 23.060 [74] subclause  9.2.1.2).

NOTE 2: After inter-system change from N1 mode to S1 mode, the MS operating in single-registration mode in a network supporting N26 interface shall deem that Local address in TFT is supported by the network on the PDN connection corresponding to the PDU session (see subclause 6.1.4.1 of 3GPP TS 24.501 [167]).

For "Protocol identifier/Next header type", the packet filter component value field shall be encoded as one octet which specifies the IPv4 protocol identifier or IPv6 next header.

For "Single local port type" and "Single remote port type", the packet filter component value field shall be encoded as two octet which specifies a port number.

For "Local port range type" and "Remote port range type", the packet filter component value field shall be encoded as a sequence of a two octet port range low limit field and a two octet port range high limit field. The port range low limit field shall be transmitted first.

For "Security parameter index", the packet filter component value field shall be encoded as four octet which specifies the IPSec security parameter index.

For "Type of service/Traffic class type", the packet filter component value field shall be encoded as a sequence of a one octet Type-of-Service/Traffic Class field and a one octet Type-of-Service/Traffic Class mask field. The Type-of-Service/Traffic Class field shall be transmitted first.

For "Flow label type", the packet filter component value field shall be encoded as three octet which specifies the IPv6 flow label. The bits 8 through 5 of the first octet shall be spare whereas the remaining 20 bits shall contain the IPv6 flow label.

Parameters list (octets z+1 to v)

For "destination MAC address type" and "source MAC address type", the packet filter component value field shall be encoded as 6 octets which specify a MAC address. When the packet filter direction field indicates "bidirectional", the destination MAC address is the remote MAC address and the source MAC address is the local MAC address.

For "802.1Q C-TAG VID type", the packet filter component value field shall be encoded as two octets which specify the VID of the customer-VLAN tag (C-TAG). The bits 8 through 5 of the first octet shall be spare whereas the remaining 12 bits shall contain the VID. If there are more than one C-TAG in the Ethernet frame header, the outermost C-TAG is evaluated.

For "802.1Q S-TAG VID type", the packet filter component value field shall be encoded as two octets which specify the VID of the service-VLAN tag (S-TAG). The bits 8 through 5 of the first octet shall be spare whereas the remaining 12 bits shall contain the VID. If there are more than one S-TAG in the Ethernet frame header, the outermost S-TAG is evaluated.

For "802.1Q C-TAG PCP/DEI type", the packet filter component value field shall be encoded as one octet which specifies the 802.1Q C-TAG PCP and DEI. The bits 8 through 5 of the octet shall be spare, the bits 4 through 2 contain the PCP and bit 1 contains the DEI. If there are more than one C-TAG in the Ethernet frame header, the outermost C-TAG is evaluated.

For "802.1Q S-TAG PCP/DEI type", the packet filter component value field shall be encoded as one octet which specifies the 802.1Q S-TAG PCP. The bits 8 through 5 of the octet shall be spare, the bits 4 through 2 contain the PCP and bit 1 contains the DEI. If there are more than one S-TAG in the Ethernet frame header, the outermost S-TAG is evaluated.

For "ethertype type", the packet filter component value field shall be encoded as two octets which specify an ethertype.

The parameters list contains a variable number of parameters that may be transferred. If the parameters list is included, the E bit is set to 1; otherwise, the E bit is set to 0.

Each parameter included in the parameters list is of variable length and consists of:

– a parameter identifier (1 octet);
– the length of the parameter contents (1 octet); and
– the parameter contents itself (v octets).

The parameter identifier field is used to identify each parameter included in the parameters list and it contains the hexadecimal coding of the parameter identifier. Bit 8 of the parameter identifier field contains the most significant bit and bit 1 contains the least significant bit. In this version of the protocol, the following parameter identifiers are specified:

– 01H (Authorization Token);

– 02H (Flow Identifier); and
– 03H (Packet Filter Identifier).

If the parameters list contains a parameter identifier that is not supported by the receiving entity the corresponding parameter shall be discarded.

The length of parameter contents field contains the binary coded representation of the length of the parameter contents field. The first bit in transmission order is the most significant bit.

When the parameter identifier indicates Authorization Token, the parameter contents field contains an authorization token, as specified in 3GPP TS 29.207 [100]. The first octet is the most significant octet of the authorization token and the last octet is the least significant octet of the authorization token.

The parameters list shall be coded in a way that an Authorization Token (i.e. a parameter with identifier 01H) is always followed by one or more Flow Identifiers (i.e. one or more parameters with identifier 02H).

If the parameters list contains two or more consecutive Authorization Tokens without any Flow Identifiers in between, the receiver shall treat this as a semantical TFT error.

When the parameter identifier indicates Flow Identifier, the parameter contents field contains the binary representation of a flow identifier. The Flow Identifier consists of four octets. Octets 1 and 2 contains the Media Component number as specified in 3GPP TS 29.207 [100]. Bit 1 of octet 2 is the least significant bit, and bit 8 of octet 1 is the most significant bit. Octets 3 and 4 contains the IP flow number as specified in 3GPP TS 29.207 [100]. Bit 1 of octet 4 is the least significant bit, and bit 8 of octet 3 is the most significant bit.

When the parameter identifier indicates Packet Filter Identifier, the parameter contents field contains the binary representation of one or more packet filter identifiers. Each packet filter identifier is encoded in one octet, in the 4 least significant bits. This parameter is used by the MS and the network to identify one or more packet filters in a TFT when modifying the QoS of a PDP context without modifying the packet filter itself.

8

7

6

5

4

3

2

1

MBMS Service ID (octet 3, 4 and 5)

In the MBMS Service ID field bit 8 of octet 3 is the most significant bit and bit 1 of octet 5 the least significant bit.

The coding of the MBMS Service ID is the responsibility of each administration. Coding using full hexadecimal representation may be used. The MBMS Service ID consists of 3 octets.

MCC, Mobile country code (octet 6, octet 7 bits 1 to 4)

The MCC field is coded as in ITU-T Rec. E.212 [46], Annex A.

MNC, Mobile network code (octet 7 bits 5 to 8, octet 8)

The coding of this field is the responsibility of each administration but BCD coding shall be used. The MNC shall consist of 2 or 3 digits. If a network operator decides to use only two digits in the MNC, bits 5 to 8 of octet 7 shall be coded as "1111".

8

7

6

5

4

3

2

1

8

7

6

5

4

3

2

1

Bits 1 to 8 of octet 3 are spare and shall be coded as "0".

NOTE: The reason for defining the information element is to have a transparent mechanism in the SGSN available from the introduction of MBMS. This will ensure that MS – GGSN communication is possible if new MBMS bearer service related parameters are defined.

8

7

6

5

4

3

2

1

Enhanced NSAPI value (octet 2, bits 1 to 7)

8

7

6

5

4

3

2

1

Request type value (octet 1)

8

7

6

5

4

3

2

1

Notification indicator value (octet 3)

8

7

6

5

4

3

2

1

Connectivity type value (octet 1)

8

7

6

5

4

3

2

1

E-UTRAN offload acceptability value (octet 1)

8

7

6

5

4

3

2

1

NBIFOM container contents field contains the NBIFOM parameter list as defined in 3GPP TS 24.161 [158], subclause 6.1.