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  TS 24.572  Word version:  18.1.1

Top   Top   None   None   Next
1…   6…   10… 
1 Scope  2 References  3 Definitions and abbreviations  3.1 Definitions  3.2 Abbreviations  4 General  4.1 Overview  4.2 LCS-UP positioning management  4.3 Security  5 Co-existence of user plane location solutions  5.1 General  5.2 User plane location solution selection 
...

 

1  Scope  p. 8

The present document specifies the LCS user plane protocol (LCS-UPP) to support the Location Services in the 5G System (5GS) as specified in TS 23.273 for user plane positioning between the UE and the LMF.
The present document also specifies the user plane positioning connection management (UPP-CM) protocol to support the LCS secured user plane connection between the UE and the LMF.
The present document also specifies the LCS user plane protocol (LCS-UPP) to support location event reporting over an LCS secured user plane connection between the UE and the LCS client or the AF.
The present document also defines the message format, message contents, error handling and system parameters applied by the LCS-UPP and the UPP-CM protocol for supporting Location Services in 5GS.
Up

2  References  p. 8

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.273: "5G System (5GS) Location Services (LCS); Stage 2".
[3]
TS 24.571: "5G System (5GS) Control plane Location Services (LCS) procedures; Stage 3".
[4]
TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[5]
TS 23.271: "Functional stage 2 description of Location Services (LCS)".
[6]
TS 38.305: "Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN".
[7]
TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[8]
TS 33.501: "Security architecture and procedures for 5G System".
[9]
TS 24.526: "UE policies for 5G System (5GS); Stage 3".
[10]
TS 23.003: "Numbering, addressing and identification".
[11]
TS 24.080: "Mobile radio interface layer 3 supplementary services specification; Formats and coding".
[12]
TS 23.501: "System Architecture for the 5G System; Stage 2".
[13]
TS 37.355: "Technical Specification Group Radio Access Network; LTE Positioning Protocol (LPP)".
[14]
TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols; Stage 3".
Up

3  Definitions and abbreviations  p. 9

3.1  Definitions  p. 9

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.
LCS secured user plane connection:
A connection used for LCS signaling message transport via user plane between the UE and the LMF. The LCS secured user plane connection is achieved by a TLS connection between the UE and the LMF established over PDU connectivity service provided by a PDU session, and a successful binding procedure performed via the TLS connection.
User plane connection information:
The information provided by LMF during the network initiated user plane connection establishment procedure.
LCS-UP binding ID:
An identity allocated by the LMF and used to associate the UE with the LCS secured user plane connection between the UE and the LMF.
For the purposes of the present document, the following terms and definitions given in TS 23.501 apply:
PDU connectivity service
PDU session
PDU session type
Up

3.2  Abbreviations  p. 9

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.
FQDN
Fully Qualified Domain Name
LCS
LoCation Service
LCS-UP
Location Services User Plane
LCS-UPP
Location Services User Plane Protocol
LMF
Location Management Function
LPP
LTE Positioning Protocol
OMA
Open Mobile Alliance
SUPL
Secure User Plane Location
TLS
Transport Layer Security
UPP-CM
User Plane Positioning Connection Management
UPP-CMI
User Plane Positioning Connection Management Information
Up

4  General  p. 9

4.1  Overview  p. 9

The user plane location services protocols described in the present document provide signalling connectivity between UE and LMF, LCS client or AF, for 5GS.
Main functions of user plane LCS protocols are:
  • support of management of an LCS secured user plane connection for user plane positioning; and
  • user plane transport procedures to provide a transport of LPP messages and location supplementary services messages.
For the support of the above functions, the following procedures are supplied within this specification:
  • elementary procedures for UPP-CM, in clause 6; and
  • elementary procedures for LCS-UPP, in clause 7.
Security, including ciphering and integrity protection, is provided by lower layers from a user plane location services protocol perspective (see TS 24.501 for UPP-CM and clause 4.3 for LCS-UPP).
Co-existence of user plane location solutions is described in clause 5.
The UPP-CM and LCS-UPP for 5GS follow the protocol architecture model for layer 3 as described in TS 24.007.
Up

4.2  LCS-UP positioning management  p. 10

4.2.1  General  p. 10

In order to ensure the transfer of location supplementary services messages and LPP messages via the user plane, the UE and the LMF shall perform the LCS user plane positioning management including:
  1. PDU session management (see subclause 4.2.2);
  2. user plane positioning connection management (see subclause 4.2.3).

4.2.2  PDU session management  p. 10

A PDU session for the user plane positioning between the UE and the network is a prerequisite for an LCS secured user plane connection between the UE and the LMF for LCS-UPP.
The HPLMN may provide the UE with the URSP rules for the user plane positioning as defined in TS 24.526. The UE supporting the user plane positioning can use an established PDU session or establish a PDU session for the user plane positioning based on URSP rules. The URSP rules for the user plane positioning include:
  1. the traffic descriptor containing the connection capability for user plane positioning; and
  2. the route selection descriptor containing a DNN and an S-NSSAI for the user plane positioning.
During the UE requested user plane connection establishment procedure or the network initiated user plane connection establishment procedure, if there is no established PDU session for the user plane positioning, the UE shall initiate a UE-requested PDU session establishment procedure as specified in TS 24.501 to establish a new PDU session with a DNN and an S-NSSAI used for the user plane positioning.
If the PDU session for the user plane positioning is released as specified in clause 6.3.3 and clause 6.4.3 of TS 24.501, the UE may initiate the UE requested user plane connection release procedure as specified in clause 6.2.2.2.
Up

4.2.3  User plane positioning connection management  p. 10

The user plane positioning connection management is to support the establishment and release of the LCS secured user plane connection between the UE and the LMF.
To trigger the UE to establish or re-establish an LCS secured user plane connection between the UE and the LMF, the LMF shall provide the user plane connection information to the UE. The UE can also send the USER PLANE CONNECTION ESTABLISHMENT REQUEST message to the LMF to obtain the user plane connection information. The user plane connection information includes an address of the LMF and an LCS-UP binding ID. The LMF shall allocate the LCS-UP binding ID in order to associate the UE with the LCS secured user plane connection. The UE shall use the LCS-UP binding ID during the LCS-UP connection binding procedure to request binding the LCS secured user plane connection to the UE.
The LMF may monitor the LCS secured user plane connection by running an implementation specific inactivity timer, upon expiry of the implementation specific inactivity timer, the LMF shall initiate the network initiated user plane connection release procedure as specified in clause 6.2.1.2.
Up

4.3  Security  p. 11

An LCS secured user plane connection between the UE and the LMF for LCS-UPP is protected using a TLS based mechanism as described in TS 33.501 Annex Q.2.

5  Co-existence of user plane location solutions  p. 11

5.1  General  p. 11

The user plane location solution as described in the present specification, i.e. LCS-UPP, may co-exist with other user plane location solutions such as OMA SUPL. The use of OMA SUPL in a 3GPP network is described in TS 38.305 and TS 23.271.
For UEs supporting another user plane location solution in addition to LCS-UPP, the following indications and parameters can be used to control which user plane location solution is used for such UEs:
  1. LCS-UPP bit in NAS 5GMM capability IE (see TS 24.501);
  2. SUPL bit in NAS 5GMM capability IE (see TS 24.501);
  3. LCS-UPP bit in NAS 5GS network feature support IE (see TS 24.501); and
  4. SUPL bit in NAS 5GS network feature support IE (see TS 24.501).
Up

5.2  User plane location solution selection  p. 11

UEs supporting one or more user plane location solution(s) shall indicate its supported user plane location solution(s) to the network using the LCS-UPP bit, the SUPL bit or both in the 5GMM capability IE during the initial registration procedure and the mobility registration update procedure as described in TS 24.501.
If the UE supports LCS-UPP, SUPL or both, the network shall indicate support of user plane location solution(s) to the UE using LCS-UPP bit, the SUPL bit or both in the 5GS network feature support IE during the initial registration procedure and the mobility registration update procedure as described in TS 24.501. The user plane location solution(s) indicated as supported by the network to the UE is selected based on network supported solutions, UE supported solutions and operator policy.
After the UE receives the indication of the supported user plane location solution(s) by the network, and when needed, a user plane location solution supported by both the UE and the network can be initiated and used.
Up

Up   Top   ToC