name: Gi/SGi
full_form: Gateway Interface / Service Gateway Interface
context: Gi/SGi PtP tunnelling based on UDP/IP may be used to deliver Non-IP data to an AS via Gi/SGi.
  The PtP tunnel is set up by configuration of tunnel parameters in both end of the tunnel.
  The following parameters are pre-configured in the GGSN/P-GW per APN;
  -	the UDP destination port number to use when sending Non-IP data;
  -	the UDP port number it wants to receive Non-IP data;
  -	the destination IP address to be used for sending Non-IP data.
  NOTEÂ 1:	Many APNs can resolve to the same P-GW, but each APN can be unique to a particular AS.
  The following is pre-configured in the AS;
  -	the UDP destination port number to use when sending Non-IP data;
  -	the UDP port number it wants to receive Non-IP data.
  NOTEÂ 2:	The GGSN/P-GW as well as the AS can use any UDP port numbers not assigned by IANA. The port numbers used need to be aligned between peers.
  IP address allocation procedures for the UE (i.e. PDN connection) are performed by the GGSN/P-GW as described in subclauseÂ 11.2.2. 
  The UE IP address for the PDN connection or IPv6 prefix allocated for the PDN connection+suffix assigned for the PtP tunnel end point in the GGSN/P-GW is used as source address in the GGSN/P-GW and as destination address in the AS for the PtP tunnel.
  During the PDP context/PDN connection establishment, the GGSN/P-GW associates the GTP-U tunnel for the PDP context/PDN connection with the Gi/SGi PtP tunnel. The GTP-U tunnel with PDP/PDN type âNon-IPâ is used.
  The GGSN/P-GW acts as a transparent forwarding node between the UE used for CIoT and the AS.
  NOTEÂ 3:	The UE can include application level identity to AS, what kind of identity is out of scope of this specification.
  For uplink delivery, if the uplink data is received from the GTP-U tunnel the GGSN/P-GW shall forward the received data to the AS over the Gi/SGi PtP tunnel associated with the GTP-U tunnel using UDP/IP encapsulation with the destination address of the AS and the configured UDP destination port number for âNon-IPâ data as described above.
  For downlink delivery, the AS shall send the data using UDP/IP encapsulation with the IP address or IPv6 prefix+suffix of the UE as destination address and the configured UDP destination port number for âNon-IPâ data as described above.
  NOTEÂ 3:	The UDP source port number to use for both uplink and downlink Non-IP data transfer can be a pre-configured or a locally allocated port number in the GGSN/P-GW and AS respectively.
  NOTEÂ 4:	For downlink delivery, the GGSN/P-GW decapsulates the received data (i.e. removes the UDP/IP headers) and forwards the data to SGSN/S-GW on the GTP-U tunnel identified by the IP address or the IPv6 prefix of the UE (i.e. PDN connection) for delivery to the UE.
  Figure 11.8: Protocol configuration for Non-IP data (user plane) using SGiPtP tunneling
  Figure 11.9: Protocol configuration for Non-IP data (user plane) using Gi PtP tunneling.
description: A point-to-point tunnelling method based on UDP/IP used for delivering Non-IP data between the GGSN/P-GW and the AS via Gi/SGi.
explanation: Categorized as an Interface since it enables communication between network components.
biotag_Context: B-Interface,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Device,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,B-Protocol,O,O,O,B-Network,O,O,B-Protocol,O,O,O,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,B-Interface,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,B-Technology,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,B-Interface,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,B-Device,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,B-Device,O,B-Network,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Interface,O,O
biotag_Description: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Network Function,O,O