CN103428333A - Mobile terminal, server and error restoration method - Google Patents
Mobile terminal, server and error restoration method Download PDFInfo
- Publication number
- CN103428333A CN103428333A CN2012101492201A CN201210149220A CN103428333A CN 103428333 A CN103428333 A CN 103428333A CN 2012101492201 A CN2012101492201 A CN 2012101492201A CN 201210149220 A CN201210149220 A CN 201210149220A CN 103428333 A CN103428333 A CN 103428333A
- Authority
- CN
- China
- Prior art keywords
- mistake
- server
- communication unit
- mobile terminal
- sent
- 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
- Telephone Function (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a mobile terminal. The mobile terminal comprises a detecting unit, a communication unit and a restoration unit, wherein the detecting unit detects running conditions of the mobile terminal and records errors when the errors occur in the mobile terminal; the communication unit is connected to the detecting unit, sends the errors to a server and receives restoration patches which come from the server and correspond to the errors; and the restoration unit is connected to the communication unit and restores the errors according to the corresponding restoration patches. According to the technical scheme, the errors in the mobile terminal can be monitored, the running conditions are reported, the errors which occur are restored actively, and system stability is improved. The invention further provides the server and an error restoration method.
Description
Technical field
The present invention relates to communication technical field, in particular to mobile terminal, server and errors repair method.
Background technology
Development along with intelligent terminal; various application software are also arisen at the historic moment; in use; often there will be system mistake or software error; if application software collapse, the user can only close by force this application software or reinstall application software, if in the system running collapse or go out to misrepresent deliberately abnormal after; the user also can't solve, can only restarting systems.
Secondly, if certain File lose or document lending in terminal system, or in system, certain module startup makes mistakes, and terminal can remain on the blank screen state always, can't continue to start, and has had a strong impact on user's normal use.
Summary of the invention
Consider the above-mentioned background technology, an object of the present invention is to provide a kind of mobile terminal, can repair system or the mistake that occurs when operation of software, improve the stability of a system.
In view of this, according to an aspect of the present invention, provide a kind of mobile terminal, having comprised: detecting unit, the ruuning situation of detection mobile terminal, when mistake appears in mobile terminal, record described mistake; Communication unit, be connected to described detecting unit, and described mistake is sent to server and receives the reparation patch corresponding with described mistake from described server; Repair unit, be connected to described communication unit, according to described corresponding reparation patch, repair described mistake.
When mistake appears in mobile terminal, can in daily record, record this wrong situation, and mistake is sent to server, issue this wrong solution by server, and repair this mistake, and then improved the stability of mobile terminal, avoid the user to run into this mistake just needs positive closing software or system at every turn, affects user's normal use.
In technique scheme, preferably, described detecting unit is also for adding up the number of times that records of described mistake, described, when recording number of times and being more than or equal to threshold value, orders described communication unit that described mistake is sent to described server.
When running into mistake, can in daily record, record occurred mistake, and add up the number of times of every kind of mistake, if number of times exceeds threshold value, illustrate that this mistake is serious and often occur, this mistake can be reported to server, repair corresponding mistake.If number of times is one time twice, the chance made a mistake after illustrating is less, can repair, and avoids the frequent normal use that affects the user of repairing.
In above-mentioned arbitrary technical scheme, preferably, whether described detecting unit also, for when described mobile terminal can't normally start, detects described communication unit and starts, if described communication unit starts, by described communication unit, the mistake of described appearance is sent to described server.
In the process started at mobile terminal, normally start by sequence in unit one by one, a unit can't start the startup that can not affect other unit, but can cause terminal to rest on the blank screen stage always, and then cause terminal can't continue to start, have a strong impact on user's use, if communication unit normally starts, the mistake that other unit can be occurred reports server by information unit, reception is from the reparation patch of server, thereby repair the mistake that other unit occur, avoid terminal to rest on the blank screen stage always.
In technique scheme, preferably, can also comprise: Tip element, be connected to described detecting unit, when described detecting unit detects described communication unit and is not activated, the prompting user will close described mobile terminal.
If detect not normal startup of communication unit, point out the described communication unit of user there is no the normal information started.
According to a further aspect in the invention, also provide a kind of server, having comprised: communication unit, receive from as above-mentioned arbitrary technical scheme described in the mistake of mobile terminal, and will search the reparation patch that unit finds out and be sent to described mobile terminal; Memory cell, carry out corresponding stored by mistake and reparation patch; The described unit of searching, be connected to described communication unit and described memory cell, and the mistake received according to described communication unit finds out the reparation patch corresponding with the mistake of described reception in described memory cell.
According to another aspect of the invention, also provide a kind of errors repair method, comprised the following steps: the ruuning situation of sense terminals, when mistake appears in terminal, record described mistake and described mistake be sent to server; According to mistake preset in described server and the corresponding relation of repairing patch, find out the corresponding reparation patch of mistake sent with described terminal; Described corresponding reparation patch is sent to described terminal to repair described mistake.
When mistake appears in mobile terminal, can in daily record, record this wrong situation, and mistake is sent to server, issue this wrong solution by server, and repair this mistake, and then improved the stability of mobile terminal, avoid the user to run into this mistake just needs positive closing software or system at every turn, affects user's normal use.
In technique scheme, preferably, describedly record described mistake and the step that described mistake is sent to server can also be comprised: adding up the number of times that records of described mistake, when described, when recording number of times and being more than or equal to threshold value, described mistake is sent to described server.
When running into mistake, can in daily record, record occurred mistake, and add up the number of times of every kind of mistake, if number of times exceeds threshold value, illustrate that this mistake is serious and often occur, this mistake can be reported to server, repair corresponding mistake.If number of times is one time twice, the chance made a mistake after illustrating is less, can repair, and avoids the frequent normal use that affects the user of repairing.
In above-mentioned arbitrary technical scheme, preferably, can also comprise: if described server does not find out described corresponding reparation patch, the mistake described terminal sent is sent to designated contact, described designated contact will be corresponding with the mistake of described transmission the reparation patch be sent to described server and preserved, to upgrade described preset mistake and the corresponding relation of repairing patch.
In the process started at mobile terminal, normally start by sequence in unit one by one, a unit can't start the startup that can not affect other unit, but can cause terminal to rest on the blank screen stage always, and then cause terminal can't continue to start, have a strong impact on user's use, if communication unit normally starts, the mistake that other unit can be occurred reports server by information unit, reception is from the reparation patch of server, thereby repair the mistake that other unit occur, avoid terminal to rest on the blank screen stage always.
In above-mentioned arbitrary technical scheme, preferably, can also comprise: when described terminal can't normally start, whether the communication unit that detects described terminal starts, if described communication unit starts, by described communication unit, the mistake of described appearance is sent to described server.
In technique scheme, preferably, if described communication unit is not activated, point out the user information that described letter module is not activated.
The accompanying drawing explanation
Fig. 1 shows the block diagram of mobile terminal according to an embodiment of the invention;
Fig. 2 shows the block diagram of server according to an embodiment of the invention;
Fig. 3 shows the schematic diagram that mobile terminal and server carry out data interaction according to an embodiment of the invention;
Fig. 4 shows the flow chart of errors repair method according to an embodiment of the invention;
Fig. 5 shows the flow chart of errors repair method according to still another embodiment of the invention;
Fig. 6 shows the flow chart according to the errors repair method of an embodiment more of the present invention.
Embodiment
In order more clearly to understand above-mentioned purpose of the present invention, feature and advantage, below in conjunction with the drawings and specific embodiments, the present invention is further described in detail.
A lot of details have been set forth in the following description so that fully understand the present invention; but; the present invention can also adopt other to be different from other modes described here and implement, and therefore, protection scope of the present invention is not subject to the restriction of following public specific embodiment.
Below in conjunction with drawings and Examples, the present invention will be further described.It should be noted that, in the situation that do not conflict, the application's embodiment and the feature in embodiment can combine mutually.
At first referring to figs. 1 to Fig. 3, describe in detail according to embodiments of the invention.
Fig. 1 shows the block diagram of mobile terminal according to an embodiment of the invention.
As shown in Figure 1, mobile terminal 100 comprises according to an embodiment of the invention: detecting unit 102, and the ruuning situation of detection mobile terminal, when mistake appears in mobile terminal, record described mistake; Communication unit 104, be connected to described detecting unit 102, and described mistake is sent to server 200 and receives the reparation patch corresponding with described mistake from described server 200; Repair unit 106, be connected to described communication unit 104, according to described corresponding reparation patch, repair described mistake.
When mistake appears in mobile terminal, can in daily record, record this wrong situation, and mistake is sent to server, issue this wrong solution by server, and repair this mistake, and then improved the stability of mobile terminal, avoid the user to run into this mistake just needs positive closing software or system at every turn, can not affect user's normal use.
In technique scheme, preferably, described detecting unit 102 is also for adding up the number of times that records of described mistake, described, when recording number of times and being more than or equal to threshold value, orders described communication unit 104 that described mistake is sent to described server 200.
When running into mistake, can in daily record, record occurred mistake, and add up the number of times of every kind of mistake, if number of times exceeds threshold value, illustrate that this mistake is serious and often occur, this mistake can be reported to server, repair corresponding mistake.If number of times is one time twice, the chance made a mistake after illustrating is less, can repair, and avoids the frequent normal use that affects the user of repairing.
In above-mentioned arbitrary technical scheme, preferably, whether described detecting unit 102 also, for when described mobile terminal can't normally start, detects described communication unit and starts, if described communication unit starts, by described communication unit, the mistake of described appearance is sent to described server.
In the process started at mobile terminal, normally start by sequence in unit one by one, a unit can't start the startup that can not affect other unit, but can cause terminal to rest on the blank screen stage always, and then cause terminal can't continue to start, have a strong impact on user's use, if communication unit normally starts, the mistake that other unit can be occurred reports server by information unit, reception is from the reparation patch of server, thereby repair the mistake that other unit occur, avoid terminal to rest on the blank screen stage always.
In technique scheme, preferably, can also comprise: Tip element 108, be connected to described detecting unit, when described detecting unit detects described communication unit and is not activated, the prompting user will close described mobile terminal.
If detect not normal startup of communication unit, point out the described communication unit of user there is no the normal information started.
Fig. 2 shows the block diagram of server according to an embodiment of the invention.
As shown in Figure 2, server 200 comprises according to an embodiment of the invention: communication unit 202, reception from as above-mentioned arbitrary technical scheme described in the mistake of mobile terminal 100, and will search the reparation patch that unit 206 finds out and be sent to described mobile terminal; Memory cell 204, carry out corresponding stored by mistake and reparation patch; The described unit 206 of searching, be connected to described communication unit 202 and described memory cell 204, and the mistake received according to described communication unit 202 finds out the reparation patch corresponding with the mistake of described reception in described memory cell.
Fig. 3 shows the schematic diagram that mobile terminal and server carry out data interaction according to an embodiment of the invention.As shown in Figure 3, when mobile terminal 100 starts terminal system, or the mistake occurred when system when operation or running software is added up and the mistake that statistics number exceeds threshold value is sent to server 200, in the server 200 corresponding solution of multiple mistake that prestored, the mistake sent according to mobile terminal 100 finds out the solution corresponding with this mistake (reparation patch) afterwards, corresponding solution is back to mobile terminal 100, repairs the mistake occurred.If server 200 does not find out the corresponding solution of mistake sent with mobile terminal 100, this mistake is sent to the engineer, in Fig. 3, can be sent in engineer's notebook computer 300 by mail box fashion, the engineer finds out solution after receiving this mistake, then by notebook computer 300, this mistake being sent to server 200 is preserved, when mobile terminal 100 same error occurs again, server 200 just can feed back to the solution of uploading on engineering mobile terminal 100, increased the self-regeneration function of mobile terminal, improved the stability of a system.
Fig. 4 shows the flow chart of errors repair method according to an embodiment of the invention.
As shown in Figure 4, errors repair method according to an embodiment of the invention comprises the following steps: step 402, and the ruuning situation of sense terminals, when terminal occurs that when wrong, misregistration also is sent to server by mistake; Step 404, according to mistake preset in server and the corresponding relation of repairing patch, find out the corresponding reparation patch of mistake sent with terminal; Step 406, be sent to terminal with mis repair by corresponding reparation patch.
When system or software error appear in mobile terminal, can in daily record, record this wrong situation, and mistake is sent to server, issue this wrong solution by server, and repair this mistake, and then improved the stability of system, avoid the user to run into this mistake just needs positive closing software or system at every turn, can not affect user's normal use.
In technique scheme, preferably, misregistration also can also comprise the step that mistake is sent to server: mistake of statistics record number of times, when recording number of times and be more than or equal to threshold value, mistake is sent to server.
When running into mistake, can in daily record, record occurred mistake, and add up the number of times of every kind of mistake, if number of times exceeds threshold value, illustrate that this mistake is serious and often occur, this mistake can be reported to server, repair corresponding mistake.If number of times is one time twice, the chance made a mistake after illustrating is less, can repair, and avoids the frequent normal use that affects the user of repairing.
In above-mentioned arbitrary technical scheme, preferably, can also comprise: if server does not find out corresponding reparation patch, the mistake terminal sent is sent to designated contact, designated contact will the reparation patch corresponding with the mistake sent be sent to server is preserved, to upgrade preset mistake and the corresponding relation of repairing patch.
In the process of starting terminal, normally start by sequence in unit one by one, a unit can't start the startup that can not affect other unit, but can cause terminal to rest on the blank screen stage always, and then cause terminal can't continue to start, have a strong impact on user's use, if communication unit normally starts, the mistake that other unit can be occurred reports server by information unit, reception is from the reparation patch of server, thereby repair the mistake that other unit occur, avoid terminal to rest on the blank screen stage always.
In above-mentioned arbitrary technical scheme, preferably, the system of terminal can also comprise the following steps: when can't normally start, whether the communication unit of sense terminals starts, if communication unit starts, detect the mistake that other modules occur, by communication unit, the mistake of appearance is sent to server.
In technique scheme, preferably, if communication unit is not activated, point out the user information that described communication unit is not activated.Described prompting can be the signal lamp flicker of voice suggestion, appointment etc., when terminal can normally show, also can pass through display screen display reminding information.
Further illustrate errors repair method according to still another embodiment of the invention below in conjunction with Fig. 5.
As shown in Figure 5, in step 502, when system can't normally start, detect the lattice module and whether normally start, the profiling error reason.It should be noted that, the android mobile phone is when starting, first start the linux virtual machine, then start Android system on the linux virtual machine, when starting Android system, normally each module starts successively, that is to say, a module can't start the normal startup that can not have influence on other modules in system, but but can cause cell phone system to rest on the blank screen stage always, and then causes cell phone system can't continue to start.
In step 504, judge whether communication unit normally starts, and starts if normal, enters step 506, if normally do not start, enters step 510.If the communication unit rested in the mobile phone of blank screen state has normally started, that just utilizes communication unit to come to carry out alternately with server by network, so can utilize the communication unit started to report the problem of handset starting blank screen to server, and download corresponding reparation file or system upgrade bag by communication unit, system blank screen problem is repaired.
Step is in step 510, and the prompting user is about to shut down and shut down.
In step 506, automatic detected error (for example display module goes wrong) is sent to server.
In step 508, after server is received the reason of makeing mistakes, if some system file is lost, by system communication locations, issue the file of loss; If system problem is serious, just do not lack certain file, by communication unit, automatically issue AKU in terminal.After the complete AKU of terminal downloads, Auto-mounting is also restarted terminal.
Make mistakes and rest on blank screen during the stage when cell phone system starts, carry out data interaction by communication unit and the server started, send failure cause to server, automatically download and lose or the file of makeing mistakes or download AKU and carry out system and automatically repair from server, restart mobile phone after downloading successfully, enter upgrade mode, and the loading upgrading bag, upgrade file is arranged in system, and then the self-regeneration of completion system blank screen.
Errors repair method below in conjunction with Fig. 6 explanation according to an embodiment more of the present invention
As shown in Figure 6, in step 602, when system starts, start detection system or running software situation, if system or application software operation make mistakes, automatically record in daily record.
In step 604, regularly daily record is analyzed, to the same problem number of times statistics of being made mistakes, whether the misjudgment number of times surpasses the threshold value of engineer or user's setting, if judgment result is that be, enter step 606, upload onto the server after log file analysis is arranged; If the determination result is NO, finish this flow process.
In step 608, server carries out analyzing and processing after receiving the journal file of uploading again, whether the mistake of analyzing in journal file has set in advance solution or patch in server, if the solution or the patch that set in advance have been arranged in server, according to solution, progressively deal with problems or automatically issue patch, if server can't be dealt with problems, the problem log of putting in order is preserved, and (by mail or note form) notice correlation engineering teacher, after the engineer receives problem, analyze and propose solution or develop corresponding patch, then will repair patch uploads onto the server, be issued to the terminal of makeing mistakes by server, and be kept in server after running into same problem next time and automatically solved by server.
Can real-time detecting system or the ruuning situation of software according to technical scheme of the present invention, after system or software newspaper is abnormal, automatic misregistration in daily record, engineer or user can set a threshold value, after the abnormal number of times of newspaper reaches this value, will report error situation from the trend server, server can carry out report analysis after receiving and reporting mistake, if in server, set solution or patch, server automatically issues patch file system or software is repaired, if there is no solution in server, can transfer to special engineer and carry out analyze and solve, after the engineer has solved problem, upload corresponding solution or patch on server, so that server automatically solves and processes after running into same problem next time.
In the present invention, unless otherwise clearly defined and limited, broad understanding should be done in the terms such as term " installation ", " being connected ", " connection ", " fixing ", for example, can be to be fixedly connected with, and can be also to removably connect, or connect integratedly; Can be mechanical connection, can be also to be electrically connected to; Can be directly to be connected, also can indirectly be connected by intermediary, can be the connection of two element internals.For the ordinary skill in the art, can understand as the case may be above-mentioned term concrete meaning in the present invention.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations.Within the spirit and principles in the present invention all, any modification of doing, be equal to replacement, improvement etc., within all should being included in protection scope of the present invention.
Claims (10)
1. a mobile terminal, is characterized in that, comprising:
Detecting unit, the ruuning situation of detection mobile terminal, when mistake appears in mobile terminal, record described mistake;
Communication unit, be connected to described detecting unit, and described mistake is sent to server and receives the reparation patch corresponding with described mistake from described server;
Repair unit, be connected to described communication unit, according to described corresponding reparation patch, repair described mistake.
2. mobile terminal according to claim 1, is characterized in that, described detecting unit is also for adding up the number of times that records of described mistake, described, when recording number of times and being more than or equal to threshold value, orders described communication unit that described mistake is sent to described server.
3. mobile terminal according to claim 1 and 2, it is characterized in that, described detecting unit is also for when described mobile terminal can't normally start, whether detect described communication unit starts, if described communication unit starts, by described communication unit, the mistake of described appearance is sent to described server.
4. mobile terminal according to claim 2, is characterized in that, also comprises: Tip element, be connected to described detecting unit, and when described detecting unit detects described communication unit and is not activated, the prompting user will close described mobile terminal.
5. a server, is characterized in that, comprising:
Communication unit, receive the mistake of the described mobile terminal of any one in claim 1 to 4 freely, and will search the reparation patch that unit finds out and be sent to described mobile terminal;
Memory cell, carry out corresponding stored by mistake and reparation patch;
The described unit of searching, be connected to described communication unit and described memory cell, and the mistake received according to described communication unit finds out the reparation patch corresponding with the mistake of described reception in described memory cell.
6. an errors repair method, is characterized in that, comprises the following steps:
The ruuning situation of sense terminals, when mistake appears in terminal, record described mistake and described mistake be sent to server;
According to mistake preset in described server and the corresponding relation of repairing patch, find out the corresponding reparation patch of mistake sent with described terminal;
Described corresponding reparation patch is sent to described terminal to repair described mistake.
7. errors repair method according to claim 6, it is characterized in that, describedly record described mistake and the step that described mistake is sent to server is also comprised: adding up the number of times that records of described mistake, when described, when recording number of times and being more than or equal to threshold value, described mistake is sent to described server.
8. errors repair method according to claim 6, it is characterized in that, also comprise: if described server does not find out described corresponding reparation patch, the mistake described terminal sent is sent to designated contact, described designated contact will be corresponding with the mistake of described transmission the reparation patch be sent to described server and preserved, to upgrade described preset mistake and the corresponding relation of repairing patch.
9. according to the described errors repair method of any one in claim 6 to 8, it is characterized in that, described terminal also comprises: when can't normally start, whether the communication unit that detects described terminal starts, if described communication unit starts, by described communication unit, the mistake of described appearance is sent to described server.
10. errors repair method according to claim 9, is characterized in that, if described communication unit is not activated, points out the user and close described terminal.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210149220.1A CN103428333B (en) | 2012-05-15 | 2012-05-15 | Mobile terminal, server and errors repair method |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210149220.1A CN103428333B (en) | 2012-05-15 | 2012-05-15 | Mobile terminal, server and errors repair method |
Publications (2)
Publication Number | Publication Date |
---|---|
CN103428333A true CN103428333A (en) | 2013-12-04 |
CN103428333B CN103428333B (en) | 2015-12-16 |
Family
ID=49652491
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201210149220.1A Active CN103428333B (en) | 2012-05-15 | 2012-05-15 | Mobile terminal, server and errors repair method |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN103428333B (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104794054A (en) * | 2015-04-22 | 2015-07-22 | 惠州Tcl移动通信有限公司 | Log information real-time obtaining and uploading method and system and mobile terminal |
CN105812477A (en) * | 2016-04-15 | 2016-07-27 | 广州杰赛科技股份有限公司 | Cloud disk deployment method and system |
CN106791976A (en) * | 2016-12-07 | 2017-05-31 | 康佳集团股份有限公司 | The method and system of application have been installed in a kind of Android television monitoring and treatment |
CN106776243A (en) * | 2016-12-30 | 2017-05-31 | 中国银联股份有限公司 | A kind of monitoring method and device for monitoring software |
CN107817984A (en) * | 2016-09-13 | 2018-03-20 | 高德信息技术有限公司 | A kind of hot patch loading method and device |
CN108008972A (en) * | 2016-10-27 | 2018-05-08 | 北京京东尚科信息技术有限公司 | Restorative procedure, the apparatus and system of the application program of client |
CN109933478A (en) * | 2017-12-19 | 2019-06-25 | 杭州华为数字技术有限公司 | A kind of fault handling method and storage system of storage system |
CN112822065A (en) * | 2020-12-30 | 2021-05-18 | 上海数果科技有限公司 | Linux-based talkback service monitoring system and monitoring method |
CN113641386A (en) * | 2021-08-17 | 2021-11-12 | 西安酷赛科技有限公司 | Method and system for upgrading based on error reporting frequency |
CN115277747A (en) * | 2022-06-24 | 2022-11-01 | 共青科技职业学院 | Vehicle network repairing method, system, computer device and readable storage medium |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6389288B1 (en) * | 1997-06-27 | 2002-05-14 | Fujitsu Limited | Mobile communication terminal capable of executing location-related services |
CN1470985A (en) * | 2002-07-24 | 2004-01-28 | 力捷电脑股份有限公司 | Error back-report and correction method for peripheral unit |
JP2005051583A (en) * | 2003-07-30 | 2005-02-24 | Nec Infrontia Corp | Voice data radio communication system and voice data radio communication program |
CN101175109A (en) * | 2006-10-31 | 2008-05-07 | 中兴通讯股份有限公司 | System abnormal information processing method and device |
CN101631324A (en) * | 2009-08-11 | 2010-01-20 | 酷派软件技术(深圳)有限公司 | Mobile terminal fault diagnosis and repair method and mobile terminal thereof |
CN101714105A (en) * | 2008-10-07 | 2010-05-26 | 英业达股份有限公司 | Error reporting and error solving replying system of application program and method thereof |
CN102056202A (en) * | 2009-10-29 | 2011-05-11 | 中兴通讯股份有限公司 | Mobile terminal error processing method and system |
-
2012
- 2012-05-15 CN CN201210149220.1A patent/CN103428333B/en active Active
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6389288B1 (en) * | 1997-06-27 | 2002-05-14 | Fujitsu Limited | Mobile communication terminal capable of executing location-related services |
CN1470985A (en) * | 2002-07-24 | 2004-01-28 | 力捷电脑股份有限公司 | Error back-report and correction method for peripheral unit |
JP2005051583A (en) * | 2003-07-30 | 2005-02-24 | Nec Infrontia Corp | Voice data radio communication system and voice data radio communication program |
CN101175109A (en) * | 2006-10-31 | 2008-05-07 | 中兴通讯股份有限公司 | System abnormal information processing method and device |
CN101714105A (en) * | 2008-10-07 | 2010-05-26 | 英业达股份有限公司 | Error reporting and error solving replying system of application program and method thereof |
CN101631324A (en) * | 2009-08-11 | 2010-01-20 | 酷派软件技术(深圳)有限公司 | Mobile terminal fault diagnosis and repair method and mobile terminal thereof |
CN102056202A (en) * | 2009-10-29 | 2011-05-11 | 中兴通讯股份有限公司 | Mobile terminal error processing method and system |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104794054A (en) * | 2015-04-22 | 2015-07-22 | 惠州Tcl移动通信有限公司 | Log information real-time obtaining and uploading method and system and mobile terminal |
CN105812477A (en) * | 2016-04-15 | 2016-07-27 | 广州杰赛科技股份有限公司 | Cloud disk deployment method and system |
CN107817984A (en) * | 2016-09-13 | 2018-03-20 | 高德信息技术有限公司 | A kind of hot patch loading method and device |
CN108008972A (en) * | 2016-10-27 | 2018-05-08 | 北京京东尚科信息技术有限公司 | Restorative procedure, the apparatus and system of the application program of client |
CN106791976A (en) * | 2016-12-07 | 2017-05-31 | 康佳集团股份有限公司 | The method and system of application have been installed in a kind of Android television monitoring and treatment |
CN106776243A (en) * | 2016-12-30 | 2017-05-31 | 中国银联股份有限公司 | A kind of monitoring method and device for monitoring software |
CN106776243B (en) * | 2016-12-30 | 2021-03-16 | 中国银联股份有限公司 | Monitoring method and device for monitoring software |
CN109933478A (en) * | 2017-12-19 | 2019-06-25 | 杭州华为数字技术有限公司 | A kind of fault handling method and storage system of storage system |
CN109933478B (en) * | 2017-12-19 | 2021-02-26 | 华为技术有限公司 | Storage system and fault processing method thereof |
CN112822065A (en) * | 2020-12-30 | 2021-05-18 | 上海数果科技有限公司 | Linux-based talkback service monitoring system and monitoring method |
CN113641386A (en) * | 2021-08-17 | 2021-11-12 | 西安酷赛科技有限公司 | Method and system for upgrading based on error reporting frequency |
CN115277747A (en) * | 2022-06-24 | 2022-11-01 | 共青科技职业学院 | Vehicle network repairing method, system, computer device and readable storage medium |
Also Published As
Publication number | Publication date |
---|---|
CN103428333B (en) | 2015-12-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN103428333B (en) | Mobile terminal, server and errors repair method | |
CN103377094B (en) | Method for monitoring abnormality and device | |
JP6291248B2 (en) | Firmware upgrade error detection and automatic rollback | |
CN103458086B (en) | A kind of smart mobile phone and fault detection method thereof | |
CN102591745B (en) | Method and device for system recovery based on android system and intelligent equipment | |
CN102681871A (en) | Firmware upgrading system based on communication interfaces | |
CN102508734B (en) | Operating system recovery method and intelligent equipment | |
CN103530199A (en) | Software running error repairing method, device and system | |
CN107678875B (en) | Fault detection and automatic repair method, device, terminal and storage medium | |
CN101631324A (en) | Mobile terminal fault diagnosis and repair method and mobile terminal thereof | |
CN102880527B (en) | Data recovery method of baseboard management controller | |
CN103927239A (en) | Method and device for restoring system of terminal equipment | |
CN104049999A (en) | Automatic storage device repair system based on network and method thereof | |
CN106897166B (en) | Mobile terminal and repairing method thereof | |
CN104932955A (en) | Method for backing up data during factory setting restoring of mobile terminal, and mobile terminal | |
CN103249027B (en) | The method and apparatus that a kind of terminal traffic processes | |
CN101207519A (en) | Version server, operation maintenance unit and method for restoring failure | |
CN102137154A (en) | Method and device for upgrading customer premise equipment (CPE) | |
WO2017220013A1 (en) | Service processing method and apparatus, and storage medium | |
CN111427259B (en) | Main and standby switching method of machine frame slot type, intelligent equipment and storage medium | |
WO2023240944A1 (en) | Data recovery method and apparatus, electronic device, and storage medium | |
CN114647531B (en) | Failure solving method, failure solving system, electronic device, and storage medium | |
CN111030871A (en) | Configuration information synchronization method and device based on dual-computer hot standby system | |
CN109324834A (en) | A kind of system and method that distributed storage server is restarted automatically | |
CN103632098A (en) | Method and device for repairing bugs |
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 |