Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TR 23.731  Word version:  16.0.0

Top   Top   None   None   Next
1…   5… 
1 Scope  2 References  3 Definitions and abbreviations  3.1 Definitions  3.3 Abbreviations  4 Architectural Requirements and Assumptions  4.1 Architectural Requirements  4.2 Architectural Assumptions 
...

 

1  Scope  p. 11

The objectives of this Technical Report are to enhance the service-based architecture used for location services in the 5G system, and corresponding Network Functions (NFs) and procedures, to meet the service requirements defined in, SA WG1 (e.g. TS 22.261 and TS 22.071), including the consideration of roaming and non-roaming scenarios, and access via 3GPP as well as non-3GPP access technologies (un-trusted, and trusted in TR 23.716). Of particular consideration is how to support location services in 5GS and EPS interworking scenarios, and in non-3GPP access and 3GPP access interworking scenarios.
This Technical Report will need to consider related architectures and functions developed in RAN, and implications if any.
Up

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 22.261: "Service requirements for next generation new services and markets; Stage 1".
[3]
TS 22.071: "Technical Specification Group Systems Aspects; Location Services (LCS)".
[4]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[5]
TS 23.502: "Procedures for the 5G System; Stage 2".
[6]
TS 23.271: "Functional stage 2 description of Location Services (LCS)".
[7]
TS 38.305: "NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN".
[8]
TR 38.913: "Study on scenarios and requirements for next generation access technologies".
[9]
TR 23.716: "Study on the Wireless and Wireline Convergence for the 5G system architecture".
[10]
TR 22.872: "Study on positioning use cases".
[11]
TS 38.455: "NR Positioning Protocol A (NRPPa)".
[12]
TS 36.305: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Stage 2 functional specification of User Equipment (UE) positioning in E-UTRAN".
[13]
Open Mobile Alliance, OMA AD SUPL: "Secure User Plane Location Architecture", (http://www.openmobilealliance.org).
[14]
Open Mobile Alliance, OMA TS ULP: "User Plane Location Protocol", (http://www.openmobilealliance.org).
[15]
TS 36.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); Stage 2 LTE Positioning Protocol (LPP)".
[16]
TR 38.801: "Study on new radio access technology: Radio access architecture and interfaces".
[17]
TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[18]
TS 29.172: "Location Services (LCS); Evolved Packet Core (EPC) LCS Protocol (ELP) between the Gateway Mobile Location Centre (GMLC) and the Mobile Management Entity (MME); SLg interface".
[19]
TS 29.518: "5G System; Access and Mobility Management Services; Stage 3".
[20]
TR 23.724: "Study on Cellular IoT support and evolution for the 5G System".
[21]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[22]
TS 36.300: "(E-UTRAN); Overall description; Stage 2".
[23]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[24]
TR 22.804: "Study on Communication for Automation in Vertical Domains".
[25]
TR 36.880: "Evolved Universal Terrestrial Radio Access (E-UTRA); Study on further enhancements of Minimization of Drive Tests (MDT) for E-UTRAN".
[26]
TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[27]
ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)".
Up

3  Definitions and abbreviations  p. 12

3.1  Definitions  p. 12

For the purposes of the present document, the terms and definitions given in TR 21.905 apply.

3.3  Abbreviations  p. 12

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.
EDT
Early Data Transmission
LDR
Location Deferred Request
RAI
Release Assistance Indication
TTFF
Time to First Fix

4  Architectural Requirements and Assumptions  p. 12

4.1  Architectural Requirements  p. 12

The following requirements should be applicable to 5GC LCS feature:
  • 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 5GC LCS architecture should be future proof e.g. should be able to support high accuracy positioning method and low latency positioning method.
  • Support of single or hybrid positioning methods in order to determine the normative stage-1 requirements location of user equipment (UE). Such positioning method includes methods in NG RAN (To be specified in TS 38.305).
  • It should be possible to provide position information to location services consumer existing within the PLMN, external to the PLMN, or in Mobile Equipment.
  • Support for location services as per the related service requirements defined in TS 22.261 and TS 22.071).
  • 5GC should support the same location services as defined in TS 23.271 for both roaming and non-roaming UEs in a manner compatible with support for EPS. These services comprise the following:
    • Immediate current location of a target UE using an MT-LR,
    • Deferred location of a target UE for the UE available event,
    • Periodic location of a target UE,
    • Triggered location of a target UE for the area event,
    • Triggered location of a target UE for the motion event,
    • Mobile Originated Location Request (MO-LR) for immediate current location of a UE,
    • MO-LR for transfer of assistance data to a UE,
    • MO-LR for Transfer To Third Party (TTTP).
  • 5GC LCS architecture should be able to determine the appropriate positioning method based on the Access Network(s) of the UE.
  • 5GC LCS architecture should be able to support location service in 5GS and EPS interwork scenarios; and in non-3GPP access and 3GPP access interworking scenarios while both accesses connected to 5GC.
Up

4.2  Architectural Assumptions  p. 13

As a basis for the underlying architectural further development work on commercial LCS in 5GC the following assumptions for enhancements to the 5GC to support commercial apply:
  • Positioning methods may be Access Network specific, although commonalties should be encouraged between Access Networks;
  • The location services in the Access Network is optional through support of the specified method(s);
  • The service based architecture defined in clause 4.4.4 of TS 23.501 shall be used as a starting point for this study.
  • The POI requirements and procedures of TS 23.271 pertaining to emergency services and lawful interception shall be followed.
  • Compatibility with the location solution for regulatory services defined in TS 23.501 shall be supported with the following aspects:
  • Ability to coexist in the same PLMN with location solution for regulatory services defined in TS 23.501.
  • Ability to reuse existing positioning procedures and signalling for the N1 interface defined in TS 23.502;
  • Minimize new impacts to the N2 interface and existing 5GC NFs.
Up

Up   Top   ToC