ETSI TS 136 459-2017 LTE Evolved Universal Terrestrial Radio Access Network (E-UTRAN) SLm interface Application Protocol (SLmAP) (V14 0 0 3GPP TS 36 459 version 14 0 0 Release 14)《.pdf

1、 ETSI TS 136 459 V14.0.0 (2017-04) LTE; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); SLm interface Application Protocol (SLmAP) (3GPP TS 36.459 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 136 459 V14.0.0 (2017-04)13GPP TS 36.459 version 14.0.0 Release 14Reference

2、 RTS/TSGR-0336459ve00 Keywords LTE 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 Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present

3、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 versions of the present document shall not be modified without the prior written authorization of ETSI. I

4、n 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 a specific network drive within ETSI Secretariat. Users of the present document should be aware that the d

5、ocument may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, please send your comment to one of the following services: https

6、:/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 except as authorized by written permission of ETSI. The content of the PDF version shall not be

7、modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the bene

8、fit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 136 459

9、 V14.0.0 (2017-04)23GPP TS 36.459 version 14.0.0 Release 14Intellectual 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 available for ETSI members and non-members,

10、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 server (https:/ipr.etsi.org/). Pursuant to t

11、he 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 become, essential to the present document. Fo

12、reword 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 interpreted as being references to the c

13、orresponding 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“, “need not“, “will“, “will not“, “can“ and “

14、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 136 459 V14.0.0 (2017-04)33GPP TS 36.459 version 14.0.0 Re

15、lease 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Definitions, symbols and abbreviations . 6g33.1 Definitions 6g33.2 Symbols 7g33.3 Abbreviations . 7g34 General . 7g34.1 Procedure Specification Principles . 7g34.2 For

16、wards and Backwards Compatibility 8g34.3 Specification Notations 8g35 SLmAP Services 8g36 Services Expected from Signalling Transport 8g37 Functions of SLmAP 9g38 SLmAP Procedures 9g38.1 List of SLmAP Elementary procedures 9g38.2 Measurement Procedures . 10g38.2.1 Measurement. 10g38.2.1.1 General 10

17、g38.2.1.2 Successful Operation . 10g38.2.1.3 Unsuccessful Operation 10g38.2.1.4 Abnormal Conditions 10g38.2.2 Measurement Update 11g38.2.2.1 General 11g38.2.2.2 Successful Operation . 11g38.2.2.3 Unsuccessful Operation 11g38.2.2.4 Abnormal Conditions 11g38.2.3 Measurement Abort 11g38.2.3.1 General 1

18、1g38.2.3.2 Successful Operation . 12g38.2.3.3 Unsuccessful Operation 12g38.2.3.4 Abnormal Conditions 12g38.3 Management procedures . 12g38.3.1 SLm Setup 12g38.3.1.1 General 12g38.3.1.2 Successful Operation . 12g38.3.1.3 Unsuccessful Operation 13g38.3.1.4 Abnormal Conditions 13g38.3.2 Reset . 13g38.3

19、.2.1 General 13g38.3.2.2 Successful Operation . 13g38.3.2.2.1 Reset Procedure Initiated from the E-SMLC . 13g38.3.2.2.2 Reset Procedure Initiated from the LMU 14g38.3.2.4 Abnormal Conditions 14g38.3.3 Error Indication . 14g38.3.3.1 General 14g38.3.3.2 Successful Operation . 15g39 Elements for SLmAP

20、Communication . 15g3ETSI ETSI TS 136 459 V14.0.0 (2017-04)43GPP TS 36.459 version 14.0.0 Release 149.1 Message Functional Definition and Content 15g39.1.1 MEASUREMENT REQUEST . 15g39.1.2 MEASUREMENT RESPONSE . 15g39.1.3 MEASUREMENT FAILURE 15g39.1.4 SLm SETUP REQUEST 16g39.1.5 SLm SETUP RESPONSE 16g

21、39.1.6 SLm SETUP FAILURE 16g39.1.7 RESET REQUEST . 16g39.1.8 RESET ACKNOWLEDGE 17g39.1.9 MEASUREMENT ABORT . 17g39.1.10 MEASUREMENT UPDATE . 17g39.1.11 ERROR INDICATION . 17g39.2 Information Element Definitions 18g39.2.1 General 18g39.2.2 Message Type . 18g39.2.3 SLmAP Transaction ID 18g39.2.4 UL RT

22、OA Measurement Configuration . 18g39.2.5 UL RTOA Measurements . 20g39.2.6 LMU ID 20g39.2.7 E-SMLC ID 21g39.2.8 LMU Information . 21g39.2.9 LMU Position . 21g39.2.10 Cause 22g39.2.11 Criticality Diagnostics 23g39.2.12 E-SMLC Measurement ID 24g39.3 Message and Information Element Abstract Syntax (with

23、 ASN.1) 25g39.3.1 General 25g39.3.2 Usage of Private Message Mechanism for Non-standard Use 25g39.3.3 Elementary Procedure Definitions 25g39.3.4 PDU Definitions . 29g39.3.5 Information Element definitions . 34g39.3.6 Common definitions . 39g39.3.7 Constant definitions 40g39.3.8 Container definitions

24、. 42g39.4 Message Transfer Syntax . 45g39.5 Timers 45g310 Handling of Unknown, Unforeseen and Erroneous Protocol Data 46g3Annex A (informative): Change history . 47g3History 48g3ETSI ETSI TS 136 459 V14.0.0 (2017-04)53GPP TS 36.459 version 14.0.0 Release 14Foreword This Technical Specification has b

25、een 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-released by the TSG with an identif

26、ying 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 is incremented for all changes

27、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 136 459 V14.0.0 (2017-04)63GPP TS 36.459 version 14.0.0 Release 141 Scope The present document specifies the E-UTRA

28、N radio network layer signalling protocol for the SLm interface. The SLm Application Protocol (SLmAP) supports the functions of the SLm interface by signalling procedures defined in this document. SLmAP is developed in accordance to the general principles stated in TS 36.305 2 and TS 36.456 3. 2 Ref

29、erences 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 specific reference, subsequent

30、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 present document. 1 3GPP TR 21.90

31、5: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 36.305: “Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN“. 3 3GPP TS 36.456: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); SLm interface general aspects and principles“. 4 3GPP TS 36.455: “LTE Position

32、ing Protocol A (LPPa)“. 5 3GPP TS 36.101: “User Equipment (UE) radio transmission and reception“. 6 3GPP TS 23.032: “Universal Geographical Area Description (GAD)“. 7 3GPP TS 36.413: “ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol“. 8 ITU-T Recommendation X.69

33、1 (2002-07): “Information technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)“. 9 3GPP TS 36.111: “Location Measurement Unit (LMU) performance specification; User Equipment (UE) positioning in E-UTRAN“. 10 3GPP TS 36.104: “Evolved Universal Terrestrial Radio Access Netwo

34、rk (E-UTRAN); Base Station (BS) radio transmission and reception“. 11 3GPP TS 36.211: “Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Physical Channels and Modulation“. 3 Definitions, symbols and abbreviations 3.1 Definitions For the purposes of the present document, the terms and def

35、initions given in TR 21.905 1 and the following apply. 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: SLmAP consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between L

36、MUs in the E-UTRAN and E-SMLCs in the EPC. These Elementary Procedures are defined separately and are intended to be used to build up complete sequences in a flexible manner. If the independence ETSI ETSI TS 136 459 V14.0.0 (2017-04)73GPP TS 36.459 version 14.0.0 Release 14between some EPs is restri

37、cted, it is described under the relevant EP description. Unless otherwise stated by the restrictions, the EPs may be invoked independently of each other as standalone procedures, which can be active in parallel. The usage of several SLmAP EPs together or together with EPs from other interfaces is sp

38、ecified in stage 2 specifications (e.g., TS 23.305 2). An EP consists of an initiating message and possibly a response message. Two kinds of EPs are used: - Class 1: Elementary Procedures with response (success and/or failure). - Class 2: Elementary Procedures without response. For Class 1 EPs, the

39、types of responses can be as follows: Successful: - A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response. Unsuccessful: - A signalling message explicitly indicates that the EP failed. - On time supervision expiry (i.e., absen

40、ce of expected response). Successful and Unsuccessful: - One signalling message reports both successful and unsuccessful outcome for the different included requests. The response message used is the one defined for successful outcome. Class 2 EPs are considered always successful. 3.2 Symbols - 3.3 A

41、bbreviations For the purposes of the present document, the abbreviations given in 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 any, in TR 21.905 1. LMU Location Measurement Unit SLmAP SLm Interf

42、ace Application Protocol SRS Sounding Reference Signal TNL Transport Network LayerUL RTOA Uplink Relative Time of Arrival UTDOA Uplink Time Difference of Arrival 4 General 4.1 Procedure Specification Principles The principle for specifying the procedure logic is to specify the functional behaviour o

43、f the terminating node exactly and completely. Any rule that specifies the behaviour of the originating node shall be possible to be verified with information that is visible within the system. The following specification principles have been applied for the procedure text in clause 8: - The procedu

44、re text discriminates between: ETSI ETSI TS 136 459 V14.0.0 (2017-04)83GPP TS 36.459 version 14.0.0 Release 141) Functionality which “shall“ be executed The procedure text indicates that the receiving node “shall“ perform a certain function Y under a certain condition. If the receiving node supports

45、 procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value. 2) Functionality which “shall, if supported“ be executed

46、The procedure text indicates that the receiving node “shall, if supported,“ perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the

47、requesting node about the not supported functionality. - Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall

48、 not be included. For requirements on including Criticality Diagnostics IE, see clause 10. 4.2 Forwards and Backwards Compatibility The forwards and backwards compatibility of the protocol is assured by mechanism where all current and future messages, and IEs or groups of related IEs, include ID and

49、 criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version. 4.3 Specification Notations For the purposes of the present document, the following notations apply: Procedure When referring to an elementary procedure in the specification the Procedure Name is written with the first letters in each word in upper case characters followed by the word “procedure“, e.g., E-RAB procedure. Message When referring to a message in the specification t