CN111897683A - Electronic equipment and fault repairing method and device thereof - Google Patents
Electronic equipment and fault repairing method and device thereof Download PDFInfo
- Publication number
- CN111897683A CN111897683A CN202010664433.2A CN202010664433A CN111897683A CN 111897683 A CN111897683 A CN 111897683A CN 202010664433 A CN202010664433 A CN 202010664433A CN 111897683 A CN111897683 A CN 111897683A
- Authority
- CN
- China
- Prior art keywords
- configuration data
- fault
- electronic equipment
- electronic device
- state information
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 40
- 230000008439 repair process Effects 0.000 claims abstract description 8
- 238000004590 computer program Methods 0.000 claims description 18
- 238000003860 storage Methods 0.000 claims description 15
- 238000003062 neural network model Methods 0.000 claims description 9
- 238000005067 remediation Methods 0.000 claims 1
- 230000008569 process Effects 0.000 abstract description 9
- 238000012423 maintenance Methods 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000011084 recovery Methods 0.000 description 3
- 230000002159 abnormal effect Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000004519 manufacturing process Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000009826 distribution Methods 0.000 description 1
- 239000013072 incoming material Substances 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012549 training Methods 0.000 description 1
- 230000002618 waking effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2289—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing by configuration test
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
- G06F11/3644—Software debugging by instrumenting at runtime
Abstract
The application belongs to the field of fault repair, and discloses a fault repair method of electronic equipment, which comprises the following steps: determining that the fault of the electronic equipment is caused by the problem of hardware consistency; acquiring state information corresponding to a fault caused by the problem of hardware consistency of the electronic equipment; and updating the configuration data of the electronic equipment according to the state information corresponding to the fault. Therefore, the operation parameters of the electronic equipment can be adjusted through updating the configuration data, the fault can be repaired without returning the electronic equipment to the factory for maintenance, the repairing process is simplified, and the repairing efficiency is greatly improved.
Description
Technical Field
The application belongs to the field of fault repair, and particularly relates to electronic equipment and a fault repair method and device thereof.
Background
In the production process of electronic devices, due to differences in processes, production flows and chip incoming material batches, finished electronic devices may have certain hardware differences. Hardware differences include, for example, impedance differences, capacitive reactance differences, and the like. The hardware difference brings the difference of the electrical characteristics, and the CPU and the memory of the electronic device have certain tolerance to the electrical characteristics. When the electrical characteristics are within a certain tolerance range, the electronic device can normally operate, and once the electrical characteristics exceed the certain tolerance range, operation faults can occur, such as bit flipping BitFlip of the memory, program runaway, accident-free abnormal crash and the like.
When the electronic characteristics of the electronic device exceed a certain tolerance range and an operation fault occurs, the electronic device is often handed over to a factory through customer service to be disassembled, the working voltage or working frequency of a CPU or a memory is adjusted, or a driving circuit is adjusted, and the fault repairing process is troublesome and the repairing efficiency is low.
Disclosure of Invention
In view of this, embodiments of the present application provide an electronic device and a fault repairing method and apparatus thereof, so as to solve the problems in the prior art that fault repairing of an electronic device is troublesome and repairing efficiency is not high.
A first aspect of an embodiment of the present application provides a method for repairing a fault of an electronic device, where the method includes:
determining that the fault of the electronic equipment is caused by the problem of hardware consistency;
acquiring state information corresponding to a fault caused by the problem of hardware consistency of the electronic equipment;
and updating the configuration data of the electronic equipment according to the state information corresponding to the fault.
With reference to the first aspect, in a first possible implementation manner of the first aspect, the step of updating the configuration data of the electronic device according to the state information corresponding to the fault includes:
according to the state information corresponding to the fault, adjusting configuration data in a software package manager;
and updating the electronic equipment according to the adjusted configuration data in the software package manager.
With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the step of updating the electronic device according to the adjusted configuration data in the software package manager includes:
storing the adjusted software package manager to a specified storage position;
initializing the software package manager, and reading configuration data of a specified storage position;
and configuring the electronic equipment according to the read configuration data.
With reference to the first possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the step of adjusting configuration data in the software package manager according to the state information corresponding to the fault includes:
searching configuration data corresponding to the state information of the fault according to the preset corresponding relation between the state information and the configuration data;
updating the software package manager according to the searched configuration data.
With reference to the first possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the step of adjusting configuration data in the software package manager according to the state information corresponding to the fault includes:
inputting the fault information into a neural network model which is trained in advance, and outputting configuration data of the fault information, wherein the neural network model is trained according to sample data of historical restoration;
updating the software package manager according to the outputted configuration data.
With reference to the first aspect, in a fifth possible implementation manner of the first aspect, the step of determining that the failure of the electronic device is a failure caused by a hardware consistency problem includes:
and determining that the electronic equipment fails within a preset probability range in a statistical mode, wherein the failure of the electronic equipment is caused by the problem of hardware consistency when the electronic equipment can be recovered to be normal after the failure occurs.
With reference to the first aspect, in a sixth possible implementation manner of the first aspect, the configuration data includes one or more of a voltage, a frequency, and a driving capability of a device of the electronic device.
A second aspect of an embodiment of the present application provides a fault repairing apparatus for an electronic device, the apparatus including:
the fault determining unit is used for determining that the fault of the electronic equipment is caused by the problem of hardware consistency;
the state information acquisition unit is used for acquiring state information corresponding to faults caused by the hardware consistency problem of the electronic equipment;
and the configuration data adjusting unit is used for updating the configuration data of the electronic equipment according to the state information corresponding to the fault.
A third aspect of embodiments of the present application provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the method according to any one of the first aspect when executing the computer program.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium, in which a computer program is stored, which, when executed by a processor, performs the steps of the method according to any one of the first aspect.
Compared with the prior art, the embodiment of the application has the advantages that: when the fault of the electronic equipment is determined to be caused by the problem of hardware consistency, the state information corresponding to the fault of the electronic equipment is obtained, and the configuration data of the electronic equipment is updated according to the state information, so that the operation parameters of the electronic equipment can be adjusted through updating the configuration data, the fault can be repaired without returning the electronic equipment to the factory for maintenance, the repairing process is simplified, and the repairing efficiency is greatly improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or the prior art descriptions will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive exercise.
Fig. 1 is a schematic flow chart of an implementation of a fault repairing method for an electronic device according to an embodiment of the present application;
FIG. 2 is a schematic flow chart illustrating an implementation of a method for updating an electronic device according to configuration data according to an embodiment of the present application;
fig. 3 is a schematic diagram of a fault repairing apparatus of an electronic device according to an embodiment of the present disclosure;
fig. 4 is a schematic diagram of an electronic device provided in an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system structures, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
In order to explain the technical solution described in the present application, the following description will be given by way of specific examples.
Fig. 1 is a schematic flow chart of an implementation process of a fault repairing method for an electronic device according to an embodiment of the present application, which is detailed as follows:
in step S101, it is determined that the failure of the electronic device is a failure caused by a hardware consistency problem.
The electronic equipment can be a smart phone, a smart watch or other intelligent electronic equipment.
When the electronic equipment fails (including dead halt, program run-off, bit reversal and the like), more faults are caused, including hardware consistency faults, program BUGs BUG, abnormal equipment use, hardware damage and the like. When it is determined that the electronic device is a fault caused by the hardware consistency problem, the faults of the electronic device may be counted, and whether the fault is a fault caused by the hardware consistency problem is determined according to a result of the counting.
In a possible implementation, a probability range of occurrence of a fault due to a hardware consistency problem may be set in advance. When the electronic equipment fails, the electronic equipment can be operated and operated again in a restarting mode and the like. When the electronic device can operate and work normally, the probability of the fault can be further acquired. And when the probability of occurrence accords with a preset probability range, determining that the fault is caused by the hardware consistency problem.
For example, when the electronic device crashes when waking up in sleep mode, the electronic device is restarted to determine whether the electronic device can be started and operated normally. And if the electronic equipment can be normally started and operated, acquiring the probability of the fault, and determining that the fault belongs to the fault caused by the hardware consistency problem when the probability of the fault accords with a preset probability range.
When the electronic equipment is judged to normally work, when the electronic equipment is in a crash fault, the electronic equipment can be restarted by triggering a restart instruction through the module for monitoring the running state of the electronic equipment, so that whether the restarted electronic equipment normally runs can be judged. When the system program faults other than the dead halt occur in the electronic equipment, the system can be restarted to detect that the electronic equipment can normally operate. When the non-system program running in the electronic device fails, the failed non-system program running in the electronic device may be restarted, or the electronic device may also be restarted to determine whether the failure still exists.
In step S102, status information corresponding to a failure caused by a hardware consistency problem of the electronic device is acquired.
The state information may refer to operation information of the electronic device when a fault occurs. For example, the operation state of the electronic device, the duration of the motion state, the power information of the electronic device, the operation information received by the electronic device, and the like may be included.
The state information corresponding to the time point of the fault can be determined according to the running log of the electronic equipment. When the system has a crash fault, the time point of the fault and the state information of the electronic device corresponding to the time point of the fault can be consulted after the system is restarted.
In step S103, the configuration data of the electronic device is updated according to the status information corresponding to the failure.
The configuration data of the electronic device may include one or more of a voltage, a frequency, or a driving capability configured by a device of the electronic device. For example, the device of the electronic device may include core logic CX, embedded memory MX, and the like.
When updating the configuration data of the electronic device according to the state information corresponding to the fault, the configuration data in the software package manager may be adjusted according to the state information corresponding to the fault, and then the electronic device may be configured according to the configuration data in the software package manager, including adjustment of voltage, frequency, driving capability, and the like of a device of the electronic device.
In one implementation manner, a fault occurring in the electronic device is a crash fault, and the state information corresponding to the fault includes that the electronic device is in a sleep-wake state. The configuration data determined according to the state information may include adjustment of sleep voltages of the core logic CX and the embedded memory MX, and may switch the sleep Mode of the electronic device from the retention Mode to the low power consumption Mode LPM.
In the implementation of determining the configuration data according to the state information, the configuration data may be determined according to a preset correspondence table. The state information in the corresponding relationship table may include a corresponding relationship between single information, a fault type, and configuration data in the state information. For example, the state information may be sleep wake-up state information, the fault type may be a dead halt, and the corresponding configuration data may be the sleep voltage of the adjustment core logic CX and the embedded memory MX.
Of course, the correspondence relationship may include a correspondence relationship between a plurality of pieces of information in the status information, the failure type, and the configuration data. For example, the correspondence between the duration of the sleep of the electronic device, the power of the electronic device, the operation information received by the electronic device, and the configuration data may be used.
Because of the large amount of state information, the configuration data corresponding to different state information may be different. In order to more accurately determine the configuration data corresponding to the state information, the configuration data corresponding to the state information can be calculated through the trained neural network model. The neural network model can input the fault type and the state information in the sample data into the neural network model according to the sample data of the historical repair information, output the calculated configuration information, and adjust the parameters of the neural network model according to the difference between the calculated configuration information and the configuration information in the sample data when the calculated configuration information is compared with the configuration information in the sample data. And (5) finishing training the neural network model by repeatedly optimizing until the difference meets the preset requirement.
The failure type refers to a type of failure caused by a hardware consistency problem, and includes, for example, a dead halt caused by the hardware consistency problem, a program run-off caused by the hardware consistency problem, a bit flip caused by the hardware consistency problem, and the like.
In a possible implementation manner, the configuration data of the electronic device can be determined according to the state information, the fault type and the historical case of the repair scheme.
The configuration data may include the device to be configured, as well as the type of parameter modification of the device. For example, the device may include core logic CX, embedded memory MX, or the like. The parameter modification types may include modifying voltage, frequency, drive capability, etc.
After the configuration data is determined according to the state information corresponding to the fault, the RPM of the software package manager can be adjusted and updated according to the configuration data, and the electronic equipment is updated through the software package manager. Specifically, as shown in fig. 2, the method includes:
in step S1031, the adjusted software package manager is stored to the specified storage location.
After the configuration data is updated to the software package manager, the electronic device needs to make the modified configuration data effective by reloading the configuration data.
In step S1032, the software package manager is initialized, and configuration data of a specified storage location is read.
The software package manager can be initialized by restarting the electronic device, and the configuration data in the software package manager can be extracted. The designated storage location may be a location of configuration data read by a software package manager preset by the system.
In step S1033, the electronic device is configured according to the read configuration data.
And according to the read configuration data, applying the configuration data to the electronic equipment to correspondingly change the voltage, the frequency or the driving capability of the device of the electronic equipment.
In a possible implementation manner, after the configuration data is updated, when a fault still occurs, the configuration data may be further optimized according to the frequency of occurrence of the fault. For example, when the failure frequency is reduced, the configuration data may be further adjusted according to the reduced amplitude, so as to better optimize the configuration data of the electronic device.
In a possible implementation manner, the configuration data acquired by the present application may be data corresponding to a high-pass related chip, and may be acquired through a high-pass platform.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
Fig. 3 is a schematic diagram of a fault repairing apparatus for an electronic device according to an embodiment of the present application, where as shown in fig. 3, the apparatus includes:
a failure determining unit 301, configured to determine that a failure of the electronic device is a failure caused by a hardware consistency problem;
a status information obtaining unit 302, configured to obtain status information corresponding to a fault caused by a hardware consistency problem of an electronic device;
a configuration data adjusting unit 303, configured to update the configuration data of the electronic device according to the status information corresponding to the fault.
The failure recovery apparatus for an electronic device shown in fig. 3 corresponds to the failure recovery method for an electronic device shown in fig. 1.
Fig. 4 is a schematic diagram of an electronic device according to an embodiment of the present application. As shown in fig. 4, the electronic apparatus 4 of this embodiment includes: a processor 40, a memory 41 and a computer program 42 stored in said memory 41 and operable on said processor 40, such as a fault repair program for an electronic device. The processor 40, when executing the computer program 42, implements the steps in the above-described embodiments of the method of fault recovery for each electronic device. Alternatively, the processor 40 implements the functions of the modules/units in the above-described device embodiments when executing the computer program 42.
Illustratively, the computer program 42 may be partitioned into one or more modules/units that are stored in the memory 41 and executed by the processor 40 to accomplish the present application. The one or more modules/units may be a series of computer program instruction segments capable of performing specific functions, which are used to describe the execution of the computer program 42 in the electronic device 4.
The electronic device 4 may be a computing device such as a smart phone, a smart watch, a desktop computer, a notebook, a palm computer, and a cloud server. The electronic device may include, but is not limited to, a processor 40, a memory 41. Those skilled in the art will appreciate that fig. 4 is merely an example of an electronic device 4 and does not constitute a limitation of the electronic device 4 and may include more or fewer components than shown, or some components may be combined, or different components, e.g., the electronic device may also include input-output devices, network access devices, buses, etc.
The Processor 40 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 41 may be an internal storage unit of the electronic device 4, such as a hard disk or a memory of the electronic device 4. The memory 41 may also be an external storage device of the electronic device 4, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like, which are provided on the electronic device 4. Further, the memory 41 may also include both an internal storage unit and an external storage device of the electronic device 4. The memory 41 is used for storing the computer program and other programs and data required by the electronic device. The memory 41 may also be used to temporarily store data that has been output or is to be output.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other ways. For example, the above-described embodiments of the apparatus/terminal device are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated modules/units, if implemented in the form of software functional units and sold or used as separate products, may be stored in a computer readable storage medium. Based on such understanding, all or part of the flow in the method of the embodiments described above can be realized by a computer program, which can be stored in a computer-readable storage medium and can realize the steps of the embodiments of the methods described above when the computer program is executed by a processor. . Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain other components which may be suitably increased or decreased as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media which may not include electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A method of fault remediation for an electronic device, the method comprising:
determining that the fault of the electronic equipment is caused by the problem of hardware consistency;
acquiring state information corresponding to a fault caused by the problem of hardware consistency of the electronic equipment;
and updating the configuration data of the electronic equipment according to the state information corresponding to the fault.
2. The method according to claim 1, wherein the step of updating the configuration data of the electronic device according to the status information corresponding to the failure comprises:
according to the state information corresponding to the fault, adjusting configuration data in a software package manager;
and updating the electronic equipment according to the adjusted configuration data in the software package manager.
3. The method of claim 2, wherein the step of updating the electronic device according to the adjusted configuration data in the software package manager comprises:
storing the adjusted software package manager to a specified storage position;
initializing the software package manager, and reading configuration data of a specified storage position;
and configuring the electronic equipment according to the read configuration data.
4. The method of claim 2, wherein the step of adjusting the configuration data in the software package manager according to the status information corresponding to the failure comprises:
searching configuration data corresponding to the state information of the fault according to the preset corresponding relation between the state information and the configuration data;
updating the software package manager according to the searched configuration data.
5. The method of claim 2, wherein the step of adjusting the configuration data in the software package manager according to the status information corresponding to the failure comprises:
inputting the fault information into a neural network model which is trained in advance, and outputting configuration data of the fault information, wherein the neural network model is trained according to sample data of historical restoration;
updating the software package manager according to the outputted configuration data.
6. The method of claim 1, wherein the step of determining that the failure of the electronic device is a failure caused by a hardware consistency problem comprises:
and determining that the electronic equipment fails within a preset probability range in a statistical mode, wherein the failure of the electronic equipment is caused by the problem of hardware consistency when the electronic equipment can be recovered to be normal after the failure occurs.
7. The method of claim 1, wherein the configuration data comprises one or more of voltage, frequency, drive capability of a device of the electronic device.
8. A fault repair apparatus for an electronic device, the apparatus comprising:
the fault determining unit is used for determining that the fault of the electronic equipment is caused by the problem of hardware consistency;
the state information acquisition unit is used for acquiring state information corresponding to faults caused by the hardware consistency problem of the electronic equipment;
and the configuration data adjusting unit is used for updating the configuration data of the electronic equipment according to the state information corresponding to the fault.
9. An electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the steps of the method according to any of claims 1 to 7 are implemented when the computer program is executed by the processor.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010664433.2A CN111897683A (en) | 2020-07-10 | 2020-07-10 | Electronic equipment and fault repairing method and device thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010664433.2A CN111897683A (en) | 2020-07-10 | 2020-07-10 | Electronic equipment and fault repairing method and device thereof |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111897683A true CN111897683A (en) | 2020-11-06 |
Family
ID=73192333
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010664433.2A Pending CN111897683A (en) | 2020-07-10 | 2020-07-10 | Electronic equipment and fault repairing method and device thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111897683A (en) |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1648870A (en) * | 2005-03-09 | 2005-08-03 | 北京软通科技有限责任公司 | Automatic detesting method for computer system hardware device |
| CN101631324A (en) * | 2009-08-11 | 2010-01-20 | 酷派软件技术（深圳）有限公司 | Mobile terminal fault diagnosis and repair method and mobile terminal thereof |
| CN103778044A (en) * | 2012-10-23 | 2014-05-07 | 伊姆西公司 | Method and device for diagnosing system faults |
| US20170091019A1 (en) * | 2014-09-22 | 2017-03-30 | Shenzhen Tcl New Technology Co., Ltd | Method and system for repairing fault of terminal |
| CN107920161A (en) * | 2017-10-26 | 2018-04-17 | 珠海市魅族科技有限公司 | Terminal control method and device, terminal and readable storage medium storing program for executing |
| CN108199922A (en) * | 2018-01-11 | 2018-06-22 | 承德石油高等专科学校 | A kind of system and method for diagnosing and repairing for the network equipment and server failure |
| CN108322345A (en) * | 2018-02-07 | 2018-07-24 | 平安科技（深圳）有限公司 | A kind of dissemination method and server of fault restoration data packet |
| CN108507119A (en) * | 2018-03-28 | 2018-09-07 | 珠海格力电器股份有限公司 | A kind of equipment fault restorative procedure, device, storage medium and equipment |
| CN108880901A (en) * | 2018-06-29 | 2018-11-23 | 合肥微商圈信息科技有限公司 | A kind of network equipment and server failure diagnosis and the system and method repaired |
| CN108959009A (en) * | 2018-07-26 | 2018-12-07 | 郑州云海信息技术有限公司 | A kind of server failure analysis method and its fail analysis device |
| CN109101375A (en) * | 2018-07-04 | 2018-12-28 | 维沃移动通信有限公司 | A kind of method, server and test device for repairing failure |
| CN109670584A (en) * | 2018-12-27 | 2019-04-23 | 张婧 | A kind of fault diagnosis method and system based on big data |
| US20190384758A1 (en) * | 2017-02-28 | 2019-12-19 | Microsoft Technology Licensing, Llc | Data consistency check in distributed system |
| CN110750377A (en) * | 2019-09-06 | 2020-02-04 | 深圳平安通信科技有限公司 | Fault positioning method and device |
| CN111325262A (en) * | 2020-02-14 | 2020-06-23 | 逸驾智能科技有限公司 | Method and device for analyzing vehicle faults |
-
2020
- 2020-07-10 CN CN202010664433.2A patent/CN111897683A/en active Pending
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1648870A (en) * | 2005-03-09 | 2005-08-03 | 北京软通科技有限责任公司 | Automatic detesting method for computer system hardware device |
| CN101631324A (en) * | 2009-08-11 | 2010-01-20 | 酷派软件技术（深圳）有限公司 | Mobile terminal fault diagnosis and repair method and mobile terminal thereof |
| CN103778044A (en) * | 2012-10-23 | 2014-05-07 | 伊姆西公司 | Method and device for diagnosing system faults |
| US20170091019A1 (en) * | 2014-09-22 | 2017-03-30 | Shenzhen Tcl New Technology Co., Ltd | Method and system for repairing fault of terminal |
| US20190384758A1 (en) * | 2017-02-28 | 2019-12-19 | Microsoft Technology Licensing, Llc | Data consistency check in distributed system |
| CN107920161A (en) * | 2017-10-26 | 2018-04-17 | 珠海市魅族科技有限公司 | Terminal control method and device, terminal and readable storage medium storing program for executing |
| CN108199922A (en) * | 2018-01-11 | 2018-06-22 | 承德石油高等专科学校 | A kind of system and method for diagnosing and repairing for the network equipment and server failure |
| CN108322345A (en) * | 2018-02-07 | 2018-07-24 | 平安科技（深圳）有限公司 | A kind of dissemination method and server of fault restoration data packet |
| CN108507119A (en) * | 2018-03-28 | 2018-09-07 | 珠海格力电器股份有限公司 | A kind of equipment fault restorative procedure, device, storage medium and equipment |
| CN108880901A (en) * | 2018-06-29 | 2018-11-23 | 合肥微商圈信息科技有限公司 | A kind of network equipment and server failure diagnosis and the system and method repaired |
| CN109101375A (en) * | 2018-07-04 | 2018-12-28 | 维沃移动通信有限公司 | A kind of method, server and test device for repairing failure |
| CN108959009A (en) * | 2018-07-26 | 2018-12-07 | 郑州云海信息技术有限公司 | A kind of server failure analysis method and its fail analysis device |
| CN109670584A (en) * | 2018-12-27 | 2019-04-23 | 张婧 | A kind of fault diagnosis method and system based on big data |
| CN110750377A (en) * | 2019-09-06 | 2020-02-04 | 深圳平安通信科技有限公司 | Fault positioning method and device |
| CN111325262A (en) * | 2020-02-14 | 2020-06-23 | 逸驾智能科技有限公司 | Method and device for analyzing vehicle faults |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109814524B (en) | Vehicle diagnosis method, device and system | |
| CN103023984B (en) | Terminal application server and application log filtering method thereof | |
| CN111078579A (en) | Monkey testing method and device and terminal equipment | |
| CN107590009B (en) | Fault processing method and device for host operation process | |
| CN1848089A (en) | Method and system for providing an auxiliary bios code in an auxiliary bios memory utilizing time expiry control | |
| CN111897683A (en) | Electronic equipment and fault repairing method and device thereof | |
| CN110798370A (en) | Bus protocol debugging method and device based on universal interface and terminal equipment | |
| CN110134598B (en) | Batch processing method, device and system | |
| CN110244222B (en) | Limit origin positioning method and device of motor, terminal equipment and storage medium | |
| CN112598537A (en) | Power equipment fault diagnosis method and device and terminal equipment | |
| CN115525455A (en) | Method, device, server and storage medium for repairing abnormality of multi-level system | |
| CN115061921A (en) | Automatic test method, device, electronic equipment and readable storage medium | |
| CN114721686A (en) | Configuration data updating method and device, electronic equipment and storage medium | |
| CN114968753A (en) | Equipment upgrading test method, medium, electronic equipment and test system | |
| CN113824995A (en) | Data transmission method and device for robot, electronic device and storage medium | |
| CN108459940B (en) | Configuration information modification method and device of application performance management system and electronic equipment | |
| CN111027104A (en) | Method, device and mainboard for preventing loss of network card identification data | |
| CN113190881B (en) | Method and device for determining machine number of charging module and terminal equipment | |
| CN110716747B (en) | Program operation efficiency optimization method based on function parameter statistics and terminal equipment | |
| CN113103903B (en) | Method for switching sequencing modes of charging modules and terminal equipment | |
| CN115586871B (en) | Cloud computing scene-oriented data additional writing method, device, equipment and medium | |
| CN110175116B (en) | Test date switching method, device and system | |
| US20210311787A1 (en) | System and method for state management of devices | |
| CN115905320A (en) | Switching method and device of business system, electronic equipment and storage medium | |
| CN116149941A (en) | Monitoring method and device of server component, server and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |