Tia Eia Is 801 1

TIA/EIA
INTERIM STANDARD
TIA/EIA/IS-801-1
Position Determination Service

Standards for Dual Mode Spread
Spectrum Systems
Addendum 1
TIA/EIA/IS-801-1
(Addendum No. 1 to TIA/EIA/IS-801)
MARCH 2001
TELECOMMUNICATIONS INDUSTRY ASSOCIATION
The Telecommunications Industry Association

represents the communications sector of
NOTICE
TIA/EIA Engineering Standards and Publications are designed to serve the public interest through 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 his
particular need. Existence of such Standards and Publications shall not in any respect preclude any member or
nonmember of TIA/EIA from manufacturing or selling products not conforming to such Standards and Publications,
nor shall the existence of such Standards and Publications preclude their voluntary use by those other than TIA/EIA
members, whether the standard is to be used either domestically or internationally.
Standards and Publications are adopted by TIA/EIA in accordance with the American National Standards Institute
(ANSI) patent policy. By such action, TIA/EIA does not assume any liability to any patent owner, nor does it assume
any obligation whatever to parties adopting the Standard or Publication.
Note: The user’s attention is called to the possibility that compliance with this document may require use
of one or more inventions covered by patent rights.
By publication of this standard, Interim Standard, or TSB, no position is taken with respect to the validity of
those claims or of any patent rights in connection therewith. The patent holder(s) so far identified have,
however, filed statements of willingness to grant licenses under those rights on reasonable and
nondiscriminatory terms and conditions to applicants desiring to obtain such licenses. Details may be
obtained from the standards developer.
TIA/EIA INTERIM STANDARDS
TIA/EIA Interim Standards contain information 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 TIA/EIA Standard.
TIA/EIA Interim Standards should be reviewed on an annual basis by the formulating Committee and a decision made
on whether to proceed to develop a TIA/EIA Standard on this subject. TIA/EIA Interim Standards must be cancelled
by the Committee and removed from the TIA/EIA Standards Catalog before the end of their third year of existence.
Publication of this TIA/EIA Interim Standard for trial use and comment has been approved by the
Telecommunications Industry Association. Distribution of this TIA/EIA Interim Standard for comment shall not
continue beyond 36 months from the date of publication. It is expected that following this 36 month period, this
TIA/EIA Interim Standard, revised as necessary, will be submitted to the American National Standards Institute for
approval as an American National Standard. Suggestions for revision should be directed to: Standards & Technology
Department, Telecommunications Industry Association, 2500 Wilson Boulevard, Arlington, VA 22201.
(From Project No. 4535-AD1, formulated under the cognizance of the TIA TR-45.5 Subcommittee on Spread Spectrum
Digital Technology.)
Published by
TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2001

Standards & Technology Department
2500 Wilson Boulevard
Arlington, VA 22201
PRICE: Please refer to current Catalog of

EIA ELECTRONIC INDUSTRIES ALLIANCE STANDARDS and ENGINEERING PUBLICATIONS or call Global
Engineering Documents, USA and Canada
(1-800-854-7179) International (303-397-7956)
All rights reserved

Printed in U.S.A.
PLEASE!
DON'T VIOLATE
THE
LAW!
This document is copyrighted by the TIA and may not be reproduced without
permission.
Organizations may obtain permission to reproduce a limited number of copies

through entering into a license agreement. For information, contact:
Global Engineering Documents

15 Inverness Way East
Englewood, CO 80112-5704 or call
U.S.A. and Canada 1-800-854-7179, International (303) 397-7956
TIA/EIA/IS-801-1
CONTENTS
1 1 GENERAL....................................................................................................................... 1-1
2 1.1 Terms....................................................................................................................... 1-1
3 2 MESSAGE TRANSPORT PROTOCOL .............................................................................. 2-1
4 2.1 Analog Transport Protocol........................................................................................ 2-1
5 2.2 CDMA Transport Protocol ........................................................................................ 2-1
6 2.2.1 Session Tags ...................................................................................................... 2-1
7 3 MOBILE STATION PROCEDURES.................................................................................. 3-1
8 3.1 Analog Mobile Station Procedures............................................................................ 3-1
9 3.2 CDMA Mobile Station Procedures ............................................................................ 3-1
10 3.2.1 Position Determination Data Message Processing.............................................. 3-1
11 3.2.1.1 Overview ...................................................................................................... 3-1
12 3.2.1.2 Requirements .............................................................................................. 3-2
13 3.2.2 Point-to-point Procedures .................................................................................. 3-5
14 3.2.2.1 Control Channel Procedure ......................................................................... 3-5
15 3.2.2.1.1 Mobile Station Position Determination Data Message Termination ....... 3-5
16 3.2.2.1.1.1 Base Station Request Elements Received ........................................ 3-5
17 3.2.2.1.1.2 Base Station Response Elements Received...................................... 3-9
18 3.2.2.1.2 Mobile Station Position Determination Data Message Origination....... 3-10
19 3.2.2.1.2.1 Position Determination Data Message Transmission Requirements…
20 ........................................................................................................................ 3-10
21 3.2.2.1.2.2 Unsolicited Response Elements..................................................... 3-10
22 3.2.2.1.2.3 Request Elements ......................................................................... 3-11
23 3.2.2.2 Authentication Procedures ........................................................................ 3-11
24 3.2.2.3 Traffic Channel Procedure ......................................................................... 3-11
25 3.2.2.3.1 Message Encryption ............................................................................ 3-11
26 3.2.2.3.2 Negotiation for the Position Determination Service Option .................. 3-11
27 3.2.2.3.2.1 Procedures Using Service Negotiation ........................................... 3-11
28 3.2.2.3.3 Mobile Station Position Determination Data Message Termination ..... 3-13
29 3.2.2.3.3.1 Base Station Request Elements Received ...................................... 3-13
30 3.2.2.3.3.2 Base Station Response Elements Received.................................... 3-17
31 3.2.2.3.4 Traffic Channel Setup ......................................................................... 3-17
i
TIA/EIA/IS-801-1
CONTENTS
1 3.2.2.3.5 Mobile Station Position Determination Data Message Origination in the
2 Conversation Substate ....................................................................................... 3-18
4 ........................................................................................................................ 3-18
7 3.2.3 Broadcast Procedures ...................................................................................... 3-19
8 3.2.4 Reverse Link Message Format.......................................................................... 3-19
9 3.2.4.1 Request Element Parameters Record......................................................... 3-23
10 3.2.4.2 Response Element Parameters Record....................................................... 3-27
11 4 BASE STATION PROCEDURES .................................................................................... 4-52
12 4.1 Analog Base Station Procedures ............................................................................ 4-52
13 4.2 CDMA Base Station Procedures ............................................................................. 4-52
14 4.2.1 Position Determination Data Message Processing............................................ 4-52
15 4.2.1.1 Overview .................................................................................................... 4-52
16 4.2.1.2 Requirements .............................................................................................. 4-2
17 4.2.2 Point-to-point Procedures .................................................................................. 4-5
18 4.2.2.1 Control Channel Procedure ......................................................................... 4-5
19 4.2.2.1.1 Base Station Position Determination Data Message Termination .......... 4-5
20 4.2.2.1.1.1 Mobile Station Request Elements Received ..................................... 4-5
21 4.2.2.1.1.2 Mobile Station Response Elements Received................................... 4-8
22 4.2.2.1.2 Base Station Position Determination Data Message Origination ........... 4-8
24 .......................................................................................................................... 4-8
25 4.2.2.1.2.2 Unsolicited Response Elements....................................................... 4-9
26 4.2.2.1.2.3 Request Elements ........................................................................... 4-9
27 4.2.2.2 Authentication Procedures .......................................................................... 4-9
28 4.2.2.3 Traffic Channel Procedure ........................................................................... 4-9
29 4.2.2.3.1 Message Encryption .............................................................................. 4-9
30 4.2.2.3.2 Negotiation for the Position Determination Service Option .................. 4-10
31 4.2.2.3.2.1 Procedures Using Service Negotiation ........................................... 4-10
32 4.2.2.3.3 Base Station Position Determination Data Message Termination ........ 4-10
33 4.2.2.3.3.1 Mobile Station Request Elements Received ................................... 4-11
ii
TIA/EIA/IS-801-1
CONTENTS
1 4.2.2.3.3.2 Mobile Station Response Elements Received................................. 4-13
2 4.2.2.3.4 Traffic Channel Setup ......................................................................... 4-14
3 4.2.2.3.5 Base Station Position Determination Data Message Origination in the
4 Conversation Substate ....................................................................................... 4-14
6 ........................................................................................................................ 4-14
9 4.2.3 Broadcast Procedures ...................................................................................... 4-15
10 4.2.4 Forward Link Message Format......................................................................... 4-15
11 4.2.4.1 Request Element Parameters Record......................................................... 4-19
12 4.2.4.2 Response Element Parameters Record....................................................... 4-23
13 Annex A – TIMERS ............................................................................................................ A-1
14 Annex B – REQUEST/RESPONSE ELEMENT TYPES ........................................................B-1
15 Annex C – EXAMPLE POSITION DETERMINATION DATA MESSAGE................................C-1
16 Annex D – INFORMATIVE ANNEX ON SESSION TAGS .....................................................D-1
iii
TIA/EIA/IS-801-1
TABLES
1 Table 3.2.1.2-1. Response Elements Sent in Response to Received Request Elements .... 3-4
2 Table 3.2.2.3.2.1-1. Valid Service Configuration Attributes for Service Option 35 ......... 3-12
3 Table 3.2.2.3.2.1-2. Valid Service Configuration Attributes for Service Option 36 ......... 3-12
4 Table 3.2.4-1. Reverse Link Messages ............................................................................ 3-19
5 Table 3.2.4-2. Request Element Type ............................................................................. 3-22
6 Table 3.2.4-3. Response Element Type........................................................................... 3-23
7 Table 3.2.4.2-1. Reject Reason ....................................................................................... 3-28
8 Table 3.2.4.2-2. Pilot Phase Capability........................................................................... 3-29
9 Table 3.2.4.2-3. Mapping Table for GPS Acquisition Capability ..................................... 3-29
10 Table 3.2.4.2-4. Mapping Table for Position Calculation Capability ............................... 3-30
11 Table 3.2.4.2-5. Inverse of Weighting Factor Representation ......................................... 3-32
12 Table 3.2.4.2-6. Time Reference Source ......................................................................... 3-34
13 Table 3.2.4.2-7. Multipath Indicator .............................................................................. 3-36
14 Table 3.2.4.2-8. Pseudorange RMS Error Representation .............................................. 3-37
15 Table 3.2.4.2-9. RMS Error in Pilot Phase Measurement Representation....................... 3-43
16 Table 3.2.4.2-10. Position Uncertainty ........................................................................... 3-47
17 Table 4.2.1.2-1. Response Elements Sent in Response to Received Request Elements .... 4-4
18 Table 4.2.4-1. Forward Link Messages ........................................................................... 4-15
19 Table 4.2.4-2. Request Element Type ............................................................................. 4-18
20 Table 4.2.4-3. Response Element Type........................................................................... 4-19
21 Table 4.2.4.2-1. Reject Reason ....................................................................................... 4-24
22 Table 4.2.4.2-2. Autonomous Location Determination Capability in the Base Station ... 4-26
23 Table 4.2.4.2-3. Reference PN ........................................................................................ 4-29
24 Table 4.2.4.2-4. DOPPLER_WIN Parameter Format........................................................ 4-30
25 Table 4.2.4.2-5. Code Phase Search Window Parameter Format .................................... 4-32
26 Table 4.2.4.2-6. Position Uncertainty ............................................................................. 4-57
27 Table A-1. Time Limits .....................................................................................................A-1
28 Table B-1. MS Requests and BS Responses .....................................................................B-1
29 Table B-2. MS Responses and BS Requests .....................................................................B-1
30 Table C-1. Bit Field of the Position Determination Data Message.....................................C-1
iv
TIA/EIA/IS-801-1
FOREWORD
1 (This foreword is not part of this standard)

2 This Standard was prepared by Telecommunications Industry Association Subcommittee
3 TR45.5, Spread Spectrum Digital Technology - Mobile and Personal Communications
4 Standards.
5 This standard is an adjunct standard to TIA/EIA-95-B, Mobile Station-Base Station
6 Compatibility Standard for Dual-Mode Spread Spectrum Systems or TIA/EIA/IS-2000-5,
7 Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems. This
8 standard defines a set of signaling messages between the mobile station and base station to
9 provide a position determination service.
10 This standard consists of the following sections:
11 1. General. This section defines the terms and numeric indications used in this document.
12 2. Message Transport Protocol. This section defines the transport protocol used between
13 the mobile station and base station.
14 3. Mobile Station Procedures. This section describes the procedures used by the mobile
15 station to process messages received from the base station and to send messages to the
16 base station. This section also specifies the message formats for messages sent from the
17 mobile station to the base station.
18 4. Base Station Procedures. This section describes the procedures used by the base
19 station to process messages received from the mobile station and to send messages to the
20 mobile station. This section also specifies the message formats for messages sent from the
21 base station to the mobile station.
22 Annex A. This section provides values from various timers used in the standard.
23 Annex B. This section provides the summary tables of the request/response element
24 types.
25 Annex C. This section provides an example of the Position Determination Data Message.
26 Annex D. This section provides information regarding session tags.
27
v
TIA/EIA/IS-801-1
REVISION HISTORY
2 12/04/2000 Addendum 1 Incorporated

3
vi
TIA/EIA/IS-801-1
NOTES
1 1. For purposes of this standard, “shall” and “shall not” identify requirements to be
2 followed strictly to conform to the standard, and from which no deviation is
3 permitted. “Should” and “should not” indicate that one of several possibilities is
4 recommended as particularly suitable, without mentioning or excluding others; that
5 a certain course of action is preferred, but not necessarily required; or (in negative
6 form) that a certain possibility or course of action is discouraged, but not
7 prohibited. “May” and “may not” indicate a course of action permissible within the
8 limits of this standard. “Can” and “cannot” are used for statements of possibility
9 and capability, whether material, physical or causal.
10 2. The terms “location” and “position” are used interchangeably throughout this
11 document. In this respect the definition of the term differs from the historic use of
12 location in wireless systems to identify the mobile’s current serving system.
13 3. Those wishing to deploy systems in the United States should also take notice of the
14 requirement to be compliant with Federal Communications Commission (FCC)
15 Rulings on 911 Emergency Services.
16 4. “Base station” refers to the functions performed on the land side, which are typically
17 distributed among a Base Station Transceiver (BTS), a Base Station Controller
18 (BSC), a Mobile Switching Center (MSC), Mobile Positioning Center (MPC), Position
19 Determination Entity (PDE) and any Inter-Working Function (IWF) required for
20 network connection. These elements are grouped together, because there is no need
21 to distinguish them in an air interface standard. See TSB-100 Wireless Reference
22 Model and Enhanced Wireless 9-1-1 Phase 2.
23 5. Footnotes appear at various points in this specification to elaborate and to further
24 clarify items discussed in the body of the specification.
25 6. Unless indicated otherwise, this document presents numbers in decimal form.
26 Binary numbers are distinguished in the text by the use of single quotation marks.
27 7. The following operators define mathematical operations:
28 × indicates multiplication.
29 x indicates the largest integer less than or equal to x: 1.1 = 1, 1.0 = 1.
30 x indicates the smallest integer greater or equal to x: 1.1 = 2, 2.0 = 2.
31 |x| indicates the absolute value of x: |-17|=17, |17|=17.
32 ⊕ indicates exclusive OR (modulo-2 addition).
33 min (x, y) indicates the minimum of x and y.
34 max (x, y) indicates the maximum of x and y.
35 x mod y indicates the remainder after dividing x by y: x mod y = x - (y × x/y).
36 8. References in this document are to TIA/EIA-95-B. This standard is equally
37 applicable to TIA/EIA/IS-2000. Except where explicit references are made to
38 TIA/EIA/IS-2000, the reference to TIA/EIA-95-B can be converted directly to
39 TIA/EIA/IS-2000 usage.
vii
TIA/EIA/IS-801-1
NOTES
1 9. Wherever this document refers to CDMA System time in frames, it is taken to mean
2 an integer value t such that: t = s/0.02, where s represents System Time in
3 seconds.
viii
TIA/EIA/IS-801-1
REFERENCES
1 The following standards contain provisions, which, through reference in this text,
2 constitute provisions of this standard. At the time of publication, the editions indicated
3 were valid. All standards are subject to revision, and parties to agreements based on this
4 standard are encouraged to investigate the possibility of applying the most recent editions
5 of the standards indicated below. ANSI and TIA maintain registers of currently valid
6 national standards published by them.
7
8 1. TIA/EIA-95-B, Mobile Station-Base Station Compatibility Standard for Dual-Mode

9 Spread Spectrum Systems, March 1999.
10 2. TIA/EIA/TSB58-B, Administration of Parameter Value Assignments for TIA/EIA
11 Spread Spectrum Standards, August 1999.
12 3. ICD-GPS-200C, Navstar GPS Space Segment / Navigation User Interfaces, September
13 1997.
14 4. DMA TR 8350.2, Defense Mapping Agency Publication, September 30, 1987.
15 5. J-STD-036, Enhanced Wireless 9-1-1 Phase 2, June 2000.
16 6. TIA/EIA/IS-817 A Position Determination Service Standard for Analog Systems, July
17 2000.
18 7. TSB-100, Wireless Network Reference Model, July 1998.
19 8. TIA/EIA/IS-2000-1, Introduction to cdma2000 Standards for Spread Spectrum
20 System, July 1999.
21 9. TIA/EIA/IS-2000-2, Medium Access Control (MAC) Standards for cdma2000 Spread
22 Spectrum Systems, July 1999.
23 10. TIA/EIA/IS-2000-3, Signaling Link Access Control (LAC) Standard for cdma2000
24 Spread Spectrum Systems, July 1999.
25 11. TIA/EIA/IS-2000-4, Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread
27 12. TIA/EIA/IS-2000-5, Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread
29 13. TIA/EIA/IS-2000-6, Analog Signaling Standard for cdma2000 Spread Spectrum
30 Systems, July 1999.
ix
TIA/EIA/IS-801-1
1 No text.
2
x
TIA/EIA/IS-801-1
1 1 GENERAL
2 1.1 Terms
3 2D Fix. A two-dimensional (latitude and longitude) position determination process.
4 3D Fix. A three-dimensional (latitude, longitude and height) position determination
5 process.
6 Advanced Forward Link Trilateration (AFLT). A geolocation technique that utilizes the
7 mobile station’s measured time of arrival of radio signals from the base stations (and,
8 possibly, other terrestrial measurements).
9 AFLT. See Advanced Forward Link Trilateration.
10 Almanac. See GPS Almanac.
11 Alpha. See Alpha, Beta Parameters.
12 Alpha, Beta Parameters. Ionospheric parameters which allow the “L1 only” user to utilize
13 the ionospheric mode for computation of ionospheric delay are contained in page 18 of
14 subframe 4 of GPS navigation data.
15 Angle of Axis for Position Uncertainty. Position uncertainty is represented as a 1-σ (one
16 standard deviation) ellipse. This angle is the angle of one of the ellipse’s axes with respect
17 to True North.
18 Assistance Data. The assistance data provided by the base station to the mobile station
19 for various purposes (e.g., acquisition, location calculation or sensitivity improvement).
20 Authentication. A procedure used by a base station to validate a mobile station’s identity.
21 Autonomous Mobile Station. A mobile station that is capable of detecting a navigation
22 signal without any help from the base station. The mobile station may be capable of
23 autonomously calculating its own position.
24 Autonomous Base Station. A base station capable of determining the location of the
25 mobile station without requiring any cooperation from the mobile station.
26 Azimuth. An angle that specifies a direction in the horizontal plane, expressed in degrees
27 measured clockwise from True North.
28 Bad Satellite. Bad satellite is one that is unusable for position calculation. See Satellite
29 Health.
30 Base Station. The base station includes the transceiver equipment, Mobile Switching
31 Center (MSC), Mobile Positioning Center (MPC), Position Determination Entity (PDE) and
32 any Inter-Working Function (IWF) required for network connection.
33 Base Station Almanac. The location and reference time correction for a collection of base
34 stations in the immediate neighborhood of the mobile station (the size of the immediate
35 neighborhood is a service provider option).
36 Beta. See Alpha, Beta Parameters.
1-1
TIA/EIA/IS-801-1
1 C/A Code. Coarse/Acquisition code used for spectral spreading of the GPS signal.
2 C/A Code Chip. The interval defined by the chipping (spreading) rate of the GPS C/A code.
3 Stated as a time interval, one chip equals approximately 977.5 ns; as a distance it is
4 approximately 293.0 m.
5 C/N0. The ratio of carrier signal power (C) to the power spectral density of background
6 noise (N0).
7 CDMA Code Boundary. The point in time where the system time modulo the PN code
8 period is precisely zero.
9 CDMA System Time. All base station digital transmissions are referenced to a common
10 CDMA system-wide time scale that uses the Global Positioning System (GPS) time scale,
11 which is traceable to and synchronous with Universal Coordinated Time (UTC). GPS and
12 UTC differ by an integer number of seconds, specifically the number of leap second
13 corrections added to UTC since January 6, 1980. The start of CDMA System Time is
14 January 6, 1980 00:00:00 UTC, which coincides with the start of GPS time. (See
15 TIA/EIA/95-B Section 1.2). Note that if the CDMA baseband transmit signal is modeled as
16 a complex impulse train passed through a symmetric non-causal filter, then the precise
17 zero instant of system time modulo the pilot PN sequence code period is given by the
18 midpoint between the impulse representing the last element of the pilot PN sequence and
19 the subsequent impulse representing the first element of the pilot PN sequence. The
20 impulse train represents the pilot PN sequence, where the impulses are separated by
21 exactly one PN code chip. The symmetric non-causal filter represents the baseband filter
22 shape prior to the pre-equalization filter.
23 Clock Bias. The difference between the GPS System Time and the local time in the mobile
24 station.
25 Clock Drift. The rate of change of the clock bias.
26 Code Phase. At a given time, the code phase is the fraction of the code period that has
27 elapsed since the latest code boundary (GPS or CDMA).
28 Code Phase Search Window. The expected range of possible code phase values.
29 DGPS. Differential GPS.
th th
30 Doppler n Order. The n order moment specifying a satellite’s observed Doppler.
31 Doppler Search Window. The expected range of possible Doppler values.
32 ECEF. “Earth-Centered-Earth-Fixed”. A frame of reference for specifying positions that is
33 centered in the center of the Earth and rotates with it.
34 Elevation Angle. The angle between a (GPS) satellite and the horizon, expressed in
35 degrees.
36 Ephemeris. The ephemeris data embedded in the GPS signal. The precise (high accuracy)
37 orbital parameters of one GPS satellite, as transmitted by that satellite in GPS subframes 1,
38 2, and 3. The ephemeris also includes satellite clock correction.
1-2
TIA/EIA/IS-801-1
1 Extended Base Station Almanac. The location and reference time correction for a
2 collection of base stations in the extended neighborhood of the mobile station (the size of
3 the extended neighborhood is a service provider option).
4 Fix. The process of performing position computation.
5 Frame. See GPS Navigation Message Frame.
6 Geolocation. The process of determining a geographic location.
7 GPS. Global Positioning System.
8 GPS Almanac. The almanac data embedded in the GPS signal. The almanac data are a
9 reduced-precision subset of the clock and ephemeris parameters for all satellites, as
10 transmitted by every satellite in GPS subframes 4 and 5.
11 GPS Code Boundary. The point in time where the system time modulo the C/A code
12 period is precisely zero.
13 GPS Navigation Message Frame. A GPS navigation message frame contains five
14 subframes. Subframes 1 through 3 contain ephemeris information, subframes 4 and 5
15 contain message and almanac information.
16 GPS Navigation Message Subframe. One of the five GPS subframes of the GPS navigation
17 message. Subframe is 300-bits long.
18 GPS Navigation Message Superframe. A GPS navigation message superframe consists of
19 25 frames and has a duration of 12.5 minutes.
20 ICD. Interface Control Document.
21 IWF. InterWorking Function. A network entity enabling interactions between network
22 elements, such as interactions between an MSC and a landline function. The IWF usually
23 performs protocol conversions as its primary function.
24 Legacy Terminal. A mobile station that is not compliant with the messages defined in this
25 document.
26 Location. The terms “location” and “position” are used interchangeably throughout this
27 document. In this respect, the definition of the term differs from the historic use of location
28 in wireless systems to identify the mobile’s current serving system. See Position.
29 LSB. Least Significant Bit.
30 MPC. Mobile Positioning Center: The network entity that serves as the point of interface of
31 the wireless network for the exchange of geographic position information.
32 Mobile Station (MS). A station that communicates with the base station.
33 Mobile Station Originated Message. A message originating from a mobile station.
34 Mobile Station Terminated Message. A message received by a mobile station.
35 Mobile Switching Center (MSC). A configuration of equipment that provides cellular
36 radio-telephone service. Also called the Mobile Telephone Switching Office (MTSO).
37 ms. Millisecond (10-3 second).
1-3
TIA/EIA/IS-801-1
1 MS. See Mobile Station.

2 MSB. Most Significant Bit.
3 MSC. See Mobile Switching Center.
4 Navigation Message Bits. The message bits (50 bits per second) transmitted by GPS
5 satellites, containing the satellite clock, ephemeris, almanac and other parameters.
6 ns. Nanosecond (10-9 second).
7 PDE. See Position Determination Entity.
8 PN Offset. The PN offset measured in units of 64 PN chips of a pilot, relative to the zero-
9 offset pilot PN sequence.
10 Position. The geographic position of the mobile station expressed in latitude and
11 longitude.
12 Position Determination Entity (PDE). A network entity which manages the position or
13 geographic location determination of the mobile station.
14 ppb. Parts per billion.
15 Pseudodoppler. The measured Doppler frequency shift in the signal received from the GPS
16 satellite. Since the satellite and receiver clock drifts are included, it is referred to as
17 pseudodoppler.
18 Pseudorange. The measured range (in GPS chip) from the observed satellite to the GPS
19 receiver antenna. Since the satellite and receiver clock biases are included, it is referred to
20 as pseudorange.
21 Push. An unsolicited response.
22 Reference Bit Boundary. A boundary between two 20-ms GPS bit intervals chosen as the
23 reference point for code phases.
24 s. Second.
25 Satellite Health. Satellite health is the information identifying a satellite as usable for
26 position calculation.
27 Sensitivity. The minimum level (dBm) of received GPS signal at mobile station that allows
28 the determination of the geolocation of the mobile station.
29 Subframe. See GPS Navigation Message Subframe.
30 Superframe. See GPS Navigation Message Superframe.
31 SV. Space Vehicle; a way of referring to one of the GPS satellites; note SV will often be
32 used in this context as part of a message name, so the message is associated with a
33 satellite.
34 PRN Number. The GPS PRN signal number as defined in ICD-GPS-200C, table 3-I.
35 Time of Arrival. The time occurrence, as measured at the mobile station antenna
36 connector, of the earliest arriving usable multipath component of the signal.
1-4
TIA/EIA/IS-801-1
1 Unsolicited Response. A response element that is issued in the absence of the

2 corresponding request element.
3 Weighting Factor. Weighting factor is a weight applied to the GPS measurement as part of
4 a Weighted Least Squares Filter (WLSF) implementation of the navigation algorithm used by
5 the Mobile Station to compute its position.
6 WGS-84. World Geodetic System - 1984.
7 WGS-84 reference ellipsoid. Worldwide datum reference system defining the surface of
8 the Earth (note: Supersedes WGS-72), i.e., the standard physical model of the Earth used
9 for GPS applications. Ellipsoid reference models are location specific and may be obtained
10 from Defense Mapping Agency publication DMA TR 8350.2 (September 30, 1987).
11 WLSF. Weighted Least Squares Filter navigation algorithm.
12
1-5
TIA/EIA/IS-801-1
1 2 MESSAGE TRANSPORT PROTOCOL

2 Position Determination Data Messages (see 3 and 4) can be sent over the CDMA Traffic
3 Channel or the CDMA Control Channel. Position Determination Data Messages are sent
4 using a Layer-2 protocol that provides reliable delivery and duplicate detection.
5 2.1 Analog Transport Protocol

6 The analog transport protocol is defined in [6].
7 2.2 CDMA Transport Protocol

8 The message defined in 3.2.4 and 4.2.4 shall be sent in the CHARi fields of Data Burst
9 Messages (see 6.7.1.3.2.3, 6.7.2.3.2.4, 7.7.2.3.2.9 and 7.7.3.3.2.4 of TIA/EIA-95-B). The
10 BURST_TYPE field of Data Burst Messages carrying Position Determination Data Messages
11 shall be set to ‘000101’ (as assigned in TSB58-B). The MSG_NUMBER and NUM_MSGS
12 fields shall be set to 1 and the NUM_FIELDS fields shall be set to the number of octets in
13 the Position Determination Data Message. Data Burst Messages carrying Position
14 Determination Data Message shall be sent as messages requiring Layer-2 acknowledgement
15 (see 6.6.4.1.3.1 and 7.6.4.1.3.1 of TIA/EIA-95-B).
16 2.2.1 Session Tags

17 The first CHARi field of each Data Burst Message of BURST_TYPE ‘000101’ is intended to
18 identify groups of Position Determination Data Messages that are related to one another.
19 The purpose is to assist the network in routing the data to the proper destination. See
20 Annex D.
21 Two Position Determination Data Messages are defined to be related, and the elements or
22 parts of elements they contain are defined to be related if any of the following is true.
23 • One Position Determination Data Message contains a request element and the other
24 Position Determination Data Message contains the associated response element or
25 part of the associated response element.
26 • One Position Determination Data Message contains part of a response element and
27 the other Position Determination Data Message contains another part of the same
1
28 response element.
29 • The sending entity (mobile station or base station) of a Position Determination Data
30 Message had previously received or previously sent another Position Determination
31 Data Message, and the two Position Determination Data Messages contain elements
32 that are related. The criteria for determining if a relation exists are defined by the
33 sending entity in an implementation-dependent fashion.
1
This definition covers unsolicited responses that are divided into several parts in different
messages.
2-1
TIA/EIA/IS-801-1
1 The structure of the first CHARi field is detailed in 3.2.4 and 4.2.4. It includes a session
2 tag (SESS_TAG) and three flags. Procedures for assigning a value to SESS_TAG are also
3 detailed in 3.2.4 and 4.2.4.
4 All request elements, response elements, and parts of response elements that are related
5 should, if possible, be included in the same Position Determination Data Message. A
6 Position Determination Data Message shall only include request elements, response
7 elements, or parts of response elements that are mutually related.
2-2
TIA/EIA/IS-801-1
1 3 MOBILE STATION PROCEDURES
2 3.1 Analog Mobile Station Procedures

3 The analog mobile station procedures are defined in [6].
4 3.2 CDMA Mobile Station Procedures
5 3.2.1 Position Determination Data Message Processing
6 3.2.1.1 Overview
7 The Position Determination Data Message sent by the mobile station is comprised of request
8 elements and response elements, as specified below.
9 Request elements sent by mobile station:
10 • Request BS Capabilities
11 • Request GPS Acquisition Assistance
12 • Request GPS Location Assistance
13 • Request GPS Sensitivity Assistance
14 • Request Base Station Almanac
15 • Request GPS Almanac
16 • Request GPS Ephemeris
17 • Request GPS Navigation Message Bits
18 • Request Location Response
19 • Request GPS Almanac Correction
20 • Request GPS Satellite Health Information
21 Response elements sent by mobile station:
22 • Reject
23 • Provide MS Information
24 • Provide Autonomous Measurement Weighting Factors
25 • Provide Pseudorange Measurement
26 • Provide Pilot Phase Measurement
27 • Provide Location Response
28 • Provide Time Offset Measurement
29 • Provide Cancellation Acknowledgement
30 The Position Determination Data Message received by the mobile station is also comprised of
31 request elements and response elements, as specified below.
3-1
TIA/EIA/IS-801-1
1 Request elements received by mobile station:

2 • Request MS Information
3 • Request Autonomous Measurement Weighting Factors
4 • Request Pseudorange Measurement
5 • Request Pilot Phase Measurement
7 • Request Time Offset Measurement
8 • Request Cancellation
9 Response elements received by mobile station:
10 • Reject
11 • Provide BS Capabilities
12 • Provide GPS Acquisition Assistance
13 • Provide GPS Location Assistance – Spherical Coordinates
14 • Provide GPS Location Assistance – Cartesian Coordinates
15 • Provide GPS Sensitivity Assistance
16 • Provide Base Station Almanac
17 • Provide GPS Almanac
18 • Provide GPS Ephemeris
19 • Provide GPS Navigation Message Bits
21 • Provide GPS Almanac Correction
22 • Provide GPS Satellite Health Information
23 Response elements sent by the mobile station may be generated in response to request
24 elements received by the mobile station or they may be generated as unsolicited response
25 elements. Every request element includes a REQ_TYPE (request element type) field that
26 uniquely identifies the request element (See Table 3.2.4-2). Every response element
27 includes a RESP_TYPE (response element type) field that uniquely identifies the response
28 element (See Table 3.2.4-3). Multiple response elements may be associated with a single
29 request element. Unsolicited response elements are sent with the UNSOL_RESP flag set to
30 ‘1’ (see 3.2.4).
31 3.2.1.2 Requirements
32 Each Position Determination Data Message shall contain at least one request element, or at
33 least one part of a response element, or both. No more than one request element of a
34 specific REQ_TYPE shall be included in a Position Determination Data Message. Each
35 request element shall be fully contained in a Position Determination Data Message. Some
3-2
TIA/EIA/IS-801-1
1 response elements may be divided into parts (see 3.2.4.2). Each response element part
2 shall be fully contained in a Position Determination Data Message. All Position
3 Determination Data Messages shall be no larger than 200 bytes.
4 If the mobile station sends a response element in response to a received request element, it
5 shall comply with Table 3.2.1.2-1. A “Reject” shall not be sent as a response element to a
6 “Request MS Information” request element. A “Reject” shall not be sent as a response
7 element to a “Request Cancellation” request element.
8 NOTE: The reader of this document should be aware that the request for the geographical
9 location of the mobile station may be in the context of an emergency call, for example E911
10 in the United States; however, a “Reject” should not be sent as a response element to any
11 request elements that are recognized by the mobile station to be associated with an
12 emergency position location session, if the requested capability is supported by the mobile
13 station.
14 If one or more response elements from the mobile station can be useful to the base station
15 in responding to a request from the mobile station, the mobile station should include all or
16 part of each response element and the request element in the same Position Determination
17 Data Message.
18 Upon receiving a Position Determination Data Message, the mobile station should examine
2
19 the received response elements prior to processing the request elements.
2
Consider, for example, the case in which a base station asks a mobile station for a
location fix while, at the same time, providing acquisition assistance that is needed to
achieve the fix. In that case, the base station would issue a Position Determination Data
Message containing both the request for a location fix (Request Location Response
message) and an unsolicited response with the acquisition assistance (Provide GPS
Acquisition Assistance message). Sending a message with both the request and response
avoids the additional exchange of messages that would otherwise occur if the mobile station
had to issue a request for acquisition assistance and wait for the response. However, for
this example to work correctly, the mobile station must be aware that the acquisition
assistance is available when it processes the request for a fix; hence, the recommendation
that response elements should be “examined” prior to processing the request elements.
3-3
TIA/EIA/IS-801-1
1 Table 3.2.1.2-1. Response Elements Sent in Response to Received Request Elements
Request element received Possible response elements

Request MS Information Provide MS Information
Request Autonomous Measurement Reject
Weighting Factors Provide Autonomous Measurement
Weighting Factors
Request Pseudorange Measurement Reject
Provide Pseudorange Measurement
Request Pilot Phase Measurement Reject
Provide Pilot Phase Measurement
Request Location Response Reject
Provide Location Response
Request Time Offset Measurement Reject
Provide Time Offset Measurement
Request Cancellation Provide Cancellation
Acknowledgement
3 No more than one request element shall be outstanding at any given time for each
4 REQ_TYPE in any given session. If an additional request element is received while there is
5 an outstanding request element of the same type in the same session, the additional
6 request element shall be discarded. A received request element is considered outstanding
7 until all of the corresponding response elements or a “Reject” have been sent or until a
8 “Request Cancellation” for the request element has been received. The mobile station
9 should wait T9 (see ANNEX A) seconds for a response or a “Reject” to a sent request
10 element; after T9 seconds the request element should no longer be considered outstanding.
11 Unsolicited response elements shall have the UNSOL_RESP flag set to ‘1’. If the mobile
12 station while in the Mobile Station Idle State performs an idle handoff (see section 6.6.2.1.4
13 of TIA/EIA-95B) to a base station with different SID/NID, it shall discard all of the
14 outstanding request elements. If the mobile station switches from an analog system to a
15 CDMA system or switches from a CDMA system to an analog system, the mobile station
16 shall discard all of the outstanding request elements. If the mobile station, while in the
17 Mobile Station Conversation Substate of Mobile Station Control on the Traffic Channel State,
18 performs a handoff (see section 6.6.6.2.9 of TIA/EIA-95B) to an analog system, the mobile
19 station shall discard all of the outstanding request elements.
20 If a “Reject” constitutes the response element, its REJ_REQ_TYPE shall be set to the
21 REQ_TYPE of the corresponding request element.
3-4
TIA/EIA/IS-801-1
1 3.2.2 Point-to-point Procedures

2 This section defines the procedures for the processing of mobile-terminated Position
3 Determination Data Messages that are addressed to individual mobile stations and for the
4 processing of all mobile-originated Position Determination Data Messages.
5 3.2.2.1 Control Channel Procedure
6 3.2.2.1.1 Mobile Station Position Determination Data Messa ge Termination

7 A mobile station supporting Position Determination shall accept and shall process Data
8 Burst Messages received while the mobile station is monitoring the CDMA Paging Channel
9 (see 7.7.2.3.2.9 of TIA/EIA-95-B) that are addressed to the mobile station. Processing of
10 TIA/EIA-95-B Layer-2 fields shall be in accordance with TIA/EIA-95-B. Data Burst
11 Messages used to transport Position Determination request and response elements shall
12 always be acknowledged (Layer 2) and the in-order delivery over the air interface shall be
13 guaranteed by the transmitting entities: Mobile station and base station.
14 The mobile station shall process all Data Burst Messages addressed to the mobile station
15 on the Paging Channel and having the BURST_TYPE field set to ‘000101’ (as assigned in
16 TSB58-B). The mobile station shall discard the message without further processing if one
17 or more of the following is true:
18 • MSG_NUMBER field is set to a value other than 1.
19 • NUM_MSGS field is set to a value other than 1.
20 • NUM_FIELDS field is set to zero.
21 Otherwise, the mobile station shall process the Position Determination Data contained in
22 the CHARi fields of the received Data Burst Message (see 7.7.2.3.2.9 of TIA/EIA-95-B), as
23 described below.
24 3.2.2.1.1.1 Base Station Request Elements Received

25 If the mobile station does not support the requested capability, the mobile station shall
26 respond with a “Reject” response element with the appropriate reject reason (see Table
27 3.2.4.2-1), unless the base station request element is “Request MS Information” or “Request
28 Cancellation” (these request elements cannot be rejected); otherwise, the mobile station
29 shall include the appropriate response elements in the response Position Determination
30 Data Message (see 3.2.4) as described below. The response Position Determination Data
31 shall reside in the CHARi field of the response Data Burst Message (see 6.7.1.3.2.3 of
3
32 TIA/EIA-95-B).
33 • Request MS Information: The mobile station shall include the “Provide MS
34 Information” response element in the response Position Determination Data Message.
35 The response Position Determination Data Message shall be sent within 750 ms of
36 the reception of the “Request MS Information”.
3
The parameters discussed in this subsection are defined in 4.2.4.1.
3-5
TIA/EIA/IS-801-1
1 • Request Autonomous Measurement Weighting Factors: The mobile station shall

2 include the “Provide Autonomous Measurement Weighting Factors” response
3 element in the response Position Determination Data Message. The
4 PREF_RESP_QUAL indicator provided in the “Request Location Response” shall also
5 apply to the “Request Autonomous Measurement Weighting Factors” request
6 element.
7 • Request Pseudorange Measurement: The mobile station shall send one or more
8 “Provide Pseudorange Measurement” response elements, according to that which is
9 specified by NUM_FIXES (Number of Fixes) and T_BETW_FIXES (Time between
10 Fixes) included in the “Request Pseudorange Measurement”. The mobile station
11 shall include the “Provide Pseudorange Measurement” response element in one or
12 more response Position Determination Data Messages, according to the number of
13 parts into which the response element is divided. The mobile station shall set the
14 TOTAL_PARTS, TIME_REF_SRC, OFFSET_INCL and REF_PN fields to identical
15 values in all parts of the same “Provide Pseudorange Measurement” message. The
16 mobile station should use the mobile station time reference as defined in
4
17 TIA/EIA-95 as the time reference used to perform the pseudorange measurements.
18 If the mobile station is unable to use the mobile station time reference, as defined in
19 TIA/EIA-95, to measure the pseudoranges, then the mobile station shall use an
20 alternate time reference to perform the pseudorange measurements. The mobile
21 station shall set the TIME_REF_SRC field in the “Provide Pseudorange
22 Measurement” response element to the appropriate value to indicate the source of
23 the time reference used to perform the pseudorange measurements. If the
24 pseudorange measurements performed in the mobile station contain a bias caused
25 by receiver hardware delays, then the mobile station should correct the
26 measurement values in order to remove that bias from the reported code phase
27 values The mobile station shall set the periodic rate of measurement collection equal
28 to the value of T_BETW_FIXES.
29 – If PREF_RESP_QUAL is set to ‘000’, the “Provide Pseudorange Measurement”
30 response element shall be sent within T1 seconds of the time corresponding
31 to the beginning of the measurement collection period; if PREF_RESP_QUAL
32 is set to ‘001’, the “Provide Pseudorange Measurement” response element
33 shall be sent within T2 seconds of the time corresponding to the beginning of
34 the measurement collection period; if PREF_RESP_QUAL is set to ‘010’, the
35 “Provide Pseudorange Measurement” response element shall be sent within
36 T3 seconds of the time corresponding to the beginning of the measurement
37 collection period; if PREF_RESP_QUAL is set to ‘011’, the “Provide
38 Pseudorange Measurement” response element shall be sent within T4
39 seconds of the time corresponding to the beginning of the measurement
4
The time reference used to perform the pseudorange measurements should be initialized
from the mobile station time reference as defined in TIA/EIA-95.
3-6
TIA/EIA/IS-801-1

11 collection period.
12 – If OFFSET_REQ is set to ‘1’, the “Provide Pseudorange Measurement”
13 response element shall include REF_PN and MOB_SYS_T_OFFSET;
14 otherwise the “Provide Pseudorange Measurement” response element should
15 not include REF_PN and MOB_SYS_T_OFFSET.
16 • Request Pilot Phase Measurement: The mobile station shall send one or more
17 “Provide Pilot Phase Measurement” response elements, according to that which is
19 Fixes) included in the “Request Pilot Phase Measurement”. The mobile station shall
20 include the “Provide Pilot Phase Measurement” response element in one or more
21 response Position Determination Data Messages according to the number of parts
22 into which the response element is divided. The mobile station shall set the
23 OFFSET_INCL, REF_PN, BAND_CLASS, CDMA_FREQ, BASE_ID, SID, NID and
24 TOTAL_PARTS fields to identical values in all parts of the same “Provide Pilot Phase
25 Measurement” message. The mobile station shall set the periodic rate of
26 measurement collection equal to the value of T_BETW_FIXES.
27 – If PREF_RESP_QUAL is set to ‘000’, the “Provide Pilot Phase Measurement”
30 is set to ‘001’, the “Provide Pilot Phase Measurement” response element shall
31 be sent within T2 seconds of the time corresponding to the beginning of the
32 measurement collection period; if PREF_RESP_QUAL is set to ‘010’, the
33 “Provide Pilot Phase Measurement” response element shall be sent within T3
35 collection period; if PREF_RESP_QUAL is set to ‘011’, the “Provide Pilot
36 Phase Measurement” response element shall be sent within T4 seconds of the
37 time corresponding to the beginning of the measurement collection period; if
38 PREF_RESP_QUAL is set to ‘100’, the “Provide Pilot Phase Measurement”
3-7
TIA/EIA/IS-801-1

3 time corresponding to the beginning of the measurement collection period.
4 – If DESI_PIL_PH_RES is set to ‘1’, the "Provide Pilot Phase Measurement”
5
5 response element shall be of at least 1/8 of TIA/EIA-95 PN chip resolution;
6 otherwise, the “Provide Pilot Phase Measurement” response element shall be
7 of at least 1 TIA/EIA-95 PN chip resolution.
8 – If OFFSET_REQ is set to ‘1’, the “Provide Pilot Phase Measurement” response
9 element shall include MOB_SYS_T_OFFSET; otherwise the “Provide Pilot
10 Phase Measurement” response element should not include
11 MOB_SYS_T_OFFSET.
12 • Request Location Response: The mobile station shall send one or more “Provide
13 Location Response” response elements, according to that which is specified by
14 NUM_FIXES (Number of Fixes) and T_BETW_FIXES (Time between Fixes) included
15 in the “Request Location Response”. The mobile station shall include the “Provide
16 Location Response” response element in one or more response Position
17 Determination Data Messages according to the number of parts into which the
18 response element is divided. The mobile station shall set the periodic rate of
20 – If PREF_RESP_QUAL is set to ‘000’, the “Provide Location Response”
23 is set to ‘001’, the “Provide Location Response” response element shall be
24 sent within T2 seconds of the time corresponding to the beginning of the
26 “Provide Location Response” response element shall be sent within T3
28 collection period; if PREF_RESP_QUAL is set to ‘011’, the “Provide Location
29 Response” response element shall be sent within T4 seconds of the time
30 corresponding to the beginning of the measurement collection period; if
31 PREF_RESP_QUAL is set to ‘100’, the “Provide Location Response” response
32 element shall be sent within T5 seconds of the time corresponding to the
33 beginning of the measurement collection period; if PREF_RESP_QUAL is set
34 to ‘101’, the “Provide Location Response” response element shall be sent
35 within T6 seconds of the time corresponding to the beginning of the
5
If the mobile station rejects the request with 1/8 chip resolution, it may send an
unsolicited response (see 3.2.1.1) with 1 chip resolution.
3-8
TIA/EIA/IS-801-1

2 corresponding to the beginning of the measurement collection period.
3 – If HEIGHT_REQ is set to ‘1’, the “Provide Location Response” response
4 element should include height information; otherwise, the “Provide Location
5 Response” response element should not include height information.
6 – If CLK_COR_GPS_REQ is set to ‘1’, the “Provide Location Response” response
7 element should include clock correction for GPS time; otherwise, the “Provide
8 Location Response” response element should not include clock correction for
9 GPS time.
10 – If VELOCITY_REQ is set to ‘1’, the “Provide Location Response” response
11 element should include velocity information; otherwise, the “Provide Location
12 Response” response element should not include velocity information.
13 • Request Time Offset Measurement: The mobile station shall include a “Provide Time
14 Offset Measurement” response element in the response Position Determination
15 Data. If USE_TIME is set to ‘1’, the “Provide Time Offset Measurement” response
16 element shall include the offset information determined to be valid at the
17 ACTION_TIME. If USE_TIME is set to ‘0’, the “Provide Time Offset Measurement”
18 response element shall include the offset information determined to be valid at the
19 time the “Request Time Offset Measurement” is received by the mobile station. If
20 USE_TIME is set to ‘1’, the “Provide Time Offset Measurement” response element
21 shall be sent within 750 ms of ACTION_TIME. If USE_TIME is set to ‘0’, the “Provide
22 Time Offset Measurement” response element shall be sent within 750 ms of the
23 reception of the “Request Time Offset Measurement” request element.
24 • Request Cancellation: The mobile station shall cancel the outstanding request
25 element indicated by CANCEL_TYPE. The mobile station shall include a “Provide
26 Cancellation Acknowledgement” response element in the Position Determination Data
27 Message to indicate the successful cancellation of the outstanding request element.
28 If the mobile station has no outstanding request element of the type indicated by
29 CANCEL_TYPE, it shall set the NO_OUT_REQ flag in the “Provide Cancellation
30 Acknowledgment” response element. The “Provide Cancellation Acknowledgement”
31 response element shall be sent within 750 ms of the reception of the “Request
32 Cancellation” request element.
33 3.2.2.1.1.2 Base Station Response Elements Received

34 The mobile station should process and should make use of base station response elements.
37 If the mobile station receives “Provide GPS Almanac Correction” response element, the
38 mobile station shall process the response element as follows.
39 • If DELTA_XYZ_INCL is ‘0’, the mobile station shall set the values of DELTA_X,
40 DELTA_Y, DELTA_Z, DELTA_X_1ST, DELTA_Y_1ST and DELTA_Z_1ST to 0.
3-9
TIA/EIA/IS-801-1
1 • If DELTA_CLOCK_INCL is ‘0’, the mobile station shall set the values of

2 DELTA_CLOCK and DELTA_CLOCK_1ST to 0.
3 3.2.2.1.2 Mobile Station Position Determination Data Messa ge Origination
4 3.2.2.1.2.1 Position Determination Data Message Transmissio n Requirements

5 Mobile stations supporting Position Determination shall support the Mobile Station Message
6 Transmission Operation, as defined in 6.6.2.6 of TIA/EIA-95-B.
7 When the mobile station is in the TIA/EIA-95-B Mobile Station Idle State and needs to send
8 one (or more) Position Determination Data Message(s), the mobile station shall determine
9 whether the Position Determination Data Message(s) is (are) suitable for transmission on the
6
10 Access Channel . As part of this determination, the mobile station shall determine whether
11 the length of the Position Determination Data Message(s) is such that the message(s) can be
12 sent on the Access Channel. If the Position Determination Data Message(s) is (are) not
13 suitable for the Access Channel, the mobile station shall send the Position Determination
14 Data Message(s) on the CDMA Traffic Channel, following the procedures defined in 3.2.2.3.
15 If the Position Determination Data Message(s) is (are) suitable to be sent on the Access
16 Channel, the mobile station may form one (or more) Data Burst Message(s) (see 6.7.1.3.2.3
17 of TIA/EIA-95-B), setting BURST_TYPE to ‘000101’, and send it (them) on the Access
18 Channel, following the procedure specified in 6.6.2.6 and 6.6.3 of TIA/EIA-95-B. The
19 mobile station shall set NUM_FIELDS field to the number of octets in the Position
20 Determination Data Message (see 3.2.4). The mobile station address fields shall be set
21 using the address parameter stored in the mobile station. The authentication fields shall
22 be set, as described in 3.2.2.2, using the authentication parameter stored in the mobile
23 station. The Data Burst Message contains the Position Determination Data in the CHARi
24 fields (see 6.7.1.3.2.3 of TIA/EIA-95-B). The mobile station shall wait for an appropriate
25 response from the base station in accordance with the mobile station request elements.
26 When the mobile station is in the TIA/EIA-95-B System Access State, the mobile station
27 shall wait until it exits the System Access State. If the mobile station enters the Mobile
28 Station Idle State, the mobile station shall follow the procedures specified in the above
29 paragraph. If the mobile station enters the Mobile Station Control on Traffic Channel State,
30 the mobile station shall follow the procedures defined in 3.2.2.3. If the mobile station
31 enters an analog mode task, the mobile station shall follow the procedures for a mobile
32 station in analog mode (see 3.1).
33 Position Determination Data Messages sent on the Access Channel always require a
34 TIA/EIA-95-B Layer-2 acknowledgement and the in-order delivery over the air interface
35 shall be guaranteed by the mobile station.
36 3.2.2.1.2.2 Unsolicited Response Elements

37 Reserved
6
The criteria for suitability are implementation dependent.
3-10
TIA/EIA/IS-801-1
1 3.2.2.1.2.3 Request Elements

2 Reserved
3 3.2.2.2 Authentication Procedures

4 When sending a Data Burst Message on the Access Channel, the mobile station shall use
5 the authentication procedures defined in 6.3.12 of TIA/EIA-95-B. The authentication
6 parameter shall consist of three octets generated from the first three CHARi fields of the
7 Data Burst Message.
8 The sequence of digits in the authentication parameter shall be used to compute the
9 authentication fields of the Data Burst Message in accordance with 6.3.12.1.8 of TIA/EIA-
10 95-B.
11 3.2.2.3 Traffic Channel Procedure
12 3.2.2.3.1 Message Encryption

13 To enhance the security of the position determination session and to protect sensitive
14 subscriber location information, Position Determination Data Messages on the Traffic
15 Channel should be encrypted as deemed appropriate. Encryption of the Forward and
16 Reverse CDMA Traffic Channel messages is defined in 6.3.12.2 of TIA/EIA-95-B and Annex
17 A of TIA/EIA-95-B.
18 3.2.2.3.2 Negotiation for the Position Determination Service Option

19 Negotiation for the Position Determination Service Option is only required when no other
20 service option is connected.
21 The Position Determination Service Option described by this standard shall use service
22 option number 35 and is called Service Option 35 when using Multiplex Option 1. The
23 Position Determination Service Option shall use service option number 36 and is called
24 Service Option 36 when using Multiplex Option 2.
25 The mobile station shall negotiate for Service Option 35 using service negotiation when
26 using Multiplex Option 1 (see 3.2.2.3.2.1).
27 The mobile station shall negotiate for Service Option 36 using service negotiation when
28 using Multiplex Option 2 (see 3.2.2.3.2.1).
29 3.2.2.3.2.1 Procedures Using Service Negotiation

30 The mobile station shall perform service negotiation for Service Option 35 or Service Option
31 36 as described in TIA/EIA-95-B. The negotiated service configuration shall include only
32 valid attributes for the negotiated service option consistent with those specified in Table
33 3.2.2.3.2.1-1 and Table 3.2.2.3.2.1-2.
3-11
TIA/EIA/IS-801-1
1 Table 3.2.2.3.2.1-1. Valid Service Configuration Attributes for Service Option 35
Service Configuration Attribute Valid Selections

Forward Multiplex Option Multiplex Option 1
Reverse Multiplex Option Multiplex Option 1
Forward Transmission Rates Rate Set 1 with all four rates enabled
Reverse Transmission Rates Rate Set 1 with all four rates enabled
Forward Traffic Type None. This service option does not use nor
generate any forward traffic other than signaling.
Reverse Traffic Type None. This service option does not use nor
generate any reverse traffic other than signaling.
3 Table 3.2.2.3.2.1-2. Valid Service Configuration Attributes for Service Option 36
Service Configuration Attribute Valid Selections

Forward Multiplex Option Multiplex Option 2
Reverse Multiplex Option Multiplex Option 2
Forward Transmission Rates Rate Set 2 with all four rates enabled
Reverse Transmission Rates Rate Set 2 with all four rates enabled
Forward Traffic Type None. This service option does not use nor
generate any forward traffic other than signaling.
Reverse Traffic Type None. This service option does not use nor
generate any reverse traffic other than signaling.
5 If the mobile station accepts a service configuration, as specified in a Service Connect

6 Message, that includes a service option connection using Service Option 35 or Service
7 Option 36, then the service option connection shall become part of the current service
8 configuration at the action time associated with the Service Connect Message. Service
9 Option 35 or Service Option 36 is considered to be connected when the current service
10 configuration includes a service option connection for it.
11 If Service Option 35 (or Service Option 36) is connected when the mobile station enters the
12 Waiting for Mobile Station Answer Substate, or Service Option 35 (or Service Option 36)
13 becomes connected while the mobile station is in the Waiting for Mobile Station Answer
14 Substate, the mobile station shall send a Connect Order to the base station as a message
15 requiring acknowledgment without waiting for the user to explicitly command the call to be
16 answered. The mobile station shall enter the Conversation Substate.
17 The mobile station shall not send a Service Option Control Message for Service Option 35 or
18 Service Option 36. The mobile station shall send a Mobile Station Reject Order (ORDQ =
3-12
TIA/EIA/IS-801-1
1 ‘00000001’, unspecified reason), if it receives a Service Option Control Message for Service
2 Option 35 or Service Option 36 from the base station.
3 3.2.2.3.3 Mobile Station Position Determination Data Messa ge Termination

4 A mobile station supporting Position Determination shall accept and shall process Data
5 Burst Messages received on the CDMA Forward Traffic Channel (see 7.7.2.3.2.9 of
6 TIA/EIA-95-B). Processing of TIA/EIA-95-B Layer-2 fields shall be in accordance with
7 TIA/EIA-95-B. Data Burst Messages used to transport Position Determination request and
8 response elements shall always be acknowledged (Layer 2) and the in-order delivery over
9 the air interface shall be guaranteed by the transmitting entities: Mobile station and base
10 station.
11 The mobile station shall process all Data Burst Messages addressed to the mobile station
12 on the Forward Traffic Channel and having the BURST_TYPE field set to ‘000101’ (as
13 assigned in TSB58-B). The mobile station shall discard the message without further
14 processing if one or more of the following is true:
18 Otherwise, the mobile station shall process the Position Determination Data contained in
19 the CHARi fields of the received Data Burst Message (see 7.7.3.3.2.4 of TIA/EIA-95-B), as
20 described below.
21 3.2.2.3.3.1 Base Station Request Elements Received

22 If the mobile station is unable to respond with the requested information, the mobile
23 station shall respond with a “Reject” response element with the appropriate reject reason,
24 unless the base station request element is “Request MS Information” or “Request
25 Cancellation” (these request elements cannot be rejected); otherwise, the mobile station
26 shall include the appropriate response elements in the response Position Determination
27 Data (see 3.2.4) as described below. The response Position Determination Data shall reside
7
28 in the CHARi fields of the response Data Burst Message (see 6.7.2.3.2.4 of TIA/EIA-95-B).
29 • Request MS Information: The mobile station shall include the “Provide MS
30 Information” response element in the response Position Determination Data. The
31 response Position Determination Data Message shall be sent within 750 ms of the
32 reception of the “Request MS Information”.
33 • Request Autonomous Measurement Weighting Factors: The mobile station shall
34 include the “Provide Autonomous Measurement Weighting Factors” response
35 element in the response Position Determination Data. The PREF_RESP_QUAL
36 indicator provided in the “Request Location Response” shall also apply to the
37 “Request Autonomous Measurement Weighting Factors” request element.
7
3-13
TIA/EIA/IS-801-1
1 • Request Pseudorange Measurement: The mobile station shall send one or more
2 “Provide Pseudorange Measurement” response elements, according to that which is
4 Fixes) included in the “Request Pseudorange Measurement”. The mobile station
5 shall include the “Provide Pseudorange Measurement” response element in one or
6 more response Position Determination Data Messages according to the number of
7 parts into which the response element is divided. The mobile station shall set the
8 TOTAL_PARTS, TIME_REF_SRC, OFFSET_INCL and REF_PN fields to identical
9 values in all parts of the same “Provide Pseudorange Measurement” message. The
10 mobile station should use the mobile station time reference as defined in
8
11 TIA/EIA-95 as the time reference used to perform the pseudorange measurements.
12 If the mobile station is unable to use the mobile station time reference as defined in
13 TIA/EIA-95 to measure the pseudoranges, then the mobile station shall use an
14 alternate time reference to perform the pseudorange measurements. The mobile
15 station shall set the TIME_REF_SRC field in the “Provide Pseudorange
16 Measurement” response element to the appropriate value to indicate the source of
17 the time reference used to perform the pseudorange measurements. If the
18 pseudorange measurements performed in the mobile station contain a bias caused
19 by receiver hardware delays, then the mobile station should correct the
20 measurement values in order to remove that bias from the reported code phase
21 values. The mobile station shall set the periodic rate of measurement collection
22 equal to the value of T_BETW_FIXES.
23 – If PREF_RESP_QUAL is set to ‘000’, the “Provide Pseudorange Measurement”
26 is set to ‘001’, the “Provide Pseudorange Measurement” response element
27 shall be sent within T2 seconds of the time corresponding to the beginning of
28 the measurement collection period; if PREF_RESP_QUAL is set to ‘010’, the
29 “Provide Pseudorange Measurement” response element shall be sent within
30 T3 seconds of the time corresponding to the beginning of the measurement
8
The time reference used to perform the pseudorange measurements should be initialized
from the mobile station time reference as defined in TIA/EIA-95.
3-14
TIA/EIA/IS-801-1

4 collection period.
5 – If OFFSET_REQ is set to ‘1’, the “Provide Pseudorange Measurement”
6 response element shall include REF_PN and MOB_SYS_T_OFFSET;
7 otherwise the “Provide Pseudorange Measurement” response element should
8 not include REF_PN and MOB_SYS_T_OFFSET.
9 • Request Pilot Phase Measurement: The mobile station shall send one or more
10 “Provide Pilot Phase Measurement” response elements, according to that which is
12 Fixes) included in the “Request Pilot Phase Measurement”. The mobile station shall
13 include the “Provide Pilot Phase Measurement” response element in one or more
14 response Position Determination Data Messages according to the number of parts
15 into which the response element is divided. The mobile station shall set the
16 OFFSET_INCL, REF_PN, BAND_CLASS, CDMA_FREQ, BASE_ID, SID, NID and
17 TOTAL_PARTS fields to identical values in all parts of the same “Provide Pilot Phase
18 Measurement” message. The mobile station shall set the periodic rate of
20 – If PREF_RESP_QUAL is set to ‘000’, the “Provide Pilot Phase Measurement”
30 time corresponding to the beginning of the measurement collection period; if
31 PREF_RESP_QUAL is set to ‘100’, the “Provide Pilot Phase Measurement”
41 time corresponding to the beginning of the measurement collection period.
3-15
TIA/EIA/IS-801-1
1 – If DESI_PIL_PH_RES is set to ‘1’, the “Provide Pilot Phase Measurement”

9
2 response element shall be of at least 1/8 of TIA/EIA-95 PN chip resolution;
3 otherwise, the “Provide Pilot Phase Measurement” response element shall be
4 of at least 1 TIA/EIA-95 PN chip resolution.
5 – If OFFSET_REQ is set to ‘1’, the “Provide Pilot Phase Measurement” response
6 element shall include MOB_SYS_T_OFFSET; otherwise the “Provide Pilot
7 Phase Measurement” response element should not include
8 MOB_SYS_T_OFFSET.
9 • Request Location Response: The mobile station shall send one or more “Provide
10 Location Response” response elements, according to that which is specified by
11 NUM_FIXES (Number of Fixes) and T_BETW_FIXES (Time between Fixes) included
12 in the “Request Location Response”. The mobile station shall include the “Provide
13 Location Response” response element in one or more response Position
14 Determination Data Messages according to the number of parts into which the
15 response element is divided. The mobile station shall set the periodic rate of
17 – If PREF_RESP_QUAL is set to ‘000’, the “Provide Location Response”
20 is set to ‘001’, the “Provide Location Response” response element shall be
21 sent within T2 seconds of the time corresponding to the beginning of the
27 corresponding to the beginning of the measurement collection period; if
28 PREF_RESP_QUAL is set to ‘100’, the “Provide Location Response” response
29 element shall be sent within T5 seconds of the time corresponding to the
30 beginning of the measurement collection period; if PREF_RESP_QUAL is set
31 to ‘101’, the “Provide Location Response” response element shall be sent
32 within T6 seconds of the time corresponding to the beginning of the
38 corresponding to the beginning of the measurement collection period.
9
If the mobile station rejects the request with 1/8 chip resolution, it may send an
unsolicited response (see 3.2.1.1) with 1 chip resolution.
3-16
TIA/EIA/IS-801-1

3 Response” response element should not include height information.
5 element should include clock correction for GPS time; otherwise, the “Provide
6 Location Response” response element should not include clock correction for
7 GPS time.
11 • Request Time Offset Measurement: The mobile station shall include a “Provide Time
12 Offset Measurement” response element in the response Position Determination
13 Data. If USE_TIME is set to ‘1’, the “Provide Time Offset Measurement” response
14 element shall include the offset information determined to be valid at the
15 ACTION_TIME. If USE_TIME is set to ‘0’, the “Provide Time Offset Measurement”
16 response element shall include the offset information determined to be valid at the
17 time the “Request Time Offset Measurement” is received by the mobile station. If
18 USE_TIME is set to ‘1’, the “Provide Time Offset Measurement” response element
19 shall be sent within 750 ms of ACTION_TIME. If USE_TIME is set to ‘0’, the “Provide
20 Time Offset Measurement” response element shall be sent within 750 ms of the
21 reception of the “Request Time Offset Measurement” request element.
22 • Request Cancellation: The mobile station shall cancel the outstanding request
23 element indicated by CANCEL_TYPE. The mobile station shall include a “Provide
24 Cancellation Acknowledgement” response element in the Position Determination Data
25 Message to indicate the successful cancellation of the outstanding request element.
26 If the mobile station has no outstanding request element of the type indicated by
27 CANCEL_TYPE, it shall set the NO_OUT_REQ flag in the “Provide Cancellation
28 Acknowledgment” response element. The “Provide Cancellation Acknowledgement”
29 response element shall be sent within 750 ms of the reception of the “Request
30 Cancellation” request element.
31 3.2.2.3.3.2 Base Station Response Elements Received

32 The mobile station should process and should make use of base station response elements.
35 If the mobile station receives “Provide GPS Almanac Correction” response element, the
36 mobile station shall process the response element as follows.
37 • If DELTA_XYZ_INCL is ‘0’, the mobile station shall set the values of DELTA_X,
38 DELTA_Y, DELTA_Z, DELTA_X_1ST, DELTA_Y_1ST and DELTA_Z_1ST to 0.
39 • If DELTA_CLOCK_INCL is ‘0’, the mobile station shall set the values of
40 DELTA_CLOCK and DELTA_CLOCK_1ST to 0.
41 3.2.2.3.4 Traffic Channel Setup
3-17
TIA/EIA/IS-801-1
1 When a mobile station in the TIA/EIA-95-B Mobile Station Idle State intends to send
2 Position Determination Data Message on a Traffic Channel, the following procedures apply:
3 • The mobile station shall send an Origination Message (see 6.7.1.3.2.4 of
4 TIA/EIA-95-B) containing no dialed digits and requesting Service Option 35 or
5 Service Option 36. The base station should complete an authentication Unique
6 Challenge-Response Procedure (see 6.3.12.1.5 of TIA/EIA-95-B) immediately after
7 assigning the traffic channel. The Unique Challenge-Response Procedure should be
8 completed successfully before the Position Determination Data Messages are sent to
9 the mobile station, and before the mobile-originated Position Determination Data
10 Messages are forwarded to other network entities.
11 • Call processing following the transmission of the Origination Message shall follow
12 the procedures defined in 6.6 of TIA/EIA-95-B. When the mobile station enters the
13 Conversation Substate, the mobile station may send the Position Determination Data
14 Messages in accordance with the procedures defined in the next section.
15 3.2.2.3.5 Mobile Station Position Determination Data Messa ge Origination in the

16 Conversation Substate

18 When the mobile station is in the TIA/EIA-95-B Mobile Station Conversation Substate and
19 needs to send one (or more) Position Determination Data Message(s), the mobile station shall
20 form one (or more) Data Burst Message(s) (see 6.7.2.3.2.4 of TIA/EIA-95-B), setting
21 BURST_TYPE to ‘000101’ and send the Data Burst Message(s) on the Reverse Traffic
22 Channel. The mobile station shall set the MSG_NUMBER and NUM_MSGS fields to 1, and
23 shall set NUM_FIELDS field to the number of octets in the Position Determination Data
24 Message (see 3.2.4). The Data Burst Message contains the Position Determination Data in
25 the CHARi fields (see 6.7.2.3.2.4 of TIA/EIA-95-B). The mobile station shall set the
26 ACK_REQ Layer-2 field to ‘1’. If the only connected service option is Service Option 35 or
27 Service Option 36, the mobile station should enter the Release Substate with a mobile
28 station release indication (see 6.6.4.5 of TIA/EIA/95-B) when Position Determination Data
29 Messages have not been received or have not been sent during a period of time which is
30 implementation-dependent. If any service option in addition to Service Option 35 or Service
31 Option 36 is connected, the mobile station shall remain in the Conversation Substate, and
32 the mobile station should initiate Service Negotiation to drop Service Option 35 or Service
33 Option 36 when Position Determination Data Messages have not been received or have not
34 been sent during a period of time which is implementation-dependent. If the user needs to
35 initiate a call and Service Option 35 or 36 is the only service option connected, then the
36 mobile station should release the call for Service Option 35 or 36 if needed to connect the
37 user call.

39 Reserved
3-18
TIA/EIA/IS-801-1
1 Reserved
2 3.2.3 Broadcast Procedures

3 Reserved
4 3.2.4 Reverse Link Message Format

5 The reverse link Position Determination Data Messages are summarized in Table 3.2.4-1.
6 Table 3.2.4-1. Reverse Link Messages
Message Name PD_MSG_TYPE

Position Determination Data ‘00000000’
Message
Reserved for future standardization ‘00000001’ through
‘10111111’
Available for manufacturer-specific ‘11000000’ through
Message definition as specified in
TSB-58
Reserved ‘11111111’
8 The Position Determination Data Message from mobile station to base station has the
9 following variable length format:
10
Field Length (bits)

SESS_START 1
SESS_END 1
SESS_SOURCE 1
SESS_TAG 5
PD_MSG_TYPE (‘00000000’) 8
NUM_REQUESTS 4
NUM_RESPONSES 4
The mobile station shall include NUM_REQUESTS
occurrences of the following record:
RESERVED 4
REQ_TYPE 4
REQ_PAR_LEN 8
3-19
TIA/EIA/IS-801-1
REQ_PAR_RECORD 8 × REQ_PAR_LEN
The mobile station shall include NUM_RESPONSES
RESERVED 3
UNSOL_RESP 1
RESP_TYPE 4
RESP_PAR_LEN 8
RESP_PAR_RECORD 8 × RESP_PAR_LEN
2 SESS_START – Start-of-session indicator.

3 If the mobile station has previously sent or received a
4 Position Determination Data Message related to this
5 Position Determination Data Message (as defined in
6 2.2.1) it shall set this field to ‘0’; otherwise, it shall set
7 this field to ‘1’.
8 SESS_END – End-of-session indicator.
9 If the mobile station does not expect to receive or send
10 any more Position Determination Data Messages related
11 to this Position Determination Data Message (as defined
12 in 2.2.1) the mobile station shall set this field to ‘1’;
13 otherwise, it shall set this field to ‘0’. The criteria for
14 setting this field are implementation dependent.
10
15 SESS_SOURCE – Session-source indicator.
16 If SESS_START is set to ‘1’ the mobile station shall set
17 this field to ‘1’; otherwise it shall set this field to the
18 same value as the SESS_SOURCE field that appeared
19 in a previously-received or previously-sent Position
20 Determination Data Message that was related to this
22 2.2.1).
10
This field indicates which side (mobile station or base station) initiated this session.
3-20
TIA/EIA/IS-801-1
1 SESS_TAG – Session tag.

2 If SESS_START is set to ‘0’ the mobile station shall set
3 this field to the same value as the SESS_TAG field that
4 appeared in a previously-received or previously-sent
5 Position Determination Data Message that was related
7 in 2.2.1); otherwise (if SESS_START is set to ‘1’), the
8 mobile station shall set this field to one more (modulo
9 32) than the value it assigned to this field in the latest
10 Position Determination Data Message that it sent with
11 SESS_START set to ‘1’. If no such latest Position
12 Determination Data Message exists, the mobile station
13 shall set this field to ‘00000’. The definition of “latest”
14 is implementation dependent.
15 PD_MSG_TYPE – Position Determination Data Message type.
16 The mobile station shall set this field to ‘00000000’.
17 NUM_REQUESTS – Number of request element parameter records.
18 The mobile station shall set this field to the number of
19 request element parameters records included in the
20 message in the range from 0 to 15.
21 NUM_RESPONSES – Number of response element parameter records.
23 response element parameters records included in the
25 RESERVED – Reserved bits.
27 REQ_TYPE – Request element type.
28 The mobile station shall set this field to the value
29 shown in Table 3.2.4-2.
3-21
TIA/EIA/IS-801-1
1 Table 3.2.4-2. Request Element Type
Description REQ_TYPE
(binary)
Reserved ‘0000’
Request BS Capabilities ‘0010’
Request GPS Acquisition Assistance ‘0100’
Request GPS Location Assistance ‘0110’
Reserved ‘0111’
Request GPS Sensitivity Assistance ‘0101’
Request Base Station Almanac ‘0011’
Request GPS Almanac ‘1000’
Request GPS Ephemeris ‘1001’
Request GPS Navigation Message Bits ‘1010’
Request Location Response ‘0001’
Request GPS Almanac Correction ‘1011’
Request GPS Satellite Health Information ‘1100’
All other REQ_TYPE values are reserved.
3 REQ_PAR_LEN – Request element parameters length.

5 octets included in the REQ_PAR_RECORD field in the
6 range from 0 to 255.
7 REQ_PAR_RECORD – Request element parameters record.
8 The mobile station shall set this record as described in
9 3.2.4.1.
11 The mobile station shall set these bits to ‘000’.
12 UNSOL_RESP – Unsolicited response indicator.
13 If the response element is an unsolicited response
14 element, the mobile station shall set this field to ‘1’;
15 otherwise the mobile station shall set this field to ‘0’.
16 RESP_TYPE – Response element type.
18 shown in Table 3.2.4-3.
3-22
TIA/EIA/IS-801-1
1 Table 3.2.4-3. Response Element Type
Description RESP_TYPE
(binary)
Reject ‘0000’
Provide MS Information ‘0010’
Provide Autonomous Measurement Weighting Factors ‘0011’
Provide Pseudorange Measurement ‘0100’
Provide Pilot Phase Measurement ‘0101’
Provide Location Response ‘0001’
Provide Time Offset Measurement ‘0110’
Provide Cancellation Acknowledgement ‘0111’
All other RESP_TYPE values are reserved.
3 RESP_PAR_LEN – Response element parameters length.

4 The mobile station shall set RESP_PAR_LEN to the
5 number of octets included in the response element in
6 the range from 0 to 255.
7 RESP_PAR_RECORD – Response element parameters record.
8 The mobile station shall set this record as described in
9 3.2.4.2.
10 3.2.4.1 Request Element Parameters Record

11
11 The mobile station shall set REQ_PAR_RECORD as described below .
12 If REQ_TYPE in Position Determination Data Message is equal to ‘0010’, or if REQ_TYPE is
13 equal to ‘0101’, or if REQ_TYPE is equal to ‘1000’, or if REQ_TYPE is equal to ‘1100’, the
14 mobile station shall not include this record. If REQ_TYPE in Position Determination Data
15 Message is equal to ‘0001’, or if REQ_TYPE is equal to ‘0011’, or if REQ_TYPE is equal to
16 ‘0100’, or if REQ_TYPE is equal to ‘0110’, or if REQ_TYPE is equal to ‘1001’, or if REQ_TYPE
17 is equal to ‘1010’, or if REQ_TYPE is equal to ‘1011’, the mobile station shall include the
18 record REQ_PAR_RECORD and set its fields as described below.
11
A request element includes any parameters that directly specify the structure or contents
of the expected response. It does not include parameters that convey information about the
"state" (or status) of the mobile, or values of parameters stored in the mobile. If such
parameters are needed in support of the request, they can be conveyed in an unsolicited
response. (Note: "state" does not refer to the IS-95 state of the mobile; rather, it refers, in
general, to the internal status of the mobile).
3-23
TIA/EIA/IS-801-1
1 If REQ_TYPE is equal to ‘0100’ (Request GPS Acquisition Assistance), REQ_PAR_RECORD

2 shall include the following record:
3
Field Length (bits)

DOPP _REQ 1
ADD_DOPP_REQ 1
CODE_PH_PAR_REQ 1
AZ_EL_REQ 1
RESERVED 4
4
th
5 DOPP _REQ – Doppler (0 order) term requested.
th
6 If Doppler (0 order) terms are requested, the mobile
7 station shall set this field to ‘1’; otherwise the mobile
8 station shall set this field to ‘0’.
9 ADD_DOPP_REQ – Additional Doppler terms requested.
th
10 If the Doppler (0 order) terms, the Doppler High-
11 Order terms and the Doppler search window terms are
12 requested, the mobile station shall set this field to ‘1’;
14 CODE_PH_PAR_REQ – Code phase parameters requested.
15 If the code phase parameters are requested, the mobile
18 AZ_EL_REQ – Azimuth and elevation angle requested.
19 If azimuth and elevation angle are requested, the
20 mobile station shall set this field to ‘1’; otherwise the
21 mobile station shall set this field to ‘0’.
24 If REQ_TYPE is equal to ‘0110’ (Request GPS Location Assistance), REQ_PAR_RECORD
26
Field Length (bits)

COORD_TYPE 1
RESERVED 7
27
3-24
TIA/EIA/IS-801-1
1 COORD_TYPE – Coordinate type requested.

2 If Cartesian coordinates are requested, the mobile
3 station shall set this field to ‘0’. If spherical
4 coordinates are requested, the mobile station shall set
8 If REQ_TYPE is equal to ‘0011’ (Request Base Station Almanac), REQ_PAR_RECORD shall
9 include the following record:
10
Field Length (bits)

EXT_BS_ALM 1
RESERVED 7
11
12 EXT_BS_ALM – Extended base station almanac requested.

13 If the extended base station almanac is requested, the
14 mobile station shall set this field to ‘1’. If the base
15 station almanac is requested, the mobile station shall
16 set this field to ‘0’.
19 If REQ_TYPE is equal to ‘1001’ (Request GPS Ephemeris), REQ_PAR_RECORD shall include
20 the following record:
21
Field Length (bits)

AB_PAR_REQ 1
RESERVED 7
22
23 AB_PAR_REQ – Alpha/Beta parameters requested.

24 If Alpha/Beta parameters are requested, the mobile
29 If REQ_TYPE is equal to ‘1010’ (Request GPS Navigation Message Bits), REQ_PAR_RECORD
3-25
TIA/EIA/IS-801-1
Field Length (bits)

SUBF_4_5_REQ 1
RESERVED 7
2 SUBF_4_5_REQ – Subframes 4 and 5 requested.

3 If subframes 4 and 5 are requested, the mobile station
4 shall set this field to ‘1’; otherwise the mobile station
5 shall set this field to ‘0’.
8 If REQ_TYPE is equal to ‘0001’ (Request Location Response), REQ_PAR_RECORD shall
10
Field Length (bits)

HEIGHT_REQ 1
CLK_COR_GPS_REQ 1
VELOCITY_REQ 1
RESERVED 5
11
12 HEIGHT_REQ – Height information requested.

13 If height information is requested, the mobile station
16 CLK_COR_GPS_REQ – Clock correction for GPS time requested.
17 If clock correction for GPS time is requested, the
18 mobile station shall set this field to ‘1’; otherwise the
20 VELOCITY_REQ – Velocity information requested.
21 If velocity information is requested, the mobile station
26 If REQ_TYPE is equal to ‘1011’ (Request GPS Almanac Correction), REQ_PAR_RECORD
3-26
TIA/EIA/IS-801-1
Field Length (bits)

TOA 8
WEEK_NUM 8
3 TOA – Time of almanac.

4 The mobile station shall set this field to the time of
5 applicability of the almanac for which the correction is
6 requested, in units of 4096 s, in the range from 0 to
7 602,112 s.
8 WEEK_NUM – GPS week number.
9 The mobile station shall set this field to the 8 least
10 significant bits of the GPS week number of the
11 almanac for which the correction is requested. The
12 range for this field is from 0 to 255.
13 3.2.4.2 Response Element Parameters Record

14 The mobile station shall set RESP_PAR_RECORD as described below.
15 If RESP_TYPE in Position Determination Data Message is equal to ‘0000’ (Reject),
16 RESP_PAR_RECORD shall include the following record:
17
Field Length (bits)
REJ_REQ_TYPE 4
REJ_REASON 3
RESERVED 1
18
19 REJ_REQ_TYPE – Reject request type.

20 The mobile station shall set this field to the value of
21 the REQ_TYPE corresponding to the request element it
22 rejects. See Table 4.2.4-2.
23 REJ_REASON – Reject reason.
25 shown in Table 3.2.4.2-1.
3-27
TIA/EIA/IS-801-1
1 Table 3.2.4.2-1. Reject Reason
REJ_REASON
Reason for rejection
(binary)
Capability not supported by the mobile station ‘000’
Capability normally supported by the mobile ‘001’
station but temporarily not available or not
12
enabled
All other REJ_REASON values are reserved.

5 If RESP_TYPE is equal to ‘0010’ (Provide MS Information), RESP_PAR_RECORD shall
6 include the following variable-length record:
7
Field Length (bits)
MS_LS_REV 6
MS_MODE 4
PILOT_PH_CAP 6
GPS_ACQ_CAP 12
LOC_CALC_CAP 12
9 MS_LS_REV – The mobile station location standard revision number.

10 The revision number of IS-801 that the mobile station
11 is using. The mobile station shall set this field to
12 ‘000000’.
13 MS_MODE – The digital mode indicator.
15 PILOT_PH_CAP – Pilot phase capability.
12
For example, the position determination feature may be disabled by the user.
3-28
TIA/EIA/IS-801-1
1 Table 3.2.4.2-2. Pilot Phase Capability
PILOT_PH IS-95 Pilot Phase Capability

(binary)
‘000000’ Full Chip Measurement Capability
‘000001’ Half Chip Measurement Capability
‘000010’ Quarter Chip Measurement Capability
‘000011’ Eighth Chip Measurement Capability
‘000100’ One Sixteenth Chip Measurement Capability
All other PILOT_PH values are reserved.
3 GPS_ACQ_CAP – GPS acquisition capability.

4 GPS_ACQ_CAP consists of 12 bits, each of the LSB’s
5 represents one GPS acquisition capability. The
6 mapping of the bits is listed in Table 3.2.4.2-3. If a
7 GPS acquisition capability is supported, the mobile
8 station shall set the corresponding bit in
9 GPS_ACQ_CAP to ‘1’; otherwise the mobile station
10 shall set the corresponding bit to ‘0’. Bits 8-12 shall
11 be set to ‘00000’.
12
13 Table 3.2.4.2-3. Mapping Table for GPS Acquisition Capability
Corresponding Bit in GPS_ACQ_CAP GPS Acquisition Capability

Bit 1 (LSB) GPS Acquisition Assistance
Bit 2 GPS Sensitivity Assistance
Bit 3 GPS Almanac
Bit 4 GPS Ephemeris
Bit 5 GPS Navigation Message Bits
Bit 6 GPS Almanac Correction
Bit 7 GPS Autonomous Acquisition Capable
Bits 8 – 12 Reserved
14
3-29
TIA/EIA/IS-801-1
1 LOC_CALC_CAP – Position calculation capability.

2 LOC_CALC_CAP consists of 12 bits, each of the LSB’s
3 represents one position calculation capability. The
4 mapping of the bits is listed in Table 3.2.4.2-4. If a
5 position calculation capability is supported, the mobile
6 station shall set the corresponding bit in
7 LOC_CALC_CAP to ‘1’; otherwise the mobile station
8 shall set the corresponding bit to ‘0’. Bits 9-11 shall
9 be set to ‘000’.
10
11 Table 3.2.4.2-4. Mapping Table for Position Calculation Capability
Corresponding Bit in LOC_CALC_CAP Position Calculation Capability

Bit 1 (LSB) Location Calculation Capable using
Location Assistance – Spherical
Bit 2 Location Calculation Capable using
Location Assistance – Cartesian
Bit 3 Advanced Forward Link Trilateration
(AFLT) Location Calculation Capable
Bit 4 Location Calculation Capable using GPS
Almanac Assistance
Ephemeris Assistance
Almanac Correction
Bit 7 Autonomous Location Calculation Capable
Bit 8 Hybrid GPS and AFLT Location
Calculation Capable
Bit 9 –11 Reserved
Bits 12 (MSB) Pre-programmed Location
12
13 If RESP_TYPE is equal to ‘0011’ (Provide Autonomous Measurement Weighting Factors),

14 RESP_PAR_RECORD shall include the following variable length record:
3-30
TIA/EIA/IS-801-1
Field Length (bits)

TIME_REF_CDMA 14
DGPS 1
NUM_SV 4
GPS_WEIGHT 4
The mobile station shall include NUM_SV occurrences of the
following fields:
SV_PRN_NUM 6
INV_WEIGHT_FA 6
RESERVED 0 - 7 (as needed)
2 TIME_REF_CDMA – CDMA system time at the time the solution is valid.

3 The mobile station shall set this field to (t/50 mod
4 16384), where t is the CDMA system time in frames, as
5 defined in 1.2 of TIA/EIA-95-B, at the time the
6 solution is valid. This is the time at which the values
7 of the parameters reported in this response element
8 parameter record are valid.
9 DGPS – DGPS flag.
10 If differential GPS is used, the mobile station shall set
11 this field to ‘1’; otherwise the mobile station shall set
13 NUM_SV – Number of GPS satellites in solution.
15 GPS satellites used to compute the solution, in the
16 range from 1 to 16, where the binary value of the field
17 conveys the number of satellites minus one.
18 GPS_WEIGHT – Ratio of GPS weight to total weight.
19 The mobile station shall set this field to the ratio of
20 GPS weight to total weight (GPS weight and pilot phase
21 weight) used to compute the solution, in the range
22 from 0 to 1, with a resolution of 1/15.
3-31
TIA/EIA/IS-801-1
1 SV_PRN_NUM – Satellite PRN number.

3 the PRN signal number for which the measured data is
4 valid. It is represented as an unsigned value in the
6 conveys the satellite PRN number minus one.
7 INV_WEIGHT_FA – Inverse of weighting factor.
8 The mobile station shall set this field to the inverse of
9 the weighting factor used for the satellite. A “floating-
10 point” representation is used where the 3 most
11 significant bits constitute the exponent and the 3 least
12 significant bits constitute the mantissa as specified in
13 Table 3.2.4.2-5.
14
15 Table 3.2.4.2-5. Inverse of Weighting Factor Representation
Index value, i Floating-Point Inverse Weighting

Exponent, X Mantissa, Y
=Y+8×X value, fi Factor value, σ (m)
‘000’ ‘000’ 0 0.5 σ < 0.5
‘000’ ‘001’ 1 0.5625 0.5 ≤ σ < 0.5625
2 ≤ i ≤ 61 fi-1 ≤ σ < fi
X
X Y 0.5×(1 + Y/8)×2
‘111’ ‘110’ 62 112 104 ≤ σ < 112
‘111’ ‘111’ 63 Not Applicable 112 ≤ σ
16

18 The mobile station shall add reserved bits as needed in
19 order to make the length of the response element
20 parameters record equal to an integer number of
21 octets. The mobile station shall set these bits to ‘0’.
3-32
TIA/EIA/IS-801-1
1 If RESP_TYPE is equal to ‘0100’ (Provide Pseudorange Measurement), RESP_PAR_RECORD

2 shall include the following variable length record:
3
Field Length (bits)

PART_NUM 3
TOTAL_PARTS 3
NUM_PS_RANGES_P 6
TIME_REF 24
TIME_REF_SRC 2
OFFSET_INCL 1
REF_PN 0 or 9
MOB_SYS_T_OFFSET 0 or 14
The mobile station shall include NUM_PS_RANGES_P
occurrences of the following fields:
SV_PRN_NUM 6
SV_CNO 6
PS_DOPPLER 16
SV_CODE_PH_WH 10
SV_CODE_PH_FR 10
MUL_PATH_IND 3
PS_RANGE_RMS_ER 6
5 PART_NUM – The part number.

6 The mobile station shall set this field to specify the
7 part number of the Pseudorange Measurement data, in
8 the range from 1 to TOTAL_PARTS, where the binary
9 value of the field conveys the part number minus one.
10 TOTAL_PARTS – The total number of parts.
12 total number of parts that the Pseudorange
13 Measurement data is divided into, in the range from 1
14 to 8, where the binary value of the field conveys the
15 total number of parts minus one.
3-33
TIA/EIA/IS-801-1
1 NUM_PS_RANGES_P – Number of pseudoranges in this part.

3 pseudoranges included in this part of the response
4 element, in the range from 1 to 64, where the binary
5 value of the field conveys the number of satellites
6 minus one.
7 TIME_REF – The time of validity of the parameters reported in this
8 response element.
9 The mobile station shall set this field to
10 (t mod 14,400,000), where t is the time of validity in
11 units of 1 ms, based on the time reference specified by
12 TIME_REF_SRC (see Table 3.2.4.2-6). This is the time
13 at which the values of the parameters reported in this
14 response element parameter record are valid.
15 TIME_REF_SRC – Time reference source.
16 The mobile station shall set this field according to
17 Table 3.2.4.2-6.
18
19 Table 3.2.4.2-6. Time Reference Source
TIME_REF_SRC
Time reference source
(binary)
Mobile station time reference as defined in 6.1.5.1 of ‘00’
TIA/EIA-95-B
GPS time reference ‘01’
Other time reference ‘10’
Reserved ‘11’
20
21 OFFSET_INCL – Offset Included.

22 If the response element includes REF_PN and
23 MOB_SYS_T_OFFSET fields, then the mobile station
26 REF_PN – Time reference PN sequence offset.
27 If the OFFSET_INCL field is set to ‘1’, then the mobile
28 station shall set this field to the PN sequence offset of
29 the pilot used by the mobile station to derive its time
30 reference, relative to the zero offset pilot PN sequence
31 in units of 64 PN chips; otherwise the mobile station
32 shall not include this field.
3-34
TIA/EIA/IS-801-1
1 MOB_SYS_T_OFFSET – Mobile station system time offset.

3 station shall set this field to the two’s complement
4 value of the offset between mobile station time
5 reference and time of occurrence of Reference PN, in
13
6 units of 1/16 TIA/EIA-95-B chips , in the range from
7 -512 to +511.9375 TIA/EIA-95-B chips; otherwise the
8 mobile station shall not include this field. The sign of
9 this quantity shall be positive if the reference PN
10 occurs earlier than the mobile station time reference;
11 otherwise it shall be negative.
12 SV_PRN_NUM – Satellite PRN number.
14 the PRN signal number for which the measured data is
15 valid. It is represented as an unsigned value in the
17 conveys the satellite PRN number minus one.
18 SV_CNO – Satellite C/N0.
20 the satellite C/N0, as referenced to the antenna
14
21 connector , in units of 1 dB-Hz, in the range from 0 to
22 63 dB-Hz.
23 PS_DOPPLER – Pseudodoppler.
24 The mobile station shall set this field to the two’s
25 complement value of the measured satellite
26 pseudodoppler, in units of 0.2 Hz, in the range from
27 -6,553.6 Hz to +6,553.4 Hz.
28 SV_CODE_PH_WH – Satellite code phase – whole chips.
29 The mobile station shall set this field to the measured
30 satellite code phase, in units of 1 GPS chip, in the
31 range from 0 to 1022 chips, where increasing binary
32 values of the field signify increasing measured
33 pseudoranges.
13 th
This field supports a maximum resolution of 1/16 of a TIA/EIA-95-B chip. However,
th
mobile stations not capable of 1/16 chip measurement resolution are also supported by
this standard (See Table 3.2.4.2-2). Measurements made at lower resolutions are reported
th
in this field using 1/16 chip resolution.
14
If an active antenna is employed (i.e., one with a built-in amplifier and/or filter), then
C/N0 should be referenced to the antenna port prior to any amplifier or filter.
3-35
TIA/EIA/IS-801-1
1 Note: Generally, this value is obtained from a

2 specification of the associated parameter that has a
3 larger number of bits of resolution. These values shall
4 be obtained by simple truncation without rounding-off.
5
6 SV_CODE_PH_FR – Satellite code phase – fractional chips.

7 The mobile station shall set this field to the residual
10
8 satellite code phase, in units of 1/2 of GPS chips, in
10 10
9 the range from 0 to (2 -1)/2 GPS chips.
10 MUL_PATH_IND – Multipath indicator.
13
14 Table 3.2.4.2-7. Multipath Indicator
Threshold MUL_PATH_IND
Description
(binary)
Not measured Not specified ‘000’
Low MP Error ≤ 5 m ‘001’
Medium 5 m < MP Error ≤ 43 m ‘010’
High MP Error > 43 m ‘011’
All other MUL_PATH_IND values are reserved.
15
16 PS_RANGE_RMS_ER – Pseudorange RMS error.

17 The mobile station shall set this field to the
18 pseudorange RMS error used for the satellite. A
19 “floating-point” representation is used where the 3
20 most significant bits constitute the exponent and the 3
21 least significant bits constitute the mantissa as
22 specified in Table 3.2.4.2-8.
23 Note: ‘111111’ may indicate that the mobile was
24 unable to estimate pseudorange RMS error.
25
3-36
TIA/EIA/IS-801-1
1 Table 3.2.4.2-8. Pseudorange RMS Error Representation
RMS Error in
Index value, i Floating-Point Pseudorange
Exponent, X Mantissa, Y
= Y + 8×X value, fi Measurement
value, σ (m)
‘000’ ‘000’ 0 0.5 P < 0.5
‘000’ ‘001’ 1 0.5625 0.5 ≤ P < 0.5625
2 ≤ i ≤ 61 fi-1 ≤ P < fi
X
X Y 0.5×(1 + Y/8)×2
‘111’ ‘110’ 62 112 104 ≤ P < 112
‘111’ ‘111’ 63 Not Applicable 112 ≤ P

3-37
TIA/EIA/IS-801-1
1 If RESP_TYPE is equal to ‘0101’ (Provide Pilot Phase Measurement), RESP_PAR_RECORD

2 shall include the following variable length record:
3
Field Length (bits)

TIME_REF_MS 24
OFFSET_INCL 1
MOB_SYS_T_OFFSET 0 or 14
REF_PN 9
REF_PILOT_STRENGTH 6
BAND_CLASS 5
CDMA_FREQ 11
BASE_ID 16
SID 15
NID 16
TOTAL_RX_PWR 5
PART_NUM 3
TOTAL_PARTS 3
NUM_PILOTS_P 6
The mobile station shall include NUM_PILOTS_P occurrences
of the following three-field record:
PILOT_PN_PHASE 19
PILOT_STRENGTH 6
RMS_ERR_PHASE 6
ADD_PILOTS_INCL 1
ADD_BAND_CLASS 0 or 5
ADD_CDMA_FREQ 0 or 11
ADD_TOTAL_RX_PWR 0 or 5
NUM_ADD_PILOTS_P 0 or 6
If ADD_PILOT_INCL is set to ‘1’, the mobile station shall
include NUM_ADD_PILOTS_P occurrences of the following
three-field record:
ADD_PILOT_PN_PH 19
ADD_PILOT_STRENGTH 6
3-38
TIA/EIA/IS-801-1
ADD_RMS_ERR_PH 6
1 TIME_REF_MS – The time of validity of the parameters reported in this

2 response element.
5 units of 1 ms, based on mobile station time reference
6 as defined in 6.1.5.1 of TIA/EIA-95-B. This is the time
9 OFFSET_INCL – Offset Included.
10 If the response element includes MOB_SYS_T_OFFSET
11 field, then the mobile station shall set this field to ‘1’;
13 MOB_SYS_T_OFFSET – Mobile station system time offset. See 6.1.5.1 of
14 TIA/EIA-95-B.
17 value of the offset between mobile station time
18 reference and time of occurrence of Reference PN, in
19 units of 1/16 TIA/EIA-95-B chips, in the range from
20 -512 to +511.9375 TIA/EIA-95-B chips; otherwise the
21 mobile station shall not include this field. The sign of
22 this quantity shall be positive if the reference PN
23 occurs earlier than the mobile station time reference;
26 The mobile station shall set this field to the PN
27 sequence offset of the pilot used by the mobile station
28 to derive its time reference, relative to the zero offset
29 pilot PN sequence in units of 64 PN chips.
30 REF_PILOT_STRENGTH – Pilot strength.
31 This parameter conveys the Ec/Io of this pilot (as
32 specified in 6.6.6.2.2 of TIA/EIA-95-B), in the units of
33 0.5 dB, in the range from 0 to –31.5 dB. The mobile
34 station shall set this field to
35 -2 × 10 log10 PS,
3-39
TIA/EIA/IS-801-1
1 where PS is the strength of the pilot used by the

2 mobile station to derive its time reference (see 6.1.5.1
3 of TIA/EIA-95-B), measured as specified in 6.6.6.2.2 of
4 TIA/EIA-95-B. If this value (-2 × 10 log10 PS) is less
5 than 0, the mobile station shall set this field to
6 ‘000000’. If this value is greater than 63, the mobile
8 BAND_CLASS – Band class.
9 The mobile station shall set this field to the CDMA
10 band class of the pilots that are reported in this
11 response element, as specified in TSB58-B.
12 CDMA_FREQ – Frequency assignment.
13 The mobile station shall set this field to the CDMA
14 Channel number, in the specified CDMA band class, of
15 the pilots that are reported in this response element,
16 as specified in 6.1.1.1 of TIA/EIA-95-B.
17 BASE_ID – Base Station Identification.
18 If the mobile station is on the Paging Channel, the
19 mobile station shall set this field to the base station
20 identification number obtained from the Paging
21 Channel that the mobile station is demodulating;
22 otherwise, the mobile station shall set this field to the
23 base station identification number obtained from the
24 Paging Channel that the mobile station last
25 demodulated.
26 SID – System Identification.
28 mobile station shall set this field to the system
32 system identification number obtained from the Paging
33 Channel that the mobile station last demodulated.
3-40
TIA/EIA/IS-801-1
1 NID – Network Identification.

3 mobile station shall set this field to the network
7 network identification number obtained from the
8 Paging Channel that the mobile station last
9 demodulated.
10 TOTAL_RX_PWR – Total received power.
12 max ( 0, min ( 31, (total_received_power+110)/2 ))
13 where total_received_power is the mean input power
14 received by the mobile station on frequency
15 CDMA_FREQ, in dBm/1.23 MHz.
16 Note that this definition is taken from the
17 SF_TOTAL_RX_PWR (serving frequency total received
18 power) defined in TIA/EIA-95-B Section 6.7.2.3.2.20:
19 Candidate Frequency Search Report Message.
22 part number of the Pilot Phase Measurement data, in
27 total number of parts that the Pilot Phase
28 Measurement data is divided into, in the range from 1
30 total number of parts minus one.
31 NUM_PILOTS_P – Number of pilots in this part.
33 pilots to be reported in this part of the response
34 element (not including additional pilots, as defined by
35 NUM_ADD_PILOTS_P) in the range from 0 to 63.
3-41
TIA/EIA/IS-801-1
1 The mobile station shall include NUM_PILOTS_P occurrences of the following three fields for
2 each pilot in the Active Set, and for each pilot in the Candidate or Neighbor Set whose pilot
15
3 strength is greater than T_DROP , other than the pilot identified by the REF_PN field. The
4 mobile station may also include other pilots.
5 PILOT_PN_PHASE – Pilot measured phase.
6 The mobile station shall set this field to the phase of
7 the pilot PN sequence relative to the zero offset pilot PN
8 sequence of this pilot, in units of 1/16 TIA/EIA-95 PN
9 chips, in the range from 0 to 32,767.9375 chips. The
10 pilot arrival time shall be the time of occurrence, as
11 measured at the mobile station antenna connector, of
12 the earliest arriving usable multipath component of
13 the pilot. See 6.6.6.2.4 of TIA/EIA-95-B.
14 PILOT_STRENGTH – Pilot strength.

16 -2 × 10 log10 PS,
17 where PS is the strength of this pilot, measured as

18 specified in 6.6.6.2.2 of TIA/EIA-95-B. If this value is
19 less than 0, the mobile station shall set this field to
20 ‘000000’. If this value is greater than ‘111111’, the
22 RMS_ERR_PHASE – RMS error in phase measurement. This field
23 represents the mobile station’s best estimate of the
24 standard deviation of PILOT_PN_PHASE.
25 The mobile station shall set this field to the estimated
26 standard deviation of PILOT_PN_PHASE. A “floating-
27 point” representation is used where the 3 most
28 significant bits constitute the exponent and the 3 least
29 significant bits constitute the mantissa as specified in
30 Table 3.2.4.2-9.
31
15 T_DROP is defined in TIA/EIA-95-B.
3-42
TIA/EIA/IS-801-1
1 Table 3.2.4.2-9. RMS Error in Pilot Phase Measurement Representation
RMS Error in Pilot

Index value, i Floating-Point
Exponent, X Mantissa, Y Phase Measurement
= Y + 8×X value, fi
Value, σ (m)
‘000’ ‘000’ 0 1 σ<1
‘000’ ‘001’ 1 1.125 1 ≤ σ < 1.125
2 ≤ i ≤ 61 Fi-1 ≤ σ < fi
X
X Y (1 + Y/8)×2
‘111’ ‘110’ 62 224 208 ≤ σ < 224
‘111’ ‘111’ 63 Not Applicable 224 ≤ σ
3 ADD_PILOTS_INCL – Additional pilots included.

4 If this part of the response element includes additional
5 pilots belonging to a different CDMA channel number
6 or to a different CDMA band class, the mobile station
9 ADD_BAND_CLASS – Additional band class.
10 If ADD_PILOTS_INCL is set to ‘1’, the mobile station
11 shall set this field to the CDMA band class of the
12 additional pilots that are reported in this part of the
13 response element, as specified in TSB58-B; otherwise
14 the mobile station shall not include this field.
15 ADD_CDMA_FREQ – Additional frequency assignment.
17 shall set this field to the CDMA channel number, in
18 the specified CDMA band class, of the additional pilots
19 that are reported in the response element, as specified
20 in 6.1.1.1 of TIA/EIA-95-B; otherwise the mobile
21 station shall not include this field.
22 ADD_TOTAL_RX_PWR – Total received power on the additional frequency.
24 shall set this field to
25 max ( 0, min ( 31, (total_received_power+110)/2 ))
26 where total_received_power is the mean input power
27 received by the mobile station on frequency
28 ADD_CDMA_FREQ, in dBm/1.23 MHz; otherwise the
29 mobile station shall omit this field.
3-43
TIA/EIA/IS-801-1
1 Note that this definition is taken from the

2 SF_TOTAL_RX_PWR (serving frequency total received
3 power) defined in TIA/EIA-95-B Section 6.7.2.3.2.20:
4 Candidate Frequency Search Report Message.
5 NUM_ADD_PILOTS_P – Number of additional pilots in this part.
7 shall set this field to the number of additional pilots to
8 be reported in this part of the response element, in the
10 conveys the number of pilots minus one; otherwise the
11 mobile station shall not include this field.
12 The mobile station shall include NUM_ADD_PILOTS_P occurrences of the following three
15
13 fields for pilots whose pilot strength is greater than T_DROP . The mobile station may also
14 include other pilots.
15 ADD_PILOT_PN_PH – Additional pilot measured phase.
16 The mobile station shall set this field to the phase of
17 the pilot PN sequence relative to the zero offset pilot PN
18 sequence of this pilot, in units of 1/16 TIA/EIA-95 PN
19 chips, in the range from 0 to 32,767.9375 chips. The
20 pilot arrival time shall be the time of occurrence, as
21 measured at the mobile station antenna connector, of
22 the earliest arriving usable multipath component of
23 the pilot. See 6.6.6.2.4 of TIA/EIA-95-B.
24 ADD_PILOT_STRENGTH – Pilot strength.
26 -2 × 10 log10 PS,
27 where PS is the strength of this pilot, measured as

28 specified in 6.6.6.2.2 of TIA/EIA-95-B. If this value is
29 less than 0, the mobile station shall set this field to
30 ‘000000’. If this value is greater than ‘111111’, the
32 ADD_RMS_ERR_PH – Additional pilot RMS error in phase measurement.
33 This field represents the mobile station’s best estimate
34 of the standard deviation of ADD_PILOT_PN_PH.
35 The mobile station shall set this field to a value
36 according to Table 3.2.4.2-9.
3-44
TIA/EIA/IS-801-1

6 If RESP_TYPE is equal to ‘0001’ (Provide Location Response), RESP_PAR_RECORD shall
7 include the following variable length record:
8
Field Length (bits)

TIME_REF_CDMA 14
LAT 25
LONG 26
LOC_UNCRTNTY_ANG 4
LOC_UNCRTNTY_A 5
LOC_UNCRTNTY_P 5
FIX_TYPE 1
VELOCITY_INCL 1
VELOCITY_HOR 0 or 9
HEADING 0 or 10
VELOCITY_VER 0 or 8
CLOCK_INCL 1
CLOCK_BIAS 0 or 18
CLOCK_DRIFT 0 or 16
HEIGHT_INCL 1
HEIGHT 0 or 14
LOC_UNCRTNTY_V 0 or 5

11 The mobile station shall set this field to (t/50 mod
3-45
TIA/EIA/IS-801-1
1 LAT – Latitude.
25
3 complement value of the latitude, in units of 180/2
-24
4 degrees, in the range from -90 degrees to +90×(1-2 )
5 degrees, referenced to the WGS-84 reference ellipsoid,
6 counting positive angles north of the equator and
7 negative angles south of the equator,
8 LONG – Longitude.
26
10 complement value of the longitude, in units of 360/2
11 degrees, in the range from -180 degrees to
-25
12 +180×(1-2 ) degrees, referenced to the WGS-84
13 reference ellipsoid, counting positive angles east of the
14 Greenwich meridian and negative angles west of the
15 Greenwich meridian.
16 LOC_UNCRTNTY_ANG – Angle of axis with respect to True North for position
17 uncertainty.
18 The mobile station shall set this field to the angle of
19 axis for position uncertainty, in units of 5.625 degrees,
20 in the range from 0 to 84.375 degrees, where 0 degrees
21 is True North and the angle increases toward the East.
22 LOC_UNCRTNTY_A – Standard deviation of axis along angle specified for
23 position uncertainty.
24 The mobile station shall set this field to represent the
25 standard deviation of axis along angle specified for
26 position uncertainty as specified in Table 3.2.4.2-10.
3-46
TIA/EIA/IS-801-1
1 Table 3.2.4.2-10. Position Uncertainty
LOC_UNCRTNTY Standard Deviation for Position Uncertainty (meters)

‘00000’ 0.5
‘00001’ 0.75
‘00010’ 1
‘00011’ 1.5
‘00100’ 2
‘00101’ 3
‘00110’ 4
‘00111’ 6
‘01000’ 8
‘01001’ 12
‘01010’ 16
‘01011’ 24
‘01100’ 32
‘01101’ 48
‘01110’ 64
‘01111’ 96
‘10000’ 128
‘10001’ 192
‘10010’ 256
‘10011’ 384
‘10100’ 512
‘10101’ 768
‘10110’ 1,024
‘10111’ 1,536
‘11000’ 2,048
‘11001’ 3,072
‘11010’ 4,096
‘11011’ 6,144
‘11100’ 8,192
‘11101’ 12,288
‘11110’ >12,288
‘11111’ Not computable
3-47
TIA/EIA/IS-801-1
2 LOC_UNCRTNTY_P – Standard deviation of axis perpendicular to angle

3 specified for position uncertainty.
4 The mobile station shall set this field to represent the
5 Standard Deviation of Axis Perpendicular to Angle
6 Specified for Position Uncertainty as specified in Table
7 3.2.4.2-10.
8 FIX_TYPE – Fix type.
9 The mobile station shall set this field to ‘0’ for 2D fix
10 and to ‘1’ for 3D fix.
11 VELOCITY_INCL – Velocity information included.
12 If velocity information is included in this response
13 element, the mobile station shall set this field to ‘1’. If
16
14 velocity information is not included in this response
15 element, the mobile station shall set this field to ‘0’.
16 VELOCITY_HOR – Horizontal velocity magnitude.
17 If VELOCITY_INCL is set to ‘1’, the mobile station shall
18 set this field to the horizontal velocity, in units of 0.25
19 m/s, in the range from 0 to 127.75 m/s; otherwise the
20 mobile station shall not include this field.
21 Note that this field is not included for cases in which
22 the measurement technique does not permit
23 calculation of value.
24 HEADING – Heading.
25 If VELOCITY_INCL is set to ‘1’, the mobile station shall
10
26 set this field to Heading, in units of 360/2 degrees, in
-10
27 the range from 0 to 360×(1-2 ) degrees; otherwise the
28 mobile station shall not include this field, where 0
29 degrees is True North and the angle increases toward
30 the East.
16
Velocity information includes the horizontal and vertical components of velocity, as well
as heading.
3-48
TIA/EIA/IS-801-1
1 VELOCITY_VER – Vertical velocity.

2 If VELOCITY_INCL and FIX_TYPE are set to ‘1’, the
3 mobile station shall set this field to the two’s
4 complement value of Vertical Velocity, in units of 0.5
5 m/s, in the range from -64 m/s to +63.5 m/s;
6 otherwise the mobile station shall not include this
7 field.
11 CLOCK_INCL – Clock information included.
12 If clock information is included in this response
13 element, the mobile station shall set this field to ‘1’. If
14 clock information is not included in this response
15 element, the mobile station shall set this field to ‘0’.
16 CLOCK_BIAS – Clock bias.
17 If CLOCK_INCL is set to ‘1’, the mobile station shall set
18 this field to the clock bias in units of 1 ns, in the range
19 from -13,000 ns to +249,143 ns, where the binary
20 value of the field conveys the clock bias plus 13,000
21 ns; otherwise, the mobile station shall not include this
22 field. This parameter is computed as true GPS time
23 minus mobile station time reference as defined in
24 TIA/EIA-95.
25 Note that as part of a GPS fix, the computation yields
26 an estimate of the discrepancy between the time
27 specified by the local clock and true GPS time. This
28 parameter reports the discrepancy. The main cause of
29 this discrepancy is going to be the propagation delay
30 from the base station to the MS, which is always
31 positive. Accordingly, the range allowed for this
32 parameter is not symmetric.
33 CLOCK_DRIFT – Clock drift.
34 If CLOCK_INCL is set to ‘1’, the mobile station shall set
35 this field to the two’s complement value of the rate of
36 change of clock bias in units of ppb (ns/s), in the
37 range from -32768 ppb (ns/s) to +32767 ppb (ns/s);
38 otherwise the mobile station shall not include this
39 field.
40 HEIGHT_INCL – Height information included.
3-49
TIA/EIA/IS-801-1
1 If height information is included in this response

2 element, the mobile station shall set this field to ‘1’;
3 otherwise, the mobile station shall set this field to ‘0’.
4 HEIGHT – Height.
5 If HEIGHT_INCL is set to ‘1’, the mobile station shall
6 set this field to the height above the WGS-84 reference
7 ellipsoid, in units of 1 meter, in the range from -500 m
8 to 15883 m, where the binary value of the field
9 conveys the height plus 500 m; otherwise, it shall not
10 include this field.
14 LOC_UNCRTNTY_V – Standard deviation of vertical error for position
15 uncertainty.
16 If HEIGHT_INCL is set to ‘1’, the mobile station shall
17 include this field and set this field to represent the
18 Standard Deviation Vertical Error for Position
19 Uncertainty as specified in Table 3.2.4.2-10; otherwise
20 the mobile station shall not include this field.
29 If RESP_TYPE is equal to ‘0110’ (Provide Time Offset Measurement), RESP_PAR_RECORD
31
Field Length (bits)

TIME_REF_MS 24
REF_PN 9
MOB_SYS_T_OFFSET 14
RESERVED 1
32
33 TIME_REF_MS – The time of validity of the parameters reported in this

3-50
TIA/EIA/IS-801-1

3 units of 1 ms, based on mobile station time reference
4 as defined in 6.1.5.1 of TIA/EIA-95-B. This is the time
8 The mobile station shall set this field to the PN
9 sequence offset of the pilot used by the mobile station
10 to derive its time reference, relative to the zero offset
11 pilot PN sequence in units of 64 PN chips.
12 MOB_SYS_T_OFFSET – Mobile station system time offset.
14 complement value of the offset between mobile station
15 time reference and time of occurrence of Reference PN,
16 in units of 1/16 TIA/EIA-95 chips, in the range from
17 -512 to +511.9375 TIA/EIA-95 chips. The sign of this
18 quantity shall be positive if the reference PN occurs
19 earlier than the mobile station time reference;
23 If RESP_TYPE is equal to ‘0111’ (Provide Cancellation Acknowledgement),
25
Field Length (bits)

CANCEL_TYPE_ACK 4
NO_OUT_REQ 1
RESERVED 3
26
27 CANCEL_TYPE_ACK – Cancellation type.

29 CANCEL_TYPE included in the corresponding request
30 element (“Request Cancellation”).
31 NO_OUT_REQ – No outstanding request element.
32 If there is no outstanding request element of the type
33 indicated by CANCEL_TYPE_ACK, the mobile station
3-51
TIA/EIA/IS-801-1

3 4 BASE STATION PROCEDURES
4 4.1 Analog Base Station Procedures

5 The analog base station procedures are defined in [6].
6 4.2 CDMA Base Station Procedures
7 4.2.1 Position Determination Data Message Processing
8 4.2.1.1 Overview
9 The Position Determination Data Message sent by the base station is comprised of request
10 elements and response elements, as specified below.
11 Request elements sent by base station:
12 • Request MS Information
13 • Request Autonomous Measurement Weighting Factors
14 • Request Pseudorange Measurement
15 • Request Pilot Phase Measurement
17 • Request Time Offset Measurement
18 • Request Cancellation
19 Response elements sent by base station:
20 • Reject
21 • Provide BS Capabilities
22 • Provide GPS Acquisition Assistance
23 • Provide GPS Location Assistance – Spherical Coordinates
24 • Provide GPS Location Assistance – Cartesian Coordinates
25 • Provide GPS Sensitivity Assistance
26 • Provide Base Station Almanac
27 • Provide GPS Almanac
28 • Provide GPS Ephemeris
29 • Provide GPS Navigation Message Bits
31 • Provide GPS Almanac Correction
4-52
TIA/EIA/IS-801-1
1 • Provide GPS Satellite Health Information

2 The Position Determination Data Message received by the base station is also comprised of
3 request elements and response elements, as specified below.
4 Request elements received by base station:
5 • Request BS Capabilities
6 • Request GPS Acquisition Assistance
7 • Request GPS Location Assistance
8 • Request GPS Sensitivity Assistance
9 • Request Base Station Almanac
10 • Request GPS Almanac
11 • Request GPS Ephemeris
12 • Request GPS Navigation Message Bits
14 • Request GPS Almanac Correction
15 • Request GPS Satellite Health Information
16 Response elements received by base station:
17 • Reject
18 • Provide MS Information
19 • Provide Autonomous Measurement Weighting Factors
20 • Provide Pseudorange Measurement
21 • Provide Pilot Phase Measurement
23 • Provide Time Offset Measurement
24 • Provide Cancellation Acknowledgement
25 Response elements sent by the base station may be generated in response to request
26 elements received by the base station or they may be generated as unsolicited response
27 elements. Every request element includes a REQ_TYPE (request element type) field that
28 uniquely identifies the request element (See Table 4.2.4-2). Every response element
29 includes a RESP_TYPE (response element type) field that uniquely identifies the response
30 element (See Table 4.2.4-3). Multiple response elements may be associated with a single
31 request element. Unsolicited response elements are sent with the UNSOL_RESP flag set to
32 ‘1’ (see 4.2.4).
33 4.2.1.2 Requirements
34 Each Position Determination Data Message shall contain at least one request element, or at
35 least one part of a response element, or both. No more than one request element of a
4-2
TIA/EIA/IS-801-1
1 specific REQ_TYPE shall be included in a Position Determination Data Message. Each

2 request element shall be fully contained in a Position Determination Data Message. Some
3 response elements may be divided in parts (see 4.2.4.2). Each response element part shall
4 be fully contained in a Position Determination Data Message.
5 If the base station sends a response element in response to a received request element, it
6 shall comply with Table 4.2.1.2-1. A “Reject” shall not be sent as a response element to a
7 “Request BS Capabilities” request element.
8 If one or more response elements from the base station can be useful to the mobile station
9 in responding to a request from the base station, the base station should include all or part
10 of each response element and the request element in the same Position Determination Data
11 Message.
12 Upon receiving a Position Determination Data Message, the base station should examine the
13 received response elements prior to processing the request elements.
14
4-3
TIA/EIA/IS-801-1
1 Table 4.2.1.2-1. Response Elements Sent in Response to Received Request Elements
Request element received Possible response elements

Request BS Capabilities Provide BS Capabilities
Reject
Request GPS Acquisition Assistance
Provide GPS Acquisition Assistance
Reject
Provide GPS Location Assistance –
Spherical Coordinates And
Request GPS Location Assistance Provide GPS Acquisition Assistance
Provide GPS Location Assistance –
Cartesian Coordinates And
Provide GPS Acquisition Assistance
Reject
Request GPS Sensitivity Assistance
Provide GPS Sensitivity Assistance
Reject
Request Base Station Almanac
Provide Base Station Almanac
Reject
Request GPS Almanac
Provide GPS Almanac
Reject
Request GPS Ephemeris
Provide GPS Ephemeris
Reject
Request GPS Navigation Message Bits
Provide GPS Navigation Message Bits
Reject
Request Location Response
Provide Location Response
Reject
Request GPS Almanac Correction
Provide GPS Almanac Correction
Reject
Request GPS Satellite Health
Information Provide GPS Satellite Health
Information
3 No more than one request element shall be outstanding at any given time for each
4 REQ_TYPE in any given session. If an additional request element is received while there is
5 an outstanding request element of the same type in the same session, the additional
6 request element shall be discarded. A received (or sent) request element is considered
7 outstanding until all of the corresponding response elements or a “Reject” for the request
4-4
TIA/EIA/IS-801-1
1 element have been sent (or received). Unsolicited response elements shall have the
2 UNSOL_RESP flag set to ‘1’.
3 If a “Reject” constitutes the sent response element, its REJ_REQ_TYPE shall be set to the
4 REQ_TYPE of the corresponding request element.
5 4.2.2 Point-to-point Procedures

6 This section defines the procedures for the processing of mobile-terminated Position
7 Determination Data Messages that are addressed to individual mobile stations and for the
8 processing of all mobile-originated Position Determination Data Messages.
9 4.2.2.1 Control Channel Procedure
10 4.2.2.1.1 Base Station Position Determination Data Message Termination

11 A base station supporting Position Determination shall accept and shall process Data Burst
12 Messages received on the CDMA Access Channel (see 6.7.1.3.2.3 of TIA/EIA-95-B). The
13 processing of TIA/EIA-95-B Layer-2 fields shall be in accordance with TIA/EIA-95-B. Data
14 Burst Messages used to transport Position Determination request and response elements
15 shall always be acknowledged (Layer 2) and the in-order delivery over the air interface shall
16 be guaranteed by the transmitting entities: Mobile station and base station.
17 The base station shall process all Data Burst Messages received on the Access Channel and
18 having the BURST_TYPE field set to ‘000101’.
19 The base station shall discard the message without further processing if one or more of the
20 following is true:
24 Otherwise, the base station shall process the Position Determination Data contained in the
25 CHARi fields of the received Data Burst Message (see 6.7.1.3.2.3 of TIA/EIA-95-B), as
26 described below.
27 4.2.2.1.1.1 Mobile Station Request Elements Received

28 If the base station does not support the requested capability, the base station shall respond
29 with a “Reject” response element with the appropriate reject reason, unless the mobile
30 station request element is “Request BS Capabilities”; otherwise, the base station shall
31 include the appropriate response elements in the response Position Determination Data
32 (see 4.2.4) as described below. The response Position Determination Data shall reside in
17
33 the CHARi fields of the response Data Burst Message (see 7.7.2.3.2.9 of TIA/EIA-95-B).
34 • Request BS Capability: The base station shall respond with the “Provide BS
35 Capabilities” response element.
17
4-5
TIA/EIA/IS-801-1
1 • Request GPS Acquisition Assistance: The base station shall respond with the
2 “Provide GPS Acquisition Assistance” response element.
3 – If DOPP_REQ is set to ‘1’, the “Provide GPS Acquisition Assistance” response
th
4 element shall include the Doppler 0 order term and ADD_DOPP_INCL flag;
5 otherwise, the “Provide GPS Acquisition Assistance” response element should
th
6 not include the Doppler 0 order term and ADD_DOPP_INCL flag.
7 – If ADD_DOPP_REQ is set to ‘1’, the “Provide GPS Acquisition Assistance”
8 response element shall include the high-order Doppler and the Doppler
9 search window terms; otherwise, the “Provide GPS Acquisition Assistance”
10 response element should not include the high-order Doppler and the Doppler
11 search window terms.
12 – If CODE_PH_PAR_REQ is set to ‘1’, the “Provide GPS Acquisition Assistance”
13 response element shall include the code phase parameters; otherwise, the
14 “Provide GPS Acquisition Assistance” response element should not include
15 the code phase parameters.
16 – If AZ_EL_REQ is set to ‘1’, the “Provide GPS Acquisition Assistance” response
17 element shall include the azimuth and elevation angles; otherwise, the
19 the azimuth and elevation angles.
20 • Request GPS Location Assistance: The base station shall respond with the “Provide
21 GPS Location Assistance – Spherical Coordinates” or with the “Provide GPS Location
22 Assistance – Cartesian Coordinates” response element. If COORD_TYPE is set to ‘1’,
23 the base station shall provide the “Provide GPS Location Assistance – Spherical
24 Coordinates” response element; otherwise, the base station shall provide the
25 “Provide GPS Location Assistance – Cartesian Coordinates” response element. The
26 base station shall also send the “Provide GPS Acquisition Assistance” response
27 element in the same Position Determination Data Message that contains the “Provide
28 GPS Location Assistance – Spherical Coordinates” response element or the “Provide
29 GPS Location Assistance – Cartesian Coordinates” response element. The value of
30 NUM_SV_P in each part of the “Provide GPS Location Assistance – Spherical
31 Coordinates” response element or the “Provide GPS Location Assistance – Cartesian
32 Coordinates” response element shall be the same as the value of NUM_SV_P in the
33 part of the “Provide GPS Acquisition Assistance” response element that appears in
34 the same Position Determination Data Message. The “Provide GPS Location
35 Assistance – Spherical Coordinates” response element or the “Provide GPS Location
36 Assistance – Cartesian Coordinates” response element shall have the satellite
37 related fields repeated in the same SV_PRN_NUM order as contained in the “Provide
38 GPS Acquisition Assistance” response element.
39 • Request GPS Sensitivity Assistance: The base station shall respond with a “Provide
40 GPS Sensitivity Assistance” response element in one or more response Position
41 Determination Data Messages, according to the number of parts into which the
42 response element is divided. The base station shall set the TOTAL_PARTS fields to
4-6
TIA/EIA/IS-801-1
1 identical value in all parts of the same “Provide GPS Sensitivity Assistance”
2 message.
3 • Request Base Station Almanac: The base station shall respond with a “Provide Base
4 Station Almanac” response element in one or more response Position Determination
5 Data Messages, according to the number of parts into which the response element
6 is divided. The base station shall set the REF_PN, TIME_CRRCTION_REF, LAT_REF,
7 LONG_REF, HEIGHT_REF and TOTAL_PARTS fields to identical values in all parts of
8 the same “Provide Base Station Almanac” message. If EXT_BS_ALM is set to ‘1’, the
9 “Provide Base Station Almanac” response element shall include the extended base
10 station almanac; otherwise, the “Provide Base Station Almanac” response element
11 shall include the base station almanac.
12 • Request GPS Almanac: The base station shall respond with a “Provide GPS Almanac”
13 response element in one or more response Position Determination Data Messages,
14 according to the number of parts into which the response element is divided. The
15 base station shall set the TOTAL_PARTS fields to identical value in all parts of the
16 same “Provide GPS Almanac” message.
17 • Request GPS Ephemeris: The base station shall respond with a “Provide GPS
18 Ephemeris” response element in one or more response Position Determination Data
19 Messages, according to the number of parts into which the response element is
20 divided. If AB_PAR_REQ is set to ‘1’, the “Provide GPS Ephemeris” response element
21 shall include the Alpha and Beta parameters; otherwise, the “Provide GPS
22 Ephemeris” response element should not include the Alpha and Beta parameters.
23 The base station shall set the TOTAL_PARTS, AB_PAR_INCL, ALPHA_0, ALPHA_1,
24 ALPHA_2, ALPHA_3, BETA_0, BETA_1, BETA_2 and BETA_3 fields to identical
25 values in all parts of the same “Provide GPS Ephemeris” message.
26 • Request GPS Navigation Message Bits: The base station shall respond with a
27 “Provide GPS Navigation Message Bits” response element in one or more response
28 Position Determination Data Messages, according to the number of parts into which
29 the response element is divided. The base station shall set the TOTAL_PARTS fields
30 to identical value in all parts of the same “Provide GPS Navigation Message Bits”
31 message. If SUBF_4_5_REQ is set to ‘1’, the “Provide GPS Navigation Message Bits”
32 response element shall include the subframes 4 and 5; otherwise, the “Provide GPS
33 Navigation Message Bits” response element shall not include the subframes 4 and 5.
34 • Request Location Response: The base station shall respond with the “Provide
35 Location Response“ response element.
36 – If HEIGHT_REQ is set to ‘1’, the Location response element should include
37 height information; otherwise, the “Provide Location Response” response
38 element should not include height information.
40 element should include clock correction for mobile station time; otherwise,
41 the “Provide Location Response” response element should not include clock
42 correction for mobile station time.
4-7
TIA/EIA/IS-801-1

4 • Request GPS Almanac Correction: The base station shall respond with a “Provide
5 GPS Almanac Correction” response element in one or more response Position
7 response element is divided. The base station shall set the REF_TIME and
8 TOTAL_PARTS fields to identical values in all parts of the same “Provide GPS
9 Almanac Correction” message.
10 • Request GPS Satellite Health Information: The base station shall respond with the
11 “Provide GPS Satellite Health Information” response element.
12 4.2.2.1.1.2 Mobile Station Response Elements Received

13 The base station should process and should make use of the mobile station response
14 elements. Upon receiving a Position Determination Data Message, the base station should
15 examine the received response elements prior to processing the request elements.
16 4.2.2.1.2 Base Station Position Determination Data Message Origination

18 The requirements of this section apply when Position Determination Data Messages
19 addressed to individual mobile stations are to be sent by the base station and the
20 destination mobile station is not on a Traffic Channel.
21 When the base station has to send one (or more) Position Determination Data Message(s),
22 and the addressed mobile station is not on a Traffic Channel, the base station shall
23 determine whether the Position Determination Data Message(s) is (are) suitable to be sent on
18
24 the Paging Channel. If the Position Determination Data Message(s) is (are) suitable, the
25 base station may form one (or more) Paging Channel Data Burst Message(s) (see 7.7.2.3.2.9
26 of TIA/EIA-95-B), setting BURST_TYPE to ‘000101’. The base station shall set the
27 MSG_NUMBER and NUM_MSGS fields to 1, and shall set the NUM_FIELDS field to the
28 number of characters in the Position Determination Data Message(s) (as appropriate).
29 When a Position Determination Data Message is to be sent on the Paging Channel, the base
30 station shall send the message following the procedures specified in 7.6.2 of TIA/EIA-95-B.
31 The base station may send the Position Determination Data Message throughout the area
32 where the mobile is registered. Alternatively, the base station may page the mobile station
33 to determine which Paging Channel to use to communicate with the mobile; the base
34 station may use Service Option 35 or 36 in the Page Record; then, the base station may
35 send the Position Determination Data Message on the Paging Channel corresponding to the
36 Access Channel on which the mobile station responded. The base station may then send a
37 Release Order to the mobile station.
18
The criteria for suitability are implementation dependent.
4-8
TIA/EIA/IS-801-1
1 If the Position Determination Data Message(s) is (are) unsuitable for transmission on the
19
2 Paging Channel , the base station shall send the Position Determination Data Message(s) on
3 the CDMA Traffic Channel, following the procedures defined in 4.2.2.3.
4 The base station shall set the ACK_REQ Layer-2 field to ‘1’. The base station shall
5 guarantee the in-order delivery of Position Determination Data Messages.

7 If “Provide GPS Acquisition Assistance” is sent as an unsolicited response element, the base
8 station shall set CODE_PH_PAR_INCL to ‘1’ and it shall include REFERENCE_PN,
9 SV_CODE_PH, SV_CODE_PH_INT, GPS_BIT_NUM and SV_CODE_PH_WIN.
10 If “Provide GPS Location Assistance – Spherical Coordinates” or the “Provide GPS Location
11 Assistance – Cartesian Coordinates” is sent as an unsolicited response element, the base
12 station shall also send “Provide GPS Acquisition Assistance” response element in the same
13 Position Determination Data Message. The value of NUM_SV_P in each part of the “Provide
14 GPS Location Assistance – Spherical Coordinates” response element or the “Provide GPS
15 Location Assistance – Cartesian Coordinates” response element shall be the same as the
16 value of NUM_SV_P in the part of the “Provide GPS Acquisition Assistance” response
17 element that appears in the same Position Determination Data Message. The “Provide GPS
18 Location Assistance – Spherical Coordinates” response element or the “Provide GPS
19 Location Assistance – Cartesian Coordinates” response element shall have the satellite
20 related fields repeated in the same SV_PRN_NUM order as contained in the “Provide GPS
21 Acquisition Assistance” response element.

23 A “Request Autonomous Measurement Weighting Factors” shall not be issued unless a
24 “Request Location Response” is issued in the same Position Determination Data Message.
25 4.2.2.2 Authentication Procedures

26 If the mobile station includes authentication information when sending an activation
27 origination, the base station should process the authentication data as required in 7.3.1 of
28 TIA/EIA-95-B. During the position determination session, the base station should invoke
29 signaling message encryption whenever available, as appropriate.
30 4.2.2.3 Traffic Channel Procedure
31 4.2.2.3.1 Message Encryption

32 To enhance the security of the position determination session and to protect sensitive
33 subscriber location information, the base station should enable message encryption as
19
For example, the choice to use the Paging Channel or a Forward Traffic Channel, when
multiple Position Determination Data Messages are waiting to be transmitted, is
implementation dependent.
4-9
TIA/EIA/IS-801-1
1 appropriate (see 7.3.2 of TIA/EIA-95-B). Encryption of the Forward and Reverse CDMA
2 Traffic Channel messages is defined in Annex A of TIA/EIA-95-B.
3 4.2.2.3.2 Negotiation for the Position Determination Service Option

4 Negotiation for the Position Determination Service Option is only required when no other
5 service option is connected.
6 The Position Determination Service Option described by this standard shall use service
7 option number 35 and is called Service Option 35 when using Multiplex Option 1. The
8 Position Determination Service Option shall use service option number 36 and is called
9 Service Option 36 when using Multiplex Option 2.
10 The base station shall negotiate for Service Option 35 using service negotiation (see
11 4.2.2.3.2.1).
12 The base station shall negotiate for Service Option 36 using service negotiation (see
13 4.2.2.3.2.1).
14 4.2.2.3.2.1 Procedures Using Service Negotiation

15 The base station shall perform service negotiation for Service Option 35 or Service Option
16 36 as described in TIA/EIA-95-B. The negotiated service configuration shall include only
17 valid attributes for the negotiated service option consistent with those specified in Tables
18 3.2.3.1.2-1 and 3.2.3.1.2-2.
19 If the base station establishes a service configuration, as specified in a Service Connect
20 Message, that includes a service option connection using Service Option 35 or Service
21 Option 36, then the service option connection shall become part of the current service
22 configuration at the action time associated with the Service Connect Message. Service
23 Option 35 or Service Option 36 is considered to be connected when the current service
24 configuration includes a service option connection for it.
25 The base station shall not send a Service Option Control Message for Service Option 35 or
26 Service Option 36.
27 4.2.2.3.3 Base Station Position Determination Data Message Termination

28 For mobile-originated calls with no dialed digits in the Origination Message, the base station
29 should complete an authentication Unique Challenge-Response Procedure (see 6.3.12.1.5
30 of TIA/EIA-95-B) immediately after assigning the traffic channel. The Unique Challenge-
31 Response Procedure should be completed successfully before Position Determination Data
32 Messages are sent to the mobile station and before any mobile-originated Position
33 Determination Data Messages are forwarded to other network entities.
34 A base station supporting Position Determination shall accept and shall process Data Burst
35 Messages received on the CDMA Reverse Traffic Channel (see 6.7.2.3.2.4 of TIA/EIA-95-B).
36 Processing of TIA/EIA-95-B Layer-2 fields shall be in accordance with TIA/EIA-95-B. Data
37 Burst Messages used to transport Position Determination request and response elements
38 shall always be acknowledged (Layer 2) and the in-order delivery over the air interface shall
39 be guaranteed by the transmitting entities: Mobile station and base station.
4-10
TIA/EIA/IS-801-1
1 The base station shall process all Data Burst Messages received on the Reverse Traffic
2 Channel and having the BURST_TYPE field set to ‘000101’ (as assigned in TSB58-B). The
3 base station shall discard the message without further processing, if one or more of the
4 following is true:
8 Otherwise, the base station shall process the Position Determination Data contained in the
9 CHARi fields of the received Data Burst Message (see 6.7.2.3.2.4 of TIA/EIA-95-B), as
10 described in the next section.
11 If the only connected service option is Service Option 35 or Service Option 36, the base
12 station should release the traffic channel when no Position Determination Data Messages
13 have been received or have been sent during a period of time which is implementation-
14 dependent.
15 4.2.2.3.3.1 Mobile Station Request Elements Received

16 If the base station does not support the requested capability, the base station shall respond
17 with a “Reject” response element with the appropriate reject reason, unless the mobile
18 station request element is “Request BS Capabilities”; otherwise, the base station shall
19 include the appropriate response elements in the response Position Determination Data
20 (see 4.2.4) as described below. The response Position Determination Data shall reside in
20
21 the CHARi fields of the response Data Burst Message (see 7.7.3.3.2.4 of TIA/EIA-95-B).
22 • Request BS Capability: The base station shall respond with the “Provide BS
23 Capabilities” response element.
24 • Request GPS Acquisition Assistance: The base station shall respond with the
25 “Provide GPS Acquisition Assistance” response element.
26 – If DOPP_REQ is set to ‘1’, the “Provide GPS Acquisition Assistance” response
th
27 element shall include the Doppler 0 order term and ADD_DOPP_INCL flag;
28 otherwise, the “Provide GPS Acquisition Assistance” response element should
th
29 not include the Doppler 0 order term and ADD_DOPP_INCL flag.
30 – If ADD_DOPP_REQ is set to ‘1’, the “Provide GPS Acquisition Assistance”
31 response element shall include the high-order Doppler and Doppler search
32 window terms; otherwise, the “Provide GPS Acquisition Assistance” response
33 element should not include the high-order Doppler and Doppler search
34 window terms.
35 – If CODE_PH_PAR_REQ is set to ‘1’, the “Provide GPS Acquisition Assistance”
36 response element shall include the code phase parameters; otherwise, the
20
4-11
TIA/EIA/IS-801-1

2 the code phase parameters.
3 – If AZ_EL_REQ is set to ‘1’, the “Provide GPS Acquisition Assistance” response
4 element shall include the azimuth and elevation angles; otherwise, the
6 the azimuth and elevation angles.
7 • Request GPS Location Assistance: The base station shall respond with the “Provide
8 GPS Location Assistance – Spherical Coordinates” or with the “Provide GPS Location
9 Assistance – Cartesian Coordinates” response elements. If COORD_TYPE is set to
10 ‘1’, the base station shall provide the “Provide GPS Location Assistance – Spherical
11 Coordinates” response element; otherwise, the base station shall provide the
12 “Provide GPS Location Assistance – Cartesian Coordinates” response element. The
13 base station shall also send the “Provide GPS Acquisition Assistance” response
14 element in the same Position Determination Data Message that contains the “Provide
15 GPS Location Assistance – Spherical Coordinates” response element or the “Provide
16 GPS Location Assistance – Cartesian Coordinates” response element. The value of
17 NUM_SV_P in each part of the “Provide GPS Location Assistance – Spherical
18 Coordinates” response element or the “Provide GPS Location Assistance – Cartesian
19 Coordinates” response element shall be the same as the value of NUM_SV_P in the
20 part of the “Provide GPS Acquisition Assistance” response element that appears in
21 the same Position Determination Data Message. The “Provide GPS Location
22 Assistance – Spherical Coordinates” response element or the “Provide GPS Location
23 Assistance – Cartesian Coordinates” response element shall have the satellite
24 related fields repeated in the same SV_PRN_NUM order as contained in the “Provide
25 GPS Acquisition Assistance” response element.
26 • Request GPS Sensitivity Assistance: The base station shall respond with a “Provide
27 GPS Sensitivity Assistance” response element in one or more response Position
29 response element is divided. The base station shall set the TOTAL_PARTS fields to
30 identical value in all parts of the same “Provide GPS Sensitivity Assistance”
31 message.
32 • Request Base Station Almanac: The base station shall respond with a “Provide Base
33 Station Almanac” response element in one or more response Position Determination
34 Data Messages, according to the number of parts into which the response element
35 is divided. The base station shall set the REF_PN, TIME_CRRCTION_REF, LAT_REF,
36 LONG_REF, HEIGHT_REF and TOTAL_PARTS fields to identical values in all parts of
37 the same “Provide Base Station Almanac” message. If EXT_BS_ALM is set to ‘1’, the
38 “Provide Base Station Almanac” response element shall include the extended base
39 station almanac; otherwise, the “Provide Base Station Almanac” response element
40 shall include the base station almanac
41 • Request GPS Almanac: The base station shall respond with a “Provide GPS Almanac”
42 response element in one or more response Position Determination Data Messages,
43 according to the number of parts into which the response element is divided. The
4-12
TIA/EIA/IS-801-1
1 base station shall set the TOTAL_PARTS fields to identical value in all parts of the
2 same “Provide GPS Almanac” message.
3 • Request GPS Ephemeris: The base station shall respond with a “Provide GPS
4 Ephemeris” response element in one or more response Position Determination Data
5 Messages, according to the number of parts into which the response element is
6 divided. If AB_PAR_REQ is set to ‘1’, the “Provide GPS Ephemeris” response element
7 shall include the Alpha and Beta parameters; otherwise, the “Provide GPS
8 Ephemeris” response element should not include the Alpha and Beta parameters.
9 The base station shall set the TOTAL_PARTS, AB_PAR_INCL, ALPHA_0, ALPHA_1,
10 ALPHA_2, ALPHA_3, BETA_0, BETA_1, BETA_2 and BETA_3 fields to identical
11 values in all parts of the same “Provide GPS Ephemeris” message.
12 • Request GPS Navigation Message Bits: The base station shall respond with a
13 “Provide GPS Navigation Message Bits” response element in one or more response
14 Position Determination Data Messages, according to the number of parts into which
15 the response element is divided. The base station shall set the TOTAL_PARTS fields
16 to identical value in all parts of the same “Provide GPS Navigation Message Bits”
17 message. If SUBF_4_5_REQ is set to ‘1’, the “Provide GPS Navigation Message Bits”
18 response element shall include the subframes 4 and 5; otherwise, the “Provide GPS
19 Navigation Message Bits” response element shall not include the subframes 4 and 5.
20 • Request Location Response: The base station shall respond with the “Provide
21 Location Response” response element.
24 Response” response element should not include height information
26 element should include clock correction for mobile station time; otherwise,
27 the “Provide Location Response” response element should not include clock
28 correction for mobile station time.
32 • Request GPS Almanac Correction: The base station shall respond with a “Provide
33 GPS Almanac Correction” response element in one or more response Position
35 response element is divided. The base station shall set the REF_TIME and
36 TOTAL_PARTS fields to identical values in all parts of the same “Provide GPS
37 Almanac Correction” message.
38 • Request GPS Satellite Health Information: The base station shall respond with the
39 “Provide GPS Satellite Health Information” response element.
40 4.2.2.3.3.2 Mobile Station Response Elements Received
4-13
TIA/EIA/IS-801-1
1 The base station should process and should make use of the mobile station response
2 elements. Upon receiving a Position Determination Data Message, the base station should
3 examine the received response elements prior to processing the request elements.
4 4.2.2.3.4 Traffic Channel Setup

5 When a base station is to send Position Determination data on a Traffic Channel, and the
6 addressed mobile station is not on a Traffic Channel, the following procedures apply.
7 The mobile station address shall be used for messages sent over the paging channel. The
8 base station shall page the mobile station and establish a Traffic Channel using the
9 procedures defined in 7.6 of TIA/EIA-95-B. The base station shall request Service Option
10 35 or Service Option 36.
11 When the base station enters the Conversation Substate, the base station may send the
12 Position Determination Data Messages in accordance with the procedures defined in
13 4.2.2.3.5.
14 4.2.2.3.5 Base Station Position Determination Data Message Origination in the

15 Conversation Substate

17 The requirements of this section shall be followed when the addressed mobile station is in
18 the TIA/EIA-95-B Conversation Substate of the Mobile Station Control on the Traffic Channel
19 State.
20 The base station shall form one (or more) Data Burst Message(s) (see 7.7.3.3.2.4 of TIA/EIA-
21 95-B), setting BURST_TYPE to ‘000101’ and send the message(s) on the Forward Traffic
22 Channel. The base station shall set the MSG_NUMBER and NUM_MSGS fields to 1 and
23 shall set the NUM_FIELDS field to the number of octets in the Position Determination Data
24 message (see 4.2.4). The base station shall set the ACK_REQ Layer-2 field to ‘1’.
25 If the only connected service option is Service Option 35 or Service Option 36, the base
26 station should release the traffic channel when Position Determination Data Messages have
27 not been received or have not been sent during a period of time which is implementation-
28 dependent. If any service option in addition to Service Option 35 or Service Option 36 is
29 connected, the base station should initiate Service Negotiation to drop Service Option 35 or
30 Service Option 36 when Position Determination Data Messages have not been received or
31 have not been sent during a period of time which is implementation-dependent. After
32 sending a Position Determination Data Message, the base station should delay the traffic
33 channel release for a period of time sufficient to allow the mobile station to return any
34 requested acknowledgments.

36 If “Provide GPS Acquisition Assistance” is sent as an unsolicited response element, the base
37 station shall set CODE_PH_PAR_INCL to ‘1’ and it shall include REFERENCE_PN,
38 SV_CODE_PH, SV_CODE_PH_INT, GPS_BIT_NUM and SV_CODE_PH_WIN.
4-14
TIA/EIA/IS-801-1
1 If “Provide GPS Location Assistance – Spherical Coordinates” or the “Provide GPS Location
2 Assistance – Cartesian Coordinates” is sent as an unsolicited response element, the base
3 station shall also send “Provide GPS Acquisition Assistance” response element in the same
4 Position Determination Data Message. The value of NUM_SV_P in each part of the “Provide
5 GPS Location Assistance – Spherical Coordinates” response element or the “Provide GPS
6 Location Assistance – Cartesian Coordinates” response element shall be the same as the
7 value of NUM_SV_P in the part of the “Provide GPS Acquisition Assistance” response
8 element that appears in the same Position Determination Data Message. The “Provide GPS
9 Location Assistance – Spherical Coordinates” response element or the “Provide GPS
10 Location Assistance – Cartesian Coordinates” response element shall have the satellite
11 related fields repeated in the same SV_PRN_NUM order as contained in the “Provide GPS
12 Acquisition Assistance” response element.

14 A “Request Autonomous Measurement Weighting Factors” shall not be issued unless a
15 “Request Location Response” is issued in the same Position Determination Data Message.
16 4.2.3 Broadcast Procedures

17 Reserved
18 4.2.4 Forward Link Message Format

19 The forward link Position Determination Data Messages are summarized in Table 4.2.4-1.
20 Table 4.2.4-1. Forward Link Messages
Message Name PD_MSG_TYPE

Message
Reserved for future standardization ‘00000001’ through
‘10111111’
Available for manufacturer-specific ‘11000000’ through
Message definition as specified in
TSB-58
Reserved ‘11111111’
21
22 The Position Determination Data Message from base station to mobile station has the
23 following variable length message format:
24
4-15
TIA/EIA/IS-801-1
Field Length (bits)

SESS_START 1
SESS_END 1
SESS_SOURCE 1
SESS_TAG 5
PD_MSG_TYPE (‘00000000’) 8
NUM_REQUESTS 4
NUM_RESPONSES 4
The base station shall include NUM_REQUESTS occurrences
of the following record:
RESERVED 4
REQ_TYPE 4
REQ_PAR_LEN 8
REQ_PAR_RECORD 8×REQ_PAR_LEN
The base station shall include NUM_RESPONSES
RESERVED 3
UNSOL_RESP 1
RESP_TYPE 4
RESP_PAR_LEN 8
RESP_PAR_RECORD 8 × RESP_PAR_LEN
2 SESS_START – Start-of-session indicator.

3 If the base station has previously sent or received a
4 Position Determination Data Message related to this
6 2.2.1) it shall set this field to ‘0’; otherwise, it shall set
8 SESS_END – End-of-session indicator.
9 If the base station does not expect to receive or send
10 any more Position Determination Data Messages related
12 in 2.2.1) the base station shall set this field to ‘1’;
13 otherwise, it shall set this field to ‘0’. The criteria for
14 setting this field are implementation dependent.
4-16
TIA/EIA/IS-801-1
21
1 SESS_SOURCE – Session-source indicator.
2 If SESS_START is set to ‘1’ the base station shall set
3 this field to ‘0’; otherwise it shall set this field to the
4 same value as the SESS_SOURCE field that appeared
5 in a previously-received or previously-sent Position
6 Determination Data Message that was related to this
8 2.2.1).
9 SESS_TAG – Session tag.
10 If SESS_START is set to ‘0’ the base station shall set
11 this field to the same value as the SESS_TAG field that
12 appeared in a previously-received or previously-sent
13 Position Determination Data Message that was related
15 in 2.2.1); otherwise, the base station shall set this field
16 to one more (modulo 32) than the value it assigned to
17 this field in the latest Position Determination Data
18 Message that it sent with SESS_START set to ‘1’. If no
19 such latest Position Determination Data Message
20 exists, the base station shall set this field to ‘00000’.
21 The definition of “latest” is implementation dependent.
22 PD_MSG_TYPE – Position Determination Data Message type.
23 The base station shall set this field to ‘00000000’.
24 NUM_REQUESTS – Number of request element parameter records.
25 The base station shall set this field to the number of
26 request element parameters record included in the
28 NUM_RESPONSES – Number of response element parameter records.
30 response element parameters record included in the
34 REQ_TYPE – Request element type.
35 The base station shall set this field to the value shown
36 in Table 4.2.4-2.
37
21
This field indicates which side (mobile station or base station) initiated this session.
4-17
TIA/EIA/IS-801-1
1 Table 4.2.4-2. Request Element Type
REQ_TYPE
Description
(binary)
Reserved ‘0000’
Request MS Information ‘0010’
Request Autonomous Measurement Weighting Factors ‘0011’
Request Pseudorange Measurement ‘0100’
Request Pilot Phase Measurement ‘0101’
Request Location Response ‘0001’
Request Time Offset Measurement ‘0110’
Request Cancellation ‘0111’
All other REQ_TYPE values are reserved.
3 REQ_PAR_LEN – Request element parameters length.

5 octets included in the REQ_PAR_RECORD field in the
7 REQ_PAR_RECORD – Request element parameters record.
8 The base station shall set this record as described in
9 4.2.4.1.
11 The base station shall set these bits to ‘000’.
12 UNSOL_RESP – Unsolicited response indicator.
13 The base station shall set this field to ‘1’ if the
14 response element is an unsolicited response element;
15 otherwise the base station shall set this field to ‘0’.
16 RESP_TYPE – Response element type.
18 in Table 4.2.4-3.
4-18
TIA/EIA/IS-801-1
2 Table 4.2.4-3. Response Element Type
RESP_TYPE
Description
(binary)
Reject ‘0000’
Provide BS Capabilities ‘0010’
Provide GPS Acquisition Assistance ‘0100’
Provide GPS Location Assistance – Spherical Coordinates ‘0110’
Provide GPS Location Assistance – Cartesian Coordinates ‘0111’
Provide GPS Sensitivity Assistance ‘0101’
Provide Base Station Almanac ‘0011’
Provide GPS Almanac ‘1000’
Provide GPS Ephemeris ‘1001’
Provide GPS Navigation Message Bits ‘1010’
Provide Location Response ‘0001’
Provide GPS Almanac Correction ‘1011’
Provide GPS Satellite Health Information ‘1100’
All other RESP_TYPE values are reserved.
4 RESP_PAR_LEN – Response element parameters length.

5 The base station shall set RESP_PAR_LEN to the
6 number of octets included in the RESP_PAR_RECORD
7 field in the range from 0 to 255.
8 RESP_PAR_RECORD – Response element parameters record.
9 The base station shall set this record as described in
10 4.2.4.2.
11 4.2.4.1 Request Element Parameters Record

12 If REQ_TYPE in Position Determination Data Message is equal to ‘0010’, or if REQ_TYPE is
13 equal to ‘0011’, the base station shall not include this record. If REQ_TYPE is equal to
14 ‘0001’, or if REQ_TYPE is equal to ‘0100’, or if REQ_TYPE is equal to ‘0101’, or if REQ_TYPE
15 is equal to ‘0110’, or if REQ_TYPE is equal to ‘0111’, the base station shall include the
16 record REQ_PAR_RECORD and set its fields as described below.
17 If REQ_TYPE in Position Determination Data Message is equal to ‘0100’ (Request

18 Pseudorange Measurement), REQ_PAR_RECORD shall include the following fields:
4-19
TIA/EIA/IS-801-1
Field Length (bits)

PREF_RESP_QUAL 3
NUM_FIXES 8
T_BETW_FIXES 8
OFFSET_REQ 1
RESERVED 4
2 PREF_RESP_QUAL – Preferred response quality.

3 The base station shall set this according to 3.2.2.1.1.1
4 and 3.2.2.3.3.1.
5 NUM_FIXES – Number of fixes.
6 The base station shall set this field to the requested
7 number of fixes, in the range from 1 to 256, where the
8 binary value of the field conveys the number of fixes
9 minus one.
10 T_BETW_FIXES – Time between fixes.
12 seconds between fixes, in the range from 0 to 255.
13 OFFSET_REQ – Offset requested.
14 If REF_PN and MOB_SYS_T_OFFSET are requested,
15 the base station shall set this field to ‘1’; otherwise the
16 base station shall set this field to ‘0’.
19 If REQ_TYPE is equal to ‘0101’ (Request Pilot Phase Measurement), REQ_PAR_RECORD
20 shall include the following fields:
21
Field Length (bits)

PREF_RESP_QUAL 3
NUM_FIXES 8
T_BETW_FIXES 8
OFFSET_REQ 1
DESI_PIL_PH_RES 1
RESERVED 3
4-20
TIA/EIA/IS-801-1

3 The base station shall set this field according to
4 3.2.2.1.1.1 and 3.2.2.3.3.1.
9 minus one.
13 OFFSET_REQ – Offset requested.
14 If MOB_SYS_T_OFFSET is requested, the base station
15 shall set this field to ‘1’; otherwise the base station
17 DESI_PIL_PH_RES – Desired pilot phase resolution.
18 If at least one TIA/EIA-95 PN chip pilot phase
19 resolution is requested, the base station shall set this
20 field to ‘0’. If at least 1/8 TIA/EIA-95 PN chip pilot
21 phase resolution is requested, the base station shall
22 set this field to ‘1’.
25 If REQ_TYPE is equal to ‘0001’ (Request Location Response), REQ_PAR_RECORD shall
26 include the following fields:
27
Field Length (bits)

PREF_RESP_QUAL 3
NUM_FIXES 8
T_BETW_FIXES 8
HEIGHT_REQ 1
CLK_COR_GPS_REQ 1
VELOCITY_REQ 1
RESERVED 2
28
4-21
TIA/EIA/IS-801-1

2 The base station shall set this field according to
3 3.2.2.1.1.1 and 3.2.2.3.3.1.
8 minus one.
12 HEIGHT_REQ – Height information requested.
13 If the height information is requested, the base station
16 CLK_COR_GPS_REQ – Clock correction for GPS time requested.
17 If the clock correction for GPS time is requested, the
18 base station shall set this field to ‘1’; otherwise the
20 VELOCITY_REQ – Velocity information requested.
21 If velocity information is requested, the base station
26 If REQ_TYPE is equal to ‘0110’ (Request Time Offset Measurement), REQ_PAR_RECORD
27 shall include the following fields:
28
Field Length (bits)

USE_TIME 1
ACTION_TIME 0 or 6
RESERVED 7 or 1 (as needed)
29
30 USE_TIME – Use action time indicator.

31 This field indicates whether an ACTION_TIME is
32 specified in this request element.
4-22
TIA/EIA/IS-801-1
1 If an ACTION_TIME is specified in this message, the

2 base station shall set this field to ‘1’; otherwise, the
4 ACTION_TIME – Action time.
5 If the USE_TIME field is set to ‘1’, the base station
6 shall set this field to (t mod 64), where t is System
7 Time in units of 80 ms, at which the offset
8 measurement is to take effect. If the USE_TIME field
9 is set to ‘0’ the base station shall not include this field.
11 The base station shall add reserved bits as needed in
12 order to make the length of the request element
14 octets. The base station shall set these bits to ‘0’.
15 If REQ_TYPE is equal to ‘0111’ (Request Cancellation), REQ_PAR_RECORD shall include
16 the following fields:
17
Field Length (bits)

CANCEL_TYPE 4
RESERVED 4
18
19 CANCEL_TYPE – Cancellation type.

20 The base station shall set this field to the type of
21 request element to be cancelled, according to Table
22 4.4.1.1-1.
25 4.2.4.2 Response Element Parameters Record

26 The base station shall set RESP_PAR_RECORD as described below.
27 If RESP_TYPE in Position Determination Data Message is equal to ‘0000’ (Reject),

29
Field Length (bits)
REJ_REQ_TYPE 4
REJ_REASON 3
4-23
TIA/EIA/IS-801-1
RESERVED 1
1 REJ_REQ_TYPE – Reject request type.

2 The base station shall set this field to the value of the
3 REQ_TYPE corresponding to the request element it
4 rejects. See Table 3.2.4-2.
5 REJ_REASON – Reject reason.
7 in Table 4.2.4.2-1.
8
9 Table 4.2.4.2-1. Reject Reason
REJ_REASON
Reason for rejection
(binary)
Capability not supported by the base station ‘000’
Capability normally supported by the base station but ‘001’
temporarily not available or not enabled
All other REJ_REASON values are reserved.
10

13 If RESP_TYPE is equal to ‘0010’ (Provide BS Capabilities), RESP_PAR_RECORD shall
14 include the following fields:
15
Field Length (bits)

BS_LS_REV 6
GPSC_ID 1
AFLTC_ID 1
APDC_ID 8
16
17 BS_LS_REV – The base station location standard revision number.

18 The revision number of IS-801 that the base station is
19 using. The base station shall set this field to ‘000000’.
20 GPSC_ID – GPS capability indicator.
21 If the base station can do all of the following:
4-24
TIA/EIA/IS-801-1
1 • provide the “GPS Assist” response elements

2 (“Provide GPS Acquisition Assistance”; “Provide
3 GPS Location Assistance – Spherical Coordinates”;
4 “Provide GPS Location Assistance – Cartesian
5 Coordinates”; “Provide GPS Sensitivity Assistance”;
6 “Provide GPS Almanac”; “Provide GPS Ephemeris”;
7 “Provide GPS Navigation Message Bits”; “Provide
8 GPS Satellite Health Information”), and
9 • determine the position of the mobile station based
10 on information provided by the mobile station
11 through the GPS response elements (“Provide
12 Autonomous Measurement Weighting Factors”;
13 “Provide Pseudorange Measurement”), and
14 • accept a “Provide Location Response” response
15 element from the mobile station with autonomous
16 positioning technology,
17 then the base station shall set this field to ‘1’;
19 AFLTC_ID – Advanced forward link trilateration capability
20 indicator.
22 • provide the “Provide Base Station Almanac”
23 response element, and
24 • determine the position of the mobile station based
25 on information provided by the mobile station
26 through the “Provide Pilot Phase Measurement”
27 response element, and
31 then the base station shall set this field to ‘1’;
33 APDC_ID – Autonomous position determination capability
34 indicator.
36 • determine the position of the mobile station
37 autonomously (i.e., without mobile station
38 involvement), and
4-25
TIA/EIA/IS-801-1

4 then the base station shall set this field to a value
5 other than ‘00000000’ according to Table 4.2.4.2-2;
6 otherwise the base station shall set this field to
7 ‘00000000’.
8
9 Table 4.2.4.2-2. Autonomous Location Determination Capability in the Base Station
APDC_ID Location Determination Capability
No Autonomous Location Determination

‘00000000’
Capability
‘00000001’ – ‘11111111’ Autonomous Location Technology Identifier
10
4-26
TIA/EIA/IS-801-1
1 If RESP_TYPE is equal to ‘0100’ (Provide GPS Acquisition Assistance), RESP_PAR_RECORD

3
Field Length (bits)

NUM_SV 4
TIME_OF_APP 8
DOPP_INCL 1
ADD_DOPP_INCL 0 or 1
CODE_PH_PAR_INCL 1
REFERENCE_PN 0 or 10
AZ_EL_INCL 1
The base station shall include NUM_SV occurrences of the
following fields:
SV_PRN_NUM 6
DOPPLER0 0 or 12
DOPPLER1 0 or 7
DOPPLER_WIN 0 or 3
SV_CODE_PH 0 or 10
SV_CODE_PH_INT 0 or 5
GPS_BIT_NUM 0 or 2
SV_CODE_PH_WIN 0 or 5
AZIMUTH 0 or 5
ELEVATION 0 or 3
5 NUM_SV – Number of GPS satellites.

7 data fields (one or more) for all applicable satellites, in
8 the range from 1 to 16, where the binary value of the
9 field conveys the number of satellites minus one.
10 TIME_OF_APP – The CDMA system time at the time when the
11 acquisition assistance data is applicable.
12 The base station shall set this field to (t/64 mod
4-27
TIA/EIA/IS-801-1

2 acquisition assistance data is applicable.
3 Note that this field has units of 1.28 s, and therefore
4 this 8-bit field may range beyond 320 s; however, 320
5 evenly divides the number of seconds in a week, thus
6 simplifying changes from CDMA system time to GPS
7 time.
th
8 DOPP_INCL – Doppler (0 order) term included.
9 If DOPPLER0 is included in this response element, the
10 base station shall set this field to ‘1’; otherwise the
12 ADD_DOPP_INCL – Additional Doppler information included.
13 If DOPP_INCL is set to ‘1’, the base station shall
14 include this field and, if DOPPLER1 and
15 DOPPLER_WIN are included in this response element,
16 it shall set ADD_DOPP_INCL to ‘1’; if DOPPLER1 and
17 DOPPLER_WIN are not included in this response
18 element, it shall set ADD_DOPP_INCL to ‘0’. If
19 DOPP_INCL is set to ‘0’, the base station shall not
21 CODE_PH_PAR_INCL – Code phase information included.
22 If code phase information is included in this response
23 element, the base station shall set this field to ‘1’. If
24 code phase information is not included in this
25 response element, the base station shall set this field
26 to ‘0’.
27 REFERENCE_PN – Reference PN.
28 If CODE_PH_PAR_INCL is set to ‘1’, the base station
29 shall include this field. If the SV_CODE_PH
30 information included in this element uses a pilot PN
31 sequence as its reference, then the base station shall
32 set the most significant bit of this field to ‘0’ and the 9
33 least significant bits of this field to the PN sequence
34 offset of the pilot that is used as time reference,
35 relative to the zero offset pilot PN sequence in units of
36 64 PN chips. If the SV_CODE_PH information
37 included in this element does not use any pilot PN
38 sequence as its reference, then the base station shall
39 set this field to ‘1000000000’. See Table 4.2.4.2-3. If
40 CODE_PH_PAR_INCL is set to ‘0’, the base station
4-28
TIA/EIA/IS-801-1
2 Table 4.2.4.2-3. Reference PN
REFERENCE_PN PN sequence offset value

(binary)
‘0xxxxxxxxx’ ‘xxxxxxxxx’
‘1000000000’ No Pilot PN sequence used as reference
All other REFERENCE_PN values are reserved.
4 AZ_EL_INCL – Azimuth and elevation angle included.

5 If azimuth and elevation angle are included in this
6 response element, the base station shall set this field
7 to ‘1’. If azimuth and elevation angle are not included
8 in this response element, the base station shall set
10 SV_PRN_NUM – The satellite PRN number.
12 PRN signal number for which the data is valid. It is
13 represented as an unsigned value in the range from 1
15 satellite PRN number minus one.
th
16 DOPPLER0 – The 0 order Doppler.
17 If DOPP_INCL is set to ‘1’, the base station shall set
th
18 this field to the two’s complement value of the 0 order
19 Doppler, in units of 2.5 Hz, in the range from -5120 Hz
20 to +5117.5 Hz; otherwise the base station shall not
25 be obtained by simple truncation without round-off.
st
26 DOPPLER1 – The 1 order Doppler.
27 If ADD_DOPP_INCL is included and set to ‘1’, the base
st
29 value of the 1 order Doppler, in units of 1/64 Hz/s, in
30 the range from -1 Hz/s to +63/64 Hz/s; otherwise the
31 base station shall not include this field.
32 DOPPLER_WIN – The Doppler search window.
4-29
TIA/EIA/IS-801-1
1 If ADD_DOPP_INCL is included and ADD_DOPP_INCL

2 is set to ‘1’, the base station shall set this field to
3 represent the total size of the two sided symmetric
4 Doppler search window as specified in Table 4.2.4.2-4;
5 otherwise the base station shall not include this field.
6
7 Table 4.2.4.2-4. DOPPLER_WIN Parameter Format
DOPPLER_WIN Doppler Search Window

‘000’ 200 Hz
‘001’ 100 Hz
‘010’ 50 Hz
‘011’ 25 Hz
‘100’ 12.5 Hz
All other values of DOPPLER_WIN are reserved.
9 SV_CODE_PH – The GPS code phase.

10 If CODE_PH_PAR_ INCL is set to ‘1’, the base station
11 shall include this field and set this field to the code
12 phase, in units of 1 GPS chip, in the range from 0 to
13 1022 GPS chips, where increasing binary values of the
14 field signify increasing predicted pseudoranges;
15 otherwise, the base station shall not include this field.
19 be obtained by simple truncation without rounding-off.
20 SV_CODE_PH_INT – The integer number of code periods that have elapsed
21 since the latest GPS bit boundary.
23 shall set this field to number of the code periods that
24 have elapsed since the latest GPS bit boundary, in
25 units of C/A code period, in the range from 0 to 19;
27 GPS_BIT_NUM – The two least significant bits of the bit number (within
28 the GPS frame) being currently transmitted.
30 shall set this field to represent the two least significant
31 bits of the bit number being received at TIME_OF_APP
32 in the range from 0 to 3; otherwise the base station
4-30
TIA/EIA/IS-801-1
1 shall not include this field. The bit number within the
2 GPS frame is in the range from 0 to 1499.
3 SV_CODE_PH_WIN – The total code phase window.
5 shall set this field to represent the total size of the two
6 sided symmetric code phase search window as
7 specified in Table 4.2.4.2-5; otherwise the base station
9
4-31
TIA/EIA/IS-801-1
1 Table 4.2.4.2-5. Code Phase Search Window Parameter Format
SV_CODE_PH_WIN Code Phase Search Window

(GPS chips)
‘00000’ 1023
‘00001’ 1
00010’ 2
‘00011’ 3
‘00100’ 4
‘00101’ 5
‘00110’ 6
‘00111’ 8
‘01000’ 10
‘01001’ 12
‘01010’ 14
‘01011’ 18
‘01100’ 22
‘01101’ 26
‘01110’ 30
‘01111’ 38
‘10000’ 46
‘10001’ 54
‘10010’ 62
‘10011’ 78
‘10100’ 94
‘10101’ 110
‘10110’ 126
4-32
TIA/EIA/IS-801-1
‘10111’ 158
‘11000’ 190
‘11001’ 222
‘11010’ 254
‘11011’ 318
‘11100’ 382
‘11101’ 446
‘11110’ 512
‘11111’ 640
2 AZIMUTH – Azimuth of the GPS satellite.

3 If AZ_EL_ INCL is set to ‘1’, the base station shall set
4 this field to the azimuth, in units of 11.25 degrees, in
5 the range from 0 to 348.75 degrees; otherwise the base
11 ELEVATION – Elevation angle of the GPS satellite.
12 If AZ_EL_ INCL is set to ‘1’, the base station shall set
13 this field to the elevation angle, in units of 11.25
14 degrees, in the range from 0 to 78.75 degrees;
25
4-33
TIA/EIA/IS-801-1
1 If RESP_TYPE is equal to ‘0110’ (Provide GPS Location Assistance – Spherical Coordinates),

3
Field Length (bits)

LAT_REF 20
LONG_REF 20
HEIGHT_REF 7
NUM_DLY 3
NUM_SV 4
The base station shall include NUM_DLY occurrences of the
following fields:
PILOT_PN 9
DLY_ONEWAY 11
following fields:
DOPPLER0_LSB 4
SV_CODE_PH_FR 10
AZIMUTH_LSB 11
ELEVATION_LSB 11
5 LAT_REF – Reference latitude.

6 The base station shall set this field to the two’s
20
7 complement value of the latitude, in units of 180/2
-19
9 degrees, referenced to the WGS-84 reference ellipsoid,
10 counting positive angles north of the equator and
11 negative angles south of the equator.
12 LONG_REF – Reference longitude.
20
14 complement value of the longitude, in units of 360/2
-19
16 +180×(1-2 ) degrees, referenced to the WGS-84
17 reference ellipsoid, counting positive angles east of the
18 Greenwich meridian and negative angles west of the
19 Greenwich meridian.
4-34
TIA/EIA/IS-801-1
1 HEIGHT_REF – Reference height.

2 The base station shall set this field to the reference
3 height, in units of 40 m, in the range from -400 m to
4 +4680 m, where the binary value of the field conveys
5 the reference height plus 400 m.
6 Note that the reference height is defined as the height
7 above the WGS-84 reference ellipsoid.
8 NUM_DLY – Number of delays.
10 repeated data fields for all applicable PN offsets, in the
17 PILOT_PN – Pilot PN sequence offset index.
18 The base station shall set this field to the pilot PN
19 sequence offset for the base station, in units of 64
20 TIA/EIA-95 PN chips.
21 DLY_ONEWAY – One way delay.
22 The base station shall set this field to the one way
23 delay, in units of 1/16 TIA/EIA-95 PN chips, in the
24 range from 0 to 127.9375 chips.
th
25 DOPPLER0_LSB – The LSB’s of the 0 order term Doppler. This field is a
26 resolution extension of DOPPLER0 in a “Provide GPS
27 Acquisition Assistance” response element. When
28 appended to the bit representation DOPPLER0 in a
29 “Provide GPS Acquisition Assistance” response element
30 included in the same Position Determination Data
31 Message, it provides higher-resolution version of the
th
32 0 order term Doppler.
33 The base station shall set this field to the LSB’s of the
th 4
34 0 order Doppler, in units of 2.5/2 Hz, in the range
-4
35 from 0 to 2.5×(1-2 ) Hz.
36 SV_CODE_PH_FR – The fractional chip of code phase. This field is a
37 resolution extension of SV_CODE_PH in “Provide GPS
39 appended to the chip representation SV_CODE_PH in
40 “Provide GPS Acquisition Assistance” response
4-35
TIA/EIA/IS-801-1
1 element, it provides higher-resolution version of the

2 code phase.
3 The base station shall set this field to the fractional
-10
4 chip of code phase, in units of 2 GPS chips, in the
-10
5 range from 0 to (1- 2 ) chips.
6 AZIMUTH_LSB – The LSB’s of the azimuth. This field is a resolution
7 extension of AZIMUTH in a “Provide GPS Acquisition
8 Assistance” response element. When appended to the
9 bit representation AZIMUTH in a “Provide GPS
10 Acquisition Assistance” response element included in
11 the same Position Determination Data Message, it
12 provides higher-resolution version of the azimuth.
11
14 azimuth, in units of 11.25/2 degrees, in the range
-11
15 from 0 to 11.25×(1-2 ) degrees.
16 ELEVATION_LSB – The LSB’s of the elevation angle. This field is a
17 resolution extension of ELEVATION in a “Provide GPS
19 appended to the bit representation ELEVATION in a
20 “Provide GPS Acquisition Assistance” response element
21 included in the same Position Determination Data
22 Message, it provides higher-resolution version of the
23 elevation angle.
11
25 elevation angle, in units of 11.25/2 degrees, in the
-11
26 range from 0 to 11.25×(1-2 ) degrees.
32 If RESP_TYPE is equal to ‘0111’ (Provide GPS Location Assistance – Cartesian Coordinates),
34
Field Length (bits)

NUM_DLY 3
NUM_SV 4
The base station shall include NUM_DLY occurrences of the
following fields:
4-36
TIA/EIA/IS-801-1
PILOT_PN 9
DLY_ONEWAY 11
following fields:
DOPPLER0_LSB 4
SV_COOR_X 27
SV_COOR_Y 27
SV_COOR_Z 27
2 NUM_DLY – Number of delays.

4 repeated data fields for all applicable PN offsets, in the
13 sequence offset for the base station, in units of 64
14 TIA/EIA-95 PN chips.
15 DLY_ONEWAY – One way delay.
16 The base station shall set this field to the One way
17 delay, in units of 1/16 TIA/EIA-95 PN chips, in the
18 range from 0 to 127.9375 chips.
19 DOPPLER0_LSB – This field is a resolution extension of DOPPLER0 in a
20 “Provide GPS Acquisition Assistance” response
21 element. When appended to the bit representation
22 DOPPLER0 in a “Provide GPS Acquisition Assistance”
23 response element included in the same Position
24 Determination Data Message, it provides higher-
th
25 resolution version of the 0 order term Doppler.
th 4
27 0 order Doppler, in units of 2.5/2 Hz, in the range
-4
28 from 0 to 2.5×(1-2 ) Hz.
4-37
TIA/EIA/IS-801-1
1 SV_COOR_X – The X coordinate of the satellite in ECEF format.

3 complement of the X coordinate of the satellite, in
26
4 units of 0.4125 m, in the range from -0.4125×2 m to
26
5 0.4125×(2 - 1) m.
6 SV_COOR_Y – The Y coordinate of the satellite in ECEF format.
8 complement of the Y coordinate of the satellite, in
26
26
10 0.4125×(2 - 1) m.
11 SV_COOR_Z – The Z coordinate of the satellite in ECEF format.
13 complement of the Z coordinate of the satellite, in
26
26
15 0.4125×(2 - 1) m.
4-38
TIA/EIA/IS-801-1
1 If RESP_TYPE is equal to ‘0101’ (Provide GPS Sensitivity Assistance), RESP_PAR_RECORD

3
Field Length (bits)

REF_BIT_NUM 11
NUM_DR_P 4
DR_SIZE 8
PART_NUM 3
TOTAL_PARTS 3
The base station shall include NUM_DR_P occurrences of the
following record of (NUM_SV_DR+2) fields:
NAV_MSG_BITS 2 × DR_SIZE
NUM_SV_DR 4
The base station shall include NUM_SV_DR occurrences of
the following field:
SV_PRN_NUM 6
5 REF_BIT_NUM – The reference bit number.

6 This parameter conveys the position of a particular bit
7 in the 1500-bit GPS frame to be called the “reference
8 bit”, which is the last bit of the first half of the
9 NAV_MSG_BITS field. The base station shall set this
10 field to the position of the reference bit in the range
11 from 0 to 1499.
12 NUM_DR_P – Number of data records in this part.
13 The base station shall set this field to specify the
14 number of records (one or more) in this part of the
15 response element, in the range from 1 to 16, where the
16 binary value of the field conveys the number of data
17 records minus one.
18 DR_SIZE – Data record size.
19 The base station shall set this field to specify the data
20 record size in 2-bit units, in the range from 0 to 510
21 bits.
4-39
TIA/EIA/IS-801-1

2 The base station shall set this field to specify the part
3 number of the GPS Sensitivity Assistance data, in the
4 range from 1 to TOTAL_PARTS, where the binary value
5 of the field conveys the part number minus one.
7 The base station shall set this field to specify the total
8 number of parts that the GPS Sensitivity Assistance
9 data is divided into, in the range from 1 to 8, where
10 the binary value of the field conveys the total number
11 of parts minus one.
12 NAV_MSG_BITS – Navigation message bits.
14 Navigation message bits.
15 NUM_SV_DR – Number of GPS satellites in this data record.
17 repeated data fields for all applicable satellites in this
18 data record, in the range from 1 to 16, where the
19 binary value of the field conveys the number of
20 satellites minus one.
4-40
TIA/EIA/IS-801-1
1 If RESP_TYPE is equal to ‘0011’ (Provide Base Station Almanac), RESP_PAR_RECORD shall

3
Field Length (bits)

REF_PN 9
TIME_CRRCTION_REF 9
LAT_REF 23
LONG_REF 24
HEIGHT_REF 10
PART_NUM 3
TOTAL_PARTS 3
NUM_PILOTS_P 9
The base station shall include NUM_PILOTS_P occurrences of
the following six-field record:
PILOT_PN 9
BASE_ID 16
TIME_CORRECTION 9
LOC_SAME_AS_PREV 1
DELTA_LAT 0 or 16
DELTA_LONG 0 or 16
HEIGHT 0 or 10
5 REF_PN – Pilot PN sequence offset of the reference base station.

7 sequence offset of the pilot transmitted by the
8 reference base station with respect to which locations
9 of other base stations are reported, relative to the zero
10 offset pilot PN sequence in units of 64 PN chips.
11 TIME_CRRCTION_REF– Reference time correction.
13 complement value of the reference time correction of
14 the base station transmitting pilot REF_PN in units of
15 1/16 TIA/EIA-95 PN chips, in the range from -16 to
16 +15.9375 chips.
4-41
TIA/EIA/IS-801-1
1 LAT_REF – Reference latitude.
2 The base station shall set this field to the latitude of the
3 base station antenna transmitting pilot REF_PN,
4 referenced to the WGS-84 reference ellipsoid, in units
5 of 0.125” (arc seconds), expressed as a two’s complement
6 signed number with positive numbers signifying north
7 latitudes. The base station shall set this field to a value
8 in the range from –324000” to 324000” inclusive
9 (corresponding to the range from -90° to +90°).
10 LONG_REF – Reference longitude.
11 The base station shall set this field to the longitude of the
12 base station antenna transmitting pilot REF_PN,
13 referenced to the WGS-84 reference ellipsoid, in units
14 of 0.125” (arc seconds), expressed as a two’s complement
15 signed number with positive numbers signifying east
16 longitudes. The base station shall set this field to a value
17 in the range from –648000” to 648000” inclusive
18 (corresponding to the range from -180° to +180°).
19 HEIGHT_REF – Reference height.

20 The base station shall set this field to the height, above
21 the WGS-84 reference ellipsoid, of the base station
22 antenna transmitting pilot REF_PN, in units of 4 m, in
23 the range from 0 to 4092 m.
26 number of the Base Station Almanac data, in the
27 range from 1 to TOTAL_PARTS, where the binary value
28 of the field conveys the part number minus one.
31 number of parts that the Base Station Almanac data is
32 divided into, in the range from 1 to 8, where the binary
33 value of the field conveys the total number of parts
34 minus one.
35 NUM_PILOTS_P – Number of pilots in this part.
37 pilots to be reported in this part of the response
38 element, in the range from 0 to 511.
4-42
TIA/EIA/IS-801-1

3 sequence offset of the pilot transmitted by the base
4 station whose location is being reported, relative to the
5 zero offset pilot PN sequence in units of 64 PN chips.
6 BASE_ID – Base Station Identification.
7 The base station shall set this field to the base station
8 identification number corresponding to pilot
9 PILOT_PN.
10 TIME_ CORRECTION – The (GPS) reference time correction for Pilot PILOT_PN.
12 complement value of the reference time correction of
13 the base station antenna transmitting pilot PILOT_PN,
14 in units of 1/16 TIA/EIA-95 PN chips, expressed as a
15 two’s complement signed number in the range from
16 -16 to +15.9375 chips.
17 LOC_SAME_AS_PREV– Location same as the previous.
18 If the location of the base station antenna transmitting
19 this pilot PN is the same as the location of the previous
20 base station antenna, the base station shall set this
21 field to ‘1’; otherwise, the base station shall set this
22 field to ‘0’.
23 DELTA_LAT – The difference in the latitude of this base station
24 antenna and the latitude of the reference base station
25 antenna.
26 If LOC_SAME_AS_PREV is set to ‘0’, the base station shall

27 set this field to the difference in the latitude of the base
28 station antenna transmitting pilot PILOT_PN and the
29 latitude of the reference base station antenna (latitude
30 of base station antenna transmitting pilot PILOT_PN
31 minus latitude of reference base station antenna) with
32 both latitudes referenced to the WGS-84 reference
33 ellipsoid, in units of 0.125” (arc seconds), expressed as
34 a two’s complement signed number in the range from -
35 4096” to +4095.875”; otherwise, the base station shall
36 omit this field.
37 DELTA_LONG – The difference in the longitude of this base station

38 antenna and the longitude of the primary base station
39 antenna.
40 If LOC_SAME_AS_PREV is set to ‘0’, the base station shall
41 set this field to the difference in the longitude of the
4-43
TIA/EIA/IS-801-1
1 base station antenna transmitting PILOT_PN and the

2 longitude of the reference base station antenna
3 (longitude of base station antenna transmitting pilot
4 PILOT_PN minus longitude of reference base station
5 antenna) with both longitudes referenced to the
6 WGS-84 reference ellipsoid, in units of 0.125” (arc
7 seconds), expressed as a two’s complement signed
8 number in the range from –4096” to +4095.875”;
9 otherwise, the base station shall omit this field.
10 HEIGHT – The height of the base station antenna.

11 The base station shall set this field to the height, above
12 the WGS-84 reference ellipsoid, of the base station
13 antenna transmitting pilot PILOT_PN, in units of 4 m,
14 in the range form 0 to 4092 m.
20 If RESP_TYPE is equal to ‘1000’ (Provide GPS Almanac), RESP_PAR_RECORD shall include
21 the following record:
22
Field Length (bits)

NUM_SV_P 6
WEEK_NUM 8
TOA 8
PART_NUM 5
TOTAL_PARTS 5
4-44
TIA/EIA/IS-801-1
The base station shall include NUM_SV_P occurrences of the

following ten-field record:
SV_PRN_NUM 5
DELTA_INCLINATION 16
MO 24
ECCENTRICITY 16
A_SQRT 24
OMEGA_0 24
OMEGA 24
OMEGADOT 16
AF1 11
AF0 11
2 NUM_SV_P – Number of satellites in this part.

4 number of records (one or more) for all applicable
5 satellites in this part of the response element, in the
8 WEEK_NUM – The GPS week number of the almanac.
9 The base station shall set this field to the 8 least
22
11 almanac from which parameters in this message are
12 obtained. The range for this field is from 0 to 255.
13 TOA – The reference time of the almanac.
22
15 reference time of the almanac from which parameters
16 in this message are obtained, in units of 4096 s, in the
17 range from 0 to 602,112 s.
20 number of the Almanac data, in the range from 1 to
22
See Reference 3.
4-45
TIA/EIA/IS-801-1
1 TOTAL_PARTS, where the binary value of the field

2 conveys the part number minus one.
5 number of parts that the Almanac data is divided into,
6 in the range from 1 to 32, where the binary value of
7 the field conveys the total number of parts minus one.
14 DELTA_INCLINATION – Correction to inclination.
15 The base station shall set this field to the value
16 contained in the associated parameter of the specified
22
17 GPS almanac .
18 M0 – Mean anomaly at reference time.
22
21 GPS almanac .
22 ECCENTRICITY – Eccentricity.
22
25 GPS almanac .
26 A_SQRT – Square root of the semi-major axis.
22
29 GPS almanac .
30 OMEGA_0 – Longitude of ascending node of orbit plane at weekly
.
31 epoch
22
34 GPS almanac .
35 OMEGA – Argument of perigee.
22
38 GPS almanac .
39 OMEGADOT – Rate of right ascension.
4-46
TIA/EIA/IS-801-1

22
3 GPS almanac .
4 AF1 – Apparent satellite clock correction af1.
22
7 GPS almanac .
22
11 GPS almanac .
17 If RESP_TYPE is equal to ‘1001’ (Provide GPS Ephemeris), RESP_PAR_RECORD shall
19
Field Length (bits)

NUM_SV_P 4
PART_NUM 5
TOTAL_PARTS 5
AB_PAR_INCL 1
ALPHA_0 0 or 8
ALPHA_1 0 or 8
ALPHA_2 0 or 8
ALPHA_3 0 or 8
BETA_0 0 or 8
BETA _1 0 or 8
BETA _2 0 or 8
BETA _3 0 or 8
4-47
TIA/EIA/IS-801-1

following twenty-two-field record:
SV_PRN_NUM 5
IODE 8
C_RS 16
DELTA_N 16
M0 32
C_UC 16
ECCENTRICITY 32
C_US 16
A_SQRT 32
TOE 16
C_IC 16
OMEGA_0 32
C_IS 16
ANGLE_INCLINATION 32
C_RC 16
OMEGA 32
OMEGADOT 24
IDOT 14
TOC 16
AF2 8
AF1 16
AF0 22

4 number of records (one or more) for all applicable
10 number of the Ephemeris data, in the range from 1 to
4-48
TIA/EIA/IS-801-1
1 TOTAL_PARTS, where the binary value of the field

2 conveys the part number minus one.
5 number of parts that the Ephemeris data is divided
6 into, in the range from 1 to 32, where the binary value
7 of the field conveys the total number of parts minus
8 one.
9 AB_PAR_INCL – Inclusion of the alpha and beta parameters.
10 The base station shall set this field to ‘1’ if the alpha
11 and beta parameters are included in the response
12 element; otherwise the base station shall set this field
13 to ‘0’.
14 ALPHA_0 – Ionospheric correction parameter α0.
15 If AB_PAR_INCL is set to ‘1’, the base station shall set
16 this field to the value contained in the associated
23
17 parameter of the specified GPS ephemeris ; otherwise
18 the base station shall not include this field.
Ionospheric correction parameter α1
.
19 ALPHA_1 –
23
23
23
34 BETA_0 – Ionospheric correction parameter β0.
23
See Reference 3.
4-49
TIA/EIA/IS-801-1
23
23
23
23
24 IODE – Issue of data.
23
27 GPS ephemeris .
28 C_RS – Amplitude of the sine harmonic correction term to the
29 orbit radius.
23
32 GPS ephemeris .
33 DELTA_N – Mean motion difference from the computed value.
23
36 GPS ephemeris .
4-50
TIA/EIA/IS-801-1
1 M0 – Mean anomaly at the reference time.

23
4 GPS ephemeris .
5 C_UC – Amplitude of the cosine harmonic correction term to
6 the argument of latitude.
23
9 GPS ephemeris .
10 ECCENTRICITY – Eccentricity.
23
13 GPS ephemeris .
14 C_US – Amplitude of the sine harmonic correction term to the
15 argument of latitude.
23
18 GPS ephemeris .
19 A_SQRT – Square root of the semi-major axis.
23
22 GPS ephemeris .
23 TOE – ephemeris reference time.
23
26 GPS ephemeris .
27 C_IC – Amplitude of the cosine harmonic correction term to
28 the angle of inclination.
23
31 GPS ephemeris .
32 OMEGA_0 – Longitude of ascending node of orbit plane at weekly
33 epoch.
23
36 GPS ephemeris .
37 C_IS – Amplitude of the sine harmonic correction term to the
38 angle of inclination.
4-51
TIA/EIA/IS-801-1

23
3 GPS ephemeris .
4 ANGLE_INCLINATION– Inclination angle at the reference time.
23
7 GPS ephemeris .
8 C_RC – Amplitude of the cosine harmonic correction term to
9 the orbit radius.
23
12 GPS ephemeris .
13 OMEGA – Argument of perigee.
23
16 GPS ephemeris .
17 OMEGADOT – Rate of right ascension.
23
20 GPS ephemeris .
21 IDOT – Rate of inclination angle.
23
24 GPS ephemeris .
25 TOC – Clock data reference time.
23
28 GPS ephemeris .
23
32 GPS ephemeris .
23
36 GPS ephemeris .
4-52
TIA/EIA/IS-801-1

23
3 GPS ephemeris .
9 If RESP_TYPE is equal to ‘1010’ (Provide GPS Navigation Message Bits),
11
Field Length (bits)

NUM_SV_P 6
PART_NUM 5
TOTAL_PARTS 5
SUBF_4_5_INCL 1
SUBF_4_5 0 or 15000
following two-field record:
SV_PRN_NUM 6
SUB_1_2_3 900
12

15 records (one or more) for all applicable satellites in this
16 part of the response element, in the range from 1 to
17 64, where the binary value of the field conveys the
18 number of satellites minus one.
21 number of the GPS Navigation Message Bits data, in
4-53
TIA/EIA/IS-801-1
2 number of parts that the GPS Navigation Message Bits
3 data is divided into, in the range from 1 to 32, where
4 the binary value of the field conveys the total number
5 of parts minus one.
6 SUBF_4_5_INCL – Inclusion of the additional parameters indicator.
7 The base station shall set this field to ‘1’ if the
8 subframes 4 and 5 are included in the response
9 element; otherwise the base station shall set this field
10 to ‘0’.
11 SUBF_4_5 – GPS subframes 4 and 5.
12 If SUBF_4_5_INCL is set to ‘1’, the base station shall
13 set this field to the contents of GPS navigation
14 message subframes 4 and 5; otherwise the base
16 Note that the data shall be current as of the time of
17 transmission; time-dependent fields shall be
18 represented as they will occur in the next whole frame
19 (for subframes 1, 2 and 3) or in the next whole
20 superframe (for subframes 4 and 5) from the time the
21 request is received by the base station.
28 SUBF_1_2_3 – The subframes 1, 2 and 3.
29 The base station shall set this field to the contents of
30 GPS navigation message subframes 1, 2 and 3
31 transmitted by the satellite specified in the previous
32 field.
33 Note that the data shall be current as of the time of
34 transmission; time-dependent fields shall be
35 represented as they will occur in the next whole frame
36 (for subframes 1, 2 and 3) or in the next whole
37 superframe (for subframes 4 and 5) from the time the
38 request is received by the base station.
4-54
TIA/EIA/IS-801-1

3 If RESP_TYPE is equal to ‘0001’ (Provide Location Response), RESP_PAR_RECORD shall
5
Field Length (bits)

TIME_REF_CDMA 14
LAT 25
LONG 26
LOC_UNCRTNTY_ANG 4
LOC_UNCRTNTY_A 5
LOC_UNCRTNTY_P 5
FIX_TYPE 1
VELOCITY_INCL 1
VELOCITY_HOR 0 or 9
HEADING 0 or 10
VELOCITY_VER 0 or 8
CLOCK_INCL 1
CLOCK_BIAS 0 or 18
CLOCK_DRIFT 0 or 16
HEIGHT_INCL 1
HEIGHT 0 or 14
LOC_UNCRTNTY_V 0 or 5

14 LAT – Latitude.
4-55
TIA/EIA/IS-801-1

2 complement value of the latitude, referenced to the
25
3 WGS-84 reference ellipsoid, in units of 180/2
-24
5 degrees, counting positive angles north of the equator
6 and negative angles south of the equator.
7 LONG – Longitude.
9 complement value of the longitude, referenced to the
26
10 WGS-84 reference ellipsoid, in units of 360/2
-25
12 +180×(1-2 ) degrees, counting positive angles east of
13 the Greenwich meridian and negative angles west of
14 the Greenwich meridian.
15 LOC_UNCRTNTY_ANG – Angle of axis with respect to True North for position
16 uncertainty.
17 The base station shall set this field to the angle of axis
18 for position uncertainty, in units of 5.625 degrees, in
19 the range from 0 to 84.375 degrees, where 0 degrees is
20 True North and the angle increases toward the East.
21 LOC_UNCRTNTY_A – Standard deviation of axis along angle specified for
22 position uncertainty.
23 The base station shall set this field to represent the
24 standard deviation of axis along angle specified for
25 position uncertainty as specified in Table 4.2.4.2-6.
26
4-56
TIA/EIA/IS-801-1
1 Table 4.2.4.2-6. Position Uncertainty
LOC_UNCRTNTY Standard Deviation for

Position Uncertainty
(meters)
‘00000’ 0.5
‘00001’ 0.75
‘00010’ 1
‘00011’ 1.5
‘00100’ 2
‘00101’ 3
‘00110’ 4
‘00111’ 6
‘01000’ 8
‘01001’ 12
‘01010’ 16
‘01011’ 24
‘01100’ 32
‘01101’ 48
‘01110’ 64
‘01111’ 96
‘10000’ 128
‘10001’ 192
‘10010’ 256
‘10011’ 384
‘10100’ 512
‘10101’ 768
‘10110’ 1,024
‘10111’ 1,536
‘11000’ 2,048
‘11001’ 3,072
‘11010’ 4,096
‘11011’ 6,144
4-57
TIA/EIA/IS-801-1
‘11100’ 8,192
‘11101’ 12,288
‘11110’ >12,288
‘11111’ Not computable
1 LOC_UNCRTNTY_P – Standard deviation of axis perpendicular to angle

2 specified for position uncertainty.
3 The base station shall set this field to represent the
4 Standard Deviation of Axis Perpendicular to Angle
5 Specified for Position Uncertainty as specified in Table
6 4.2.4.2-6.
7 FIX_TYPE – Fix type.
8 The base station shall set this field to ‘0’ for 2D fix and
9 to ‘1’ for 3D fix.
10 VELOCITY_INCL – Velocity information included.
11 If velocity information is included in this response
13 velocity information is not included in this response
14 element, the base station shall set this field to ‘0’.
15 VELOCITY_HOR – Horizontal velocity magnitude.
16 If VELOCITY_INCL is set to ‘1’, the base station shall
17 set this field to the horizontal velocity, in units of 0.25
18 m/s, in the range from 0 to 127.75 m/s; otherwise the
19 base station shall not include this field.
23 HEADING – Heading.
24 If VELOCITY_INCL is set to ‘1’, the base station shall
10
25 set this field to Heading, in units of 360/2 degrees, in
-10
26 the range from 0 to 360×(1-2 ) degrees; otherwise the
27 base station shall not include this field, where 0
28 degrees is True North and the angle increases toward
29 the East.
4-58
TIA/EIA/IS-801-1
1 VELOCITY_VER – Vertical velocity.

2 If VELOCITY_INCL and FIX_TYPE are set to ‘1’, the
3 base station shall set this field to the two’s
4 complement value of Vertical Velocity, in units of 0.5
5 m/s, in the range from -64 m/s to +63.5 m/s;
10 CLOCK_INCL – Clock information included.
11 If clock information is included in this response
13 clock information is not included in this response
14 element, the base station shall set this field to ‘0’.
15 CLOCK_BIAS – Clock bias.
16 If CLOCK_INCL is set to ‘1’, the base station shall set
17 this field to the clock bias in ns, in the range from
18 -13,000 ns to +249,143 ns, where the binary value of
19 the field conveys the clock bias plus 13,000 ns;
20 otherwise, the base station shall not include this field.
21 This parameter is computed as true GPS time minus
22 mobile station time reference as defined in
23 TIA/EIA-95.
24 Note that as part of a GPS fix, the computation yields
25 an estimate of the discrepancy between the time
26 specified by the local clock and true GPS time. This
27 parameter reports the discrepancy. The main cause of
28 this discrepancy is going to be the propagation delay
29 from the base station to the MS, which is always
30 positive. Accordingly, the range allowed for this
31 parameter is not symmetric.
32 CLOCK_DRIFT – Clock drift.
33 If CLOCK_INCL is set to ‘1’, the base station shall set
34 this field to the two’s complement value of the rate of
35 change of clock bias in units of ppb (ns/s), in the
36 range from -32768 ppb (ns/s) to +32767 ppb (ns/s);
38 HEIGHT_INCL – Height information included.
4-59
TIA/EIA/IS-801-1
1 If height information is included in this response

3 HEIGHT is not included in this response element, the
5 HEIGHT – Height.
6 If HEIGHT_INCL is set to ‘1’, the base station shall set
7 this field to the height, above WGS-84 reference
8 ellipsoid, in units of 1 meter, in the range from -500 m
9 to 15883 m, where the binary value of the field
10 conveys the height plus 500 m; otherwise, it shall not
15 LOC_UNCRTNTY_V – Standard deviation of vertical error for position
16 uncertainty.
17 If HEIGHT_INCL is set to ‘1’, the base station shall
18 include this field and set this field to represent the
19 Standard Deviation Vertical Error for Position
20 Uncertainty as specified in Table 4.2.4.2-6; otherwise
30 If RESP_TYPE is equal to ‘1011’ (Provide GPS Almanac Correction), RESP_PAR_RECORD
32
Field Length (bits)

NUM_SV_P 4
REF_TIME 8
TOA 8
WEEK_NUM 8
PART_NUM 5
TOTAL_PARTS 5
4-60
TIA/EIA/IS-801-1

following fields:
SV_PRN_NUM 5
DELTA_XYZ_INCL 1
DELTA_X 0 or 15
DELTA_Y 0 or 15
DELTA_Z 0 or 15
ST
DELTA_X_1 0 or 7
ST
DELTA_Y_1 0 or 7
ST
DELTA_Z_1 0 or 7
DELTA_CLOCK_INCL 1
DELTA_CLOCK 0 or 17
ST
DELTA_CLOCK_1 0 or 8
2 NUM_SV_P – Number of satellites in the part.

7 REF_TIME – The time of validity of the parameters reported in this
8 response element.
9 The base station shall set this field to the time of
10 validity of these almanac corrections.
12 250), where t is the GPS time of validity of the
13 corrections in units of 1 ms.
14 TOA – Time of almanac.
16 reference time of the almanac from which parameters
17 in this message are obtained, in units of 4096 s, in the
18 range from 0 to 602,112 s.
19 WEEK_NUM – GPS week number.
20 The base station shall set this field to the 8 least
4-61
TIA/EIA/IS-801-1
1 almanac for which the almanac corrections are

2 provided. The range for this field is from 0 to 255.
3 PART_NUM – Part number.
5 the current part in the response element, in the range
6 from 1 to TOTAL_PARTS, where the binary value of the
7 field conveys the part number minus one.
8 TOTAL_PARTS – Total parts.
9 The base station shall set this field to the total number
10 of parts that constitute the response element, in the
12 conveys the total number of parts minus one.
19 DELTA_XYZ_INCL – Correction for XYZ included.
20 The base station shall set this field to ‘1’ if delta XYZ
21 information is included in the message; otherwise it
24
23 DELTA_X – Correction for X coordinate.
24 If DELTA_XYZ_INCL is set to ‘1’ the base station shall
25 include DELTA_X and set this field to the two’s
th
26 complement value of the 0 order position correction X
27 term, in units of 0.5 m, in the range from -8192 m to
28 +8191.5 m; otherwise the base station shall not
24
29 include this field .
30 DELTA_Y – Correction for Y coordinate.
32 include DELTA_Y and set this field to the two’s
th
33 complement value of the 0 order position correction Y
24
37 DELTA_Z – Correction for Z coordinate.
24
See 3.2.2.1.1.2 and 3.2.2.3.3.2
4-62
TIA/EIA/IS-801-1

2 include DELTA_Z and set this field to the two’s
th
3 complement value of the 0 order position correction Z
24
st
7 DELTA_X_1ST – 1 order correction for X coordinate.
9 include DELTA_X_1ST and set this field to the two’s
st
10 complement value of the 1 order position correction X
11 term, in units of 2.5 cm/s, in the range from -160
12 cm/s to +157.5 cm/s; otherwise the base station shall
13 not include this field.
st
14 DELTA_Y_1ST – 1 order correction for Y coordinate.
16 include DELTA_Y_1ST and set this field to the two’s
st
17 complement value of the 1 order position correction Y
st
21 DELTA_Z_1ST – 1 order correction for Z coordinate.
23 include DELTA_Z_1ST and set this field to the two’s
st
24 complement value of the 1 order position correction Z
28 DELTA_CLOCK_INCL – Correction for clock included.
29 The base station shall set this field to ‘1’ if delta clock
30 information is included in the message; otherwise it
32 DELTA_CLOCK – Correction for clock.
33 If DELTA_CLOCK_INCL is set to ‘1’ the base station
34 shall include DELTA_CLOCK and set this field to the
th
35 two’s complement value of the delta clock 0 order, in
36 units of 1 ns, in the range from -65536 ns to
37 65535 ns; otherwise the base station shall not include
38 this field.
st
39 DELTA_CLOCK_1ST – 1 order correction for clock.
40 If DELTA_CLOCK_INCL is set to ‘1’ the base station
41 shall include DELTA_CLOCK_1ST and set this field to
4-63
TIA/EIA/IS-801-1
st
1 the two’s complement value of the delta clock 1 order,
2 in units of 0.1 ppb, in the range from -12.8 ppb to
3 +12.7 ppb; otherwise the base station shall not include
4 this field.
10 If RESP_TYPE is equal to ‘1100’ (Provide GPS Satellite Health Information),
12
Field Length (bits)

BAD_SV_PRESENT 1
NUM_BAD_SV 0 or 4
If BAD_SV_PRESENT is set to ‘1’, the base station shall
include NUM_BAD_SV occurrences of the following one-field
record:
BAD_SV_PRN_NUM 5
13
14 BAD_SV_PRESENT – Bad GPS satellites present.

15 If the response element includes information about
16 bad GPS satellites, the base station shall set this field
17 to ‘1’; otherwise, the base station shall set this field to
18 ‘0’.
19 NUM_BAD_SV – The number of bad GPS satellites.
20 If BAD_SV_PRESENT is set to ‘1’, the base station
21 shall set this field to the number of bad satellites (one
22 or more) included, in the range from 1 to 16, where the
23 binary value of the field conveys the number of bad
24 satellites minus one; otherwise, the base station shall
26 BAD_SV_PRN_NUM – The satellite PRN number.
28 PRN signal number of the bad satellite. It is
4-64
TIA/EIA/IS-801-1

4-65
TIA/EIA/IS-801-1
1 No text.
4-66
TIA/EIA/IS-801-1
1 Annex A – TIMERS
2 The following table provides values for time limits given in the text.
3 Table A-1. Time Limits
Time
Description Value References
Limit
T1 Time limit for preferred quality of “Provide Pseudorange 2s 3.2.2.1.1.1
Measurement”, “Provide Pilot Phase Measurement” and 3.2.2.3.3.1
“Provide Location Response” response elements when
PREF_RESP_QUAL = ‘000’
T4 Time limit for preferred quality of “Provide Pseudorange 16 s 3.2.2.1.1.1
T9 The time limit for the mobile station to wait for a response 35 s 3.2.1.2
or a “Reject” to a sent request element
A-1
TIA/EIA/IS-801-1
1 No text.
A-2
TIA/EIA/IS-801-1
1 Annex B – REQUEST/RESPONSE ELEMENT TYPES

2 Table B-1. MS Requests and BS Responses
Code REQUEST Elements sent by MS Code RESPONSE Elements sent by BS
0000 Reserved 0000 Reject
0001 Request Location Response 0001 Provide Location Response
0010 Request BS Capabilities 0010 Provide BS Capabilities
0011 Request Base Station Almanac 0011 Provide Base Station Almanac
0100 Request GPS Acquisition Assistance 0100 Provide GPS Acquisition Assistance
0101 Request GPS Sensitivity Assistance 0101 Provide GPS Sensitivity Assistance
0110 Request GPS Location Assistance 0110 Provide GPS Location Assistance –
Spherical Coordinate
0111 Reserved 0111 Provide GPS Location Assistance –

Cartesian Coordinate
1000 Request GPS Almanac 1000 Provide GPS Almanac
1001 Request GPS Ephemeris 1001 Provide GPS Ephemeris
1010 Request GPS Navigation Message Bits 1010 Provide GPS Navigation Message Bits
1011 Request GPS Almanac Correction 1011 Provide GPS Almanac Correction
1100 Request GPS Satellite Health 1100 Provide GPS Satellite Health
Information Information
3 See Table 3.2.4-2. Request Element Type and Table 4.2.4-3. Response Element Type.
4
5 Table B-2. MS Responses and BS Requests
Code RESPONSE Elements sent by MS Code REQUEST Elements sent by BS
0000 Reject 0000 Reserved
0001 Provide Location Response 0001 Request Location Response
0010 Provide MS Information 0010 Request MS Information
0011 Provide Autonomous Measurement 0011 Request Autonomous Measurement

Weighting Factor Weighting Factor
0100 Provide Pseudorange Measurement 0100 Request Pseudorange Measurement
0101 Provide Pilot Phase Measurement 0101 Request Pilot Phase Measurement
0110 Provide Time Offset Measurement 0110 Request Time Offset Measurement
B-1
TIA/EIA/IS-801-1
0111 Provide Cancellation Acknowledgement 0111 Request Cancellation
1 See Table 3.2.4-3. Response Element Type and Table 4.2.4-2. Request Element Type.
B-2
TIA/EIA/IS-801-1
1 Annex C – EXAMPLE POSITION DETERMINATION DATA MESSAGE

2 The following is an example of a mobile station originated Position Determination Data
3 Message. The example merely serves as an aid in understanding the format specified in the
4 body of the document. The example accommodates two mobile station requests, along with
5 a mobile station response (to a previous base station request to the mobile). The example
6 shows how the individual records (and fields) (i.e. REQ_TYPEs, REQ_PAR_RECORDs, etc.)
7 are built from the most significant bit (MSB) to the least significant bit (LSB), the length of
8 the individual records, and the ordering of the individual records within the final Position
9 Determination Data Message. Finally, the entire bit string for the Position Determination
10 Data Message is constructed.
11 The Mobile requests the following information from the base station:
12 • GPS Acquisition Assistance
13 • GPS Almanac Correction
14 The mobile is also responding to a base station request for “Provide MS Information”
16 Individual fields of the Position Determination Data Message are listed in Table C-1.
17
18 Table C-1. Bit Field of the Position Determination Data Message
FIELD TYPE MSB → LSB COMMENTS
SESS_START 0 Not the first message of a session
SESS_END 1 The last message of a session
SESS_SOURCE 0 Base station originated the session
SESS_TAG 01100 Tag of the session
PD_MSG_TYPE 00000000 From Table 3.2.4-1
NUM_REQUESTS 0010 Making 2 requests
NUM_RESPONSES 0001 Making 1 response
REQ_TYPE 00000100 4 RESERVED bits + Request GPS

Acquisition Assistance
REQ_PAR_LEN 00000001 Indicates one octet in following

REQ_PAR_RECORD
REQ_PAR_RECORD 11110000 Requests DOPP_REQ, ADD_DOPP_REQ,

CODE_PH_PAR_REQ, AZ_EL_REQ + 4
RESERVED bits
REQ_TYPE 00001011 4 RESERVED bits + Request GPS Almanac

Correction
C-1
TIA/EIA/IS-801-1
REQ_PAR_LEN 00000010 Two octets in following REQ_PAR_RECORD
REQ_PAR_RECORD
TOA 10010011 Requested reference Time Of Almanac =

602112 s
WEEK_NUM 10101010 Requested WEEK_NUM = 170
UNSOL_RESP 0000 3 RESERVED bits + Indication that the

response is not unsolicited
RESP_TYPE 0010 Provide MS Information
RESP_PAR_LEN 00000101 Five octets in following REQ_PAR_RECORD
RESP_PAR_RECORD
MS_LS_LEV 000000 by definition
MS_MODE 0000 by definition
PILOT_PH_CAP 000000 Set to indicate Full Chip Measurement

Capability (Table 3.2.4.2-2)
GPS_ACQ_CAP 000000100001 Set to indicate GPS Acquisition Assistance

and GPS Almanac Correction Capability
(Table 3.2.4.2-3)
LOC_CALC_CAP 000010100101 Set to indicate Location Assistance-

Spherical, AFLT, GPS Almanac Correction,
Hybrid Position Calculation Capability
(Table 3.2.4.2-4)
2 Therefore the entire Position Determination Data Message consists of 16 octets or 128 bits
3 as follows:
4 MSB and beginning of message
5 ↓
6 00000000001000010000010000000001111100000000
7 10110000001010010011101010100000001000000101
8 0000000000000000000000100001000010100101
9 ↑
10 LSB end of message
C-2
TIA/EIA/IS-801-1
1 Annex D – INFORMATIVE ANNEX ON SESSION TAGS

2 This Annex considers two distinct uses of session tags:
3 1. As a mechanism that may help determine routing of IS801 messages within the network
4 2. To help IS-801-1-compliant entities to handle multiple, simultaneous sessions
5 Session Tag Use for Routing in the Network

6 In a network that employs multiple PDEs, a mechanism must be implemented to route
7 messages to specific PDEs. Because a mobile station does not have enough information to
8 address a PDE, a function within the network must perform this task; otherwise, mobile-
9 initiated (also called mobile originated) sessions will not succeed. The scope of this
10 standard is limited to defining an air interface; and, therefore, explaining any network
11 functionality for routing based on session tags is only included in this Informative Annex.
12 The actual entity/entities carrying out the addressing and routing depend upon details of
13 the network and implementation. Further details of the network may be covered in J-STD-
14 036, Enhanced Wireless 9-1-1 Phase 2 from TR45.2 AHES, which is the same as Reference
15 5 of this document.
16 The following is an example of how session tags could be used to route PDDMs:
17 Upon receiving a Position Determination Data Message, the network checks the value of the
18 SESS_START field. If the SESS_START field is set to ‘1’, the network entity checks the
19 SESS_SOURCE field. If SESS_SOURCE = ‘0’, the routing network entity (for example, an
20 MSC) stores the SESS_TAG along with the addresses of the originating PDE and the target
21 mobile station. If SESS_SOURCE = ‘1’, the network entity selects a PDE, and stores the
22 SESS_TAG along with the addresses of the selected PDE and the originating mobile station.
23 Otherwise, if SESS_START is set to ‘0’, the network would not change the SESS_TAG
24 related information in its memory.
25 When routing Position Determination Data Messages that originated in a mobile station,
26 the serving network entity looks up the PDE address stored in its memory indexed by the
27 mobile station address and the value of the SESS_TAG field.
28 Further Information Concerning Session Tags
29 Session tags can also serve an important purpose in enabling the network and the MS to
30 handle multiple sessions simultaneously; that is, session tags may help IS801-compliant
31 entities to keep track of simultaneous sessions that proceed at the same time.
32 Session tags may enable:
33 • An alert to the serving network entity when MS-initiated requests occur and no PDE is
34 assigned yet.
35 • An alert to the serving network entity when a TCAP session is to begin and to end.
36 These points concerning Session Tags should be noted:
37 • The Session Tag value, SESS_TAG, is assigned by the initiator. It should be set to one
38 more than the previous SESS_TAG value. The session tag value never changes
39 throughout the life of a session.
D-1
TIA/EIA/IS-801-1
1 • The MS may be able to handle multiple sessions through the use of session tags;
2 however, having multiple session tags active towards a mobile is allowed only under the
3 restriction that there is only one outstanding request of a given REQ_TYPE active at any
4 time for each session. Any new request with the same REQ_TYPE as the outstanding
5 request type will be discarded if it is done within a single session.
6 • The SESS_START tag is set on the initial message only.
7 • SESS_END tag indicates that the sender considers the session to be finished. Setting of
8 the SESS_END tag, however, may not end the session. The session ends when both
9 sender and receiver mutually agree, and all in-transit messages have been handled.
10 The value of SESS_SOURCE indicates who set the SESS_START tag, with 0, meaning
11 the source was a BS, and 1, meaning the source was an MS. This value never changes
12 throughout the life of a session.
13
D-2

Tia Eia Is 801 1

Încărcat de

Informații document

Descriere originală:

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Tia Eia Is 801 1

Încărcat de

Drepturi de autor:

Formate disponibile

TIA/EIA

Position Determination Service

TELECOMMUNICATIONS INDUSTRY ASSOCIATION

The Telecommunications Industry Association

TIA/EIA INTERIM STANDARDS

TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2001

PRICE: Please refer to current Catalog of

All rights reserved

Organizations may obtain permission to reproduce a limited number of copies

Global Engineering Documents

1 (This foreword is not part of this standard)

2 12/04/2000 Addendum 1 Incorporated

8 1. TIA/EIA-95-B, Mobile Station-Base Station Compatibility Standard for Dual-Mode

1 MS. See Mobile Station.

1 Unsolicited Response. A response element that is issued in the absence of the

1 2 MESSAGE TRANSPORT PROTOCOL

5 2.1 Analog Transport Protocol

7 2.2 CDMA Transport Protocol

16 2.2.1 Session Tags

1 3 MOBILE STATION PROCEDURES

2 3.1 Analog Mobile Station Procedures

4 3.2 CDMA Mobile Station Procedures

5 3.2.1 Position Determination Data Message Processing

1 Request elements received by mobile station:

1 Table 3.2.1.2-1. Response Elements Sent in Response to Received Request Elements

Request element received Possible response elements

1 3.2.2 Point-to-point Procedures

5 3.2.2.1 Control Channel Procedure

6 3.2.2.1.1 Mobile Station Position Determination Data Messa ge Termination

24 3.2.2.1.1.1 Base Station Request Elements Received

1 • Request Autonomous Measurement Weighting Factors: The mobile station shall

1 seconds of the time corresponding to the beginning of the measurement

1 collection period; if PREF_RESP_QUAL is set to ‘111’, the “Provide Pilot

1 Response” response element shall be sent within T8 seconds of the time

33 3.2.2.1.1.2 Base Station Response Elements Received

1 • If DELTA_CLOCK_INCL is ‘0’, the mobile station shall set the values of

3 3.2.2.1.2 Mobile Station Position Determination Data Messa ge Origination

4 3.2.2.1.2.1 Position Determination Data Message Transmissio n Requirements

36 3.2.2.1.2.2 Unsolicited Response Elements

1 3.2.2.1.2.3 Request Elements

3 3.2.2.2 Authentication Procedures

11 3.2.2.3 Traffic Channel Procedure

12 3.2.2.3.1 Message Encryption

18 3.2.2.3.2 Negotiation for the Position Determination Service Option

29 3.2.2.3.2.1 Procedures Using Service Negotiation

1 Table 3.2.2.3.2.1-1. Valid Service Configuration Attributes for Service Option 35

Service Configuration Attribute Valid Selections

3 Table 3.2.2.3.2.1-2. Valid Service Configuration Attributes for Service Option 36

Service Configuration Attribute Valid Selections

5 If the mobile station accepts a service configuration, as specified in a Service Connect

3 3.2.2.3.3 Mobile Station Position Determination Data Messa ge Termination

21 3.2.2.3.3.1 Base Station Request Elements Received

1 collection period; if PREF_RESP_QUAL is set to ‘111’, the “Provide

1 – If DESI_PIL_PH_RES is set to ‘1’, the “Provide Pilot Phase Measurement”

1 – If HEIGHT_REQ is set to ‘1’, the “Provide Location Response” response

31 3.2.2.3.3.2 Base Station Response Elements Received

41 3.2.2.3.4 Traffic Channel Setup

15 3.2.2.3.5 Mobile Station Position Determination Data Messa ge Origination in the

17 3.2.2.3.5.1 Position Determination Data Message Transmissio n Requirements

38 3.2.2.3.5.2 Unsolicited Response Elements

40 3.2.2.3.5.3 Request Elements

2 3.2.3 Broadcast Procedures