CN101371498B - Method for scheduling the device management and terminal thereof - Google Patents
Method for scheduling the device management and terminal thereof Download PDFInfo
- Publication number
- CN101371498B CN101371498B CN2007800028325A CN200780002832A CN101371498B CN 101371498 B CN101371498 B CN 101371498B CN 2007800028325 A CN2007800028325 A CN 2007800028325A CN 200780002832 A CN200780002832 A CN 200780002832A CN 101371498 B CN101371498 B CN 101371498B
- Authority
- CN
- China
- Prior art keywords
- dispatch environment
- terminal
- server
- environment
- condition
- 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 terminal comprises a first entity adapted to receive a scheduling context from a server, to selectively verify the received scheduling context, and to install the received scheduling context; and a second entity adapted to perform a scheduled device management based on the scheduling context installed by the first element, wherein the scheduling context includes at least one of: a first elementto specify a command for a device management; a second element to specify a condition to execute the command; a third element to specify an interaction with a user; a fourth element to specify whether or not a result from executing the command should be reported to the server; and a fifth element to specify whether or not a state of the scheduling context should be reported to the server.
Description
Technical field
The present invention relates to method and terminal thereof that equipment control (DM:Device Management) is dispatched.
Background technology
In general, equipment control (DM) technology is used for the management of DM server to terminal.The DM server is managed this client thus easily by visiting terminal (client) with reference to the resource that is positioned at the DM object form on the DM tree.
According to the DM technology, the DM server can the requesting client treatment facility order of management.Then, this client can be carried out corresponding order immediately, and follows the result of report executing.The DM server can be to the change/renewal/deletion of DM object client request to specific function.
Yet in existing DM technology, only this terminal just asks the DM server to carry out administration order when mistake or abnormal operation appear in terminal.Therefore, the diagnostic procedure of terminal needs high expense, and can't carry out proper step before problem takes place.
Summary of the invention
Therefore, the purpose of this invention is to provide a kind of can be by equipment control (DM) system of server management of terminal, and the method for scheduling DM.
In order to realize these and other advantages, and according to purpose of the present invention, as concrete enforcement and broadly described here, a kind of terminal is provided, this terminal comprises: first entity, it is suitable for from server receiving scheduling environment (scheduling context), optionally verifying received dispatch environment, and the dispatch environment that this receives is installed; And second entity, it is suitable for carrying out scheduling device management based on the described dispatch environment of being installed by described first entity, wherein said dispatch environment comprise following one of them: first element, it has stipulated the order of equipment control; Second element, it has stipulated to carry out the condition of described order; Element, it has stipulated mutual with the user; The quaternary element, it has stipulated whether should report to described server the execution result of described order; And The Fifth Element, it has stipulated whether should report to described server the state of described dispatch environment.
In order to realize these and other advantages, and according to purpose of the present invention, as concrete enforcement and broadly described here, a kind of server also is provided, this server comprises: the device management scheduling enabler, it is suitable for creating dispatch environment, request is installed the dispatch environment of being created to terminal and also received the response of described dispatch environment is installed, and described dispatch environment comprises first element of specified devices administration order and second element of the condition that regulation is carried out described order.
In order to realize these and other advantages, and according to purpose of the present invention, as concrete enforcement and broadly described here, a kind of method of carrying out scheduling device management (scheduleddevice management) in terminal also is provided, described method comprises: the installation request of receiving scheduling environment, this dispatch environment comprise first element of specified devices administration order and second element of the condition that regulation is carried out described order; Authenticate or verify described dispatch environment; Described dispatch environment is installed; And carry out scheduling device management according to the dispatch environment of installing.
In order to realize these and other advantages, and according to purpose of the present invention, as concrete enforcement and broadly described here, a kind of method of carrying out scheduling device management in terminal also is provided, described method comprises: the installation request of receiving scheduling environment, this dispatch environment comprise first element of specified devices administration order and second element of the condition that regulation is carried out described order; Authenticate or verify described dispatch environment; Described dispatch environment is installed; And monitor condition in the described dispatch environment; As the result of described monitoring, when detecting the condition coupling, at the execution and the user interactions of described order; Carry out described order; The gating execution result; And the execution result that is not trapped to the report of described server.
In conjunction with the accompanying drawings, by the following detailed description of the present invention, aforementioned and other purposes of the present invention, feature, aspect and advantage will become more obvious.
Description of drawings
Accompanying drawing is included further understanding of the invention to be provided and to be merged in a part that constitutes the application, and accompanying drawing shows embodiments of the present invention, and is used from explanation principle of the present invention with specification one.In the accompanying drawings:
Fig. 1 shows the allocation plan according to terminal of the present invention and equipment control (DM) server;
Fig. 2 shows the exemplary view of dispatch environment;
Fig. 3 shows the exemplary view of DM tree;
Fig. 4 shows first embodiment of the invention is installed the processing of dispatch environment by the DM server of Fig. 1 flow chart;
Fig. 5 shows the flow chart that the processing of dispatch environment is installed by the DM server of Fig. 1 second embodiment of the invention;
Fig. 6 shows the flow chart according to DM dispatching method of the present invention.
Embodiment
The various details preferred implementation has illustrated its example in the accompanying drawing.
Fig. 1 shows the allocation plan according to terminal of the present invention and equipment control (DM) server, and Fig. 2 shows the exemplary view of dispatch environment, and Fig. 3 shows the exemplary view of DM tree.
As shown in Figure 1, comprise DM server 100 and terminal 200 according to DM of the present invention system.
DM server 100
DM scheduling enabler server 110 comprises dispatch environment administration module 111 and status report processing module 112.
Dispatch environment administration module 111 is the unit that are used for creating dispatch environment and are used for installing in terminal 200 dispatch environment of being created.As shown in Figure 2, this dispatch environment can comprise scheduling device management.
Below with reference to Fig. 2 dispatch environment is described.Dispatch environment comprises overall information, and at least one scheduling ingredient.This overall information can comprise at least one in following: the identifier of dispatch environment, the title of dispatch environment and the information relevant with server.This scheduling ingredient can comprise scheduling device management.More particularly, scheduling ingredient can comprise in following at least one: whether whether condition element (or second element), regulation and the user's of the command element (or task element or first element) of the order of specified devices management, the exectorial condition of regulation mutual user interactions (UI) element (or element), regulation should be reported gating (gating) element (quaternary element) of command execution results and stipulate to server should be to the incident element (The Fifth Element) of the state of server reporting terminal or incident.
At this, one or more device management command can be packaged in a piece of news.Therefore, command element has stipulated to comprise the message of one or more order, but not each order of separate provision.And this scheduling ingredient comprises also whether regulation should write down the record element (or hexa-atomic element) of the history relevant with equipment control in terminal.Should be mentioned that dispatch environment is not limited to above-mentioned configuration.
Scheduling ingredient described above comprise in command element, condition element, user interaction elements, gating element and the incident element at least one or more a plurality of.But should be mentioned that these elements can directly be contained in the dispatch environment.
Dispatch environment administration module 111 can be set up the DM session based on OMA-DM standard and terminal 200, and then via the DM conversation request of setting up the dispatch environment of being created is installed in terminal 200.
Dispatch environment administration module 111 can ask to revise the dispatch environment in the terminal 200.And dispatch environment administration module 111 can ask to delete the dispatch environment in the terminal 200.
When installing or amended dispatch environment when changing in terminal 200, or when making a mistake in the terminal 200, dispatch environment administration module 111 receives message from terminal 200, handles thus.
Status report processing module 112 is to be used for the unit that receives execution results or status report and received content is resolved from terminal 200.More particularly, status report processing module 112 receives the execution result or the status report of order from terminal 200, thereby resolves, and checks which dispatch environment this result or status report belong to.Then, status report processing module 112 guides to dispatch environment administration module 111 with execution result or status report.Yet when the result who receives from terminal 200 or status report can not directly be handled, status report processing module 112 can guide to it another server.
DM scheduling enabler client 210 comprises the first entity 210a and the second entity 210b.The first entity 210a comprises dispatch environment installed module 211.And the second entity 210b comprises condition matching module 212, user interactive module 213, command execution module 214, gating module 215, reporting modules 216 and logging modle 217.
Dispatch environment installed module 211 is to be used for from the installation request of DM scheduling enabler server 110 receiving scheduling environment and the unit of execution installation.That is, dispatch environment installed module 211 utilizes dispatch environment in the DM of terminal 200 tree at least one node to be installed.The DM tree can comprise total body portion, and at least one scheduling ingredient.
Below with reference to Fig. 3 the DM tree is described.Total body portion can comprise the ID node of expression dispatch environment identifier, Name (title) node of expression dispatch environment title and Server (server) node of representing the owner of dispatch environment.
Scheduling ingredient can comprise task (task) node (or first node) of the order of specified devices management, stipulate Cond (condition) node (or Section Point) of exectorial condition, UI (user interactions) node (or the 3rd node) of regulation user interactions, whether regulation should be to server report executing result's Gating (gating) node (the 4th node), and whether regulation should be to the state of server reporting terminal or the Events of incident (incident) node (or the 5th node).In addition, this scheduling ingredient also comprises and is used to control record controls (LogCtrl) node (or the 6th node) that the history relevant with equipment control is write down.At this, task node can stipulate to comprise the message of one or more order, rather than each order of separate provision.And, this condition node comprises with the next item down or more multinomial: regulation based on Timer (timer) node of timer condition, regulation based on Trap (trap) node of the condition of trap and regulation Th (threshold value) node (that is, whether the value of the specific management object in the terminal reaches threshold value) based on the condition of threshold value.The timer node can the stipulated time, duration, cycle, a set point at interval.This timer node comprise regulation with Base (basis) node of the time point of expressed intact formal representation, stipulate cycline rule (RRule) node whether this condition circulates.Therefore, if not regulation circulation in cycline rule (RRule) node then can be forbidden this condition based on timer after in a single day order is carried out.
More than described scheduling ingredient and comprised in following at least one or multinomial: task node, condition node, user interactions node, gating node and event node.Yet, it should be noted that these nodes can directly be included in the dispatch environment, rather than are included in the scheduling ingredient.
Before by DM server 100 dispatch environment being installed, dispatch environment installed module 21 can carry out user interactions, maybe can check the authority that whether DM server 100 has needs.Dispatch environment installed module 211 can verify whether the dispatch environment that will install is effective.At this, can whether have any error configurations by checking, whether exist between the composition wrong, whether can carry out to wait and carry out this checking.
When guard condition, condition matching module 212 can require addition item.That is the project that, in dispatch environment, can comprise the mode that is used for rated condition matching module 212 guard conditions.For example, in dispatch environment, can comprise request condition matching module 212 at the fixed time at interval in or institute if having time in the request items of control survey value or variable.
User interactive module 213 is the unit that are used for carrying out according to ' UI ' node of DM tree user interactions when condition matching module 212 affirmation conditions are coupling.
Logging modle 217 is to be used for unit that the history relevant with the DM scheduling operation is write down.As previously mentioned, logging modle 217 can be come log history according to ' LogCtrl ' node in the DM tree.For example, logging modle 217 can write down and the relevant information of various situations (that is, when the situation of determining the condition coupling, when exectorial situation or when the situation to DM server 100 report executing results).When needed, can be by DM server 100 Visitor Logs modules 217 stored log.Reason is for when because unexpected mistake causes status report processing module 216 prevent that DM server 100 from determining that mistakenly terminal 200 is in normal condition can not the executing state report time.
As previously mentioned, logging modle 217 can be by coming the storage device in the office terminal 200 with reference to ' LogCtrol ' node in the DM tree.For example, logging modle 217 can be adjusted at and be the size of log store assigned portions in the storage device, maybe can be chosen in the storage means (for example, circular buffering method, linear buffer method etc.) in this storage device.Logging modle 217 can be included in the DM scheduler 210, or can make up separately.
So far the DM server of having described 100 comprises DM scheduling enabler server 110 and DM enabler server 120, DM scheduling enabler server 110 comprises dispatch environment administration module 111 and status report processing module 112, and terminal 200 comprises DM scheduling enabler client 210 and DM enabler client 220, but can make up server 100 or terminal 200 by mutual combining processor (not shown), network interface (not shown) and storage device (not shown).
Below with reference to Fig. 4 to Fig. 6 operation according to DM of the present invention system is described.Details is not disclosed among Fig. 4 to Fig. 6 for simplicity.Yet, it should be understood that DM server 100 and terminal 200 realize by these details.
The installation of DM dispatch environment
Fig. 4 shows the flow chart that the processing of dispatch environment is installed by the DM server of first embodiment of the invention shown in Figure 1, and Fig. 5 shows the flow chart that the processing of dispatch environment is installed by DM server second embodiment of the invention shown in Figure 1.
With reference to figure 4, DM server 100 is set up the DM session with DM enabler client 220, and dispatch environment is installed thus.
Below, will the processing according to the installation dispatch environment of first embodiment of the invention be described.
1) DM server 100 (more particularly, the dispatch environment administration module 111) is created dispatch environment.
2) DM server 100 is set up the DM session with the DM enabler client 220 of terminal 200, and sends the installation request of the dispatch environment of being created to the DM of terminal 200 enabler client 220.
3) the DM enabler client 220 of terminal 200 is forwarded to DM scheduling enabler client 210 (more particularly, dispatch environment installed module 211) with request, and then dispatch environment installed module 211 checks whether this dispatch environment is effective.
4) when checking end, DM scheduling enabler client 210 (more particularly, the dispatch environment installed module 211) is carried out at the installation and the user of this dispatch environment alternately.
5) when user interactions finishes, the DM of terminal 200 scheduling enabler client 210 (more particularly, the dispatch environment installed module 211) is installed this dispatch environment in the DM of terminal 200 tree.
6) when end is installed, the DM of terminal 200 scheduling enabler client 210 is to the installation results of DM server 100 these dispatch environment of report.
Describe with reference to 5 pairs of processing of figure according to the installation dispatch environment of second embodiment of the invention.
As shown in Figure 5, according to second embodiment of the invention, DM server 100 is installed dispatch environment to DM scheduling enabler client 210 rather than 220 requests of DM enabler client.
1) DM server 100 (more particularly, the dispatch environment administration module 111) is created dispatch environment.
2) DM server 100 is set up the DM session with the DM scheduling enabler client 210 of terminal 200, and sends the installation request of the dispatch environment of being created to the DM of terminal 200 scheduling enabler client 210.
3) then, the dispatch environment installed module 211 of terminal 200 checks whether this dispatch environment is effective.
4) when having checked, DM scheduling enabler client 210 (more particularly, the dispatch environment installed module 211) is carried out at the installation and the user of this dispatch environment alternately.
5) when user interactions finishes, the DM of terminal 200 scheduling enabler client 210 (more particularly, the dispatch environment installed module 211) is installed this dispatch environment in the DM of terminal 200 tree.
6) when end is installed, the DM of terminal 200 scheduling enabler client 210 is to the installation results of DM server 100 these dispatch environment of report.
Fig. 6 shows the flow chart according to DM dispatching method of the present invention.
As shown in Figure 6, DM server 100 provides the device management command that will carry out and the condition of carrying out this order to terminal 200 in terminal 200.Then, if determine the condition coupling, terminal 200 is carried out this administration order.Therefore, terminal 200 recognizes that DM server 100 will provide this device management command immediately as long as terminal 200 needs this device management command.
Below with reference to Fig. 6 DM dispatching method according to the present invention is described.
1) DM scheduling enabler client 210 (more particularly, condition matching module 212) is come the inspection condition according to ' Cond ' node in the DM tree, and monitors whether detect the condition coupling.As previously mentioned, this condition can be based on the condition of ' timer ', based on the condition of ' trap ' and based on one in the condition of ' threshold value '.
2) when detecting the condition coupling, DM scheduling enabler client 210 (more particularly, user interactive module 213) is optionally carried out with the user alternately.As previously mentioned, can realize user interactions according to ' UI ' node that is included in the DM tree.
3) when successfully having carried out this user interactions, DM scheduling enabler client 210 (more particularly, command execution module 214) is by cooperating with fill order with DM enabler client 220.
4) when command execution finishes, DM scheduling enabler client 210 (more particularly, the gating module 215) gating execution result.As previously mentioned, can carry out gating (gating) according to ' Gating ' node in the DM tree.
5) DM scheduling enabler client 210 (more particularly, reporting modules 216) is not trapped the execution result of (gated-off) or the state of terminal 200 to 100 reports of DM server.That is, whether reporting modules 216 orders successful execution or the reason that makes a mistake to DM server 100 report.In order to report, reporting modules 216 utilizes execution result to create report message, and then this message is sent to DM server 100.
6) 100 pairs of these status reports of DM server that receive status report are resolved.
Although not shown among Fig. 6, the DM scheduling enabler client 210 (more particularly, logging modle 217) of terminal 200 can write down with each and handle relevant history.For example, when detecting condition when coupling, during maybe when carrying out user interactions or when fill order or when report, can in the storage device of terminal 200, storing corresponding daily record.
Can realize by software and hardware or the combination between the two according to DM dispatching method of the present invention.For example, this method can realize by the code or the order that can be stored in the software program in the storage device (for example, the internal storage of portable terminal, flash memory, hard disk etc.) or that can be carried out by processor (for example, the internal microprocessor of portable terminal).
In the present invention, the DM server provides the device management command that will carry out and the condition of carrying out this order to terminal in advance in terminal.Then, this terminal is carried out administration order based on this condition.Therefore, terminal 200 recognizes that DM server 100 will provide this device management command immediately as long as terminal 200 requires device management command.
Owing under the situation that does not break away from spirit of the present invention or substantive characteristics, can implement the present invention by various ways, what therefore will also be understood that is the details restriction that above-mentioned execution mode is not subjected to above-mentioned any description, unless specialize, and should in spirit and scope defined by the appended claims, carry out wide in range explanation, all modifications example and the modified example that therefore fall into claim scope or equivalency range are all contained by appended claim.
Claims (19)
1. terminal, this terminal comprises:
First entity, it is suitable for from server receiving scheduling environment, thereby optionally verifies received dispatch environment, and the dispatch environment that this receives is installed; And
Second entity, it is suitable for carrying out scheduling device management based on the described dispatch environment of being installed by described first entity,
Wherein said dispatch environment comprises overall information and scheduling ingredient,
Wherein said overall information comprises the title of the identifier of described dispatch environment, described dispatch environment and the information relevant with described server,
Wherein said scheduling ingredient comprises:
First element, it has stipulated the order of equipment control; And
Second element, it has stipulated to carry out the condition of the described order in described first element.
2. terminal according to claim 1, wherein said second entity comprises:
First module, it is suitable for monitoring that described condition in described second element is to carry out the described order in described first element; And
Three module, it is suitable for carrying out the described order in described first element.
3. terminal according to claim 1, wherein said dispatch environment also comprises:
Element, it has stipulated mutual with the user;
The quaternary element, it has stipulated whether should report to described server the execution result of described order;
The Fifth Element, it has stipulated whether should report to described server the state of described dispatch environment; And
Hexa-atomic element, this hexa-atomic element has stipulated whether should write down the history of the operation of carrying out according to described dispatch environment.
4. terminal according to claim 1, wherein said first entity is realized described installation by create each node corresponding with each element of described dispatch environment in device management tree.
5. terminal according to claim 1, the user of wherein said server or described terminal can make amendment or deletes described dispatch environment.
6. terminal according to claim 3, wherein said second entity also comprises:
Second module, it is suitable for when detecting described condition coupling execution and user interactions at described order;
Four module, it is suitable for the result of the described execution of gating;
The 5th module, it is suitable for the execution result that is not trapped to the report of described server, or reports the state of described terminal to described server; And
The 6th module, its be suitable for writing down with following at least one relevant information: whether detect the result that described condition is mated, whether carried out described user interactions, whether carried out described order and whether reported described execution.
7. terminal according to claim 1, wherein first entity is checked the authority of described server.
8. terminal according to claim 1, the wherein first entity inspection: whether the grammaticality of described dispatch environment or described dispatch environment exist any error configurations or can not carry out described dispatch environment.
9. terminal according to claim 1, wherein said condition be following at least one of them: based on the condition of timer, based on the condition of threshold value and based on the condition of trap.
10. terminal according to claim 1, wherein said condition is disabled according to this condition fill order the time.
11. terminal according to claim 2, wherein said three module by with described terminal in another module or entity cooperate and carry out described order.
12. a method of carrying out scheduling device management in terminal, this method comprises:
The installation request of receiving scheduling environment, this dispatch environment comprises overall information and scheduling ingredient,
Wherein said overall information comprises the title of the identifier of described dispatch environment, described dispatch environment and the information relevant with described server,
Wherein said dispatch environment comprises first element of the order of having stipulated equipment control and has stipulated to carry out second element of the condition of described order;
Authenticate or verify described dispatch environment;
Described dispatch environment is installed; And
Carry out scheduling device management according to the dispatch environment of installing.
13. method according to claim 12, wherein said dispatch environment also comprises:
Element, it has stipulated mutual with the user;
The quaternary element, it has stipulated whether should report to described server the execution result of described order; And
The Fifth Element, it has stipulated whether should report to described server the state of described terminal.
14. method according to claim 13, wherein said dispatch environment also comprises hexa-atomic element, and this hexa-atomic element has stipulated whether should write down the history relevant with described equipment control.
15. method according to claim 12 wherein when authenticating or verifying described dispatch environment, is checked the grammaticality of described dispatch environment or the authority of described server.
16. method according to claim 12 wherein when authenticating or verifying described dispatch environment, is checked whether described dispatch environment exists any error configurations, or can not carried out described dispatch environment.
17. also comprising, method according to claim 12, this method when the state variation of the dispatch environment of installing in the described terminal, send message.
18. a method of carrying out scheduling device management in terminal, this method comprises:
The installation request of receiving scheduling environment, this dispatch environment comprises overall information and scheduling ingredient,
Wherein said overall information comprises the title of the identifier of described dispatch environment, described dispatch environment and the information relevant with described server,
Wherein said scheduling ingredient comprises: stipulated the order of equipment control first element, stipulated to carry out the condition of described order second element, stipulated with user's mutual element, whether stipulated and should report the The Fifth Element that the quaternary of execution result of described order is plain and stipulated whether should report to described server the state of described terminal to described server;
Authenticate or verify described dispatch environment;
Described dispatch environment is installed;
Monitor the condition in the described dispatch environment;
As the result of described supervision, when detecting the condition coupling, at the execution and the user interactions of described order;
Carry out described order;
The gating execution result; And
The execution result that is not trapped to server report.
19. method according to claim 18, this method also comprises:
Record with following at least one relevant information: the condition that whether detects is mated, whether has been carried out user interactions, whether carried out described order and whether reported execution result.
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US76094306P | 2006-01-23 | 2006-01-23 | |
| US60/760,943 | 2006-01-23 | ||
| US76251706P | 2006-01-27 | 2006-01-27 | |
| US60/762,517 | 2006-01-27 | ||
| PCT/KR2007/000344 WO2007083954A1 (en) | 2006-01-23 | 2007-01-19 | Method for scheduling device management and terminal thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101371498A CN101371498A (en) | 2009-02-18 |
| CN101371498B true CN101371498B (en) | 2011-06-08 |
Family
ID=40414020
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007800028325A Expired - Fee Related CN101371498B (en) | 2006-01-23 | 2007-01-19 | Method for scheduling the device management and terminal thereof |
| CN2007800028522A Expired - Fee Related CN101371242B (en) | 2006-01-23 | 2007-01-22 | Method for interacting with user and terminal thereof |
Family Applications After (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007800028522A Expired - Fee Related CN101371242B (en) | 2006-01-23 | 2007-01-22 | Method for interacting with user and terminal thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN101371498B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1326189A2 (en) * | 2001-12-12 | 2003-07-09 | Microsoft Corporation | Controls and displays for acquiring preferences, inspecting behaviour, and guiding the learning and decision policies of an adaptive communications prioritization and routing systems |
-
2007
- 2007-01-19 CN CN2007800028325A patent/CN101371498B/en not_active Expired - Fee Related
- 2007-01-22 CN CN2007800028522A patent/CN101371242B/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1326189A2 (en) * | 2001-12-12 | 2003-07-09 | Microsoft Corporation | Controls and displays for acquiring preferences, inspecting behaviour, and guiding the learning and decision policies of an adaptive communications prioritization and routing systems |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101371242A (en) | 2009-02-18 |
| CN101371498A (en) | 2009-02-18 |
| CN101371242B (en) | 2013-12-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10158670B1 (en) | Automatic privilege determination | |
| US11196627B1 (en) | Managed remediation of non-compliant resources | |
| US11501000B2 (en) | Auto-injection of security protocols | |
| CN101778004B (en) | Terminal and method for performing device management scheduled based on threshold thereof | |
| CN104219080A (en) | Method for recording logs of error pages of websites | |
| US20030217155A1 (en) | Send of software tracer messages via IP from several sources to be stored by a remote server | |
| US8407329B2 (en) | Reporting information to a network | |
| CN111367693B (en) | Method, system, device and medium for scheduling plug-in tasks based on message queue | |
| WO2007083954A1 (en) | Method for scheduling device management and terminal thereof | |
| KR101443071B1 (en) | Error Check System of Webpage | |
| CN101375266A (en) | Device management scheduling based on trap mechanism | |
| EP3835978A1 (en) | Software license manager | |
| US20020188568A1 (en) | Systems and methods of containing and accessing generic policy | |
| CN111698126B (en) | Information monitoring method, system and computer readable storage medium | |
| Bouchenak et al. | From autonomic to self-self behaviors: The jade experience | |
| US11593463B2 (en) | Execution type software license management | |
| US7984335B2 (en) | Test amplification for datacenter applications via model checking | |
| Jammal et al. | A formal model for the availability analysis of cloud deployed multi-tiered applications | |
| KR100824298B1 (en) | Method for scheduling device management and terminal thereof | |
| CN101371498B (en) | Method for scheduling the device management and terminal thereof | |
| CN104702421B (en) | Configuration management system based on Web | |
| KR101392915B1 (en) | Device managemet using event | |
| CN115774581A (en) | Method and related apparatus for executing robot feet | |
| CN113220407B (en) | Fault exercise method and device | |
| CN113377616B (en) | Interface monitoring method, device and computer readable medium |
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: 20110608 Termination date: 20170119 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |