Space data and information transfer systems — Mission Operations Message Abstraction Layer - JAVA API

ISO 20210:2015 is the definition of all concepts and terms that establish a Java API for consuming and providing MO services on top of the MAL. The MAL Java API is intended to maximize the portability of the MO components across various underlying MAL implementations and transport protocols.

Systèmes de transfert des informations et données spatiales — Couche d'abstraction des messages des opérations de mission — JAVA API

General Information

Status
Published
Publication Date
10-Aug-2015
Current Stage
9093 - International Standard confirmed
Start Date
14-Nov-2023
Completion Date
19-Apr-2025
Ref Project
Standard
ISO 20210:2015 - Space data and information transfer systems -- Mission Operations Message Abstraction Layer - JAVA API
English language
276 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


INTERNATIONAL ISO
STANDARD 20210
First edition
2015-08-15
Space data and information transfer
systems — Mission Operations
Message Abstraction Layer - JAVA API
Systèmes de transfert des informations et données spatiales — Couche
d’abstraction des messages des opérations de mission — JAVA API
Reference number
©
ISO 2015
© ISO 2015, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO 2015 – 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 20210 was prepared by the Consultative Committee for Space Data Systems (CCSDS) (as
CCSDS 523.1-M-1, April 2013) 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.

Recommendation for Space Data System Practices
MISSION OPERATIONS
MESSAGE
ABSTRACTION LAYER—
JAVA API
RECOMMENDED PRACTICE
CCSDS 523.1-M-1
MAGENTA BOOK
April 2013
CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API
AUTHORITY
Issue: Recommended Practice, Issue 1
Date: April 2013
Location: 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 documents is detailed in Organization and Processes for
the Consultative Committee for Space Data Systems (CCSDS A02.1-Y-3), 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
Space Communications and Navigation Office, 7L70
Space Operations Mission Directorate
NASA Headquarters
Washington, DC 20546-0001, USA
CCSDS 523.1-M-1 Page i April 2013
CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API
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 Recommendations and are not in
themselves considered binding on any Agency.
CCSDS Recommendations take two forms: Recommended Standards that are prescriptive
and are the formal vehicles by which CCSDS Agencies create the standards that specify how
elements of their space mission support infrastructure shall operate and interoperate with
others; and Recommended Practices that are more descriptive in nature and are intended to
provide general guidance about how to approach a particular problem associated with space
mission support. This Recommended Practice is issued by, and represents the consensus of,
the CCSDS members. Endorsement of this Recommended Practice is entirely voluntary
and does not imply a commitment by any Agency or organization to implement its
recommendations in a prescriptive sense.
No later than five years from its date of issuance, this Recommended Practice 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 Practice is issued, existing
CCSDS-related member Practices and implementations are not negated or deemed to be non-
CCSDS compatible. It is the responsibility of each member to determine when such Practices
or implementations are to be modified. Each member is, however, strongly encouraged to
direct planning for its new Practices and implementations towards the later version of the
Recommended Practice.
CCSDS 523.1-M-1 Page ii April 2013
CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API
FOREWORD
Through the process of normal evolution, it is expected that expansion, deletion, or
modification of this document may occur. This Recommended Practice is therefore subject
to CCSDS document management and change control procedures, which are defined in the
Organization and Processes for the Consultative Committee for Space Data Systems
(CCSDS A02.1-Y-3). 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 523.1-M-1 Page iii April 2013
CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API
At time of publication, the active Member and Observer Agencies of the CCSDS were:
Member Agencies
– Agenzia Spaziale Italiana (ASI)/Italy.
– Canadian Space Agency (CSA)/Canada.
– Centre National d’Etudes Spatiales (CNES)/France.
– China National Space Administration (CNSA)/People’s Republic of China.
– Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR)/Germany.
– European Space Agency (ESA)/Europe.
– Federal Space Agency (FSA)/Russian Federation.
– Instituto Nacional de Pesquisas Espaciais (INPE)/Brazil.
– Japan Aerospace Exploration Agency (JAXA)/Japan.
– National Aeronautics and Space Administration (NASA)/USA.
– UK Space Agency/United Kingdom.
Observer Agencies
– Austrian Space Agency (ASA)/Austria.
– Belgian Federal Science Policy Office (BFSPO)/Belgium.
– Central Research Institute of Machine Building (TsNIIMash)/Russian Federation.
– China Satellite Launch and Tracking Control General, Beijing Institute of Tracking
and Telecommunications Technology (CLTC/BITTT)/China.
– Chinese Academy of Sciences (CAS)/China.
– Chinese Academy of Space Technology (CAST)/China.
– Commonwealth Scientific and Industrial Research Organization (CSIRO)/Australia.
– CSIR Satellite Applications Centre (CSIR)/Republic of South Africa.
– Danish National Space Center (DNSC)/Denmark.
– Departamento de Ciência e Tecnologia Aeroespacial (DCTA)/Brazil.
– European Organization for the Exploitation of Meteorological Satellites
(EUMETSAT)/Europe.
– European Telecommunications Satellite Organization (EUTELSAT)/Europe.
– Geo-Informatics and Space Technology Development Agency (GISTDA)/Thailand.
– 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.
– Korea Aerospace Research Institute (KARI)/Korea.
– Ministry of Communications (MOC)/Israel.
– National Institute of Information and Communications Technology (NICT)/Japan.
– National Oceanic and Atmospheric Administration (NOAA)/USA.
– National Space Agency of the Republic of Kazakhstan (NSARK)/Kazakhstan.
– National Space Organization (NSPO)/Chinese Taipei.
– Naval Center for Space Technology (NCST)/USA.
– Scientific and Technological Research Council of Turkey (TUBITAK)/Turkey.
– Space and Upper Atmosphere Research Commission (SUPARCO)/Pakistan.
– Swedish Space Corporation (SSC)/Sweden.
– United States Geological Survey (USGS)/USA.
CCSDS 523.1-M-1 Page iv April 2013
CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API
DOCUMENT CONTROL
Document Title Date Status
CCSDS Mission Operations Message April 2013 Current issue
523.1-M-1 Abstraction Layer—JAVA API,
Recommended Practice, Issue 1
CCSDS 523.1-M-1 Page v April 2013
CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API
CONTENTS
Section Page
1  INTRODUCTION . 1-1

1.1  PURPOSE OF THIS RECOMMENDED PRACTICE . 1-1
1.2  SCOPE . 1-1
1.3  APPLICABILITY . 1-1
1.4  RATIONALE . 1-1
1.5  DOCUMENT STRUCTURE . 1-1
1.6  DEFINITIONS . 1-2
1.7  CONVENTIONS . 1-2
1.8  REFERENCES . 1-4

2  OVERVIEW . 2-1

2.1  GENERAL . 2-1
2.2  MO SERVICE FRAMEWORK JAVA MAPPING . 2-3
2.3  MAPPING FROM MAL DOCUMENT . 2-5

3  MAL API . 3-1

3.1  GENERAL . 3-1
3.2  MAL PACKAGE . 3-3
3.3  DATA STRUCTURES PACKAGE . 3-40
3.4  CONSUMER PACKAGE . 3-58
3.5  PROVIDER PACKAGE . 3-94
3.6  BROKER PACKAGE . 3-134

4  SERVICE MAPPING . 4-1

4.1  OVERVIEW . 4-1
4.2  DEFINITION . 4-1
4.3  CONSUMER . 4-8
4.4  PROVIDER . 4-25
4.5  DATA STRUCTURES . 4-40
4.6  ELEMENT FACTORY CLASSES . 4-50
4.7  MULTIPLE ELEMENT BODY CLASSES . 4-51
4.8  HELPER AND ELEMENT FACTORY CLASSES . 4-53

5  TRANSPORT API . 5-1

5.1  GENERAL . 5-1
5.2  CLASSES AND INTERFACES . 5-1

CCSDS 523.1-M-1 Page vi April 2013
CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API
CONTENTS (continued)
Section Page
6  ACCESS CONTROL API . 6-1

6.1  GENERAL . 6-1
6.2  CLASSES AND INTERFACES . 6-1

7  ENCODING API . 7-1

7.1  OVERVIEW .
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.