7.2.19 Create Indirect Data Forwarding Tunnel Response

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

A Create Indirect Data Forwarding Tunnel Response message shall be sent by the SGW to the MME/SGSN as a response to a Create Indirect Data Forwarding Tunnel Request message.

Table 7.2.19-1 specifies the presence requirements and the conditions of the IEs in the message.

The Cause value indicates if the Indirect Data Forwarding Tunnels has been created in the SGW or not. No Indirect Data Forwarding Tunnels have been created in the SGW if the Cause differs from "Request accepted" or "Request accepted partially". Possible Cause values are specified in Table 8.4-1. Message specific cause values are:

– "Request accepted".

– "Request accepted partially".

– "Data forwarding not supported".

– "Context not found".

Table 7.2.19-1: Information Elements in a Create Indirect Data Forwarding Tunnel Response

Information elements	P	Condition / Comment	IE Type	Ins.
Cause	M		Cause	0
Sender F-TEID for Control Plane	C	This IE shall be included by an SGW if the SGW receives a Sender F-TEID for Control Plane IE from an MME/SGSN in a Create Indirect Data Forwarding Tunnel Request message. See also NOTE 1 in Table 7.2.18-1.	F-TEID	0
Bearer Contexts	M	Several IEs with this type and instance value may be included as necessary to represent a list of Bearers	Bearer Context	0
Recovery	CO	This IE shall be included if contacting the peer for the first time	Recovery	0
Private Extension	O		Private Extension	VS

Table 7.2.19-2: Bearer Context within Create Indirect Data Forwarding Tunnel 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 tunnel setup was successful, and if not, gives information on the reason.	Cause	0
S1-U SGW F-TEID for DL data forwarding	C	This IE shall be included in the response sent from the SGW selected by the source MME for indirect data forwarding to the source MME. See NOTE 3.	F-TEID	0
S12 SGW F-TEID for DL data forwarding	C	S12 usage only. This IE shall be included in the response sent from the SGW selected by the source SGSN for indirect data forwarding to the source SGSN. See NOTE 3.	F-TEID	1
S4-U SGW F-TEID for DL data forwarding	C	S4-U usage only. This IE shall be included in the response sent from the SGW selected by the source SGSN for indirect data forwarding to the source SGSN. See NOTE 3.	F-TEID	2
SGW F-TEID for DL data forwarding	C	This IE shall be included in the response message sent from the SGW selected by the target MME/SGSN for indirect data forwarding to the target MME/SGSN. See NOTE 3.	F-TEID	3
S1-U SGW F-TEID for UL data forwarding	O	If available this IE may be included in the response sent during the intra-EUTRAN HO from the SGW selected by the source MME for indirect data forwarding to the source MME. See NOTE 4.	F-TEID	4
SGW F-TEID for UL data forwarding	O	If available this IE may be included in the response message sent during the intra-EUTRAN HO from the SGW selected by the target MME for indirect data forwarding to the target MME. See NOTE 4.	F-TEID	5
NOTE 1: For DL data forwarding if the SGW does not have enough information to decide which of the F-TEID instance from S1-U, S12, S4-U and SGW to include in the message, it may include all of them. NOTE 2: For UL data forwarding if the SGW does not have enough information to decide which of the F-TEID instance from S1-U and SGW to include in the message, it may include both of them. NOTE 3: For DL data forwarding the SGW shall set the interface type in the F-TEID to 23, i.e "SGW GTP-U interface for DL data forwarding" for S1-U/S4-U/S12/SGW. NOTE 4: For UL data forwarding the SGW shall set the interface type in the F-TEID to 28, i.e "SGW GTP-U interface for UL data forwarding" for S1-U/SGW.