5 Mobile initiated location services operations

24.0303GPPLocation Services (LCS)Release 17Stage 3Supplementary service operationsTS

5.1 Mobile Originated Location Request (MO-LR)

5.1.1 Normal operation

The MS invokes a MO-LR by sending a REGISTER message to the network containing a LCS-MOLR invoke component. SS Version Indicator value 1 or above shall be used.

The receiving network entity shall initiate the handling of location request in the network. The network shall pass the result of the location procedure to the MS by sending a FACILITY message to the MS containing a LCS-MOLR return result component. When location estimate is kept in the network entity and this information satisfies the requested accuracy and the requested maximum age of location, then the network may reuse this information and the positioning measurement procedure may be skipped.

The network shall pass the result of the location procedure to the MS only if the location estimate is given in a format that the MS supports, as indicated by either the presence (and content) or the absence of the parameter supportedGADShapes, which may be sent by the MS in the LCS-MOLR operation.

The MS may terminate the dialogue by sending a RELEASE COMPLETE message in the case of single location request (see figure 5.1). The MS may also initiate another location request operation by sending a FACILITY message to the network containing a LCS-MOLR invoke component (see figure 5.2). After the last location request operation the MS shall terminate the dialogue by sending a RELEASE COMPLETE message.

If the network is unable to successfully fulfil the request received from the MS (e.g. to provide a location estimate or location assistance information), it shall clear the transaction by sending a RELEASE COMPLETE message containing a return error component. Error values are specified in 3GPP TS 24.080. If the network is unable to provide a location estimate due to lack of support in the MS for the type of shape of the location estimate, then it shall use the error Facility Not Supported.

If the network has returned a result to the MS in a FACILITY message but, after some PLMN administered time period has elapsed, has not received either a new location request operation in a FACILITY message or a RELEASE COMPLETE message from the MS, the network may clear the transaction by sending a RELEASE COMPLETE message.

During the MO-LR operation the MS shall run a timer T(LCSL). This timer is started when the operation is sent, and stopped when a response is received from the network. If this timer expires the MS shall assume that the operation has failed, and may terminate the dialogue by sending a RELEASE COMPLETE message, and shall inform the user of the failure.

To support Periodic Location features (see TS 23.271 for details), the LCS-MOLR Invoke and the LCS-MOLR Return Result components carry the periodic location information between the MS and the network. These information are applicable to the instigation, cancellation, and reporting of the periodic location event and the location estimates.

MS Network

REGISTER

————————————————————————————————————————>

Facility (Invoke = LCS-MOLR (molr-Type, locationMethod, lcs-QoS, lcsClientExternalID, mlc-Number, gpsAssistanceData, supportedGADShapes, lcsServiceTypeID, ageOfLocationInfo, locationType, pseudonymIndicator,

h-gmlc-address, locationEstimate, velocityEstimate, referenceNumber, periodicLDRInfo,

locationUpdateRequest, sequenceNumber, terminationCause, mo-lrShortCircuit,

ganssAssistanceData))

FACILITY

<————————————————————————————————————————

Facility (Return result = LCS-MOLR (locationEstimate, velocityEstimate, decipheringKeys, add-LocationEstimate,

referenceNumber, h-gmlc-address, mo-lrShortCircuit, reportingPLMNList))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Return error (Error))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Reject (Invoke_problem))

RELEASE COMPLETE

————————————————————————————————————————>

Figure 5.1: Single mobile originated location request

MS Network

REGISTER

————————————————————————————————————————>

Facility (Invoke = LCS-MOLR (molr-Type, locationMethod, lcs-QoS, lcsClientExternalID, mlc-Number, gpsAssistanceData, supportedGADShapes, lcsServiceTypeID, ageOfLocationInfo, locationType, pseudonymIndicator,

h-gmlc-address, locationEstimate, velocityEstimate, referenceNumber, periodicLDRInfo,

locationUpdateRequest, sequenceNumber, terminationCause, mo-lrShortCircuit,

ganssAssistanceData))

FACILITY

<————————————————————————————————————————

Facility (Return result = LCS-MOLR (locationEstimate, velocityEstimate, decipheringKeys, add-LocationEstimate,

referenceNumber, h-gmlc-address, mo-lrShortCircuit, reportingPLMNList))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Return error (Error))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Reject (Invoke_problem))

FACILITY

————————————————————————————————————————>

Facility (Invoke = LCS-MOLR (molr-Type, locationMethod, lcs-QoS, lcsClientExternalID, mlc-Number, gpsAssistanceData, supportedGADShapes, lcsServiceTypeID, ageOfLocationInfo, locationType, pseudonymIndicator,

h-gmlc-address, locationEstimate, velocityEstimate, referenceNumber, periodicLDRInfo,

locationUpdateRequest, sequenceNumber, terminationCause, mo-lrShortCircuit,

ganssAssistanceData))

FACILITY

<————————————————————————————————————————

Facility (Return result = LCS-MOLR (locationEstimate, velocityEstimate, decipheringKeys, add-LocationEstimate,

referenceNumber, h-gmlc-address, mo-lrShortCircuit, reportingPLMNList))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Return error (Error))

RELEASE COMPLETE

<- – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –

Facility (Reject (Invoke_problem))

RELEASE COMPLETE

————————————————————————————————————————>

Figure 5.2: Multiple mobile originated location requests

Annex A (informative):
Change History

Change history

Date

Meeting

TDoc

CR

Rev

Cat

Subject/Comment

New version

CN#07

–

04.30 v7.1.0 – Transferred to 3GPP

3.0.0

CN#08

001

1

Clarifications on GSM vs. UMTS specific parts

3.1.0

CN#08

002

Correction of MO-LR procedure for LCS

3.1.0

CN#11

Version increased from R99 to Rel-4 after CN#11

4.0.0

CN#11

003

1

Adaptation of SS to PS domain

4.0.0

CN#12

005

Handle new parameters in LCS-MOLR

4.1.0

CN#14

009

Specify usage of SS Version Indicator

4.2.0

CN#14

011

Correction of MO-LR procedure

4.2.0

CN#15

012

Introduction of the "Requestor ID"

5.0.0

CN#16

013

LCS: Codeword and Service Type

5.1.0

CN#22

014

1

Deferred MT-LR Area Event

6.0.0

CN#23

015

Removal of R-GMLC Address

6.1.0

CN#23

016

MO-LR Service Identity support

6.1.0

CN#26

020

1

Correction of missing description for T(LCSN) and T(LCSL)

6.2.0

CN#27

023

1

Pseudonym indicator support in MO-LR

6.3.0

CT#29

024

1

Enabling the Providing of Velocity

7.0.0

CT#29

0025

Addition of Periodic Location Feature Support

7.1.0

CT#36

0026

1

Add Assisted GANSS as a New Positioning Method

7.2.0

CT#36

0028

Unimplemented CR for Reuse of UEs location

7.2.0

CT#42

Upgraded unchanged from Rel-7

8.0.0

2009-12

–

Update to Rel-9 version (MCC)

9.0.0

2011-03

–

Update to Rel-10 version (MCC)

10.0.0

2012-09

–

Update to Rel-11 version (MCC)

11.0.0

2014-09

–

Update to Rel-12 version (MCC)

12.0.0

2015-12

–

Update to Rel-13 version (MCC)

13.0.0

2017-03

–

Update to Rel-14 version (MCC)

14.0.0

2018-06

–

Update to Rel-15 version (MCC)

15.0.0

2020-07

–

Update to Rel-16 version (MCC)

16.0.0

2022-03

CT#95e

–

Update to Rel-17 version (MCC)

17.0.0