BioNet BioNet, 14-Oct-20082008 CCSDS Fall Meeting Kevin Gifford, Sebastian Kuzminsky, Shea Williams BioNet Executive Overview BioNet 2.0 software framework

BioNet

BioNet, 14-Oct-20082008 CCSDS Fall Meeting

Kevin Gifford, Sebastian Kuzminsky, Shea Williams

BioNet Executive Overview

BioNet 2.0 software frameworkBioNet is a candidate for the PnP application support layer for SOIS

2008 CCSDS Spring Meeting, Wash. D.C.

BioNet


Presentation Outline

• BioNet prototyping status– What is BioNet?

– Features and Benefits

– Prototype and Deployment Status

• BioNet-SOIS alignment concept

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– Previous demonstrations at NASA-JSC for medical / sciences– Demonstration for SOIS/CCSDS in Spring 2008– 2009 Demonstrations

• NASA JSC Wireless Lunar Habitat (DTN follow-on)• NASA JSC

• Since STS-77 (1996) the BioServe Communications Stack (BCS) has flown on all missions

– Can upgrade payload software subsystems remotely from groundside– 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 Brief Synopsis

BioNet


• BioServe Space Technologies, UC-Boulder– Have flown 21 sortie and 6 ISS missions (CGBA, PGBA

payloads)• 18 Shuttle sorties; 2 to Mir; 6 to ISS• New experiments manifested for next 4 Shuttle flights

to ISS (experiments benefit from ease of BioNet)• 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 is currently deployed on our ISS payloads (CGBA-4 / CGBA-5)– BioNet middleware, and BioServe Communication Stack, on

CGBA-4, CGBA-5 payloads– Use BioNet PnP framework to upload new experiment software in

modular fashion; includes uploading of software for DTN

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


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 (under development)

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 STTRDevelopment FY08 FY09 FY10 FY11

Phase IIKick-off

Jun-09

Phase IIcompletion

BioNet v2.2 DTN May-09

Potential Phase III project activities

v2 patentapplication

15-Jan-09

JSCdemo

BioNet v2.0 P2P

BDM Nov-09

CM Plan

01-Aug

Apr-09

EVAdemo

BioNet v2.1

Security Dec-09

BioNet


BioNet-SOIS proposed alignment concept

BioNet


BioNet-SOIS alignment proposed concept

BioNet



Assume that the hardware (h/w) device connected to the 1553 bus is a control moment gyro (CMG) and the hardware device connected to the 4-port SpaceWire hub is a second CMG. The hardware could be any digital device

At the PHY layer there are two communication buses, the first a 1553 serial bus and the second a SpaceWire bus. In this example both buses are wired but they could just as easily be wireless (e.g., IEEE 802.11 or IEEE 802.15.4)

Kernel-space (or in some instances user-space) device drivers provide the low-level protocol interface to the attached hardware

BioNet


BioNet-SOIS alignment proposed conceptThe SOIS Subnetwork service provides a standardized interface that sits on top (interfaces to) the device drivers. The SOIS Subnetwork abstracts the nuances of the different kernel-space, or user-space, device drivers via a standardized, published application programmer interface (API) to the BioNet-SOIS hardware abstractor

The BioNet-SOIS-HAB utilizes the SOIS Subnetwork API to interface (read and write) to the attached hardware in a standardized fashion.

The “bottom-half” of the BioNet-SOIS-HAB utilizes the SOIS-Subnetwork API to interface to the actual hardware, while the “top-half” of the HAB normalizes the data, and publishes data to any interested clients.

BioNet



The BioNet middleware proxies the client subscriptions to the HAB publishers in a network transparent manner. The BioNet middleware provides a standardized message bus over which data is sent from publishers (HABs) to client subscribers (Apps).

The BioNet middleware provides additional services including data compression, data security (authorization, authentication, confidentiality and integrity), Quality of Service, and time synchronization.

Applications subscribe to any data which they are interested in.

BioNet


SOIS Wireless and Plug-and-Play concepts to move forward

A position to contemplate

BioNet


SOIS PnP proposed forward concept

• Wireless RFID, WLAN, WPAN should not move out of SOIS– RFID, WPAN, WLAN activities are essentially small-diameter fast

local networks either for intra-vehicle or proximity vehicle / habitat networks – but SOIS may want to consider a more network-centric view

– PnP is part of this architecture because wired or wireless plug and play is typically a subnetwork service, more that a network service

– CCSDS Surface-to-surface (not proximity) and orbiter-to-surface wireless networks requirements and scenarios need to be defined with multi-agency consensus and an agreed-to CCSDS strategy

• For any PnP-type system, to be of practical use to CxP, the system would need to support DTN– This capability for BioNet, while in its initial stages, is still a few

months down the road– Suggest concentrating on solving the PnP problem within SOIS with

an eye towards the future of solving both PnP networks (not devices) and network mobility problem as a future research focus area

– Prototype the system, test with real hardware, evolve

BioNet


Characteristics of the proposed integration activity

• In a nutshell: One BioNet client application, two different hardware devices (CMGs) on two different buses that use the extensibility and modularity of both BioNet as a plug-and-play middleware and SOIS as a plug-and-play Subnetwork controller as the baseline system to demonstrate.

• Both SOIS and BioNet have substantial roles to play.

• It is a natural decomposition of both effort and functionality.

• The project integrates real spacecraft hardware and enables true plug-and-play software and hardware device integration.

• Project Goal: This system achieves the primary SOIS goal of enabling easy-to-compose, re-useable application software. Written correctly, both the BioNet-SOIS-HAB and the SOIS Subnetwork services will be re-useable across multiple spacecraft significantly decreasing effort, cost, and increasing reliability.

BioNet


Back-up slides

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


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


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, 14-Oct-20082008 CCSDS Fall Meeting Kevin Gifford, Sebastian Kuzminsky, Shea Williams BioNet Executive Overview BioNet 2.0 software framework