toby
/
zotero-db
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
zotero-db/storage/IKXJVFCL/.zotero-ft-cache

5466 lines
132 KiB
Plaintext
Raw Normal View History

First ZDB push. Testing repo functionality.
2024-08-12 13:51:37 -05:00
NAVSTAR GLOBAL POSITIONING SYSTEM
INTERFACE SPECIFICATION IS-GPS-200 Revision D
IRN-200D-001
7 March 2006
Navstar GPS Space Segment/Navigation User Interfaces
Deputy System Program Director GPS JOINT PROGRAM OFFICE
Headquarters Space and Missile Systems Center (SMC) Navstar GPS Joint Program Office (SMC/GP)
2420 Vela Way, Suite 1866 El Segundo, CA 90245-4659
U.S.A.
By ARINC Engineering Services, LLC 2250 E. Imperial Highway, Suite 450
El Segundo, CA 90245 U.S.A.
Cage Code: 0VYX1 DISTRIBUTION STATEMENT A. APPROVED FOR PUBLIC RELEASE; DISTRIBUTION IS UNLIMITED
(This page intentionally left blank.)
IS-GPS-200D 7 Dec 2004
ii
REVISION RECORD
REV
DESCRIPTION
DOCUMENT APPROVED DATE
NC
Initial Release
25 Jan 1983
A
Incorporates IRN-200NC-001, IRN-200NC-002, and IRN-
200NC-003
25 Sep 1984
B
Incorporates IRN-200A-001A
30 Nov 1987
C
Incorporates IRN-200B-001 thru IRN-200B-007
10 Oct 1993
C
Re-formatted in Microsoft Word 6.0 in GEMS compatible format 10 Oct 1993 12 Jan 1996
C
Changed distribution status to Public Release
25 Sep 1997 20 Oct 1997
D
Incorporates IRN-200C-001 thru IRN-200C-005R1, change ICD-
7 Dec 2004 23 Nov 2004
GPS-200 to IS-GPS-200, introduce and specify the requirements of
Improved Clock and Ephemeris (ICE) message for L2 C signal, and
other additional updates
IRN-200D-001 Adds additional PRN sequences to Section 6
7 Mar 2006 9 Mar 2006
IRN-200D-001 IS-GPS-200D
7 Mar 2006 iii
(This page intentionally left blank.)
IS-GPS-200D 7 Dec 2004
iv
Pages
i ii iii iv v vi vii - xi xii - xiii xiv - xvi 1 – 5 6 7 – 17 18 19 – 56 56a – 56l 57 – 193
Revision
IRN-200D-001 D IRN-200D-001 D IRN-200D-001 D IRN-200D-001 D IRN-200D-001 D IRN-200D-001 D IRN-200D-001 D IRN-200D-001 D
Page Revision Record Pages
Revision
IRN-200D-001 IS-GPS-200D
7 Mar 2006 v
(This page intentionally left blank.)
IS-GPS-200D 7 Dec 2004
vi
TABLE OF CONTENTS
1. SCOPE.....................................................................................................................................................................1 1.1 Scope ...............................................................................................................................................................1 1.2 IS Approval and Changes ................................................................................................................................1
2. APPLICABLE DOCUMENTS..............................................................................................................................3 2.1 Government Documents ..................................................................................................................................3 2.2 Non-Government Documents..........................................................................................................................3
3. REQUIREMENTS .................................................................................................................................................5 3.1 Interface Definition .........................................................................................................................................5 3.2 Interface Identification ....................................................................................................................................5 3.2.1 Ranging Codes ......................................................................................................................................5 3.2.1.1 P-Code.........................................................................................................................................6 3.2.1.2 Y-Code ........................................................................................................................................6 3.2.1.3 C/A-Code ....................................................................................................................................6 3.2.1.4 L2 CM-Code (IIR-M, IIF, and subsequent blocks) .....................................................................6 3.2.1.5 L2 CL-Code (IIR-M, IIF, and subsequent blocks) ......................................................................6 3.2.1.6 Non-Standard Codes .................................................................................................................11 3.2.2 NAV Data............................................................................................................................................11 3.2.3 L1/L2 Signal Structure ........................................................................................................................12 3.3 Interface Criteria............................................................................................................................................14 3.3.1 Composite Signal ................................................................................................................................14 3.3.1.1 Frequency Plan..........................................................................................................................14 3.3.1.2 Correlation Loss ........................................................................................................................14 3.3.1.3 Carrier Phase Noise...................................................................................................................14 3.3.1.4 Spurious Transmissions.............................................................................................................14 3.3.1.5 Phase Quadrature.......................................................................................................................15 3.3.1.6 User-Received Signal Levels ....................................................................................................15 3.3.1.7 Equipment Group Delay............................................................................................................17 3.3.1.7.1 Group Delay Uncertainty ................................................................................................17 3.3.1.7.2 Group Delay Differential ................................................................................................17 3.3.1.8 Signal Coherence.......................................................................................................................17 3.3.1.9 Signal Polarization ....................................................................................................................17 3.3.2 PRN Code Characteristics ...................................................................................................................18 3.3.2.1 Code Structure...........................................................................................................................18
IRN-200D-001 IS-GPS-200D
7 Mar 2006 vii
3.3.2.2 P-Code Generation ....................................................................................................................20 3.3.2.3 C/A-Code Generation................................................................................................................30 3.3.2.4 L2 CM-/L2 CL-Code Generation..............................................................................................35 3.3.3 Navigation Data...................................................................................................................................38 3.3.3.1 Navigation Data Modulation (L2 CM)......................................................................................38
3.3.3.1.1 Forward Error Correction................................................................................................38 3.3.4 GPS Time and SV Z-Count.................................................................................................................40 4. NOT APPLICABLE.............................................................................................................................................43 5. NOT APPLICABLE.............................................................................................................................................45 6. NOTES...................................................................................................................................................................47 6.1 Acronyms ......................................................................................................................................................47 6.2 Definitions .....................................................................................................................................................51 6.2.1 User Range Accuracy..........................................................................................................................51 6.2.2 SV Block Definitions ..........................................................................................................................51
6.2.2.1 Developmental SVs...................................................................................................................51 6.2.2.2 Operational SVs ........................................................................................................................51
6.2.2.2.1 Block II SVs....................................................................................................................51 6.2.2.2.2 Block IIA SVs.................................................................................................................51 6.2.2.2.3 Block IIR SVs .................................................................................................................52 6.2.2.2.4 Block IIR-M SVs ............................................................................................................52 6.2.2.2.5 Block IIF SVs..................................................................................................................52 6.2.3 Operational Interval Definitions..........................................................................................................52 6.2.3.1 Normal Operations ....................................................................................................................52 6.2.3.2 Short-term Extended Operations ...............................................................................................52 6.2.3.3 Long-term Extended Operations ...............................................................................................52 6.2.4 GPS Week Number .............................................................................................................................53 6.2.5 L5 Civil Signal ....................................................................................................................................53 6.3 Supporting Material.......................................................................................................................................53 6.3.1 Received Signals .................................................................................................................................53 6.3.2 Extended Navigation Mode (Block II/IIA)..........................................................................................55 6.3.3 Block IIA Mode (Block IIR/IIR-M)....................................................................................................56 6.3.4 Autonomous Navigation Mode ...........................................................................................................56 6.3.5 PRN Code sequences expansion ....................................................................................................... 56a 6.3.5.1 Additional C/A-code PRN sequences ..................................................................................... 56a 6.3.5.2 Additional P-Code PRN sequences .........................................................................................56b
IRN-200D-001 IS-GPS-200D
7 Mar 2006 viii
6.3.5.2.1 Additional P-code Generation.......................................................................................56b 6.3.5.3 Additional L2 CM-/L2 CL-Code PRN sequences....................................................................56i 10. APPENDIX I. LETTERS OF EXCEPTION...................................................................................................57 10.1 Scope ...........................................................................................................................................................57 10.2 Applicable Documents ................................................................................................................................57 10.3 Letters of Exception ....................................................................................................................................57 20. APPENDIX II. GPS NAVIGATION DATA STRUCTURE FOR DATA, D(t) ...........................................65 20.1 Scope ...........................................................................................................................................................65 20.2 Applicable Documents. ...............................................................................................................................65 20.2.1 Government Documents....................................................................................................................65 20.2.2 Non-Government Documents............................................................................................................65 20.3 Requirements...............................................................................................................................................67 20.3.1 Data Characteristics...........................................................................................................................67 20.3.2 Message Structure .............................................................................................................................67 20.3.3 Message Content ...............................................................................................................................81 20.3.3.1 Telemetry Word ......................................................................................................................81 20.3.3.2 Handover Word (HOW)..........................................................................................................81 20.3.3.3 Subframe 1 ..............................................................................................................................83
20.3.3.3.1 Subframe 1 Content.......................................................................................................83 20.3.3.3.2 Subframe 1 Parameter Characteristics ..........................................................................86 20.3.3.3.3 User Algorithms for Subframe 1 Data ..........................................................................86 20.3.3.4 Subframes 2 and 3 ...................................................................................................................93 20.3.3.4.1 Content of Subframes 2 and 3 .......................................................................................93 20.3.3.4.2 Subframe 2 and 3 Parameter Characteristics.................................................................95 20.3.3.4.3 User Algorithm for Ephemeris Determination ..............................................................95 20.3.3.4.4 NMCT Validity Time..................................................................................................101 20.3.3.5 Subframes 4 and 5 .................................................................................................................102 20.3.3.5.1 Content of Subframes 4 and 5 .....................................................................................102 20.3.3.5.2 Algorithms Related to Subframe 4 and 5 Data............................................................117 20.3.4 Timing Relationships ......................................................................................................................126 20.3.4.1 Paging and Cutovers..............................................................................................................126 20.3.4.2 SV Time vs. GPS Time .........................................................................................................126 20.3.4.3 Speed of Light .......................................................................................................................126 20.3.4.4 Data Sets................................................................................................................................127 20.3.4.5 Reference Times....................................................................................................................130
IRN-200D-001 IS-GPS-200D
7 Mar 2006 ix
20.3.5 Data Frame Parity............................................................................................................................133 20.3.5.1 SV/CS Parity Algorithm........................................................................................................133 20.3.5.2 User Parity Algorithm ...........................................................................................................133
30. APPENDIX III. GPS NAVIGATION DATA STRUCTURE FOR CNAV DATA, DC(t)..........................137 30.1 Scope .........................................................................................................................................................137 30.2 Applicable Documents. .............................................................................................................................137 30.2.1 Government Documents..................................................................................................................137 30.2.2 Non-Government Documents..........................................................................................................137 30.3 Requirements.............................................................................................................................................139 30.3.1 Data Characteristics.........................................................................................................................139 30.3.2 Message Structure ...........................................................................................................................139 30.3.3 Message Content .............................................................................................................................139 30.3.3.1 Message Type 10 and 11 Ephemeris and Health Parameters ...............................................155 30.3.3.1.1 Message Type 10 and 11 Ephemeris and Health Parameter Content .........................155 30.3.3.1.2 Message Type 10 and 11 Ephemeris Parameter Characteristics .................................158 30.3.3.1.3 User Algorithm for Determination of SV Position......................................................158 30.3.3.2 Message Types 30 Through 37 SV Clock Correction Parameters. .......................................163 30.3.3.2.1 Message Type 30 Through 37 SV Clock Correction Parameter Content....................163 30.3.3.2.2 Clock Parameter Characteristics .................................................................................163 30.3.3.2.3 User Algorithms for SV Clock Correction Data .........................................................163 30.3.3.2.4 SV Clock Accuracy Estimates ....................................................................................165 30.3.3.3 Message Type 30 Ionospheric and Group Delay Correction Parameters ..............................168 30.3.3.3.1 Message Type 30 Ionospheric and Group Delay Correction Parameter Content........168 30.3.3.4 Message Types 31, 12, and 37 Almanac Parameters.............................................................171 30.3.3.4.1 Almanac Reference Week...........................................................................................171 30.3.3.4.2 Almanac Reference Time............................................................................................171 30.3.3.4.3 SV PRN Number.........................................................................................................171 30.3.3.4.4 Signal Health (L1/L2/L5)............................................................................................171 30.3.3.4.5 Midi Almanac Parameter Content...............................................................................172 30.3.3.4.6 Reduced Almanac Parameter Content.........................................................................172 30.3.3.5 Message Type 32 Earth Orientation Parameters (EOP) ........................................................175 30.3.3.5.1 EOP Content ...............................................................................................................175 30.3.3.6 Message Type 33 Coordinated Universal Time (UTC) Parameters ......................................179 30.3.3.6.1 UTC Parameter Content ..............................................................................................179 30.3.3.6.2 UTC and GPS Time ....................................................................................................179
IRN-200D-001 IS-GPS-200D
7 Mar 2006 x
30.3.3.7 Message Types 34, 13, and 14 Differential Correction Parameters ......................................181 30.3.3.7.1 Differential Correction Parameters Content................................................................181 30.3.3.7.2 DC Data Packet ...........................................................................................................181 30.3.3.7.3 Application of Clock-Related DC Data.......................................................................184 30.3.3.7.4 Application of Orbit-Related DC Data........................................................................184 30.3.3.7.5 SV Differential Range Accuracy Estimates ................................................................186
30.3.3.8 Message Type 35 GPS/GNSS Time Offset...........................................................................187 30.3.3.8.1 GPS/GNSS Time Offset Parameter Content ...............................................................187 30.3.3.8.2 GPS and GNSS Time ..................................................................................................187
30.3.3.9 Message Types 36 and 15 Text Messages.............................................................................188 30.3.4 Timing Relationships ......................................................................................................................189
30.3.4.1 Paging and Cutovers..............................................................................................................189 30.3.4.2 SV Time vs. GPS Time .........................................................................................................190 30.3.4.3 Speed of Light .......................................................................................................................190 30.3.5 Data Frame Parity............................................................................................................................191 30.3.5.1 Parity Algorithm....................................................................................................................191
IRN-200D-001 IS-GPS-200D
7 Mar 2006 xi
LIST OF FIGURES
Figure 3-1. Figure 3-2. Figure 3-3. Figure 3-4. Figure 3-5. Figure 3-6. Figure 3-7. Figure 3-8. Figure 3-9. Figure 3-10. Figure 3-11. Figure 3-12. Figure 3-13. Figure 3-14. Figure 3-15. Figure 3-16. Figure 6-1. Figure 10-1. Figure 20-1. Figure 20-2. Figure 20-3. Figure 20-4. Figure 20-5. Figure 30-1. Figure 30-2. Figure 30-3. Figure 30-4. Figure 30-5. Figure 30-6. Figure 30-7. Figure 30-8. Figure 30-9. Figure 30-10.
Generation of P-, C/A-Codes and Modulating Signals ...................................................................19 X1A Shift Register Generator Configuration..................................................................................21 X1B Shift Register Generator Configuration..................................................................................22 X2A Shift Register Generator Configuration..................................................................................23 X2B Shift Register Generator Configuration..................................................................................24 P-Code Generation..........................................................................................................................26 P-Code Signal Component Timing .................................................................................................27 G1 Shift Register Generator Configuration ....................................................................................31 G2 Shift Register Generator Configuration ....................................................................................32 Example C/A-Code Generation ......................................................................................................33 C/A-Code Timing Relationships.....................................................................................................34 L2 CM-/L2 CL-Code Timing Relationships ...................................................................................36 L2 CM/L2 CL Shift Register Generator Configuration ..................................................................37 Convolutional Encoder ...................................................................................................................39 Convolutional Transmit/Decoding Timing Relationships...............................................................39 Time Line Relationship of HOW Message .....................................................................................42 User Received Minimum Signal Level Variations (Example, Block II/IIA/IIR)............................54 Letters of Exception. .......................................................................................................................59 Data Format ....................................................................................................................................69 TLM and HOW Formats.................................................................................................................82 Sample Application of Correction Parameters................................................................................92 Ionospheric Model ........................................................................................................................123 Example Flow Chart for User Implementation of Parity Algorithm.............................................135 Message Type 10 - Ephemeris 1 ...................................................................................................141 Message Type 11 - Ephemeris 2 ...................................................................................................142 Message Type 30 - Clock, IONO & Group Delay ........................................................................143 Message Type 31 - Clock & Reduced Almanac ...........................................................................144 Message Type 32 - Clock & EOP .................................................................................................145 Message Type 33 - Clock & UTC.................................................................................................146 Message Type 34 - Clock & Differential Correction ....................................................................147 Message Type 35 - Clock & GGTO .............................................................................................148 Message Type 36 - Clock & Text ..................................................................................
IS-GPS-200D 7 Dec 2004
xii
Figure 30-11. Figure 30-12. Figure 30-13. Figure 30-14. Figure 30-15. Figure 30-16.
Message Type 12 - Reduced Almanac..........................................................................................151 Message Type 13 – Clock Differential Correction .......................................................................152 Message Type 14 – Ephemeris Differential Correction ................................................................153 Message Type 15 - Text................................................................................................................154 Reduced Almanac Packet Content ................................................................................................174 Differential Correction Data Packet..............................................................................................182
IS-GPS-200D 7 Dec 2004
xiii
LIST OF TABLES
Table 3-I. Table 3-II. Table 3-III. Table 3-IV. Table 3-V. Table 3-VI. Table 3-VII. Table 6-I Table 6-II. Table 20-I. Table 20-II. Table 20-III. Table 20-IV. Table 20-V. Table 20-VI. Table 20-VII. Table 20-VIII. Table 20-IX. Table 20-X. Table 20-XI. Table 20-XII. Table 20-XIII. Table 20-XIV. Table 30-I. Table 30-II. Table 30-III. Table 30-IV. Table 30-V. Table 30-VI. Table 30-VII. Table 30-VIII. Table 30-IX. Table 30-X.
Code Phase Assignments ..................................................................................................................7 Code Phase Assignments (IIR-M, IIF, and subsequent blocks only)................................................9 Signal Configuration .......................................................................................................................13 Composite L1 Transmitted Signal Phase ........................................................................................16 Received Minimum RF Signal Strength .........................................................................................16 P-Code Reset Timing ......................................................................................................................28 Final Code Vector States.................................................................................................................29 Additional C/A-/P-Code Phase Assignments................................................................................ 56c Additional L2 CM-/L2 CL-Code Phase Assignments ...................................................................56i Subframe 1 Parameters ...................................................................................................................87 Ephemeris Data Definitions ............................................................................................................94 Ephemeris Parameters.....................................................................................................................96 Elements of Coordinate Systems ....................................................................................................97 Data IDs and SV IDs in Subframes 4 and 5..................................................................................105 Almanac Parameters .....................................................................................................................107 NAV Data Health Indications .......................................................................................................109 Codes for Health of SV Signal Components.................................................................................110 UTC Parameters............................................................................................................................113 Ionospheric Parameters .................................................................................................................114 IODC Values and Data Set Lengths (Block II/IIA) .....................................................................128 IODC Values and Data Set Lengths (Block IIR/IIR-M/IIF) ........................................................129 Reference Times ...........................................................................................................................132 Parity Encoding Equations............................................................................................................134 Message Types 10 and 11 Parameters...........................................................................................159 Elements of Coordinate System ....................................................................................................161 Clock Correction and Accuracy Parameters .................................................................................164 Group Delay Differential Parameters............................................................................................168 Midi Almanac Parameters.............................................................................................................173 Reduced Almanac Parameters.......................................................................................................174 Earth Orientation Parameters .........................................................................................................176 Application of EOP Parameters ......................................................................................
IRN-200D-001 IS-GPS-200D
7 Mar 2006 xiv
Table 30-XI. GPS/GNSS Time Offset Parameters .............................................................................................188 Table 30-XII. Message Broadcast Intervals.........................................................................................................189
IRN-200D-001 IS-GPS-200D
7 Mar 2006 xv
(This page intentionally left blank.)
IRN-200D-001 IS-GPS-200D
7 Mar 2006 xvi
1. SCOPE 1.1 Scope. This Interface Specification (IS) defines the requirements related to the interface between the Space Segment (SS) of the Global Positioning System (GPS) and the navigation User Segment (US) of the GPS for radio frequency (RF) link 1 (L1) and link 2 (L2). 1.2 IS Approval and Changes. ARINC Engineering Services, LLC has been designated the Interface Control Contractor (ICC), and is responsible for the basic preparation, approval, distribution, retention, and Interface Control Working Group (ICWG) coordination of the IS in accordance with GP-03-001. The Navstar GPS Joint Program Office is the necessary authority to make this IS effective. The Joint Program Office (JPO) administers approvals under the auspices of the Configuration Control Board (CCB), which is governed by the appropriate JPO Operating Instruction (OI). Military organizations and contractors are represented at the CCB by their respective segment member. All civil organizations and public interest are represented by the Department of Transportation representative of the GPS JPO. A proposal to change the approved version of this IS can be submitted by any ICWG participating organization to the GPS JPO and/or the ICC. The ICC is responsible for the preparation of the change paper and change coordination, in accordance with GP-03-001. The ICC prepares the change paper as a Proposed Interface Revision Notice (PIRN) and is responsible for coordination of PIRNs with the ICWG. The ICWG coordinated PIRN must be submitted to the GPS JPO CCB for review and approval. The ICWG review period for all Proposed Interface Revisions Notices (PIRNs) is 45 days after receipt by individual addressees. A written request to extend the review period may be submitted to the ICC for consideration.
IS-GPS-200D 7 Dec 2004
1
(This page intentionally left blank.)
IS-GPS-200D 7 Dec 2004
2
2. APPLICABLE DOCUMENTS
2.1 Government Documents. The following documents of the issue specified contribute to the definition of the interfaces between the GPS Space Segment and the GPS navigation User Segment, and form a part of this IS to the extent specified herein.
Specifications Federal None Military None Other Government Activity None
Standards Federal None Military None
Other Publications GP-03-001 14 Nov 2003
GPS Interface Control Working Group Charter
2.2 Non-Government Documents. The following documents of the issue specified contribute to the definition of the interfaces between the GPS Space Segment and the GPS Navigation User Segment and form a part of this IS to the extent specified herein.
Specifications None
Other Publications None
IS-GPS-200D 7 Dec 2004
3
(This page intentionally left blank.)
IS-GPS-200D 7 Dec 2004
4
3. REQUIREMENTS
3.1 Interface Definition. The interface between the GPS Space Segment (SS) and the GPS navigation User Segment (US) includes two RF links, L1 and L2. Utilizing these links, the space vehicles (SVs) of the SS shall provide continuous earth coverage signals that provide to the US the ranging codes and the system data needed to accomplish the GPS navigation (NAV) mission. These signals shall be available to a suitably equipped user with RF visibility to an SV.
3.2 Interface Identification. The carriers of L1 and L2 are typically modulated by one or more bit trains, each of which normally is a composite generated by the modulo-2 addition of a pseudo-random noise (PRN) ranging code and the downlink system data (referred to as NAV data).
3.2.1 Ranging Codes. Three PRN ranging codes are transmitted: the precision (P) code which is the principal NAV ranging code; the Y-code, used in place of the P-code whenever the anti-spoofing (A-S) mode of operation is activated; and the coarse/acquisition (C/A) code which is used for acquisition of the P (or Y) code (denoted as P(Y)) and as a civil ranging signal. Code-division-multiple-access techniques allow differentiating between the SVs even though they may transmit at the same frequencies. The SVs will transmit intentionally "incorrect" versions of the C/A and the P(Y) codes where needed to protect the users from receiving and utilizing anomalous NAV signals as a result of a malfunction in the SV's reference frequency generation system. These two "incorrect" codes are termed non-standard C/A (NSC) and non-standard Y (NSY) codes.
For Block IIR-M, IIF, and subsequent blocks of SVs, two additional PRN ranging codes are transmitted. They are the L2 civil-moderate (L2 CM) code and the L2 civil-long (L2 CL) code. The SVs will transmit intentionally "incorrect" versions of the L2 CM and L2 CL codes where needed to protect the users from receiving and utilizing anomalous NAV signals as a result of a malfunction in the SV's reference frequency generation system. These "incorrect" codes are termed non-standard L2 CM (NSCM) and non-standard L2 CL (NSCL) codes. The SVs shall also be capable of initiating and terminating the broadcast of NSCM and/or NSCL code(s) independently of each other, in response to CS command.
IS-GPS-200D 7 Dec 2004
5
3.2.1.1 P-Code. The PRN P-code for SV ID number i is a ranging code, Pi(t), of 7 days in length at a chipping rate of 10.23 Mbps. The 7 day sequence is the modulo-2 sum of two sub-sequences referred to as X1 and X2i; their lengths are 15,345,000 chips and 15,345,037 chips, respectively. The X2i sequence is an X2 sequence selectively delayed by 1 to 37 chips thereby allowing the basic code generation technique to produce a set of 37 mutually exclusive P-code sequences of 7 days in length. Of these, 32 are designated for use by SVs and 5 are reserved for other purposes (e.g. ground transmitters, etc.). Assignment of these code phase segments by SV-ID number (or other use) is given in Table 3-I. Additional PRN P-code sequences with assigned PRN numbers are provided in Section 6.3.5.2, Table 6-I
3.2.1.2 Y-Code. The PRN Y-code is used in place of the P-code when the A-S mode of operation is activated.
3.2.1.3 C/A-Code. The PRN C/A-Code for SV ID number i is a Gold code, Gi(t), of 1 millisecond in length at a chipping rate of 1023 Kbps. The Gi(t) sequence is a linear pattern generated by the modulo-2 addition of two subsequences, G1 and G2i, each of which is a 1023 chip long linear pattern. The epochs of the Gold code are synchronized with the X1 epochs of the P-code. As shown in Table 3-I, the G2i sequence is a G2 sequence selectively delayed by pre-assigned number of chips, thereby generating a set of different C/A-codes. Assignment of these by GPS PRN signal number is given in Table 3-I. Additional PRN C/A-code sequences with assigned PRN numbers are provided in Section 6.3.5.1, Table 6-I
3.2.1.4 L2 CM-Code (IIR-M, IIF, and subsequent blocks). The PRN L2 CM-code for SV ID number i is a ranging code, CM,i(t), which is 20 milliseconds in length at a chipping rate of 511.5 Kbps. The epochs of the L2 CM-code are synchronized with the X1 epochs of the P-code. The CM,i(t) sequence is a linear pattern which is short cycled every count of 10230 chips by resetting with a specified initial state. Assignment of initial states by GPS PRN signal number is given in Table 3-II. Additional PRN L2 CM-code sequence pairs are provided in Section 6.3.5.3, Table 6-II
3.2.1.5 L2 CL-Code (IIR-M, IIF, and subsequent blocks). The PRN L2 CL-code for SV ID number i is a ranging code, CL,i(t), which is 1.5 seconds in length at a chipping rate of 511.5 Kbps. The epochs of the L2 CL-code are synchronized with the X1 epochs of the P-code. The CL,i(t) sequence is a linear pattern which is generated using the same code generator polynomial as the one used for CM,i(t). However, the CL,i(t) sequence is short cycled by resetting with a specified initial state every code count of 767250 chips. Assignment of initial states by GPS PRN signal number is given in Table 3-II. Additional PRN L2 CL-code sequence pairs are provided in Section 6.3.5.3, Table 6-II
IRN-200D-001 IS-GPS-200D
7 Mar 2006 6
Table 3-I. Code Phase Assignments (sheet 1 of 2)
SV GPS PRN Code Phase Selection
ID Signal
No.
No.
C/A(G2i)**** (X2i)
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
9
9
10
10
11
11
12
12
13
13
14
14
15
15
16
16
17
17
18
18
19
19
2 ⊕ 6
1
3 ⊕ 7
2
4 ⊕ 8
3
5 ⊕ 9
4
1 ⊕ 9
5
2 ⊕ 10
6
1 ⊕ 8
7
2 ⊕ 9
8
3 ⊕ 10
9
2 ⊕ 3
10
3 ⊕ 4
11
5 ⊕ 6
12
6 ⊕ 7
13
7 ⊕ 8
14
8 ⊕ 9
15
9 ⊕ 10
16
1 ⊕ 4
17
2 ⊕ 5
18
3 ⊕ 6
19
Code Delay Chips
C/A
P
5
1
6
2
7
3
8
4
17
5
18
6
139
7
140
8
141
9
251
10
252
11
254
12
255
13
256
14
257
15
258
16
469
17
470
18
471
19
First 10 Chips Octal*
C/A
1440 1620 1710 1744 1133 1455 1131 1454 1626 1504 1642 1750 1764 1772 1775 1776 1156 1467 1633
First 12 Chips
Octal P
4444 4000 4222 4333 4377 4355 4344 4340 4342 4343
⏐ ⏐ ⏐ ⏐ ⏐ ⏐ ⏐ ⏐ 4343
* In the octal notation for the first 10 chips of the C/A code as shown in this column, the first digit (1) represents a "1" for the first chip and the last three digits are the conventional octal representation of the remaining 9 chips. (For example, the first 10 chips of the C/A code for PRN Signal Assembly No. 1 are: 1100100000).
** C/A codes 34 and 37 are common. *** PRN sequences 33 through 37 are reserved for other uses (e.g. ground transmitters). **** The two-tap coder utilized here is only an example implementation that generates a limited set
of valid C/A codes. ⊕ = "exclusive or"
NOTE: The code phase assignments constitute inseparable pairs, each consisting of a specific C/A and a specific P code phase, as shown above.
IS-GPS-200D 7 Dec 2004
7
Table 3-I. Code Phase Assignments (sheet 2 of 2)
SV GPS PRN Code Phase Selection
ID Signal
No.
No.
C/A(G2i)**** (X2i)
20
20
4 ⊕ 7
20
21
21
5 ⊕ 8
21
22
22
6 ⊕ 9
22
23
23
1 ⊕ 3
23
24
24
4 ⊕ 6
24
25
25
5 ⊕ 7
25
26
26
6 ⊕ 8
26
27
27
7 ⊕ 9
27
28
28
8 ⊕ 10
28
29
29
1 ⊕ 6
29
30
30
2 ⊕ 7
30
31
31
3 ⊕ 8
31
32
32
4 ⊕ 9
32
***
33
5 ⊕ 10
33
*** 34**
4 ⊕ 10
34
***
35
1 ⊕ 7
35
***
36
2 ⊕ 8
36
*** 37**
4 ⊕ 10
37
Code Delay Chips
C/A
P
472
20
473
21
474
22
509
23
512
24
513
25
514
26
515
27
516
28
859
29
860
30
861
31
862
32
863
33
950
34
947
35
948
36
950
37
First 10 Chips Octal*
C/A
1715 1746 1763 1063 1706 1743 1761 1770 1774 1127 1453 1625 1712 1745 1713 1134 1456 1713
First 12 Chips
Octal P
4343 ⏐ ⏐ ⏐ ⏐ ⏐ ⏐ ⏐ ⏐ ⏐ ⏐ ⏐ ⏐ ⏐ ⏐ ⏐ ⏐
4343
* In the octal notation for the first 10 chips of the C/A code as shown in this column, the first digit (1) represents a "1" for the first chip and the last three digits are the conventional octal representation of the remaining 9 chips. (For example, the first 10 chips of the C/A code for PRN Signal Assembly No. 1 are: 1100100000).
** C/A codes 34 and 37 are common. *** PRN sequences 33 through 37 are reserved for other uses (e.g. ground transmitters). **** The two-tap coder utilized here is only an example implementation that generates a limited
set of valid C/A codes. ⊕ = "exclusive or"
NOTE: The code phase assignments constitute inseparable pairs, each consisting of a specific C/A and a specific P code phase, as shown above.
IS-GPS-200D 7 Dec 2004
8
Table 3-II. Code Phase Assignments (IIR-M, IIF, and subsequent blocks only) (sheet 1 of 2)
SV GPS PRN Initial Shift Register State (Octal)
ID
Signal
No.
No.
L2 CM
L2 CL
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
9
9
10
10
11
11
12
12
13
13
14
14
15
15
16
16
17
17
18
18
19
19
742417664 756014035 002747144 066265724 601403471 703232733 124510070 617316361 047541621 733031046 713512145 024437606 021264003 230655351 001314400 222021506 540264026 205521705 064022144
624145772 506610362 220360016 710406104 001143345 053023326 652521276 206124777 015563374 561522076 023163525 117776450 606516355 003037343 046515565 671511621 605402220 002576207 525163451
End Shift Register State (Octal)
L2 CM *
L2 CL **
552566002 034445034 723443711 511222013 463055213 667044524 652322653 505703344 520302775 244205506 236174002 654305531 435070571 630431251 234043417 535540745 043056734 731304103 412120105
267724236 167516066 771756405 047202624 052770433 761743665 133015726 610611511 352150323 051266046 305611373 504676773 272572634 731320771 631326563 231516360 030367366 713543613 232674654
* Short cycled period = 10230 ** Short cycled period = 767250 *** PRN sequences 33 through 37 are reserved for other uses (e.g. ground transmitters).
NOTE: There are many other available initial register states which can be used for other signal transmitters including any additional SVs in future.
IS-GPS-200D 7 Dec 2004
9
Table 3-II. Code Phase Assignments (IIR-M, IIF, and subsequent blocks only) (sheet 2 of 2)
SV GPS PRN Initial Shift Register State (Octal)
ID
Signal
No.
No.
L2 CM
L2 CL
20
20
21
21
22
22
23
23
24
24
25
25
26
26
27
27
28
28
29
29
30
30
31
31
32
32
***
33
***
34
***
35
***
36
***
37
120161274 044023533 724744327 045743577 741201660 700274134 010247261 713433445 737324162 311627434 710452007 722462133 050172213 500653703 755077436 136717361 756675453 435506112
266527765 006760703 501474556 743747443 615534726 763621420 720727474 700521043 222567263 132765304 746332245 102300466 255231716 437661701 717047302 222614207 561123307 240713073
End Shift Register State (Octal)
L2 CM *
L2 CL **
365636111 143324657 110766462 602405203 177735650 630177560 653467107 406576630 221777100 773266673 100010710 431037132 624127475 154624012 275636742 644341556 514260662 133501670
641733155 730125345 000316074 171313614 001523662 023457250 330733254 625055726 476524061 602066031 012412526 705144501 615373171 041637664 100107264 634251723 257012032 703702423
* Short cycled period = 10230 ** Short cycled period = 767250 *** PRN sequences 33 through 37 are reserved for other uses (e.g. ground transmitters).
NOTE: There are many other available initial register states which can be used for other signal transmitters including any additional SVs in future.
IS-GPS-200D 7 Dec 2004
10
3.2.1.6 Non-Standard Codes. The NSC, NSCM, NSCL, and NSY codes, used to protect the user from a malfunction in the SV's reference frequency system (reference paragraph 3.2.1), are not for utilization by the user and, therefore, are not defined in this document.
3.2.2 NAV Data. The NAV data, D(t), includes SV ephemerides, system time, SV clock behavior data, status messages and C/A to P (or Y) code handover information, etc. The 50 bps data is modulo-2 added to the P(Y)and C/A- codes; the resultant bit-trains are used to modulate the L1 and L2 carriers. For a given SV, the data train D(t), if present, is common to the P(Y)- and C/A- codes on both the L1 and L2 channels. The content and characteristics of the NAV data, D(t), are given in Appendix II of this document.
For Block IIR-M, Block IIF, and subsequent blocks of SVs, civil navigation (CNAV) data, DC(t), also includes SV ephemerides, system time, SV clock behavior, status messages, etc. The DC(t) is a 25 bps data stream which is coded by a rate ½ convolutional coder. When selected by ground command, the resulting 50 sps symbol stream is modulo-2 added to the L2 CM-code; the resultant bit-train is combined with L2 CL-code using chip by chip timedivision multiplexing method (i.e. alternating between L2 CM ⊕ data and L2 CL chips); the multiplexed bit-train is used to modulate the L2 carrier. The content and characteristics of the CNAV data, DC(t), are given in Appendix III of this document.
During the initial period of Block IIR-M SVs operation, prior to Initial Operational Capability of L2 C signal, Block IIR-M may modulo-2 add the NAV data, D(t), to the L2 CM-code instead of CNAV data, DC(t). Moreover, the NAV data, D(t), can be used in one of two different data rates which are selectable by ground command. D(t) with a data rate of 50 bps can be commanded to be modulo-2 added to the L2 CM-code, or D(t) with a symbol rate of 50 symbols per second (sps) (rate ½ convolutional encode of a 25 bps NAV data) can be commanded to be modulo-2 added to the L2 CM-code. The resultant bit-train is combined with L2 CL-code using chip by chip time-division multiplexing method (i.e. alternating between L2 CM ⊕ data and L2 CL chips). This multiplexed bit-train is used to modulate the L2 carrier.
IS-GPS-200D 7 Dec 2004
11
3.2.3 L1/L2 Signal Structure. The L1 consists of two carrier components which are in phase quadrature with each other. Each carrier component is bi-phase shift key (BPSK) modulated by a separate bit train. One bit train is the modulo-2 sum of the P(Y)-code and NAV data, D(t), while the other is the modulo-2 sum of the C/A-code and the NAV data, D(t). For Block II/IIA and IIR, the L2 is BPSK modulated by only one of those two bit trains; the bit train to be used for L2 modulation is selected by ground command. A third modulation mode is also selectable on the L2 channel by ground command: it utilizes the P(Y)-code without the NAV data as the modulating signal. For a particular SV, all transmitted signal elements (carriers, codes and data) are coherently derived from the same onboard frequency source.
For Block IIR-M, Block IIF, and subsequent blocks of SVs, the L2 consists of two carrier components. One carrier component is BPSK modulated by the bit train which is the modulo-2 sum of the P(Y)-code with or without NAV data D(t), while the other is BPSK modulated by any one of three other bit trains which are selectable by ground command. The three possible bit trains are: (1) the modulo-2 sum of the C/A-code and D(t); (2) the C/A-code with no data and; (3) a chip-by-chip time multiplex combination of bit trains consisting of the L2 CM-code with DC(t) and the L2 CL-code with no data. The L2 CM-code with the 50 sps symbol stream of DC(t) is time-multiplexed with L2 CL-code at a 1023 kHz rate as described in paragraph 3.2.2. The first L2 CM-code chip starts synchronously with the end/start of week epoch.
During the initial period of Block IIR-M SVs operation, prior to Initial Operational Capability of L2 C signal, Block IIR-M may modulo-2 add the NAV data, D(t), to the L2 CM-code instead of CNAV data, DC(t). In such configuration, the data rate of D(t) may be 50 bps (i.e. without convolution encoding) or it may be 25 bps. The D(t) of 25 bps shall be convolutionally encoded resulting in 50 sps.
The different configuration and combination of codes/signals specified in this section are shown in Table 3-III.
IS-GPS-200D 7 Dec 2004
12
Table 3-III. Signal Configuration
SV Blocks
In-Phase*
L1 Quadrature-Phase*
In-Phase*
L2** Quadrature-Phase*
Block II/IIA/IIR P(Y) ⊕ D(t)
C/A ⊕ D(t)
P(Y) ⊕ D(t) or
P(Y) or
C/A ⊕ D(t)
Not Applicable
Block IIR-M*** P(Y) ⊕ D(t)
C/A ⊕ D(t)
P(Y) ⊕ D(t) or
P(Y)
L2 CM ⊕ D(t) with L2 CL or
L2 CM ⊕ D′(t) with L2 CL or
C/A ⊕ D(t) or C/A
Block IIR-M/IIF P(Y) ⊕ D(t)
C/A ⊕ D(t)
P(Y) ⊕ D(t) or
P(Y)
L2 CM ⊕ DC(t) with L2 CL or
C/A ⊕ D(t) or C/A
Notes:
1) The configuration identified in this table reflects only the content of Section 3.2.3 and does not show all available codes/signals on L1/L2. 2) It should be noted that there are no flags or bits in the navigation message to directly indicate which signal option is broadcast for L2 Civil (L2 C) signal.
⊕ = “exclusive-or” (modulo-2 addition) D(t) = NAV data at 50 bps D′(t) = NAV data at 25 bps with FEC encoding resulting in 50 sps DC(t) = CNAV data at 25 bps with FEC encoding resulting in 50 sps
* Terminology of “in-phase” and “quadrature-phase” is used only to identify the relative phase quadrature relationship of the carrier components (i.e. 90 degrees offset of each other).
** The two carrier components on L2 may not have the phase quadrature relationship. They may be broadcast on same phase (ref. Section 3.3.1.5).
*** Possible signal configuration for Block IIR-M only during the initial period of Block IIR-M SVs operation, prior to Initial Operational Capability of L2 C signal. See paragraph 3.2.2.
IS-GPS-200D 7 Dec 2004
13
3.3 Interface Criteria. The criteria specified in the following define the requisite characteristics of the SS/US interface for the L1 and L2.
3.3.1 Composite Signal. The following criteria define the characteristics of the composite signals.
3.3.1.1 Frequency Plan. The signals shall be contained within two 20.46-MHz bands centered about L1 and L2. The carrier frequencies for the L1 and L2 signals shall be coherently derived from a common frequency source within the SV. The nominal frequency of this source -- as it appears to an observer on the ground -- is 10.23 MHz. The SV carrier frequency and clock rates -- as they would appear to an observer located in the SV -- are offset to compensate for relativistic effects. The clock rates are offset by ∆ f/f = -4.4647E-10, equivalent to a change in the P-code chipping rate of 10.23 MHz offset by a ∆ f = -4.5674E-3 Hz. This is equal to 10.22999999543 MHz. The nominal carrier frequencies (f0) shall be 1575.42 MHz, and 1227.6 MHz for L1 and L2, respectively.
3.3.1.2 Correlation Loss. Correlation loss is defined as the difference between the SV power received in a 20.46 MHz bandwidth and the signal power recovered in an ideal correlation receiver of the same bandwidth. On the L1 and L2 channels, the worst case correlation loss occurs when the carrier is modulated by the sum of the P(Y) code and the NAV data stream. For this case, the correlation loss apportionment shall be as follows:
1.
SV modulation imperfections 0.6 dB
2.
Ideal UE receiver waveform distortion 0.4 dB
(due to 20.46 MHz filter)
3.3.1.3 Carrier Phase Noise. The phase noise spectral density of the unmodulated carrier shall be such that a phase locked loop of 10 Hz one-sided noise bandwidth shall be able to track the carrier to an accuracy of 0.1 radians rms.
3.3.1.4 Spurious Transmissions. In-band spurious transmissions shall be at least 40 dB below the unmodulated L1 and L2 carriers over the allocated 20.46 MHz channel bandwidth.
IS-GPS-200D 7 Dec 2004
14
3.3.1.5 Phase Quadrature. The two L1 carrier components modulated by the two separate bit trains (C/A-code plus data and P(Y)-code plus data) shall be in phase quadrature (within ±100 milliradians) with the C/A signal carrier lagging the P signal by 90 degrees. Referring to the phase of the P carrier when Pi(t) equals zero as the "zero phase angle", the P(Y)- and C/A-code generator output shall control the respective signal phases in the following manner: when Pi(t) equals one, a 180-degree phase reversal of the P-carrier occurs; when Gi(t) equals one, the C/A carrier advances 90 degrees; when the Gi(t) equals zero, the C/A carrier shall be retarded 90 degrees (such that when Gi(t) changes state, a 180-degree phase reversal of the C/A carrier occurs). The resultant nominal composite transmitted signal phases as a function of the binary state of only the two modulating signals are as shown in Table 3-IV.
For Block IIR-M, IIF, and subsequent blocks of SVs, phase quadrature relationship between the two L2 carrier components can be the same as for the two L1 carrier components as described above. However, for the L2 case, the civil signal carrier component is modulated by any one of three (IIF) or four (IIR-M) different bit trains as described in paragraph 3.2.3. Moreover, the two L2 carrier components can be in same phase. The resultant composite transmitted signal phases will vary as a function of the binary state of the modulating signals as well as the signal power ratio and phase quadrature relationship. Beyond these considerations, additional carrier components in Block IIR-M, IIF, and subsequent blocks of SVs will result in composite transmitted signal phase relationships other than the nominal special case of Table 3-IV.
For Block IIF, the crosstalk between the C/A, when selected, and P(Y) signals shall not exceed –20 dB in the L1 and L2. The crosstalk is the relative power level of the undesired signal to the desired reference signal.
3.3.1.6 User-Received Signal Levels. The SV shall provide L1 and L2 navigation signal strength at end-of-life (EOL), worst-case, in order to meet the minimum levels specified in Table 3-V. The minimum received power is measured at the output of a 3 dBi linearly polarized user receiving antenna (located near ground) at worst normal orientation, when the SV is above a 5-degree elevation angle. The received signal levels are observed within the inband allocation defined in para. 3.3.1.1.
The Block IIF SV shall provide L1 and L2 signals with the following characteristic: the L1 off-axis power gain shall not decrease by more than 2 dB from the Edge-of-Earth (EOE) to nadir, nor more than 10 dB from EOE to 20 degrees off nadir, and no more than 18 dB from EOE to 23 degrees off nadir; the L2 off-axis power gain shall not decrease by more than 2 dB from EOE to nadir, and no more than 10 dB from EOE to 23 degrees off nadir; the power drop off between EOE and ±23 degrees shall be in a monotonically decreasing fashion.
Additional related data is provided as supporting material in paragraph 6.3.1.
IS-GPS-200D 7 Dec 2004
15
Table 3-IV. Composite L1 Transmitted Signal Phase ** (Block II/IIA and IIR SVs Only)
Nominal Composite L1 Signal Phase*
0° -70.5° +109.5° 180°
Code State
P
C/A
0
0
1
0
0
1
1
1
* Relative to 0, 0 code state with positive angles leading and negative angles lagging. ** Based on the composite of two L1 carrier components with 3 dB difference in the power levels of the two.
SV Blocks II/IIA/IIR IIR-M/IIF
Table 3-V.
Channel
L1 L2 L1 L2
Received Minimum RF Signal Strength
Signal
P(Y)
-161.5 dBW
-164.5 dBW
or
-161.5 dBW
-161.5 dBW
C/A or L2 C -158.5 dBW -164.5 dBW -158.5 dBW -160.0 dBW
IS-GPS-200D 7 Dec 2004
16
3.3.1.7 Equipment Group Delay. Equipment group delay is defined as the delay between the signal radiated output of a specific SV (measured at the antenna phase center) and the output of that SV's on-board frequency source; the delay consists of a bias term and an uncertainty. The bias term is of no concern to the US since it is included in the clock correction parameters relayed in the NAV data, and is therefore accounted for by the user computations of system time (reference paragraphs 20.3.3.3.3.1, 30.3.3.2.3). The uncertainty (variation) of this delay as well as the group delay differential between the signals of L1 and L2 are defined in the following.
3.3.1.7.1 Group Delay Uncertainty. The effective uncertainty of the group delay shall not exceed 3.0 nanoseconds (two sigma).
3.3.1.7.2 Group Delay Differential. The group delay differential between the radiated L1 and L2 signals (i.e. L1 P(Y) and L2 P(Y), L1 P(Y) and L2 C) is specified as consisting of random plus bias components. The mean differential is defined as the bias component and will be either positive or negative. For a given navigation payload redundancy configuration, the absolute value of the mean differential delay shall not exceed 15.0 nanoseconds. The random variations about the mean shall not exceed 3.0 nanoseconds (two sigma). Corrections for the bias components of the group delay differential are provided to the US in the Nav message using parameters designated as TGD (reference paragraph 20.3.3.3.3.2) and Inter-Signal Correction (ISC) (reference paragraph 30.3.3.3.1.1).
3.3.1.8 Signal Coherence. All transmitted signals for a particular SV shall be coherently derived from the same on-board frequency standard; all digital signals shall be clocked in coincidence with the PRN transitions for the Psignal and occur at the P-signal transition speed. On the L1 channel the data transitions of the two modulating signals (i.e., that containing the P(Y)-code and that containing the C/A-code), L1 P(Y) and L1 C/A, shall be such that the average time difference between the transitions does not exceed 10 nanoseconds (two sigma).
3.3.1.9 Signal Polarization. The transmitted signal shall be right-hand circularly polarized (RHCP). For the angular range of ±14.3 degrees from boresight, L1 ellipticity shall be no worse than 1.2 dB for Block II/IIA and shall be no worse than 1.8 dB for Block IIR/IIR-M/IIF SVs. L2 ellipticity shall be no worse than 3.2 dB for Block II/IIA SVs and shall be no worse than 2.2 dB for Block IIR/IIR-M/IIF over the angular range of ±14.3 degrees from boresight.
IS-GPS-200D 7 Dec 2004
17
3.3.2 PRN Code Characteristics. The characteristics of the P-, L2 CM-, L2 CL-, and the C/A-codes are defined below in terms of their structure and the basic method used for generating them. Figure 3-1 depicts a simplified block diagram of the scheme for generating the 10.23 Mbps Pi(t) and the 1.023 Mbps Gi(t) patterns (referred to as Pand C/A-codes respectively), and for modulo-2 summing these patterns with the NAV bit train, D(t), which is clocked at 50 bps. The resultant composite bit trains are then used to modulate the signal carriers. 3.3.2.1 Code Structure. The Pi(t) pattern (P-code) is generated by the modulo-2 summation of two PRN codes, X1(t) and X2(t - iT), where T is the period of one P-code chip and equals (1.023 x 107)-1 seconds, while i is an integer from 1 through 37. This allows the generation of 37 unique P(t) code phases (identified in Table 3-I) using the same basic code generator.
The linear Gi(t) pattern (C/A-code) is the modulo-2 sum of two 1023-bit linear patterns, G1 and G2i. The latter sequence is selectively delayed by an integer number of chips to produce many different G(t) patterns (defined in Table 3-I).
The CM,i(t) pattern (L2 CM-code) is a linear pattern which is reset with a specified initial state every code count of 10230 chips. Different initial states are used to generate different CM,i(t) patterns (defined in Table 3-II). The CL,i(t) pattern (L2 CL-code) is also a linear pattern but with a longer reset period of 767250 chips. Different initial states are used to generate different CL,i(t) patterns (defined in Table 3-II). For a given SV-ID, two different initial states are used to generate different CL,i(t) and CM,i(t) patterns. Section 6.3.5 provides a selected subset of additional P-, L2 CM-, L2 CL-, and the C/A-code sequences with assigned PRN numbers.
IRN-200D-001 IS-GPS-200D
7 Mar 2006 18
Z-COUNT
ZCOUNTER
RESET COMMAND GENERATOR
REMOTE COMMAND
EPOCH RESET
EPOCH DETECT
X1 EPOCH
EPOCH RESET
50 Hz
20
X1 CODE GENERATOR
1.023
MHz
10
GOLD CODE GENERATOR
1 KHz
EPOCH DETECT
X1(t)
X2i(t) CODE
SELECT DEVICE
RECLOCKING DEVICE
Gi(t) Pi(t)
Gi(t) D(t)
FORMATTED DATA
D(t)
DATA
ENCODER
X2 CODE GENERATOR
10.23 MHz FREQUENCY
SOURCE
Pi(t) D(t) Pi(t)
Figure 3-1. Generation of P-, C/A-Codes and Modulating Signals
IS-GPS-200D 7 Dec 2004
19
3.3.2.2 P-Code Generation. Each Pi(t) pattern is the modulo-2 sum of two extended patterns clocked at 10.23 Mbps (X1 and X2i). X1 itself is generated by the modulo-2 sum of the output of two 12-stage registers (X1A and X1B) short cycled to 4092 and 4093 chips respectively. When the X1A short cycles are counted to 3750, the X1 epoch is generated. The X1 epoch occurs every 1.5 seconds after 15,345,000 chips of the X1 pattern have been generated. The polynomials for X1A and X1B, as referenced to the shift register input, are:
X1A: 1 + X6 + X8 + X11 + X12, and X1B: 1 + X1 + X2 + X5 + X8 + X9 + X10 + X11 + X12.
Samples of the relationship between shift register taps and the exponents of the corresponding polynomial, referenced to the shift register input, are as shown in Figures 3-2, 3-3, 3-4 and 3-5.
The state of each generator can be expressed as a code vector word which specifies the binary sequence constant of each register as follows: (a) the vector consists of the binary state of each stage of the register, (b) the stage 12 value appears at the left followed by the values of the remaining states in order of descending stage numbers, and (c) the shift direction is from lower to higher stage number with stage 12 providing the current output. This code vector convention represents the present output and 11 future outputs in sequence. Using this convention, at each X1 epoch, the X1A shift register is initialized to code vector 001001001000 and the X1B shift register is initialized to code vector 010101010100. The first chip of the X1A sequence and the first chip of the X1B sequence occur simultaneously in the first chip interval of any X1 period.
The natural 4095 chip cycles of these generating sequences are shortened to cause precession of the X1B sequence with respect to the X1A sequence during subsequent cycles of the X1A sequence in the X1 period. Reinitialization of the X1A shift register produces a 4092 chip sequence by omitting the last 3 chips (001) of the natural 4095 chip X1A sequence. Re-initialization of the X1B shift register produces a 4093 chip sequence by omitting the last 2 chips (01) of the natural 4095 chip X1B sequence. This results in the phase of the X1B sequence lagging by one chip for each X1A cycle in the X1 period.
The X1 period is defined as the 3750 X1A cycles (15,345,000 chips) which is not an integer number of X1B cycles. To accommodate this situation, the X1B shift register is held in the final state (chip 4093) of its 3749th cycle. It remains in this state until the X1A shift register completes its 3750th cycle (343 additional chips). The completion of the 3750th X1A cycle establishes the next X1 epoch which re-initializes both the X1A and X1B shift registers starting a new X1 cycle.
IS-GPS-200D 7 Dec 2004
20
STAGE NUMBERS
POLYNOMIAL X1A:
1 + X 6 + X 8 + X 11 + X 12
1
2
3
4
5
6
7
8
9
10
11
12
0
0
0
1
0
0
1
0
0
1
0
0
OUTPUT
0
1
2
3
4
5
6
7
8
9
10
11
12
INITIAL CONDITIONS
SHIFT DIRECTION
TAP NUMBERS
Figure 3-2. X1A Shift Register Generator Configuration
IS-GPS-200D 7 Dec 2004
21
STAGE NUMBERS
POLYNOMIAL X1B: 1 + X1 + X2 + X5 + X8 + X9 + X10 + X11 + X12
1
2
3
4
5
6
7
8
9
10
11
12
0
0
1
0
1
0
1
0
1
0
1
0
OUTPUT
0
1
2
3
4
5
6
7
8
9
10
11
12
INITIAL CONDITIONS
SHIFT DIRECTION
TAP NUMBERS
Figure 3-3. X1B Shift Register Generator Configuration
IS-GPS-200D 7 Dec 2004
22
STAGE NUMBERS
POLYNOMIAL X2A: 1 + X1 + X3 + X4 + X5 + X7 + X8 + X9 + X10 + X11 + X12
1
2
3
4
5
6
7
8
9
10
11
12
1
0
1
0
0
1
0
0
1
0
0
1
OUTPUT
0
1
2
3
4
5
6
7
8
9
10
11
12
INITIAL CONDITIONS
SHIFT DIRECTION
TAP NUMBERS
Figure 3-4. X2A Shift Register Generator Configuration
IS-GPS-200D 7 Dec 2004
23
STAGE NUMBERS
POLYNOMIAL X2B: 1 + X2 + X3 + X4 + X8 + X9 + X12
1
2
3
4
5
6
7
8
9
10
11
12
0
0
1
0
1
0
1
0
1
0
1
0
OUTPUT
0
1
2
3
4
5
6
7
8
9
10
11
12
INITIAL CONDITIONS
SHIFT DIRECTION
TAP NUMBERS
Figure 3-5. X2B Shift Register Generator Configuration
IS-GPS-200D 7 Dec 2004
24
The X2i sequences are generated by first producing an X2 sequence and then delaying it by a selected integer number of chips, i, ranging from 1 to 37. Each of the X2i sequences is then modulo-2 added to the X1 sequence thereby producing up to 37 unique P(t) sequences.
The X2A and X2B shift registers, used to generate X2, operate in a similar manner to the X1A and X1B shift registers. They are short-cycled, X2A to 4092 and X2B to 4093, so that they have the same relative precession rate as the X1 shift registers. X2A epochs are counted to include 3750 cycles and X2B is held in the last state at 3749 cycle until X2A completes its 3750th cycle. The polynomials for X2A and X2B, as referenced to the shift register input, are:
X2A: 1 + X1 + X3 + X4 + X5 + X7 + X8 + X9 + X10 + X11 + X12, and X2B: 1 + X2 + X3 + X4 + X8 + X9 + X12.
(The initialization vector for X2A is 100100100101 and for X2B is 010101010100).
The X2A and X2B epochs are made to precess with respect to the X1A and X1B epochs by causing the X2 period to be 37 chips longer than the X1 period. When the X2A is in the last state of its 3750th cycle and X2B is in the last state of its 3749th cycle, their transitions to their respective initial states are delayed by 37 chip time durations.
At the beginning of the GPS week, X1A, X1B, X2A and X2B shift registers are initialized to produce the first chip of the week. The precession of the shift registers with respect to X1A continues until the last X1A period of the GPS week interval. During this particular X1A period, X1B, X2A and X2B are held when reaching the last state of their respective cycles until that X1A cycle is completed (see Table 3-VI). At this point, all four shift registers are initialized and provide the first chip of the new week.
Figure 3-6 shows a functional P-code mechanization. Signal component timing is shown in Figure 3-7, while the end-of-week reset timing and the final code vector states are given in Tables 3-VI and 3-VII, respectively.
IS-GPS-200D 7 Dec 2004
25
10.23 MHz
6, 8, 11, 12
RESUME
C
X1A
R
I
REGISTER
1 6
12
SET X1A EPOCH A
4092 DECODE
X1 EPOCH
3750
CLOCK CONTROL
HALT
C
X1B
R
I
REGISTER
1
12
1, 2, 5, 8, 9, 10, 11, 12
CLOCK CONTROL
HALT
C
X2A
R
I
REGISTER
1
12
SET X1B EPOCH
3749
Z-COUNTER 403,200
B
4093 DECODE
7 DAY RESET
END/WEEK
REGISTER INPUTS
3750
SET X2A EPOCH C
C - CLOCK I - INPUT R - RESET TO
INITIAL CONDITIONS ON NEXT CLOCK
1, 3, 4, 5, 7, 8, 9, 10, 11, 12
4092 DECODE
START/WEEK
RESUME
X2
EPOCH
37
ENABLE
A
HALT
END/WEEK
X1
B
Pi
CLOCK CONTROL
C
X2B
R
I
REGISTER
1 2
12
SET X2B EPOCH
3749
C
X2 i
1 i
2, 3, 4, 8, 9, 12
4093 DECODE
X2
SHIFT
REGISTER
Figure 3-6. P-Code Generation
IS-GPS-200D 7 Dec 2004
26
0
1
2
3
0
1
2
3
0
X1 EPOCHS
37 Chips
74 Chips
X2 EPOCHS *
P Epoch
TIME 0
1.5 sec 3.0 sec 4.5 sec 7 days
* Does not include any offset due to PRN delay.
Figure 3-7. P-Code Signal Component Timing
14 days
IS-GPS-200D 7 Dec 2004
27
Table 3-VI. P-Code Reset Timing (Last 400 µsec of 7-day period) **
X1A-Code
Code Chip
X1B-Code
X2A-Code
1 • • • 3023
• • • 3127
345 • • •
3367
• • • 3471
1070 • • •
4092 • • •
4092
• • • 3749
• • • 4092*
• • • 4093 • • • 4093
• • • 4092
• • • 4092
* Last Chip of Week. ** Does not include any X2 offset due to PRN delay.
X2B-Code
967 • • •
3989
• • • 4093 • • • 4093
• • • 4093
IS-GPS-200D 7 Dec 2004
28
Table 3-VII. Final Code Vector States
Code
Chip Number
Vector State
Vector State for 1st Chip following Epoch
4091 X1A
4092
100010010010 000100100100
001001001000
4092 X1B
4093
100101010101 001010101010
010101010100
4091 X2A
4092
111001001001 110010010010
100100100101
4092 X2B
4093
000101010101 001010101010
010101010100
NOTE: First Chip in each sequence is output bit whose leading edge occurs simultaneously with the epoch.
IS-GPS-200D 7 Dec 2004
29
3.3.2.3 C/A-Code Generation. Each Gi(t) sequence is a 1023-bit Gold-code which is itself the modulo-2 sum of two 1023-bit linear patterns, G1 and G2i. The G2i sequence is formed by effectively delaying the G2 sequence by an integer number of chips. The G1 and G2 sequences are generated by 10-stage shift registers having the following polynomials as referred to in the shift register input (see Figures 3-8 and 3-9).
G1 = X10 + X3 + 1, and G2 = X10 + X9 + X8 + X6 + X3 + X2 + 1. The initialization vector for the G1 and G2 sequences is 1111111111. The G1 and G2 shift registers are initialized at the P-coder X1 epoch. The G1 and G2 registers are clocked at 1.023 MHz derived from the 10.23 MHz P-coder clock. The initialization by the X1 epoch phases the 1.023 MHz clock to insure that the first chip of the C/A code begins at the same time as the first chip of the P-code. The effective delay of the G2 sequence to form the G2i sequence may be accomplished by combining the output of two stages of the G2 shift register by modulo-2 addition (see Figure 3-10). However, this two-tap coder implementation generates only a limited set of valid C/A codes. Table 3-I contains a tabulation of the G2 shift register taps selected and their corresponding P-code X2i and PRN signal numbers together with the first several chips of each resultant PRN code. Timing relationships related to the C/A code are shown in Figure 3-11.
IS-GPS-200D 7 Dec 2004
30
STAGE NUMBERS
POLYNOMIAL G1:
1 + X 3 + X 10
INPUT
1
2
3
4
5
6
7
8
9
10
1
1
1
1
1
1
1
1
1
1
OUTPUT
0
1
2
3
4
5
6
7
8
9
10
INITIAL CONDITIONS
SHIFT DIRECTION
TAP NUMBERS
Figure 3-8. G1 Shift Register Generator Configuration
IS-GPS-200D 7 Dec 2004
31
STAGE NUMBERS
POLYNOMIAL G2:
1 + X 2 + X 3 +X6 + X 8 + X 9 + X 10
INPUT
1
2
3
4
5
6
7
8
9
10
1
1
1
1
1
1
1
1
1
1
OUTPUT
0
1
2
3
4
5
6
7
8
9
10
INITIAL CONDITIONS
SHIFT DIRECTION
TAP NUMBERS
Figure 3-9. G2 Shift Register Generator Configuration
IS-GPS-200D 7 Dec 2004
32
X1 EPOCH
10.23 MHz SYNCH
10
SYNCH
G EPOCH 20
1 Kbps
1023 DECODE
3
10
I
S
G1
G1
REGISTER
C
2 3 6 8 9 10
I
C
G2
REGISTER
S
Gi
G2i PHASE SELECT
LOGIC
50 bps TO DATA ENCODER
REGISTER INPUTS
CIS-
CLOCK INPUT SET ALL ONES
Figure 3-10. Example C/A-Code Generation
IS-GPS-200D 7 Dec 2004
33
X1 Epoch @ 2/3 bps
1023
1023
1023 BIT Gold Code @ 1023 Kbps
1023
1023
1023
etc.
1 msec
0
1
2
18
19
0
Gold Code Epochs @ 1000/sec
Data @ 50 cps 20 msec
Figure 3-11. C/A-Code Timing Relationships
IS-GPS-200D 7 Dec 2004
34
3.3.2.4 L2 CM-/L2 CL-Code Generation. Each CM,i(t) pattern (L2 CM-code) and CL,i(t) pattern (L2 CL-code) are generated using the same code generator polynomial each clocked at 511.5 Kbps. Each pattern is initiated and reset with a specified initial state (defined in Table 3-II). CM,i(t) pattern is reset after 10230 chips resulting in a code period of 20 milliseconds, and CL,i(t) pattern is reset after 767250 chips resulting in a code period of 1.5 seconds. The L2 CM and L2 CL shift registers are initialized at the P-coder X1 epoch. The first L2 CM-code chip starts synchronously with the end/start of week epoch. Timing relationships related to the L2 CM-/L2 CLcodes are shown in Figure 3-12. The maximal polynomial used for L2 CM- and L2 CL-codes is 1112225171 (octal) of degree 27. The L2 CM and L2 CL code generator is conceptually described in Figure 3-13 using modular-type shift register generator.
IS-GPS-200D 7 Dec 2004
35
0 End/start of week
1.5 second
X1 Epoch @ 2/3 bps
767250 Chips 767250 BIT L2 CL-Code @ 511.5 Kbps
1 10230
2 10230
3 10230
10230 BIT L2 CM-Code @ 511.5 Kbps
4 10230
73 10230
74 10230
1
etc.
75
10230
etc.
20 msec
Data @ 50 cps
L2 CM @ 511.5 Kbps L2 CL @ 511.5 Kbps L2 C @ 1023 Kbps
Figure 3-12. L2 CM-/L2 CL-Code Timing Relationships
36
IS-GPS-200D 7 Dec 2004
DELAY NUMBERS
POLYNOMIAL:
1 + X3 + X4 +X5 + X6 + X9 + X11 + X13 + X16 + X19 + X21 + X24 + X27
Figure 3-13. L2 CM/L2 CL Shift Register Generator Configuration
IS-GPS-200D 7 Dec 2004
37
3
3
2
3
3
2
2
3
1
1
1
3
OUTPUT
INITIAL CONDITIONS ARE A FUNCTION OF PRN AND CODE PERIOD (MODERATE/LONG) SHIFT DIRECTION
3.3.3 Navigation Data. The content and format of the NAV data, D(t), and the CNAV data, DC(t), are given in Appendices II and III, respectively, of this document.
3.3.3.1 Navigation Data Modulation (L2 CM). For Block IIR-M, Block IIF, and subsequent blocks of SVs, the CNAV bit train, DC(t), is rate ½ encoded and, thus, clocked at 50 sps. The resultant symbol sequence is then modulo-2 added to the L2 CM-code. During the initial period of Block IIR-M SVs operation, prior to Initial Operational Capability of L2 C signal, and upon ground command, the NAV bit train, D(t), at one of two data rates, may be modulo-2 added to the L2 CM-code instead of CNAV data, DC(t), as further described in Section 3.2.2.
3.3.3.1.1 Forward Error Correction. The CNAV bit train, DC(t), will always be Forward Error Correction (FEC) encoded by a rate 1/2 convolutional code. For Block IIR-M, the NAV bit train, D(t), can be selected to be convolutionally encoded. The resulting symbol rate is 50 sps. The convolutional coding will be constraint length 7, with a convolutional encoder logic arrangement as illustrated in Figure 3-14. The G1 symbol is selected on the output as the first half of a 40-millisecond data bit period.
Twelve-second navigation messages broadcast by the SV are synchronized with every eighth of the SV's P(Y)-code X1 epochs. However, the navigation message is FEC encoded in a continuous process independent of message boundaries (i.e. at the beginning of each new message, the encoder registers illustrated in Figure 3-14 contains the last six bits of the previous message).
Because the FEC encoding convolves successive messages, it is necessary to define which transmitted symbol is synchronized to SV time, as follows. The beginning of the first symbol that contains any information about the first bit of a message will be synchronized to every eighth X1 epoch (referenced to end/start of week). The users’ convolutional decoders will introduce a fixed delay that depends on their respective algorithms (usually 5 constraint lengths, or 35 bits), for which they must compensate to determine system time from the received signal. This convolutional decoding delay and the various relationships with the start of the data block transmission and SV time are illustrated in Figure 3-15.
IS-GPS-200D 7 Dec 2004
38
DATA INPUT (25 BPS)
G2 (133 OCTAL)
G1 (171 OCTAL)
OUTPUT SYMBOLS (50 SPS)
(ALTERNATING G1/G2)
SYMBOL CLOCK
Figure 3-14. Convolutional Encoder
ENCODED DATA BLOCK TRANSMITTED ON L2
ENCODED DATA BLOCK RECEIVED BY USER
EARLY
DATA BLOCK DECODED BY USER
USER’S DECODING DELAY
DOWNLINK DELAY
LATER
SV 12 SECOND EPOCHS
Figure 3-15. Convolutional Transmit/Decoding Timing Relationships
IS-GPS-200D 7 Dec 2004
39
3.3.4 GPS Time and SV Z-Count. GPS time is established by the Control Segment and is referenced to Coordinated Universal Time (UTC) as maintained by the U.S. Naval Observatory (UTC(USNO)) zero time-point defined as midnight on the night of January 5, 1980/morning of January 6, 1980. The largest unit used in stating GPS time is one week defined as 604,800 seconds. GPS time may differ from UTC because GPS time shall be a continuous time scale, while UTC is corrected periodically with an integer number of leap seconds. There also is an inherent but bounded drift rate between the UTC and GPS time scales. The OCS shall control the GPS time scale to be within one microsecond of UTC (modulo one second). The NAV data contains the requisite data for relating GPS time to UTC. The accuracy of this data during the transmission interval shall be such that it shall relate GPS time (maintained by the MCS of the CS) to UTC (USNO) within 90 nanoseconds (one sigma). This data is generated by the CS; therefore, the accuracy of this relationship may degrade if for some reason the CS is unable to upload data to a SV. At this point, it is assumed that alternate sources of UTC are no longer available, and the relative accuracy of the GPS/UTC relationship will be sufficient for users. Range error components (e.g. SV clock and position) contribute to the GPS time transfer error, and under normal operating circumstances (two frequency time transfers from SV(s) whose navigation message indicates a URA of eight meters or less), this corresponds to a 97 nanosecond (one sigma) apparent uncertainty at the SV. Propagation delay errors and receiver equipment biases unique to the user add to this time transfer uncertainty.
IS-GPS-200D 7 Dec 2004
40
In each SV the X1 epochs of the P-code offer a convenient unit for precisely counting and communicating time. Time stated in this manner is referred to as Z-count, which is given as a 29-bit binary number consisting of two parts as follows:
a. The binary number represented by the 19 least significant bits of the Z-count is referred to as the time of week (TOW) count and is defined as being equal to the number of X1 epochs that have occurred since the transition from the previous week. The count is short-cycled such that the range of the TOW-count is from 0 to 403,199 X1 epochs (equaling one week) and is reset to zero at the end of each week. The TOWcount's zero state is defined as that X1 epoch which is coincident with the start of the present week. This epoch occurs at (approximately) midnight Saturday night-Sunday morning, where midnight is defined as 0000 hours on the UTC scale which is nominally referenced to the Greenwich Meridian. Over the years the occurrence of the "zero state epoch" may differ by a few seconds from 0000 hours on the UTC scale since UTC is periodically corrected with leap seconds while the TOW-count is continuous without such correction. To aid rapid ground lock-on to the P-code signal, a truncated version of the TOW-count, consisting of its 17 most significant bits, is contained in the hand-over word (HOW) of the L1 and L2 NAV data (D(t)) stream; the relationship between the actual TOW-count and its truncated HOW version is illustrated by Figure 3-16.
b. The ten most significant bits of the Z-count are a modulo 1024 binary representation of the sequential number assigned to the current GPS week (see paragraph 6.2.4). The range of this count is from 0 to 1023 with its zero state being defined as the GPS week number zero and every integer multiple of 1024 weeks, thereafter (i.e. 0, 1024, 2048, etc.).
IS-GPS-200D 7 Dec 2004
41
X1 EPOCHS
P(Y)-CODE EPOCH (END/START OF WEEK)
1.5 sec
403,192
403,196
0 123 4 567 8
403,199
DECIMAL EQUIVALENTS OF ACTUAL TOW COUNTS
SUBFRAME EPOCHS
6 sec
100,799
0
1
2
3
DECIMAL EQUIVALENTS OF HOW-MESSAGE TOW COUNTS
NOTES:
1. TO AID IN RAPID GROUND LOCK-ON THE HAND-OVER WORD (HOW ) OF EACH SUBFRAME CONTAINS A TRUNCATED TIME-OF-WEEK (TOW) COUNT
2. THE HOW IS THE SECOND WORD IN EACH SUBFRAME (REFERENCE PARAGRAPH 20.3.3.2).
3. THE HOW-MESSAGE TOW COUNT CONSISTS OF THE 17 MSBs OF THE ACTUAL TOW COUNT AT THE START OF THE NEXT SUBFRAME.
4. TO CONVERT FROM THE HOW-MESSAGE TOW COUNT TO THE ACTUAL TOW COUNT AT THE START OF THE NEXT SUBFRAME, MULTIPLY BY FOUR.
5. THE FIRST SUBFRAME STARTS SYNCHRONOUSLY WITH THE END/START OF WEEK EPOCH.
Figure 3-16. Time Line Relationship of HOW Message
IS-GPS-200D 7 Dec 2004
42
4. NOT APPLICABLE
IS-GPS-200D 7 Dec 2004
43
(This page intentionally left blank.)
IS-GPS-200D 7 Dec 2004
44
5. NOT APPLICABLE
IS-GPS-200D 7 Dec 2004
45
(This page intentionally left blank.)
IS-GPS-200D 7 Dec 2004
46
6. NOTES 6.1 Acronyms
AI AODO A-S Autonav BPSK CDC CNAV cps CRC CS DC DN EAROM ECEF ECI EDC EOE EOL ERD FEC GGTO GNSS GPS HOW ICC ID IERS
-
Availability Indicator
-
Age of Data Offset
-
Anti-Spoofing
-
Autonomous Navigation
-
Bi-Phase Shift Key
-
Clock Differential Correction
-
Civil Navigation
-
cycles per second
-
Cyclic Redundancy Check
-
Control Segment
-
Differential Correction
-
Day Number
-
Electrically Alterable Read-Only Memory
-
Earth-Centered, Earth-Fixed
-
Earth-Centered, Inertial
-
Ephemeris Differential Correction
-
Edge-of-Earth
-
End of Life
-
Estimated Range Deviation
-
Forward Error Correction
-
GPS/GNSS Time Offset
-
Global Navigation Satellite System
-
Global Positioning System
-
Hand-Over Word
-
Interface Control Contractor
-
Identification
-
International Earth Rotation and Reference Systems Service
IS-GPS-200D 7 Dec 2004
47
IODC IODE IRM IRP IS ISC LSB LSF L2 C L2 CL L2 CM MCS MSB NAV NDUS NMCT NSC NSCL NSCM NSY OBCP OCS PRN RF RMS SA SEP sps
-
Issue of Data, Clock
-
Issue of Data, Ephemeris
-
IERS Reference Meridian
-
IERS Reference Pole
-
Interface Specification
-
Inter-Signal Correction
-
Least Significant Bit
-
Leap Seconds Future
-
L2 Civil Signal
-
L2 Civil-Long Code
-
L2 Civil-Moderate Code
-
Master Control Station
-
Most Significant Bit
-
Navigation
-
Nudet Detection User Segment
-
Navigation Message Correction Table
-
Non-Standard C/A-Code
-
Non-Standard L2 CL-Code
-
Non-Standard L2 CM-Code
-
Non-Standard Y-code
-
On-Board Computer Program
-
Operational Control System
-
Pseudo-Random Noise
-
Radio Frequency
-
Root Mean Square
-
Selective Availability
-
Spherical Error Probable
-
symbols per second
IS-GPS-200D 7 Dec 2004
48
SS SV SVN TBD TBS TLM TOW UE URA URE US USNO UTC WGS 84 WN WNe
-
Space Segment
-
Space Vehicle
-
Space Vehicle Number
-
To Be Determined
-
To Be Supplied
-
Telemetry
-
Time Of Week
-
User Equipment
-
User Range Accuracy
-
User Range Error
-
User Segment
-
U.S. Naval Observatory
-
Coordinated Universal Time
-
World Geodetic System 1984
-
Week Number
-
Extended Week Number
IS-GPS-200D 7 Dec 2004
49
(This page intentionally left blank.)
IS-GPS-200D 7 Dec 2004
50
6.2 Definitions
6.2.1 User Range Accuracy. User range accuracy (URA) is a statistical indicator of the ranging accuracies obtainable with a specific SV. URA is a one-sigma estimate of the user range errors in the navigation data for the transmitting satellite. It includes all errors for which the Space and Control Segments are responsible. It does not include any errors introduced in the user set or the transmission media. While the URA may vary over a given subframe fit interval, the URA index (N) reported in the NAV message corresponds to the maximum value of URA anticipated over the fit interval.
6.2.2 SV Block Definitions. The following block definitions are given to facilitate discussion regarding the capability of the various blocks of GPS satellites to support the SV-to-US interface.
6.2.2.1 Developmental SVs. The original concept validation satellites developed by Rockwell International and designated as satellite vehicle numbers (SVNs) 1-11 are termed "Block I" SVs. These SVs were designed to provide 3-4 days of positioning service without contact from the CS. These SVs transmitted a configuration code of 000 (reference paragraph 20.3.3.5.1.4). There are no longer any active Block I SVs in the GPS constellation. The last Block I SV was decommissioned in 1995.
6.2.2.2 Operational SVs. The operational satellites are designated Block II, Block IIA, Block IIR, Block IIR-M and Block IIF SVs. Characteristics of these SVs are provided below. Modes of operation for these SVs and accuracy of positioning services provided are described in paragraphs 6.3.2 through 6.3.4. These SVs transmit configuration codes as specified in paragraph 20.3.3.5.1.4. The navigation signal provides no direct indication of the type of the transmitting SV.
6.2.2.2.1 Block II SVs. The first block of full scale operational SVs developed by Rockwell International are designated as SVNs 13-21 and are termed "Block II" SVs. These SVs were designed to provide 14 days of positioning service without contact from the CS.
6.2.2.2.2 Block IIA SVs. The second block of full scale operational SVs developed by Rockwell International are designated as SVNs 22-40 and are termed "Block IIA" SVs. These SVs are capable of providing 60 days of positioning service without contact from the CS.
IS-GPS-200D 7 Dec 2004
51
6.2.2.2.3 Block IIR SVs. The block of operational replenishment SVs developed by Lockheed Martin are designated as SVNs 41-61 and are termed "Block IIR" SVs. These SVs have the capability of storing at least 60 days of navigation data with current memory margins, while operating in a IIA mode, to provide positioning service without contact from the CS for that period. (Contractual requirements for these SVs specify transmission of correct data for only 14 days to support short-term extended operations while in IIA mode.) The IIR SV will provide a minimum of 60 days of positioning service without contact from the CS when operating in autonomous navigation (Autonav) mode.
6.2.2.2.4 Block IIR-M SVs. The subset of operational replenishment SVs developed by Lockheed Martin which are “Modernized” configuration of “Block IIR” SVs are termed “Block IIR-M”.
6.2.2.2.5 Block IIF SVs. The block of operational replenishment SVs developed by Boeing are designated as SVNs 62-73 and are termed “Block IIF” SVs. This is the first block of operational SVs that transmit the L5 Civil signal. These SVs will provide at least 60 days of positioning service without contact from the CS.
6.2.3 Operational Interval Definitions. The following three operational intervals have been defined. These labels will be used to refer to differences in the interface definition as time progresses from SV acceptance of the last navigation data upload.
6.2.3.1 Normal Operations. The SV is undergoing normal operations whenever the fit interval flag (reference paragraph 20.3.3.4.3.1) is zero.
6.2.3.2 Short-term Extended Operations. The SV is undergoing short-term extended operations whenever the fit interval flag is one and the IODE (reference paragraph 20.3.4.4) is less than 240.
6.2.3.3 Long-term Extended Operations. The SV is undergoing long-term extended operations whenever the fit interval flag is one and the IODE is in the range 240-255.
IS-GPS-200D 7 Dec 2004
52
6.2.4 GPS Week Number. The GPS week numbering system is established with week number zero (0) being defined as that week which started with the X1 epoch occurring at midnight UTC(USNO) on the night of January 5, 1980/ morning of January 6, 1980. The GPS week number continuously increments by one (1) at each end/start of week epoch without ever resetting to zero. Users must recognize that the week number information contained in the Nav Message may not necessarily reflect the current full GPS week number (see paragraphs 20.3.3.3.1.1, 20.3.3.5.1.5, 20.3.3.5.2.4, and 30.3.3.1.1.1).
6.2.5 L5 Civil Signal. L5 is the GPS downlink signal at a nominal carrier frequency of 1176.45 MHz. The L5 signal is only available on Block IIF and subsequent blocks of SVs and the signal is specified/described in a separate and different interface control document.
6.3 Supporting Material
6.3.1 Received Signals. The guaranteed minimum user-received signal levels are defined in paragraph 3.3.1.6. As additional supporting material, Figure 6-1 illustrates an example variation in the minimum received power of the near-ground user-received L1 and L2 signals from Block II/IIA/IIR SVs as a function of SV elevation angle.
Higher received signals levels can be caused by such factors as SV attitude errors, mechanical antenna alignment errors, transmitter power output variations due to temperature variations, voltage variations and power amplifier variations, and due to a variability in link atmospheric path loss. For Block II/IIA and IIR SVs, the maximum received signal levels as a result of these factors is not expected to exceed -155.5 dBW and -153.0 dBW, respectively, for the P(Y) and C/A components of the L1 channel, nor -158.0 dBW for either signal on the L2 channel. For Block IIR-M and IIF SVs, the maximum received signal levels as a result of these factors is not expected to exceed -155.5 dBW and -153.0 dBW, respectively, for the P(Y) and C/A components of the L1 channel and L2 channel. In addition, due to programmable power output capabilities of Block IIR-M and IIF SVs, under certain operational scenarios, individual signal components of Block IIR-M/IIF SVs may exceed the previously stated maximum but are not expected to exceed -150 dBW.
IS-GPS-200D 7 Dec 2004
53
-155.5
RECEIVED POWER AT 3dBi LINEARLY POLARIZED ANTENNA (dBW)
-158.5 -161.5
C/A - L1 P - L1
-164.5
P - L2 or C/A - L2
0o 5o
20 o
40o
60o
USER ELEVATION ANGLE (DEG)
80 o
90 o
100o
Figure 6-1. User Received Minimum Signal Level Variations (Example, Block II/IIA/IIR)
IS-GPS-200D 7 Dec 2004
54
6.3.2 Extended Navigation Mode (Block II/IIA). The Block II and IIA SVs are capable of being uploaded by the CS with a minimum of 60 days of navigation data to support a 60 day positioning service. Due to memory retention limitations, the Block II SVs may not transmit correct data for the entire 60 days but are guaranteed to transmit correct data for at least 14 days to support short-term extended operations. Under normal conditions the CS will provide daily uploads to each SV, which will allow the SV to maintain normal operations as defined in paragraph 6.2.3.1 and described within this IS. During normal operations, the SVs will have a user range error that is at or below a level required to support a positioning accuracy of 16 meters spherical error probable (SEP). In addition, the almanac data, UTC parameters and ionospheric data will be maintained current to meet the accuracy specified in this IS.
If the CS is unable to upload the SVs (the CS is unavailable or the SV is unable to accept and process the upload), each SV will individually transition to short-term extended operations and eventually to long-term extended operations (based on time from each SV's last upload) as defined in paragraphs 6.2.3.2 and 6.2.3.3, and as further described throughout this IS. As time from upload continues through these three operational intervals, the user range error of the SV will increase, causing a positioning service accuracy degradation. The rate of accuracy degradation is slow over the short-term extended operations interval, such that at the end of this interval (approximately 14 days after upload) the US will be able to achieve a positioning accuracy of 425 meters SEP. The rate of accuracy degradation increases in the long-term extended interval, such that by the 180th day after the last upload, the positioning errors will have grown to 10 kilometers SEP. During these intervals the URA will continue to provide the proper estimate of the user range errors.
During short-term and long-term extended operations (approximately day 2 through day 62 after an upload), the almanac data, UTC parameters and ionospheric data will not be maintained current and will degrade in accuracy from the time of last upload.
IS-GPS-200D 7 Dec 2004
55
6.3.3 Block IIA Mode (Block IIR/IIR-M). The Block IIR/IIR-M SVs, when operating in the Block IIA mode, will perform similarly to the Block IIA SVs and have the capability of storing at least 60 days of navigation data, with current memory margins, to provide positioning service without contact from the CS for that period (through short-term and long-term extended operations). (Contractual requirements for these SVs specify transmission of correct data for only 14 days to support short-term extended operations while in IIA mode.) Under normal conditions, the CS will provide daily uploads to each SV, which will allow the SV to maintain normal operations as defined in paragraph 6.2.3.1 and described within this IS.
If the CS is unable to upload the SVs (the CS is unavailable or the SV is unable to accept and process the upload), each SV will individually transition to short-term extended operations and eventually to long-term extended operations (based on time from each SV’s last upload) as defined in paragraph 6.2.3.2 and 6.2.3.3, and as further described throughout this IS. As time from upload continues through these three operational intervals, the user range error (URE) of the SV will increase, causing a positioning service accuracy degradation.
6.3.4 Autonomous Navigation Mode. The Block IIR/IIR-M and Block IIF SV, in conjunction with a sufficient number of other Block IIR/IIR-M or Block IIF SVs, operates in an Autonav mode when commanded by the CS. Each Block IIR/IIR-M/IIF SV in the constellation determines its own ephemeris and clock correction parameters via SV-to-SV ranging, communication of data, and on-board data processing which updates data uploaded by the CS. In the Autonav mode the Block IIR/IIR-M/IIF SV will maintain normal operations as defined in paragraph 6.2.3.1 and as further described within this IS, and will have a URE of no larger than 6 meters, one sigma for Block IIR/IIRM. URE of 6 meters, one sigma, is expected to support 16 meter SEP accuracy under a nominal position dilution of precision. If the CS is unable to upload the SVs, the Block IIR/IIR-M/IIF SVs will maintain normal operations for period of at least 60 days after the last upload.
In the Autonav mode, the almanac data, UTC parameters and ionospheric data are still calculated and maintained current by the CS and uploaded to the SV as required. If the CS is unable to upload the SVs, the almanac data, UTC parameters and ionospheric data will not be maintained current and will degrade in accuracy from the time of the last upload.
IS-GPS-200D 7 Dec 2004
56
6.3.5 PRN Code sequences expansion. The additional PRN sequences provided in this section are for information only. The additional PRN sequences identified in this section are not applicable to Block II/IIA, IIR/IIR-M, IIF SVs. In addition, the current valid range for GPS PRN signal number for C/A- and P-code is 1 – 37 as specified in Table 3-I. The PRN sequences provided in this section are for other L1/L2 signal applications, such as Satellite Based Augmentation System (SBAS) satellite signals, and potential use in the future by GPS.
6.3.5.1 Additional C/A-code PRN sequences. The PRN C/A-code is described in Section 3.2.1.3 and 36 legacy C/A-code sequences are assigned by SV-ID number in Table 3-I. An additional set of 173 C/A-code PRN sequences are selected and assigned with PRN numbers in this section as shown in Table 6-I. Among the 173 additional sequences; PRN numbers 38 through 63 are reserved for future GPS SVs; PRN numbers 64 through 119 are reserved for future Ground Based Augmentation System (GBAS) and other augmentation systems; PRN numbers 120 through 158 are reserved for SBAS; and PRN numbers 159 through 210 are reserved for other Global Navigation Satellite System (GNSS) applications. For GPS application, the CNAV data, Dc(t), will be modulo-2 added to the C/A-code sequences of PRN numbers 38 through 63. Any assignment of a C/A-code PRN number and its code sequence for any additional SV and/or other L1/L2 signal applications, such as SBAS satellite signals, will be selected from the sequences of Table 6-I and will be approved, controlled, and managed by the GPS JPO.
It should be noted that, in Table 6-I, the C/A-code sequences are identified by “G2 Delay” and “Initial G2 Setting” which is not as same as the method used in Table 3-I. The two-tap coder implementation method referenced and used in Table 3-I is not used in Table 6-I due to its limitation in generating C/A-code sequences. The “G2 Delay” specified in Table 6-I may be accomplished by using the “Initial G2 Setting” as the initialization vector for the G2 shift register of Figure 3-9.
IRN-200D-001 IS-GPS-200D
7 Mar 2006 56a
6.3.5.2 Additional P-Code PRN sequences. The PRN P-code set of 37 mutually exclusive sequences are described in Section 3.2.1.1, and assignment of these code segments by SV-ID number is given in Table 3-I. An additional set of 173 P-code PRN sequences are described in this section. Among the 173 additional sequences; PRN numbers 38 through 63 are reserved for future GPS SVs; PRN numbers 64 through 119 are reserved for future GBAS and other augmentation systems; and PRN numbers 120 through 210 are reserved for other future applications. For GPS application, the CNAV data, Dc(t), which may include additional future military message types, will be modulo-2 added to the P-code sequences of PRN numbers 38 through 63. The P-code PRN numbers and their code sequences defined in Table 6-I are not for general use and will be approved, controlled, and managed by the GPS JPO.
6.3.5.2.1 Additional P-code Generation. The generation of 37 mutually exclusive P-code PRN sequences are described in Section 3.3.2.2. The additional set of 173 P-code PRN sequences are generated by circularly shifting each of the original 37 sequences (over one week) by an amount corresponding to 1, 2, 3, 4, or 5 days. The additional sequences are therefore time shifted (i.e. offset) versions of the original 37 sequences. These offset Pcode PRN sequences, Pi(t), are described as follows:
Pi(t) = Pi-37x(t – xT), where i is an integer from 38 to 210, x is an integer portion of (i-1)/37, and T is defined to equal 24 hours.
As an example, P-code sequence for PRN 38 would be the same sequence as PRN 1 shifted 24 hours into a week (i.e. 1st chip of PRN 38 at beginning of week is the same chip for PRN 1 at 24 hours after beginning of week). The complete list of the additional P-code PRN assignment is shown in Table 6-I. Any assignment of a P-code PRN number and its code sequence for any additional SV and/or other L1/L2 signal applications will be selected from the sequences of Table 6-I.
IRN-200D-001 IS-GPS-200D
7 Mar 2006 56b
Table 6-I
Additional C/A-/P-Code Phase Assignments (sheet 1 of 6)
PRN Signal No. *
G2 Delay (Chips)
C/A
Initial G2 Setting
(Octal)**
P
First 10 Chips (Octal)**
X2 Delay (Chips)
P-code Relative Delay
(Hours) ***
First 12 Chips (Octal)
38
67
39
103
40
91
41
19
42
679
43
225
44
625
45
946
46
638
47
161
48
1001
49
554
50
280
51
710
52
709
53
775
54
864
55
558
56
220
57
397
58
55
59
898
60
759
61
367
62
299
63
1018
0017 0541 1714 1151 1651 0103 0543 1506 1065 1564 1365 1541 1327 1716 1635 1002 1015 1666 0177 1353 0426 0227 0506 0336 1333 1745
1760 1236 0063 0626 0126 1674 1234 0271 0712 0213 0412 0236 0450 0061 0142 0775 0762 0111 1600 0424 1351 1550 1271 1441 0444 0032
1
P1(t-24)
2
P2(t-24)
3
P3(t-24)
4
P4(t-24)
5
P5(t-24)
6
P6(t-24)
7
P7(t-24)
8
P8(t-24)
9
P9(t-24)
10
P10(t-24)
11
P11(t-24)
12
P12(t-24)
13
P13(t-24)
14
P14(t-24)
15
P15(t-24)
16
P16(t-24)
17
P17(t-24)
18
P18(t-24)
19
P19(t-24)
20
P20(t-24)
21
P21(t-24)
22
P22(t-24)
23
P23(t-24)
24
P24(t-24)
25
P25(t-24)
26
P26(t-24)
3373 3757 3545 5440 4402 4023 4233 2337 3375 3754 3544 3440 5402 2423 5033 2637 3135 5674 4514 2064 5210 2726 5171 2656 5105 2660
* PRN sequences 38 through 63 are reserved for GPS.
** In the octal notation for the first 10 chips of the C/A-code or the initial settings as shown in this table, the first digit (1/0) represents a "1" or “0”, respectively, for the first chip and the last three digits are the conventional octal representation of the remaining 9 chips. (For example, the first 10 chips of the C/A code for PRN Signal Assembly No. 38 are: 1111110000).
*** Pi(t-N): P-code sequence of PRN number i shifted by N hours. See Section 6.3.5.2.1.
IRN-200D-001 IS-GPS-200D
7 Mar 2006 56c
Table 6-I
Additional C/A-/P-Code Phase Assignments (sheet 2 of 6)
PRN Signal
No.
G2 Delay (Chips)
C/A
Initial G2 Setting
(Octal)**
P
First 10 Chips (Octal)**
X2 Delay (Chips)
P-code Relative Delay
(Hours) ***
First 12 Chips (Octal)
64
729
0254
65
695
1602
66
780
1160
67
801
1114
68
788
1342
69
732
0025
70
34
1523
71
320
1046
72
327
0404
73
389
1445
74
407
1054
75
525
0072
76
405
0262
77
221
0077
78
761
0521
79
260
1400
80
326
1010
81
955
1441
82
653
0365
83
699
0270
84
422
0263
85
188
0613
86
438
0277
87
959
1562
88
539
1674
89
879
1113
90
677
1245
91
586
0606
92
153
0136
93
792
0256
94
814
1550
95
446
1234
1523 0175 0617 0663 0435 1752 0254 0731 1373 0332 0723 1705 1515 1700 1256 0377 0767 0336 1412 1507 1514 1164 1500 0215 0103 0664 0532 1171 1641 1521 0227 0543
27
P27(t-24)
28
P28(t-24)
29
P29(t-24)
30
P30(t-24)
31
P31(t-24)
32
P32(t-24)
33
P33(t-24)
34
P34(t-24)
35
P35(t-24)
36
P36(t-24)
37
P37(t-24)
1
P1(t-48)
2
P2(t-48)
3
P3(t-48)
4
P4(t-48)
5
P5(t-48)
6
P6(t-48)
7
P7(t-48)
8
P8(t-48)
9
P9(t-48)
10
P10(t-48)
11
P11(t-48)
12
P12(t-48)
13
P13(t-48)
14
P14(t-48)
15
P15(t-48)
16
P16(t-48)
17
P17(t-48)
18
P18(t-48)
19
P19(t-48)
20
P20(t-48)
21
P21(t-48)
5112 4667 2111 5266 4711 4166 2251 5306 4761 2152 5247 5736 2575 3054 3604 3520 5472 4417 2025 3230 5736 4575 2054 3204 3720 5572 4457 4005 2220 3332 3777 3555
** In the octal notation for the first 10 chips of the C/A-code or the initial settings as shown in this table, the first digit (1/0) represents a "1" or “0”, respectively, for the first chip and the last three digits are the conventional octal representation of the remaining 9 chips. (For example, the first 10 chips of the C/A code for PRN Signal Assembly No. 38 are: 1111110000)
*** Pi(t-N): P-code sequence of PRN number i shifted by N hours. See Section 6.3.5.2.1.
IRN-200D-001 IS-GPS-200D
7 Mar 2006 56d
Table 6-I
Additional C/A-/P-Code Phase Assignments (sheet 3 of 6)
PRN Signal
No.
G2 Delay (Chips)
C/A
Initial G2 Setting
(Octal)**
P
First 10 Chips (Octal)**
X2 Delay (Chips)
P-code Relative Delay
(Hours) ***
First 12 Chips (Octal)
96
264
97
1015
98
278
99
536
100
819
101
156
102
957
103
159
104
712
105
885
106
461
107
248
108
713
109
126
110
807
111
279
112
122
113
197
114
693
115
632
116
771
117
467
118
647
119
203
120
145
121
175
122
52
123
21
124
237
125
235
0260 1455 1535 0746 1033 1213 0710 0721 1763 1751 0435 0735 0771 0140 0111 0656 1016 0462 1011 0552 0045 1104 0557 0364 1106 1241 0267 0232 1617 1076
1517 0322 0242 1031 0744 0564 1067 1056 0014 0026 1342 1042 1006 1637 1666 1121 0761 1315 0766 1225 1732 0673 1220 1413 0671 0536 1510 1545 0160 0701
22
P22(t-48)
23
P23(t-48)
24
P24(t-48)
25
P25(t-48)
26
P26(t-48)
27
P27(t-48)
28
P28(t-48)
29
P29(t-48)
30
P30(t-48)
31
P31(t-48)
32
P32(t-48)
33
P33(t-48)
34
P34(t-48)
35
P35(t-48)
36
P36(t-48)
37
P37(t-48)
1
P1(t-72)
2
P2(t-72)
3
P3(t-72)
4
P4(t-72)
5
P5(t-72)
6
P6(t-72)
7
P7(t-72)
8
P8(t-72)
9
P9(t-72)
10
P10(t-72)
11
P11(t-72)
12
P12(t-72)
13
P13(t-72)
14
P14(t-72)
3444 3400 5422 2433 3037 5635 2534 5074 4614 2124 5270 2716 5165 4650 2106 5261 2752 5147 4641 2102 5263 2713 3167 3651 3506 5461 4412 2027 5231 2736
** In the octal notation for the first 10 chips of the C/A-code or the initial settings as shown in this table, the first digit (1/0) represents a "1" or “0”, respectively, for the first chip and the last three digits are the conventional octal representation of the remaining 9 chips. (For example, the first 10 chips of the C/A code for PRN Signal Assembly No. 38 are: 1111110000)
*** Pi(t-N): P-code sequence of PRN number i shifted by N hours. See Section 6.3.5.2.1.
IRN-200D-001 IS-GPS-200D
7 Mar 2006 56e
Table 6-I
Additional C/A-/P-Code Phase Assignments (sheet 4 of 6)
PRN Signal
No.
G2 Delay (Chips)
C/A
Initial G2 Setting
(Octal)**
P
First 10 Chips (Octal)**
X2 Delay (Chips)
P-code Relative Delay
(Hours) ***
First 12 Chips (Octal)
126
886
127
657
128
634
129
762
130
355
131
1012
132
176
133
603
134
130
135
359
136
595
137
68
138
386
139
797
140
456
141
499
142
883
143
307
144
127
145
211
146
121
147
118
148
163
149
628
150
853
151
484
152
289
153
811
154
202
155
1021
1764 0717 1532 1250 0341 0551 0520 1731 0706 1216 0740 1007 0450 0305 1653 1411 1644 1312 1060 1560 0035 0355 0335 1254 1041 0142 1641 1504 0751 1774
0013 1060 0245 0527 1436 1226 1257 0046 1071 0561 1037 0770 1327 1472 0124 0366 0133 0465 0717 0217 1742 1422 1442 0523 0736 1635 0136 0273 1026 0003
15
P15(t-72)
16
P16(t-72)
17
P17(t-72)
18
P18(t-72)
19
P19(t-72)
20
P20(t-72)
21
P21(t-72)
22
P22(t-72)
23
P23(t-72)
24
P24(t-72)
25
P25(t-72)
26
P26(t-72)
27
P27(t-72)
28
P28(t-72)
29
P29(t-72)
30
P30(t-72)
31
P31(t-72)
32
P32(t-72)
33
P33(t-72)
34
P34(t-72)
35
P35(t-72)
36
P36(t-72)
37
P37(t-72)
1
P1(t-96)
2
P2(t-96)
3
P3(t-96)
4
P4(t-96)
5
P5(t-96)
6
P6(t-96)
7
P7(t-96)
3175 5654 2504 5060 2612 3127 5671 4516 4065 4210 4326 4371 2356 5345 4740 2142 5243 2703 5163 4653 4107 4261 4312 2525 3070 5616 2525 3070 3616 3525
** In the octal notation for the first 10 chips of the C/A-code or the initial settings as shown in this table, the first digit (1/0) represents a "1" or “0”, respectively, for the first chip and the last three digits are the conventional octal representation of the remaining 9 chips. (For example, the first 10 chips of the C/A code for PRN Signal Assembly No. 38 are: 1111110000)
*** Pi(t-N): P-code sequence of PRN number i shifted by N hours. See Section 6.3.5.2.1.
IRN-200D-001 IS-GPS-200D
7 Mar 2006 56f
Table 6-I
Additional C/A-/P-Code Phase Assignments (sheet 5 of 6)
PRN Signal
No.
G2 Delay (Chips)
C/A
Initial G2 Setting
(Octal)**
P
First 10 Chips (Octal)**
X2 Delay (Chips)
P-code Relative Delay
(Hours) ***
First 12 Chips (Octal)
156
463
157
568
158
904
159
670
160
230
161
911
162
684
163
309
164
644
165
932
166
12
167
314
168
891
169
212
170
185
171
675
172
503
173
150
174
395
175
345
176
846
177
798
178
992
179
357
180
995
181
877
182
112
183
144
184
476
185
193
0107 1153 1542 1223 1702 0436 1735 1662 1570 1573 0201 0635 1737 1670 0134 1224 1460 1362 1654 0510 0242 1142 1017 1070 0501 0455 1566 0215 1003 1454
1670 0624 0235 0554 0075 1341 0042 0115 0207 0204 1576 1142 0040 0107 1643 0553 0317 0415 0123 1267 1535 0635 0760 0707 1276 1322 0211 1562 0774 0323
8
P8(t-96)
9
P9(t-96)
10
P10(t-96)
11
P11(t-96)
12
P12(t-96)
13
P13(t-96)
14
P14(t-96)
15
P15(t-96)
16
P16(t-96)
17
P17(t-96)
18
P18(t-96)
19
P19(t-96)
20
P20(t-96)
21
P21(t-96)
22
P22(t-96)
23
P23(t-96)
24
P24(t-96)
25
P25(t-96)
26
P26(t-96)
27
P27(t-96)
28
P28(t-96)
29
P29(t-96)
30
P30(t-96)
31
P31(t-96)
32
P32(t-96)
33
P33(t-96)
34
P34(t-96)
35
P35(t-96)
36
P36(t-96)
37
P37(t-96)
5470 4416 4025 4230 4336 2375 5354 2744 5140 4642 4103 2263 5313 2767 5151 2646 3101 5662 4513 2067 3211 3726 3571 3456 3405 3420 5432 4437 2035 5234
** In the octal notation for the first 10 chips of the C/A-code or the initial settings as shown in this table, the first digit (1/0) represents a "1" or “0”, respectively, for the first chip and the last three digits are the conventional octal representation of the remaining 9 chips. (For example, the first 10 chips of the C/A code for PRN Signal Assembly No. 38 are: 1111110000)
*** Pi(t-N): P-code sequence of PRN number i shifted by N hours. See Section 6.3.5.2.1.
IRN-200D-001 IS-GPS-200D
7 Mar 2006 56g
Table 6-I
Additional C/A-/P-Code Phase Assignments (sheet 6 of 6)
PRN Signal
No.
G2 Delay (Chips)
C/A
Initial G2 Setting
(Octal)**
P
First 10 Chips (Octal)**
X2 Delay (Chips)
P-code Relative Delay
(Hours) ***
First 12 Chips (Octal)
186
109
187
445
188
291
189
87
190
399
191
292
192
901
193
339
194
208
195
711
196
189
197
263
198
537
199
663
200
942
201
173
202
900
203
30
204
500
205
935
206
556
207
373
208
85
209
652
210
310
1665 0471 1750 0307 0272 0764 1422 1050 1607 1747 1305 0540 1363 0727 0147 1206 1045 0476 0604 1757 1330 0663 1436 0753 0731
0112 1306 0027 1470 1505 1013 0355 0727 0170 0030 0472 1237 0414 1050 1630 0571 0732 1301 1173 0020 0447 1114 0341 1024 1046
1
P1(t-120)
2
P2(t-120)
3
P3(t-120)
4
P4(t-120)
5
P5(t-120)
6
P6(t-120)
7
P7(t-120)
8
P8(t-120)
9
P9(t-120)
10
P10(t-120)
11
P11(t-120)
12
P12(t-120)
13
P13(t-120)
14
P14(t-120)
15
P15(t-120)
16
P16(t-120)
17
P17(t-120)
18
P18(t-120)
19
P19(t-120)
20
P20(t-120)
21
P21(t-120)
22
P22(t-120)
23
P23(t-120)
24
P24(t-120)
25
P25(t-120)
5067 2611 5126 4671 4116 2265 5310 2766 5151 2646 3101 3662 5513 4467 4011 4226 4331 4376 2355 5344 4740 2142 5243 2703 5163
** In the octal notation for the first 10 chips of the C/A-code or the initial settings as shown in this table, the first digit (1/0) represents a "1" or “0”, respectively, for the first chip and the last three digits are the conventional octal representation of the remaining 9 chips. (For example, the first 10 chips of the C/A code for PRN Signal Assembly No. 38 are: 1111110000)
*** Pi(t-N): P-code sequence of PRN number i shifted by N hours. See Section 6.3.5.2.1.
IRN-200D-001 IS-GPS-200D
7 Mar 2006 56h
6.3.5.3 Additional L2 CM-/L2 CL-Code PRN sequences. The PRN L2 CM-code and L2 CL-code are described in Sections 3.2.1.4 and 3.2.1.5, respectively, and 37 L2 CM-/L2 CL-code sequence pairs are assigned by SV-ID number in Table 3-II. An additional set of 80 L2 CM-/L2 CL-code PRN sequence pairs are selected and assigned with PRN numbers in this section as shown in Table 6-II. Among the 80 additional sequences, PRN numbers 38 through 63 are reserved for future GPS SVs, and PRN numbers 159 through 210 are reserved for other GNSS applications. PRN allocations do not exist for numbers 64 through 158 for L2 CM-/L2 CL-code. Any assignment of a L2 CM-/L2 CL-code PRN number and its code sequence pair for any additional SV and/or other L2 signal applications will be selected from the sequences of Table 6-II and will be approved, controlled, and managed by the GPS JPO.
Table 6-II. Additional L2 CM-/L2 CL-Code Phase Assignments (sheet 1 of 3)
PRN Signal No. ***
Initial Shift Register State (Octal)
L2 CM
L2 CL
End Shift Register State (Octal)
L2 CM *
L2 CL **
38
771353753
39
226107701
40
022025110
41
402466344
42
752566114
43
702011164
44
041216771
45
047457275
46
266333164
47
713167356
48
060546335
49
355173035
50
617201036
51
157465571
52
767360553
53
023127030
54
431343777
55
747317317
56
045706125
57
002744276
58
060036467
59
217744147
60
603340174
61
326616775
62
063240065
63
111460621
101232630 132525726 315216367 377046065 655351360 435776513 744242321 024346717 562646415 731455342 723352536 000013134 011566642 475432222 463506741 617127534 026050332 733774235 751477772 417631550 052247456 560404163 417751005 004302173 715005045 001154457
* Short cycled period = 10230 ** Short cycled period = 767250 *** PRN sequences 38 through 63 are reserved for GPS.
453413162 637760505 612775765 136315217 264252240 113027466 774524245 161633757 603442167 213146546 721323277 207073253 130632332 606370621 330610170 744312067 154235152 525024652 535207413 655375733 316666241 525453337 114323414 755234667 526032633 602375063
463624741 673421367 703006075 746566507 444022714 136645570 645752300 656113341 015705106 002757466 100273370 304463615 054341657 333276704 750231416 541445326 316216573 007360406 112114774 042303316 353150521 044511154 244410144 562324657 027501534 521240373
IRN-200D-001 IS-GPS-200D
7 Mar 2006 56i
Table 6-II. Additional L2 CM-/L2 CL-Code Phase Assignments (sheet 2 of 3)
PRN Signal
No.
Initial Shift Register State (Octal)
L2 CM
L2 CL
End Shift Register State (Octal)
L2 CM *
L2 CL **
159
604055104
160
157065232
161
013305707
162
603552017
163
230461355
164
603653437
165
652346475
166
743107103
167
401521277
168
167335110
169
014013575
170
362051132
171
617753265
172
216363634
173
755561123
174
365304033
175
625025543
176
054420334
177
415473671
178
662364360
179
373446602
180
417564100
181
000526452
182
226631300
183
113752074
184
706134401
185
041352546
186
664630154
187
276524255
188
714720530
189
714051771
190
044526647
* Short cycled period = 10230 ** Short cycled period = 767250
605253024 063314262 066073422 737276117 737243704 067557532 227354537 704765502 044746712 720535263 733541364 270060042 737176640 133776704 005645427 704321074 137740372 056375464 704374004 216320123 011322115 761050112 725304036 721320336 443462103 510466244 745522652 373417061 225526762 047614504 034730440 453073141
425373114 427153064 310366577 623710414 252761705 050174703 050301454 416652040 050301251 744136527 633772375 007131446 142007172 655543571 031272346 203260313 226613112 736560607 011741374 765056120 262725266 013051476 144541215 534125243 250001521 276000566 447447071 000202044 751430577 136741270 257252440 757666513
044547544 707116115 412264037 223755032 403114174 671505575 606261015 223023120 370035547 516101304 044115766 704125517 406332330 506446631 743702511 022623276 704221045 372577721 105175230 760701311 737141001 227627616 245154134 040015760 002154472 301767766 226475246 733673015 602507667 753362551 746265601 036253206
IRN-200D-001 IS-GPS-200D
7 Mar 2006 56j
Table 6-II. Additional L2 CM-/L2 CL-Code Phase Assignments (sheet 3 of 3)
PRN Signal
No.
Initial Shift Register State (Octal)
L2 CM
L2 CL
End Shift Register State (Octal)
L2 CM *
L2 CL **
191
207164322
192
262120161
193
204244652
194
202133131
195
714351204
196
657127260
197
130567507
198
670517677
199
607275514
200
045413633
201
212645405
202
613700455
203
706202440
204
705056276
205
020373522
206
746013617
207
132720621
208
434015513
209
566721727
210
140633660
* Short cycled period = 10230 ** Short cycled period = 767250
533654510 377016461 235525312 507056307 221720061 520470122 603764120 145604016 051237167 033326347 534627074 645230164 000171400 022715417 135471311 137422057 714426456 640724672 501254540 513322453
606512137 734247645 415505547 705146647 006215430 371216176 645502771 455175106 127161032 470332401 252026355 113771472 754447142 627405712 325721745 056714616 706035241 173076740 145721746 465052527
202512772 701234023 722043377 240751052 375674043 166677056 123055362 707017665 437503241 275605155 376333266 467523556 144132537 451024205 722446427 412376261 441570172 063217710 110320656 113765506
IRN-200D-001 IS-GPS-200D
7 Mar 2006 56k
(This page intentionally left blank.)
IRN-200D-001 IS-GPS-200D
7 Mar 2006 56l
10. APPENDIX I. LETTERS OF EXCEPTION 10.1 Scope. Approval of this document, as well as approval of any subsequent changes to the document, can be contingent upon a "letter of exception". This appendix depicts such "letters of exception" when authorized by the GPS JPO. 10.2 Applicable Documents. The documents listed in Section 2.0 shall be applicable to this appendix. 10.3 Letters of Exception. Any letter of exception which is in force for the revision of the IS is depicted in Figure 10-1.
IS-GPS-200D 7 Dec 2004
57
(This page intentionally left blank.)
IS-GPS-200D 7 Dec 2004
58
Lockheed Martin Space Systems Company Space & Strategic Missiles Valley Forge Operations P.O. Box 8555 Philadelphia, PA 19101
26 May 2003 GPS IIR-CM-MOD-147
SMC/CZK 2420 VELA WAY, SUITE 1467 LOS ANGELES AFB CA 90245-4659
Attention:
Mr. David Smith
Subject:
GPS Block IIR Modernization Contract F04701-00-C-0006 Review and approval of ICD-GPS-PIRN-200C-007B, dated 08 November 2003, post 9 April 2003 CCB (L2C = -160).
Reference:
1) PCOL# 03-012, dated 22 May 03; F04701-00-C-0006; REQUEST FOR IMPACTS DUE TO IMPLEMENTING PROPOSED CHANGES TO PIRN-200C-007 REVISION B
Dear Mr. Smith:
Lockheed Martin Space Systems Company has been asked to review and comment on changes made to ICD-GPS-PIRN-200C-007B at the JPO CCB boarded on or about 09 April 2003. It is our understanding that the ONLY change made to the 08 November 2002 of the subject ICD is L2C for IIR-M SVs changed from –161.4 dBW to –160.0 dBW.
Based on that change, Lockheed Martin takes exception to IIR-M L2 C signal power specified in Table 3III. Per Lockheed Martin contract requirements as specified in SS-SS-500, Rev. A, dated 14 May 2001, LMSSC calculates links using:
• 0-dBi circularly polarized user receiving antenna (located) near ground when the SV is above a 5° elevation angle
• Atmospheric loss of 0.5 dB at edge of earth • Assumes SV antenna gains are averaged about azimuth
Using the assumptions as specified in paragraph 3.3.1.6 of PIRN-200C-007B, the GPS IIRM SVs provide a minimum receive signal of -161.4 dBW for L2 C signal. Lockheed Martin therefore takes exception to 160 dBW for L2C of PIRN-200c-007B. Formal request for cost and schedule impacts should come through the JPO Contracting Officer.
To change from -161.4 dBW to -160.0 dBW would have to be analyzed and coordinated between Lockheed Martin and ITT. If such a change were technically possible, there would be impacts to L-Band level testing, SV level testing, test scripts, Specs, OOH, and various ICDs. These impacts would be in both cost and schedule.
Figure 10-1. Letters of Exception. 59
IS-GPS-200D 7 Dec 2004
GPS IIR-CM-MOD-147 Page 2
Currently, there is an ongoing effort between Lockheed Martin, Boeing, Arinc, Aerospace, and the JPO concerning signal flexibility under the ConOps study. Lockheed Martin recommends, based on the outcome and direction of this effort, that an impact to the ICD-200 change be included in the resulting request for ROMs for Flex Power implementation.
Note that if Lockheed Martin has taken earlier exception to a change in any requirements in a previous revision of this document, Lockheed Martin continues to take exception to that change. A letter explicitly stating that the exception is no longer valid will accomplish the retraction of an exception.
Should you have any questions, please contact Martin O’Connor at (610) 354-7866 for technical concerns, or the undersigned at (610) 354-7989 for contractual matters.
Very truly yours,
LOCKHEED MARTIN CORPORATION
Signature on file
Brent B. Achee II GPS Block IIR Deputy Program Director
xc:
Capt. K. Eggehorn
Mary Guyes
Soon Yi, ARINC
J. Windfelder, DCMC
Figure 10-1. Letters of Exception (continued). 60
IS-GPS-200D 7 Dec 2004
Lockheed Martin Space Systems Company Space & Strategic Missiles Valley Forge Operations P.O. Box 8555 Philadelphia, PA 19101
27 September 2004 GPS IIR-CM-3023, Rev A
ARINC 2250 E. Imperial Highway, Suite 450 El Segundo, CA 90245-3546
Attention:
Mr. Soon K. Yi
Subject:
Review of IS-GPS-200 Rev D
Reference:
1) Contract F04701-89-C-0073 2) IS-GPS-200D, dated 09 July 2004
Dear Mr. Yi:
Lockheed Martin Space Systems Company has reviewed the subject version of IS-GPS-200D, dated 09 July 2004. It is Lockheed Martin’s understanding that the JPO and ARINC are in the process of incorporating major changes to ICD-200C, eliminating multiple Letters of Exception, and change the Interface Control Document to an Interface Specification (IS). With this in mind, Lockheed Martin is rescinding all previous letters of exception:
1. GPS IIR-CM-1046, dated 17 August 1994 2. GPS IIR-CM-MOD-0097, dated 08 May 2002 3. GPS IIR-CM-2837, dated 26 May 2003 4. GPS IIR-CM-MOD-0177, dated 16 March 2004
Lockheed Martin would like to establish this correspondence for the review of IS-GPS-200 as the baseline letter of exception. Lockheed Martin is taking exception to:
1. L2CNAV 2. IIR-M L2C Signal Power, as defined in Table 3-V The original Letter of Exception, dated 09 September 2004 listed IODC as an exception. Lockheed Martin has been able to verify this exception no longer exists. This revision to the LOE should therefore be used in it’s place. Specific reasoning for these exceptions are documented in the attached table.
Lockheed Martin is also submitting technical comments identified herein. If this document is approved at JPO CCB, LMSSC will expect a letter from JPO requesting cost and schedule impacts to implement these out-of-scope requirements on the IIR and IIR-M contracts.
Per discussions with ARINC, telecons with the JPO, and the IS-200D review directions, it is Lockheed Martin’s understanding that the once this document is Configuration Controlled by the JPO, ICD-200 will be removed from Lockheed Martin’s contract with the government and replace with IS-200. The approved IS-200 will contain this LOE and Lockheed Martin will be notified in writing as to changes that occurred as part of the CCB process for concurrence to said changes
Figure 10-1. Letters of Exception (continued).
IS-GPS-200D 7 Dec 2004
61
Should you have any questions, please contact Marty O’Connor at (610) 354-7866 for technical concerns, or the undersigned at (610) 354-2569 for contractual matters.
Very truly yours,
LOCKHEED MARTIN CORPORATION
Signature on file
Paul E. Ruffo, CPCM Manager of Contracts GPS Block IIR, IIR-M, III
xc:
Mary Guyes
A. Trader
J. Windfelder, DCMA
Capt. Brian Knight
Figure 10-1. Letters of Exception (continued). 62
IS-GPS-200D 7 Dec 2004
Figure 10-1. Letters of Exception (continued). 63
IS-GPS-200D 7 Dec 2004
Figure 10-1. Letters of Exception (continued). 64
IS-GPS-200D 7 Dec 2004
20. APPENDIX II. GPS NAVIGATION DATA STRUCTURE FOR DATA, D(t)
20.1 Scope. This appendix describes the specific GPS navigation (NAV) data structure denoted as D(t). When transmitted as part of the NAV data, D(t), the specific data structure of D(t) shall be denoted by data ID number 2, represented by the two-bit binary notation as 01.
20.2 Applicable Documents.
20.2.1 Government Documents. In addition to the documents listed in paragraph 2.1, the following documents of the issue specified contribute to the definition of the NAV data related interfaces and form a part of this Appendix to the extent specified herein.
Specifications None
Standards None
Other Publications None
20.2.2 Non-Government Documents. In addition to the documents listed in paragraph 2.2, the following documents of the issue specified contribute to the definition of the NAV data related interfaces and form a part of this Appendix to the extent specified herein.
Specifications None
Other Publications None
IS-GPS-200D 7 Dec 2004
65
(This page intentionally left blank.)
IS-GPS-200D 7 Dec 2004
66
20.3 Requirements
20.3.1 Data Characteristics. The data stream shall be transmitted by the SV on the L1 and L2 channels at a rate of 50 bps. In addition, upon ground command, the data stream shall be transmitted by the Block IIR-M SV on the L2 CM channel at a rate of 25 bps using FEC encoding resulting in 50 sps.
20.3.2 Message Structure. As shown in Figure 20-1, the message structure shall utilize a basic format of a 1500 bit long frame made up of five subframes, each subframe being 300 bits long. Subframes 4 and 5 shall be subcommutated 25 times each, so that a complete data message shall require the transmission of 25 full frames. The 25 versions of subframes 4 and 5 shall be referred to herein as pages 1 through 25 of each subframe. Each subframe shall consist of ten words, each 30 bits long; the MSB of all words shall be transmitted first.
Each subframe and/or page of a subframe shall contain a telemetry (TLM) word and a handover word (HOW), both generated by the SV, and shall start with the TLM/HOW pair. The TLM word shall be transmitted first, immediately followed by the HOW. The latter shall be followed by eight data words. Each word in each frame shall contain parity (reference Section 20.3.5).
Block II and IIA SVs are designed with sufficient memory capacity for storing at least 60 days of uploaded NAV data. However, the memory retention of these SVs will determine the duration of data transmission. Block IIR SVs have the capability, with current memory margin, to store at least 60 days of uploaded NAV data in the Block IIA mode and to store at least 60 days of CS data needed to generate NAV data on-board in the Autonav mode. Alternating ones and zeros will be transmitted in words 3 through 10 in place of the normal NAV data whenever the SV cannot locate the requisite valid control or data element in its on-board computer memory. The following specifics apply to this default action: (a) the parity of the affected words will be invalid, (b) the two trailing bits of word 10 will be zeros (to allow the parity of subsequent subframes to be valid -- reference paragraph 20.3.5), (c) if the problem is the lack of a data element, only the directly related subframe(s) will be treated in this manner, (d) if a control element cannot be located, this default action will be applied to all subframes and all subframes will indicate ID = 1 (Block II/IIA only) (i.e., an ID-code of 001) in the HOW (reference paragraph 20.3.3.2) (Block IIR/IIR-M and IIF SVs indicate the proper subframe ID for all subframes). Certain failures of control elements which may occur in the SV memory or during an upload will cause the SV to transmit in non-standard codes (NSC and NSY) which would preclude normal use by the US. Normal NAV data transmission will be resumed by the SV whenever a valid set of elements becomes available.
IS-GPS-200D 7 Dec 2004
67
Block II/IIA SVs are uploaded with a minimum of 60 days of NAV data. However, the EAROM retentivity for Block II SVs is designed and guaranteed for only 14 days. Therefore, Block II SV memory is most likely to fail sometime during long-term extended operations after repeated write operations. In the case of memory failure, the SV will transmit alternating ones and zeros in word 3-10 as specified in the above paragraph. The EAROM retentivity for Block IIA SVs is designed and guaranteed for at least 60 days. The memory retentivity for the Block IIR/IIR-M/IIF SVs is designed and guaranteed for at least 60 days. Although the data content of the SVs will be temporarily reduced during the upload process, the transmission of valid NAV data will be continuous. The data capacity of specific operational SVs may be reduced to accommodate partial memory failures.
IS-GPS-200D 7 Dec 2004
68
SUBFRAME PAGE
NO.
NO.
1
WORD 1
DIRECTION OF DATA FLOW FROM SV
150 BITS
3 SECONDS
WORD 2
WORD 3
WORD 4
71
31
61
73 77 83 91
MSB FIRST WORD 5
121
TLM
HOW
WN
1
N/A
22 BITS
CP
22 BITS
tP
10
BITS
P
23 BITS*** P 24 BITS***
P
C/A OR P ON L2 - 2 BITS URA INDEX - 4 BITS SV HEALTH - 6 BITS
2 MSBs
L2 P DATA FLAG - 1 BIT IODC - 10 BITS TOTAL
WORD 6
DIRECTION OF DATA FLOW FROM SV
150 BITS
3 SECONDS
WORD 7
WORD 8
WORD 9
MSB FIRST WORD 10
151
181
197
211 219
241
271
TGD
toc
af2
af1
af0
1
N/A
24 BITS***
P
16
P
P8
P
t P
BITS*** 8 BITS
16 BITS
BITS 16 BITS
22 BITS
8 LSBs
IODC - 10 BITS TOTAL
*** RESERVED P = 6 PARITY BITS t = 2 NONINFORMATION BEARING BITS USED FOR PARITY COMPUTATION (SEE PARAGRAPH 20.3.5) C = TLM BITS 23 AND 24 WHICH ARE RESERVED
Figure 20-1. Data Format (sheet 1 of 11)
IS-GPS-200D 7 Dec 2004
69
SUBFRAME PAGE
NO.
NO.
1
WORD 1
DIRECTION OF DATA FLOW FROM SV
150 BITS
3 SECONDS
WORD 2
WORD 3
WORD 4
31
61 69
91
107
MSB FIRST WORD 5
121
TLM
HOW
IODE
Crs
∆n
2
N/A
CP
tP 8
P
8P
24 BITS
P
22 BITS
22 BITS
BITS 16 BITS
16 BITS BITS
M0 - 32 BITS TOTAL
MSBs
LSBs
WORD 6
DIRECTION OF DATA FLOW FROM SV
150 BITS
3 SECONDS
WORD 7
WORD 8
WORD 9
MSB FIRST WORD 10
151
167
181
211
227
241
271
287
CUC
CUS
toe
2
N/A
8P
24 BITS
P
8P
24 BITS
P
tP
16 BITS BITS
16 BITS BITS
16 BITS
e - 32 BITS TOTAL
MSBs
LSBs
MSBs
A - 32 BITS TOTAL
LSBs
FIT INTERVAL FLAG - 1 BIT AODO - 5 BITS
P = 6 PARITY BITS t = 2 NONINFORMATION BEARING BITS USED FOR PARITY COMPUTATION (SEE PARAGRAPH 20.3.5) C = TLM BITS 23 AND 24 WHICH ARE RESERVED
Figure 20-1. Data Format (sheet 2 of 11)
IS-GPS-200D 7 Dec 2004
70
SUBFRAME NO.
3
PAGE NO.
N/A
WORD 1
DIRECTION OF DATA FLOW FROM SV
150 BITS
3 SECONDS
WORD 2
WORD 3
WORD 4
1 TLM
22 BITS
31
CP
HOW 22 BITS
61
77
91
tP
Cic 16 BITS
8P BITS
24 BITS
MSB FIRST
WORD 5
121
137
Cis P
8P
16 BITS BITS
Ω0 - 32 BITS TOTAL
MSBs
LSBs i0 - 32 BITS TOTAL
WORD 6
DIRECTION OF DATA FLOW FROM SV
150 BITS
3 SECONDS
WORD 7
WORD 8
WORD 9
MSB FIRST WORD 10
151
181
211
241
271 279
•
3
N/A
24 BITS
Crc P
8P
24 BITS
P
Ω
IODE IDOT
P8
14 t P
16 BITS BITS
24 BITS
BITS BITS
LSBs
MSBs i0 - 32 BITS TOTAL
LSBs
ω - 32 BITS TOTAL
P = 6 PARITY BITS t = 2 NONINFORMATION BEARING BITS USED FOR PARITY COMPUTATION (SEE PARAGRAPH 20.3.5) C = TLM BITS 23 AND 24 WHICH ARE RESERVED
Figure 20-1. Data Format (sheet 3 of 11)
IS-GPS-200D 7 Dec 2004
71
SUBFRAME NO.
PAGE NO.
1
5
THRU
24
WORD 1
DIRECTION OF DATA FLOW FROM SV
150 BITS
3 SECONDS
WORD 2
WORD 3
WORD 4
MSB FIRST WORD 5
1 TLM
22 BITS
31
CP
HOW 22 BITS
61 63 69
tP
e 16 BITS
91 99
toa P8
BITS
δi 16 BITS
121
•
Ω
P 16 BITS
8P BITS
DATA ID - 2 BITS SV ID - 6 BITS
SV HEALTH
WORD 6
DIRECTION OF DATA FLOW FROM SV
150 BITS
3 SECONDS
WORD 7
WORD 8
WORD 9
MSB FIRST WORD 10
151
181
211
241
271 279 290
1
A
Ω0
ω
M0
5
THRU
24
P
P
P
P
24 BITS
24 BITS
24 BITS
24 BITS
tP
af0 - 11 BITS TOTAL af1 - 11 BITS TOTAL
8 MSBs
3 LSBs
P = 6 PARITY BITS t = 2 NONINFORMATION BEARING BITS USED FOR PARITY COMPUTATION (SEE PARAGRAPH 20.3.5) C = TLM BITS 23 AND 24 WHICH ARE RESERVED NOTE: PAGES 2, 3, 4, 5, 7, 8, 9 & 10 OF SUBFRAME 4 HAVE THE SAME FORMAT AS PAGES 1 THROUGH 24 OF SUBFRAME 5
Figure 20-1. Data Format (sheet 4 of 11)
IS-GPS-200D 7 Dec 2004
72