ICT Strategy Intelligent Highways: Endpoint Adapters

Agenda Intelligent Highways Roadside Devices Service-Oriented Device Architecture The OSGi Service Platform Device Management SODA Tools Streaming Services The Real-Time Enterprise Service Bus

Intelligent Highways Increasing amounts and sophistication now and in the future… …More devices (IPv6) …More data …in Real-Time…. “The right data at the right place at the right time – all the time”.

Roadside Devices Signs and Signals Sensors: Inductive loops ANPR Weather DSRC (e-Toll) Past, present and future Multi-vendor V2I/I2V

Service-Oriented Device Architecture When modelled as services, device access and control can be made available to a wide range of enterprise application software using service- oriented architecture mechanisms.

SODA Architecture In this model, responsibility for encapsulating services can be appropriately shifted to the suppliers who know them: One side deals with their device specific connections and protocol Other side deals with network interfaces needed to pump the data over a streaming protocol. A standard specified service can have a wide variety of underlying hardware, firmware, software and networking implementations.

SODA Adapters

Adapter Layers SOA binding (Bus Adapter) layer Handles the session level protocols for connecting and registering the device to an ESB Marshalling and un-marshalling Device layer Provides the meaningful input (commands), output (signals) and state (measurements) for the device Transport layer Converts between bytes and more meaningful objects or messages Initiates connection to the device Connection layer Sends and receives bytes Handles the connection to the hardware via RS485 (legacy), Ethernet, etc.

SODA Objectives To insulate SOA from device interfaces and proprietary vendor implementations. To facilitate integration. To accelerate and focus the convergence of technologies through a combination of: Standards Open source software Reference implementations Partners and community building …to achieve these objectives it builds upon the OSGi Service Platform…

OSGi (Formerly known as the Open Services Gateway initiative) The OSGi Service Platform spans: Digital mobile phones Vehicles Telematics Embedded appliances Residential gateways Industrial computers Desktop PCs High-end servers

OSGi Architecture The framework is conceptually divided into the following areas: Bundles - Bundles are normal jar components with extra manifest headers. Services - The services layer connects bundles in a dynamic way by offering a publish-find-bind model for Plain Old Java objects(POJO). Services Registry - The API for management services (ServiceRegistration, ServiceTracker and ServiceReference). Life-Cycle - The API for life cycle management (install, start, stop, update, and uninstall bundles). Modules - The layer that defines encapsulation and declaration of dependencies (how a bundle can import and export code). Security - The layer that handles the security aspects by limiting bundle functionality to pre-defined capabilities. Execution Environment - Defines what methods and classes are available in a specific platform.

Transport Example: Global System for Telematics GST Open Systems Implementation Guide Building Blocks for a Global System for Telematics Builds on OSGi Service Platform Runs on Java Virtual Machine

Device Management OSGi Network Management is protocol agnostic.

SNMP Support The SNMP Package provides an implementation of the SNMP protocol and acts as a bridge between SNMP entities and the OSGi framework plus OSGi services running on top. Its purpose is to manage the OSGi platform through SNMP.

SODA Device Kit Modeling Driven Design (MDD) Control Markup Language (CML) Auto-generate OSGi code for all four layers of the device adapter Contains more than 200 plug-ins for design time and runtime

Streaming services The real world never shuts up!!! Sensors and actuators do not match an HTTP request-response model. Data must be streaming. Enterprise Service Bus (ESB) streaming protocols include: Proprietary Message-Oriented Middleware (MoM). Java Messaging Service (JMS) for Java-centric busses. Extensible Messaging and Presence Protocol (XMPP) for low-band device data. Real-time Transport Protocol (RTP) for broadband device data. OMG Data Distribution Service (DDS) for mission-critical data.

The Real-Time Enterprise Service Bus