ETSI TS 124 572 V19.6.0 (2026-03)

5G; 5G System (5GS); User plane Location Services (LCS) protocols and procedures; Stage 3 (3GPP TS 24.572 version 19.6.0 Release 19)

RTS/TSGC-0124572vj60

General Information

• Status: Not Published
• Technical Committee: 3GPP CT 1 - MM/CC/SM [lu] (formely CN1)
• Current Stage: 8 - Draft receipt by ETSI Secretariat
• Completion Date: 10-Mar-2026

Standards Content (Sample)

TECHNICAL SPECIFICATION
5G;
5G System (5GS);
User plane Location Services (LCS) protocols and procedures;
Stage 3
(3GPP TS 24.572 version 19.6.0 Release 19)

3GPP TS 24.572 version 19.6.0 Release 19 1 ETSI TS 124 572 V19.6.0 (2026-03)

Reference
RTS/TSGC-0124572vj60
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2026.
All rights reserved.
ETSI
3GPP TS 24.572 version 19.6.0 Release 19 2 ETSI TS 124 572 V19.6.0 (2026-03)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found at 3GPP to ETSI numbering cross-referencing.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 24.572 version 19.6.0 Release 19 3 ETSI TS 124 572 V19.6.0 (2026-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 8
2 References . 8
3 Definitions and abbreviations . 9
3.1 Definitions . 9
3.2 Abbreviations . 9
4 General . 9
4.1 Overview . 9
4.2 LCS-UP positioning management . 10
4.2.1 General . 10
4.2.2 PDU session management . 10
4.2.3 User plane positioning connection management . 10
4.3 Security . 11
5 Co-existence of user plane location solutions . 11
5.1 General . 11
5.2 User plane location solution selection . 11
6 Elementary procedures for UPP-CM. 11
6.1 Overview . 11
6.1.1 General . 11
6.1.2 Types of UPP-CM procedures . 12
6.2 UPP-CM procedures. 12
6.2.1 Network initiated UPP-CM procedures . 12
6.2.1.1 Network initiated user plane connection establishment procedure . 12
6.2.1.1.1 General . 12
6.2.1.1.2 Network initiated user plane connection establishment procedure initiation by the network . 13
6.2.1.1.3 Network initiated user plane connection establishment procedure accepted by the UE . 14
6.2.1.1.4 Network initiated user plane connection establishment procedure completion by the network . 15
6.2.1.1.5 Network initiated user plane connection establishment procedure not accepted by the UE . 15
6.2.1.1.6 Abnormal cases on the network side . 16
6.2.1.1.7 Abnormal cases in the UE . 16
6.2.1.2 Network initiated user plane connection release procedure . 16
6.2.1.2.1 General . 16
6.2.1.2.2 Network initiated user plane connection release procedure initiation by LMF . 17
6.2.1.2.3 Network initiated user plane connection release procedure accepted by UE . 18
6.2.1.2.4 Abnormal cases on the network side . 18
6.2.1.3 Network initiated user plane connection modification procedure . 19
6.2.1.3.1 General . 19
6.2.1.3.2 Network initiated user plane connection modification procedure initiation by LMF . 20
6.2.1.3.3 Network initiated user plane connection modification procedure accepted by UE . 20
6.2.1.3.4 Network initiated user plane connection modification procedure not accepted by UE . 21
6.2.1.3.5 Abnormal cases on the network side . 21
6.2.2 UE initiated UPP-CM procedures . 21
6.2.2.1 UE requested user plane connection establishment procedure . 21
6.2.2.1.1 General . 21
6.2.2.1.2 UE requested user plane connection establishment procedure initiation . 22
6.2.2.1.3 UE requested user plane connection establishment procedure accepted by the network . 23
6.2.2.1.4 UE requested user plane connection establishment procedure not accepted by the network . 23
6.2.2.1.5 Void . 23
6.2.2.1.6 Abnormal cases in the UE . 23
ETSI
3GPP TS 24.572 version 19.6.0 Release 19 4 ETSI TS 124 572 V19.6.0 (2026-03)
6.2.2.1.7 Abnormal cases on the network side . 24
6.2.2.2 UE requested user plane connection release procedure. 24
6.2.2.2.1 General . 24
6.2.2.2.2 UE requested user plane connection release procedure initiation by the UE. 24
6.2.2.2.3 UE requested user plane connection release procedure accepted by the LMF . 25
6.2.2.2.4 Abnormal cases in the UE . 25
7 Elementary procedures for LCS-UPP . 26
7.1 Overview . 26
7.2 LCS-UPP message transport . 26
7.2.1 LCS-UPP message transport in IPv4, IPv6 or IPv4v6 PDU session. 26
7.3 LCS-UPP procedures . 26
7.3.1 General . 26
7.3.2 Uplink LCS-UP transport procedure. 27
7.3.2.1 General . 27
7.3.2.2 Uplink LCS-UP transport procedure initiation by the UE . 27
7.3.2.3 Uplink LCS-UP transport procedure accepted by the LMF . 27
7.3.2.4 Abnormal cases in the UE . 28
7.3.3 Downlink LCS-UP transport procedure . 28
7.3.3.1 General . 28
7.3.3.2 Downlink LCS-UP transport procedure initiation by the LMF . 28
7.3.3.3 Downlink LCS-UP transport of messages accepted by the UE . 29
7.3.3.4 Abnormal cases on the network side . 29
7.3.4 LCS-UP connection binding procedure . 29
7.3.4.1 General . 29
7.3.4.2 LCS-UP connection binding procedure initiation by the UE . 29
7.3.4.3 LCS-UP connection binding procedure accepted by the LMF . 30
7.3.4.4 LCS-UP connection binding procedure completion by the UE . 30
7.3.4.5 LCS-UP connection binding procedure not accepted by the network . 30
7.3.4.6 Abnormal cases in the UE . 30
7.3.4.7 Abnormal cases on the network side . 31
8 LCS-UPP procedures for LCS client or AF . 31
9 Handling of unknown, unforeseen and erroneous protocol data . 31
9.1 General . 31
9.2 Message too short or too long . 32
9.2.1 Message too short . 32
9.2.2 Message too long . 32
9.3 Unknown or unforeseen message type . 32
9.4 Non-semantical mandatory information element errors . 32
9.5 Unknown and unforeseen IEs in the non-imperative message part . 33
9.5.1 IEIs unknown in the message . 33
9.5.2 Out of sequence IEs . 33
9.5.3 Repeated IEs . 33
9.6 Non-imperative message part errors . 33
9.6.1 General . 33
9.6.2 Syntactically incorrect optional IEs . 33
9.6.3 Conditional IE errors . 34
9.7 Messages with semantically incorrect contents . 34
10 Message functional definitions and contents . 34
10.1 Overview . 34
10.2 LCS-UPP messages . 35
10.2.1 UL LCS-UP transport . 35
10.2.1.1 Message definition . 35
10.2.2 DL LCS-UP transport . 36
10.2.2.1 Message definition . 36
10.2.3 LCS-UP connection binding request . 36
10.2.3.1 Message definition . 36
10.2.4 LCS-UP connection binding accept . 36
10.2.4.1 Message definition . 36
10.2.5 LCS-UP connection binding reject . 37
ETSI
3GPP TS 24.572 version 19.6.0 Release 19 5 ETSI TS 124 572 V19.6.0 (2026-03)
10.2.5.1 Message definition . 37
10.3 UPP-CM messages . 37
10.3.1 User plane connection establishment command . 37
10.3.1.1 Message definition . 37
10.3.1.2 Source LMF routing information . 38
10.3.2 User plane connection establishment complete . 38
10.3.2.1 Message definition . 38
10.3.3 User plane connection establishment failure . 38
10.3.3.1 Message definition . 38
10.3.4 User plane connection establishment request . 38
10.3.4.1 Message definition . 38
10.3.5 User plane connection establishment reject . 39
10.3.5.1 Message definition . 39
10.3.5.2 Back-off timer value . 39
10.3.6 User plane connection release command . 39
10.3.6.1 Message definition . 39
10.3.6.2 Back-off timer value . 40
10.3.7 User plane connection release complete . 40
10.3.7.1 Message definition . 40
10.3.8 User plane connection release request . 40
10.3.8.1 Message definition . 40
10.3.8.2 Failure cause . 40
10.3.9 User plane connection modification command . 40
10.3.9.1 Message definition . 40
10.3.9.2 Source LMF routing information . 41
10.3.10 User plane connection modification complete . 41
10.3.10.1 Message definition . 41
10.3.11 User plane connection modification reject . 41
10.3.11.1 Message definition . 41
11 Information elements coding . 42
11.1 Overview . 42
11.1.1 UPP-CM and LCS-UPP message format . 42
11.1.2 Field format and mapping . 42
11.1.3 Message type . 43
11.2 LCS-UPP information elements . 43
11.2.1 LCS-UP payload . 43
11.2.2 LCS-UP payload type . 45
11.2.3 LCS session identity . 45
11.3 UPP-CM information elements . 46
11.3.1 LMF LCS-UP address . 46
11.3.2 GPRS timer 3 . 46
11.3.3 Failure cause . 46
11.3.4 LCS-UP binding ID . 47
11.3.5 LMF routing information . 47
11.4 Spare half octet . 48
12 List of system parameters . 48
12.1 General . 48
12.2 Timers of LCS-UPP . 48
12.3 Timers of UPP-CM . 48
Annex A (informative): Network initiated user plane connection establishment procedure with the
LCS-UP connection binding procedure call flow . 50
Annex B (informative): Change history . 51
History . 55

ETSI
3GPP TS 24.572 version 19.6.0 Release 19 6 ETSI TS 124 572 V19.6.0 (2026-03)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
In the present document, modal verbs have the following meanings:
shall indicates a mandatory requirement to do something
shall not indicates an interdiction (prohibition) to do something
The constructions "shall" and "shall not" are confined to the context of normative provisions, and do not appear in
Technical Reports.
The constructions "must" and "must not" are not used as substitutes for "shall" and "shall not". Their use is avoided
insofar as possible, and they are not used in a normative context except in a direct citation from an external, referenced,
non-3GPP document, or so as to maintain continuity of style when extending or modifying the provisions of such a
referenced document.
should indicates a recommendation to do something
should not indicates a recommendation not to do something
may indicates permission to do something
need not indicates permission not to do something
The construction "may not" is ambiguous and is not used in normative elements. The unambiguous constructions
"might not" or "shall not" are used instead, depending upon the meaning intended.
can indicates that something is possible
cannot indicates that something is impossible
The constructions "can" and "cannot" are not substitutes for "may" and "need not".
will indicates that something is certain or expected to happen as a result of action taken by an agency
the behaviour of which is outside the scope of the present document
will not indicates that something is certain or expected not to happen as a result of action taken by an
agency the behaviour of which is outside the scope of the present document
might indicates a likelihood that something will happen as a result of action taken by some agency the
behaviour of which is outside the scope of the present document
ETSI
3GPP TS 24.572 version 19.6.0 Release 19 7 ETSI TS 124 572 V19.6.0 (2026-03)
might not indicates a likelihood that something will not happen as a result of action taken by some agency
the behaviour of which is outside the scope of the present document
In addition:
is (or any other verb in the indicative mood) indicates a statement of fact
is not (or any other negative verb in the indicative mood) indicates a statement of fact
The constructions "is" and "is not" do not indicate requirements.
ETSI
3GPP TS 24.572 version 19.6.0 Release 19 8 ETSI TS 124 572 V19.6.0 (2026-03)
1 Scope
The present document specifies the LCS user plane protocol (LCS-UPP) to support the Location Services in the 5G
System (5GS) as specified in 3GPP TS 23.273 [2] 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.
2 References
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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
[3] 3GPP TS 24.571: "5G System (5GS) Control plane Location Services (LCS) procedures; Stage 3".
[4] 3GPP TS 24.501: "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[5] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)".
[6] 3GPP TS 38.305: "Stage 2 functional specification of User Equipment (UE) positioning in NG-
RAN".
[7] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[8] 3GPP TS 33.501: "Security architecture and procedures for 5G System".
[9] 3GPP TS 24.526: "UE policies for 5G System (5GS); Stage 3".
[10] 3GPP TS 23.003: "Numbering, addressing and identification".
[11] 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification; Formats
and coding".
[12] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[13] 3GPP TS 37.355: "Technical Specification Group Radio Access Network; LTE Positioning
Protocol (LPP)".
[14] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols;
Stage 3".
[15] 3GPP TS 29.641: "Technical Specification Group Core Network and Terminals; 3GPP registry for
Service Names and Port Numbers".
[16] 3GPP TS 29.572: "5G System; Location Management Services; Stage 3".
ETSI
3GPP TS 24.572 version 19.6.0 Release 19 9 ETSI TS 124 572 V19.6.0 (2026-03)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term
defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
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 3GPP TS 23.501 [12] apply:
PDU connectivity service
PDU session
PDU session type
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An
abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in
3GPP TR 21.905 [1].
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
4 General
4.1 Overview
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 transport of LPP messages and LCS 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
ETSI
3GPP TS 24.572 version 19.6.0 Release 19 10 ETSI TS 124 572 V19.6.0 (2026-03)
- 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 3GPP TS 24.501 [4] for UPP-CM and clause 4.3 for LCS-UPP).
The 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
3GPP TS 24.007 [7].
4.2 LCS-UP positioning management
4.2.1 General
In order to ensure the transfer of LCS supplementary services messages and LPP messages via the user plane, the UE
and the LMF shall perform the LCS user plane positioning management including:
a) PDU session management (see clause 4.2.2);
b) user plane positioning connection management (see clause 4.2.3).
4.2.2 PDU session management
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 3GPP TS 24.526 [9].
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:
a) the traffic descriptor containing the connection capability for user plane positioning; and
b) 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 3GPP TS 24.501 [4] to establish a new PDU session
with a DNN and an S-NSSAI used for the user plane positioning.
NOTE: The appropriate QoS parameters of the PDU session for the user plane positioning are up to the operator's
determination.
If the PDU session for the user plane positioning is released as specified in clause 6.3.3 and clause 6.4.3 of
3GPP TS 24.501 [4], the UE may initiate the UE requested user plane connection release procedure as specified in
clause 6.2.2.2.
4.2.3 User plane positioning connection management
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 TCP port number 65402 is used as destination TCP port number in establishment of TCP connection for the TLS
connection for the LCS secured user plane connection as specified in 3GPP TS 29.641 [15].
ETSI
3GPP TS 24.572 version 19.6.0 Release 19 11 ETSI TS 124 572 V19.6.0 (2026-03)
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.
NOTE: In this release of specification, one or more LCS secured user plane connections are allowed for a UE and
a maximum of one LCS secured user plane connection is allowed towards each LMF as specified in
clause 6.18 of 3GPP TS 23.273 [2].
4.3 Security
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 3GPP TS 33.501 [8] Annex Q.2.
5 Co-existence of user plane location solutions
5.1 General
The user plane location solution a
...