Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 33.127  Word version:  18.6.0

Top   Top   Up   Prev   Next
0…   5…   5.4…   5.6…   5.7…   6…   6.2.2…   6.2.3…   6.2.5…   6.3…   6.3.3…   6.3.4…   6.4…   7…   7.3…   7.4…   7.4.7…   7.5…   7.6…   7.7…   7.8…   7.9…   7.10…   7.11…   7.12…   7.13…   7.14…   7.15…   7.16…   8…   A…   A.2…   A.3…   A.4…   B…   D…   E…

 

7.10  Non-IP data delivery (NIDD) in EPSp. 115

7.10.1  Backgroundp. 115

7.10.1.1  Generalp. 115

Functions for NIDD (Non-IP Data Delivery) may be used to handle Mobile Originated (MO) and Mobile Terminated (MT) communication for unstructured data (also referred to as Non-IP). Such delivery to the SCS/AS (Service Capability Server/ Application Server) is accomplished by one of the following two mechanisms as defined in clause 4.5.14 of TS 23.682:
  • Delivery using SCEF.
  • Delivery using a Point-to-Point (PtP) SGi tunnel.
If the subscription includes a "SCEF Identity for NIDD" corresponding with the APN information, then the MME selects that SCEF and uses the T6a interface to that SCEF, otherwise, the MME selects a SGW and PGW which handle this PDN connection. The PDN GW shares a SGi tunnel with the SCS/AS for the NIDD traffic exchange. If SCEF is used, the NIDD traffic is forwarded by SCEF to the SCS/AS.NIDD applies to non-roaming and roaming with home-routed roaming architecture.
Up

7.10.1.2  NIDD in non-roaming situationp. 115

7.10.1.2.1  Delivery using SCEFp. 115
Figure 7.10-1 presents the architecture for delivery of NIDD using SCEF in non-roaming scenario. NIDD using SCEF requires a control plane PDN connection. The PDN connection is established between UE and SCEF via MME. The user traffic (i.e. NIDD traffic) is exchanged with DoNAS (Data over NAS) between UE and MME, then over T6a interface between MME and SCEF and finally over T8 interface between SCEF and SCS/AS.
Copy of original 3GPP image for 3GPP TS 33.127, Fig. 7.10-1: EPS Architecture for NIDD using SCEF
Figure 7.10-1: EPS Architecture for NIDD using SCEF
(⇒ copy of original 3GPP image)
Up
7.10.1.2.2  Delivery using a PtP SGi tunnelp. 115
Figure 7.10-2 shows the architecture for delivery of NIDD using a PtP SGi tunnel in non-roaming scenario. The user traffic is exchanged with DoNAS between UE and MME, over S11 interface between MME and SGW, over S5 interface between SGW and PGW and finally over a PtP SGi tunnel between PGW and AF. The tunnel is typically a UDP/IP tunnel.
Copy of original 3GPP image for 3GPP TS 33.127, Fig. 7.10-2: EPS Architecture for NIDD using a PtP SGi tunnel
Up

7.10.1.3  NIDD in roaming situationp. 116

7.10.1.3.1  Delivery using SCEFp. 116
In roaming scenario, the PDN connection for NIDD using SCEF is established between UE and SCEF via MME and IWK-SCEF in the visited network and SCEF in the home network. The user traffic is exchanged with DoNAS between UE and MME, over T6a interface between MME and IWK-SCEF, over T7a interface between IWK-SCEF and SCEF and finally over T8 interface between SCEF and SCS/AS. Figure 7.10-3 shows the architecture for delivery of NIDD using SCEF in roaming situation.
Copy of original 3GPP image for 3GPP TS 33.127, Fig. 7.10-3: EPS Architecture for NIDD using SCEF in roaming situation
Up
7.10.1.3.2  Delivery using a PtP SGi tunnelp. 116
In roaming scenario, the PDN connection for NIDD using PtP SGi tunnel is established between UE and PGW via MME and SGW in the visited network and PGW in the home network. The user traffic is exchanged with DoNAS between UE and MME, over S11 interface between MME and SGW, over S8 interface between SGW and PGW and finally over a PtP SGi tunnel between PGW and SCS/AS (Figure 7.10-4).
Copy of original 3GPP image for 3GPP TS 33.127, Fig. 7.10-4: EPS Architecture for NIDD using a PtP SGi tunnel in roaming situation
Up

7.10.2  LI for NIDDp. 116

7.10.2.1  LI for NIDD using SCEFp. 116

In non-roaming scenario, only SCEF will provide IRI-POI and CC-POI.
In roaming scenario, IWK-SCEF shall provide the IRI-POI and CC-POI functions for the visited network while SCEF in the home network provides IRI-POI and CC-POI.
LI for NIDD using SCEF or IWK-SCEF is described in clause 7.10.2.2.
Packet header reporting and non-3GPP access are not applicable to NIDD.

7.10.2.2  LI for NIDD using a PtP SGi tunnelp. 117

In non-roaming scenario, the PGW provides an IRI-POI and a CC-POI. Although SGW provides an IRI POI and a CC-POI for IP and Ethernet-based PDN connections, PGW terminates the PtP SGI tunnel with the SCS/AS and has the same capabilities as SCEF for NIDD.
In roaming scenario, SGW in the visited network and PGW in the home network shall provide the IRI-POI and CC-POI functions as shown in Figure 6.3-2 which also concerns IRI-POI and CC-POI functions for IP and Ethernet-based PDN connections.
The LI architecture for NIDD using a PtP SGi tunnel is the same as presented in Figure 6.3-2.
However, the user plane packets between UE and PGW flow through the MME and SGW as shown in Figure 7.10-2 and Figure 7.10-4.
The same xIRIs as specified in clause 6.3.3.3 for PDN connections of IP or Ethernet type and the same xCC are also considered for PDN connections for NIDD using a PtP SGi tunnel, considering unstructured payload format.
Up

Up   Top   ToC