7 Information storage

23.2733GPP5G System (5GS) Location Services (LCS)Release 18Stage 2TS

7.1 UDM

For each UE subscriber the UDM stores LCS related data as part of the Subscriber Data Management (SDM) service as defined in clause 5.2.3.3.1 of TS 23.502 [19].

The privacy profile data is defined in table 7.1-1 containing data for the privacy classes for which location of the target UE is permitted. For the meaning of each LCS privacy profile data type and included data, refer to clause 5.4.2.

Table 7.1-1: LCS privacy profile data stored in the UDM for a UE Subscriber

Privacy Profile Data Type

Presence

UDM data

Location Privacy Indication

M

O

Indication of one of the following mutually exclusive global settings:

– Location is disallowed

– Location is allowed (default)

Time period when the Location Privacy Indication is valid

Call/session Unrelated Class

M

O

O

O

O

O

O

O

O

O

O

O

O

O

For any LCS client or AF not in the external LCS client list or otherwise identified for the Call/session Unrelated Class, the following data may be present:

– One of the following mutually exclusive options:

– Location not allowed (default case)

– Location allowed with notification

– Location with notification and privacy verification; location allowed if no response

– Location with notification and privacy verification; location restricted if no response

– Time period when positioning is allowed

– Geographical area where positioning is allowed

– Indication that codeword shall be checked in UE or one or more codeword values to be checked in GMLC

External LCS client list: a list of zero or more LCS clients, AFs and LCS Client groups with the following data for each entry:

– One of the following mutually exclusive options:

– Location allowed without notification (default case)

– Location allowed with notification

– Location with notification and privacy verification; location allowed if no response

– Location with notification and privacy verification; location restricted if no response

– Time period when positioning is allowed

– Geographical area where positioning is allowed

Service types list: a list of one or more service types for which the LCS client is allowed to locate the particular UE. The possible service types are defined in TS 22.071 [2]. The following data may be present for each service type in the list:

– One of the following mutually exclusive options:

– Location allowed without notification (default case)

– Location allowed with notification

– Location with notification and privacy verification; location allowed if no response

– Location with notification and privacy verification; location restricted if no response

– Time period when positioning is allowed

– Geographical area where positioning is allowed

– Indication that codeword shall be checked in UE or one or more codeword values to be checked in GMLC

PLMN Operator Class

O

LCS client list: a list of one or more generic classes of LCS client that are allowed to locate the particular UE. The following classes are distinguished:

– LCS client broadcasting location related information

– O&M LCS client in the HPLMN

– O&M LCS client in the VPLMN

– LCS client recording anonymous location information

– LCS Client supporting a bearer service, teleservice or supplementary service to the target UE

– NWDAF in the HPLMN (when the UE is currently being served by the HPLMN)

– NWDAF in the VPLMN

User Plane Connection

O

Indication of one of the following mutually exclusive global settings:

– UE is allowed to report periodic or triggered location events via user plane to an LCS Client or AF

– UE is not allowed to report periodic or triggered location events via user plane to an LCS Client or AF (default)

The Mobile Originating data is defined in table 7.1-1 containing the LCS MO-LR services that a UE can receive.

Table 7.1-2: LCS Mobile Originated data for a UE Subscriber

MO-LR Data

Presence

UDM data

Mobile Originated data

M

List of MO-LR services allowed for a UE subscriber:

– Basic Self Location (UE can receive its own location)

– Autonomous Self Location (UE can receive location assistance data)

– Transfer to Third Party

List of Assistance Data Types for MO-LR

O

A list of one or more types of location assistance data that may be provided to the UE in the MO-LR procedure.

Table 7.1-3: LCS broadcasting data for a UE subscriber

Broadcasting Data

Presence

Description

List of Assistance Data Types

O

A list of one or more types of location assistance data for which ciphering keys should be provided to the UE if requested by the UE when the assistance data is broadcast using ciphering.

7.2 GMLC

7.2.1 Information for an LCS Client

The GMLC holds information for external LCS clients which are permitted to request location information for UE subscribers. Table 7.2.1-1 shows the information which may be stored in the GMLC for an external LCS Client.

Table 7.2.1-1: GMLC Information for an External LCS Client

LCS Client Information

Status

Description

LCS Client Type

M

Identifies the type of LCS client from among the following:

– Emergency Services

– Value Added Services

– PLMN Operator Services

– Lawful Intercept Services

External identifier

O

A list of one or more identifiers used to identify an external LCS client. The identifier may be used for a 5GC-MT-LR and/or 5GC-MO-LR. The format of the identifier is an international E.164 address, ITU-T Recommendation E.164 [23].

Authentication data

MO

Data employed to authenticate an external LCS client if the authentication is not done by a security gateway – details are outside the scope of the present document

Internal identifier

O

Identifies the sub-type of a PLMN operator services LCS Client from among the following:

– LCS client broadcasting location related information

– O&M LCS client in the HPLMN

– O&M LCS client in the VPLMN

– LCS client recording anonymous location information

– LCS Client supporting a bearer service, teleservice or supplementary service to the target UE

Client name

O

An address string which is associated with the LCS client’s external identity (i.e. E.164 address).

Client name type

O

Indication of the type of the LCS client name. The type of the LCS client name can be one of the following:

– Logical name

– MSISDN

– E-mail address (RFC 2396 [25])

– URL (RFC 2396 [25])

– SIP URL (RFC 3261 [26])

– IMS public identity (1 23.228 [27])

– GPSI

Privacy Override Indication

O

Indication of whether the LCS client possesses the POI capability (only applicable to lawful intercept and emergency services clients)

Authorized UE List

O

A list of SUPIs and/or groups of SUPI for which the LCS client may issue a request for a 5GC-MT-LR for immediate or deferred location.

Priority

O

The priority of the LCS client

QoS parameters

M

The default QoS requirements for the LCS client, comprising:

– Accuracy

– Response time

– LCS QoS Class

Service Coverage

O

A list of E.164 country codes for geographic areas, ITU-T Recommendation E.164 [23] where the LCS client is permitted to request and receive UE location information.

Allowed LCS Request Types

M

Indicates which of the following are allowed:

– Request of current immediate location

– Request of current or last known immediate location

– Request of deferred location for the UE available event

– Request of deferred location for UE periodic events

– Request of deferred location for the Area Event

– Request of deferred location for the Motion Event

Local Co-ordinate System

O

Definition of the co-ordinate system(s) in which a location estimate shall be provided – details are outside the scope of the present document

Access Barring List(s)

O

List(s) of SUPIs or groups of SUPI for which a location request is barred

Service types

O

List of service type allowed for the LCS client.

Maximum Target UE Number

O

The maximum number of the Target UEs in one LCS request. For a specific LCS Client, this parameter may have different values for different service types.

User Plane location reporting

O

Indicates whether or not the LCS Client is allowed to request event reporting for a periodic or triggered MT-LR over user plane.

O

Default user plane address for event reporting over user plane.

O

Default security information for event reporting over user plane.