资源描述:
《A Clock and Ephemeris Algorithm for Dual 英文文献资料》由会员上传分享,免费在线阅读,更多相关内容在行业资料-天天文库。
1、ChangeVieChangeVieF-XwF-XwDeDerrPPwClicktobuyNOW!wClicktobuyNOW!wmwmwowo.dock.c.dock.cu-tracu-tracAClockandEphemerisAlgorithmforDualFrequencySBASJuanBlanch,ToddWalter,PerEnge.StanfordUniversity.ABSTRACTcarriercoherence(CCC),andthesignaldeformation(SQM)[1].ThistermisdesignatedintheMinimumInthenexty
2、ears,thenewGPSandGalileosignals(L1,OperationalPerformanceStandards[3]asσflt.InthecaseL5)willallowciviluserstoremovetheionosphericdelayofWAAS,thistermistheproductoftheUDREandainthepseudoranges.ThiswillhavealargeimpactontheshapingmatrixcontainedinMessageType28[4].TheSatelliteBasedAugmentationSystems
3、(SBAS),asthebroadcastindexUDREisthemaximumoftheoutputofionosphericdelayiscurrentlythelargesterror.OncethistheUDREalgorithmandthefloorimposedbyboththesourceoferrorisremoved,theVerticalProtectionLevelsCCCandSQMmonitors.willdecreasesubstantially,andothererrorsourceswilldominate.Theremainingtermsinthe
4、errorboundwereWAAStodayprovidesverticalguidanceinthemuchlesscriticalthantheionosphericdelayerrorbound,conterminousU.SandAlaskawithveryhighavailability.sotheyhavereceivedlessattention.ItisthereforelikelyHowever,ifwewanttoeitherachievebetterlevelsofthattheycanstillbeoptimized.Thisistrueinparticulars
5、erviceorbemorerobustagainstdepletedconstellations,itfortheUserDifferentialRangeError(UDRE)algorithmwillbenecessarytoreducetheProtectionLevels.Thiswhichcomputestheclockandephemeriserrorbounds.IncouldbedonebymodifyingtheVerticalProtectionLeveladdition,newSBASmessageswillbebroadcastintheL5[5],[6]orby
6、reducingthetermσflt.Withthedevelopmentchannel,andtheircontentisstillnotfixed.Therefore,itisofWAASdualfrequency,thereisanopportunitytoagoodopportunitytodeterminewhetherchangescanbeupgradethealgorithms.Inthispaper,weoutlinethebroadmadebothintheUDREandMessageType28(MT28)linesofaclockandephemerisalgor
7、ithmthathasthecomputationandtransmissiontoincreaseoverallSBASpotentialtoreducetheWAASerrorboundssignificantly.performance.Thisalgorithmusesideassimilartotheonesdescribedin[11],butdiffersinsomekeypoints.Inthefirst