7.2.21 Release Access Bearers Request

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

The Release Access Bearers Request message shall be sent on the S11 interface by the MME to the SGW as part of the S1 release procedure and eNodeB initiated Connection Suspend procedure.

It may also be sent on the S11 interface by the MME to the SGW as part of the Establishment of S1-U bearer during Data Transport in Control Plane CIoT EPS optimisation procedure (see clause 5.3.4B.4 of 3GPP TS 23.401 [3]).

NOTE: The S1 release procedure is also used to release the S11-U bearers for the Control Plane CIoT EPS optimisation, except in the case of data buffering in the MME.

The message shall also be sent on the S4 interface by the SGSN to the SGW as part of the procedures:

– RAB release using S4

– Iu Release using S4

– READY to STANDBY transition within the network

Table 7.2.21-1: Information Element in Release Access Bearers Request

Information elements	P	Condition / Comment	IE Type	Ins.
List of RABs	C	Shall be present on S4 interface when this message is used to release a subset of all active RABs according to the RAB release procedure. Several IEs with this type and instance values shall be included as necessary to represent a list of RABs to be released.	EBI	0
Originating Node	CO	This IE shall be sent on S11 interface, if ISR is active in the MME. This IE shall be sent on S4 interface, if ISR is active in the SGSN See NOTE 1.	Node Type	0
Indication Flags	CO	This IE shall be included if any one of the applicable flags is set to 1. Applicable flags are: Abnormal Release of Radio Link: This flag shall be set to 1 on the S11 interface – if the S1 release is due to an abnormal release of the radio link, e.g. when the MME receives UE CONTEXT RELEASE REQUEST with the cause value set to Radio Connection With UE Lost, or – if the MME performs DL data buffering and the operator specified policy/configuration conditions for triggering the PGW pause of charging are met (e.g. number/fraction of packets/bytes dropped at MME in downlink) as specified in clause 5.3.6A of 3GPP TS23.401 [3].	Indication	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 from eNodeB in a Connection Suspend, or S1 release procedure. The MME shall set the IRPGW flag to "0", to indicate that the IE shall not be forwarded to the PGW. 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: If SGW has the S1-U F-TEIDs for the UE, but the Originating Node IE contains value "SGSN", then the SGW shall not release the user plane and shall send a positive response to the SGSN. If SGW has the S12 RNC TEIDs or S4-U SGSN TEIDs for the UE, but the Originating Node IE contains value "MME", then the SGW shall not release the user plane and shall send a positive response to the MME.