Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 23.008  Word version:  16.3.0

Top   Top   Up   Prev   Next
0…   2…   2.3…   2.4…   2.5…   2.8…   2.10…   2.13…   2.13.50…   2.13.100…   2.13.150…   2.14…   2.16…   2.22…   2.23…   2.25…   3…   3.2…   3.4…   3.10…   3.13…   3.14…   3.15…   4…   5.1   5.2   5.2A   5.2B   5.3   5.4…   5.6…   5.8…   5.10…

 

3.2  Data related to registration |R5|

3.2.1  Registration Status

The Registration Status, specified in TS 29.228, contains the status of registration of a Public User Identity or a Public Service Identity (i.e. registered, not registered, unregistered). A Public Service Identity shall have only the registration status not registered or unregistered.
The Registration Status is temporary subscriber data and is stored in HSS.

3.2.2  S-CSCF Name

For an IMS subscriber, the S-CSCF Name identifies the S-CSCF allocated to the IMS subscriber when the subscriber is registered to IP Multimedia Services. It is used during mobile terminated sessions set-up and re-registrations.
For a Public Service Identity the S-CSCF Name identities the S-CSCF allocated to the PSI for basic IMS routing. It is used during terminated call set-up for a PSI user.
The S-CSCF Name shall be in the form of a SIP URL as defined in RFC 3261 and RFC 2396.
For an IMS subscriber and PSI user, the S-CSCF Name is temporary data and is stored in HSS.
Up

3.2.2A  AS Name |R6|Word‑p. 94
For a PSI user the AS Name identifies the application server hosting the Public Service Identity and is used for direct routing of a Public Service Identity.
The AS Name shall be in the form of a SIP URL as defined in RFC 3261 and RFC 2396.
The AS Name is permanent data and is stored in the HSS.

3.2.3  Diameter Client Identity of S-CSCF

The Diameter Client Identity of the S-CSCF identifies the Diameter client in the S-CSCF when the IMS subscriber is registered to IP Multimedia Services or a PSI user has an assigned S-CSCF. It is used in requests sent by the HSS to the S-CSCF. The format of the Diameter Client Identity is the Diameter Identity defined in RFC 3588.
The Diameter Client Identity of the S-CSCF is temporary data and is stored in HSS.

3.2.4  Diameter Server Identity of HSS

The Diameter Server Identity of HSS identifies the Diameter Server in the HSS when the IMS subscriber is registered to IP Multimedia Services or the identity of HSS holding the IMS data of a PSI user. It is used in requests send by the S-CSCF to the HSS. The format of the Diameter Server Identity is the Diameter Identity defined in RFC 3588.
For an IMS subscriber and PSI user, the Diameter Server Identity of the HSS is temporary data and is stored in S-CSCF.
Up

3.2.5  UE Not Reachable via IP-SM-GW Flag (UNRI) |R7|

The UNRI is temporary subscriber data stored in the HLR/HSS and in the IP-SM-GW (AS). It indicates whether the UE is marked not reachable for short message delivery via the IMS.

3.2.6  UE Not Reachable via IP-SM-GW Reason (UNRR) |R7|

The UNRR is temporary subscriber data stored in the HLR/HSS. It indicates the reason why MT short message delivery failed at the IP-SM-GW.

3.2.7  S-CSCF Restoration Information |R8|

The S-CSCF Restoration Information, specified in TS 29.228, contains information for the S-CSCF to restore services for the user, including the list of SIP Proxies in the Path header, the Contact information and the UE's subscription information.
The S-CSCF Restoration Information is temporary subscriber data and is stored in the HSS and S-CSCF.

3.2.8  Maximum Number Of Allowed Simultaneous Registrations |R11|

The Maximum Number Of Allowed Simultaneous Registrations per public user identity is specified in TS 29.228.
It is permanent subscriber data and is stored in the HSS and S-CSCF.

3.3  Data related to authentication and ciphering |R5|Word‑p. 95
The Data related to authentication and ciphering are applicable to IMS subscribers only.

3.3.1  Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK) and Authentication Token (AUTN)

For contents of Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key(IK) and Authentication Token (AUTN) see clause 2.3.2.
A set of quintuplet vectors are calculated in the HSS, and sent from the HSS to the S-CSCF (see TS 29.228).
These data are temporary subscriber data conditionally stored in the HSS and in the S-CSCF.

3.3.2  Data related to SIP Digest Authentication |R8|

3.3.2.1  Digest Nonce

The Digest Nonce is a random (non-predictable) value selected by the S-CSCF (see TS 29.228) and used by the client to calculate the authentication response (see RFC 2617).
The Digest Nonce is temporary subscriber data and is stored in the S-CSCF.

3.3.2.2  Digest HA1

Digest HA1 is the value calculated as defined in RFC 2617. It is calculated by the HSS and used by the S-CSCF to create the Expected Response (see 3.3.2.14). It is also used to create the Response-Auth (see 3.3.2.15) after a successful authentication verification has occurred.
HA1 is permanent subscriber data and is stored in the HSS and the S-CSCF.

3.3.2.3  Digest Nextnonce

Nextnonce is the nonce the server wishes the client to use for a future authentication response (see RFC 2617).
Digest Nextnonce is temporary subscriber data and is stored in the S-CSCF.

3.3.2.4Void

3.3.2.5  Authentication Pending Flag

The Authentication Pending flag, described in TS 29.228, indicates that the authentication of a Public User Identity - Private User Identity pair is pending and waiting for confirmation.
The Authentication Pending Flag is temporary data and is stored in the HSS.

3.3.3  Data related to NASS Bundled Authentication |R8|

3.3.3.1  Line Identifier List

Line Identifier List contains a list of fixed broadband access line identifiers associated to the user and used by the S-CSCF to authenticate the user.
Line Identifier List is permanent subscriber data and is stored in HSS and the S-CSCF.


Up   Top   ToC