LOGIC : Communications/Position, Navigation, and Timing (PNT)

1. International Deep Space Interoperability Standards - https://www.internationaldeepspacestandards.com/

1.1. International Communication System Interoperability Standards (ICSIS)

The purpose of the ICSIS document is to define the functional, interface and performance standards necessary to support interoperable and compatible communications between a human exploration spacecraft, ground infrastructure, and other space and surface vehicles that interface with the human exploration spacecraft.

The scope of the standard is for deep space human spaceflight missions and spacecraft that interface with human missions (i.e. visiting vehicles, landers, etc.). The focus of this version of the document is on a space vehicle/platform used for human exploration in cislunar space, a Cislunar Space Platform (CSP) used for human exploration, and its interfaces. This CSP could be transiting in space or orbiting the moon. Extensibility to other deep space human missions has also been considered and where practicable the document includes content that is also relevant to future deep space human exploration missions. Future revisions of the document will incorporate any additional information or modifications needed for deep space human exploration missions. Further definition of what is covered in the current version and what will be addressed in future revisions is given in Table 3.2-1, Baseline Standards Content. Interoperable, cross supportable, and compatible communications between space vehicles/systems, ground infrastructure, etc. is critical to the success of human exploration. It enables interchangeable use of National Aeronautics and Space Administration (NASA), International Partner, and commercial assets; decreases development and procurement costs; and reduces operational and training complexity.


1.2. International Thermal System Interoperability Standards (ITSIS)

All spacecraft require a thermal management system to maintain a tolerable thermal environment for the spacecraft crew and/or equipment. The purpose of this document is to state standards for when common fluids are employed in active external and internal coolant loops and agreed-to requirements for coldplates that interface directly to those coolant loops. Future revisions of the document will incorporate any additional content for deep space missions that is not already included. This standard supports reliability and commonality for cooling systems that work across elements, when there is agreement to utilize common coolant(s). This document also provides basic, common design parameters to allow developers to independently develop and/or provide compatible coldplates.


2. International Organization for Standardization (ISO) - https://www.iso.org

2.1. Space systems - Global navigation satellite system (GNSS) receiver class codes (ISO 24245:2023)

This document specifies class codes to classify global navigation satellite system (GNSS) receivers. The class codes represent how signals transmitted from radionavigation satellites are processed. This document applies to all types of GNSS receiver devices. The class codes in this document are not applicable to the following items:

  • condition of radionavigation satellites;
  • radio propagation environment including multipath, masking and obstacle;
  • additional antenna of a receiver device;
  • additional application software in a receiver device.


2.2. Space data and information transfer systems - Time code formats (ISO 11104:2011)

ISO 11104:2011 establishes a small number of standardized recommended time code formats for use in data interchange applications between agencies of the CCSDS. ISO 11104:2011 does not address timing performance issues such as stability, precision, accuracy, etc.

Time codes are digital representations of time information. ISO 11104:2011 describes four standard recommended time codes (one "unsegmented" and three "segmented" codes) which use the international standard second as the fundamental unit of time. An unsegmented time code is a pure binary count of time units and fractional time units from a starting time called the "epoch". A segmented time code is one in which the count of time units and fractional time units is accumulated in two or more cascaded counters which count modulo of various bases and start from the epoch.


3. Internet Engineering Task Force (IETF) - https://www.ietf.org/

3.1. QUIC: A UDP-Based Multiplexed and Secure Transport (RFC 9000)

This document defines the core of the Quick User Datagram Protocol Internet Connections (QUIC) transport protocol. QUIC provides applications with flow-controlled streams for structured communication, low-latency connection establishment, and network path migration. QUIC includes security measures that ensure confidentiality, integrity, and availability in a range of deployment circumstances. Accompanying documents describe the integration of Transport Layer Security (TLS) for key negotiation, loss detection, and an exemplary congestion control algorithm.


3.2. Bundle Protocol Version 7 (RFC 9171)

This document presents a specification for the Bundle Protocol, adapted from the experimental Bundle Protocol specification developed by the Delay-Tolerant Networking Research Group of the Internet Research Task Force and documented in RFC 5050.


4. Interoperability Plenary - https://www.interoperabilityplenary.org/home.aspx

4.1. Space Frequency Coordination Group (SFCG)

The SFCG was established in order to provide a less formal and more flexible environment, as compared to the official organs of the International Telecommunications Union (ITU) (i.e., Radiocommunication Bureau (RB); Radio Communication Study Groups (SG) of the Radiocommunication Sector), for the solution of frequency management problems encountered by member space agencies. The Terms of Reference and other aspects of SFCG organization and procedures may be found in Section II of the SFCG Handbook.

The SFCG is concerned with the effective use and management of those radio frequency bands that are allocated by the Radio Regulations of the ITU to the Space Research, Space Operations, Earth Exploration Satellite, and Meteorological Satellite services. The Group will also concern itself with feeder links and data relay satellites operated in connection with these services, and with satellite-borne radio astronomy (including radar astronomy). Within the formal framework of the Radio Regulations, there is the need and opportunity for international informal agreement among participating space agencies concerning assignment of specific frequencies, and related technical issues.

The principal result of SFCG meetings is the adoption of resolutions and recommendations which express technical and administrative agreements. These agreements may be used by space agencies to make best use of allocated bands and to avoid interference.

To date, the SFCG has issued technical resolutions (25), recommendations (38), and reports (22).


4.2. Interagency Operations Advisory Group (IOAG)

The IOAG was founded by the Interoperability Plenary (IOP) to:

  1. Understand issues related to interagency interoperability and other space communications matters;
  2. Identify solutions complying with IOP policies; and,
  3. Recommend resolutions to the IOP for specific actions by the IOP.

The IOAG provides a forum for identifying common needs across multiple agencies related to mission operations, space communications, and navigation interoperability. The IOAG will undertake activities it deems appropriate related to multi-agency space communications. A specific IOAG goal is the achievement of full interoperability among member space agencies.

The IOAG has reports (14), some of which contain requirements stated with "shalls."



  1. The IOAG has several active sub-groups - https://www.ioag.org/Lists/Participants/Active%20Subgroups.aspx

5. Consultative Committee for Space Data Systems (CCSDS) - https://public.ccsds.org/default.aspx

5.1. Lossless Data Compression (CCSDS 121.0-B-3)

5.2. Image Data Compression (CCSDS 122.0-B-2)

5.3. Spectral Preprocessing Transform for Multispectral and Hyperspectral Image Compression (CCSDS 122.1-B-1)

5.4. Low-Complexity Lossless and Near-Lossless Multispectral and Hyperspectral Image Compression (CCSDS 123.0-B-2)

5.4.1. Technical Corrigendum 1 to CCSDS 123.0-B-2, Issued February 2019 (CCSDS 123.0-B-2 Cor. 1)

5.4.2. Technical Corrigendum 2 to CCSDS 123.0-B-2, Issued February 2019 (CCSDS 123.0-B-2 Cor. 2)

5.4.3. Technical Corrigendum 3 to CCSDS 123.0-B-2, Issued February 2019 (CCSDS 123.0-B-2 Cor. 3)

5.5. Robust Compression of Fixed-Length Housekeeping Data (CCSDS 124.0-B-1)

5.6. TM Synchronization and Channel Coding (CCSDS 131.0-B-5)

5.7. Flexible Advanced Coding and Modulation Scheme for High Rate Telemetry Applications (CCSDS 131.2-B-2)

5.8. CCSDS Space Link Protocols over ETSI DVB-S2 Standard (CCSDS 131.3-B-2)

5.9. TM Space Data Link Protocol (CCSDS 132.0-B-3)

5.10. Space Packet Protocol (CCSDS 133.0-B-2)

5.11. Encapsulation Packet Protocol (CCSDS 133.1-B-3)

5.12. Optical Communications Physical Layer (CCSDS 141.0-B-1)

5.13. Optical Communications Coding and Synchronization (CCSDS 142.0-B-1)

5.14. Proximity-1 Space Link Protocol-Data Link Layer (CCSDS 211.0-B-6)

5.15. Proximity-1 Space Link ProtocolPhysical Layer (CCSDS 211.1-B-4)

5.16. Proximity-1 Space Link ProtocolCoding and Synchronization Sublayer (CCSDS 211.2-B-3)

5.17. TC Synchronization and Channel Coding (CCSDS 231.0-B-4)

5.18. TC Space Data Link Protocol (CCSDS 232.0-B-4 )

5.18.1. Technical Corrigendum to CCSDS 232.0-B-4, Issued October 2021 (CCSDS 232.0-B-4 Cor. 1)

5.19. Communications Operation Procedure-1 (CCSDS 232.1-B-2)

5.19.1. Technical Corrigendum 1 to CCSDS 232.1-B-2, Issued September 2010-CCSDS 232.1-B-2 Cor. 1

5.20. Time Code Formats (CCSDS 301.0-B-4)

5.21. CCSDS Cryptographic Algorithms (CCSDS 352.0-B-2)

5.22. Space Data Link Security Protocol (CCSDS 355.0-B-2)

5.23. Space Data Link Security Protocol--Extended Procedures (CCSDS 355.1-B-1)

5.24. Network Layer Security Adaptation Profile (CCSDS 356.0-B-1)

5.25. CCSDS Authentication Credentials (CCSDS 357.0-B-1)

5.26. Radio Frequency and Modulation Systems—Part 1: Earth Stations and Spacecraft  (CCSDS 401.0-B-32)

5.27. Pseudo-Noise (PN) Ranging Systems (CCSDS 414.1-B-3)

5.28. Data Transmission and PN Ranging for 2 GHz CDMA Link via Data Relay Satellite (CCSDS 415.1-B-1)

5.29. Variable Coded Modulation Protocol (CCSDS 431.1-B-1)

5.29.1. Technical Corrigendum 1 to CCSDS 431.1-B-1, Issued February 2021  (CCSDS 431.1-B-1 Cor. 1 )

5.30. Orbit Data Messages  (CCSDS 502.0-B-3)

5.31. Tracking Data Message (CCSDS 503.0-B-2)

5.31.1. Technical Corrigendum 1 to CCSDS 503.0-B-2, Issued June 2020  (CCSDS 503.0-B-2 Cor. 1)

5.32. Attitude Data Messages (CCSDS 504.0-B-2)

5.33. XML Specification for Navigation Data Messages (CCSDS 505.0-B-3)

5.34. Delta-DOR Raw Data Exchange Format (CCSDS 506.1-B-1)

5.35. Conjunction Data Message (CCSDS 508.0-B-1)

5.35.1. Corrigendum 1 to CCSDS 508.0-B-1, Issued June 2013 (CCSDS 508.0-B-1 Cor. 1)

5.35.2. Technical Corrigendum 2 to CCSDS 508.0-B-1, Issued June 2013  (CCSDS 508.0-B-1 Cor. 2 )

5.36. Re-entry Data Message (CCSDS 508.1-B-1)

5.36.1. Technical Corrigendum 1 to CCSDS 508.1-B-1, Issued November 2019  (CCSDS 508.1-B-1 Cor. 1 )

5.37. Pointing Request Message (CCSDS 509.0-B-1)

5.37.1. Technical Corrigendum 1 to CCSDS 509.0-B-1, Issued February 2018 (CCSDS 509.0-B-1 Cor. 1)

5.37.2. Technical Corrigendum 2 to CCSDS 509.0-B-1, Issued February 2018 (CCSDS 509.0-B-1 Cor. 2)

5.38. Mission Operations Message Abstraction Layer (CCSDS 521.0-B-3)

5.39. Mission Operations Common Object Model (CCSDS 521.1-B-1)

5.40. Mission Operations--Common Services (CCSDS 522.0-B-1)

5.41. Mission Operations Monitor & Control Services  (CCSDS 522.1-B-1 )

5.42. Mission Operations--MAL Space Packet Transport Binding and Binary Encoding (CCSDS 524.1-B-1)

5.43. Mission Operations--Message Abstraction Layer Binding to TCP/IP Transport and Split Binary Encoding (CCSDS 524.2-B-1 )

5.44. Mission Operations--Message Abstraction Layer Binding to HTTP Transport and XML Encoding (CCSDS 524.3-B-1)

5.45. Mission Operations--Message Abstraction Layer Binding to ZMTP Transport (CCSDS 524.4-B-1)

5.46. Standard Formatted Data Units — Structure and Construction Rules (CCSDS 620.0-B-2)

5.47. Standard Formatted Data Units — Referencing Environment (CCSDS 622.0-B-1)

5.48. Standard Formatted Data Units — Control Authority Procedures (CCSDS 630.0-B-1)

5.49. Standard Formatted Data Units — Control Authority Data Structures (CCSDS 632.0-B-1)

5.50. Parameter Value Language Specification (CCSD0006 and CCSD0008) (CCSDS 641.0-B-2)

5.51. ASCII Encoded English (CCSD0002) (CCSDS 643.0-B-1)

5.52. The Data Description Language EAST Specification (CCSD0010) (CCSDS 644.0-B-3)

5.53. Data Entity Dictionary Specification Language (DEDSL)—Abstract Syntax (CCSD0011) (CCSDS 647.1-B-1)

5.54. Data Entity Dictionary Specification Language (DEDSL)—PVL Syntax (CCSD0012) (CCSDS 647.2-B-1)

5.55. Data Entity Dictionary Specification Language (DEDSL)—XML/DTD Syntax (CCSD0013) (CCSDS 647.3-B-1)

5.56. Producer-Archive Interface Specification (PAIS) (CCSDS 651.1-B-1)

5.57. XML Telemetric and Command Exchange--Version 1.2 (CCSDS 660.0-B-2)

5.58. XML Formatted Data Unit (XFDU) Structure and Construction Rules (CCSDS 661.0-B-1)

5.59. IP over CCSDS Space Links (CCSDS 702.1-B-1)

5.59.1. Technical Corrigendum 1 to CCSDS 702.1-B-1, issued September 2012 (CCSDS 702.1-B-1 Cor. 1)

5.59.2. Technical Corrigendum 2 to CCSDS 702.1-B-1, issued September 2012 (CCSDS 702.1-B-1 Cor. 2)

5.60. Space Communications Protocol Specification (SCPS)—Transport Protocol (CCSDS 714.0-B-2 )

5.61. CCSDS File Delivery Protocol (CFDP) (CCSDS 727.0-B-5)

5.62. AOS Space Data Link Protocol  (CCSDS 732.0-B-4 )

5.63. Unified Space Data Link Protocol  (CCSDS 732.1-B-2 )

5.64. Licklider Transmission Protocol (LTP) for CCSDS (CCSDS 734.1-B-1)

5.65. CCSDS Bundle Protocol Specification (CCSDS 734.2-B-1)

5.66. Schedule-Aware Bundle Routing (CCSDS 734.3-B-1)

5.67. Asynchronous Message Service (CCSDS 735.1-B-1)

5.68. Digital Motion Imagery (CCSDS 766.1-B-3)

5.69. Voice and Audio Communications  (CCSDS 766.2-B-1 )

5.70. Spacecraft Onboard Interface Services--XML Specification for Electronic Data Sheets (CCSDS 876.0-B-1)

5.71. Spacecraft Onboard Interface Services--RFID  (CCSDS 881.1-B-1 )

5.72. Spacecraft Onboard Interface Services-High Data Rate Wireless Proximity Network Communications (CCSDS 883.0-B-1)

5.73. Cross Support Service Management--Simple Schedule  (CCSDS 902.1-B-1 )

5.73.1. Technical Corrigendum 1 to CCSDS 902.1-B-1, Issued May 2018 (CCSDS 902.1-B-1 Cor. 1)

5.74. Cross Support Service—Management Communications Planning Information Format  (CCSDS 902.2-B-1 )

5.75. Space Link Extension-Return All Frames Service Specification (CCSDS 911.1-B-5)

5.76. Space Link Extension-Return Channel Frames Service Specification (CCSDS 911.2-B-4)

5.77. Space Link Extension-Return Operational Control Fields Service Specification (CCSDS 911.5-B-4)

5.78. Space Link Extension-Forward CLTU Service Specification (CCSDS 912.1-B-5)

5.79. Space Link Extension--Internet Protocol for Transfer Services (CCSDS 913.1-B-2)

5.80. Cross Support Transfer Service—Specification Framework (CCSDS 921.1-B-2)

5.81. Cross Support Transfer Services—Monitored Data Service  (CCSDS 922.1-B-2 )

5.82. Cross Support Transfer Service-Tracking Data Service  (CCSDS 922.2-B-2)

5.83. Cross Support Transfer Service—Forward Frame Service (CCSDS 922.3-B-1)

5.84. Terrestrial Generic File Transfer (CCSDS 927.1-B-1)

6. LunaNet - https://esc.gsfc.nasa.gov/projects/TEMPO?tab=lunanet

6.1. LunaNet Interoperability Specification Document

The purpose of this specification is to define the standard services and interfaces for LunaNet service providers to administer interoperable services to meet the needs of missions operating in the lunar vicinity. This document is not intended to replace either the International Communication System Interoperability Standards (ICSIS) or the Interagency Operations Advisory Group’s (IOAG) Lunar Communications Architecture Documents. This document provides the minimum set of standard services and interfaces that will be available to lunar users, such that users may design their systems with the expectation of available providers. Any individual provider is not required to offer all services and interfaces in this document, but the aggregation of providers will have the interfaces and services described. It is also possible for providers to offer services and interfaces beyond what is described in this document. However, those services and interfaces will likely not be interoperable between service providers, thereby limiting the service options for a user.


7. 3rd Generation Partnership Project (3GPP) - https://www.3gpp.org/