ISO 22669:2003

INTERNATIONAL ISO
STANDARD 22669
First edition
2003-12-15
Space data and information transfer
systems — Space link extension (SLE) —
Return-all-frames service
Systèmes de transfert des informations et données spatiales —
Extension de liaisons spatiales (SLE) — Service de retour par tout
réseau
Reference number
©
ISO 2003
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 2003
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 2003 — 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.
International Standard ISO 22669 was prepared by the Consultative Committee for Space Data Systems
(CCSDS) (as CCSDS 911.1-B-1, April 2002) 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 22669:2003(E)

Space data and information transfer systems — Space link
extension (SLE) — Return-all-frames service
1 Scope
This International Standard specifies a return-all-frames (RAF) service for a space link extension (SLE)
service. The RAF service is an SLE transfer service that delivers all telemetry frames to a mission user from
one space link physical channel.
It defines, in an abstract manner, the RAF service in terms of:
a) the operations necessary to provide the service;
b) the parameter data associated with each operation;
c) the behaviours that result from the invocation of each operation; and
d) the relationship between, and the valid sequence of, the operations and resulting behaviours.
The scope and field of application are furthermore detailed in subclauses 1.1 and 1.2 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 911.1-B-1, April 2002, Space link extension — Return all frames service specification.
For the purposes of international standardization, the modifications outlined below shall apply to the specific
clauses and paragraphs of publication CCSDS 911.1-B-1.
Pages i to vii
This part is information which is relevant to the CCSDS publication only.
Pages1-12 to 1-13
Add the following information to the references indicated:
[1] Document CCSDS 910.4-B-1, May 1996, is equivalent to ISO 15396:1998.
1)
[2] Document CCSDS 101.0-B-5, June 2001, is equivalent to ISO 11754:2003 .

1) Document CCSDS 101.0-B-5, June 2001, has been cancelled and replaced by CCSDS 101.0-B-6, October 2002.
CCSDS 101.0-B-6 is currently under ISO vote for approval as the third edition of ISO 11754.
[3] Document CCSDS 102.0-B-5, November 2000, is equivalent to ISO 13419:2003.
2)
[4] Document CCSDS 701.0-B-3, June 2001, is equivalent to ISO 13420:— .
[5] Document CCSDS 301.0-B-3, January 2001, is equivalent to ISO 11104:2003.
[7] ISO/IEC 8824:1990, has been cancelled and replaced by ISO/IEC 8824-1:2003.
[8] ISO/IEC 9594-2:1998, has been cancelled and replaced by ISO/IEC 9594-2:2001.
3 Revision of publication CCSDS 911.1-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 911.1-B-1. To this end, NASA will act as a liaison body between CCSDS and ISO.

2) To be published. (Revision of ISO 13420:1997)
2 © ISO 2003 — All rights reserved

RECOMMENDATION FOR SPACE
DATA SYSTEM STANDARDS
SPACE LINK EXTENSION—
RETURN ALL FRAMES
SERVICE SPECIFICATION
CCSDS 911.1-B-1
BLUE BOOK
April 2002
(Blank page)
4 © ISO 2003 — All rights reserved

CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

AUTHORITY
Issue: Blue Book, Issue 1
Date: April 2002
Location: Oberpfaffenhofen, Germany

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 Recommendation is published and maintained by:

CCSDS Secretariat
Program Integration Division (Code M-3)
National Aeronautics and Space Administration
Washington, DC 20546, USA
CCSDS 911.1-B-1 Page i April 2002
CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES 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 which 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 911.1-B-1 Page ii April 2002
6 © ISO 2003 — All rights reserved

CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES 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 Return All Frames 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 [2], [3], and [4]) within
the framework established by the CCSDS Space Link Extension 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 the Procedures
Manual for the Consultative Committee for Space Data Systems. 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 911.1-B-1 Page iii April 2002
CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES 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.
– Communications Research Centre (CRC)/Canada.
– Communications Research Laboratory (CRL)/Japan.
– 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 and Astronautical Science (ISAS)/Japan.
– 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 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 911.1-B-1 Page iv April 2002
8 © ISO 2003 — All rights reserved

CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

DOCUMENT CONTROL
Document Title Date Status
CCSDS Space Link Extension— April 2002 Original Issue
911.1-B-1 Return All Frames Service
Specification
CCSDS 911.1-B-1 Page v April 2002
CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES 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 RETURN ALL FRAMES SERVICE. 2-1

2.1 OVERVIEW.2-1
2.2 SPACE LINK EXTENSION REFERENCE MODEL. 2-1
2.3 SERVICE MANAGEMENT.2-3
2.4 ARCHITECTURE MODEL—FUNCTIONAL VIEW . 2-4
2.5 ARCHITECTURE MODEL—CROSS SUPPORT VIEW . 2-7
2.6 FUNCTIONAL DESCRIPTION.2-8
2.7 OPERATIONAL SCENARIO.2-17

3 RAF SERVICE OPERATIONS. 3-1

3.1 GENERAL CONSIDERATIONS.3-1
3.2 RAF-BIND.3-12
3.3 RAF-UNBIND.3-19
3.4 RAF-START.3-23
3.5 RAF-STOP.3-28
3.6 RAF-TRANSFER-DATA.3-30
3.7 RAF-SYNC-NOTIFY.3-34
3.8 RAF-SCHEDULE-STATUS-REPORT.3-37
3.9 RAF-STATUS-REPORT.3-41
3.10 RAF-GET-PARAMETER.3-44
3.11 RAF-PEER-ABORT.3-48

4 RAF PROTOCOL . 4-1

4.1 GENERIC PROTOCOL CHARACTERISTICS . 4-1
4.2 RAF SERVICE PROVIDER BEHAVIOR. 4-4
CCSDS 911.1-B-1 Page vi April 2002
10 © ISO 2003 — All rights reserved

CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

CONTENTS (CONTINUED)
Section Page
ANNEX A DATA TYPE DEFINITIONS . A-1
ANNEX B INDEX TO DEFINITIONS. B-1
ANNEX C ACRONYMS. C-1
ANNEX D CONFORMANCE MATRIX. D-1
ANNEX E INFORMATIVE REFERENCES.E-1
Figure
1-1 SLE Services Documentation. 1-4
2-1 Return Space Link Processing SLE-FG . 2-4
2-2 RAF Service Production and Provision. 2-6
2-3 Example of the Management and Provision of RAF Service. 2-7
2-4 Simplified RAF Service Provider State Transition Diagram. 2-10
2-5 Mapping of RAF Service Operations to SLE-PDUs. 2-12
2-6 Buffers and Delivery Modes . 2-16

Table
2-1 RAF Operations . 2-9
3-1 RAF-BIND Parameters . 3-13
3-2 RAF-UNBIND Parameters. 3-20
3-3 RAF-START Parameters . 3-24
3-4 RAF-STOP Parameters . 3-28
3-5 RAF-TRANSFER-DATA Parameters . 3-30
3-6 RAF-SYNC-NOTIFY Parameters. 3-34
3-7 RAF-SCHEDULE-STATUS-REPORT Parameters. 3-38
3-8 RAF-STATUS-REPORT Parameters. 3-41
3-9 RAF-GET-PARAMETER Parameters. 3-44
3-10 RAF-PEER-ABORT Parameters. 3-48
4-1 Provider Behavior . 4-6
4-2 Event Description References. 4-12
4-3 Predicate Descriptions. 4-12
4-4 Boolean Flags . 4-13
4-5 Compound Action Definitions . 4-13
D-1 Conformance Matrix for RAF Service (Operations). D-1
D-2 Conformance Matrix for RAF Service (Other Requirements). D-2

CCSDS 911.1-B-1 Page vii April 2002
(Blank page)
12 © ISO 2003 — All rights reserved

CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

1 INTRODUCTION
1.1 PURPOSE OF THIS RECOMMENDATION
The purpose of this Recommendation is to define the Space Link Extension (SLE) Return All
Frames (RAF) service in conformance with the SLE Reference Model (reference [1]). The
RAF service is an SLE transfer service that delivers to a mission user all telemetry frames
from one space link physical channel.
1.2 SCOPE
This Recommendation defines, in an abstract manner, the RAF service in terms of:
a) the operations necessary to provide the 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 acquire telemetry frames from signals
received from a spacecraft;
d) the methods or technologies required to provide a suitable environment for
communications; or
e) the management activities required to schedule, configure, and control the RAF
service.
1.3 APPLICABILITY
1.3.1 APPLICABILITY OF THIS RECOMMENDATION
This Recommendation provides a basis for the development of real systems that implement the
RAF service. Implementation of the RAF service in a real system additionally requires the
availability of a communications service to convey invocations and returns of RAF service
operations between RAF service users and providers. This Recommendation requires that
such a communications service must ensure that invocations and returns of operations are
transferred:
a) in sequence;
CCSDS 911.1-B-1 Page 1-1 April 2002
CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

b) completely and with integrity;
c) without duplication;
d) with flow control that notifies the application layer in the event of congestion; and
e) with notification to the application layer in the event that communications between the
RAF service user and the RAF service provider are disrupted, possibly resulting in a
loss of data.
It is the specific intent of this Recommendation to define the RAF service in a manner that is
independent of any particular communications services, protocols, or technologies.
1.3.2 LIMITS OF APPLICABILITY
1.3.2.1 Relationship to Real Systems
This Recommendation specifies the RAF 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.3.2.2 RAF Service and Telemetry Channel Coding
Telemetry channel coding on the space link is specified by reference [2]. This specification is
more restrictive with respect to telemetry channel coding than is reference [2]. In particular,
the provision of RAF service requires that Reed-Solomon coding must be present or absent on
all frames of a physical channel. RAF service is not supported where there is a concurrent
mix, on one physical channel, of some frames with Reed-Solomon coding and some frames
without.
1.4 RATIONALE
The goal of this Recommendation is to create a standard for interoperability between the
tracking stations or ground data handling systems of various Agencies and the consumers of
spacecraft telemetry.
1.5 DOCUMENT STRUCTURE
1.5.1 ORGANIZATION
This document is organized as follows:
a) section 1 presents the purpose, scope, applicability and rationale of this Recommenda-
tion and lists the definitions, conventions, and references used throughout the
Recommendation;
CCSDS 911.1-B-1 Page 1-2 April 2002
14 © ISO 2003 — All rights reserved

CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

b) section 2 provides an overview of the RAF service including a functional description,
the service management context, and protocol considerations;
c) section 3 specifies the operations of the RAF service;
d) section 4 specifies the dynamic behavior of the RAF service in terms of the state
transitions of the RAF service provider;
e) annex A provides a formal specification of RAF service data types using Abstract
Syntax Notation One (ASN.1);
f) annex B lists all terms used in this Recommendation and identifies where they are
defined;
g) annex C lists all acronyms used within this document;
h) annex D provides a conformance matrix that defines what capabilities must be
provided for an implementation to be considered compliant with this
Recommendation;
i) annex E provides a list of informative references.
1.5.2 SLE SERVICES DOCUMENTATION TREE
This Recommendation is based on the cross support model defined in the SLE Reference
Model (reference [1]). It expands upon the concept of an SLE transfer service as an
interaction between an SLE Mission User Entity (MUE) and an SLE transfer service provider
for the purpose of providing the RAF 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 Domain Services;
c) Part 3: Ground Communications Services.
The basic organization of the SLE services documentation is shown in figure 1-1. The various
documents are described in the following paragraphs.
CCSDS 911.1-B-1 Page 1-3 April 2002
CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

Standard Terminology
Conventions, and
Cross Support
Methodology for
Concept
Defining Data Services
Part 1:
SLE Services
Cross Support
Reference Model
Part 1:
SLE Services
SLE Transfer Services
SLE Service Forward Return
Management SLE SLE
Specification Suite Service Specifications Service Specifications

Figure 1-1: SLE Services Documentation
a) Standard Terminology, Conventions and Methodology for Defining Data Services
(reference [E2]): a Report identifying selected international standards relevant for the
definition of data services;
b) Cross Support Concept—Part 1: Space Link Extension Services (reference [E4]): a
Report introducing the concepts of cross support and the SLE services;
c) Cross Support Reference Model—Part 1: Space Link Extension Services (reference [1]): a
Recommendation that defines the framework and terminology for the specification of SLE
services;
d) SLE Return Service Specifications: a set of Recommendations that will provide
specification of all return link SLE services (this Recommendation is one of the
specifications in that set);
e) SLE Forward Service Specifications: a set of Recommendations that will provide
specification of all forward link SLE services;
f) SLE Service Management Specifications: a set of Recommendations that establish the
basis of SLE service management (reference [E3] is the primary Recommendation in that
set).
1.6 DEFINITIONS, NOMENCLATURE, AND CONVENTIONS
1.6.1 DEFINITIONS
1.6.1.1 Definitions from OSI Basic Reference Model
This Recommendation makes use of a number of terms defined in reference [6]. The use of
those terms in this Recommendation shall be understood in a generic sense; i.e., in the sense
CCSDS 911.1-B-1 Page 1-4 April 2002
16 © ISO 2003 — All rights reserved

CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES 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) application process;
e) flow control;
f) Open Systems Interconnection (OSI);
g) real system;
h) 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 RAF service operation invocations and returns. The use of ASN.1 as a
descriptive language is intended to support the specification of the abstract RAF
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 RAF
service operation invocations and returns.
1.6.1.3 Definitions from Directory Service Models
This Recommendation makes use of the following terms defined in reference [8]:
a) distinguished name (DN);
b) relative distinguished name (RDN).
CCSDS 911.1-B-1 Page 1-5 April 2002
CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

1.6.1.4 Definitions from Telemetry Channel Coding
This Recommendation makes use of the following terms defined in reference [2]:
a) attached sync marker;
b) codeblock;
c) convolutional code;
d) pseudo-randomization;
e) Reed-Solomon check symbols;
f) Reed-Solomon code.
1.6.1.5 Definitions from Packet Telemetry
This Recommendation makes use of the following term defined in reference [3]:
a) frame error control field;
b) transfer frame.
1.6.1.6 Definitions from AOS Architecture Specification
This Recommendation makes use of the following terms defined in reference [4]:
a) coded virtual channel data unit (CVCDU);
b) cyclic redundancy code (CRC);
c) VCDU error control field;
d) virtual channel data unit (VCDU).
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;
d) abstract service;
e) invoker;
CCSDS 911.1-B-1 Page 1-6 April 2002
18 © ISO 2003 — All rights reserved

CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

f) Mission Data Operation System (MDOS);
g) Mission User Entity (MUE);
h) offline delivery mode;
i) online delivery mode;
j) operation;
k) performer;
l) physical channel;
m) return data;
n) Return All Frames channel (RAF channel);
o) Return All Frames service (RAF service);
p) service agreement;
q) service provider (provider);
r) service user (user);
s) SLE Complex;
t) SLE Complex Management;
u) SLE data channel;
v) SLE functional group (SLE-FG);
w) SLE protocol data unit (SLE-PDU);
x) SLE service data unit (SLE-SDU);
y) SLE service package;
z) SLE System;
aa) SLE transfer service instance;
bb) SLE transfer service production;
cc) SLE transfer service provision;
dd) SLE Utilization Management;
ee) space link;
ff) space link data channel;
gg) space link data unit (SL-DU);
CCSDS 911.1-B-1 Page 1-7 April 2002
CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

hh) space link session.
1.6.1.8 Additional Definitions
1.6.1.8.1 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.2 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.3 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.4 Delivery Criteria
Delivery criteria are rules that determine whether a data unit acquired from the space link by
an SLE service provider shall be delivered to a user.
NOTE – For RAF service, the delivery criteria are:
a) the Earth Receive Time (ERT) of the frame is within the period defined by the
start and stop times specified in the RAF-START operation; and
b) the frame quality of the frame matches the requested frame quality specified in
the RAF-START operation.
1.6.1.8.5 Error Control Field
The error control field of a frame is the frame error control field (reference [3]) if the frame is
a transfer frame or the VCDU error control field (reference [4]) if the frame is a VCDU or
CVCDU.
CCSDS 911.1-B-1 Page 1-8 April 2002
20 © ISO 2003 — All rights reserved

CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

1.6.1.8.6 Initiator
The initiator is the object that issues the request to bind to another object (the responder).
1.6.1.8.7 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.8 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.9 Performance
The performance of an operation is the carrying out of the operation by an object (the
performer).
1.6.1.8.10 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.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.
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.
CCSDS 911.1-B-1 Page 1-9 April 2002
CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

1.6.1.8.14 Telemetry Frame
A telemetry frame is a transfer frame (as defined in reference [3]) or a VCDU or CVCDU (as
defined in reference [4]).
1.6.1.8.15 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 conventions apply 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 RAF service.
The specification of each operation is divided into subsections as follows:
1.6.3.1.2 Purpose Subsection
The Purpose subsection provides a brief description of the purpose 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 911.1-B-1 Page 1-10 April 2002
22 © ISO 2003 — All rights reserved

CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES 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
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
1.6.3.2.1 Operation Names
Names of RAF service operations appear in uppercase and begin with the characters ‘RAF-’
(e.g., RAF-TRANSFER-DATA).
1.6.3.2.2 Parameter Names
In the main text, names of parameters of RAF service operations generally 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).
1.6.3.2.3 Value Names
The values of many parameters discussed in this Recommendation are represented by names.
In the main text, those names are shown in quotation marks (e.g., ‘no such service instance’).
The corresponding name in annex A is formed by omitting any hyphens or white space
CCSDS 911.1-B-1 Page 1-11 April 2002
CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

contained in the name and using mixed-case (e.g., noSuchServiceInstance). The
actual value associated with the name is constrained by the type of the parameter taking on
that value. Parameter types are specified in annex A of this Recommendation.
NOTE – The name of a value does not imply anything about its type. For example, the
value ‘no such service instance’ has the appearance of a character string but might
be assigned to a parameter whose type is ‘integer’.
1.6.3.2.4 State Names
This Recommendation specifies the states of RAF service providers. States may be referred
to by number (e.g., state 2) or by name. State names are always shown in quotation marks
(e.g., ‘active’).
1.6.3.2.5 SLE-PDU Names
The names of SLE-PDUs appear in mixed-case (e.g., rafBindInvocation).
1.6.3.2.6 Data Type Definitions
Data type definitions for the RAF service are presented in annex A in the form of a set of
ASN.1 modules. Regardless of the conventions used elsewhere in this Recommendation, the
text of the ASN.1 modules is typeset entirely in a fixed-width font.
1.6.3.3 Other Conventions
This Recommendation uses the conventions specified in reference [1].
1.7 REFERENCES
The following documents contain provisions that, through reference in this text, constitute
provisions of this Recommendation. At the time of publication, the editions indicated were
valid. All documents are subject to revision, and users of this Recommendation are
encouraged to investigate the possibility of applying the most recent editions of the documents
indicated below. The CCSDS Secretariat maintains a register of currently valid CCSDS
Recommendations.
NOTE – A list of informative references is provided in annex E.
[1] Cross Support Reference Model—Part 1: Space Link Extension Services.
Recommendation for Space Data System Standards, CCSDS 910.4-B-1. Blue Book.
Issue 1. Washington, D.C.: CCSDS, May 1996.
CCSDS 911.1-B-1 Page 1-12 April 2002
24 © ISO 2003 — All rights reserved

CCSDS RECOMMENDATION FOR SLE RETURN ALL FRAMES SERVICE

[2] Telemetry Channel Coding. Recommendation for Space Data System Standards,
CCSDS 101.0-B-5. Blue Book. Issue 5. Washington, D.C.: CCSDS, June 2001.
[3] Packet Telemetry. Recommendation for Space Data System Standards, CCSDS 102.0-
B-5. Blue Book. Issue 5. Washington, D.C.: CCSDS, November 2000.
[4] Advanced Orbiting Systems, Networks and Data Links: Architectural Specification.
Recommendation for Space Data System Standards, CCSDS 701.0-B-3. Blue Book.
Issue 3. Washington, D.C.: CCSDS, June 2001.
[5] Time Code Formats. Recommendation for Space Data System Standards, CCSDS
301.0-B-3. Blue Book. Issue 3. Washington, D.C.: CCSDS, January 2002.
[6] Information Technology—Open Systems Interconnection—Basic Reference Model:
The Basic Model. International Standard, ISO/IEC 7498-1. 2nd ed. Geneva: ISO,
1994.
[7] Information Technology—Open Systems Interconnection—Specification of Abstract
Syntax Notation One (ASN.1). International Standard, ISO/IEC 8824:1990. 2nd ed.
Geneva: ISO, 1990.
[8] Information Technology—Open Systems Interconnection—The Directory: Models.
International Standard, ISO/IEC 9594-2:1998. 3rd ed. Geneva: ISO, 1998.
CCSDS 911.1-B-1 Page 1-13 April 2002
...