EN 16603-50-25:2022

SLOVENSKI STANDARD
01-september-2022
Nadomešča:
SIST EN 16603-50-04:2015
Vesoljska tehnika - Sprejem obvestila CCSDS 232.0-B-3, protokol vesoljske
podatkovne povezave TC
Space engineering - Adoption Notice of CCSDS 232.0-B-3, TC Space Data Link Protocol
Raumfahrttechnik - Adaption CCSDS 232.0-B-3, Telekommando-Weltraum-
Datenübertragungsprotokoll
Ingénierie spatiale - Notice d’adoption de la CCSDS 232.0-B-3, TC Space Data Link
Protocol
Ta slovenski standard je istoveten z: EN 16603-50-25:2022
ICS:
49.140 Vesoljski sistemi in operacije Space systems and
operations
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN 16603-50-25

NORME EUROPÉENNE
EUROPÄISCHE NORM
July 2022
ICS 49.140
Supersedes EN 16603-50-04:2014
English version
Space engineering - Adoption Notice of CCSDS 232.0-B-3,
TC Space Data Link Protocol
Ingénierie spatiale - Notice d'adoption de la CCSDS Raumfahrttechnik - Adaption CCSDS 232.0-B-3,
232.0-B-3, TC Space Data Link Protocol Telekommando-Weltraum-
Datenübertragungsprotokoll
This European Standard was approved by CEN on 13 March 2022.

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, France, Germany, Greece, Hungary, Iceland, Ireland, Italy,
Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia,
Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.

CEN-CENELEC Management Centre:
Rue de la Science 23, B-1040 Brussels
© 2022 CEN/CENELEC All rights of exploitation in any form and by any means
Ref. No. EN 16603-50-25:2022 E
reserved worldwide for CEN national Members and for
CENELEC Members.
Table of contents
European Foreword . 3
1 Scope . 4
2 Context information. 5
3 Abbreviated terms . 6
4 Application requirements . 7
Bibliography . 19

Tables
Table 4-1: Applicability table for CCSDS 232.0-B-3 . 7

European Foreword
This document (EN 16603-50-25:2022) has been prepared by Technical Committee CEN-
CENELEC/TC 5 “Space”, the secretariat of which is held by DIN.
This standard (EN 16603-50-25:2022) originates from ECSS-E-AS-50-25C.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by January 2023, and conflicting national standards shall
be withdrawn at the latest by January 2023.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
EN 16603-50-24, EN 16603-50-25 and EN 16603-50-26 together supersede EN16603-50-04:2014.
The main changes with respect to EN16603-50-04:2014 are listed below:
- Replacement of document by three Adoption Notices.
This document has been prepared under a standardization request given to CEN by the European
Commission and the European Free Trade Association.
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, Serbia, Slovakia, Slovenia,
Spain, Sweden, Switzerland, Turkey and the United Kingdom.
Scope
This document identifies the clauses and requirements modified with respect to
the standard CCSDS 232.0-B-3, TC Space Data Link Protocol, Issue 3, September
2015 for application in ECSS.
Context information
In the standard CCSDS 232.0-B-3, TC Space Data Link Protocol, CCSDS specifies a
data link layer protocol for the efficient transfer of space application data of
various types and characteristics over ground-to-space links. The
Communications Operation Procedure-1 (COP-1) specified in CCSDS 232.1-B-2
is used with the TC Space Data Link Protocol: it provides a mechanism for
delivery of frames in sequence and without gaps or duplication.
This Adoption Notice adopts and applies CCSDS 232.0-B-3 with a minimum set
of modifications, identified in the present document, to allow for reference and
for a consistent integration in the ECSS system of standards.
The TC Transfer Frame specified in CCSDS 232.0-B-3 is similar to the TC
Transfer Frame specified in clauses 5 (Segmentation sublayer) and 6 (Transfer
sublayer) in the EN 16603-50-04:2014 (ECSS-E-ST-50-04) Space data links –
Telecommand protocols synchronization and channel coding.
EN 16603-50-04:2014 (ECSS-E-ST-50-04) is superseded by the following three
Adoption Notices: EN 16603-50-24 (ECSS-E-ST-50-24), EN 16603-50-25 (ECSS-E-
AS-50-25) and EN 16603-50-26 (ECSS-E-AS-50-26).
Differences between these two standards that are not covered by the normative
modifications in clause 4 are described in the informative Annex A.

Overview of superseded EN 16603-50-xx Standards
Superseded EN New EN Based on CCSDS
EN 16603-50-01:2014 EN 16603-50-21 CCSDS 131.0-B-3 (Sept. 2017)
EN 16603-50-03:2014 EN 16603-50-22 CCSDS 132.0-B-2 (Sept. 2015)
EN 16603-50-23 CCSDS 732.0-B-3 (Sept. 2015)
EN 16603-50-04:2014 EN 16603-50-24 CCSDS 231.0-B-3 (Sept. 2017)
EN 16603-50-25 CCSDS 232.0-B-3 (Sept. 2015)
EN 16603-50-26 CCSDS 232.1-B-2 (Sept. 2010)

Abbreviated terms
Abbreviation Meaning
Communications Operation Procedure
COP
Frame Acceptance and Reporting Mechanism
FARM
Frame Data Unit
FDU
Global Virtual Channel Identifier
GVCID
Space Data Link Security
SDLS
Application requirements
a. CCSDS 232.0-B-3, TC Space Data Link Protocol, Issue 3, September 2015 shall apply with the following modifications listed in Table 4-1.
Table 4-1: Applicability table for CCSDS 232.0-B-3
Clause or Applicability Applicable text Comments Text as in the original
requirement document
(the new/added text is underlined)
number
(deleted text with strikethrough)
4.1.1b Modified Transfer Frame Data Field (up to 1017 CCSDS requirement modified: Transfer Frame Data Field (up to
octets, mandatory); 1019 or 1017 octets, mandatory);
number “1019” deleted
4.1.1c Modified Frame Error Control Field (2 octets, CCSDS requirement modified: Frame Error Control Field (2 octets,
mandatory). word “optional” replaced by the optional).
word “mandatory.”
4.1.3.2.1.4 Modified NOTE 1 CCSDS existing NOTE is given a NOTE
new number – the content of the
(renumbered
note is unchanged
NOTE)
4.1.3.2.1.4 Modified NOTE 2 – If the Packet Assembly New NOTE is added
Controller Function specified in 4.4.9 is
(new NOTE)
used, there can be Frame Data Units that
carry a MAP Reset command. In this case,
the Frame Data Unit consists of a Segment
Header only and the User Data field is
absent. See 4.4.9.4.
4.1.4.1.1 Modified Requirement deleted The Frame Error Control Field is
optional; its presence or absence
(deleted
shall be established by
requirement)
management.
4.1.4.1.2 Modified The Frame Error Control Field shall occupy CCSDS requirement modified: If present, the Frame Error Control
the two octets following, without gap, the words “if present” deleted. Field shall occupy the two octets
Transfer Frame Data Field. following, without gap, the
Transfer Frame Data Field.
4.1.4.1.3 Modified Requirement deleted If present, the Frame Error Control
Field shall occur within every
(deleted
Transfer Frame transmitted within
requirement)
the same Physical Channel
throughout a Mission Phase.
Note 2, below Modified NOTE deleted Whether this field should be used
4.1.4.1.3 on a particular Physical Channel
(deleted NOTE)
will be determined based on the
mission requirements for data
quality and the selected options for
the underlying Channel Coding
Sublayer.
Note 1 in Modified The No Bit Lock Flag provides a CCSDS requirement modified: The No Bit Lock Flag is an optional,
4.2.1.8.3.1 performance quality indicator that indicates words “mission specific mission-specific engineering
(modified NOTE)
specifically whether the Physical Layer is engineering measurement that” measurement that provides a
working normally by having enough signal deleted. performance quality indicator that
energy to achieve bit synchronization with indicates specifically whether the
the received data stream. Physical Layer is working normally
by having enough signal energy to
achieve bit synchronization with
the received data stream.
4.2.1.8.3.2 Modified The No Bit Lock Flag shall be set as follows: CCSDS requirement modified to Use of the No Bit Lock Flag is
‘0’ when at least one of the spacecraft refer to spacecraft demodulation optional; if used,
demodulation units for the physical units for the physical channel. a) ‘0’ shall indicate bit lock has been
channel has achieved bit lock; Sentences “Use of the No Bit Lock achieved;
‘1’ when none of the spacecraft Flag is optional; if used, b) ‘1’ shall indicate bit lock has not
demodulation units for the physical a) ‘0’ shall indicate bit lock has been achieved.
channel has achieved bit lock. been achieved;
b) ‘1’ shall indicate bit lock has
not been achieved.”deleted.
4.2.1.8.3.3 Modified The No Bit Lock Flag shall always carry an CCSDS requirement modified to The single No Bit Lock Flag shall
actual report of the status of the physical refer to actual report of the status apply to all Virtual Channels and
channel, even when other fields in the of the physical channel. Sentense shall be updated whenever a
CLCW report the status of an inactive “The single No Bit Lock Flag shall change is signaled by the Physical
virtual channel. apply to all Virtual Channels and Layer.
shall be updated whenever a
change is signaled by the Physical
Layer”. deleted.
4.2.1.8.3.4 Modified Requirement deleted If the No Bit Lock Flag is not used,
it shall be set permanently to ‘0’.
(deleted
requirement)
4.4.1.6 (new) New requirement When extracting and reconstructing New requirement added:
Packets from Frame Data Units, the Packet
added the Packet Assembly
Assembly Controller Function specified in
Controller
4.4.9 may be used.
4.4.2.5 (new) New requirement When extracting and reconstructing New requirement added:
MAP_SDUs from Frame Data Units, the
added the Packet Assembly
Packet Assembly Controller Function
Controller
specified in 4.4.9 may be used.
4.4.9 New section Packet Assembly Controller Function New section with new
requirements added (4.4.9)
4.4.9.1 New Overview New
The Packet Assembly Controller Function
can be used by the MAP Packet Extraction
Function to reassemble Packets and by the
MAP Reception Function to reassemble
MAP_SDUs.
The Packet Assembly Controller Function
includes the handling of exceptions. When
the function detects an exception it enters a
lockout state. In the lockout state, it does
not reassemble or deliver Packets or
MAP_SDUs. When it receives a valid MAP
Reset command, the Packet Assembly
Controller Function exits lockout state.
Despite the word “packet” in its name, the
function can be used for Packets and for
MAP_SDUs: the name is inherited from
earlier standards.
4.4.9.2 New MAP Identifiers for the Packet Assembly
Controller Function
4.4.9.2.1 New requirement Each instance of the Packet Assembly
Controller Function shall use a pair of MAP
Identifiers with the following properties:
a) The pair of MAP Identifiers identifies
one MAP for data and one MAP for control.
b) The MAP Identifier for the data MAP has
the most significant bit set to ‘0’.
c) The MAP Identifier for the control MAP
has the same value as the data MAP except
that the most significant bit is set to ‘1’.
NOTE The MAP Identifier is a 6-bit
value. T
...