![](https://csdnimg.cn/release/download_crawler_static/1448750/bg11.jpg)
WiMAX Forum Network Architecture - WIMAX Over-The-Air Provisioning & Activation Protocol based on OMA
DM Specifications
Page - 9
WiMAX FORUM PROPRIETARY AND CONFIDENTIAL – SUBJECT TO CHANGE WITHOUT NOTICE
5. OMA DM Protocol Overview 1
5.1 Introduction to OMA DM Protocol 2
The OMA DM Protocol [DMPRO] defines a management framework and a protocol for various management 3
procedures. This section describes briefly the core components of OMA DM architecture. 4
5.1.1 Management Tree 5
Every device that supports OMA DM SHALL contain a management tree. All available MOs are logically grouped 6
in the MS as a hierarchical tree structure called the management tree. Thus, the management of a service or 7
application in the DM framework requires accessing nodes in the management tree corresponding to the service or 8
application. 9
The management tree is structured on the basis of services, and applications. Each node in the management tree is 10
addressed with a URI as described in the OMA DM Tree and Descriptions specification [DMTND]. 11
Using the Device Description Framework (DDF) [DMDDFDTD] of the management tree, and the tree exchange 12
mechanism [DMTND], the management server knows the URI [DMPRO] of the location to be referred to for a 13
specific management action. 14
In the management tree, WiMAX objects would be specific sub-trees. Similarly application objects form other sub-15
trees of the management tree. Annex A describes the WiMAX management tree. 16
5.1.2 Device Description 17
The MOs in the management tree are made known to the management server through the DDF of the MS. The DDF 18
document is an XML document [XML], which is made available to the management server. The DDF Document 19
Type Definition (DTD) specified in [DMDDFDTD] is used to describe the management syntax and semantics for a 20
particular MS. 21
The DDF description gives the properties, such as type, format, description etc of each object, and their relative 22
location in the management tree. The server learns the MOs and how to manage the objects from the DDF 23
description. 24
The DDF mechanism provides management of new and customized features in the device. 25
Features common to a class of devices can be grouped and standardized for interoperability and can coexist as a 26
standardized MOs in the management tree of such a device along with non-standardized MOs. The elements, or 27
nodes, that describe the common features of all WiMAX devices described in Annex A of this document, SHALL 28
be grouped into a single standardized WiMAX MO that can be represented using the DDF DTD. 29
5.1.3 Bootstrap Mechanism 30
In order for the DM client of a device to initiate a management session, a bootstrap process MUST be performed to 31
provision the device with the required settings to initiate a session with a specific DM server. OMA DM supports 32
three possible methods for the bootstrap process: factory bootstrap, bootstrap from smartcard, or secure server-33
initiated bootstrap for initial provisioning. The bootstrap mechanism is defined in the OMA DM Bootstrap 34
specification [DMBOOT]. 35
This document specifies how the server-initiated and WiMAX specific client-initiated bootstrap (WIB) are 36
implemented in WiMAX. The other bootstrap methods are fully implemented in WiMAX as defined in [DMBOOT] 37
except as stated otherwise in this specification. 38
5.1.4 OMA DM Packages and Messages 39
In OMA DM, a set of messages exchanged between the DM client and the management server, is conceptually 40
combined into a package. In most situations a package corresponds to a single message, but when large objects are 41
involved in the transfer, each package is sent over multiple DM messages. A DM message is a well-formed XML 42