Cause

M

See NOTE 2 and NOTE 4.

Cause

0

Change Reporting Action

C

This IE shall be included on the S5/S8 and S4/S11 interfaces with the appropriate Action field if the location Change Reporting mechanism is to be started or stopped for this subscriber in the SGSN/MME.

Change Reporting Action

0

CSG Information Reporting Action

CO

This IE shall be included on the S5/S8 and S4/S11 interfaces with the appropriate Action field if the CSG Info reporting mechanism is to be started or stopped for this subscriber in the SGSN/MME.

CSG Information Reporting Action

0

H(e)NB Information Reporting

CO

This IE shall be included on the S5/S8 and S4/S11 interfaces with the appropriate Action field if H(e)NB information reporting is to be started or stopped (during a TAU/RAU with SGW change if started earlier) for the PDN connection in the SGSN/MME.

H(e)NB Information Reporting

0

Sender F-TEID for Control Plane

C

This IE shall be sent on the S11/S4 interfaces. For the S5/S8/ S2a/S2b interfaces it is not needed because its content would be identical to the IE PGW S5/S8/ S2a/S2b F-TEID for PMIP based interface or for GTP based Control Plane interface.

F-TEID

0

PGW S5/S8/ S2a/S2b F-TEID for PMIP based interface or for GTP based Control Plane interface

C

The PGW shall include this IE on the S5/S8 interfaces during the Initial Attach, a Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN, UE requested PDN connectivity, PDP Context Activation and a Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN procedures.

If the SGW receives this IE it shall forward the IE to MME/S4-SGSN on the S11/S4 interface.

This IE shall include the TEID for GTP based S5/S8 case and the uplink GRE key in the PMIP based S5/S8 case.

For PMIP based S5/S8, this IE shall be included on the S11/S4 interface and shall contain the PGW S5/S8 IP address for control plane; the same IP address shall be used for both control plane and the user plane communication if the Bearer Context IE does not contain a S5/S8-U PGW F-TEID IE. See NOTE 7.

The PGW shall include this IE on the S2b interface during the Attach with GTP on S2b, UE initiated Connectivity to Additional PDN with GTP on S2b, Handover to Untrusted Non-3GPP IP Access with GTP on S2b procedures and Initial Attach for emergency session (GTP on S2b).

The PGW shall include this IE on the S2a interface during the Initial Attach in WLAN on GTP S2a, an Initial Attach in WLAN for Emergency Service on GTP S2a, UE initiated Connectivity to Additional PDN with GTP on S2a and Handover to TWAN with GTP on S2a procedures

See NOTE 6.

F-TEID

1

PDN Address Allocation (PAA)

C

This IE shall be included on the S5/S8, S4/S11 and S2a/S2b interfaces for the E-UTRAN initial attach, a Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN, PDP Context Activation, a Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN, UE requested PDN connectivity, Attach with GTP on S2b, UE initiated Connectivity to Additional PDN with GTP on S2b, Handover to Untrusted Non-3GPP IP Access with GTP on S2b, Initial Attach for emergency session (GTP on S2b), Initial Attach in WLAN on GTP S2a, Initial Attach in WLAN for Emergency Service on GTP S2a, UE initiated Connectivity to Additional PDN with GTP on S2a and Handover to TWAN with GTP on S2a.

The PDN type field in the PAA shall be set to IPv4, or IPv6 or IPv4v6, Non-IP or Ethernet by the PGW. See NOTE4.

For the S4/S11 and S5/S8 interfaces, if the PGW uses DHCPv4 for IPv4 address allocation, the IPv4 address field shall be set to 0.0.0.0; otherwise, the IPv4 address field shall be set to non-zero value as specified in 3GPP TS 23.401 [3] and 3GPP TS 23.402 [45].

When assigning an IPv6 address the PGW shall send a non-zero Interface Identifier. See NOTE 8.

For Non-IP or Ethernet PDN connections, the PDN Address and Prefix field shall not be present.

PAA

0

APN Restriction

C

This IE shall be included on the S5/S8 and S4/S11 interfaces in the E-UTRAN initial attach, a Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN, PDP Context Activation, a Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN and UE Requested PDN connectivity procedures.

This IE shall also be included on S4/S11 during the Gn/Gp SGSN to S4 SGSN/MME RAU/TAU procedures.

This IE denotes the restriction on the combination of types of APN for the APN associated with this EPS bearer Context.

APN Restriction

0

Aggregate Maximum Bit Rate (APN-AMBR)

C

This IE represents the APN-AMBR. It shall be included on the S5/S8, S4/S11 and S2a/S2b interfaces if the received APN-AMBR has been modified by the PCRF.

AMBR

0

Linked EPS Bearer ID

C

This IE shall be sent on the S4/S11 interfaces during Gn/Gp SGSN to S4-SGSN/MME RAU/TAU procedure to identify the default bearer the PGW selects for the PDN Connection.

EBI

0

Protocol Configuration Options (PCO)

C

If ePCO is not supported by the UE or the network, and if the PGW decides to return PCO to the UE during the Attach, PDN connectivity or Handover to 3GPP access procedures, PGW shall send PCO to SGW. If SGW receives the PCO IE, SGW shall forward it to MME/SGSN.

PCO

0

CO

For trusted WLAN access, if single-connection mode or multiple-connection mode is used, the PGW may include this IE over the S2a interface to send PCO to the UE.

Bearer Contexts created

M

EPS bearers corresponding to Bearer Contexts sent in request message. Several IEs with the same type and instance value may be included on the S5/S8 and S4/S11 as necessary to represent a list of Bearers. One single IE shall be included on the S2a/S2b interface.

One bearer shall be included for E-UTRAN Initial Attach, a Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN, PDP Context Activation, a Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN, UE Requested PDN Connectivity , Attach with GTP on S2b, UE initiated Connectivity to Additional PDN with GTP on S2b, Handover to Untrusted Non-3GPP IP Access with GTP on S2b, Initial Attach for emergency session (GTP on S2b), Initial Attach in WLAN on GTP S2a, an Initial Attach in WLAN for Emergency Service on GTP S2a, UE initiated Connectivity to Additional PDN with GTP on S2a and Handover to TWAN with GTP on S2a.

One or more created bearers shall be included for a Handover/TAU/RAU with an SGW change. See NOTE 2.

Bearer Context

0

Bearer Contexts marked for removal

C

EPS bearers corresponding to Bearer Contexts to be removed that were sent in the Create Session Request message.

For each of those bearers an IE with the same type and instance value shall be included on the S4/S11 interfaces.

Bearer Context

1

Recovery

C

This IE shall be included on the S4/S11, S5/S8 and S2a/S2b interfaces if contacting the peer for the first time

Recovery

0

Charging Gateway Name

C

When Charging Gateway Function (CGF) Address is configured, the PGW shall include this IE on the S5 interface. See NOTE 1.

FQDN

0

Charging Gateway Address

C

When Charging Gateway Function (CGF) Address is configured, the PGW shall include this IE on the S5 interface. See NOTE 1.

IP Address

0

PGW-FQ-CSID

C

This IE shall be included by the PGW on the S5/S8 and S2a/S2b interfaces and, when received from S5/S8 be forwarded by the SGW on the S11 interface according to the requirements in 3GPP TS 23.007 [17].

FQ-CSID

0

SGW-FQ-CSID

C

This IE shall be included by the SGW on the S11 interface according to the requirements in 3GPP TS 23.007 [17].

FQ-CSID

1

SGW LDN

O

This IE is optionally sent by the SGW to the MME/SGSN on the S11/S4 interfaces (see 3GPP TS 32.423 [44]), when communicating the LDN to the peer node for the first time.

Local Distinguished Name (LDN)

0

PGW LDN

O

This IE is optionally included by the PGW on the S5/S8 and S2a/S2b interfaces (see 3GPP TS 32.423 [44]), when communicating the LDN to the peer node for the first time.

Local Distinguished Name (LDN)

1

PGW Back-Off Time

O

This IE may be included on the S5/S8 and S4/S11 interfaces when the PDN GW rejects the Create Session Request with the cause "APN congestion". It indicates the time during which the MME or S4-SGSN should refrain from sending subsequent PDN connection establishment requests to the PGW for the congested APN for services other than Service Users/emergency services.

See NOTE 3.

EPC Timer

0

Additional Protocol Configuration Options (APCO)

CO

If multiple authentications are supported by the PGW and if PGW received the Additional Protocol Configuration Options IE in the Create Session Request, the PGW shall include this IE on the S2b interface and perform the corresponding procedures as specified for PAP and CHAP authentication of the UE with external networks in 3GPP TS 33.402 [50].

Additional Protocol Configuration Options (APCO)

0

O

If the PGW supports the Additional Protocol Configuration Options IE and if the PGW has received the Additional Protocol Configuration Options IE with the "DNS IPv4/IPv6 Server Address Request" parameter in the Create Session Request over S2b interface, the PGW may include this IE over the S2b interface with the "DNS IPv4/IPv6 Server Address" parameter as specified in 3GPP TS 24.008 [5].

If the PGW supports the Additional Protocol Configuration Options IE and if the PGW has received the Additional Protocol Configuration Options IE with the P-CSCF IPv4 Address Request, or P-CSCF IPv6 Address Request or both parameters in the Create Session Request over the S2b interface, the PGW may include this IE over the S2b interface with the P-CSCF IPv4 Address, or P-CSCF IPv6 Address, or both parameters respectively as specified in 3GPP TS 24.008 [5].

If the PGW supports the Additional Protocol Configuration Options IE and if the PGW has received the Additional Protocol Configuration Options IE with a PDU session ID in the Create Session Request over the S2b interface, the PGW may include this IE over the S2b interface with the S-NSSAI and the PLMN ID that the S-NSSAI relates to as specified in 3GPP TS 24.302 [63] and 3GPP TS 24.008 [5].

O

The PGW may include this IE on the S2a interface to provide the TWAN with additional IP configuration parameters (e.g. DNS server), if a corresponding request was received in the Create Session Request message.

Trusted WLAN IPv4 Parameters

CO

The PGW shall include this IE on the S2a interface to a Trusted WLAN Access if PDN Type in the PAA is set to IPv4 or IPv4v6 and the transparent single-connection mode is used as specified in 3GPP TS 23.402 [45].

This IE shall include:

• The Subnet Prefix Length of the subnet from which the PGW allocates the UE’s IPv4 address.
• The IPv4 Default Router Address which belongs to the same subnet as the IPv4 address allocated to the UE.

IPv4 Configuration Parameters (IP4CP)

0

Indication Flags

CO

This IE shall be included if any one of the applicable flags is set to 1.

Applicable flags are:

• PDN Pause Support Indication: this flag shall be set to 1 on the S5/S8 interface if the PGW supports the PGW Pause of Charging procedure.
• PDN Pause Enable Indication: this flag shall be set to 1 on the S5/S8 interface if the PGW enables the SGW to use the PGW Pause of Charging procedure for this PDN connection.
• Associate OCI with PGW node’s identity: The PGW shall set this flag to 1 on the S5/S8 interface or S2a/S2b interface if it has included the "PGW’s Overload Control Information" and if this information is to be associated with the node identity (i.e. FQDN or the IP address received from the HSS or DNS during the PGW selection) of the serving PGW. This flag shall be set to 1 by the PGW if the "PGW’s Overload Control Information" is included and the Cause IE is set to a rejection cause code. The SGW shall set this flag on the S11/S4 interface if it supports the overload control feature and if the flag is set on the S5/S8 interface.
• Associate OCI with SGW node’s identity: The SGW shall set this flag to 1 on the S11/S4 interface if it has included the "SGW’s Overload Control Information" and if this information is to be associated with the node identity (i.e. FQDN or the IP address received from the DNS during the SGW selection) of the serving SGW. This flag shall be set to 1 by the SGW if the "SGW’s Overload Control Information" is included and the Cause IE is set to a rejection cause code.
• Delay Tolerant Connection Indication: the flag shall be set to 1 on the S5/S8 and S11/S4 interface if the PDN connection is "Delay Tolerant" (see clause 8.12).
• Triggering SGSN initiated PDP Context Creation/Modification Indication: this flag shall be set to 1 on the S5/S8 interfaces if the network-initiated NBIFOM mode is used for this PDN connection. The SGW shall set this flag on the S4 interface if it supports the NBIFOM feature and the flag is set on the S5/S8 interface.
• Notify Start Pause of charging via User plane Support Indication: this flag shall be set to 1 on the S5/S8 interface if PDN Pause Enable Indication is set to "1" and if the PGW-C and PGW-U support the Notify Start Pause of Charging via user plane feature as specified in clause 5.30 of 3GPP TS 29.244 [80].

Indication

0

Presence Reporting Area Action

CO

This IE shall be included on the S5/S8 and S11/S4 interfaces with the appropriate Action field if reporting changes of UE presence in a Presence Routing Area is to be started, stopped or modified for this subscriber in the MME/SGSN.

Several IEs with the same type and instance value may be included as necessary to represent a list of Presence Reporting Area Actions. One IE shall be included per PRA to be started, stopped or modified.

Presence Reporting Area Action

0

PGW’s node level Load Control Information

O

The PGW may include this IE on the S5/S8 or S2a/S2b interface, providing its node level load information, if the load control feature is supported by the PGW and is activated for the PLMN to which the access network node, i.e. MME/S4-SGSN for 3GPP access network, ePDG/TWAN for non-3GPP access network, belongs (see clause 12.2.6).

Load Control Information

0

CO

If the SGW receives this IE and if it supports the load control feature, it shall forward it to the MME/S4-SGSN on the S11/S4 interface.

PGW’s APN level Load Control Information

O

The PGW may include this IE on the S5/S8 or S2a/S2b interface, providing APN level load information, if the APN level load control feature is supported by the PGW and is activated for the PLMN to which the access network node, i.e. MME/S4-SGSN for 3GPP access network, ePDG/TWAN for non-3GPP access based network, belongs (see clause 12.2.6).

When present, the PGW shall provide one or more instances of this IE, up to maximum of 10, with the same type and instance value, each representing the load information for a list of APN(s).

See NOTE 9, NOTE 11.

Load Control Information

1

CO

If the SGW receives this IE and if it supports APN level load control feature, it shall forward it to the MME/S4-SGSN on the S11/S4 interface.

SGW’s node level Load Control Information

O

The SGW may include this IE, over the S11/S4 interface if the load control feature is supported by the SGW and is activated in the network (see clause 12.2.6).

When present, the SGW shall provide only one instance of this IE, representing its node level load information.

Load Control Information

2

PGW’s Overload Control Information

O

During an overload condition, the PGW may include this IE on the S5/S8 or S2a/S2b interface, if the overload control feature is supported by the PGW and is activated for the PLMN to which the access network node, i.e. MME/S4-SGSN for 3GPP access based network, ePDG/TWAN for non-3GPP access based network, belongs (see clause 12.3.11).

When present, the PGW shall provide:

• node level overload control, in one instance of this IE; and/or
• APN level overload control , in one or more instances of this IE, up to maximum of 10, with the same type and instance value, each representing the overload information for a list of APN(s).

See NOTE 10, NOTE 12.

Overload Control Information

0

CO

If the SGW receives this IE and if it supports the overload control feature, it shall forward it to the MME/S4-SGSN on the S11/S4 interface.

SGW’s Overload Control Information

O

During an overload condition, the SGW may include this IE over the S11/S4 interface if the overload control feature is supported by the SGW and is activated in the network (see clause 12.3.11).

When present, the SGW shall provide only one instance of this IE, representing its overload information.

Overload Control Information

1

NBIFOM Container

CO

This IE shall be included on the S5/S8 or S2a/S2b interfaces if the PGW needs to send NBIFOM informationas specified in 3GPP TS 23.161 [71].

The Container Type shall be set to 4.

F-Container

0

CO

If the SGW receives an NBIFOM Container from the PGW, the SGW shall forward this IE to the MME/S4-SGSN on the S11/S4 interface.

PDN Connection Charging ID

CO

The PGW shall include this IE on the S5/S8 or S2a/S2b interfaces, during an Initial Attach, Initial PDN connection establishment, or Addition of an access procedures, when using NBIFOM, as specified in 3GPP TS 23.161 [71].

Charging ID

0

Extended Protocol Configuration Options (ePCO)

CO

If the PGW decides to return ePCO to the UE during an Initial Attach, UE requested PDN Connectivity procedure, and if the PGW supports the ePCO and the EPCOSI flag is set to 1 in the Create Session Request message, the PGW shall send ePCO to the SGW.

If the SGW receives the ePCO IE, the SGW shall forward it to the MME.

See NOTE 13.

ePCO

0

PGW node name

CO

This IE shall be included over S5/S8 interfaces by the PGW when it receives the corresponding Create Session Request message with the CSRMFI flag set to "1", and the creation of the PDN connection has been accepted.

If the SGW receives this IE, the SGW shall forward it to the MME over S11 interface. (See NOTE 14)

FQDN

1

SGi PtP Tunnel Address

CO

This IE shall be included on the S5/S8 and S4/S11 interfaces, if the PDN Type is "Non-IP" and SGi PtP tunnelling based on UDP/IP is used (see clause 4.3.17.8.3.3.2 of 3GPP TS 23.401 [3]).

When present, the IE shall contain the IPv4 or IPv6 address, and optionally the UDP port, that is allocated for the SGi PtP tunnel based on UDP/IP.

SGi PtP Tunnel Address

0

PGW Change Info

CO

This IE shall be included on the S5/S8/S2b interface by the PGW if it supports the Restoration of PDN connections after an PGW-C/SMF Change procedure as specified in clause 31 of 3GPP TS 23.007 [17] and if the "Restoration of PDN connections after an PGW-C/SMF Change Support Indication" was set to 1 in the request.

An SGW that supports the Restoration of PDN connections after an PGW-C/SMF Change procedure as specified in clause 31 of 3GPP TS 23.007 [17], shall transparently forward this IE over the S11 interface if it is received in a Create Session Response or a Modify Bearer Response message from the PGW over S5/S8.

PGW Change Info

0

Alternative PGW-C/SMF FQDN

O

This IE may be included by the PGW on the S5/S8 interfaces, when the PGW rejects the Create Session Request with the cause "PGW mismatch with network slice subscribed by the UE".

If the SGW receives this IE, the SGW shall forward it to the MME over the S11 interface.

When present, the IE shall contain the FQDN of the other PGW that the MME should use for establishing the PDN connection.

Several IEs with the same type and instance value may be included to represent a list of Alternative PGW-C/SMF FQDNs. (See NOTE 15)

FQDN

3

Alternative PGW-C/SMF IP Address

O

This IE may be included by the PGW on the S5/S8 interfaces, when the PGW rejects the Create Session Request with the cause "PGW mismatch with network slice subscribed by the UE".

If the SGW receives this IE, the SGW shall forward it to the MME over the S11 interface.

When present, the IE shall contain the IP Address of the other PGW that the MME should use for establishing the PDN connection.

Several IEs with the same type and instance value may be included to represent a list of Alternative PGW-C/SMF FQDNs. (See NOTE 15)

IP Address

1

UP Security Policy

CO

This IE shall be included on the S5/S8 and S11 interfaces in the E-UTRAN initial attach and UE Requested PDN connectivity procedures, if UP Integrity Protection is supported by the UE, MME and E-UTRAN (i.e. if the UPIPSI flag was set to 1) and if User Plane Integrity Protection policy is available for the PDN connection. When present, it shall indicate whether User Plane integrity protection is required, preferred or not needed for the traffic of the PDN connection.

UP Security Policy

0

Private Extension

O

This IE may be sent on the S5/S8, S4/S11 and S2a/S2b interfaces.

Private Extension

VS

NOTE1: Both Charging Gateway Name and Charging Gateway Address shall not be included at the same time. When both are available, the operator configures a preferred value.

NOTE2: If the SGW cannot accept any of the "Bearer Context Created" IEs within Create Session Request message, the SGW shall send the Create Session Response with appropriate reject Cause value.

NOTE 3: The last received value of the PGW Back-Off Time IE shall supersede any previous values received from that PGW and for this APN in the MME/SGSN.

NOTE4: 3GPP TS 23.401 [3] (see clause 5.3.1.1) and 3GPP TS 23.060 [35] (see clause 9.2.1) specify the handling of the cases when UE has requested IPv4v6 PDN Type, but PGW restricts the usage of IPv4v6 PDN Type.

NOTE 5: The conditions of presence of the IEs in the Create Session Response for the MME and S4-SGSN triggered Serving GW relocation (see clause 5.10.4 of 3GPP TS 23.401 [3] and clause 9.2.2.4 of 3GPP TS 23.060 [35]) are identical to those specified respectively for X2 handover with SGW relocation and for Enhanced Serving RNS Relocation with SGW relocation.

NOTE 6: The IP address and TEID/GRE key in "PGW S5/S8/ S2a/S2b F-TEID for PMIP based interface or for GTP based Control Plane interface" IE are only provided for the subsequent GTP-C initial messages related to this PDN connection and shall NOT be used for other PDN connections.

NOTE 7: For PMIP based S5/S8, the ‘S5/S8-U PGW F-TEID’ IE and the ‘PGW S5/S8/ S2a/S2b F-TEID for PMIP based interface or for GTP based Control Plane interface’ IE shall contain the same uplink GRE key; the Interface Type in these IEs shall be set to the value 9 (S5/S8 PGW PMIPv6 interface).

NOTE 8: The Interface Identifier value of zero is a reserved value (see IETF RFC 5453 [58]). Clause 5.3.1.2.2 of 3GPP TS 23.401 [3] specifies the mechanism for preventing UE’s link-local address collision with the PGW’s link-local address.

NOTE 9: The receiver, not supporting the APN level load control feature, shall ignore all the occurrence(s) of this IE, i.e. "Load Control Information" IE with instance number "1". The receiver, supporting the APN level load control feature and supporting the APN level load information for the maximum of 10 APNs, shall handle the APN level load information for the first 10 APNs and ignore any more APN level load information.

NOTE 10: The receiver, supporting the APN level overload information for the maximum of 10 APNs, shall handle the APN level overload information for the first 10 APNs and ignore any more APN level overload information.

NOTE 11: The APN level load information, provided within and across different instances of the "PGW’s APN level Load Control Information" IE(s) shall be limited to 10 different APNs.

NOTE 12: The APN level overload information, provided within and across different instances of the "PGW’s Overload Control Information" IE(s) shall be limited to 10 different APNs.

NOTE 13: The MME shall consider the presence of the ePCO IE in the Create Session Response message as an indication that the PGW and the SGW support the ePCO. The UE considers that the PGW supports ePCO when it receives an ePCO from the PGW.

NOTE 14: The MME shall update the PGW FQDN associated with this PDN connection using this IE.

NOTE 15: For a given alternative PGW, either the Alternative PGW-C/SMF FQDN IE or the Alternative PGW-C/SMF IP Address IE may be present, not both.

Octets 2 and 3

Length = n

Octets 4

Spare and Instance fields

Information elements

P

Condition / Comment

IE Type

Ins.

EPS Bearer ID

M

EBI

0

Cause

M

This IE shall indicate if the bearer handling was successful, and if not, it gives information on the reason. (NOTE 1, NOTE 2, NOTE 3)

Cause

0

S1-U SGW F-TEID

C

This IE shall be included on the S11 interface if the S1-U interface is used, i.e. if the S11-U Tunnel flag was not set in the Create Session Request. . See NOTE 6.

F-TEID

0

S4-U SGW F-TEID

C

This IE shall be included on the S4 interface if the S4-U interface is used.

F-TEID

1

S5/S8-U PGW F-TEID

C

For GTP-based S5/S8, this User Plane IE shall be included on S4/S11 and S5/S8 interfaces during the "E-UTRAN Initial Attach", a Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN, a "PDP Context Activation", a Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN or a "UE Requested PDN Connectivity".

F-TEID

2

For PMIP-based S5/S8, this IE shall be included on the S4/S11 interface during the "E-UTRAN Initial Attach", a Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN, a "PDP Context Activation", a Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN or a "UE Requested PDN Connectivity" if the PGW provided an alternate address for user plane, i.e. an IP address for user plane which is different from the IP address for control plane.

When present, this IE shall contain the alternate IP address for user plane and the uplink GRE key.

See NOTE 4 and NOTE 5.

S12 SGW F-TEID

C

This IE shall be included on the S4 interface if the S12 interface is used.

F-TEID

3

S2b-U PGW F-TEID

C

This IE (for user plane) shall be included on the S2b interface during the Attach with GTP on S2b, UE initiated Connectivity to Additional PDN with GTP on S2b, Handover to Untrusted Non-3GPP IP Access with GTP on S2b, and Initial Attach for emergency session (GTP on S2b).

F-TEID

4

S2a-U PGW F-TEID

C

This IE (for user plane) shall be included on the S2a interface during the Initial Attach in WLAN on GTP S2a, an Initial Attach in WLAN for Emergency Service on GTP S2a, UE initiated Connectivity to Additional PDN with GTP on S2a, and Handover to TWAN with GTP on S2a.

F-TEID

5

Bearer Level QoS

C

This IE shall be included on the S5/S8, S4/S11 and S2a/S2b interfaces if the received QoS parameters have been modified.

Bearer QoS

0

Charging Id

C

This IE shall be included on the S5/S8 interface for an E-UTRAN initial attach, a Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN, a PDP Context Activation, a Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN and a UE requested PDN connectivity.

Charging Id

0

O

If the S5/S8 interface is GTP, this IE may be included on the S4 interface, in order to support CAMEL charging at the SGSN, for a PDP Context Activation, a Handover from Trusted or Untrusted Non-3GPP IP Access to UTRAN/GERAN, inter S4-SGSN RAU with SGW change and Gn/Gp to S4-SGSN RAU.

CO

This IE shall be included on the S2a/S2b interface for an Initial Attach in WLAN on GTP S2a, an Initial Attach in WLAN for Emergency Service on GTP S2a, Attach with GTP on S2b, UE initiated Connectivity to Additional PDN with GTP on S2b, Handover to Untrusted Non-3GPP IP Access with GTP on S2b, Initial Attach for emergency session (GTP on S2b, UE initiated Connectivity to Additional PDN with GTP on S2a, and Handover to TWAN with GTP on S2a.

Bearer Flags

O

Applicable flags are:

• PPC (Prohibit Payload Compression) : this flag may be set on the S5/S8 and S4 interfaces.

Bearer Flags

0

S11-U SGW F-TEID

C

This IE shall be included on the S11 interface if the S11-U interface is used, i.e. if the S11-U Tunnel flag was set in the Create Session Request.

If the SGW supports both IP address types, the SGW shall send both IP addresses within the F-TEID IE. If only one IP address is included, then the MME shall assume that the SGW does not support the other IP address type.

F-TEID

6

NOTE 1: According to 3GPP TS 23.401 [3] e.g. clause 5.5.1.2.2 "S1-based handover, normal" and 3GPP TS 23.060 [35], during the handover procedure with an SGW change, except in the case of X2-handover (NOTE2 addresses X2 based HO with SGW change case), the target MME/S4-SGSN initiates the Create Session Request/Response and Modify Bearer Request/Response procedures one after the other. After receiving the "Bearer Context to be Created" IEs within Create Session Request message, the SGW may not accept some of these bearers. The SGW however shall return all bearers with the "Bearer Context Created" IEs within Create Session Response message (this table), but with different Cause values. Bearers that were not accepted by the SGW shall have an appropriate rejection value in the Cause IE. The target MME/S4-SGSN shall send these non-accepted bearers to the target SGW within the "Bearer Context to be removed" IE in a subsequent Modify Bearer Request message. Therefore, the SGW shall allocate the DL S5/S8 SGW F-TEIDs also for the non-accepted bearers. MME/S4-SGSN should remove all of the non-accepted bearers by separate procedures (e.g. an MME/S4-SGSN initiated Dedicated Bearer Deactivation procedure).

NOTE 2: According to 3GPP TS 23.401 [3] clause 5.5.1.1.3, "X2-based handover with Serving GW relocation", and 3GPP TS 23.060 [35] clause 6.9.2.2.5A "Enhanced Serving RNS Relocation Procedure using S4", during the X2-handover procedure with an SGW change and Enhanced Serving RNS Relocation Procedure with an SGW change, the target MME/S4-SGSN shall initiate only the Create Session Request/Response procedure. The SGW shall return all bearers (including those not accepted by the SGW) with a "Bearer Context Created" IE within Create Session Response message (this table), but with different Cause values. Bearers that were not accepted by the SGW shall have an appropriate rejection value in the Cause IE, The MME/S4-SGSN should remove these non-accepted bearers by separate procedures as well.

NOTE 3: According to 3GPP TS 23.401 [3] e.g. clause 5.3.3.1 "Tracking Area Update procedure with Serving GW change" and 3GPP TS 23.060 [35], during the RAU/TAU procedure with an SGW change, the target MME/S4-SGSN shall initiate only the Create Session Request/Response procedure. The SGW shall return all bearers (including those not accepted by the SGW) with a "Bearer Context Created" IE within Create Session Response message (this table), but with different Cause values. Bearers that were not accepted by the SGW shall have an appropriate rejection value in the Cause IE. When Active Flag or Follow-on request is set during TAU/RAU procedure, MME/S4-SGSN should not establish user plane tunnel over S1 or Iu for those bearer contexts which were not accepted by the target SGW, while in the corresponding Modify Bearer Request message, the MME/S4-SGSN shall include all accepted bearer contexts in the "Bearer Context to be modified" IE and include all non-accepted bearer contexts in the "Bearer Context to be removed" IE. The MME/S4-SGSN should remove the bearers non-accepted by either SGW or eNB/RNC by separate procedures as well.

NOTE 4: The capability to receive from the LMA an alternate LMA address for user plane shall be supported homogeneously across all the SGWs, when supported over PMIP-based S5/S8.

NOTE 5: For PMIP based S5/S8, the ‘S5/S8-U PGW F-TEID’ IE and the ‘PGW S5/S8/ S2a/S2b F-TEID for PMIP based interface or for GTP based Control Plane interface’ IE shall contain the same uplink GRE key; the Interface Type in these IEs shall be set to the value 9 (S5/S8 PGW PMIPv6 interface).

NOTE 6: When Control Plane CIoT EPS Optimization is supported, the IP address spaces for S1-U and S11-U may be different, based on operator’s deployment. If so, the following requirements shall apply:
1) if the CPOPCI (Control Plane Only PDN Connection Indication) flag is not set in the Create Session Request message, the SGW shall include both the S11-U SGW F-TEID and S1-U SGW F-TEID in the Create Session Response message, regardless of whether the S11-U Tunnel flag is set in the Create Request Request.
2) all the MMEs in the PLMN shall support receiving both the S11-U SGW F-TEID and S1-U SGW F-TEID in the Create Session Response response; the MME shall use them according to whether the CIoT Control Plane Optimization is used.

Octets 2 and 3

Length = n

Octet 4

Spare and Instance fields

Information elements

P

Condition / Comment

IE Type

Ins.

EPS Bearer ID

M

EBI

0

Cause

M

This IE shall indicate if the bearer handling was successful, and if not, gives the information on the reason.

Cause

0

Octets 2 and 3

Length = n

Octet 4

Spare and Instance fields

Information elements

P

Condition / Comment

IE Type

Ins.

Load Control Sequence Number

M

See clause 12.2.5.1.2.1 for the description and use of this parameter.

Sequence Number

0

Load Metric

M

See clauses 12.2.5.1.2.2 and 12.2.5.1.2.3 for the description and use of this parameter.

Metric

0

List of APN and Relative Capacity

CO

The IE shall (only) be present in the "PGW’s APN level Load Control Information" IE.

For indicating the APN level load, the PGW shall include one or more instances of this IE, up to maximum of 10, with the same type and instance value, representing a list of APN(s) & its respective "Relative Capacity" (sharing the same "Load Metric").

See clause 12.2.5.1.2.3 for the description and use of this parameter.

See NOTE 1.

APN and Relative Capacity

0

NOTE 1: If more than 10 occurrences of "APN and Relative Capacity" IE are received within one instance of the Load Control Information IE, the receiver shall treat it as a protocol error and ignore the entire Load Control Information IE instance.

Octets 2 and 3

Length = n

Octet 4

Spare and Instance fields

Information elements

P

Condition / Comment

IE Type

Ins.

Overload Control Sequence Number

M

See clause 12.3.5.1.2.1 for the description and use of this parameter.

Sequence Number

0

Overload Reduction Metric

M

See clauses 12.3.5.1.2.3 and 12.3.5.1.2.4 for the description and use of this parameter.

Metric

0

Period of Validity

M

See clause 12.3.5.1.2.2 for the description and use of this parameter.

This IE should be set to "0" if the "Overload Reduction Metric" is null. This IE shall be ignored by the receiver if the "Overload Reduction Metric" is null.

EPC Timer

0

List of Access Point Name (APN)

CO

The IE may (only) be present in the "PGW’s Overload Control Information" IE.

For indicating the APN level overload, the PGW shall include one or more instances of this IE, up to maximum of 10, with the same type and instance value, representing a list of APN(s) (sharing the same "Overload Reduction Metric" and "Period of Validity"). See NOTE 1.

APN

0

NOTE 1: If more than 10 occurrences of APNs are received within one instance of the Overload Control Information IE, the receiver shall treat it as a protocol error and ignore the entire Overload Control Information IE instance.

Octets 2 and 3

Length = n

Octet 4

Spare and Instance fields

Information elements

P

Condition / Comment

IE Type

Ins.

PGW Set FQDN

C

When present, this IE shall contain the PGW Set FQDN of the PGW-C/SMF set to which the PGW-C/SMF belongs.

(NOTE)

PGW FQDN

0

Alternative PGW-C/SMF IP Address

C

When present, this IE shall contain alternative PGW-C/SMF IP addresses within the PGW-C/SMF set to which the PGW-C/SMF belongs.

Several IEs with the same type and instance value may be included to represent a list of Alternative PGW-C/SMF IP Addresses.

(NOTE)

IP Address

0

Alternative PGW-C/SMF FQDN

C

When present, this IE shall contain alternative PGW-C/SMF FQDN within the PGW-C/SMF set to which the PGW-C/SMF belongs.

Several IEs with the same type and instance value may be included to represent a list of Alternative PGW-C/SMF FQDNs.

(NOTE)

PGW FQDN

1

Group Id

O

When present, this IE shall identify the group to which the PDN connection pertains (see clause 31.6 of 3GPP TS 23.007 [17]).

Group Id

0

NOTE: Either the PGW Set FQDN IE, the Alternative PGW-C/SMF IP Address IE, or the Alternative PGW-C/SMF FQDN IE shall be present.