BioNet BioNet, Mar. 11, 20082008 CCSDS Spring Meeting Kevin Gifford, Sebastian Kuzminsky, Shea Williams BioNet Executive Overview BioNet 2.0 software framework

BioNet

BioNet, Mar. 11, 20082008 CCSDS Spring Meeting

Kevin Gifford, Sebastian Kuzminsky, Shea Williams

BioNet Executive Overview

BioNet 2.0 software framework for aerospace command, control and

communications

2008 CCSDS Spring Meeting, Wash. D.C.

BioNet


Presentation Outline

• BioNet brief history

• Why this is important

• What is BioNet?

• BioNet support for NASA projects

• Features and Benefits

• A design-driving scenario

• BioNet technical details (in brief)

• BioNet Demo

• Strategies for BioNet alignment for SOIS

BioNet


• BioNet Phase I NASA STTR awarded January 2006; Phase II awarded July 2007– Integrate disparate devices, heterogeneous networks into common data

integration framework– Involved with CCSDS standardization activities since 2004

• BioServe Space Technologies, UC-Boulder– Has flown 20 sortie and 6 ISS missions (CGBA, PGBA payloads)

• 18 Shuttle sorties; 2 to Mir; 6 to ISS• CGBA-2 payload launched on STS 112 (10/07/02 launch) (returned

Aug 2007; 5 yrs!)• CGBA-4 payload launched on ISS 12A.1 (12/14/06): currently on-orbit• CGBA-5 payload launched on ISS 13A.1 (8/8/07); currently on-orbit• BioNet middleware, and BioServe Communication Stack, on CGBA-4,

CGBA-5 payloads

• Since STS-77 (1996) the BioServe Communications Stack (BCS) has flown on all missions– First developers to fly Linux on the Shuttle and on the ISS– Flight proven for a decade and at TRL 9– Provides uplink commanding and automated, efficient receipt of flight

telemetry to groundside

BioNet Team / BioServe Space Technologies / Brief Synopsis

BioNet


BioNet Product Definition

• BioNet is a peer-to-peer enterprise-class data management middleware solution specifically designed for aerospace command and control operations

• Ease application development (data consumers)• Ease integration of hardware

BioNet


Why is this important

• Why is this an important problem: Complex aerospace vehicle systems need to have interoperable systems for command, control and communication

– BioNet’s unique advantage is that it enables all digital devices and networks “to talk to each other”, enabling interoperability, reducing costs and eliminating vendor lock-in

BioNet


BioNet


Benefit Requirement/Feature

Data interoperability Integration of data from any data-producing device or program. Voice, video and data can be stored, transported and displayed by a single unified enterprise data management system

No vendor lock-in Multi-vendor hardware integrated into a unified system. Non-proprietary (open) as well as proprietary solutions are readily integrated.

Independent development

The BioNet framework and development kit (DevKit) enables software composed by independent developers to be integrated. The framework enforces conceptual integrity of all software.

Mobility BioNet is explicitly designed for seamless roaming regardless of wireless technology enabling untethered mobility for personnel, vehicles, instrumentation and sensors

Scalability Peer-to-peer architecture enables highly scalable systems from tens of devices to thousands of data-producers required in aerospace “system of systems” architectures

Network robustness and reliability

Peer-to-peer network architecture automatically reconfigures to enable entire sub-networks to dynamically enter and leave the communications and control network

Benefits and Features

BioNet


Benefit Requirement/Feature

Eases flight software certification

Reduces time and costs associated with critical flight software certification by providing a service-oriented middleware infrastructure that is certified once; add-on software flight certified as required without recertification of the middleware.

Standards-based interoperable network communications

Enables interoperability of differing wireless (RF) technologies along with traditional wired data transmission for maximum flexibility [RFID, IEEE 1902.1 (RuBee), 802.11 (Wi-Fi), 802.15.1 (Bluetooth), 802.15.4 (ZigBee), 802.16 (WiMax), 1394, etc.]

Integrated security BioNet employs network and transport layer security architectures for authentication, authorization, data privacy, and data integrity.

Interplanetary Internet BioNet provides reliable message transfer across high-latency, intermittently-connected links via delay tolerant networking (DTN), enabling networked interplanetary communications.

Add-on and retro-fit activities

Facilitates late / retro-fit addition of additional sensors, controllers, etc. to add additional required functionality as new capabilities are deemed necessary through product life cycle.

Endpoint reprogrammability

Enables endpoint devices (sensors, radios, etc.) to be selectively chosen and dynamically reprogrammed to upgrade functionality while maintaining nominal operation of network.

Benefits and Features

BioNet


BioNet 2.0 Executive Summary

• BioNet major deliverables for v2.0:

– Peer-to-peer decentralized messaging architecture

– BioNet historical database: BioNet Data Manager, BDM

– Integrated security: network and application (BioNet)

– Provision of Delay Tolerant Networking, DTN

BioNet


Earth-to-Lunar network topology

BioNet


Lunar Habitat network topology

BioNet


Surface installation network topology

BioNet


Rover network topology

BioNet


BioNet Phase I: Centralized Message Broker

PowerMonitor

EventMonitor

RT DataDisplay

DeviceCommand

CustomApps

DataLogging

Network Aggregator (NAG)

HAB1

Net1

HAB2

Net2

HAB3

Net3

HABN

NetN

APP

API withnetworking

Devicehardware

BioNet


BioNet Phase II: Distributed Message Bus Architecture

BioNet


BioNet HABs BioNet clients

BioNet libraries

Peer DiscoveryInformation

(pub/sub + request/reply)

BPP DNS-SD BIP AMSQuick Silver

mDNS DNS TCPUDP

mcast

BioNet Communication Abstraction Layer (CAL)

CAL {

The CAL is used to investigate differing communication and peer protocols

BioNet


BioNet Demo(don’t forget webplots)

BioNet


SOIS Alignment Strategies for discussion

• SOIS historical has focused on small networks (a s/c bus) for a single spacecraft– BioNet focused on integrating disparate devices– BioNet focused on ease of application development – BioNet could potentially be used to a multiple-network

communication paradigm with multiple communicating assets using disparate physical layers and data formats

• SOIS context – BioNet provides application support services (middleware)

• Similar goals as SOIS Application Support Services– BioNet provides plug-and-play capability for disparate

hardware and disparate networks• Device discovery and service discovery• Similar goals as SOIS Plug-and-Play

– Modular incorporation of new standards and systems as they evolve

BioNet


SOIS Architecture

BioNet


BioNet


Presentation Summary

• Middleware “frameworks” ease software development– Provide software development framework and operational

infrastructure– Ensure conceptual integrity– Ease flight certification process

• SOIS historically focuses on smaller networks for a single spacecraft– BioNet can help to evolve to a network-centric communication

paradigm with multiple communicating assets using disparate physical layers and data formats

• SOIS context – BioNet provides application support services (middleware)– BioNet provides plug-and-play capability for disparate

hardware and disparate networks– Modular incorporation of new standards and systems as they

evolve

Documents

BioNet BioNet, Mar. 11, 20082008 CCSDS Spring Meeting Kevin Gifford, Sebastian Kuzminsky, Shea Williams BioNet Executive Overview BioNet 2.0 software framework