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 S-CSCF1.
| |
| - |
After S-CSCF1 deregistration notification procedure S-CSCF1 immediately sends a NOTIFY
request towards UE1 in 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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| - |
When the Network Initiated Deregistration Event occurs in S-CSCF1, S-CSCF1 informs the HSS
that the user is no longer registered. S-CSCF1 either notifies the HSS to clear or requests to keep its
location information for that subscriber. The HSS then either clears or keeps S-CSCF1 name for that
subscriber according to request. In case S-CSCF1 location information is cleared from the HSS, the
state of the subscriber identity is stored as "not registered" in the HSS. In case S-CSCF1 location
information is kept in the HSS, the state of the subscriber identity is stored as "unregistered" in the HSS
and S-CSCF1. The HSS acknowledges the request.
|
|
|
|
|
|
|
|
