IS-GPS-800A - US Coast Guard Navigation Center

IS-GPS-800A - US Coast Guard Navigation Center IS-GPS-800A - US Coast Guard Navigation Center

navcen.uscg.gov
from navcen.uscg.gov More from this publisher
13.07.2015 Views

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

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

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!