Bosch IoT Remote Manager Documentation

Package Overview

Functions

The TR-069 Device Management package provides a management solution for TR-069 enabled devices.

Key Features

The main features of the TR-69 enabled devices are:

  • Flexible and scalable security policy - for details refer to the Security Policy of TR-069 Device Management

  • Dynamic discovery of devices' parameters - ensures successful cooperation with any kind of data model that a TR-069 device may have and implies that no integration efforts are needed for custom data structures support

  • Vendor-specific parameters support - as a consequence of the independence of the ACS implementation of data models, vendor-specific parameters are supported

  • Vendor-specific methods providers - just by registering OSGi services on the backend, a third party can add vendor-specific CPE or ACS RPC methods for custom TR-069 devices

  • Representation of TR-069 Devices as Control Units - as the control unit abstraction provides means for unified management of devices or other resources (see TR-069 Devices as Control Units), it brings some of the following advantages:

    • For each TR-069 device several management scripts and rules can be executed

    • Advanced views and mass management operations - various filters for devices can be applied (based on device info, parameter values, group location and so on)

    • Local and remote access via the Generic Device Manager API

    • Notification for changes on the devices

  • Tree to Control Unit Mapping - developers can easily represent devices with specific parameter structure in a friendly way as a set of optimized control units by using RM's tree-to-CU mapping. The transformation is based on the exact mapping between concrete device tree nodes and the control units (more info in Tree to Control Unit Mapping)

  • Auto-tasks - the device operator can define a set of rules and actions that should be performed during a device's management life-cycle. For instance, he can define that when a device registers/connects specific parameter, values should be set or certain nodes have to be synchronized (more info in Auto-Tasks, part of TR-069 Device Management Model)

  • Support of TR-069 related specifications:

    • TR-069, "CPE WAN Management Protocol" - Original, Amendments 1, 2 and 3

    • TR-098, "Internet Gateway Device Data Model for TR-069" - Original, Amendments 1 and 2 (1.0.0, 1.1.0, 1.2.0)

    • TR-104, "Provisioning Parameters for VoIP CPE" - Original, including the tone and ring download files defined there

    • TR-106, "Data Model Template for TR-069-Enabled Devices" - Original, Amendments 1, 2 and 3, supporting the Device Type and Device Instance XML documents

    • TR-111, "Applying TR-069 to Remote Management of Home Networking Devices" - Both mechanisms, "Device-Gateway Association" and "Connection Request via NAT Gateway", are supported

    • TR-135, "Data Model for a TR-069 Enabled STB"

    • TR-140, "TR-069 Data Model for Storage Service Enabled Devices" - This data model is supported as a consequence of the general data model support. No data model description in XML format can be used with RM yet

    • TR-142, "Framework for TR-069 enabled PON Devices" - Issue 2. The PON data model is supported as a consequence of the TR-098 and TR-104 data models

    • TR-143, "Enabling Network Throughput Performance Tests and Statistical Monitoring" - The data model is supported

    • TR-157, "Component Objects for CWMP" - Original and Amendment 1

    • TR-196, "Femto Access Point Service Data Model"

  • SAX-based SOAP parser, prepared for some types of non well-formatted messages (some devices may send non well-formatted, but still readable messages)

  • Fine-grained configuration of the ACS to precisely define the mechanism for treating a particular TR-069 device

Package Dependencies

The TR-069 Device Management package requires the following packages for its proper operation:

  • System Package - comprises the core of the RM system.

  • Generic Device Management - delivers the general model (called "Control Unit" model) for managing various type of devices and/or other manageable resources in a common way.

  • Software Repository - provides a central and unified storage for deployment units which can be downloaded and installed on devices of different types.

  • User Management - provides features for management of user access to TR-069 devices.


images/confluence2/download/attachments/88359423/tr-069managementpackageoverview-version-1-modificationdate-1699430052000-api-v2.png


Directory Structure

Directory

Sub-Directory

Description

lib


/api/tr069dm-api.jar

The public API of the RM TR-069 Device Management Package, which may be used for compilation of custom applications.

/rac/tr069dm-rac.jar

Remote Access Client library of the RM TR-069 Device Management Package. Provides remote connectivity and Java API to the RM servers.

licenses

/TR-069 Device Management

Holds the license agreement of the package.

packages

/tr069dm

Contains bundles for managing Mobile OSGi devices, installed on the backend.

initial_config


/tr069_autotasks

Contains the auto-task XML schema and definitions.

/tr106

Contains the data model XML schemas for the models defined by the Broadband Forum.

/tree2cu

Contains the Tree to Control Unit Mapping schema and XML files.