3GPP TS 24.228 -- IMS Signalling flows for Register
|
|
|
|
|
|
|
| Session Initiation: Non Hiding |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| Session Initiation: Hiding |
| |
|
| |
|
| |
|
| |
|
| | |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| - |
This signalling flow assumes that:
1. the same PDP Context allocated during the initial registration scenario is still used for deregistration
2. the DHCP procedure employed for P-CSCF discovery is not needed
3. the S-CSCF selection procedure invoked by the I-CSCF is not needed.
| |
| - |
UE1 intends to de-register itself. It does so by sending a new REGISTER request. This request looks
similar as in reregister case, but the Expires header contains zero. This request is sent to the same P-CSCF
with which UE1 initially registered.
|
|
|
|
|
|
|
|
| - |
P-Access-Network-Info:
UE1 provides the access-type and access-info, related to the serving access network.
| |
| - |
From:
This indicates the public user identity originating the REGISTER request. The public user identity
may be obtained from the USIM.
| |
| - |
To:
This indicates public user identity. This is the identity by which other parties know this subscriber.
| |
| - |
Contact:
This indicates the point-of-presence for the subscriber - the IP address of UE1. This is the
temporary identifier for the subscriber that is being de-registered. The 0 value of the expires
parameter indicates the registration is being cancelled.
| |
| - |
Authorization:
It carries authentication information. The private user identity is carried in the usernamed field of
the Digest AKA protocol. The deregistration process also includes the cached information (realm,
nonce, algorithm, uri, response).
| |
| - |
Request-URI:
The Request-URI (the URI that follows the method name, "REGISTER", in the first line) indicates
the destination domain of this REGISTER request. The rules for routing a SIP request describe
how to use DNS to resolve this domain name ("home1.net") into an address or entry point into the
home operator's network (the I-CSCF). This information is stored in the USIM.
| |
| - |
Security-Verify:
Contains the security agreement as represented by the received Security-Server header.
| |
| - |
Supported:
This header is included to indicate to the recipient that the UE supports the Path header.
| |
| - |
Upon receiving this request the P-CSCF will reset the SIP registration timer for this UE to 0.
|
|
|
|
|
|
|
|
|
| - |
Based on the user's URI, P-CSCF1 determines that UE1 is registering from a visiting domain and performs
a DNS query to locate the I-CSCF in the home network. The look up in the DNS is based on the address
specified in the Request URI. The DNS provides P-CSCF1 with an address of the I-CSCF in the home
network. P-CSCF1 must not use the I-CSCF address cached as a result of the previous registration.
|
|
|
|
|
|
|
|
| - |
P-CSCF1 removes the Security-Client header and associated "sec-agree" option-tags prior to
forwarding the request. As the Proxy-Require header is empty, it removes this header completely.
| |
| - |
Path:
This is P-CSCF1 URI and is included to inform S-CSCF1 where to route terminating requests.
| |
| - |
Require:
This header is included to ensure that the recipient correctly handles the Path header. If the
recipient does not support the path header, a response will be received with a status code of
420 and an Unsupported header indicating "path". Such a response indicates a
misconfiguration of the routing tables and the request has been routed outside the IM CN
subsystem.
| |
| - |
P-Visited-Network-ID:
It contains the identifier of P-CSCF1 network at the home network.
|
|
|
|
|
|
|
|
|
| - |
Cx-Query, or Diameter UAR: User-Authorization-Request:
The I-CSCF makes a request for information related to the Subscriber registration status by sending the
private user identity ("user1_private@home1.net"), public user identity ("user1_public1@home1.net")
and visited domain identifier ("Visited Network Number 1") to the HSS.
| |
| - |
Cx-Query response, or Diameter UAA: User-Authorization-Answer:
The HSS returns the S-CSCF
required capabilities and the I-CSCF uses this information to select a suitable S-CSCF.
|
|
|
|
|
|
|
|
| - |
I-CSCF1 (THIG) adds itself to the Path header.
| |
| - |
Upon receiving this request the S-CSCF will reset the SIP registration timer for this UE to 0.
|
|
|
|
|
|
|
|
|
| - |
S-CSCF1 informs the HSS that the user is no longer registered and 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 the
S-CSCF name for that subscriber according to request. In both cases the state of the subscriber identity is
stored as unregistered in the HSS and the S-CSCF. The HSS acknowledges the request.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
