ETSI TS 122 071 V15.1.0 (2020-03)

Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; 5G; Location Services (LCS); Service description; Stage 1 (3GPP TS 22.071 version 15.1.0 Release 15)

RTS/TSGS-0122071vf10

General Information

• Status: Published
• Publication Date: 30-Mar-2020
• Technical Committee: 3GPP SA 1 - Services
• Current Stage: 12 - Completion
• Completion Date: 31-Mar-2020

Standards Content (Sample)

TECHNICAL SPECIFICATION
Digital cellular telecommunications system (Phase 2+) (GSM);
Universal Mobile Telecommunications System (UMTS);
LTE;
5G;
Location Services (LCS);
Service description;
Stage 1
(3GPP TS 22.071 version 15.1.0 Release 15)

3GPP TS 22.071 version 15.1.0 Release 15 1 ETSI TS 122 071 V15.1.0 (2020-03)

Reference
RTS/TSGS-0122071vf10
Keywords
5G,GSM,LTE,UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
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 at www.etsi.org/deliver.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
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 2020.
All rights reserved.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.

3GPP™ and LTE™ 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.
ETSI
3GPP TS 22.071 version 15.1.0 Release 15 2 ETSI TS 122 071 V15.1.0 (2020-03)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is 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 Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, 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.
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 under http://webapp.etsi.org/key/queryform.asp.
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 22.071 version 15.1.0 Release 15 3 ETSI TS 122 071 V15.1.0 (2020-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2. References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definitions and abbreviations . 8
3.1 Abbreviations . 8
3.2 Definitions . 8
4 Functional Requirements . 10
4.0 General . 10
4.1 High Level Requirements . 10
4.2 Location Information . 12
4.2.1 Geographic Location. 12
4.2.2 Velocity . 12
4.2.3 Dispatchable Location . 12
4.3 Quality of Service . 12
4.3.1 Horizontal Accuracy . 12
4.3.2 Vertical Accuracy . 14
4.3.3 Response Time . 14
4.3.4 LCS QoS Class . 15
4.3.5 Dispatchable Location accuracy . 15
4.4 Reliability . 16
4.5 Priority . 16
4.6 Timestamp . 16
4.7 Security . 16
4.8 Privacy . 17
4.8.1 Service Type Privacy . 18
4.8.1.1 Standardized Service Types . 18
4.9 Service Authorization . 19
4.10 Service Activation and De-Activation . 19
4.11 Coverage. 20
4.12 Roaming Target UE. 20
4.13 Support for all UEs . 21
4.14 Support for Unauthorized UEs . 21
4.15 Periodic Location Reporting. 21
4.16 UE-Based Location Calculation . 22
4.17 UE_Assisted LCS Location Calculation . 22
4.18 Mobile Originating Location . 22
4.19 Network support for LCS . 23
5 Logical Description . 23
5.1 Logical Reference Model . 23
5.2 Functional Entities . 24
5.2.1 LCS Client . 24
5.2.2 LCS Server. 24
5.2.3 Positioning Function . 24
5.2.4 Target UE. 24
5.3 Functional Interfaces . 24
5.3.1 LCS Client / LCS Server Interface . 24
5.3.1.1 Location Service Request . 24
5.3.1.2 Location Service Response . 25
ETSI
3GPP TS 22.071 version 15.1.0 Release 15 4 ETSI TS 122 071 V15.1.0 (2020-03)
5.3.1.3 Location Service Request Report . 26
5.4 Location information . 26
5.4.1 Sources of location information . 26
6 Service Provision . 26
6.1 Identification of a Target UE . 26
6.2 Location Information Provided to the LCS Client . 27
6.3 LCS Client Subscription . 27
6.4 Target UE Subscription . 28
6.4.1 Privacy Subscription Options . 28
6.4.2 Codeword . 28
6.4.2.1 Enhanced codeword . 28
6.4.3 Privacy Exception List . 28
6.4.4 Privacy Override Indicator . 30
6.4.5 Subscription to Mobile Originating Location . 30
6.4.6 Void . 30
6.4A Requestor . 30
6.5 Security . 30
6.6 Charging . 30
6.7 LCS Open Service Architecture and Application Programming Interface . 31
7 Provisioning and Administration . 31
7.1 Procedures for an LCS Client . 31
7.1.1 Provisioning . 31
7.1.2 Withdrawal . 31
7.1.3 Invocation . 31
7.2 Procedures for a Target UE . 32
7.2.1 Provisioning . 32
7.2.2 Withdrawal . 32
7.2.3 User Control. 32
7.3 Barring Capability of the Location Service . 32
8 Interactions with Bearer and Teleservices and Other Services . 32
9 Cross Phase Compatibility between releases . 33
9.1 Compatibility with existing standards . 33
9.2 Compatibility with future releases . 33
9.2.1 Void . 33
9.2.2 Location determination in call or PDP context activation and release . 33
9.2.3 Void . 33
9.2.4 Defined geographical areas . 33
9.2.5 Continuous check of location. 33
9.2.6 Identification of a target UE . 34
9.2.7 Void . 34
9.2.8 VHE . 34
Annex A (informative): USA FCC Wireless E911 Rules . 35
Annex B (informative): Descriptions of possible location based services . 37
B1 Public Safety Services . 37
B1.1 Emergency Services . 37
B1.1.1 Attributes . 37
B1.1.2 Emergency Alert Services . 37
B2 Location Based Charging . 37
B2.1 Attributes . 38
B2.1.1 Target Subscriber Notification . 38
B2.1.2 Charging . 38
B2.1.3 Roaming . 39
B3 Tracking Services . 39
B3.1 Fleet and Asset Management Services. 39
B3.2 Traffic Monitoring . 40
B3.2.1 Attributes . 40
B3.2.1.1 Privacy . 40
ETSI
3GPP TS 22.071 version 15.1.0 Release 15 5 ETSI TS 122 071 V15.1.0 (2020-03)
B4 Enhanced Call Routing . 40
B5 Location-Based Information Services . 40
B5.1 Navigation. 40
B5.2 City Sightseeing . 41
B5.3 Location Dependent Content Broadcast . 41
B5.4 Mobile Yellow Pages . 41
B5.5 Location Sensitive Internet . 41
B6 Network Enhancing Services . 41
B6.1 Applications for Network Planning . 41
B6.2 Applications for Network QoS Improvements . 41
B6.3 Improved Radio Resource Management . 42
Annex C (Informative): Attributes of Specific Services . 43
Annex D (informative): Change history . 51
History . 54

ETSI
3GPP TS 22.071 version 15.1.0 Release 15 6 ETSI TS 122 071 V15.1.0 (2020-03)
Foreword
This Technical Specification (TS) has been produced by the 3GPP.
The contents of this document are subject to continuing work within the TSG and may change following formal TSG
approval. Should the TSG modify the contents of this TS, 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 specification;

ETSI
3GPP TS 22.071 version 15.1.0 Release 15 7 ETSI TS 122 071 V15.1.0 (2020-03)
1 Scope
This document provides the Stage One description of Location Services (LCS). A Stage One description provides an
overall service description, primarily from the service subscriber's and user's points of view, but not dealing with the
details of the Man Machine Interface (MMI). This TS includes information applicable to network operators, service
providers and terminal, base station system, switch, and data base manufacturers.
NOTE: Location Services may be considered as a network provided enabling technology consisting of
standardized service capabilities which enable the provision of location-based applications. These
applications may be service provider specific. The description of the numerous and varied possible
location applications which are enabled by this technology are outside the scope of this specification.
However, clarifying examples of how the functionality being specified may be used to provide specific
location services is included in various sections of the specification.
This document provides core requirements to an extent sufficient to derive a complete definition of location services at
the service level. However, the present document also provides additional requirements which may suggest in a non-
normative manner certain ways the system may be implemented to support location services.
LCS can be offered without subscription to basic telecommunication services. LCS is available to the following
categories of LCS clients:
• Value Added Services LCS Clients – use LCS to support various value-added services. These clients can include
UE subscribers as well as non-subscribers to other services.
• PLMN Operator LCS Clients – use LCS to enhance or support certain O&M related tasks, supplementary
services, IN related services and bearer services and teleservices.
• Emergency Services LCS Clients – use LCS to enhance support for emergency calls from subscribers.
• Lawful Intercept LCS Clients – use LCS to support various legally required or sanctioned services.
LCS is applicable to any target UE whether or not the UE supports LCS, but with restrictions on choice of positioning
method or notification of a location request to the UE user when LCS or individual positioning methods, respectively,
are not supported by the UE.
LCS is being developed in phases with enhancements added in 3GPP releases.
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.
2.1 Normative references
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 23.032: "Universal Geographical Area Description".
[3] 3GPP TS 22.101: "Service principles".
[4] 3GPP TS 22.105: "Services and Service Capabilities".
ETSI
3GPP TS 22.071 version 15.1.0 Release 15 8 ETSI TS 122 071 V15.1.0 (2020-03)
[5] 3GPP TS 22.115: "Charging and Billing"
[6] Open Mobile Alliance (OMA): OMA-RD-Parlay_Service_Access-V1_0-20100427-A
[7] 3GPP TS 23.110: " UMTS Access Stratum; Services and Functions".
2.2 Informative references
[8] 3GPP TR 25.923: "Report on Location Services (LCS)".
[9] PD 30.lcs: "Project Plan for location services in UMTS".
[10] Third generation (3G) mobile communication system; Technical study report on the location
services and technologies, ARIB ST9 December 1998.
[11] The North American Interest Group of the GSM MoU ASSOCIATION: Location Based Services,
Service Requirements Document of the Services Working Group
[12] FCC, Fourth Report and Order: Wireless E911 Location Accuracy Requirements, February 3,
2015, https://www.fcc.gov/document/fcc-adopts-new-wireless-indoor-e911-location-accuracy-
requirements-0
[13] FCC, Erratum, Wireless E911 Location Accuracy Requirements, March 3, 2015,
https://apps.fcc.gov/edocs_public/index.do?document=332342
3 Definitions and abbreviations
3.1 Abbreviations
For the purposes of the present document, in addition to 3GPP TR.21.905, the following abbreviations apply:
BDS BeiDou Navigation Satellite System
BLE Bluetooth Low Energy
EGNOS European Geographic Navigation Overlay System
E-OTD Enhanced Observed Time Difference
GAGAN GPS Aided Geo Augmented Navigation (or GPS and Geo Augmented Navigation)
GLONASS GLObal NAvigation Satellite System
GNSS Global Navigation Satellite System
IPDL-OTDOA Idle Period Downlink- Observed Time Difference Of Arrival
LCS Location Service
MSAS Multi-functional Satellite Augmentation System
NA-ESRD North American Emergency Services Routing Digits
NA-ESRK North American Emergency Services Routing Key
NANP North American Numbering Plan
PSAP Public Safety Answering Point
QZSS Quasi Zenith Satellite System
SBAS Satellite Based Augmentation Systems
TBS Terrestrial Beacon Systems
U-TDOA Uplink Time Difference of Arrival
WAAS Wide Area Augmentation System

NOTE: In the present document, acronyms are used in the text as if they are read either in their fully expanded
form or in their alphabet names with no consistent principle.
3.2 Definitions
For the purposes of the present document the following definitions apply:
ETSI
3GPP TS 22.071 version 15.1.0 Release 15 9 ETSI TS 122 071 V15.1.0 (2020-03)
Change of Area: is one event supported for deferred Location Requests. Change of Area means that the network is
required to report the location or the occurrence of the event of the requested subscriber in triggered fashion
immediately after the network (MSC/SGSN) processes the mobility event for the new location of the subscriber.
Usually new location is noticed after the Location Update, Tracking Area Update, Handover, RAU, Registration or
RANAP Location Report, e.g. when the SAI changes.
Codeword: access code, which is used by a Requestor or LCS Client in order to gain acceptance of a location request
for a Target UE. The codeword is part of the privacy information that may be registered by a Target UE user.
Current Location: after a location attempt has successfully delivered a location estimate or Dispatchable Location and
its associated time stamp, the location estimate or Dispatchable Location and time stamp are referred to as the ‘current
location’ at that point in time.
Deferred location request: a location request where the location response (responses) is (are) required after specific
event has occurred. Event may or may not occur immediately. In addition, event may occur many times.
Dispatchable Location: The civic location of a UE and/or a valid Mobile Equipment (ME), expressed as civic data
(e.g. floor, street number, city.) The Dispatchable Location shall be represented in a well-defined universal format.
Regional regulations may specify the mandatory and optional elements in this universal format to be included in a
Dispatchable Location.
Immediate location request: a location request where a single location response only is required immediately.
Initial Location: in the context of an originating emergency call the location estimate or Dispatchable Location and the
associated time stamp at the commencement of the call set-up is referred to as ‘initial location’.
Last Known Location: The current location estimate or Dispatchable Location and the associated time stamp for
Target UE stored in the LCS Server is referred to as the ‘last known location’ and until replaced by a later location
estimate or Dispatchable Location and a new time stamp is referred to as the ‘last known location’.
LCS Client: a software and/or hardware entity that interacts with an LCS Server for the purpose of obtaining location
information for one or more Mobile Stations. LCS Clients subscribe to LCS in order to obtain location information.
LCS Clients may or may not interact with human users. The LCS Client is responsible for formatting and presenting
data and managing the user interface (dialogue). The LCS Client is identified by a unique international identification,
e.g. E.164.
NOTE: The LCS Client may reside inside or outside the PLMN.
LCS Client Access barring list: an optional list of MSISDNs per LCS Client where the LCS Client is not allowed to
locate any MSISDN therein.
LCS Client Subscription Profile: a collection of subscription attributes of LCS related parameters that have been
agreed for a contractual period of time between the LCS client and the service provider.
LCS Feature: the capability of a PLMN to support LCS Client/server interactions for locating Target UEs.
LCS Server: a software and/or hardware entity offering LCS capabilities. The LCS Server accepts requests, services
requests, and sends back responses to the received requests. The LCS server consists of LCS components which are
distributed to one or more PLMN and/or service provider.
Location Estimate: the geographic location of a UE and/or a valid Mobile Equipment (ME), expressed in latitude and
longitude data. The Location Estimate shall be represented in a well-defined universal format. Translation from this
universal format to another geographic location system may be supported, although the details are considered outside
the scope of the primitive services.
NG-RAN: a radio access network connecting to the 5G core network which uses NR, E-UTRA, or both.
North American Emergency Services Routing Digits (NA-ESRD): a telephone number in the North American
Numbering Plan (NANP) that can be used to identify a North American emergency services provider and its associated
LCS client. The ESRD also identifies the base station, cell site or sector from which a North American emergency call
originates.
North American Emergency Services Routing Key (NA-ESRK): a telephone number in the North American
Numbering Plan (NANP) assigned to an emergency services call by a North American VPLMN for the duration of the
call. The NA-ESRK is used to identify (e.g. route to) both the emergency services provider and the switch in the
ETSI
3GPP TS 22.071 version 15.1.0 Release 15 10 ETSI TS 122 071 V15.1.0 (2020-03)
VPLMN currently serving the emergency caller. During the lifetime of an emergency services call, the NA-ESRK also
identifies the calling mobile subscriber.
PLMN Access barring list: an optional list of MSISDN per PLMN where any LCS Client is not allowed to locate any
MSISDN therein except for certain exceptional cases.
Privacy Class: list of LCS Clients defined within a privacy exception class to which permission may be granted to
locate the target UE. The permission shall be granted either on activation by the target UE or permanently for a
contractual period of time agreed between the target UE and the service provider.
Service Identifier: A service provided by an LCS Client is identified by a Service Identifier. One LCS client may have
one or more services. The combination of the LCS client Identifier and the Service Identifier constitutes a unique
identification of a service.
Privacy Exception List: a list consisting of various types of privacy classes (i.e. operator related, personal etc.).
Certain types of classes may require agreement between the service provider and the target UE.
Requestor: an originating entity, which has requested the location of the target UE from the LCS client.
Target UE: The UE being positioned.
Target UE Subscription Profile: the profile detailing the subscription to various types of privacy classes.
UE available: deferred Location Request event in which the MSC/SGSN has established a contact with the UE. Note,
this event is considered to be applicable when the UE is temporarily unavailable due to inaction by the UE user,
temporarily loss of radio connectivity or IMSI detach and so on. Note that IMSI detach is only applicable in the case
UE has previously been registered and information is still kept in the node.
4 Functional Requirements
4.0 General
3GPP standards shall support location service features, to allow new and innovative location-based services to be
developed. It shall be possible to identify and report in a standard format (e.g. geographical co-ordinates) the current
location of the user’s terminal and to make the information available to the user, ME, network operator, service
provider, value added service providers and for PLMN internal operations.
The location is provided to identify the likely location of specific MEs. This is meant to be used for charging, location-
based services, lawful interception, emergency calls, etc., as well as the positioning services.
The standard shall support NG-RAN, E-UTRAN, GERAN and UTRAN to facilitate determination of the location of a
mobile station.
The following subsections provide general descriptions of attributes that can be used to describe or characterize various
location services.
The relative importance of these attributes varies from service to service. However, accuracy, coverage, privacy and
transaction rate may be considered the primary distinguishing attributes that define a value-added service. Briefly:
• accuracy is the difference between actual location and estimated location,
• coverage is an expression of the geographic area in which the UE user will receive an adequate perceived
quality of service,
• privacy describes the user’s perception of confidentiality of the location information, and
• transaction rate indicates how frequently network messaging is required to support the service.
A general comparison of the specific attributes of various location-based services is provided in Annex C of this
document.
4.1 High Level Requirements
The following high-level requirements are applicable:
ETSI
3GPP TS 22.071 version 15.1.0 Release 15 11 ETSI TS 122 071 V15.1.0 (2020-03)
1 The supporting mechanisms should incorporate flexible modular components with open interfaces that facilitate
equipment interoperability and the evolution of service providing capabilities.
2 The network should be sufficiently flexible to accommodate evolving enabling mechanisms and service
requirements to provide new and improved services.
3 It shall be possible to provide multiple layers of permissions to comply with local, national, and regional privacy
requirements.
4 Multiple positioning methods should be supported in the different Access Networks, including (but not limited
to):
- Modernized GPS;
- SBAS (Satellite Based Augmentation Systems: EGNOS, WAAS, GAGAN, MSAS);
- QZSS (Quasi Zenith Satellite System);
- GLONASS
- BDS
- Galileo
- U-TDOA
- E-OTD
- IPDL-OTDOA
- Network Assisted GNSS (e.g. Network Assisted GPS or Network Assisted GALILEO)
- UE ambient condition sensors-based positioning
- Motion sensors (e.g. accelerometers, gyroscopes)
- Environmental sensors (e.g. barometer)
- Position sensors (e.g. magnetometers, orientation sensors)
- TBS
- Beacon identity for location lookup (e.g. WiFi access points or BLE beacons)
- RF Pattern Matching
- Methods using cell site or sector information and Timing Advance or RoundTrip Time measurements.
5 The location determining process should be able to combine diverse positioning techniques and local knowledge
when considering quality of service parameters to provide an optimal positioning request response.
6 It should be possible to provide position information to location services applications existing within the PLMN,
external to the PLMN, or in Mobile Equipment;
7 Support should be provided for networks based on Intelligent Network architecture (i.e. with specific support for
CAMEL based Location Services).
8 Support may optionally be provided to enable the routing of emergency calls based on the geographic
coordinates (latitude and longitude) of the calling party.
9 It shall be possible to provide the originating party’s serving cell id to the LCS client.

ETSI
3GPP TS 22.071 version 15.1.0 Release 15 12 ETSI TS 122 071 V15.1.0 (2020-03)
4.2 Location Information
Location Information consists of Geographic Location, Velocity, Civic Location and Quality of Service information, as
described in the subsequent sections.
4.2.1 Geographic Location
Provision of the geographic location of a target UE is applicable to all LCS services.
Note: For services other than LCS the network may also determine within which Cell, Service Area, or
Tracking Area the Target UE is located ("Service Area" and "Tracking Area" are UTRAN and E-UTRAN
concepts respectively and both may consist of one (in R99) or more than one cell). The Service or
Tracking Area information or Cell ID may be used for routing of calls or for CAMEL applications, if
supported.
It should be noted that the Service and Tracking Area concepts are different from the Localized Service Area concept
used for SoLSA.
4.2.2 Velocity
Velocity is the combination of speed and direction of a Target UE. It shall be possible for a UE to provide its velocity to
the LCS server.
Note: This requirement only applies to satellite-based positioning systems.
For Value Added Services and PLMN Operator Services, the following is applicable:
Provision of the velocity of a target UE is application driven. Location Services may allow an LCS Client to request
or negotiate the provision of velocity.
For Emergency Services there is no requirement to provide velocity.
4.2.3 Dispatchable Location
Provision of the Dispatchable Location of a target UE in civic form is applicable to Emergency Services based on
regional regulatory requirements.
An example of Dispatchable Location regional regulatory requirements for the United States can be found in [12] and
[13].
4.3 Quality of Service
4.3.1 Horizontal Accuracy
The accuracy that can be provided with various positioning technologies depends on a number of factors, many of
which are dynamic in nature. As such the accuracy that will be realistically achievable in an operational system will
vary due to such factors as the dynamically varying radio environments (considering signal attenuation and multipath
propagation), network topography in terms of base station density and geography, and positioning equipment available.
The accuracy for location services can be expressed in terms of a range of values that reflect the general accuracy level
needed for the application. Different services require different levels of positioning accuracy. The range may vary from
tens of meters (navigation services) to perhaps kilometers (fleet management).
The majority of attractive value-added location services are enabled when location accuracies of between 25m and
200m can be provided.
ETSI
3GPP TS 22.071 version 15.1.0 Release 15 13 ETSI TS 122 071 V15.1.0 (2020-03)
Based on decreasing accuracy requirement some examples of location services are provided in table 4.1. The LCS
service shall provide techniques that allow operators to deploy networks that can provide at least the level of accuracy
required by the regional regulatory bodies (e.g. Annex A).
Table 4.1; Example of location services with decreasing accuracy requirem
...