1、 ETSI TS 1Digital cellular telecommUniversal Mobile TelLocatLCS Applicbetween the Moand Evolved Serving(3GPP TS 29.1TECHNICAL SPECIFICATION129 171 V13.2.0 (2016mmunications system (Phase elecommunications System (LTE; cation Services (LCS); lication Protocol (LCS-AP) obile Management Entity (MMing M
2、obile Location Centre (ESLs interface .171 version 13.2.0 Release 1316-04) e 2+) (GSM); (UMTS); ME) (E-SMLC); 13) ETSI ETSI TS 129 171 V13.2.0 (2016-04)13GPP TS 29.171 version 13.2.0 Release 13Reference RTS/TSGC-0429171vd20 Keywords GSM,LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis C
3、edex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association 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
4、 may be made available in electronic versions and/or in print. The content of any electronic and/or print 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 i
5、n print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on 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
6、 of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.asp If you find 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
7、 or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm 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 ext
8、end to reproduction in all media. European Telecommunications Standards Institute 2016. All rights reserved. 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 Member
9、s and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 171 V13.2.0 (2016-04)23GPP TS 29.171 version 13.2.0 Release 13Intellectual Property Rights IPRs essential or potentially essential to the present document may
10、 have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available 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 st
11、andards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (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
12、 referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, 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 s
13、pecifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be 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.
14、 Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need 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“
15、are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 129 171 V13.2.0 (2016-04)33GPP TS 29.171 version 13.2.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions and abbrev
16、iations . 7g33.1 Definitions 7g33.2 Abbreviations . 7g34 Functional Overview 7g34.1 General . 7g35 LCS-AP Message Transport . 8g35.1 General . 8g35.2 Protocol Layering . 8g35.3 Usage of SCTP Associations 9g36 LCS-AP Procedures . 9g36.1 General . 9g36.2 Procedures Applicable to LCS-AP . 9g36.2.1 Loca
17、tion Service Request . 9g36.2.1.1 General 9g36.2.1.2 Successful Operation . 9g36.2.1.3 Unsuccessful Operation 11g36.2.2 Location Information Exchange . 11g36.2.2.1 Connection Oriented Information Transfer . 11g36.2.2.1.1 General 11g36.2.2.1.2 Successful Operation . 12g36.2.2.1.3 Abnormal Conditions
18、12g36.2.2.2 Connectionless Information Transfer 12g36.2.2.2.1 General 12g36.2.2.2.2 Successful Operation . 13g36.2.2.2.3 Unsuccessful Operation . 13g36.2.2.2.4 Abnormal Conditions 13g36.3 Exception Procedures . 14g36.3.1 Location Abort 14g36.3.1.1 General 14g36.3.1.2 Normal Operation . 14g36.3.1.3 A
19、bnormal Conditions 14g36.3.2 Reset . 14g36.3.2.1 General 14g36.3.2.2 Normal Operation . 15g36.3.2.3 Abnormal Conditions 15g36.4 Error Handling 15g36.4.1 Abnormal Conditions 15g36.4.2 Overload . 15g37 LCS-AP Messages and Message Formats 16g37.1 General . 16g37.2 Message Formats 16g37.3 LCS-AP Message
20、s 16g37.3.1 LCS-AP Location Request message . 17g37.3.2 LCS-AP Location Response message . 17g37.3.3 LCS-AP Location Abort Request message . 18g3ETSI ETSI TS 129 171 V13.2.0 (2016-04)43GPP TS 29.171 version 13.2.0 Release 137.3.4 LCS-AP Connection Oriented Information message 18g37.3.5 LCS-AP Connec
21、tionless Information message . 18g37.3.6 LCS-AP Reset Request message 19g37.3.7 LCS-AP Reset Acknowledge message . 19g37.4 Information Elements . 19g37.4.1 General 19g37.4.2 Message Type . 20g37.4.3 Location Type . 20g37.4.4 E-CGI 20g37.4.5 LCS Client Type . 21g37.4.6 LCS Priority 21g37.4.7 LCS QoS
22、. 21g37.4.8 UE Positioning Capability 22g37.4.9 Include Velocity 22g37.4.10 IMSI 22g37.4.11 IMEI 23g37.4.12 Geographic Area . 24g37.4.13 Positioning Data 25g37.4.14 Velocity Estimate 29g37.4.15 Accuracy Fulfilment Indicator 29g37.4.16 LCS Cause 30g37.4.17 Payload Type 31g37.4.18 APDU . 31g37.4.19 Ne
23、twork Element 31g37.4.20 Return Error Request 31g37.4.21 Return Error Cause . 31g37.4.22 Altitude and direction . 32g37.4.23 Geographical Coordinates . 32g37.4.24 Uncertainty Ellipse . 33g37.4.25 Horizontal Speed and Bearing 33g37.4.26 Vertical Velocity . 33g37.4.27 PLMN Identity 34g37.4.28 Correlat
24、ion ID . 34g37.4.29 eNB ID 35g37.4.30 LCS Service Type ID 35g37.4.31 Cell Portion ID 35g37.4.32 Civic Address 35g37.4.33 Barometric Pressure 36g37.5 Message and information element abstract syntax . 36g37.5.1 General 36g37.5.2 Usage of protocol extension mechanism for non-standard use . 36g37.5.3 El
25、ementary procedure definitions . 36g37.5.4 PDU definitions 39g37.5.5 Information element definitions 43g37.5.6 Common definitions . 50g37.5.7 Constant definitions 50g37.5.8 Container Definitions 51g37.5.9 Message transfer syntax . 53g37.6 Handling of unknown, unforeseen and erroneous protocol data 5
26、3g38 LCS-AP Timers 53g38.1 General . 53g38.2 Timers of LCS-AP 53g3Annex A (informative): Change history 54g3History 55g3ETSI ETSI TS 129 171 V13.2.0 (2016-04)53GPP TS 29.171 version 13.2.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GP
27、P). 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-released by the TSG with an identifying change of release date and an increase in version num
28、ber 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 is incremented for all changes of substance, i.e. technical enhancements, corrections, up
29、dates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 129 171 V13.2.0 (2016-04)63GPP TS 29.171 version 13.2.0 Release 131 Scope The present document specifies the procedures and information coding for LCS Application Protocol (L
30、CS-AP) that is needed to support the location services in E-UTRAN. The LCS-AP message set is applicable to the SLs interface between the E-SMLC and the MME. LCS-AP is developed in accordance to the general principles stated in 3GPP TS 23.271 3. 2 References The following documents contain provisions
31、 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 specific reference, subsequent revisions do not apply. - For a non-specific refer
32、ence, 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 present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS
33、 36.305: “Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN“. 3 3GPP TS 23.271: “Functional stage 2 description of Location Services (LCS)“. 4 IETF RFC 4960: “Stream Control Transmission Protocol“. 5 TIA/EIA/IS-J-STD-036 (2000): “Wireless Enhanced Emergency Services“. 6
34、3GPP TS 23.032: “Universal Geographical Area Description (GAD)“. 7 3GPP TS 36.413: “S1 Application Protocol (S1AP)“. 8 ITU-T Recommendation X.680 (07/2002): “Information Technology - Abstract Syntax Notation One (ASN.1): Specification of basic notation“. 9 ITU-T Recommendation X.681 (07/2002): “Info
35、rmation Technology - Abstract Syntax Notation One (ASN.1): Information object specification“. 10 3GPP TS 22.071: “Location Services (LCS); Service Description; Stage1“. 11 3GPP TS 23.003: “Numbering, addressing and identification“. 12 ITU-T Recommendation X.691 (07/2002): “Information Technology - A
36、SN.1 encoding rules - Specification of Packed Encoding Rules (PER)“. 13 IETF RFC 4119: “A Presence-based GEOPRIV Location Object Format“. 14 IETF RFC 5139: “Revised Civic Location Format for Presence Information Data Format Location Object“. 15 IETF RFC 6848: “Specifying Civic Address Extensions in
37、the Presence Information Data Format Location Object (PIDF-LO)“. ETSI ETSI TS 129 171 V13.2.0 (2016-04)73GPP TS 29.171 version 13.2.0 Release 133 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following a
38、pply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. Elementary Procedure: LCS-AP protocol consists of Elementary Procedures (EPs). An LCS-AP Elementary Procedure is a unit of interaction between the MME and the E-SMLC. An EP con
39、sists of an initiating message and possibly a response message. Two kinds of EPs are used: - Class 1: Elementary Procedures with response (success or failure), - Class 2: Elementary Procedures without response. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR
40、 21.905 1 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. CID Cell-ID (positioning method) E-CID Enhanced Cell-ID (positioning method) E-SMLC Enhanced Serving Mobile Location Centre E-UTRA
41、N Envolved Universal Terrestrial Radio Access Network GNSS Global Navigation Satellite System GPS Global Positioning System LCS LoCation ServicesLCS-AP LCS Application Protocol LPP LTE Positioning Protocol LPPa LTE Positioning Protocol Annex LTE Long Term Evolution MBS Metropolitan Beacon System MO-
42、LR Mobile Originated Location Request MT-LR Mobile Terminated Location RequestNI-LR Network Induced Location Request MME Mobility Management Entity OTDOA Observed Time Difference Of Arrival PDU Protocol Data Unit SCTP Stream Control Transmission Protocol SET SUPL Enabled Terminal SLP SUPL Location P
43、latformSUPL Secure User Plane Location TA Timing Advanced UE User EquipmentU-TDOA Uplink Time Difference Of Arrival 4 Functional Overview 4.1 General Figure 4.1-1 below shows the architecture applicable to the positioning of a UE with E-UTRAN access. The SLs interface is used to convey LCS-AP messag
44、es and parameters between the MME to the E-SMLC. It is also used for tunnelling LTE Positioning Protocols (LPP between the E-SMLC and the target UE, LPPa between the E-SMLC and the eNB), which are transparent to the MME as described in 3GPP TS 36.305 2. ETSI ETSI TS 129 171 V13.2.0 (2016-04)83GPP TS
45、 29.171 version 13.2.0 Release 13UE Serving eNB S1 Neighbor eNB S1 MME E-SMLC SLs LTE-Uu Figure 4.1-1 Positioning Interfaces in E-UTRAN 5 LCS-AP Message Transport 5.1 General The LCS-AP is a logical interface between the MME and the E-SMLC. This section specifies the standards for signaling transpor
46、t to be used across LCS-AP. 5.2 Protocol Layering Figure 5.2-1 below shows the protocol layering used to support the transfer of LCS-AP PDUs between an E-SMLC and a MME. The LTE Positioning Protocols (LPP and LPPa) can be carried in LCS-AP messages which are transparent to the MME. L1 L2 IP SCTP S1-
47、AP L1 L2 IP SCTP LCS-AP L1 L2 IP LCS-AP LPP/ LPPa MME SLs SCTP E-SMLC NAS Relay Figure 5.2-1 Protocol Layering for LCS-AP ETSI ETSI TS 129 171 V13.2.0 (2016-04)93GPP TS 29.171 version 13.2.0 Release 135.3 Usage of SCTP Associations SCTP (see IETF RFC 4960 4) shall be supported as the transport layer
48、 of LCS-AP messages. Semi-permanent SCTP associations shall be established between MME and E-SMLC, i.e. the SCTP associations shall remain up under normal circumstances. Local multi-homing should be supported. Remote multi-homing shall be supported. Multiple local SCTP endpoints may be supported. Mu
49、ltiple remote SCTP endpoints shall be supported. When multiple local or remote SCTP endpoints are configured, several simultaneous SCTP associations shall be supported between MME and E-SMLC. The MME shall establish the SCTP association. Since under normal operation there should always be an SCTP association established between an MME and an E-SMLC, if the E-SMLC needs to initiate a message towards an MME it shall do so over an existing SCTP association already established with that MME. When an entity detects that an SCTP associat
