System and method for provisioning device management tree parameters over a client provisioning protocol

• US 20050232175A1
• Filed: 04/16/2004
• Published: 10/20/2005
• Est. Priority Date: 04/16/2004
• Status: Abandoned Application

• Current Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Klots, Boris, Draluk, Vadim, Latypov, Dmitri R.
• Application Number:
  US10/826,833
• Publication Number:
  US 20050232175A1
• Time in Patent Office: Days
• US Class Current: 370/310
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

A client device (102) of a communication system (100) comprising a provisioning and management framework (206). The framework (206) receives (404) a client provisioning document from a source (110), and the client provisioning document includes a device management characteristic. The client device (102) then identifies (408) a device management characteristic from the client provisioning document. Thereafter, the client device (102) provides (424) data based on the device management characteristic of the client provisioning document to a device management tree (226, 426).

Claims

1. A method for a client device of a communication system comprising:

receiving a client provisioning document from a source;

identifying a device management characteristic from the client provisioning document; and

storing data based on the device management characteristic of the client provisioning document to a device management tree.

2. The method of claim 1, wherein receiving a client provisioning document from a source includes receiving the client provisioning document from a remote server over a wireless communication link.

3. The method of claim 1, wherein identifying a device management characteristic from the client provisioning document includes identifying at least one of a URI parameter, an OP parameter and a DATA parameter corresponding to the device management characteristic.

4. The method of claim 3, further comprising appending the URI parameter if the client provisioning document only includes the URI parameter.

5. The method of claim 3, further comprising setting the OP parameter to a REPLACE status if the device management characteristic does not include the OP parameter.

6. The method of claim 3, further comprising resetting the DATA parameter to a default value if the device management characteristic does not include the DATA parameter.

7. A client device of a communication system comprising:

a provisioning and management framework configured to receive a client provisioning document, the client provisioning document includes a device management characteristic.

8. The client device of claim 7, wherein the provisioning and management framework receives the client provisioning device from a remote server over a wireless communication link.

9. The client device of claim 7, wherein the device management characteristic corresponds to at least one of a URI parameter, an OP parameter and a DATA parameter.

10. The client device of claim 9, wherein the provisioning and management framework appends the URI parameter if the client provisioning document only includes the URI parameter.

11. The client device of claim 9, wherein the provisioning and management framework sets the OP parameter to a REPLACE status if the device management characteristic does not include the OP parameter.

12. The client device of claim 9, wherein the provisioning and management framework resets the DATA parameter to a default value if the device management characteristic does not include the DATA parameter.

13. The client device of claim 7, further comprising a device management engine communicating with the provisioning and management framework, the device management engine being configured to update a device management tree based on the device management characteristic of the client provisioning document.