Device Management Method Using Nodes Having Additional Attribute and Device Management Client Thereof

• US 20080201475A1
• Filed: 09/29/2006
• Published: 08/21/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 8,001,150 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/08 Configuration management of networks or network elements address allocation H04L61/50
• CPC Class Codes: H04L 51/234 for tracking messages
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network

Abstract

A device management (DM) method and a device management (DM) client use a node having an additional attribute. The DM client includes a node having a common attribute indicating attribute information that is common to every node and an additional attribute indicating attribute information of each node. The DM method includes: receiving a node generation command; and generating a node having a common attribute indicating attribute information that is common to every node and an additional attribute indicating attribute information of each node according to the node generation command.

Claims

1. A device management (DM) client, comprising:

a node including a common attribute and an additional attribute;

wherein the common attribute includes at least one field that is common to every node, and the additional attribute includes at least one field that is specified to each node.

2. The client of claim 1, wherein the field of the common attribute includes information on a type or a state of the additional attribute.

3. The client of claim 1, wherein if the node relates to log data, the field of the additional attribute includes information on the location of original data to be logged.

4. The client of claim 3, wherein the information is a URI (Uniform Resource Indicator) where the original data to be logged was located.

5. The client of claim 1, wherein if the node relates to log data, the field of the additional attribute includes information on a reason why the log data has been generated.

6. The client of claim 5, wherein if the log data has been generated according to a scheduling command, the field of the additional attribute includes a scheduling ID.

7. The client of claim 5, wherein if the log data has been generated according to a logging request of an external device, the filed of the additional attribute includes an ID of the logging request.

8. The client of claim 1, wherein if the node relates to an e-mail message, the field of the additional attribute includes information on whether a message object of the node has been read.

9. The client of claim 1, wherein if the node relates to the e-mail message, the filed of the additional attribute includes information on whether the message has been deleted.

10. The client of claim 1, wherein if the node relates to the e-mail message, the filed of the additional attribute includes information on whether the message is a newly received message.

11. The client of claim 1, wherein if the node relates to the e-mail message, the filed of the additional attribute includes information indicating that the message has been created but not sent yet.

12. The client of claim 1, wherein if the node relates to the e-mail message, the filed of the additional attribute includes information on whether a reply to the message has been sent.

13. A device management method comprising:

receiving a command for generating a node; and

generating a node including a common attribute and an additional attribute, according to the command;

wherein the common node includes at least one filed that is common to every node, and the additional attribute includes at least one filed that is specified to each node.

14. The method of claim 13, wherein the command comprises instructions to generate the common attribute having the filed, and the additional attribute having the filed.

15. The method of claim 13, wherein the filed of the common attribute includes information indicating a type and a state of the additional attribute.

16. The method of claim 13, wherein if the generated node relates to log data, the filed of the additional attribute includes information indicating the location of the original data to be logged.

17. The method of claim 13, wherein if the generated node relates to log data, the filed of the additional attribute includes information indicating a reason of the generation of the log data.

18. The method of claim 13, wherein if the generated node relates to an e-mail m essage, the filed of the additional attribute includes information indicating whether a message has been read.

19. The method of claim 13, wherein if the generated node relates to an e-mail message, the filed of the additional attribute includes information indicating whether the message has been deleted.

20. The method of claim 13, wherein if the generated node relates to an e-mail message, the filed of the additional attribute includes information indicating that the message is a newly received message.

21. The method of claim 13, wherein if the generated node relates to an e-mail message, the filed of the additional attribute includes information indicating that the message has been created but not sent yet.

22. The method of claim 13, wherein if the generated node relates to an e-mail message, the field of the additional attribute includes information indicating that a reply to the message has been sent in the additional attribute.

23. A device management(DM) client comprising:

a node including a common attribute and an additional attribute;

wherein, the common attribute includes at least one filed that is common to every node and the additional attribute includes at least one filed that relates to log information.

24. The client of claim 23, wherein the filed of the common attribute includes information indicating that the node relates to the log information.

25. The client of claim 23, wherein a first field of the additional attribute may be a ‘

DATASOURCE’

field indicating the location of original data to be logged and a second field of the additional attribute may be a ‘

REASON’

field indicating a reason of generation of the log data.

26. The client of claim 25, wherein when the node has been generated according to a logging request from outside, the ‘

REASON’

field includes an ID of the logging request.

27. The client of claim 25, wherein when the node has been generated according to a scheduling command, the ‘

REASON’

field includes a scheduling ID.

28. The client of claim 25, wherein the ‘

DATASOURCE’

field includes a URI where the original data to be logged was located.

29. A device management (DM) client comprising:

a node including a common attribute and an additional attribute;

wherein the common attribute includes at least one filed that is common to every node in the DM client and the additional attribute includes at least filed indicating a state of a received message.

30. The client of claim 29, wherein the filed of the common attribute includes information indicating that the node relates to an e-mail message.

31. The client of claim 29, wherein the filed of the additional attribute indicates whether the message has been read.

32. The client of claim 29, wherein the field of the additional attribute indicates whether the message has been deleted.

33. The client of claim 29, wherein the filed of the additional attribute indicates whether the message has been newly received.

34. The client of claim 29, wherein the filed of the additional attribute indicates that the message has been created but not sent yet.

35. The client of claim 29, wherein the filed of the additional attribute indicates whether a reply to the message has been sent.

36. A device management method in a mail server that communicates with a plurality of mail clients, comprising:

receiving a message from any mail client;

generating a message object node including an additional attribute which includes at least one field indicating a state of the received message; and

changing the field of the additional attribute according to a message processing request from the mail client and storing it.

37. The method of claim 36, further comprising:

performing initial synchronization when the mail client is connected with the mail server; and

providing information in the field of the additional attribute to the mail client.

38. The method of claim 36, wherein the filed of the additional attribute indicates whether the message has been read.

39. The method of claim 38, wherein the filed of the additional attribute is changed when the mail server receives a request for synchronizing the message from the mail client.

40. The method of claim 36, wherein the filed of the additional attribute indicates whether the message has been deleted.

41. The method of claim 40, wherein the filed of the attribute value is changed when the mail server receives a request for deleting the message from the mail client.

42. The method of claim 36, wherein the field of the additional attribute indicates whether the message is a newly received message.

43. The method of claim 42, wherein the field of the additional attribute is changed after the mail server informs the mail client about the reception of the message.

44. The method of claim 36, wherein the field of the additional attribute indicates that the message has been not sent to a recipient mail client.

45. The method of claim 44, wherein the filed of the additional attribute is changed when the mail server receives a request for storing the newly created message from the mail client.

46. The method of claim 36, wherein the field of the additional attribute indicates that a reply to the message has been sent.

47. The method of claim 46, wherein the field of the attribute value is changed when the mail server receives a request for sending the reply.

48. A device management client, comprising:

a node including at least one attribute with respect to log data for a management object.

49. The client of claim 48, wherein a value of the attribute is determined according to the log information, respectively.

50. The client of claim 48, wherein a first attribute with respect to the log data corresponds to ‘

DATASOURCE’

indicating a location of the original data to be logged and a second attribute with respect to the log data corresponds to ‘

REASON’

indicating a reason of the generation of the log data.

51. The client of claim 50, wherein when the node has been generated according to a logging request from outside, the ‘

REASON’

includes an ID of the logging request.

52. The client of claim 50, wherein when the node has been generated according to a scheduling command, the ‘

REASON’

includes a scheduling ID.

53. The client of claim 50, wherein the ‘

DATASOURCE’

includes a URI where the original data to be logged was located.

54. A device management client comprising:

a message object including at least one attribute with respect to a received message.

55. The client of claim 54, wherein the attribute indicates a state of a message object to which they belong, respectively.

56. The client of claim 54, wherein the attribute indicates whether a message has been read.

57. The client of claim 54, wherein the attribute indicates whether the message has been deleted.

58. The client of claim 54, wherein the attribute indicates whether the message has been newly received.

59. The client of claim 54, wherein the attribute indicates that the message has been created but not sent yet.

60. The client of claim 54, wherein the attribute indicates whether a reply to the message has been sent.