6.18 Service-level interworking: Status Report procedure for chat session message to Short Message interworking

23.2043GPPRelease 17Stage 2Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) accessTS

Figure 6.18: Status report procedure for chat session message to Short Message interworking

1) A chat session message from the UE is successfully delivered to the SMS user after service-level interworking according to clause 6.15. The chat session message requested a success or failure delivery report.

NOTE 1: A Request for success or failure delivery report can be requested in a chat session message sent by the UE as described in IETF RFC 4975 [19].

2) The SMS-SC sends a Status report to the SMS-GMSC.

NOTE 2: The Status report, from the SMS-GMSC’s point of view, will be treated as any SM termination.

NOTE 3: The Status report is an optional message.

3a) The SMS GMSC interrogates the HLR/HSS to retrieve routeing information. Based on the pre-configured IP-SM-GW address for the user, the HLR/HSS forwards the request to the corresponding IP-SM-GW.

3b) The HLR/HSS returns the IMSI and the address(es) of the current MSC, SGSN, MME and/or SMSF to the IP-SM-GW for delivery of the Short Message in CS/PS domain.

3c) The IP-SM-GW creates a MT Correlation ID as per TS 23.040 [2], which associates the Routing Info retrieval with the subsequent Forward Short Message messages(s), and stores this along with the IMSI of the receiving subscriber. The IP-SM-GW returns to the SMS-GMSC the address of itself, along with the MT Correlation ID in the IMSI field, as routeing information. Alternatively, the IP-SM-GW may return the address(es) of the current MSC, SGSN, MME and/or SMSF, in which case, the subsequent procedure to forward the message is the same as defined in TS 23.040 [2].

4) The SMS-GMSC sends the status report in the Forward Short Message to the IP-SM-GW.

5) The IP-SM-GW translates and maps the Status report in the Forward Short Message into a report request as described in MSRP IETF RFC 4975 [19].

6) The IP-SM-GW sends a Delivery report (SMS-DELIVER-REPORT) to the SMS-GMSC.

7) The SMS-GMSC sends an acknowledgement back to the SMS-SC.

8-9) The IP-SM-GW sends a success of failure report based on the value in the status report.

NOTE 4: Step 6 and 8 can happen independently of each other.

Annex A (informative):
Service-level interworking: IM or CPM user sends an Instant Message to a group list including SMS users

Figure A.1: IM user sends an Instant Message to a group list via service-level interworking

1) The UE registers to S-CSCF according the IMS registration procedure.

2) UE generates Instant Message which includes group information, e.g. Group identifier in the Request-URI and/or recipient list in the body of the Instant Message. UE submits the Instant Message to the S-CSCF using an appropriate SIP method.

3) Based on the stored iFC, S-CSCF forwards the Instant Message to an AS in charge of the group delivery, e.g., the controlling function server defined in OMA-TS-SIMPLE_IM-V1_0 [12] or the controlling function server defined in OMA-TS-CPM_Conv_Fnct-V1_0 [17].

4) The group delivery AS replicates per Instant Message for per recipient according to the group information it obtains acting as a B2BUA. See detail in OMA-TS-SIMPLE_IM-V1_0 [12] or in OMA-TS-CPM_Conv_Fnct-V1_0 [17].

5) The group delivery AS sends the generated multiple Instant Messages to S-CSCF (e.g., the Instant Messages can be delivered as what the list server does defined in the TS 24.247 [14]).

6) The S-CSCF forwards the Instant Messages to the IP-SM-GW based on the stored iFC.

7) The IP-SM-GW shall decide whether to perform service-level interworking depending on SIP request header (e.g. Request-URI), operator policy, when the Instant Message is not routeable in the IMS. If IP-SM-GW decided to perform service-level interworking, the IP-SM-GW performs service authorization based on the stored subscriber data retrieved from the HLR/HSS at the time of the third party registration procedure as described in the clause 6.1. The IP-SM-GW shall check whether the originating subscriber is authorised to use the interworking service .If the result of service authorization is negative, the IP-SM-GW shall not forward the message, and shall return the appropriate error information to the UE in a failure report. Otherwise, the IP-SM-GW shall translate the IMS message to a Short Message (SMS- SUBMIT) and forwards it towards the SMS-SC (SC Address) via the SMS-IWMSC (as described in TS 23.040 [2]).

8) If service authorization is successful, the IP-SM-GW acknowledges the Instant Messages.

9-11) Instant Message acknowledgement is forwarded by S-CSCF to UE.

12) The SMS-IWMSC forwards the Short Messages (SMS- SUBMIT) to the SMS-SC (see TS 23.040 [2]).

13) The SMS-SC sends multiple Submit reports (SMS-SUBMIT REPORT) to SMS-IWMSC (see TS 23.040 [2]).

14) SMS-IWMSC sends the Submit reports to IP-SM-GW (see TS 23.040 [2]).

15) IP-SM-GW translates the received Submit reports to appropriate IMS delivery notifications defined in RFC 5438 [13], and forwards the IMS delivery notifications to the S-CSCF.

16) The S-CSCF forwards the IMS delivery notifications to the group delivery AS.

17) The group delivery AS aggregates the delivery notifications of the same type from different recipients into a single delivery notification.

18) The group delivery AS sends the delivery notification to the S‑CSCF.

19) The S-CSCF forwards the delivery notification to the UE.

20-23) Acknowledgement of the delivery notification is forwarded by S-CSCF to IP-SM-GW.

Annex B (informative):
Group chat sessions