1、BSI Standards PublicationBS EN 16603-50-53:2015Space engineering SpaceWire CCSDS packettransfer protocolBS EN 16603-50-53:2015 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of EN16603-50-53:2015.The UK participation in its preparation was entrusted to TechnicalCommi
2、ttee 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 Standards I
3、nstitution 2015. Published by BSI StandardsLimited 2015ISBN 978 0 580 86757 6ICS 33.040.40; 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 28 February 2015.
4、Amendments issued since publicationDate Text affectedBS EN 16603-50-53:2015EUROPEAN STANDARD NORME EUROPENNE EUROPISCHE NORM EN 16603-50-53 January 2015 ICS 33.040.40; 49.140 English version Space engineering - SpaceWire - CCSDS packet transfer protocol Ingnierie spatiale - SpaceWire - protocole de
5、transfert de paquets CCSDS Raumfahrtproduktsicherung - SpaceWire - Protokoll zur CCSDS-Paketbertragung This European Standard was approved by CEN on 23 November 2014. CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this
6、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 in three
7、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 are the
8、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, Malta, Nether
9、lands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom. CEN-CENELEC Management Centre: Avenue Marnix 17, B-1000 Brussels 2015 CEN/CENELEC All rights of exploitation in any form and by any means reserved worldwide for CEN national Members a
10、nd for CENELEC Members. Ref. No. EN 16603-50-53:2015 EBS EN 16603-50-53:2015EN 16603-50-53:2015 (E) 2 Table of contents Foreword 4 1 Scope . 5 2 Normative references . 6 3 Terms, definitions and abbreviated terms 7 3.1 Terms defined in other standards . 7 3.2 Terms specific to the present standard .
11、 7 3.3 Abbreviated terms. 7 3.4 Conventions 7 4 Principles 8 4.1 Purpose 8 4.2 Protocol features 8 4.3 Services 9 4.4 Guide to this document . 10 5 Requirements 11 5.1 Service parameters . 11 5.1.1 CCSDS packet 11 5.1.2 Packet length 11 5.1.3 Status code . 11 5.1.4 Target SpaceWire Address . 11 5.1.
12、5 Target Logical Address . 12 5.1.6 User Application Value 12 5.2 Service primitives 12 5.2.1 CCSDS Packet Transfer Service . 12 5.2.2 CCSDS_PACKET_SEND.request . 12 5.2.3 CCSDS_PACKET_RECEIVED.indication . 13 5.3 CCSDS Packet Transfer Protocol fields 14 5.3.1 Target SpaceWire Address field 14 5.3.2
13、 Target Logical Address field 14 5.3.3 Protocol Identifier field . 14 BS EN 16603-50-53:2015EN 16603-50-53:2015 (E) 3 5.3.4 Reserved field . 14 5.3.5 User Application field 14 5.3.6 Packet field . 15 5.4 CCSDS Packet Transfer Protocol format 15 5.5 CCSDS Packet Transfer Protocol Action 16 5.5.1 Over
14、view . 16 5.5.2 Send request . 16 5.5.3 Transfer packet . 17 5.5.4 Receive indication . 17 Annex A (informative) Managed parameters 19 Bibliography . 20 Figures Figure 4-1: Protocol configuration . 8 Figure 5-1: Encapsulated CCSDS Packet format . 15 Figure 5-2: CCSDS Packet Transfer Protocol Packet
15、Transfer . 16 BS EN 16603-50-53:2015EN 16603-50-53:2015 (E) 4 Foreword This document (EN 16603-50-53:2015) has been prepared by Technical Committee CEN/CLC/TC 5 “Space”, the secretariat of which is held by DIN. This standard (EN 16603-50-53:2015) originates from ECSS-E-ST-50-53C. This European Stand
16、ard shall be given the status of a national standard, either by publication of an identical text or by endorsement, at the latest by July 2015, and conflicting national standards shall be withdrawn at the latest by July 2015. Attention is drawn to the possibility that some of the elements of this do
17、cument may be the subject 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 develope
18、d to cover specifically space 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 implemen
19、t this European Standard: 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, Sl
20、ovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. BS EN 16603-50-53:2015EN 16603-50-53:2015 (E) 5 1 Scope There is a number of communication protocols that can be used in conjunction with the SpaceWire Standard (ECSS-E-ST-50-12), to provide a comprehensive set of services
21、for onboard user applications. To distinguish between the various protocols a protocol identifier is used, as specified in ECSS-E-ST-50-51. This Standard specifies the CCSDS packet transfer protocol, which is one of these protocols that works over SpaceWire. The aim of the CCSDS Packet Transfer Prot
22、ocol is to transfer CCSDS Packets across a SpaceWire network. It does this by encapsulating the CCSDS Packet in a SpaceWire packet, transferring it across the SpaceWire network and then extracting the CCSDS Packet at the target. This standard may be tailored for the specific characteristic and const
23、rains of a space project in conformance with ECSS-S-ST-00. BS EN 16603-50-53:2015EN 16603-50-53:2015 (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, subsequent
24、amendments to, or revision 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 more recent editions of the normative documents indicated below. For undated references, the latest edition o
25、f 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-12 ECSS-E-ST-50-12 Space engineering - SpaceWire - Links, nodes, routers and networks EN 16603-50-51 ECSS-E-ST-50-51 Space engineering - SpaceWire pr
26、otocol identification CCSDS 133.0-B-1 Space Packet Protocol, Blue Book BS EN 16603-50-53:2015EN 16603-50-53:2015 (E) 7 3 Terms, definitions and abbreviated terms 3.1 Terms defined in other standards For the purpose of this Standard, the terms and definitions from ECSS-S-ST-00-01 and ECSS-E-ST-50-51
27、apply. 3.2 Terms specific to the present standard None. 3.3 Abbreviated terms The following abbreviations are defined and used within this standard: Abbreviation Meaning CCSDS Consultative Committee for Space Data Systems EEP error end of packet EOP end of packet SpW SpaceWire 3.4 Conventions In thi
28、s document hexadecimal numbers are written with the prefix 0x, for example 0x34 and 0xDF15. Binary numbers are written with the prefix 0b, for example 0b01001100 and 0b01. Decimal numbers have no prefix. BS EN 16603-50-53:2015EN 16603-50-53:2015 (E) 8 4 Principles 4.1 Purpose The CCSDS Packet Transf
29、er Protocol has been designed to encapsulate a CCSDS Space Packet into a SpaceWire packet, transfer it from an initiator to a target across a SpaceWire network, extract it from the SpaceWire packet and pass it to a target user application. This protocol does not provide any means for ensuring delive
30、ry of the packet nor is it responsible for the contents of the packet being a CCSDS Space Packet. The CCSDS Space Packet Protocol is defined in the following document: CCSDS 133.0-B-1 Space Packet Protocol. Blue Book. Issue 1. September 2003 or a later issue Figure 4-1 illustrates the location of th
31、e CCSDS Space Packet transfer Protocol in a typical onboard protocol stack. The CCSDS Space Packet transfer Protocol provides a unidirectional data transfer service from a single source user application to a single destination user application through a SpaceWire network. CCSDS Space packetTransfer
32、Protocol User ApplicationSpaceWire NetworkSpaceWire NetworkCCSDS Space packetTransfer Protocol User ApplicationFigure 4-1: Protocol configuration 4.2 Protocol features The CCSDS Space Packet transfer Protocol provides the capability to transfer CCSDS Space Packets between onboard users of a SpaceWir
33、e network. The CCSDS space packets may be of variable length or fixed size at the discretion of the user and may be submitted for transmission at variable intervals. The BS EN 16603-50-53:2015EN 16603-50-53:2015 (E) 9 composition of the CCSDS space packet is under the responsibility of the user appl
34、ication and is not checked by the CCSDS space packet transfer protocol. 4.3 Services The CCSDS Space Packet Transfer Protocol provides users with data transfer services. The point at which a service is provided by a protocol entity to a user is called a Service Access Point. A Service Access Point o
35、f the Space Packet Transfer Protocol is identified by a SpaceWire address and each service user is also identified by a SpaceWire Address. Service data units submitted to a Service Access Point are processed in the order of submission. Implementations may be required to perform flow control at a Ser
36、vice Access Point between the service user and the service provider. However, this standard does not recommend a scheme for flow control between the user and the provider. The followings features are offered by the data transfer service defined in this Standard: Unidirectional (one way) data transfe
37、r service. Asynchronous Service. There are no predefined timing rules for the transfer of service data units supplied by the service user. The user may request data transfer at any time it desires, but there may be restrictions imposed by the provider on the data generation rate. Unconfirmed Service
38、: the sending user does not receive confirmation from the receiving end that data has been received. Incomplete Services. The services do not guarantee completeness, nor do they provide a retransmission mechanism. SDU format: the service does not check the format of the submitted CCSDS Space packet.
39、 Non sequence Preserving Service. The sequence of service data units supplied by the sending user may not be preserved through the underlying network The end-to-end quality-of-service provided to service users is the one that is provided by the underlying SpaceWire network. The Space Packet Transfer
40、 Protocol does not provide any mechanisms for guaranteeing a particular quality-of-service; it is the responsibility of implementing organizations to ensure that the end-to-end performance of a particular service instance meets the requirements of its users. Sequence preservation of packets in a Spa
41、ceWire network is dependent on the underlying network topology and configuration. Topologies and configurations which allow only a single route from the source to the destination, i.e. configurations that are not using group adaptive routing, are sequence preserving. BS EN 16603-50-53:2015EN 16603-5
42、0-53:2015 (E) 10 4.4 Guide to this document Clause 4 presents the purpose, protocol features and an overview of the services the CCSDS packet transfer protocol offers. Clause 5.1 defines the service parameters. Clause 5.2 specifies the service primitives provided by the protocol. Clause 5.3 defines
43、the protocol fields used in the CCSDS packet transfer protocol packets. Clause 5.4 specifies the format of the packets used by the CCSDS packet transfer protocol. Clause 5.5 specified the action of the CCSDS packet transfer protocol. Annex A lists the managed parameters associated with this protocol
44、. BS EN 16603-50-53:2015EN 16603-50-53:2015 (E) 11 5 Requirements 5.1 Service parameters 5.1.1 CCSDS packet a. The CCSDS packet parameter, intended as the service data unit transferred by the CCSDS packet transfer service, shall be the CCSDS Space Packet as defined in CCSDS 133.0-B-1 Space Packet Pr
45、otocol, Blue Book, Issue 1, September 2003. 5.1.2 Packet length a. The value of the packet length shall be equal to at least 7 and at most 65542 octets. b. Individual project organizations may establish the maximum length for a particular mission. NOTE The length parameter defines the length of the
46、Data Unit submitted by the user. 5.1.3 Status code a. The Status code parameter shall be used to indicate the validity of the packet to the receiving service user. b. The Status code parameter shall take one of the following values: 1. 0x00 indicates that the packet is ok 2. 0x01 indicates packet ar
47、rived terminated by EEP 3. 0x02 indicates reserved field was non-zero 5.1.4 Target SpaceWire Address a. The Target SpaceWire Address parameter shall be used to define the path to the Target when SpaceWire path addressing is being used. BS EN 16603-50-53:2015EN 16603-50-53:2015 (E) 12 5.1.5 Target Lo
48、gical Address a. The Target Logical Address parameter shall be used to define the logical address of the Target that is to receive the CCSDS packet. 5.1.6 User Application Value a. The User Application Value shall be an 8-bit value which is transferred along with the CCSDS packet to the Target. NOTE
49、 Its value and use is user specific. 5.2 Service primitives 5.2.1 CCSDS Packet Transfer Service a. The service primitives associated with this service shall be the following 1. CCSDS_PACKET_SEND.request, 2. CCSDS_PACKET_RECEIVE.indication. 5.2.2 CCSDS_PACKET_SEND.request 5.2.2.1 Function a. At the initiator, the CCSDS Packet Transfer service user shall pass a CCSDS_PACKET_SEND.request primitive to the service provider to request that a CCSDS Packet is transferred to the user at the target across the SpaceWire network. 5.2.2.2 Semantics a. The CCSDS_PACKET.request primit
