Performing scheduled device management

• US 20070192158A1
• Filed: 01/22/2007
• Published: 08/16/2007
• Est. Priority Date: 01/23/2006
• Status: Abandoned Application

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: Kim, Te-Hyun
• Application Number:
  US11/655,851
• Publication Number:
  US 20070192158A1
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: G06F 9/4843 by program, e.g. task dispatcher, supervisor, operating system
• CPC Class Codes: H04L 12/2823 Reporting information sensed by appliance or service execution status of appliance services in a home automation network device-related reporting H04L43/065; arrangements in telecontrol or telemetry systems for selectively calling a substation from a main station, in which substation desired apparatus is selected for applying a control signal thereto or for obtaining measured values therefrom H04Q9/00
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor
• CPC Class Codes: H04L 41/0681 Configuration of triggering conditions
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network

Abstract

For performing scheduled device management, a server generates a scheduling context that includes commands for device management and generates a device management object that includes a schedule for executing such commands, and transmits these to a terminal. The terminal monitors the schedule included in the management object, and according to the schedule, executed the commands within the scheduling context.

Claims

1. A terminal comprising:

a first entity adapted to identify a first management object through an address or an identifier of the first management object, and to monitor whether it is on a schedule included in the identified first management object;

wherein the address or the identifier is specified in a second management object; and

a second entity adapted to execute a command for device management included in a scheduling context, if it is determined by the first entity that it is on the schedule.

2. The terminal of claim 1, wherein

the schedule comprises at least one of a timer-based condition, a trap-based condition, and a threshold-based condition.

3. The terminal of claim 1, wherein

at least one of the first management object, the second management object, and the scheduling context is received from a server.

4. The terminal of claim 1, wherein

at least one of the first management object, the second management object, and the scheduling context is stored in a device management tree in the terminal.

5. The terminal of claim 1, wherein

the second management object includes a schedule reference node specifying the address or the identifier of the first management object.

6. The terminal of claim 1, wherein

the first management object corresponds to a schedule management object, and

the second management object corresponds to a diagnose management object.

7. A terminal comprising

a first entity adapted to monitor whether it is on a schedule included in a management object;

and

a second entity adapted to execute a command for device management included in a scheduling context, if it is determined by the first entity that it is on the schedule.

8. The terminal of claim 7, wherein

at least one of the management object, and the scheduling context is received from a server.

9. The terminal of claim 7, wherein

the management object includes a diagnose monitoring configuration node that includes the schedule.

10. The terminal of claim 7, wherein

the management object and the scheduling context is connected to each other through an address.

11. The terminal of claim 7, wherein

the schedule includes at least one of a timer-based condition, a trap-based condition, and a threshold-based condition.

12. The terminal of claim 7, wherein

the schedule includes a threshold-based condition.

13. The terminal of claim 12, wherein

the scheduling context further includes at least one of a timer-based condition, and a trap-based condition.

14. The terminal of claim 13, wherein

the first entity generates an event if the threshold-based condition is satisfied, and

the second entity determines whether the generated event satisfies the trap-based condition, and if so, executes the command.

15. The terminal of claim 7, wherein

the scheduling context includes a node which specifies an address or identifier of the management object.

16. A terminal, comprising:

a first entity adapted to monitor whether a threshold-based condition is satisfied or not, according to a first schedule management object including the threshold-based condition;

a second entity adapted to monitor whether a timer-based condition is satisfied or not, according to a second schedule management object including the timer-based condition; and

a third entity adapted to execute a command for device management included in a scheduling context if at least one of the threshold-based condition and the timer-based condition is satisfied.

17. The terminal of claim 16, wherein

at least one of the first schedule management object and the second schedule management object further includes a trap-based condition.

18. The terminal of claim 16, wherein

the scheduling context further includes a node which specifies an address or identifier of the diagnose management object.

19. A terminal, comprising:

a transceiver for receiving from a server at least one of a scheduling context including at least one command for device management, a schedule management object including a schedule for executing the command, and a diagnose management object; and

a processor for installing at least one of the scheduling context, the schedule management object, and the diagnose management object in a device management tree.

20. The terminal of claim 19, wherein

the processor monitors the schedule of the schedule management object through an address of the schedule management object which is specified in the diagnose management object, and executes the command for device management.

21. A terminal, comprising:

a transceiver for receiving from a server at least one of a scheduling context which includes at least one command for device management, and a diagnose management object which includes a schedule for executing the command, and; and

a processor for installing at least one of the scheduling context, and the diagnose management object in a device management tree.

22. The terminal of claim 21, wherein

the processor monitors the schedule of the diagnose management object, and executes the command for device management.

23. The terminal of claim 21, wherein

the schedule includes at least one of a timer-based condition, a trap-based condition, and a threshold-based condition.

24. The terminal of claim 21, wherein

the schedule includes a threshold-based condition.

25. The terminal of claim 24, wherein

the schedule further includes at least one of a timer-based condition, and a trap-based condition.

26. A terminal, comprising:

a transceiver for receiving from a server at least one of a first schedule management object including a timer-based condition, a second schedule management object including a threshold-based condition, and a scheduling context including at least one command for device management; and

a processor for installing at least one of the first schedule management object, the second schedule management object, and the scheduling context in a device management tree.

27. A method for performing scheduled device management by a terminal, the method comprising:

monitoring whether it is on a schedule according to a diagnose management object; and

executing a command for device management included in a scheduling context if it is on the schedule as a result of the monitoring.