1、 TIA DOCUMENT TIA/EIA-41-D Location Services Enhancements TIA-881 MARCH 2004 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through
2、 eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Publications shall not in an
3、y respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Publications. Neither shall the existence of such Documents preclude their voluntary use by non-TIA members, either domestically or internationally. TIA DOCUMENTS TIA Documents contain in
4、formation deemed to be of technical value to the industry, and are published at the request of the originating Committee without necessarily following the rigorous public review and resolution of comments which is a procedural part of the development of a American National Standard (ANS). Further de
5、tails of the development process are available in the TIA Engineering Manual, located at http:/www.tiaonline.org/standards/sfg/engineering_manual.cfm TIA Documents shall be reviewed on a five year cycle by the formulating Committee and a decision made on whether to reaffirm, revise, withdraw, or pro
6、ceed to develop an American National Standard on this subject. Suggestions for revision should be directed to: Standards Telecommunications Industry Association; July 2000TTC: JP-3GB-S.R0006, Wireless Features Description; TheTelecommunication Technology Committee; March 2000TIA/EIA-413GPP2: N.S0005
7、, Cellular Radiotelecommunications IntersystemOperationsCCSA: YD/T-1031-1999, Technical Specification of 800 MHzCDMA Digital Cellular Mobile Telecommunication Network MobileApplication Part; Chinese Communications Standards Association;December 1999TIA: TIA/EIA-41-D, Cellular Radiotelecommunications
8、 IntersystemOperations; Telecommunications Industry Association;December 1997TTA: TTAE.3G-N.S0005, Cellular RadiotelecommunicationsIntersystem Operations; Telecommunications TechnologyAssociation; July 2000IS-8013GPP2: C.S0022-0 Version 3.0, Position Determination ServiceStandard for Dual-Mode Sprea
9、d Spectrum Systems; April 2001ARIB: STD-T64-C.S0022-0-1, Position Determination ServiceStandard for Dual-Mode Spread Spectrum Systems; Association ofRadio Industries and BusinessTIA: TIA/EIA/IS-801-1, Position Determination Service Standard forDual-Mode Spread Spectrum Systems Addendum 1;Telecommuni
10、cations Industry Association; March 2001J-STD-034TIA: TIA/EIA J-STD-034, Wireless Enhanced Emergency Services;Telecommunications Industry Association; October 19971.See TIA-843for a description of Wireless Intelligent Network (WIN) Location Based Services.TIA-881Introduction1234567891011121314151617
11、18192021222324252627282930313233343536373839404142434445464748495051525354555657585960Organization2J-STD-036TIA: TIA/EIA J-STD-036-A, Wireless Enhanced Wireless 9-1-1Phase 2; Telecommunications Industry Association; March 2002World Geodetic System 1984 (WGS-84) standardizes latitude and longitude. W
12、GS-84 isthe standard for conversion between local systems, in this case national geodetics andprojection maps.WGS-84World Geodetic System, WGS-84. United States Department ofDefense, MIL-STD-2401, 1984.3 ORGANIZATIONThis document is organized as follows: The TIA/EIA-664Modifications section provides
13、 the additions and modificationsto TIA/EIA-664-A“Wireless Features Descriptions” for Location ServicesEnhancements. The TIA/EIA/41.1Modifications section provides the modifications and additionsto TIA/EIA-41-DChapter 1 “Functional Overview” for Location ServicesEnhancements. The TIA/EIA/41.3Modifica
14、tions section provides the modifications and additionsto TIA/EIA-41-DChapter 3 “Automatic Roaming Information Flows” forLocation Services Enhancements. The TIA/EIA/41.5Modifications section provides the modifications and additionsto TIA/EIA-41-DChapter 5 “Signaling Protocol” for the Location Service
15、sEnhancements. The TIA/EIA/41.6Modifications section provides the modifications and additionsto TIA/EIA-41-DChapter 6 “Signaling Procedures” for Location ServicesEnhancements. Annex A (informative) provides guidance on minimizing the interaction of ValueAdded Services and Emergency Services position
16、 determination when CDMAMS-assisted position determination is used for both.4 ASSUMPTIONSThe following assumptions were used in the development of this document:a. The wireless subscriber may designate a list of LCS Clients that are explicitlyauthorized to obtain position information for the subscri
17、bers MS. This exceptionlist is stored in the wireless subscribers Home MPC.b. A wireless service provider may offer several Location Information Restriction(LIR) mode subscription options. The LIR mode information is stored in thewireless subscribers Home MPC and HLR. The Home MPC is the control poi
18、ntfor the LIR mode information.c. LIR mode information is stored in the wireless subscribers home system and istransferred to the serving system (i.e., Serving VLR, Serving MSC) as part of thesubscriber profile.TIA-8811234567891011121314151617181920212223242526272829303132333435363738394041424344454
19、64748495051525354555657585960Assumptions Introduction3d. The MPC shall use the requested Position Quality of Service (PQOS) value toselect a Position Determining Entity (PDE) that supports the required positionaccuracy.e. Communications between the LCS Client and the MPC can use SS7-based datatransf
20、er services or IP-based data transfer services. This document only illustratesthe use of TIA/EIA-41Mobile Application Part (MAP) protocol forcommunications between the LCS Client and the MPC. However, otherapplication layer protocols may be used for the L1 reference point.f. Communications between M
21、PCs (e.g., Home MPC to Serving MPC) can use SS7-based data transfer services or IP-based data transfer services.g. The LCS Client requests a PQOS level for the geographic position estimate. If theMPC can determine ahead of time that PQOS cannot be met, positiondetermination should not be initiated.
22、If a position estimate is obtained but doesnot 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 trafficchannel for CDMA MS-assisted po
23、sition determination prior to invoking the PDE(i.e., for IS-801message exchange).i. For CDMA MS-assisted position determination, the PDE shall notify the ServingMSC when the IS-801geoposition session has been completed.j. An MPC may cancel an ongoing position determination at a PDE (e.g., because of
24、an emergency services position information request).k. Emergency and Value Added Services may be deployed on separate MPCs. Atmost, one Emergency Services MPC and one Value Added Services MPC may beassociated with a single MSC.l. An MPC expects to receive an InterSystemPositionRequest INVOKE from ak
25、nown LCS Client or from a Home MPC that is requesting the positioninformation for a roaming MS.m. The Serving MPC shall include the LIRAuthorization parameter in theInterSystemPositionRequest INVOKE sent to the Serving MSC when the ServingMPC does not have the Target MS LIR Mode information and the
26、request forposition information was not received from an authorized entity (e.g., the HomeMPC for the Target MS). The presence of the LIRAuthorization parameter in theInterSystemPositionRequest INVOKE indicates that the Serving MSC shallverify that Target MSs LIR Mode permits the MSs position to be
27、determined. Theabsence of the LIRAuthorization parameter in the InterSystemPositionRequestINVOKE directs the Serving MSC to provide the Target MS geographic positioninformation regardless of the Target MSs LIR Mode information.n. Voice services such as call delivery and call origination (including a
28、n EmergencyServices call origination) involving a Target MS shall not be rejected if the TargetMS has already been assigned to a traffic channel for position determination.Traffic channel resources allocated specifically for position determination shall bereleased if the MSC receives a request for v
29、oice services for the same Target MS.o. Coarse positioning can be used to obtain geographic position information for thecell serving the Target MS. This information is useful to services that do notrequire high accuracy geographic position information.TIA-881Introduction12345678910111213141516171819
30、2021222324252627282930313233343536373839404142434445464748495051525354555657585960Assumptions4p. 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 determinethe identity of the serving cell. When t
31、he MS is engaged in a call, coarse positioncan be obtained when the Target MS is in the Anchor System or after intersystemhandoff.q. The association of a PDE with multiple MPCs is not explicitly addressed.r. This document does not support multiple concurrent IS-801CDMA positiondetermination sessions
32、 for a given MS.s. When IS-801CDMA position determination is underway for a Value AddedService, the initiation of an Emergency Services call shall cause the ongoingposition determination processing to be stopped.t. Within the serving network, it is the Serving MPC that coordinates multipleconcurrent
33、 LCS requests received for a given MS. Specifically, in a single ServingMPC per MSC configuration, the Serving MPC handles the interaction betweenconcurrent Emergency Services-related and Value Added Services-related LCSrequests received for the same MS.u.IS-801CDMA position determination may operat
34、e concurrently with otherposition determination technologies for a given MS.v.IS-801preempt capabilityis applicable when an Emergency Services MPC and aseparate VAS MPC are associated with a single MSC. This capability enables anemergency services call that requires CDMA position determination to pr
35、eemptongoing Value Added Service (VAS) CDMA position determination, for a givenMS.IS-801 preempt capabilityis an MSC configuration option and is applicableto all IS-801position determination sessions handled by that MSC. When an MSC is configured for IS-801 preempt capability, an MSC shallsend a Pos
36、itionEventNotification INVOKE to the VAS MPC when the MSCdetects an emergency services call. In cases where VAS positiondetermination has been initiated at an MSC and then handoff has occurred,only the position determination initiating MSC shall send aPositionEventNotification INVOKE to the VAS MPC
37、when it detects anemergency services call. When an MSC is configured for IS-801 preempt capability, the MSC shall“reject” an SMDPPreceived for VAS IS-801CDMA position determinationduring an emergency services call, unless the ActionCode parameterindicating CDMA Handset-Based Position Determination C
38、ompleteisreceived. If a VAS SMDPPindicating CDMA Handset-Based PositionDetermination Completeis received, the MSC shall send any received bearerdata to the indicated MS. When IS-801CDMA position determination has been initiated for anemergency services call, all IS-801data bursts received from the M
39、Sshall be sent to the Emergency Services PDE/MPC. When an MSC is configured for IS-801 preempt capability, the MSC shallrespond negatively to an ISPOSREQreceived from a VAS MPC requestingallocation of a traffic channel for CDMA position determination during anemergency services call.TIA-881123456789
40、101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960Editorial Conventions Introduction5 For Value Added Services (VAS), a PDE shall include an indication of VASin the SMDPPsent to an MSC for IS-801CDMA position determination.IS-801 preempt capability
41、is not applicable when a single MPC is associatedwith an MSC and is used for both Emergency Services and Value AddedServices position determination.w. This document does not support the initiation of a VAS-related IS-801CDMAposition determination session by the transmission of an IS-801message by an
42、MS.x. The MobilePositionCapability (MPCAP) for a Target MS may not be known tothe HLR (associated with the Target MS) and may not be provided to the ServingMPC1. If the Serving MPC does not receive the Target MS MPCAP in the requestfor the Target MS position, the Serving MPC may use local procedures
43、 todetermine the Target MS position and to satisfy the requested PQOS.y. This document does not support intersystem handoff of an MS that has beenassigned to a traffic channel specifically for the purpose of CDMA handset-basedposition determination.z. This document does not address the interactions
44、of CDMA MS-assisted positiondetermination with other non-voice services that use SMSDeliveryPointToPointoperations (e.g., OTA, Short Message Delivery).aa. This document does not specifically address the interactions of LCS and circuit-switched data telecommunications services.ab. This document does
45、not consider the interactions of LCS and packet-switchedtelecommunications services.5 EDITORIAL CONVENTIONSThe following editorial conventions are used for this document: underline: additioncross out: deletion change bar: indicates additions or deletions new sub-sections are identified in the sub-se
46、ction heading for clarity, new sub-sections are shown with vertical change bars but are notunderlined automatic roaming information flows between the LCS Client and MPC areshown in red when: communications between these entities can use SS7-based data transferservices or IP-based data transfer servi
47、ces for IP-based transfer services, the signaling protocol may not be TIA/EIA-41MAP-based1.A MobilePositionCapability parameter may not be received or a MobilePositionCapability parameterindicating Undened Mobile Position Capabilitiesis received.TIA-881Introduction12345678910111213141516171819202122
48、2324252627282930313233343536373839404142434445464748495051525354555657585960Editorial Conventions6 for IP-based data transfer services, the LCS Client may be external to thewireless network automatic roaming information flows between the MPCs are shown in green whencommunications between these entit
49、ies (e.g., Home MPC to Serving MPC) canuse SS7-based or IP-based data transfer servicesTIA-881123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960References TIA/EIA-664 Modications7TIA/EIA-664MODIFICATIONSThis section provides additions and modifications to TIA/EIA-664 required for enhancedLocation Services (LCS).2 REFERENCES2.1 Normative References(see TIA/EIA-664-000, page 3)The following standards contain provisions that, through reference in this text, constituteprovisions of this Standard.At th
