ETSI TS 144 071 V13.0.0 (2016-01)

Digital cellular telecommunications system (Phase 2+); Location Services (LCS); Mobile radio interface layer 3 LCS specification (3GPP TS 44.071 version 13.0.0 Release 13)

RTS/TSGG-0244071vd00

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 1144 071 V13.0.0 (201616-01)

TECHNICAL SPECIFICATIONION
Digital cellular telecocommunications system (Phahase 2+);
Locatcation Services (LCS);
Mobile radio inteterface layer 3 LCS specificatation
(3GPP TS 44.0.071 version 13.0.0 Release 13 13)

R
GLOBAL SYSTTEME FOR
MOBILE COMMUUNNICATIONS
3GPP TS 44.071 version 13.0.0 Release 13 1 ETSI TS 144 071 V13.0.0 (2016-01)

Reference
RTS/TSGG-0244071vd00
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
3GPP TS 44.071 version 13.0.0 Release 13 2 ETSI TS 144 071 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
3GPP TS 44.071 version 13.0.0 Release 13 3 ETSI TS 144 071 V13.0.0 (2016-01)
Contents
Intellectual Property Rights . 2
Foreword . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Generic procedures for the control of location services . 8
4.1 Overview of the generic protocol and its scope . 8
4.2 Functional procedures for the control of location services . 8
4.2.1 General . 8
4.2.2 Common Information Element Category . 9
4.2.3 Location service procedures . 9
4.2.3.1 Introduction . 9
4.2.3.2 Handling of protocol errors in LCS procedures . 9
4.2.3.3 Handling of other errors in LCS procedures . 9
4.2.4 Multiple location service invocations . 10
4.2.5 Recovery procedures. 10
4.2.6 Generic protocol error handling for the component part of location services operations . 10
4.2.6.1 Single component errors . 10
4.2.6.2 Multiple component errors . 10
5 Location service support procedures . 10
5.1 General . 10
5.2 Location service support establishment . 10
5.2.1 Location service support establishment at the originating side . 10
5.2.2 Location service support establishment at the terminating side . 11
5.3 Location service support information transfer phase . 11
5.4 Location service support release . 11
5.5 Recovery procedures . 11
5.6 Message flow (single operation example) . 11
5.6.1 LMU initiated location service transaction . 12
5.6.2 Network initiated location service transaction . 13
5.7 Handling of unknown, unforeseen, and erroneous protocol data . 13
5.7.1 General . 13
5.7.2 Message too short . 14
5.7.3 Unknown or unforeseen transaction identifier . 14
5.7.4 Unknown or unforeseen message type. 14
5.7.5 Non-semantical mandatory Information Element Error. 14
5.7.6 Unknown and Unforeseen IEs in the non-imperative part . 15
5.7.6.1 IEIs unknown in the message . 15
5.7.6.2 Out of sequence IEs . 15
5.7.6.3 Repeated IEs . 15
5.7.7 Non-imperative message part errors . 15
5.7.7.1 Syntactically incorrect optional IEs (other than Facility) . 15
5.7.7.2 Conditional IE errors . 15
6 Message functional definitions and contents . 16
6.1 General . 16
6.2 Messages for location services control . 16
6.3 Facility . 17
ETSI
3GPP TS 44.071 version 13.0.0 Release 13 4 ETSI TS 144 071 V13.0.0 (2016-01)
6.4 Register . 17
6.4.1 Register (network to LMU direction) . 17
6.4.2 Register (LMU to network direction) . 17
6.5 Release complete . 18
6.5.1 Cause . 18
6.5.2 Facility . 18
7 General message format and information elements coding. 18
7.1 Overview . 18
7.2 Protocol discriminator . 19
7.3 Transaction identifier . 19
7.4 Message type . 19
7.5 Facility information element . 19
7.6 Release forbidden . 19
8 Detailed message format and information elements coding . 20
8.1 Transparent LCS Information. 20
8.1.1 Operation Code . 21
8.1.2 Error Code . 21
8.1.3 Problem Code . 22
9 LMU LCS Protocol operation specifications . 22
9.1 General . 22
9.2 Operation types . 23
9.2.1 Operation types description . 26
9.2.1.1 StartRIT (network --> LMU) . 26
9.2.1.2 ReportRIT (LMU -->network) . 26
9.2.1.3 StopRIT (network --> LMU) . 26
9.2.1.4 IndicateRITError (LMU --> network) . 26
9.2.1.5 (void) . 26
9.2.1.6 StatusQuery (network --> LMU). 26
9.2.1.7 StatusUpdate (LMU --> network) . 26
9.2.1.8 ResetRequest (network --> LMU) . 26
9.2.1.9 OMMngrRequest (network --> LMU) . 26
9.2.1.10 OMAgntRequest (LMU --> network) . 26
10.3 Error types . 26
10.3.1 Error types ASN.1 specification . 26
10.3.2 Error types description . 27
10.3.2.1 (void) . 27
10.3.2.2 (void) . 27
10.3.2.3 (void) . 27
10.3.2.4 SystemFailure . 27
10.3.2.5 DataMissing . 27
10.3.2.6 UnexpectedDataValue . 27
10.3.2.7 ResourcesNotAvailable . 27
10.3.2.9 UnDefinedError . 27
10.4 Operations and errors implementation . 28
11 LMU LCS Protocol (LLP) messages . 29
11.1 Messages, data types and identifiers. 29
11.1.1 General . 29
11.1.2 ASN.1 data types . 29
11.1.3 Identifiers definition . 37
Annex A (informative): RIT messages . 38
A.1 Introduction . 38
A.2 Messages . 38
A.2.1 RIT Measurement Request Message . 38
A.2.1.1 RIT Measurement Request Message Information Elements . 38
A.2.1.1.1 Message Type IE . 38
A.2.1.1.2 Measurement Instructions IE . 38
A.2.1.1.3 BTS List IE . 40
A.2.2 RIT Measurement Response Message . 41
ETSI
3GPP TS 44.071 version 13.0.0 Release 13 5 ETSI TS 144 071 V13.0.0 (2016-01)
A.2.2.1 RIT Measurement Response Message Information Elements . 41
A.2.2.1.1 Message type IE . 41
A.2.2.1.2 RIT Measurement IE . 41
A.2.3 RIT Measurement Stop Message . 46
A.2.3.1 RIT Measurement Stop Message Information Elements . 46
A.2.3.1.1 Message type IE . 46
A.2.4 RIT Measurement Error Message . 46
A.2.4.1 RIT Measurement Error Message Information Elements. 47
A.2.4.1.1 Message type IE . 47
A.2.4.1.2 RIT Error Type IE . 47
A.2.4.1.3 RIT Error IE . 47
Annex B (informative): (void) . 48
Annex C (informative): Status Messages . 49
C.1 Introduction . 49
C.2 Messages . 49
C.2.1 Status Query Message . 49
C.2.1.1 Status Query Message Information Elements . 49
C.2.1.1.1 Message Type IE . 49
C.2.2 Status Query Result Message. 49
C.2.2.1 Status Query Result Message Information Elements . 49
C.2.2.1.1 Message Type IE . 49
C.2.2.1.2 Time IE . 50
C.2.2.1.3 RIT Status IE . 50
C.2.2.1.4 Reserved IE . 50
C.2.2.1.5 O&M Status IE . 50
C.2.3 Status Update Message . 51
C.2.3.1 Status Update Message Information Elements . 51
C.2.3.1.1 Message Type IE . 51
C.2.3.1.2 Reason for Status Update IE . 51
Annex D (informative): Change history . 52
History . 53

ETSI
3GPP TS 44.071 version 13.0.0 Release 13 6 ETSI TS 144 071 V13.0.0 (2016-01)
Foreword
rd
This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).
The present document defines the contents of LCS assistance data broadcast messages from the Serving Mobile
Location Centre (SMLC) and the Mobile Station (MS).
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
3GPP TS 44.071 version 13.0.0 Release 13 7 ETSI TS 144 071 V13.0.0 (2016-01)
1 Scope
The present document contains the coding of information necessary for support of location service operation on the
mobile radio interface layer 3 between the LMU and SMLC.
Clause 4 defines generic procedures for the control of location services. In clause 5 location service support procedures
are defined. Clause 6 gives the functional definitions and contents of messages for location service operations. Clause 7
gives the general format and coding for messages used for location service and the format and coding of information
elements used for location service operations. Clause 6 gives the detailed message format and information elements
coding between the LMU and SMLC.
Clause 8 gives the specification of the LMU LCS Protocol (LLP) operations. In clause 9 LMU - SMLC messages, data
types and identifiers are given.
This version does not support segmentation of messages.
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 TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface Data Link (DL)
layer specification".
[3] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[4] 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control Protocol".
[5] 3GPP TS 43.059: "Functional Stage 2 Description of Location Services (LCS) in GERAN".
[6] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[7] ITU-T Recommendation X.691 (1997) | ISO/IEC 8825-2 (1998): "Information technology -
ASN.1 encoding rules: Specification of Packed Encoding Rules (PER)".
[8] ITU-T Recommendation X.690 (1997) | ISO/IEC 8825-1 (1998): "Information technology -
ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules
(CER) and Distinguished Encoding Rules (DER)".
[9] ITU-T Recommendation X.680 (1997) | ISO/IEC 8824-1 (1998): "Information technology -
Abstract Syntax Notation One (ASN.1): Specification of basic notation".
[10] ITU-T Recommendation Q.773: "Transaction capabilities formats and encoding".
[11] (void)
[12] 3GPP TS 44.004: "Layer 1; General requirements".
[13] 3GPP TS 44.005: "Data Link (DL) layer General aspects".
[14] 3GPP TS 24.008: "Mobile radio interface layer 3 specification; Core Network Protocols; Stage 3".
ETSI
3GPP TS 44.071 version 13.0.0 Release 13 8 ETSI TS 144 071 V13.0.0 (2016-01)
[15] 3GPP TS 45.002: "Multiplexing and Multiple Access on the Radio Path".
[16] 3GPP TS 52.071: "Location Services (LCS); Location services management".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
E-OTD Assistance Data Message: contains the RTD and BTS coordinates of the neighbours that should be used in E-
OTD measurements. This E-OTD Assistance Data is broadcasted using CBCH channel using SMSCB DRX service.
The reception of this broadcast message enables MS to calculate its own location.
GPS Assistance Data Message: contains GPS differential corrections. The reception of this broadcast message enables
MS to have calculate more accurate location estimate.
GANSS Assistance Data Message: contains GANSS differential corrections. The reception of this broadcast message
enables MS to have calculate more accurate location estimate.
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 and 3GPP TS 43.059.
4 Generic procedures for the control of location
services
4.1 Overview of the generic protocol and its scope
One generic protocol is defined for the control of location services at the radio interface. This protocol operates at
layer 3 of the radio interface and assumes the use of layers 1 and 2 conform to 3GPP TS 45-series and 3GPP TS 44.004,
3GPP TS 44.005 and 3GPP TS 44.006. The generic protocol uses the acknowledged information transfer service
available at the layer 2 - layer 3 interface.
The Functional protocol is based on the use of the Facility information element and the FACILITY message as well as
other specific functional messages specified in the present document.
4.2 Functional procedures for the control of location services
4.2.1 General
This subclause specifies the functional signalling procedures for the control of location services at the radio interface.
The functional protocol utilizes functions and services defined in 3GPP TS 24.008, 3GPP TS 44.018 and the functions
of the data link layer as defined in 3GPP TS 44.006. This protocol utilizes also definitions in 3GPP TS 24.007.
The Common Information Element Category utilizes the Facility information element to transport the protocol defined
in the present document. The use of the Facility information element is common to many services, and its contents
indicates what type of procedure is being requested. This category can be signalled both in the LMU to network and the
network to LMU directions.
The correlation of location service operations and their responses, is provided by the combination of the transaction
identifier of the messages containing the Facility information element and the Invoke identifier present within the
Facility information element itself.
ETSI
3GPP TS 44.071 version 13.0.0 Release 13 9 ETSI TS 144 071 V13.0.0 (2016-01)
4.2.2 Common Information Element Category
The Common Information Element Category uses operations defined in the present document for location services
signalling. Procedures are initiated by sending an operation including an invoke component. The invoke component
may yield a Return Error, Return Result or Reject component (also included in an operation) depending on the outcome
of the procedure.
The operation state machines, and procedures for management of Invoke IDs specified in ITU-T
Recommendation Q.774 White Book are used.
A REGISTER message, a FACILITY message or RELEASE COMPLETE message is used to carry the Facility
information element which includes these operations. These operations request, acknowledge or reject the desired
location service procedure.
4.2.3 Location service procedures
4.2.3.1 Introduction
For location service procedures independent of any call, the initiating side must establish a MM-connection between the
network and the LMU according to the rules given in 3GPP TS 24.007 and 3GPP TS 24.008. The LMU or the network
starts the transaction by transferring a REGISTER message across the radio interface. This transaction is identified by
the transaction identifier associated with the REGISTER message present in the component part of the Facility
information element. Following the REGISTER message one or more FACILITY messages may be transmitted, all of
them related by the use of the same transaction identifier. If the transaction is no longer used, it shall be released by
sending a RELEASE COMPLETE message. This procedure is specified in detail in clause 5, and the text in clause 5
takes precedence over this introduction.
To convey the location service invocation, the Facility information element is used. The Facility information element
present either in the REGISTER message or a subsequent message identifies the location service involved and the type
of component (i.e. Invoke, Return result, Return error or Reject component).
When the REGISTER or FACILITY message contains a Facility information element and the requested service is
available, a FACILITY message containing a Facility information element may be returned. One or more exchanges of
FACILITY messages may subsequently occur. To terminate the service interaction and release the transaction identifier
value, a RELEASE COMPLETE message is sent as specified for the specific location service procedure. The
RELEASE COMPLETE message may also contain the Facility information element.
4.2.3.2 Handling of protocol errors in LCS procedures
Messages containing a Facility information element shall be checked for protocol errors before the contents of the
Facility IE is acted on. The checks shall be performed in the following order:
1) The message carrying the Facility IE shall be checked for protocol errors as specified in subclause 5.7. If a
protocol error is found then the procedures in subclause 5.7 apply.
2) The contents of the Facility IE shall be checked for protocol errors as specified in subclause 4.2.6. If a protocol
error is found then the procedures in subclause 4.2.6 apply.
4.2.3.3 Handling of other errors in LCS procedures
If the tests specified in subclause 4.2.3.2 have been passed without the detection of a protocol error, the receiver will
attempt to process the contents of the Facility Information Element. If errors occur during this processing (e.g. system
failure, or information in the Facility IE is incompatible with the requested operation) then the procedures specified in
the individual service specifications apply.
An example of the behaviour that could occur in this case is:
- the LMU or network sends a Facility information element containing a return error component in a FACILITY
or RELEASE COMPLETE message. If the FACILITY message is used then the MM Connection may continue
to be used for further signalling.
ETSI
3GPP TS 44.071 version 13.0.0 Release 13 10 ETSI TS 144 071 V13.0.0 (2016-01)
4.2.4 Multiple location service invocations
It is possible for several LCS transactions to be used simultaneously. LCS transactions can also exist in parallel with
other CM-Layer and MM transactions. The handling of multiple MM connections is defined in 3GPP TS 24.007 and
3GPP TS 24.008.
A single Facility Information Element shall not contain more than one component.
4.2.5 Recovery procedures
In case a transaction is not terminated according to the normal procedure as described in the present document the
network side has to ensure that the transaction is terminated e.g. by a supervision timer.
4.2.6 Generic protocol error handling for the component part of location
services operations
If a location service operation is to be rejected the operation will be denied, and provided the transaction is still in
progress, an appropriate reject component will be returned in a Facility Information Element.
4.2.6.1 Single component errors
The reject component shall be sent in a RELEASE COMPLETE message.
If the component containing the error was itself sent in a RELEASE COMPLETE message then the contents of the
component shall be ignored, and no reject component is sent.
4.2.6.2 Multiple component errors
If a single Facility IE contains more than one component then a RELEASE COMPLETE message with the cause
"Facility rejected" and without any component shall be sent.
5 Location service support procedures
5.1 General
This clause describes the location service support procedures at the radio interface. These procedures are provided by
the location service support entity defined in 3GPP TS 24.007. The location service support procedures provide the
means to transfer messages for the location service procedures. These procedures are regarded as the user of the
location service support.
5.2 Location service support establishment
At the beginning of each location service procedure a location service support must be established.
5.2.1 Location service support establishment at the originating side
If the entity that uses the location support procedures needs to send a REGISTER message, the location service support
entity shall first request the establishment of an MM-connection. This MM-connection is established according to
3GPP TS 24.008 and 3GPP TS 24.007. If the network is the initiating side then MM-connection establishment may
involve paging the LMU.
The location service support entity shall send the REGISTER message as the first CM-message on the MM-connection.
The REGISTER message is sent to the corresponding peer entity on the MM-connection and the location service
support shall be regarded as being established.
ETSI
3GPP TS 44.071 version 13.0.0 Release 13 11 ETSI TS 144 071 V13.0.0 (2016-01)
5.2.2 Location service support establishment at the terminating side
At the terminating side a location service support is regarded as being established when an MM-connection is
established. According 3GPP TS 24.008 this can be ascertained by the receipt of the first message, with a new
transaction identifier. For successful establishment of location service support this message shall be a REGISTER
message.
If the terminating side needs to reject the establishment of location services support then it may be immediately initiate
location services support release (see subclause 5.4).
5.3 Location service support information transfer phase
After the establishment of the location service support both users may exchange FACILITY messages by use of the
location service support.
5.4 Location service support release
At the end of each location service procedure the established location service support is released, if a permanent
connection is not used.
The side closing the transaction shall release the transaction by sending the RELEASE COMPLETE message to its
corresponding peer entity.
Both location service support entities release the MM-connection locally.
5.5 Recovery procedures
The location service support does not provide recovery procedures, i.e. the operations are transparent to the location
service support.
5.6 Message flow (single operation example)
This subclause contains examples of message flows for a single transaction consisting of a single operation. These
examples may not show all possibilities.
ETSI
3GPP TS 44.071 version 13.0.0 Release 13 12 ETSI TS 144 071 V13.0.0 (2016-01)
5.6.1 LMU initiated location service transaction
LMU Network
REGISTER
------------------------------------------------------------------------------------------------------------------------------------>
Facility (Invoke = Operation (Location service code, Parameter(s)))

RELEASE COMPLETE or FACILITY
<------------------------------------------------------------------------------------------------------------------------------------
Facility (Return result = Operation (Parameter(s)))

RELEASE COMPLETE or FACILITY
<- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Facility (Return error (Error))

RELEASE COMPLETE
<- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Facility (Reject (Invoke_problem))

RELEASE COMPLETE (note)
<- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

RELEASE COMPLETE (note)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >
NOTE: To prevent transactions being kept open following exceptional cases, either side of the transaction may
release it by sending a RELEASE COMPETE message without a Facility IE.

Figure 5.6.1: LMU initiated location service transaction
ETSI
3GPP TS 44.071 version 13.0.0 Release 13 13 ETSI TS 144 071 V13.0.0 (2016-01)
5.6.2 Network initiated location service transaction
LMU Network
REGISTER
<------------------------------------------------------------------------------------------------------------------------------------
Facility (Invoke = Operation (Location service code, Parameter(s)))

RELEASE COMPLETE or FACILITY (note 1)
------------------------------------------------------------------------------------------------------------------------------------>
Facility (Return result = Operation (Parameter(s))

RELEASE COMPLETE or FACILITY (note 1)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ->
Facility (Return error (Error))

RELEASE COMPLETE (note 1)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ->
Facility (Reject (Invoke_problem))

RELEASE COMPLETE (note 1, note 2)
- - - - -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
...