all rights reserved © alcatel-lucent 2006, ##### osgi: remote management support for tr-069 willem...

All Rights Reserved © Alcatel-Lucent 2006, #####

OSGi: remote management support

for TR-069

Willem Acke

February, 2007

All Rights Reserved © Alcatel-Lucent 2006, #####2 | OSGi: remote management support for TR-069 | March 2007

Agenda

1. Introduction TR-069

2. OSGi support for TR-069 remote management

3. Conclusion


1 (short) TR-069 introduction


The CPE WAN Management Protocol: TR-069

DSLHome (from DSLForum) defined the CPE WAN management protocol (TR-069) for Auto-configuration and dynamic service provisioning Software/firmware image management Status and performance monitoring Log file, and dynamic notification Diagnostics

TR-069 features TR-069 has notion of sessions over TCP/IP (integrity, authentication, security) Simple TR-069 object model and profiles (all standardized!!!) TR-069 is an event-driven model TR-069 has dynamic active and passive notification TR-069 CPE WAN remote management protocol is access agnostic TR-069 allows End-users devices (RG, STB, VoIP,…) management (TR-111) TR-069 is designed to handle millions of devices (scalability, robustness)

Interoperability guaranteed through standardized objects models and plug fest

Huge Market traction and adoption (by SP, chipset vendors, CPEs vendors)


TR-069 topics (1/2)

Protocol HTTPS/SOAP CPE initiated connections

Periodic Triggered by parameter change (‘Active Notification’)

ACS initiated connections Connection request NAT support: TR-111

RPC methods: General methods:GetRPCMethods CPE methods: Get-/Set- ParameterValues, Get-/Set

ParameterAttributes, … ACS methods: RequestDownload


TR-069 topics (2/2)

Data model: Standardized models, with possible vendor extensions Structured in tree Each parameter is a name-value pair

E.g. Device.Device.DeviceInfo.Description E.g. Device.Services.OSGi.FrameworkInfo.version

Each parameter has attributes E.g. Notification, Access List


2 OSGi support for TR-069 management


TR-069: OSGi remote management

Define mechanisms to enable TR-069 remote management for: Platform management Bundle life-cycle management Bundle configuration management Eventing and logging Mapping of discovered devices to TR-069: e.g. UPnP devices


OSGi TR-069 management checklist (1/2)

Platform and bundle management

Discovery Discovery of platform Discovery of bundles Discovery of services

Bundle life cycle management Start/stop/uninstall Download (via TR-069 extension) Startlevel Permissions


OSGi TR-069 management checklist (2/2)

Bundle configuration and control Configuration admin interface (some limitations

identified) Bundle run-time configuration/actions

Needs TR-069 compatible interface Mobile approach (DMTAdmin/DMT Tree) does not map to TR-069

requirements

Events and logging Events (via Event Admin service + notification) Logging(via Log Service + TR-069 upload)

External device discovery UPnP


TR-069 management for OSGi: new requirement

Requirement:

TR-069 compatible bundle interface

Why:

- TR-069 based remote management of OSGi platform is natural extension of current remote management of fixed devices (gateway, VoIP, STB, …)

- Current mobile spec (DMT Admin/DMT tree) does not map to TR-069 protocol and data model

What:

standardize bundle interface, and procedures (e.g. registering interface in the service registry) for TR-069 based remote management


Conclusion

Most features necessary for basic TR-069 based remote management are available

The one missing feature is a bundle interface compatible with TR-069 based management


Backup


High level overview of TR-069 object model

OSGi information starts under Device.Services branch of data model (conform to TR-106)

Main OSGi related top level branches: .OSGi.FrameworkInfo .OSGi.FrameworkConfig .OSGi.Bundle.{i} .OSGi.Services.{i}

Detected UPnP services also start from Device.Services .UPnP.Devices.{i}


www.alcatel-lucent.com

all rights reserved © alcatel-lucent 2006, ##### osgi: remote management support for tr-069 willem...

Documents