6 Services for SBI-based SMS
23.5403GPP5G System: Technical realization of Service Based Short Message ServiceRelease 17Stage 2TS
6.1 General
This clause introduces the services for SBI-based SMS.
6.2 UDM services for SBI-based SMS
6.2.1 General
The following table illustrates the UDM services for SBI-based SMS.
Table 6.2.1-1: UDM Services for SBI-based SMS
|
Service Name |
Service Operations |
Operation Semantics |
Service Privider(s) |
Service Consumer(s) |
|
UE Context Management (UECM) |
SendRoutingInfoForSM |
request / response |
UDM |
SMS-GMSC |
|
ReportSMDeliveryStatus |
Request |
request / response |
UDM |
SMS-GMSC, IP-SM-GW, |
|
EventExposure |
Subscribe |
subscribe / notify |
UDM |
SMS-GMSC |
6.2.2 Nudm_ReportSMDeliveryStatus service
6.2.2.1 General
For the Nudm_ReportSMDeliveryStatus service the following service operations are defined:
– Request
6.2.2.2 Nudm_ReportSMDeliveryStatus_Request service operation
Service operation name: Nudm_ReportSMDeliveryStatus_Request
Description: reports the SM-Delivery Status to UDM.
Inputs, Required: GPSI, SM-Delivery status
Inputs, Optional: None.
Outputs, Required: report SM-Delivery status result.
Outputs, Optional: None.
6.2.3 Nudm_EventExposure service
Service Description: This service is defined in clause 5.2.3.5 of 3GPP TS 23.502 [4], in addition, this clause defines the enhancement of Nudm_EventExposure for alert sc.
Except the existing events that are exposed by UDM, events "UE_MEMORY_AVAILABLE_FOR_SMS" and "UE_REACHABILITY_FOR_SMS" should be supported.
6.2.4 Nudm_UECM service
Service Description: This service is defined in clause 5.2.3.2 of 3GPP TS 23.502 [4], in addition, this clause defines the enhancement of Nudm_UECM service.
The new service operation SendRoutingInfoForSM shall be supported to get the target valid node(s) serving the UE from the UDM, which will be used by the SMS-GMSC to deliver the MT SMS.
6.3 SMS-IWMSC services for SBI-based SMS
6.3.1 General
The following table illustrates the SMS-IWMSC services for SBI-based SMS.
Table 6.3.1-1: SMS-IWMSC Services for SBI-based SMS
|
Service Name |
Service Operations |
Operation Semantics |
Service Privider(s) |
Service Consumer(s) |
|
SMService |
MoForwardSm |
request / response |
SMS-IWMSC |
SMSF |
6.3.2 Niwmsc_SMService service
6.3.2.1 General
Service Description: This service can be used for SBI-based MO SM transfer and Delivery Report through SMS-IWMSC.
6.3.2.2 Niwmsc_SMService_MoForwardSm service operation
Service operation name: Niwmsc_SMService_MoForwardSm.
Description: Service request from consumer to SMS-IWMSC for MO SM transmit.
Inputs, Required: the SM record to be sent, the Service Centre address, the callbackURI for MO SMS Delivery Report, the timer for waiting MO SMS Delivery Report.
Inputs, Optional: Access Type.
Outputs, Required: On success, Delivery Report should be returned.
On failure or redirection, the appropriate HTTP status code (e.g. "403 Forbidden", "504 Gateway Timeout") indicating the error shall be returned.
Outputs, Optional: None.
6.4 SMSF services for SBI-based SMS
6.4.1 General
The following table illustrates the SMSF services for SBI-based SMS.
Table 6.4.1-1: SMSF Services for SBI-based SMS
|
Service Name |
Service Operations |
Operation Semantics |
Service Privider(s) |
Service Consumer(s) |
|
SMService |
MtForwardSm |
request / response |
SMSF |
SMS-GMSC, IP-SM-GW, SMS Router |
6.4.2 Nsmsf_SMService service
6.4.2.1 General
Service Description: This service can be used for SBI-based MT SM transfer through SMSF.
6.4.2.2 Nsmsf_SMService_MtForwardSm service operation
Service operation name: Nsmsf_SMService_MtForwardSm
Description: transfer downlink SMS message from consumer NF to SMSF.
Inputs, Required: GPSI, SMS payload
Inputs, Optional: None.
Outputs, Required: SMS message transmission result.
Outputs, Optional: None.
6.5 IP-SM-GW services for SBI-based SMS
6.5.1 General
The following table illustrates the IP-SM-GW services for SBI-based SMS.
Table 6.5.1-1: IP-SM-GW Services for SBI-based SMS
|
Service Name |
Service Operations |
Operation Semantics |
Service Privider(s) |
Service Consumer(s) |
|
SMService |
RoutingInfo |
request / response |
IP-SM-GW |
UDM |
|
MtForwardSm |
request / response |
IP-SM-GW |
SMS-GMSC |
6.5.2 Nipsmgw_SMService service
6.5.2.1 General
Service Description: This service can be used for SBI-based MT SM transfer through IP-SM-GW.
6.5.2.2 Nipsmgw_SMService_RoutingInfo service operation
Service operation name: Nipsmgw_SMService_RoutingInfo
Description: provides the SMSF Instance Id to the IP-SM-GW.
Inputs, Required: GPSI, SMSF Instance Id.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None.
6.5.2.3 Nipsmgw_SMService_MtForwardSm service operation
Service operation name: Nipsmgw_SMService_MtForwardSm
Description: transfer downlink SMS message from consumer NF to IP-SM-GW and return the MT SMS Delivery Report to the consumer NF.
Inputs, Required: GPSI, SMS payload
Inputs, Optional: None.
Outputs, Required: MT SMS Delivery Report.
Outputs, Optional: None.
6.6 SMS Router services for SBI-based SMS
6.6.1 General
The following table illustrates the SMS Router services for SBI-based SMS.
Table 6.6.1-1: SMS Router Services for SBI-based SMS
|
Service Name |
Service Operations |
Operation Semantics |
Service Privider(s) |
Service Consumer(s) |
|
SMService |
RoutingInfo |
request / response |
SMS Router |
UDM |
|
MtForwardSm |
request / response |
SMS Router |
SMS-GMSC |
6.6.2 Nrouter_SMService service
6.6.2.1 General
Service Description: This service can be used for SBI-based MT SM transfer through SMS Router.
6.6.2.2 Nrouter_SMService_RoutingInfo service operation
Service operation name: Nrouter_SMService_RoutingInfo
Description: provides the SMSF Instance Id to the SMS Router.
Inputs, Required: GPSI, SMSF Instance Id.
Inputs, Optional: None.
Outputs, Required: Result.
Outputs, Optional: None.
6.6.2.3 Nrouter_SMService_MtForwardSm service operation
Service operation name: Nrouter_SMService_MtForwardSm
Description: transfer downlink SMS message from consumer NF to SMS Router and return the MT SMS Delivery Report to the consumer NF.
Inputs, Required: GPSI, SMS payload
Inputs, Optional: None.
Outputs, Required: MT SMS Delivery Report.
Outputs, Optional: None.
6.7 MNPF services for SBI-based SMS
6.7.1 General
The following table illustrates the MNPF services for SBI-based SMS.
Table 6.7.1-1: MNPF Services for SBI-based SMS
|
Service Name |
Service Operations |
Operation Semantics |
Service Privider(s) |
Service Consumer(s) |
|
NPStatus |
Get |
request / response |
MNPF |
SMS-GMSC, SCP |
6.7.2 Nmnpf_NPStatus service
6.7.2.1 General
Service Description: This service can be used to retrieve the PLMN ID of the Subscription Network of a GPSI.
6.7.2.2 Nmnpf_NPStatus_Get service operation
Service operation name: Nmnpf_NPStatus_Get
Description: retrieve the PLMN ID of the Subscription Network of a GPSI.
Inputs, Required: GPSI.
Inputs, Optional: None.
Outputs, Required: PLMN Id.
Outputs, Optional: None.
6.8 NEF services for SBI-based SMS
6.8.1 General
The following table illustrates the NEF services for SBI-based SMS.
Table 6.8.1-1: NEF Services for SBI-based SMS
|
Service Name |
Service Operations |
Operation Semantics |
Service Privider(s) |
Service Consumer(s) |
|
SMService |
MoForwardSm |
request / response |
NEF |
SMS-SC |
6.8.2 Nnef_SMService service
6.8.2.1 General
This service can be used for SBI-based MO SM transfer through NEF for MSISDN-less MO SMS.
6.8.2.2 Nnef_SMService_MoForwardSm service operation
Service operation name: Nnef_SMService_MoForwardSm
Description: transmit MO SMS message from consumer NF to NEF.
Inputs, Required: SMS payload, Application port ID, SUPI, destination SME address (long/short code of the AF).
Inputs, Optional: None.
Outputs, Required: SMS message transmission result.
Outputs, Optional: None.
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2021-10 |
CT4#106e |
C4-215046 |
C4-215046 as basis |
0.1.0 |
|||
|
2021-10 |
CT4#106e |
C4-215513 |
Implementation of C4-215417, C4-215418, C4-215453 and C4-215454 in CT4#106e |
0.2.0 |
|||
|
2021-12 |
CT4#107e |
C4-216466 |
Implementation of C4-216442, C4-216443, C4-216444 and C4-216546 in CT4#107e |
0.3.0 |
|||
|
2022-01 |
CT4#107bis-e |
C4-220540 |
Implementation of C4-220029, C4-220341, C4-220374, C4-220408 and C4-220409 in CT4#107bis-e |
0.4.0 |
|||
|
2022-02 |
CT4#108e |
C4-221588 |
Implementation of C4-221438, C4-221573, C4-221595 and C4-221692 in CT4#108e |
0.5.0 |
|||
|
2022-04 |
CT4#109e |
C4-222340 |
Implementation of C4-222229, C4-222271, C4-222301, C4-222329, C4-222330, C4-222394, C4-222395, C4-222396, C4-222397 and C4-222418 in CT4#109e |
0.6.0 |
|||
|
2022-05 |
CT4#110e |
C4-223449 |
Implementation of C4-223277, C4-223342 and C4-223358 in CT4#110e |
0.7.0 |
|||
|
2022-06 |
CT#96 |
CP-221077 |
TS for information and approval |
1.0.0 |
|||
|
2022-06 |
CT#96 |
CP-221077 |
TS approved in CT#96 |
17.0.0 |
|||
|
2022-09 |
CT#97e |
CP-222027 |
0001 |
– |
B |
TS 23.540 Alignment of MNPF |
17.1.0 |
|
2022-09 |
CT#97e |
CP-222027 |
0002 |
– |
B |
Add NEF and MNPF in SBI-based SMS system architecture |
17.1.0 |
|
2022-09 |
CT#97e |
CP-222027 |
0003 |
– |
F |
Description of the Alert procedure |
17.1.0 |
|
2022-09 |
CT#97e |
CP-222027 |
0004 |
– |
F |
Correction on Operation Semantic of UDM service |
17.1.0 |