Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 29.228  Word version:  18.0.0

Top   Top   None   None   Next
1…   6…   A… 
1 Scope  2 References  3 Definitions, symbols and abbreviations  3.1 Definitions  3.2 Abbreviations  4 Main Concept  5 General Architecture 
...

 

1  Scope  p. 8

This 3GPP Technical Specification (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.
  3. 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.
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.
Up

2  References  p. 8

[1]
TS 23.228: "IP Multimedia (IM) Subsystem - Stage 2".
[2]
TS 24.228: "Signalling flows for the IP multimedia call control based on SIP and SDP".
[3]
TS 33.203: "Access security for IP-based services".
[4]
TS 23.002: "Network architecture".
[5]
TS 29.229: "Cx Interface based on Diameter - Protocol details".
[6]
TS 23.218: "IP Multimedia (IM) Session Handling; IP Multimedia (IM) call model".
[7]
RFC 2045  "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies".
[8]
TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP" - stage 3.
[9]  Void.
[10]
TS 23.141: "Presence Service; Architecture and Functional Description".
[11]
RFC 3261  "SIP: Session Initiation Protocol".
[12]
RFC 4566  "SDP: Session Description Protocol".
[13]
IEEE 1003.1-2004, Part 1: Base Definitions.
[14]
RFC 2486:  "The Network Access Identifier".
[15]
RFC 3966:  "The tel URI for Telephone Numbers".
[16]  Void.
[17]
TS 23.003: "Numbering, addressing and identification".
[18]
TS 23.008: "Organization of subscriber data".
[19]
TS 23.380: "IMS Restoration Procedures".
[20]  Void
[21]
RFC 4005:  "Diameter Network Access Server Application".
[22]
RFC 4412:  "Communications Resource Priority for the Session Initiation Protocol (SIP)".
[23]
TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[24]
RFC 7683:  "Diameter Overload Indication Conveyance".
[25]
TS 22.153: "Multimedia Priority Service".
[26]
ANSI X3.4: "Coded Character Set - 7-bit American Standard Code for Information Interchange".
[27]
RFC 7944:  "Diameter Routing Message Priority".
[28]  Void
[29]
RFC 8583:  "Diameter Load Information Conveyance".
[30]
TS 23.280: "Common functional architecture to support mission critical services".
[31]
RFC 6733:  "Diameter Base Protocol".
[32]
TS 24.323: "3GPP IP Multimedia Subsystem (IMS) service level tracing management object (MO)".
[33]
RFC 7616:  "HTTP Digest Access Authentication".
Up

3  Definitions, symbols and abbreviations  p. 9

3.1  Definitions  p. 9

For the purposes of the present document, the following terms and definitions given in TS 23.003 apply:
Distinct Public Service Identity
Distinct Public User Identity
Public Service Identity
Public User Identity
Wildcarded Public Service Identity
Wildcarded Public User Identity
For the purposes of the present document, the following terms and definitions apply.
Common Part (of a user profile):
Contains Initial Filter Criteria instances that should be evaluated both for registered and unregistered Public User Identities, or for unregistered Public Service Identities in the S-CSCF.
Complete user profile:
Contains the Initial Filter Criteria instances of all three different user profile parts; registered part, unregistered part and common part.
IP Multimedia session:
IP Multimedia session and IP Multimedia call are treated as equivalent in this specification.
Authentication pending flag:
A flag that indicates that the authentication of a Public User Identity - Private User Identity pair is pending and waiting for confirmation.
Charging information:
Data that is sent in the Charging-Information AVP.
Allowed WAF and/or WWSF identities:
A list of network addresses identifying WebRTC Authentication Functions (WAFs) and/or WebRTC Web Server Functions (WWSFs) allowed for a subscription.
Implicitly registered Public User Identity set:
A set of Public User Identities, which are registered and de-registered simultaneously when any of the Public User Identities belonging to that set is registered or de-registered.
Not Registered State:
Public Identity is not Registered and has no S-CSCF assigned.
Private Identity:
Either a Private User Identity or a Private Service Identity.
Public Identity:
Either a Public User Identity or a Public Service Identity.
Registered Part (of a user profile):
Contains Initial Filter Criteria instances that should be evaluated only for registered Public User Identities in the S-CSCF. iFCs from the registered part need not be evaluated when the Public Identity is unregistered.
Registered State:
Public User Identity is Registered at the request of the user and has an S-CSCF assigned.
S-CSCF reassignment pending flag:
A flag that is handled only when IMS Restoration Procedures are supported.and that indicates that the subscription may be reassigned to a new S-CSCF (i.e. the current S-CSCF is not responding)
Unregistered part (of a user profile):
Contains Initial Filter Criteria instances that should be evaluated only for unregistered Public Identities in the S-CSCF. iFCs from the unregistered part need not be evaluated when the Public User Identity is registered.
Unregistered State:
Public Identity is not Registered but has a serving S-CSCF assigned to execute Unregistered state services as a consequence of a terminating request, or an originating request from an AS on behalf of a user, or there is an S-CSCF keeping the user profile stored.
User information:
The user related data that the S-CSCF requests from the HSS or HSS pushes to the S-CSCF, e.g. user profile,charging information, allowed WAF and/or WWSF identities and authentication information.
User profile:
Data that is sent in the User-Data AVP.
Up

3.2  Abbreviations  p. 10

For the purposes of the present document, the following abbreviations apply:
AVP
Attribute Value Pair
C
Conditional
CSCF
Call Session Control Function
DRMP
Diameter Routing Message Priority
DSCP
Differentiated Services Code Point
GIBA
GPRS-IMS-Bundled-Authentication
HSS
Home Subscriber Server
IE
Information Element
IP
Internet Protocol
I-CSCF
Interrogating CSCF
IM
IP Multimedia
IMS
IP Multimedia Subsystem
M
Mandatory
MPS
Multimedia Priority Service
NASS
Network Attachment SubSystem
O
Optional
P-CSCF
Proxy CSCF
SIP
Session Initiation Protocol
SLF
Server Locator Function
S-CSCF
Serving CSCF
WAF
WebRTC Authentication Function
WWSF
WebRTC Web Server Function
Up

4  Main Concept  p. 11

This document presents the Cx interface related functional requirements of the communicating entities.
It gives a functional classification of the procedures and describes the procedures and message parameters.
Error handling flows, protocol version identification, etc. procedures are also included.

5  General Architecture  p. 11

This clause further specifies the architectural assumptions associated with the Cx reference point, building on TS 23.228 and also the Px reference point building upon TS 23.141.

5.1  Functional requirements of network entities  p. 11

5.1.1  Functional requirements of P-CSCF  p. 11

There is no requirement for the interaction between the P-CSCF and the HSS.

5.1.2  Functional requirements of I-CSCF  p. 11

The I-CSCF communicates with the HSS over the Cx interface.
For functionality of the I-CSCF refer to TS 23.002.

5.1.3  Functional requirements of S-CSCF  p. 11

The S-CSCF communicates with the HSS over the Cx interface.
For functionality of the S-CSCF refer to TS 23.002.

5.1.4  Functional requirements of HSS  p. 11

The HSS communicates with the I-CSCF and the S-CSCF over the Cx interface.
For functionality of the HSS refer to TS 23.002.

5.1.5  Functional classification of Cx interface procedures  p. 11

Operations on the Cx interface are classified in functional groups:
  1. Location management procedures
    • The operations regarding registration and de-registration.
    • Location retrieval operation.
  2. User data handling procedures
    • The download of user information during registration and to support recovery mechanisms.
    • Operations to support the updating of user data and recovery mechanisms.
  3. User authentication procedures
  4. IMS Restoration Procedures (see TS 23.380) to support S-CSCF service interruption
Up

5.1.6  Functional Requirements of the Presentity Presence Proxy |R6|  p. 12

The interaction between the Presentity Presence Proxy and the HSS, referred to as the Px interface, is handled using the mechanisms defined for the Cx interface.

Up   Top   ToC