TIA/EIA-41-D Location Services Enhancements

Transcription

1 GPP X.S000-0 Version.0 Date: March 00 TIA/EIA--D Location Services Enhancements COPYRIGHT GPP and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the GPP Secretariat at Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See for more information.

2 Revision History Revision Date Rev. 0 Initial Publication March 00

3 X.S000-0 v CONTENTS TIA/EIA--D LOCATION SERVICES ENHANCEMENTS List of Figures... vi List of Tables... vii Revision History... viii Introduction... Objective... References... Organization... Assumptions... Editorial Conventions... TIA/EIA- Modifications... References.... Normative References... Definitions and Concepts.... Definitions... Y Network Capabilities...0 Y. Location Services (LCS)...0 Y.. Position Information...0 Y... Reference System...0 Y... Shapes... Y... Velocity... Y...Timestamp... Y.. LCS Client Subscription... Y.. Position Quality of Service (PQOS)... Y..Security... Y.. Target MS Privacy... Y.. Normal Procedures with Successful Outcome... Y.. Exception Procedures or Unsuccessful Outcome... Y.. Alternate Procedures... Y.. Interactions With Other Network Services... Y. Location Information Restriction (LIR)... Y.. Normal Procedure With Successful Outcome... Y.. Exception Procedures or Unsuccessful Outcome...0 Y.. Alternative Procedures... Y..Interactions With Other Wireless Services... i Contents

4 X.S000-0 v.0 TIA/EIA-. Modifications... Definitions and Documentation Conventions.... Definitions... Symbols and Abbreviations... Network Reference Model....X Location Services Enhancements....X. Network Entities... TIA/EIA-. Modifications....X General Position Determination Technologies....X. Successful Position Determination....X.. MS Registration....X.. Successful Position Determination: Home MPC is the Serving MPC... 0.X.. Successful Position Determination: Home MPC is Not Serving MPC....X..Successful Position Determination: Serving MPC Address Has Changed....X.. Successful Position Determination After Intersystem Handoff....X.. Multiple LCS Client Requests Managed by Home MPC....X.. Multiple LCS Client Requests Managed by Serving MPC....X.. Successful Serving System Initiated Position Determination....X.. Position Determination for HLR-Based Service....X..0 Successful Call-Related LCS....X. Unsuccessful Position Determination....X.. LCS Client Denied Access by Home MPC....X.. Unsuccessful Serving System Initiated Position Determination....Y CDMA MS-Assisted Position Determination....Y. Successful CDMA MS-Assisted Position Determination....Y.. MS Idle....Y.. MS Engaged in Call....Y.. Continuation of Position Determination After Handoff....Y. Call-Related LCS Call Release....Y. Interaction with Non-Emergency Services Calls....Y.. Successful Resumption of Position Determination after Call Delivery....Y.. Unsuccessful Position Determination: Call Delivery While Awaiting MS Response....Y.. Unsuccessful Position Determination: Call Delivery After Response Sent to PDE....Y..Unsuccessful Position Determination: Non-Emergency Services Call Origination... 0.Y.Interactions with Phase II Emergency Services Calls....Y.. Ongoing Position Determination Ended by Emergency Services Call....Y.. Blocking of Value Added Service Positioning....Y.. Interactions After Intersystem Handoff Contents ii

5 X.S000-0 v Y.. VAS Position Determination Delayed by Emergency Services Call Single MPC....Y.. Position Determination Initiated in Anchor System Ended by Emergency Services Call After Intersystem Handoff....Y.. Position Determination Initiated in a Tandem System Ended by Emergency Services Call...0.Y. Failure Cases...0.Y.. Radio Contact Failure...0.Y.. Traffic Channel Failure or Traffic Channel Release...0.Y.. Failure After Intersystem Handoff...0.Y..PDE Unavailable....Y.. PDE Failure....Y.. Traffic Channel Inactivity Timer Expiry....Y.. Traffic Channel Inactivity Timer Expiry While Awaiting MS Response....Z Coarse Position Determination....Z. MS Idle....Z. MS Engaged in Call....Z. Position Determination After Intersystem Handoff... TIA/EIA-. Modifications... Data Transfer Services.... SS-Based Data Transfer Services... Application Services....MAP Operations..... General Operation Specifiers..... Operation Definitions FlashRequest RegistrationNotification SMSDeliveryPointToPoint......am GeoPositionRequest......an InterSystemPositionRequest......ao InterSystemPositionRequestForward......au LCSParameterRequest......ay PositionEventNotification...0. Map Parameters..... General Parameter Identifiers..... Parameter Definitions AccessDeniedReason ActionCode Profile SMS_CauseCode......w ServiceIndicator......fk GeographicPosition fo MobInfo_CDMA... iii Contents

6 X.S000-0 v.0...fr PositionInformation......fs PositionRequestType......ft PositionResult......gd CDMAServingOneWayDelay......go LCS_Client_ID......gx LCSBillingID gy LIRAuthorization......gz LIRMode......ha MPCAddress......hb MPCID......hc PositionQualityOfService......hd PQOS_HorizontalPosition he PQOS_HorizontalVelocity......hf PQOS_MaximumPositionAge......hg PQOS_PositionPriority......hh PQOS_ResponseTime......hi PQOS_VerticalPosition......hj PQOS_VerticalVelocity......hk Horizontal_Velocity......hl Vertical_Velocity hm MPCAddressList... TIA/EIA-. Modifications... Basic Call Processing.... Registration Call Tasks..... Loading of Profile Parameters... Intersystem Procedures.... Registration Notification..... MSC Initiating MS Registration..... VLR Receiving RegistrationNotification INVOKE.... SMS Delivery Point-To-Point..... MSC Receiving an SMSDeliveryPointToPoint INVOKE..... Anchor MSC Initiating SMS Delivery Point-To-Point V SMS Delivery Point-To-Point for Position Data Message Exchange V. MSC Receiving SMDPP INVOKE for Position Data Message Exchange... 0.W InterSystem Position Request... 0.W. MSC Receiving an InterSystemPositionRequest INVOKE... 0.X Intersystem Position Request Forward....X. MSC Receiving an InterSystemPositionRequestForward INVOKE....Y LCS Parameter Request....Y. HLR Receiving LCSParameterRequest INVOKE....Z Position Event Notification....Z. MSC Initiating Position Event Notification... Operation Timer Values Contents iv

7 X.S000-0 v D Annex D: SMS Air Interface Delivery Point-To-Point... D. Serving MSC Receiving an SMD-REQUEST... Annex A: Mobile Station Implementation... Annex B: MPC and PDE Operation Timer Implementation... v Contents

8 X.S000-0 v.0 LIST OF FIGURES Introduction TIA/EIA- Modifications TIA/EIA-. Modifications Figure X Network Reference Model for Location Services Enhancements... TIA/EIA-. Modifications TIA/EIA-. Modifications TIA/EIA-. Modifications Annex A: Mobile Station Implementation Annex B: MPC and PDE Operation Timer Implementation List of Figures vi

9 X.S000-0 v LIST OF TABLES Introduction TIA/EIA- Modifications Table LIR Subscription Options... TIA/EIA-. Modifications TIA/EIA-. Modifications TIA/EIA-. Modifications Table MTP Message Priority Values for TIA/EIA- Operations... Table TIA/EIA- MAP Operation Specifiers... Table 0 Summary of MAP Operations... Table NE Combinations for GPOSREQ... Table NE Combinations for ISPOSREQ... Table NE Combinations for ISPOSREQFWD... Table NE Combinations for LCSParameterRequest... Table NE Combinations for PositionEventNotification...0 Table TIA/EIA- MAP Parameter Identifiers... Table Horizontal Position Accuracy r Corresponding to Values of K... Table Vertical Position Accuracy r Corresponding to Values of K... TIA/EIA-. Modifications Table HLR LCSParameterRequest Response... Table Operation Timer Values... Annex A: Mobile Station Implementation Annex B: MPC and PDE Operation Timer Implementation Table Guidelines for MPC and PDE Operation Timer Values... vii List of Tables

10 X.S000-0 v.0 REVISION HISTORY Revision Date Remarks 0 March 00 Initial Publication Revision History viii

11 X.S000-0 v INTRODUCTION OBJECTIVE This document presents a recommended plan for the implementation of Location Services Enhancements for use in the Wireless Radiotelephone Service. This purpose of this document is to specify the intersystem operations that enable a wireless system to provide enhanced location services. REFERENCES This document builds on the following standards and specifications: TIA/EIA- TIA/EIA- IS-0 J-STD-0 GPP: S.R000, Cellular Features Description TIA: TIA/EIA--A, Wireless Features Description; Telecommunications Industry Association; July 000 TTC: JP-GB-S.R000, Wireless Features Description; The Telecommunication Technology Committee; March 000 GPP: N.S000, Cellular Radiotelecommunications Intersystem Operations CCSA: YD/T-0-, Technical Specification of 00 MHz CDMA Digital Cellular Mobile Telecommunication Network Mobile Application Part; Chinese Communications Standards Association; December TIA: TIA/EIA--D, Cellular Radiotelecommunications Intersystem Operations; Telecommunications Industry Association; December TTA: TTAE.G-N.S000, Cellular Radiotelecommunications Intersystem Operations; Telecommunications Technology Association; July 000 GPP: C.S00-0 Version.0, Position Determination Service Standard for Dual-Mode Spread Spectrum Systems; April 00 ARIB: STD-T-C.S00-0-, Position Determination Service Standard for Dual-Mode Spread Spectrum Systems; Association of Radio Industries and Business TIA: TIA/EIA/IS-0-, Position Determination Service Standard for Dual-Mode Spread Spectrum Systems Addendum ; Telecommunications Industry Association; March 00 TIA: TIA/EIA J-STD-0, Wireless Enhanced Emergency Services; Telecommunications Industry Association; October. See TIA- for a description of Wireless Intelligent Network (WIN) Location Based Services. Objective Introduction

12 X.S000-0 v.0 J-STD-0 TIA: TIA/EIA J-STD-0-A, Wireless Enhanced Wireless -- Phase ; Telecommunications Industry Association; March 00 World Geodetic System (WGS-) standardizes latitude and longitude. WGS- is the standard for conversion between local systems, in this case national geodetics and projection maps. ORGANIZATION WGS-World Geodetic System, WGS-. United States Department of Defense, MIL-STD-0,. This document is organized as follows: ASSUMPTIONS The TIA/EIA- Modifications section provides the additions and modifications to TIA/EIA--A Wireless Features Descriptions for Location Services Enhancements. The TIA/EIA/. Modifications section provides the modifications and additions to TIA/EIA--D Chapter Functional Overview for Location Services Enhancements. The TIA/EIA/. Modifications section provides the modifications and additions to TIA/EIA--D Chapter Automatic Roaming Information Flows for Location Services Enhancements. The TIA/EIA/. Modifications section provides the modifications and additions to TIA/EIA--D Chapter Signaling Protocol for the Location Services Enhancements. The TIA/EIA/. Modifications section provides the modifications and additions to TIA/EIA--D Chapter Signaling Procedures for Location Services Enhancements. Annex A (informative) provides guidance on minimizing the interaction of Value Added Services and Emergency Services position determination when CDMA MS-assisted position determination is used for both. The following assumptions were used in the development of this document: a. The wireless subscriber may designate a list of LCS Clients that are explicitly authorized to obtain position information for the subscriber s MS. This exception list is stored in the wireless subscriber s Home MPC. b. A wireless service provider may offer several Location Information Restriction (LIR) mode subscription options. The LIR mode information is stored in the wireless subscriber s Home MPC and HLR. The Home MPC is the control point for the LIR mode information. c. LIR mode information is stored in the wireless subscriber s home system and is transferred to the serving system (i.e., Serving VLR, Serving MSC) as part of the subscriber profile Introduction Organization

13 X.S000-0 v d. The MPC shall use the requested Position Quality of Service (PQOS) value to select a Position Determining Entity (PDE) that supports the required position accuracy. e. Communications between the LCS Client and the MPC can use SS-based data transfer services or IP-based data transfer services. This document only illustrates the use of TIA/EIA- Mobile Application Part (MAP) protocol for communications between the LCS Client and the MPC. However, other application layer protocols may be used for the L reference point. f. Communications between MPCs (e.g., Home MPC to Serving MPC) can use SS- based data transfer services or IP-based data transfer services. g. The LCS Client requests a PQOS level for the geographic position estimate. If the MPC can determine ahead of time that PQOS cannot be met, position determination should not be initiated. If a position estimate is obtained but does not meet the requested PQOS, the position estimate is returned to the LCS Client. Bi-lateral agreements may override or modify this treatment of PQOS. h. The Serving MPC shall direct the Serving MSC to assign the MS to a traffic channel for CDMA MS-assisted position determination prior to invoking the PDE (i.e., for IS-0 message exchange). i. For CDMA MS-assisted position determination, the PDE shall notify the Serving MSC when the IS-0 geoposition session has been completed. j. An MPC may cancel an ongoing position determination at a PDE (e.g., because of an emergency services position information request). k. Emergency and Value Added Services may be deployed on separate MPCs. At most, one Emergency Services MPC and one Value Added Services MPC may be associated with a single MSC. l. An MPC expects to receive an InterSystemPositionRequest INVOKE from a known LCS Client or from a Home MPC that is requesting the position information for a roaming MS. m. The Serving MPC shall include the LIRAuthorization parameter in the InterSystemPositionRequest INVOKE sent to the Serving MSC when the Serving MPC does not have the Target MS LIR Mode information and the request for position information was not received from an authorized entity (e.g., the Home MPC for the Target MS). The presence of the LIRAuthorization parameter in the InterSystemPositionRequest INVOKE indicates that the Serving MSC shall verify that Target MS's LIR Mode permits the MS's position to be determined. The absence of the LIRAuthorization parameter in the InterSystemPositionRequest INVOKE directs the Serving MSC to provide the Target MS geographic position information regardless of the Target MS s LIR Mode information. n. Voice services such as call delivery and call origination (including an Emergency Services call origination) involving a Target MS shall not be rejected if the Target MS has already been assigned to a traffic channel for position determination. Traffic channel resources allocated specifically for position determination shall be released if the MSC receives a request for voice services for the same Target MS. o. Coarse positioning can be used to obtain geographic position information for the cell serving the Target MS. This information is useful to services that do not require high accuracy geographic position information. Assumptions Introduction

14 X.S000-0 v.0 p. Coarse position can be obtained for a Target MS that is idle or is engaged in a call. When an MS is idle, radio contact must be established with the MS to determine the identity of the serving cell. When the MS is engaged in a call, coarse position can be obtained when the Target MS is in the Anchor System or after intersystem handoff. q. The association of a PDE with multiple MPCs is not explicitly addressed. r. This document does not support multiple concurrent IS-0 CDMA position determination sessions for a given MS. s. When IS-0 CDMA position determination is underway for a Value Added Service, the initiation of an Emergency Services call shall cause the ongoing position determination processing to be stopped. t. Within the serving network, it is the Serving MPC that coordinates multiple concurrent LCS requests received for a given MS. Specifically, in a single Serving MPC per MSC configuration, the Serving MPC handles the interaction between concurrent Emergency Services-related and Value Added Services-related LCS requests received for the same MS. u. IS-0 CDMA position determination may operate concurrently with other position determination technologies for a given MS. v. IS-0 preempt capability is applicable when an Emergency Services MPC and a separate VAS MPC are associated with a single MSC. This capability enables an emergency services call that requires CDMA position determination to preempt ongoing Value Added Service (VAS) CDMA position determination, for a given MS.» IS-0 preempt capability is an MSC configuration option and is applicable to all IS-0 position determination sessions handled by that MSC.» When an MSC is configured for IS-0 preempt capability, an MSC shall send a PositionEventNotification INVOKE to the VAS MPC when the MSC detects an emergency services call. In cases where VAS position determination has been initiated at an MSC and then handoff has occurred, only the position determination initiating MSC shall send a PositionEventNotification INVOKE to the VAS MPC when it detects an emergency services call.» When an MSC is configured for IS-0 preempt capability, the MSC shall reject an SMDPP received for VAS IS-0 CDMA position determination during an emergency services call, unless the ActionCode parameter indicating CDMA Handset-Based Position Determination Complete is received. If a VAS SMDPP indicating CDMA Handset-Based Position Determination Complete is received, the MSC shall send any received bearer data to the indicated MS. When IS-0 CDMA position determination has been initiated for an emergency services call, all IS-0 data bursts received from the MS shall be sent to the Emergency Services PDE/MPC.» When an MSC is configured for IS-0 preempt capability, the MSC shall respond negatively to an ISPOSREQ received from a VAS MPC requesting allocation of a traffic channel for CDMA position determination during an emergency services call Introduction Assumptions

15 X.S000-0 v » For Value Added Services (VAS), a PDE shall include an indication of VAS in the SMDPP sent to an MSC for IS-0 CDMA position determination.» IS-0 preempt capability is not applicable when a single MPC is associated with an MSC and is used for both Emergency Services and Value Added Services position determination. w. This document does not support the initiation of a VAS-related IS-0 CDMA position determination session by the transmission of an IS-0 message by an MS. x. The MobilePositionCapability (MPCAP) for a Target MS may not be known to the HLR (associated with the Target MS) and may not be provided to the Serving MPC. If the Serving MPC does not receive the Target MS MPCAP in the request for the Target MS position, the Serving MPC may use local procedures to determine the Target MS position and to satisfy the requested PQOS. y. This document does not support intersystem handoff of an MS that has been assigned to a traffic channel specifically for the purpose of CDMA handset-based position determination. z. This document does not address the interactions of CDMA MS-assisted position determination with other non-voice services that use SMSDeliveryPointToPoint operations (e.g., OTA, Short Message Delivery). aa. ab. This document does not specifically address the interactions of LCS and circuitswitched data telecommunications services. This document does not consider the interactions of LCS and packet-switched telecommunications services. EDITORIAL CONVENTIONS The following editorial conventions are used for this document: underline: addition cross out: deletion change bar: indicates additions or deletions new sub-sections are identified in the sub-section heading for clarity, new sub-sections are shown with vertical change bars but are not underlined automatic roaming information flows between the LCS Client and MPC are shown in red when:» communications between these entities can use SS-based data transfer services or IP-based data transfer services» for IP-based transfer services, the signaling protocol may not be TIA/EIA- MAP-based. A MobilePositionCapability parameter may not be received or a MobilePositionCapability parameter indicating Undefined Mobile Position Capabilities is received. Editorial Conventions Introduction

16 X.S000-0 v.0» for IP-based data transfer services, the LCS Client may be external to the wireless network automatic roaming information flows between the MPCs are shown in green when communications between these entities (e.g., Home MPC to Serving MPC) can use SS-based or IP-based data transfer services Introduction Editorial Conventions

17 X.S000-0 v TIA/EIA- MODIFICATIONS This section provides additions and modifications to TIA/EIA- required for enhanced Location Services (LCS). REFERENCES. Normative References (see TIA/EIA--000, page ) The following standards contain provisions that, through reference in this text, constitute provisions of this Standard.At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Standard are encouraged to investigate the possibility of applying the most recent editions of the standards indicated below. ANSI and TIA maintain registers of currently valid national standards published by them. [WGS-] World Geodetic System, WGS-. United States Department of Defense, MIL-STD-0,. DEFINITIONS AND CONCEPTS. Definitions (see TIA/EIA--000, page ) Accuracy The difference between the actual position of the target MS and the position estimate (e.g., as provided by position determining entity). Actual Position The actual coordinates of the Target MS based on a geographic measure. Altitude The geodetic position of the Target MS in terms of distance above or below the WGS- ellipsoid surface. Call-Related Location Service A Location Service related to a specific MS call (e.g., emergency services call, enhanced call routing based on the MS position). If the call is released while the LCS Client request for the Target MS position is being processed, the position processing should be canceled. Confidence The confidence by which the position of a Target MS is known to be within the shape description, (expressed as a percentage). References TIA/EIA- Modifications

18 X.S000-0 v.0 Current Position After a position determination has successfully provided a position estimate and its associated time stamp, the position estimate is referred to as the current position at that point in time. Last Known Position The current position estimate (and its associated time stamp) that is stored for the Target MS is referred to as the last known position until replaced by a later position estimate and its time stamp. LCS Location Services LCS Client An entity (e.g., service control function) that interacts with the network for the purpose of obtaining position information for one or more Target MSs within a set of specified parameters such as PQOS. LCS Clients subscribe to LCS in order to obtain position information for the purpose of providing location based applications. The LCS Client is responsible for formatting and presenting data and managing the user interface. The LCS Client may reside in the MS. LCS Client Subscriber Profile A collection of subscription attributes of LCS related parameters that have been agreed to between the LCS Client and the LCS service provider. LIR Location Information Restriction Mobile Position Center (MPC) The MPC serves as the point of interface to the wireless network for the position determination network. The MPC serves as the entity that retrieves, forwards, stores and controls position information within the position network. It can select the PDE(s) to use in position determination and forwards the position estimate to the requesting entity (e.g., LCS Client) or stores it for subsequent retrieval. The MPC may restrict access to position information for a Target MS (e.g. release position information to authorized entities only). Position Determining Entity (PDE) The PDE facilitates determination of the geographical position of a Target MS. The input to the PDE for requesting the position is a set of parameters such as PQOS requirements. Multiple PDEs may serve the coverage area of an MPC and multiple PDEs may serve the same coverage area of an MPC utilizing different position determining technologies. Position Estimate The geographic position of a Target MS as determined by a PDE and the Target MS. The reference system for the coding of the Target MS position is the World Geodetic System, (WGS-) TIA/EIA- Modifications Definitions

19 X.S000-0 v Position Quality Of Service (PQOS) A set of attributes associated with a request for the geographic position of a Target MS. The attributes include the required horizontal position accuracy, vertical position accuracy, horizontal velocity accuracy, vertical velocity accuracy, response time, priority, and maximum age of the Target MS position. Priority Requests for the position of a Target MS may be processed according to different levels of priority. A request with a higher priority may be given faster access to position determining resources than a lower priority request. Target MS The target MS is the MS whose position information is requested by the LCS Client. Target MS Privacy Profile The profile detailing the location privacy information for the MS (e.g., LIR mode, LCS Client exception list). Transaction Rate The frequency of position information requests for a location based service. Definitions TIA/EIA- Modifications

20 X.S000-0 v.0 Y NETWORK CAPABILITIES Y. Location Services (LCS) Y.. Y... (New Section for TIA/EIA-) Location Services (LCS) are network capabilities that enable the deployment of location based applications. The descriptions of possible location applications that are enabled by these capabilities are outside the scope of this document. Applicability to Telecommunications Services LCS are available to a variety of LCS Clients including: Value Added Services (or external) LCS Clients Wireless Service Provider LCS Clients MS LCS Clients LCS are applicable to any Target MS that is idle or has established a call, and are subject to the location information restrictions specified by the MS subscriber. LCS are limited by the position determination method in use at the serving system and the positioning capability of the MS. Position Information The position information is an estimate of the geographic position of a target MS. The position estimate is expressed as a shape. A shape is used to represent the uncertainty of the Target MS position. Velocity may be used to describe the speed and bearing of the Target MS. Reference System The reference system for the coding of positions is the World Geodetic System, (WGS ). The origin of the WGS coordinate system is the geometric center of the WGS ellipsoid. The ellipsoid is constructed by the rotation of an ellipse around the minor axis that is oriented in the North-South direction. The rotation axis is the polar axis of the ellipsoid, and the plane orthogonal to it and including the center of symmetry is the equatorial plane. The relevant dimensions are as follows: Major Axis = meters Minor Axis =. meters Coordinates are then expressed in terms of longitude and latitude relevant to this ellipsoid. The range of longitude is - 0 to +0, and the range of latitude is -0 to longitude corresponds to the Greenwich Meridian, and positive angles are to the East, while negative angles are to the West. 0 latitude corresponds to the equator, and positive angles are to the North, while negative angles are to the South. Altitudes are defined as the distance between the ellipsoid and the point, along a line orthogonal to the ellipsoid TIA/EIA- Modifications 0 Network Capabilities

21 X.S000-0 v Y... Y... Shapes The geodetic position of the Target MS is expressed as a shape. A number of different shapes can be selected according to need. Ellipsoid Point Information that describes a point on the surface of the WGS- ellipsoid that consists of latitude and longitude. In practice, such a description can be used to refer to a point on Earth s surface, or close to Earth s surface, with the same longitude and latitude. Ellipsoid Point with Uncertainty Information that describes a point that is characterized by the coordinates of an ellipsoid point (the origin) and a distance r. It describes the set of points on the ellipsoid that are at a distance from the origin less than or equal to r, the distance being the geodesic distance over the ellipsoid, i.e., the minimum length of a path staying on the ellipsoid and joining the two points. Similar to the ellipsoid point, this can be used to indicate points on the Earth surface, or near the Earth surface, of same latitude and longitude. The typical use of this shape is to indicate a point when its position is known only with a limited accuracy, but the geometric contributions of uncertainty can be quantified. Ellipsoid Point with Altitude and Uncertainty Information that describes a point that is characterized by the coordinates of an ellipsoid point, an uncertainty distance r, an altitude a and an altitude uncertainty h. It describes the set of points that are at a vertical distance h or less from the origin. The origin is a point at altitude a above an ellipsoid point with uncertainty. The typical use of this shape is to indicate a point when its position is known only with a limited accuracy, but the geometric contributions of uncertainty can be quantified. Velocity A description of velocity may be applicable to a Target MS on or close to the Earth s surface. Horizontal Velocity Information that describes the horizontal speed and bearing. The horizontal speed gives the magnitude of the horizontal component of the velocity of a Target MS. The bearing provides the direction of the horizontal component of velocity taken clockwise from North. Horizontal and Vertical Velocity Information that describes the horizontal speed and bearing, vertical speed and direction. The horizontal speed and bearing characterize the horizontal component of velocity. The vertical speed and direction provides the component of velocity of a Target MS in a vertical direction. Horizontal Velocity with Uncertainty Information that describes the horizontal speed and bearing as a vector V and an uncertainty speed s. This describes a set of velocity vectors v that are related to the given velocity vector V as follows: a. V v s Location Services (LCS) TIA/EIA- Modifications

22 X.S000-0 v.0 Y... Y.. Y.. Horizontal and Vertical Velocity with Uncertainty Information that describes the horizontal speed and bearing, giving a horizontal velocity vector V x,y, a vertical speed and direction giving a vertical velocity component Vz, and uncertainty speeds s and s. It describes the set of velocity vectors v with horizontal and vertical components v x,y, and v z that are related to the given velocity components V x,y, and V z as follows: a. V x,y v x,y s b. V z v z s Timestamp All position estimates provided to an LCS Client shall indicate the time when the estimate was obtained. LCS Client Subscription The LCS Client may subscribe to LCS features. The LCS Client Subscriber Profile may contain the range of PQOS levels that are applicable for the LCS Client and other subscription parameters. LCS Client ID The identity of the LCS Client. LCS Client MS Barring List The LCS Client is not permitted to obtain the position of the MSs identified in this optional list. LCS Client Target MS List The LCS Client is only permitted to obtain the position for the MSs identified in this optional list. LCS Client Priority The Priority levels that are applicable for the LCS Client. LCS Client Maximum Transaction Rate The maximum rate of position information requests applicable for the LCS Client. Response Time The maximum time delay for obtaining the response to a position information request. Position Quality of Service (PQOS) The Position Quality of Service (PQOS) is a set of attributes that reflect the accuracy, response time, priority and maximum age of the position information needed for a location based service. Different services may require different levels of accuracy, response time and age of the position information TIA/EIA- Modifications Location Services (LCS)

23 X.S000-0 v The LCS Client specifies the PQOS required for the Target MS s position estimate. If it can be determined at the time of the request that the PQOS cannot be met, position determination should not be initiated. Bi-lateral agreements may determine whether a position estimate that does not meet the requested PQOS shall not be returned to the LCS Client. The LCS Client shall be able to specify the required horizontal accuracy. The horizontal accuracy of the position estimate shall be satisfied as closely as possible to the requested horizontal accuracy, when other quality of service factors are not in conflict. Horizontal position estimates, vertical position estimates and velocity estimates may be requested independently. Applications may require one, two or all three. The requested PQOS may specify different levels of accuracy for each estimate. Given that the position estimate is the best possible estimate within the bounds of required response time, the position estimates of the Target MS (assuming several estimates are made) will reveal a spread of estimates around the actual MS position. The distribution of position estimates can be described by normal statistical parameters and suggests that a small proportion of position estimates may lie outside of the acceptable PQOS parameters for specific services. It may be possible to provide information on the confidence associated with a position estimate. This may be used by location services to determine if a position update should be requested, for example, if the reported accuracy falls below a threshold determined by the LCS Client for a specific service. It may also be possible to determine velocity (speed and heading) information from a single position request (e.g., the response to a single request may provide the results of multiple positioning determinations). When delivered with a position estimate, the confidence region parameters, speed and heading may allow an application to improve the service delivered to the MS user. Some examples are given below: a. Confidence Region: Measure of uncertainty that specifies the size and orientation of the ellipse in which an MS is likely to lie with a predetermined confidence (e.g., %). The size of the confidence region may be used by the LCS Client to request an updated position estimate. b. Speed: Enables road traffic congestion monitoring and average travel time estimates between positions. c. Heading: The position estimate of a vehicle may be improved to identify the appropriate side of the highway. This may enable the provision of traffic information that relates only to the Target MS direction of travel. Response Time Different location based services, or different LCS Clients, may have different requirements (depending on the urgency of the positioning request) for obtaining a response. Trade-offs may be necessary between the positioning accuracy and response time requirements. Location Services (LCS) TIA/EIA- Modifications

24 X.S000-0 v.0 Y.. Y.. Y.. Response Time is one of the PQOS parameters. The LCS client may specify the required response time either at provisioning or when the request for position information is made. When a response time is specified, the response time requirement shall be satisfied as closely as possible, when other quality of service parameters are not in conflict. The following response time options are applicable: Security. no delay: any available Last Known Position estimate of the target MS shall be immediately returned. If no position estimate is available, a failure indication shall be returned and, optionally, the procedures to obtain a position estimate may be initiated (e.g., to be available for a future request).. low delay: fulfillment of the response time requirement takes precedence over fulfillment of the accuracy requirement. The Current Position shall be returned with minimum delay. The position estimate shall be obtained to fulfill the accuracy requirement, but in doing so shall not add additional delay (i.e., a response with lower accuracy is more desirable than waiting for a more accurate response).. delay tolerant: fulfillment of the accuracy requirement takes precedence over fulfillment of the response time requirement. If necessary, the response for providing the position estimate shall be delayed until the accuracy requirements of the requesting LCS Client are met. The Current Position shall be obtained to fulfill the accuracy requirement. Position information shall be safeguarded against unapproved disclosure or usage. Position information shall also be provided in a secure and reliable manner that ensures the information is neither lost nor corrupted nor disclosed to an unauthorized third party. The identity and authorization privileges of the LCS Client shall be verified before responding to the LCS Client request. Target MS Privacy The MS subscriber shall have means to restrict access to position information for value added services (See Section Y., Location Information Restriction). Normal Procedures with Successful Outcome Authorization LCS may be generally available or may be provided after pre-arrangement with the service provider based on the subscription profile. For certain Wireless Service Provider controlled LCS Clients, a subscription profile may be unnecessary. For these LCS Clients, subscription to the LCS feature is given implicitly. These LCS Clients are empowered to request position information for a Target MS TIA/EIA- Modifications Location Services (LCS)

25 X.S000-0 v De- Authorization LCS may be withdrawn at the subscriber s request or for administrative reasons. Registration Registration occurs when a subscription profile is created for an LCS Client. De-Registration De-registration occurs when a subscription profile is removed. Activation LCS is activated upon authorization. De-Activation LCS shall be de-activated upon de-authorization. Invocation LCS is invoked by an LCS Client requesting Target MS position information. The LCS Client shall specify the desired PQOS in the request for position information. Normal Operation with Successful Outcome Position information shall be disclosed to a properly authorized LCS Client if considerations of Target MS privacy are satisfied and the requested PQOS level can be met. In case position information is not available to the required PQOS level, position information may still be disclosed to the LCS Client. The position information disclosed may be the current position or the last known position of the Target MS. Data Recording The following data may be recorded when position determination is completed: Type and identity of the LCS Client. Identity of the Target MS. Success or failure. PDE and position technology used. Position estimate (including confidence). Response time. Time stamp. Reliability information indicating the measure of how often position information requests that satisfy the PQOS requirements are successful, may be recorded. Location Services (LCS) TIA/EIA- Modifications

26 X.S000-0 v.0 Y.. Y.. Y.. Exception Procedures or Unsuccessful Outcome Registration None identified. De-Registration None identified. Activation None identified. De-Activation None identified. Invocation A negative response shall be provided to the LCS Client if any of the following conditions occur: The LCS Client is not authorized to request position information for the Target MS. The LCS Client requests an unauthorized PQOS level. Position information is not available to the requested PQOS level and a lower level of quality is not consistent with bi-lateral agreements. The LCS Client requests call-related position information for a Target MS and the call has been released. The LCS Client requests call-related position information for a Target MS that is not engaged in a call. The LCS Client requests call-related position information for a Target MS but does not provide the correct digits for dialed digit validation. Position information is not available due to emergency services call preemption. In the case of a call-related Location Service, release of the call should result in cancellation of the ongoing processing of the LCS Client request for the Target MS position. Alternate Procedures None identified. Interactions With Other Network Services No interactions have been identified with the following exceptions: TIA/EIA- Modifications Location Services (LCS)

27 X.S000-0 v Circuit-Switched Telecommunications Services A request to initiate or end a circuit-switched telecommunications service may result in an LCS failure. Emergency Services (--) A request for Target MS position from an Emergency Services system shall take precedence over LCS. Location Information Restriction (LIR) LIR takes precedence over LCS. Location Services (LCS) TIA/EIA- Modifications

28 X.S000-0 v.0 Y. Location Information Restriction (LIR) Y.. Location Information Restriction (LIR) restricts presentation of a Target MS s position information. LIR restricts the presentation of a Target MS s position only to those LCS Clients that are authorized to receive the location information. The position information is restricted regardless of whether the MS is engaged in a telecommunications service or is idle. LIR does not impact an MS user s ability to engage in telecommunications services. Applicability to Telecommunications Services LIR is applicable to LCS, and not applicable to any other services. Normal Procedure With Successful Outcome Authorization LIR may be generally available or may be provided after pre-arrangement with the home service provider TIA/EIA- Modifications Location Information Restriction (LIR)

29 X.S000-0 v LIR may be offered with several subscription options: Subscription Options De-Authorization LIR may be withdrawn at the subscriber s request or for administrative reasons. Registration The LCS exception list (i.e., the list of LCS Clients exempt from the Target MS s location privacy restrictions) shall be registered upon authorization for subscribers to LIR modes of Pre-Authorized LCS Clients Only and Pre-Authorized LCS Clients and User Authorized LCS Clients. De-Registration The LCS exception list shall be de-registered upon de-authorization. Activation LIR Mode LIR is activated upon authorization. Values Unconditionally Restricted. Position information for the Target MS shall only be disclosed to: An LCS Client that has been exempted from the MS s location privacy restrictions by regulatory or legal actions, A service provider controlled LCS Client that requires the position information for internal network operations. Pre-Authorized LCS Clients Only. Position information for the Target MS shall only be disclosed to: An LCS Client that has been exempted from the MS s location privacy restrictions by regulatory or legal actions, A service provider controlled LCS Client that requires the position information for internal network operations, An LCS Client that is on a semi-permanent list of LCS Clients that have been explicitly authorized by the subscriber to receive the position information. Pre-Authorized LCS Clients and User Authorized LCS Clients. Position information for the MS shall only be disclosed to: An LCS Client that has been exempted from the MS s location privacy restrictions by regulatory or legal actions, A service provider controlled LCS Client that requires the position information for internal network operations, An LCS Client that is on a semi-permanent list of LCS Clients that have been explicitly authorized by the subscriber to receive the position information, An LCS Client that has received temporary authorization for the position information upon explicit service invocation by the MS user. This authorization applies only to that specific service instance for a limited duration. Unrestricted. Position information for the Target MS may be disclosed to any LCS Client. Table LIR Subscription Options Location Information Restriction (LIR) TIA/EIA- Modifications

30 X.S000-0 v.0 Y.. De-Activation LIR shall be de-activated upon de-authorization. Invocation LIR is invoked when the network attempts to provide position information to an LCS Client. Normal Operation With Successful Outcome When position information is to be sent to the LCS Client, the Target MS Privacy Profile is checked to determine if the LCS Client is authorized to have access to the position information. If such authorization exists, the position information is provided to the LCS Client. If not authorized, the position information is not provided to the LCS Client. Some LCS Clients shall be exempt from LIR: A wireless service provider controlled LCS Client that requires position information for internal network operations, such as:» An LCS Client supporting network operator applications (e.g., customer service).» An LCS Client supporting location-based services where the subscriber identity remains anonymous (e.g., network traffic measurement, network radio engineering).» An LCS Client that is invoked in response to disruption of network operations by a specific MS.» An LCS Client that is invoked in response to a specific MS that fraudulently accesses network services. LCS Clients that have been exempted from the Target MS's location privacy restrictions by regulatory or legal actions, including, in some countries, LCS Clients supporting certain emergency services (e.g., calls to Public Safety agencies). The interaction between LIR and LCS Clients is determined by the home service provider. The Serving service provider may be involved in the interaction between LIR and at least certain LCS Clients. Data Recording The system should record information for LIR rejection of an LCS Client request. Exception Procedures or Unsuccessful Outcome Registration None identified TIA/EIA- Modifications 0 Location Information Restriction (LIR)

31 X.S000-0 v Y.. Y.. De-Registration None identified. Activation None identified. De-Activation None identified. Invocation None identified. Exceptions While Roaming Unconditionally Restricted LIR Mode treatment may be applied to roaming subscribers. Exceptions During Intersystem Handoff None identified. Alternative Procedures None identified. Interactions With Other Wireless Services No interactions have been identified with the following exceptions: Emergency Services (ES) ES takes precedence over LIR. Location Services (LCS) LIR may restrict the release of position information to an LCS Client. Non-Public Service Mode (NP) Interaction is beyond the scope of this standard. Location Information Restriction (LIR) TIA/EIA- Modifications

32 X.S000-0 v.0 TIA/EIA-. MODIFICATIONS This section provides new functional overview information for Location Services Enhancements according to the structure of TIA/EIA--D Chapter. DEFINITIONS AND DOCUMENTATION CONVENTIONS. Definitions Anchor MPC The MPC that is associated with the Anchor MSC for the Target MS. Coarse Position ES (See TIA/EIA-., page ) An estimate of the Target MS's position based upon the identity of the serving cell-sector. Emergency Services ES MPC The MPC that is associated with the serving MSC and which is involved in position determination of a target MS for an Emergency Services Call. ES PDE A PDE that is associated with the serving MSC and which is involved in position determination of a target MS for an Emergency Services Call. Home MPC LCS The MPC that is associated with the Target MS subscriber s Home System and to which the MS s user identity (e.g., directory number, MSID) is assigned for location-based services. Location Services LCS Client An entity (e.g., service control function) that interacts with the network for the purpose of obtaining position information for one or more Target MSs within a set of specified parameters such as PQOS. LCS Clients subscribe to LCS in order to obtain position TIA/EIA-. Modifications Definitions and Documentation Conventions

33 X.S000-0 v LIR information for the purpose of providing location based applications. The LCS Client is responsible for formatting and presenting data and managing the user interface. The LCS Client may reside in the MS. Location Information Restriction Mobile Position Center (MPC) MPC PDE The MPC serves as the point of interface to the wireless network for the position determination network. The MPC serves as the entity which retrieves, forwards, stores, and controls position information within the position network. It can select the PDE(s) to use in position determination and forwards the position estimate to the requesting entity (e.g., LCS Client) or stores it for subsequent retrieval. The MPC may restrict access to position information for a Target MS (e.g., release position information to authorized entities). Mobile Position Center Position Determining Entity Position Determining Entity (PDE) PQOS The PDE facilitates determination of the geographical position of a Target MS. The input to the PDE for requesting the position is a set of parameters such as PQOS requirements and information about the current radio environment of the MS. Multiple PDEs may serve the coverage area of an MPC and multiple PDEs may serve the same coverage area of an MPC utilizing different position determining technologies. Position Quality Of Service Serving MPC The MPC that is associated with the Serving MSC for the Target MS. Target MS VAS The target MS is the MS whose position information is requested by the LCS Client. Value Added Services Definitions TIA/EIA-. Modifications