Deployment Viewpoint for MOIMS Services in SEA Reference Architecture

Identification of physical nodes and their connections, functional deployments showcasing interoperable interfaces between nodes, and classification of space and earth user nodes in the context of MOIMS services for the SEA reference architecture.

• Deployment Viewpoint
• MOIMS Services
• SEA Reference Architecture
• Physical Nodes
• User Nodes

hsell 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 Physical / Deployment 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 Services for SEA Reference Architecture 2

3. Full color JPEG without the .ORG. Introduction Example Deployment Viewpoint for MOIMS Services Two parts: Physical: identification of a representative set of example Deployment Nodes and their physical connections (in terms of the Protocol viewpoint contexts already identified) Deployment: example Functional deployments showing the exposed interoperable application level interfaces between Nodes (in terms of the Service and Data viewpoints already identified). Nodes identified in the Protocol Viewpoint are consistent with the SCCS ADD: generic Space User Node; Earth User Node; and ESLT The Physical model identifies various classes of User Nodes that are representative of existing or planned space systems and relevant to the MOIMS functions. It should, however, be stressed that these are only example classes of User Node and that an actual system may have a different physical architecture. 08/10/2024 MOIMS Services for SEA Reference Architecture 3

4. Full color JPEG without the .ORG. Physical Node Identification Space User Nodes: Spacecraft Lander/Rover Relay Habitat / Suit Earth User Nodes: Mission Operations Centre [MOC] PI / Payload Operations Centre [POC] Navigation Services Centre [NSC] Data Processing Centre [DPC] Data Archive Centre [DAC] Spacecraft Manufacturer [SCM] Not clear that we need these space user node type distinctions for MO and SOIS. It does not appears that they are different from the MO point of view. Leave them in only to record that we are aware of these different classes of users. Many kinds of users, external to the systems 08/10/2024 MOIMS Services for SEA Reference Architecture 4

5. Full color JPEG without the .ORG. New Earth User Node diagrams Specific diagrams for each of these exposing what makes them different Based on SCCS ADD Node diagrams Earth User Nodes: Mission Operations Centre [MOC] PI / Payload Operations Centre [POC] Navigation Services Centre [NSC] Data Processing Centre [DPC] Data Archive Centre [DAC] Spacecraft Manufacturer [SCM] 08/10/2024 MOIMS Services for SEA Reference Architecture 5

6. Full color JPEG without the .ORG. Figure 5-1: Generic ABA Building Block and Functions The configuration of each generic Link-Layer ABA node type should be shown as follows. Generic ABA Node Application 1 Application 2 Element Management Data Store Data Forwarding Link Type A Link Type B Link A Processing Link B Processing 6

7. Full color JPEG without the .ORG. Figure 5-2: ABA ESLT Node The configuration of each ABA Earth-Space Link Terminal node type should be shown as follows. ABA ESLT Node Service Management Provision Management Element Management Data Store Service Delivery Data Forwarding Space Link Terrestrial Link Link A Processing (SLE Tunnel) Link B Processing 7

8. Full color JPEG without the .ORG. Figure 5-3: ABA Earth User Node The configuration of each ABA Earth User node type should be shown as follows. ABA Earth User Node Application 1 Service Management Utilization Management Element Management Data Store Service Delivery Data Forwarding Terrestri al Link Link A Processing (SLE Tunnel) 8

9. Full color JPEG without the .ORG. Figure 5-4: ABA Space User Node The configuration of each ABA Space node type should be shown as follows. ABA Space User Node Application 2 Element Management Data Store Data Forwarding Space Link Link B Processing 9

10. Figure 5-5: Generic SSI Building Block and Functions Full color JPEG without the .ORG. The configuration of each generic SSI node type should be shown as follows. Generic SSI Node Application 1 Application 2 Element Management Data Store Network Management Network B Processing Network A Processing Routing Link Type A Link Type B Link A Processing Link B Processing 10

11. Full color JPEG without the .ORG. Figure 5-11: Earth User Node The configuration of each Earth User SSI node type should be shown as follows. SSI Earth User Node Application 1 Service Management Utilization Management Data Store Network Management Network A Processing Routing Service Delivery Terrestri al Link Link A Processing 11

12. Figure 5-12: Space User Node Connected via a Space or Planet Surface Link Full color JPEG without the .ORG. The configuration of each SSI Space node type should be shown as follows. SSI Space/Planet User Node Application 1 Element Management Element Management Data Store Network Management Network A/B Processing Routing Space Link (or Planet Surface) Link A/B Processing 12

13. Full color JPEG without the .ORG. Figure 5-13: Hybrid Science/Routing Node The configuration of each SSI Hybrid Science/Routing node type should be shown as follows. SSI Hybrid Science/Routing Node Application 1 Application 2 Element Management Element Management Data Store Network Management Network C Processing Network B Processing Routing Space Link Space Link Link B Processing Link C Processing 13

14. Full color JPEG without the .ORG. Physical Model (SSI Example) Spacecraft Spacecraft Lander/Rover Inter-Satellite Link Proximity Link Router/Store-and-Forward Space Link SSI ESLT TD-CSTS Logical Link Space Link Extension NSC MOC DPC DAC SMC PI / POC User Terrestrial Link/Network 08/10/2024 MOIMS Services for SEA Reference Architecture 14

15. Full color JPEG without the .ORG. Deployment on Physical Model (SSI Example) Spacecraft Spacecraft Lander/Rover MCS MPS MCS MPS MCS MPS DSA NAVT DSA NAVT DSA NAVT ESLT Many of these deployments seem the same. Is that correct? TT&C NSC MOC DPC DSA DAC NAVT MPS NAVT DSA MCS MPS OPS DSA NAVT Mission Data Processing SMC PI/POC User Terrestrial Link/Network MCS MPS OPS Spacecraft Development & Maintenance User Support DSA NAVT 08/10/2024 MOIMS Services for SEA Reference Architecture 15

16. Full color JPEG without the .ORG. MOIMS Deployment in space (Example) [OLD] Spacecraft Ground Station Mission Control User Node TT&C NAVT CSS-SM CSS M&C Navigation & Timing Navigation & Timing NAVT NAVT Planning & Scheduling Planning & Scheduling User Support MPS MPS MDP MCS MCS MPS NAVT MDP Mission Control Mission Control MCS S/C Manufacturer MCS Satellite Dev. & Maint. On-board Configuration Operations Preparation OPD OPD MPS MCS NAVT OPD MCS NAVT OPD On-board Data Storage Data Storage & Archiving MDP MDP Note: interaction between functions within a deployment node are omitted for clarity see previous slide 08/10/2024 MOIMS Services for SEA Reference Architecture 16

17. Full color JPEG without the .ORG. MOIMS Bespoke Deployment (Example) [OLD] Spacecraft Ground Station Mission Control User Node TT&C NAVT CSS-SM CSS M&C Navigation & Timing NAVT Planning & Scheduling User Support MPS MCS MCS MPS NAVT MDP Mission Execution Mission Control Bespoke S/C Manufacturer MCS Satellite Dev. & Maint. On-board Configuration Operations Preparation OPD Bespoke MCS NAVT OPD On-board Data Storage Data Storage & Archiving Bespoke MDP Might change this one without the MOIMS svcs on board. Might also show a diagram (or two) of current agency / mission deployments. Note: interaction between functions within a deployment node are omitted for clarity see previous slide 08/10/2024 MOIMS Services for SEA Reference Architecture 17