EN 16603-50-53:2015

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Vesoljska tehnika - SpaceWire - Protokol za CCSDS-paketni prenosRaumfahrttechnik - SpaceWire - Protokoll zur CCSDS-PaketübertragungIngénierie spatiale - SpaceWire - protocole de transfert de paquets CCSDSSpace engineering - SpaceWire - CCSDS packet transfer protocol49.140Vesoljski sistemi in operacijeSpace systems and operations33.040.40Podatkovna komunikacijska omrežjaData communication networksICS:Ta slovenski standard je istoveten z:EN 16603-50-53:2015SIST EN 16603-50-53:2015en01-april-2015SIST EN 16603-50-53:2015SLOVENSKI
STANDARD
EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 16603-50-53
January 2015 ICS 33.040.40; 49.140
English version
Space engineering - SpaceWire - CCSDS packet transfer protocol
Ingénierie spatiale - SpaceWire - protocole de transfert de paquets CCSDS
Raumfahrtproduktsicherung - SpaceWire - Protokoll zur CCSDS-Paketübertragung 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 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 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 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, Netherlands, 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 and for CENELEC Members. Ref. No. EN 16603-50-53:2015 E SIST EN 16603-50-53:2015

Figures Figure 4-1: Protocol configuration . 8 Figure 5-1: Encapsulated CCSDS Packet format . 15 Figure 5-2: CCSDS Packet Transfer Protocol Packet Transfer . 16
This document has been developed 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 implement 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, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. SIST EN 16603-50-53:2015

This standard may be tailored for the specific characteristic and constrains of a space project in conformance with ECSS-S-ST-00. SIST EN 16603-50-53:2015

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 protocol identification
CCSDS 133.0-B-1 Space Packet Protocol, Blue Book
3.4 Conventions In this 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. SIST EN 16603-50-53:2015

CCSDS Space packetTransfer Protocol User ApplicationSpaceWire NetworkSpaceWire NetworkCCSDS Space packetTransfer Protocol User Application Figure 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 SpaceWire 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 SIST EN 16603-50-53:2015

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 of 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 Service 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 transfer 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: 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. • 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 qu
...