CN101442529B - Device management system and device management command scheduling method thereof - Google Patents
Device management system and device management command scheduling method thereof Download PDFInfo
- Publication number
- CN101442529B CN101442529B CN 200810186737 CN200810186737A CN101442529B CN 101442529 B CN101442529 B CN 101442529B CN 200810186737 CN200810186737 CN 200810186737 CN 200810186737 A CN200810186737 A CN 200810186737A CN 101442529 B CN101442529 B CN 101442529B
- Authority
- CN
- China
- Prior art keywords
- device management
- scheduling
- node
- server
- management command
- 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
A device management system and device management scheduling method thereof, in which a server transmits to a client a scheduling context including a device management command and a schedule for the performing of the device management command, and the client generates a device management tree using the device management scheduling context, performs the command when a specific scheduling condition is satisfied, and, if necessary, reports the command performance result to the server, whereby the server performs a device management such as requesting a command to be performed under a specific condition, dynamically varying the scheduling condition, and the like.
Description
The application is to be that on July 8th, 2005, national applications number are 200580020148.0 (PCT/KR2005/002203) applying date, and denomination of invention is divided an application for the patent application of " equipment management system and device management command scheduling method ".
Technical field
The present invention relates to equipment control and data synchronization technology, and relate to particularly equipment management system and device management command scheduling method thereof.
Background technology
Usually, equipment control (DM) technology relates to from server and connecing once receiving that the particular procedure order is by the order of client executing particular procedure.
In such DM technology, the DM server sends processing command to the DM client, and the DM client is carried out corresponding order immediately.Then, the relevant reporting process of carrying out the result of these orders of this DM client executing.
In addition, DM server request DM client changes, upgrades and the deletion specific function.If the current state that to carry out from the request of DM server that is in of DM client, be used for then confirming that the DM dialogue of DM client state should periodically produce and/or inquire about by the DM server, and should consider associated result (issue) and problem.Therefore, in the prior art of DM method, so that can carrying out the process of the order of DM server under expected time point, state, the DM server also do not propose so far.
In addition, in the prior art, because the DM client must be carried out DM order (being sent by the DM server) immediately at the DM session when opening (unlatching) DM dialogue, consider that the internal state of equipment is maybe when a plurality of event occurs, can not outside the DM dialogue, (afterwards) carry out such DM order, and can not in specific expected time or situation, carry out.These prior art restrictions have not only increased the related expense of equipment executing state diagnostic program, in addition, can not carry out effective diagnosis, so that can solve problem by adequate measures before problem may occur.Equally, these prior art restrictions also need for the new DM dialogue of carrying out the DM order, and therefore need to stand the high equipment control cost of not expecting.
Summary of the invention
Therefore, the purpose of this invention is to provide a kind of like this equipment management system, the wherein server device management scheduling of administrative client dynamically, and the device management scheduling method in this system.
Another object of the present invention provides a kind of equipment management system and device management scheduling method, wherein server can be in client the apparatus for establishing management and dispatching, and can change and delete the device management scheduling of having set up.
Another purpose of the present invention provides a kind of equipment management system and the device management scheduling method in this system, device management command or data synch command that wherein server can dispatching client, so the program of the state that client can reporting facility, operation dispatching and use optimum parameter value.
In order to obtain these and other advantages and according to purpose of the present invention, as example here with wide in range description, provide device management scheduling method, it comprises: transmit the dispatch environment file to client from server; Produce device management tree by client with the dispatch environment file of this transmission, and the apparatus for establishing management and dispatching; And carry out this device management scheduling by client according to the command execution condition (namely being used for exectorial condition) of the device management scheduling of setting up.
This device management scheduling method also comprises: use the new dispatch environment file that transmits from server to produce device management tree, and change device management scheduling; Choose information according to the status report in the device management tree that produces, by client selectively to the execution result of server reporting facility management and dispatching; And pass through the server request client and delete the device management scheduling of setting up in advance.
Preferably, the step of apparatus for establishing management and dispatching comprises: the validity of confirming the dispatch environment file of transmission; When full confirmation dispatch environment file, set up at least one or multiple equipment management scheduling subtree more with this device management scheduling environment file.
In order to reach these and other advantages and according to purpose of the present invention, equipment management system comprises: server, for generation of comprising device management command with transmission and be used for carrying out the dispatch environment file (scheduling context) of the schedule information (schedule) of this device management command; Client, it uses the device management scheduling environment file that transmits to produce device management tree, produce thus device management scheduling, and come the actuating equipment management and dispatching according to the command execution condition (namely being used for exectorial condition) of the device management scheduling that produces.
Preferably, server transmits new dispatch environment file to client, changes device management scheduling with requesting client, and transfer equipment management delete command is to client, with the preassembled device management scheduling environment file of request deletion.
Preferably, client is chosen information according to the status report of device management scheduling, selectively to the execution result of server reporting facility management and dispatching.
Preferably, this client comprises: command processing module, and it receives the dispatch environment file from server afterwards for generation of talking with the equipment control of server; And scheduler module, be used for using the dispatch environment file that transmits from command processing module to produce device management tree, when the command execution condition is satisfied, be satisfied to command processing module notification command executive condition, to carry out corresponding device management command, and from the result of command processing module receiving equipment administration order, selectively it is reported to DM (equipment control) server.
Preferably, command processing module comprises: be used for being sent to from the dispatch environment file that server sends the functional unit of scheduler module; Be used for the order of dispatching according to the notice execution correspondence of scheduler module and the functional unit that the execution result of correspondence order is sent to scheduler module; And be used for to send the functional unit of server to from the dispatch environment file status report that scheduler module transmits based on command execution results.
Preferably, this scheduler module comprises: the first functional unit is used for using the dispatch environment file that transmits from server to produce the device management scheduling subtree; The second functional unit is used for the dispatching command executive condition (namely exectorial condition) of fetch equipment management and dispatching subtree, thereby constantly checks the state that the command execution condition is satisfied; The 3rd functional unit, it is used for, and the command execution functional unit of request command scheduler module comes the actuating equipment administration order when the command execution condition is satisfied; The 4th functional unit, its be used for according to the device management scheduling subtree choose that nodal value determines whether should be to the command execution results of server report about the command execution functional unit; The five-function unit, it is used for the command execution results to the server report from the transmission of the 4th functional unit, or the check result of the command execution condition of the second functional unit; The 6th functional unit, it is used for deleting the device management scheduling subtree of setting up in advance according to the device management scheduling delete command from server request.
Preferably, in the method and system, the dispatch environment file comprises device management command and the schedule information that is associated with the execution of order, and has XML (extensible markup language) text formatting.
Preferably, in the method and system, the dispatch environment file comprises: the information element that is used for the command execution condition; The information element that is used for the device management command of scheduling; The information element that is used for user interface; And the information element of choosing (gate) for status report.
Preferably, in the method and system, the device management scheduling subtree comprises: the scheduling node; The node that is used for the identifier of indication equipment management and dispatching environment file; The node of executive condition that is used for the device management command of expression scheduling; The node that is used for the information of expression user interface; And be used for expression whether report order execution result node or be used for expression to the node of the server address of the execution result of its report order.
Preferably, in the method and system, equipment represents customer premises equipment such as terminal, PDA, notebook-PC (PC), Desktop PC etc.
Aforementioned and other targets of the present invention, feature, aspect and advantage, more apparent from following detailed description of the present invention when by reference to the accompanying drawings.
Description of drawings
Included accompanying drawing is used for providing for further understanding of the present invention, and is included in its part of formation in the specification, and accompanying drawing is described embodiments of the invention, and is used for together explaining principle of the present invention with specification.
In each accompanying drawing:
Fig. 1 is the block diagram that shows according to equipment management system of the present invention;
Fig. 2 is the figure that shows the structure of order XML (extensible markup language) document shown in Fig. 1;
Fig. 3 is the figure of the DTD (DTD) of display command XML document;
Fig. 4 is the figure that is presented at the structure of the schedule information XML document shown in Fig. 1;
Fig. 5 is the figure of the DTD of display scheduling information XML document;
Fig. 6 is the figure that shows the embodiment of duration Dur element;
Fig. 7 is the figure that defines the content of threshold value Th element;
Fig. 8 is defined in the operator used in the Th element and the figure of special symbol;
Fig. 9 is the figure that shows the form of Th element;
Figure 10 shows to use Th unit usually to construct the figure of the embodiment of scheduling META data;
Figure 11 is the figure that shows detailed structure according to the equipment management system of the present invention shown in Fig. 1;
Figure 12 is the figure that shows according to the stream of the signal in the device management scheduling method in equipment management system of the present invention;
Figure 13 is the details drawing that shows according to the signal stream in the step that produces and carry out DM (equipment control) scheduling in the device management scheduling method of equipment management system of the present invention shown in Figure 12;
Figure 14 is the details drawing that shows according to the stream of the signal in the step of the scheduling of the change DM in the device management scheduling method in the equipment management system of the present invention shown in Figure 12;
Figure 15 is according to the detailed flow figure in the step of the scheduling of the deletion DM in the device management scheduling method in the equipment management system of the present invention shown in Figure 12.
Embodiment
Now will be in detail with reference to preferred embodiments more of the present invention, example of the present invention is described in the accompanying drawings.
The invention provides such equipment management system, the server device management scheduling of administrative client dynamically wherein, it is synchronous to be used for equipment control or data; And be provided at device management scheduling method in the correspondence system.
In addition, the invention provides a kind of like this equipment management system, the wherein equipment control of server scheduling client or device management command, and client correspondingly spontaneous reporting facility (such as terminal) state, carry out the program (diagnostic program, state recording program, virus checker etc.) be scheduled, and use optimum parameter value according to the variation of the environment for use under particular point in time or state.The present invention also is provided at the device management scheduling method in this correspondence system.
For this reason, in this equipment management system and device management scheduling method thereof, the server transmission comprises that equipment control (DM) the dispatch environment file (schedulingcontext) of DM order and schedule information is to the client of target device, and this client uses this DM dispatch environment file to produce DM tree (namely one type information management hierarchy or have the structure of similar " tree " of a plurality of classifications (level) or branch), and carries out corresponding DM according to command execution condition (namely being used for exectorial condition) after this and order.Preferably, target device refers to subscriber's installation (UE) such as terminal, PDA, notebook-PC (PC) and Desktop PC etc., for convenient, only provides the explanation for terminal in these customer premises equipment.The below introduces preferred embodiments more of the present invention in detail.
Fig. 1 is the block diagram that illustrates according to equipment management system of the present invention.
As shown in FIG. 1, equipment management system according to the present invention comprises: equipment control (DM) server 100, and it is for generation of DM dispatch environment file and send it to equipment (for example terminal); DM client 200, it is used for use and produces the DM tree from the dispatch environment file that DM server 100 sends in terminal, and when command execution condition (namely being used for exectorial condition) DM order corresponding to execution when being satisfied.
This DM dispatch environment file comprises DM order and the schedule information that is associated with the execution of DM order, the information element Condition that for example is used for the command execution condition, be used for the information element Commands that the DM that dispatches of institute orders, the information element " UserInter " that is used for user interface is used for status report and chooses the information element of (gating) etc.
Fig. 1 shows the example of the DM tree that is produced by the DM client.
With reference to figure 1, DM tree 40 comprises that at least one or more MD dispatch subtree 41, each subtree comprises a plurality of scheduling nodes, namely dispatches node Sched_1, SchedID node, Condition node, Commands node, UserInter node, Gating node etc.
Scheduling node Sched_1 represents each device management scheduling (Sched_1), and Commands node and Condition node are connected to each other.Especially, scheduling node Sched_1 is used as " placeholder " (namely basis, position node).The Condition node indicates to carry out the condition of DM order.The Commands node represents the DM that the is scheduled order that (namely under particular point in time or state) will be carried out by the DM client when satisfying the command execution condition.Equally, the UserInter node represents when satisfying the command execution condition whether execution about the order of correspondence should receive the user and confirm.The Gating node represents whether notify the DM execution result of order to DM server 100.In addition, DM scheduling subtree 41 further selectively (alternatively) comprise DM server Mgmtsvr node.Preferably, the server address of the execution result of Mgmtsvr node storage report DM order.For example, if result will report to the other server except corresponding DM server, or will change according to each result to its DM server of reporting result, the Mgmtsvr node comprises ACL (Access Control List) information, and this information represents that server has administration authority to each node.
The Universal Database 50 that wherein stores the manageable a plurality of information of DM server is used for being stored in the actual value that DM dispatches each node of subtree 41.Especially, Commands node and Condition node correspond respectively to order XML (extensible markup language) document and scheduling XML document.
The order XML document is included in will be by the DM order of DM client process under time point that schedulable condition is satisfied or the state.Each command lanuage is comprised of the order that utilizes the DM protocol definition.
Fig. 2 shows the structure of order XML document, and Fig. 3 shows the DTD (DTD) of order XML document.As shown in Fig. 2 and Fig. 3, the root element of order XML document refers to the Commands element.The command lanuage element that defines in the DM of correspondence agreement is included in the content of Commands element.
When structure DM scheduling subtree, DM client 200 receives the DM order from DM server 100, and they are stored in the Universal Database 50.After this, the DM order can change or deletion in another DM dialogue.
The scheduling XML document comprises schedule information, and this schedule information is described the condition that will be performed comprising the DM order in the order XML document.Fig. 4 illustrates the structure of schedule information XML document, and Fig. 5 is the DTD of this schedule information XML document.
With reference to figure 4 and Fig. 5, the scheduling XML document is an effective XML document, wherein＜Sched〉element is root element.Each information element is described schedulable condition.When making up DM scheduling subtree 41, the schedule information that DM client 200 receives from DM server 100, and it is stored in the Universal Database 50.Afterwards, schedule information can change or deletion in another DM dialogue.
Scheduling Sched element as the root element of schedule information XML document, is made of one or more single scheduling SimpSched elements.Sched element definition trigger.Usually, the Sched element corresponding to the trigger of SimpSched element definition and (sum).The time point or the condition that are included in the DM order in the order XML document that trigger notice DM client is pending are satisfied.
SimpSched element definition simple scheduling explanation (specification) and an one or more trigger.The scheduling of (definitive) explanation defines by integrating a plurality of simple scheduling explanations fully.Completely scheduling explanation is usually defined by Sched unit.The SimpSched element is made of the cell scheduling explanation of one or more definition of duration Dur, cycle (period) Per and threshold value Th element.Be formed for the correlation of distributive condition between the cell scheduling explanation, the trigger that wherein produces from each element will be passed to the DM client.Namely, if the value of discrete cell element is " vacation ", the trigger that then produces from another unity element can not be passed to the DM client.
The Dur element is the cell scheduling explanation that is used to specify period or particular point in time.Define simultaneously logical value and trigger described period, and described particular point in time only defines trigger.
Fig. 6 is the embodiment of duration Dur element.
With reference to figure 6, such as the plaintext based on the following specific syntax that will describe, the content of duration element is by using starting point and the end point of certain operations symbol " .. " scope setup time.The duration element represents with date and time.When date and time together used, the date was placed on before the time and date and time utilization " T " separates.For example, 23: 59 on the 26th July in 2004,59 stopwatches were shown " 2004-07-26T23:59:59 ".In addition, the minimum unit of duration element is restricted to 10 seconds, and " * ", " im " and "～" definition " per hour ", " immediately " and " continuously " respectively successively.At this moment, "～" can use with " im ".
Cycle Per element, the cell scheduling element as being used for the definition time cycle uses with another cell scheduling element, and periodically produce sequential trigger (sequential trigger) when condition is "True".
The Per element utilizes the second unit delimiting period, and refers to the digital text that uses integer or real number and do not use any symbolic representation.This Per element can not use in the SimpSched element independently.Trigger can not produce in the Per element when " vacation " in the condition that is associated, but the condition of can work as is changed into for the first time "True" and repeatedly produced during by the cycle maintenance "True" of Per element definition when the condition basis from " vacation ".
Threshold value Th element as the cell scheduling element that is used for the definition value scope, can define the two kinds of dissimilar scopes and the particular value that wherein produce trigger.The Th element can together use with other cell scheduling elements, for example another Th element, Dur element or Per element.The Th element has property value " Hyst ", and expression is used for the lagged value of specific threshold.The Th element also has property value " MgmtObj " and the URI (Uniform Resource Identifier) of the management objectives that are associated with the Th element.The content of threshold value element is based on the plain text string that the following specific syntax that will describe consists of.
Fig. 7 is the figure that defines threshold value (Th) element content, and it is described based on the ABNF (expansion Bacchus-Nore normal form, Augmented Backus-Naur Form) by RFC 2234 definition.
As shown in FIG. 7, the content of Th element is the plain text string that is made of management objectives value, special symbol and operator.The order of enumerating among the priority of operator and Fig. 8 is the same.
The contents table of Th element is shown as " ThContent " that is made of " ThContentItem " that separate more than one usefulness " IS " operator.At this moment, one of " ThContentItem " definition " ThGroup ", " ThRange " and " EventRange ".
ThGroup defines one or more triggers that represented by the combination between the combination between " Threshold " and " Delta " or " TW (*) " and " ThExc ".This trigger can produce from Th element, Dur element and Per element, is the designator that should be performed for the order that the notice client is associated.At this moment, relevant with the change of the management objectives value that is associated by the trigger of trigger element generation.
" Threshold " defines threshold value, and it is defined as the particular value of the management objectives that are associated, and uses in the increment (delta) of definition boundary value, trigger and threshold range.
" TW " that be used for defining the special symbol that is called the threshold value asterisk wildcard represents all management objectives values.At this moment, produce trigger according to the change of management objectives value, but threshold value asterisk wildcard definite condition not.
The threshold value that " ThExc " definition is got rid of from another sets of threshold values, and usually and the threshold value asterisk wildcard together use.
" Delta " is made of one or more threshold values, and each threshold value represents each increment.At this moment, the boundary value of event scope utilizes presentation of events to begin usually to represent with the event unit of event end.When the event of event scope begins to occur, be "True" by the logical value of the condition of " EventRange " element representation.When the event of event scope finished to occur, the logical value of this condition was " vacation ".The such event of " Event " expression: the management objectives value has particular value or falls in the certain limit.Therefore, can represent " Event " with threshold value, sets of threshold values and threshold range.For example, wherein the management objectives value event that has particular value or fall into the scope of default value can be " Event ".The one or both sides of range of components can be open, and the scope of both sides all is the open event scope asterisk wildcard that is called as.
" ThRange " of definition threshold range is used for definite condition and produces trigger.The a certain side of threshold range can be open.The particular range that both sides are all opened is called as the threshold range asterisk wildcard.The threshold range asterisk wildcard can not use separately, but when being useful when together using with " ThRangeExc ".When the logical value of the condition that is defined by threshold range is changed into "True" for the first time, can produce trigger.Then, no matter when the logical value of condition is changed, and also produces trigger.
" ThRangeExc " element is made of the TREP more than, thereby expression is from the eliminating of specific threshold scope.At this moment, TREP is the assembly that only uses in " ThRangeExc ".
" EventRange " element of presentation of events scope can definite condition and trigger conduct " ThRange ".At this moment, the boundary value of event scope is begun the event element representation that finishes with event by presentation of events.When the event of event scope begins to occur, be "True" by the logical value of the condition of " EventRange " element representation.When the event of event scope finished to occur, the logical value of condition was " vacation ".Representations of events management objectives value has particular value or falls into the interior event of certain limit.Therefore, can use threshold value, sets of threshold values and threshold range to represent this event.For example, wherein the management objectives value event that has particular value or fall into the scope of default value can be this event.The one or both sides of event scope can be opened, and the open scope in both sides is called as event scope asterisk wildcard.
Fig. 8 shows the operator used and the definition of special symbol in the Th element, Fig. 9 shows the Th attribute of an element, and Figure 10 shows for the embodiment that uses Th element structure DM dispatch environment file.
Embodiment shown in Figure 10 represents the DM dispatch environment file for " Get ", be used for equaling 1200,1400 when nodal value ..., 3000 maybe when this value falls into 1800 and 3000 between in the time of 60 seconds, the order " Get " of indication processing nodal value.
Figure 11 is the figure that is shown in greater detail in the structure of the DM system shown in Fig. 1.
As shown in drawings, DM server 100 and DM client 200 (scheduler module and command processing module) comprise a plurality of functional units, need these functional units to be used for carrying out for example scheduling generation/foundation, DM scheduled for executing, DM scheduling change/deletion, the report of DM dispatch state etc.
The dispatch environment file that arranges in DM server 100 produces/changes functional unit 10 and produces DM dispatch environment files, and the command processing module 20 of request DM client 200 is installed or changed DM dispatch environment file.
Installation/when changing the dispatch environment file, dispatch environment file installation/recombination function unit 31 produces DM scheduling subtrees and sets to produce DM when DM server 100 is asked by the request transmitting function unit 21 of command processing module 20.If necessary, dispatch environment file installation/recombination function unit 31 can receive user's affirmation before the dispatch environment file is installed.
The command execution condition is confirmed the command execution condition of functional unit 32 affirmation scheduling in DM scheduling subtree, and constantly checks the state that the command execution condition is satisfied.For example, when another management objectives value that exists in DM tree corresponding to assign thresholds, or at particular point in time, or according to whether particular event has occured, can determine whether the command execution condition is satisfied in equipment.When satisfying the command execution condition, if necessary, command execution condition affirmation functional unit 32 is carried out the user according to the information of the user interface UserInter in DM scheduling subtree and is confirmed program.
When confirming to satisfy the command execution condition in the functional unit 32 in the command execution condition or when the user allows the DM operation, the command execution functional unit 22 of DM command execution functional unit 33 request command processing modules 20 is carried out the DM order.
Command execution functional unit 22 is carried out the DM order of the scheduling in the DM scheduling subtree according to the request for the DM command execution of confirming functional unit 32 from the command execution condition.Command execution functional unit 22 transmits command execution results (state/result/generic alarm) to scheduler module 30 by response message.Response message, for example, comprise relate to order carry out fully, because how etc. which kind of reason makes a mistake, equipment state command execution results code after fill order.
Status report is chosen the data that functional unit 34 filters DM server 100 to be reported to.Status report is chosen functional unit 34 and is determined whether should report to DM server 100 from the command execution results (state/result/generic alarm) that command execution functional unit 22 transmits.
The command execution results (state/result/generic alarm) that functional unit 34 transmits is chosen in dispatch environment file status function of reporting unit 35 to the report of DM server from status report, and can use the ACL information of Mgmtsvr node to report command execution results to another server.Dispatch environment file status function of reporting unit 35 uses specific protocol (for example generic alarm) delivery status report PDU (protocol Data Unit), thereby carries out the processing that is used for the report of DM dispatch environment file status.
Preferably, status report PDU consists essentially of for the PDU of delivery status command lanuage, result command language, generic alarm command lanuage (status PDU, as a result PDU and generic alarm PDU), and the termination request PDU of the DM dispatch environment file of carrying out for the user.
If necessary, the command execution condition of scheduler module 30 confirms that functional unit 32 and DM command execution functional unit 33 can be integrated in the functional unit.If necessary, status report is chosen functional unit 34 and also can be integrated together (represented such as dotted line) with dispatch environment file status function of reporting unit 35.
Provide more detailed explanation referring now to accompanying drawing to execution/change/function that deletion DM dispatches and the function of reporting the DM dispatch state.In this case, between DM server and DM client 200, set up the DM dialogue.After session establishment was got up, the authentication (authentication) of carrying out between DM server 100 and DM client 200 was processed.
Set up the function of DM scheduling
By using the DM agreement to produce equipment control (DM) dispatch environment file, connect the DM dialogue and DM dispatch environment file is sent to equipment (for example terminal) and ask to set up the DM scheduling.
Namely, as shown in Figure 11 and Figure 12, the dispatch environment file of DM server 100 produces/changes the dispatch environment file that functional unit 10 produces DM order and the schedule information of the execution that comprises relevant DM order.The dispatch environment file produces/changes functional unit 10 and by the DM agreement dispatch environment file that produces is sent to equipment (for example terminal).Here, the dispatch environment file produces/changes functional unit 10 usefulness ADD and orders to add the DM order, and comes so that all DM order by a group scheduling with autocommand.As a result, the dispatch environment file produces/changes functional unit 10 permission equipment (namely terminal) and processes together one group DM order.Equally, this dispatch environment file produces/changes functional unit 10 and also comprise UI alarm order in autocommand, confirms to receive the user before at equipment corresponding dispatch environment file being installed.
Be sent to the dispatch environment file of DM client 200 from DM server 100, by the request transmitting function unit 21 of command processing module 20, be sent to again dispatch environment file installation/recombination function unit 31 (S11) of scheduler module 30.
After UI alarm order reception user affirmation, dispatch environment file installation/recombination function unit 31 uses DM dispatch environment files to produce DM tree 40, thus installation DM dispatch environment file.DM dispatch environment file, as shown in FIG. 1, the DM scheduling subtree 41 that has at least one or more scheduling nodes (=DM target) by generation is installed on the DM tree 40.When forming the DM tree, the actual value of a plurality of scheduling nodes is stored in the Universal Database 50.Especially, Condition nodal value and Commands nodal value have the effective XML document form that is stored in respectively in order XML document and the schedule information XML document.
In addition, when producing DM scheduling subtree 41, whether grammer and the context of the XML document of the DM dispatch environment file that dispatch environment file installation/recombination function unit 31 checking transmits be correct, and whether DM dispatch environment file can be mounted (such as the access right of server, client performance etc.).Then, the installation results (shown in dotted line) that DM servers 100 are associated with the request that DM dispatch environment file is installed is notified in dispatch environment file installation/recombination function unit 31.
Carry out the function of DM scheduling
Therefore in the good authentication XML document and produce DM tree 40 namely after DM scheduling subtree 41, the schedule information XML document of DM client 200 analytical databases 50 comes operation dispatching to process.Namely, when producing a DM scheduling subtree 41, the command execution condition confirms that functional unit 32 is with constant cycle (time interval attribute of Th element), read the information of the DM command execution condition of DM dispatch environment file from the schedule information XML document, and then constantly check the state (S12) that DM command execution condition is satisfied.Whether the command execution condition is satisfied, and can for example determine when another management objectives value that exists in the DM tree reaches setting threshold or at the particular point in time place or according to whether particular event has occured in equipment.
When satisfying the command execution condition, if should receive user's affirmation according to the information of the user interface UserInter in the DM scheduling subtree 41, then carry out the user and confirm to process.In the user confirms to process, provide the guiding (namely notice, information etc.) of ordering about carrying out DM at screen, and therefore the user can allow or cancel the execution that DM orders.If the user cancels the DM command execution, command execution condition affirmation functional unit 32 is not carried out the DM order of dispatching but is carried out again the processing that is used for confirming the command execution condition.
If confirm to satisfy the command execution condition in the functional unit 32 in the command execution condition, or the user allows DM operation (S13), and the command execution functional unit 22 of DM command execution functional unit 33 request command processing modules 20 is carried out DM order (S14).Command execution functional unit 22 is ordered according to the DM that carries out scheduling in DM scheduling subtree 41 from the request of DM command execution functional unit 33, and chooses functional unit 34 (S15) by using response message to send command execution results (state/result/generic alarm) to status report.
Status report is chosen functional unit 34 and is determined whether and command execution results (state/result/generic alarm) will be reported to DM server 100 (S16) according to the nodal value of choosing that DM dispatches subtree 41.
Status report is chosen functional unit 34 provides part DM command execution results to dispatch environment file status function of reporting unit 35 (S17) according to choosing nodal value.Dispatch environment file status function of reporting unit 35 utilizes the status report transmitting function unit 23 of command processing module 20 command execution results of correspondence to be reported to the status report processing function unit 11 (S18 and S19) of DM server 100.At this moment, dispatch environment file status function of reporting unit 35 uses specific protocol (for example generic alarm) to transmit PDU (protocol Data Unit), and carries out the processing that is used for report DM dispatch environment file status.Status report PDU consists essentially of PDU (status PDU, as a result PDU and generic alarm PDU), and these PDU are used for delivery status command lanuage, result command language and generic alarm command lanuage.
Namely, as shown in Figure 13, DM server 100 is sent to DM client 200 with DM dispatch environment file, and request DM client 200 produces DM scheduling (S50).The DM client 200 of requested generation DM scheduling is confirmed corresponding order (request), and uses DM dispatch environment file to produce DM scheduling subtree, then utilizes DM client 200 to send its result to DM server 100 (S51 and S52).Then, the command execution condition (S53) of DM client 200 inquiry DM scheduling subtrees.When respective conditions satisfied, DM client 200 was processed the DM order (S54) of scheduling, and optionally result is reported to DM server 100 (S55).
Change the function of DM scheduling
Along with DM server 100 changes the DM dispatch environment file that has been mounted and passes through the DM dispatch environment file of DM agreement transmission through changing, request changes DM dispatches (for the processing that transmits DM dispatch environment file).Its signal stream is the same with the signal stream in the above-mentioned DM scheduled for executing.In this case, because in this equipment, there has been DM scheduling subtree, usually can use Replace (replacement) order.When carrying out the processing that is used for transmission DM dispatch environment file, the DM server allows the DM client to manage the DM order that all are scheduled by transmitting autocommand by group.In addition, when carrying out the processing that is used for transmission DM dispatch environment file, should by in autocommand, comprise UI alarm order, before carrying out for the processing that changes DM dispatch environment file, receive the user and confirm.After receiving user's affirmation, DM dispatch environment file installation/recombination function unit 31 reconstruct DM dispatch environment file in equipment of DM client 100.
Namely, DM scheduling installation/recombination function unit 31 uses the new DM dispatch environment file that has transmitted to produce new DM scheduling subtree in DM tree 40, and notice DM server 100 results (being illustrated by the broken lines) for the request that changes DM dispatch environment file.
In other words, as shown in Figure 14, DM server 100 sends new DM dispatch environment file to DM client 200 and asks DM client 200 to change DM scheduling (S60).Asked to change the order (request) corresponding to DM client 200 checkings of DM scheduling, and used new DM dispatch environment file to change DM scheduling subtree, then the result of change is transmitted to DM server 100 (S61 and S62).
The function of deletion DM scheduling
Deletion DM scheduling relates to the DM tree that deletion has produced, the DM scheduling subtree 41 in DM tree 40 of namely utilizing DM server 100 to produce.The request of deletion DM dispatch environment file is sent to dispatch environment file delete function unit 36 (S20) of DM client 200 from the dispatch environment file deletion requests functional unit 12 of DM server 100.At this moment, dispatch environment file deletion requests functional unit 12 uses the URI of DM scheduling subtree 41 to be deleted that the DeleteDM order is sent to dispatch environment file delete function unit 36.Therefore, DM scheduling subtree 41 corresponding to dispatch environment file delete function unit 36 deletions.As a result, the DM dispatch environment file that 36 deletions of dispatch environment file delete function unit have been mounted, the notified dispatch environment file deletion requests of the result of deletion functional unit 12 (S21).
Namely, as shown in Figure 15, DM server 100 transmits Delete DM and orders to DM client 200, and the 200 deletion DM scheduling (S70) of request DM client.The DM client 200 of having asked to delete the DM scheduling is verified corresponding order (request) and changes existing DM scheduling subtree that then the result of change is transmitted to DM server 100 (S71 and S72).
The function of report DM dispatch state
The situation of having carried out the report of DM dispatch state to utilizing status report to choose provides explanation, and this situation namely command processing result is reported to the situation of DM server 100.Yet, when making a mistake in the processing of carry out to be used for confirming the command execution condition, or when carrying out the termination of user's request scheduling environment file when confirming to process the user, can carry out the report of DM dispatch state.In these cases, dispatch environment file status function of reporting unit 35 transmits DM dispatch environment file status report PDU to DM server 100.The status report processing function unit 11 that has received the DM server 100 of control PDU is carried out DM dispatch environment file status report processing.
As previously mentioned, in the present invention, the DM dispatch environment file that server transmits the DM order and comprises schedule information is to the client in the equipment, and client install DM dispatch environment file with after carry out corresponding DM according to schedulable condition and order.As a result, the DM schedule information of effectively dynamic management client of server.
Namely, in the prior art, for so that server can be confirmed the particular state of terminal, periodically produce the state of DM dialogue and inquiry terminal.But this method requires a large amount of communication resources does not obtain special result.As a result, it causes the waste of the communication resource and the shortening of battery use case.Therefore, shown in the present invention, when end under specific circumstances the time, the state of terminal is reported to server to solve such problem.
In addition, in terminal, can install or exist a lot of programs, for example diagnostic program, state recording program, virus checker etc.Using in the situation of the present invention, the DM server can operation dispatching, like this program can the expected time put or expectation state under carry out.In case program implementation is scheduled, server does not need to set up individually the DM dialogue with executive program at every turn, thereby causes the reduction of radio resource loss.These advantages can not be useful in the situation that connects communication channel between DM client and the DM server.
In addition, being used for correctly, a plurality of parameters of operating terminal are present in terminal.Determine the value of these parameters, so that terminal can obtain optimum performance.Yet, if when using terminal, change environment for use, can adjust optimum parameter value according to this change so.Therefore, the application of the invention, but the environment of server sense terminals, operation dispatching uses optimum parameter value to detect according to this thus.Can carry out in real time and do not need independent DM dialogue for this adjusting of parameter value, thereby user satisfaction and superior performance are provided.
The present invention can realize by various ways and not depart from spirit of the present invention or intrinsic propesties, can also know that the above embodiments are not limited by the details of aforementioned description, unless otherwise noted, but can be as explaining widely in the spirit and scope that define in claims, so all fall into the boundary line of claim and the change within the scope and being equal to of modification or these boundary lines and scope and are also included within accessory claim.
Claims (27)
1. device management scheduling method in terminal, the method use device management protocol to utilize the management of server actuating equipment, and the method comprises:
Use device management protocol by the scheduling that be used for equipment control of device management session reception from described server, wherein said scheduling comprises device management command and is used for carrying out the trigger of described device management command;
The scheduling that receives is installed in the equipment control target; And
Carry out described device management command and need not to receive device management command from described server in response to being included in described trigger in the described scheduling, and
According in described equipment control target, choosing node to the result of the described device management command of described server report executing,
Wherein, whether the described result who chooses the described device management command of node indication execution will report to described server.
2. according to claim 1 method also comprises the new scheduling of installing from described server.
3. according to claim 1 method also comprises the request that receives from the described scheduling of deletion of described server.
4. according to claim 1 method, extensible markup language (XML) document format is observed in wherein said scheduling.
5. according to claim 1 method, wherein said scheduling further comprise one or more in following:
Node for the described trigger of carrying out described device management command;
The node that is used for described device management command; And
The node that is used for user interactions.
6. according to claim 5 method, wherein each described node comprises one or more elements.
7. according to claim 5 method, the described node that wherein is used for described trigger comprise following one or more:
Be used for defining the duration element of special time value or time range;
The period element that is used for the definition time cycle; And
Be used for defining the threshold value element of threshold value.
8. according to claim 1 method, described scheduling wherein is installed comprises:
Check the validity of the scheduling that receives; And
Use corresponding scheduling to generate at least one or a plurality of subtree in the device management tree.
9. according to claim 1 method, wherein, described scheduling further comprises one or more in following:
The ID node;
The trigger node;
The order node; And
The user interactions node.
10. according to claim 9 method, wherein said trigger node represents be used to the condition of carrying out described device management command, wherein, described condition indicates described device management command with the time that is performed, and described order node represents described device management command.
11. representing whether should receive the user when satisfying described trigger, method according to claim 9, wherein said user interactions node confirm.
12. method according to claim 1, wherein said equipment comprise terminal, personal digital assistant PDA, notebook PC and Desktop PC at least one.
13. method is according to claim 1 wherein carried out described device management scheduling and is comprised:
Check whether described trigger satisfies;
Information and executing user according to user interface when satisfying described trigger confirms; And
When confirming, described user carries out described device management command when receiving.
14. the device management scheduling method in terminal, the method utilize the management of server actuating equipment, the method comprises:
To be installed to for the scheduling of equipment control the equipment control target; Wherein use device management protocol to receive described scheduling by device management session from described server;
According to the trigger actuating equipment administration order that is included in the described scheduling, wherein carry out described device management command in response to described trigger, and need not to receive the device management command from described server,
According in described equipment control target, choosing node to the result of the described device management command of described server report executing,
Wherein, whether the described result who chooses the described device management command of node indication execution will report to described server, and
Wherein, described equipment control target has the access control lists of the identifier that comprises described server, and this server has described scheduling, and described scheduling comprises device management command and is used for carrying out the trigger of described device management command.
15. method according to claim 14 also comprises the new scheduling of installing from described server.
16. method according to claim 14 also comprises the request of deleting described scheduling from described server that receives.
17. method according to claim 14, wherein said scheduling further comprise one or more in following:
Node for the described trigger of carrying out described equipment control;
The node that is used for described device management command;
The node that is used for user interactions.
18. method according to claim 17, the described node that wherein is used for described trigger comprise following one or more:
Be used for defining the duration element of special time value or time range;
The period element that is used for the definition time cycle; And
Be used for defining the threshold value element of threshold value.
19. method according to claim 14, described scheduling further comprise one or more in following:
The ID node;
The trigger node;
The order node;
The user interactions node.
20. method according to claim 19, wherein said trigger node represents the condition for the actuating equipment administration order, the condition that wherein said condition indicates described device management command to be performed, and described order node represents described device management command.
21. representing whether should receive the user when satisfying described trigger, method according to claim 19, wherein said user interactions node confirm.
22. method is according to claim 14 wherein carried out described device management scheduling and is comprised:
Check whether satisfy described trigger;
Information and executing user according to user interface when satisfying described trigger confirms; And
When confirming, described user carries out described device management command when receiving.
23. a mobile communication terminal comprises:
Equipment control DM client is used for using DM agreement and server apparatus for establishing management of dialogs;
Reception is from the scheduling that is used for equipment control of described server;
To be installed to the equipment control target from the described scheduling that described server receives, and according in described equipment control target, choosing node to the result of the described device management command of described server report executing;
Wherein, whether the described result who chooses the described device management command of node indication execution will report to described server, and
Wherein said scheduling comprises device management command and is used for carrying out the trigger of described device management command that wherein, described device management command is carried out in response to described trigger, and need not to receive the device management command from described server; And
The DM scheduling broker is if be used for satisfying described trigger then carry out described device management command.
24. terminal according to claim 23, wherein, if need the user to confirm process, described DM scheduling broker is confirmed process according to the information and executing user of the user interactions of described equipment control target.
25. terminal according to claim 23, described DM scheduling broker use the information of device management server node of described equipment control target to the result of the described device management command of another server report executing.
26. terminal according to claim 23, wherein said equipment control target comprises:
The ID node;
The trigger node;
The order node; And
The user interactions node.
27. terminal according to claim 26, described ID node represents the identifier of described scheduling, and described trigger indication is used for carrying out the condition of described device management command, the wherein said condition indication time when described device management command should be performed.
Applications Claiming Priority (13)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR20040053663 | 2004-07-09 | ||
| KR10-2004-0053663 | 2004-07-09 | ||
| KR1020040053663 | 2004-07-09 | ||
| KR10-2004-0061846 | 2004-08-05 | ||
| KR20040061846 | 2004-08-05 | ||
| KR1020040061846 | 2004-08-05 | ||
| US62159004P | 2004-10-22 | 2004-10-22 | |
| US60/621,590 | 2004-10-22 | ||
| US67704605P | 2005-05-02 | 2005-05-02 | |
| US60/677,046 | 2005-05-02 | ||
| KR1020050060764A KR100641238B1 (en) | 2004-07-09 | 2005-07-06 | Device management system and device management command scheduling method thereof |
| KR1020050060764 | 2005-07-06 | ||
| KR10-2005-0060764 | 2005-07-06 |
Related Parent Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005800201480A Division CN100514915C (en) | 2004-07-09 | 2005-07-08 | Device management system and device management command scheduling method thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101442529A CN101442529A (en) | 2009-05-27 |
| CN101442529B true CN101442529B (en) | 2013-05-01 |
Family
ID=38077187
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005800201480A Expired - Fee Related CN100514915C (en) | 2004-07-09 | 2005-07-08 | Device management system and device management command scheduling method thereof |
| CN 200810186737 Expired - Fee Related CN101442529B (en) | 2004-07-09 | 2005-07-08 | Device management system and device management command scheduling method thereof |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005800201480A Expired - Fee Related CN100514915C (en) | 2004-07-09 | 2005-07-08 | Device management system and device management command scheduling method thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN100514915C (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101409632B (en) * | 2007-10-10 | 2011-02-02 | 华为技术有限公司 | Transmission method, system and apparatus for remote procedure call command |
| CN101505550B (en) | 2008-02-04 | 2012-08-22 | 华为技术有限公司 | Method, terminal, apparatus and system for device management |
| US9026582B2 (en) * | 2010-03-23 | 2015-05-05 | Htc Corporation | Device management methods and related apparatus for enhancing applicability of status messages in response to commands |
| CN106982445A (en) * | 2016-01-19 | 2017-07-25 | 西安中兴新软件有限责任公司 | A kind of transmission method, equipment and the system of abnormal information of upgrading |
| JP6447689B1 (en) * | 2017-09-11 | 2019-01-09 | 富士ゼロックス株式会社 | Information processing apparatus and program |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1373415A (en) * | 2001-02-22 | 2002-10-09 | 日本电气株式会社 | Network application program scatter executing system, terminal, network application program executing method, and terminal operating method |
-
2005
- 2005-07-08 CN CNB2005800201480A patent/CN100514915C/en not_active Expired - Fee Related
- 2005-07-08 CN CN 200810186737 patent/CN101442529B/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1373415A (en) * | 2001-02-22 | 2002-10-09 | 日本电气株式会社 | Network application program scatter executing system, terminal, network application program executing method, and terminal operating method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1969504A (en) | 2007-05-23 |
| CN101442529A (en) | 2009-05-27 |
| CN100514915C (en) | 2009-07-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7752296B2 (en) | Device management system and device management command scheduling method thereof | |
| CN109889551B (en) | Method for accessing intelligent hardware to Internet of things cloud platform | |
| CN101515926B (en) | Device management method for device management system | |
| EP1766866B1 (en) | Network device management command scheduling | |
| AU2006201516B2 (en) | Service delivery platform | |
| US7701859B2 (en) | Method and apparatus for identifying problem causes in a multi-node system | |
| US20060136558A1 (en) | Event manager for use in a facilities monitoring system having network-level and protocol-neutral communication with a physical device | |
| CN101442529B (en) | Device management system and device management command scheduling method thereof | |
| GB2427490A (en) | Network usage monitoring with standard message format | |
| EP1977324B1 (en) | Terminal and method for performing device management scheduled based on threshold | |
| CN101227470B (en) | System and method of business management | |
| CN106452839A (en) | Message report method and device | |
| US20040260774A1 (en) | Protocol method for provisioning services | |
| CN106713471A (en) | Method and device for acquiring configuration file | |
| CN109274715A (en) | The platform resource management system of vehicle-mounted multi-channel communication systems | |
| KR100766567B1 (en) | Contents update relay system and method for providing contents update information to mobile equipment | |
| Gorski et al. | SOA-readiness of REST | |
| RU2337489C1 (en) | System of device control and its method for device control command scheduling | |
| CN101706901A (en) | Device and method for realizing shielding of different working flow products | |
| CN113542313B (en) | Third-party Internet of things platform equipment docking system and method | |
| Falchuk et al. | An open service platform for deploying and managing services at network edges | |
| KR101101614B1 (en) | Service control system and method at end-to-end virtual home network | |
| KR20150049827A (en) | Mobile integrated control server | |
| CN117082129A (en) | Big data acquisition platform system based on distributed architecture | |
| KR20100099189A (en) | System for connecting universal plug and play (upnp) devices in a upnp network |
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: 20130501 Termination date: 20190708 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |