Recommendation for Space Data System Practices



Download 2.26 Mb.
Page6/35
Date31.07.2017
Size2.26 Mb.
#24990
1   2   3   4   5   6   7   8   9   ...   35

1.6Definitions

1.6.1Definition of Terms used in this Document

1.6.1.1Definitions from the SLE Reference Model


This Recommended Practice makes use of the following terms defined in reference [3]:

  1. invoker;

  2. offline delivery mode;

  3. online delivery mode;

  4. operation;

  5. performer;

  6. service provider (provider);

  7. service user (user);

  8. SLE protocol data unit (SLE-PDU);

  9. SLE transfer service instance (service instance);

  10. SLE transfer service production (service production);

  11. SLE transfer service provision (service provision);

  12. SLE transfer service provision period (provision period).

1.6.1.2Definitions from the ISO Abstract Service Definitions and Conventions


This Recommended Practice makes use of the following terms defined in reference [19]:

  1. initiator;

  2. responder.

1.6.1.3Definitions from SLE Transfer Service Specifications


This Recommended Practice makes use of the following terms defined in references [4], [5], [6], [7], and [8]:

  1. association;

  2. communications service;

  3. confirmed operation;

  4. invocation;

  5. parameter (of an operation);

  6. port identifier;

  7. return;

  8. unconfirmed operation.

1.6.1.4Additional Definitions

1.6.1.4.1General

For the purpose of this Recommended Practice, the following definitions also apply:
1.6.1.4.2Component

A software module, providing a well-defined service via a set of interfaces. In this document the term component is used only to refer to the API components defined by this Recommended Practice.
1.6.1.4.3Component Interface

An interface exported by a component.
1.6.1.4.4Component Object

An object within a component that can be accessed by one or more interfaces exported by the component. Objects providing more than one interface support navigation between these interfaces.
1.6.1.4.5Client

A software entity that uses the services of a component or of an object by invocation of the methods of an interface provided by the component or object. In this Recommended Practice the qualified term ‘local client’ is used to stress the difference between an interface to a software entity on the same computer and the interface between an SLE service user and an SLE service provider.
1.6.1.4.6Interface

The abstraction of a service that only defines the operations supported by that service, but not their implementations. The specification of an operation is referred to as a method.

1.6.2Nomenclature

1.6.2.1Normative Text


The following conventions apply for the normative specifications in this Recommended Standard:

  1. the words ‘shall’ and ‘must’ imply a binding and verifiable specification;

  2. the word ‘should’ implies an optional, but desirable, specification;

  3. the word ‘may’ implies an optional specification;

  4. the words ‘is’, ‘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.6.2.2Informative Text


In the normative sections of this document, informative text is set off from the normative specifications either in notes or under one of the following subsection headings:

  • Overview;

  • Background;

  • Rationale;

  • Discussion.

1.6.2.3Use of the Term ‘Client’


In a complete SLE API, the API Proxy interacts with the API Service Element in the same process and with a peer proxy across the network. However, the proxy might also be used in an environment where some other software entity interfaces locally to the proxy and supplies the interfaces defined for the API Service Element. An example for such a configuration is a gateway. Therefore this specification uses the term ‘client’ when referring to the entity with which the proxy interacts locally.

Where it is necessary to explicitly distinguish between interaction with the peer proxy across the network and interactions with the client on the local computer, the qualified term ‘local client’ is used.


1.6.2.4Use of the Term ‘Release’


The term ‘release an object’ (or a resource) must be understood to mean that all actions shall be taken that are required to free the allocated memory or other operating system resources. For interfaces defined in this specification, this means that the method Release() must be called for every reference to an interface that a component holds. (See annex A.1.48.1.1.1.1.2 for a description of the method Release() and of the reference counting scheme.)

1.7References


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 investigate the possibility of applying the most recent editions of the documents indicated below. The CCSDS Secretariat maintains a register of currently valid CCSDS documents.

NOTE – A list of informative references is provided in annex A.1.81.1.1.1.1.3.

[1] Time Code Formats. Issue 4. Recommendation for Space Data System Standards (Blue Book), CCSDS 301.0-B-4. Washington, D.C.: CCSDS, November 2010.

[2] Cross Support Concept—Part 1: Space Link Extension Services. Issue 3. Report Concerning Space Data System Standards (Green Book), CCSDS 910.3-G-3. Washington, D.C.: CCSDS, March 2006.

[3] Cross Support Reference Model—Part 1: Space Link Extension Services. Issue 2. Recommendation for Space Data System Standards (Blue Book), CCSDS 910.4-B-2. Washington, D.C.: CCSDS, October 2005.

[4] Space Link Extension—Return All Frames Service Specification. Issue 3. Recommendation for Space Data System Standards (Blue Book), CCSDS 911.1-B-3. Washington, D.C.: CCSDS, January 2010.

[5] Space Link Extension—Return Channel Frames Service Specification. Issue 2. Recommendation for Space Data System Standards (Blue Book), CCSDS 911.2-B-2. Washington, D.C.: CCSDS, January 2010.

[6] Space Link Extension—Return Operational Control Fields Service Specification. Issue 2. Recommendation for Space Data System Standards (Blue Book), CCSDS 911.5-B-2. Washington, D.C.: CCSDS, January 2010.

[7] Space Link Extension—Forward CLTU Service Specification. Issue 3. Recommendation for Space Data System Standards (Blue Book), CCSDS 912.1-B-3. Washington, D.C.: CCSDS, July 2010.

[8] Space Link Extension—Forward Space Packet Service Specification. Issue 2. Recommendation for Space Data System Standards (Blue Book), CCSDS 912.3-B-2. Washington, D.C.: CCSDS, July 2010.

[9] Space Link Extension—Internet Protocol for Transfer Services. Issue 2. Recommendation for Space Data System Standards (Blue Book), CCSDS 913.1-B-2. Washington, D.C.: CCSDS, September 2015.

[10] Space Link Extension—Application Program Interface for Return All Frames Service. Issue 2. Recommendation for Space Data System Practices (Magenta Book), CCSDS 915.1-M-2. Washington, D.C.: CCSDS, September 2015.

[11] Space Link Extension—Application Program Interface for Return Channel Frames Service. Issue 2. Recommendation for Space Data System Practices (Magenta Book), CCSDS 915.2-M-2. Washington, D.C.: CCSDS, September 2015.

[12] Space Link Extension—Application Program Interface for Return Operational Control Fields Service. Issue 2. Recommendation for Space Data System Practices (Magenta Book), CCSDS 915.5-M-2. Washington, D.C.: CCSDS, September 2015.

[13] Space Link Extension—Application Program Interface for the Forward CLTU Service. Issue 2. Recommendation for Space Data System Practices (Magenta Book), CCSDS 916.1-M-2. Washington, D.C.: CCSDS, September 2015.

[14] Space Link Extension—Application Program Interface for the Forward Space Packet Service. Issue 2. Recommendation for Space Data System Practices (Magenta Book), CCSDS 916.3-M-2. Washington, D.C.: CCSDS, September 2015.

[15] Information Technology—Abstract Syntax Notation One (ASN.1): Specification of Basic Notation. 4th ed. International Standard, ISO/IEC 8824-1:2008. Geneva: ISO, 2008.

[16] Information Technology—ASN.1 Encoding Rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). 4th ed. International Standard, ISO/IEC 8825-1:2002. Geneva: ISO, 2008.

[17] Information Technology—Open Systems Interconnection—The Directory—Part 2: Models. 7th ed. International Standard, ISO/IEC 9594-2:2014. Geneva: ISO, 2014.

[18] Information Technology—Open Systems Interconnection—The Directory—Part 8: Public-Key and Attribute Certificate Frameworks. 7th ed. International Standard, ISO/IEC 9594-8:2014. Geneva: ISO, 2014.

[19] Information Technology—Text Communication—Message-Oriented Text Interchange Systems (MOTIS)—Part 3: Abstract Service Definition Conventions. International Standard, ISO/IEC 10021-3:1990 [Withdrawn]. Geneva: ISO, 1990.

[20] Programming Languages—C++. 3rd ed. International Standard, ISO/IEC 14882:2011. Geneva: ISO, 2011.

[21] Secure Hash Standard (SHS). Federal Information Processing Standards Publication 180-4. Gaithersburg, Maryland: NIST, March 2012.

1   2   3   4   5   6   7   8   9   ...   35



The database is protected by copyright ©ininet.org 2024
send message
    Main page
possibility that some
management council