Device management scheduling based on trap mechanism

• US 20070174447A1
• Filed: 01/24/2007
• Published: 07/26/2007
• Est. Priority Date: 01/25/2006
• Status: Active Grant

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: Kim, Te-Hyun, Hernandez, Pablo
• Granted Patent: US 9,021,488 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: G06F 15/173 using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/064 involving time analysis
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 67/01 Protocols

Abstract

Performing device management scheduling based upon a trap mechanism is provided. A scheduling context, upon receipt from a server, is installed. The scheduling context may have at least one of a first element specifying information including at least one command for device management and a second element specifying a trap-based condition to execute the command. The command in the message specified by the first element is executed, if an occurrence of a particular event specified by the second element is found.

Claims

1. A terminal, comprising:

a first entity adapted to install, upon receipt from a server, a scheduling context,

wherein the scheduling context comprises at least one of a first element which specifies information including at least one command for device management, and a second element which specifies a trap-based condition to execute the command; and

a second entity adapted to execute the command in the information specified by the first element, if a particular event specified by the second element occurs.

2. The terminal of claim 1, wherein

the first element corresponds to a task element, or the second element corresponds to a trap element.

3. The terminal of claim 1, wherein the second element comprises

a identifier element which specifies an identifier to the particular event.

4. The terminal of claim 1, wherein the second element further specifies

a timer-based condition to execute the command.

5. The terminal of claim 4, wherein the second element further comprises

a base element which specifies a predetermined time.

6. The terminal of claim 4, wherein the second element further comprises

a recursive rule element which specifies whether the condition should be recursive or not.

7. The terminal of claim 1, wherein

the particular event occurs if an arrival at a predetermined time is found.

8. The terminal of claim 1, wherein

the particular event occurs if it is found that a value of a particular management object in the terminal crosses a predetermined threshold value.

9. The terminal of claim 1, further comprising:

a event monitoring module adapted to monitor whether the particular event occurs and to inform to the second entity so that the second entity can execute the command.

10. The terminal of claim 1, wherein the second entity comprises:

a first module adapted to execute the command when an occurrence of the particular event is acquired;

a second module adapted to determine whether to report a result from executing the command to the server; and

a third module to report at least one of the result determined to be reported by the second module and a state of the scheduling context.

11. A server, comprising:

a first entity adapted to generate a scheduling context and to request an installation of the scheduling context to a terminal;

wherein the scheduling context comprises at least one of a first element which specifies information including at least one command for device management, and a second element which specifies a trap-based condition to execute the command, the second element including an identifier of a particular event so that the terminal can execute the command if the particular event corresponding to the identifier occurs; and

a second entity adapted to receive a result obtained from executing the command from the terminal.

12. The server of claim 11, wherein

the first element corresponds to a task element, or the second element corresponds to a trap element.

13. The server of claim 11, wherein

the particular event may occur if an arrival at a predetermined time is found, or if it is found that a value of a particular management object in the terminal crosses a predetermined threshold.

14. The server of claim 11, wherein the second element further specifies

a timer-based condition to execute the command.

15. The server of claim 14, wherein the second element further comprises

a base element which specifies a predetermined time.

16. The server of claim 14, wherein the second element further comprises

a recursive rule element which specifies whether the condition should be recursive or not.

17. A method for performing device management scheduled based on a trap mechanism, the method comprising:

installing, upon receipt from a server, a scheduling context comprising at least one of a first element which specifies information including at least one command for device management, and a second element which specifies a trap-based condition to execute the command;

wherein the second element includes an identifier of a particular event, and

executing the command in the information specified by the first element if an occurrence of the particular event corresponding to the identifier is found.

18. The method of claim 17, wherein

the particular event occurs if an arrival at a predetermined time is found.

19. The method of claim 17, wherein

the particular event occurs if it is found that a value of a particular management object in the terminal crosses a predetermined threshold value.

20. The method of claim 17, wherein the executing step comprises:

monitoring whether or not the particular event occurs; and

executing the command if an occurrence of the particular event is found.

21. The method of claim 17, wherein the installing step comprises:

requesting, by a DM scheduling enabler of the terminal, an event monitoring module of the terminal to inform about whether the particular event has occurred or not; and

requesting, by the event monitoring module of the terminal, a management object of the terminal to inform about whether the particular event has occurred or not.

22. The method of claim 20, wherein the monitoring step comprises:

transmitting, by the management object of the terminal, a message to the event monitoring module of the terminal informing the occurrence of the particular event; and

transmitting, by the event monitoring module, a message to the DM scheduling enabler informing the occurrence of the particular event.