Terminal and method for performing device management scheduled based on threshold

Information

  • Patent Application
  • 20070174444
  • Publication Number
    20070174444
  • Date Filed
    January 22, 2007
    18 years ago
  • Date Published
    July 26, 2007
    18 years ago
Abstract
Commands for device management to be executed within a terminal and threshold-based conditions for executing such commands included within a scheduling context are provided to the terminal ahead of time. Therefore, the terminal can perform the commands for device management, before errors occurs within the terminal since a value of a particular management object reaches the threshold.
Description

BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 shows exemplary conceptual structures of a server and a terminal according to the present invention.



FIG. 2 shows the scheduling context as an exemplary device management tree structure according to the present invention.



FIG. 3 shows the scheduling context as an another exemplary device management tree structure according to the present invention.



FIG. 4 shows an exemplary flow chart of a scheduling context installation procedure according to the present invention.



FIG. 5 shows a flow chart for an exemplary method for performing device management scheduling according to the present invention.



FIG. 6 shows an exemplary method for performing a threshold-based device management scheduling procedure.



FIG. 7 shows another exemplary method for performing a trap-based device management scheduling procedure.


Claims
  • 1. A terminal, comprising: a first module adapted to receive at least one or more scheduling contexts from a server, and to install the at least one or more scheduling contexts, wherein each scheduling context includes a command and a threshold-based condition to execute the command;a second module adapted to sample a value of a specified management object in the terminal, and to compare the sampled value with the threshold; anda third module adapted to execute a device management command for the management object, if it is determined by the second module that the sampled value of the management object has reached the threshold.
  • 2. The terminal of claim 1, wherein the second module samples each value for one or more specified management objects in the terminal and compares each value with each specified threshold.
  • 3. The terminal of claim 1, wherein the sampled value and the threshold are related to each other in a one-to-one, one-to-multi, or multi-to-multi manner.
  • 4. The terminal of claim 1, wherein the second module uses an address or an identifier of the management object to sample the value.
  • 5. The terminal of claim 4, wherein the address is represented with at least one of an absolute location and a relative location.
  • 6. The terminal of claim 4, wherein the second module further uses additional information if the identifier is used.
  • 7. The terminal of claim 6, wherein the additional information includes at least one of a relative location and a value of the management object.
  • 8. The terminal of claim 1, wherein the second module monitors the value at specified intervals.
  • 9. The terminal of claim 1, wherein the second module further compares the sampled value with a previously sampled value.
  • 10. The terminal of claim 9, wherein the previously sampled value is ignored if the previously sampled value corresponds to one before rebooting.
  • 11. The terminal of claim 1, wherein the third module executes the command, if the currently sampled value is equal to or greater than the threshold and if a previously sampled value was less than the threshold.
  • 12. The terminal of claim 1, wherein the third module executes the command, if the currently sampled value is equal to or less than the threshold and if a previously sampled value was greater than the threshold.
  • 13. The terminal of claim 1, wherein the third module can not execute the command after executing once the command, until the sampled value falls below or rises by a specified margin for the threshold.
  • 14. The terminal of claim 1, wherein the third module executes the command, if the currently sampled value is equal to the threshold and if a previously sampled value was not equal to the threshold.
  • 15. The terminal of claim 1, wherein the second module compares a difference between the sampled value and a previously sampled value with the threshold, if the threshold is specified as delta.
  • 16. The terminal of claim 1, wherein the condition includes at least one of: a first element to specify an address of the management object;a second element to specify an interval for sampling the value for the management object;a third element to specify the threshold;a fourth element to specify a format of the threshold as a bool, character, integer, float, date, or time;a fifth element to specify a type of the threshold as an absolute value or a delta value;a sixth element to specify the threshold as rising, falling, or static; anda seventh element to specify a margin for the threshold.
  • 17. The terminal of claim 16, wherein the first element includes at least one of: a first sub-element to specify a uniform resource identifier of the management object;a second sub-element to specify an identifier of the management object; anda third sub-element to specify additional information for distinguishing a particular management object from other management objects due to an existence of same identifiers if the second sub-element is used.
  • 18. The terminal of claim 17, wherein the third sub-element includes at least one of: a URI of the management object that is relative to a root node of the device management tree;a value of the management object; anda format of the value.
  • 19. The terminal of claim 1, wherein the at least one or more scheduling contexts may interwork each other by the threshold.
  • 20. The terminal of claim 1, wherein the third module executes a command of a first scheduling context of the at least one or more scheduling contexts if a condition of the first scheduling context is satisfied, and executes a command of a second scheduling context t of the at least one or more scheduling contexts if a condition of the second scheduling context is satisfied.
  • 21. A terminal, comprising a first module adapted to receive from a server at least one or more scheduling contexts, each of which comprises a command and a threshold-based condition to execute the command, and to install the at least one or more scheduling contexts; wherein the condition includes at least one of a first element to specify an address of the particular management object, a second element to specify an interval for sampling the value of the particular management object, a third element to specify a threshold, a fourth element to specify a type of the threshold, a fifth element to specify a direction of the threshold, and a sixth element to specify a margin for the threshold, anda second module adapted to execute the command for the management object, if it is determined that a value of the particular management object has reached the threshold.
  • 22. The terminal of claim 21, wherein the fourth element specifies the type of the threshold as an absolute value or a delta value.
  • 23. The terminal of claim 21, wherein the condition further comprises a seventh element to specify a format of the threshold as a bool, character, integer, float, date, or time.
  • 24. A server, comprising: a DM scheduling enabler which creates at least one or more scheduling contexts and requests an installation of the at least one or more scheduling contexts to a terminal so that the terminal can perform device management according to the at least one or more scheduling contexts,wherein each scheduling context includes a command and a threshold-based condition to execute the command.
  • 25. The terminal of claim 24, wherein the condition includes at least one of: a first element to specify an address of the management object;a second element to specify an interval for monitoring the value for the management object;a third element to specify the threshold;a fourth element to specify a format of the threshold as a bool, character, integer, float, date, or time;a fifth element to specify a type of the threshold as an absolute value or a delta value;a sixth element to specify the threshold as rising, falling, or static; anda seventh element to specify a margin for the threshold.
  • 26. A method for managing a device, comprising sampling a value of a specified management object;comparing the sampled value with a specified threshold; andexecuting a device management command for the management object, if it is determined that the value of the management object has reached the threshold.
  • 27. The method of claim 26, further comprising receiving at least one or more scheduling contexts from a server, wherein each scheduling context includes a command and a threshold-based condition to execute the command; andinstalling the received scheduling context.
  • 28. The method of claim 27, wherein the condition includes at least one of: a first element to specify an address of the management object;a second element to specify an interval for monitoring the value for the management object;a third element to specify the threshold;a fourth element to specify a format of the threshold as a bool, character, integer, float, date, or time;a fifth element to specify a type of the threshold as an absolute value or a delta value;a sixth element to specify the threshold as rising, falling, or static; anda seventh element to specify a margin for the threshold.
Priority Claims (3)
Number Date Country Kind
10-2006-0043155 May 2006 KR national
10-2007-0005821 Jan 2007 KR national
10-2007-0005822 Jan 2007 KR national
Provisional Applications (2)
Number Date Country
60760942 Jan 2006 US
60762517 Jan 2006 US