5.3 LCS message and coding
24.5713GPP5G System (5GS)Control plane Location Services (LCS) proceduresRelease 17Stage 3TS
5.3.1 Messages for Location services operations
The LCS message format and information elements coding for the MO-LR, LocationNotification, EventReport, PeriodicTriggeredInvoke, CancelDeferredLocation and LocationPrivacySetting operations (clause 5.2) are defined in 3GPP TS 24.080 [5] for the following messages:
– Register message
– Facility message
– Release Complete message
5.3.2 Messages for LTE Positioning Protocol (LPP)
5.3.2.1 Downlink Positioning Information Transport using LPP messages
The AMF shall set the Payload container type to "LPP message container" in the DL NAS TRANSPORT message.
The AMF includes a Routing identifier in the Additional information IE of the DL NAS TRANSPORT message which identifies the LMF and the positioning session between the AMF and LMF when a positioning session is being used.
The Routing identifier is the Correlation ID, which is defined in 3GPP TS 29.572 [6], so that the AMF can map the Routing identifier to the LMF and the Correlation identifier when the AMF receives a UL NAS TRANSPORT message including the responding LPP message.
5.3.2.2 Uplink Positioning Information Transport using LPP messages
The UE shall set the Payload container type to "LPP message container" in the UL NAS TRANSPORT message.
The UE includes a Routing identifier received in the Additional Information IE of the DL NAS TRANSPORT message in the Additional Information IE of the UL NAS TRANSPORT message. This association of the Routing Identifier is provided at the LPP level: the UL NAS TRANSPORT message carries an LPP message that is a response to or instigated by the LPP message in the DL NAS TRANSPORT message. The Routing identifier is the Correlation ID, which is defined in 3GPP TS 29.572 [6], so that the AMF can map the Routing identifier to the Correlation identifier when the AMF receives the UL NAS TRANSPORT message.
Annex A (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2019-08 |
CT1#119 |
Draft skeleton provided by the rapporteur |
0.0.0 |
||||
|
2019-10 |
CT1#120 |
Includes the following contribution agreed by CT1 at CT1#120:C1-196563 |
0.1.0 |
||||
|
2019-11 |
CT1#121 |
Includes the following contributions agreed by CT1 at CT1#121:C1-198290, C1-198720 |
0.2.0 |
||||
|
2019-12 |
CT#86 |
CP-193155 |
Presentation for information to TSG CT |
1.0.0 |
|||
|
2020-03 |
CT#87e |
CP-200287 |
Implementation of pCRs CP-200102 and 103 approved by TSG CT. |
2.0.0 |
|||
|
2020-03 |
CT#87e |
Version 16.0.0 created after approval |
16.0.0 |
||||
|
2020-03 |
CT#87e |
Editorial corrections |
16.0.1 |
||||
|
2020-06 |
CT#88e |
CP-201098 |
0001 |
B |
Adding Location Privacy Setting operation |
16.1.0 |
|
|
2020-09 |
CT#89e |
CP-202148 |
0002 |
3 |
B |
UE initiated Event Reporting Procedure for Low Power Event Reporting |
16.2.0 |
|
2020-09 |
CT#89e |
CP-202148 |
0003 |
F |
Additional function of MO-LR procedure |
16.2.0 |
|
|
2021-12 |
CT#84e |
CP-213031 |
0004 |
1 |
F |
TS reference update and multiplePositioningProtocolPDUs limit clarification |
17.0.0 |
|
2022-03 |
CT#95e |
CP-220243 |
0006 |
1 |
B |
AMF LCS functionality for satellite access |
17.1.0 |
|
2022-03 |
CT#95e |
CP-220243 |
0008 |
1 |
F |
Clarification on multiplePositioningProtocolPDUs IE |
17.1.0 |
|
2022-03 |
CT#95e |
CP-220243 |
0009 |
4 |
F |
Clarification on the LMF ID |
17.1.0 |
|
2022-03 |
CT#95e |
CP-220243 |
0010 |
1 |
F |
Clarification on Routing information |
17.1.0 |
|
2022-06 |
CT#96 |
CP-221207 |
0011 |
1 |
F |
The Location Service partially applicable for SNPN |
17.2.0 |
|
2022-06 |
CT#96 |
CP-221207 |
0012 |
1 |
B |
Additional of Scheduled Location Time |
17.2.0 |
|
2022-06 |
CT#96 |
CP-221207 |
0013 |
1 |
F |
Handling of Scheduled Location Time by UE |
17.2.0 |
|
2022-12 |
CT#98e |
CP-223115 |
0014 |
1 |
F |
Correction on country verification for satellite access |
17.3.0 |