Device management system using log management object and method for generating and controlling logging data therein

• US 7,917,476 B2
• Filed: 09/29/2006
• Issued: 03/29/2011
• Est. Priority Date: 10/01/2005
• Status: Active Grant

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: Kim, Te-Hyun
• Primary Examiner(s): Fleurantin; Jean B.
• Assistant Examiner(s): Jami; Hares
• Application Number:
  US12/065,746
• Publication Number:
  US 20080195671A1
• Time in Patent Office: 1,642 Days
• Field of Search: 707/790, 707/802, 707/803, 707/609, 707/661, 707/665, 707/672, 711/161, 711/162
• US Class Current: 707/661
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 41/044 comprising hierarchical management structures
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network

Abstract

A device management (DM) system using a log management object and a method for effectively generating and controlling logging data in the system are disclosed. A DM server includes only information that a client can transfer processing of a corresponding command to a logging sub-tree manager in the logging data storage command and transmits it, and an accurate location at which the logging data is to be stored is determined by the logging sub-tree manager by itself by using control information of the logging sub-tree upon receiving the logging data storage command. Each node storing the logging data has a source attribute value and a reason attribute value. Accordingly, the DM server or a scheduling context does not involve in a complicate logging data storage procedure, and when logged node is checked, the particulars of the logged data can be easily recognized.

Claims

1. A method for generating and controlling logging data in a device management (DM) system comprising:

receiving, by a DM client, a command for storing logging data from a DM server;

determining, by the DM client, a position for storing the logging data in a logging sub-tree,

wherein the logging sub-tree comprises a ‘

Control’

node;

a control part connected with the ‘

Control’

node for controlling a method for storing the logging data;

a ‘

Data’

node; and

a data part connected with the ‘

Data’

node for providing a space for storing the logging data,

wherein the control part comprises a ‘

Size’

node indicating a maximum number of logging data that can be stored, a ‘

Current’

node indicating a position where a next logging data is to be stored, and a ‘

Recursive’

node indicating how to process new logging data when the space for storing the logging data is full; and

storing, by the DM client, the logging data in the determined position in the logging sub-tree,

wherein the step of storing the logging data comprises;

checking, by the DM client, whether there is an empty logging storage space;

if there is an empty logging space, generating, by the DM client, a new folder node indicated by a value of the ‘

Current’

node and storing the logging data in the new folder node;

if there is no empty space, checking, by the DM client, whether a value in the ‘

Recursive’

node within the logging sub-tree is true;

determining, by the DM client, a position of a node to be deleted with reference to a value of the ‘

current’

node if the value of the ‘

Recursive’

node is true; and

deleting, by the DM client, all data included in the determined node and storing the logging data.

2. The method of claim 1, wherein the command for storing logging data includes a DM object to be logged and a Uniform Resource Identifier (URI) of a position where a value of the DM object is to be stored.

3. The method of claim 1, wherein the command for storing logging data is a copy command for duplicating a value of a certain DM object to the logging sub-tree.

4. The method of claim 1, wherein the logging sub-tree management unit responds to the command for storing logging data only when the command for storing logging data instructs the ‘

Data’

node as a storage position of the logging data.

5. The method of claim 1, wherein the command for storing logging data is received from the DM server or a scheduling context.

6. The method of claim 1, wherein the data part comprises:

a plurality of folder nodes; and

at least one or more data nodes which are connected with each folder node to store the logging data.

7. The method of claim 1, further comprising:

discarding the logging data if there is no empty storage space and the value of the ‘

Recursive’

node is false.

8. The method of claim 1, wherein a name of the generated new folder node increases sequentially from 1 up to a value of the ‘

Size’

node.

9. The method of claim 1, wherein when the logging data is stored, a source attribute value for indicating an original Uniform Resource Identifier (URI) of the logging data and a reason attribute value for indicating a cause of the logging are also stored together in each data node that stores the corresponding logging data.

10. The method of claim 9, wherein the reason attribute value is a scheduling context ID.