GSO ISO 18440:2017

Gulf Standard   Current Edition
· Approved on 03 October 2017 ·

Space data and information transfer systems -- Space Link Extension -- Internet Protocol for Transfer Services

Space systems and operations
Including space data and information transfer systems, and ground support equipment for launch site operations

GSO ISO 18440:2017 Files

English 67 Pages
Current Edition Reference Language
85.35 OMR

GSO ISO 18440:2017 Scope

The Space Link Extension (SLE) Reference Model identifies a set of SLE Transfer Services that enable missions to send forward space link data units to a spacecraft and to receive return space link data units from a spacecraft. A subset of these services is specified by the SLE Transfer Service Recommended Standards. The SLE Transfer Service Recommended Standards specify: a) the operations necessary to provide the transfer 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. However, they deliberately do not specify the methods or technologies required for communications. The purpose of this International Standard is to define a protocol for transfer of SLE Protocol Data Units (PDUs) defined in the SLE Transfer Service Recommended Standards using the Internet protocols TCP (Transmission Control Protocol and IP (Internet Protocol) for data transfer and the Abstract Syntax Notation One (ASN.1) for data encoding. This protocol is referred to as the Internet SLE Protocol One (ISP1). This International Standard defines a protocol for transfer of SLE PDUs between an SLE user and an SLE provider system in terms of: a) the procedures used to establish and release associations; b) the messages exchanged on an established association; c) the procedures used to monitor the status of data communication connections; and d) the methods used to ensure that data are converted between different formats and representations on different platforms. It does not specify: a) individual designs, implementations, or products; b) the configuration of the data communications infrastructure, including configuration of the TCP and IP protocols; c) the means by which addresses (IP addresses and TCP port numbers) are agreed, assigned, and communicated. This International Standard responds to the requirements imposed by the International Standards for SLE transfer services that were available when this International Standard was released. The protocol specified in this International Standard conforms to the requirements on data communication services set forth in those International Standard The scope and field of application are furthermore detailed in subclause 1.3 of the enclosed CCSDS publication.

Best Sellers From Information Sector

OS GSO ISO/TR 18492:2017
GSO ISO/TR 18492:2017 
Omani Standard
Long-term preservation of electronic document-based information
GSO ISO/TR 18492:2017
ISO/TR 18492:2005 
Gulf Standard
Long-term preservation of electronic document-based information
GSO ISO/TR 13028:2013
ISO/TR 13028:2010 
Gulf Standard
Information and documentation - Implementation guidelines for digitization of records
GSO ISO 16175-2:2013
ISO 16175-2:2011 
Gulf Standard
Information and documentation -- Principles and functional requirements for records in electronic office environments -- Part 2: Guidelines and functional requirements for digital records management systems

Recently Published from Information Sector

GSO ISO/IEC TR 3445:2024
ISO/IEC TR 3445:2022 
Gulf Standard
Information technology — Cloud computing — Audit of cloud services
GSO ISO/IEC 30169:2024
ISO/IEC 30169:2022 
Gulf Standard
Internet of Things (IoT) — IoT applications for electronic label system (ELS)
GSO ISO/IEC 30162:2024
ISO/IEC 30162:2022 
Gulf Standard
Internet of Things (IoT) — Compatibility requirements and model for devices within industrial IoT systems
GSO ISO/IEC 30107-3:2024
ISO/IEC 30107-3:2023 
Gulf Standard
Information technology — Biometric presentation attack detection — Part 3: Testing and reporting