CN101371235B - Device management scheduling method and apparatus thereof - Google Patents
Device management scheduling method and apparatus thereof Download PDFInfo
- Publication number
- CN101371235B CN101371235B CN2007800028043A CN200780002804A CN101371235B CN 101371235 B CN101371235 B CN 101371235B CN 2007800028043 A CN2007800028043 A CN 2007800028043A CN 200780002804 A CN200780002804 A CN 200780002804A CN 101371235 B CN101371235 B CN 101371235B
- Authority
- CN
- China
- Prior art keywords
- scheduling
- node
- terminal
- contextual
- context
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Computer And Data Communications (AREA)
- Telephonic Communication Services (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
vice management commands to be executed within a terminal and conditions included within a scheduling context for executing such commands are provided to the terminal ahead of time. A server generates a scheduling context (or other type of scheduling information) that includes device management scheduled by the server to allow more effective scheduling to be performed by the terminal. A terminal receives the scheduling context from the server and performs the scheduled device management procedures accordingly.
Description
Technical field
The present invention relates to device management scheduling method and device thereof.
Background technology
Usually, equipment control (DM) technology relates to equipment control (DM) server (or other network entities) and shows that (or indication) equipment control (DM) client computer (being terminal or other subscriber equipmenies) is as the resource that is present in the management object on equipment control (DM) tree hierarchy or the logical format of the other types of equipment control (or be used for), permission conducts interviews to it, and makes the DM server can manage this terminal like a cork.
In this type of DM technology, the DM server can come the treatment facility administration order by indicating terminal, and the terminal of being managed can report to execution result the DM server immediately after executing corresponding order.And the DM server can the requesting terminal changes, upgrades, deletes or handle the specific function that is used for equipment control.
One aspect of the present invention is the cognition of inventor to the following defective in the existing DM technology.That is, in the prior art, only when having mistake or fault in the terminal, terminal just can be ordered to DM server requests DM.Thus, the diagnostic routine of prior art terminal becomes more expensive, and owing to can't before this type of problem takes place, expecting or finding them, so can not solve diagnosis problem effectively.
Summary of the invention
Therefore, in order to address the aforementioned drawbacks, the invention provides the server of a kind of generation scheduling context (or schedule information of other types), the scheduling context comprises through the device management information of this server scheduling to allow terminal to carry out more effective scheduling.
The present invention also provides a kind of terminal of also correspondingly carrying out the equipment control step of being dispatched from server receiving scheduling context.
The invention provides a kind of terminal, this terminal has: first module (or other hardware, software, or its combination), be used for receiving and install scheduling context (or scheduling framework of other types) from server, described scheduling context comprises at least one equipment control of being dispatched (promptly, element, device etc.), and comprise that general information, this general information have the first node of expression scheduling context state (or situation) point of other types (or in the hierarchy) and relate to the Section Point of the dispatching contextual State Control point of other types (or in the hierarchy); And second module (or other hardware, software, or its combination), be used for carrying out the equipment control of being dispatched according to the scheduling context of being installed.
The invention provides a kind of server, this server comprises: the device management scheduling enabler, be used for generating and requesting terminal installation scheduling context, and carry out the equipment control of being dispatched according to the scheduling context of being installed, this scheduling context comprises the equipment control that at least one is dispatched and has the first node of the contextual state of expression scheduling and the general information that relates to the Section Point of dispatching contextual State Control.
Description of drawings
Fig. 1 shows the exemplary conceptual structures according to server of the present invention and terminal.
Fig. 2 shows according to scheduling context of the present invention with demonstration equipment management tree structure.
Fig. 3 shows according to scheduling context of the present invention with another kind of demonstration equipment management tree structure.
Fig. 4 shows the exemplary flow chart according to scheduling context installation steps of the present invention.
Fig. 5 shows the process flow diagram according to the exemplary method of actuating equipment management and dispatching of the present invention.
Fig. 6 shows the exemplary method of execution based on the device management scheduling step of threshold value.
Fig. 7 shows the another kind of exemplary method of execution based on the device management scheduling step of trap (trap).
Embodiment
Exemplary embodiment of the present invention is described below with reference to accompanying drawings.Can know to be understood that these embodiments only are exemplary, be not to limit the present invention.
Fig. 1 shows the exemplary conceptual structures according to server of the present invention (being the DM server) and terminal (being the DM client computer), and Fig. 2 shows the scheduling context with demonstration equipment management tree structure.In addition, Fig. 3 shows the scheduling context with another kind of demonstration equipment management tree structure.
Description to Fig. 1 also is used to describe Fig. 2 and Fig. 3.
Fig. 1 shows according to exemplary DM server of the present invention (100) and terminal (200).
(1) feature of DM server
DM server (100) can comprise DM scheduling enabler (110) or other similar hardware, software or its combination in any.
DM scheduling enabler (110) can comprise similar hardware, software or its combination in any of DM scheduler context manager module (111) and status report processing module (112) and/or other types.
Scheduler context manager module (111) can have and is used for generating scheduling context and requesting terminal (200) and installs and carry out its unit (i.e. part, element etc., or its combination).
More specifically, scheduler context manager module (111) is set up and equipment control (DM) session of terminal (200) (or other types communicate by letter time limit or cycle) according to relative standard's (for example DM standard), can come requesting terminal (200) that the scheduling context is installed via the DM session of being set up then.
The scheduling context can comprise general information and one or more scheduling ingredient.Also comprise the information, parameter of additional and/or alternative type etc.At this, general information can comprise with the next item down or more multinomial: dispatch the state elements of contextual identifier elements, name element, corresponding server element, effective period element, the contextual state of expression scheduling, and relate to StateOP (node) element of dispatching contextual State Control.
Scheduling ingredient can comprise with the next item down or more multinomial: specify the DM order Task (task) element, specify Cond (condition) element, appointment and the user of the condition (being reason, factor, parameter etc.) of carrying out the DM order mutual User Interaction (user interactions) element, specify and whether the result who carries out the DM order should be reported to Gating (gating) element of (or indication to) server, and indicate whether should be to the state of server reporting terminal or the Event of incident (incident) element.Yet, it should be noted that element is not limited in column element, but can use different additional elements or only use in institute's column element some.
At this, device management command can be included in the message.In other words, this message can comprise at least one or more a plurality of device management command.If use message, then task element is specified this message.And, above-mentioned condition can be based on timer, based on trap or based on threshold value.Additional or the alternative basis of all right service condition.And the gating condition represents whether terminal (200) needs the report executing result after carrying out the DM order.
Simultaneously, may there be one or more scheduling ingredient in the scheduling context, and can has the binding logical relation between these scheduling ingredients.That is, scheduling ingredient can be (interworked) that acts on each other.For example, this " effect each other " can refer to that if satisfy the condition of first scheduling, then module (or other entities) is carried out the order of first scheduling ingredient, and stops the order of second scheduling ingredient.This is very useful for the scheduling based on threshold value, can carry out one or more composition respectively based on concrete threshold value by over-over mode thus.
The notion of " effect each other " can be applicable to dispatch context.That is to say that if the contextual first scheduling context of at least one or more a plurality of scheduling begins, then described at least one or the contextual second scheduling context of more a plurality of scheduling stop.
The scheduling context can be revised (promptly proofread and correct, change, modification etc.) as required by scheduler context manager module (111), or can ask this type of revision to terminal (200).And, scheduler context manager module (111) but the scheduling context installed of requesting terminal (200) deletion.
In addition, when the scheduling context of installing in the terminal (200) or reinstalling changes or mistake occurs, if perhaps the scheduling context state changes, then scheduler context manager module (111) can receive message (or other indications) and carry out its suitable processing from terminal (200).
Task element, Cond element have been described above, User Interaction element, Gating element, and the Event element is included in the situation in the scheduling ingredient.But, should be noted that as shown in Figure 3 these elements can directly be included in the scheduling context.
(2) feature of terminal
Terminal (200) can comprise DM scheduling enabler (210) and DM enabler (220).At this, will be understood that and also can use other similar hardware, software or its combination in any.
DM scheduling enabler (210) can comprise scheduling context installed module (211), condition matching module (212), DM command execution module (213), gating module and status report module (215).At this, will be understood that and also can use other similar hardware, software or its combination in any.
Scheduling context installed module (211) is and to carry out its suitably unit of processing (that is, partly, element etc., or its combination) from the request of installing of server (110) (that is, DM dispatch enabler (110)) receiving scheduling context.At this, the scheduling context can receive by DM enabler (220), can be delivered to scheduling context installed module (211) then.Scheduling context installed module (211) utilization scheduling context generates one or more node (or classification node of other types) in equipment control (DM) tree (or the hierarchy of other types or logical format) of using in the terminal (200).At this, the DM tree can be formed by general information nodes and one or more scheduling ingredient (equipment control of being dispatched).
Describe DM tree (promptly dispatch context form is installed) in detail with reference to Fig. 2.
Fig. 2 shows exemplary DM tree.More specifically, universal nodes (as shown in Figure 2) can comprise the Id node of the contextual identifier of scheduling that expression is installed, Name (title) node of the contextual title of expression scheduling, Valid (effectively) node of the contextual effectual time of expression scheduling, the contextual owner's of expression scheduling Server (server) node, State (state) node of the contextual current state of expression scheduling, and the StateOP node of the contextual State Control of expression scheduling.Can know to be understood that the title of these nodes and type only are exemplary.
At this, some examples of the contextual current state of scheduling that can be represented by the State node are as shown in the table.That is, the scheduling context can be one of following state: Stopped (stopping), Running (operation) or Suspended (time-out).Also have many other additional or alternative states.
| State | Describe |
| Stopped | The activity of scheduling context right and wrong.And, all right and wrong activities of included whole scheduling ingredients.The scheduling context of just having installed and having disposed and reconfigure can be in this state.The scheduling context can be converted to this state after despatching work is finished.Leave this state, the scheduling context starts from having each scheduling ingredient of himself original state. |
| Running | The scheduling context is movable.More specifically, at least one scheduling ingredient can be movable.If the neither one scheduling ingredient is movable, then dispatches context and must be automatically changeb to halted state. |
| Suspended | The activity of scheduling context right and wrong.Included whole scheduling ingredients are all kept their state.Leave this state, the scheduling context begins the state when it suspends to continue. |
Dispatching contextual state can be by server (100), by terminal (200) self, or changes (promptly revise, adjustment etc.) by the user of terminal (200).Can use various conditions to trigger this change.
For example, if when carrying out equipment control, or equipment control is when finishing, or carrying out mistake having occurred before any modification or the deletion owing to server (100) or user's request, then dispatches context and can change (promptly changing) to halted state.
The StateOP node can comprise Start (beginning) child node, Stop (stopping) child node, Suspend (time-out) child node and Resume (continuation) child node.Clearly, can use the additional of other types or alternative node.Describe these child nodes below in detail:
| Child node | Describe | The state of being suitable for |
| Start | This operation is used for beginning to dispatch context from original state, promptly dispatches context and begins to be set to the operation of assigning to of being scheduled to of initial value separately.If success is then dispatched context and is moved to running status. | Stopped |
| Stop | This operation is used to stop to dispatch context.If success then dispatch context and move to halted state, and included scheduling ingredient must become non-activity. | Running, Suspended |
| Suspend | This operation is used for suspending the contextual operation of scheduling.Specifically, during this state, the state of included scheduling ingredient must keep.If success is then dispatched context and is moved to halted state. | Running |
| Resume | This operation is used for continuing the traffic control context from time-out.If success is then dispatched context and is moved to running status. | Suspended |
Utilize each child node, can realize that (specify or carry out) is to dispatching the control of contextual state.In other words, if received execution (Exec) order (or order of other types) from server (100) in (or for) specific child node, then terminal (200) is carried out the Exec order so that the scheduling context change (changes) to receive the corresponding state of specific child node that Exec orders.
Like this, when the scheduling context changed its state according to the StateOP node, the state after this change can be reflected in the contextual State node of scheduling subsequently.
Scheduling ingredient can comprise with the next item down or multinomial: the Task node of expression DM order, specify the Condition node of the condition (or environment) of carrying out the DM order, specify mutual UI node with the user, specify the Gating node that whether result after the execution DM order should be reported to (or being notified to) server, whether expression should report the Event node of the state of (or notice) terminal to server, the State node of the current state (or situation) of expression scheduling ingredient, and InitState (original state) node of the original state of indication (or notice) scheduling ingredient.Clearly, can use the additional of other types or alternative node.
At this, the DM order is included in the message.Therefore, the Task node can be specified the message that comprises the DM order.Simultaneously, as mentioned above, Task node, Cond node, User Interaction node, Gating node, and the Event node is included in the scheduling ingredient.But, it should be noted that as shown in Figure 3 these elements can directly be included in the scheduling context.
The state of the scheduling ingredient that can be represented by the State node can change according to the contextual state of scheduling.That is,, then can enable scheduling ingredient according to the original state of representing by the InitState node if under the Running state, begin to dispatch context.And when the scheduling context was the Stopped state, scheduling ingredient can be changed into disabled state.When the scheduling context is the Suspended state, can keep this scheduling ingredient.After this, when the scheduling context continued, scheduling ingredient can be returned its Suspended state.Simultaneously, the state of a scheduling ingredient also can be owing to another scheduling ingredient changes.That is, first scheduling ingredient of described at least one or more a plurality of scheduling can make the second scheduling ingredient inertia of described at least one or more a plurality of scheduling when activity.This can be described as the effect each other of scheduling ingredient.
Owing to before the scheduling context is installed from the order of DM server (100), if desired, dispatch context installed module (211) and can optionally check scheduling contextual validity (or authenticity).
Condition matching module (212) be a kind of monitoring or the unit of checking the condition coupling that whether has execution in the scheduling ingredient (promptly, partly, element etc., or its combination), and when the condition of carrying out is mated, can send the request of carrying out with the corresponding DM order of these conditions to DM command execution module (213).At this, the condition of carrying out the DM order can be based on timer, based on trap, or based on threshold value.Also can use condition basis additional or alternative.
Specified the value of the cura specialis entity in the terminal (200) whether to reach pre-set threshold based on the step of threshold value.Therefore, carry out the value of condition matching module (212) monitoring (or inspection) the cura specialis entity of above-mentioned steps, itself and threshold value are compared, when reaching threshold value, can send the request of carrying out the DM order to DM command execution module (213).
In carrying out the condition matching module (212) of above-mentioned steps existence one or more scheduling ingredient (promptly, Equipment Management Function that has been scheduled or step), if and each scheduling ingredient all comprises with respect to the execution of the same cura specialis entity condition based on the step of threshold value, execution can act on respect to this cura specialis entity each other based on the condition of the step of threshold value, also can be monitored.
For example, we suppose that first scheduling ingredient (equipment control that promptly has been scheduled) and second scheduling ingredient (equipment control that promptly has been scheduled) are present in respectively in the scheduling context.And, we suppose that first scheduling ingredient comprises DM order and carries out first condition based on the step of threshold value with respect to the cura specialis entity, and second scheduling ingredient comprises the 2nd DM order and with respect to the execution second of the same cura specialis entity condition based on the step of threshold value.If like this, then, the value of cura specialis entity carries out first during based on the condition of the step of threshold value when satisfying, and condition matching module (212) request DM command execution module (213) is carried out DM order.And, when satisfying, the value of cura specialis entity carries out second during based on the condition of the step of threshold value, and condition matching module (212) request DM command execution module (213) is carried out the 2nd DM order.
Simultaneously, in order to monitor the condition of carrying out above-mentioned steps, may need the exectorial additional requirement of condition matching module (212).That is, in order to make condition matching module (212) fill order, the scheduling context can comprise how indication monitors the clause of executive condition (item).And the scheduling context can comprise the request (212) (coming fill order) for the condition matching module, and this request expression should still be monitored which measured value or variable randomly with specified time interval.
The unit that DM command execution module (213) if cooperate with DM enabler (220) when being a kind of condition coupling that exist to carry out the DM order is ordered with execution DM (, partly, element etc., or its combination).In other words, DM command execution module (213) sends the DM order to DM enabler (220), and receives by carrying out the result that the DM order obtains from DM enabler (220).
When carrying out the DM order, gating module (214) is a kind of unit that determines whether the status report of the execution result that occurs or terminal (200) is given DM server (100) (that is, partly, element etc., or its combination).As mentioned above, gating module (214) can determine whether the result of report executing order according to the Gating node.Alternatively, gating module (214) can determine whether report condition based on the Event node.
Status report module (215) is a kind of to the state of DM server (100) reporting terminal (200) or the unit of execution result.As mentioned above, when the state of contextual state of scheduling or scheduling ingredient changed, status report module (215) can be reported to DM server (100).And, as the result who carries out the DM order, need report by gating module (214) if think, then status report module (215) utilizes DM command execution results (that is, Status (state) message, Result (result) message or Alert (warning) message) to generate the report message that can send to DM server (100).At this, can utilize the message of general warning message or other types or the state of indicating to send to DM server (100) with report message or terminal (200).
DM enabler (220) is a kind of the cooperation with command execution module (213) to carry out the unit of DM order.More specifically, DM enabler (220) is carried out the DM order that receives from command execution module (214), then its result is returned (that is 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), and have DM scheduling enabler (210) terminal (200) of (comprising scheduling context installed module (211), condition matching module (212), DM command execution module (213), gating module (214) and status report module (215)), and DM enabler (220) has been described the formation element of DM of the present invention system.Yet these elements also can be realized by the combination in any of processor (not shown), network interface (not shown) and memory device (not shown).
The feature of the method according to this invention
The operation of DM of the present invention system is described with reference to Fig. 4 and Fig. 5 below.Do not have the details of the whole elements of depicted in greater detail although it should be understood that Fig. 4 and Fig. 5, each step all can usually be carried out by above-mentioned DM server (100) and each yuan in the terminal (200).
Fig. 4 is the process flow diagram that illustrates according to scheduling context installation steps of the present invention, and Fig. 5 is the process flow diagram that illustrates according to the method for operation dispatching equipment control of the present invention.
As shown in Figure 4, in installation steps of the present invention, DM server (100) is set up the DM session (or communication link of some other types) with DM enabler (220), and this scheduling context is installed.
To describe example schedule context installation steps of the present invention below in detail.
1) DM server (100) (specifically, being its scheduler context manager module (111)) generates (or establishment) scheduling context.
2) the DM session of DM server (100) foundation and terminal (200), and utilize DM agreement (or other suitable communication protocols) to send the contextual request of scheduling (or instruction) that installation generates to the DM scheduling enabler (210) of terminal (200).At this, request can be delivered to DM scheduling enabler (210) by DM enabler (220).
3) DM of terminal (200) scheduling enabler (210) (specifically, being its scheduling context installed module (211)) is checked the contextual validity of scheduling.
4) after validity check is finished, the DM scheduling enabler (210) (specifically, being its scheduling context installed module (211)) of terminal (200) will be dispatched context and be installed in the DM tree (or the hierarchy of other types or logical format) of terminal (200).At this, Fig. 2 shows the example of aforesaid DM tree.
5) finish when installing, the knot that the DM of terminal (200) scheduling enabler (210) (specifically, being its scheduling context installed module (211)) will be dispatched the context installation reports to DM server (100).
With reference to Fig. 5 example schedule composition disposal route of the present invention is described below.
1) the condition node that representative scheduling context is installed in DM scheduling enabler (210) (specifically, being its condition matching module (212)) the inspection DM tree, and monitor the coupling that whether exists with its executive condition.At this, this condition can be based on timer, based on trap, or based on threshold value.Also can use other conditions additional or alternative.
2) according to this monitoring, if confirm to exist the coupling of executive condition, then DM scheduling enabler (210) (specifically, being its DM command execution module (213)) is cooperated with DM enabler (220) to carry out the DM order.
3) when finishing the execution of DM order, DM scheduling enabler (210) (specifically, being its gating module (214)) determines whether the result of command execution is sent to DM server (100).
4) determine according to this that DM scheduling enabler (210) (specifically, being its status report module (215)) is given DM server (100) with the status report of execution result or terminal (200).That is, can notify DM server (100) DM order whether to obtain suitably carrying out to the report of execution result, or the reason that makes a mistake.This reporting step can utilize execution result to create report message (or indication of some other types), can send to DM server (100) subsequently.
When 5) receiving status report, DM server (100) (specifically, being its status report processing module (112)) is resolved (or other processing) to the status report that receives.
Fig. 6 shows the exemplary method of carrying out based on the equipment control of threshold value, and Fig. 7 shows the exemplary method of carrying out based on the equipment control of trap.
As shown in Figure 6, the scheduling context can comprise two scheduling ingredients.More detailed, if the value of cura specialis entity for example, surpasses 1 if work as the threshold value of the wave point entity with stable throughput, then dispatch contextual first scheduling ingredient (that is the equipment control of, being dispatched) and allow to carry out the DM order that variable " foo " is become " bar ".And,, then dispatch contextual second scheduling ingredient and allow to carry out the DM order that variable " bar " is become " foo " if the value of cura specialis entity becomes steady state (SS) again.And because hypothesis, the handling capacity that first and second scheduling ingredients can be ignored particular wireless interface exceeds threshold value 1 but follows the situation of threshold value below 1 that fall back, if this gap is considered to less relatively (that is, interior if drop on hypothesis (permission) scope).This is in order to get rid of the unsettled reason of system that noise (or other disturb) causes.
The exemplary execution procedure of first and second compositions will be described below.
(1) first composition and second composition change to activity (or enabling) state and are performed from original state.
(2), then carry out the DM order of first scheduling ingredient if the handling capacity of particular radio (wireless) interfacing equipment surpasses threshold value 1.
(3) carried out this DM order after, variable " foo " becomes " bar ", first scheduling ingredient becomes non-activity (or forbidden energy), and carries out the second scheduling composition.
(4), then carry out the DM order of second scheduling ingredient if the handling capacity of particular radio (wireless) interfacing equipment is reduced to threshold value below 2.
(5) carry out this DM order after, variable " bar " becomes " foo ", second scheduling ingredient becomes non-activity (or forbidden energy), and carries out first scheduling ingredient.
Fig. 7 shows the scheduling context (that is the equipment control of, being dispatched) that comprises two scheduling ingredients.More detailed, dispatching that contextual first scheduling ingredient allows when generation incident 1 the terminal operation mode initialization is emergency mode, and carries out second scheduling ingredient.Dispatch contextual second scheduling ingredient and periodically check whether there is abnormality,, then allow terminal to return its normal mode from emergency mode if removed (or solution) abnormality.
The exemplary execution procedure of first and second scheduling ingredients is as described below.
(1) when the scheduling context was installed, second composition became non-activity (or forbidden energy) state from its original state, and first scheduling ingredient becomes activity or enabled state and is performed from its original state.
(2) when particular event 1 takes place, carry out the DM order of first scheduling ingredient.
(3) after the execution DM order, the terminal operation pattern becomes emergency mode, and first scheduling ingredient becomes non-activity (or forbidden energy), and second scheduling ingredient becomes activity (or enabling).
(4) when second scheduling ingredient becomes active state and is performed, second scheduling ingredient checks whether the state of terminal is normal, checks that herein carry out (for example per 10 minutes) in a periodic manner.
When (5) carrying out this periodic test, be normal if find the state of terminal, the DM that then carries out second composition orders.
(6) when carrying out the DM order, the terminal operation pattern becomes normal condition from the emergency circumstance, and second scheduling ingredient is by forbidden energy, and first scheduling ingredient is enabled.
Method of the present invention can be embodied as software, hardware, or its combination in any.For example, method of the present invention can be embodied as code or the instruction in the software program that is stored in the storage medium (for example internal storage of terminal, flash memory, hard disk etc.) and is carried out by processor (for example microprocessor in the terminal).
In order to reach effect of the present invention, by the DM order that will carry out in terminal and the condition of carrying out these DM orders (being included in the scheduling context) are provided to terminal (shifting to an earlier date), and make terminal carry out these DM orders according to these conditions, the result will be no matter when terminal to DM server requests DM order, terminal all with these command recognition for seeming to provide from the DM server immediately.
And,, can appear at the mistake in the terminal so can prevent (or minimizing at least) effectively because the present invention allows to carry out the DM order according to certain threshold level.
In addition, by comprising one or more scheduling ingredient in the context, and allow, can carry out the DM order, more effectively handle thus according to the mode of system more according to certain threshold level operation dispatching composition respectively in an alternating manner based on threshold value in scheduling.
It should be understood that feature of the present invention and notion relate to various device management (DM) standard of being controlled by some respective standard tissue.Therefore, the various respective standard of appointment herein and/or notion also are parts of the present invention.
Although the present invention has specified the various titles of the order that relates to equipment control (DM), node, child node etc., can know to be understood that these titles and label only are exemplary.Therefore feature of the present invention is not restricted, because can use other title of equal value or labels, as long as they refer to function identical or of equal value and/or feature.
Any quoting of " embodiment ", " embodiment ", " illustrative embodiments " etc. all is meant comprises at least one embodiment of the present invention and finishing should special characteristic, structure or the characteristic that embodiment is described among the present invention.This type of word that occurs among the present invention might not refer to identical embodiment.In addition, when describing special characteristic, structure or characteristic, suppose that those skilled in the art can realize these features, structure or characteristic in conjunction with other embodiments in conjunction with any embodiment.
Although described the present invention in conjunction with illustrative embodiments, what it should be understood that is a plurality of other modifications and the embodiment that can be designed the scope that falls into principle of the present invention by those skilled in the art.More specifically, in the scope of the disclosure, accompanying drawing and appended claim, can there be variations and modifications in the arrangement of ingredient and/or object assembled arrangement.Except the variation and modification of ingredient and/or arrangement, those skilled in the art thought the application mode of alternative easily.
Claims (29)
1. the terminal of an equipment control of being dispatched, this terminal comprises:
First module, be suitable for receive the scheduling context from server after, this scheduling context being installed, this scheduling context comprises at least one scheduling ingredient of general information and the equipment control that is used to be dispatched, and wherein this general information comprises about representing this first node of dispatching contextual current state and relate to control that this dispatches the information of the Section Point of contextual state; And
Second module, the equipment control of being dispatched carried out in the scheduling context that is suitable for installing according to first module.
2. terminal according to claim 1, wherein this scheduling context is to install with the form of the device management tree of the equipment control that is used to be dispatched, this device management tree has the node and the child node of classification relationship.
3. terminal according to claim 1, wherein this general information also comprises following at least one:
This dispatches contextual identifier;
This dispatches contextual title;
This dispatches contextual respective server; And
This dispatches the contextual term of validity.
4. terminal according to claim 3 is if if wherein the contextual term of validity of this scheduling is included in the described general information and this expiration of licence, then delete this scheduling context automatically.
5. terminal according to claim 1, wherein the contextual state of this scheduling is to stop, moving and one of suspend.
6. terminal according to claim 1, wherein when this scheduling context was installed, this scheduling context was in halted state.
7. terminal according to claim 1, if wherein when the equipment control of being dispatched, when the equipment control of being dispatched is finished or based on from this server or user's request and make amendment or delete before mistake has taken place, this scheduling context is converted to halted state.
8. terminal according to claim 1, wherein the contextual state of this scheduling can be changed by the user.
9. terminal according to claim 1, wherein Section Point comprises at least one in enable node and the forbidden energy node.
10. terminal according to claim 1, wherein Section Point comprises at least one in start node, Stop node, time-out node and the continuation node.
11. terminal according to claim 10, wherein this start node, Stop node, time-out node and continuation node are triggered by fill order.
12. terminal according to claim 1, if the scheduling context existence of wherein being installed changes, then first module sends message to this server.
13. terminal according to claim 1, wherein
This scheduling context also comprises about following at least one information: specify the mutual user interactions node with the user; Whether specify should be to the result's of this server report executing device management command gating node; And the event node that indicates whether to report to this server event in the state of this terminal or this terminal;
The management object that is used for described equipment control of being dispatched comprises the message with at least one device management command, and comprises the condition of carrying out this order.
14. terminal according to claim 1, wherein said scheduling context and different scheduling context interactions.
15. terminal according to claim 14, wherein
If described second module begins described scheduling context, then described second module stops described different scheduling context.
16. the server of an equipment control of being dispatched, this server comprises:
The device management scheduling enabler, this device management scheduling enabler comprises:
Be suitable for generating at least one or the contextual module of more a plurality of scheduling, each scheduling context all comprises general information and at least one or more a plurality of management object of the equipment control that is used to be dispatched; And
Thereby be suitable for the requesting terminal described at least one or more a plurality of scheduling context carry out the equipment control of being dispatched in this terminal module is installed,
Wherein this general information comprise about represent this dispatch the first node of contextual state and relate to control this dispatch the information of the Section Point of contextual state.
17. server according to claim 16, wherein Section Point comprises at least one in enable node and the forbidden energy node.
18. server according to claim 16, wherein Section Point comprises at least one in start node, Stop node, time-out node and the continuation node.
19. server according to claim 18, wherein fill order is sent at least one in this start node, Stop node, time-out node and the continuation node, to change the contextual state of scheduling in this terminal.
20. server according to claim 19, wherein
This server also comprises the module of event from the result of the contextual state-transition of this terminal receiving scheduling or this terminal.
21. the method for an equipment control of being dispatched in end, this method may further comprise the steps:
Receiving step, receive the contextual request of scheduling of installing from server, this scheduling context comprises one or more management object of general information and the equipment control that is used to be dispatched, and wherein this general information comprises about representing that this dispatches the first node of contextual state and relate to control that this dispatches the information of the Section Point of contextual state;
Installation steps are installed this scheduling context according to the request that receives; And
The step of the equipment control that execution is dispatched is carried out the equipment control of being dispatched according to the scheduling context of being installed.
22. method according to claim 21, this method is further comprising the steps of:
If when the equipment control of being dispatched, when the equipment control of being dispatched is finished, perhaps based on from this server or user's request and make amendment or delete before mistake has taken place, then stop this scheduling context.
23. method according to claim 21, this method is further comprising the steps of:
If the scheduling context existence of being installed changes,, then send message to this server if perhaps in this terminal particular event has taken place.
24. method according to claim 21, the step of wherein carrying out the equipment control of being dispatched comprises:
Begin described scheduling context; And
Carry out the equipment control of being dispatched according to described scheduling context.
25. method according to claim 24, wherein
Stop different scheduling contexts in response to the contextual beginning of described scheduling.
26. method according to claim 21, the step of wherein carrying out the equipment control of being dispatched also comprises:
Begin this scheduling context;
Suspend the contextual request of described scheduling if received, then suspend this scheduling context; And
Continue the contextual request of described scheduling if received, then continue this scheduling context.
27. method according to claim 21, described receiving step:
In the beginning child node of the device management tree that comprises state node and child node by hierarchical relationship, stop child node, suspend child node and continue that any one place carries out described receiving step in the child node, and the request that receives comprises fill order; And
The step of the equipment control that described execution is dispatched comprise by receive described exectorial described beginning child node, described at least one that stops in child node, described time-out child node and the described continuation child node carrying out that described fill order begins, stops, suspending or continue in the described scheduling context in any one place operated.
28. method according to claim 27, this method is further comprising the steps of:
The contextual current state of the described scheduling of reflection in described state node.
29. method according to claim 28, the state of wherein said state node are a kind of in the middle of running status, halted state and the halted state.
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 | ||
| KR10-2006-0043155 | 2006-05-12 | ||
| KR20060043155 | 2006-05-12 | ||
| KR1020060043155 | 2006-05-12 | ||
| KR10-2007-0005821 | 2007-01-18 | ||
| KR1020070005821 | 2007-01-18 | ||
| KR1020070005821A KR101342372B1 (en) | 2006-01-23 | 2007-01-18 | Terminal and method for pefforming scheduled device managemnt thereof |
| PCT/KR2007/000377 WO2007083971A1 (en) | 2006-01-23 | 2007-01-22 | Device management scheduling method and apparatus thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101371235A CN101371235A (en) | 2009-02-18 |
| CN101371235B true CN101371235B (en) | 2010-09-15 |
Family
ID=40414019
Family Applications (3)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007800028823A Expired - Fee Related CN101371236B (en) | 2006-01-23 | 2007-01-22 | Terminal and method for performing device management scheduled based on threshold |
| CN2007800029582A Expired - Fee Related CN101371243B (en) | 2006-01-23 | 2007-01-22 | Performing scheduled device management |
| CN2007800028043A Expired - Fee Related CN101371235B (en) | 2006-01-23 | 2007-01-22 | Device management scheduling method and apparatus thereof |
Family Applications Before (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007800028823A Expired - Fee Related CN101371236B (en) | 2006-01-23 | 2007-01-22 | Terminal and method for performing device management scheduled based on threshold |
| CN2007800029582A Expired - Fee Related CN101371243B (en) | 2006-01-23 | 2007-01-22 | Performing scheduled device management |
Country Status (1)
| Country | Link |
|---|---|
| CN (3) | CN101371236B (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 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1041768A2 (en) * | 1999-04-01 | 2000-10-04 | Seiko Epson Corporation | Device management network system, management server, and computer |
| CN1547120A (en) * | 2003-12-10 | 2004-11-17 | 沈阳东软软件股份有限公司 | Network monitoring management system |
| CN1549501A (en) * | 2003-05-13 | 2004-11-24 | 中兴通讯股份有限公司 | Distributed central management method for special shaped network equipment in distributing network environment |
| CN1635740A (en) * | 2003-12-26 | 2005-07-06 | 华为技术有限公司 | Application distributed network management system and method |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| KR20050046932A (en) * | 2003-11-14 | 2005-05-19 | 삼성전자주식회사 | System for checking state of slave devices using i2c bus |
-
2007
- 2007-01-22 CN CN2007800028823A patent/CN101371236B/en not_active Expired - Fee Related
- 2007-01-22 CN CN2007800029582A patent/CN101371243B/en not_active Expired - Fee Related
- 2007-01-22 CN CN2007800028043A patent/CN101371235B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1041768A2 (en) * | 1999-04-01 | 2000-10-04 | Seiko Epson Corporation | Device management network system, management server, and computer |
| CN1549501A (en) * | 2003-05-13 | 2004-11-24 | 中兴通讯股份有限公司 | Distributed central management method for special shaped network equipment in distributing network environment |
| CN1547120A (en) * | 2003-12-10 | 2004-11-17 | 沈阳东软软件股份有限公司 | Network monitoring management system |
| CN1635740A (en) * | 2003-12-26 | 2005-07-06 | 华为技术有限公司 | Application distributed network management system and method |
Non-Patent Citations (2)
| Title |
|---|
| JP 特开2004-5170 A,全文. |
| JP特开2000-347976A 2000.12.15 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101371236A (en) | 2009-02-18 |
| CN101371243A (en) | 2009-02-18 |
| CN101371243B (en) | 2011-04-27 |
| CN101371236B (en) | 2012-05-23 |
| CN101371235A (en) | 2009-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109408210B (en) | Distributed timed task management method and system | |
| US10212055B2 (en) | System and method for dynamically grouping devices based on present device conditions | |
| CN106549829B (en) | Big data computing platform monitoring system and method | |
| EP1962538B1 (en) | Method for managing terminal device | |
| US6782408B1 (en) | Controlling a number of instances of an application running in a computing environment | |
| CN111552556B (en) | GPU cluster service management system and method | |
| CN101375266B (en) | Based on the device management scheduling of trap mechanism | |
| US20070198554A1 (en) | Apparatus for business service oriented management infrastructure | |
| WO2006058090A2 (en) | Message management facility for an industrial process control environment | |
| CN109067597A (en) | A kind of distributed system dynamic and intelligent service administering method | |
| CN101778004B (en) | Terminal and method for performing device management scheduled based on threshold thereof | |
| US20100122119A1 (en) | Method to manage performance monitoring and problem determination in context of service | |
| CN101095089A (en) | Transparent relocation of an active redundant engine in supervisory process control data acquisition systems | |
| CN104598300A (en) | Distributive business process customization method and system | |
| Keller et al. | Automating the provisioning of application services with the BPEL4WS workflow language | |
| CN108037984B (en) | Resource management method, system and readable storage medium for data analysis | |
| EP2492805A1 (en) | Computer network, computer system, computer-implemented method, and computer program product for controlling application landscapes | |
| EP4024761A1 (en) | Communication method and apparatus for multiple management domains | |
| CN101371235B (en) | Device management scheduling method and apparatus thereof | |
| CN110798339A (en) | Task disaster tolerance method based on distributed task scheduling framework | |
| US7793301B2 (en) | Method and system for providing efficient object-based network management | |
| CN105589788B (en) | Monitoring system | |
| CN104010008A (en) | Method for controlling mass invalid access to server | |
| JP5530878B2 (en) | Data replication management method in distributed system | |
| CN101371242B (en) | Method for interacting with user and terminal thereof |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100915 Termination date: 20170122 |