Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.501  Word version:  18.5.0

Top   Top   Up   Prev   Next
1…   3…   4.2.3   4.2.4   4.2.5…   4.2.8…   4.2.8.2.2   4.2.8.2.3…   4.2.8.4…   4.2.9…   4.2.15…   4.3…   4.3.3   4.3.4   4.3.5   4.4…   4.4.6…   4.4.8…   5…   5.3…   5.3.3…   5.4…   5.5…   5.6…   5.6.7…   5.7…   5.7.2…   5.7.3…   5.7.4   5.7.5…   5.8…   5.8.2.11…   5.9…   5.10…   5.11…   5.15…   5.15.11…   5.16…   5.17…   5.18…   5.19…   5.21…   5.22…   5.27…   5.28…   5.29…   5.30…   5.31…   5.32…   5.32.6…   5.33…   5.34…   5.35…   5.38…   5.43…   6…   6.3…   6.3.8…   7…   7.2…   8…   8.2.4   8.2.5…   8.3…   A…   D…   E…   F   G…   G.3   G.4…   H…   J   K…   M…   N…   O…   P…

 

4.4  Specific servicesp. 85

4.4.1  Public Warning Systemp. 85

The Public Warning System architecture for 5G System is specified in TS 23.041.

4.4.2  SMS over NASp. 85

4.4.2.0  General |R17|p. 85

This clause introduces legacy SMS over NAS architecture, in which the interfaces between SMSF/UDM and SMS-GMSC/SMS-IWMSC/IP-SM-GW/SMS Router are still based on legacy protocol (i.e. MAP or Diameter).
The SBI-based SMS architecture and interfaces are specified in TS 23.540.

4.4.2.1  Architecture to support SMS over NASp. 85

Figure 4.4.2.1-1 shows the non-roaming architecture to support SMS over NAS using the Service-based interfaces within the Control Plane.
Reproduction of 3GPP TS 23.501, Fig. 4.4.2.1-1: Non-roaming System Architecture for SMS over NAS
Up
Figure 4.4.2.1-2 shows the non-roaming architecture to support SMS over NAS using the reference point representation.
Reproduction of 3GPP TS 23.501, Fig. 4.4.2.1-2: Non-roaming System Architecture for SMS over NAS in reference point representation
Up
Figure 4.4.2.1-3 shows the roaming architecture to support SMS over NAS using the Service-based interfaces within the Control Plane.
Reproduction of 3GPP TS 23.501, Fig. 4.4.2.1-3: Roaming architecture for SMS over NAS
Up
Figure 4.4.2.1-4 shows the roaming architecture to support SMS over NAS using the reference point representation.
Reproduction of 3GPP TS 23.501, Fig. 4.4.2.1-4: Roaming architecture for SMS over NAS in reference point representation
Up

4.4.2.2  Reference point to support SMS over NASp. 87

N1:
Reference point for SMS transfer between UE and AMF via NAS.
Following reference points are realized by service based interfaces:
N8:
Reference point for SMS Subscription data retrieval between AMF and UDM.
N20:
Reference point for SMS transfer between AMF and SMS Function.
N21:
Reference point for SMS Function address registration management and SMS Management Subscription data retrieval between SMS Function and UDM.

4.4.2.3  Service based interface to support SMS over NASp. 87

Nsmsf:
Service-based interface exhibited by SMSF.

4.4.3  IMS supportp. 87

IMS support for 5GC is defined in TS 23.228.
The 5G System architecture supports N5 interface between PCF and P-CSCF and supports Rx interface between PCF and P-CSCF, to enable IMS service. See TS 23.228, TS 23.503 and TS 23.203.
Up

4.4.4  Location servicesp. 88

4.4.4.1  Architecture to support Location Servicesp. 88

Location Service feature is optional and applicable to both regulatory services and commercial services in this Release of the specification. The non-roaming and roaming architecture to support Location Services are defined in clause 4.2 of TS 23.273.

4.4.4.2  Reference point to support Location Servicesp. 88

The reference points to support Location Services are defined in clause 4.4 of TS 23.273.

4.4.4.3  Service Based Interfaces to support Location Servicesp. 88

The Service Based Interfaces to support Location Services are defined in clause 4.5 of TS 23.273.

4.4.5  Application Triggering Servicesp. 88

See clause 5.2.6.1 of TS 23.502.
Application trigger message contains information that allows the network to route the message to the appropriate UE and the UE to route the message to the appropriate application. The information destined to the application, excluding the information to route it, is referred to as the Trigger payload. The Trigger payload is implementation specific.
Up

Up   Top   ToC