CN101371236A - Terminal and method for performing device management scheduled based on threshold - Google Patents
Terminal and method for performing device management scheduled based on threshold Download PDFInfo
- Publication number
- CN101371236A CN101371236A CNA2007800028823A CN200780002882A CN101371236A CN 101371236 A CN101371236 A CN 101371236A CN A2007800028823 A CNA2007800028823 A CN A2007800028823A CN 200780002882 A CN200780002882 A CN 200780002882A CN 101371236 A CN101371236 A CN 101371236A
- Authority
- CN
- China
- Prior art keywords
- value
- threshold value
- terminal
- key element
- management object
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Images
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
Technical field
The present invention relates to be used to carry out the terminal and the method for the equipment control of dispatching based on its threshold value.
Background technology
Usually, equipment control (DM) technology relates to equipment control (DM) server (or other network entities) and shows that (or indication) is as in equipment control (DM) tree (the perhaps hierarchical structure of other types, the logical format that perhaps is used for equipment control) client (promptly to go up the equipment control as management object (DM) that exists, terminal or other subscriber equipmenies) resource, allow these resources of visit, and make the manageable described terminal of described DM server.
In this DM technology, the DM server can the administration order of indicating terminal actuating equipment, and the terminal of just being managed can be reported its result to described DM server after carrying out corresponding order immediately.And described DM server can be asked described terminal to change, upgrade, delete or otherwise be handled the specific function that is used for equipment control.
Summary of the invention
One aspect of the present invention is the following shortcoming that the present inventor recognizes the DM technology of prior art.That is, in the prior art, have only when the value of specific management object then can produce mistake or fault above threshold value in terminal, terminal just can be ordered to DM server requests DM.Therefore, the diagnostic procedure of the terminal of prior art is may be more expensive, and can not effectively solve diagnosis problem because before this problem takes place unpredictable to or find this problem.
Therefore, in order to overcome above-mentioned shortcoming, the invention provides a kind of terminal, this terminal receives the scheduling context (scheduling context) that comprises based on the equipment control of threshold value scheduling from server, and according to described threshold value actuating equipment management process.
In addition, the invention provides a kind of server, this server generates the scheduling context (the perhaps schedule information of other types) that comprises based on the equipment control of threshold value scheduling, so that terminal can be carried out more effective scheduling.
Description of drawings
Fig. 1 shows the exemplary concepts structure according to server of the present invention and terminal.
Fig. 2 shows according to the scheduling context as exemplary equipment control tree construction of the present invention.
Fig. 3 shows according to the scheduling context as another exemplary equipment control tree construction of the present invention.
Fig. 4 shows the exemplary process diagram that scheduling context according to the present invention is written into process.
Fig. 5 shows the process flow diagram that is used for the illustrative methods of actuating equipment management and dispatching according to of the present invention.
Fig. 6 shows the illustrative methods that is used to carry out based on the device management scheduling process of threshold value.
Fig. 7 shows another illustrative methods that is used for carrying out based on the device management scheduling process of trapping (trap).
Embodiment
The invention provides a kind of terminal, this terminal has: first module (perhaps other hardware, software or its combination), and the value that its value to the regulation management object in the described terminal is sampled and will be sampled is compared with the threshold value of regulation; With second module (perhaps other hardware, software or its combination), when its value in the sampling of the definite management object of described first module has reached described threshold value, at the administration order of described management object actuating equipment.
The present invention also provides a kind of terminal, this terminal has: first module (perhaps other hardware, software or its combination), it receives one or more scheduling context at least from server, and be written into described at least one or a plurality of scheduling context, wherein each scheduling context condition of comprising order and carrying out described order based on threshold value; Second module (perhaps other hardware, software or its combination), the value that its value to the regulation management object in the described terminal is sampled and will be sampled is compared with the threshold value of regulation; With three module (perhaps other hardware, software or its combination), when its value in the sampling of the definite described management object of described first module has reached described threshold value, at the administration order of described management object actuating equipment.
The present invention also provides a kind of server, this server comprises DM scheduling activator appliance, this DM scheduling activator appliance generates at least one or a plurality of scheduling context and request described at least one or a plurality of scheduling context is loaded into terminal, make that described terminal can be according to described at least one or a plurality of scheduling context actuating equipment management, wherein each scheduling context condition of comprising order and carrying out described order based on threshold value.
The present invention also provides a kind of method that is used for management equipment, and this method comprises: the value to the regulation management object is sampled; The value of sampling is compared with the threshold value of regulation; With when the value of determining described management object has reached described threshold value, at the administration order of described management object actuating equipment.
Hereinafter, illustrative embodiments of the present invention will be described with reference to the accompanying drawings in further detail.Can be expressly understood that these embodiments are exemplary, and not mean that limitation of the present invention.
Fig. 1 shows according to server of the present invention (that is, the DM server) and terminal (that is) exemplary concepts structure, the DM client, and Fig. 2 shows the scheduling context as exemplary apparatus management tree structure.And Fig. 3 shows the scheduling context as another exemplary apparatus management tree structure.
With explanation, also with key drawing 2 and 3 to Fig. 1.
Fig. 1 shows according to exemplary DM server (100) of the present invention and terminal (100).
(1) feature of DM server
DM server (100) can comprise DM scheduling activator appliance (110) or other similar hardware, software or its combination.
DM scheduling activator appliance (110) can comprise similar hardware, software or its any combination of scheduler context manager module (111) and status report processing module (112) and/or other types.
Scheduler context manager module (111) can have and generates scheduling context and requesting terminal (200) and be written into and carry out this and dispatch contextual unit (that is, partly, assembly etc. or its combination).
More particularly, scheduler context manager module (111) is created equipment control (DM) session (the perhaps communication item of some other types or process) according to relevant standard (for example DM standard), can be written into described scheduling context by the DM session of creating in requesting terminal (200) then.
Described scheduling context can comprise general information and one or more schedule component as shown in Figure 2.Can also comprise the information, parameter of additional and/or alternative type etc.At this, described general information can comprise one or more in the following information: dispatch contextual identifier element, title key element, corresponding with service device key element and term of validity key element.Described schedule component can comprise one or more in the following information: specify the elements of mission of DM order and the condition element that the condition (that is, reason, factor, parameter etc.) of described DM order is carried out in appointment.Yet, should be noted that these that key element is not limited only to list above, but can use other different key elements or only use in the key element list some.
At this, device management command can be included in the message.In other words, message can comprise at least one or a plurality of device management command.If use message, then described elements of mission specify message.And, above-mentioned condition can be based on timer, based on trapping or based on threshold value.Also can use other condition bases or replacement condition basis.
Simultaneously, can have one or more schedule component in described scheduling context, these schedule component can have the logical relation of binding each other.That is, described schedule component can be interconnected.For example, this interconnected can finger,, module (perhaps other entities) is if when satisfying first condition of dispatching then carrying out the order of first schedule component, stop the order of second schedule component.For this is particularly useful based on the scheduling of threshold value, can carry out one or more assembly in an alternating manner respectively according to specific threshold value thus.
This interconnected notion can be applied to described scheduling context.That is,, then stop the second scheduling context in described at least one or a plurality of scheduling context if begin the first scheduling context at least one or a plurality of scheduling context.
If desired, can revise (that is, correction, change, change etc.) scheduling context, perhaps can ask this modification to terminal (200) with scheduler context manager module (111).In addition, scheduler context manager module (111) can the loaded scheduling context of requesting terminal (200) deletion.
In addition, when in terminal (200) if in be written into or be written into again the scheduling change in context time or when making a mistake or the scheduling context state change, scheduler context manager module (111) can receive message (perhaps other indications) and carry out its suitable processing from terminal (200).
Described elements of mission described above and described condition element are included in the described schedule component.But, should be noted that these key elements can directly be included in the described scheduling context, as shown in Figure 3.
(2) feature of terminal
Terminal (200) can comprise DM scheduling activator appliance (210) and DM activator appliance (220).At this, be appreciated that and also can use other similar hardware, software or its any combination.
DM scheduling activator appliance (210) can comprise that the scheduling context insmods (211), condition matching module (212), DM command execution module (213) and status report module (214).At this, be appreciated that and also can use other similar hardware, software or its any combination.
The scheduling context insmod (211) be to be written into request and to carry out its unit of suitably handling (that is, partly, assembly etc. or its combination) from server (110) (that is, DM scheduling activator appliance (110)) receiving scheduling context.At this, can pass through DM activator appliance (220) receiving scheduling context, this scheduling context transfer can be given scheduling context insmod (211) then.The scheduling context insmod (211) use described scheduling context, generation one or more node (the perhaps level of other types point) in equipment control (DM) tree (the perhaps hierarchical structure of other types or logical format) that comes in terminal (200), to use.At this, the DM tree can be formed by general information nodes and one or more schedule component (equipment control of scheduling).
With reference to figure 2, explain DM tree (that is, the scheduling context is written into form) in more detail.
Fig. 2 shows exemplary DM tree.More particularly, general information nodes (as shown in Figure 2) can comprise Id node, title node, effective node and server node, the Id node is represented the contextual identifier of the scheduling that is written into, the title node represents to dispatch contextual title, effectively node represents to dispatch the contextual term of validity, and server node represents to dispatch the contextual owner.Can be expressly understood that the title of these nodes and type are exemplary.
Schedule component can comprise with in the lower node one or more: the task node of expression DM order and specify the condition node of the condition (perhaps environment) of carrying out the DM order.Obviously, also can use the additional or substitute node of other types.
At this, the DM order is included in the message.Therefore, task node can be specified the message that comprises the DM order.And as mentioned above, described condition can be based on threshold value.Therefore, described condition node comprises the Th node of regulation based on the condition of threshold value.
As shown in Figure 2, the Th node comprises at least one in the following node: address node, the address of its regulation management object; Time interval node, the time interval of the value of its regulation monitoring management object; The threshold value node, its specified threshold; Threshold value form node, the form of its specified threshold are Boolean type, character type, integer, floating type, date type or time type; Threshold value type node, the type of its specified threshold are absolute value or increment size; Direction node, its specified threshold are to rise, descend or static state; With the hysteresis node, the allowance of its specified threshold.
In addition, described address node can comprise at least one in the following node: URI node, the unified resource identifier (URI) of its regulation management object; The MOI node, it stipulates management object identifier (MOI); With the MOI filter node, its regulation is used for management object that will regulation and the additional information that other management objects distinguish because of the coexistence that has the management object of identical MOI when using the MOI node.
If there is not the MOI node, then the URI node can be stipulated sufficient address.Yet if the MOI node is arranged, the URI node can be with respect to the root regulation relative address of management object.
Specifically, the MOI filter node comprises at least one in URI node, value node and the form node.
Be included in URI node in the MOI filter node and stipulated the unified resource identifier (URI) with respect to the root of management object of management object.
For the situation that has the management object that has identical management object identifier (MOI) more than, for regulation management object and other management objects are distinguished, the value node that is included in the MOI filter node has been stipulated the value that will compare with the value of the regulation management object of being indicated by the URI node of MOI filter node.If have the URI node that is included in the MOI filter node, then the value in the described value node can be compared with the value of URI.Yet,, the root name of value in the value node and management object can be claimed compare if be not included in URI node in the MOI filter node.
Be included in form node in the MOI filter node and stipulated the form of the value in the value node.Possible values is 64 system types, binary type, Boolean type, integer, xml, date type, time type or floating type.If there is not the form node, can think that then the form of value node is a character type.
At this, threshold value node specified threshold, and the value of threshold value node is the digital text character string, the various forms of expression threshold value.Determine the actual format of threshold value by threshold value form node.The sampling statistical value of the management object selected is compared with the value of threshold value node.But, if the value of current sampling is first value (for example, scheduling operation just begins after heavily powering on), and if do not have previous sampling, then the most last sampling is not counted.When this threshold value is the rising threshold value, if the value of current sampling is greater than or equal to this threshold value, and if the most last sampling less than this threshold value, condition coupling then appears.When this threshold value was the decline threshold value, then Conditions mated in the opposite direction.When this threshold value is configured to the static gates limit value, if current sampled value equals this threshold value with intersect irrelevant, and if the most last sampling be not equal to this threshold value, the condition match event then appears one time.But as long as sampled value equals this threshold value, the logic state of condition is true just.If stipulated hysteresis, after threshold value intersection incident takes place, another condition coupling can take place just when sampled value descends to such an extent that be lower than with respect to this threshold value or be elevated to the allowance that is higher than the regulation that lags behind.
The actual format of threshold value form node specified threshold and hysteresis.The possible values of threshold value form node is Boolean type, character type, integer, date type, time type or floating type.
Threshold value type node specified threshold type.The possible values of threshold value type node is absolute value or increment size.Be absolute value if this is worth, then with the sampled value of management object directly and threshold value compare.Be increment size if this is worth, then deduct the sampled value of last sampling, then gained difference and threshold value are compared from current sampled value.
The value of direction node regulation when threshold value intersection incident takes place changes behavior.Possible values is for rising, descend or static state.The static gates limit value represents, when sampled value equals threshold value and with crisscross irrelevant, and Conditions couplings all.
The value that hysteresis node regulation lags behind.The value of hysteresis node is the text-string of the various forms of expression lagged value.Determine the actual format of lagged value by threshold value form node.Use to lag behind, prevented from when sampled value fluctuates near threshold value because of noise, to take place too much threshold value intersection incident.For example, in the situation of rising threshold value,, just can not carry out this order again, unless sampled value hangs down the allowance of hysteresis node regulation with respect to threshold value in case carried out order.
Wherein, task node has been described above and the condition node is included in the schedule component.But, should be noted that these key elements can directly be included in the scheduling context, as shown in Figure 3.
The instruction according to DM server (100) be written into the scheduling context before, if necessary, the scheduling context insmod (211) can optionally check the scheduling contextual validity (perhaps authority).
Condition matching module (212) is such unit (that is, partly, assembly etc. or its combination), that is, it is used for monitoring or check the coupling based on the condition of threshold value that whether is used to carry out in schedule component.Whether the value based on the specific management object in the condition designated terminal (200) of threshold value reaches the threshold value that sets in advance.In view of the above, the value of condition matching module (212) monitoring (perhaps checking) specific management object, should value and threshold value compare, and when reaching threshold value, can ask DM command execution module (213) execution to be ordered corresponding to the DM of condition.
In the condition matching module (212) of carrying out said process, there is one or more schedule component (promptly, Equipment Management Function of having dispatched or process), if and each schedule component comprises and is used to carry out condition based on the process of threshold value at same cura specialis entity, then can be and these are used to carry out based on the condition of the process of threshold value interconnected at this cura specialis entity, and can monitor these conditions.
For example, suppose in the scheduling context, first schedule component (that is the equipment control of having dispatched) and second schedule component (that is the equipment control of, having dispatched) are arranged respectively.And, suppose first schedule component comprise DM order and at the cura specialis entity be used to carry out condition based on the process of first threshold value, second schedule component comprises the 2nd DM order and is used to carry out condition based on the process of second threshold value at same cura specialis entity.If like this, then when the value of this cura specialis entity satisfied the condition that is used to carry out based on the process of first threshold value, condition matching module (212) request DM command execution module (213) was carried out DM order.And when the value of this cura specialis entity satisfied the condition that is used to carry out based on the process of second threshold value, condition matching module (212) request DM command execution module (213) was carried out the 2nd DM order.
DM command execution module (213) is such unit (that is, partly, assembly etc. or its combination), and it cooperates with DM activator appliance (220) and to carry out DM and order when the coupling that exists the condition that is used to carry out the DM order.In other words, DM command execution module (213) sends the DM order to DM activator appliance (220), and receives the result that execution DM order obtains from DM activator appliance (220).
Status report module (214) is such unit (that is, partly, assembly etc. or its combination), that is, and and the result that it obtains to the state or the fill order of DM server (100) reporting terminal (22).Status report module (214) is used DM command execution results (that is, status message, results messages or alarm information), generates the report message that can send to DM server (100).At this, can use general alarm information or message or indication by some other types, give DM server (100) with the state transfer of report message or terminal (200).In addition, as mentioned above, when dispatching the state variation of contextual state or schedule component, status report module (214) can be reported to DM server (100).
DM activator appliance client (220) is to cooperate the unit of carrying out the DM order with command execution module (214).More particularly, DM activator appliance client (220) is carried out the DM order that receives from command execution module (214), then its result is returned (for example, report) and gives command execution module (214).
So far, at DM server (100) with scheduler context manager module (111) and status report processing module (112), with terminal (200), the inscape of DM of the present invention system has been described with DM scheduling activator appliance (210) (comprise that the scheduling context insmods (211), condition matching module (212), DM command execution module (213) and status report module (214)) and DM activator appliance (220).Yet these key elements also can be implemented as any combination of processor (not shown), network interface (not shown) and memory storage (not shown).
The feature of the method according to this invention
The operation of DM of the present invention system will be described in further detail with reference to Figure 4 and 5.Although should be noted that Figure 4 and 5 the details of all key elements is not described, each process can be carried out by above-mentioned DM server (100) and the various assemblies in the terminal (200).
Fig. 4 illustrates the process flow diagram that scheduling context according to the present invention is written into process, and Fig. 5 illustrates the process flow diagram that is used to carry out the method for the equipment control of having dispatched according to of the present invention.
As shown in Figure 4, be written in the process of the present invention, DM server (100) is set up the DM session (the perhaps communication linkage of some other types) with DM activator appliance (220), thereby is written into the scheduling context.
To explain in further detail that below exemplary scheduling context of the present invention is written into process.
1) DM server (100) (its scheduler context manager module (111) specifically) generates (perhaps creating) scheduling context.
2) the DM session of DM server (100) foundation and terminal (200) uses DM agreement (perhaps other suitable communication protocols) to transmit the request (perhaps instruction) that the scheduling context that will generate is loaded into the DM scheduling activator appliance client (210) of terminal (200) then.At this, can send described request to DM scheduling activator appliance client (210) by DM activator appliance (220).
3) DM of terminal (200) scheduling activator appliance (210) (specifically, its scheduling context insmods (211)) is checked the contextual validity of described scheduling.
4) finish validity check after, the scheduling context in the DM tree (the perhaps hierarchical structure of other types or logical format) of the DM of terminal (200) scheduling activator appliance (210) (specifically, its scheduling context insmods (211)) loading terminal (200).At this, aforesaid Fig. 2 and 3 shows the example of DM tree.
5) when finishing described being written into, the result that the DM of terminal (200) scheduling activator appliance (210) (specifically, its scheduling context insmods (211)) is written into to DM server (100) report scheduling context.
With reference to figure 5 exemplary schedule component disposal route of the present invention is described.
1) DM scheduling activator appliance (210) (specifically, its condition matching module (212)) is checked the condition node in the DM tree that expression scheduling context is written into, and monitoring whether with its executive condition coupling.At this, described condition can be based on threshold value.It also can be the condition of adding or substitute.
2) according to described monitoring, if confirm and the executive condition coupling, then DM scheduling activator appliance (210) (its DM command execution module (213) specifically) cooperates with DM activator appliance (220) and carries out DM and order.
3) when finishing the execution of DM order, DM scheduling activator appliance (210) (its status report module (214) specifically) is given DM server (100) with the status report of execution result or terminal (200).That is, the report of execution result can be informed to DM server (100) and whether correctly carried out DM order or the wrong reason that takes place.The report message (the perhaps indication of some other types) that described reporting process can use execution result to create can to send to DM server (100).
4) after receiving status report, the status report execution analysis (perhaps other processing) of DM server (100) (its status report processing module (120) specifically) to receiving.
Fig. 6 shows the illustrative methods that is used to carry out based on the device management scheduling of threshold value, and Fig. 7 shows the illustrative methods that is used to carry out based on the device management scheduling of trapping.
As shown in Figure 6, the scheduling context can comprise two schedule component.More particularly, if the value of cura specialis entity (for example, threshold value when the radio interface entity has the stabilized communication amount) surpass 1, contextual first schedule component of then described scheduling (that is the equipment control of, having dispatched) allows to carry out the DM order that variable foo is changed into bar.In addition, if the value of cura specialis entity is got back to steady state (SS), contextual second schedule component of then described scheduling allows to carry out the DM order that variable bar is changed into foo.In addition, owing to lag behind, the handling capacity that first and second schedule component can be ignored the specific wireless electrical interface surpasses threshold value 1 and falls back to the situation that is lower than threshold value 1 once more, if the words that this species diversity is considered to smaller (for example, in (permission) scope of hysteresis).This is in order to get rid of because The noise (perhaps other interference) causes the unsettled reason of system.
To the exemplary implementation of first and second assemblies be described.
(1) first assembly and second assembly become activation (perhaps enabling) from original state, and are performed.
(2), then carry out the DM order of first schedule component if the handling capacity of particular radio (wireless) interfacing equipment surpasses threshold value 1.
(3) after carrying out the DM order, variable foo changes bar into, and first schedule component becomes inactivation (perhaps forbidding), and carries out second schedule component.
(4) be lower than threshold value 2 if the handling capacity of particular radio (wireless) interfacing equipment drops to, then carry out the DM order of second schedule component.
(5) after carrying out the DM order, variable bar becomes foo, and second schedule component becomes inactivation (perhaps forbidding), and carries out first schedule component.
Fig. 7 shows the scheduling context that comprises two schedule component (that is the equipment control of, having dispatched).More particularly, contextual first schedule component permission of described scheduling terminal operation pattern when particular event 1 takes place is set to emergency mode, and carries out second schedule component.Contextual second schedule component of described scheduling makes regular check on whether abnormality is arranged, if elimination (has perhaps solved) abnormality, then allows described terminal to turn back to its normal mode from emergency mode.
The exemplary implementation of first and second schedule component is as described below.
(1) when being written into the scheduling context, second assembly becomes inactivation (perhaps forbidding) state from its original state, and first schedule component becomes activation or initiate mode from its original state, and is performed.
(2) when particular event 1 takes place, carry out the DM order of first schedule component.
(3) after carrying out the DM order, the terminal operation pattern becomes emergency mode, and first schedule component becomes inactivation (perhaps forbidding), and second schedule component becomes activation (perhaps enabling).
(4) when second schedule component becomes state of activation and is performed, second schedule component checks whether the state of terminal is normal, and regularly (for example, every 10 minutes) carry out this inspection.
(5) after carrying out this making regular check on, be normal if find the state of terminal, then carry out the DM order of second assembly.
(6) when carrying out the DM order, the terminal operation pattern becomes normal mode from emergency mode, forbids second schedule component, and enables first schedule component.
Method of the present invention can be implemented as software, hardware or its any combination.For example, method of the present invention can be implemented as code or the instruction in the software program that is stored in the storage medium (for example, the internal storage of terminal, flash memory, hard disk etc.) and carries out by processor (for example, the microprocessor in the terminal etc.).
About effect of the present invention, by the DM order that will carry out in terminal and the condition based on threshold value of carrying out described DM order (being included in the scheduling context) are provided to terminal (shifting to an earlier date), and make terminal according to carry out these DM orders based on the condition of threshold value, its result is: no matter when terminal is from DM server requests DM order, and terminal is all treated as these orders directly to be provided from the DM server as them.
And, order because the present invention allows to carry out DM according to specified threshold, so can prevent (perhaps minimized at least) contingent mistake in terminal effectively.
In addition,, can carry out the DM order, therefore can handle the DM order more effectively in the mode of system more by carry out one or more scheduling context in an alternating manner respectively according to specified threshold.
Should be noted that feature of the present invention and notion relate to various types of equipment controles by the respective standard organization management (DM) standard.Therefore, various corresponding standard and wherein the regulation notion also be a part of the present invention.
Although this instructions has stipulated to relate to the various titles of order, node, child node of equipment control (DM) etc., can be expressly understood that these titles and label are exemplary.Feature of the present invention is not limited, and can use other title that is equal to or labels, as long as their expression function identical or that be equal to and/or features.
Any in this manual to the quoting of " embodiment ", " embodiment ", " exemplary embodiment " etc., all represent to be included at least one embodiment of the present invention at special characteristic, structure or characteristics that described embodiment is described.The different in this manual local this statements that occur differ and establish a capital with reference to same embodiment.And, when describing special characteristic, structure or characteristics, implying in conjunction with other embodiment and realizing that this feature, structure or characteristics are also in the thinkable scope of those skilled in the art at arbitrary embodiment.
Although described embodiment with reference to several illustrative embodiments, should be appreciated that those skilled in the art can envision many other modification and embodiments, they also drop in the spirit and scope of principle of prospectus.More particularly, in the scope of prospectus, accompanying drawing and appending claims, can carry out various variations and change to the ingredient and/or the arrangement of object unitized construction.Except variation and change to ingredient and/or arrangement, the also clear other application of those skilled in the art.
Claims (28)
1, a kind of terminal, it comprises:
First module, it is used for receiving one or more scheduling context at least from server, and is written into described at least one or a plurality of scheduling context, wherein, the condition that each scheduling context comprises order and carries out described order based on threshold value;
Second module, it is used for the value of the management object of the regulation of described terminal is sampled, and the value that will sample is compared with described threshold value; With
Three module, it is used for having reached under the situation of described threshold value in the value of the sampling of the definite described management object of described second module, at the administration order of described management object actuating equipment.
2, terminal as claimed in claim 1, wherein
Described second module is sampled to each value of the management object of one or more regulation in the described terminal, and the threshold value of each value and each regulation is compared.
3, terminal as claimed in claim 1, wherein
The value of sampling and described threshold value with one to one, the mode of one-to-many or the multi-to-multi connection that is relative to each other.
4, terminal as claimed in claim 1, wherein
Described second module uses the address of described management object or identifier to come described value is sampled.
5, terminal as claimed in claim 4, wherein, described address is represented with in specific address and the relative address at least one.
6, terminal as claimed in claim 4, wherein
If used described identifier, then described second module is also used additional information.
7, terminal as claimed in claim 6, wherein
Described additional information comprises the relative position of described management object and at least one in the value.
8, terminal as claimed in claim 1, wherein, described second module is monitored described value at interval with official hour.
9, terminal as claimed in claim 1, wherein
Described second module also compares the value of described sampling with previous value of sampling.
10, terminal as claimed in claim 9, wherein
If the value of described previous sampling corresponding to the value before restarting, is then ignored the value of described previous sampling.
11, terminal as claimed in claim 1, wherein
If the value of current sampling is equal to, or greater than described threshold value, and if the value of previous sampling less than described threshold value, then described three module is carried out described order.
12, terminal as claimed in claim 1, wherein
If the value of current sampling is equal to or less than described threshold value, and if the value of previous sampling greater than described threshold value, then described three module is carried out described order.
13, terminal as claimed in claim 1, wherein
After carrying out once described order, drop to respect to threshold value up to the value of described sampling and to be lower than or to be elevated to when being higher than the regulation allowance, described three module could be carried out described order.
14, terminal as claimed in claim 1, wherein
If the value of current sampling equals described threshold value, and if the value of previous sampling be not equal to described threshold value, then described three module is carried out described order.
15, terminal as claimed in claim 1, wherein
If described threshold value is defined as increment size, then described second module compares the value of current sampling and the difference and the described threshold value of previous value of sampling.
16, terminal as claimed in claim 1, wherein, described condition comprises at least one in the following key element:
The first element, it is used to stipulate the address of described management object;
Second key element, it is used for regulation and samples time interval of value of described management object;
Three elements, it is used to stipulate described threshold value;
The 4th key element, its format specification that is used for described threshold value is Boolean type, character type, integer, floating type, date type or time type;
Five elements, its type stated that is used for described threshold value is absolute value or increment size;
The 6th key element, it is used for described threshold value is defined as rising, descends or static state; With
The 7th key element, it is used to stipulate the allowance of described threshold value.
17, terminal as claimed in claim 16, wherein, the described first element comprises at least one in the following sub-key element:
The first sub-key element, it is used to stipulate the unified resource identifier of described management object;
The second sub-key element, it is used to stipulate the identifier of described management object; With
The 3rd sub-key element, it is used for regulation because of existing identical identifier to be used for the additional information that specific management object and other management objects are distinguished under the situation of the described second sub-key element using.
18, terminal as claimed in claim 17, wherein, the described the 3rd sub-key element comprises at least one in following:
The URI with respect to the root node of described device management tree of described management object;
The value of described management object; With
The form of described value.
19, terminal as claimed in claim 1, wherein
Described at least one or a plurality of scheduling context can be interconnected by described threshold value.
20, terminal as claimed in claim 1, wherein
If satisfy the contextual condition of first scheduling in described at least one or a plurality of scheduling context, then described three module is carried out the contextual order of described first scheduling, if and satisfy the contextual condition of second scheduling in described at least one or a plurality of scheduling context, then carry out the contextual order of described second scheduling.
21, a kind of terminal, it comprises:
First module, it is used for receiving one or more scheduling context at least from server, and is written into described at least one or a plurality of scheduling context, the condition based on threshold value that each scheduling context comprises order and carries out described order; Wherein, described condition comprises at least one in the following key element: the first element, and it is used for the address of regulation specific management object; Second key element, it is used to stipulate time interval that the value of described specific management object is sampled; Three elements, it is used for specified threshold; The 4th key element, it is used to stipulate the type of described threshold value; Five elements, it is used to stipulate the direction of described threshold value; With the 6th key element, it is used to stipulate the allowance of described threshold value; With
Second module, it is used for carrying out described order at described management object when the value of determining described specific management object has reached described threshold value.
22, terminal as claimed in claim 21, wherein
Described the 4th key element is absolute value or increment size with the type stated of described threshold value.
23, terminal as claimed in claim 21, wherein, described condition also comprises:
The 7th key element, its format specification that is used for described threshold value is Boolean type, character type, integer, floating type, date type or time type.
24, a kind of server, it comprises:
DM dispatches activator appliance, it is used to generate at least one or a plurality of scheduling context and request described at least one or a plurality of scheduling context is loaded into terminal, make that described terminal can be according to described at least one or a plurality of scheduling context actuating equipment management
Wherein, each scheduling context comprises the condition based on threshold value of order and the described order of execution.
25, terminal as claimed in claim 24, wherein, described condition comprises at least one in the following key element:
The first element, it is used to stipulate the address of described management object;
Second key element, it is used for the time interval that regulation is monitored the value of described management object;
Three elements, it is used to stipulate described threshold value;
The 4th key element, its format specification that is used for described threshold value is Boolean type, character type, integer, floating type, date type or time type;
Five elements, its type stated that is used for described threshold value is absolute value or increment size;
The 6th key element, it is used for described threshold value is defined as rising, descends or static state; With
The 7th key element, it is used to stipulate the allowance of described threshold value.
26, a kind of method of management equipment, it comprises:
Value to the regulation management object is sampled;
The value of sampling is compared with the threshold value of regulation; With
If when determining that the value of described management object has reached described threshold value, then at the administration order of described management object actuating equipment.
27, method as claimed in claim 26, it also comprises:
Receive one or more scheduling context at least from server, wherein each scheduling context comprises the condition based on threshold value of order and the described order of execution; With
Be written into the scheduling context that is received.
28, method as claimed in claim 27, wherein, described condition comprises at least one in the following key element:
The first element, it is used to stipulate the address of described management object;
Second key element, it is used for the time interval that regulation is monitored the value of described management object;
Three elements, it is used to stipulate described threshold value;
The 4th key element, its format specification that is used for described threshold value is Boolean type, character type, integer, floating type, date type or time type;
Five elements, its type stated that is used for described threshold value is absolute value or increment size;
The 6th key element, it is used for described threshold value is defined as rising, descends or static state; With
The 7th key element, it is used to stipulate the allowance of described threshold value.
Applications Claiming Priority (11)
| 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 | ||
| KR1020060043155 | 2006-05-12 | ||
| KR10-2006-0043155 | 2006-05-12 | ||
| KR20060043155 | 2006-05-12 | ||
| KR1020070005822A KR101342370B1 (en) | 2006-01-23 | 2007-01-18 | Terminal and method for pefforming device managemnt scheduled based on treshold thereof |
| KR1020070005822 | 2007-01-18 | ||
| KR10-2007-0005822 | 2007-01-18 | ||
| PCT/KR2007/000379 WO2007083973A1 (en) | 2006-01-23 | 2007-01-22 | Terminal and method for performing device management scheduled based on threshold |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010101153896A Division CN101778004B (en) | 2006-01-23 | 2007-01-22 | Terminal and method for performing device management scheduled based on threshold thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101371236A true CN101371236A (en) | 2009-02-18 |
| CN101371236B CN101371236B (en) | 2012-05-23 |
Family
ID=40414019
Family Applications (3)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007800028043A Expired - Fee Related CN101371235B (en) | 2006-01-23 | 2007-01-22 | Device management scheduling method and apparatus thereof |
| CN2007800029582A Expired - Fee Related CN101371243B (en) | 2006-01-23 | 2007-01-22 | Performing scheduled device management |
| CN2007800028823A Expired - Fee Related CN101371236B (en) | 2006-01-23 | 2007-01-22 | Terminal and method for performing device management scheduled based on threshold |
Family Applications Before (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007800028043A Expired - Fee Related CN101371235B (en) | 2006-01-23 | 2007-01-22 | Device management scheduling method and apparatus thereof |
| CN2007800029582A Expired - Fee Related CN101371243B (en) | 2006-01-23 | 2007-01-22 | Performing scheduled device management |
Country Status (1)
| Country | Link |
|---|---|
| CN (3) | CN101371235B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101888119B (en) * | 2010-05-28 | 2012-07-18 | 北京中恒博瑞数字电力科技有限公司 | Generation method of scheduling operating command ticket |
| CN104301179B (en) * | 2014-10-15 | 2017-12-22 | 东华大学 | Sensor data transmission system failure monitoring method based on Ethernet |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP3834452B2 (en) * | 1999-04-01 | 2006-10-18 | セイコーエプソン株式会社 | Device management system, management server, and computer-readable recording medium |
| JP4852226B2 (en) * | 2002-12-27 | 2012-01-11 | セイコーエプソン株式会社 | Device monitoring system |
| FI116426B (en) * | 2003-05-02 | 2005-11-15 | Nokia Corp | Initiate device management between the management server and the client |
| CN1309211C (en) * | 2003-05-13 | 2007-04-04 | 中兴通讯股份有限公司 | Distributed central management method for special shaped network equipment in distributing network environment |
| KR20050046932A (en) * | 2003-11-14 | 2005-05-19 | 삼성전자주식회사 | System for checking state of slave devices using i2c bus |
| CN1547120A (en) * | 2003-12-10 | 2004-11-17 | 沈阳东软软件股份有限公司 | Network monitoring management system |
| CN100370739C (en) * | 2003-12-26 | 2008-02-20 | 华为技术有限公司 | Application distributed network management system and method |
-
2007
- 2007-01-22 CN CN2007800028043A patent/CN101371235B/en not_active Expired - Fee Related
- 2007-01-22 CN CN2007800029582A patent/CN101371243B/en not_active Expired - Fee Related
- 2007-01-22 CN CN2007800028823A patent/CN101371236B/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CN101371235B (en) | 2010-09-15 |
| CN101371243B (en) | 2011-04-27 |
| CN101371236B (en) | 2012-05-23 |
| CN101371235A (en) | 2009-02-18 |
| CN101371243A (en) | 2009-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101778004B (en) | Terminal and method for performing device management scheduled based on threshold thereof | |
| US20070192158A1 (en) | Performing scheduled device management | |
| CN101636738B (en) | Method for obstruction and capacity information unification monitoring in unification management system environment and system for thereof | |
| CN109271331A (en) | Generation method, device, computer equipment and the storage medium of log | |
| CN111510468B (en) | Scheduling method and device of computing task, server and computing system | |
| CN111026602A (en) | Health inspection scheduling management method and device of cloud platform and electronic equipment | |
| CN101408852B (en) | Method, apparatus and system for scheduling task | |
| US8104037B2 (en) | Terminal and method for performing device management scheduled based on threshold | |
| CN109426510A (en) | Software processing method, device, electronic equipment and computer readable storage medium | |
| US7793301B2 (en) | Method and system for providing efficient object-based network management | |
| CN101371236B (en) | Terminal and method for performing device management scheduled based on threshold | |
| EP1577813A1 (en) | Software structure driven approach for implementing workflow | |
| Silva Souza et al. | Designing an adaptive computer‐aided ambulance dispatch system with Zanshin: an experience report | |
| US8132181B2 (en) | Method, apparatus and media for indication management in an information model environment | |
| CN115048158A (en) | Process arranging and calling method, system and computer equipment thereof | |
| Vasilev et al. | I4. 0 Component Models based on IEC/EN 62264 | |
| CN105808348A (en) | Data service scheduling apparatus, system and method | |
| Kokash | Risk management for service-oriented systems | |
| CN109271306A (en) | Life test method, device, equipment and medium based on direct fault location | |
| CN106844021A (en) | Computing environment resource management system and management method thereof | |
| US20240078102A1 (en) | Information providing device, information providing method, information management device, and computer-readable recording medium | |
| CN104137481A (en) | Network of devices forming a diagnostic system | |
| EP4030366A1 (en) | Method and system for automatic service level agreement conflict and accountability resolution | |
| CN114114983A (en) | E-commerce operation control method, system, terminal device and storage medium | |
| Park et al. | Proactive self-healing system for application maintenance in ubiquitous computing environment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20120523 Termination date: 20190122 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |