5.2.2 Mobile initiated location services operations

24.5713GPP5G System (5GS)Control plane Location Services (LCS) proceduresRelease 17Stage 3TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.2.2.1 Mobile Originiated Location Request(MO-LR)

5.2.2.1.1 General

The supplementary services MO-LR operation enables the UE to launch MO positioning session or request location assistance data using NAS signaling. The NAS signaling are transported using the DL NAS Transport message and the Uplink NAS Transport message defined in 3GPP TS 24.501 [3]. Figure 5.2.2.1.1-1 illustrates an example of the NAS signaling transport for an MO-LR session.

Figure 5.2.2.1.1-1: NAS signaling transport for MO-LR

NOTE: The optional Additional Information IE of the UL/DL NAS TRANSPORT message is not used when the MO-LR signaling is transported in the Payload container.

5.2.2.1.2 Normal operation

The UE 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 UE by sending a FACILITY message to the UE 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 UE only if the location estimate is given in a format that the UE supports, as indicated by either the presence (and content) or the absence of the parameter supportedGADShapes, which may be sent by the UE in the LCS-MOLR operation.

The UE may terminate the dialogue by sending a RELEASE COMPLETE message in the case of single location request (see figure 5.2.2.1.1-1). The UE 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.2.1.1-2). After the last location request operation the UE shall terminate the dialogue by sending a RELEASE COMPLETE message.

If the network is unable to successfully fulfil the request received from the UE (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 [5]. If the network is unable to provide a location estimate due to lack of support in the UE 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 UE 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 UE, the network may clear the transaction by sending a RELEASE COMPLETE message.

During the MO-LR operation the UE 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 UE 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.

UE Network

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

Facility (Invoke = LCS-MOLR (molr-Type, lcs-QoS, lcsClientExternalID, mlc-Number, supportedGADShapes, lcsServiceTypeID, ageOfLocationInfo, locationType, pseudonymIndicator, h-gmlc-address,multiplePositioningProtocolPDUs, scheduledLocTime))

FACILITY

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

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

RELEASE COMPLETE

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

Facility (Return error (Error))

RELEASE COMPLETE

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

Facility (Reject (Invoke_problem))

RELEASE COMPLETE

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

Figure 5.2.2.1.1-1: Single mobile originated location request

UE Network

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

Facility (Invoke = LCS-MOLR Request (molr-Type, lcs-QoS, lcsClientExternalID, mlc-Number, supportedGADShapes, lcsServiceTypeID, ageOfLocationInfo, locationType, pseudonymIndicator, h-gmlc-address, multiplePositioningProtocolPDUs, scheduledLocTime))

FACILITY

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

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

RELEASE COMPLETE

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

Facility (Return error (Error))

RELEASE COMPLETE

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

Facility (Reject (Invoke_problem))

FACILITY

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

FACILITY

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

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

RELEASE COMPLETE

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

Facility (Return error (Error))

RELEASE COMPLETE

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

Facility (Reject (Invoke_problem))

RELEASE COMPLETE

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

Figure 5.2.2.1.1-2: Multiple mobile originated location requests

NOTE 1: Only the following IEs defined in MO-LR operations in 3GPP TS 24.080 [5] are used for NG-RAN LCS:

– molr-Type

– lcs-QoS

– lcsServiceTypeID

– ageOfLocationInformation

– locationType

– mlc-Number

– lcsClientExternalID

– pseudonymIndicator

– supportedGADShapes

– multiplePositioningProtocolPDUs

– locationEstimate

– h-gmlc-address

– decipheringKeys

– scheduledLocTime

NOTE 2: multiplePositioningProtocolPDUs IE is added to the MO-LR Request to allow for passing multiple UE positioning information LPP messages (e.g. UE location measurements or UE capabilities) to the LMF for NG-RAN LCS. Its ASN.1 description is given in 3GPP TS 24.080 [5], where the maximum number of LPP messages is specified. There is one or more types of multiple LPP messages can be encapsulated in one multiplePositioningProtocolPDUs IE.

5.2.2.2 UE initiated Cancel Deferred Location

5.2.2.2.1 General

The supplementary services MSCancelDeferredLocation operation enables the UE to cancel ongoing periodic or triggered location in a target LMF using NAS signalling as described in 3GPP TS 23.273 clause 6.3.3 [2]. The supplementary services MCancelDeferredLocation messages are transported using the UL NAS TRANSPORT message and the DL NAS TRANSPORT message defined in 3GPP TS 24.501 [3]. The deferred routing identifier in the Additional information IE of the UL NAS TRANSPORT message for the cancellation of periodic or triggered location event reporting can be an LMF ID.

Figure 5.2.2.2.1-1: NAS signaling transport for UE initiated Cancel Deferred Location

5.2.2.2.2 Normal operation

The UE invokes a cancel deferred location procedure by sending a REGISTER message containing a LCS-MSCancelDeferredLocation invoke component to the LMF as defined in 3GPP TS 24.080 [5].

The LMF shall terminate the ongoing periodic or triggered location if this can be identified from the information in the LCS-MSCancelDeferredLocation invoke component.

The LMF shall then return a RELEASE COMPLETE message containing an LCS-MSCancelDeferredLocation return result component (see Figure 5.2.2.2.2-1).

If the LMF is unable to process the request received from the UE or can not identify the ongoing periodic or triggered location to be terminated, it shall return an error indication by sending a RELEASE COMPLETE message containing a return error component. Error values are specified in 3GPP TS 24.080 [5].

UE Network

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

Facility (Invoke = LCS-MSCancelDeferredLocation (referenceNumberExt, h-gmlc-callBackUri))

RELEASE COMPLETE

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

Facility (Return result = LCS-MSCancelDeferredLocation)

RELEASE COMPLETE

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

Facility (Return error (Error))

RELEASE COMPLETE

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

Facility (Reject (Invoke_problem))

RELEASE COMPLETE

– – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – ->

Figure 5.2.2.2.2-1: Cancel Deferred Location

NOTE: Only the following IEs defined in MSCancelDeferredLocation operations in 3GPP TS 24.080 [5] are used for NG-RAN LCS:

– referenceNumberExt

– h-gmlc-callBackUri

5.2.2.3 UE initiated Positioning Information Transport

The UE sends LPP message and the associated Routing identifier in the UL NAS Transport message (refer to 3GPP TS 24.501 [3] and 3GPP TS 23.273 [2] clause 6.11.1). Figure 5.2.2.3-1 illustrates an example of the NAS signalling transport for uplink LPP messages.

Figure 5.2.2.3-1: NAS signalling transport for uplink LPP messages

5.2.2.4 UE initiated Event Reporting Procedure

5.2.2.4.1 General

The supplementary services EventReport operation enables the UE to report the periodic or triggered location event invoked by the LMF via LCS PeriodicTriggered Invoke operation as described in clause 6.3.1 of 3GPP TS 23.273 [2] when some certain events are detected in the UE. The supplementary services EventReport message is transferred to the LMF via the serving AMF in a UL NAS TRANSPORT message defined in 3GPP TS 24.501 [3]. A response from the LMF may be returned to the UE via the serving AMF and be transferred to the UE in a DL NAS TRANSPORT message. The deferred routing identifier in the Additional information IE of the UL NAS TRANSPORT for reporting the periodic or triggered location event can be an LMF ID. If the serving LMF is changed, the deferred routing identifier may be included in the EventReport Acknowledgement message (refer to clause 6.3.1 of 3GPP TS 23.273 [2]).

Figure 5.2.2.4.1-1 illustrates an example of the NAS signalling transport for EventReport messages,

Figure 5.2.2.4.1-1: NAS signalling transport for EventReport messages

5.2.2.4.2 Normal operation

The UE invokes an EventReport procedure by sending a REGISTER message containing an EventReport component to the LMF as defined in 3GPP TS 24.080 [5].

The LMF shall return a supplementary services acknowledgement of event report if it can handle this event report.

The LMF shall then return a RELEASE COMPLETE message containing an EventReport Acknowledge component (see Figure 5.2.2.4.2-1).

UE Network

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

Facility (Invoke = LCS-EventReport (eventType, referenceNumberExt, h-gmlc-callBackUri, lcs-QoS, locationInfo, supportedGADShapes, multiplePositioningProtocolPDUs, terminationCause))

RELEASE COMPLETE

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

Facility (Return result = LCS-EventReport Acknowledgement)

RELEASE COMPLETE

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

Facility (Return error (Error))

RELEASE COMPLETE

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

Facility (Reject (Invoke_problem))

RELEASE COMPLETE

– – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – ->

Figure 5.2.2.4.2-1: EventReport

NOTE: Only the following IEs defined in EventReport operations in 3GPP TS 24.080 [5] are used for NG-RAN LCS:

– eventType

– referenceNumberExt

– h-gmlc-callBackUri

– lcs-QoS

– locationInfo

– supportedGADShapes

– multiplePositioningProtocolPDUs

– terminationCause

5.2.2.5 UE Location Privacy Setting Procedure

5.2.2.5.1 General

The supplmentary services LocationPrivacySetting operation enables the UE to update the UE Location Privacy Indication information via UE Location Privacy Setting procedure as described in clause 6.12.1 of 3GPP TS 23.273 [2] when the UE has generated or updated the UE Location Privacy Indication. The supplementary services LocationPrivacySetting message is transferred to the serving AMF in a UL NAS TRANSPORT message and an acknowledgement from the serving AMF may be returned to the UE in DL NAS TRANSPORT message defined in 3GPP TS 24.501 [3].

Figure 5.2.2.5.1-1 illustrates an example of the NAS signalling transport for UE Location Privacy Setting procedure,

Figure 5.2.2.5.1-1: NAS signalling transport for LocationPrivacySetting messages

5.2.2.5.2 Normal operation

The UE invokes a Location Privacy Setting procedure by sending a REGISTER message containing an LocationPrivacySetting message as defined in 3GPP TS 24.080 [5]. UE’s Location Privacy Indication information is included in LocationPrivacySetting message.

The AMF shall transfers the UE Location Privacy Indication information in LocationPrivacySetting message to UDM and response a supplementary services acknowledgement of LocationPrivacyIndication message

The AMF shall then return a RELEASE COMPLETE message containing a LocationPrivacySetting Acknowledgement component (see figure 5.2.2.5.2-1) if it can handle this LocationPrivacySetting message correctly.

If the AMF is unable to process the request received from the UE or can not identify that provisioning the parameters of UE Location Privacy Setting information to UDM is executed successfully, it shall return an error indication by sending a RELEASE COMPLETE message containing a return error component. Error values are specified in 3GPP TS 24.080 [5].

UE Network

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

Facility (Invoke = LCS-LocationPrivacySetting (locationPrivacyIndication, validTimePeriod)

RELEASE COMPLETE

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

Facility (Return result = LCS-LocationPrivacySetting Acknowledgement)

RELEASE COMPLETE

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

Facility (Return error (Error))

RELEASE COMPLETE

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

Facility (Reject (Invoke_problem))

RELEASE COMPLETE

– – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – ->

Figure 5.2.2.5.2-1: LocationPrivacySetting

NOTE: Only the following IEs defined in LocationPrivacySetting operations in 3GPP TS 24.080 [5] are used for NG-RAN LCS:

– locationPrivacyIndication

– validTimePeriod

5.2.2.6 UE initiated Event Reporting Procedure for Low Power Event Reporting and Triggered 5GC-MT-LR

5.2.2.6.1 General

The supplementary services EventReport operation enables the UE to report the periodic or triggered location event invoked by the LMF via LCS PeriodicTriggered Invoke operation as described in clause 6.7.1 of 3GPP TS 23.273 [2] when certain events are detected in the UE and when the UE supports and the LMF allows the use of Control Plane CIoT 5GS Optimisation. The supplementary services EventReport message is transferred to the LMF via the serving AMF in a CONTROL PLANE SERVICE REQUEST message defined in 3GPP TS 24.501 [3]. A response from the LMF may be returned to the UE via the serving AMF and be transferred to the UE in a DL NAS TRANSPORT message defined in 3GPP TS 24.501 [3]. The deferred routing identifier in the Additional information IE of the CONTROL PLANE SERVICE REQUEST message for reporting the periodic or triggered location event can be an LMF ID. If the serving LMF is changed, the deferred routing identifier may be included in the EventReport Acknowledgement message (refer to clause 6.3.1 of 3GPP TS 23.273 [2]).

Figure 5.2.2.x.1-1 illustrates an example of the NAS signalling transport for EventReport messages,

Figure 5.2.2.6.1-1: NAS signalling transport for EventReport messages using Low Power Event Reporting and Triggered 5GC-MT-LR

5.2.2.6.2 Normal operation

Normal operation is as described for the UE initiated Event Reporting Procedure in clause 5.2.2.4.2.