WO2007083973A1 - Terminal et procédé de gestion programmée d'un dispositif sur la base d'un seuil - Google Patents

Terminal et procédé de gestion programmée d'un dispositif sur la base d'un seuil Download PDF

Info

Publication number
WO2007083973A1
WO2007083973A1 PCT/KR2007/000379 KR2007000379W WO2007083973A1 WO 2007083973 A1 WO2007083973 A1 WO 2007083973A1 KR 2007000379 W KR2007000379 W KR 2007000379W WO 2007083973 A1 WO2007083973 A1 WO 2007083973A1
Authority
WO
WIPO (PCT)
Prior art keywords
threshold
terminal
specify
value
command
Prior art date
Application number
PCT/KR2007/000379
Other languages
English (en)
Inventor
Te-Hyun Kim
Pablo Hernandez
Original Assignee
Lg Electronics Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020070005822A external-priority patent/KR101342370B1/ko
Application filed by Lg Electronics Inc. filed Critical Lg Electronics Inc.
Priority to EP07708560.3A priority Critical patent/EP1977324B1/fr
Priority to CN2007800028823A priority patent/CN101371236B/zh
Priority to DK07708560.3T priority patent/DK1977324T3/da
Publication of WO2007083973A1 publication Critical patent/WO2007083973A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/02—Standardisation; Integration
    • H04L41/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources

Definitions

  • the present invention relates to a terminal and method for performing device management scheduled based on threshold thereof.
  • device management (DM) technology relates to showing (or indicating), to a device management (DM) server (or other network entity), the resources of a device management (DM) client (i.e., a terminal or other user device) as management objects that exist on a device management (DM) tree (or other type of hierarchy structure or logical format that is used for device management), allowing access thereto, and letting the DM server easily manage the terminal.
  • DM device management
  • the DM server may instruct the terminal to process commands for device management, while the terminal being managed, after immediately performing the corresponding command, may report the results thereof to the DM server. Also, the DM server may request the terminal to change, update, delete or otherwise process a particular function for device management.
  • One aspect of the present invention is the recognition by the present inventors of the following drawbacks in the related art DM technology. Namely, in the related art, the terminal may request the DM server for DM commands only when a value of a particular management object exceeds over a threshold and then an error or malfunction occurs within the terminal. As such, the diagnostic procedures of the related art terminal become more expensive, and do not allow effective resolution of diagnostic problems because such problems cannot be anticipated or discovered before they occur.
  • the present invention provides a terminal that receives, from the server, the scheduling context including device management scheduled based on threshold and performs the device management procedures according to the threshold.
  • the present invention provides a server that generates a scheduling context (or other type of scheduling information) that includes device management scheduled based on a threshold to allow more effective scheduling to be performed by the terminal.
  • Figure 1 shows exemplary conceptual structures of a server and a terminal according to the present invention.
  • Figure 2 shows the scheduling context as an exemplary device management tree structure according to the present invention.
  • Figure 3 shows the scheduling context as an another exemplary device management tree structure according to the present invention.
  • Figure 4 shows an exemplary flow chart of a scheduling context installation procedure according to the present invention.
  • Figure 5 shows a flow chart for an exemplary method for performing device management scheduling according to the present invention.
  • Figure 6 shows an exemplary method for performing a threshold-based device management scheduling procedure.
  • Figure 7 shows another exemplary method for performing a trap-based device management scheduling procedure.
  • the present invention provides a terminal with a first module (or other hardware, software, or a combination thereof) that samples a value of a specified management object in the terminal and compares the sampled value with a specified threshold; and a second module (or other hardware, software, or a combination thereof) that executes a device management command for the management object, if it is determined by the first module that the sampled value of the management object has reached the threshold.
  • a first module or other hardware, software, or a combination thereof
  • a second module or other hardware, software, or a combination thereof
  • the present invention also provides a terminal with a first module (or other hardware, software, or a combination thereof) that receives at least one or more scheduling contexts from a server, and installs 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 (or other hardware, software, or a combination thereof) that samples a value of a specified management object in the terminal and compares the sampled value with a specified threshold; and a third module (or other hardware, software, or a combination thereof) that executes a device management command for the management object, if it is determined by the first module that the sampled value of the management object has reached the threshold.
  • a first module or other hardware, software, or a combination thereof
  • the present invention also provides 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.
  • 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.
  • the present invention also provides a method for managing a device, comprising sampling a value of a specified management object; comparing the sampled value with a specified threshold; and executing a device management command for the management object, if it is determined that the value of the management object has reached the threshold.
  • Figure 1 shows exemplary conceptual structures of a server (i.e., a DM server) and a terminal (i.e., a DM client) according to the present invention
  • Figure 2 shows the scheduling context as an exemplary device management tree structure
  • Figure 3 shows the scheduling context as an another exemplary device management tree structure.
  • Figure 1 shows an exemplary DM server (100) and a terminal (100) according to the present invention.
  • the DM server (100) may include a DM scheduling enabler (110) or other similar hardware, software, or any combination thereof.
  • the DM scheduling enabler (110) may be comprised of a scheduling context management module (111) and a status reporting processing module (112) and/or other types of similar hardware, software, or any combination thereof.
  • the scheduling context management module (111) may have a unit (i.e., portion, element, etc. or a combination thereof) that generates a scheduling context and requests the terminal (200) to install and execute it.
  • the scheduling context management module (111) establishes a device management (DM) session (or some other type of communication term or period) with the terminal (200) according to a relative standard (such as DM standard) and then can request the terminal (200) to install the scheduling context via the established DM session.
  • DM device management
  • the scheduling context may include general information and one or more scheduling components as illustrated in Figure 2. Additional and/or alternative types of information, parameters, and the like may also be included.
  • the general information may include one or more of the following: an identifier element of the scheduling context, a name element, a corresponding server element, and a validity period element.
  • the scheduling component may include one or more of the following: a Task element that designates a DM command, and a Condition element that designates a condition(s) (i.e., reasons, factors, parameters, etc.) for executing the DM command.
  • a Task element that designates a DM command
  • a Condition element that designates a condition(s) (i.e., reasons, factors, parameters, etc.) for executing the DM command.
  • the elements are not limited to only those listed above, but different additional elements or only some of the listed elements may be used.
  • the command for the device management may be included in a message.
  • the message may include at least one or more commands for device management. If the message is used, the task element designates the message. And, the conditions above may be timer-based, trap-based, or threshold-based. Additional or alternative basis for the conditions may be used as well.
  • one or more scheduling components may exist within the scheduling context, and these scheduling components may have a binding logical relationship therebetween.
  • the scheduling components may be interworked.
  • this interworking may refer to when a module (or other entity) executes a command of a first schedule component if a condition of a first schedule is satisfied, and terminates a command of a second schedule component. This is particularly useful for threshold- based scheduling, whereby one or more components can be respectively executed in an alternating manner based upon a particular threshold value.
  • This concept of the interworking may be applied to the scheduling context. That is, if a first scheduling context of at least one or more scheduling context is started, a second scheduling context of the at least one or more scheduling context is stopped.
  • the scheduling context may be revised (i.e., corrected, adapted, modified, etc.) by the scheduling context management module (111) as necessary, or such revision may be requested to the terminal (200). Also, the scheduling context management module (111) may request the terminal (200) to delete the installed scheduling context.
  • the scheduling context management module (111) may receive a message (or other indication) from the terminal (200) and perform appropriate processing thereof.
  • the terminal (200) may comprise a DM scheduling enabler (210) and a DM enabler
  • the DM scheduling enabler (210) may be comprised of a scheduling context installation module (211), a condition matching module (212), a DM command executing module (213), and a status reporting module (214).
  • the scheduling context installation module (211) is a unit (i.e., portion, element, etc. or a combination thereof) that may receive a scheduling context installation request from the server (110) (i.e., the DM scheduling enabler (110)) and perform appropriate processing thereof.
  • the scheduling context may be received trough the DM enabler (220), then may be delivered to the scheduling context installation module (211).
  • the scheduling context installation module (211) uses the scheduling context to generate one or more nodes (or other types of hierarchy points) in a device management (DM) tree (or other type of hierarchy structure or logical format) that is used within the terminal (200).
  • DM device management
  • the DM tree may be formed of general information nodes and one or more schedule components (scheduled device management).
  • FIG. 2 An exemplary DM tree is shown in Figure 2.
  • the general information nodes may be comprised of an Id node indicating an identifier of the installed scheduling context, an Name node indicating a name of the scheduling context, an Valid node indicating a valid period of the scheduling context, and an Server node indicating the owner of the scheduling context. It can be clearly understood that the names and types of these nodes are merely exemplary.
  • the schedule component may be comprised of one or more of the following: an
  • Task node that indicates a DM command
  • Condition node that designates a condition (or circumstance) for performing the DM command.
  • Other types of additional or alternative nodes are possible.
  • the DM command is included in a message.
  • the Task node may designate the message including the DM command.
  • the condition may be threshold-based. Therefore, the Condition node includes a Th node that specifies a threshold-based condition.
  • the Th node includes at least one of a Address node to specify an address of the management object, a Interval node to specify an interval for monitoring the value for the management object, a Threshold node to specify the threshold, a ThFormat node to specify which a format of the threshold is of bool, character, integer, float, date, or time, a ThType node to specify whether a type of the threshold is absolute value or delta value, a Direction node to specify which the threshold is of rising, falling and static, and a Hysteresis node to specify a margin for the threshold.
  • the Address node includes at least one of a URI node to specify an uniform resource identifier (URI) of the management object, a MOI node to specify a the management object identifier (MOI), and a MOIfilter node to specify an additional in- formation for distinguishing the specified management object from other management objects due to a coexistence of management objects with same MOI if the MOI node is used.
  • URI uniform resource identifier
  • MOI management object identifier
  • MOIfilter node to specify an additional in- formation for distinguishing the specified management object from other management objects due to a coexistence of management objects with same MOI if the MOI node is used.
  • the URI node may specify a full address, if the MOI node is not present. However, if the MOI node is present, then the URI node may specify a relative address to the root of the management object.
  • the MOIfilter node includes at least one of a URI node, a Value node, and a Format node.
  • the URI node included in the MOIfilter node specifies a uniform resource identifier
  • the Value node included in the MOIfilter node specifies a value to be compared with a value of the specified management object indicated by the URI node of the MOIfilter node, in order to distinguish the specified management object from other management objects in case there are more than one management object with the same management object identifier (MOI).
  • the value in the Value node can be compared with the value of the URI, if the URI node included in the MOIfilter node is present. However, if the URI node included in the MOIfilter node is not present, then the value in Value node can be compared with the root name of the management object.
  • the Format node included in the MOIfilter node specifies a format of the value in the Value node.
  • the possible values are b64, bin, bool, int, xml, date, time, or float. If the Format node is not present, then the format of the Value node would be considered as character.
  • the Threshold node specifies the threshold, and a value of the
  • Threshold node is the numeric text string representing the various formats of the threshold value.
  • the actual format of the threshold is determined by the ThFormat node.
  • the sample statistics of the selected management object will be compared with the value of the Threshold node. But, if the currently sampled value is the first one (e.g. after power recycles, the Scheduling Operation is just started), and if there is no previous sample, the last sample is not taken into account.
  • this threshold is the rising-threshold, a single condition match occurs if the currently sampled value is greater than or equal to this threshold, and if the last sample was less than this threshold.
  • this threshold is the falling-threshold, condition match occurs in the opposite direction.
  • this threshold is set to the static-threshold
  • a single condition match event occurs when the current sample value is equal to this threshold irrespective of the crossing, and if the last sample was not equal to this threshold. But the logical status of the condition will be true as long as the sampled value is equal to this threshold. If the hysteresis is specified, after a threshold crossing event is generated, another one will not be generated until the sampled value falls below or rises above this threshold by the margin specified by the hysteresis.
  • the ThFormat node specifies the real format of the threshold and the hysteresis.
  • ThFormat node Possible values of the ThFormat node are, bool, chr, int, date, time, or float.
  • the ThType node specifies the threshold type. Possible values of the ThType node are absolute or delta. If the value is Absolute, the sampled value of the management object will be compared directly with the threshold. If the value is Delta, the sampled value at the last sampling will be subtracted from the currently sampled value, and the difference will be compared with the threshold.
  • the Direction node specifies the behavior of the value changes as the threshold crossing event occurs. Possible values are rising ,falling or static.
  • the static-threshold means that the condition match occurs when the sampled value is equal to the threshold irrespective of the direction of the crossing.
  • the Hysteresis node specifies a value of the hysteresis.
  • the value of the Hysteresis node is the text string representing the various formats of the hysteresis value.
  • the real format of the hysteresis value is determined by the ThFormat node. Using hysteresis prevents too many threshold crossing events from being generated if the sample valued fluctuates around the threshold due to noise. For example, in case of rising-threshold, once the command is executed, it will not be executed again, unless the sampled value becomes less than the threshold by the margin specified by this node.
  • the scheduling context installation module (211) may selectively check the validity (or authenticity) of the scheduling context, if necessary.
  • the condition matching module (212) is a unit (i.e., portion, element, etc. or a combination thereof) that monitors or checks whether there is a matching of threshold- based conditions in the schedule component for execution.
  • the Threshold-based condition designates whether a value of a particular management object within the terminal (200) reaches a previously set threshold value. Accordingly, the condition matching module (212) monitors (or checks) the value of the particular management object, compares such with the threshold value, and when the threshold value is reached, then a request to the DM command executing module (213) to execute the DM command corresponding to the condition can be made.
  • condition matching module (212) that performs the above procedure, one or more schedule components (i.e., a device management function or procedure that has been scheduled) exist, and if each respective schedule component contains conditions for executing the threshold-based procedure with respect to the same particular management entity, the conditions for executing the threshold-based procedure can be interworked with respect to the particular management entity and can also be monitored.
  • schedule components i.e., a device management function or procedure that has been scheduled
  • a first schedule component i.e., device management that has been scheduled
  • a second schedule component i.e., device management that has been scheduled
  • the first schedule component includes a first DM command and conditions for executing a first threshold-based procedure with respect to a particular management entity
  • the second schedule component includes a second DM command and conditions for executing a second threshold-based procedure with respect to the same particular management entity. If so, when the value of the particular management entity satisfies the conditions for executing the first threshold- based procedure, the condition matching module (212) requests to the DM command executing module (213) to execute the first DM command. Also, when the value of the particular management entity satisfies the conditions for executing the second threshold-based procedure, the condition matching module (212) requests to the DM command executing module (213) to execute the second DM command.
  • the DM command executing module (213) is a unit (i.e., portion, element, etc. or a combination thereof) that cooperates with the DM enabler (220) to execute the DM command if there is a matching of the conditions for executing the DM command.
  • the DM command executing module (213) sends the DM command to the DM enabler (220), and receives a result obtained by executing the DM command from the DM enabler (220).
  • the status reporting module (214) is a unit that reports to the DM server (100) about the state of the terminal (22) or about results obtained from executing the command.
  • the status reporting module (214) uses the DM command execution results (i.e., a Status message, a Result message, or an Alert message) to generate a report message, which can be sent to the DM server (100).
  • the report message or the state of the terminal (200) can be transmitted to the DM server (100) by using a Generic Alert Message or by some other type of message or indication.
  • the status reporting module (214) may report to the DM server (100) when the state of the scheduling context or the state of the scheduling component changes.
  • the DM enabler client (220) is a unit that cooperates with the command execution module (214) to execute the DM commands.
  • the DM enabler client (220) executes a DM command received from the command execution module (214), and then the results thereof is returned back (i.e. reported) to the command execution module (214).
  • DM server having a scheduling context management module (111) and a status reporting processing module (112), and a terminal (200) having a DM scheduling enabler (210) (containing a scheduling context installation module (211), a condition matching module (212), a DM command executing module (213), and a status reporting module (214)), and a DM enabler (220).
  • these elements may also be implemented as any combination of a processor (not shown), a network interface (not shown), and a storage device (not shown).
  • Figure 4 is a flow chart showing a scheduling context installing procedure according to the present invention
  • Figure 5 is a flow chart showing a method for performing a scheduled device management according to the present invention.
  • the DM server (100) in the installing procedure of the present invention, establishes a DM session (or some other type of communication link) with the DM enabler (220), and the scheduling context is installed.
  • the DM server (100) establishes a DM session with the terminal (200), and uses the DM protocol (or other appropriate communications protocol) to deliver a request (or instruction) to install the generated scheduling context to the DM scheduling enabler client (210) of the terminal (200).
  • the request can be delivered through the DM enabler (220) to the DM scheduling enabler client (210).
  • the DM scheduling enabler (210) of the terminal (200) (in particular, the scheduling context installation module (211) thereof) checks the validity of the scheduling context.
  • the DM scheduling enabler (210) of the terminal (200) (in particular, the scheduling context installation module (211) thereof) installs the scheduling context in the DM tree (or other type of hierarchy structure or logical format) of the terminal (200).
  • the DM scheduling enabler (210) of the terminal (200) (in particular, the scheduling context installation module (211) thereof) reports the results of the scheduling context installation to the DM server (100).
  • the DM scheduling enabler (210) (in particular, the status reporting module (214) thereof) reports the execution results or the state of the terminal (200) to the DM server (100). Namely, the report of the execution results may inform the DM server (100) about whether the DM command was properly performed, or the reason(s) why an error has occurred. Such reporting procedure may use the execution results to create a report message (or some other type of indication), which may then be sent to the DM server (100).
  • the DM server (100) Upon receiving the status report, the DM server (100) (in particular, the status reporting processing module (120) thereof) performs parsing (or other processing) on the received status report.
  • Figure 6 shows an exemplary method for performing threshold-based device management scheduling
  • Figure 7 shows an exemplary method for performing trap-based device management scheduling.
  • the scheduling context may be comprised of two schedule components.
  • the first schedule component i.e., scheduled device management
  • the second schedule component of the scheduling context allows execution of a DM command that changes the variable bar to foo, if the value of a particular management entity goes back to a stable state.
  • the first and second schedule components may ignore the situations where the throughput of a particular radio interface exceeds threshold 1 but then again falls below threshold 1, if such difference is considered to he relatively small (i.e., if within the hysteresis (allowed) range). This is to exclude the causes for system instability due to the effects of noise (or other interference).
  • An exemplary execution procedure of the first and second components will be described. [82] (1) The first component and the second component change from an initial state to an active (or enabled) and are executed. [83] (2) If the throughput of a particular radio (wireless) interface device exceeds threshold 1, the DM command of the first schedule component is executed.
  • FIG. 7 shows a scheduling context that comprises two schedule components (i.e., scheduled device management).
  • the first schedule component of the scheduling context allows the terminal operation mode to be set to emergency mode when a particular event 1 occurs, and executes a second schedule component.
  • the second schedule component of the scheduling context periodically checks whether there is an abnormal state, and if the abnormal state is removed (or resolved), the terminal is allowed to return to its normal mode from the emergency mode.
  • An exemplary execution procedure of the first and second schedule component is as follows. [89] (1) When the scheduling context is installed, the second component changes from its initial state to an inactive (or disable) state, the first schedule component changes from its initial state to an active or enabled state and is executed. [90] (2) When the particular event 1 occurs, the DM command of the first schedule component is executed. [91] (3) Upon execution of the DM command, the terminal operation mode changes to emergency mode, the first schedule component becomes inactive (or disabled), and the second schedule component becomes active (or enabled).
  • the second schedule component checks whether the state of the terminal is normal, whereby this checking is performed in a periodic manner, such as every 10 minutes. [93] (5) Upon this periodic checking, if the state of the terminal is found to be normal, the DM command of the second component is executed. [94] (6) When the DM command executed, the terminal operation mode changes from emergency mode to normal mode, the second schedule component is disabled, and the first schedule component is enabled.
  • the method of the present invention may be implemented as software, hardware, or any combination thereof.
  • the method of the present invention may be implemented as codes or instructions within a software program that is stored in a storage medium (e.g., an internal memory of the terminal, a Flash memory, a hard disk, etc.) and executed by a processor (e.g., a microprocessor within the terminal, etc.).
  • a storage medium e.g., an internal memory of the terminal, a Flash memory, a hard disk, etc.
  • a processor e.g., a microprocessor within the terminal, etc.
  • the DM commands may be executed a more systematic manner and thus handled more effectively.
  • example embodiment means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention.
  • the appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des commandes de gestion d'un dispositif devant être exécutées dans un terminal ainsi que des conditions basées sur un seuil pour l'exécution de ces commandes, comprises dans un contexte de programmation, sont préalablement fournies au terminal. Le terminal peut ainsi exécuter les commandes pour la gestion du dispositif avant que des erreurs se produisent dans le terminal, lorsque valeur d'un objet de gestion particulier atteint le seuil.
PCT/KR2007/000379 2006-01-23 2007-01-22 Terminal et procédé de gestion programmée d'un dispositif sur la base d'un seuil WO2007083973A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP07708560.3A EP1977324B1 (fr) 2006-01-23 2007-01-22 Terminal et procédé de gestion programmée d'un dispositif sur la base d'un seuil
CN2007800028823A CN101371236B (zh) 2006-01-23 2007-01-22 用于执行基于门限值调度的设备管理的终端和方法
DK07708560.3T DK1977324T3 (da) 2006-01-23 2007-01-22 Terminal og fremgangsmåde til at gennemføre programmeret styring af en indretning på basis af en tærskelværdi

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US76094206P 2006-01-23 2006-01-23
US60/760,942 2006-01-23
US76251706P 2006-01-27 2006-01-27
US60/762,517 2006-01-27
KR10-2006-0043155 2006-05-12
KR20060043155 2006-05-12
KR10-2007-0005822 2007-01-18
KR1020070005822A KR101342370B1 (ko) 2006-01-23 2007-01-18 단말 및 그 단말에서의 임계-값 기반으로 장치관리를수행하는 방법

Publications (1)

Publication Number Publication Date
WO2007083973A1 true WO2007083973A1 (fr) 2007-07-26

Family

ID=38287857

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2007/000379 WO2007083973A1 (fr) 2006-01-23 2007-01-22 Terminal et procédé de gestion programmée d'un dispositif sur la base d'un seuil

Country Status (1)

Country Link
WO (1) WO2007083973A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000038033A2 (fr) * 1998-12-22 2000-06-29 Computer Associates Think, Inc. Systeme de planification et de commande de processus informatiques
US20030204640A1 (en) * 2002-04-30 2003-10-30 Nokia Corporation Method and device for management of tree data exchange
JP2005234736A (ja) * 2004-02-18 2005-09-02 Fuji Xerox Co Ltd スケジュール管理プログラム、スケジュール管理方法、スケジュール管理装置
US20050216222A1 (en) * 2004-03-29 2005-09-29 Sony Computer Entertainment Inc. Methods and apparatus for achieving thermal management using processing task scheduling

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000038033A2 (fr) * 1998-12-22 2000-06-29 Computer Associates Think, Inc. Systeme de planification et de commande de processus informatiques
US20030204640A1 (en) * 2002-04-30 2003-10-30 Nokia Corporation Method and device for management of tree data exchange
JP2005234736A (ja) * 2004-02-18 2005-09-02 Fuji Xerox Co Ltd スケジュール管理プログラム、スケジュール管理方法、スケジュール管理装置
US20050216222A1 (en) * 2004-03-29 2005-09-29 Sony Computer Entertainment Inc. Methods and apparatus for achieving thermal management using processing task scheduling

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1977324A4 *

Similar Documents

Publication Publication Date Title
EP1977324B1 (fr) Terminal et procédé de gestion programmée d'un dispositif sur la base d'un seuil
US8490100B2 (en) Terminal and method for performing device management scheduled based on threshold
US8161150B2 (en) Device management system and device management command scheduling method thereof
KR101474413B1 (ko) 스케줄링된 장치관리를 수행하는 단말 및 방법
EP1766866B1 (fr) Programmation de commande de gestion de dispositif de réseau
US9385916B2 (en) Device management scheduling based on trap mechanism
US20080071651A1 (en) Asynchronous events in meta-data driven instrumentation
WO2007083954A1 (fr) Procédé de programmation de la gestion d'un dispositif et terminal associé
CN110505219B (zh) 基于dubbo的微服务服务注册控制管理系统及方法
WO2007083973A1 (fr) Terminal et procédé de gestion programmée d'un dispositif sur la base d'un seuil
CN101371236B (zh) 用于执行基于门限值调度的设备管理的终端和方法
CN108769260B (zh) 一种集群升级过程中事件处理方法及其装置
RU2337489C1 (ru) Система управления устройствами и ее способ планирования команд управления устройствами
MX2008009282A (en) Terminal and method for performing device management scheduled based on threshold
US20030131080A1 (en) Method for updating a database
CN116185570A (zh) 一种基于kubernetes的实例状态管理方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2781/KOLNP/2008

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: MX/a/2008/009282

Country of ref document: MX

WWE Wipo information: entry into national phase

Ref document number: 200780002882.3

Country of ref document: CN

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2007708560

Country of ref document: EP