1、BSI Standards PublicationBS ISO 20210:2015Space data and informationtransfer systems MissionOperations MessageAbstraction Layer - JAVA APIBS ISO 20210:2015 BRITISH STANDARDNational forewordThis British Standard is the UK implementation of ISO 20210:2015.The UK participation in its preparation was en
2、trusted to Technical Committee ACE/68, Space systems and operations.A list of organizations represented on this committee can be obtained on request to its secretary.This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct applica
3、tion. The British Standards Institution 2015.Published by BSI Standards Limited 2015ISBN 978 0 580 87910 4 ICS 49.140 Compliance with a British Standard cannot confer immunity from legal obligations.This British Standard was published under the authority of the Standards Policy and Strategy Committe
4、e on 31 December 2015.Amendments/corrigenda issued since publicationDate T e x t a f f e c t e dBS ISO 20210:2015 ISO 2015Space data and information transfer systems Mission Operations Message Abstraction Layer - JAVA APISystmes de transfert des informations et donnes spatiales Couche dabstraction d
5、es messages des oprations de mission JAVA APIINTERNATIONAL STANDARDISO20210First edition2015-08-15Reference numberISO 20210:2015(E)BS ISO 20210:2015ISO 20210:2015(E)ii ISO 2015 All rights reservedCOPYRIGHT PROTECTED DOCUMENT ISO 2015, Published in SwitzerlandAll rights reserved. Unless otherwise spe
6、cified, 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
7、ISOs member body in the country of the requester.ISO copyright officeCh. de Blandonnet 8 CP 401CH-1214 Vernier, Geneva, SwitzerlandTel. +41 22 749 01 11Fax +41 22 749 09 47copyrightiso.orgwww.iso.orgBS ISO 20210:2015ISO 20210:2015(E) ISO 2015 All rights reserved iiiForeword ISO (the International Or
8、ganization 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 establ
9、ished 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 standardizati
10、on. 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.
11、 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 pa
12、tent 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, Subc
13、ommittee SC 13, Space data and information transfer systems. BS ISO 20210:2015BS ISO 20210:2015Recommendation for Space Data System Practices MISSION OPERATIONS MESSAGE ABSTRACTION LAYERJAVA API RECOMMENDED PRACTICE CCSDS 523.1-M-1 MAGENTA BOOK April 2013 BS ISO 20210:2015CCSDS RECOMMENDED PRACTICE
14、FOR MO MAL JAVA API CCSDS 523.1-M-1 Page i April 2013 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 th
15、e 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 a
16、uthorization 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 ISO 20
17、210:2015(E) ISO 2015 All rights reservedBS ISO 20210:2015CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API CCSDS 523.1-M-1 Page ii April 2013 STATEMENT OF INTENT The Consultative Committee for Space Data Systems (CCSDS) is an organization officially established by the management of its members. The Com
18、mittee 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 the
19、mselves 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
20、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. Endors
21、ement 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 wh
22、ether 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 i
23、mplementations 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 l
24、ater version of the Recommended Practice. ISO 20210:2015(E) ISO 2015 All rights reservedBS ISO 20210:2015CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API CCSDS 523.1-M-1 Page iii April 2013 FOREWORD Through the process of normal evolution, it is expected that expansion, deletion, or modification of th
25、is 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 maint
26、ained 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. ISO 20210:2015(E) ISO 2015 All rights reservedBS ISO 20210:2015CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA A
27、PI CCSDS 523.1-M-1 Page iv April 2013 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 dEtudes Spatiales (CNES)/France. China National Space Administration (CN
28、SA)/Peoples Republic of China. Deutsches Zentrum fr 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 Aeronautic
29、s 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 Cont
30、rol 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 Cent
31、re (CSIR)/Republic of South Africa. Danish National Space Center (DNSC)/Denmark. Departamento de Cincia e Tecnologia Aeroespacial (DCTA)/Brazil. European Organization for the Exploitation of Meteorological Satellites (EUMETSAT)/Europe. European Telecommunications Satellite Organization (EUTELSAT)/Eu
32、rope. 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 b) section 2 gives an overview
33、 of the API; c) section 3 defines the MAL API that represents the MAL service interface; d) section 4 defines how a MAL service specification is mapped to Java; e) section 5 defines the transport API that represents the MAL transport interface; ISO 20210:2015(E) ISO 2015 All rights reservedBS ISO 20
34、210:2015CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API CCSDS 523.1-M-1 Page 1-2 April 2013 f) section 6 defines the access control API that represents the MAL access control interface; g) section 7 defines the encoding API, an optional set of interfaces that can be used by the transport layer in ord
35、er to externalize the encoding behaviour. NOTE Some application code examples are given in annex C. 1.6 DEFINITIONS Attribute: Either a field of a Java class called attribute, the data type MAL:Attribute, or the interface Attribute defined in the MAL Java API. 1.7 CONVENTIONS 1.7.1 NOMENCLATURE The
36、following conventions apply for the normative specifications in this Recommended Practice: 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 i
37、s, are, and will imply statements of fact. NOTE These conventions do not imply constraints on diction in text that is clearly informative in nature. 1.7.2 INFORMATIVE TEXT In the normative sections of this document (sections 3-7), informative text is set off from the normative specifications either
38、in notes or under one of the following subsection headings: Overview; Background; Rationale; Discussion. ISO 20210:2015(E) ISO 2015 All rights reservedBS ISO 20210:2015CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API CCSDS 523.1-M-1 Page 1-3 April 2013 1.7.3 USE OF CAPITAL LETTERS Names of interfaces
39、and classes of the MAL Java API are shown with the first letter of each word capitalized. 1.7.4 CODE TEMPLATE VARIABLES Some code templates are given throughout this document. Those templates are parameterized with variables. A variable is used by placing its name between the enclosing characters .
40、For example, the variable method name is used in the following code line: public void () If a variable contains a list of values, then the values are iterated with the following syntax: The variable i is the iteration index starting from 0. The variable N is the size of the list minus one. If the li
41、st size is zero, then nothing is written in the code template. If the list size is greater than zero, then the part is iterated N times and the part is finally written in the code template. For example, the variable type contains a list of types. A method m taking those types as parameters is declar
42、ed as follows: public void m( p, p) If the list is empty, then the result is: public void m() If the list contains one element A then the result is: public void m(A p0) The names of variables are not case-sensitive: field name and FIELD NAME designate the same variable. ISO 20210:2015(E) ISO 2015 Al
43、l rights reservedBS ISO 20210:2015CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API CCSDS 523.1-M-1 Page 1-4 April 2013 However, the value of the variable is case sensitive following the rules explained in table 1-1. Table 1-1: Variable Value Case Rules Variable name case Variable value case All the le
44、tters in lower case. Example: No change First letter in upper case and the other in lower case. Example: No change except the first letter in upper case All the letters in upper case. Example: Upper case All the letters in lower case and between an initial and final character !. Example: Lower case
45、1.7.5 JAVA CLASS PACKAGES In the code templates, the package of classes is not indicated if there is no ambiguity. However, the real Java code needs either to prefix the package name to the class name or to declare the package in an import clause at the beginning of the class definition. 1.8 REFEREN
46、CES The following documents contain provisions which, through reference in this text, constitute provisions of this Recommended Practice. At the time of publication, the editions indicated were valid. All documents are subject to revision, and users of this Recommended Practice are encouraged to inv
47、estigate the possibility of applying the most recent editions of the documents indicated below. The CCSDS Secretariat maintains a register of currently valid CCSDS documents. 1 Mission Operations Message Abstraction Layer. Recommendation for Space Data System Standards, CCSDS 521.0-B-1. Blue Book. I
48、ssue 1. Washington, D.C.: CCSDS, October 2010. 2 James Gosling, et al. The Java Language Specification. 3rd Ed. Boston: Addison-Wesley, 2005. 3 T. Berners-Lee, R. Fielding, U.C. Irvine, and L. Masinter. Uniform Resource Identifiers (URI): Generic Syntax. RFC 2396. Reston, Virginia: ISOC, August 1998
49、. ISO 20210:2015(E) ISO 2015 All rights reservedBS ISO 20210:2015CCSDS RECOMMENDED PRACTICE FOR MO MAL JAVA API CCSDS 523.1-M-1 Page 1-5 April 2013 4 R. Hinden, B. Carpenter, and L. Masinter. Format for Literal IPv6 Addresses in URLs. RFC 2732. Reston, Virginia: ISOC, December 1999. NOTE Informative references are listed in annex B. ISO 20210:2015(E) ISO 2015 All rights reservedBS ISO 20210:2015CCSDS RECOMMENDE
