Device Management System Using Log Management Object and Method for Generating and Controlling Logging Data Therein

• US 20080195671A1
• Filed: 09/29/2006
• Published: 08/14/2008
• 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
• Granted Patent: US 7,917,476 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• 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 a command for storing logging data; and

determining, by a logging sub-tree management unit of a DM client, a location for storing the logging data in a logging sub-tree and storing it the determined location in the logging sub-tree.

2. The method of claim 1, wherein the storage command includes a DM object to be logged and a URI of a location where a value of the DM object is to be stored.

3. The method of claim 2, wherein the URI is Log/Data.

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

5. The method of claim 1, wherein the logging sub-tree management unit performs the storage command only when the storage command instructs the Log/Data as a storage location of the logging data.

6. The method of claim 1, wherein the storage command is received from the DM server or a scheduling context.

7. The method of claim 1, wherein the logging sub-tree comprises:

a Log/Control node;

a control part, connected with the Log/Control node, for controlling a way how to store the logging data;

a Log/Data node; and

a data part, connected with the Log/Data node, for indicating a location where the logging data is stored.

8. The method of claim 7, wherein the control part comprises Size, Current and Recursive nodes.

9. The method of claim 8, wherein the Size node indicates the maximum number of logging data that can be stored, and the Current node indicates a location where the next logging data is to be stored.

10. The method of claim 8, wherein the Recursive node indicates how to process new logging data when the storage space for logging data is full.

11. The method of claim 7, 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 and actually store the logging data.

12. The method of claim 1, wherein the logging sub-tree management unit determines the storage location of the logging data with reference to a value of the control part of the logging sub-tree.

13. The method of claim 1, wherein the storing of the logging data comprises:

checking whether there is an empty logging storage space;

generating a new folder node and storing the logging data when there is an empty space;

checking whether a Log/Control/Recursive value within the logging sub-tree is true when there is no empty space;

determining a location of a folder node to be updated with reference to a Log/Control/Current value if the Log/Control/Recursive value is true; and

deleting every data node included in the determined folder node and storing the logging data.

14. The method of claim 13, further comprising:

discarding the logging data if there is no empty storage space and the Log/Control/Recursive value is false.

15. The method of claim 13, wherein the name of the newly generated folder node increases sequentially from 1 up to Log/Control/Size.

16. The method of claim 1, wherein when the logging data is stored, a source attribute value and a reason attribute value can be also stored together in each data node that stores the corresponding logging data.

17. The method of claim 16, wherein the source attribute value is the original URI of the logging data.

18. The method of claim 16, wherein the reason attribute value is information for allowing a cause of the logging recognized, namely, a scheduling context ID.

19. A logging data sub-tree in a device management (DM) system, comprising:

a Log/Control node;

a control part, connected with the Log/Control node, for controlling a way how to store the logging data;

a Log/Data node; and

a data part connected, with the Log/Data node, for indicating a storage space of the logging data.

20. The sub-tree of claim 19, wherein the control part includes Size, Current and Recursive nodes.

21. The sub-tree of claim 20, wherein the Size node indicates the maximum number of logging data that can be stored, and the Current node indicates a location where the next logging data is to be stored.

22. The sub-tree of claim 20, wherein the Recursive node indicates how to process new logging data when the storage space for logging data is full.

23. The sub-tree of claim 19, 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 and actually store the logging data.

24. The sub-tree of claim 23, wherein each data node is stored together with a source attribute value and a reason attribute value of the logging data.

25. The sub-tree of claim 24, wherein the source attribute value is the original URI of the copied logging data.

26. The sub-tree of claim 24, wherein the reason attribute value is information of indicating a cause of the logging data.

27. The sub-tree of claim 24, wherein the reason attribute value is a scheduling context ID.

28. A device management (DM) system comprising:

a DM server for transmitting a DM command for storing logging data;

a logging sub-tree for actually storing the logging data therein; and

a DM client for determining a location for storing the logging data in a logging sub-tree and storing the logging data in the determined location in the logging sub-tree, when the received DM command indicates storing of the logging data in the logging sub-tree.

29. The system of claim 28, wherein the DM command is a duplicating command for instructing storing of a value of a certain DM object in the logging sub-tree.

30. The system of claim 29, wherein the copy command defines only Log/Data.

31. The system of claim 28, further comprising:

a front end for transferring the DM command to a logging sub-tree management unit when the DM command includes Log/Data; and

the logging sub-tree management unit for determining a location for storing the logging data in the logging sub-tree according to a logging data storage management policy and storing the logging data the determined location in the logging sub-tree, when the DM command defining Log/Data is received from the front end.

32. The system of claim 28, wherein the logging sub-tree comprises:

a Log/Control node;

a control part, connected with the Log/Control node, for controlling a method for storing and recording logging data;

a Log/Data node; and

a data part, connected with the Log/Data node, for indicating a storage space of the logging data.

33. The system of claim 32, wherein the control part includes Size, Current and Recursive nodes.

34. The system of claim 33, wherein the Size node indicates the maximum number of logging data that can be stored, and the Current node indicates a location where the next logging data is to be stored.

35. The system of claim 33, wherein the Recursive node indicates how to process new logging data when the storage space for logging data is full.

36. The system of claim 32, 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 and actually store the logging data.

37. The system of claim 31, wherein when the logging sub-tree management unit stores the logging data, it also stores a source attribute value and a reason attribute value of the logging data.

38. The system of claim 37, wherein the source attribute value is the original URI of the duplicated logging data.

39. The system of claim 37, wherein the reason attribute value is information for allowing a cause of the logging recognized, namely, a scheduling context ID.

40. The system of claim 31, wherein the logging sub-tree management unit determines a storage location of the logging data with reference to a value of the control part of the logging sub-tree.