Date post: | 30-Dec-2015 |
Category: |
Documents |
Upload: | tracey-flowers |
View: | 216 times |
Download: | 3 times |
DTN Network Management
Will Ivancic
216-433-3494
Ed Birrane
443-778-7423
Several Institutions working on NM
MITREKeith Scott
UMBCDeepinder Sidhu
SNMP and the degree to which Protocols, software, and MIBs can be ported to DTNs
Ohio UniversityHans Kruse
Working on NM protocols and constructing a DTN network to emulate space-based scenarios to derive NM needs.
NASA Glenn Research Center
William Ivancic
Managing remote nodes for N4C project.Trinity College,
DublinStephen Farrell
Discussion of deep-space network management mechanisms developed and used on EPOXI during DINET.
NASA JPLScott Burleigh
Network Management Architectures for DTNsJHU/APLEd Birrane
Ensuring new BPA implementation includes support for emerging NMS capabilities. Also, generting a draft DTN NM MIB.
BBNJosh Bers
Area of ResearchInstitutionName
Source: Ed Birrane, APL
Scope of Work
Five major areas identified for NMStart by bounding the NM problem, defining how/why of NMData definitions should be guided by this analysisUsage, velocity, and aggregation of data based on what data we collectApplications should be data drivenSignificant prototyping is needed to flesh out these guidelines.
We examine each of these areas in turn.
SystemArchitecture
Data Definition
Data Usage
ApplicationArchitecture
Prototyping,M&S
Guides Bounds Defines Drives
RefinesRefinesRefinesRefines
Source: Ed Birrane, APL
System ArchitectureProposed Documents
CONOPS / Use Cases / Motivations Under development by GRC Need use cases geared specifically at Network
management Fault response, remote configuration, etc…
Network Characteristics Under development by APL, review needed!
Network Requirements (High Level) Started by APL, help wanted!
Data/Control flows Volunteers!
Source: Ed Birrane, APL
System ArchitectureOpen Questions
Do we use Bundles to communicate network management data?
Really probably no choice But, should be able to use out of band channels also
What conops require push versus pull? Although we realize a pull in not a interactive query
such as SNMPWhat other subsystems affect (naming) or are
affected by (routing) NM?
Source: Ed Birrane, APL
Data DefinitionIdentify types of data to be collected
Fault Monitoring, Responses, ReportingConfiguration (Remote and Local)AccountingPerformance (Esp. for dynamic algorithms)Security
StructureMetadata: Do data have verbosities? Pre-defined
velocities?Formatting: MIBs? YANG?
Source: Ed Birrane, APL
Data Definition
Open QuestionsDo we recommend maturing existing
approaches? Rmon? Netconf?What features/functions support critical
configuration (and rollback) for DTN nodes?What is the criticality of this information in terms
of mission risk?
Source: Ed Birrane, APL
Data Usage
Guidance on when to collect dataData collection heuristics
Use cases Data velocity, verbosity settings
Requirements for data aggregation Usefulness of data to external nodes Algorithms for adjusting when to aggregate data
Source: Ed Birrane, APL
Application Specification
Application architectureLocal Data Collector
Populates data stores at the DTN node Exists at the Application layer above the transport
layer. Collects high speed data.
Data Aggregator Samples locally collected data Emits data over network as necessary Receives network management data from remote
aggregators.
Source: Ed Birrane, APL
Prototyping and M&SPrototyping
Use of NASA DTN Engineering Network (DEN) testbed and DTNbone to test network management
Coding examples to flesh out interfacesMIB Implementationsrmon/netconf modifications
Modeling and SimulationExpected network management overheadMonte Carlo simulations of network disruptionsNeed emulation environment for DTN
DEN and DTNBone Suggestions welcome!
Source: Ed Birrane, APL
Network ManagementRequirements Document DTN Scenarios . . . . . . . . . . . . . . . . . .
Deep Space Mars Relay . . . . . . . . . . . . . . Simple Sensor Networks . . . . . . . . . . . . . . . . . . Data Mule . . . . . . . . . . . . . . . . . . . . . . . . Rapid Disruption . . . . . . . . . . . . . . . . . . . . . Low Earth Orbiting Sensor Satellite . . . . . . . . . . . Geostationary Bent Pipe Relay Satellite . . . . . . . . . Unmanned Aeronautical Vehicles . . . . . . . . . . . . . .
Bundle Processing . . . . . . . . . . . . . . . . . . . . . . Bundle Statistics . . . . . . . . . . . . . . . . . . . . Bundle Fragmentation . . . . . . . . . . . . . . . . . . .
Network ManagementRequirements Document System Characteristics . . . . . . . . . . . . . . . . . . . .
Convergence Layers . . . . . . . . . . . . . . . . . . . . Internet Protocol . . . . . . . . . . . . . . . . . .
TCP/IP . . . . . . . . . . . . . . . . . . . . . . UDP/IP . . . . . . . . . . . . . . . . . . . . . . SCTP/IP . . . . . . . . . . . . . . . . . . . . .
CCSDS . . . . . . . . . . . . . . . . . . . . . . . . Licklider Transport Protocol . . . . . . . . . . . . .
Bluetooth . . . . . . . . . . . . . . . . . . . . . . Removable Storage . . . . . . . . . . . . . . . . . .
Multi-Homing . . . . . . . . . . . . . . . . . . . . . . . DARPA Dynamic Spectrum Access (DSA) Radio Deep Space / Proximity . . . . . . . . . . . . . . . .
Radios . . . . . . . . . . . . . . . . . . . . . . . . . . Fixed Rate . . . . . . . . . . . . . . . . . . . . . . Bandwidth On Demand . . . . . . . . . . . . . . . . .
Processing Power . . . . . . . . . . . . . . . . . . . . . Onboard Storage . . . . . . . . . . . . . . . . . . . . .
Network ManagementRequirements Document Routing . . . . . . . . . . . . . . . . . . . . . . . . . Name Resolution . . . . . . . . . . . . . . . . . . . . . Local and Network Time . . . . . . . . . . . . . . . . . . Security . . . . . . . . . . . . . . . . . . . . . . . . .
Multi-layer Security . . . . . . . . . . . . . . . . . IP . . . . . . . . . . . . . . . . . . . . . . . . . . Radio . . . . . . . . . . . . . . . . . . . . . . . . DTN . . . . . . . . . . . . . . . . . . . . . . . . .
General Requirements . . . . . . . . . . . . . . . . . . . Local Network Management . . . . . . . . . . . . . . .
Requirement for Local Network Management . . . . . Rationale for Local Network Management . . . . . .
Remote Network Management . . . . . . . . . . . . . . Requirement for Remote Network Management . . . . Rationale for Remote Network Management . . . . .
Utilities – beginnings of NetMgt
(Make utilities interoperable between ION and DTN-2) DTN-ping DTN-send/receive DTN-traceroute DTN-perf DTN-heartbeat DTN-email DTN-chat Bundle Count / Traffic Measurement (NEW Request)
DTNGW
Rover
Habitat
ScienceSensor
1 Mbps
256 kbps
128 kbpsEARTH
MOON
L2Relay
LunarRelay
Always ON ?
Intermittent
Multiple Switched Ground Stations emulated as one single DTN GW
InternationalPartner #2
InternationalPartner #1
Switched
DTNGW
L2Relay
Habitat
LunarRelay
Rover
Sensor
SW
SW
CS
CS
CS
CS
Real-time Control Plan via IPv6
CS Channel Simulator(Rate, BER and Connectivity)
DTN Data Flow
NASA DEN Phase-0 Scenario
GRCEVAION
JSCRoverION
GSFCW. SandsION|LTP
GSFCL. RelayION|LTP
JSCAltair
ION/UDP
MSFCMCC/POCC
DTN2/[TCP|UDP]JPLXXX
DTN2/[TCP/UDP]
APLXXXION
Phase-0Continuous ConnectivityStatic routingNo BP Security
Delay: Lunar 3 secBW: 128kbps [>100Mbps]BP/LTP/Encap orBP/LTP/IP/Encap
Delay: 100s msec?BW: 72/k/192k
UDPTCP
BPUDP
BW: 10Mbps
StoryEVA sending some sort of telemetry (different kinds to APL and JPL)Understand that EVA data wouldn’t really go to APL/JPL
BPUDP
BPLTPUDP
BPLTPUDP
BP/LTP/Encap or BP/LTP/IP/Encap?OhioU has TCPCL for ION?
BW: 10Mbps
JPLAthleteDTN2
Limit the amount of available storage (later)
Mars Relay
Mars Odyssey Spacecraft +-------+ _ +-------+ | |:_:| | Deep Space Link +-------+ +-------+ _,,..--''' . . ___..---'' `. Proximity -.._ `. `. Link `- /\''' `. _,,. /__\ `,-' Deep ,'.------. Space `. / | Mars | Network `. | | Expl.| | | Rover| | `------'
Odyssey Relay Operations
Data Mule .-------. |Bundle | .-------. |Agent 1| |Bundle | .--o `-------' /''\. |Agent 5| / `. `. .' '._ .-----.,--. `-------' / | \ | `.._|Data | ``. \ / `. / |Mule | `-. \ ' |_ | `-----' `. ,/ | | Movement \.,.--- | ' <<======= | / | / | | Path Well .-------. | | Traveled |Bundle | | | |Agent 3| | / ...._ `-------' \ | | `. / `\ \ _.. | `./ .' `' `---`... `.._ `-. ,' .-------. _, ". ``. \ _,,' |Bundle |,' `. \ `--...,-'. |Agent 2| `. `. | `-------' `. _ \ .-------. ' `'-...._ | |Bundle | `"--------' |Agent 4|
LEO Sensor Satellite +-------+ _ +-------+ | |:_:| | +-------+ +-------+ ,' `. Space/Ground ,' `-. Space/Ground Link 1 ,-' `. Link 2 ,' `._ ,' `. ,' Connect Connect `._ _,' T1 T2 `. . ' ` / Ground `. ..,' Ground Station /\'' ___...------'''''''------....__ /\ Station 1 /__\.,--' `'--./__\ 2 _,,-' ._ _, `--.._ ' `. Ground/Ground Ground/Ground ,' ' `-. Link 1 Link 2 ,-' `._ ,-' `. _,' ' .-----------. | Data | |Collection | | Center | `-----------'
Low Earth Orbiting Satellite
Unmanned Aeronautical Vehicle (UAV)
. ,' `._ NORTH ,' `._ POLE ,-' `-.__ _,,-' Above 60 Degrees `'------''' +-------+ No Ku-Band |Iridium| Connectivity .'--'. +-------+ |UAV | XXXXXXXXXXXXXXXXXXXXXXX `-++-' XXXXXXXXXXXXXXXXXX X +--------------+ XX GEO X +--------------+ XX GEO Bent Pipe X || X Bent Pipe Relay Satellite X +--++--+ X Relay Satellite +-----+ _ +-----+ XX +------+ X +-----+ _ +-----+ | |:_:| | XX X | |:_:| | +-----+ +-----+ X X +-----+ +-----+ . XXXXXXXXXXXXX `: . . `. `. . _, \ /\''' .,'/\ ,' \/__\ /__\,' \ Ku-Band Ku-Band ,-' \ ASIA North / \ PACIFIC America ,' | OCEAN ,' NORTH ASIA | / AMERICA | ,' | / \ '
None ASCII Art - UAV