1、BS ISO 18441:2016Space data and informationtransfer systems Spacelink extension Applicationprogram interface for transferservices Core specificationBSI Standards PublicationWB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06BS ISO 18441:2016 BRITISH STANDARDNational forewordThis British Standar
2、d is the UK implementation of ISO 18441:2016. It supersedes BS ISO 18441:2013 which is withdrawn. The UK participation in its preparation was entrusted to TechnicalCommittee ACE/68, Space systems and operations.A list of organizations represented on this committee can beobtained on request to its se
3、cretary.This publication does not purport to include all the necessaryprovisions of a contract. Users are responsible for its correctapplication. The British Standards Institution 2016. Published by BSI Standards Limited 2016ISBN 978 0 580 93379 0ICS 49.140Compliance with a British Standard cannot c
4、onfer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy and Strategy Committee on 30 November 2016.Amendments/Corrigenda issued since publicationDate Text affectedBS ISO 18441:2016Reference number ISO 18441:2016(E) ISO 2016INTERNATIONAL STA
5、NDARDISO 18441Space data and information transfer systems Space link extension Application program interface for transfer services Core specification Systmes de transfert des informations et donnes spatiales Extension de liaisons spatiales Interface du programme dapplication pour les services de tra
6、nsfert Spcification de base Second edition 2016-11-15BS ISO 18441:2016ISO 18441:2016(E) COPYRIGHT PROTECTED DOCUMENT ISO 2016 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, in
7、cluding 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 ISOs member body in the country of the requester. ISO copyright office Ch. de Blandonnet 8 CP 401 CH-1214 Vernier, Geneva, Switzerlan
8、d Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 copyrightiso.org Web www.iso.org Published in Switzerland ii ISO 2016 All rights reservedBS ISO 18441:2016ISO 18441:2016(E) ISO 2016 All rights reserved iiiForeword ISO (the International Organization for Standardization) is a worldwide federation of na
9、tional 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. Intern
10、ational 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. The procedures used to develop this document and those inte
11、nded for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of ISO documents should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2. www.iso
12、.org/directives 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. Details of any patent rights identified during the development of the document will b
13、e in the Introduction and/or on the ISO list of patent declarations received. www.iso.org/patents Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement. For an explanation on the meaning of ISO specific terms and expressions rel
14、ated to conformity assessment, as well as information about ISOs adherence to the WTO principles in the Technical Barriers to Trade (TBT) see the following URL: Foreword - Supplementary information ISO 18441 was prepared by the Consultative Committee for Space Data Systems (CCSDS) (as CCSDS 914.0-M-
15、2, September 2015) 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. This second edition cancels and replaces the first
16、 edition (ISO 18441:2013), which has been technically revised. BS ISO 18441:2016CCSDS 914.0-M-2 Page ii September 2015 API FOR SLE TRANSFER SERVICESCORE SPECIFICATION STATEMENT OF INTENT The Consultative Committee for Space Data Systems (CCSDS) is an organization officially established by the manage
17、ment 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 Recomm
18、endations 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 sha
19、ll 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 o
20、f, 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
21、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 newdirections; or (3) be retired or canceled.In those instances when a new version of a Recommended Practice is issued, existing CCSDS-rela
22、ted 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 imp
23、lementations towards the later version of the Recommended Practice. ISO 18441:2016(E) ISO 2016 All rights reserved BS ISO 18441:2016CCSDS 914.0-M-2 Page iii September 2015 API FOR SLE TRANSFER SERVICESCORE SPECIFICATION FOREWORD Attention is drawn to the possibility that some of the elements of this
24、 document may be the subject of patent rights. CCSDS has processes for identifying patent issues and for securing from the patent holder agreement that all licensing policies are reasonable and non-discriminatory. However, CCSDS does not have a patent law staff, and CCSDS shall not be held responsib
25、le for identifying any or all such patent rights. Through the process of normal evolution, it is expected that expansion, deletion, or modification of this document may occur. This Recommended Standard is therefore subject to CCSDS document management and change control procedures, which are defined
26、 in Organization and Processes for the Consultative Committee for Space Data Systems (CCSDS A02.1-Y-4). 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 sent to the CCSDS Secretariat
27、 at the e-mail address indicated on page i. ISO 18441:2016(E) ISO 2016 All rights reserved BS ISO 18441:2016API FOR SLE TRANSFER SERVICESCORE SPECIFICATION CCSDS 914.0-M-2 Page iv September 2015 At time of publication, the active Member and Observer Agencies of the CCSDS were: Member Agencies Agenzi
28、a Spaziale Italiana (ASI)/Italy. Canadian Space Agency (CSA)/Canada. Centre National dEtudes Spatiales (CNES)/France. China National Space Administration (CNSA)/Peoples Republic of China. Deutsches Zentrum fr Luft- und Raumfahrt (DLR)/Germany. European Space Agency (ESA)/Europe. Federal Space Agency
29、 (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
30、 Policy Office (BFSPO)/Belgium. Central Research Institute of Machine Building (TsNIIMash)/Russian Federation. China Satellite Launch and Tracking Control General, Beijing Institute of Tracking andTelecommunications Technology (CLTC/BITTT)/China. Chinese Academy of Sciences (CAS)/China. Chinese Acad
31、emy of Space Technology (CAST)/China. Commonwealth Scientific and Industrial Research Organization (CSIRO)/Australia. Danish National Space Center (DNSC)/Denmark. Departamento de Cincia e Tecnologia Aeroespacial (DCTA)/Brazil. Electronics and Telecommunications Research Institute (ETRI)/Korea. Europ
32、ean 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
33、 Organization (ISRO)/India. Institute of Space Research (IKI)/Russian Federation. KFKI Research Institute for Particle differentiatesapplicability by SLEservice specificationversion; updates references.NOTE Substantive changes from the previous issue are marked with change bars in the inside margin.
34、 ISO 18441:2016(E) ISO 2016 All rights reservedBS ISO 18441:2016API FOR SLE TRANSFER SERVICESCORE SPECIFICATION CCSDS 914.0-M-2 Page vi September 2015 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-2 1.4 RATIONALE 1-3 1.5 DOC
35、UMENT STRUCTURE . 1-4 1.6 DEFINITIONS 1-7 1.7 REFERENCES . 1-10 2 DESCRIPTION OF THE SLE API . 2-1 2.1 INTRODUCTION 2-1 2.2 SPECIFICATION METHOD AND NOTATION . 2-2 2.3 LOGICAL VIEW . 2-7 2.4 SECURITY ASPECTS OF CORE SLE API CAPABILITIES 2-58 3 SPECIFICATION OF API COMPONENTS 3-1 3.1 INTRODUCTION 3-1
36、 3.2 API PROXY . 3-1 3.3 API SERVICE ELEMENT . 3-27 3.4 SLE OPERATIONS . 3-52 3.5 SLE UTILITIES . 3-56 3.6 SLE APPLICATION 3-64 3.7 HANDLING OF IN PROCESS THREADS AND EXTERNAL EVENTS 3-71 4 STATE TABLES 4-1 4.1 INTRODUCTION 4-1 4.2 NOTATION 4-1 4.3 GENERAL ERROR HANDLING CONVENTIONS 4-2 4.4 STATE TA
37、BLE FOR ASSOCIATIONS . 4-2 4.5 STATE TABLES FOR SERVICE INSTANCES 4-15 ANNEX A SPECIFICATION OF COMMON INTERFACES (NORMATIVE) A-1 ANNEX B RESULT CODES (NORMATIVE) B-1 ANNEX C STRUCTURE OF THE SERVICE INSTANCE IDENTIFIER FOR VERSION 1 OF THE SLE SERVICES RAF, RCF, AND CLTU (NORMATIVE) . C-1 ANNEX D S
38、IMPLE COMPONENT MODEL (NORMATIVE). D-1 ISO 18441:2016(E) ISO 2016 All rights reservedBS ISO 18441:2016API FOR SLE TRANSFER SERVICESCORE SPECIFICATION CCSDS 914.0-M-2 Page vii September 2015 CONTENTS (continued) Section Page ANNEX E CONFORMANCE (NORMATIVE) E-1 ANNEX F INTERACTION OF COMPONENTS (INFOR
39、MATIVE) . F-1 ANNEX G INTERFACE CROSS REFERENCE (INFORMATIVE) G-1 ANNEX H INDEX TO DEFINITIONS (INFORMATIVE) H-1 ANNEX I ACRONYMS AND ABBREVIATIONS (INFORMATIVE) I-1 ANNEX J INFORMATIVE REFERENCES (INFORMATIVE) . J-1 Figure 1-1 SLE Services and SLE API Documentation . 1-6 2-1 UML Stereotypes Used in
40、 This Recommended Practice 2-3 2-2 Top Level Decomposition of the API . 2-7 2-3 Structure of the Package API Proxy . 2-9 2-4 Reporting and Tracing by the Proxy . 2-10 2-5 Configuration Database of the Proxy 2-20 2-6 Structure of the Package API Service Element 2-23 2-7 Reporting and Tracing by the S
41、ervice Element 2-24 2-8 Sequential Control Interface Component Class Controlled Component 2-39 2-9 Concurrent Control Interface 2-43 2-10 Structure of the Package SLE Application . 2-44 2-11 Reporting and Tracing Interfaces Provided by the Application . 2-45 2-12 Operation Objects . 2-49 2-13 Operat
42、ion Object Interfaces for Common Association Management . 2-53 2-14 Common SLE Operation Objects . 2-54 2-15 SLE Utilities . 2-56 4-1 Processing Context for the Association State Table . 4-3 4-2 Processing Context for the Service Instance State Table . 4-16 B-1 Structure of Result Codes .B-1 F-1 Con
43、figuration of Components F-3 F-2 Configuration of Interfaces for Service Provisioning . F-3 F-3 Interaction of API Components F-4 F-4 Initialization and Shutdown F-5 F-5 Collaboration Diagram for Use of Operation Objects F-8 F-6 Sequence Diagram for Use of Operation Objects . F-9 F-7 User Side Bindi
44、ng (User Initiated Bind). F-12 F-8 User Side Unbinding (User Initiated Bind) F-13 F-9 Provider Side Binding (User Initiated Bind) F-14 F-10 Provider Side Unbinding (User Initiated Bind) F-16 ISO 18441:2016(E) ISO 2016 All rights reservedBS ISO 18441:2016API FOR SLE TRANSFER SERVICESCORE SPECIFICATIO
45、N CCSDS 914.0-M-2 Page viii September 2015 CONTENTS (continued) Table Page C-1 Identifiers and Abbreviations for Attributes .C-3 E-1 Optional Features for the API Proxy E-3 E-2 Optional Features for the API Service Element E-6 E-3 Parameters That May Be Constrained by a Proxy E-9 E-4 Parameters That
46、 May Be Constrained by a Service Element . E-10 ISO 18441:2016(E) ISO 2016 All rights reservedBS ISO 18441:2016API FOR SLE TRANSFER SERVICESCORE SPECIFICATION CCSDS 914.0-M-2 Page 1-1 September 2015 1 INTRODUCTION 1.1 PURPOSE OF THIS RECOMMENDED PRACTICE The purpose of this Recommended Practice is t
47、o define a C+ Application Program Interface (API) for CCSDS Space Link Extension (SLE) Transfer Services, which is independent of any specific technology used for communications between an SLE service user and an SLE service provider. This API is intended for use by application programs implementing
48、 SLE services. It can be configured to support SLE service user applications or SLE service provider applications. This API is also intended to simplify the implementation of gateways that are required to achieve interoperability between SLE service provider and SLE service user applications using d
49、ifferent communications technologies. Using this Application Program Interface Recommended Practice, API implementations (software packages) able to run on specific platforms can be developed. Once developed, such a package can be supplied to new users of SLE services for integration with their user or production facilities, thus minimizing their investment to buy into SLE support. 1.2 SCOPE 1.2.1 ITEMS COVERED BY THIS RECOMMENDED PRACTICE This Recommended Practice defines the Applicatio
