9 Cross Phase Compatibility between releases

22.0713GPPLocation Services (LCS)Release 17Service descriptionStage 1TS

This section details the cross-phase compatibility requirements relating to the service requirements in this document.

Note: when a change is introduced which affects the 3GPP specifications, it is said to be ‘backward compatible’ if existing equipment can continue to operate and perform correctly with equipment that conforms to the new implementation.

9.1 Compatibility with existing standards

Where the service and operational requirements in this document relate to a core network functionality, compatibility is required.

UTRAN, E-UTRAN, and NG-RAN LCS shall be developed to maximise synergies with earlier LCS phases.

9.2 Compatibility with future releases

It is envisaged that 3GPP standards will evolve in future releases, for example with the addition of new service requirements. The standards which define the technical implementation of LCS should be developed in such a way that it is practical to add the requirements in this section in a backward compatible manner.

Following chapters include requirements that are foreseen for future release.

9.2.1 Void

9.2.2 Location determination in call or PDP context activation and release

A possible future enhancement in LCS is that location information of a specific target UE may be obtained at the activation of a Call or PDP Context. A corresponding mechanism to obtain the location information of a specific target UE at the release of a Call or PDP Context may also be feasible.

9.2.3 Void

9.2.4 Defined geographical areas

It shall be possible to specify a geographical area as ellipse to a resolution that will be limited by the accuracy capability of the part of the serving network where the user is registered.

It may be possible to identify and report when the user’s terminal enters or leaves a specified geographic area.

In order to enable ME to determine itself if it enters or leaves a defined geographical area information about the defined geographical area shall be made available to client. The method is FFS, one alternative is that cells covering parts of the geographical area broadcasts information about the geographical area.

9.2.5 Continuous check of location

The client may continuously check its current location with or without requesting signalling support from the network using the Self Location feature. In this way the client may become aware of entering or leaving a predefined geographical area, as defined above, and/ or it can supply the user or an application with real-time tracking information.

9.2.6 Identification of a target UE

In future releases usage of IP addresses for UE identification shall be supported by the standard.

9.2.7 Void

9.2.8 VHE

LCS shall support VHE 22.121 [6].

Annex A (informative):
USA FCC Wireless E911 Rules

Action was taken by the FCC on January 29, 2015, with respect to E911 location technology by the Fourth Report and Order (FCC 15-9).The following revisions to the wireless E911 rules (see [12] and [13] for the specific rules) are reproduced from the Fourth Report and Order (revisions on compliance, enforcement, testing, test bed, reporting, submission of plans and reports is not included):

• Location Delivery Latency (Time to First Fix) is set at a maximum of 30 seconds from the time the user initiates an emergency service call to the time it is available at the location information center.
• Defines the following:
  1. Dispatchable location: A location delivered to the PSAP by the network with an emergency service call that consists of the street address of the calling party, plus additional information such as suite, apartment or similar information necessary to adequately identify the location of the calling party. The street address of the calling party must be validated and, to the extent possible, corroborated against other location information prior to delivery of dispatchable location information by the PLMN operator to the PSAP.
  2. National Emergency Address Database (NEAD): A database that utilizes MAC address information to identify a dispatchable location for nearby wireless devices within the PLMN operator’s coverage area.
  3. Nationwide PLMN operator: a PLMN operator whose service extends to a majority of the population and land area of the United States.
  4. Non-nationwide PLMN operator: Any PLMN operator other than a nationwide PLMN operator.
• Sets the following indoor location accuracy standards for 911 calls:
  • 1. For horizontal location

1. Nationwide PLMN operators shall provide either a dispatchable location or x/y location within 50 meters for the following percentages of wireless emergency service calls within the following timeframes from the effective date of the adoption of these rules
   1. Within 2 years: 40% of all wireless emergency service calls
   2. Within 3 years: 50% of all wireless emergency service calls
   3. Within 5 years: 70% of all wireless emergency service calls
   4. Within 6 years: 80% of all wireless emergency service calls
2. Non-nationwide PLMN operators shall provide either a dispatchable location or x/y location within 50 meters for the following percentages of wireless emergency service calls within the following timeframes from the effective date of the adoption of these rules
   1. Within 2 years: 40% of all wireless emergency service calls
   2. Within 3 years: 50% of all wireless emergency service calls
   3. Within 5 years or within 6 months of deploying VoLTE whichever is later: 70% of all wireless service calls
   4. Within 6 years or within one year of deploying VoLTE, whichever is later: 80% of all wireless emergency service calls
      1. For vertical location, PLMN operators shall provide vertical location information with wireless emergency service calls within the following timeframes from the effective date of the adoption of these rules
3. Within 3 years: All PLMN operators shall make uncompensated barometric data available to PSAPs with respect to any 911 call placed from any UE with the capability to deliver barometric sensor information
4. Within 3 years: Nationwide PLMN operators shall develop one or more z-axis metrics validated by an independently administered and transparent test bed process and shall submit the proposed metrics and testing results to the FCC for approval.
5. Within 6 years: In each of the top 25 Cellular Market Areas (CMA), nationwide PLMN operators shall deploy either dispatchable location or z-axis technology in compliance with any z-axis accuracy metric that has been approved by the FCC.
   1. In each CMA where dispatchable location is used: nationwide PLMN operators must ensure that the NEAD is populated with a sufficient number of total dispatchable location reference points to equal 25% of the CMA population.
   2. In each CMA where z-axis is used: nationwide PLMN operators must deploy z-axis technology to cover 80% of the CMA population.
6. Within 8 years: In each of the top 50 CMAs, nationwide PLMN operators shall deploy either dispatchable location or such z-axis technology in compliance with any z-axis accuracy metric that has been approved by the FCC.
7. Non-nationwide PLMN operators that serve any of the top 25 or 50 CMAs will have an additional year to meet the vertical location benchmarks in C & D.

• Specifies the delivery of location confidence and uncertainty data
  • • 1. PLMN operators shall provide for all wireless emergency service calls, whether from outdoor or indoor locations, x- and y-axis confidence and uncertainty information on a per-call basis upon the request of a PSAP. The data shall specify the caller’s location with a uniform confidence level of 90 percent and the radius in meters from the reported position at the same confidence level. All entities responsible for transporting confidence and uncertainty between CMRS providers and PSAPs including PLMN operators, owners of E911 networks and emergency service providers, must enable the transmission of confidence and uncertainty data provided by PLMN operators to the requesting PSAP.
      2. Upon meeting the 3 year timeframe for the horizontal location standards, PLMN operators shall provide with emergency service calls that have a dispatchable location the confidence and uncertainty data for the x- and y- axis required in these regulations.
      3. Upon meeting the 6 year timeframe for the horizontal location standards, PLMN operators shall provide with wireless emergency service calls that have a dispatchable location the confidence and uncertainty data for the x- and y- axis required in these regulations.
• Specifies the live emergency service call data recording requirements
  • • • 1. PLMN operators must record information on all live emergency calls including, but not limited to, the positioning source method used to provide a location fix associated with the call. PLMN operators must also record the confidence and uncertainty data they provide. This information must be made available to PSAPs upon request, and shall be retained for a period of two years.
• Defines when the requirements of the location accuracy regulations apply

The requirements shall be applicable only to the extent that the administrator of the applicable designated PSAP has requested the services required under these regulations and the PSAP is capable of receiving and utilizing the requested data elements and has a mechanism for recovering the PSAP’s costs associated with them.

Annex B (informative):
Descriptions of possible location based services

B1 Public Safety Services

Service providers offer these location-based services for the good of the public. They are made available without requiring pre-subscription.

B1.1 Emergency Services

Specific consideration of mandated Emergency Services is outside the scope of this specification. Such requirements may be regionally or nationally specific.

B1.1.1 Attributes

Specific consideration of the attributes for mandated Emergency Services is outside the scope of this specification. However, the current requirements specified by the U.S. FCC [12] and [13] may be useful as examples.

The FCC’s Fourth Report and Order (FCC 15-9) in the matter of Wireless E911 Location Accuracy Requirements (PS Docket No. 07-114), adopted January 29, 2015, is reproduced here:

All CMRS providers must provide (1) dispatchable location, or (2) x/y location within 50 meters, for the following percentages of wireless 911 calls within the following timeframes, measured from the effective date of rules adopted in this Order (“Effective Date”):

 Within 2 years: 40 percent of all wireless 911 calls.

 Within 3 years: 50 percent of all wireless 911 calls.

 Within 5 years: 70 percent of all wireless 911 calls.

 Within 6 years: 80 percent of all wireless 911 calls.

Within 6 years: Nationwide CMRS provides must deploy either (1) dispatchable location, or (2) z-axis technology that achieves the Commission-approved z-axis metric, in each of the top 25 Cellular Market Areas

Within 8 years: Nationwide CMRS providers must deploy dispatchable location or z-axis technology in accordance with the above benchmarks in each of the top 50 CMAs.

Note 1: The Fourth Report and Order definition of a dispatchable location as reproduced here:
Dispatchable location is the street address of the calling party plus additional information such as floor, suite, apartment or similar information that may be needed to adequately identify the location of the calling party. See the Report and Order [12] for more information.

The network should be sufficiently flexible to accommodate evolving enabling mechanisms and service requirements to provide new and improved services.

B1.1.2 Emergency Alert Services

Emergency Alert Services may be enabled to notify wireless subscribers within a specific geographic location of emergency alerts. This may include such alerts as tornado warnings, pending volcano eruptions, etc.

No requirements currently exist for Emergency Alert Services, and they may be considered for further study.

B2 Location Based Charging

Location Based Charging allows a subscriber to be charged different rates depending on the subscriber’s location or geographic zone, or changes in location or zone. The rates charged may be applicable to the entire duration of the call, or to only a part of call’s duration. This service may be provided on an individual subscriber basis, or on a group basis.

For example, when provided on an individual basis this service could apply reduced rates to those areas most often frequented by the subscriber by taking into consideration the subscriber’s daily route and lifestyle. Different rates may be applied at country clubs, golf courses, or shopping malls. For example, a "home" zone may be defined which is centered around a user’s home, an agreed larger area, work or travel corridor or some unrelated zone. The zone may vary in size and shape from a cell (or sector) coverage area to a precisely defined polygon completely independent of cell coverage.

Additionally, different rates may be applied in different zones based on the time of day or week.

In addition to being applicable on an individual basis, this service may be applicable on a group basis, which may be desirable for example, for business groups. Locations may be defined for business groups to include corporate campuses, work zones or business zones with different tiers of charging rates.

Individual and group subscribers should be notified of the zone or billing rate currently applicable, and be notified when the rate changes. Location Based Charging may be invoked upon initial registration. A charging zone would then be associated with the subscriber’s location. When the subscriber moves to a different zone, the subscriber would be notified.

This service should be transparently provided to the subscriber (i.e. independent of existing voice calls, data, or other services being provided).

B2.1 Attributes

Normal service operation includes invocation upon initial registration, autonomous registration, call origination, and call termination. Location-Based Charging should analyze location information to compare against service zones established for the subscriber. The service would notify the subscriber of their relative location to the established service zone, indicating either "in" or "out" of zone. As the subscriber changes location or predefined location service area they should be notified of their location-based charging service opportunity, being "in" or "out" of a subscribed zone. Except for subscriber notification, the user should experience transparency in interaction with other services (Voice, Data, SMS, etc).

This service may, as an option, be activated/de-activated using special feature codes on a subscriber or business customer basis.

B2.1.1 Target Subscriber Notification

The user needs to be informed on an ongoing basis which zone and billing rate is currently applicable.

Users should be enabled to make an informed decision on expected call charges and therefore need to be provided charging zone information accurately, and in a timely manner, being notified which zone they are in when a call is set up. Notification to the subscriber/user could be provided in several forms including tone, announcement, or short message.

The billing system will need to consider the following possible scenarios:

1. For the duration of the call, the subscriber remains in a single charging zone

2. During the call, the charging zones may change

2.1. The user may initiate a call in one zone, then move to a different zone where the call is terminated.

2.2. The user may cross back and forth between zones multiple times during the duration of a call, and the call may terminate in the zone it was originated from, or in a different zone.

Notification to the user may be via the UE MMI prior to initiation of the call and, during the call.

B2.1.2 Charging

To support appropriate charging, call detail records may need to include the following additional information:

1 Location Service (Location Based Charging) Identification

2 Location Information

3 Zone Information

4 Type of Event

5 Duration of Event

B2.1.3 Roaming

If a subscriber with active location-based charging roams into a system that does not support the service, the subscriber may be notified of an "out of coverage zone" notification using the best possible method (UE display, SMS, etc.).

B3 Tracking Services

Although Fleet and Asset Management services may be offered as separate services, within this document they are described as a single service category. In a similar manner, Person Tracking may be viewed as a form of personal asset tracking.

B3.1 Fleet and Asset Management Services

Fleet and Asset Management services allow the tracking of location and status of specific service group users. Examples may include a supervisor of a delivery service who needs to know the location and status of employees, parents who need to know where their children are, animal tracking, and tracking of assets.

The service may be invoked by the managing entity, or the entity being managed, depending on the service being provided.

Fleet Management may enable an enterprise or a public organization to track the location of vehicles (cars, trucks, etc.) and use location information to optimize services.

Asset management services, for example, may range from asset visualization (general reporting of position) to stolen vehicle location and geofencing (reporting of location when an asset leaves or enters a defined zone). The range of attributes for these services is wide.

For Fleet and Asset Management services, a distinction may be made between the manager of the fleet/assets in charge of tracking, and the entities being tracked (service group users, etc). The tracking service may make use of mobile station handsets with possible specialized functions (Web browsers, etc) to allow for tracking and specific methods for communicating with the managing entity. A managing entity would be able to access one or several managed entities’ location and status information through a specified communication interface (Internet, Interactive Voice Response, Data service, etc). The managing entity would be able to access both real-time and recent location and status results of managed entities.

The network shall provide the capability to provide the last known location and timestamp. In cases where the service group user’s mobile station is not registered (i.e. Inactive, out of coverage) the last known location information and timestamp may optionally be provided. If this information is unavailable in real-time, a reason for why the information is unattainable may be provided. The managing entity may also be able to relay messages to service group users through the appropriate interface, as well as receive messages originated by the service group users.

Activation of Fleet and Asset Management services could be performed via subscriber provisioning by the service provider, as well as by offering subscriber-based service activation codes to the service group user/subscriber. The managing entity could also initiate service via requests to a provisioning system through Interactive Voice Response or Internet request. A feature code may optionally also be provided to allow for specific mobile user group subscriber activation by the managing entity (*FC + Mobile ID). A specific user group mobile could also be able to self-activate through the use of a feature code.

B3.2 Traffic Monitoring

Mobiles in automobiles on freeways anonymously sampled to determine average velocity of vehicles. Congestion detected and reported.

Congestion, average flow rates, vehicle occupancy and related traffic information can be gathered from a variety of sources including roadside telematic sensors, roadside assistance organizations and ad-hoc reports from individual drivers. In addition, average link speeds can be computed through anonymous random sampling of UE locations.

B3.2.1 Attributes

B3.2.1.1 Privacy

Anonymous sampling of target UE requires all unique information relating to the UE location to be retained by the network operator. Depending on the capabilities of the location method (ref. section 3.4) traffic behavior described above can only be determined if a UE is sampled at least twice within a finite predetermined period.

The UE identification must be sufficiently unique to allow time separated measurements to be paired before discarding the source UE identification.

The level of uniqueness can be a highly truncated form of the UE-IMSI (or equivalent). For example, maintaining 1000 unattached location estimates for subsequent pairing with future estimates will only require 3 least significant digits of the IMSI. Ambiguity in matching will occur but at a low (detectable) rate. Finally, all unattached estimates can be set to expire after a preset time.

B4 Enhanced Call Routing

Enhanced Call Routing (ECR) allows subscriber or user calls to be routed to the closest service client based on the location of the originating and terminating calls of the user. The user may optionally dial a feature or service code to invoke the service (*GAS for closest gas station, etc).

In addition to routing the call based on location, ECR should be capable of delivering the location information to the associated service client. For example, this capability may be needed for services such as Emergency Roadside Service. This could be used for the purpose of dispatching service agents for ECR service clients that can make use of this information.

ECR services may be offered, for example, through menu driven access allowing users to interactively select from a variety of services.

B5 Location-Based Information Services

Location-Based Information services allow subscribers to access information for which the information is filtered and tailored based on the location of the requesting user. Service requests may be initiated on demand by subscribers, or automatically when triggering conditions are met, and may be a singular request or result in periodic responses.

The following subsections provide some examples of possible location-based information services.

B5.1 Navigation

The purpose of the navigation application is to guide the handset user to his/her destination. The destination can be input to the terminal, which gives guidance how to reach the destination. The guidance information can be e.g. plain text, symbols with text information (e.g. turn + distance) or symbols on the map display. If the handset’s velocity is available in addition to its position, real-time, adaptable turn-by-turn directions can be provided. The instructions may also be given verbally to the users by using a voice call.

Note: this may involve a service provider giving verbal directions to a lost motorist or providing periodic short text messages (possibly using SMS), in addition to, or as an alternative to the provision of a graphic map.

This can be accomplished through carrying a mobile phone that has location technology capabilities down to a few feet. Less granularity impedes the applicability of this functionality.

This service can either be menu driven from a handset using SIM Application Toolkit or a WAP based terminal with a map application running – similar to a GPS system. A central server may handle all mapping of locations, and may save specific locations (i.e., favorite fishing holes).

B5.2 City Sightseeing

City Sightseeing would enable the delivery of location specific information to a sightseer. Such information might consist of combinations of the services described throughout this document to describe historical sites, providing navigation directions between sites, facilitate finding the nearest restaurant, bank, airport, bus terminal, restroom facility, etc.

B5.3 Location Dependent Content Broadcast

The main characteristic of this service category is that the network automatically broadcasts information to terminals in a certain geographical area. The information may be broadcast to all terminals in a given area, or only to members of specific group (perhaps only to members of a specific organization). The user may disable the functionality totally from the terminal or select only the information categories that the user is interested in.

An example of such a service may be localized advertising. For example, merchants could broadcast advertisements to passersby based on location / demographic / psychographic information (for example "today only, 30% off on blue jeans").

B5.4 Mobile Yellow Pages

The internet has also changed how people find phone numbers. Instead of thumbing through the yellow pages or calling Directory assistance you simply go online and search the number. The need for paper copy phonebooks is gone. Wireless takes this one step further by adding the location of the subscriber to the search. Now the phone number of the nearest location can be ascertained as opposed to all locations within a 50-mile area.

Mobile Yellow Pages services provide the user with the location of the nearest service point, e.g. Italian restaurant. The result of the query may be a list of service points fulfilling the criteria (e.g. Italian restaurants within three kilometers). The information can be provided to the users in text format (e.g. name of the restaurant, address and telephone number) or in graphical format (map showing the location of the user and the restaurants).

B5.5 Location Sensitive Internet

Location Sensitive Internet is for further study.

B6 Network Enhancing Services

The Network Enhancing Services described in this section are for further study and privacy issues will require further consideration.

B6.1 Applications for Network Planning

The network operator may be able to use location information to aid network planning. The operator may be able to locate calls in certain areas to estimate the distribution of calls and user mobility for network planning purposes. These applications may be used for hot spot detection and user behavior modeling

B6.2 Applications for Network QoS Improvements

The network operator may be able to use location services to improve the Quality of Service of the network. The location system may be used to track dropped calls to identify problematic areas. The system may also be used to identify poor quality areas.

B6.3 Improved Radio Resource Management

The location of the handset may be used for more intelligent handovers and more efficient channel allocation techniques.

Annex C (Informative):
Attributes of Specific Services

The following table (provided by the GSM Alliance Services Working Group) depicts ranges of values that may be expected for various attributes of location based services.

Requirement -> Service Category	Service Authorization		Privacy				Target Subscriber Notification		Horizontal Accuracy		Vertical Accuracy	Response Time	Reliability	Security	Periodic Location Reporting	Service Registration	Service Activation	Service De-Activation	Service Invocation	Roaming	Service Specific Considerations	Interactions With Other Wireless Services
Public Safety Services
Emergency Services	None req’d		Implied when dialing 911 info provided to safety organizations				Not required		Network based: 100m (67%) 300m (95%) Handset based: 50m (67%) 150m (95%)		n/a now (5-15m future?	5 sec.	Same as GSM	Same as GSM	Required Period TBD suggest 1-10 minutes	None req’d	None required	Not Allowed	Keystroke or Dialed string (911)	Required if emergency call can be made		Lat and Long. To PSAP
Emergency Alert Services	Req’d		Info only passed to subscribed to service provider				Not required		125 m (10 m future?)		n/a now (5-15m future?	5 sec.	Same as GSM	Same as GSM	Required Period TBD suggest 1-10 minutes	Req’d	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	Automatic	Preferred where roaming is allowed		Lat & Long to Service Provider Live, SMS or other data service (WAP,GPRS) return msg.
Location Sensitive Charging
Home-Zone Billing	Req’d		Info only passed to subscribed to carrier				Not required		Depends on billing zone (5m-300m)		n/a	Depends on increments of billing.	Same as GSM	Same as GSM	Required depends on billing increment and coverage zone	Req’d	Interactive with Carrier	Interactive with Carrier	Automatic	n/a		Lat & Long to Carrier
Tracking Services
Fleet Mgment.	Req’d		Info only passed to subscribed to service provider				Not required		125m-Cell ID		n/a	5 sec.	Same as GSM	Same as GSM	Required (1-10 minutes)	Req’d	Interactive or live operator	Interactive or live operator	Interactive or live operator	Preferred where roaming is allowed		Lat & Long to Service Provider To requesting customer’s interface (e-mail, Web or live operator
Asset Mgment	Req’d		Info only passed to subscribed to service provider				Not required		10m-125m		n/a (5-15m future?	5 sec.	Same as GSM	Same as GSM	Required (1-10 minutes)	Req’d	Interactive or live operator	Interactive or live operator	Interactive or live operator	Preferred where roaming is allowed	Special Terminal	Lat & Long to Service Provider To requesting customer’s interface (e-mail, Web or live operator
Person Tracking	Req’d		Info only passed to subscribed to service provider				May be required (Child versus Employee?)		10m-125m		n/a (5-15m future?	5 sec.	Same as GSM	Same as GSM	Required (1-10 minutes)	Req’d	Interactive or live operator	Interactive or live operator	Interactive or live operator	Preferred where roaming is allowed		Lat & Long to Service Provider To requesting customer’s interface (e-mail, Web or live operator
Pet Tracking	Req’d		Info only passed to subscribed to service provider				Not required		10m-125m		n/a (5-15m future?	5 sec.	Same as GSM	Same as GSM	Required (1-10 minutes)	Req’d	Interactive or live operator	Interactive or live operator	Interactive or live operator	Preferred where roaming is allowed	Special Terminal	Lat & Long to Service Provider To requesting customer’s interface (e-mail, Web or live operator
Traffic Monitoring
Traffic Congestion Reporting	Req’d		No specific Target UE info allowed				Not required		10-40m Hi- res. req’d muti- near proximity lanes (opposing and adjacent)		May be req’d for over-passes	5 sec.	Same as GSM	Same as GSM	Required (1-2 minutes)	Req’d	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	Preferred where roaming is allowed	High bandwidth req on network.	Lat & Long to Service Provider Live or SMS return msg.
Enhanced Call Routing
Routing to Nearest Commercial Enterprise	Req’d		Info only passed to subscribed to service provider				Not required		10m-125m		n/a	5 sec.	Same as GSM	Same as GSM	Not required	Req’d	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	Preferred where roaming is allowed		Lat & Long to Service Provider
Roadside Assistance	Req’d		Info only passed to subscribed to service provider				Not required		10m-125m		n/a	5 sec.	Same as GSM	Same as GSM	Not required	Req’d	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	Preferred where roaming is allowed		Lat & Long to Service Provider Live or SMS return msg.
Location Based Information Services
Navigation	Req’d		Info only passed to subscribed to service provider				Required		10m-125m		n/a	5 sec.	Same as GSM	Same as GSM	Required (1-10 minutes)	Req’d	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	Preferred where roaming is allowed		Lat & Long to Service Provider Live, SMS or other data service (WAP,GPRS) return msg.
City Sightseeing	Req’d		Info only passed to subscribed to service provider				Not required		10m-125m		n/a	5 sec.	Same as GSM	Same as GSM	Not required	Req’d	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	Preferred where roaming is allowed		Lat & Long to Service Provider Live, SMS or other data service (WAP,GPRS) return msg.
Localized Advertising	Req’d		Info only passed to subscribed to service provider				Not required		125m-Cell ID		n/a	Not sensitive (default to 5 sec.)	Same as GSM	Same as GSM	Not required	Req’d	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	Preferred where roaming is allowed		Lat & Long to Service Provider SMS return msg.
Mobile Yellow Pages	Req’d		Info only passed to subscribed to service provider				Not required		125m-Cell ID		n/a	5 sec.	Same as GSM	Same as GSM	Not required	Req’d	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	By menu, keystroke, interactive or live operator	Preferred where roaming is allowed		Lat & Long to Service Provider Live, SMS or other data service (WAP,GPRS) return msg.
Service Provider Specific Services
Network Planning	Not Req’d		Specific Target UE info allowed				Not Required		10m-Cell ID		n/a	5 sec.	Same as GSM	Same as GSM	Required (1 minute)	Not Req’d	N/a	n/a	n/a	n/a		n/a
Dynamic Network Control	Not Req’d		Specific Target UE info allowed				Not Required		10m-Cell ID		n/a	5 sec.	Same as GSM	Same as GSM	Required (1 minute)	Not Req’d	N/a	n/a	n/a	n/a		n/a

Annex D (informative):
Change history

Change history
TSG SA#	SA Doc.	SA1 Doc	Spec	CR	Rev	Rel	Cat	Subject/Comment	Old	New	WI
Jun 1999			GSM  02.71					Transferred to 3GPP SA1	7.0.0
SP-04			22.071						3.0.0
SP-05	SP-99486	S1-99831	22.071	0001	1	R99	C	UMTS LCS service requirements support for mobile originated positioning requests, and velocity as a service parameter	3.0.0	3.1.0
SP-05	SP-99438	S1-99832	22.071	0002		R99	B	UMTS LCS service requirements	3.0.0	3.1.0
SP-05	SP-99438	S1-99833	22.071	0003		R99	C	LCS accuracy requirements	3.0.0	3.1.0
SP-05	SP-99479	S1-99625	22.071	0004		R99	D	Editorial changes for alignment	3.0.0	3.1.0
SP-06	SP-99522	S1-99955	22.071	0005		R99	D	U.S. specific Emergency Services requirements included as an informative annex.	3.1.0	3.2.0
SP-08	SP-000212	S1-000338	22.071	0006		R00	C	Incorporation of TSG SA1#8 LCS Contributions and email contributions	3.2.0	4.0.0
SP-09	SP-000378	S1-000484	22.071	0008		R4	F	Correction to LCS Service Description Stage 1 Document (R’00)	4.0.0	4.1.0
SP-09	SP-000392	S1-000667	22.071	0009		R4	C	Provision of Velocity for Location Services	4.0.0	4.1.0
SP-09	SP-000392	S1-000670	22.071	0010		R4	B	External LCS client identity	4.0.0	4.1.0
SP-09	SP-000392	S1-000671	22.071	0011		R4	B	Privacy Control for LCS	4.0.0	4.1.0
SP-09	SP-000392	S1-000672	22.071	0012		R4	F	Privacy Control for LCS	4.0.0	4.1.0
SP-09	SP-000392	S1-000673	22.071	0013		R4	D	Clarifications to LCS on privacy and Service response	4.0.0	4.1.0
SP-09	SP-000392	S1-000674	22.071	0014		R4	F	LCS: Geographic Location	4.0.0	4.1.0
SP-09	SP-000392	S1-000675	22.071	0015		R4	D	Adding statement on “active” and “idle” UE in chapter 4.13	4.0.0	4.1.0
SP-09	SP-000392	S1-000676	22.071	0016		R4	D	Radio Access Network support for LCS	4.0.0	4.1.0
SP-09	SP-000392	S1-000677	22.071	0017		R4	D	LCS, Identification of a Target UE using IP addresses	4.0.0	4.1.0
SP-09	SP-000392	S1-000678	22.071	0018		R4	D	LCS: LCS Open Service Architecture (OSA) and Application Programming Interface.	4.0.0	4.1.0
SP-10	SP-000544	S1-000787	22.071	0019		Rel-4	B	Privacy Exception List	4.1.0	4.2.0	LCS
SP-10	SP-000544	S1-000788	22.071	0020		Rel-4	B	Periodic Location Reporting	4.1.0	4.2.0	LCS
SP-10	SP-000544	S1-000791	22.071	0021		Rel-4	B	Location Service Request	4.1.0	4.2.0	LCS
SP-10	SP-000544	S1-000851	22.071	0022		Rel-4	C	Periodic Location Reporting amendment	4.1.0	4.2.0	LCS1
SP-10	SP-000544	S1-000803	22.071	0023		Rel-4	C	Addition of achieved location information accuracy with reference to TS 23.032	4.1.0	4.2.0	LCS1
SP-11	SP-010044	S1-010235	22.071	0024		Rel-4	C	Quality level negation	4.2.0	4.3.0	LCS1
SP-11	SP-010044	S1-010239	22.071	0025		Rel-4	C	Location determination in call or PDP context activation and release	4.2.0	4.3.0	LCS1-PS
SP-11	SP-010044	S1-010237	22.071	0026		Rel-4	C	OSA support for LCS	4.2.0	4.3.0	LCS1
SP-11	SP-010044	S1-010218	22.071	0027		Rel-4	D	Editorial Cleanup	4.2.0	4.3.0	LCS1
SP-11	SP-010044	S1-010269	22.071	0028		Rel-4	C	Number of LCS Clients	4.2.0	4.3.0	LCS1
SP-14	SP-010673	S1-011285	22.071	0029		Rel-5	C	Privacy Override Indicator	4.3.0	5.0.0	LCS1
SP-15	SP-020047	S1-020467	22.071	0030		Rel-5	B	CR 22.071 Rel.5 B Requestor	5.0.0	5.1.0	LCS1
SP-15	SP-020047	S1-020478	22.071	0031		Rel-5	B	CR 22.071 Rel.5 B Introducing service type privacy for location services	5.0.0	5.1.0	LCS1
SP-15	SP-020047	S1-020479	22.071	0032		Rel-5	C	Introduction of a Codeword Setting	5.0.0	5.1.0	LCS1
SP-15	SP-020047	S1-020632	22.071	0033		Rel-5	B	CR to 22.071 on Clarifying checking of requester ID	5.0.0	5.1.0	LCS1
SP-15	SP-020043	S1-020455	22.071	0036		Rel-5	A	CR 22.071 Rel-5 A Closure of a loophole in the privacy settings	5.0.0	5.1.0	TEI
SP-15	SP-020047	S1-020466	22.071	0037		Rel-5	B	CR 22.071 Rel.5 B Deferred Location Request with Change of Area Event	5.0.0	5.1.0	LCS1
SP-15	SP-020045	S1-020457	22.071	0039	–	Rel-5	A	Editorial CR to correct terms and references	5.0.0	5.1.0	CORRECT
			22.071	–	–	Rel-5		Editorial to change page layout for Annex C	5.1.0	5.1.1
SP-16	SP-020254	S1-020864	22.071	0040		Rel-6	C	CR to TS 22.071 Rel-6 Privacy control in HPLMN	5.1.1	6.0.0	LCS1
SP-16	SP-020254	S1-020922	22.071	0041		Rel-6	C	Enhancement of Codeword Requirements for LCS	5.1.1	6.0.0	LCS1
SP-17	SP-020556	S1-021662	22.071	0042		Rel-6	D	CR to 22.071: Too big file size	6.0.0	6.1.0	LCS1
SP-17	SP-020556	S1-021794	22.071	0043		Rel-6	B	CR to 22.071 on LCS Anonymous requestor and anonymous target mobile (REL6)	6.0.0	6.1.0	LCS1
SP-17	SP-020556	S1-021490	22.071	0044		Rel-6	B	CR to 22.071 on LCS Codeword improvements (REL6)	6.0.0	6.1.0	LCS1
SP-17	SP-020556	S1-021491	22.071	0045		Rel-6	B	LCS extended user privacy	6.0.0	6.1.0	LCS1
SP-17	SP-020556	S1-021799	22.071	0046		Rel-6	C	Update to 22.071 for regional specific location accuracy requirements	6.0.0	6.1.0	LCS
SP-18	SP-020657	S1-022013	22.071	0047		Rel-6	C	CR to LCS stage 1 ‘Service Type’	6.1.0	6.2.0	LCS2
SP-18	SP-020657	S1-022299	22.071	0048		Rel-6	C	Handling of privacy checks for Network Induced Location Requests	6.1.0	6.2.0	LCS2
SP-19	SP-030020	S1-030277	22.071	0049	–	Rel-6	B	Applicability of barring capability to the Location Service	6.2.0	6.3.0	LCS2
SP-20	SP-030252	S1-030526	22.071	0050	–	Rel-6	B	Introduction of codeword generation by network or UE	6.3.0	6.4.0	LCS
SP-20	SP-030252	S1-030392	22.071	0051	–	Rel-6	B	LCS in IMS	6.3.0	6.4.0	LCS
SP-20	SP-030252	S1-030557	22.071	0052		Rel-6	F	Clarification of requirement regarding ‘Query, Cancel of activated location requests for the Target UE’	6.3.0	6.4.0	LCS
SP-20	SP-030322	S1-030650	22.071	0053		Rel-6	B	Routing of Emergency Calls based on Geographic Coordinates	6.3.0	6.4.0	LCS2
SP-21	SP-030455	S1-030945	22.071	0056	–	Rel-6	A	Correction of requirements on the identity format of LCS clients	6.4.0	6.5.0	TEI
SP-21	SP-030459	S1-030946	22.071	0057	–	Rel-6	C	Clarification of Mobile Originating Location	6.4.0	6.5.0	TEI6
SP-21	SP-030459	S1-030947	22.071	0058	–	Rel-6	B	A requirement of authentication to the Target UE user	6.4.0	6.5.0	LCS
SP-21	SP-030459	S1-030948	22.071	0059	–	Rel-6	B	Introduction of LCS QoS Classes	6.4.0	6.5.0	LCS2
SP-22	SP-030690	S1-031328	22.071	0062	–	Rel-6	A	Removal of misleading and obsolete text	6.5.0	6.6.0	LCS1
SP-22	SP-030697	S1-031272	22.071	0063	–	Rel-6	F	Correction of "velocity" requirements	6.5.0	6.6.0	LCS1
SP-22	SP-030697	S1-031329	22.071	0064	–	Rel-6	B	Cell ID	6.5.0	6.6.0	LCS
SP-23	SP-040090	S1-040199	22.071	0069	–	Rel-6	F	Inclusion of U-TDOA positioning method	6.6.0	6.7.0	LCS
SP-24	SP-040300	S1-040514	22.071	0070	–	Rel-7	C	Accuracy of information Indication of capability	6.7.0	7.0.0	LCS2; EMC1
SP-26	SP-040907		22.071	0072	1	Rel-7	C	Velocity Service Description	7.0.0	7.1.0	LCS-R7
SP-28	SP-050221	S1-050531	22.071	0073	–	Rel-7	C	Introducing notification based on current location of target UE	7.1.0	7.2.0	LCS3
SP-29	SP-050584	–	22.071	0071	1	Rel-7	C	Introducing A-GNSS concept to extend A-GPS to include GALILEO	7.2.0	7.3.0	A-GNSS
SP-30	SP-050749	S1-051127	22.071	0074	2	Rel-7	B	Identification of the UE based on the IMEI	7.3.0	7.4.0	LCS3
SP-38	SP-070855	S1-071669	22.071	0075	1	Rel-8	C	E-UTRAN support for location services	7.4.0	8.0.0	AIPN-SAE
SP-42	SP-080775	S1-083376	22.071	0077	2	Rel-8	C	Support for Additional Navigation Satellite Systems (ANSS) for LCS	8.0.0	8.1.0	TEI8
SP-46	–	–	–	–	–	–	–	Updated to Rel-9 by MCC	8.1.0	9.0.0
SP-49	SP-100575	S1-102049	22.071	0079	–	Rel-9	D	Removal of references to 3GPP OSA	9.0.0	9.1.0	TEI9
2011-03	–	–	–	–	–	–	–	Update to Rel-10 version (MCC)	9.1.0	10.0.0
2012-09	–	–	–	–	–	–	–	Updated to Rel-11 by MCC	10.0.0	11.0.0
2014-10	–	–	–	–	–	–	–	Update to Rel-12 version (MCC)	11.0.0	12.0.0
2015-06	–	—	–	–	–	–	–	Update to Rel-13 version (MCC) because of the creation of Rel-14 (see SP-150271)	12.0.0	13.0.0
SP-68	SP-150271	S1-151488	22.071	80	2	Rel-14	C	Addition of Z-axis requirements for emergency calls	12.0.0	14.0.0	ELIOT
SP-68	SP-150271	S1-151454	22.071	81	1	Rel-14	C	Revise Annex A to reflect new FCC Emergency Service Location Accuracy Regulations	12.0.0	14.0.0	ELIOT
SP-69	SP-150538	S1-152739	22.071	82	2	Rel-14	B	Addition of civic location reporting for Emergency Services	14.0.0	14.1.0	ELIOT
2018-06	–	–	–	–	–	–	–	Update to Rel-15 version (MCC)	14.1.0	15.0.0
2020-03	SP-200121	S1-201075	22.071	0083	1	Rel-15	F	Add “NG-RAN” to the Location Service stage 1	15.0.0	15.1.0	TEI15
SA#88e	–	–	–	–	–	–	–	Update to Rel-16 version (MCC)	15.1.0	16.0.0
2022-03	–	–	–	–	–	–	–	Updated to Rel-17 by MCC	16.0.0	17.0.0