ETSI TS 148 031 V13.0.0 (2016-01)

Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Serving Mobile Location Centre - Serving Mobile Location Centre (SMLC - SMLC); SMLCPP specification (3GPP TS 48.031 version 13.0.0 Release 13)

RTS/TSGG-0248031vd00

General Information

• Status: Published
• Publication Date: 24-Jan-2016
• Technical Committee: 3GPP GERAN 2 - Protocol aspects
• Current Stage: 12 - Completion
• Due Date: 20-Jan-2016
• Completion Date: 25-Jan-2016

Standards Content (Sample)

ETSI TS 1148 031 V13.0.0 (201616-01)






TECHNICAL SPECIFICATIONION
Digital cellular telecocommunications system (Phahase 2+);
Locatcation Services (LCS);
Serving M Mobile Location Centre -
Serving Mobile L Location Centre (SMLC - SMMLLC);
SMLMLCPP specification
(3GPP TS 48.0.031 version 13.0.0 Release 1313)

R
GLOBAL SYSTTEME FOR
MOBILE COMMUUNNICATIONS

---------------------- Page: 1 ----------------------
3GPP TS 48.031 version 13.0.0 Release 13 1 ETSI TS 148 031 V13.0.0 (2016-01)



Reference
RTS/TSGG-0248031vd00
Keywords
GSM
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture 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 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 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 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 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 reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP 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 the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3GPP TS 48.031 version 13.0.0 Release 13 2 ETSI TS 148 031 V13.0.0 (2016-01)
Intellectual 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, 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 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 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 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.
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" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 3 ----------------------
3GPP TS 48.031 version 13.0.0 Release 13 3 ETSI TS 148 031 V13.0.0 (2016-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 5
1 Scope . 6
2 References . 6
3 Abbreviations . 7
4 Procedures . 7
4.1 RIT Procedures . 7
4.1.1 RIT Query Operation . 8
4.1.2 RIT Indication Operation . 8
4.1.3 RIT Query Stop Operation . 9
4.2 (void) . 10
4.3 Deciphering Keys Procedure . 10
4.3.1 Deciphering Keys Update Operation . 10
5 Error Handling . 10
5.1 Missing Message Part . 10
5.2 Repeated Message Part . 10
5.3 Unforeseen Message Part . 11
5.4 Incorrect Data . 11
5.5 Repeated Operation . 11
5.6 Unforeseen Operation . 11
5.7 Unknown Request ID . 11
5.8 Dublicate Request ID . 11
5.9 No RIT Information. 12
5.10 (void) . 12
5.11 Deciphering Keys Error . 12
5.12 Internal Error . 12
5.13 Other Error Situations . 12
5.14 Summary of Indications . 12
6 Signalling Elements . 13
6.1 Messages . 13
6.1.1 Operation Code . 14
6.1.2 Request ID . 16
6.1.3 Argument . 16
6.1.4 Result . 16
6.1.5 Error Indication . 16
6.2 ASN.1 Definition of Arguments, Results, and IEs . 17
Annex A (normative): Operation and Error Definition . 21
Annex B (informative): Description of Arguments, Results and Information elements . 22
B.1 Description of elements . 22
B.1.1 Arguments and Results . 22
B.1.1.1 RIT Query Operation . 22
B.1.1.1.1 Argument . 22
B.1.1.1.2 Result . 22
B.1.1.2 RIT Indication . 22
B.1.1.2.1 Argument . 22
B.1.1.2.2 Result . 23
B.1.1.3 RIT Query Stop . 23
B.1.1.3.1 Argument . 23
ETSI

---------------------- Page: 4 ----------------------
3GPP TS 48.031 version 13.0.0 Release 13 4 ETSI TS 148 031 V13.0.0 (2016-01)
B.1.1.3.2 Result . 23
B.1.1.4 (void) . 23
B.1.1.5 Send Deciphering Keys . 23
B.1.1.5.1 Request . 23
B.1.1.5.2 Result . 23
B.1.2 Information elements . 23
B.1.2.1 Request Type IE . 23
B.1.2.2 Cell List IE . 24
B.1.2.3 Reference Clock IE . 25
B.1.2.4 RIT Data IE . 27
B.1.2.5 (void) . 29
B.1.2.6 (void) . 29
B.1.2.7 (void) . 29
B.1.2.8 (void) . 29
B.1.2.9 (void) . 29
B.1.2.10 (void) . 29
B.1.2.11 (void) . 29
B.1.2.12 (void) . 29
B.1.2.13 (void) . 29
B.1.2.14 (void) . 29
B.1.2.15 (void) . 29
B.1.2.16 Deciphering Key Type IE . 29
B.1.2.17 Deciphering Keys IE . 29
B.1.2.18 Location Area IE . 29
B.1.2.19 (void) . 29
Annex C (informative): Change History . 30
History . 31

ETSI

---------------------- Page: 5 ----------------------
3GPP TS 48.031 version 13.0.0 Release 13 5 ETSI TS 148 031 V13.0.0 (2016-01)
Foreword
rd
This Technical Specification has been produced by the 3 Generation 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 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 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

---------------------- Page: 6 ----------------------
3GPP TS 48.031 version 13.0.0 Release 13 6 ETSI TS 148 031 V13.0.0 (2016-01)
1 Scope
The present document contains the definition of the 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 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 scope 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 SMLCPP 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 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, version 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 that 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 Stage 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) 'Specification of Basic Notation' ITU-T Rec.X.680 (1997)
| ISO/IEC 8824 – 1:1998.
[10] (void)
ETSI

---------------------- Page: 7 ----------------------
3GPP TS 48.031 version 13.0.0 Release 13 7 ETSI TS 148 031 V13.0.0 (2016-01)
[11] 3GPP TS 44.071: "Mobile radio interface layer 3 Location Services (LCS) specification".
[12] 3GPP TS 49.031: "Location Services (LCS); Base Station 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 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.
SMLC SMLC
Client Server
RIT Query
RIT Indication

In 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.
SMLC SMLC
Client Server
RIT Query
RIT Indication
. . .
RIT Indication
RIT Query Stop

In this 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 (e.g., by O&M).
ETSI

---------------------- Page: 8 ----------------------
3GPP TS 48.031 version 13.0.0 Release 13 8 ETSI TS 148 031 V13.0.0 (2016-01)
SMLC SMLC
Client Server
RIT Indication
. . .
RIT Indication

In the autonomous mode the procedure consists of one or more RIT Indication operations.
Three RIT related operations are then included in the SMLCPP, one for requesting the provision of RIT data, the second
for provision, and the third one for stopping open-ended repetitive indications.
4.1.1 RIT Query Operation
SMLC SMLC
RIT Query Request(Request ID, …)
RIT Query Response(Request ID)
RIT Query Error(Request ID, …)

This operation allows a SMLC to query RIT information from another SMLC. This operation consists of sending of a
RIT Query Request. It includes the Request ID , that is used to identify different queries. The RIT Query Request also
includes the description of the scheduling of RIT Indication operations in the reverse direction. This includes the
following cases:
- single indication; 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
acknowledgement. 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.
4.1.2 RIT Indication Operation
SMLC SMLC
RIT Indication Request(Request ID, …)
RIT Indication Response(Request ID)
RIT Indication Error(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 information on request.
The RIT Indication Request contains RIT information to be delivered. It also contains the Request ID that:
ETSI

---------------------- Page: 9 ----------------------
3GPP TS 48.031 version 13.0.0 Release 13 9 ETSI TS 148 031 V13.0.0 (2016-01)
- has the same value as the RIT Query operation, that invoked the RIT Indication (RIT provision 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
situation (e.g. syntax errors, or unknown Request ID values).
4.1.3 RIT Query Stop Operation
SMLC SMLC
RIT Query Stop Request(Request ID)
RIT Query Stop Response(Request ID)
RIT Query Stop Error(Request ID, …)

This operation allows a SMLC to send an indication to another SMLCPP to stop sending RIT information, that 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 as 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

---------------------- Page: 10 ----------------------
3GPP TS 48.031 version 13.0.0 Release 13 10 ETSI TS 148 031 V13.0.0 (2016-01)
4.2 (void)
4.3 Deciphering Keys Procedure
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. 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.
SMLC SMLC
Server Client
Deciphering Keys Update

4.3.1 Deciphering Keys Update Operation
SMLC SMLC
Deciphering 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 Server, if it detects an error situation
(e.g. syntax errors). It contains the same Request ID values as the Request.
5 Error Handling
In this Clause it is described how the SMLC should act in different error situations.
5.1 Missing Message Part
When a SMLC receives a Request message that does not contain one or more expected message parts (e.g. information
elements, Arguments, Request ID), it sends an Error with the indication 'Missing Message Part' (if the operation type is
known), and ignores the Request.
When a SMLC receives a Response or Error message that does not contain one or more expected message parts, it
ignores the message.
5.2 Repeated Message Part
When a SMLC receives a Request message that contains one or more message parts (e.g. information elements,
Arguments, Request ID) more times than expected, it sends an Error with the indication 'Repeated Message Part', and
ignores the Request.
ETSI

---------------------- Page: 11 ----------------------
3GPP TS 48.031 version 13.0.0 Release 13 11 ETSI TS 148 031 V13.0.0 (2016-01)
When a SMLC receives a Response or Error message that contains one or more message parts more times than
expected, it ignores the message.
5.3 Unforeseen Message Part
When a SMLC receives a Request message that contains one or more unforeseen message parts (e.g. information
elements, Result), it sends an Error with the indication 'Unforeseen Message Part', and ignores the Request.
When a SMLC receives a Response or Error message that contains one or more unforeseen message parts, it ignores the
message.
5.4 Incorrect Data
When a SMLC receives a Request message that it can not fully understand, that contains syntax errors, or incorrect
values, and no other Error Indication applies, it sends an Error with the indication 'Incorrect Data' (if the operation type
is known), and ignores the Request. If the SMLC can not understand the operation of the Request,it just ignores the
Request.
When a SMLC receives a Response or Error message that it can not fully understand, that contains syntax errors, or
incorrect values, it ignores the message.
5.5 Repeated Operation
When a SMLC receives a Request message containing a Request ID, that is already in use by the same type of
operation, the SMLC sends an Error with the indication 'Repeated Operation', and ignores the latter Request. In order to
avoid mistaken use of this error indication for an open-ended repetitive RIT Indication, an SMLC server may choose
not to send a RIT Indication Request until it has received a RIT Indication Response or RIT Indication Error from the
SMLC Client for any previous RIT Indication Request. An SMLC Client may likewise choose no
...