IS-GPS-800A - US Coast Guard Navigation Center
IS-GPS-800A - US Coast Guard Navigation Center IS-GPS-800A - US Coast Guard Navigation Center
Table 3.5-7.Midi Almanac ParametersParameterNo. ofBits**ScaleFactor(LSB)EffectiveRange***Unitst oae i ****AΩ 0M 0a f0a f181111*11*1716*16*16*11*10*2 122 -162 -142 -332 -42 -152 -152 -152 -20602,112 secondsdimensionlesssemi-circlessemi-circles/secmeterssemi-circlessemi-circlessemi-circlessecondssec/sec* Parameters so indicated shall be in two's complement notation;** See Figure 3.5-5 for complete bit allocation in subframe 3, page 4;*** Unless otherwise indicated in this column, effective range is the maximum range attainable withindicated bit allocation and scale factor;**** Relative to i 0 = 0.30 semi-circles.3.5.4.4 Subframe 3, Page 5 – Differential CorrectionSubframe 3, page 5, Figure 3.5-6, contains the Differential Correction (DC) parameters. These parameters provideusers with sets of correction terms that apply to the clock and ephemeris data transmitted by other SVs. DCparameters are grouped in packets, as described in this section. The availability of this data is subject to the controland determination of the CS. The contents of subframe 3, page 5, are defined below, and followed by materialpertinent to the use of the data.3.5.4.4.1 Differential Correction Parameter ContentSubframe 3, page 5 shall contain DC parameters that apply to the clock and ephemeris data transmitted by anotherSV. One subframe 3, page 5, as depicted in Figure 3.5-6, shall contain 34 bits of clock differential correction (CDC)parameters and 92 bits of ephemeris differential correction (EDC) parameters for one SV other than the transmitting60 IS-GPS-800A8 June 2010
SV. Bit 37 of subframe 3, page 5 shall be a DC Data Type indicator that indicates the data type for which the DCparameters apply. Zero (0) signifies that the corrections apply to CNAV-2 data, D L1C (t), and one (1) signifies thatthe corrections apply to NAV (legacy) data, D(t), defined in Appendix II of IS-GPS-200.The content of an individual data packet is depicted in Figure 3.5-10. The bit lengths, scale factors, ranges, andunits of all fields in the DC packet are given in Table 3.5-8.3.5.4.4.2 Differential Correction Data Predict Time of WeekThe DC data predict time of week (t op-D ) provides the epoch time of week, in increments of 300 seconds (i.e. fiveminutes), at which the prediction for the associated DC data was performed.3.5.4.4.3 Time of Differential Correction DataThe time of DC data, t OD , specifies the reference time of week, in increments of 300 seconds (i.e., five minutes)relative to the GPS week, for the associated CDC and EDC data.3.5.4.4.4 DC Data PacketEach DC data packet contains: corrections to SV clock polynomial coefficients provided in subframe 2 of thecorresponding SV; corrections to quasi-Keplerian elements referenced to t OD of the corresponding SV; and UserDifferential Range Accuracy (UDRA) and UDRA indices that enable users to estimate the accuracy obtained aftercorrections are applied. Each DC packet is made up of two different segments. The first segment contains 34 bitsfor the CDC parameters and the second segment contains 92 bits of EDC parameters totaling 126 bits. The CDCand EDC parameters form an indivisible pair and users must utilize CDC and EDC as a pair.3.5.4.4.4.1 SV PRN IdentificationThe PRN ID of both CDC and EDC as depicted in Figure 3.5-10 identifies the satellite to which the subject 126-bitdifferential correction packet data applies (by PRN code assignment). A value of all ones “11111111” in any PRNID field shall indicate that no DC data is contained in the remainder of the data block. In this event, the remainderof the data block shall be filler bits, i.e., alternating ones and zeros beginning with one.3.5.4.4.4.2 Application of DC DataThe application of CDC data and EDC data is defined in paragraphs 30.3.3.7.3, 30.3.3.7.4, and 30.3.3.7.5 of IS-GPS-200.61 IS-GPS-800A8 June 2010
- Page 17 and 18: The overlay codes are derived from
- Page 19 and 20: 3.2-2 L1C Ranging Codes Parameter A
- Page 21 and 22: GPS PRNSignal No.3.2-3 L1C O Overla
- Page 23 and 24: FIXED LENGTH-10223 LEGENDRE SEQUENC
- Page 25 and 26: 3.2.2.2 Non-Standard CodesThe non-s
- Page 27 and 28: corresponding to MSB = 0. (A SV tra
- Page 29 and 30: This code has the following charact
- Page 31 and 32: 3.2.3.5 InterleavingThe 1748 encode
- Page 33 and 34: 3.3 Signal ModulationThe signals mo
- Page 35 and 36: Bit valueL1C DbitstreamSubcarrier s
- Page 37 and 38: 3.5 Message DefinitionAs shown in F
- Page 40 and 41: DIRECTION OF DATA FLOW FROM SV100 B
- Page 42 and 43: DIRECTION OF DATA FLOW FROM SV100 B
- Page 44 and 45: DIRECTION OF DATA FLOW FROM SV100 B
- Page 46 and 47: 3.5.3 Subframe 2Subframe 2 provides
- Page 48 and 49: Table 3.5-1. Subframe 2 Parameters
- Page 50 and 51: 3.5.3.1 Transmission Week NumberBit
- Page 52 and 53: 3.5.3.6 Ephemeris Parameter Charact
- Page 54 and 55: Table 3.5-2. Elements of Coordinate
- Page 56 and 57: The user shall use the broadcast UR
- Page 58 and 59: where, ISC L1CD is provided to the
- Page 60 and 61: 3.5.3.10.1 Integrity Status Flag (I
- Page 62 and 63: The ionospheric data shall be updat
- Page 64 and 65: 3.5.4.2.3 User Algorithm for Applic
- Page 66 and 67: transmitted by the SVs will degrade
- Page 70 and 71: MSBCDC = Clock Differential Correct
- Page 72 and 73: 3.5.4.5 Subframe 3, Page 6 - TextSu
- Page 74 and 75: 5. RESERVED66 IS-GPS-800A8 June 201
- Page 76 and 77: LSF - Leap Seconds FutureL1C - Comm
- Page 78 and 79: Table 6.2-1.Legendre Sequence (Octa
- Page 80 and 81: Table 6.2-2 LDPC Submatrix A for Su
- Page 82 and 83: Table 6.2-2 LDPC Submatrix A for Su
- Page 84 and 85: Table 6.2-2 LDPC Submatrix A for Su
- Page 86 and 87: Table 6.2-2 LDPC Submatrix A for Su
- Page 88 and 89: Table 6.2-2 LDPC Submatrix A for Su
- Page 90 and 91: Table 6.2-3. LDPC Submatrix B for S
- Page 92 and 93: Table 6.2-7. LDPC Submatrix T for s
- Page 94 and 95: Table 6.2-7. LDPC Submatrix T for s
- Page 96 and 97: Table 6.2-8. LDPC Submatrix A for s
- Page 98 and 99: Table 6.2-8. LDPC Submatrix A for s
- Page 100 and 101: Table 6.2-9. LDPC Submatrix B for S
- Page 102 and 103: Table 6.2-13. LDPC Submatrix T for
- Page 104 and 105: Table 6.2-16. Number of 1’s in LD
- Page 106 and 107: 6.3 Supporting Material6.3.1 Additi
- Page 108 and 109: Table 6.3-1 Additional L1C Ranging
- Page 110 and 111: Table 6.3-1 Additional L1C Ranging
- Page 112 and 113: Table 6.3-1 Additional L1C Ranging
- Page 114 and 115: PRNSignalNo.Table 6.3-2. Additional
- Page 116 and 117: PRNSignalNo.Table 6.3-2 Additional
Table 3.5-7.Midi Almanac ParametersParameterNo. ofBits**ScaleFactor(LSB)EffectiveRange***Unitst oae i ****AΩ 0M 0a f0a f181111*11*1716*16*16*11*10*2 122 -162 -142 -332 -42 -152 -152 -152 -20602,112 secondsdimensionlesssemi-circlessemi-circles/secmeterssemi-circlessemi-circlessemi-circlessecondssec/sec* Parameters so indicated shall be in two's complement notation;** See Figure 3.5-5 for complete bit allocation in subframe 3, page 4;*** Unless otherwise indicated in this column, effective range is the maximum range attainable withindicated bit allocation and scale factor;**** Relative to i 0 = 0.30 semi-circles.3.5.4.4 Subframe 3, Page 5 – Differential CorrectionSubframe 3, page 5, Figure 3.5-6, contains the Differential Correction (DC) parameters. These parameters provideusers with sets of correction terms that apply to the clock and ephemeris data transmitted by other SVs. DCparameters are grouped in packets, as described in this section. The availability of this data is subject to the controland determination of the CS. The contents of subframe 3, page 5, are defined below, and followed by materialpertinent to the use of the data.3.5.4.4.1 Differential Correction Parameter ContentSubframe 3, page 5 shall contain DC parameters that apply to the clock and ephemeris data transmitted by anotherSV. One subframe 3, page 5, as depicted in Figure 3.5-6, shall contain 34 bits of clock differential correction (CDC)parameters and 92 bits of ephemeris differential correction (EDC) parameters for one SV other than the transmitting60 <strong>IS</strong>-<strong>GPS</strong>-<strong>800A</strong>8 June 2010
Change language