CN1852537A - Method and apparatus for processing fault task in apparatus management - Google Patents
Method and apparatus for processing fault task in apparatus management Download PDFInfo
- Publication number
- CN1852537A CN1852537A CNA2005101129241A CN200510112924A CN1852537A CN 1852537 A CN1852537 A CN 1852537A CN A2005101129241 A CNA2005101129241 A CN A2005101129241A CN 200510112924 A CN200510112924 A CN 200510112924A CN 1852537 A CN1852537 A CN 1852537A
- Authority
- CN
- China
- Prior art keywords
- task
- terminal equipment
- type
- management server
- device management
- 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
Links
Images
Landscapes
- Computer And Data Communications (AREA)
Abstract
In the method, when terminal device reports message that executed task is failure to device management server, the device management server determines type of failure based on error id in the message, and executes treatment strategy corresponding to the type of failure. The invention also discloses a device management server. The device management server includes communication module, judgment module, and executive module.
Description
Technical field
The present invention relates to the device management techniques of communication technical field, relate in particular to method and the device of in equipment control, handling failed tasks.
Background technology
Portable terminal is the important component part in the whole mobile operation service system.Increasingly sophisticated along with termination function, the possibility that terminal software goes wrong significantly increases.Competition between the following operator is growing more intense, and how effectively to guarantee user experience, improves user's loyalty, keeps efficiently service quality and low-cost device to safeguard a significant concern point that has become operator, manufacturer terminal.
OMA DM standard is a kind of management, diagnosis, safeguard the technology of mobile terminal device.It manages terminal equipment by OTA (Over The Air downloads in the air) mode, bookkeeping comprises the setting of terminal equipment parameter, firmware update, software installation and upgrade, use be provided with, functions such as the collection of the mistake of equipment and event information and processing.
Wireless network is an important applied field of equipment control (DM), but since wireless be a kind of insecure media, there is unreliability in the connection that is based upon on the wireless network, for example: signal exists that the instability of the power of blind area (as elevator), signal, signal are disturbed easily, the mobility of terminal equipment etc. all can cause connecting or the interruption of session, in addition, the self problem of personal communications terminal equipment also usually causes some problems, such as: crash, go offline, phenomenon such as shutdown automatically.As above problem all might cause the DM managing conversation to stop, and makes the management role of device management server fail.
In addition, having the processing action after a kind of failure at present, mainly is behind operation failure, available for the safety that keeps terminal equipment, can carry out rollback to certain operations, generally can do following processing:
If this operation of A is an atomic operation, when atomic operation also imperfect tense, the situation of operation failure has appearred, then the rollback that can operate;
If this operation of B is the some operations in the sequence of operation, when certain operation failure in this sequence of operation, can carry out rollback to this operation, rollback is not then carried out in the operation that has finished this operation front.
Though present technology can guarantee terminal and still can normally use behind operation failure, but this bookkeeping can not be finished the work for terminal equipment effective processing is provided, cause the operation cost of the processing pressure of DMS and network bigger, and the success rate of bookkeeping is lower.
Summary of the invention
The invention provides a kind of method of in equipment control, handling failed tasks, exist DMS processing pressure and network main operation cost bigger to solve prior art bookkeeping failed tasks, and the lower problem of success rate.
The invention provides following technical scheme:
A kind of method of handling failed tasks in equipment control comprises the steps:
The terminal equipment failure of executing the task is to the device management server reporting message;
Device management server is determined Fail Type according to the error identification in the described message, and the processing policy of carrying out this Fail Type correspondence is to manage the task of described execution failure.
Wherein:
Described Fail Type comprises: mutual overtime type, cancellation task type and execute exception type.
When device management server determined that Fail Type is mutual overtime type, described processing policy made terminal equipment can re-execute described task.
Described processing policy comprises the steps:
A1, device management server are judged the type of failed tasks, if common task then carries out steps A 2, if customized task then carries out steps A 3;
A2, will carry out the failure Task Switching be customized task and be handed down to terminal equipment;
A3, whether there is the task of described execution failure to terminal inquiry, if, the state of the task of then resetting and trigger condition; Otherwise device management server regenerates customized task and is handed down to terminal equipment.
When device management server determined that failure cause is the cancellation task, the processing policy of execution made terminal equipment no longer carry out described task.
When device management server determines that failure cause is execute exception, further determine to cause unusual action type; Described processing policy makes terminal equipment no longer carry out described task according to action type or makes terminal equipment can re-execute described task.
When device management server determined that described task causes the task execute exception for operating or need not action type, described processing policy made terminal equipment no longer carry out described task.
When but device management server was determined described task for action type, described processing policy issued or postpones the described task that issues again to terminal equipment, makes terminal equipment can re-execute this task.
Device management server takes a step forward in the task of issuing and judges the type of failed tasks, is that control terminal is deleted this task when having this task on customized task and the described terminal equipment in definite described failed tasks.
But device management server is determined described task for wouldn't action type the time, but described processing policy makes terminal equipment re-execute described task retardation time.
A kind of device management server comprises:
The communication module that is used to receive reporting message and issues task;
Be used for judging the judge module of Fail Type according to the failure of executing the task that described communication module receives;
The Fail Type that is used for determining according to judge module is carried out corresponding processing policy, to manage the Executive Module of described failed tasks.
Wherein, if when described judge module determines that Fail Type is mutual overtime type, the processing policy that described Executive Module is carried out makes terminal equipment can re-execute described task; If when described judge module determined that Fail Type is the cancellation task type, the processing policy that described Executive Module is carried out made terminal equipment no longer carry out described task; When if described judge module determines that Fail Type is the execute exception type, the processing policy that described Executive Module is carried out makes terminal equipment no longer carry out described task or makes terminal equipment can re-execute described task.
The present invention adopts corresponding handling process to manage according to the different reasons of the failure of executing the task, make terminal equipment can re-execute this task, thereby can improve the success rate of bookkeeping, also can alleviate the operating pressure of DMS simultaneously and reduce the network operation cost, and strengthen user experience.
Description of drawings
Fig. 1 issues the interaction flow of bookkeeping to terminal equipment for DMS in the prior art;
Fig. 2 determines the flow chart of failure cause according to the error identification in the terminal equipment reporting message for DMS among the present invention;
The process chart of DMS when Fig. 3 does not have respond style for failure cause among the present invention for the user;
The processing flow graph of DMS when Fig. 4 cancels task type for failure cause among the present invention for the user;
But the process chart of Fig. 5 DMS during for the action type in the execute exception among the present invention;
But Fig. 6 in the execute exception among the present invention wouldn't action type the time DMS process chart;
Fig. 7 is the structured flowchart of device management server among the present invention.
Embodiment
Can carry out follow-up management to failed tasks when failing in order to execute the task at terminal equipment, report when failure of executing the task at terminal equipment to device management server, device management server is carried out corresponding processing policy so that failed tasks is carried out follow-up management according to Fail Type.Be that the present invention is described in detail for example mainly below to carry out equipment control by OMA DM agreement.
Based on existing OMA DM agreement,, cause equipment control (DM) to carry out failure cause and can be divided into three kinds from user's angle:
(1) user does not have response, to such an extent as to overtime alternately, finally cause mission failure;
(2) user is reluctant to carry out, and has selected refusal or cancellation, causes issuing the task executions failure;
(3) user accepts the task of issuing, but occurs unusual final leading to the failure in the task implementation.
The user does not have and responds normally that the user (converses such as the user for some reason; perhaps mobile phone does not wait at one's side) and device management server (DMS) not being issued for a long time of task responds; session can not keep always in this case; usually can return a mutual timeout mode information, for example:
<Status>
<MsgRef>1</MsgRef>
<CmdRef>2</CmdRef>
<CmdID>3</CmdID>
<Cmd>Alert</Cmd>
＜Data〉408＜/Data〉＜!--overtime--〉
</Status>
The user cancel task normally in reciprocal process user refusal carry out this task in terminal, perhaps, originally the user agrees, but in the implementation of task, the user has changed idea and ended task executions.In this case, terminal can be returned a cancellation or unenforced state information, for example:
<Status>
<MsgRef>1</MsgRef>
<CmdRef>2</CmdRef>
<CmdID>3</CmdID>
<Cmd>Alert</Cmd>
＜Data〉214/215＜/Data〉＜!--operation cancel/is not carried out--〉
</Status>
In the implementation of task, various the proving an abortion of task execution that cause unusually can appear, and these unusually roughly can be divided three classes.
A, can not operate and need not the operation
It is unusual class of operation to include but not limited to that unauthorized, terminal do not support that task type, authentification failure, order do not allow etc.This class is unusual normally because DMS or terminal lack of competence or task of not having the ability execution to issue produce at all, but does not get rid of other possibility.
Need not class of operation and mainly be state owing to current device does not need to carry out issuing of task again and produces.It is unusual that it includes but not limited to that task existence or executed, target do not exist etc.
B, can operate
Such unusual main issuing of task occurs mistake in the process of implementation and produces, and the data item of include but not limited to that order is imperfect, URI is oversize, asking is excessive etc.
C, wouldn't operate
The unusual generation of this class is normally because the task that the equipment state of current terminal is not suitable for or can not issues.It includes but not limited to that low memory, memory space are full etc.
Existing OMA DM agreement all has the conditional code of expression corresponding error reason to the reason of various mission failures, such as overtimely be 408 alternately, the operation cancellation is 214, unsupported type and form are 415 etc., the part error code is as shown in the table:
| Conditional code | Meaning |
| 214 | The operation cancellation |
| 215 | Operation is not carried out |
| 304 | User's refusal |
| 401 | Unauthorized |
| 405 | Order does not allow |
| 406 | Unsupported optional feature |
| 407 | No authentication information |
| 408 | Overtime alternately |
| 412 | Incomplete order |
| 415 | Unsupported medium type or form |
| 416 | Terminal is unsupported mutual |
| 500 | The order failure |
| 516 | Atomic operation rollback failure |
In existing OMA DM agreement, the interaction flow that DMS issues bookkeeping to terminal equipment as shown in Figure 1:
Step 1: server is initiated operational notification to terminal equipment.
Step 2: terminal is set up session connection (validation-cross partly omits).
Step 3: server issues the bookkeeping task.
Step 4: terminal equipment prompting user issues the bookkeeping mission bit stream.
Three square frames 1,2,3 among Fig. 1, task is carried out the interaction flow of failure under three kinds of situations after having represented respectively.As can be seen from Figure 1, terminal equipment can return the conditional code that task is carried out failure to DMS.
Therefore, in the present invention, DMS can be according to these conditional codes of returning type of failure cause that sets the tasks, thereby carries out corresponding handling process, main processing procedure as shown in Figure 2:
The type of step 210, judgement failure cause; If the user does not have respond style, promptly overtime alternately, then carry out step 230, if the user cancels type, then carry out step 260, if execute exception then carry out step 220.
But step 220, DMS further judge the operational readiness of execute exception; If for can not/need not action type, then carry out step 260, if but be action type, then carry out step 240, if but be wouldn't action type, then carry out step 250.
The user does not have that to respond normally the user inconvenient and cause the mutual overtime mission failure that causes, and therefore, DMS can transform into task a customized task, is handed down to terminal equipment again.At this moment, on the display screen of terminal equipment, have a display element that is similar to active icon and be used to remind the user, so that the user at the convenient time carries out task executions.Consult shown in Figure 3ly, do not have respond style for failure cause for the user, the key step of handling process 1 is as follows:
Step 300, DMS judge the type of failed tasks, if be common task, then carry out steps 310, if be customized task, then carry out steps 320.
Step 310, common task is transformed into a customized task, be handed down to terminal equipment.
The customized task that step 320, DMS fail to terminal inquiry.
Step 330, judge whether there is customized task on the terminal equipment,, then carry out step 340, otherwise carry out step 350 if exist.
The state and the trigger condition of step 340, notice terminal equipment replacement customized task.
Step 350, regenerate a customized task, init state and trigger condition are handed down to terminal equipment.
User's cancellation task produces owing to user itself is unwilling to carry out this task, consults shown in Figure 4ly, cancels task type for failure cause for the user, and the key step of handling process 2 is as follows:
Step 400, DMS judge the type of failed tasks, if be common task, then carry out steps 410, if be customized task, then carry out steps 420.
The customized task that step 410, DMS fail to terminal inquiry.
Step 420, judge whether there is customized task on the terminal equipment,, then carry out step 430, otherwise carry out step 440 if exist.
Step 430, control terminal are deleted this task.
Step 440, DMS no longer issue this task to terminal equipment.
For operating and need not action type in the execute exception, show DMS or terminal lack of competence usually or do not have ability to carry out issuing of task at all, and the implication that need not action type has more shown the unnecessary property of the task that issues.Therefore, when receiving this two class when unusual, DMS does not need again terminal to be issued this task, can adopt the mode identical with handling process 2 to handle and get final product, and promptly DMS carries out handling process 2.
But for the action type in the execute exception, the state that shows terminal equipment usually is normal, and mistake occurred in the process of executing the task.This situation needs DMS that issuing of task is adjusted, and according to the state of current terminal equipment task is issued or postpones issuing then again.Consult shown in Figure 5, but for the action type in the execute exception, the key step of handling process 3 is as follows:
The customized task that step 510, DMS fail to terminal inquiry.
The customized task of step 530, DMS notice terminal equipment deletion failure.
Type for failed tasks is the situation of common task, and adjusted task type can be a common task, also can be the customized task after transforming.
But in the execute exception wouldn't action type, mean that usually the state of current terminal equipment is not suitable for carrying out issuing of task, therefore, best choice is postponed task executions exactly.Consult shown in Figure 6, but in the execute exception wouldn't action type, the key step of handling process 4 is as follows:
The customized task that step 610, DMS fail to terminal inquiry.
The state and the trigger condition of step 630, notice terminal equipment replacement customized task are carried out this customized task to postpone.
If the type of failed tasks is a common task, the task type of Chuan Jianing can be a common task again, also can be the customized task after transforming.
Accordingly, the device management server structure that realizes said method as shown in Figure 7, this device management server comprises communication module, judge module and Executive Module (some basic function module of finishing existing capability are not shown in the drawings).Wherein:
Communication module is used for communicating by letter with terminal equipment, the reporting message of receiving terminal apparatus and issue task to terminal equipment.
Judge module has in logic annexation with communication module, is used for judging Fail Type according to the failure of executing the task that described communication module receives.
Executive Module has in logic annexation with judge module, and the Fail Type that is used for determining according to judge module is carried out corresponding processing policy, to manage the Executive Module of described failed tasks.
If when described judge module determined that Fail Type is mutual overtime type, the processing policy that described Executive Module is carried out made terminal equipment can re-execute described task;
If when described judge module determined that Fail Type is the cancellation task type, the processing policy that described Executive Module is carried out made terminal equipment no longer carry out described task;
When if described judge module determines that Fail Type is the execute exception type, the processing policy that described Executive Module is carried out makes terminal equipment no longer carry out described task or makes terminal equipment can re-execute described task.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (15)
1, a kind of method of handling failed tasks in equipment control is characterized in that, comprises the steps:
The terminal equipment failure of executing the task is to the device management server reporting message;
Device management server is determined Fail Type according to the error identification in the described message, and the processing policy of carrying out this Fail Type correspondence is to manage the task of described execution failure.
2, processing method as claimed in claim 1 is characterized in that, described Fail Type comprises: mutual overtime type, cancellation task type and execute exception type.
3, processing method as claimed in claim 2 is characterized in that, when device management server determined that Fail Type is mutual overtime type, described processing policy made terminal equipment can re-execute described task.
4, processing method as claimed in claim 3 is characterized in that, described processing policy comprises the steps:
A1, device management server are judged the type of failed tasks, if common task then carries out steps A 2, if customized task then carries out steps A 3;
A2, will carry out the failure Task Switching be customized task and be handed down to terminal equipment;
A3, whether there is the task of described execution failure to terminal inquiry, if, the state of the task of then resetting and trigger condition; Otherwise device management server regenerates customized task and is handed down to terminal equipment.
5, processing method as claimed in claim 2 is characterized in that, when device management server determined that failure cause is the cancellation task, the processing policy of execution made terminal equipment no longer carry out described task.
6, processing method as claimed in claim 2 is characterized in that, when device management server determines that failure cause is execute exception, further determines to cause unusual action type; Described processing policy makes terminal equipment no longer carry out described task according to action type or makes terminal equipment can re-execute described task.
7, processing method as claimed in claim 6 is characterized in that, when device management server determined that described task causes the task execute exception for operating or need not action type, described processing policy made terminal equipment no longer carry out described task.
8, as claim 5 or 7 described processing methods, it is characterized in that described processing policy comprises the steps:
B1, device management server are judged the type of failed tasks, if common task then no longer issues described task to described terminal equipment, if customized task then carries out step B2;
B2, whether there is the task of described execution failure, and knowing that the notice terminal equipment is deleted this task when having this task to terminal equipment inquiry.
9, processing method as claimed in claim 6 is characterized in that, but device management server is determined described task when the action type, and described processing policy issues or postpone the described task that issues again to terminal equipment, makes terminal equipment can re-execute this task.
10, processing method as claimed in claim 9, it is characterized in that, device management server takes a step forward in the task of issuing and judges the type of failed tasks, is that control terminal is deleted this task when having this task on customized task and the described terminal equipment in definite described failed tasks.
11, processing method as claimed in claim 6 is characterized in that, but device management server is determined described task for wouldn't action type the time, but described processing policy makes terminal equipment re-execute described task retardation time.
12, processing method as claimed in claim 11 is characterized in that, described processing policy comprises step:
C1, device management server are judged the type of failed tasks, if common task then carries out step C3, if customized task then carries out step C2;
C2, whether there is the task of described execution failure to terminal equipment inquiry, if, the state of replacement task and trigger condition; Otherwise carry out step C3;
C3, creation task and postpone and to be handed down to terminal equipment again.
13, as claim 9 or 12 described processing methods, it is characterized in that when described failed tasks was common task, device management server still issued common task to terminal, perhaps common task is converted to customized task and is issued to terminal equipment.
14, a kind of device management server is characterized in that, comprising:
The communication module that is used to receive reporting message and issues task;
Be used for judging the judge module of Fail Type according to the failure of executing the task that described communication module receives;
The Fail Type that is used for determining according to judge module is carried out corresponding processing policy, to manage the Executive Module of described failed tasks.
15, device management server as claimed in claim 14 is characterized in that, if when described judge module determines that Fail Type is mutual overtime type, the processing policy that described Executive Module is carried out makes terminal equipment can re-execute described task; If when described judge module determined that Fail Type is the cancellation task type, the processing policy that described Executive Module is carried out made terminal equipment no longer carry out described task; When if described judge module determines that Fail Type is the execute exception type, the processing policy that described Executive Module is carried out makes terminal equipment no longer carry out described task or makes terminal equipment can re-execute described task.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005101129241A CN100373976C (en) | 2005-10-14 | 2005-10-14 | Method and apparatus for processing fault task in apparatus management |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005101129241A CN100373976C (en) | 2005-10-14 | 2005-10-14 | Method and apparatus for processing fault task in apparatus management |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1852537A true CN1852537A (en) | 2006-10-25 |
| CN100373976C CN100373976C (en) | 2008-03-05 |
Family
ID=37134000
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005101129241A Expired - Fee Related CN100373976C (en) | 2005-10-14 | 2005-10-14 | Method and apparatus for processing fault task in apparatus management |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100373976C (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009021460A1 (en) * | 2007-08-15 | 2009-02-19 | Huawei Technologies Co., Ltd. | Method for reporting implement result of policy, network communication system and equipment |
| WO2010020083A1 (en) * | 2008-08-20 | 2010-02-25 | 中兴通讯股份有限公司 | Method and system for reporting the policy installation failure |
| WO2011110014A1 (en) * | 2010-09-08 | 2011-09-15 | 华为技术有限公司 | Paging processing method, system and serving gateway |
| CN102811448A (en) * | 2012-07-31 | 2012-12-05 | 中兴通讯股份有限公司 | Error code recognition method and mobile terminal |
| WO2013082808A1 (en) * | 2011-12-09 | 2013-06-13 | Motorola Mobility, Inc. | Methods and apparatus to trigger firmware update request in response to a failure event |
| CN103618786A (en) * | 2013-11-27 | 2014-03-05 | 乐视网信息技术（北京）股份有限公司 | Playing error processing method and server |
| US8713164B2 (en) | 2008-08-20 | 2014-04-29 | Zte Corporation | Feedback method and processing system for policy installation failures |
| CN104144076A (en) * | 2014-05-28 | 2014-11-12 | 腾讯科技（深圳）有限公司 | Method, device and system for flow error control |
| CN107547238A (en) * | 2016-06-29 | 2018-01-05 | 阿里巴巴集团控股有限公司 | Event monitoring system, method and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FR2811191B1 (en) * | 2000-06-30 | 2003-01-10 | Nortel Matra Cellular | CELLULAR RADIO COMMUNICATION SYSTEM WITH LOCATION OF FAULTY TERMINALS |
| EP1237084A1 (en) * | 2001-01-23 | 2002-09-04 | Koninklijke Philips Electronics N.V. | Method for reporting errors during program execution in an electronic terminal |
| US6999755B2 (en) * | 2002-03-12 | 2006-02-14 | Welgate Corp. | Method and device for providing information of unfinished call |
| EP1868382A3 (en) * | 2002-09-13 | 2008-02-27 | Sharp Kabushiki Kaisha | Broadcast program recording method, communication control device, and mobile communication device |
-
2005
- 2005-10-14 CN CNB2005101129241A patent/CN100373976C/en not_active Expired - Fee Related
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2009021460A1 (en) * | 2007-08-15 | 2009-02-19 | Huawei Technologies Co., Ltd. | Method for reporting implement result of policy, network communication system and equipment |
| US8725867B2 (en) | 2008-08-20 | 2014-05-13 | Zte Corporation | Method and system for reporting the policy installation failure |
| CN101355808B (en) * | 2008-08-20 | 2013-01-16 | 中兴通讯股份有限公司 | Method for reporting failure of policy installation |
| US8713164B2 (en) | 2008-08-20 | 2014-04-29 | Zte Corporation | Feedback method and processing system for policy installation failures |
| WO2010020083A1 (en) * | 2008-08-20 | 2010-02-25 | 中兴通讯股份有限公司 | Method and system for reporting the policy installation failure |
| US8995250B2 (en) | 2010-09-08 | 2015-03-31 | Huawei Technologies Co., Ltd. | Paging processing method and system, serving gateway |
| WO2011110014A1 (en) * | 2010-09-08 | 2011-09-15 | 华为技术有限公司 | Paging processing method, system and serving gateway |
| CN103988538A (en) * | 2011-12-09 | 2014-08-13 | 摩托罗拉移动有限责任公司 | Methods and apparatus to trigger firmware update request in response to a failure event |
| WO2013082808A1 (en) * | 2011-12-09 | 2013-06-13 | Motorola Mobility, Inc. | Methods and apparatus to trigger firmware update request in response to a failure event |
| CN103988538B (en) * | 2011-12-09 | 2018-02-16 | 谷歌技术控股有限责任公司 | In response to the method and apparatus of event of failure triggering firmware renewal request |
| US9715379B2 (en) | 2011-12-09 | 2017-07-25 | Google Technology Holdings LLC | Methods and apparatus to trigger firmware update request in response to a failure event |
| CN102811448A (en) * | 2012-07-31 | 2012-12-05 | 中兴通讯股份有限公司 | Error code recognition method and mobile terminal |
| CN102811448B (en) * | 2012-07-31 | 2017-12-15 | 中兴通讯股份有限公司 | A kind of error code recognition method and mobile terminal |
| CN103618786A (en) * | 2013-11-27 | 2014-03-05 | 乐视网信息技术（北京）股份有限公司 | Playing error processing method and server |
| WO2015180504A1 (en) * | 2014-05-28 | 2015-12-03 | Tencent Technology (Shenzhen) Company Limited | A method, device, and system for flow process error control |
| CN104144076B (en) * | 2014-05-28 | 2016-03-30 | 腾讯科技（深圳）有限公司 | A kind of flow process error control method, device and system |
| CN104144076A (en) * | 2014-05-28 | 2014-11-12 | 腾讯科技（深圳）有限公司 | Method, device and system for flow error control |
| CN107547238B (en) * | 2016-06-29 | 2020-11-24 | 阿里巴巴集团控股有限公司 | Event monitoring system, method and device |
| CN107547238A (en) * | 2016-06-29 | 2018-01-05 | 阿里巴巴集团控股有限公司 | Event monitoring system, method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100373976C (en) | 2008-03-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1852537A (en) | Method and apparatus for processing fault task in apparatus management | |
| CN1852538A (en) | Method and apparatus for monitoring and updating software in apparatus management | |
| CN1852534A (en) | Data backing-up and recovering method and system | |
| CN1866854A (en) | Method for updating and recovering terminal device data in device management | |
| CN1794646A (en) | Method for obtaining of daily information from network element equipment by network management server | |
| CN1248453C (en) | Method for realtime synchronisation of net element and telecommunication system | |
| CN1889047A (en) | System and method for realizing program resource sharing | |
| CN1946230A (en) | Anti-theft method for cell phone | |
| CN1859177A (en) | Method for processing customized task in equipment management | |
| CN1946226A (en) | Method, device for upgrading telecommunication equipment and upgrading engine unit | |
| CN1402580A (en) | Data recording system and method | |
| CN101039312A (en) | Method and apparatus for preventing service function entity of general authentication framework from attack | |
| CN1848761A (en) | Software assembly parameter configuration method and system and terminal equipment thereof | |
| CN1867004A (en) | Realization method for indicating user terminal state | |
| CN101039263A (en) | Method for processing node overload of core network and mobile switch equipment and communication system | |
| CN1859140A (en) | Method for realizing enabled positioning and positioning platform system | |
| CN101047880A (en) | Message transmission method and system | |
| US20140378116A1 (en) | Method And System For Sending Notification Message, Management Control Apparatus, And Terminal Device | |
| CN1882178A (en) | Method for solving calling/called impact in wireless network | |
| CN1882152A (en) | Data configuration method for access network device | |
| CN1863085A (en) | Method and system for ensuring network managment and element configuration data consistency | |
| EP2282603B1 (en) | Method for erasing data of terminal and terminal device | |
| KR20060114661A (en) | System and method for interacting with user in managing device | |
| CN1858709A (en) | Method and device for co-ordinating executing sequence facing user function | |
| CN1889718A (en) | Control system and control method for short message value-added service |
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: 20080305 Termination date: 20161014 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |