1 / 15

OSGi: remote management support for TR-069

This article introduces the TR-069 protocol and discusses the support for remote management through OSGi. It covers topics such as protocol features, data models, and the checklist for OSGi TR-069 management. The article also suggests the need for a TR-069 compatible bundle interface for OSGi management.

aperez
Download Presentation

OSGi: remote management support for TR-069

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OSGi: remote management support for TR-069 Willem Acke February, 2007

  2. Agenda • 1. Introduction TR-069 • OSGi support for TR-069 remote management • Conclusion

  3. 1 (short) TR-069 introduction

  4. 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)

  5. 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

  6. 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

  7. 2 OSGi support for TR-069 management

  8. 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

  9. 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

  10. 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

  11. 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

  12. 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

  13. Backup

  14. 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}

  15. www.alcatel-lucent.com

More Related