12 Usage of Network Capabilities

29.5383GPPApplication Programming Interfaces (API) specificationEnabling MSGin5G ServiceRelease 18Stage 3TS

As specified in 3GPP TS 23.554 [2], MSGin5G Server may perform procedures of UE reachability monitoring and device triggering by consuming the 3GPP core network capabilities from SCEF/NEF as specified in 3GPP TS 29.522 [23], with description of the AF applies to the MSGin5G Server. With usage of network capabilities, the following procedure for UE reachability monitoring and device triggering procedure could be supported. Upon the MSGin5G Server receiving a request to send MSGin5G message to a MSGin5G UE, the MSGin5G Server may determine whether the recipient MSGin5G Client is not reachable:

– by using the recipient’s information received when performing the procedures specified in clause 8.9.2.2 of 3GPP TS 23.554 [2]; or

– by using the recipient’s availability information provided by MSGin5G Client at registration as specified in clause 8.2.1 of 3GPP TS 23.554 [2].

If the recipient MSGin5G Client is not reachable, the MSGin5G Server may send a request for device triggering to SCEF/NEF as specified in clause 4.4.3 of 3GPP TS 29.522 [23]. The request uses the information provided by the MSGin5G Client at registration in the MSGin5G Client Triggering Information IE. And the MSGin5G Server may use the MSGin5G Client communication availability and/or pre-configured information to determine the timing of the device triggering request, e.g. the trigger request may be sent to ensure that the target UE is reachable prior to resuming MSGin5G communications.

As specified in clause 4.4.6 of 3GPP TS 29.122 [24], upon the MSGin5G Server receiving an HTTP POST request from SCEF/NEF indicating the result of the triggering delivery, the MSGin5G Server shall respond with an HTTP 200 OK or 204 No Content response.

Annex A (normative):
OpenAPI specification