Subscriber Data Management

1y ago
15 Views
1 Downloads
574.29 KB
22 Pages
Last View : 22d ago
Last Download : 2m ago
Upload by : Averie Goad
Transcription

Subscriber Data ManagementCx/Dx Interface Description910-6854-001 Revision BSeptember 2013

Copyright 2013 TekelecAll Rights ReservedPrinted in the USA.Legal Information can be accessed from the Main Menu of the optical disc or on theTekelec Customer Support web site in the Legal Information folder of the Product Support tabSales Representative can provide you with information about how to order additional discs.

Publication HistoryRevisionABDateReasonSeptember 2013September 2013Initial Release. Same as 910-6715-001 rev a. Date updated.Added copyright on header page.Cx/Dx Interface Description910-6854-001 Revision Biii

Table of ContentsREFERENCES . V1.INTRODUCTION. 61.1General . 61.2Architecture . 61.3HSS and SLF implications . 61.4Acronyms . 72.SUPPORTED CX/DX MESSAGES . 82.1List of Cx/Dx Messages received by the HSS/SLF . 82.2List of Cx Messages initiated by the HSS . 83.CX MESSAGE FLOWS . 93.1Registration – user not registered . 93.2Registration – user currently registered . 103.3Mobile initiated de-registration . 113.4Registration timeout . 113.5Administrative de-registration . 123.6Service Platform initiated de-registration . 123.7Mobile terminated SIP session set-up . 133.8Initiation of a session to a non-registered user . 133.9User profile update . 144.DX MESSAGE FLOWS . 154.1Dx message to SLF, redirected to Tekelec HSS . 154.2Cx message to HSS, user unknown . 154.3Dx message to SLF, redirected to external HSS . 165.CX MESSAGE CONTENT . 175.1UAR (User-Authorization-Request) . 175.2UAA (User-Authorization-Answer) . 175.3SAR (Server-Assignment-Request) . 175.4SAA (Server-Assignment-Answer) . 185.5LIR (Location-Info-Request) . 185.6LIA (Location-Info-Answer) . 185.7MAR (Multimedia-Auth-Request) . 195.7.1SIP-Auth-Data-Item Content - Request . 195.7.2SIP-Auth-Data-Item Content - Request: Synchronization Failure . 195.8MAA (Multimedia-Auth-Answer) . 195.8.1SIP-Auth-Data-Item Content. 205.9RTR (Registration-Termination-Request) . 205.10RTA (Registration-Termination-Answer) . 205.11PPR (Push-Profile-Request) . 205.12PPA (Push-Profile-Answer) . 216.DX MESSAGE CONTENT . 21Cx/Dx Interface Description910-6854-001 Revision Biv

REFERENCES 3GPP TS 23.008 V6.11.0 (2006-09): “Organization of subscriber data”. 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”. 3GPP TS 33.203 V6.10.0 (2006-09): “Access security for IP-based services”.Cx/Dx Interface Description910-6854-001 Revision Bv

1. Introduction1.1 GeneralThis document aims to provide a description of the SDM Diameter-based Cx and Dx interfaces. The Cxinterface is a basic functionality of the Tekelec HSS component of the Tekelec platform, while the Dxinterface is part of the optional Subscription Locator Function package. The full set of functionalitydescribed 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 keymessages exchanged between the SDM HSS/SLF and the external IMS Diameter peers.1.2 ArchitectureIM-SSFSiSIP-AS SCFDx3GPPCoreNetworkbluesliceMRFCBGCFC, D, Gr, witched: PSTN 3GPP CS CoreCSNetworksSS7IPMultimediaNetworksMedia1.3 HSS and SLF implicationsThe Tekelec HSS implementation is scalable and distributed and therefore does not require the presenceof SLF nodes. In the case where several HSS from different vendors are deployed, the SLF functionalitycan be added to redirect incoming Cx messages to the right HSS. Both the HSS and SLF areimplemented in the same Software process on the SDM, but appear as different Diameter peers toexternal nodes. Both the HSS and SLF can co-reside or be activated independently.Cx/Dx Interface Description910-6854-001 Revision B6

1.4 UAAUARWEEE3GPPDescriptionAuthentication CenterAuthentication TokenBreakout Gateway Control FunctionCall Session Control FunctionEuropean UnionHome Subscriber ServerInterrogating-Control Session Control FunctionIP MultimediaIP Multimedia - Home Subscriber ServiceIP Multimedia Service Switching FunctionIP Multimedia SubsystemInternet ProtocolIP Connectivity Access ndatoryMultimedia-Auth-AnswerMobile Application PartMultimedia-Auth-RequestMedia Gateway Control FunctionMultimedia Resource Function ControllerMultimedia Resource Function ProcessorTekelec Home Location RegisterOptionalOSA Service Capability ServerProxy Call Session Control triction of Hazardous ion-Termination-RequestServing Call Session Control RequestSubscriber Data ManagementSubscriber Data ServerSubscription Locator -RequestWaste Electronic and Electrical Equipment3rd Generation Partnership ProjectCx/Dx Interface Description910-6854-001 Revision B7

2.Supported Cx/Dx Messages2.1 List of Cx/Dx Messages received by the HSS/SLFCx/Dx messageCx-Query Cx-Select-PullCx-Query Resp Cx-Select-Pull RespCx-Put Cx-PullCx-Put Resp Cx-Pull RespCx-Location-QueryCx-Location-Query RespCx-AuthDataReqCx-AuthDataRespDiameter RMAA2.2 List of Cx Messages initiated by the HSSCx messageCx-DeregisterCx-Deregister RespCx-Update Subscr DataCx-Update Subscr Data RespCx/Dx Interface DescriptionDiameter Profile-Answer910-6854-001 Revision BAbbreviationRTRRTAPPRPPA8

3.Cx Message Flows3.1 Registration – user not registeredI-CSCFHSSS-CSCF1 : UAR(Public-User-Identity, Private-User-Identity, Visited-Network-Identity, [User-Authorization-Type], [Destination-Host])2 : UAA(Experimental-Result, [Server-Capabilities])3 : REGISTER()4 : MAR(Public-User-Identity, Private-User Identity, Server-Name, SIP-Number-Auth-Items, SIP-Auth-Data-Item, [Destination-Host])5 : MAA(Public-User-Identity, Private-User-Identity,SIP-Number-Auth-Items, SIP-Auth-Data-Item, Result-Code)6 : 401 UNAUTHORISED()7 : UAR((Public-User-Identity, Private-User-Identity, Visited-Network-Identity, [User-Authorization-Type], [Destination-Host])8 : UAA(Result-Code,Server-Name)9 : REGISTER()10 : SAR(Public-User-Identity,Private-User-Identity, Server-Name, Server-Assignment-Type, User-Data-Already-Available, [Destination-Host])11 : SAA(Private-User-Identity, Result-Code, User-Data, Charging-Information, [Associated-Identities])12 : OK()1: User-Authorization-Type REGISTRATION (0) (default value if not present)2: Experimental-Result-Code {DIAMETER FIRST REGISTRATION (2001),DIAMETER ERROR USER UNKNOWN (5001),DIAMETER ERROR IDENTITIES DONT MATCH (5002),DIAMETER ERROR ROAMING NOT ALLOWED (5004)}5: Result-Code DIAMETER SUCCESS (2001) or Experimental-Result-Code DIAMETER ERROR AUTH SCHEME NOT SUPPORTED (5006)7: User-Authorization-Type REGISTRATION (0) (default value if not present)8: Experimental-Result-Code {DIAMETER FIRST REGISTRATION (2001),DIAMETER ERROR USER UNKNOWN (5001),DIAMETER ERROR IDENTITIES DONT MATCH (5002),DIAMETER ERROR ROAMING NOT ALLOWED (5004)}Cx/Dx Interface Description910-6854-001 Revision B9

10: Server-Assignment-Type REGISTRATION (1)11: Result-Code DIAMETER SUCCESS (2001)3.2 Registration – user currently registeredI-CSCFHSSS-CSCF1 : UAR(Public-User-Identity, Private-User-Identity, Visited-Network-Identity, [User-Authorization-Type], [Destination-Host])2 : UAA(Experimental-Result, Server-Name)3 : REGISTER()4 : SAR(Public-User-Identity,Private-User-Identity, Server-Name, Server-Assignment-Type, User-Data-Already-Available, [Destination-Host])5 : SAA(Private-User-Identity, Result-Code, User-Data, Charging-Information, [Associated-Identities])6 : OK()1: User-Authorization-Type REGISTRATION (0) (default value if not present)2: Experimental-Result-Code {DIAMETER SUBSEQUENT REGISTRATION (2002),DIAMETER ERROR USER UNKNOWN (5001),DIAMETER ERROR IDENTITIES DONT MATCH (5002),DIAMETER ERROR ROAMING NOT ALLOWED (5004)}4: Server-Assignment-Type RE REGISTRATION (2)5: Result-Code DIAMETER SUCCESS (2001)Steps 4 and 5 are optional.Cx/Dx Interface Description910-6854-001 Revision B10

3.3 Mobile initiated de-registrationI-CSCFHSSS-CSCF1 : UAR(Public-User-Identity, Private-User-Identity, Visited-Network-Identity, User-Authorization-Type, [Destination-Host])2 : UAA(Result-Code, Server-Name)3 : REGISTER()4 : SAR([Public-User-Identity], [Private-User-Identity], Server-Name, Server-Assignment-Type, User-Data-Already-Available, [Destination-Host])5 : SAA(Private-User-Identity, Result-Code)6 : OK()1: User-Authorization-Type DE REGISTRATION (1)2: Result-Code DIAMETER SUCCESS (2001) or Experimental-Result-Code {DIAMETER ERROR USER UNKNOWN (5001),DIAMETER ERROR IDENTITIES DONT MATCH (5002)}4:Server-Assignment-Type USER DEREGISTRATION (5)Public-User-Identity or Private-User-Identity must be present5: Result-Code DIAMETER SUCCESS (2001)3.4 Registration timeoutHSSS-CSCF1 : SAR([Public-user-Identity], [Private-User-Identity], Server-Name, Server-Assignmant-Type, User-Data-Already-Available, [Destination-Host])2 : SAA(Private-User-Identity, Result-Code)1: Server-Assignment-Type {TIMEOUT DEREGISTRATION (4),TIMEOUT DEREGISTRATION STORE SERVER NAME (6)}Public-User-Identity or Private-User-Identity must be present2: Result-Code DIAMETER SUCCESS (2001)Cx/Dx Interface Description910-6854-001 Revision B11

3.5 Administrative de-registratiHSSS-CSCF1 : RTR([Public-User-Identity], Private-User-Identity, Deregistration-Reason, Destination-Host, [Associated-Identities])2 : RTA(Result-Code, [Associated-Identities])1: Deregistration-Reason Reason-Code {PERMANENT TERMINATION (0)} Reason-Info{“Subscription deleted”}2: Result-Code {DIAMETER SUCCESS (2001), or Experimental-Result-Code {DIAMETER ERROR USER UNKNOWN (5001),DIAMETER ERROR IDENTITIES DONT MATCH (5002)}3.6 Service Platform initiated de-registration\HSSS-CSCF1 : SAR([Public-User-Identity], [Private-User-Identity], Server-Name, Server-Assignmant-Type, User-Data-Already-Available, [Destination-Host])2 : SAA(Private-User-Identity, Result-Code)1: Server-Assignment-Type ADMINISTRATIVE DEREGISTRATION (8)Public-User-Identity or Private-User-Identity must be present2: Result-Code DIAMETER SUCCESS (2001) or Experimental-Result-Code {DIAMETER ERROR USER UNKNOWN (5001),DIAMETER ERROR IDENTITIES DONT MATCH (5002)}Cx/Dx Interface Description910-6854-001 Revision B12

3.7 Mobile terminated SIP session set-upI-CSCFHSSS-CSCF1 : LIR(Public-User-Identity, [Destination-Host])2 : LIA(Result-Code, [Server-Name])3 : INVITE()2: Result-Code DIAMETER SUCCESS (2001) or{DIAMETER ERROR USER UNKNOWNDIAMETER ERROR INDENTITY NOT REGISTERED (5003)}Experimental-Result-Code (5001),3.8 Initiation of a session to a non-registered userI-CSCFHSSS-CSCF1 : LIR(Public-User-Identity, [Destination-Host])2 : LIA(Experimental-Result, [Server-Capabilities])3 : INVITE()4 : SAR(Public-User-Identity, Private-User-Identity, Server-Name, Server-Assignment-Type, User-Data-Already-Available, [Destination-Host])5 : SAA(Private-User-Identity, Result-Code, User-Data, Charging-Information, [Associated-Identities])6 : 200 OK()2:Experimental-Result-Code {DIAMETER UNREGISTERED SERVICEDIAMETER ERROR USER UNKNOWN (5001)}If Experimental-Result-Code 2003 then Server-Capabilities must be present(2003),4: Server-Assignment-Type UNREGISTERED USER (3)5: Result-Code DIAMETER SUCCESS (2001)Cx/Dx Interface Description910-6854-001 Revision B13

3.9 User profile updateHSSS-CSCF1 : PPR(Private-User-Identity, [User-Data], [Charging-Information], Destination-Host)2 : PPA(Result-Code)1: User-Data and/or Charging-Information must be present2: Result-Code {DIAMETER SUCCESS (2001), DIAMETER UNABLE TO COMPLY (5012)}or Experimental-Result-Code DIAMETER ERROR USER UNKNOWN (5001),DIAMETER ERROR TOO MUCH DATA (5008),DIAMETER ERROR NOT SUPPORTED USER DATA (5009)}Cx/Dx Interface Description910-6854-001 Revision B14

4.Dx Message Flows4.1 Dx message to SLF, redirected to Tekelec HSSCSCFHSSSLFUAR(User)UAA(DiameterSucess RedirectHost AVP HSS)UAR(User)UAA(DiameterSucess)4.2 Cx message to HSS, user unknownCSCFHSSSLFHSSUAR(User)UAA(User Unknown)UAR(User)UAA(DiameterSucess RedirectHost AVP HSS)UAR(User)UAA(DiameterSucess)Cx/Dx Interface Description910-6854-001 Revision B15

4.3 Dx message to SLF, redirected to external HSSCSCFHSSSLFHSSUAR(User)UAA(DiameterSucess RedirectHost AVP HSS)UAR(User)UAA(DiameterSucess)Cx/Dx Interface Description910-6854-001 Revision B16

5.Cx Message ContentCat values: M (Mandatory), O (Optional)5.1 UAR rted ValuesREGISTRATION (0) – DefaultDE REGISTRATION (1)5.2 UAA (User-Authorization-Answer)AVPCatSupported ValuesResult-Code / ExperimentalResultMResult-Code DIAMETER SUCCESS (2001)Experimental-Result-Code DIAMETER FIRST REGISTRATION(2001)DIAMETER SUBSEQUENT REGISTRATION(2002)DIAMETER ERROR USER UNKNOWN(5001)DIAMETER ERROR IDENTITIES DONT MATCH(5002)DIAMETER ERROR ROAMING NOT ALLOWED (5004)DIAMETER REDIRECT INDICATION (3006)Server-CapabilitiesOServer-NameO5.3 SAR ityOPrivate-User-IdentityOServer-NameMCx/Dx Interface DescriptionSupported Values910-6854-001 Revision B17

MDestination-HostOREGISTRATION (1)RE REGISTRATION (2)UNREGISTERED USER (3)TIMEOUT DEREGISTRATION (4)USER DEREGISTRATION (5)TIMEOUT DEREGISTRATION STORE SERVER NAME (6)ADMINISTRATIVE DEREGISTRATION (8)5.4 SAA ityOResult-Code / Associated-IdentitiesODestination-HostOSupported ValuesResult-Code DIAMETER SUCCESS (2001)Experimental-Result-Code DIAMETER ERROR USER UNKNOWN(5001)DIAMETER ERROR IDENTITIES DONT MATCH (5002)DIAMETER REDIRECT INDICATION (3006)5.5 LIR Destination-HostOSupported Values5.6 LIA (Location-Info-Answer)AVPCatSupported ValuesResult-Code / ExperimentalResultMResult-Code DIAMETER SUCCESS (2001)Experimental-Result-Code DIAMETER UNREGISTERED SERVICE(2003)DIAMETER ERROR USER UNKNOWN(5001)DIAMETER ERROR IDENTITY NOT REGISTERED (5003)DIAMETER REDIRECT INDICATION (3006)Cx/Dx Interface Description910-6854-001 Revision B18

Server-CapabilitiesOServer-NameO5.7 MAR upported ValuesSee sections 4.7.1 and 4.7.2SIP-Auth-Data-Item Content - RequestAVPCatSupported -Scheme “Digest-AKAv1-MD5”5.7.2SIP-Auth-Data-Item Content - Request: Synchronization FailureAVPCatSupported -Scheme “Digest-AKAv1-MD5”SIP-AuthorizationMRAND AUTS (binary encoded)5.8 MAA uth-Data-ItemOCx/Dx Interface DescriptionSupported ValuesSee section 4.8.1910-6854-001 Revision B19

Result-Code / ExperimentalResult5.8.1MResult-Code DIAMETER SUCCESS (2001)Experimental-Result-CodeDIAMETER ERROR AUTH SCHEME NOT SUPPORTED(5006)DIAMETER REDIRECT INDICATION (3006) SIP-Auth-Data-Item ContentAVPCatSupported P-Authentication-Scheme “Digest-AKAv1-MD5”SIP-AuthenticateMRAND AUTN (binary Integrity-KeyM5.9 RTR ted ValuesReason-Code PERMANENT TERMINATION (0)Reason-Info “Subscription deleted”5.10 RTA (Registration-Termination-Answer)AVPCatSupported ValuesResult-Code / ExperimentalResultMResult-Code DIAMETER SUCCESS (2001)Experimental-Result-Code DIAMETER ERROR USER UNKNOWN(5001)DIAMETER ERROR IDENTITIES DONT MATCH (5002)Associated-IdentitiesO5.11 PPR (Push-Profile-Request)AVPCx/Dx Interface DescriptionCatSupported Values910-6854-001 Revision B20

onODestination-HostM5.12 PPA (Push-Profile-Answer)AVPCatSupported ValuesResult-Code / ExperimentalResultMResult-Code DIAMETER SUCCESS(2001)DIAMETER UNABLE TO COMPLY (5012)Experimental-Result-Code DIAMETER ERROR USER UNKNOWN(5001),DIAMETER ERROR TOO MUCH DATA(5008),DIAMETER ERROR NOT SUPPORTED USER DATA (5009)6.Dx Message ContentThe Dx interface message content is the same as the Cx message content described in Section 8, withthe addition of the RedirectHost AVP in the UAA, SAA, LIA, MAA messages.Cx/Dx Interface Description910-6854-001 Revision B21

Subscriber Data ManagementCx/Dx Interface Description910-6854-001Revision BCx/Dx Interface Description910-6854-001 Revision B22

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. Cx/Dx Interface Description 910-6854-001 Revision B 8 2. .

Related Documents:

construct over a shared Subscriber Access Detection Subscriber authentication and authorization Subscriber address management G0/1.10 Create a per subscriber interface ("subscriber session") G0/1.10 John Mike Ted John Mike Ted Subscribers are John, Mike and Ted. John and Mike are HSI users, Ted is VoIP user There are 3 subscribers

A subscriber key is a text field that contains a unique value assigned to each subscriber. The subscriber key is used: When a subscriber you import or create already exists in the system. When a subscriber appears multiple times on a data extension (helps with deduplication).

Verifying the Scheduling and Shaping Configuration for Subscriber Access. 70. Configuring Hierarchical CoS Scheduling on MPLS Ethernet Pseudowire Subscriber Interfaces. Interfaces. 72. Enhanced Subscriber Management Subscriber Logical Interfaces or Interface Sets Over Underlying . Logical Interfaces for a CoS scheduler Hierarchy. 72

Subscriber Agreement for each individual Subscriber accessing NASDAQ U.S. data. NASDAQ's definition of Non-Professional Subscriber may permit individuals associated with certain non- commercial organizations (i.e., family investment trusts, investment clubs, etc.) to access NASDAQ U.S. market data at Non-Professional rates.

Per-Subscriber Support of Maximum Transmission Unit for Dynamic Profiles. 54. Understanding Per-subscriber Support of Maximum Transmission Unit for Dynamic Profiles. 54. Configuring Per-subscriber Maximum Transmission Unit for Dynamic Profiles. 56. Dynamic Variables Overview. 58. Predefined Variables in Dynamic Profiles. 60. Junos OS Predefined .

management; 3G call and event data for the Packet Switched (PS) domain . LTE S6a/S6d Interface Description 910-6880-001 Revision B 7 Ref Doc number . LTE S6a/S6d Interface Description 910-6880-001 Revision B 9 2. Functional Description 2.1 SDM ARCHITECTURE OVERVIEW The Subscriber Data Management (SDM) is an Evolved Subscriber Data Management .

SCHOOL RETIREE PREMIUMS WITH1 EMPLOYER CONTRIBUTION (MONTHLY RATE) LEVEL OF COVERAGE CDHP POS Subscriber Only 69.31 146.06 Subscriber 1 Child 101.76 213.04 Subscriber Children 145.46 302.80 Subscriber Spouse 309.66 488.49 Family 359.20 590.21 1 Eligibility information can be found in the Retiree Benefits Guide.

the Subscriber to a reduction in the fees to be paid by it. 7.4 If the Subscriber does not meet the system requirements pursuant to Annex 1 or does not make adaptions pursuant to section 4.2 in a timely manner and malfunctions in the Amadeus System originate therefrom, Amadeus Germany shall be entitled to disconnect the Subscriber from the