Content for TR 23.700-71 Word version: 18.0.0

...

1 Scope p. 11

The scope of this Technical Report is to study further enhancements to the to the 5GC LoCation Services including the following aspects:

Investigate potential architectural enhancements to location service (e.g. in scenarios like edge computing, and other), i.e. support Positioning Signalling via user plane.
Investigate potential architectural enhancements to location service (e.g. in scenarios like edge computing, and other), i.e. reduction of location service latency, signalling overhead and location estimate exposure.
Study how the location services can benefit from NWDAF reporting and how the NWDAF use cases can benefit from location services, e.g. enhanced accuracy in certain UE location or population flow statistics data that require UE locations smaller than TA/cell
Study enhancements to support low power positioning (e.g. for RedCap) including the requirements related to low power high accuracy positioning described in TS 22.104.
Study necessary enhancement to support regulatory requirement i.e. the network should not notify the UE by any means during the LCS session.
Study enhancement to support the Flexible and Efficient Periodic and Triggered Location for UE power saving purpose.
In collaboration with RAN, study specific network functionality related to use of Positioning Reference Units (PRUs) as defined by RAN WGs and study how 5GS to support a specific UE (i.e. Reference UE) to improve the accuracy of positioning, and reduce the signalling:
Study enhancements to support the location service continuity for UE mobility, i.e. between EPS and 5GS;
For 5G with satellite access, in collaboration with RAN, study LCS architectural enhancement to support network verified UE location, and to meet location services related requirements defined in TS 22.261.

2 References p. 11

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]

TR 21.905: "Vocabulary for 3GPP Specifications".

[2]

TS 23.501: "System Architecture for the 5G System; Stage 2".

[3]

TS 23.502: "Procedures for the 5G System; Stage 2".

[4]

TS 23.271: "Functional stage 2 description of Location Services (LCS)".

[5]

TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".

[6]

TS 38.305: "Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN".

[7]

TS 22.104: "Service requirements for cyber-physical control applications in vertical domains".

[8]

TS 22.261: "Service requirements for the 5G system".

[9]

TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".

[10]

TS 23.548: "5G System Enhancements for Edge Computing; Stage 2".

[11]

S3i210282: "LS OUT on UE location aspects in NTN" https://www.3gpp.org/ftp/TSG_SA/WG3_Security/TSGS3_LI/2021_81e-a/Docs/s3i210282.zip.

[12]

RP-213690: "New WI: NR NTN (Non-Terrestrial Networks) enhancements".

[13]

OMA-AD-SUPL-V2_0: "Secure User Plane Location Architecture Approved Version 2.0".

[14]

OMA-TS-ULP-V2_0_6: "User Plane Location Protocol Approved Version 2.0.6".

[15]

TS 37.355: "LTE Positioning Protocol (LPP)".

[16]

TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2".

[17]

TR 23.700-81: "Study on Enablers for Network Automation for 5G; Phase 3".

[18]

TS 22.071: "Location Services (LCS); Service description; Stage 1".

[19]

TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".

[20]

RFC 5246: "The Transport Layer Security (TLS) Protocol Version 1.2".

[21]

TS 24.080: "Supplementary services specification; Formats and coding".

[22]

TS 38.300: "NR; NR and NG-RAN Overall description; Stage-2".

[23]

TR 23.700-86: "Study on Architecture Enhancement to support Ranging based services and sidelink positioning".

[24]

TS 29.522: "5G System; Network Exposure Function Northbound APIs; Stage 3".

[25]

TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)".

[26]

TS 23.032: "Universal Geographical Area Description (GAD)".

3 Definitions of terms, symbols and abbreviations p. 12

3.1 Terms p. 12

For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.

Positioning Reference Unit (PRU):

As defined in TS 38.305.

Reference UE:

A UE with a location assumed known to the network that can obtain location related information of one or more target UE(s), which may assist the network to improve the positioning performance of target UE(s). In this technical report, the Reference UE is the PRU and the location related information is the measurements provided by PRU.

3.2 Abbreviations p. 13

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.

EASDF

Edge Application Server Discovery Function

EDC

Edge DNS Client

FQDN

Fully Qualified Domain Name

LCS

LoCation Service

LCUP

LCs User Plane

LMF

Location Management Function

LPP

LTE Positioning Protocol

LPPe

LPP extension

NPN

Non-Public Network

NWDAF

Network Data Analytics Function

PRU

Positioning Reference Unit

TAI

Tracking Area Identity

ULI

User Location Information

URSP

UE Route Selection Policy

4 Architectural Assumptions and Requirements p. 13

4.1 Architecture assumptions p. 13

The existing 5G LCS architecture is the bases for further enhancement work, with following add on assumption:

Positioning methods may be Access Network specific, although commonalties should be encouraged between Access Networks.

4.2 Architecture requirements p. 13

The following requirements are applicable to further enhance the existing 5GC LCS architecture defined in TS 23.273:

The further enhancement to the 5GC LCS architecture should incorporate flexible modular components with open interfaces that facilitate equipment interoperability and the architectural requirements based on evolution of service providing capabilities.
The further enhancement to the 5GC LCS architecture should be future proof.