CN1969504A - Device management system and device management command scheduling method thereof - Google Patents

Device management system and device management command scheduling method thereof Download PDF

Info

Publication number
CN1969504A
CN1969504A CN 200580020148 CN200580020148A CN1969504A CN 1969504 A CN1969504 A CN 1969504A CN 200580020148 CN200580020148 CN 200580020148 CN 200580020148 A CN200580020148 A CN 200580020148A CN 1969504 A CN1969504 A CN 1969504A
Authority
CN
China
Prior art keywords
device management
command
node
scheduling
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN 200580020148
Other languages
Chinese (zh)
Other versions
CN100514915C (en
Inventor
金兑炫
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of CN1969504A publication Critical patent/CN1969504A/en
Application granted granted Critical
Publication of CN100514915C publication Critical patent/CN100514915C/en
Expired - Fee Related legal-status Critical Current
Anticipated expiration legal-status Critical

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

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 equipment management system and device management command scheduling method thereof particularly.
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 requests 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 to then confirm 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, the process that makes the DM server can carry out the order of DM server under expected time point, state did not also 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, a plurality of incident maybe when taking place in the internal state of considering equipment, can not outside the DM dialogue, (afterwards) carry out such DM order, and can not under 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, make and can solve problem by adequate measures before problem may take place.Equally, these prior art restrictions also need to be used to carry out the new DM dialogue of DM order, and therefore need 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, the state that wherein device management command or the data sync order that server can dispatching client, so client can reporting facility, the program of operation dispatching are also used 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 from server and give client; Use the dispatch environment file of this transmission to produce device management tree by client, and the apparatus for establishing management and dispatching; And carry out this device management scheduling according to the command execution condition (just being used for exectorial condition) of the device management scheduling of setting up by client.
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 requests 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, use this device management scheduling environment file to set up one or more at least device management scheduling subtrees.
In order to reach these and other advantages and according to purpose of the present invention, equipment management system comprises: server is used to produce and transmit the dispatch environment file (scheduling context) that comprises device management command and be used to carry out the schedule information (schedule) of this device management command; Client, it uses the device management scheduling environment file that is transmitted to produce device management tree, produce device management scheduling thus, and come the actuating equipment management and dispatching according to the command execution condition (just being used for exectorial condition) of the device management scheduling that is produced.
Preferably, server transmits new dispatch environment file and gives 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 its equipment control that is used to produce with server is talked with, and receives the dispatch environment file from server afterwards; And scheduler module, be used to use 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 the corresponding equipment administration order, 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: the functional unit that is used for the dispatch environment file that sends from server is sent to scheduler module; Be used for order of dispatching and the functional unit that the execution result of correspondence order is sent to scheduler module according to the notice execution correspondence of 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: first functional unit is used to use the dispatch environment file that transmits from server to produce the device management scheduling subtree; Second functional unit is used for the dispatching command executive condition (just 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, its command execution functional unit that is used for request command scheduler module when the command execution condition is satisfied comes the actuating equipment administration order; The 4th functional unit, its be used for according to the device management scheduling subtree choose that nodal value determines whether should be to server report command execution results about the command execution functional unit; The five-function unit, it is used for to the command execution results of server report from the transmission of the 4th functional unit, or the check result of the command execution condition of 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 requests.
Preferably, in this 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 this method and system, the dispatch environment file comprises: the information element that is used for the command execution condition; The information element of the device management command that is used to dispatch; The information element that is used for user interface; And be used for the information element that status report is chosen (gate).
Preferably, in this 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; Be used to represent the node of the executive condition of the device management command dispatched; Be used to represent the node of the information of user interface; And the node or be used to that is used to represent whether to report the execution result of order is represented the node to the server address of the execution result of its report order.
Preferably, in this method and system, equipment is represented customer premises equipment for example 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 in conjunction with the accompanying drawings.
Description of drawings
Included accompanying drawing is used to provide 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 explaining principle of the present invention together 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 of the structure of order XML (extensible markup language) document shown in the displayed map 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 of the content of definition 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 signal flow 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 flow 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 signal flow 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, wherein the server device management scheduling of administrative client dynamically is used for equipment control or data sync; And be provided at device management scheduling method in the corresponding 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 the state of the correspondingly spontaneous reporting facility of client (for example terminal), 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, server transmits the client that comprises that DM orders and equipment control (DM) the dispatch environment file (schedulingcontext) of schedule information is given target device, and this client uses this DM dispatch environment file to produce DM tree (just 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 (just being used for exectorial condition) after this and order.Preferably, target device refers to subscriber's installation (UE) for example terminal, PDA, notebook-PC (PC) and Desktop PC etc., for convenience, only provides the explanation for terminal in these customer premises equipment.Introduce preferred embodiments more of the present invention below 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 used to produce DM dispatch environment file and sends it to equipment (for example terminal); DM client 200, it is used for using the dispatch environment file that sends from DM server 100 to produce the DM tree in terminal, and carries out corresponding DM when being satisfied when command execution condition (just being used for exectorial condition) and order.
DM client 200 comprises: command processing module 20 is used to receive the dispatch environment file from DM server 100; Scheduler module 30, be used to use the dispatch environment file that transmits from command processing module 20 to produce DM tree 40, and when satisfying the command execution condition, the command execution condition is satisfied is notified to command processing module 20, carrying out corresponding DM order, thereby and receive DM process of commands results from command processing module 20 and optionally it is reported to the DM server.
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 of the DM that dispatches order, be used for the information element " UserInter " of user interface, be used for status report and choose the information element of (gating) or the like.
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, just dispatches node Sched_1, SchedID node, Condition node, Commands node, UserInter node, Gating node or the like.
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 " (basis, position node just).The Condition node indicates to carry out the condition of DM order.The Commands node is represented the DM that the is scheduled order that (just 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 DM the 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 representation server has administration authority to each node.
DM tree 40 refers to such logic data structure, and wherein the DM server can be by DM dialogue and the DM agreement all identical to all dissimilar equipment, comes the information in the Universal Database 50 of managed storage in equipment remotely.DM tree 40 provides title for each information in the Universal Database 50 of being stored in and is provided for the path of each information of access.DM tree 40 comprises the logic of information for example and physical format or the like attribute.
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 time point or the state that schedulable condition is satisfied down will be by the DM order of DM client process.Each command lanuage is made up 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.Scheduling explanation is completely 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, wherein the trigger that produces from each element will be passed to the DM client.Just, if the value of discrete cell element is " vacation ", then the trigger that 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 logical value and trigger described period simultaneously, and described particular point in time only defines trigger.
Fig. 6 is the embodiment of duration Dur element.
With reference to figure 6, as the plaintext based on the following specific syntax that will describe, the content of duration element is by using the starting point and the end point of certain operations symbol " .. " scope setup time.The duration element uses date and time to represent.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 as the cell scheduling element that is used for the definition time cycle, uses with another cell scheduling element, and periodically produces sequential trigger (sequential trigger) when condition is for " very ".
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 " very " and repeatedly produced during by the cycle maintenance " very " 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 certain threshold level.The Th element also has the property value " MgmtObj " and the URI (unified 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 constitutes.
Fig. 7 is the figure of definition threshold value (Th) element content, and it is described based on the ABNF (expansion Bacchus-Nore normal form, Augmented Backus-Naur Form) by the RFC2234 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 of being 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 the order that is used to notify client to be associated should be performed.At this moment, relevant by the trigger of trigger element generation with the change of the management objectives value that is associated.
" 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 is represented each increment.At this moment, the boundary value of incident scope utilizes presentation of events to begin usually to represent with the incident unit of incident end.When the incident of incident scope begins to take place, be " very " by the logical value of the condition of " EventRange " element representation.When the incident of incident scope finished to take place, the logical value of this condition was " vacation ".The such incident of " Event " expression: the management objectives value has particular value or falls in the certain limit.Therefore, can use threshold value, sets of threshold values and threshold range to represent " Event ".For example, wherein the management objectives value incident 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 incident 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 " very " 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 certain threshold level 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 incident scope is begun the incident element representation that finishes with incident by presentation of events.When the incident of incident scope begins to take place, be " very " by the logical value of the condition of " EventRange " element representation.When the incident of incident scope finished to take place, the logical value of condition was " vacation ".Representations of events management objectives value has particular value or falls into the interior incident of certain limit.Therefore, can use threshold value, sets of threshold values and threshold range to represent this incident.For example, wherein the management objectives value incident that has particular value or fall into the scope of default value can be this incident.The one or both sides of incident scope can be opened, and the open scope in both sides is called as incident 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 the embodiment that is used to use Th element structure DM dispatch environment file.
Embodiment shown in Figure 10 represents to be used for the DM dispatch environment file of " 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 or the like.
Dispatch environment file generations/the changes functional unit 10 generation DM dispatch environment files that in DM server 100, are provided with, and ask the command processing module 20 of DM client 200 to be installed or change DM dispatch environment file.
When DM server 100 was asked installation/change dispatch environment file by the request transmitting function unit 21 of command processing module 20, dispatch environment file installation/recombination function unit 31 produced DM scheduling subtree to produce the DM tree.If desired, 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 on the DM tree, exists corresponding to assign thresholds, or at particular point in time, or, can determine whether the command execution condition is satisfied in equipment according to whether particular event has taken place.When satisfying the command execution condition, if desired, 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) by response message and gives scheduler module 30.Response message, for example, comprise relate to order carry out fully, because how or the like which kind of reason makes a mistake, equipment state command execution results code after fill order.
Status report is chosen functional unit 34 and is filtered the data of waiting to report to DM server 100.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.
Dispatch environment file status function of reporting unit 35 is chosen the command execution results (state/result/generic alarm) that functional unit 34 transmits 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 the PDU that is used for delivery status command lanuage, result command language, generic alarm command lanuage (status PDU, PDU and generic alarm PDU) as a result, and the termination request PDU of the DM dispatch environment file of carrying out for the user.
If desired, 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 desired, status report is chosen functional unit 34 and also can be integrated together (represented as dotted line) with dispatch environment file status function of reporting unit 35.
Provide more detailed explanation referring now to accompanying drawing to the function of execution/change/deletion DM scheduling and the function of report 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 of carrying out between DM server 100 and DM client 200 (authentication) was handled.
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.
Just, as shown in Figure 11 and Figure 12, the dispatch environment file generation/change functional unit 10 of DM server 100 produces the dispatch environment file of the DM order and the schedule information of the execution that comprises relevant DM order.Dispatch environment file generation/change functional unit 10 is sent to equipment (for example terminal) by the DM agreement with the dispatch environment file that produces.Here, dispatch environment file generation/change functional unit 10 use ADD order and add the DM order, and use autocommand to make all DM orders by a group scheduling.As a result, dispatch environment file generation/change functional unit 10 permission equipment (terminal just) are handled one group DM order together.Equally, this dispatch environment file generation/change functional unit 10 also comprises 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,, be sent to dispatch environment file installation/recombination function unit 31 (S11) of scheduler module 30 again by the request transmitting function unit 21 of command processing module 20 from DM server 100.
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 the grammer and the context of the XML document of the DM dispatch environment file that 31 checkings of dispatch environment file installation/recombination function unit are transmitted be correct, and whether DM dispatch environment file can be mounted (for example 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 just after DM scheduling subtree 41, the schedule information XML document of DM client 200 analytical databases 50 comes operation dispatching to handle.Just, 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 constantly check the state (S12) that DM command execution condition is satisfied then.Whether the command execution condition is satisfied, and can for example determine when another management objectives value that exists on the DM tree reaches setting threshold or at the particular point in time place or according to whether particular event has taken place in equipment.
When satisfying the command execution condition,, then carry out the user and confirm to handle if should receive user's affirmation according to the information of the user interface UserInter in the DM scheduling subtree 41.In the user confirms to handle, on screen, provide guiding (just notice, information etc.), and therefore the user can allow or cancel the execution that DM orders about execution DM order.If the user cancels the DM command execution, command execution condition affirmation functional unit 32 is not carried out the DM order of being dispatched but is carried out the processing that is used to confirm the command execution condition again.
If satisfy the command execution condition in the command execution condition is confirmed functional unit 32, 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 to report DM dispatch environment file status.Status report PDU consists essentially of PDU (status PDU, PDU and generic alarm PDU) as a result, and these PDU are used for delivery status command lanuage, result command language and generic alarm command lanuage.
Just, 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).Be requested to produce the corresponding order (request) of DM client 200 affirmations of DM scheduling, and used DM dispatch environment file to produce DM scheduling subtree, utilized DM client 200 to send its result to DM server 100 (S51 and S52) then.Then, the command execution condition (S53) of DM client 200 inquiry DM scheduling subtrees.When respective conditions satisfied, DM client 200 was handled 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 (being used to transmit the processing of DM dispatch environment file).Its signal flow is the same with the signal flow in the above-mentioned DM scheduled for executing.In this case, because in this equipment, there has been DM scheduling subtree, can use Replace (replacement) order usually.When execution was used to transmit the processing of DM dispatch environment file, the DM server allowed the DM client to manage all DM that is scheduled orders by transmitting autocommand by group.In addition, when execution is used to transmit the processing of DM dispatch environment file, should be by in autocommand, comprising UI alarm order, be used to change in execution and receive the user before the processing of DM dispatch environment file 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.
Just, 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 is for the processing of request result's (being illustrated by the broken lines) who 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 corresponding order (request) of DM client 200 checkings of DM scheduling, and used new DM dispatch environment document change DM scheduling subtree, the result of change is transmitted to DM server 100 (S61 and S62) then.
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 just 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, the corresponding DM scheduling subtree 41 of 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).
Just, 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 the result of change is transmitted to DM server 100 (S71 and S72) then.
The function of report DM dispatch state
Provide explanation to the situation of utilizing status report to choose to carry out the report of DM dispatch state, this situation just command processing result is reported to the situation of DM server 100.Yet, when making a mistake in the processing that is used to confirm the command execution condition in execution, or when carrying out the termination of user's request scheduling environment file when confirming to handle 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 and gives 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 given 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 server dynamic management client effectively.
Just, in the prior art,, periodically produce the state of DM dialogue and inquiry terminal in order to make server can confirm the particular state of 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 that battery uses incident.Therefore, as 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 or the like.Using under 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 under 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, make terminal can obtain optimum performance.Yet,, can adjust optimum parameter value according to this change so if when using terminal, change environment for use.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 multiple mode 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 (56)

1. device management scheduling method in equipment management system, wherein server utilizes the client executing equipment control by device management protocol, and this method comprises:
Transmit the dispatch environment file from described server to described client;
Use the dispatch environment file that is transmitted to produce device management tree by described client, and the apparatus for establishing management and dispatching; And
According to the command execution condition of the device management scheduling of being set up, by the described device management scheduling of described client executing.
2. according to the method for claim 1, comprise that also use produces device management tree from the new dispatch environment file that described server transmits, and change this device management scheduling afterwards.
3. according to the method for claim 1, also comprise according to the status report in the device management tree that is produced and choose information, report the execution result of this device management scheduling by described client selectively to described server.
4. according to the method for claim 1, also comprise the device management scheduling of setting up in advance by the described client deletion of described server requests.
5. according to the process of claim 1 wherein that described dispatch environment file comprises device management command and the schedule information that is associated with the execution of this order, and has extensible markup language (XML) document format.
6. according to the process of claim 1 wherein that described dispatch environment file transmits with adding order, autocommand and UI (user interface) alarm order.
7. according to the process of claim 1 wherein that described dispatch environment file comprises:
The information element that is used for the command execution condition;
The information element of the device management command that is used to dispatch;
The information element that is used for user interface; And
Be used for the information element that status report is chosen.
8. according to the method for claim 7, the wherein said information element that is used for the command execution condition is made of at least one or a plurality of simple schedule element, and described simple schedule element is made of one or more cell scheduling elements.
9. method according to Claim 8, wherein said cell scheduling element comprises:
Be used to define the duration element of special time value or time range;
The period element that is used for the definition time cycle; And
Be used to define threshold value element with the internal state of facility management client or information-related scheduled basis.
10. according to the process of claim 1 wherein that the step of described apparatus for establishing management and dispatching comprises:
The validity of the device management scheduling environment file that checking is transmitted; And
When verifying described dispatch environment file fully, use this corresponding dispatch environment file to produce at least one or multiple equipment management scheduling subtree more.
11. according to the method for claim 10, the device management scheduling subtree comprises:
The Sched_x node;
The SchedId node;
The Condition node;
The Commands node;
The UserInter node; And
The Gating node,
Wherein x be integer (as 1,2,3,4 ...).
12. according to the method for claim 11, wherein the Sched_x node is represented each device management scheduling, and the SchedId node is represented the identifier of described device management scheduling environment file.
13. according to the method for claim 11, wherein the Condition node represents wherein to carry out the condition of the device management command of being dispatched, and the Commands node is represented the device management command dispatched.
14. according to the method for claim 11, wherein the UserInter node represents that the user that whether should receive relevant this correspondence order when satisfying the command execution condition confirms, and the Gating node represents whether the DM command execution results will be reported to the DM server.
15. according to the method for claim 11, wherein said device management scheduling subtree also comprises equipment control Mgmtsvr node, is used to indicate to the address of the server of its report command execution results.
16. according to the process of claim 1 wherein that described equipment is meant subscriber's installation, for example terminal, PDA (personal digital assistant), notebook type PC, Desktop PC or the like.
17. according to the process of claim 1 wherein that the step of described actuating equipment management and dispatching comprises:
Read the command execution conditional information of described dispatch environment file, and check whether this command execution condition is satisfied;
When this command execution condition is satisfied, according to information and executing user's affirmation of user interface; And
When receiving the device management command of carrying out when described user confirms corresponding to described command execution condition.
18. an equipment management system, it comprises:
Server, it is used for producing and transfer equipment management and dispatching environment file, and this device management scheduling environment file comprises device management command and is used to carry out the schedule information of this device management command; And
Client, it is used for producing device management scheduling by using the device management scheduling environment file that is transmitted to generate device management tree, and carries out described device management scheduling according to the command execution condition of the device management scheduling that is produced.
19. system according to claim 18, wherein said server transmits new dispatch environment file to described client, to ask described client to change this device management scheduling, and transfer equipment management delete command, delete preassembled device management scheduling environment file to ask described client.
20. according to the system of claim 18, wherein said client is chosen information according to the status report of described device management scheduling, reports the execution result of described device management scheduling selectively to described server.
21. according to the system of claim 18, wherein said dispatch environment file has extensible markup language (XML) document format, and together is transmitted with interpolation order, autocommand and UI alarm order.
22. according to the system of claim 18, wherein said dispatch environment file comprises:
The information element that is used for the command execution condition;
The information element of the device management command that is used to dispatch;
The information element that is used for user interface; And
Be used for the information element that status report is chosen.
23. according to the system of claim 22, the wherein said information element that is used for the command execution condition is made of at least one or how simple schedule element, and described simple schedule element is made of one or more cell scheduling elements.
24. according to the system of claim 22, wherein said cell scheduling element comprises:
Be used to define the duration element of special time value or time range;
The period element that is used for the definition time cycle; And
Be used to define threshold value element with the internal state of facility management client or information-related scheduled basis.
25. according to the system of claim 18, the validity of the dispatch environment file that wherein said client validation transmitted produces the device management scheduling subtree afterwards, thereby sets up described device management scheduling.
26. according to the system of claim 25, wherein the device management scheduling subtree comprises:
The Sched_x node;
The SchedId node;
The Condition node;
The Commands node;
The UserInter node; And
The Gating node,
Wherein x be integer (as 1,2,3,4 ...).
27. according to the system of claim 26, wherein the Sched_x node is represented each device management scheduling, and the SchedID node is represented the identifier of described device management scheduling environment file.
28. according to the system of claim 26, wherein the Condition node is represented the wherein condition of the device management command of operation dispatching, and the Commands node is represented the device management command dispatched.
29. according to the system of claim 26, wherein the UserInter node represents that the user that whether should receive relevant this correspondence order when satisfying the command execution condition confirms, and the Gating node represents whether the DM command execution results will be reported to the DM server.
30. according to the system of claim 26, wherein said device management scheduling subtree also comprises equipment control Mgmtsvr node, this Mgmtsvr node is represented the address of the server that described command execution results will report to.
31. according to the system of claim 18, wherein said server comprises:
The functional unit that is used to produce described device management scheduling environment file and the described client foundation of request or changes described device management scheduling;
Be used to transmit the functional unit of deletion administration order to described client and the described client sweep equipment management and dispatching of request; And
Be used to handle the functional unit of the status report of the device management scheduling of reporting by described client.
32. according to the system of claim 18, wherein said client comprises:
Command processing module, its equipment control that is used to produce with described server is talked with, and receives the described dispatch environment file from described server then; And scheduler module, it is used to use the described dispatch environment file that transmits from described command processing module to produce device management tree, when satisfying described command execution condition, the command execution condition is satisfied is notified to described command processing module, to carry out the corresponding equipment administration order, and receive result, selectively this result is reported to described server from the device management command of described command processing module.
33. according to the system of claim 32, wherein said command processing module comprises:
Be used for transmitting the functional unit of described dispatch environment file to described scheduler module from described server;
Be used for carrying out the order of corresponding scheduling and the execution result of correspondence order being sent to the functional unit of described scheduler module according to the notice of described scheduler module; And
Be used for the dispatch environment file status report that transmits from described scheduler module being sent to the functional unit of described server according to this command execution results.
34. according to the system of claim 18, wherein said scheduler module comprises:
First functional unit, it is used to use the described dispatch environment file that transmits from described server to produce the device management scheduling subtree;
Second functional unit, it is used to read the dispatching command executive condition (just exectorial condition) of described device management scheduling subtree, and constantly checks the state that described command execution condition is satisfied thus;
The 3rd functional unit, it is used for asking the command execution functional unit of described command scheduling module to carry out this device management command when satisfying described command execution condition;
The 4th functional unit, its be used for according to described device management scheduling subtree choose that nodal value determines whether should be to the command execution results of described server report about described command execution functional unit;
The five-function unit, it is used for the check result of the command execution condition of the execution result of order from described the 4th functional unit to the report of described server that transmit from or described second functional unit; And
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 of described server requests.
35. according to the system of claim 34, wherein, if desired, described second functional unit is carried out the user according to the user interface information of described device management scheduling subtree and is confirmed to handle.
36. according to the system of claim 34, wherein said five-function unit uses the information of the device management server node of described device management scheduling subtree that command execution results is reported to another server.
37. the device management scheduling method in terminal, this terminal with server apparatus for establishing management of dialogs after, use device management protocol to utilize described server actuating equipment management, this method comprises:
Reception is from the dispatch environment file of described server;
The described dispatch environment file that use receives produces the device management scheduling subtree;
According to the information of the command execution condition of the device management scheduling subtree that is produced, actuating equipment administration order; And
Status report according to described device management scheduling subtree is chosen information, and the execution result with device management command reports to described server selectively.
38., also comprise the new dispatch environment file of reception, and change described device management scheduling subtree then from described server according to the method for claim 37.
39. according to the method for claim 37, also comprise the device management command of reception, delete the device management scheduling subtree of being set up then from described server.
40. according to the method for claim 37, wherein said dispatch environment file comprises device management command and the schedule information that is associated with the execution of this order, and has extensible markup language (XML) document format.
41. according to the method for claim 40, wherein the dispatch environment file comprises:
The information element that is used for the command execution condition;
The information element of device management command is used to be scheduled;
The information element that is used for user interface; And
Be used for the information element that status report is chosen.
42. according to the method for claim 40, wherein said device management scheduling subtree comprises:
The Sched_x node;
The SchedId node;
The Condition node;
The Commands node;
The UserInter node; And
The Gating node,
Wherein x be integer (as 1,2,3,4 ...).
43. according to the method for claim 42, wherein the Sched_x node is represented each device management scheduling, and the SchedID node is represented the identifier of described device management scheduling environment file.
44. according to the method for claim 42, wherein the Condition node is represented the wherein condition of the device management command of operation dispatching, and the Commands node is represented the device management command dispatched.
45. according to the method for claim 42, wherein UserInter represents that the user that whether should receive relevant corresponding order when satisfying the command execution condition confirms, and the Gating node represents whether the execution result of DM order will be reported to the DM server.
46. according to the method for claim 42, wherein the device management scheduling subtree also comprises equipment control Mgmtsvr node, this Mgmtsvr node is represented the address of the server that command execution results will report to.
47. a mobile communication terminal, it comprises:
Command processing module, it is used to produce with the equipment control dialogue of server and receives dispatch environment file from described server; And
Scheduler module, it is used to use the dispatch environment file that is transmitted by described command processing module to produce device management tree, thereby apparatus for establishing management and dispatching, when the command execution condition of the device management scheduling of being set up is satisfied, command execution condition satisfied is notified to described command processing module, with the device management command of operation dispatching, and reception reports to described server with this result thus selectively from the result of the device management command of described command processing module.
48. according to the terminal of claim 47, wherein said command processing module comprises:
Be used for transmitting the functional unit of described dispatch environment file to described scheduler module from described server;
Be used for carrying out corresponding dispatching command and the execution result of correspondence order being sent to the functional unit of described scheduler module according to the notice of described scheduler module; And
Be used for the dispatch environment file status report that transmits from described scheduler module being sent to the functional unit of described server based on this command execution results.
49. according to the terminal of claim 47, wherein said scheduler module comprises:
First functional unit, it is used to use the described dispatch environment file that transmits from described server to produce the device management scheduling subtree;
Second functional unit, it is used to read the dispatching command executive condition (just exectorial condition) of described device management scheduling subtree, and constantly checks the state that the command execution condition is satisfied thus;
The 3rd functional unit, it is used for asking the command execution functional unit of described command scheduling module to carry out this device management command when satisfying described command execution condition;
The 4th functional unit, the nodal value of choosing that it is used for according to described device management scheduling subtree, determining whether should be to the command execution results of described server report about described command execution functional unit;
The five-function unit, it is used for the check result of the command execution condition of the execution result of order from described the 4th functional unit to the report of described server that transmit from or described second functional unit; And
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 of described server requests.
50. according to the terminal of claim 49, wherein, if desired, described second functional unit is carried out the user according to the user interface information of described device management scheduling subtree and is confirmed to handle.
51. according to the terminal of claim 49, described five-function unit uses the information of the device management server node of described device management scheduling subtree that command execution results is reported to another server.
52. according to the terminal of claim 49, wherein said device management scheduling subtree comprises:
The Sched_x node;
The SchedId node;
The Condition node;
The Commands node;
The UserInter node; And
The Gating node,
Wherein x be integer (as 1,2,3,4 ...).
53. according to the terminal of claim 52, wherein the Sched_x node is represented each device management scheduling, and the SchedID node is represented the identifier of described device management scheduling environment file.
54. according to the terminal of claim 52, wherein the Condition node is represented the wherein condition of the device management command of operation dispatching, and the Commands node is represented the device management command dispatched.
55. according to the terminal of claim 52, wherein UserInter represents that the user that whether should receive relevant corresponding order when the command execution condition is satisfied confirms, and the Gating node represents whether the execution result of DM order will be reported to the DM server.
56. according to the terminal of claim 52, wherein said device management scheduling subtree also comprises equipment control Mgmtsvr node, this Mgmtsvr node is represented the address of the server that command execution results will report to.
CNB2005800201480A 2004-07-09 2005-07-08 Device management system and device management command scheduling method thereof Expired - Fee Related CN100514915C (en)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR1020040053663 2004-07-09
KR20040053663 2004-07-09
KR1020040061846 2004-08-05
US60/621,590 2004-10-22
US60/677,046 2005-05-02
KR1020050060764 2005-07-06

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN 200810186737 Division CN101442529B (en) 2004-07-09 2005-07-08 Device management system and device management command scheduling method thereof

Publications (2)

Publication Number Publication Date
CN1969504A true CN1969504A (en) 2007-05-23
CN100514915C CN100514915C (en) 2009-07-15

Family

ID=38077187

Family Applications (2)

Application Number Title Priority Date Filing Date
CN 200810186737 Expired - Fee Related CN101442529B (en) 2004-07-09 2005-07-08 Device management system and device management command scheduling method thereof
CNB2005800201480A Expired - Fee Related CN100514915C (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
CN 200810186737 Expired - Fee Related CN101442529B (en) 2004-07-09 2005-07-08 Device management system and device management command scheduling method thereof

Country Status (1)

Country Link
CN (2) CN101442529B (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009049542A1 (en) * 2007-10-10 2009-04-23 Huawei Technologies Co., Ltd. A method, system and correlative apparatus for transmitting remote procedure call command
WO2009100632A1 (en) * 2008-02-04 2009-08-20 Huawei Technologies Co., Ltd. Method, terminal, apparatus and system for device management
TWI462015B (en) * 2010-03-23 2014-11-21 Htc Corp Device management methods and systems, and related apparatus
CN106982445A (en) * 2016-01-19 2017-07-25 西安中兴新软件有限责任公司 A kind of transmission method, equipment and the system of abnormal information of upgrading

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6447689B1 (en) * 2017-09-11 2019-01-09 富士ゼロックス株式会社 Information processing apparatus and program

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3743620B2 (en) * 2001-02-22 2006-02-08 日本電気株式会社 Network application distributed execution system

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009049542A1 (en) * 2007-10-10 2009-04-23 Huawei Technologies Co., Ltd. A method, system and correlative apparatus for transmitting remote procedure call command
CN101409632B (en) * 2007-10-10 2011-02-02 华为技术有限公司 Transmission method, system and apparatus for remote procedure call command
US8327391B2 (en) 2007-10-10 2012-12-04 Huawei Technologies Co., Ltd. Method, system and apparatus for transmitting remote procedure call commands
WO2009100632A1 (en) * 2008-02-04 2009-08-20 Huawei Technologies Co., Ltd. Method, terminal, apparatus and system for device management
US8613062B2 (en) 2008-02-04 2013-12-17 Huawei Technologies Co., Ltd. Method, terminal, apparatus, and system for device management in network communications
US9246781B2 (en) 2008-02-04 2016-01-26 Huawei Technologies Co., Ltd. Method, terminal, apparatus, and system for device management
TWI462015B (en) * 2010-03-23 2014-11-21 Htc Corp Device management methods and systems, and related apparatus
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
WO2017124736A1 (en) * 2016-01-19 2017-07-27 中兴通讯股份有限公司 Method, device and system for transmitting upgrade abnormality information

Also Published As

Publication number Publication date
CN101442529A (en) 2009-05-27
CN100514915C (en) 2009-07-15
CN101442529B (en) 2013-05-01

Similar Documents

Publication Publication Date Title
US8161150B2 (en) Device management system and device management command scheduling method thereof
CN1957345A (en) Device management method for device management system
CN1863052A (en) Remote-controlling system and method
CN1859160A (en) Method and its system for managing user stationed equipment configuration
CN1968134A (en) Middleware-based multimedia consolidation service realizing method and system
CN1659843A (en) Method for implementing content delivery network (CDN) internetworking, respective networks and interface component
CN1846402A (en) Specifying management nodes in a device management system
CN1897581A (en) Information exchange system, management server, and method for reducing the network load
EP1766866B1 (en) Network device management command scheduling
JP2010517175A (en) System management policy certification, distribution, and formulation
CN1901517A (en) Information exchange system and management server, terminal device and method for reducing network load
CN1716251A (en) Method and apparatus for accessing web services
CN1968283A (en) Network management system and method
US8490100B2 (en) Terminal and method for performing device management scheduled based on threshold
CN1852175A (en) Data-logging method and system therefor
US9053444B2 (en) Deploying applications in a smart thin client server
CN1969504A (en) Device management system and device management command scheduling method thereof
EP1977324B1 (en) Terminal and method for performing device management scheduled based on threshold
CN101047726A (en) Terminal failure diagnosis system and method
CN103297275A (en) Dynamic discovery and loading system and method for Web network management client module
CN101056220A (en) Central monitoring method of the data service system without network management interface
CN1750486A (en) Network measuring system structure and its realizing method
CN101075990A (en) Method for issuing instant telecommunication software and instant telecommunication server
CN101047896A (en) Value-added service allocation method and value-added service system based on package
CN1859197A (en) Method for determining QoS strategy

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 1106357

Country of ref document: HK

C14 Grant of patent or utility model
GR01 Patent grant
REG Reference to a national code

Ref country code: HK

Ref legal event code: GR

Ref document number: 1106357

Country of ref document: HK

CF01 Termination of patent right due to non-payment of annual fee
CF01 Termination of patent right due to non-payment of annual fee

Granted publication date: 20090715

Termination date: 20190708