Views
2 years ago

SISG Operations Concept for SSI - InterPlanetary Networking ...

SISG Operations Concept for SSI - InterPlanetary Networking ...

6.3 SSI

6.3 SSI User ApplicationsOperations Concept for a Solar System Internetwork (SSI)IOAG.T.RC.001.V1User applications include file, message, and other data transfer over DTN or IP. They aretransparent to the SSI. The SSI will also support communications between users andstandardized “last-hop” user applications.6.4 Acquisition and ContactThe acquisition of the link between two SSI nodes (provider or user), and in particularbetween a landed spacecraft and a Relay Spacecraft, may be pre-programmed or use ondemandrequests. The acquisition is carried out autonomously in accordance with the prenegotiatedcontact plan, without near real-time intervention. Either node may send ahailing signal to indicate the start of the pass and initiate acquisition.When establishing the link between the Relay Spacecraft and its MOC, the Relay SpacecraftMOC will use service management requests to initiate the space link, configure, manage,and monitor it. Once the space link is established, SSI traffic may flow directly from nodesthat have staged data to the Relay Spacecraft.The Relay Spacecraft will forward data from the landed spacecraft on the deep space link toan Earth Station. Due to orbital geometry or the capability of the Relay Spacecraft, the deepspace link may not be contemporaneous with the link between the lander and RelaySpacecraft, in which case data will be stored on the Relay Spacecraft until the next availabledownlink opportunity. The network layer, typically based on DTN, will be used to addressthe intermittent link connectivity and the acknowledgement process in the presence of long,round-trip light times. (Today these are handled as a mixture of application and link-layerfunctions.)A reverse process occurs to accomplish communications from the landed spacecraft MOC tothe landed spacecraft.End-to-end relay operations will be programmed to operate autonomously. A prioridecisions of the agencies will ensure availability and coherency of the physical elements(e.g., frequencies, pointing, bandwidth, storage, etc.) and logical elements involved (e.g.,authorisations, priorities). Relay Spacecraft nodes will be designed to accommodate theexpected data and service requests of the lander(s) they are designed to support.6.5 Node CapabilitiesUser nodes will initiate end-to-end data transfers. Data will be staged as DTN bundles forforwarding on the Relay Spacecraft, and will be distinguishable from data belonging to otherrelay sessions. Intermediate provider nodes will be able to store data until the next hopbecomes accessible (possibly with a time out). Provider nodes will not reassemble user data(e.g., files) at each hop and may transfer user data in pieces, possibly via different relaypaths. Only the end user node will reassemble the user data. Users may force a set of userdata to be delivered fully assembled by sending the data in a single bundle.Nodes will use DTN protocols to identify the next node, establish the communications withthe next node, and transfer the data to that node. Nodes may employ static routing, or theymay use Contact Graph Routing, which can adapt to available paths.Page | 34

Operations Concept for a Solar System Internetwork (SSI)IOAG.T.RC.001.V1Nodes may verify data on receipt, may securely transfer data (with Bundle Security Protocol[BSP] or via user encryption), or may delete data if requested.A data handling system is provided at each provider node for bundle data staging.Individual bundles will specify priorities, and provider nodes will forward bundles based onestablished policies. A user or provider (under certain defined conditions) will be able todelete a well defined set of user data (e.g., all bundles associated with the identified userdata).Link-layer services and protocols will support transfer of data over individual hops. The DTNBundle Agents and upper-layer applications will manage reliable end-to-end delivery andsignalling.6.6 Emergency Services (Last Hop)In support of emergency situations where the landed spacecraft no longer has networkfunctionality, last-hop services will be employed to establish physical or link-layer commandand telemetry service to/from the landed spacecraft and a standardized Delivery Agentapplication resident on the Relay Spacecraft.To implement this emergency service, packets and other low-level frame/link transmissionsmust be supported as a point-to-point transmission across the “last-hop” proximity link. Toprovide this service, the User MOC of the mission must embed the required link-layer datastructures, packets, or frames into files, along with the necessary link configuration anddelivery information, and the files will be handled by the SSI as usual, until they aredelivered to a standardized Delivery Agent application running on the Relay Spacecraft. ThisDelivery Agent accepts the data to be delivered and the instructions, and performs thenecessary link configuration and data delivery services at the requested time.Between the Relay Spacecraft and the landed spacecraft, Proximity-1 will support the directtransmission of space packets, but frames and other data structures (e.g., Bose-Chaudhuri-Hocquenghem [BCH] encoded TC frames) may also be transferred over reliable bit stream(User Defined Data [UDD]). The delivery instructions state how the link is to be configured,how the data are to be extracted and sent (packets, frames), when the data are to be sent,how often, and under what conditions this transmission is to be terminated. A similarreturn service is also implemented by an application on the Relay Spacecraft. As with theforward service, this application accepts a service request that instructs it how to configurethe proximity link, what data to capture, and when to record the data. The resulting dataset is placed in a file, along with a report of what was done and its success or failure, andthis information is sent via SSI services back to the user. These return services may deliveressential telemetry, open loop sampled data from the Radio Frequency (RF) link itself, andtiming or radiometric data from Proximity-1.Page | 35

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