B.3 Signalling flows demonstrating how IP-SM-GW indicates to HSS the availability of public user identity for delivery of short messages
24.3413GPPRelease 18Stage 3Support of SMS over IP networksTS
Figure B.3-1: IP-SM-GW registration signalling
Figure B.3-1 shows the registration signalling flow for the scenario when IP-SM-GW registers 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
NOTE 1: 3GPP TS 24.228 [9] contains Rel-5 registration; additional parameters might appear in Rel-7 registration.
2. Initial filter criteria
The S-CSCF analyses the incoming request against the initial filter criteria and decides to send a third-party REGISTER request to the IP-SM-GW. Initial Filter Criteria for IP-SM-GW includes a Service Information that contains the MSISDN belonging to "sip:user1_public1@home1.net".
3. REGISTER request (S-CSCF to IP-SM-GW) – see example in table B.3-1
This signalling flow forwards the REGISTER request from the S-CSCF to the IP-SM-GW.
Table B.3-1: REGISTER request (S-CSCF to IP-SM-GW)
REGISTER sip:ipsmgw.home1.net SIP/2.0
Via: SIP/2.0/UDP sip:scscf1.home1.net
Max-Forwards: 70
P-Access-Network-Info:
P-Visited-Network-ID:
P-Charging-Vector:
P-Charging-Function-Addresses:
From: <sip:scscf1.home1.net>;tag=14142
To: <sip:user1_public1@home1.net>
Contact: <sip:scscf1.home1.net>
Expires: 600000
Call-ID: apb03a0s09dkjdfglkj49112
CSeq: 43 REGISTER
Content-Type: application/3gpp-ims+xml
Content-Length: (…)
<?xml version="1.0" encoding="UTF-8"?>
<ims-3gpp version="1">
<service-info>11111111</service-info>
</ims-3gpp>
4. 200 OK response (IP-SM-GW to S-CSCF) – see example in table B.3-2
The IP-SM-GW sends a 200 (OK) response to the S-CSCF indicating that registration was successful.
Table B.3-2: 200 OK response (IP-SM-GW to S-CSCF)
SIP/2.0 200 OK
Via: SIP/2.0/UDP sip:scscf1.home1.net
From:
To:
Call-ID:
Contact: <sip:scscf1.home1.net>;expires=600000
CSeq:
Date: Wed, 11 July 2001 08:49:37 GMT
Content-Length:
5. SUBSCRIBE request (IP-SM-GW to S-CSCF) – see example in table B.3-3
The IP-SM-GW subscribes to the S-CSCF for the registration status of the registered subscriber.
Table B.3-3 SUBSCRIBE request (IP-SM-GW to S-CSCF)
SUBSCRIBE sip:user1_public1@home1.net SIP/2.0
Max-Forwards: 70
Route: <sip:scscf1.home1.net;lr>
P-Asserted-Identity: <sip:ipsmgw.home1.net>
P-Charging-Vector: icid-value="gwrg65hy35gw5hfrD46=583735358"; orig-ioi="type-3home1.net"
P-Charging-Function-Addresses: ccf=[5555:c88:d77::c66]; ecf=[5555:c88:d77::e67]
From: <sip:ipsmgw.home1.net>;tag=31415286
To: <sip: user1_public1@home1.net>
Call-ID: 56uher6y5hrwy5wseg5y4w
CSeq: 111 SUBSCRIBE
Event: reg
Expires: 600000
Accept: application/reginfo+xml
Contact: <sip:ipsmgw.home1.net>
Content-Length: 0
Request-URI: Public user identity whose registration status event the IP-SM-GW subscribes to.
6. 200 (OK) response (S-CSCF to IP-SM-GW) – see example in table B.3-4
The S-CSCF sends a 200 (OK) response to the IP-SM-GW.
Table B.3-4: 200 (OK) response (S-CSCF to IP-SM-GW)
SIP/2.0 200 OK
Via: SIP/2.0/UDP scscf1.home1.net;branch=z9hG4bK240tfe2
P-Asserted-Identity:
From: <sip:ipsmgw.home1.net>;tag=31415286
To: <sip:scscf1.home1.net>;tag=14142
Call-ID:
CSeq:
Contact:
Expires:
Content-Length:
7. NOTIFY request (S-CSCF to IP-SM-GW) – see example in table B.3-5
The S-CSCF sends a first NOTIFY request to the IP-SM-GW. The notification indicates that the monitored public user identity registered using an SMS capable UE.
Table B.3-5: 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=600000
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="active">
<contact id="76" state="active" event="registered">
<uri>sip:[5555::aaa:bbb:ccc:ddd]</uri>
<unknown-param name="+g.3gpp.smsip"/>
</contact>
</registration>
</reginfo>
8. 200 (OK) response (IP-SM-GW to S-CSCF) – see example in table B.3-6
IP-SM-GW sends a 200 (OK) response to the S-CSCF.
Table B.3-6: 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
9. MAP: AnyTimeModification
The IP-SM-GW sends the request to inform the HSS/HLR that the user with MSISDN "11111111" is ready 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.3-7 provides the parameters in the AnyTimeModification request, which are sent to the HSS/HLR.
Table B.3-7: Data update procedure (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 (activate) towards HSS/HLR |
10. 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.