Tech-invite  3GPPspecsRELsGlossariesSIP
Info21222324252627282931323334353637384‑5x

full Contents for  TS 23.501  Word version:   16.4.0

Top   Up   Prev   Next
1…   3…   4…   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.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.16…   5.17…   5.18…   5.19…   5.21…   5.22…   5.27…   5.28…   5.29…   5.30…   5.31…   5.32…   5.33…   5.34…   5.35…   6…   6.3…   7…   7.2…   8…   8.2.4   8.2.5…   8.3…   A…   D…   E…   F   G…   G.3   G.4…   J…

 

4.4  Specific servicesWord-p. 66
4.4.1  Public Warning System
The Public Warning System architecture for 5G System is specified in TS 23.041.
4.4.2  SMS over NAS
4.4.2.1  Architecture to support SMS over NAS
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.
Up
Figure 4.4.2.1-2 shows the non-roaming architecture to support SMS over NAS using the reference point representation.
Up
NOTE 1:
SMS Function (SMSF) may be connected to the SMS-GMSC/IWMSC/SMS Router via one of the standardized interfaces as shown in TS 23.040.
NOTE 2:
UDM may be connected to the SMS-GMSC/IWMSC/SMS Router via one of the standardized interfaces as shown in TS 23.040.
NOTE 3:
Each UE is associated with only one SMS Function in the registered PLMN.
NOTE 4:
SMSF re-allocation while the UE is in RM REGISTERED state in the serving PLMN is not supported in this Release of the specification. When serving AMF is re-allocated for a given UE, the source AMF includes SMSF identifier as part of UE context transfer to target AMF. If the target AMF, e.g. in the case of inter-PLMN mobility, detects that no SMSF has been selected in the serving PLMN, then the AMF performs SMSF selection as specified in clause 6.3.10.
NOTE 5:
To support MT SMS domain selection by IP-SM-GW/SMS Router, IP-SM-GW/SMS Router may connect to SGs MSC, MME and SMSF via one of the standardized interfaces as shown in TS 23.040.
Figure 4.4.2.1-3 shows the roaming architecture to support SMS over NAS using the Service-based interfaces within the Control Plane.
Up
Figure 4.4.2.1-4 shows the roaming architecture to support SMS over NAS using the reference point representation.
Up
4.4.2.2  Reference point to support SMS over NASWord-p. 68
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 NAS
Nsmsf:
Service-based interface exhibited by SMSF.
4.4.3  IMS support
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.
NOTE 1:
Rx support between PCF and P-CSCF is for backwards compatibility for early deployments using Diameter between IMS and 5GC functions.
NOTE 2:
When service based interfaces are used between the PCF and P-CSCF in the same PLMN, the P-CSCF performs the functions of a trusted AF in the 5GC.
Up
4.4.4  Location services
4.4.4.1  Architecture to support Location Services
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 Services
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 Services
The Service Based Interfaces to support Location Services are defined in clause 4.5 of TS 23.273.
4.4.5  Application Triggering ServicesWord-p. 69
See TS 23.502, clause 5.2.6.1.
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.
NOTE:
The application in the UE may perform actions indicated by the Trigger payload when the Triggered payload is received at the UE. For example initiation of immediate or later communication with the application server based on the information contained in the Trigger payload, which includes the PDU Session Establishment procedure if the related PDU Session is not already established.
Up

Up   Top   ToC