7.2.17 Delete Bearer Command and Failure Indication

29.2743GPP3GPP Evolved Packet System (EPS)Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C)Release 18Stage 3TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

7.2.17.1 Delete Bearer Command

A Delete Bearer Command message shall be sent on the S11 interface by the MME to the SGW and on the S5/S8 interface by the SGW to the PGW as a part of the eNodeB requested bearer release or MME-Initiated Dedicated Bearer Deactivation procedure.

The message shall also be sent on the S4 interface by the SGSN to the SGW and on the S5/S8 interface by the SGW to the PGW as part of the MS and SGSN Initiated Bearer Deactivation procedure using S4.

Table 7.2.17.1-1: Information Elements in Delete Bearer Command

Information elements	P	Condition / Comment	IE Type	Ins.
Bearer Contexts	M	This IE shall be used to indicate dedicated bearers. When used, at least one dedicated bearer shall be present. Several IEs with this type and instance values shall be included as necessary to represent a list of Bearers	Bearer Context	0
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. The SGW shall forward this IE on the S5/S8 interface if it receives it from the MME/SGSN. See NOTE 1.	ULI	0
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.	ULI Timestamp	0
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
UE Time Zone	CO	The SGW shall forward this IE on the S5/S8 interface if the SGW receives it from the MME/SGSN.	UE Time Zone	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
MME/S4-SGSN’s Overload Control Information	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.	Overload Control Information	0
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
Sender F-TEID for Control Plane	CO	The SGW shall include this IE on the S5/S8 interfaces and set it to the last value sent to the PGW. If the Sender F-TEID for Control Plane is received, the PGW shall only handle the Delete Bearer Command message if the Sender F-TEID for Control Plane in this message is the same as the last Sender F-TEID for Control Plane received on the given interface.	F-TEID	0
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 in an MME Initiated Dedicated 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
Secondary RAT Usage Data Report	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.	Secondary RAT Usage Data Report	0
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		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].

Table 7.2.17.1-2: Bearer Context within Delete Bearer Command

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
Bearer Flags	CO	Applicable flags are: VB (Voice Bearer) indicator shall be set to indicate a voice bearer for PS-to-CS (v)SRVCC handover. Vind (vSRVCC indicator) indicator shall be set to indicate a video bearer for PS-to-CS vSRVCC handover.	Bearer Flags	0
RAN/NAS Release 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 available and this information is permitted to be sent to the PGW operator according to 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.	RAN/NAS Cause	0

Table 7.2.17.1-3: Overload Control Information within Delete Bearer Command

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

7.2.17.2 Delete Bearer Failure Indication

A Delete Bearer Failure Indication shall be sent on the S5/S8 interface by the PGW to the SGW and on the S11 interface by the SGW to the MME as part of failure of eNodeB requested bearer release or MME Initiated Dedicated Bearer Deactivation procedure.

The message shall also be sent on the S5/S8 interface by the PGW to the SGW and on the S4 interface by the SGW to the SGSN as part of failure of MS and SGSN Initiated Bearer Deactivation procedure using S4.

This message shall be sent back if none of the bearers (not even a single one) included in the Delete Bearer Command message could be deleted.

The Cause IE indicates that the EPS bearer has not been deleted in the PGW.

When the SGW receives a Delete Bearer Failure Indication message from the PGW with the TEID set to zero in the GTPv2 header and the Cause IE is set to "Context Not Found", which implies that the PDN connection does not exist in the PGW, the SGW may send a Delete Bearer Request message to delete the PDN connection towards the MME/SGSN after sending the Delete Bearer Failure Indication message.

Possible Cause values are specified in Table 8.4-1. Message specific cause values are:

– "Context not found"

Table 7.2.17.2-1: Information Elements in a Delete Bearer Failure Indication

Information elements	P	Condition / Comment	IE Type	Ins.
Cause	M		Cause	0
Bearer Context	M	This IE shall contain the list of failed bearers. See clause 6.1.1 "Presence requirements of Information Elements". Several IEs with the same type and instance value may be included as necessary to represent a list of failed bearers.	Bearer Context	0
Recovery	C	This IE shall be included If contacting the peer for the first time.	Recovery	0
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 Overload Control Information	O	During an overload condition, the PGW may include this IE on the S5/S8, 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 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 1, NOTE 2.	Overload Control Information	0
PGW’s Overload Control Information	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.	Overload Control Information	0
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
Private Extension	O		Private Extension	VS
NOTE 1: 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 2: 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.17.2-2: Bearer Context within Delete Bearer Failure Indication

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	See clause 6.1.1 "Presence requirements of Information Elements".	EBI	0
Cause	M	This IE shall indicate the reason of the unsuccessful handling of the bearer.	Cause	0

Table 7.2.17-3: Overload Control Information within Delete Bearer Failure Indication

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.