910-6854-001 Rev B PDF
910-6854-001 Rev B PDF
910-6854-001 Rev B PDF
1. INTRODUCTION............................................................................................................................ 6
1.1 General ................................................................................................................................. 6
1.2 Architecture ........................................................................................................................... 6
1.3 HSS and SLF implications .................................................................................................... 6
1.4 Acronyms .............................................................................................................................. 7
3GPP TS 23.218 V6.4.0 (2006-06): “IP Multimedia (IM) session handling; IM call model”.
3GPP TS 23.228 V6.14.0 (2006-06): “IP Multimedia Subsystem (IMS); Stage 2”.
3GPP TS 29.228 V6.11.0 (2006-06): “IP Multimedia (IM) Subsystem Cx/Dx Interface;
Signaling flows and message contents”.
3GPP TS 29.229 V6.9.0 (2006-09): “Cx/Dx Interface based on the Diameter protocol;
Protocol details”.
1.1 General
This document aims to provide a description of the SDM Diameter-based Cx and Dx interfaces. The Cx
interface is a basic functionality of the Tekelec HSS component of the Tekelec platform, while the Dx
interface is part of the optional Subscription Locator Function package. The full set of functionality
described in this document is available in Tekelec Release 4.0 onwards.
The document details technical compliance of the interface and provides example call flows of key
messages exchanged between the SDM HSS/SLF and the external IMS Diameter peers.
1.2 Architecture
IM-SSF
Si
SIP-AS / Sh
OSA-SCS
Dh
IM-HSS
Cx
P-CSCF S-CSCF
Dx
SLF
IP-CAN Cx C, D, Gr, Gc
3GPP
UE
HLR/AuC Core
I-CSCF Dx Network
MRFC blueslice
SIP
IM-
MGCF H.248
MGW
Diameter
Circuit-Switched:
• PSTN SS7
• 3GPP CS Core
IP Media
CS Multimedi
Networks a
Networks
The Tekelec HSS implementation is scalable and distributed and therefore does not require the presence
of SLF nodes. In the case where several HSS from different vendors are deployed, the SLF functionality
can be added to redirect incoming Cx messages to the right HSS. Both the HSS and SLF are
implemented in the same Software process on the SDM, but appear as different Diameter peers to
external nodes. Both the HSS and SLF can co-reside or be activated independently.
Acronym Description
AuC Authentication Center
AUTN Authentication Token
BGCF Breakout Gateway Control Function
CSCF Call Session Control Function
EU European Union
HSS Home Subscriber Server
I-CSCF Interrogating-Control Session Control Function
IM IP Multimedia
IM-HSS IP Multimedia - Home Subscriber Service
IM-SSF IP Multimedia Service Switching Function
IMS IP Multimedia Subsystem
IP Internet Protocol
IP-CAN IP Connectivity Access Network
LIA Location-Info-Answer
LIR Location-Info-Request
M Mandatory
MAA Multimedia-Auth-Answer
MAP Mobile Application Part
MAR Multimedia-Auth-Request
MGCF Media Gateway Control Function
MRFC Multimedia Resource Function Controller
MRFP Multimedia Resource Function Processor
ngHLR Tekelec Home Location Register
O Optional
OSA-SCS OSA Service Capability Server
P-CSCF Proxy Call Session Control Function
PPA Push-Profile-Answer
PPR Push-Profile-Request
RoHS Restriction of Hazardous Substances
RTA Registration-Termination-Answer
RTR Registration-Termination-Request
S-CSCF Serving Call Session Control Function
SAA Server-Assignment-Answer
SAR Server-Assignment-Request
SDM Subscriber Data Management
SDS Subscriber Data Server
SLF Subscription Locator Function
UAA User-Authorization-Answer
UAR User-Authoriztion-Request
WEEE Waste Electronic and Electrical Equipment
3GPP 3rd Generation Partnership Project
2 : UAA(Experimental-Result, [Server-Capabilities])
3 : REGISTER()
6 : 401 UNAUTHORISED()
8 : UAA(Result-Code,Server-Name)
9 : REGISTER()
12 : OK()
2 : UAA(Experimental-Result, Server-Name)
3 : REGISTER()
6 : OK()
2 : UAA(Result-Code, Server-Name)
3 : REGISTER()
5 : SAA(Private-User-Identity, Result-Code)
6 : OK()
HSS S-CSCF
2 : SAA(Private-User-Identity, Result-Code)
HSS S-CSCF
2 : RTA(Result-Code, [Associated-Identities])
HSS S-CSCF
2 : SAA(Private-User-Identity, Result-Code)
1 : LIR(Public-User-Identity, [Destination-Host])
2 : LIA(Result-Code, [Server-Name])
3 : INVITE()
1 : LIR(Public-User-Identity, [Destination-Host])
2 : LIA(Experimental-Result, [Server-Capabilities])
3 : INVITE()
6 : 200 OK()
HSS S-CSCF
2 : PPA(Result-Code)
UAR(User)
UAR(User)
UAA(DiameterSucess)
UAR(User)
UAA(User_Unknown)
UAR(User)
UAR(User)
UAA(DiameterSucess)
UAR(User)
UAR(User)
UAA(DiameterSucess)
Private-User-Identity M
Visited-Network-Identifier M
Server-Name O
Private-User-Identity O
Server-Name M
Destination-Host O
Charging-Information O
Associated-Identities O
Destination-Host O
Destination-Host O
Server-Name O
Private-User-Identity M
SIP-Number-Auth-Items M
Server-Name M
Destination-Host O
Private-User-Identity O
SIP-Number-Auth-Items O
SIP-Authorization M XRES
Confidentiality-Key O
Integrity-Key M
Private-User-Identity M
Associated-Identities O
User-Data O
Charging-Information O
Destination-Host M
6. Dx Message Content
The Dx interface message content is the same as the Cx message content described in Section 8, with
the addition of the RedirectHost AVP in the UAA, SAA, LIA, MAA messages.