CN101371243B - Performing scheduled device management - Google Patents
Performing scheduled device management Download PDFInfo
- Publication number
- CN101371243B CN101371243B CN2007800029582A CN200780002958A CN101371243B CN 101371243 B CN101371243 B CN 101371243B CN 2007800029582 A CN2007800029582 A CN 2007800029582A CN 200780002958 A CN200780002958 A CN 200780002958A CN 101371243 B CN101371243 B CN 101371243B
- Authority
- CN
- China
- Prior art keywords
- node
- server
- condition
- value
- 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.)
- Expired - Fee Related
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 operation dispatching equipment control (scheduled device management).
Background technology
In general, equipment control (DM:Device Management) technology relates to equipment control (DM) server (or other network entities) and shows that (or indication) goes out to be positioned at the resource of the equipment control as management object (DM) client (being terminal or other subscriber equipmenies) on equipment control (DM) tree hierarchical structure or the logical format of the other types of equipment control (or be used for), permission conducts interviews to this resource, and allows the DM server like a cork terminal to be managed.
In this class DM technology, the DM server can the administration order of indicating terminal treatment facility, and the terminal of being managed can be to the result of DM server report executing after carrying out corresponding order immediately.And the DM server can the requesting terminal changes, upgrades, deletion or the concrete function of treatment facility management otherwise.
One aspect of the present invention is by the understanding of inventor to the following defective in some DM technology.That is, in some DM technology, have only when existence in the terminal is wrong or unusual, terminal is just ordered to DM server requests DM.Thus, the diagnostic procedure of terminal makes expense very big, and because not expectability or discovery before these problems take place, so this diagnostic procedure can't solve diagnosis problem effectively.
Summary of the invention
Thus, in order to address the above problem, the invention provides a kind of terminal, this terminal can be before potential problem takes place from administration order of server receiving equipment and the condition of carrying out described order, monitor whether to satisfy this condition, and if condition satisfy then the actuating equipment administration order.
Description of drawings
Each feature according to exemplary embodiment of the present invention has been shown in the accompanying drawing, wherein:
Fig. 1 shows equipment control (DM) terminal and equipment control (DM) server.
Fig. 2 is the process flow diagram of an example of terminal diagnostics method.
Fig. 3 is the process flow diagram of an example of the method for operation dispatching equipment control.
Fig. 4 illustrates figure according to the dispatch environment of first embodiment of the invention with an exemplary tree structure.
Fig. 5 illustrates figure according to the diagnosis management object of first embodiment of the invention with an exemplary tree structure.
Fig. 6 illustrates figure according to the management and running object of second embodiment of the invention with an exemplary tree structure.
Fig. 7 is the figure that the diagnosis management object that is connected to management and running object shown in Figure 6 is shown with an exemplary tree structure.
Fig. 8 is the figure that the diagnosis management object of the 3rd exemplary embodiment according to the present invention is shown with an exemplary tree structure.
Fig. 9 is the figure that the dispatch environment that is connected to diagnosis management object shown in Figure 8 is shown with an exemplary tree structure.
Figure 10 illustrates figure according to the dispatch environment of four embodiment of the invention and diagnosis management object with an exemplary tree structure.
Figure 11 illustrates figure according to the dispatch environment of fifth embodiment of the invention and diagnosis management object with an exemplary tree structure.
Embodiment
As shown in Figure 1, the DM system of exemplary embodiment comprises DM server 100 and terminal 200 according to the present invention.Can expect, can also implement server, network entity of other types etc.Terminal can be user's set, subscriber equipment (UE), portable terminal, customer set up etc.
DM scheduling enabler server 110 can comprise dispatch environment (scheduling context) administration module 111 (comprising hardware, software or its combination in any) and status report processing module 112 (comprising hardware, software or its combination in any).Be appreciated that in the DM scheduling enabler server 110 and can have entity and key element additional and/or alternative.
Dispatch environment administration module 111 can generate dispatch environment (i.e. the summary of using when the actuating equipment management and dispatching, basis, framework etc.) and this dispatch environment is installed in requesting terminal 200.Dispatch environment administration module 111 can be set up the DM session with terminal 200, and by the DM conversation request terminal of setting up 200 dispatch environment that is generated is installed.
Dispatch environment can comprise at least one in following: regulation comprises the task element (for example first element) of the message of at least one device management command (or instruction), and the condition element (for example second element) of rated condition (key element, environment etc.).Described condition can be at least one in following: based on the condition of timer, based on the condition of trap and based on the condition of threshold value.Here, those skilled in the art can be interpreted as the scheme based on condition (that is, particular event makes hardware, software (being operating system) or their combination with ad hoc fashion work) that is meant certain type with term " trap (trap) " (as using in trap item, the trap mechanism etc.).In addition, as shown in Figure 4, dispatch environment can also comprise additional information, will be described in detail this below.
Status report processing module 112 can be from terminal 200 receiving state reports (for example, the result who obtains from fill order, or the result who obtains from diagnosis and monitoring terminal 200), and this status report is handled.
As shown in the figure, terminal 200 can comprise DM scheduling enabler client 210, DM enabler client 220 and diagnostic monitoring enabler client 230.Be understandable that, can have entity or key element additional and/or alternative in the terminal 200.
DM scheduling enabler client 210 can be included in the first entity 210a that this dispatch environment is installed when server 100 receives dispatch environment, and the second entity 210b of actuating equipment administration order.Be understandable that, can have entity and key element additional and/or alternative in the DM scheduling enabler client 210.
The first entity 210a can comprise dispatch environment installed module 211.Dispatch environment installed module 211 is handled from the dispatch environment of DM server 100 request is installed.That is, dispatch environment installed module 211 can be installed dispatch environment by the form (or other are used for the hierarchical structure or the logical format of equipment control) of DM tree.
Here, dispatch environment installed module 211 can be carried out the process of replenishing and to handle this dispatch environment request is installed.For example, dispatch environment installed module 211 request diagnostic monitoring enabler client 230 are circulated a notice of when particular event has taken place.
Dispatch environment installed module 211 can optionally be verified the validity of this dispatch environment before dispatch environment is installed.
The second entity 210b can comprise condition matching module 212, task execution module 213 and status report module 214.Be understandable that and have entity and key element additional and/or alternative among the second entity 210b.
Whether condition matching module 212 can mate by guard condition, and if coupling, then this condition matching module 212 can ask task execution module 213 to carry out the order corresponding with this condition.If this condition is corresponding to the condition based on trap, then condition matching module 212 has been circulated a notice of decision condition coupling under the situation of generation of particular event in diagnostic monitoring enabler client 230.
When exectorial condition was judged as coupling, task execution module 213 can be cooperated so that can fill order with DM enabler client 220.
And DM enabler client 220 is set up session with DM server 100 so that DM scheduling enabler client 210 is communicated by letter with DM server 100.In addition, DM enabler client 220 receives diagnosis management object 232, and should diagnose management object to be delivered to diagnostic monitoring enabler client 230.
Simultaneously, diagnostic monitoring enabler client 230 comprises diagnostic monitoring agency 231 and diagnosis management object 232.
As mentioned above, DM server 100 can comprise DM scheduling enabler server 110 and DM enabler server 120, and terminal 200 can comprise DM scheduling enabler client 210, DM enabler client 220, diagnostic monitoring enabler client 230.Yet, can construct server 100 or terminal 200 by processor (not shown), network interface (not shown) and memory storage (not shown) are carried out combination with one another.Here, be understandable that and use other similar hardware, software or its combination in any.
Operation
Describe according to the terminal of exemplary embodiment and the operation of DM server to Fig. 3 referring now to Fig. 2.Although Fig. 2 does not at length illustrate all key elements to Fig. 3, be appreciated that each operation each corresponding key element execution by DM server 100 and terminal 200.
Fig. 2 is the process flow diagram of an example of terminal diagnostics method.
As shown in the figure, DM server 100 provides device management command and the exectorial condition that will carry out in terminal 200 to terminal 200.Then, if determine condition coupling, then terminal 200 fill orders.Therefore, terminal 200 is recognized: as long as terminal 200 requires order, DM server 100 will provide device management command immediately.
1) DM server 100 (specifically, the diagnostic monitoring server 130) is created the diagnosis management object.
2) DM server 100 is set up the DM session with terminal 200, and sends the diagnosis management object of being created to terminal 200.
3) then, terminal 200 (specifically, the DM enabler client 220) receives the diagnosis management object and sends this diagnosis management object to diagnostic monitoring agency 231.
4) diagnostic monitoring agency 231 configuration diagnostics management object in terminal 200.
5) after this, DM server 110 sends the order that activates the diagnosis management object to terminal 200.
6) then, terminal 200 (specifically, the DM enabler client 220) receives order.And DM enabler client 220 is carried out this order.
7) as to exectorial response, activate the diagnosis management object.
8) diagnostic monitoring agency 231 begins terminal 200 is diagnosed or monitored.Here, collection and hardware, core dump (memory dump), mistake, the code that makes the mistake, one or more the information that application program is relevant.
9) diagnostic monitoring agency 231 sends result to the diagnosis or the supervision of terminal 200 to DM enabler client 220.
10) then, DM enabler client 220 sends the result to DM server 100.
Fig. 3 is the process flow diagram of an example that carries out the method for scheduling device management.
As shown in Figure 3, DM server 100 bases are created dispatch environment to the diagnosis of terminal 200 and the result of supervision, and send the request that dispatch environment is installed.
Each step of processing procedure is as follows.
Step 1)～10) similar with step shown in Figure 2, therefore omitted description to same steps as for avoid obscuring the present invention meaninglessly.
11) DM server 100 (specifically, the dispatch environment administration module 111) is according to dispatch environment is created in the diagnosis of terminal 200 or the result of supervision.That is, DM server 100 (specifically, dispatch environment administration module 111) is created dispatch environment with according to the problem that will run in future that found that to the diagnosis of terminal 200 or supervision, and solves this type of problem.
12) DM server 100 utilizes DM agreement request terminal 200 that the DM dispatch environment that is generated is installed.
13) then, the DM enabler client 220 of terminal 200 is sent this dispatch environment to DM scheduling enabler client 210.
14) DM scheduling enabler client 210 (specifically, the dispatch environment installed module 211) is handled the request of installation.
15) subsequently, DM scheduling enabler client 210 (specifically, the dispatch environment installed module 211) request diagnostic monitoring agency 231 circulates a notice of when particular event takes place.In this case, can send this request by registration message.
16) in response to this request, this diagnosis management object 232 of diagnostic monitoring agency 231 registrations.
17) diagnostic monitoring agency 231 finishes to the 210 circular registrations of DM scheduling enabler client.Can realize this circular by sending affirmation (ACK) message to DM scheduling enabler client 210.
18) after receiving ACK message, DM scheduling enabler client 210 is to the 100 circular dispatch environment installations of DM server.Can realize this circular by sending ACK message to DM server 100.
19)～20), after this, if capture the generation of particular event, then diagnostic monitoring agency 231 is to 210 these generations of circular of DM scheduling enabler client.
21) then, DM scheduling enabler client 210 (specifically, the condition matching module 212) judges whether the particular event that takes place can satisfy condition.If satisfy condition, the device management command in the condition matching module 212 request task execution module 213 operation dispatching environment then.
22) if finish execution, then the status report module 214 of DM scheduling enabler client 210 is to the result of DM server 100 report executing orders.
23) then, DM server 100 (specifically, the status report processing module 112 of DM scheduling enabler server 110) receives report, and this report is resolved.
Exemplary method has more than been described.Being understandable that described method can make up by software, hardware or its realizes.For example, described method can be stored in the storage medium (being the internal storage, flash memory, hard disk etc. of portable terminal), or can be implemented as code or command language in the software program that can be carried out by processor (for example internal microprocessor of portable terminal).
Dispatch environment
Fig. 4 is the figure that dispatch environment is shown with an exemplary tree structure (point of node in the hierarchical structure or other types, placeholder etc.).
As shown in Figure 4, dispatch environment can comprise overall information part and scheduling part.
The overall information part can comprise Valid (effectively) node of the term of validity of the ID node of the identifier of representing dispatch environment, Name (title) node of representing the title of dispatch environment, regulation dispatch environment, expression dispatch environment owner's Server (server) node, State (state) node of expression dispatch environment state and state operation (state of operation) node (or StateOP node) of control dispatch environment state.The node that the additional or alternative of other types clearly, also can be arranged.
This scheduling part can comprise following in one or more multinomial: regulation comprises that Cond (condition) node (being Section Point) of Task (task) node (being first node), the exectorial condition of regulation of the message of at least one device management command and regulation whether should be to Reporting (report) nodes (i.e. the 3rd node) of the state of the result of server report executing order and dispatch environment.
The Cond node can comprise at least one in following: regulation based on Timer (timer) node of the condition of timer, regulation based on Trap (trap) node of the condition (that is, whether particular event taking place) of trap and regulation Th (threshold value) node based on the condition (whether the value that is the specific management object in the terminal reaches threshold value) of threshold value.
At first, this Timer node can the stipulated time, duration, cycle, a set point at interval.This Timer node can comprise Base (basis) node of regulation with the time point of expressed intact formal representation, and has stipulated whether round-robin cycline rule (RRule) node of condition.Therefore, if regulation circulation in the RRule regular node then can be forbidden condition based on timer after once in command execution.
And the Trap node can comprise the trap reference mode (TrapRef node or identifier) of the identifier of regulation particular event.
Th node as shown in Figure 4 comprises at least one in following: Address (address) node of the address of regulation management object, Interval (at interval) node at the interval of the value of regulation monitor management object, the Threshold of defined threshold (threshold value) node, the form of defined threshold is boolean (bool), character type, integer, floating type, date, or the ThFormat node of time, the type of defining node is the ThType node of absolute value or variate-value, defined threshold is to rise, descend or static Direction (direction) node, and the hysteresis of the tolerance limit of defined threshold (Hyst) node.
And the Address node comprises at least one in following: the URI node of the unified resource identifier (URI) of regulation management object, the MOI node of regulation management object identifier (MOI) and owing to have MOIfilter (MOI filtrator) node that the management object coexistence of identical MOI is given for the additional information that appointment management object and other management objects are distinguished under the situation of using the MOI node.
If there is no MOI node, then the URI node can be stipulated full address.Yet if there is the MOI node, the URI node can be stipulated the relative address with respect to the root of management object so.
Specifically, the MOIfilter node comprises in following at least one: URI node, Value (value) node and Format (form) node.
The URI node that is included in the MOIfilter node has stipulated to specify the unified resource identifier (URI) of management object with respect to the root of management object.
Be included in Value node in the MOIfilter node and stipulated and the value of comparing by the value of the appointment management object of the URI node indication of MOIfilter node, with under the situation that has a more than management object with identical management object identifier (MOI) to specifying management object and other management objects to distinguish.If there is the URI node that is contained in the MOIfilter node, then the value in the Value node can compare with the value of URI.Yet, if there is no being contained in the URI node in the MOIfilter node, the value in the Value node can claim with the root name of management object to compare so.
Be contained in the form of the value in the Format node regulation Value node in the MOIfilter node.Possible form is ' b64 ', ' bin ', ' bool ', ' int ', ' xml ', ' date ', ' time ' or ' floating-point '.If there is no the Format node can think that so the form of Value node is a character type.
Simultaneously, Threshold node defined threshold, and the value of Threshold node is the digital text string of the threshold value of the various forms of expression.The actual format of threshold value is determined by the ThFormat node.The sampling statistics of selected management object will compare with the value of Threshold node.But, if current sampled value is first sampled value (for example restarting the back scheduling operation at power supply just starts), and if do not have previous sampling, then do not consider last sampling.
The actual format of ThFormat node defined threshold and hysteresis.The probable value of ThFormat node is ' bool ', ' chr ', ' int ', ' date ', ' time ' or ' floating-point '.
ThType node defined threshold type.The probable value of ThType node is ' absolute value ' or ' changing (delta) value '.If described value is ' absolute value ', then the sampled value of management object compares direct and threshold value.If described value is ' changing value ', will from current sampled value, deducts the sampled value of last sampling, and this difference and described threshold value will be compared.
The behavior that value when Direction node regulation threshold of generation is handed over (threshold crossing) incident changes.Possible values is ' rising ', ' decline ' or ' static state '.Static threshold is meant occurrence condition coupling when sampled value equals threshold value, and does not consider the direction that threshold is handed over.When this threshold value is the rising threshold value, if current sampled value more than or equal to this threshold value, and if last sampling single condition coupling takes place during less than this threshold value.When this threshold value is falling-threshold value, if current sampled value is less than this threshold value, and if last sampling during greater than this threshold value, then occurrence condition coupling.When this threshold setting is static threshold, when not considering that current sampled value equals this threshold value under the situation that threshold is handed over, and if last sampling when being not equal to this threshold value, single condition coupling takes place.But as long as sampled value equals this threshold value, the logic state of condition is value of true just.
Hysteresis node regulation lagged value.The value of Hysteresis node is the text string of the lagged value of the various forms of expression.The actual format of lagged value is determined by the ThFormat node.If stipulated hysteresis, after generating threshold friendship incident, be reduced to be lower than or to be increased to this threshold tolerance that is higher than by this hysteresiss regulation until sampled value and just can generate another threshold friendship incident.If because noise causes sampled value fluctuation around threshold value, utilize hysteresis can prevent to generate too much threshold and hand over incident.For example, under the situation of rising threshold value, command execution once will can not carried out once more, unless sampled value becomes less than the threshold tolerance by this node regulation.
Simultaneously, Task (task) node can comprise XML node and Binary node, whether XML node regulation message comprises the order that has based on XML (extend markup language) data, and whether Binary node regulation message comprises the order based on binary data.
Reporting (report) node comprises at least one in following: whether regulation should be to the result's of DM server 100 report executing orders Gating (gating) node, and whether regulation should be to Event (incident) node of the state of DM server 100 report dispatch environment.
Fig. 5 illustrates the figure according to the diagnosis management object of first embodiment of the invention with an exemplary tree structure (having point, placeholder of the node of hierarchical structure or other types etc.).
With reference to figure 5, will the diagnosis management object be described with an exemplary tree structure.
As mentioned above, diagnose management object to comprise required information is diagnosed or monitored to terminal 200.In other words, the terminal management object comprises DFID node, ServerID (server ID) node, diagnostic monitoring configuration node, diagnostic monitoring back end, Operation (operation) node and State (state) node.
The title of DFID node regulation diagnostic function.And, the identifier of the DM server 200 that ServerID node regulation will be reported.
The title of DFID node indication diagnostic function.The state of ServerID node report diagnostic operation when carrying out diagnostic function, or the sign (ID) of instruction (indication) device management server that execution result will be reported to.The diagnostic monitoring configuration node is meant the folder node or the internal node of the setting value that the storage particular diagnostic function is required.The diagnostic monitoring back end is meant the node or the folder node of storage diagnostic result.
Start in the Operation node (beginning) node is to be used to allow DM server (100) to carry out the node of diagnostic function with remote mode.In addition, Stop (end) node in the Operation node is to be used to allow DM server (100) to stop the node of ongoing diagnostic function.Report in the Operation node (report) node is to be used to allow DM server (100) to receive the node of diagnostic result report.The State node is the node that is used to circulate a notice of the state of diagnostic function.
Fig. 6 illustrates figure according to the management and running object of second embodiment of the invention with an exemplary tree structure.And Fig. 7 is the figure that the diagnosis management object that is connected to management and running object shown in Figure 6 is shown with an exemplary tree structure.
According to second exemplary embodiment, whether diagnostic monitoring enabler client (230) can mate by guard condition.
For this reason, as can be known, condition (being Timer node, Trap node, Threshold node) can be separated with dispatch environment from Fig. 6 and Fig. 7, constitutes the management object of (independence) separately thus.
And for this reason, the diagnostic monitoring configuration node of diagnosis management object can comprise the scheduling reference mode of the address (or ID or URI) of regulation (indication) scheduling DM object.Therefore, scheduling DM object can be connected to this diagnosis management object, and whether diagnostic monitoring enabler client (230) can mate by guard condition.If determine the condition coupling, then diagnostic monitoring enabler client (230) generates the incident of sending (forwarding) to condition matching module (212).Here, condition matching module (212) is determined the condition coupling according to described incident, and request task execution module (213) fill order.
Fig. 8 illustrates figure according to the management and running object of third embodiment of the invention with an exemplary tree structure.And Fig. 9 is the figure that the dispatch environment that is connected to management and running object shown in Figure 8 is shown with an exemplary tree structure.
According to the 3rd embodiment, with second embodiment similarly, whether diagnostic monitoring enabler client (230) can guard condition satisfies.
For this reason, as shown in Figure 8, in dispatch environment, isolate condition (being Timer node, Trap node, Threshold node), and this condition can be included in the diagnosis management object.And as shown in Figure 9, the condition node of diagnosis management object and dispatch environment can be connected by address or ID (or URI).
Therefore, if diagnostic monitoring enabler client (230) is determined the condition coupling, then generate incident and this incident is sent (forwarding) to condition matching module (212).Here, condition matching module (212) determines that according to described incident condition mates, and can ask task execution module (213) fill order.
Figure 10 illustrates figure according to the dispatch environment of four embodiment of the invention and diagnosis management object with an exemplary tree structure.
As reference Figure 10 as can be known, according to the 4th embodiment, diagnostic monitoring enabler client (230) can monitor whether the condition (promptly being stored in the condition in the threshold value node) based on threshold value mates, and whether condition matching module (212) can monitor the condition (promptly being stored in the condition in the Timer node) based on timer and mate based on the condition (promptly being stored in the condition in the Trap node) of incident.
Shown in Figure 10 (a), the Cond of dispatch environment (condition) node can comprise Timer node and Trap node.And the Cond node can also comprise the management node (or MO node) of the specific management object in the indicating terminal 200.This MO node can comprise at least one in URI node and Value (value) node, the URI node is indicated the unified resource identifier of concrete management object, and the Value node is given for whether the concrete management object of additionally determining by the indication of URI node is the value of expection.Yet obviously other embodiments of these nodes (or node additional and/or alternative) also are fine.
Shown in Figure 10 (b), the management object after the separation can comprise diagnostic monitoring configuration node (or DiagMonConfig node).The diagnostic monitoring configuration node can comprise above-mentioned Th (threshold value) node.
Management object after will further describing above-mentioned dispatch environment and separate by some examples below.If incident then takes place in the value of management object and the threshold crossings of being indicated by Th (threshold value) node of diagnostic monitoring configuration node arbitrarily.Then, whether any management object of inspection generation incident is corresponding with the specific management object of being indicated by the URI node of the management object node in the dispatch environment.If this any management object is corresponding with it, check further then whether event is corresponding with the incident of being indicated by the Trap node of dispatch environment.If event is corresponding with it, then condition matching module 212 determines that condition satisfies, and follows task execution module 213 fill orders.
Figure 11 illustrates figure according to the dispatch environment of fifth embodiment of the invention and diagnosis management object with an exemplary tree structure.
According to the 5th embodiment, terminal (200) can adopt different modules to monitor condition (promptly being stored in the condition in the Threshold node) based on threshold value, and if determine the condition coupling, then generate incident.And according to the 5th embodiment, terminal (200) can adopt another different module to monitor condition (promptly being stored in the condition of Timer node) based on timer, and if determine the condition coupling, then can generate incident.If like this, then condition matching module (212) receives the incident that is generated, and can ask task execution module (213) fill order.
Shown in Figure 11 (a), the Cond of dispatch environment (condition) node only comprises management object.MO (management object) node can comprise at least one in URI node and the Value node, the unified resource identifier of this URI node indication specific management object, and this Value node is given for whether the specific management object of additionally determining by the indication of URI node is the value of expection.
Shown in Figure 11 (b), the timer dispatching management object that comprises (separating with dispatch environment) Timer node can comprise at least one in following: cycline rule node (or RRule node) and Trap node that whether Base (basis) node of the particular point in time of regulation actuating equipment administration order, regulation should recycle specified point.This Trap node can comprise at least one in following: regulation when the Trap node arrives specified point with identifier node (or ID node), Report (report) node and Schedule (scheduling) node of the identifier of the particular event of generation.Here, this Report node comprises at least one in identifier server node (or ServerID node) and the user interactions node (UI node), the identifier of the server that this particular event is reported to if particular event takes place this ServerID node regulation, and whether this UI node regulation is with regard to the generation and the user interactions of particular event.Scheduling node comprises at least one in UI node and the reference mode (or ToRef node or identifier), this UI node regulation whether with user interactions, and the identifier of ToRef node regulation dispatch environment.
Shown in Figure 11 (c), the threshold monitoring management object that comprises (separating with dispatch environment) Threshold node can comprise at least one in following: the Threshold node and the Trap node of the threshold value of the specific management object that the unified resource identifier node (or URI node) of the identifier of the specific management object that regulation will monitor, regulation will monitor.
To further describe above-mentioned dispatch environment and time scheduling management object by some examples below.If find to have arrived the time point of indicating in the base node, then incident takes place.Then, whether the identifier of checking event is corresponding with the identifier stipulated in the Identifier node of Trap node.If the identifier of stipulating in the Identifier node of the identifier of event and Trap node is corresponding, then terminal 200 is reported this situation according to the identifier server node of Report node to server.And event is delivered to dispatch environment by ToRef node regulation, the device management command of the Task node regulation of terminal 200 operation dispatching environment.
In addition, by some examples above-mentioned dispatch environment and threshold monitoring management object are described.If intersected by the value of the specific management object of URI node regulation and threshold value by Threshold node regulation, then incident takes place.And whether the identifier of checking institute's event is corresponding with the identifier of the ID node regulation of Trap node.If the identifier of event is corresponding with the identifier of the ID node regulation of Trap node, then terminal 200 is reported this situation according to the identifier server node of Report node to server.And to sending institute's event by the dispatch environment of ToRef node regulation.Then, the device management command of stipulating in the Task node of terminal 200 operation dispatching environment.
As mentioned above, described terminal, server and method can have following feature.
Promptly, the present invention is by allowing terminal condition from the administration order of server receiving equipment and this order of execution before potential problem takes place, if and condition satisfies then carries out this device management command thus, allows the equipment control of expecting automatically at reasonable time.
The invention provides a kind of terminal, this terminal comprises: first entity, and it is suitable for discerning first management object by the address of first management object or identifier, and monitors whether meet the scheduling that comprises in first management object of being discerned; Wherein in second management object, stipulate described address or described identifier; And second entity, it is suitable for carrying out the device management command that is included in the dispatch environment under described first entity determines to meet the situation of described scheduling.
In addition, the invention provides a kind of terminal, this terminal comprises: first entity, and it is suitable for monitoring whether meet the scheduling that comprises in the diagnosis management object; And second entity, it is suitable for carrying out the device management command that is included in the dispatch environment under described first entity determines to meet the situation of described scheduling.
In addition, the invention provides a kind of terminal, this terminal comprises: first entity, and it is suitable for according to comprising that the first management and running object based on the condition of threshold value monitors the condition that whether satisfies based on threshold value; Second entity, it is suitable for according to comprising that the second management and running object based on the condition of timer monitors the condition that whether satisfies based on timer; And the 3rd entity, its be suitable for satisfy described based on threshold value condition and one of them the situation at least of described condition based on timer under carry out the device management command that is included in the dispatch environment.
It should be noted that feature described herein and notion relate to the various standards at the equipment control (DM) of being answered the normal structure management by specific phase.Therefore, the standard and/or the notion of the various correspondences of regulation also are a part of this disclosure here.
For example, some aspect described herein relates to concrete standard (for example OMA, GSM, 3GPP, 3GPP2, IEEE etc.).Therefore, at least some features described herein are applicable to that these have been developed or just in the standard of evolution.
Although the present invention has stipulated the various titles of the order relevant with equipment control (DM), node, child node etc., can know to be understood that this type of title and label only are exemplary.Feature of the present invention is restricted never thus, because can use other equivalent title or labels, as long as it refers to identical or equivalent function and/or feature.
In instructions to " a kind of embodiment ", " embodiment ", quoting of " illustrative embodiments " etc. is meant that concrete feature, structure or the characteristic described in conjunction with this embodiment are to be included at least a embodiment of the present invention.This type of word that each position occurs in this instructions might not refer to same embodiment.In addition, when describing concrete feature, structure or characteristic, think that those skilled in the art can realize these features, structure or characteristic in conjunction with other embodiments in conjunction with any embodiment.
Although each embodiment is described, it should be understood that those skilled in the art can design a plurality of other modifications and the embodiment that falls in the principle of the invention scope in conjunction with illustrative embodiments.More particularly, the assembled arrangement of ingredient and/or object structure can exist various modifications and variation in the scope of the disclosure, accompanying drawing and appended claim.Except the modification and variation of ingredient and/or structure, application in addition also is conspicuous to those skilled in the art.
Claims (4)
1. mobile communication terminal, this mobile communication terminal comprises:
Transceiver;
Processor, it is used to operate diagnostic monitoring agency, equipment control enabler client and device management scheduling enabler client;
Wherein, the state of the described mobile communication terminal of described diagnostic monitoring agency diagnosis and the result who sends the described mobile communication terminal of diagnosis to described equipment control enabler client;
Wherein, described equipment control enabler client sends described result and from described server receiving scheduling information, described schedule information comprises to server: regulation comprises the task element of message of at least one device management command and the condition element that is used to carry out described order;
Wherein, described server produces described schedule information according to described result;
Wherein, the URI of described condition regulation trap incident, threshold value and management object;
Wherein, described device management scheduling enabler client is installed described schedule information, monitor the generation of described trap incident, value to the described management object of described URI sign is sampled, with the value of being sampled and described threshold ratio, and if the value of being sampled with described threshold value coupling then the inner described order of execution and not being connected with described server.
2. mobile communication terminal according to claim 1, wherein
Described condition is also stipulated the condition based on timer.
3. mobile communication terminal according to claim 1, wherein
The mounted schedule information of storage in the device management tree in described mobile communication terminal.
4. one kind is carried out the method for scheduling device management by mobile communication terminal, and this method comprises:
Diagnose described mobile communication terminal;
Send the result of the described mobile communication terminal of diagnosis to server;
From described server receiving scheduling information, described schedule information comprises: regulation comprises the task element of message of at least one device management command and the condition element that is used to carry out described order;
Wherein, described server produces described schedule information according to the result who is sent;
Wherein, the URI of described condition regulation trap incident, threshold value and management object;
Described information is installed;
Monitor the generation of described trap incident;
Value to the described management object of described URI sign is sampled, with the value of being sampled and described threshold ratio; And
If the value of being sampled is with described threshold value coupling then the inner described order of execution and not being connected with described server.
Applications Claiming Priority (13)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US76094306P | 2006-01-23 | 2006-01-23 | |
| US76094206P | 2006-01-23 | 2006-01-23 | |
| US60/760,942 | 2006-01-23 | ||
| US60/760,943 | 2006-01-23 | ||
| US76251706P | 2006-01-27 | 2006-01-27 | |
| US60/762,517 | 2006-01-27 | ||
| KR1020060124992 | 2006-12-08 | ||
| KR10-2006-0124992 | 2006-12-08 | ||
| KR1020060124992A KR20070108432A (en) | 2006-01-23 | 2006-12-08 | Method for scheduling device mangament |
| KR10-2007-0005812 | 2007-01-18 | ||
| KR1020070005812A KR101474413B1 (en) | 2006-01-23 | 2007-01-18 | Terminal for pefforming scheduled device mangament and method thereof |
| KR1020070005812 | 2007-01-18 | ||
| PCT/KR2007/000378 WO2007083972A1 (en) | 2006-01-23 | 2007-01-22 | Performing scheduled device management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101371243A CN101371243A (en) | 2009-02-18 |
| CN101371243B true CN101371243B (en) | 2011-04-27 |
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 |
| 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 |
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 |
| CN2007800028823A Expired - Fee Related CN101371236B (en) | 2006-01-23 | 2007-01-22 | Terminal and method for performing device management scheduled based on threshold |
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 |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1512382A (en) * | 2002-12-27 | 2004-07-14 | ������������ʽ���� | Apparatus monitoring system, monitoring program and monitoring method and device |
| KR20050046932A (en) * | 2003-11-14 | 2005-05-19 | 삼성전자주식회사 | System for checking state of slave devices using i2c bus |
Family Cites Families (5)
| 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 |
| 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 |
| 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 CN2007800028823A patent/CN101371236B/en not_active Expired - Fee Related
- 2007-01-22 CN CN2007800029582A patent/CN101371243B/en not_active Expired - Fee Related
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1512382A (en) * | 2002-12-27 | 2004-07-14 | ������������ʽ���� | Apparatus monitoring system, monitoring program and monitoring method and device |
| KR20050046932A (en) * | 2003-11-14 | 2005-05-19 | 삼성전자주식회사 | System for checking state of slave devices using i2c bus |
Non-Patent Citations (1)
| Title |
|---|
| JP特开2002-216279A 2002.08.02 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101371243A (en) | 2009-02-18 |
| CN101371235B (en) | 2010-09-15 |
| CN101371236B (en) | 2012-05-23 |
| CN101371235A (en) | 2009-02-18 |
| CN101371236A (en) | 2009-02-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20070192158A1 (en) | Performing scheduled device management | |
| CN101375266B (en) | Based on the device management scheduling of trap mechanism | |
| CN101778004B (en) | Terminal and method for performing device management scheduled based on threshold thereof | |
| US8069238B2 (en) | Device management system and device management command scheduling method thereof | |
| RU2636112C1 (en) | Object of interface management service, function service object and method of control of elements | |
| EP1766866A1 (en) | Device management system and device management command scheduling method thereof | |
| US8104037B2 (en) | Terminal and method for performing device management scheduled based on threshold | |
| US20020188568A1 (en) | Systems and methods of containing and accessing generic policy | |
| CN110535928A (en) | A kind of event method for pushing of the JAVA intelligence contract of block chain | |
| CN101371243B (en) | Performing scheduled device management | |
| CN110505219B (en) | Dubbo-based micro-service registration control management system and method | |
| CN104468708A (en) | Data collaborating method and data collaborating device | |
| CN103166779A (en) | Alarm confirming and processing method and device based on mobile terminal | |
| CN110989977B (en) | Intelligent home environment personalized customization method for disabled people | |
| CN101699814A (en) | Assembly management system and method | |
| CN112650573B (en) | Task scheduling method and device | |
| CN117093480A (en) | Method and device for optimizing extraction flow, computer equipment and readable storage medium | |
| Moskal et al. | VALIDATION PROTOCOL-THE MISSING PUZZLE PIECE | |
| Shin et al. | Design and implementation of the management agent for mobile devices based on OMA DM | |
| CN101371498B (en) | Method for scheduling the device management and terminal thereof | |
| WO2007083973A1 (en) | Terminal and method for performing device management scheduled based on threshold | |
| CN113312242A (en) | Interface information management method, device, equipment and storage medium | |
| Fan et al. | Integrating workflow and forum via event management | |
| CN102044000A (en) | Method for generating installation scheduling document |
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: 20110427 Termination date: 20170122 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |