Views
3 years ago

SISG Operations Concept for SSI - InterPlanetary Networking ...

SISG Operations Concept for SSI - InterPlanetary Networking ...

Operations Concept for a Solar System Internetwork (SSI)IOAG.T.RC.001.V1that will use these services. This evolution may initially involve static routing and manualconfiguration of the space assets, but the end goal is for space internetworking to besupported by a higher degree of automation, which in principle may even include dynamicrouting—and therefore dynamic reconfiguration—onboard. SSI evolutionConstitutes a migration towards fully automated space internetwork (DTN- and IPbased),and will familiarize the user and provider missions with interoperableoperationsResponds to the needs of potential user missions planned for launch in the 2015-2020 timeframeAllows testing and validation of the Internetworking concept before it is fullyadopted in its final configuration for future flying missionsThis operations concept describes the SSI end state and, where appropriate, providesguidelines regarding the evolutionary phase toward that end state to ensure maximumcoherence and continuity between the point-to-point mission operations of the past and theintended network of the future.Page | 18

Operations Concept for a Solar System Internetwork (SSI)IOAG.T.RC.001.V13 SSI PrinciplesThe SISG has identified a set of management, planning, and execution principles thatidentify the roles of the different elements in the SSI and how they are intended to operateand evolve. These operational principles reflect both lessons learned from the terrestrialInternet, as well as experience with the unique aspects of space communications.3.1 Management PrinciplesMA—1 SCOPE: End-to-end cross support shall be the goal of the SSI, where cross supportembraces what is known today as ground cross support and space cross support.MA—2 AGREEMENTS: Cross support is ruled by high-level documents agreed between theuser agency and the provider agency(ies); typically a Memorandum of Understanding (MOU)and a service agreement. Lower level interface control documents (ICDs) are developed asnecessary.MA—3 ASSET RESPONSIBILITY: Each agency is responsible for the planning, control, andoperations of its own assets, including payload configuration (e.g., for cross support).MA—4 NETWORK RESPONSIBILITY: Each agency shall contribute interoperable elements tothe overall functioning of the network in support of user services.MA—5 COMMUNICATIONS PROTOCOLS: The operations concept shall, as far as possible, beindependent of the communications protocols below the network layer to offer stableguidelines robust to the risks inherent to space missions (financial, delays, technicaldifficulties) and to ensure it is not bound too much to the specific implementations of suchprotocols.MA—6 VALIDATION: An end-to-end validation shall occur between the definition/setup ofthe network and the start of its operational usage (e.g., via “demo passes”) or followingmajor failure and recovery of network elements. Validation shall also be performed uponaddition or removal of significant elements of the network.MA—7 SECURITY: A trusted level of security/confidentiality must be agreed in advance andrespected between the provider and the user. Security is required for the exchange ofinformation and files leading to the establishment of the mission timeline, the configurationof sessions and services, and in the exchange of data to be transmitted to the user node viathe provider nodes.MA—8 ADDRESSING: Asset addressing must be constructed and managed at the networklevel using network-layer identifiers (IP address, DTN node name) and also existing link-layerelements (Spacecraft Identification [SCID], Multiplexer Access Point [MAP], etc.), along withthe identifiers required to allow the intended routing and preclude non-intendedcommunication. The SSI will require management and maintenance of the SSI addressspace.MA—9 NETWORK SERVICES: The defining characteristic of the SSI end state operationsconcept is the presence of a functional network layer in the protocol stack. Applicationlayer functionality is only present at the endpoints of an end-to-end service (e.g., CCSDS FilePage | 19

CS 406-01 Lecture 18 Network Concepts
Operator Guide to 2012 - Association of Pallet Networks
Ground Station Networks for Efficient Operation of Distributed Small ...
Mobile Network Operators and Cooperation - IMP Group
Teaching Materials: Networking and Computing Concepts Slides
Operating System & Networks 2003
CABLE NETWORK OPERATORS
Shim6: Network Operator Concerns
Concept of Operations for Intersection Conflict Warning ... - Enterprise
Intelligent Transport Network for Network Operators - Infinera
ranking the world's biggest network operators - Total Telecom
CC-NIE - Network Operations Center
Operations Research and the Captivating Study of Networks
Software Defined Networks (SDN) and Network Function Virtualization (NFV) Market Impact on Network Operators 2015-2020
From World IPv6 Day to World IPv6 Launch - UK Network Operators ...
Net Neutrality: view from over the top - UK Network Operators' Forum
Multi-Technology Mobile Networks for Emerging Operators ... - Tecore
Distributed Virtual Network Operations Center (DVNOC ... - Caida
HFC Network Catalog for Cable Operators - JDSU
UAVs as Communications Routing Nodes in Network ... - aero.com
Operator Strategies for profitable small cell networks ... - 4G Americas
Operations Concept for a Solar System Internetwork
The Interplanetary Network Supplement to the BATSE... - Space ...
The Routing of Interplanetary Internet
(ESA Portal - Interplanetary networking: ESA\222s Mars Express wi...)
Unit 5: Networking Operating Systems
IPv6 integration in operational networks
Computer Networks and Operating System