Management tree management in a mobile handset
First Claim
Patent Images
1. A mobile device managed by a device management server, the mobile device comprising:
- a device management tree comprising a plurality of nodes and leaves from several different environments, wherein the plurality of nodes and leaves represent at least a firmware component and at least a software component including a provisioning parameter and a configuration parameter, and wherein the device management tree is capable of being manipulated by the device management server;
wherein at least one of the firmware component and the software component is resident in the mobile device;
a first mechanism providing access to the device management tree operable via a management client to provide read and/or write synchronization of the plurality of nodes and leaves; and
a second mechanism providing access to the device management tree operable via an agent to provide access to the plurality of nodes and leaves during a compilation of the agent with an associated application interface or component interface of the management tree;
wherein the device management tree being locally accessible by at least a subset of the at least one of a firmware component and a software component resident in the mobile device via each of the first and second mechanisms providing access to the device management tree; and
wherein at least one of the plurality of nodes and leaves comprises a special node that is located at a predetermined location in memory that is known and accessible by the at least a subset of the at least one of a firmware component and a software component resident in the mobile device.
7 Assignments
0 Petitions
Accused Products
Abstract
A mobile handset network employs a device management server to manage managed objects that are located in a management tree. Access to the managed objects in the management tree is provided to applications and components that execute in the same environment or in different environments. Special managed objects are employed that are accessible by the DM client as well as by the update agents in the mobile handset.
-
Citations
19 Claims
-
1. A mobile device managed by a device management server, the mobile device comprising:
-
a device management tree comprising a plurality of nodes and leaves from several different environments, wherein the plurality of nodes and leaves represent at least a firmware component and at least a software component including a provisioning parameter and a configuration parameter, and wherein the device management tree is capable of being manipulated by the device management server; wherein at least one of the firmware component and the software component is resident in the mobile device; a first mechanism providing access to the device management tree operable via a management client to provide read and/or write synchronization of the plurality of nodes and leaves; and a second mechanism providing access to the device management tree operable via an agent to provide access to the plurality of nodes and leaves during a compilation of the agent with an associated application interface or component interface of the management tree; wherein the device management tree being locally accessible by at least a subset of the at least one of a firmware component and a software component resident in the mobile device via each of the first and second mechanisms providing access to the device management tree; and wherein at least one of the plurality of nodes and leaves comprises a special node that is located at a predetermined location in memory that is known and accessible by the at least a subset of the at least one of a firmware component and a software component resident in the mobile device. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A mobile device that facilitates the creation and manipulation of a plurality of managed objects in a management tree based upon information received via a communication network, the mobile device comprising:
-
non-volatile memory including the plurality of management objects from several different environments representing at least firmware and software components including provisioning parameters and configuration parameters, the management tree having a root serving as a gateway or navigation point to the plurality of managed objects in the management tree; a firmware component comprising update agent code for converting at least a portion of the non-volatile memory from a first version of code to a second version of code; one or both of an operating system and/or an application; a management client providing the one or both of an operating system and/or an application with access to at least a subset of the managed objects to provide read and/or write synchronization of the management objects; an agent providing the one or both of an operating system and/or an application with access to at least a subset of the managed objects during a compilation of the agent with an associated application interface or component interface of the management tree; and at least a subset of the managed objects being special managed objects each of whose physical location in the non-volatile memory is assigned to a predetermined memory address, wherein the special managed objects are accessed and executed from the predetermined memory address in the non-volatile memory by each of the firmware component and the management client. - View Dependent Claims (10, 11, 12, 13, 14, 15, 16, 17, 18, 19)
-
Specification