Galileo OS SIS ICD (797928), страница 8
Текст из файла (страница 8)
2-4.Reference:Issue:Revision:Date:GAL OS SIS ICD/D.0Draft023/05/2006Page418.3.1.4 Base register 2 start value for E5b-QThe octal format base register 2 start value with the conventions defined in 8.3.1.1 is asdefined in the following Table 19 for each primary code number (1-50).The hexadecimal format of the first 24 code-chips with the conventions defined in 8.3.1.1 isalso given in Table 19.420H421H42H423HCodeNoStartValueInitialSequence1234567891011121314151617181920212223242503331061432532223371004133623517750047451300537140301552023703461316622714605547024563001300322107612676736004307130766221610E49AF0CE701F54B709641AB1FBD0AE0D8BC9805FA5D86BA0A7E921067E553E4B587D82FBE33BC231372C46676FD2613EEB443C3FD0B1FCB7CFB8381548224A0FEE2538D33BC135B971DE13CodeNoStartValueInitialSequence26272829303132333435363738394041424344454647484950201341126210706341431105125460176653235421230201461136237246163441503425471256462215704336163560407502626117063701127041310247E8CFBB536C3B8E68C1E7272B75B69533F65812B412C4DE1759E2C7E6434B4364005671B8C6FE0978D4E5319BF5164996E4292DC86A38C46BEDF0B03E9A5B2B0E55307DBAC4778E437AF4FTable 20: Base register 2 start values and first code chips for E5b-Q8.3.2 E1-B and E1-C Primary CodesThe E1-B and E1-C primary codes are pseudo-random memory code sequences according tothe hexadecimal representation provided in Annex 1.Note, for each signal component E1-B and E1-C, overall 50 different codes are defined.©, 2006, European Space Agency / Galileo Joint UndertakingDocument subject to terms of use and disclaimers p.
2-4.Reference:Issue:Revision:Date:GAL OS SIS ICD/D.0Draft023/05/2006Page428.4 SECONDARY CODES8.4.1 Definition of secondary codesThe secondary codes are fixed sequences as defined in hexadecimal notation in Table 20 andTable 21, following again the convention used in Par. 8.3.1.1 extended to codes with lengthnot being an integer multiple of 4.
The nth group of four consecutive code-chips in time c4nth3,…,c4n (in logic level notation) translates into the n hexadecimal symbol from the left, thevalue defined as 8·c4n-3 + 4·c4n-2+ 2·c4n-1 + c4n. For secondary codes whose length is notdividable by four (case of CS251), the last (most right-hand) hexadecimal symbol is obtainedby filling up the last group of code-chips with zeros at the end in time (to the right), to reach afinal length of 4 binary symbols.The code identifier together with the code length, the number of hexadecimal symbols (rangefor n), the hexadecimal representation for the secondary codes and the number of filled zerosare listed in Table 20 and Table 21.Notation example: The hexadecimal representation for the CS251 code in Table 20corresponds to the binary sequence [0 0 1 1 1 0 0 0 0 0 0 0 1 0 1 0 1 1 0 1 1 0 0 1 0], the firstbinary value corresponding to the first secondary code chip in time.42H425H426HPPBBBBPPBBBBB427HBBBBB428H429HCode identifierCodelengthNumber of hexadecimalsymbolsNumber of filledup zerosCode sequence (Hexadecimal)CS41410EBBCS2012050842E9CS2512573380AD90CS100110025083F6F69D8F6E15411FB8C9B1CCS100210025066558BD3CE0C7792E83350525CS100310025059A025A9C1AF0651B779A8381CS1004100250D3A32640782F7B18E4DF754B7CS1005100250B91FCAD7760C218FA59348A93CS1006100250BAC77E933A779140F094FBF98CS1007100250537785DE280927C6B58BA6776CS1008100250EFCAB4B65F38531ECA22257E2BBBBBBBBBBBBBBBBBBBB10025079F8CAE838475EA5584BEFC9BCS10010CS1009100250CA5170FEA3A810EC606B66494CS100111002501FC32410652A2C49BD845E567CS10012100250FE0A9A7AFDAC44E42CB95D261CS10013100250B03062DC2B71995D5AD8B7DBECS10014100250F6C398993F598E2DF4235D3D5CS100151002501BB2FB8B5BF24395C2EF3C5A1CS100161002502F920687D238CC7046EF6AFC9CS1001710025034163886FC4ED7F2A92EFDBB8CS1001810025066A872CE47833FB2DFD5625ADCS1001910025099D5A70162C920A4BB9DE1CA8CS1002010025081D71BD6E069A7ACCBEDC66CACS10021100250A654524074A9E6780DB9D3EC6CS10022100250C3396A101BEDAF623CFC5BB37CS10023100250C3D4AB211DF36F2111F2141CDBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB©, 2006, European Space Agency / Galileo Joint UndertakingDocument subject to terms of use and disclaimers p.
2-4.Reference:Issue:Revision:Date:GAL OS SIS ICD/D.0Draft023/05/2006Page43CS100241002503DFF25EAE761739265AF145C1CS10025100250994909E0757D70CDE389102B5CS10026100250B938535522D119F40C25FDAECCS10027100250C71AB549C0491537026B390B7CS100281002500CDB8C9E7B53F55F5B0A0597BCS1002910025061C5FA252F1AF81144766494FCS10030100250626027778FD3C6BB4BAA7A59DCS10031100250E745412FF53DEBD03F1C9A633CS100321002503592AC083F3175FA724639098CS1003310025052284D941C3DCAF2721DDB1FDCS1003410025073B3D8F0AD55DF4FE814ED890CS1003510025094BF16C83BD7462F6498E0282CS10036100250A8C3DE1AC668089B0B45B3579CS10037100250E23FFC2DD2C14388AD8D6BEC8CS10038100250F2AC871CDF89DDC06B5960D2BCS1003910025006191EC1F622A77A526868BA1CS1004010025022D6E2A768E5F35FFC8E01796CS1004110025025310A06675EB271F2A09EA1DCS100421002509F7993C621D4BEC81A0535703CS10043100250D62999EACF1C99083C0B4A417CS10044100250F665A7EA441BAA4EA0D01078CCS1004510025046F3D3043F24CDEABD6F79543CS10046100250E2E3E8254616BD96CEFCA651ACS10047100250E548231A82F9A01A19DB5E1B2CS10048100250265C7F90A16F49EDE2AA706C8CS10049100250364A3A9EB0F0481DA0199D7EACS100501002509810A7A898961263A0F749F56BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBTable 21: Secondary code sequences (Part 1)Code identifierCodelengthNumber of hexadecimalsymbolsNumber of filledup zerosCode sequence (Hexadecimal)CS10051100250CFF914EE3C6126A49FD5E5C94CS10052100250FC317C9A9BF8C6038B5CADAB3CS10053100250A2EAD74B6F9866E414393F239CS1005410025072F2B1180FA6B802CB84DF997CS1005510025013E3AE93BC52391D09E84A982CS1005610025077C04202B91B22C6D3469768ECS10057100250FEBC592DD7C69AB103D0BB29CCS100581002500B494077E7C66FB6C51942A77CS10059100250DD0E321837A3D52169B7B577CCS1006010025043DEA90EA6C483E7990C3223FCS100611002500366AB33F0167B6FA979DAE18CS1006210025099CCBBFAB1242CBE31E1BD52DCS10063100250A3466923CEFDF451EC0FCED22CS100641002501A5271F22A6F9A8D76E79B7F0CS100651002503204A6BB91B49D1A2D3857960BBBBBBBBBBBBBBBBBBBBBBBBBBBBBB©, 2006, European Space Agency / Galileo Joint UndertakingDocument subject to terms of use and disclaimers p.
2-4.Reference:Issue:Revision:Date:GAL OS SIS ICD/D.0Draft023/05/2006Page44CS1006610025032F83ADD43B599CBFB8628E5BCS100671002503871FB0D89DB77553EB613CC1CS100681002506A3CBDFF2D64D17E02773C645CS100691002502BCD09889A1D7FC219F2EDE3BCS100701002503E49467F4D4280B9942CD6F8CCS10071100250658E336DCFD9809F86D54A501CS10072100250ED4284F345170CF77268C8584CS1007310025029ECCE910D832CAF15E3DF5D1CS10074100250456CCF7FE9353D50E87A708FACS10075100250FB757CC9E18CBC02BF1B84B9ACS100761002505686229A8D98224BC426BC7FCCS10077100250700A2D325EA14C4B7B7AA8338CS100781002501210A330B4D3B507D854CBA3FCS10079100250438EE410BD2F7DBCDD85565BACS100801002504B9764CC455AE1F61F7DA432BCS10081100250BF1F45FDDA3594ACF3C4CC806CS10082100250DA425440FE8F6E2C11B8EC1A4CS10083100250EE2C8057A7C16999AFA33FED1CS100841002502C8BD7D8395C61DFA96243491CS10085100250391E4BB6BC43E98150CDDCADACS10086100250399F72A9EADB42C90C3ECF7F0CS1008710025093031FDEA588F88E83951270CCS10088100250BA8061462D873705E95D5CB37CS10089100250D24188F88544EB121E963FD34CS10090100250D5F6A8BB081D8F383825A4DCACS100911002500FA4A205F0D76088D08EAF267CS10092100250272E909FAEBC65215E263E258CS100931002503370F35A674922828465FC816CS1009410025054EF96116D4A0C8DB0E07101FCS10095100250DE347C7B27FADC48EF1826A2BCS1009610025001B16ECA6FC343AE08C5B8944CS100971002501854DB743500EE94D8FC768EDCS1009810025028E40C684C87370CD0597FAB41002505E42C19717093353BCAAF403310025064310BAD8EB5B36E38646AF01BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBCS10099BBCS100100BBTable 22: Secondary code sequences (Part 2)8.4.2 Secondary codes assignmentThe assignment of secondary codes of Par.
8.4.1 to the signal components is according toTable 22.For the 4, 20 and 25 bit secondary codes the same code is used for all associated primarycodes. For the 100 bit codes, an independent secondary code is assigned for each primarycode.430H431H©, 2006, European Space Agency / Galileo Joint UndertakingDocument subject to terms of use and disclaimers p. 2-4.Signal ComponentE5a-IE5a-QE5b-IE5b-QE6-BE6-CE1-BE1-CReference:Issue:Revision:Date:GAL OS SIS ICD/D.0Draft023/05/2006Page45Secondary code assignmentCS201CS1001-50CS41CS10051-100–CS1001-50–CS251BBBBBBBBBBBBTable 23: Secondary code assignment8.5 CODE ASSIGNMENTS TO SATELLITESAssignment of primary and secondary code numbers to satellites will be published in a futureupdate of this ICD.©, 2006, European Space Agency / Galileo Joint UndertakingDocument subject to terms of use and disclaimers p.
2-4.Reference:Issue:Revision:Date:GAL OS SIS ICD/D.0Draft023/05/2006Page469. GALILEO MESSAGE STRUCTURE9.1GENERAL MESSAGE FORMAT SPECIFICATION9.1.1 General Navigation Message ContentThe Galileo signal-in-space data channels transmit different message types according to thegeneral contents identified in Table 23 below.• F/NAV is the acronym for Freely Accessible Navigation message type• I/NAV is the acronym for Integrity Navigation message type432HMessagetypeServicesChannel(s)F/NAVOSI/NAVOS/CS/SOLE5A-IE5B-IE1-BTable 24: Message allocation and general data content9.1.2 General Navigation Message structure9.1.2.1 Message Data FramesThe complete navigation message data is transmitted on each data channel as a sequence offrames.A frame is composed of several sub-frames, and a sub-frame in turn is composed of severalpages.
The page is the basic structure for building the navigation message.This arrangement allows accomplishing the three different main categories of data to betransmitted, which are repeated at fast (for urgent data, such as integrity), medium (like datarequired for warm start TTF) and slow rates (like data required for cold start TTF), thecorresponding page, sub-frame and frame are used.9.1.2.2 Page StructureThe general layout of a page is presented in Figure 13:43HSynchronisationPage symbolsTotal[symbols]NMN+MData pageM/2Total [bits]M/2Figure 13: General page layoutwhere:©, 2006, European Space Agency / Galileo Joint UndertakingDocument subject to terms of use and disclaimers p.
2-4.-Reference:Issue:Revision:Date:GAL OS SIS ICD/D.0Draft023/05/2006Page47The symbol page starts with a page synchronisation field, which contains a fixedsynchronization pattern (unique word of N symbols, N depending on the page type),as shown in Table 24, allowing the receiver to achieve synchronisation to the pageboundary. This synchronisation pattern is applied as unencoded data symbols at thetransmitterThe page symbols field is the result of the channel encoding process of the data page(FEC encoding and interleaving as presented in Par. 9.1.4).43H-435HMessageTypeF/NAVI/NAVServicesOSOSNumber ofSymbols1210Frame BitAllocation65Binary Pattern (TBC)1011011100000101100000Table 25: Synchronisation patterns9.1.3 Bit and byte ordering criteriaAll data values are encoded using the following bit and byte ordering criteria: For numbering, the most significant bit/byte is numbered as bit/byte 0. For bit/byte ordering, the most significant bit/byte is transmitted first.9.1.4 FEC Coding and Interleaving Parameters9.1.4.1 FEC encoding and Viterbi decodingThe convolutional encoding for all data channels is performed according to the parametersgiven in Table 25.436HCode ParameterCoding rateCoding schemeConstraint lengthValue½Convolutional7G1=171oGeneratorpolynomialsG2=133oEncoding sequenceG1 then G2Table 26: Data coding parametersFigure 14 depicts the convolutional coding scheme.437H©, 2006, European Space Agency / Galileo Joint UndertakingDocument subject to terms of use and disclaimers p.
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
