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-2. Elements of Coordinate System (part 2 of 2)Element/Equation * k = k + nu k = C us-n sin2 k + C uc-n cos2 kr k = C rs-n sin2 k + C rc-n cos2 ki k = C is-n sin2 k + C ic-n cos2 kDescriptionArgument of LatitudeArgument of Latitude CorrectionRadial CorrectionInclination CorrectionSecond HarmonicPerturbationsu k = k + u kr k = A k (1 – e n cos E k ) + r kCorrected Argument of LatitudeCorrected Radiusi k= i o-n + (i o-n -DOT)t k + i kCorrected Inclinationx k ' = r k cos u ky k ' = r k sin u kPositions in orbital plane = REF + ∆ *** k = 0-n + ( − e ) t k – e t oeRate of Right AscensionCorrected Longitude of Ascending Nodex k = x k ' cos k y k ' cos i k sin ky k = x k ' sin k + y k ' cos i k cos kEarth-fixed coordinates of SV antenna phase centerz k = y k ' sin i k•*** REF = 2.6 x 10 -9 semi-circles/second.3.5.3.7 Clock Parameter CharacteristicsThe bit lengths, scale factors, ranges, and units of the clock correction parameters shall be as specified inTable 3.5-1.3.5.3.7.1 User Algorithms for SV Clock Correction DataThe algorithms defined in paragraph 20.3.3.3.3.1 of IS-GPS-200 allow all users to correct the code phase timereceived from the SV with respect to both SV code phase offset and relativistic effects. However, since the SVclock corrections of equations in paragraph 20.3.3.3.3.1 of IS-GPS-200 are estimated by the CS using dualfrequency L1 P(Y) and L2 P(Y) code measurements, the single-frequency (L1) user and the dual-frequency (L1/L2and L1/L5) user must apply additional terms to the SV clock correction equations. These terms are described inparagraph 3.5.3.9. In addition, users shall use t oe , provided in bits 39 through 49 of subframe 2, to replace t oc in thealgorithms in paragraph 20.3.3.3.3.1 of IS-GPS-200.46 IS-GPS-800A8 June 2010
3.5.3.8 SV Clock Accuracy EstimatesBits 460 through 470 of subframe 2 shall contain the URA oc Index, URA oc1 Index, and URA oc2 Index of the SV(reference paragraph 6.2.1) for the user. The URA oc Index together with URA oc1 Index and URA oc2 Index shall givethe clock-related user range accuracy of the SV as a function of time since the prediction (t op ) used to generate theuploaded clock correction polynomial terms.Clock-related URA (URAoc) accounts for signal-in-space contributions to user range error that include, but are notlimited to, the following: the net effect of clock parameter and code phase error in the transmitted signal for singlefrequencyusers who correct the code phase as described in Section 3.5.3.9.1, as well as the net effect of clockparameter, code phase, and intersignal correction error for dual-frequency L1/L2 and L1/L5 users who correct forgroup delay and ionospheric effects as described in Section 3.5.3.9.2 and Section 3.5.3.9.3.The user shall calculate the clock-related URA with the equation (in meters):URA oc = URA ocb + URA oc1 (t – t op )URA oc = URA ocb + URA oc1 (t – t op ) + URA oc2 (t – t op – 93,600) 2for t-t op < 93,600 secondsfor t-t op > 93,600 secondswheret = GPS time (must account for beginning or end of week crossovers),t op = time of week of the state estimate utilized for the prediction of satellite clock correction parameters.The CS shall derive URA ocb at time t op which, when used together with URA oc1 and URA oc2 in the above equations,results in the minimum URA oc that is greater than the predicted URA oc during the entire duration up to 14 daysafter t op .47 IS-GPS-800A8 June 2010
- Page 3 and 4: REVISION RECORDLTR DESCRIPTION DATE
- Page 5 and 6: 3.2.3.3 Cyclic Redundancy Check ...
- Page 7 and 8: LIST OF FIGURESFigure 3.2-1. Genera
- Page 9 and 10: 1. INTRODUCTION1.1 ScopeThis Interf
- Page 11 and 12: 3. SIGNAL REQUIREMENTSThe requireme
- Page 13 and 14: Carriers of the two L1C components
- Page 15 and 16: 3.2.2 PRN Code CharacteristicsThe c
- 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 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 68 and 69: Table 3.5-7.Midi Almanac Parameters
- 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
3.5.3.8 SV Clock Accuracy EstimatesBits 460 through 470 of subframe 2 shall contain the URA oc Index, URA oc1 Index, and URA oc2 Index of the SV(reference paragraph 6.2.1) for the user. The URA oc Index together with URA oc1 Index and URA oc2 Index shall givethe clock-related user range accuracy of the SV as a function of time since the prediction (t op ) used to generate theuploaded clock correction polynomial terms.Clock-related URA (URAoc) accounts for signal-in-space contributions to user range error that include, but are notlimited to, the following: the net effect of clock parameter and code phase error in the transmitted signal for singlefrequencyusers who correct the code phase as described in Section 3.5.3.9.1, as well as the net effect of clockparameter, code phase, and intersignal correction error for dual-frequency L1/L2 and L1/L5 users who correct forgroup delay and ionospheric effects as described in Section 3.5.3.9.2 and Section 3.5.3.9.3.The user shall calculate the clock-related URA with the equation (in meters):URA oc = URA ocb + URA oc1 (t – t op )URA oc = URA ocb + URA oc1 (t – t op ) + URA oc2 (t – t op – 93,600) 2for t-t op < 93,600 secondsfor t-t op > 93,600 secondswheret = <strong>GPS</strong> time (must account for beginning or end of week crossovers),t op = time of week of the state estimate utilized for the prediction of satellite clock correction parameters.The CS shall derive URA ocb at time t op which, when used together with URA oc1 and URA oc2 in the above equations,results in the minimum URA oc that is greater than the predicted URA oc during the entire duration up to 14 daysafter t op .47 <strong>IS</strong>-<strong>GPS</strong>-<strong>800A</strong>8 June 2010