1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelLocatDiameter-based SL(3GPP TS 29.1TECHNICAL SPECIFICATION129 173 V13.0.0 (2016communications system (Phaelecommunications System (LTE; cation Services (LCS); SLh interface for Control Plan.173 version 13.0.0 Release 1316-01) hase 2+); (UMTS); ane
2、 LCS 13) ETSI ETSI TS 129 173 V13.0.0 (2016-01)13GPP TS 29.173 version 13.0.0 Release 13Reference RTS/TSGC-0429173vd00 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Associ
3、ation but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print
4、 versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on
5、a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find
6、errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm
7、except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserv
8、ed. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by t
9、he GSM Association. ETSI ETSI TS 129 173 V13.0.0 (2016-01)23GPP TS 29.173 version 13.0.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly avai
10、lable for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web serv
11、er (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may becom
12、e, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be
13、interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “ne
14、ed not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 129 173 V13.0.0 (2
15、016-01)33GPP TS 29.173 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 General Description 7g34.1 Introduction
16、 7g34.2 Architecture Overview . 7g34.3 Functional Requirements of SLh Interface . 8g35 Diameter-based SLh Interface 8g35.1 Introduction 8g35.2 Procedure Descriptions . 8g35.2.1 Send Routing Information for LCS . 8g35.2.1.1 General 8g35.2.1.2 Detailed Behaviour of the HSS . 10g35.2.1.3 Detailed Behav
17、iour of the GLMC . 10g36 Protocol Specification and Implementations 11g36.1 Introduction 11g36.1.1 Use of Diameter Base Protocol . 11g36.1.2 Securing Diameter Messages 11g36.1.3 Accounting Functionality . 11g36.1.4 Use of Sessions . 11g36.1.5 Transport Protocol 11g36.1.6 Routing Considerations . 11g
18、36.1.7 Advertising Application Support 11g36.1.8 Diameter Application Identifier 12g36.1.9 User Identity to HSS resolution 12g36.2 Commands 12g36.2.1 Introduction. 12g36.2.2 Command-Code values . 12g36.2.3 LCS-Routing-Info-Request (RIR) Command . 13g36.2.4 LCS-Routing-Info-Answer (RIA) Command . 13g
19、36.3 Result-Code AVP and Experimental-Result AVP Values . 14g36.3.1 General 14g36.3.2 Success 14g36.3.3 Permanent Failures . 14g36.3.3.1 DIAMETER_ERROR_USER_UNKNOWN (5001) 14g36.3.3.2 DIAMETER_ERROR_UNAUTHORIZED_REQUESTING_NETWORK (5490) . 14g36.3.4 Transient Failures . 15g36.3.4.1 DIAMETER_ERROR_AB
20、SENT_USER (4201) 15g36.4 AVPs 15g36.4.1 General 15g36.4.2 LMSI. 16g36.4.3 Serving-Node 16g36.4.4 MME-Name 16g36.4.5 MSC-Number . 16g36.4.6 LCS-Capabilities-Sets . 17g3ETSI ETSI TS 129 173 V13.0.0 (2016-01)43GPP TS 29.173 version 13.0.0 Release 136.4.7 GMLC-Address 17g36.4.8 Additional-Serving-Node 1
21、7g36.4.9 PPR-Address . 17g36.4.10 Feature-List-ID AVP 17g36.4.11 Feature-List AVP 17g36.4.12 MME-Realm . 18g36.4.13 SGSN-Name . 18g36.4.14 SGSN-Realm 18g3Annex A (informative): Change history . 19g3History 20g3ETSI ETSI TS 129 173 V13.0.0 (2016-01)53GPP TS 29.173 version 13.0.0 Release 13Foreword Th
22、is Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-rel
23、eased by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit
24、 is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 173 V13.0.0 (2016-01)63GPP TS 29.173 version 13.0.0 Release 131 Scope The presen
25、t document describes the Diameter-based SLh interface between the GMLC and the HSS defined for the Control Plane LCS in EPC. LCS procedures over the SLh interface are defined in the 3GPP TS 23.271 2. This specification defines the Diameter application for the GMLC-HSS, SLh reference point. The inter
26、actions between the HSS and the GMLC are specified, including the signalling flows. As LCS procedures over the Diameter-based SLh interface are identical to the MAP-based Lh interface, the descriptions of the Lh MAP operations defined in the 3GPP TS 29.002 3 are mapped into the descriptions of the S
27、Lh Diameter commands. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a spec
28、ific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the presen
29、t document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 23.271: “Functional stage 2 description of Location Services (LCS)“. 3 3GPP TS 29.002: “Mobile Application Part (MAP) specification“. 4 3GPP TS 29.228: “IP multimedia (IM) Subsystem Cx Interface; Signalling flows and Messa
30、ge Elements“. 5 IETF RFC 3588: “Diameter Base Protocol“. 6 3GPP TS 33.210: “3G security; Network Domain Security (NDS); IP network layer security“. 7 IETF RFC 4960: “Stream Control Transport Protocol“. 8 3GPP TS 29.229: “Cx and Dx Interfaces based on the Diameter protocol; protocol details“. 9 3GPP
31、TS 29.329: “Sh Interface based on the Diameter protocol; protocol details“. 10 3GPP TS 23.003: “Numbering, addressing and identification “. 11 3GPP TS 23.012: “Location Management Procedures“. 12 3GPP TS 29.272: “Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interface
32、s based on Diameter protocol“. 13 IETF RFC 2234: “Augmented BNF for syntax specifications“. 14 Void 15 ITU-T Recommendation E.164: “The international public telecommunication numbering plan“. 16 3GPP TS 29.273: “Evolved Packet System (EPS); 3GPP EPS AAA interfaces“. ETSI ETSI TS 129 173 V13.0.0 (201
33、6-01)73GPP TS 29.173 version 13.0.0 Release 133 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 1, 3GPP TS 23.271 2 and the following apply. A term defined in the present document takes precedence over
34、 the definition of the same term, if any, in TR 21.905 1. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if
35、 any, in 3GPP TR 21.905 1. ABNF Augmented Backus-Naur form AVP Attribute Value Pair H-GMLC Home-Gateway Mobile Location Centre IANA Internet Assigned Numbers Authority PMD Pseudonym mediation device functionality PPR Privacy Profile Register R-GMLC Requesting-Gateway Mobile Location Centre RFC Reque
36、st For Comments V-GMLC Visited-Gateway Mobile Location Centre 4 General Description 4.1 Introduction The SLh reference point between the GMLC and the HSS is defined in the 3GPP TS 23.271 2. This document describes the Diameter-based SLh interface related procedures, message parameters and protocol s
37、pecifications. 4.2 Architecture Overview The architecture for support of Location Services in GSM, UMTS and EPS has been defined in 3GPP TS 23.271 2 and the relevant network elements and interfaces are shown in the figure 4.2-1. ETSI ETSI TS 129 173 V13.0.0 (2016-01)83GPP TS 29.173 version 13.0.0 Re
38、lease 13ExternalLCS ClientMME SGSNMSC/MSC ServerPPR PMDGMLCHSSSLhSLgLgLg Lpp LidLeAAA ServerLaFigure 4.2-1: Overview of the LCS Functional Architecture In this architecture, the SLh interface is defined between the Gateway Mobile Location Center (GMLC) and the Home Subscriber Server (HSS) to allow t
39、he GMLC to request routing information from the HLR or HSS. 4.3 Functional Requirements of SLh Interface The requirements for SLh interface are defined in 3GPP TS 23.271 2. The SLh interface is used by the GMLC to request routing information from the HSS i.e. the address of the H-GMLC, and/or the ad
40、dress of the visited MSC/MSC server, SGSN, 3GPP AAA server or MME for a particular target UE whose location has been requested. 5 Diameter-based SLh Interface 5.1 Introduction This section describes the Diameter-based SLh interface related procedures and Information elements exchanged between functi
41、onal entities. In the tables that describe the Information Elements transported by each Diameter command, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional in the “Cat.“ column. For the correct handling of the Information Element according to the category type, see
42、 the description detailed in section 6 of the 3GPP TS 29.228 4. 5.2 Procedure Descriptions 5.2.1 Send Routing Information for LCS 5.2.1.1 General This procedure is used between the GMLC and the HSS. The procedure is invoked by the GMLC and is used: - To retrieve routing information for LCS for a spe
43、cified user from the HSS. ETSI ETSI TS 129 173 V13.0.0 (2016-01)93GPP TS 29.173 version 13.0.0 Release 13This procedure is mapped to the commands LCS-Routing-Info-Request/Answer in the Diameter application specified in chapter 6. Tables 5.2.1.1/1 and 5.2.1.1/2 detail the involved information element
44、s. Table 5.2.1.1/1: Send Routing Information for LCS (SLh-LCS-SRI) Information element name Mapping to Diameter AVP Cat. Description IMSI User-Name C This information element shall contain the IMSI of the targeted user. This IE shall be present if the MSISDN is absent. MSISDN MSISDN C This informati
45、on element shall contain the MSISDN of the targeted user. This IE shall be present if the IMSI is absent. GMLC Number GMLC-Number O This information element shall contain the ISDN (E.164) number of the requesting GMLC. Supported Features (See 3GPP TS 29.229 8) Supported-Features O If present, this i
46、nformation element shall contain the list of features supported by the origin host. Table 5.2.1.1/2: Send Routing Information for LCS (SLh-LCS-SRI) Resp Information element name Mapping to Diameter AVP Cat. Description Result (See 5.3.5) Result-Code / Experimental-Result M Result of the request. Res
47、ult-Code AVP shall be used for errors defined in the Diameter Base Protocol. Experimental-Result AVP shall be used for SLh errors. This is a grouped AVP which contains the 3GPP Vendor ID in the Vendor-Id AVP, and the error code in the Experimental-Result-Code AVP. IMSI User-Name C This information e
48、lement shall contain the IMSI of the targeted user. This IE shall be present if Result-Code is DIAMETER_SUCCESS and the MSISDN is absent. MSISDN MSISDN C This information element shall contain the MSISDN of the targeted user. This IE shall be present if Result-Code is DIAMETER_SUCCESS and the IMSI i
49、s absent. LMSI LMSI C This information element shall contain the LMSI allocated by the VLR. This IE should be present if Result-Code is DIAMETER_SUCCESS and LMSI is available in the HSS and MSC-Number is included in the Serving-Node AVP or in an Additional-Serving-Node AVP. Serving Node Serving-Node C This information element shall contain the information about the network node serving the targeted user i.e. the name/number of the serving node (MME, SGSN, 3GPP AAA server or MSC/MSC server), the LCS capabilities sets supp
