IS-GPS-800A - US Coast Guard Navigation Center
IS-GPS-800A - US Coast Guard Navigation Center IS-GPS-800A - US Coast Guard Navigation Center
3.5.3.10.1 Integrity Status Flag (ISF)Bit 566 of subframe 2 shall be the Integrity Status Flag (ISF). A “0” in bit position 566 indicates that the conveyingsignal is provided with the legacy level of integrity assurance. That is, the probability that the instantaneous URE ofthe conveying signal exceeds 4.42 times the upper bound value of the current broadcast URA index, for more than5.2 seconds, without an accompanying alert, is less than 1 x 10^-5 per hour. A “1” in bit position 566 indicates thatthe conveying signal is provided with an enhanced level of integrity assurance. That is, the probability that theinstantaneous URE of the conveying signal exceeds 5.73 times the upper bound value of the current broadcast URAindex, for more than 5.2 seconds, without an accompanying alert, is less than 1 x 10^-8 per hour. The probabilitiesassociated with the nominal and lower bound values of the current broadcast URA are not defined.In this context, an “alert” is defined as any indication or characteristic in the conveying signal, as specifiedelsewhere in this document, which signifies that the conveying signal may be invalid and should not be used, suchas, not Operational-Healthy, Non-Standard Code, parity error, etc.3.5.4 Subframe 3Subframe 3 provides users with other navigation data which is commutated over multiple pages. The contents ofsubframe 3 data are defined below.Every subframe 3 page begins with an 8-bit PRN number of the transmitting SV with a range of 0 (00000000) to255 (11111111). Each subframe 3 page is identified by a 6-bit page number provided in bits 9 through 14.3.5.4.1 Subframe 3, Page 1 – UTC & IONOAs depicted in Figure 3.5-2, subframe 3, page 1 contains the UTC and ionospheric correction parameters. Thecontents of subframe 3, page 1, are defined below, and followed by material pertinent to the use of the data.3.5.4.1.1 UTC Parameter ContentSubframe 3, page 1 shall contain the parameters related to correlating UTC(USNO) time with GPS Time. The bitlengths, scale factors, ranges, and units of these parameters are given in Table 3.5-3. See Figure 3.5-2 for completebit allocation in subframe 3, page 1.The parameters relating GPS time to UTC(USNO) shall be updated by the CS at least once every three days whilethe CS is able to upload the SVs. If the CS is unable to upload the SVs, the accuracy of the UTC parameterstransmitted by the SVs will degrade over time.3.5.4.1.1.1 UTC and GPS TimeSubframe 3, page 1 includes: (1) the parameters needed to relate GPS Time to UTC(USNO), and (2) notice to theuser regarding the scheduled future or recent past (relative to navigation message upload) value of the delta time52 IS-GPS-800A8 June 2010
due to leap seconds (t LSF ), together with the week number (WN LSF ) and the day number (DN) at the end of whichthe leap second becomes effective. Information required to use these parameters to calculate t UTC is in paragraph20.3.3.5.2.4 of IS-GPS-200 except the following definition of t UTC shall be used:t UTC = t LS + A 0-n + A 1-n (t E – t ot + 604800 (WN – WN ot )) + A 2-n (t E – t ot + 604800 (WN – WN ot )) 2 seconds.Table 3.5-3.UTC ParametersParameterNo. ofBits**Scale Factor(LSB)EffectiveRange***UnitsA 0-nA 1-nA 2-nBias coefficient of GPS time scalerelative to UTC time scaleDrift coefficient of GPS time scalerelative to UTC time scaleDrift rate correction coefficient of GPStime scale relative to UTC time scale16* 2 -35 seconds13* 2 -51 sec/sec7* 2 -68 sec/sec 2∆t LS Current or past leap second count 8* 1 secondst ot Time data reference Time of Week 16 2 4 604,784 secondsWN ot Time data reference Week Number 13 1 weeksWN LSF Leap second reference Week Number 13 1 weeksDN Leap second reference Day Number 4**** 1 days∆t LSF Current or future leap second count 8* 1 seconds* Parameters so indicated shall be in two's complement notation;** See Figure 3.5-2 for complete bit allocation;*** Unless otherwise indicated in this column, effective range is the maximum range attainable with indicatedbit allocation and scale factor;**** Right justified.3.5.4.1.2 Ionospheric DataThe ionospheric parameters which allow the “L1 only” user to utilize the ionospheric model for computation of theionospheric delay are contained in subframe 3, page 1. The “one frequency” user should use the model given inparagraph 20.3.3.5.2.5 of IS-GPS-200 to make this correction for the ionospheric effects. The bit lengths, scalefactors, ranges, and units of these parameters are given in Table 20-X of IS-GPS-200.53 IS-GPS-800A8 June 2010
- 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 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 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
- 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
3.5.3.10.1 Integrity Status Flag (<strong>IS</strong>F)Bit 566 of subframe 2 shall be the Integrity Status Flag (<strong>IS</strong>F). A “0” in bit position 566 indicates that the conveyingsignal is provided with the legacy level of integrity assurance. That is, the probability that the instantaneous URE ofthe conveying signal exceeds 4.42 times the upper bound value of the current broadcast URA index, for more than5.2 seconds, without an accompanying alert, is less than 1 x 10^-5 per hour. A “1” in bit position 566 indicates thatthe conveying signal is provided with an enhanced level of integrity assurance. That is, the probability that theinstantaneous URE of the conveying signal exceeds 5.73 times the upper bound value of the current broadcast URAindex, for more than 5.2 seconds, without an accompanying alert, is less than 1 x 10^-8 per hour. The probabilitiesassociated with the nominal and lower bound values of the current broadcast URA are not defined.In this context, an “alert” is defined as any indication or characteristic in the conveying signal, as specifiedelsewhere in this document, which signifies that the conveying signal may be invalid and should not be used, suchas, not Operational-Healthy, Non-Standard Code, parity error, etc.3.5.4 Subframe 3Subframe 3 provides users with other navigation data which is commutated over multiple pages. The contents ofsubframe 3 data are defined below.Every subframe 3 page begins with an 8-bit PRN number of the transmitting SV with a range of 0 (00000000) to255 (11111111). Each subframe 3 page is identified by a 6-bit page number provided in bits 9 through 14.3.5.4.1 Subframe 3, Page 1 – UTC & IONOAs depicted in Figure 3.5-2, subframe 3, page 1 contains the UTC and ionospheric correction parameters. Thecontents of subframe 3, page 1, are defined below, and followed by material pertinent to the use of the data.3.5.4.1.1 UTC Parameter ContentSubframe 3, page 1 shall contain the parameters related to correlating UTC(<strong>US</strong>NO) time with <strong>GPS</strong> Time. The bitlengths, scale factors, ranges, and units of these parameters are given in Table 3.5-3. See Figure 3.5-2 for completebit allocation in subframe 3, page 1.The parameters relating <strong>GPS</strong> time to UTC(<strong>US</strong>NO) shall be updated by the CS at least once every three days whilethe CS is able to upload the SVs. If the CS is unable to upload the SVs, the accuracy of the UTC parameterstransmitted by the SVs will degrade over time.3.5.4.1.1.1 UTC and <strong>GPS</strong> TimeSubframe 3, page 1 includes: (1) the parameters needed to relate <strong>GPS</strong> Time to UTC(<strong>US</strong>NO), and (2) notice to theuser regarding the scheduled future or recent past (relative to navigation message upload) value of the delta time52 <strong>IS</strong>-<strong>GPS</strong>-<strong>800A</strong>8 June 2010