B.4 Signalling flows demonstrating how IP-SM-GW indicates to HSS the unavailability of UE for delivery of short messages

24.3413GPPRelease 18Stage 3Support of SMS over IP networksTS

Figure B.4-1: IP-SM-GW deregistration signalling

Figure B.4-1 shows the registration signalling flow for the scenario when IP-SM-GW deregisters to HSS. The details of the signalling flows are as follows:

1. See 3GPP TS 24.228 [9], clause 6.2 steps 1 through 22

Expires header set to zero. Public user identity deregisters its last SMS capable contact.

NOTE 1: A flow for deregistration is not provided in 3GPP TS 24.228 [9]. However, deregistration is similar to a registration with the Expires header set to zero. Compared to a Rel-5 deregistration additional parameters might appear in a later release.

2. NOTIFY request (S-CSCF to IP-SM-GW) – see example in table B.4-1

The S-CSCF sends a first NOTIFY request to the IP-SM-GW. The notification indicates that the monitored public user identity is not registered any more with an SMS capable UE.

Table B.4-1: NOTIFY request (S-CSCF to IP-SM-GW)

NOTIFY sip:ipsmgw.home1.net SIP/2.0

Max-Forwards: 70

From: <sip: user1_public1@home1.net>;tag=14142

To: <sip:ipsmgw.home1.net>;tag=31415286

Call-ID: 56uher6y5hrwy5wseg5y4w

CSeq: 222 NOTIFY

Subscription-State: active;expires=234546

Event: reg

Content-Type: application/reginfo+xml

Contact: <sip:scscf1.home1.net>

Content-Length: (…)

<?xml version="1.0"?>

<reginfo xmlns="urn:ietf:params:xml:ns:reginfo" version="1" state="full">

<registration aor="sip:user1_public1@home1.net" id="a7" state="terminated">

<contact id="77" state="terminated" event="unregistered">

<uri>sip:[5555::aaa:bbb:ccc:ddd]</uri>

</contact>

</registration>

<registration aor="sip:user1_public2@home1.net" id="a8" state="active">

<contact id="77" state="active" event="registered">

<uri>sip:[5555::aaa:bbb:ccc:eee]</uri>

</contact>

</registration>

</reginfo>

3. 200 (OK) response (IP-SM-GW to S-CSCF) – see example in table B.4-2

IP-SM-GW sends a 200 (OK) response to the S-CSCF.

Table B.4-2: 200 (OK) response (IP-SM-GW to S-CSCF)

SIP/2.0 200 OK

Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK240tfe2

From:

To:

Call-ID:

CSeq:

Content-Type:

Content-Length: 0

4. MAP: AnyTimeModification

The IP-SM-GW sends the request to inform the HSS/HLR that the user with MSISDN "11111111" is not available to receive short messages for delivery via IP via the sender of the request.

For detailed message flows and coding see 3GPP TS 29.002 [11].

Table B.4-3 provides the parameters in the AnyTimeModification request, which are sent to the HSS/HLR.

Table B.4-3: MAP: AnyTimeModification request (IP-SM-GW to HSS/HLR)

Message source and destination	MAP Information element name	Information source	Description
IP-SM-GW to HSS/HLR	SubscriberIdentity	MSISDN in SIP REGISTER request	This information element indicates the MSISDN of the subscriber
IP-SM-GW to HSS/HLR	gsmSCF-Address	(static) IP-SM-GW	HSS/HLR should forward messages related to SM delivery to this address
IP-SM-GW to HSS/HLR	modifyRegistrationStatus of the modificationRequestFor-SM-GW-Data	(static) IP-SM-GW	This information element indicates the registration status (deactivate) towards HSS/HLR.

5. MAP: AnyTimeModification response

The HSS/HLR acknowledges the request.

NOTE 2: The positive ATM response (Result message) does not contain any result code; negative response (Error message) contains an error code.