Recommendation for Space Data System Standards
SPACE COMMUNICATIONS
PROTOCOL SPECIFICATION (SCPS)—
TRANSPORT PROTOCOL
(SCPS-TP)
RECOMMENDED STANDARD
CCSDS 714.0-B-2
BLUE BOOK
October 2006
CCSDS RECOMMENDED STANDARD FOR SCPS TRANSPORT PROTOCOL (SCPS-TP)
AUTHORITY
Issue:
Date:
Location:
Recommended Standard, Issue 2
October 2006
Washington, DC, USA
This document has been approved for publication by the Management Council of the
Consultative Committee for Space Data Systems (CCSDS) and represents the consensus
technical agreement of the participating CCSDS Member Agencies. The procedure for
review and authorization of CCSDS Recommendations is detailed in the Procedures Manual
for the Consultative Committee for Space Data Systems, and the record of Agency
participation in the authorization of this document can be obtained from the CCSDS
Secretariat at the address below.
This document is published and maintained by:
CCSDS Secretariat
Office of Space Communication (Code M-3)
National Aeronautics and Space Administration
Washington, DC 20546, USA
CCSDS 714.0-B-2
Page i
October 2006
CCSDS RECOMMENDED STANDARD FOR SCPS TRANSPORT PROTOCOL (SCPS-TP)
STATEMENT OF INTENT
The Consultative Committee for Space Data Systems (CCSDS) is an organization officially
established by the management of its members. The Committee meets periodically to address
data systems problems that are common to all participants, and to formulate sound technical
solutions to these problems. Inasmuch as participation in the CCSDS is completely
voluntary, the results of Committee actions are termed Recommended Standards and are
not considered binding on any Agency.
This Recommended Standard is issued by, and represents the consensus of, the CCSDS
members. Endorsement of this Recommendation is entirely voluntary. Endorsement,
however, indicates the following understandings:
o Whenever a member establishes a CCSDS-related standard, this standard will be in
accord with the relevant Recommended Standard. Establishing such a standard
does not preclude other provisions which a member may develop.
o Whenever a member establishes a CCSDS-related standard, that member will
provide other CCSDS members with the following information:
-- The standard itself.
-- The anticipated date of initial operational capability.
-- The anticipated duration of operational service.
o Specific service arrangements shall be made via memoranda of agreement. Neither
this Recommended Standard nor any ensuing standard is a substitute for a
memorandum of agreement.
No later than five years from its date of issuance, this Recommended Standard will be
reviewed by the CCSDS to determine whether it should: (1) remain in effect without change;
(2) be changed to reflect the impact of new technologies, new requirements, or new
directions; or (3) be retired or canceled.
In those instances when a new version of a Recommended Standard is issued, existing
CCSDS-related member standards and implementations are not negated or deemed to be non-
CCSDS compatible. It is the responsibility of each member to determine when such
standards or implementations are to be modified. Each member is, however, strongly
encouraged to direct planning for its new standards and implementations towards the later
version of the Recommended Standard.
CCSDS 714.0-B-2
Page ii
October 2006
CCSDS RECOMMENDED STANDARD FOR SCPS TRANSPORT PROTOCOL (SCPS-TP)
FOREWORD
Through the process of normal evolution, it is expected that expansion, deletion, or
modification of this document may occur. This Recommendation is therefore subject to
CCSDS document management and change control procedures as defined in reference [B1].
Current versions of CCSDS documents are maintained at the CCSDS Web site:
http://www.ccsds.org/
Questions relating to the contents or status of this document should be addressed to the
CCSDS Secretariat at the address indicated on page i.
CCSDS 714.0-B-2
Page iii
October 2006
CCSDS RECOMMENDED STANDARD FOR SCPS TRANSPORT PROTOCOL (SCPS-TP)
At time of publication, the active Member and Observer Agencies of the CCSDS were:
Member Agencies
– Agenzia Spaziale Italiana (ASI)/Italy.
– British National Space Centre (BNSC)/United Kingdom.
– Canadian Space Agency (CSA)/Canada.
– Centre National d’Etudes Spatiales (CNES)/France.
– Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR)/Germany.
– European Space Agency (ESA)/Europe.
– Federal Space Agency (Roskosmos)/Russian Federation.
–
Instituto Nacional de Pesquisas Espaciais (INPE)/Brazil.
– Japan Aerospace Exploration Agency (JAXA)/Japan.
– National Aeronautics and Space Administration (NASA)/USA.
Observer Agencies
– Austrian Space Agency (ASA)/Austria.
– Belgian Federal Science Policy Office (BFSPO)/Belgium.
– Central Research Institute of Machine Building (TsNIIMash)/Russian Federation.
– Centro Tecnico Aeroespacial (CTA)/Brazil.
– Chinese Academy of Space Technology (CAST)/China.
– Commonwealth Scientific and Industrial Research Organization (CSIRO)/Australia.
– Danish Space Research Institute (DSRI)/Denmark.
– European Organization for the Exploitation of Meteorological Satellites
(EUMETSAT)/Europe.
Indian Space Research Organization (ISRO)/India.
Institute of Space Research (IKI)/Russian Federation.
– European Telecommunications Satellite Organization (EUTELSAT)/Europe.
– Hellenic National Space Committee (HNSC)/Greece.
–
–
– KFKI Research Institute for Particle & Nuclear Physics (KFKI)/Hungary.
– Korea Aerospace Research Institute (KARI)/Korea.
– MIKOMTEK: CSIR (CSIR)/Republic of South Africa.
– Ministry of Communications (MOC)/Israel.
– National Institute of Information and Communications Technology (NICT)/Japan.
– National Oceanic & Atmospheric Administration (NOAA)/USA.
– National Space Organization (NSPO)/Taipei.
– Space and Upper Atmosphere Research Commission (SUPARCO)/Pakistan.
– Swedish Space Corporation (SSC)/Sweden.
– United States Geological Survey (USGS)/USA.
CCSDS 714.0-B-2
Page iv
October 2006
CCSDS RECOMMENDED STANDARD FOR SCPS TRANSPORT PROTOCOL (SCPS-TP)
DOCUMENT CONTROL
Document
Title
CCSDS
714.0-B-1
CCSDS
714.0-B-2
Space Communications
Protocol Specification
(SCPS)—Transport Protocol
(SCPS-TP)
Space Communications
Protocol Specification
(SCPS)—Transport Protocol
(SCPS-TP), Recommended
Standard, Issue 2
Date
May
1999
October
2006
Status
Original issue, superseded
Current issue:
– adds optional support for
Selective Acknowledgements
(SACK) and Explicit
Congestion Notification
(ECN);
– defines semantics to extend
SCPS-TP signaling to allow
optional inclusion of vendor-
and community-specific
options;
– clarifies some ambiguities in
the original specification
regarding:
• inclusion/position of
compressed short-form
SNACK options in
compressed SCPS-TP
headers (the position of the
compressed SNACK option
within the header is given);
• what connection identifier is
transmitted in compressed
headers (the one sent to the
peer during the SYN
exchange);
• what N-user protocol ID is
used to calculate the pseudo
header checksum when
header compression is in
use (decimal 105).
NOTE – Revision bars in the inside margin indicate changes from the previous issue.
CCSDS 714.0-B-2
Page v
October 2006
CCSDS RECOMMENDED STANDARD FOR SCPS TRANSPORT PROTOCOL (SCPS-TP)
Section
Page
CONTENTS
1 INTRODUCTION.......................................................................................................... 1-1
1.1 PURPOSE............................................................................................................... 1-1
1.2 SCOPE.................................................................................................................... 1-1
1.3 APPLICABILITY................................................................................................... 1-1
1.4 RATIONALE.......................................................................................................... 1-1
1.5 ORGANIZATION OF THIS RECOMMENDATION........................................... 1-1
1.6 HOW TO READ THIS DOCUMENT ................................................................... 1-2
1.7 CONVENTIONS AND DEFINITIONS ................................................................ 1-3
1.8 REFERENCES ....................................................................................................... 1-7
2 OVERVIEW................................................................................................................... 2-1
3 SCPS-TP EXTENSIONS TO STANDARD TCP ....................................................... 3-1
3.1 RELATIONSHIP BETWEEN SCPS-TP AND TCP ............................................. 3-1
3.2 CONNECTION MANAGEMENT......................................................................... 3-1
3.3 DATA TRANSFER.............................................................................................. 3-11
3.4 ERROR RECOVERY........................................................................................... 3-16
3.5 SELECTIVE NEGATIVE ACKNOWLEDGMENT OPTION ........................... 3-19
3.6 SCPS-TP HEADER COMPRESSION................................................................. 3-25
3.7 MULTIPLE TRANSMISSIONS FOR FORWARD ERROR CORRECTION ... 3-31
4 USER DATAGRAM PROTOCOL EXTENSION ..................................................... 4-1
5 MANAGEMENT INFORMATION BASE (MIB) REQUIREMENTS.................... 5-1
5.1 TYPES OF MANAGEMENT INFORMATION ................................................... 5-1
5.2 MIB REQUIREMENTS FOR ROUTE-SPECIFIC INFORMATION .................. 5-1
5.3 MIB REQUIREMENTS FOR SCPS TRANSMISSION CONTROL PROTOCOL5-5
5.4 MIB REQUIREMENTS FOR SCPS USER DATAGRAM PROTOCOL ............ 5-7
6 CONFORMANCE REQUIREMENTS ....................................................................... 6-1
6.1 GENERAL REQUIREMENTS.............................................................................. 6-1
6.2 TRANSMISSION CONTROL PROTOCOL REQUIREMENTS......................... 6-1
6.3 USER DATAGRAM PROTOCOL REQUIREMENTS ...................................... 6-12
6.4 NETWORK MANAGEMENT REQUIREMENTS............................................. 6-14
ANNEX A SYMBOLS AND ABBREVIATIONS.......................................................... A-1
ANNEX B INFORMATIVE REFERENCES .................................................................B-1
ANNEX C PROTOCOL IMPLEMENTATION CONFORMANCE
STATEMENT PROFORMA........................................................................ C-1
ANNEX D SERVICES OF THE TRANSPORT PROTOCOL.................................... D-1
CCSDS 714.0-B-2
Page vi
October 2006
CCSDS RECOMMENDED STANDARD FOR SCPS TRANSPORT PROTOCOL (SCPS-TP)
CONTENTS (continued)
Figure
Page
3-1 SCPS Capabilities Option............................................................................................. 3-3
3-2 Beginning of Extended Capabilities Signaling............................................................. 3-6
3-3 Format for Extended Capabilities................................................................................. 3-6
3-4 Single Extended SCPS Capabilities Option with Multiple Extended
Capability Binding Spaces............................................................................................ 3-8
3-1 Using Multiple SCPS Capabilities Options to Express Multiple
Extended Capabilities ................................................................................................... 3-9
3-2 An Extended SCPS-TP capability Specified by a Binding Space
Identifier in the 256-511 Range.................................................................................. 3-10
3-7 Out-of-Sequence Queue for SNACK Example .......................................................... 3-23
3-8 SNACK Option Resulting from Out-of-Sequence Queue Example........................... 3-23
3-9 SNACK Options (without SNACK Bit-Vector) Resulting from
Out-of-Sequence Queue Example .............................................................................. 3-24
3-10 Compressed SCPS-TP Header.................................................................................... 3-29
D-1 SCPS-TP Composite Service Diagram for Connection-Oriented Services............... D-22
D-2 Local Service Provider State Diagram....................................................................... D-23
D-3 Composite SCPS-TP Service State Diagram for Connection-Oriented
Types of Service ........................................................................................................ D-24
D-4 State Diagram for Unacknowledged Service............................................................. D-25
Table
1-1 Values of the N-User_Internet_Protocol_Number Parameter Used by SCPS-TP ....... 1-6
3-1 SCPS Capabilities Option Bit-Vector Contents ........................................................... 3-4
3-2 Compressed Header Bit-Vector Contents................................................................... 3-26
D-1 SCPS-TP Services and Types of Service..................................................................... D-2
D-2 SCPS-TP Data Transport Characteristics .................................................................... D-4
D-3 Specific SCPS-TP Data Transfer Capabilities............................................................. D-6
D-4 SCPS-TP Service Request Primitives.......................................................................... D-7
D-5 SCPS-TP Service Confirm and Indication Primitives ............................................... D-15
CCSDS 714.0-B-2
Page vii
October 2006