MOIMS Protocol Viewpoint for SEA Reference Architecture Updates

This content describes the MOIMS Protocol Viewpoint inputs to the SEA Reference Architecture updates by Roger Thompson from ESA SAWG. It includes details about the graphical conventions, data store elements, organizational domains, network layers, communications protocols, and space communications cross-support architecture. The images and descriptions provide insights into the configurations and connections within the architecture for space communications. Reference diagrams and basic configurations are also presented.

• MOIMS Protocol
• SEA Reference Architecture
• Updates
• Space Communications
• Architectural Conventions

kard139 Follow

Uploaded on Oct 08, 2024 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

Presentation Transcript

1. MOIMS Protocol Viewpoint Inputs to SEA Reference Architecture Roger Thompson ESA SAWG Updates 9May17 08/10/2024

2. Full color JPEG without the .ORG. RASDS Graphical Conventions Data Store Data Store Organizational Element Service Provider Organizational Domain Physical Node Service Consumer DATA Physical or Logical Link between Elements Link Layer User Service Access Point Peering Arrangement Functional Connection Physical, Logical, & Service Connectors Communications Protocol Router Functional Element As all Functions are Application Layer overload by Functional Group Color Keys: Application Link Layer function User Node Element Management Routing function Earth Routing Node Network Management Space Routing Node Forwarding function Network Layer function Data Store WAN Node 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 2

3. Full color JPEG without the .ORG. Reference Diagram MO Servce Messages may be carried in files over CFDP. Ground-Ground may be mapped over terrestrial protocols such as 0MQ/TCP or FTP SLE may be used to extend space link. This is transparent to application level. 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 3

4. Full color JPEG without the .ORG. SCCS Context SCCS ABA/SSI User User I I Applications Applications Space Communications Cross Support (SCCS) Architecture Describes Communications Architecture for two primary cases: ABA: a single-hop space communications configuration that involves only a single direct to/from Earth space link. Term derives from the notion of an Agency A using the ground station of an Agency B to communicate between its MOC and its spacecraft, hence ABA. SSI: A loose confederation of independent space communications networks that all share a single Network-Layer protocol that allows them to interoperate and exchange Network-Layer PDUs, each often owned and administered by a different space agency. 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 4

5. Full color JPEG without the .ORG. SCCS Basic ABA Configuration This figure and the next belong in the Physical view along with other node types Service Management Interface Earth User Node Space User Node ABA ESLT Terrestrial Service Provider Interface Space-Link Service Provider Interface 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 5

6. Full color JPEG without the .ORG. SCCS SSI Core Configuration Terrestrial- Link Interfaces Space Link Interfaces Interfaces Space-Link Earth User Node Space User Node Space Routing Node Terrestrial WANs SSI ESLT Service Management Interface Earth Routing Node 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 6

7. Full color JPEG without the .ORG. MOIMS Services Protocol Binding MOIMS Concerns Application Level Services, end to end MOIMS Standards are defined in terms of two principle information exchange paradigms: Message Based Interaction File Transfer In terms of Communications Architecture, MOIMS Services may be deployed in 3 principle contexts: Across a Space Link, using CCSDS SCCS ARD compliant communications protocol stacks. It should be noted that this includes the use of Space Link Extension services, or SSI protocols deployed over terrestrial networks. Across a Terrestrial Network, using industry standard communications protocol stacks Within a Spacecraft, using CCSDS SOIS services [TBC] Bridging between these contexts is performed at application level. Where the MO MAL is used, a generic MAL bridge can provide this as an application independent service 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 7

8. Full color JPEG without the .ORG. MOIMS Comms Context: Space Link MOIMS Space User Node Space or Earth User Node Information Exchange MOIMS MOIMS MOIMS User Application User Application Space Link Communications Processing Space Link Communications Processing Any SCCS Architecture (ABA/SSI) Space Link 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 8

9. Full color JPEG without the .ORG. MOIMS Comms Context: Terrestrial Link MOIMS Earth User Node Earth User Node Information Exchange MOIMS MOIMS MOIMS User Application User Application Terrestrial Link Communications Processing Terrestrial Link Communications Processing Any Terrestrial Network Architecture Terrestrial Link 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 9

10. Full color JPEG without the .ORG. MOIMS Comms Context: On-board Link MOIMS Information Exchange Space User Node MOIMS MOIMS MOIMS User Application User Application SOIS SOIS Communications Processing Communications Processing SOIS Compatible On-board Architecture SOIS Link 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 10

11. Full color JPEG without the .ORG. MOIMS Generic Protocol Stacks MO Compliant Service MOIMS File Exchange MOIMS MOIMS User Application User Application MO API Optional File Format Specification in terms of MAL MO Service MOIMS File Format MO Language Binding MAL MAL MALTechnology Binding Encoding MAL Encoding Transport Transfer Protocol File Transfer Protocol Messaging or File Transport Protocol Transport Protocol Transport/Network Layer Link Layer Link Layer Physical Link/Network Blue layers correspond to Communications Layers: Transfer (Application) Layer (e.g. FTP, HTTP or 0MQ) providing message exchange or file transfer Transport and Network Layers combined (e.g. TCP/IP or UDP/IP) Physical Link Layer or Network (e.g. RF Space Link, WAN, LAN or WLAN) Protocol stacks must match between communicating User Applications MO Language Binding can differ between communicating User Applications For File Exchange, the transfer must be independently initiated at Communications Protocol level, either directly by the User Application or by a 3rd party. 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 11

12. Full color JPEG without the .ORG. MOIMS Generic Deployment Example User Node User Node MOIMS MOIMS User Application (Provider) User Application (Consumer) MOIMS MO API MO API MO Service MO Service MAL MAL MAL Technology Binding MAL Technology Binding Transfer Protocol Transfer Protocol Transport Protocol Transport Protocol Link Layer Link Layer 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 12

13. Full color JPEG without the .ORG. MOIMS Specific Service Example User Node User Node Monitoring & Control (Provider) Monitoring & Control (Consumer) M&C MO API MO API MO M&C MO M&C MAL MAL MAL Technology Binding MAL Technology Binding Transfer Protocol Transfer Protocol Transport Protocol Transport Protocol Link Layer Link Layer 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 13

14. Full color JPEG without the .ORG. MOIMS Over Space Link MO Compliant Service over Space Packet and/or CFDP MOIMS File Exchange MOIMS MOIMS User Application User Application Entire Service or Single Message MO API MO Service MOIMS File Format MAL MAL SPP MAL CFDP Bidirectional: TM and TC Packets CFDP CFDP CCSDS Space Packet CCSDS Space Packet Communications Processing Communications Processing Any SCCS Architecture (ABA/SSI) (ABA/SSI) Any SCCS Architecture 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 14

15. Full color JPEG without the .ORG. MOIMS Over Space Link (ABA Deployment Example) Space User Node ESLT (Ground Stn) Earth User Node MOIMS MOIMS MOIMS User Application User Application MO API MO API MO Service MO Service MAL MAL MAL SPP MAL CFDP MAL SPP MAL CFDP Multiple service options, eg. R-AF + F-CLTU CFDP CFDP CCSDS Space Packet CCSDS Space Packet Space Data Link Space Data Link CCSDS CSTS/SLE CCSDS CSTS/SLE SLE-SI SLE-SI Coding & Synch C&S TCP/IP TCP/IP RF & Mod RF & Mod Network Network 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 15

16. Full color JPEG without the .ORG. MOIMS Over Terrestrial Link MO Compliant Service over HTTP and/or FTP MOIMS File Exchange MOIMS MOIMS User Application User Application MO API MOIMS File Format MO Service MAL MAL HTTP MAL FTP HTTP FTP FTP TCP/IP TCP/IP Link Layer Link Layer Note that HTTP and FTP are example protocols others, such as 0MQ may be used if MAL binding exists MO Language Binding can differ between communicating User Applications For File Exchange, the transfer must be independently initiated at Communications Protocol level, either directly by the User Application or by a 3rd party. 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 16

17. Full color JPEG without the .ORG. MOIMS Over Terrestrial Link (Deployment Example) Earth User Node Earth User Node MOIMS MOIMS User Application (Provider) User Application (Consumer) MOIMS MO API MO API MO Service MO Service MAL MAL MAL FTP MAL HTTP MAL HTTP MAL FTP FTP HTTP HTTP FTP TCP/IP TCP/IP Link Layer Link Layer Network: WAN, LAN or WLAN 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 17

18. Full color JPEG without the .ORG. MAL Bridging User Node User Node MAL Bridge MOIMS MOIMS User Application (Provider) User Application (Consumer) MOIMS MO API MO API MO Service MO Service MAL MAL MAL MAL TFB MAL TFA MAL TFA MAL TFB Transfer Protocol A TF A TF B Transfer Protocol B Transport Protocol A TP A Transport Protocol B TP B Link A Link A Link B Link B MAL Bridge supports two technology bindings and translates between them Example above is for two Messaging Technologies (A and B) All MO Services defined in terms of MAL can be transferred across the same generic MAL Bridge Can be used to link different Communications contexts (Space-Ground or Ground-Ground) 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 18

19. Full color JPEG without the .ORG. MOIMS Data Archive Protocol Stack DAI Compliant Services MOIMS Archive Consumer MOIMS Archive Producer PAIS CAIS AAL Archive Binding Archive Interface ARCHIVE AAL: Archive Abstraction Layer PAIS: Producer Archive Interface Service CAIS: Consumer Archive Interface Service ARCHIVE: may be a Science Data Archive, Enterprise Data Archive, Mission Operations Data Archive, Document Archive Archive Interface: any legacy or proprietary interface to a Data Archive 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 19

20. Full color JPEG without the .ORG. Data Archive Deployment (Option 1) Producer Node Consumer Node Data Archive MOIMS Archive Consumer MOIMS Archive Producer CAIS PAIS AAL AAL Archive Binding Archive Binding Archive Interface Archive Interface Archive Interface ARCHIVE [Science, Enterprise, Operations or Document] Archive Producer, Data Archive and Archive Consumer may be distributed over separate nodes Binding is to existing legacy or proprietary Archive Interface Communications layers are encapsulated within the Archive Interface and available within the Producer and Consumer Nodes 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 20

21. Full color JPEG without the .ORG. Data Archive Deployment (Option 2) Producer Node Consumer Node Data Archive MOIMS Archive Consumer MOIMS Archive Producer CAIS PAIS AAL AAL AAL Archive Binding Archive Interface ARCHIVE [Science, Enterprise, Operations or Document] Archive Producer, Data Archive and Archive Consumer may be distributed over separate nodes Binding is to existing legacy or proprietary Archive Interface, at the Data Archive Node Distributed Communications are managed within the Archive Abstraction Layer using a standardised communications protocol (technology and protocol stack TBD). 08/10/2024 MOIMS Protocol Viewpoint for SEA Reference Architecture 21