7.2.10 Delete Session Response and Delete Bearer Response
29.2743GPP3GPP Evolved Packet System (EPS)Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C)Release 18Stage 3TS
7.2.10.1 Delete Session Response
A Delete Session Response message shall be sent on the S11 interface by the SGW to the MME and on the S5/S8 interface by the PGW to the SGW as part of the following procedures:
– EUTRAN Initial Attach
– UE, HSS or MME Initiated Detach
– UE or MME Requested PDN Disconnection
It shall also be sent on the S4 interface by the SGW to the SGSN and on the S5/S8 interface by the PGW to the SGW as part of the procedures:
– MS, HLR or SGSN initiated detach procedure
– Combined GPRS/IMSI Attach
– MS and SGSN Initiated Default Bearer Deactivation Procedure using S4
On the S11 interface by the SGW to the MME as part of the procedures:
– Tracking Area Update with SGW Change
– S1 Based Handover with SGW Change
– X2 Based Handover with SGW Relocation
– E-UTRAN to UTRAN Iu mode Inter RAT handover with SGW change
– E-UTRAN to GERAN A/Gb mode Inter RAT handover with SGW change
– Inter RAT handover cancel with SGW change
– MME to 3G Gn/Gp SGSN combined hard handover and SRNS relocation procedure
– MME to SGSN Routing Area Update
– E-UTRAN to Gn/Gp SGSN Inter RAT handover
– S1 Based handover cancel with SGW change
– Optimised Active Handover: E-UTRAN Access to CDMA2000 HRPD Access
– MME triggered Serving GW relocation
And on the S4 interface by the SGW to the SGSN as part of the procedures:
– Enhanced Serving RNS Relocation with SGW relocation using S4
– Routing Area Update with SGW change
– SGSN to MME Tracking Area Update with SGW change
– Serving RNS relocation with SGW change
– UTRAN Iu mode to E-UTRAN Inter RAT handover with SGW change
– GERAN A/Gb mode to E-UTRAN Inter RAT handover with SGW change
– S4 SGSN to Gn/Gp SGSN Routeing Area Update
– S4 SGSN to Gn/Gp SGSN Serving RNS Relocation Procedures
– S4 SGSN to Gn/Gp SGSN PS handover Procedures
– S4-SGSN triggered Serving GW relocation
The message shall also be sent on the S2b interface by the PGW to the ePDG as part of procedures:
– UE/ePDG Initiated Detach with GTP on S2b
– UE Requested PDN Disconnection with GTP on S2b
– HSS/AAA Initiated Detach with GTP on S2b
The message shall also be sent on the S2a interface by the PGW to the TWAN as part of procedures:
– UE/TWAN Initiated Detach and UE/TWAN Requested PDN Disconnection in WLAN on GTP S2a
– HSS/AAA Initiated Detach in WLAN on GTP S2a
This message may also be sent on S5/S8 interface by the PGW to the SGW:
– If Downlink Data Notification Acknowledge message with Context not found cause value is received.
The sending entity shall include Cause IE in the Delete Session Response message. The IE indicates if the peer has deleted the bearer, or not.
Possible Cause values are specified in Table 8.4-1. Message specific cause values are:
– "Context not found".
– "Invalid peer".
Table 7.2.10.1-1 specifies the presence of the IEs in the message.
Table 7.2.10.1-1: Information Elements in a Delete Session Response
Information elements |
P |
Condition / Comment |
IE Type |
Ins. |
Cause |
M |
Cause |
0 |
|
Recovery |
C |
This IE shall be included on the S5/S8, S4/S11 and S2a/S2b interfaces if contacting the peer for the first time |
Recovery |
0 |
Protocol Configuration Options (PCO) |
C |
The PGW shall include Protocol Configuration Options (PCO) IE on the S5/S8 interface, if available and if the UE or the network does not support ePCO. 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 multi-connection mode is used, the PGW may include this IE over the S2a interface to send PCO to the UE. |
|||
Indication Flags |
CO |
This IE shall be included if any one of the applicable flags is set to 1. Applicable flags are:
|
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 1, NOTE 3. |
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
See NOTE 2, NOTE 4. |
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 |
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 |
APN RATE Control Status |
CO |
If APN RATE Control Status is available in PGW, 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 |
Private Extension |
O |
This IE may be sent on the S5/S8, S4/S11 and S2a/S2b interfaces. |
Private Extension |
VS |
NOTE 1: 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 2: 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 3: 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 4: 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. |
Table 7.2.10.1-2: Load Control Information within Delete Session Response
Octet 1 |
Load Control Information IE Type = 181 (decimal) |
|||
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 clause 12.2.5.1.2.2 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. |
Table 7.2.10.1-3: Overload Control Information within Delete Session Response
Octet 1 |
Overload Control Information IE Type = 180 (decimal) |
|||
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. |
7.2.10.2 Delete Bearer Response
The Delete Bearer Response shall be sent as a response of Delete Bearer Request.
Possible Cause values are specified in Table 8.4-1. Message specific cause values are:
– "Request accepted".
– "Request accepted partially".
– "Context not found".
– "Temporarily rejected due to handover/TAU/RAU procedure in progress".
Table 7.2.10.2-1: Information Elements in Delete Bearer Response
Information elements |
P |
Condition / Comment |
IE Type |
Ins. |
Cause |
M |
Cause |
0 |
|
Linked EPS Bearer ID (LBI) |
C |
If the response corresponds to the bearer deactivation procedure in case all the bearers associated with the default bearer of a PDN connection shall be released, 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. |
EBI |
0 |
CO |
During a TAU/RAU/HO, if an MME/SGSN has received a Delete Bearer Request message with Cause value "ISR deactivation" and multiple LBIs, the MME/SGSN shall include all these LBIs in the response message on S4/S11 interface. All LBI IEs shall have the same type and instance value to represent a list of IEs. |
|||
Bearer Contexts |
C |
It shall be used on the S4/S11, S5/S8 and S2a/S2b interfaces for bearers different from default one. In this case at least one bearer shall be included. Several IEs with this type and instance values shall be included as necessary to represent a list of Bearers. Used for dedicated bearers. When used, at least one dedicated bearer shall be present. All the bearer contexts included in the EPS Bearer IDs IE of the corresponding Delete Bearer Request shall be included. |
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 MME the on S11 interface and shall be forwarded by the SGW on S5/S8 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 S5/S8 interface 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) |
CO |
An MME/SGSN shall include the PCO IE if such information was received from the UE. If the SGW receives this IE, the SGW shall forward it to PGW on the S5/S8 interface. |
PCO |
0 |
CO |
For the multi-connection mode, if the default bearer of the PDN connection is being deleted and if the TWAN receives the PCO from the UE, the TWAN shall forward the PCO IE to the PGW. |
|||
UE Time Zone |
CO |
This IE shall be included, if available, 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 2. |
ULI |
0 |
CO |
The SGW shall forward this IE on the S5/S8 interface if it receives it from the MME/SGSN. See NOTE 1. |
|||
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 1. |
ULI Timestamp |
0 |
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 interface 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 |
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 when there is at least one bearer remaining for the given PDN connection after the bearer deletion, and 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 |
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 |
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 |
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 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 PDN GW initiated bearer deactivation procedure. 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: If ISR is active, after receiving both the Delete Bearer Response messages from the MME and the SGSN, the SGW shall include the most recent time and the related User Location Information in the Delete Bearer Response message on S5/S8 interface. NOTE 2: 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. |
Table 7.2.10.2-2: Bearer Context within Delete Bearer Response
Octet 1 |
Bearer Context IE Type = 93 (decimal) |
|||
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 information on the reason. |
Cause |
0 |
Protocol Configuration Options (PCO) |
CO |
An MME/SGSN shall include the PCO IE if such information was received from the UE. If the SGW receives this IE, the SGW shall forward it to PGW on the S5/S8 interface. This bearer level IE takes precedence over the PCO IE in the message body if they both exist. |
PCO |
0 |
RAN/NAS Cause |
CO |
The MME shall include this IE on the S11 interface to indicate the RAN release cause and/or NAS release cause to release the bearer, if this information is available and is permitted to be sent to the PGW operator according to the MME operator’s policy. If both a RAN release cause and a NAS release 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. See NOTE 1. |
RAN/NAS Cause |
0 |
Extended Protocol Configuration Options (ePCO) |
CO |
An MME shall include the ePCO IE if such information is received from the UE. If the SGW receives this IE, the SGW shall forward it to the PGW on the S5/S8 interface. |
ePCO |
0 |
NOTE 1: The MME may defer the deactivation of GBR bearers for a short period (in the order of seconds) upon receipt of an S1AP UE Context Release Request due to radio reasons, so as to allow the UE to re-establish the corresponding radio and S1 bearers and thus avoid the deactivation of the GBR bearers. If the MME receives then a Delete Bearer Request while it is still deferring the sending of a Delete Bearer Command, the MME shall include in the Delete Bearer Response the RAN/NAS Cause IE it would have included in the Delete Bearer Command. See clauses 5.3.5 and 5.4.4.1 of 3GPP TS 23.401 [3]. |
Table 7.2.10.2-3: Overload Control Information within Delete Bearer Response
Octet 1 |
Overload Control Information IE Type = 180 (decimal) |
|||
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 |