You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Concepts
This table explain briefly the concepts around Device Management Enabler (or service) its protocol and how device functions are exposed (via a management tree) to the remote server
Concept | Description | Diagram |
---|
Device Management Enabler | | |
Device Management Protocol | Protocol Commands: - Get: Retrieves the value associated with the target node in the Management Tree
- Replace: Sets the value associated with the target node, overwriting the previous value of the node
- Add: Creates a new node at the specified location in the Management Tree. The new node can be a leaf node or the root node for a management object
- Delete: Deletes a node, and the entire sub-tree beneath that node, if one exists
- Exec: Executes a predefined function, that is statically bound to the target node, on the device. Examples include initiating software download, running a diagnostic test etc.
- Copy: Replicates the structure and the node values associated with a sub-tree at one location to a different location within the Management Tree.
| |
Device Management Tree | The OMA DM protocol supports the notion of Management Objects (MOs). These are abstract representations of remotely manageable capabilities exposed by the device. All the available MOs pertaining to a device are organized in a hierarchical tree structure known as the Management Tree. The Management Tree may be looked upon as the complete management view of a device’s configuration and operational status. Different DM Servers may “see” different trees, depending upon their access rights to different portions of the Management Tree. | |