1、BSI Standards PublicationBS EN 16603-50-03:2014Space engineering Spacedata links Telemetry transferframe protocolBS EN 16603-50-03:2014 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of EN16603-50-03:2014.The UK participation in its preparation was entrusted to Techn
2、icalCommittee ACE/68, Space systems and operations.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. The British St
3、andards Institution 2014. Published by BSI StandardsLimited 2014ISBN 978 0 580 84100 2ICS 49.140Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 30 September 2014.A
4、mendments issued since publicationDate Text affectedBS EN 16603-50-03:2014EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 16603-50-03 September 2014 ICS 49.140 English version Space engineering - Space data links - Telemetry transfer frame protocol Ingnierie spatiale - Liaisons des donnes spati
5、ales - Protocole trame de transfert de tlmesure Raumfahrtproduktsicherung - Telemetriebertragungs-Rahmen-Protokoll This European Standard was approved by CEN on 11 April 2014. CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giv
6、ing this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to any CEN and CENELEC member. This European Standard exists
7、in three official versions (English, French, German). A version in any other language made by translation under the responsibility of a CEN and CENELEC member into its own language and notified to the CEN-CENELEC Management Centre has the same status as the official versions. CEN and CENELEC members
8、 are the national standards bodies and national electrotechnical committees of Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malt
9、a, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2014 CEN/CENELEC All rights of exploitation in any form and by any means reserved worldwide for CEN national
10、Members and for CENELEC Members. Ref. No. EN 16603-50-03:2014 EBS EN 16603-50-03:2014EN 16603-50-03:2014 (E) 2 Table of contents Foreword 4 1 Scope . 5 2 Normative references . 6 3 Terms, definitions and abbreviated terms 7 3.1 Terms from other standards 7 3.2 Terms specific to the present standard
11、. 7 3.3 Abbreviated terms. 8 3.4 Conventions 8 3.4.1 bit 0, bit 1, bit N1 . 8 3.4.2 most significant bit. 8 3.4.3 use of capitals for the names of data structures and fields 8 4 Overview 9 4.1 General . 9 4.2 Physical channel . 9 4.3 Master channels and virtual channels . 10 4.4 Sharing transmission
12、 resources 10 4.5 Data fields in the frame . 10 5 TM Transfer Frame . 11 5.1 General . 11 5.2 Transfer Frame Primary Header . 13 5.2.1 General . 13 5.2.2 Master Channel Identifier 14 5.2.3 Virtual Channel Identifier . 15 5.2.4 Operational Control Field Flag 15 5.2.5 Master Channel Frame Count . 15 5
13、.2.6 Virtual Channel Frame Count 16 5.2.7 Transfer Frame Data Field Status . 16 5.3 Transfer Frame Secondary Header 19 5.3.1 General . 19 BS EN 16603-50-03:2014EN 16603-50-03:2014 (E) 3 5.3.2 Transfer Frame Secondary Header Identification 20 5.3.3 Transfer Frame Secondary Header Data Field 21 5.3.4
14、Extended virtual channel frame count . 21 5.4 Transfer Frame Data Field 22 5.4.1 Overview . 22 5.4.2 General . 22 5.4.3 Packet processing and extraction functions 23 5.4.4 Asynchronously inserted data . 26 5.5 Operational Control Field 27 5.5.1 General . 27 5.5.2 Type Flag 27 5.5.3 Type-1-Report . 2
15、7 5.5.4 Type-2-Report . 28 5.6 Frame Error Control Field . 28 5.6.1 General . 28 5.6.2 Frame Error Control Field encoding procedure . 29 5.6.3 Frame Error Control Field decoding procedure . 30 Annex A (informative) Frame error control . 31 Annex B (informative) Changes from ESA-PSS-04-106 . 33 Annex
16、 C (informative) Differences from CCSDS recommendations . 36 Annex D (informative) Mission configuration parameters . 37 Bibliography . 42 Figures Figure 3-1: Bit numbering convention . 8 Figure 5-1: TM Transfer Frame format . 13 Figure 5-2: Format of Transfer Frame Primary Header . 14 Figure A-1 :
17、Encoder 31 Figure A-2 : Decoder 32 Tables Table 5-1: Major fields in a TM Transfer Frame . 11 Table B-1: Differences in names from ESA-PSS-04-106 for fields in a Telemetry Transfer Frame 35 Table B-1 : Differences in names from ESA-PSS-04-106 for fields in a Telemetry Transfer Frame 35 BS EN 16603-5
18、0-03:2014EN 16603-50-03:2014 (E) 4 Foreword This document (EN 16603-50-03:2014) has been prepared by Technical Committee CEN/CLC/TC 5 “Space”, the secretariat of which is held by DIN. This standard (EN 16603-50-03:2014) originates from ECSS-E-ST-50-03C. This European Standard shall be given the stat
19、us of a national standard, either by publication of an identical text or by endorsement, at the latest by March 2015, and conflicting national standards shall be withdrawn at the latest by March 2015. Attention is drawn to the possibility that some of the elements of this document may be the subject
20、 of patent rights. CEN and/or CENELEC shall not be held responsible for identifying any or all such patent rights. This document has been prepared under a mandate given to CEN by the European Commission and the European Free Trade Association. This document has been developed to cover specifically s
21、pace systems and has therefore precedence over any EN covering the same scope but with a wider domain of applicability (e.g. : aerospace). According to the CEN-CENELEC Internal Regulations, the national standards organizations of the following countries are bound to implement this European Standard:
22、 Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
23、Sweden, Switzerland, Turkey and the United Kingdom. BS EN 16603-50-03:2014EN 16603-50-03:2014 (E) 5 1 Scope This Standard contains the definition for Telemetry Transfer Frames which are fixed-length data structures, suitable for transmission at a constant frame rate on a space data channel. The Tele
24、metry Transfer Frame provides a standardized data structure for the transmission of space-acquired data over a telemetry space data link. Usually, the source of the data is located in space and the receiver is located on the ground. However, this Standard may also be applied to space-to-space teleme
25、try data links. Further provisions and guidance on the application of this standard can be found, respectively, in the following publications: The higher level standard ECSS-E-ST-50, Communications, which defines the principle characteristics of communication protocols and related services for all c
26、ommunication layers relevant for space communication (physical- to application-layer), and their basic relationship to each other. The handbook ECSS-E-HB-50, Communications guidelines, which provides information about specific implementation characteristics of these protocols in order to support the
27、 choice of a certain communications profile for the specific requirements of a space mission Users of this present standard are invited to consult these documents before taking decisions on the implementation of the present one. This standard may be tailored for the specific characteristics and cons
28、traints of a space project in conformance with ECSS-S-ST-00. BS EN 16603-50-03:2014EN 16603-50-03:2014 (E) 6 2 Normative references The following normative documents contain provisions which, through reference in this text, constitute provisions of this ECSS Standard. For dated references, subsequen
29、t amendments to, or revisions of any of these publications, do not apply. However, parties to agreements based on this ECSS Standard are encouraged to investigate the possibility of applying the most recent editions of the normative documents indicated below. For undated references the latest editio
30、n of the publication referred to applies. EN reference Reference in text Title EN 16601-00-01 ECSS-S-ST-00-01 ECSS system Glossary of terms EN 16603-50-01 ECSS-E-ST-50-01 Space engineering Space data links Telemetry synchronization and channel coding EN 16603-50-04 ECSS-E-ST-50-04 Space engineering
31、Space data links Telecommand protocols, synchronization and channel coding CCSDS 133.0-B-1 Space Packet Protocol Blue Book, Issue 1, September 2003 CCSDS 135.0-B-3 Space Link Identifiers Blue Book, Issue 3, October 2006 BS EN 16603-50-03:2014EN 16603-50-03:2014 (E) 7 3 Terms, definitions and abbrevi
32、ated terms 3.1 Terms from other standards For the purpose of this Standard, the terms and definitions from ECSS-ST-00-01 apply. 3.2 Terms specific to the present standard 3.2.1 idle data data which carries no information, but is sent to conform to timing or synchronization requirements NOTE The bit
33、pattern of idle data is not specified. 3.2.2 mission phase period of a mission during which specified telemetry characteristics are fixed NOTE The transition between two consecutive mission phases can cause an interruption of the telemetry services. 3.2.3 octet group of eight bits NOTE 1 The numberi
34、ng for octets within a data structure starts with 0. NOTE 2 Refer to clause 3.4 for the convention for the numbering of bits. 3.2.4 packet variable-length data structure consisting of higher layer user data encapsulated within standard header information 3.2.5 static unchanged within a specific virt
35、ual channel or within a specific master channel NOTE This Standard contains requirements on the invariability, throughout one or all mission phases, of certain characteristics of the data structures specified in it. BS EN 16603-50-03:2014EN 16603-50-03:2014 (E) 8 3.3 Abbreviated terms For the purpos
36、e of this Standard, the abbreviated terms from ECSS-ST-00-01 and the following apply: Abbreviation Meaning ASM attached sync marker CCSDS Consultative Committee for Space Data Systems FECF Frame Error Control Field MSB most significant bit TM Telemetry 3.4 Conventions 3.4.1 bit 0, bit 1, bit N1 To i
37、dentify each bit in an N-bit field, the first bit in the field to be transferred (i.e. the most left justified in a graphical representation) is defined as bit 0; the following bit is defined as bit 1 and so on up to bit N-1. Figure 3-1: Bit numbering convention 3.4.2 most significant bit When an N-
38、bit field is used to express a binary value (such as a counter), the most significant bit is the first bit of the field, i.e. bit 0 (see Figure 3-1). 3.4.3 use of capitals for the names of data structures and fields In this Standard initial capitals are used for the names of data structures and fiel
39、ds. This enables field names to be easily identified in the surrounding text. For example, the field Transfer Frame Data Field is easier to see than transfer frame data field in text containing words such as frame and data and field. It also prevents ambiguity over where the name begins and ends. Fo
40、r example, there are fields Transfer Frame Secondary Header and Transfer Frame Secondary Header Length. The capitals help the reader to distinguish between the Transfer Frame Secondary Header length (meaning the length of the Transfer Frame Secondary Header) and the Transfer Frame Secondary Header L
41、ength (meaning the field of that name). BS EN 16603-50-03:2014EN 16603-50-03:2014 (E) 9 4 Overview 4.1 General The Telemetry Transfer Frame is a fixed-length data structure that provides an envelope for transmitting data units of several types over a telemetry space link. The frame is compatible wit
42、h the ECSS standard for telemetry synchronization and channel coding defined in ECSS-E-ST-50-01. The telemetry transfer frame protocol can operate in various configurations of the telemetry space link, depending on the telemetry channel coding scheme and security options selected. The correct operat
43、ion of the protocol can only occur if a high-quality data channel is provided between the peer entities of the protocol. NOTE 1 The Standard for telemetry channel coding, ECSS-E-ST-50-01, defines the coding mechanisms for a high-quality data channel, including frame synchronization and randomization
44、. CCSDS 350.0-G-2 describes the security options. NOTE 2 In this Standard the terms TM Transfer Frame and Telemetry Transfer Frame are used interchangeably, i.e. they are synonyms and have the same meaning as. NOTE 3 Annex D describes the mission configuration parameters within the scope of this Sta
45、ndard. 4.2 Physical channel A data channel carrying a stream of bits in a single direction is referred to as a physical channel. For the TM Transfer Frame specified in this Standard, the value of the Transfer Frame Version Number is constant for all frames of a physical channel. The length of the fr
46、ames for a given physical channel is fixed for a mission phase. BS EN 16603-50-03:2014EN 16603-50-03:2014 (E) 10 4.3 Master channels and virtual channels The TM Transfer Frame supports the division of the physical channel into master channels and virtual channels by means of identifier fields in the
47、 frame header. A master channel is identified by the values of the Transfer Frame Version Number and the Spacecraft Identifier. Within a given physical channel, a master channel consists of all the frames that have the same Transfer Frame Version Number and the same Spacecraft Identifier. For a typi
48、cal space mission, all the frames on a physical channel have the same value for the Spacecraft Identifier, so in this case there is one master channel on the physical channel. However, multiple master channels can share a physical channel, which, for example, can be the case when one spacecraft is t
49、ransporting another spacecraft such as a probe. A master channel is divided into virtual channels using the Virtual Channel Identifier field. This is a 3-bit field and therefore supports up to eight virtual channels on a master channel. 4.4 Sharing transmission resources Virtual channels enable one physical channel to be shared among multiple higher-layer data streams, each of which can have different characteristics. The mechanisms and parameters for sharing access by the virtual channels to the physical channel are implementation dependent and not within
