Transcription
Subscriber Data ManagementLTE S6a/S6d Interface Description910-6720-001 Revision AJune 2013
Copyright 2013 TekelecAll Rights ReservedNoticeInformation in this documentation is subject to change without notice. Unauthorized use, copying, or translation of thisdocumentation can result in civil or criminal penalties.Any export of Tekelec products is subject to the export controls of the United States and the other countries whereTekelec has operations.No part of this documentation may be reproduced, translated, or transmitted in any form or by any means, electronicor mechanical, including photocopying or recording, for any purpose without the express written permission of anauthorized representative of Tekelec.Other product names used herein are for identification purposes only, and may be trademarks of their respectivecompanies.RoHS 5/6 - As of July 1, 2006, all products that comprise new installations shipped to European Union membercountries will comply with the EU Directive 2002/95/EC "RoHS" (Restriction of Hazardous Substances). Theexemption for lead-based solder described in the Annex will be exercised. RoHS 5/6 compliant components will haveunique part numbers as reflected in the associated hardware and installation manuals.WEEE - All products shipped to European Union member countries comply with the EU Directive 2002/96/EC, WasteElectronic and Electrical Equipment. All components that are WEEE compliant will be appropriately marked. For moreinformation regarding Tekelec's WEEE program, contact your sales representative.TrademarksTEKELEC, ngHLR, Subscriber Data Server (SDS) are trademarks of Tekelec. Tekelec and the Tekelec logo areregistered trademarks of Tekelec. All other trademarks are the property of their respective owners.Ordering InformationYour Tekelec Sales Representative can provide you with information about how to order additional discs.TekelecSubscriber Data Management1751 RichardsonSuite 5.200Montréal, CanadaTel: (514) 935-9700Fax: (514) 932-9701http://www.tekelec.com
Publication HistoryRevisionADateJune 2013SDM LTE S6a/S6d Interface DescriptionReasonInitial Release.Same as 910-6506 and 6560-001. Date and copyright updated.910-6720-001 Revision Aiii
TABLE OF CONTENTS1.INTRODUCTION . 61.1General . 61.2Document Scope . 61.3References. 61.4Acronyms . 82.FUNCTIONAL DESCRIPTION . 102.1SDM Architecture Overview. 102.2LTE-HSS Subscriber Profiles . 112.3LTE-HSS Use Cases . 112.4S6a/S6d Supported Messages . 122.5Protocol Stack & compliance . 123.LOCATION MANAGEMENT PROCEDURES . 133.1Update Location Procedure . 133.1.1 HSS Behavior . 133.1.2 ULR message . 153.1.3 ULA message . 163.2Cancel Location Procedure . 193.2.1 HSS Behavior . 193.2.2 CLR message . 203.2.3 CLA message . 213.3Purge UE Procedure . 213.3.1 HSS Behavior . 213.3.2 PUR message . 223.3.3 PUA message. 234.SUBSCRIBER DATA HANDLING PROCEDURES . 244.1Insert Subscriber Data Procedure . 244.1.1 HSS Behavior . 244.1.2 IDR message . 254.1.3 IDA message . 284.2Delete Subscriber Data Procedure . 294.2.1 HSS Behavior . 294.2.2 DSR message . 304.2.3 DSA message. 315.AUTHENTICATION PROCEDURES . 325.1Authentication Information Retrieval Procedure . 325.1.1 HSS Behavior . 325.1.2 AIR message . 325.1.3 AIA message . 34SDM LTE S6a/S6d Interface Description910-6720-001 Revision Aiv
6.FAULT RECOVERY PROCEDURES . 356.1Reset Procedure . 356.1.1 HSS Behavior . 356.1.2 RSR message . 356.1.3 RSA message. 357.NOTIFICATION PROCEDURES . 367.1Notification Procedure . 367.1.1 HSS Behavior . 367.1.2 NOR message . 377.1.3 NOA message . 39SDM LTE S6a/S6d Interface Description910-6720-001 Revision Av
1. Introduction1.1 GeneralThis document aims to provide a description of the S6a/S6d Diameter-based interface as supported bythe SDM. The S6a/S6d interface is part of the LTE-HSS front-end component of the SDM, alongside the3GPP HLR, IMS HSS, AAA server, SIP Application Server and ENUM server. Like all these other frontend components, the LTE HSS leverages the centralized Subscriber Data Server (SDS 3000 ) back-enddatabase for subscriber profile information.1.2 Document ScopeThis document provides interface compliance details in order to enable interoperability testing betweenthe Tekelec LTE-HSS and other vendor’s Mobility Management Entities (MME) and Serving GPRSSupport Nodes (SGSN). For both S6a (MME-HSS) and S6d (SGSN-HSS), the document will provide thesupported use cases and messages, as well as supported AVPs.1.3 ReferencesDoc numberVersionAuthorDoc name[1]TS 29.272V9.0.03GPPMME and SGSN related interfaces based on Diameter protocol[2]TS 23.401V9.2.03GPPGPRS enhancements for E-UTRAN access[3]TS 23.008V9.0.03GPPOrganization of subscriber data[4]TS 23.003V9.0.03GPPNumbering, addressing and identification[5]TS 24.301V9.0.03GPPNon-Access-Stratum (NAS) protocol for Evolved PacketSystem (EPS)[6]TS 33.401V9.1.03GPP3GPP System Architecture Evolution: Security Architecture[7]TS 33.102V9.0.03GPP3G Security; Security Architecture[8]TS 33.210V8.3.03GPP3G Security; Network Domain Security, IP Networks LayerSecurity[9]TS 33.220V9.1.03GPPGeneric Authentication Architecture (GAA); Genericbootstrapping architecture[10]TS 29.002V7.4.03GPPMAP[11]TS 29.273V9.0.03GPP3GPP EPS AAA interfaces[12]RFC 3588IETFDiameter Base Protocol[13]RFC 2104IETFHMAC: Keyed-Hashing for Message AuthenticationRefLTE S6a/S6d Interface Description910-6720-001 Revision A6
AuthorDoc nameRFC 4004IETFDiameter Mobile IPv4 Application[15]RFC 5447IETFDiameter Mobile IPv6[16]TS 29.2123GPPPolicy and charging control over Gx reference point[17]TS 29.2143GPPPolicy and charging control over Rx reference point[18]TS 32.2993GPPTelecommunication management; Charging management;Diameter charging applications[19]TS 32.2513GPPTelecommunication management; Charging management;Packet Switched (PS) domain charging[20]TS 32.0153GPPTelecommunications management; Charging management; 3Gcall and event data for the Packet Switched (PS) domain[21]TS 32.2153GPPTelecommunication management; Charging management;Charging data description for the Packet Switched (PS) domain[22]TS 23.0603GPPGeneral Packet Radio Service (GPRS); Service description;Stage 2[23]TS 29.0613GPPInterworking between the Public Land Mobile Network (PLMN)supporting packet based services and Packet Data Networks(PDN)[24]TS 29.0603GPPGeneral Packet Radio Service (GPRS); GPRS TunnelingProtocol (GTP) across the Gn and Gp interface[25]TS 29.2293GPPCx and Dx interfaces based on the Diameter protocol; Protocoldetails[26]TS 29.3293GPPSh interface based on the Diameter protocol; Protocol detailsRefDoc number[14]VersionLTE S6a/S6d Interface Description910-6720-001 Revision A7
1.4 IPSLFSRFTCPDescriptionrd3 Generation Project ProgramAuthentication Information AnswerAuthentication Information RequestAuthentication CenterAttribute Value PairBarring of Outgoing International CallsCancel Location AnswerCancel Location RequestConcerned Signaling PointDelete Subscriber Data AnswerDelete Subscriber Data RequestElectronic NumbersEvolved Subscriber Data ManagementEvolved UMTS Terrestrial Radio Access NetworkGSM/Edge Radio Access NetworkGeneral Packet Radio ServiceHome Location RegisterHome Subscriber ServerInsert Subscriber Data AnswerInsert Subscriber Data RequestInternational Mobile StationInternational Mobile Subscriber IdentityLong Term EvolutionMobile Application PartMobility Management EntitiesMobile Number PortabilityMobile Station (international) ISDN NumberNotify AnswerNotify RequestPacket Data NetworkPurge UE AnswerPurge UE RequestReset AnswerReset RequestStream Control Transmission ProtocolSubscriber Data ManagementSubscriber Data ServerServing GPRS Support NodesSubscriber Identity ModuleSession Initiation ProtocolSubscription Locator FunctionSignaling Relay FunctionTest Communications ProcessorLTE S6a/S6d Interface Description910-6720-001 Revision A8
AcronymUEULULAULRUMTSUTRANDescriptionUser ElementUpdate LocationUpdate Location AnswerUpdate-Location-RequestUniversal Mobile Telecommunications SystemUMTS Terrestrial Radio Access NetworkLTE S6a/S6d Interface Description910-6720-001 Revision A9
2. Functional Description2.1 SDM Architecture OverviewThe Subscriber Data Management (SDM) is an Evolved Subscriber Data Management (eSDM) platform,built with the objective to manage any number and type of profiles of a given subscriber.The high-level architecture of the SDM is divided in 4 parts: The SDS, a distributed back-end subscriber databaseThe Global Schema abstraction layerThe front-end eSDM applicationsThe protocol stacks (interface layer)All the SDM front-end eSDM applications leverage the same subscriber profile database, which acts as a3GPP User Data Repository. The front-end applications also share subscriber state and context, andtherefore can trigger inter-application logic.Alongside the LTE-HSS, the other currently supported front-end eSDM applications are; 3GPP HLR/AuCIMS HSS and SLFSIP Application Server (Registrar, Redirection server, User Agent Gateway)AAA serverENUM serverSubscriber Signaling Router, including MNP-SRFLTE S6a/S6d Interface Description910-6720-001 Revision A10
The LTE-HSS application shares the following components with the other elements of the SDM platform: Shared subscription profiles across GPRS/UMTS (PS) and LTE (EPS)Shared subscriber volatile data across GPRS/UMTS (PS) and LTE (EPS)Shared AuC for GERAN, UTRAN and E-UTRAN authenticationShared Base Diameter Stack with the IMS-HSS2.2 LTE-HSS Subscriber ProfilesThe LTE-HSS subscriber profile leverages the existing 3GPP Release-6 compliant Packet-SwitchedDomain subscriber profile. Among other things, it leverages the multi-SIM / Multi-IMSI / Multi-MSISDN /Multi-Service-Profile architecture of the Tekelec SDM. New LTE-specific subscription fields have beenadded to the profile.The PDN context required for LTE is supported alongside the GPRS context already existing forGPRS/UMTS. Operators therefore have the choice to provision one or the other (or both).2.3 LTE-HSS Use CasesPhaseTarget SW vehicleUse casesLTE-HSS Phase 1R5.3.0S6a and S6d IOT with MME/SGSN E mobilityInter-MME mobilityE-UTRAN authenticationS6a, S6d and Gr IOT with MME/SGSN vendors:R5.3.2ISR/ISADSR/DSA3G/4G mobility with non-S6d SGSNsGERAN/UTRAN/EUTRAN authenticationHSS-triggered provisioningPUR/PUARSR/RSAProvide Authentication toward Legacy network.LTE-HSS Phase 2LTE-HSS Phase 3-LTE-HSS Phase 4LTE-HSS Phase 5R5.3.3R6.1.0Compute a MAP-SAI message and send to legacyHLR upon AIR for IMSI defined with an Off BoardSimTypeProvide a seamless 3G-4G and 4G-3G roaming withlegacy HLRs.-Compute a MAP-UL upon ULR if the IMSI was 3Gregistered in an external HLR upon 3G-4G roaming-Send CLR message to MME upon 4G-3G roamingwhen receiving a MAP-CL from legacy HLRFull R9 standard compliancyCS Voice redirection to OneVoiceLTE S6a/S6d Interface Description910-6720-001 Revision A11
2.4 S6a/S6d Supported MessagesMessageAbbreviationMessage directionLTE-HSS complianceUpdate-Location-RequestULRMME - HSSSupported 5.3.0Update-Location-AnswerULAHSS - MMESupported 5.3.0Authentication-Information-RequestAIRMME - HSSSupported 5.3.0Authentication-Information-AnswerAIAHSS - MMESupported 5.3.0Cancel-Location-RequestCLRHSS - MMESupported 5.3.3Cancel-Location-AnswerCLAMME - HSSSupported 5.3.3Insert-Subscriber-Data-RequestIDRHSS - MMESupported 5.3.3Insert-Subscriber-Data-AnswerIDAMME - HSSSupported 5.3.3Delete-Subscriber-Data-RequestDSRHSS - MMESupported 5.3.3Delete-Subscriber-Data-AnswerDSAMME - HSSSupported 5.3.3Purge-UE-RequestPURMME - HSSSupported 5.3.3Purge-UE-AnswerPUAHSS - MMESupported 5.3.3Reset-RequestRSRHSS - MMESupported 5.3.3Reset-AnswerRSAMME - HSSSupported 5.3.3Notify-RequestNORMME - HSSSupported 5.3.3Notify-AnswerNOAHSS - MMESupported 5.3.32.5 Protocol Stack & complianceThe Tekelec LTE HSS supports S6a/S6d application over Diameter/TCP and Diameter/SCTP.The S6a/S6d implementation in R5.3.3 is compliant with TS 29.272 v9.0.0 (Sep-2009) and TS 23.401v9.2.0 (Sep-2009).LTE S6a/S6d Interface Description910-6720-001 Revision A12
3. Location Management Procedures3.1 Update Location ProcedureThe Update Location Procedure shall be used between the MME and the HSS and between the SGSNand the HSS to update location information in the HSS. The procedure shall be invoked by the MME orSGSN and is used: to inform the HSS about the identity of the MME or SGSN currently serving the user, andoptionally in addition;to update MME or SGSN with user subscription data;to provide the HSS with other user data, such as Terminal Information.This procedure uses the commands Update-Location-Request/Answer (ULR/ULA) in the Diameterapplication.3.1.1 HSS Behavior When receiving an Update Location request the HSS will check whether the IMSI is known.If it is not known, a Result Code of DIAMETER ERROR USER UNKNOWN will be returned.If it is known, but the subscriber has no Subscriber Profile Assigned, the HSS returns a ResultCode of DIAMETER ERROR UNKNOWN EPS SUBSCRIPTION.If the Update Location Request is received over the S6a interface, and the subscriber has not anyAPN configuration, the HSS will return a Result Code ofDIAMETER ERROR UNKNOWN EPS SUBSCRIPTION.The HSS will check whether the RAT type the UE is using is allowed. If it is not, a Result Code ofDIAMETER ERROR RAT NOT ALLOWED will be returned.The HSS will check whether roaming is not allowed in the VPLMN due to ODB. If so a ResultCode of DIAMETER ERROR ROAMING NOT ALLOWED will be returned.If the Update Location Request is received over the S6a interface, the HSS will send a CancelLocation Request (CLR) to the previous MME (if any) and replace the stored MME-Identity withthe received value (the MME-Identity is received within the Origin-Host AVP). If the "Initial-AttachIndicator" flag was set in the received request, the HSS will send a Cancel Location Request(CLR) to the SGSN if there is an SGSN registration.If the Update Location Request is received over the S6d interface, the HSS will send a CancelLocation Request (CLR) to the previous SGSN (if any) and replace the stored SGSN-Identity withthe received value (the SGSN-Identity is received within the Origin-Host AVP). If the "InitialAttach-Indicator" flag was set in the received request, the HSS will send a Cancel LocationRequest (CLR) to the MME if there is an MME registration.If the "Single-Registration-Indication" flag was set in the received request, the HSS will send aMAP Cancel Location message to the SGSN, delete the stored SGSN address and SGSNnumber.If no result code has been sent to the MME or SGSN so far, the HSS will include the subscriptiondata in the ULA command according to the ULR-Flags and the supported/unsupported features ofthe MME or SGSN, unless an explicit "skip subscriber data" indication has been received in therequest, and will return a Result Code of DIAMETER SUCCESS.LTE S6a/S6d Interface Description910-6720-001 Revision A13
3.1.1.1 When the APN-Configuration-Profile AVP is present in the Subscription-Data AVP sent within aULA, the AVP will contain at least the default APN Configuration and a Context-Identifier AVPthat identifies the per subscriber’s default APN configuration.The GPRS Subscription data (if available in the HSS) will only be present in the ULA command ifit was indicated by the serving node in the ULR-Flags AVP, or when the Update LocationRequest is received over the S6d interface and there is no EPS subscription data stored for thesubscriber.Subscriber-Status AVP will be present in the Subscription-Data AVP when sent within a ULA. Ifthe value "OPERATOR DETERMINED BARRING" is sent, the Operator-Determined-BarringAVP or HPLMN-ODB AVP will also be present in the Subscription-Data AVP, or vice versa.If a Result Code of DIAMETER SUCCESS is returned, the HSS will set the Separation Indicationin the response.Not supported in current releaseLCS-Info, All LCS-related procedures and Trace FunctionLTE S6a/S6d Interface Description910-6720-001 Revision A14
3.1.2 ULR messageThe table below provides the supported ULR esYesYesOOOYesMBitBit 0Bit 1Bit 2Bit 3Bit 4Bit YesCUTRAN (1000)GERAN (1001)EUTRAN (1004)e.164 addressLTE S6a/S6d Interface DescriptionCatMMMMMMMNotesSpecified by MMENO STATE MAINTAINEDSpecified by MMESpecified by MMEHSS hostHSS realmMust contain the active IMSI of the subscriber (note: LTE-HSS supportsthe Multi-IMSI per SIM card, and dynamic association of IMSIs)Supported by the HSS in this d-IndicatorSkip Subscriber catorInitial-Attach-Indicator910-6720-001 Revision Aexpected value010 or 10 or 10015
3.1.3 ULA messageThe table below provides the supported ULA -Access-ModeNoYesCCLTE S6a/S6d Interface DescriptionNotesSpecified by MMENO STATE MAINTAINEDSpecified by MMESpecified by MMESupported by the HSS in this xHCHSS will reply only with the set of features that are supported by boththe MME/SGSN and HSS.DIAMETER SUCCESSDIAMETER ERROR USER UNKNOWN (5001)DIAMETER ERROR UNKNOWN EPS SUBSCRIPTION (5420)DIAMETER ERROR RAT NOT ALLOWED (5421)DIAMETER ERROR ROAMING NOT ALLOWED (5004)Bit 0 – Separation Indication – HSS always sets this bit to 1Includes the complete subscription profile of the user. Present ifsuccess is reported, unless an explicit "skip subscriber data"indication was present in the ULR.SERVICE GRANTED (0)OPERATOR DETERMINED BARRING (1)The MSISDN set as displayed for this IMSI. Note the LTE-HSSsupports Multi-MSISDN per subscription.Not supported, not sent by HSSPACKET AND CIRCUIT (0)ONLY PACKET (2)910-6720-001 Revision A16
BitDescription0All Packet Oriented Services Barred1Roamer Access HPLMN-AP Barred2Roamer Access to VPLMN-AP Barred3Barring of all outgoing calls4Barring of all outgoing international calls5Barring of all outgoing international calls except thosedirected to the home PLMN country6Barring of all outgoing inter-zonal calls7Barring of all outgoing inter-zonal calls except thosedirected to the home PLMN country8Barring of all outgoing international calls except thosedirected to the home PLMN country and Barring of all outgoing interzonal callsBitDescription0HPLMN specific barring type 11HPLMN specific barring type 22HPLMN specific barring type 33HPLMN specific barring type 4Up to 10 Zone Codes, as provisioned in the subscriber esCBitDescription0UTRAN Not Allowed1GERAN Not Allowed2GAN Not Allowed3I-HSPA-Evolution Not Allowed4E-UTRAN Not Allowed5HO-To-Non-3GPP-Access Not AllowedAs provisioned in the subscriber -Info-ListNoYesYesYesCCCCNot supported, not sent by HSSAs provisioned in the subscriber profileAs provisioned in the subscriber profileAs provisioned in the subscriber t-IdentifierServed-Party-IPAddressYesYesCCAs provisioned in the subscriber profileAs provisioned in the subscriber profileYesYesCCAs provisioned in the subscriber profileAs provisioned in the subscriber profileYesCAs provisioned in the subscriber profileYesCAs provisioned in the subscriber profileYesYesCCAs provisioned in the subscriber profileAll APN CONFIGURATIONS INCLUDED (0)MODIFIED/ADDED APN CONFIGURATIONS INCLUDED (1)YesYesYesCCCAs provisioned in the subscriber profileAs provisioned in the subscriber profileAs provisioned in the subscriber profileLTE S6a/S6d Interface Description910-6720-001 Revision A17
esCCNotesIPv4 (0)IPv6 (1)IPv4v6 (2)IPv4 OR IPv6 (3)Wildcard APN not supportedAs provisioned in the subscriber profileYesCAs provisioned in the subscriber profileYesCAs provisioned in the subscriber profileYesCAs provisioned in the subscriber profileYesCAs provisioned in the subscriber profileYesCAs provisioned in the subscriber profileYesCYesYesCCNOTALLOWED (0)ALLOWED (1)As provisioned in the subscriber profileAs provisioned in the subscriber profileYesCAs provisioned in the subscriber profileYesCAs provisioned in the subscriber profileYesCYesCSTATIC (0)DYNAMIC (1)As provisioned in the subscriber profileYesYesCCAs provisioned in the subscriber profileAs provisioned in the subscriber profileYesCAs provisioned in the subscriber profileYesYesCCAs provisioned in the subscriber profileAs provisioned in the subscriber profileNoYesYesCCCYesYesYesYesYesYesCCCCCCNot supported, not sent by HSSAs provisioned in the subscriber profileAll PDP CONTEXTS INCLUDED (0)MODIFIED/ADDED PDP CONTEXTS INCLUDED (1)As provisioned in the subscriber profileAs provisioned in the subscriber profileAs per 29.002As provisioned in the subscriber profileAs per 29.002As provisioned in the subscriber profileYesCWildcard APN not supportedLTE S6a/S6d Interface DescriptionCatC910-6720-001 Revision A18
otesAs provisioned in the subscriber profileAs provisioned in the subscriber profileAs provisioned in the subscriber profileAs provisioned in the subscriber re (0)3.2 Cancel Location ProcedureThe Cancel Location Procedure shall be used between the HSS and the MME and between the HSS andthe SGSN to delete a subscriber record from the MME or SGSN. The procedure shall be invoked by theHSS and is used: to inform the MME or SGSN about the subscriber’s subscription withdrawal orto inform the MME or SGSN about an ongoing update procedure i.e. MME or SGSN change.to inform the MME or SGSN about an initial attach procedure.This procedure uses the commands Cancel-Location-Request/Answer (CLR/CLA) in the Diameterapplication.3.2.1 HSS Behavior 3.2.1.1 The HSS will make use of this procedure when the subscriber’s subscription is withdrawn by theHSS operator and when the HSS detects that the UE has moved to a new MME or SGSN area.The HSS will include a cancellation type of "Subscription Withdrawal" if the subscriber’ssubscription is withdrawn by the operator and will include a cancellation type of "MME UpdateProcedure" if the UE moved to a new MME area and will include a cancellation type of "SGSNUpdate Procedure" if the UE moved to a new SGSN area, and will include a cancellation type of"Initial Attach Procedure" if the cancel location is initiated due to an Initial Attach from the UE.Not supported in current releaseOperator-triggered Cancel Location is not supported (only Mobility-related Cancel LocationRequests). CLR is triggered upon Subscription deletion.LTE S6a/S6d Interface Description910-6720-001 Revision A19
3.2.2 CLR messageThe table below provides the supported CLR cellation-TypeYesCatMMMMMMMOOOOMNotesSpecified by HSSNO STATE MAINTAINEDSpecified by HSSSpecified by HSSMME hostMME realmThe active IMSI registered with this MME/SGSN
The Subscriber Data Management (SDM) is an Evolved Subscriber Data Management (eSDM) platform, built with the objective to manage any number and type of profiles of a given subscriber. The high-level architecture of the SDM is divided in 4 parts: The SDS, a distributed back-end subscriber database
