Tech-invite3GPP-SpecsFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TS 29.228 (CT4)
IMS Cx and Dx Interfaces – Signalling Flows and Message Contents

use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
for a better overview, the Table of Contents (ToC) is reproduced
V16.0.0 (Wzip)2019/09  82 p.
V15.3.0 (PDF)2019/09  91 p.
V14.6.02019/09  91 p.
V13.5.0  2017/09  89 p.
V12.10.0  2017/06  86 p.
V11.11.0  2015/09  79 p.
V10.8.0  2013/09  75 p.
V9.12.0  2013/09  73 p.
V8.19.0  2013/09  73 p.
V7.18.0  2013/03  65 p.
V6.17.0  2010/12  60 p.
V5.22.0  2010/12  53 p.

Rapporteur:  Ms. Bartolome, Maria-Cruz

This TS specifies:
  • The interactions between the HSS (Home Subscriber Server) and the CSCF (Call Session Control Functions), referred to as the Cx interface.
  • The interactions between the CSCF and the SLF (Server Locator Function), referred to as the Dx interface.
  • The interactions between the SIP Core and the SIP database, referred to as the Cx interface, for the Mission Critical Services, where this interface is named as AAA-1, as described in TS 23.280.

full Table of Contents for  TS 29.228  Word version:   16.0.0

 

Here   Top

 

1  ScopeWord-p. 7
2  References
3  Definitions, symbols and abbreviationsWord-p. 8
4  Main ConceptWord-p. 10
5  General Architecture
6  Procedure Descriptions
6.1  Location management proceduresWord-p. 12
6.2  User data handling proceduresWord-p. 29
6.3  Authentication proceduresWord-p. 32
6.4  User identity to HSS resolutionWord-p. 36
6.5  Implicit registrationWord-p. 37
6.6  Download of the Relevant User Profile and Charging Information and Allowed WAF and/or WWSF Identities
6.7  S-CSCF Assignment
7  Information element contentsWord-p. 42
7.1  Visited Network Identifier
7.2  Public User IdentityUp
7.2a  Public Service Identity [R6]
7.2b  Wildcarded Public Identity [R7]
7.2cVoid
7.3  Private User Identity
7.3a  Private Service Identity [R6]
7.4  S-CSCF Name
7.4a  AS Name [R6]
7.5  S-CSCF CapabilitiesWord-p. 43
7.6  Result
7.7  User Profile
7.8  Server Assignment TypeUp
7.9  Authentication Data
7.10  Number Authentication Items
7.11  Reason for de-registration
7.12  Charging informationUp
7.13  Routing information
7.14  Type of authorization
7.15Void
7.16  User Data Already AvailableWord-p. 46
7.17  Associated Private Identities [R6]
7.18  Originating-Request [R7]
7.19  User Authorization Request Flags [R7]
7.20  Loose-Route Indication [R7]
7.21  S-CSCF Restoration Information [R8]
7.22  Associated Registered Private Identities [R8]
7.23  Multiple Registration Indication [R8]Up
7.24  Session-Priority [R8]
7.25  Identities with Emergency Registration [R8]
7.26  Priviledged-Sender Indication [R10]Word-p. 47
7.27  LIA Flags [R11]
7.28  Server Assignment Request Flags [R12]
7.29  Allowed WAF and/or WWSF Identities [R12]
7.30  RTR Flags [R15]
8  Error handling procedures
9  Protocol version identification
10  Operational Aspects
A (Normative)  Mapping of Cx operations and terminology to DiameterWord-p. 49
B  User profile UML modelWord-p. 57
C  Conjunctive and Disjunctive Normal FormWord-p. 64
D  High-level format for the User ProfileWord-p. 67
E (Normative)  XML schema for the Cx interface user profileWord-p. 68
F (Normative)  Definition of parameters for service point trigger matchingWord-p. 73
G (Normative)  Emergency registrations [R7]
H (Normative)  Diameter overload control mechanism [R12]Word-p. 74
I  Diameter overload node behaviour [R12]Word-p. 75
J (Normative)  Diameter message priority mechanism [R13]
K (Normative)  Diameter load control mechanism [R14]Word-p. 77
L  Change historyWord-p. 78

Up   Top