SIPifying OSGi - M Ma

SIPifying OSGiPanasonic Information and Networking Technologies LaboratoryPanasonic TechnologiesPrinceton, New Jersey USA

Dennis BushmitchAlex GelmanAlan KaplanMatthew [email protected]

Outline

Consumer Networking Convergence (CNC)A Step Toward CNC – SIPifying OSGISummary

Consumer Networking ConvergenceThe Basis For a Value Proposition

Consumer applications must serve at least one of the following areas

Domestic productivityEconomics Education/profession/businessEntertainmentFamily/community/social lifeHealthcare/welfareSafety

Consumer Networking Convergence can be only supported byapplication-specific networked devices that are part of personal lifestyle

Consumer Networking Convergence can be only supported byapplication-specific networked devices that are part of personal lifestyle

Consumer Networking Convergence ParadigmThe Networking Scenario

ApplianceControl Network

HomeComputing Network

OO

HomeEntertainment Network

Home Server

InternetInternet

STB + BGW

Public Area Hot Spots

ASP

Consumer Networking Convergence Applications Paradigm Shift

InformationAccess andProcessing

Entertainment

Communications

Disjointed ComputingDisjointed Computing

Entertainment

ConvergentComputing

Communications

Convergent ComputingConvergent Computing

InformationAccess andProcessing

InformationAccess andProcessing

Autonomicself-aware, self-configuring, self-maintaining

Cognitiveenvironmentally perceptive and reactive

Transparentoperate and adapt with minimal impact on consumer

Pervasiveanytime, anywhere, anybody

AutonomicAutonomicself-aware, self-configuring, self-maintaining

CognitiveCognitiveenvironmentally perceptive and reactive

TransparentTransparentoperate and adapt with minimal impact on consumer

PervasivePervasiveanytime, anywhere, anybody

• DTV Channel Monitoring & Control• Recording/Play-Back Control

InternetInternet

Wireless Carrier

RGW Home Server

Remote Parental Control

Panasonic

An Example of CNCIn and Out of Home Device Control

InternetInternet

Wireless Carrier

RGW Home Server

Remote Parental Control

Panasonic

• DTV Channel Monitoring & Control• Recording/Play-Back Control

An Example of CNCIn and Out of Home Device Control

Consumer Networking ConvergenceBasic Architectural Approach

Middleware & Protocols are the key in a convergent computing world

Hide the complexities and heterogeneity in a convergent world

Different hardware, OS, protocols, networks

Enable the creation of novel services and applications

Internet Protocols

Platform: OS & HW

Convergent Computing Protocols

Convergent Computing Middleware

DTV AppliancesMobile HomeNetComp&Ent

TransparentTransparentPervasivePervasive

AutonomicAutonomicCognitiveCognitive

OSGi and SIP

Create a specification for an OSGi service, which defines APIs that enable:

Secure wide area support of device registration, communication, control, and event handling utilizing SIP (e.g., 4G Mobile)OSGi Device mobility (application layer) using SIPInter-working and inter-gateway bridging of heterogeneous local area device communication protocols (e.g., UPnP, Jini) across wide area network

Use Case 1: Secure WAN Communication of Diverse Devices

UPnP Service SIP UA

InternetInternet

Home Content Server

Wireless Carrier

MobileDevice

UPnP Ctrl.Pt.Jini

G/W

SIP Stack

ProposedOSGi SIP

Service

OSGi UPnPService

OSGi JiniService

• SIP protocol enables secure access from wide area to local devices connected to the gateway

• An OSGi SIP service will bring OSGi Framework support to mobile SIP devices

Use Case 2: Device / Service Mobility using SIPUPnP device (camcorder) moves from GW1 to GW2

SIP Proxy

UPnP device in GW1 is registered with SIP proxy as SIP device. Upon relocation to GW2, it re-registers with SIP proxy, given it a newlocation

OSGi GW1

UPnP SIP

OSGi GW2

UPnP SIP

CamcorderServiceBundle

Implications: Home gateway devices can roam to foreign gateways without service interruptions

Use Case 3: Inter-gateway Bridging

Use SIP to import/export OSGi devices from/to service registries

OSGi GW 1

UPnP SIP

OSGi GW 2

UPnPSIP

OSGI service registry OSGI service registry

Implications: Home devices/services accessible as local devices/services on the car gateway and vice-versa

Additional motivations behind the proposed service

Many vendors investigating SIP for device to device control in various home networking scenarios OSGi is an ideal unifying framework, which can bridge multiple device control frameworks (UPnP, Jini, now SIP)Proposed service will provide OSGi framework with ability to interact with new types of devices

Intro to SIP

SIP - Session Initiation Protocol (RFC2543)Originally thought as a signaling protocol for multimedia session establishmentClient - Server Protocol

Basic request - response protocolSIP User Agents (UAS and UAC are communicating with each other)

Supports event notificationCritical function for the device control

Can be extended with new METHODS and HEADERS via standardization in IETF

Example use of SIP for instant messaging

Main Aspects of SIP

“Application” layer protocol, which supports MIME type attachments as payloadsCan be used as a “mobile transport” protocol as application-specific chunks of data can be transported within MIME Supports service and device mobility

Logical naming for device in a form of URLs creates an abstraction for a physical device: service tied to devices capability and not a physical deviceSIP proxies route the messages to a recipient based on registration informationSender of SIP message doesn’t need to know the location of the receiver

These combined make SIP a very powerful protocol for device / service discovery and device control

Background: SIP and Device Control

SIP protocol provides all the needed capabilities for device/service/control point mobility, discovery, registration, eventing, control, presentation

Existing SIP methods accommodate functionalityREGISTER, MESSAGE, SUBSCRIBEAdditional information can be carried inside new MIME type

The related proposed SIP extensions in IETF:Device control (Telcordia) – http://www.argreenhouse.com/iappDevice/service capability negotiation, CC/PP over SIP (Fujitsu)Instant messaging and presence (SIMPLE) –http://www.ietf.org/html.charters/simple-charter.html

Defining Characteristics

Proposed service is different from a vanilla SIP protocol bundleProvides “high end” SIP device control service to other bundles / end userUnderlying SIP device control issues need to be transparent to application developersProposed service is different from API specification to SIP protocol’s general functionality

Examples of similar level OSGi services: Jini, UPnPExample level of abstraction in the proposed API

SIP device reference via SIPDevice SIP device registration via SIPServerSIP device communication interface SIPUserAgent

Proposed Service Requirements

OSGi APIs have to be provided for:Export of OSGi devices into mobile SIP-based device communication frameworkImport of SIP device functionality into OSGi framework

Use OSGi device access driver modelSIP Device Service Driver must register SIP devices with OSGiFramework

SIP devices need to be devices in the context of the OSGiframework’s device manager

More Service Requirements

Bundles need to discover registered SIP devicesBundles must be able to listen to SIP-devices’ eventsBundles must be able to control SIP devices and be controlled by SIP devicesProvide SIP globally unique URIs to devices

Use of SIP logical naming for OSGi devicesProvide communication between device driver and a device using SIP

Summary

An OSGi SIP Service for device communication enables capabilities currently not in the OSGi specification

Secure, wide-area access to the OSGi gatewayMobility/roaming of devices and servicesInter-gateway bridging of devices and services

SIPifying OSGi provides the foundation for Consumer Networking Convergence!

Questions?