ETSI TS 148 031-2016 Digital cellular telecommunications system (Phase 2+) Location Services (LCS) Serving Mobile Location Centre - Serving Mobile Location Centre (SMLC - SMLC) SML.pdf

1、 ETSI TS 1Digital cellular telecoLocatServing MServing Mobile LSML(3GPP TS 48.0TECHNICAL SPECIFICATION148 031 V13.0.0 (2016communications system (Phacation Services (LCS); Mobile Location Centre - Location Centre (SMLC - SMLMLCPP specification .031 version 13.0.0 Release 13GLOBAL SYSTEMOBILE COMMUN1

2、6-01) hase 2+); MLC); ) TEM FOR ICATIONSRETSI ETSI TS 148 031 V13.0.0 (2016-01)13GPP TS 48.031 version 13.0.0 Release 13Reference RTS/TSGG-0248031vd00 Keywords GSM 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 0

3、0017 - 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 may be made available in electronic versions and/or in print. The content of any

4、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 in print, the only prevailing document is the print of the Portable Document Format

5、 (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 of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/

6、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 or utilized in any form or by any means, electronic or mechanical, including phot

7、ocopying 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 extend to reproduction in all media. European Telecommunications Standards Institute

8、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 Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks re

9、gistered and owned by the GSM Association. ETSI ETSI TS 148 031 V13.0.0 (2016-01)23GPP TS 48.031 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, i

10、f 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 standards“, which is available from the ETSI Secretariat. Latest updates are availab

11、le 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 referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are,

12、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 specifications or reports using their 3GPP identities, UMTS identities or GSM ident

13、ities. 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. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “

14、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“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETS

15、I TS 148 031 V13.0.0 (2016-01)33GPP TS 48.031 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Abbreviations . 7g34 Procedures 7g34.1 RIT Procedures . 7g34.1.1 RIT Query Operation 8g34.1.2 RIT Indica

16、tion Operation 8g34.1.3 RIT Query Stop Operation 9g34.2 (void) 10g34.3 Deciphering Keys Procedure 10g34.3.1 Deciphering Keys Update Operation 10g35 Error Handling 10g35.1 Missing Message Part . 10g35.2 Repeated Message Part . 10g35.3 Unforeseen Message Part . 11g35.4 Incorrect Data . 11g35.5 Repeate

17、d Operation 11g35.6 Unforeseen Operation . 11g35.7 Unknown Request ID . 11g35.8 Dublicate Request ID . 11g35.9 No RIT Information 12g35.10 (void) 12g35.11 Deciphering Keys Error 12g35.12 Internal Error 12g35.13 Other Error Situations 12g35.14 Summary of Indications . 12g36 Signalling Elements 13g36.

18、1 Messages 13g36.1.1 Operation Code . 14g36.1.2 Request ID 16g36.1.3 Argument 16g36.1.4 Result 16g36.1.5 Error Indication . 16g36.2 ASN.1 Definition of Arguments, Results, and IEs . 17g3Annex A (normative): Operation and Error Definition . 21g3Annex B (informative): Description of Arguments, Results

19、 and Information elements 22g3B.1 Description of elements 22g3B.1.1 Arguments and Results . 22g3B.1.1.1 RIT Query Operation 22g3B.1.1.1.1 Argument . 22g3B.1.1.1.2 Result. 22g3B.1.1.2 RIT Indication . 22g3B.1.1.2.1 Argument. 22g3B.1.1.2.2 Result . 23g3B.1.1.3 RIT Query Stop . 23g3B.1.1.3.1 Argument .

20、 23g3ETSI ETSI TS 148 031 V13.0.0 (2016-01)43GPP TS 48.031 version 13.0.0 Release 13B.1.1.3.2 Result . 23g3B.1.1.4 (void) . 23g3B.1.1.5 Send Deciphering Keys . 23g3B.1.1.5.1 Request 23g3B.1.1.5.2 Result. 23g3B.1.2 Information elements 23g3B.1.2.1 Request Type IE 23g3B.1.2.2 Cell List IE 24g3B.1.2.3

21、Reference Clock IE . 25g3B.1.2.4 RIT Data IE . 27g3B.1.2.5 (void) . 29g3B.1.2.6 (void) . 29g3B.1.2.7 (void) . 29g3B.1.2.8 (void) . 29g3B.1.2.9 (void) . 29g3B.1.2.10 (void) . 29g3B.1.2.11 (void) . 29g3B.1.2.12 (void) . 29g3B.1.2.13 (void) . 29g3B.1.2.14 (void) . 29g3B.1.2.15 (void) . 29g3B.1.2.16 Dec

22、iphering Key Type IE . 29g3B.1.2.17 Deciphering Keys IE . 29g3B.1.2.18 Location Area IE . 29g3B.1.2.19 (void) . 29g3Annex C (informative): Change History 30g3History 31g3ETSI ETSI TS 148 031 V13.0.0 (2016-01)53GPP TS 48.031 version 13.0.0 Release 13Foreword This Technical Specification has been prod

23、uced 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 identifying cha

24、nge 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 of subst

25、ance, 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 148 031 V13.0.0 (2016-01)63GPP TS 48.031 version 13.0.0 Release 131 Scope The present document contains the definition of th

26、e SMLCPP protocol to be used between two Serving Mobile Location Centres (SMLC). The LCS architecture is described in 3GPP TS 43.059. The following aspects of it are relevant to the issue: - each SMLC controls a number of LMUs, and a given LMU is under the direct control of a single SMLC; - there is

27、 a direct communication path, independent of SMLCPP, between a LMU and the SMLC that controls it; - deciphering keys are controlled by one SMLC in the location area and sent to other SMLCs in the same location area. SMLCPP runs between two SMLC functions in the same PLMN. Transport is outside the sc

28、ope of the present document. It assumes a transport service between these functions, as provided by BSSAP-LE. The present document assumes that the underlying transport (e.g., as described by BSSAP-LE specifications) provides for transport and routing for any two pairs of SMLCs which need to run SML

29、CPP exchanges. The main functions of SMLCPP are described in 5. The key aspects are: a) allowing an SMLC to ask for and obtain information about Radio Interface Timing (RIT), as known from measurements done by LMUs not under its direct control; c) allowing an SMLC, that controls deciphering keys in

30、the location area, to sent them to other SMLCs in the same location area. 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, v

31、ersion number, etc.) or non-specific. For a specific 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 t

32、hat document in the same Release as the present document. 1 3GPP TS 21.905: “Vocabulary for 3GPP Specifications“. 2 (void) 3 3GPP TS 24.007: “Mobile radio interface signalling layer 3; General aspects“. 4 3GPP TS 24.008: “Mobile radio interface layer 3 specification“. 5 3GPP TS 43.059: “Functional S

33、tage 2 Description of Location Services in GERAN (Release 4)“. 6 3GPP TS 29.002: “Mobile Application Part (MAP) specification“. 7 ASN.1 encoding rules Specification of Packet Encoding Rules (PER) ITU-T Rec. X.691 (1997) | ISO/IEC 8825-2:1998. 8 (void) 9 Abstract Syntax Notation One (ASN.1) Specifica

34、tion of Basic Notation ITU-T Rec.X.680 (1997) | ISO/IEC 8824 1:1998. 10 (void) ETSI ETSI TS 148 031 V13.0.0 (2016-01)73GPP TS 48.031 version 13.0.0 Release 1311 3GPP TS 44.071: “Mobile radio interface layer 3 Location Services (LCS) specification“. 12 3GPP TS 49.031: “Location Services (LCS); Base S

35、tation System Application Part LCS Extension (BSSAP-LE)“. 3 Abbreviations Abbreviations used in the present document are listed in 3GPP TS 21.905 or in 3GPP TS 43.059. 4 Procedures 4.1 RIT Procedures Two modes of operation are supported: - provision of RIT information on request. In this mode a SMLC

36、 Client needing RIT information requests it from another SMLC using the RIT Query operation. The SMLC Server sends the requested RIT information using the RIT Indication operation. There are two cases: - single indication: RIT Indication is requested only once. SMLCServerSMLCClientRIT IndicationRIT

37、QueryIn this case the procedure consists of one RIT Query and one RIT Indication operations. - Open-ended repetitive RIT Indications: RIT information is requested on a regular basis until the RIT Query Stop operation. SMLCServerSMLCClientRIT Indication. . .RIT IndicationRIT QueryRIT Query StopIn thi

38、s case the procedure consists of one RIT Query, one or more RIT Indication, and one RIT Query Stop operations. - Autonomous provision of RIT information. In this mode, the RIT information is provided automatically by the SMLC Server, according to an internal configuration not managed through SMLCPP

39、(e.g., by O RIT Indication is requested only once; - open-ended repetitive indications; RIT Indication operations are requested on a regular basis until the RIT Query Stop operation. A RIT Query Response includes the same Request ID that the Request included, and it is used as a positive acknowledge

40、ment. A RIT Query Error message can be sent in return, if the SMLC Server detects an error situation (e.g. syntax errors, or overlapping Request ID values), or it can not fullfil the Request (e.g. RIT information is requested for unknown BTSs ). It contains the same Request ID values as the Request.

41、 4.1.2 RIT Indication Operation SMLCSMLCRIT Indication Request(Request ID, )RIT Indication Error(Request ID, )RIT Indication Response(Request ID)This operation allows a SMLC to send RIT information to another SMLC. It can be used both in the cased of autonomous provision, and the provision of RIT in

42、formation on request. The RIT Indication Request contains RIT information to be delivered. It also contains the Request ID that: ETSI ETSI TS 148 031 V13.0.0 (2016-01)93GPP TS 48.031 version 13.0.0 Release 13- has the same value as the RIT Query operation, that invoked the RIT Indication (RIT provis

43、ion on request); - has a reserved value indicating autonomous provision. A RIT Indication Response includes the same Request ID that the Request included, and it is used as a positive acknowledgement. The SMLC Client can send a RIT Indication Error to the SMLC Server, if it detects an error situatio

44、n (e.g. syntax errors, or unknown Request ID values). 4.1.3 RIT Query Stop Operation SMLCSMLCRIT Query Stop Request(Request ID)RIT Query Stop Error(Request ID, )RIT Query Stop Response(Request ID)This operation allows a SMLC to send an indication to another SMLCPP to stop sending RIT information, th

45、at it has originally asked to obtain on open-ended repetitive basis. The RIT Query Stop Request includes the Request ID values that is the same as in the corresponding RIT Query that should be stopped. A RIT Query Stop Response includes the same Request ID that the Request included, and it is used a

46、s a positive acknowledgement. The SMLC Server can send a RIT Query Stop Error to the SMLC Client, if it detects an error situation (e.g. syntax errors, or unknown Request ID values). ETSI ETSI TS 148 031 V13.0.0 (2016-01)103GPP TS 48.031 version 13.0.0 Release 134.2 (void) 4.3 Deciphering Keys Proce

47、dure This procedure includes one operation that is related to LCS assistance data broadcast deciphering keys. With this operation the SMLC Server controlling the deciphering keys (needed in LCS Assistance Data broadcast) can send the deciphering keys to other SMLC Clients in the same location area.

48、One SMLC (i.e. SMLC Server) in location area is selected to control the deciphering keys and sending the keys to other SMLC Clients in location area. The sending has to be done to each SMLC Client with a separate message. SMLCClientSMLCServerDeciphering Keys Update4.3.1 Deciphering Keys Update Opera

49、tion SMLCSMLCDeciphering Keys Update Request(Request ID, )Deciphering Keys Update Response(Request ID)Deciphering Keys Update Error(Request ID, )This operation allows a SMLC controlling deciphering keys to send the keys to another SMLC Client. The Deciphering Keys Update Request includes the Request ID and information of keys. A Deciphering Keys Update Response includes only the same Request ID that the Request included, and it is used as a positive acknowledgement. The SMLC Client can send a Deciphering Keys Update Error to the SMLC