ISO 22672:2006

INTERNATIONAL ISO
STANDARD 22672
First edition
2006-06-01
Space data and information transfer
systems — Space link extension (SLE) —
Forward space packet service
Systèmes de transfert des informations et données spatiales —
Extension de liaisons spatiales (SLE) — Envoi de données spatiales
par paquets
Reference number
©
ISO 2006
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.

©  ISO 2006
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2006 – All rights reserved

Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 22672 was prepared by the Consultative Committee for Space Data Systems (CCSDS) (as
CCSDS 912.3-B-1, November 2004) and was adopted (without modifications except those stated in Clause 2
of this International Standard) by Technical Committee ISO/TC 20, Aircraft and space vehicles, Subcommittee
SC 13, Space data and information transfer systems.

INTERNATIONAL STANDARD ISO 22672:2006(E)

Space data and information transfer systems — Space link
extension (SLE) — Forward space packet service
1 Scope
The Forward Space Packet (FSP) service is a Space Link Extension (SLE) transfer service that enables a
mission to send Space Packets to a spacecraft in sequence-controlled or expedited mode. This International
Standard defines, in an abstract manner, the FSP service in terms of
⎯ the operations necessary to provide the transfer service;
⎯ the parameter data associated with each operation;
⎯ the behaviours that result from the invocation of each operation;
⎯ the relationship between, and the valid sequence of, the operations and resulting behaviours.
It does not specify
⎯ individual implementations or products;
⎯ the implementation of entities or interfaces within real systems;
⎯ the methods or technologies required to radiate Space Packets to a spacecraft and to acquire telemetry
frames from the signals received from that spacecraft for extraction of the Operational Control Field;
⎯ the methods or technologies required for communications;
⎯ the management activities necessary to schedule, configure, and control the FSP service.
The scope and field of application are furthermore detailed in subclauses 1.1 to 1.3 of the enclosed CCSDS
publication.
2 Requirements
Requirements are the technical recommendations made in the following publication (reproduced on the
following pages), which is adopted as an International Standard:
CCSDS 912.3-B-1, November 2004, Space link extension (SLE) — Forward space packet service
specification.
For the purposes of international standardization, the modifications outlined below shall apply to the specific
clauses and paragraphs of publication CCSDS 912.3-B-1.
Pages i to vi
This part is information which is relevant to the CCSDS publication only.
Page 1-13
Add the following information to the reference indicated:
[1] Document CCSDS 910.4-B-1, May 1996, is equivalent to ISO 15396:1998.
[2] Document CCSDS 301.0-B-3, January 2002, is equivalent to ISO 11104:2003.
[3] Document CCSDS 231.0-B-1, September 2003, is equivalent to ISO 22642:2005.
[4] Document CCSDS 232.0-B-1, September 2003, is equivalent to ISO 22664:2005.
[5] Document CCSDS 232.1-B-1, September 2003, is equivalent to ISO 22667:2005.
[6] Document CCSDS 133.0-B-1, September 2003, is equivalent to ISO 22646:2005.
[7] ISO/IEC 8824:1998 has been cancelled and replaced by ISO/IEC 8824:2002.
Page G-1
Add the following information to the reference indicated:
[G4] Document CCSDS 201.0-B-3, June 2000, is equivalent to ISO 12171:2002.
[G5] Document CCSDS 202.0-B-3, June 2001, is equivalent to ISO 12172:2003.
[G6] Document CCSDS 202.1-B-2, June 2001, is equivalent to ISO 12173:2003.
[G7] Document CCSDS 203.0-B-2, June 2001, is equivalent to ISO 12174:2003.
3 Revision of publication CCSDS 912.3-B-1
It has been agreed with the Consultative Committee for Space Data Systems that Subcommittee
ISO/TC 20/SC 13 will be consulted in the event of any revision or amendment of publication
CCSDS 912.3-B-1. To this end, NASA will act as a liaison body between CCSDS and ISO.

2 © ISO 2006 – All rights reserved

RECOMMENDATION FOR SPACE
DATA SYSTEM STANDARDS
SPACE LINK EXTENSION—
FORWARD SPACE PACKET
SERVICE SPECIFICATION
CCSDS 912.3-B-1
BLUE BOOK
November 2004
CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
AUTHORITY
Issue: Blue Book, Issue 1
Date: November 2004
Location: Toulouse, France
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 reference [G1], and the
record of Agency participation in the authorization of this document can be obtained from
the CCSDS Secretariat at the address below.

This Recommendation is published and maintained by:

CCSDS Secretariat
Program Integration Division (Code M-3)
National Aeronautics and Space Administration
Washington, DC 20546, USA
CCSDS 912.3-B-1 Page ii November 2004
4 © ISO 2006 – All rights reserved

CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
STATEMENT OF INTENT
The Consultative Committee for Space Data Systems (CCSDS) is an organization officially
established by the management of member space Agencies. 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
Recommendations and are not considered binding on any Agency.
This Recommendation is issued by, and represents the consensus of, the CCSDS Plenary
body. Agency endorsement of this Recommendation is entirely voluntary. Endorsement,
however, indicates the following understandings:
o Whenever an Agency establishes a CCSDS-related standard, this standard will be in
accord with the relevant Recommendation. Establishing such a standard does not
preclude other provisions that an Agency may develop.

o Whenever an Agency establishes a CCSDS-related standard, the Agency will provide
other CCSDS member Agencies 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
Recommendation nor any ensuing standard is a substitute for a memorandum of
agreement.
No later than five years from its date of issuance, this Recommendation 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 Recommendation is issued, existing CCSDS-
related Agency standards and implementations are not negated or deemed to be non-CCSDS
compatible. It is the responsibility of each Agency to determine when such standards or
implementations are to be modified. Each Agency is, however, strongly encouraged to direct
planning for its new standards and implementations towards the later version of the
Recommendation.
CCSDS 912.3-B-1 Page iii November 2004
CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
FOREWORD
This document is a technical Recommendation for use in developing ground systems for
space missions and has been prepared by the Consultative Committee for Space Data
Systems (CCSDS). The Space Link Extension (SLE) Forward Space Packet (FSP) Service
described herein is intended for missions that are cross-supported between Agencies of the
CCSDS.
This Recommendation specifies a data service that extends certain of the space-to-ground
communications services previously defined by CCSDS (references [3], [4], [5], and [6])
within the framework established by the CCSDS SLE Reference Model (reference [1]). It
allows implementing organizations within each Agency to proceed with the development of
compatible, derived Standards for the ground systems that are within their cognizance.
Derived Agency Standards may implement only a subset of the optional features allowed by
the Recommendation and may incorporate features not addressed by the Recommendation.
Through the process of normal evolution, it is expected that expansion, deletion or
modification to this document may occur. This Recommendation is therefore subject to
CCSDS document management and change control procedures, as defined in reference [G1].
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 ii.

CCSDS 912.3-B-1 Page iv November 2004
6 © ISO 2006 – All rights reserved

CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
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.
– Instituto Nacional de Pesquisas Espaciais (INPE)/Brazil.
– National Aeronautics and Space Administration (NASA)/USA.
– National Space Development Agency of Japan (NASDA)/Japan.
– Russian Space Agency (RSA)/Russian Federation.

Observer Agencies
– Austrian Space Agency (ASA)/Austria.
– 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.
– European Telecommunications Satellite Organization (EUTELSAT)/Europe.
– Federal Service of Scientific, Technical & Cultural Affairs (FSST&CA)/Belgium.
– Hellenic National Space Committee (HNSC)/Greece.
– Indian Space Research Organization (ISRO)/India.
– Institute of Space Research (IKI)/Russian Federation.
– KFKI Research Institute for Particle & Nuclear Physics (KFKI)/Hungary.
– MIKOMTEK: CSIR (CSIR)/Republic of South Africa.
– Korea Aerospace Research Institute (KARI)/Korea.
– Ministry of Communications (MOC)/Israel.
– National Institute of Information and Communications Technology (NICT)/Japan.
– National Oceanic & Atmospheric Administration (NOAA)/USA.
– National Space Program Office (NSPO)/Taipei.
– Space and Upper Atmosphere Research Commission (SUPARCO)/Pakistan.
– Swedish Space Corporation (SSC)/Sweden.
– United States Geological Survey (USGS)/USA.

CCSDS 912.3-B-1 Page v November 2004
CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
DOCUMENT CONTROL
Document Title Date Status
CCSDS Space Link Extension— November Original Issue
912.3-B-1 Forward Space Packet 2004
Service Specification
CCSDS 912.3-B-1 Page vi November 2004
8 © ISO 2006 – All rights reserved

CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
CONTENTS
Section Page
1 INTRODUCTION. 1-1

1.1 PURPOSE OF THIS RECOMMENDATION. 1-1
1.2 SCOPE.1-1
1.3 APPLICABILITY.1-1
1.4 RATIONALE.1-2
1.5 DOCUMENT STRUCTURE.1-2
1.6 DEFINITIONS, NOMENCLATURE, AND CONVENTIONS . 1-4
1.7 REFERENCES.1-12

2 DESCRIPTION OF THE FORWARD SPACE PACKET SERVICE . 2-1

2.1 OVERVIEW.2-1
2.2 SPACE LINK EXTENSION REFERENCE MODEL. 2-2
2.3 SERVICE MANAGEMENT.2-3
2.4 ARCHITECTURE MODEL—FUNCTIONAL VIEW.2-4
2.5 ARCHITECTURE MODEL—CROSS SUPPORT VIEW . 2-6
2.6 FUNCTIONAL DESCRIPTION.2-7
2.7 OPERATIONAL SCENARIO.2-15
2.8 SECURITY ASPECTS OF THE SLE FORWARD SPACE PACKET (FSP)
TRANSFER SERVICE . 2-16

3 FSP SERVICE OPERATIONS . 3-1

3.1 GENERAL CONSIDERATIONS.3-1
3.2 FSP-BIND.3-10
3.3 FSP-UNBIND.3-16
3.4 FSP-START.3-19
3.5 FSP-STOP.3-23
3.6 FSP-TRANSFER-DATA.3-26
3.7 FSP-ASYNC-NOTIFY.3-36
3.8 FSP-SCHEDULE-STATUS-REPORT.3-50
3.9 FSP-STATUS-REPORT.3-54
3.10 FSP-GET-PARAMETER.3-61
3.11 FSP-THROW-EVENT.3-66
3.12 FSP-INVOKE-DIRECTIVE.3-71
3.13 FSP-PEER-ABORT.3-76
CCSDS 912.3-B-1 Page vii November 2004
CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE

4 FSP PROTOCOL. 4-1

4.1 GENERIC PROTOCOL CHARACTERISTICS. 4-1
4.2 FSP SERVICE PROVIDER BEHAVIOR. 4-4

ANNEX A Data Type Definitions. A-1
ANNEX B FSP Queues and Multiplexing Behaviour Definition .B-1
ANNEX C Production Status. C-1
ANNEX D Index to Definitions. D-1
ANNEX E Acronyms .E-1
ANNEX F Conformance Matrix.F-1
ANNEX G Informative References . G-1
ANNEX H Throw Event Definitions. H-1

Figure
1-1: Space Link Extension (SLE) Services Documentation. 1-4
2-1: Forward TC VC Data Insertion SLE-FG . 2-4
2-2: FSP Service Production and Provision. 2-6
2-3: Example of the Management and Provision of FSP Service. 2-7
2-4: Simplified FSP Service Provider State Transition Diagram . 2-10
2-5: Communications Realization of FSP Service . 2-13
B-1: FSP MAP and TC Frame Multiplexing .B-1
B-2: MAP and VC Multiplexing .B-2
B-3: FSP Queues.B-5
C-1: FSP Production Status Diagram .C-1

Table
2-1: FSP Service Operations. 2-8
3-1: Setting of FSP Service Operation Parameters. 3-6
3-2: FSP-BIND Parameters. 3-11
3-3: FSP-UNBIND Parameters. 3-17
3-4: FSP-START Parameters. 3-19
3-5: FSP-STOP Parameters. 3-23
3-6: FSP-TRANSFER-DATA Parameters . 3-27
3-7: FSP-ASYNC-NOTIFY Parameters. 3-36
3-8: FSP-SCHEDULE-STATUS-REPORT Parameters . 3-50
3-9: FSP-STATUS-REPORT Parameters. 3-54
3-10: FSP-GET-PARAMETER Parameters. 3-61
CCSDS 912.3-B-1 Page viii November 2004
10 © ISO 2006 – All rights reserved

CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
CONTENTS (CONTINUED)
3-11: FSP Service Parameters. 3-62
3-12: FSP-THROW-EVENT Parameters . 3-67
3-13: FSP-INVOKE-DIRECTIVE Parameters. 3-71
3-14: FSP-PEER-ABORT Parameters. 3-76
4-1: Provider Behavior. 4-6
4-2: Event Description References . 4-11
4-3: Predicate Definitions . 4-12
4-4: Boolean Flags . 4-12
4-5: Compound Action Definitions . 4-13
C-1: Production Status Transitions.C-2
C-2: Effects of Production Status on Operations.C-3
F-1: Conformance Matrix for FSP Service (Operations).F-1
F-2: Conformance Matrix for FSP Service (Other Requirements).F-2
H-1: Throw Event Examples . H-1

CCSDS 912.3-B-1 Page ix November 2004
(Blank page)
12 © ISO 2006 – All rights reserved

CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
1 INTRODUCTION
1.1 PURPOSE OF THIS RECOMMENDATION
This Recommendation defines the Forward Space Packet (FSP) service in conformance with
the transfer services specified in reference [1], Cross Support Reference Model―Part 1: SLE
Services. The FSP service is a Space Link Extension (SLE) transfer service that enables a
mission to send Space Packets to a spacecraft in sequence-controlled or expedited mode.
1.2 SCOPE
This Recommendation defines, in an abstract manner, the FSP service in terms of:
a) the operations necessary to provide the transfer service;
b) the parameter data associated with each operation;
c) the behaviors that result from the invocation of each operation; and
d) the relationship between, and the valid sequence of, the operations and resulting
behaviors.
It does not specify:
a) individual implementations or products;
b) the implementation of entities or interfaces within real systems;
c) the methods or technologies required to radiate Space Packets to a spacecraft and to
acquire telemetry frames from the signals received from that spacecraft for extraction
of the Operational Control Field;
d) the methods or technologies required for communications; or
e) the management activities necessary to schedule, configure, and control the FSP
service.
NOTE – While the FSP service as described in reference [1] is conceived to handle a
variety of packet data structures, this version of the FSP Recommendation is
restricted to the handling of Space Packets as defined in reference [6].
1.3 APPLICABILITY
1.3.1 APPLICABILITY OF THIS RECOMMENDATION
This Recommendation provides a basis for the development of real systems that implement
the FSP service. Implementation of the FSP service in a real system additionally requires the
availability of a communications service to convey invocations and returns of FSP service
CCSDS 912.3-B-1 Page 1-1 November 2004
CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
operations between FSP service users and providers. This Recommendation requires that
such a communications service ensures that invocations and returns of operations are
transferred:
a) in sequence;
b) completely and with integrity;
c) without duplication;
d) with flow control that notifies backpressure to the application layer in the event of
congestion; and
e) with notification to the application layer in the event that communications between
the FSP service user and the FSP service provider are disrupted, possibly resulting in
a loss of data.
It is the specific intent of this Recommendation to define the FSP service in a manner that is
independent of any particular communications services, protocols, or technologies.
1.3.2 LIMITS OF APPLICABILITY
This Recommendation specifies the FSP service that may be provided by an SLE System for
inter-Agency cross support. It is neither a specification of, nor a design for, real systems that
may be implemented for the control and monitoring of existing or future missions.
1.4 RATIONALE
The goal of this Recommendation is to create a standard for interoperability between the
tracking stations and/or ground data handling systems of various agencies and the users of
forward services.
1.5 DOCUMENT STRUCTURE
1.5.1 ORGANIZATION
This Recommendation is organized as follows:
a) section 1 provides the purpose, scope, applicability, and rationale of this
Recommendation and lists definitions, nomenclature, conventions, and references
used throughout the Recommendation;
b) section 2 provides an overview of the FSP service including a functional description,
the service management context, and protocol considerations;
c) section 3 specifies the operations of the FSP service;
CCSDS 912.3-B-1 Page 1-2 November 2004
14 © ISO 2006 – All rights reserved

CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
d) section 4 specifies the dynamic behavior of the FSP service in terms of the state
transitions of the FSP service provider;
e) annex A provides a formal specification of FSP service data types, using the Abstract
Syntax Notation One (ASN.1);
f) annex B provides a specification of the multiplexing between concurrent FSP service
instances sharing the same TC Virtual Channel (VC) as well as the multiplexing
between TC VCs sharing the same physical space link data channel;
g) annex C presents the FSP production status and its transitions;
h) annex D lists all terms used in this document and identifies where they are defined;
i) annex E lists all acronyms used within this document;
j) annex F provides a conformance matrix that defines what capabilities must be
provided for an implementation to be considered compliant with this
Recommendation;
k) annex G contains a list of informative references;
l) annex H contains examples of usage of the FSP-THROW-EVENT operation.
1.5.2 SLE SERVICES DOCUMENTATION TREE
This Recommendation is based on the architectural model for cross support defined in
reference [1]. It expands upon the concept of an SLE Transfer Service as interactions
between an SLE Mission User Entity (MUE) and an SLE Transfer Service provider for the
purpose of providing the FSP Transfer Service.
This Recommendation is part of a suite of documents specifying the SLE services. The SLE
services constitute one of the three types of Cross Support Services:
a) Part 1: SLE Services;
b) Part 2: Ground Communications Services;
c) Part 3: Ground Domain Services.
The basic organization of the SLE services documentation is shown in figure 1-1. The
documents are described in the following paragraphs.

CCSDS 912.3-B-1 Page 1-3 November 2004
CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
SpSpacacee L Liinknk Ex Extteennssiioonn
CCrroossss S Suupppportort
CrCrossoss S Supuppoporrtt CoConcepncept t SSLLE EE Exxecutiecutivvee
RRefefereerencnce Me Moodedel l
PaParrtt 1 1::  SLSLE E SeSerrvviicceess SuSummmmaryary
PaParrtt 1 1:: SL SLE SeE Serrvviicceess
SLSLSLEEE Tr Tr Trananansfesfesferrr S S Seeerrrvvviciciceeesss
FFFooorrrwwwaaarrrddd SL SL SLE SeE SeE Serrrvvviiiccceee   SLSLSLE APIE APIE API f f fooorrr
RRReeetttuuurrrnnn SL SL SLE SE SE Seeerrrvvviiiccceee  SLSLSLE SE SE Seeerrrvvviiiccceee
SSSpppecececifififiiicccatatationionionsss  TTTrrrananansssfffeeerrr Ser Ser Servvviiiccceseses
SSSpppecececiiiffficicicaaatttioioionsnsns  MMMaaanananagegegemmmeeentntnt S S Suiuiuitetete
RRReeeporporporttt (G (G (Greereereennn))) RRReeeport (Yport (Yport (Yellowellowellow)))
RecRecRecooommmmmmeeennndadadatttiiiooonnn
LLLegeegeegennnd:d:d:
Figure 1-1: Space Link Extension (SLE) Services Documentation
a) Cross Support Concept — Part 1: Space Link Extension Services (reference [G3]): a
Report introducing the concepts of cross support and SLE services;
b) Cross Support Reference Model — Part 1: Space Link Extension Services (reference
[1]): a Recommendation that defines the reference model that provides a common
framework and terminology for the specification of SLE services;
c) SLE Service Management Specifications; a set of Recommendations that establish the
basis of SLE service management;
d) Forward SLE Service Specifications: a set of Recommendations that will provide
specification of all forward link SLE transfer services (this Recommendation is one of
the specifications in that set);
e) Return SLE Service Specifications; a set of Recommendations that will provide
specification of all return link SLE transfer services.
1.6 DEFINITIONS, NOMENCLATURE, AND CONVENTIONS
1.6.1 DEFINITIONS
1.6.1.1 Definitions from Open Systems Interconnection (OSI) Basic Reference Model
This Recommendation makes use of a number of terms defined in reference [8]. The use of
those terms in this Recommendation shall be understood in a generic sense; i.e., in the sense
CCSDS 912.3-B-1 Page 1-4 November 2004
16 © ISO 2006 – All rights reserved

CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
that those terms are generally applicable to technologies that provide for the exchange of
information between real systems. Those terms are:
a) abstract syntax;
b) application entity;
c) application layer;
d) flow control;
e) Open Systems Interconnection (OSI);
f) real system;
g) service access point (SAP).
1.6.1.2 Definitions from Abstract Syntax Notation One
This Recommendation makes use of the following terms defined in reference [7]:
a) Abstract Syntax Notation One (ASN.1);
b) object identifier;
c) (data) type;
d) (data) value.
NOTE – In annex A of this Recommendation, ASN.1 is used for specifying the abstract
syntax of the invocations and returns of the operations of the FSP service. The
use of ASN.1 as a descriptive language is intended to support the specification of
the abstract FSP service; it is not intended to constrain implementations. In
particular, there is no requirement for implementations to employ ASN.1
encoding rules. ASN.1 is simply a convenient tool for formally describing the
abstract syntax of the invocations and returns of the FSP service.
1.6.1.3 Definitions from TC Synchronization and Channel Coding
This Recommendation makes use of the following term defined in reference [3]:
Communications Link Transmission Unit (CLTU).
1.6.1.4 Definitions from TC Space Data Link Protocol
This Recommendation makes use of the following terms defined in reference [4]:
a) AD, BD, BC;
CCSDS 912.3-B-1 Page 1-5 November 2004
CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
b) Communications Link Control Word (CLCW);
c) Communications Operation Procedure (COP);
d) Control Word Type;
e) Frame Operation Procedure (FOP);
f) Frame Sequence Number;
g) Multiplexer Access Point (MAP);
h) Operational Control Field (OCF);
i) Segment;
j) Telecommand Transfer Frame (TC Transfer Frame or TC frame);
k) Virtual Channel (VC).
1.6.1.5 Definitions from Communications Operation Procedure-1
This Recommendation makes use of the following terms defined in reference [5]:
a) FOP_Sliding_Window_Width;
b) Receiver_Frame_Sequence_Number V(R);
c) Timeout_Type;
d) Transmitter_Frame_Sequence_Number V(S);
e) T1_Initial.
1.6.1.6 Definitions from Space Packet Protocol
This Recommendation makes use of the following terms defined in reference [6]:
a) Application Process Identifier (APID);
b) Space Packet.
1.6.1.7 Definitions from SLE Reference Model
This Recommendation makes use of the following terms defined in reference [1]:
a) abstract binding;
b) abstract object;
c) abstract port;
CCSDS 912.3-B-1 Page 1-6 November 2004
18 © ISO 2006 – All rights reserved

CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
d) abstract service;
e) Forward Space Packet channel (FSP channel);
f) Forward Space Packet service (FSP service);
g) invoker;
h) Mission Data Operation System (MDOS);
i) Mission User Entity (MUE);
j) offline delivery mode;
k) online delivery mode;
l) operation;
m) performer;
n) physical channel;
o) service agreement;
p) service provider (provider);
q) service user (user);
r) SLE Complex;
s) SLE Complex Management;
t) SLE data channel;
u) SLE functional group (SLE-FG);
v) SLE protocol data unit (SLE-PDU);
w) SLE service data unit (SLE-SDU);
x) SLE service package;
y) SLE System;
z) SLE transfer service instance;
aa) SLE transfer service production;
bb) SLE transfer service provision;
cc) SLE Utilization Management;
dd) space link;
ee) space link data channel;
CCSDS 912.3-B-1 Page 1-7 November 2004
CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
ff) space link data unit (SL-DU);
gg) space link session.
1.6.1.8 Additional Definitions
For the purposes of this Recommendation, the following definitions also apply.
1.6.1.8.1 Acknowledged (Space Packet)
A Space Packet is said to be acknowledged when evaluation of the CLCWs returned by the
space element shows that all TC frames containing parts of the Space Packet reported have
been acknowledged by the space element.
NOTE — This status applies only to the sequence-controlled transmission mode (AD).
Although a Space Packet is “acknowledged”, packet re-assembly and/or
execution may still fail. This can only be determined by examining telemetry.
1.6.1.8.2 Association
An association is a cooperative relationship between an SLE service-providing application
entity and an SLE service-using application entity. An association is formed by the exchange
of SLE protocol data units through the use of an underlying communications service.
1.6.1.8.3 Communications Service
A communications service is a capability that enables an SLE service-providing application
entity and an SLE service-using application entity to exchange information.
NOTE – If an SLE service user and an SLE service provider are implemented using
different communications services, then interoperability between them is possible
only by means of a suitable gateway. Adherence to this Recommendation
ensures, at least in principle, that it is possible to construct such a gateway.
1.6.1.8.4 Confirmed Operation
A confirmed operation is an operation that requires the performer to return a report of its
outcome to the invoker.
1.6.1.8.5 Initiator
The initiator is the object that issues the request to bind to another object (the responder).
CCSDS 912.3-B-1 Page 1-8 November 2004
20 © ISO 2006 – All rights reserved

CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
1.6.1.8.6 Invocation
The invocation of an operation is the making of a request by an object (the invoker) to
another object (the performer) to carry out the operation.
1.6.1.8.7 Parameter
A parameter of an operation is data that may accompany the operation’s invocation or return.
NOTE – The term parameter is also used to refer to mission-dependent configuration
information used in the production or provision of the service.
1.6.1.8.8 Performance
The performance of an operation is the carrying out of the operation by an object (the
performer).
1.6.1.8.9 Port Identifier
A port identifier identifies a source or a destination in a communications system.
NOTE – See 2.6.4.5 for more information.
1.6.1.8.10 Radiated (Space Packet)
A Space Packet is said to be radiated when, based on the ground equipment monitoring, the
FSP production process can assume that all the CLTUs containing parts of the Space Packet
reported have been transmitted to the spacecraft.
1.6.1.8.11 Responder
The responder is the object that receives a request to bind and completes the binding (if
possible) with the initiator in order for a service association to exist between the two objects.
1.6.1.8.12 Return
The return of an operation is a report, from the performer to the invoker, of the outcome of
the performance of the operation.
CCSDS 912.3-B-1 Page 1-9 November 2004
CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
1.6.1.8.13 Service Instance Provision Period
A service instance provision period is the time during which a service instance (i.e., the
capability to transfer one or more SLE data channels of a given type) is scheduled to be
provided.
1.6.1.8.14 Unconfirmed Operation
An unconfirmed operation is an operation that does not require a report of its outcome to be
returned to the invoker by the performer.
1.6.2 NOMENCLATURE
The following nomenclature applies throughout this Recommendation:
a) the words ‘shall’ and ‘must’ imply a binding and verifiable specification;
b) the word ‘should’ implies an optional, but desirable, specification;
c) the word ‘may’ implies an optional specification;
d) the words ‘is’, ‘are’, and ‘will’ imply statements of fact.
1.6.3 CONVENTIONS
1.6.3.1 Specification of Operations
1.6.3.1.1 General
Section 3 of this Recommendation specifies the operations that constitute the FSP service.
The specification of each operation is divided into subsections as follows:
1.6.3.1.2 Purpose Subsection
The Purpose subsection briefly describes the purpose and functioning of the operation.
Additionally, it indicates whether the operation may be invoked by the user, provider, or
both; whether the operation is confirmed or unconfirmed; and whether there are any
constraints on when the operation may be invoked.
1.6.3.1.3 Invocation, Return, and Parameters Subsection
The Invocation, Return, and Parameters subsection describes the parameters associated with
each operation, including their semantics. A table accompanying the description of each
operation lists all parameters associated with the operation and, for both the invocation and
return, whether the parameter is always present, always absent, or conditionally present.
CCSDS 912.3-B-1 Page 1-10 November 2004
22 © ISO 2006 – All rights reserved

CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
For parameters that are conditionally present, the parameter description specifies the
conditions for the presence or absence of the parameter. The condition is generally based on
the value of another parameter in the same invocation or return; for example, in the return of
an operation, the diagnostic parameter is present if and only if the value of the result
parameter is ‘negative result’. For a conditional parameter in a return, the condition may be
based on the value of a parameter in the corresponding invocation.
In the table, the following convention is used to indicate whether a parameter is always
present, always absent, or conditionally present:
M always present (mandatory)
C conditionally present
Blank always absent
NOTE – Even though a parameter may be characterized as always present, its description
may specify that its value is permitted to be ‘null’ or ‘unused’ or the like.
1.6.3.1.4 Effects Subsection
The Effects subsection describes the effects an operation has on the invoker, the performer,
the association between them, or any combination thereof. The details of how those effects
occur or the mechanisms used are outside the scope of this Recommendation.
1.6.3.2 Typographic Conventions
Typographic conventions used in this Recommendation are described in the following
subsections.
1.6.3.2.1 Operation Names
Names of FSP service operations appear in uppercase and begin with the characters ‘FSP-’
(e.g., FSP-TRANSFER-DATA).
1.6.3.2.2 Parameter Names
In the main text, names of parameters of FSP service operations appear in lowercase and are
typeset in a fixed-width font (e.g., responder-port-identifier). In annex A, the
corresponding name is formed by omitting any hyphens contained in the name and using
mixed-case (e.g., responderPortIdentifier).
CCSDS 912.3-B-1 Page 1-11 November 2004
CCSDS RECOMMENDATION FOR SLE FORWARD SPACE PACKET SERVICE
1.6.3.2.3 Value Names
The values of many parameters discussed in this Recommendation are represented by names.
In t
...