IS-GPS-200H (797934), страница 22
Текст из файла (страница 22)
Message Type 30 - Clock, IONO & Group Delay143IS-GPS-200H24 Sep 2013192115PRN6BITS8 BITS6BITSMESSAGETOW COUNT*top17 BITS11 BITS5BITS"ALERT" FLAG - 1 BITtocaf0-n11 BITS26 BITSMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS101128118141149af1-naf2-nWNa-ntoa17 LSBs10 BITS13 BITS8 BITS180Reduced AlmanacPacket 1Reduced AlmanacPacket 231 BITS21 MSBsMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS20110 LSBs9872URANED2 INDEX - 3 BITSURANED1 INDEX - 3 BITSaf1-n – 3 MSBsURANED0 INDEXMESSAGE TYPE IDPREAMBLEMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS385055 58 6139211273 277242Reduced AlmanacPacket 3Reduced AlmanacPacket 431 BITS31 BITSReduced Almanac Packet 2CRC4BITS24 BITSRESERVED* MESSAGE TOW COUNT = 17 MSB OF ACTUAL TOW COUNT AT START OF NEXT 12-SECOND MESSAGEFigure 30-4. Message Type 31 - Clock & Reduced Almanac144IS-GPS-200H24 Sep 2013192115PRN6BITS8 BITS6BITSMESSAGETOW COUNT*top17 BITS11 BITS5BITS"ALERT" FLAG - 1 BITtocaf0-n11 BITS26 BITSMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS101144128118165180af1-naf2-ntEOPPM-X•PM-X17 LSBs10 BITS16 BITS21 BITS15 BITS15 BITS21 BITS277266247216•PM-YPM-YMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS2019872URANED2 INDEX - 3 BITSURANED1 INDEX - 3 BITSaf1-n – 3 MSBsURANED0 INDEXMESSAGE TYPE IDPREAMBLEMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS385055 58 6139∆UT1•∆UT1RESERVEDCRC31 BITS19 BITS11 BITS24 BITS* MESSAGE TOW COUNT = 17 MSB OF ACTUAL TOW COUNT AT START OF NEXT 12-SECOND MESSAGEFigure 30-5.Message Type 32 - Clock & EOP145IS-GPS-200H24 Sep 2013192115PRN6BITS8 BITS6BITSMESSAGETOW COUNT*top17 BITS11 BITS5BITS"ALERT" FLAG - 1 BITtocaf0-n11 BITS26 BITSMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS1011281189872URANED2 INDEX - 3 BITSURANED1 INDEX - 3 BITSaf1-n – 3 MSBsURANED0 INDEXMESSAGE TYPE IDPREAMBLEMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS385055 58 6139144157164172188af1-naf2-nA0-nA1-nA2-n∆tLStotWNot17 LSBs10 BITS16 BITS13 BITS7 BITS8 BITS16 BITS13 BITSDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS214 218201WNLSF13 BITSDN277226∆tLSF4BITS 8 BITSMSB FIRSTRESERVEDCRC51 BITS24 BITS* MESSAGE TOW COUNT = 17 MSB OF ACTUAL TOW COUNT AT START OF NEXT 12-SECOND MESSAGEFigure 30-6.Message Type 33 - Clock & UTC146IS-GPS-200H24 Sep 2013192115PRN6BITS8 BITS6BITSMESSAGETOW COUNT*top17 BITS11 BITS"ALERT" FLAG - 1 BIT101128118af2-n17 LSBs10 BITStocaf0-n11 BITS26 BITSDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS150139151top-Daf1-n5BITS9872URANED2 INDEX - 3 BITSURANED1 INDEX - 3 BITSaf1-n – 3 MSBsURANED0 INDEXMESSAGE TYPE IDPREAMBLEMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS385055 58 613911 BITSMSB FIRST185tODCDCEDC11 BITS34 BITS16 MSBsDC DATA TYPE – 1 BITDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS277201*MSB FIRSTEDCCRC76 LSBs24 BITSMESSAGE TOW COUNT = 17 MSB OF ACTUAL TOW COUNT AT START OF NEXT 12-SECOND MESSAGECDC = Clock Differential CorrectionEDC = Ephemeris Differential CorrectionFigure 30-7.Message Type 34 - Clock & Differential Correction147IS-GPS-200H24 Sep 2013192115PRN6BITS8 BITS6BITSMESSAGETOW COUNT*top17 BITS11 BITS5BITS"ALERT" FLAG - 1 BITtocaf0-n11 BITS26 BITSDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS1011281189872URANED2 INDEX - 3 BITSURANED1 INDEX - 3 BITSaf1-n – 3 MSBsURANED0 INDEXMESSAGE TYPE IDPREAMBLEMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS3855 58 615039157 160144MSB FIRST189176af1-naf2-ntGGTOWNGGTOA0GGTOA1GGTO17 LSBs10 BITS16 BITS13 BITS16 BITS13 BITSDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDSA2GGTO7 BITS 5 BITSRESERVEDGNSS ID – 3 BITSMSB FIRST277201RESERVEDCRC76 BITS24 BITS* MESSAGE TOW COUNT = 17 MSB OF ACTUAL TOW COUNT AT START OF NEXT 12-SECOND MESSAGEFigure 30-8.Message Type 35 - Clock & GGTO148196IS-GPS-200H24 Sep 2013121159PRN6BITS8 BITS6BITSMESSAGETOW COUNT*top17 BITS11 BITS5BITS"ALERT" FLAG - 1 BITtocaf0-n11 BITS26 BITSMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS1019872URANED2 INDEX - 3 BITSURANED1 INDEX - 3 BITSaf1-n – 3 MSBsURANED0 INDEXMESSAGE TYPE IDPREAMBLEMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS385055 58 6139128118af1-naf2-n17 LSBs10 BITSTEXT MESSAGE (18 8-BIT CHAR)73 MSBsMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS272201276277TEXT MESSAGE (18 8-BIT CHAR)CRC4BITS71 LSBsTEXT PAGE24 BITSRESERVED – 1 BIT* MESSAGE TOW COUNT = 17 MSB OF ACTUAL TOW COUNT AT START OF NEXT 12-SECOND MESSAGEFigure 30-9.Message Type 36 - Clock & Text149IS-GPS-200H24 Sep 2013192115PRN6BITS8 BITS6BITSMESSAGETOW COUNT*top17 BITS11 BITS5BITS"ALERT" FLAG - 1 BITtocaf0-n11 BITS26 BITSMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS1011281189872URANED2 INDEX - 3 BITSURANED1 INDEX - 3 BITSaf1-n – 3 MSBsURANED0 INDEXMESSAGE TYPE IDPREAMBLEMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS385055 58 6139141af1-naf2-nWNa-n17 LSBs10 BITS13 BITStoa149155 15818011 BITS11 BITS191•ΩA11 BITS10 MSBsδiePRNa8 BITS 6 BITS169L1 HEALTH – 1 BITL2 HEALTH – 1 BITL5 HEALTH – 1 BITMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS201240224208256277267AΩ0ωM0af0af1CRC7 LSBs16 BITS16 BITS16 BITS11 BITS10 BITS24 BITS* MESSAGE TOW COUNT = 17 MSB OF ACTUAL TOW COUNT AT START OF NEXT 12-SECOND MESSAGEFigure 30-10.
Message Type 37 - Clock & Midi Almanac150IS-GPS-200H24 Sep 20131159PRN8 BITS6BITS6BITS21MESSAGETOW COUNT*toa8 BITS31 BITSWNa-n13 BITS17 BITS91Reduced AlmanacPacket 110 MSBsReduced Almanac Packet 2MESSAGE TYPE IDPREAMBLEMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS38605239"ALERT" FLAG - 1 BITDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS122101Reduced AlmanacPacket 221 LSBs153184Reduced AlmanacPacket 4Reduced AlmanacPacket 3215Reduced AlmanacPacket 531 BITS31 BITSDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS201MSB FIRST17 MSBsMSB FIRST277246Reduced AlmanacPacket 5Reduced AlmanacPacket 6Reduced AlmanacPacket 7CRC14 LSBs31 BITS31 BITS24 BITS* MESSAGE TOW COUNT = 17 MSB OF ACTUAL TOW COUNT AT START OF NEXT 12-SECOND MESSAGEFigure 30-11.
Message Type 12 - Reduced Almanac151IS-GPS-200H24 Sep 2013121159MESSAGETOW COUNT*PRN8 BITS6BITS6BITStop-D11 BITS17 BITS9697CDCtODMESSAGE TYPE IDPREAMBLEMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS613850396211 BITS34 BITSDC DATA TYPE – 1 BITDC DATA TYPE – 1 BITCDC - 4 MSBs"ALERT" FLAG - 1 BITMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS131166132167101CDCCDCCDC30 LSBs34 BITS34 BITSDC DATA TYPE – 1 BITDC DATA TYPE – 1 BITDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS236237201202CDCMSB FIRST271277CDC34 BITS34 BITS6BITSCRC24 BITSDC DATA TYPE – 1 BITDC DATA TYPE – 1 BITRESERVED* MESSAGE TOW COUNT = 17 MSB OF ACTUAL TOW COUNT AT START OF NEXT 12-SECOND MESSAGECDC = Clock Differential CorrectionFigure 30-12. Message Type 13 - Clock Differential Correction152IS-GPS-200H24 Sep 20131159PRN8 BITS6BITS6BITSDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS386150396221MESSAGETOW COUNT*17 BITStop-D11 BITSMESSAGE TYPE IDPREAMBLEEDCtOD11 BITSMSB FIRST39 MSBsDC DATA TYPE – 1 BIT"ALERT" FLAG - 1 BITDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDSMSB FIRST154155101EDCEDC53 LSBs46 MSBsDC DATA TYPE – 1 BITDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS247201MSB FIRST277EDCRESERVEDCRC46 LSBs30 BITS24 BITS* MESSAGE TOW COUNT = 17 MSB OF ACTUAL TOW COUNT AT START OF NEXT 12-SECOND MESSAGEEDC = Ephemeris Differential CorrectionFigure 30-13.
Message Type 14 - Ephemeris Differential Correction153IS-GPS-200H24 Sep 20131159PRN8 BITS6BITS6BITSMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS383921MESSAGETOW COUNT*TEXT MESSAGE (29 8-BIT CHAR)62 MSBs17 BITSMESSAGE TYPE IDPREAMBLE"ALERT" FLAG - 1 BITMSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS101TEXT MESSAGE (29 8-BIT CHAR)BITS 63-162MSB FIRSTDIRECTION OF DATA FLOW FROM SV100 BITS4 SECONDS271201275277TEXT MESSAGE (29 8-BIT CHAR)CRC4BITS70 LSBsTEXT PAGE24 BITSRESERVED – 2 BITS* MESSAGE TOW COUNT = 17 MSB OF ACTUAL TOW COUNT AT START OF NEXT 12-SECOND MESSAGEFigure 30-14.
Message Type 15 – Text154IS-GPS-200H24 Sep 201330.3.3.1 Message Type 10 and 11 Ephemeris and Health Parameters.30.3.3.1.1 Message Type 10 and 11 Ephemeris and Health Parameter Content.The contents of the SV health, ephemeris representation and accuracy parameters in messagetypes 10 and 11 are defined below, followed by material pertinent to the use of the data.Message type 10 in conjunction with message type 11, provides users with the requisite data tocalculate SV position. The general format of message types 10 and 11 consists of data fields forreference time tags, a set of gravitational harmonic correction terms, rates and rate corrections toquasi-Keplerian elements, and an accuracy indicator for ephemeris-related data.The ephemeris parameters in the message type 10 and type 11 describe the orbit of thetransmitting SV during the curve fit interval of three hours. The nominal transmission interval istwo hours, and shall coincide with the first two hours of the curve fit interval.
The predictedperiod of applicability for ephemeris data coincides with the entire three-hour curve fit interval.Table 30-I gives the definition of the orbital parameters using terminology typical of Keplerianorbital parameters; it is noted, however, that the transmitted parameter values are expressed suchthat they provide the best trajectory fit in Earth-Centered, Earth-Fixed (ECEF) coordinates foreach specific fit interval.
The user shall not interpret intermediate coordinate values aspertaining to any conventional coordinate system.The toe term shall provide the user with a convenient means for detecting any change in theephemeris representation parameters. The toe is provided in both message type 10 and 11 for thepurpose of comparison with the toc term in message type 30 - 37.
Whenever these three terms donot match, a data set cutover has occurred and new data must be collected. The timing of the toeand constraints on the toc and toe are defined in paragraph 30.3.4.4.Any change in the message type 10 and 11 ephemeris data will be accomplished with asimultaneous change in the toe value. The CS will assure the toe value for Block IIR-M/IIF and SSwill assure the toe value for GPS III, for at least the first data set transmitted by an SV after anupload, is different from that transmitted prior to the cutover. See Section 30.3.4.5 for additionalinformation regarding toe.The CNAV messages contain information that allows users to take advantage of situations whenintegrity is assured to the enhanced level. This is accomplished using a composite integrityassured URA value in conjunction with an integrity status flag.
The composite integrity assuredURA (IAURA) value is the RSS of an elevation-dependent function of the upper bound value ofthe URAED component and the upper bound value of the URANED component. The compositeIAURA value is assured to the enhanced level only when the integrity status flag is “1”;otherwise the IAURA value is assured to the legacy level.155IS-GPS-200H24 Sep 2013Bit 272 of Message Type 10 is the Integrity Status Flag (ISF). A "0" in bit position 272 indicatesthat the conveying signal is provided with the legacy level of integrity assurance. That is, theprobability that the instantaneous URE of the conveying signal exceeds 4.42 times the currentbroadcast IAURA value, for more than 5.2 seconds, without an accompanying alert, is less than1E-5 per hour. A "1" in bit-position 272 indicates that the conveying signal is provided with anenhanced level of integrity assurance.
That is, the probability that the instantaneous URE of theconveying signal exceeds 5.73 times the current broadcast IAURA value, for more than 5.2seconds, without an accompanying alert, is less than 1E-8 per hour. The probabilities associatedwith the nominal and lower bound values of the current broadcast URAED index, URANEDindexes, and related URA values are not defined.In this context, an "alert" is defined as any indication or characteristic of the conveying signal, asspecified elsewhere in this document, which signifies to users that the conveying signal may beinvalid or should not be used, such as the health bits not indicating operational-healthy,broadcasting non-standard code parity error, etc.Bit 273 of Message Type 10 indicates the phase relationship between L2C and P(Y) as specifiedin section 3.3.1.5.1 of IS-GPS-200.30.3.3.1.1.1 Transmission Week Number.Bits 39 through 51 of message type 10 shall contain 13 bits which are a modulo-8192 binaryrepresentation of the current GPS week number at the start of the data set transmission interval(see paragraph 6.2.4).30.3.3.1.1.2 Signal Health (L1/L2/L5).The three, one-bit, health indication in bits 52 through 54 of message type 10 refers to the L1,L2, and L5 signals of the transmitting SV.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
