TS 23.273 — 5G System (5GS) Location Services (LCS); Stage 2⚓︎
Release: Rel 17 · Version assessed: 17.11.0 · Network: · Applies to: AMF
Optional capability, configured on request
The network function software implements this specification, and the statement below records that implementation. An Expeto deployment does not configure this capability by default and the acceptance test catalog does not cover it. If your deployment needs any part of it, contact Expeto Product Support: enabling it is configuration work that Expeto scopes and carries out with you.
Mandatory items: 34, of which 15 supported, 4 partially supported and 15 not supported. A further 58 clauses of the specification carry no conformance requirement and are not listed.
Mandatory items⚓︎
| Ref. | Item | Status | Support | Remarks |
|---|---|---|---|---|
| 4.1 | General Concepts | Mandatory | Partial | Location Service through 3GPP access network over NR only. Location Service in SNPN, in the EPC interworking scenario, Roaming are not supported |
| 4.1a.1 | Network Induced Location Request (NI-LR) | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 4.1a.2 | Mobile Terminated Location Request (MT-LR) | Mandatory | Supported | |
| 4.1a.3 | Mobile Originated Location Request (MO-LR) | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 4.1a.4 | Immediate Location Request | Mandatory | Supported | |
| 4.1a.5 | Deferred Location Request | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 4.2.1 | Non-roaming reference architecture | Mandatory | Supported | |
| 4.2a.2 | Non-roaming architecture | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 4.3.1 | Access Network | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 4.3.2 | LCS Clients, Application Functions and Network Functions | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 4.3.3 | Gateway Mobile Location Centre, GMLC | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 4.3.5 | UE | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 4.3.6 | UDM | Mandatory | Supported | |
| 4.3.7 | Access and Mobility Management Function, AMF | Mandatory | Supported | |
| 4.3.8 | Location Management Function, LMF | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 4.3.10 | Unified Data Repository, UDR | Mandatory | Supported | |
| 4.4.3 | N1 Reference Point | Mandatory | Supported | Transfer of ciphering keys from an AMF absent |
| 4.4.4 | N2 Reference Point | Mandatory | Supported | |
| 4.4.7 | NL2 Reference Point | Mandatory | Supported | |
| 4.4.8 | NL6 Reference Point | Mandatory | Supported | |
| 4.4.10 | NL1 Reference Point | Mandatory | Supported | |
| 4.5 | Service Based Interfaces to Support Location Services | Mandatory | Supported | |
| 5.4.1 | General | Mandatory | Partial | Location Privacy Indication supported in LCS privacy profile data. This clause is applicable for all sections mentioning LCS privacy profile data |
| 6.1.1 | 5GC-MT-LR procedure for the regulatory location service | Mandatory | Supported | |
| 6.1.2 | 5GC-MT-LR Procedure for the commercial location service | Mandatory | Partial | ParameterProvision update procedure not supported. Service Authorization type Location allowed without notification supported (NAS interface towards UE not implemented in case of MT-Commercial LCS Procedure type) |
| 6.2 | 5GC-MO-LR Procedure | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 6.3.1 | Initiation and Reporting of Location Events | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 6.3.2 | Cancellation of Reporting of Location Events by a UE | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 6.3.3 | Cancellation of Reporting of Location Events by an AF or External LCS Client or GMLC | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 7.1 | UDM | Mandatory | Supported | |
| 7.2 | GMLC | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 7.2.1 | Information for an LCS Client | Mandatory | Not supported | Not implemented; the AMF offers the 5GC-MT-LR procedure through Namf_Location only, and the network function does not include a GMLC or LMF. |
| 8.1 | AMF Services | Mandatory | Supported | |
| 8.2 | UDM Services | Mandatory | Partial | Location Privacy Indication supported in LCS privacy profile data |
Optional items⚓︎
The specification leaves these 59 items to the implementation; 12 are supported or partially supported. An item marked Not applicable belongs to an area the platform does not provide, named in the Support column. Expand for the full list.
59 optional items
| Ref. | Item | Support | Remarks |
|---|---|---|---|
| 4.1a.5.1 | Types of event | Not supported | |
| 4.1b | LCS Quality of Service | Supported | LCS QoS is passed transparently to the LMF. |
| 4.1c | Scheduled Location Time | Not supported | |
| 4.2.2 | Roaming reference architecture | Not supported | |
| 4.2a.1 | General | Not supported | |
| 4.2a.3 | Roaming architecture | Not supported | |
| 4.3.4 | Location Retrieval Function, LRF | Not supported | |
| 4.3.9 | Network Exposure Function, NEF | Not supported | |
| 4.4.9 | N51 Reference Point | Not supported | |
| 4.4.11 | N52 Reference Point | Not supported | |
| 5.1 | LMF Selection | Not supported | |
| 5.1a | GMLC Discovery and Selection | Not supported | |
| 5.2 | 3GPP access specific aspects | Supported | |
| 5.3 | Non-3GPP Access Specific Aspects | Not supported | |
| 5.3.1 | Location Information for Non-3GPP Access | Not supported | |
| 5.3.2 | Access Type Selection for LCS Service | Partial | Location Service through 3GPP access network |
| 5.4 | UE LCS privacy | Partial | update of the UE privacy profile to UDM/UDR absent |
| 5.4.2.1 | General | Partial | Assessed per sub-clause. |
| 5.4.2.2.1 | Universal Class | Not supported | |
| 5.4.2.2.2 | Call/Session related Class | Not supported | |
| 5.4.2.2.3 | Call/Session unrelated Class | Not supported | |
| 5.4.2.2.4 | PLMN Operator Class | Not supported | |
| 5.4.2.3 | Location Privacy Indication (LPI) | Supported | |
| 5.4.3 | Provision of UE LCS privacy profile | Not supported | |
| 5.4.4 | Privacy Override Indicator (POI) | Not supported | |
| 5.4.5 | LCS service authorization for an Immediate UE Location | Partial | Location allowed without notification supported |
| 5.4.6 | LCS service authorization for a Deferred UE Location | Not supported | |
| 5.5 | Location service exposure | Not supported | |
| 5.6 | LCS Charging | Not supported | |
| 5.7 | Support of Concurrent Location Requests | Not supported | |
| 5.8 | Interworking with the IMS | Not supported | |
| 6.4 | LMF Change Procedure | Not supported | |
| 6.5.1 | Unified Location Service Exposure Procedure without routing by a UDM | Not supported | Not implemented; only the 5GC-MT-LR procedure through Namf_Location is offered. |
| 6.5.2 | Unified Location Service Exposure Procedure with routing via a UDM | Not supported | Not implemented; only the 5GC-MT-LR procedure through Namf_Location is offered. |
| 6.7.1 | Event Reporting with no change of LMF | Not supported | Not implemented; only the 5GC-MT-LR procedure through Namf_Location is offered. |
| 6.7.2 | Event Reporting with change of LMF | Not supported | Not implemented; only the 5GC-MT-LR procedure through Namf_Location is offered. |
| 6.7.3 | Event Reporting in RRC INACTIVE state for DL Positioning, RAT Independent Positioning or No Positioning | Not supported | Not implemented; only the 5GC-MT-LR procedure through Namf_Location is offered. |
| 6.7.4 | Event Reporting in RRC INACTIVE state for UL Positioning | Not supported | Not implemented; only the 5GC-MT-LR procedure through Namf_Location is offered. |
| 6.7.5 | Event Reporting in RRC INACTIVE state for UL+DL Positioning | Not supported | Not implemented; only the 5GC-MT-LR procedure through Namf_Location is offered. |
| 6.8 | Bulk Operation of LCS Service Request Targeting to Multiple UEs | Not supported | |
| 6.9.1 | Common Positioning Procedures when a UE is served by only one PLMN | Not supported | Not implemented; only the 5GC-MT-LR procedure through Namf_Location is offered. |
| 6.9.2 | MT-LR Procedures when a UE is served by Different PLMNs for 3GPP Access and Non-3GPP Access | Not supported | Not implemented; only the 5GC-MT-LR procedure through Namf_Location is offered. |
| 6.9.3 | MO-LR Procedures when UE is served by the Different PLMNs via 3GPP Access and Non-3GPP Access | Not supported | Not implemented; only the 5GC-MT-LR procedure through Namf_Location is offered. |
| 6.9.4 | NI-LR Procedures when a UE is served by Different PLMNs for 3GPP access and non-3GPP access | Not supported | Not implemented; only the 5GC-MT-LR procedure through Namf_Location is offered. |
| 6.10.1 | 5GC-NI-LR Procedure | Not supported | |
| 6.10.2 | 5GC-MT-LR Procedure without UDM Query | Not supported | |
| 6.10.3 | Location continuity for Handover of an Emergency session from NG-RAN | Not supported | |
| 6.11.1 | UE Assisted and UE Based Positioning Procedure | Not supported | |
| 6.11.2 | Network Assisted Positioning Procedure | Supported | |
| 6.11.3 | Obtaining Non-UE Associated Network Assistance Data | Supported | |
| 6.12.1 | UE Location Privacy Setting Procedure Initiated by UE | Not supported | |
| 6.12.2 | UE Location Privacy Setting Procedure Initiated by AF | Not supported | |
| 6.13.1 | MT-LR Procedure | Not supported | |
| 6.13.2 | MO-LR Transfer to a Third Party Procedure | Not supported | |
| 6.14 | Procedures for Broadcast of Assistance Data | Partial | Non-ciphered network assistance data supported |
| 6.14.1 | Broadcast of Assistance Data by an LMF | Supported | |
| 6.14.2 | Delivery of Ciphering Keys to UEs for Broadcast Assistance Data | Not supported | |
| 8.5 | NEF Services | Not supported | |
| 8.6 | UDR Services | Partial | Location Privacy Indication supported |
Assessed 2026-09-15 against TS 23.273 version 17.11.0.