Cause

M

Cause

0

Bearer Contexts

M

All the bearer contexts included in the corresponding Create Bearer Request shall be included. Several IEs with this type and instance value shall be included on the S4/S11, S5/S8 and S2a/S2b interfaces as necessary to represent a list of Bearers.

Bearer Context

0

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

MME-FQ-CSID

C

This IE shall be included by the MME on the S11 interfaceand shall be forwarded by the SGW on the S5/S8 interfaces 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 S5/S8 interfaces according to the requirements in 3GPP TS 23.007 [17].

FQ-CSID

1

ePDG-FQ-CSID

C

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

FQ-CSID

2

TWAN-FQ-CSID

C

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

FQ-CSID

3

Protocol Configuration Options (PCO)

C

If the UE includes the PCO IE, then the MME/SGSN shall copy the content of this IE transparently from the PCO IE included by the UE. If the SGW receives PCO from MME/SGSN, SGW shall forward it to the PGW.

PCO

0

UE Time Zone

O

This IE is optionally included by the MME on the S11 interface or by the SGSN on the S4 interface.

UE Time Zone

0

CO

The SGW shall forward this IE on the S5/S8 interface if the SGW receives it from the MME/SGSN.

CO

This IE shall be included by the TWAN on the S2a interface.

User Location Information (ULI)

CO

This IE shall be included by the MME on the S11 interface or by the SGSN on the S4 interface. The CGI/SAI shall be included by SGSN and the ECGI shall be included by MME.

See NOTE 1.

ULI

0

CO

The SGW shall forward this IE on the S5/S8 interface if it receives it from the MME/SGSN.

TWAN Identifier

CO

This IE shall be included by the TWAN on the S2a interface as specified in 3GPP TS 23.402 [45].

TWAN Identifier

0

MME/S4-SGSN’s Overload Control Information

O

During an overload condition, the MME/S4-SGSN may include this IE on the S11/S4 interface if the overload control feature is supported by the MME/S4-SGSN and is activated for the PLMN to which the PGW belongs (see clause 12.3.11).

When present, the MME/S4-SGSN shall provide only one instance of this IE, representing its overload information.

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 PGW on the S5/S8 interface.

SGW’s Overload Control Information

O

During an overload condition, the SGW may include this IE over the S5/S8 interface if the overload control feature is supported by the SGW and is activated for the PLMN to which the PGW belongs (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

Presence Reporting Area Information

CO

The MME/SGSN shall include this IE on S11/S4 if the PGW/PCRF/OCS has requested to start or modify reporting changes of UE presence in Presence Reporting Area(s) in the corresponding Create Bearer Request message and the MME/SGSN supports such reporting. The MME/SGSN shall then indicate whether the UE is inside or outside the newly started or modified Presence Reporting Area(s), or indicate that the Presence Reporting Area(s) is inactive.

The SGW shall include this IE on S5/S8 if it receives the Presence Reporting Area Information from 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 Information. One IE shall be included for each PRA newly started or modified.

Presence Reporting Area Information

0

MME/S4-SGSN Identifier

CO

If the overload control feature is supported by the MME/S4-SGSN and is activated for the PLMN to which the PGW belongs (see clause 12.3.11), the MME/S4-SGSN shall include this IE on the S11/S4 interface if the PGW has not been updated with the identity of the currently serving MME/S4-SGSN, i.e. if no other message carrying MME/S4-SGSN identity has been sent to the PGW during/after an inter-MME/S4-SGSN intra-SGW mobility procedure.

IP Address
(See NOTE 2)

0

TWAN/ePDG’s Overload Control Information

O

During an overload condition, the TWAN/ePDG may include this IE over the S2a/S2b interface if the overload control feature is supported by the TWAN/ePDG and is activated for the PLMN to which the PGW belongs (see clause 12.3.11).

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

Overload Control Information

2

WLAN Location Information

CO

The ePDG shall include this IE on the S2b interface if the WLAN Location Information is available.

TWAN Identifier

1

WLAN Location Timestamp

CO

The ePDG shall include this IE on the S2b interface, if the WLAN Location Timestamp is available.

TWAN Identifier Timestamp

1

UE Local IP Address

CO

The ePDG shall include this IE on the S2b interface.

IP Address
(See NOTE 2)

0

UE UDP Port

CO

The ePDG shall include this IE on the S2b interface if NAT is detected and the UDP encapsulation is used.

Port Number

0

NBIFOM Container

CO

This IE shall be included on the S11/S4 or S2a/S2b interfaces if the MME/S4-SGSN or the TWAN/ePDG receives a NBIFOM Container from the UE as specified in 3GPP TS 24.161 73]. The Container Type shall be set to 4.

F-Container

0

CO

If the SGW receives a NBIFOM Container IE from the MME/S4-SGSN, the SGW shall forward it to the PGW on the S5/S8 interface.

UE TCP Port

CO

The ePDG shall include this IE on the S2b interface if NAT is detected and the TCP encapsulation is used.

Port Number

1

PSCell ID

CO

The MME shall include this IE on the S11 interface, if it has received this information from the eNodeB.

PSCell ID

0

Private Extension

O

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

Private Extension

VS

NOTE 1: In shared networks, when the message is sent from the VPLMN to the HPLMN, the PLMN ID that is communicated in this IE shall be that of the selected Core Network Operator for supporting UEs, or that of the allocated Core Network Operator for non-supporting UEs. As an exception, based on inter-operator roaming/sharing agreement, if the information on whether the UE is a supporting or non-supporting UE is available, the PLMN ID that is communicated to the HPLMN for non-supporting UEs shall be the Common PLMN ID.
In shared networks, when the MME/S4-SGSN and PGW pertain to the same PLMN, the Primary PLMN ID shall be communicated in the ECGI to the PGW, and the Common PLMN ID shall be communicated in SAI/CGI to the PGW, for both supporting and non-supporting UEs. The Core Network Operator PLMN ID (selected by the UE for supporting UEs or allocated by the network for non-supporting UEs) shall be communicated in the TAI, RAI, UCI and the Serving Network.
See clause 4.4 of 3GPP TS 23.251 [55].

NOTE 2: It is not correct that the IP Address IE type with the same instance 0 appears twice in the message table, however, there is no problem because the MME/SGSN Identifier (received over S11/S4/S5/S8) and UE Local IP Address (received over S2b) can never appear in the same message. It was not possible to change the instance of IP Address IE type since it would have been a backward incompatible change.

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, it gives information on the reason.

Cause

0

S1-U eNodeB F-TEID

C

This IE shall be sent on the S11 interface if the S1-U interface is used.

F-TEID

0

S1-U SGW F-TEID

C

This IE shall be sent on the S11 interface. It shall be used to correlate the bearers with those in the Create Bearer Request.

F-TEID

1

S5/8-U SGW F-TEID

C

This IE shall be sent on the S5/S8 interfaces.

F-TEID

2

S5/8-U PGW F-TEID

C

This IE shall be sent on the S5/S8 interfaces. It shall be used to correlate the bearers with those in the Create Bearer Request.

F-TEID

3

S12 RNC F-TEID

C

This IE shall be sent on the S4 interface if the S12 interface is used. See NOTE1.

F-TEID

4

S12 SGW F-TEID

C

This IE shall be sent on the S4 interface. It shall be used to correlate the bearers with those in the Create Bearer Request. See NOTE1.

F-TEID

5

S4-U SGSN F-TEID

C

This IE shall be sent on the S4 interface if the S4-U interface is used. See NOTE1.

F-TEID

6

S4-U SGW F-TEID

C

This IE shall be sent on the S4 interface. It shall be used to correlate the bearers with those in the Create Bearer Request. See NOTE1.

F-TEID

7

S2b-U ePDG F-TEID

C

This IE shall be sent on the S2b interface.

F-TEID

8

S2b-U PGW F-TEID

C

This IE shall be sent on the S2b interface. It shall be used to correlate the bearers with those in the Create Bearer Request.

F-TEID

9

S2a-U TWAN F-TEID

C

This IE shall be sent on the S2a interface.

F-TEID

10

S2a-U PGW F-TEID

C

This IE shall be sent on the S2a interface. It shall be used to correlate the bearers with those in the Create Bearer Request.

F-TEID

11

Protocol Configuration Options (PCO)

CO

If the UE includes the PCO IE in the corresponding message, then the MME/SGSN shall copy the content of this IE transparently from the PCO IE included by the UE. If the SGW receives PCO from MME/SGSN, SGW shall forward it to the PGW. This bearer level IE takes precedence over the PCO IE in the message body if they both exist.

PCO

0

RAN/NAS Cause

CO

If the bearer creation failed, the MME shall include this IE on the S11 interface to indicate the RAN cause and/or the NAS cause of the bearer creation failure, if available and if this information is permitted to be sent to the PGW operator according to MME operator’s policy.
If both a RAN cause and a NAS cause are generated, then several IEs with the same type and instance value shall be included to represent a list of causes.

The SGW shall include this IE on the S5/S8 interface if it receives it from the MME.

RAN/NAS Cause

0

CO

If the bearer creation failed, the TWAN shall include this IE on the S2a interface to indicate the cause of the bearer creation failure, if available and if this information is permitted to be sent to the PGW operator according to the TWAN operator’s policy. When present, the IE shall be encoded as a Diameter or an ESM cause. See NOTE 2.

CO

If the bearer creation failed, the ePDG shall include this IE on the S2b interface to indicate the cause of the bearer creation failure, if available and if this information is permitted to be sent to the PGW operator according to the ePDG operator’s policy. When present, the IE shall be encoded as a Diameter or an IKEv2 cause. See NOTE 3.

Extended Protocol Configuration Options (ePCO)

CO

If the UE includes the ePCO IE, then the MME shall copy the content of this IE transparently from the ePCO IE included by the UE.

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

ePCO

0

NOTE 1: The SGW shall use the same F-TEID IP address and TEID values for S1-U, S4-U and S12 interfaces. However, when sending a Create Bearer Request message to an S4-SGSN for a UE in idle mode, the SGW can not know whether the S4-SGSN will establish a direct user plane tunnel between the RNC and the SGW. The SGW may include either the S4-U SGW F-TEID IE or the S12 SGW F-TEID IE in the Create Bearer Request message. The S4-SGSN will decide whether to establish a direct user plane tunnel or not and will provide accordingly either a S12 RNC F-TEID or a S4-U SGSN F-TEID in the Create Bearer Response message, where the interface type of the provided F-TEID may differ from the interface type of the SGW F-TEID used for bearer correlation, e.g. if the SGW includes the S4-U SGW F-TEID in the Create Bearer Request message, and if the SGSN decides to use Direct Tunnelling, the S4-SGSN shall provide the S12 RNC F-TEID in the Create Bearer Response message, together with S4-U SGW F-TEID. The SGW should not treat this as an error.

NOTE 2: The TWAN does not exchange signalling with the 3GPP AAA Server nor with the UE in this procedure. The TWAN may include an internal failure cause for the bearer creation failure. The protocol type used to encode the internal failure cause is implementation specific.

NOTE 3: The ePDG does not exchange signalling with the 3GPP AAA Server in this procedure. The ePDG may include an internal failure cause for the bearer creation failure. The protocol type used to encode the internal failure cause is implementation specific.

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 clause 12.3.5.1.2.3 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