in2EPS
IETF         RFCs         Groups         SIP         Presence         Security         QoS
3GPP         Specs         Glossaries         Architecture         EPC         IMS         subsD         UICC         ETSI

3GPP  CT4
TS 29.228


IMS Cx and Dx Interfaces –
Signalling flows and message contents

TopIndexPrevNext ToCETSI-search3GPP-page 
- - v5.22
CP-50
Y10-12
53 p.
 v6.17
CP-50
Y10-12
60 p.
 v7.18
CP-59
Y13-03
65 p.
 v8.19
CP-61
Y13-09
73 p.
 v9.12
CP-61
Y13-09
73 p.
 v10.8
CP-61
Y13-09
75 p.
 v11.10
CP-62
Y13-12
76 p.
 v12.5
CP-67
Y15-03
79 p.
 - - -
after the TSG Plenary Meetings, the 3GPP produces Word documents and afterwards the ETSI publishes the PDF versions
Rapporteur:   BARTOLOME, Maria-Cruz
See also:   IMS-related TS/TR
This TS specifies:
1.The interactions between the HSS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface.
2.The interactions between the CSCF and the SLF (Server Locator Function), referred to as the Dx interface.

The IP Multimedia (IM) Subsystem stage 2 is specified in TS 23.228 and the signalling flows for the IP multimedia call control based on SIP and SDP are specified in TS 24.228.

This document addresses the signalling flows for Cx and Dx interfaces.

This document also addresses how the functionality of Px interface is accomplished. The Presence Service Stage 2 description (architecture and functional solution) is specified in TS 23.141.
full Table of Contents for version:   12.5
except for a few cases, a 3GPP document of a given release is a superset of the same document for the previous release
this ToC shows the evolution of the document according to the releases
 1Scope       p. 6Top
 2References       p. 6Top
 3Definitions, symbols and abbreviations       p. 7
3.1Definitions       p. 7
3.2Abbreviations       p. 8
Top
 4Main Concept       p. 8Top
 5General Architecture       p. 9
5.1Functional requirements of network entities       p. 9
5.1.1Functional requirements of P-CSCF       p. 9
5.1.2Functional requirements of I-CSCF       p. 9
5.1.3Functional requirements of S-CSCF       p. 9
5.1.4Functional requirements of HSS       p. 9
5.1.5Functional classification of Cx interface procedures       p. 9
5.1.6Functional Requirements of the Presentity Presence Proxy
[R6]       p. 9
Top
 6Procedure Descriptions       p. 10
6.1Location management procedures       p. 10
6.1.1User registration status query       p. 10
6.1.1.1Detailed behaviour       p. 11
6.1.2S-CSCF registration/deregistration notification       p. 13
6.1.2.1Detailed behaviour       p. 17
6.1.3Network initiated de-registration by the HSS,
administrative       p. 21
6.1.3.1Detailed behaviour       p. 22
6.1.4User location query       p. 24
6.1.4.1Detailed behaviour       p. 25
6.2User data handling procedures       p. 26
6.2.1User Profile download       p. 26
6.2.2HSS initiated update of User Information       p. 26
6.2.2.1Detailed behaviour       p. 27
6.3Authentication procedures       p. 28
6.3.1Detailed behaviour       p. 32
6.4User identity to HSS resolution       p. 33
6.5Implicit registration       p. 34
6.5.1S-CSCF initiated procedures       p. 34
6.5.1.1Registration       p. 34
6.5.1.2De-registration       p. 34
6.5.1.3Authentication       p. 34
6.5.1.4Downloading the user profile       p. 34
6.5.1.5Initiation of a session to a non-registered user       p. 35
6.5.2HSS initiated procedures       p. 35
6.5.2.1Update of User Profile       p. 35
6.5.2.2De-registration       p. 35
6.5.2.3Update of the Charging information       p. 35
6.5.2.4Update of the SIP Digest Authentication Data [R8]       p. 35
6.6Download of the Relevant User Profile and Charging
Information       p. 36
6.6.1HSS initiated update of User Profile       p. 36
6.6.2S-CSCF operation       p. 36
6.7S-CSCF Assignment       p. 36
Top
 7Information element contents       p. 39
7.1Visited Network Identifier       p. 39
7.2Public User Identity       p. 39
7.2aPublic Service Identity [R6]       p. 39
7.2bWildcarded Public Identity [R7]       p. 39
7.2cVoid [R8]
7.3Private User Identity       p. 39
7.3aPrivate Service Identity [R6]       p. 39
7.4S-CSCF Name       p. 39
7.4aAS Name [R6]       p. 39
7.5S-CSCF Capabilities       p. 40
7.6Result       p. 40
7.7User Profile       p. 40
7.8Server Assignment Type       p. 40
7.9Authentication Data       p. 40
7.9.1Item Number       p. 40
7.9.2Authentication Scheme       p. 40
7.9.3Authentication Information       p. 40
7.9.4Authorization Information       p. 40
7.9.5Confidentiality Key       p. 40
7.9.6Integrity Key       p. 40
7.9.7Authentication Context       p. 41
7.9.8Digest Authenticate [R8]       p. 41
7.9.8.1Digest Realm       p. 41
7.9.8.2Void
7.9.8.3Digest Algorithm       p. 41
7.9.8.4Digest QoP       p. 41
7.9.8.5Digest HA1       p. 41
7.9.9Line Identifier [R8]       p. 41
7.10Number Authentication Items       p. 41
7.11Reason for de-registration       p. 41
7.12Charging information       p. 41
7.13Routing information       p. 41
7.14Type of authorization       p. 42
7.15Void
7.16User Data Already Available       p. 42
7.17Associated Private Identities [R6]       p. 42
7.18Originating-Request [R7]       p. 42
7.19User Authorization Request Flags [R7]       p. 42
7.20Loose-Route Indication [R7]       p. 42
7.21S-CSCF Restoration Information [R8]       p. 42
7.22Associated Registered Private Identities [R8]       p. 42
7.23Multiple Registration Indication [R8]       p. 42
7.24Session-Priority [R8]       p. 43
7.25Identities with Emergency Registration [R8]       p. 43
7.26Priviledged-Sender Indication [R10]       p. 43
7.27LIA Flags [R11]       p. 43
7.28Server Assignment Request Flags [R12]       p. 43
Top
 8Error handling procedures       p. 43
8.1Registration error cases       p. 43
8.1.1Cancellation of the old S-CSCF       p. 43
8.1.2Error in S-CSCF name       p. 44
8.1.3Error in S-CSCF assignment type       p. 44
Top
 9Protocol version identification       p. 44Top
 10Operational Aspects       p. 44Top
Annex A[N]Mapping of Cx operations and terminology to Diameter       p. 45
A.1Introduction       p. 45
A.2Cx message to Diameter command mapping       p. 45
A.3Cx message parameters to Diameter AVP mapping       p. 45
A.4Message flows       p. 46
A.4.1Registration– user not registered       p. 47
A.4.2Registration – user currently registered       p. 48
A.4.3UE initiated de-registration       p. 48
A.4.4Network initiated de-registration       p. 49
A.4.4.1Registration timeout       p. 49
A.4.4.2Administrative de-registration       p. 49
A.4.4.3De-registration initiated by service platform       p. 50
A.4.5UE Terminating SIP session set-up       p. 50
A.4.6Initiation of a session to a non-registered user       p. 51
A.4.6aAS originating session on behalf of a non-registered user
[R7]       p. 51
A.4.7User Profile update       p. 52
Top
Annex BUser profile UML model       p. 53
B.1General description       p. 53
B.2Service profile       p. 53
B.2.1Public Identification       p. 54
B.2.1ACore Network Service Authorization [R7]       p. 56
B.2.2Initial Filter Criteria       p. 57
B.2.3Service Point Trigger       p. 58
Top
Annex CConjunctive and Disjunctive Normal Form       p. 60Top
Annex DHigh-level format for the User Profile       p. 63Top
Annex E[N]XML schema for the Cx interface user profile       p. 64Top
Annex F[N]Definition of parameters for service point trigger matching       p. 69Top
Annex G[N]Emergency registrations [R7]       p. 69Top
Annex H[N]Diameter overload control mechanism [R12]       p. 70
H.1General       p. 70
H.2HSS behaviour       p. 70
H.3I/S-CSCF behaviour       p. 70
Top
Annex IDiameter overload node behaviour [R12]       p. 71
I.1Message prioritization       p. 71
Top
Annex JChange history       p. 72Top