3GPP TS 24.228 -- IMS Signalling flows for Register
|
|
|
|
|
|
|
| Session Initiation: Non Hiding |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| Session Initiation: Hiding |
| |
|
| |
|
| |
|
| |
|
| | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| - |
This example assumes that UE1 and P-CSCF1 both have subscribed for the user's registration state event
package and shows how UE1 and P-CSCF1 are notified when the network-initiated
deregistration event occurs in the HSS.
| |
| - |
HSS initiates the deregistration, sending a Cx-Deregister (subscriber identity).
| |
| - |
After getting the Cx-Deregister message S-CSCF1 immediately sends a NOTIFY request towards
UE1 order to inform about the network initiated deregistration and the subscription termination. The
same Request URI, To, From, Call-ID are used as in the first NOTIFY request. CSeq is incremented
since this is the second NOTIFY request sent towards UE1.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| - |
S-CSCF1 also sends a NOTIFY request towards P-CSCF1 to which UE1 is attached to, in order
to inform about the network initiated deregistration. The same Request URI, To, From, Call-ID are used
as in the first NOTIFY request. CSeq is incremented since this is the second NOTIFY request sent
towards P-CSCF1.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| - |
After receiving the 200 (OK) response from P-CSCF1, S-CSCF1 sends Cx-Deregister Resp to the
HSS.
|
|
|
|
|
|
|
|
