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

More documents

Recommendations

Info

The ionospheric data shall be updated by the CS at least once every six days while the CS is able to upload theSVs. If the CS is unable to upload the SVs, the ionospheric data transmitted by the SVs may not be accurate.3.5.4.2 Subframe 3, Page 2 – GGTO & EOPSubframe 3, page 2, as depicted in Figure 3.5-3, contains the GPS/Global Navigation Satellite System (GNSS) TimeOffset (GGTO) parameters and Earth Orientation Parameters (EOP). The contents of subframe 3, page 2, is definedbelow, and followed by material pertinent to the use of the data.3.5.4.2.1 GGTO Parameter ContentSubframe 3, page 2 shall contain the parameters related to correlating GPS time with other GNSS time. Bits 15through 17 of subframe 3, page 2 shall identify the other GPS-like navigation system to which the offset dataapplies. The three bits are defined as follows:000 = no data available,001 = Galileo,010 = GLONASS,011 through 111 = reserved for other systems.The bit lengths, scale factors, ranges, and units of the GGTO parameters are given in Table 3.5-4. See Figure 3.5-3for complete bit allocation in subframe 3, page 2.The validity period of the GGTO shall be 1 day as a minimum.3.5.4.2.1.1 GPS and GNSS TimeThe GPS/GNSS-time relationship is given by,t GNSS = t E – (A 0GGTO + A 1GGTO (t E – t GGTO + 604800 (WN – WN GGTO )) + A 2GGTO (t E – t GGTO + 604800 (WN – WN GGTO )) 2 )where t GNSS is in seconds, t E and WN are as defined in Section 20.3.3.5.2.4 of IS-GPS-200, and the remainingparameters are as defined in Table 3.5-4.The GGTO parameters provide a global average of the time offset between GPS time and the other GNSS timescales modulo one second. Users must also apply any integer seconds difference between the systems usingdefinitions of each system time scale as defined in respective signal interface documents.54 IS-GPS-800A8 June 2010
Table 3.5-4.GPS/GNSS Time Offset ParametersParameterNo. ofBits**ScaleFactor(LSB)EffectiveRange***UnitsA 0GGTOBias coefficient of GPS time scalerelative to GNSS time scale16*2 -35secondsA 1GGTODrift coefficient of GPS time scalerelative to GNSS time scale13*2 -51sec/secA 2GGTODrift rate correction coefficient ofGPS time scale relative to GNSStime scale7*2 -68sec/sec 2t GGTOWN GGTOTime data reference Time of WeekTime data reference WeekNumber16132 42 0 604,784secondsweeksGNSS IDGNSS Type ID3see text* Parameters so indicated shall be in two's complement notation;** See Figure 3.5-3 for complete bit allocation;*** Unless otherwise indicated in this column, effective range is the maximum rangeattainable with indicated bit allocation and scale factor.3.5.4.2.2 EOP Parameter ContentSubframe 3, page 2 shall contain earth orientation parameters. The EOP message provides users with parameters toconstruct the ECEF and ECI coordinate transformation (a simple transformation method that does not account forEOP, is defined in Section 20.3.3.4.3.3.2 of IS-GPS-200). The bit lengths, scale factors, ranges, and units of allEOP fields of subframe 3, page 2, are given in Table 3.5-5.55 IS-GPS-800A8 June 2010
Page 1 and 2:
IS-GPS-800A8 June 2010GLOBAL POSITI
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 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 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 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
Page 118 and 119:
Page 120 and 121:
show all

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

Create successful ePaper yourself

Delete template?

Save as template?