Cause

C

If ISR is being de-activated, the Cause IE shall be included on the S4/S11 interface with the value "ISR deactivation", which indicates that the SGW shall delete the bearer resources by sending Delete Bearer Request to the MME/SGSN on which ISR was activated with the same Cause value "ISR deactivation". See NOTE 3

Cause

0

CO

The MME/SGSN shall include this IE if the message is sent due to a network failure as specified in clause 15.7 of 3GPP TS 23.060 [35] and clause 5.18 of 3GPP TS 23.401 [3]. It indicates to the PGW the reason of the failure.

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

Linked EPS Bearer ID (LBI)

C

This IE shall be included on the S4/S11, S5/S8 and S2a/S2b interfaces to indicate the default bearer associated with the PDN being disconnected unless in the handover/TAU/RAU with SGW relocation procedures.

EBI

0

User Location Information (ULI)

C

The MME/SGSN shall include this IE on the S4/S11 interface for the Detach procedure. The MME shall include ECGI, SGSN shall include CGI/SAI. The SGW shall include this IE on S5/S8 if it receives the ULI from MME/SGSN. See NOTE 4.

ULI

(NOTE 7)

0

CO

The MME/SGSN shall include this IE on the S4/S11 interface for the UE or MME Requested PDN Disconnection procedure/MS and SGSN Initiated PDN connection Deactivation Procedure using S4.

The MME shall include ECGI, SGSN shall include CGI/SAI.

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

Indication Flags

C

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

Applicable flags:

• Operation Indication: This flag shall be set to 1 over S4/S11 interface, if the SGW needs to forward the Delete Session Request message to the PGW. This flag shall not be set if the ISR associated GTP entity sends this message to the SGW in the Detach procedure. This flag shall also not be set to 1 in the SRNS Relocation Cancel Using S4 (6.9.2.2.4a in 3GPP TS 23.060 [4]), Inter RAT handover Cancel procedure with SGW change TAU with Serving GW change, Gn/Gb based RAU (see 5.5.2.5, 5.3.3.1, D.3.5 in 3GPP TS 23.401 [3], respectively), S1 Based handover Cancel procedure with SGW change.

  This flag shall also not be set to 1 for, e.g., X2 based handover procedure with SGW change(see clause 5.5.1.1.3 in 3GPP TS 23.401 [3]), or S1 based handover procedure with SGW change (see clause 5.5.1.2.2 in 3GPP TS 23.401 [3]). See NOTE 1.

• Scope Indication: This flag shall be set to 1 on the S4/S11 interface, if the request corresponds to TAU/RAU/Handover with SGW change/SRNS Relocation Cancel Using S4 with SGW change, Inter RAT handover Cancel procedure with SGW change, S1 Based handover Cancel procedure with SGW change. See NOTE 1.
• Release Over Any Access Indication (ROAAI): This flag shall be set to 1 over the S4/S11 interface when an NB-IFOM capable MME/SGSN wishes to request release of the PDN connection over any applicable access, e.g.:
• during a basic P-CSCF restoration procedure; or
• when the MME/SGSN wishes that the PDN connection be reestablished via another PGW for SIPTO.

See NOTE 9.

Indication

0

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 SGW receives the PCO IE, SGW shall forward it to PGW.

PCO

0

CO

For the multi-connection mode, if the TWAN receives the PCO from the UE, the TWAN shall forward the PCO IE to the PGW.

Originating Node

C

This IE shall be included on the S4/S11 interface if the ISR is active in MME/SGSN to denote the type of the node originating the message.

The SGW shall release the corresponding Originating Node related EPS Bearer contexts information in the PDN Connection identified by the LBI.

Node Type

0

Sender F-TEID for Control Plane

O

This IE may be included on the S4/S11 interfaces except when the source MME/SGSN initiates the deletion of PDN connections not supported by the target MME/SGSN during a successful handover/TAU/RAU procedure with MME/SGSN change and without SGW change (see clauses 5.3.3.2 and 5.5.1.2.1 of 3GPP TS 23.401 [3]), in which case this IE shall not be included. See NOTE 10.

If the Sender F-TEID for Control Plane is received by the SGW, the SGW shall only accept the Delete Session Request message when the Sender F-TEID for Control Plane in this message is the same as the Sender F-TEID for Control Plane that was last received in either the Create Session Request message or the Modify Bearer Request message on the given interface.

If the ISR is activated, two F-TEIDs exist: one for the MME and the other for the SGSN. See NOTE 2.

F-TEID

0

O

This IE may be included on the S5/S8 and S2a/S2b interfaces.

If the Sender F-TEID for Control Plane is received by the PGW, the PGW shall only accept the Delete Session Request message when the Sender F-TEID for Control Plane in this message is the same as the Sender F-TEID for Control Plane that was last received in either the Create Session Request message or the Modify Bearer Request message on the given interface. See NOTE 6.

CO

The SGW shall include this IE on the S5/S8 interface if the Delete Session Request is sent to clean up a hanging PDN connection context in the PGW, i.e. as a result of receiving a Create Session Request at the SGW colliding with an existing PDN connection context (see clause 7.2.1).

UE Time Zone

CO

This IE shall be included by the MME on the S11 interface or by the SGSN on the S4 interface, for Detach and PDN Disconnection procedures, if the UE Time Zone has changed.

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, and if the Operation Indication bit received from the MME/SGSN is set to 1.

CO

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

ULI Timestamp

CO

This IE shall be included on the S4/S11 interface if the ULI IE is present. It indicates the time when the User Location Information was acquired.

The SGW shall include this IE on S5/S8 if the SGW receives it from the MME/SGSN. See NOTE 4.

ULI Timestamp

0

RAN/NAS Release Cause

CO

The MME shall include this IE on the S11 interface to indicate the NAS release cause to release the PDN connection, if available and this information is permitted to be sent to the PGW operator according to MME operator’s policy.

The SGW shall include this IE on the S5/S8 interface if it receives it from the MME and if the Operation Indication bit received from the MME is set to 1.

RAN/NAS Cause

0

CO

The TWAN shall include this IE on the S2a interface to indicate the TWAN release cause to release the PDN connection, if this information is available and 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 8.

CO

The ePDG shall include this IE on the S2b interface to indicate the release cause to release the PDN connection, if this information is available and 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.

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

TWAN Identifier Timestamp

CO

This IE shall be included by the TWAN on the S2a if the TWAN Identifier IE is present. It shall indicate the time when the TWAN acquired the TWAN Identifier information.

TWAN Identifier Timestamp

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

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

0

UE UDP Port

CO

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

Port Number

0

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 the ePCO IE, the SGW shall forward it to the PGW.

ePCO

0

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

Secondary RAT Usage Data Report

CO

If the PLMN has configured secondary RAT usage reporting, the MME shall include this IE on the S11 interface if it has received Secondary RAT usage data from eNodeB in a UE-initiated Detach procedure for E-UTRAN, MME-initiated Detach, HSS-initiated Detach, or UE or MME requested PDN disconnection.

The MME shall also include this IE on the S11 interface to the Source SGW if it has received a Secondary RAT Usage Data Report from the eNB in an S1/X2-based handover with Serving GW relocation, or MME triggered Serving GW relocation procedure, or an E-UTRAN to GERAN A/Gb mode Inter RAT handover, E-UTRAN to UTRAN Iu mode Inter RAT handover, MME to 3G SGSN combined hard handover and SRNS relocation, or Routing Area Update procedures. In this case, the IRPGW flag shall be set to "0".

Several IEs with the same type and instance value may be included, to represent multiple usage data reports.

Secondary RAT Usage Data Report

0

O

The SGW shall forward this IE on the S5/S8 interface if it receives the Secondary RAT Usage Data Report with the IRPGW flag set to "1" from MME.

Several IEs with the same type and instance value may be included, to represent multiple usage data reports.

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: For the Indication Flags, the combination (Operation Indication, Scope Indication) = 1,1 shall be considered an error if received.

NOTE 2: Following an inter RAT TAU/RAU failure, the target MME/SGSN may mistakenly initiate the implicit detach procedure while the UE is managed by the other MME/SGSN. In this case, the SGW will reject the Delete Session Request message with the cause "Invalid peer".

NOTE 3: If the UE has multiple PDN connections and only one of these is being deactivated, the MME/S4-SGSN shall not send the Cause IE with the value "ISR deactivation".

NOTE 4: If ISR is active, after receiving both the Delete Session Request messages from the MME and the SGSN, the SGW shall include the most recent ULI timestamp and the related User Location Information in the Delete Session Request message on S5/S8 interface.

NOTE 5: The conditions of presence of the IEs in the Delete Session Request 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: In some scenarios, e.g. during an S11/S4 path failure, the old SGW may send a Delete Session Request towards the PGW for a PDN connection which has already been relocated to a new SGW. In this case, the PGW shall reject the Delete Session Request message with the cause "Invalid peer".

NOTE 7: 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 8: This IE corresponds to the TWAN Release Cause IE specified in 3GPP TS 23.402 [45].

NOTE 9: An NB-IFOM capable MME/SGSN remains unaware of whether the PDN connection to be released is associated with multiple accesses or not (i.e. whether this is a NB-IFOM PDN connection).

NOTE 10: During an inter-MME/SGSN and intra SGW mobility procedure, if the Modify Bearer Request message from the target MME/SGSN arrives at the SGW before the Delete Session Request message from the source MME/SGSN, and if the Sender F-TEID for the Control Plane was included in the Delete Session Request, this would lead the SGW to reject the Delete Session Request message.

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

Linked EPS Bearer ID (LBI)

C

If the request corresponds to the bearer deactivation procedure in case all bearers belonging to a PDN connection shall be released, then this IE shall be included on the S5/S8, S4/S11 and S2a/S2b interfaces to indicate the default bearer associated with the PDN being disconnected.

This IE shall be included only when the EPS Bearer ID is not present in the message.

EBI

0

CO

During a TAU/RAU/HO if the Cause value is set to "ISR deactivation" in the Delete Session Request message, or when this message is used to delete the bearer resources on the other ISR associated CN node if the ISRAI flag is not set in the Modify Bearer Request/Modify Access Bearers Request message, an SGW shall send all LBIs for a given UE with the message on S4/S11 interface. All LBI IEs shall have the same type and instance value to represent a list of IEs (see NOTE 1 and NOTE 2).

EPS Bearer IDs

C

This IE shall be included on S5/S8, S4/S11 and S2a/S2b interfaces for deleting bearers different from the default one, i.e. for dedicated bearers. In this case at least one dedicated bearer shall be included.

This IE shall be included only when the Linked EPS Bearer ID is not present in the message.

Several IEs with this type and instance values shall be included as necessary to represent a list of Bearers.

EBI

1

Failed Bearer Contexts

O

This IE may be included on the S5/S8 and S11 interfaces if the request corresponds to MME initiated bearer deactivation procedure. This IE shall contain the list of failed bearers if partial Bearer Contexts included in the Delete Bearer Command message could not be deleted.

Bearer Context

0

Procedure Transaction Id (PTI)

C

If the request corresponds to UE requested bearer resource modification procedure for an E-UTRAN, this IE shall be included on the S5/S8 and S11 interfaces.

PTI

0

Protocol Configuration Options (PCO)

C

The PGW shall include Protocol Configuration Options (PCO) IE on the S5/S8 interface, if available and if ePCO is not supported by the UE or the network.

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

PCO

0

CO

For trusted WLAN access, if the default bearer of the PDN connection is being deleted and if the multi-connection mode is used, the PGW may include this IE over the S2a interface to send PCO to the UE.

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

Cause

C

This IE shall be sent on S5/S8 and S11/S4 interfaces if the message is caused by a handover with or without optimization from 3GPP to non-3GPP (see clause 9.3.2 in 3GPP TS 23.402 [45] and clause 5.4.4.1 in 3GPP TS 23.401 [3], respectively). In this case the Cause value shall be set to "RAT changed from 3GPP to Non-3GPP".

This IE shall also be sent on S11/S4 interfaces when the SGW requests to delete all bearer contexts for the given UE in an MME or S4-SGSN due to ISR deactivation, and the Cause value shall be set to "ISR deactivation".

This IE shall be sent on the S2a/S2b interface if the message is caused by handover from non-3GPP to 3GPP. In this case the Cause value shall be set to "Access changed from Non-3GPP to 3GPP".

Cause

0

CO

This IE shall be sent on the S5/S8 interface if the message is caused by EPS to 5GS mobility. In this case the Cause value shall be set to "EPS to 5GS Mobility".

O

This IE may be sent by a PGW on S5/S8 during PGW initiated bearer deactivation procedures for the default bearer with values of "Reactivation requested" or " PDN reconnection to this APN disallowed" or "Multiple accesses to a PDN connection not allowed" (see clause 8.4 for details).

O

This IE may be sent by a PGW on S5 during PGW initiated bearer deactivation procedures for the default bearer with values of "PDN connection inactivity timer expires" (see clause 8.4 for details).

CO

The IE shall be relayed by the SGW to the MME/S4-SGSN if received from the PGW.

CO

This IE shall be sent by the PGW on S5/S8 or S2a/S2b with the value "Reactivation requested", when the PGW initiates the bearer deactivation procedure for the default bearer as part of the P-CSCF restoration procedure over 3GPP access or WLAN access, as specified in 3GPP TS 23.380 [61].

CO

This IE shall be sent by the PGW on S5/S8 or S2a/S2b with the value "Local release", when the PGW initiates the bearer deactivation procedure, for the default bearer of the PDN connection, with local bearer release over one of the accesses associated with the NB-IFOM connection. This can be triggered, for example, as part of the P-CSCF restoration procedure specified in 3GPP TS 23.380 [61], or upon receipt by the PGW of a Delete Session Request from an MME/SGSN with the ROAA Indication set to 1. See NOTE 3.

Indication Flags

CO

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

Applicable flags are:

• 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. 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.

Indication

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 3, NOTE 5.

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 4, NOTE 6.

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 and S2a/S2b interfaces if the PGW needs to send NBIFOM information as specified in 3GPP TS 23.161 [71]. The Container Type shall be set to 4.

F-Container

0

CO

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

APN RATE Control Status

CO

If APN RATE Control Status is available in PGW and the delete bearer request is for the default Bearer, APN RATE Control Status shall be transfered on the S5/S8 interface.

The SGW shall include the APN RATE Control Status IE on the S11/S4 interface, if received from the PGW.

APN RATE Control Status

0

Extended Protocol Configuration Options (ePCO)

CO

The PGW shall include Extended Protocol Configuration Options (ePCO) IE on the S5/S8 interface, if available and if the UE and the network support ePCO.

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

ePCO

0

PGW Change Info

CO

This IE may be included on S5/S8/S2b if the PGW needs to change the PGW Change Info. It shall be included by the PGW if the PGW S5/S8/S2b IP Address for the control plane for the PDN connection is required to be changed (see PGW triggered PDN connection restoration in clauses 31.4 and 31.4B of of 3GPP TS 23.007 [17]).

The SGW shall transparently forward this IE over the S11 interface.

Several IEs with the same IE type and Instance may be present to request the MME/ePDG to re-establish PDN connections associated with either different FQ-CSIDs, or Group Ids or PGW-C/SMF IP addresses to different PGW-C/SMFs.

PGW Change Info

0

Private Extension

O

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

Private Extension

VS

NOTE 1: If the SGW has sent multiple LBIs to MME/SGSN, but have received only one LBI within the Delete Bearer Response message, this indicates that the MME/SGSN is pre Rel-10. In such case, the SGW shall send separate individual Delete Bearer Request message(s) for each of remaining LBIs.

NOTE 2: If the SGW has received Delete Session Request with Cause value set to "ISR deactivation" and has subsequently sent a Delete Bearer Request to the MME/SGSN with Cause value set to "ISR deactivation", then the MME/SGSN shall delete all PDN connections corresponding to all of the LBIs received in the Delete Bearer Request message for this UE. The MME/SGSN shall ignore any LBIs for which there are no matching PDN connections corresponding to these LBIs.

NOTE 3: Upon receiving a Delete Bearer Request message for the default bearer of the PDN connection with cause "Local release", the MME/SGSN or TWAN/ePDG shall behave as specified in clause 5.7.3 of the 3GPP TS 23.380 [61].

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 the reason of the unsuccessful handling of the bearer.

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

O

This IE may be included by a PGW if the PGW Set FQDN is changed.

PGW FQDN

0

Alternative PGW-C/SMF IP Address

O

This IE may be included by a PGW if the list of alternative PGW-C/SMF IP addresses is changed.

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

IP Address

0

Alternative PGW-C/SMF FQDN

O

This IE may be included by a PGW if the list of alternative PGW-C/SMF FQDNs is changed.

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

PGW FQDN

1

New PGW-C/SMF IP Address

C

This IE shall be included by a PGW if the PGW S5/S8/S2b IP Address for the control plane for the PDN connection is required to be changed (see PGW triggered PDN connection restoration in clauses 31.4 and 31.4B and 31.6.3 of 3GPP TS 23.007 [17]).

IP Address

1

New SGW-C IP Address

O

This IE may be included by a combined SGW/PGW to contain the SGW-C S11 IP address (pertaining to the combined SGW/PGW sending the PGW Change Info IE). The MME should use this information when deciding to which SGW-C S11 IP address should the Create Session Request message be sent, during a combined SGW-C/PGW-C/SMF triggered restoration procedure as specified in clauses 31.4a and 31.6.3A of 3GPP TS 23.007 [17].

IP Address

3

PGW-C/SMF FQ-CSID

C

This IE shall be included if the New PGW-C/SMF IP Address IE is present and if the PGW-C/SMF requests the MME/ePDG to re-establish all the PDN connections associated with a PGW-C/SMF FQ-CSID towards the PGW-C indicated in New PGW-C/SMF IP Address IE.

When present, it shall contain the PGW-C/SMF FQ-CSID for which the PDN connections are requested to be re-established.

Several IEs with the same IE type may be present to represent several FQ-CSIDsof PDN connections that need to be moved to the New PGW-C/SMF IP Address.

See also clause 31.6 of 3GPP TS 23.007 [17].

FQ-CSID

0

Group Id

C

This IE shall be included if the New PGW-C/SMF IP Address IE is present and if the PGW-C/SMF requests the MME/ePDG to re-establish all the PDN connections associated with a Group Id towards the PGW-C indicated in New PGW-C/SMF IP Address IE.

When present, it shall contain the Group Id for which the PDN connections are requested to be re-established.

Several IEs with the same IE type may be present to represent several Group Ids of PDN connections that need to be moved to the New PGW-C/SMF IP Address.

See also clause 31.6 of 3GPP TS 23.007 [17].

Group Id

0

PGW Control Plane IP Address

C

This IE shall be included if the New PGW-C/SMF IP Address IE is present and if the PGW-C/SMF requests the MME/ePDG to re-establish all the PDN connections of which PGW S5/S8/ S2a/S2b F-TEID contains the PGW Control Plane IP Address towards the PGW-C indicated in New PGW-C/SMF IP Address IE.

Several IEs with the same IE type may be present to represent several PGW-C/SMF IP addresses of PDN connections that need to be moved to the New PGW-C/SMF IP Address.

See also clause 31.6 of 3GPP TS 23.007 [17].

IP Address

2

New Group Id

O

The IE may be present if the PGW-C/SMF wants to allocate a new Group Id for the PDN connection. When present, this IE shall identify the new Group Id to which the PDN connection pertains, and the MME/ePDG shall replace any earlier Group ID received for the PDN connection with the new Group ID. If absent, the Group ID associated earlier to the PDN connection, if any, shall remain unchanged.

See also clause 31.6 of 3GPP TS 23.007 [17].

Group Id

1