CN111625384A - Method and system for analyzing abnormal problems of mobile terminal, terminal equipment and storage medium - Google Patents
Method and system for analyzing abnormal problems of mobile terminal, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN111625384A CN111625384A CN202010447214.9A CN202010447214A CN111625384A CN 111625384 A CN111625384 A CN 111625384A CN 202010447214 A CN202010447214 A CN 202010447214A CN 111625384 A CN111625384 A CN 111625384A
- Authority
- CN
- China
- Prior art keywords
- abnormal
- mobile terminal
- abnormal problem
- unique identification
- type
- 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
- 230000002159 abnormal effect Effects 0.000 title claims abstract description 221
- 238000000034 method Methods 0.000 title claims abstract description 34
- 238000004458 analytical method Methods 0.000 claims abstract description 17
- 238000004590 computer program Methods 0.000 claims description 15
- 238000000605 extraction Methods 0.000 claims description 3
- 238000012827 research and development Methods 0.000 abstract description 5
- 238000012423 maintenance Methods 0.000 abstract description 4
- 230000006698 induction Effects 0.000 abstract 1
- 238000004891 communication Methods 0.000 description 20
- 239000000284 extract Substances 0.000 description 10
- 238000011160 research Methods 0.000 description 8
- 238000012360 testing method Methods 0.000 description 6
- 238000012545 processing Methods 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
- 230000006870 function Effects 0.000 description 3
- 238000003672 processing method Methods 0.000 description 3
- 244000062793 Sorghum vulgare Species 0.000 description 2
- 238000005034 decoration Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 235000019713 millet Nutrition 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000004064 recycling Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004422 calculation algorithm Methods 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000010267 cellular communication Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012546 transfer Methods 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/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
- G06F11/0772—Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a method, a system, terminal equipment and a storage medium for analyzing abnormal problems of a mobile terminal, wherein the method comprises the following steps: acquiring a log generated when the mobile terminal has an abnormal problem, and extracting the log; determining the type of an abnormal problem occurring in the mobile terminal based on the extracted log content; writing a unique identification value corresponding to the abnormal problem type of the mobile terminal into a specific register; when the equipment is started up next time, reading the specific register to obtain the unique identification value in the specific register, and reporting the unique identification value to the server; and counting the identification values of the mobile terminals collected by the server to obtain a comprehensive statistical result of the mobile terminals about the abnormal problem types. The invention realizes the analysis and induction of abnormal problems such as crash and the like of the mobile terminal, can more intuitively see the proportion of different types of abnormal problems, is convenient for subsequent research and development personnel to specially solve the problems, and reduces the after-sale pressure and the maintenance cost of the machine.
Description
Technical Field
The present invention relates to the technical field of mobile terminal anomaly problem solution, and in particular, to a method, a system, a terminal device, and a storage medium for analyzing an anomaly problem of a mobile terminal.
Background
At present, the annual goods output of mobile terminals such as mobile phones and watches in the market is billions, and the huge goods output is thought to be very huge for the after-sale maintenance pressure of the whole market. Every company can test the products under harsh test conditions such as pressure, manual work and the like in a plurality of rounds in the research and development stage of the products. Although most of the above software and hardware problems can be solved through such a series of tests, various strange abnormal problems such as dead halt, program unresponsiveness, program crash and the like still occur when the product reaches the hands of individual users. The abnormal problems comprise various complicated software and hardware problems, the existing abnormal problems with high recurrence probability, and a test engineer can generally feed back to a research and development personnel when a product is not delivered. However, the tester is often limited by the test conditions and the test quantity, and cannot guarantee timely discovery of all abnormal problems. When the product comes into the hands of the user, especially as the magnitude of the shipment volume of the product is increasing, many abnormal problems are exposed. As the shipment volume increases, the abnormal problem accumulates more and more, which not only affects the user experience, but also puts a great strain on the after-sales.
For the abnormal problems of the user mobile terminal in the market, such as crash and the like, the traditional analysis means mainly depends on the post-sale terminal to carry out log extraction or machine return analysis on the user mobile terminal, and the analysis method not only easily causes the same abnormal problem and the state of repeated analysis of developers, but also causes the problem of each terminal to be mixed, and is not beneficial to quickly positioning the abnormal problems. Therefore, it is necessary to design a scientific abnormal problem classification method for the situation.
Disclosure of Invention
The invention aims to provide a method, a system, terminal equipment and a storage medium for analyzing abnormal problems of a mobile terminal, so that the analysis and summary of the mobile terminal dead halt or abnormal problems are realized, the occupation conditions of different types of abnormal problems are more intuitively seen, subsequent research and development personnel can conveniently and specially solve the problems, and the after-sale pressure and the maintenance cost of a machine are reduced.
The technical scheme provided by the invention is as follows:
the invention provides a method for analyzing abnormal problems of a mobile terminal, which comprises the following steps:
acquiring a log generated when the mobile terminal has an abnormal problem, and extracting the log;
determining the abnormal problem type of the mobile terminal based on the extracted log content and the corresponding relation between the preset log content and the abnormal problem type;
writing the unique identification value corresponding to the abnormal problem type appearing in the mobile terminal into a specific register according to the one-to-one correspondence relationship between the preset abnormal problem type and the unique identification value;
when the equipment is started up next time, reading the specific register to obtain the unique identification value in the specific register, and reporting the unique identification value to the server;
and counting the unique identification values of the mobile terminals collected by the server to obtain a comprehensive statistical result of the mobile terminals about the abnormal problem types.
Further, the mobile terminal is an android device, and reporting to the server specifically includes the steps of:
saving the unique identification value read from the specific register to a buffer;
inserting the unique identification value in the buffer into a launcher database;
and the control launcher reports the unique identification value to the server through the network.
Further, in the preset corresponding relationship between the log content and the abnormal problem types, the abnormal problem types are divided according to the hardware and/or software to which the abnormal problem types belong, wherein at least one of the hardware or the software is further subdivided.
Further, the acquiring of the log generated when the mobile terminal has an abnormal problem refers to extracting and extracting the log generated when the mobile terminal crashes or is abnormally restarted; the obtaining of the statistical result of the mobile terminal about the abnormal problem type is specifically to obtain the statistical result of the crash or abnormal restart type.
The invention provides a system for analyzing abnormal problems of a mobile terminal, which comprises modules:
the log extraction module is used for acquiring logs generated when the mobile terminal has abnormal problems and extracting the logs;
the type determining module is used for determining the abnormal problem type of the mobile terminal based on the extracted log content and the corresponding relation between the preset log content and the abnormal problem type;
the register writing module is used for writing the unique identification value corresponding to the abnormal problem type appearing in the mobile terminal into the specific register according to the one-to-one correspondence relationship between the preset abnormal problem type and the unique identification value;
the reading and reporting module is used for reading the specific register when the equipment is started next time to obtain the unique identification value in the specific register and reporting the unique identification value to the server;
and the collecting and counting module is used for counting the unique identification values of the mobile terminals collected by the server to obtain the statistical result of the mobile terminals about the abnormal problem types.
Further, the mobile terminal is an android device, and reporting to the server is specifically realized by adopting the following units:
a read saving unit for saving the unique identification value read from the specific register to the buffer;
the data inserting unit is used for inserting the unique identification value in the buffer into the launcher database;
and the data reporting unit is used for controlling the launcher to report the unique identification value to the server through the network.
Further, in the preset correspondence between the log content and the abnormal problem types, the abnormal problem types are divided according to the hardware and/or software to which the abnormal problem types belong, wherein at least one of the hardware or software is divided into a plurality of abnormal problem types.
Further, the extracting of the log generated when the mobile terminal has an abnormal problem refers to extracting the log generated when the mobile terminal crashes or is abnormally restarted; the obtaining of the comprehensive statistical result of the mobile terminal about the abnormal problem type is specifically to obtain a comprehensive statistical result of a crash or an abnormal restart type.
The invention provides a terminal device, which comprises a processor, a memory and a computer program stored in the memory and capable of running on the processor, wherein the processor is used for executing the computer program stored on the memory and realizing the operation executed by the abnormal problem analysis method of the mobile terminal.
The invention provides a storage medium, wherein at least one instruction is stored in the storage medium, and the instruction is loaded and executed by a processor to realize the operation executed by any one of the mobile terminal abnormal problem analysis methods.
By the method, the system, the terminal equipment and the storage medium for analyzing the abnormal problems of the mobile terminal, the mobile terminal is analyzed and summarized, the occupation conditions of different types of crashes can be seen more intuitively, subsequent research and development personnel can solve the problems in a special way, and after-sale pressure and maintenance cost of a machine are reduced.
Drawings
The above features, technical contents, advantages and implementations of a data processing method, system, terminal device and storage medium will be further described in the following description of preferred embodiments in a clearly understandable manner with reference to the accompanying drawings.
Fig. 1 is a flowchart of an embodiment of an abnormal problem analysis method of a mobile terminal according to the present invention;
FIG. 2 is a flowchart of reporting a unique identification value to a server by using an android system according to the present invention;
fig. 3 is a flowchart of another embodiment of an abnormal problem analysis method of a mobile terminal according to the present invention;
FIG. 4 is a schematic structural diagram of an embodiment of an abnormal problem analysis system of a mobile terminal according to the present invention;
FIG. 5 is a structural diagram of reporting a unique identification value to a server by using an android system according to the present invention;
FIG. 6 is a schematic structural diagram of an abnormal problem analysis system of a mobile terminal according to another embodiment of the present invention;
fig. 7 is a schematic structural diagram of an embodiment of a terminal device of the present invention.
Detailed Description
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following description will be made with reference to the accompanying drawings. It is obvious that the drawings in the following description are only some examples of the invention, and that for a person skilled in the art, other drawings and embodiments can be derived from them without inventive effort.
For the sake of simplicity, the drawings only schematically show the parts relevant to the present invention, and they do not represent the actual structure as a product. In addition, in order to make the drawings concise and understandable, components having the same structure or function in some of the drawings are only schematically illustrated or only labeled. In this document, "one" means not only "only one" but also a case of "more than one".
An embodiment of the present invention, as shown in fig. 1, is a method for analyzing an abnormal problem of a mobile terminal, including the steps of:
s100, obtaining a log generated when the mobile terminal has an abnormal problem, and extracting the log.
The mobile terminal can be a mobile phone, an intelligent watch, a tablet personal computer, an e-book and the like, and when the mobile terminal has an abnormal problem, the abnormal problem is recorded in a log mode. The invention extracts the key parts in the logs by acquiring the logs, namely extracts the contents related to the abnormal problems in the logs. Since the generation rules of the log are known, it is possible for a person skilled in the art to determine how to extract the key parts of the log and which log contents to extract.
In the present embodiment, in the preset correspondence between log content and abnormal problem types, the abnormal problem types are divided according to the hardware and/or software to which the abnormal problem types belong, that is, each type of hardware and/or software has a problem belonging to one type of abnormal problem type. For example, a mobile phone is taken as an example, and the mobile phone can be classified into an abnormal problem type a, an abnormal problem type B, and an abnormal problem type C.
S200, determining the abnormal problem type of the mobile terminal based on the extracted log content and the corresponding relation between the preset log content and the abnormal problem type. For example, the abnormal problem type occurring in the mobile terminal is determined to be abnormal problem type A.
The preset correspondence between the log content and the abnormal problem type can be obtained by the following method:
the method includes the steps of obtaining and analyzing logs of the mobile terminal with abnormal problems in advance, wherein the logs generally need a large number of logs, such as 100-500 logs, classifying and sorting the abnormal problems of the same type, and determining a characteristic part corresponding to the abnormal problems in the logs for each class of abnormal problems classified and sorted, wherein the abnormal problems of the same class may correspond to one characteristic part or multiple characteristic parts, and for example, different mobile terminals may not have different characteristic parts under the same abnormal problem type. Thus, the corresponding relation between the preset log content and the abnormal problem type can be obtained, and the characteristic part is the log content to be extracted.
S300, writing the unique identification value corresponding to the abnormal problem type appearing in the mobile terminal into a specific register according to the one-to-one correspondence relationship between the preset abnormal problem type and the unique identification value.
And each abnormal problem type corresponds to a unique identification value, the unique identification value corresponding to the abnormal problem type of the mobile terminal is stored in a characteristic register, and the flag of int type is stored in the characteristic register. The specific register has a special physical address, and an application processor (CPU) in the mobile terminal can perform read and write operations through addressing.
For example: the abnormal problem type A corresponds to a unique identification value of '1', the abnormal problem type B corresponds to a unique identification value of '2', and the abnormal problem type C corresponds to a unique identification value of '3'. When it is determined that the type of the abnormal problem occurring in the mobile terminal is the abnormal problem type a, the value written to the specific register here is "1".
S400, when the equipment is started up next time, reading the specific register to obtain the unique identification value in the specific register, and reporting the unique identification value to the server. The server may be implemented based on a web platform.
S500, counting the unique identification values of the mobile terminals collected by the server to obtain a comprehensive statistical result of the mobile terminals about the abnormal problem type, for example, a statistical report or an analysis chart of the abnormal problem may be obtained, where the comprehensive statistical result refers to that the data of the mobile terminals are counted together, rather than being counted separately. Therefore, research personnel can more visually see the proportion conditions of different abnormal problem types, and the follow-up research personnel can conveniently and specially solve the problems. The more the number of different abnormal problem types of the mobile terminals of different mobile phones are collected, the closer the statistical result is to the actual situation.
Referring to fig. 2, this embodiment specifically describes a process of reporting a unique identification value to a server by using an android system, taking a mobile terminal as an android device as an example, and specifically includes the following steps:
s401, the unique identification value read from the specific register is saved in a buffer.
buffer means a buffer area, which is used for reserving a certain space of memory size in the memory, and is mainly used for storing temporary data, so that the memory area is called as a buffer area, and the advantages of this are two: reducing actual physical reading and writing times; secondly, the buffer area is allocated with the memory when being created, and the memory area in the memory area is reused all the time, thereby reducing the times of dynamically allocating and recycling the memory.
S402, inserting the unique identification value in the buffer into a launcher database.
Launchers are commonly called as "HomeScreen", namely the first App seen after being started, and launchers are actually an App and are used for displaying and managing other apps on the mobile phone. There are many third party launchers applications on the market today, such as "millet tabletop", "91 tabletop", etc.
And S403, controlling the launcher to report the unique identification value to the server through the network.
In the foregoing embodiment, each type of hardware and/or software occurrence problem is classified into one type of abnormal problem type, and in another embodiment of the present invention, the abnormal problem types are divided according to the hardware and/or software to which the abnormal problem types belong, wherein at least one type of hardware or software is further divided into a plurality of abnormal problem types, that is, there is at least one type of hardware or software, and each type of hardware or software is divided into 2 or more abnormal problem types. For example, in the foregoing embodiment, the mobile phone is taken as an example and is divided into an abnormal problem type a, an abnormal problem type B, an abnormal problem type C1, an abnormal problem type C2 and an abnormal problem type C3, each type C1, C2 and C3 obtained by dividing the abnormal problem type C also belongs to one abnormal problem type, and each type C1, C2 and C3 has a corresponding unique identification value in a one-to-one correspondence relationship between a preset abnormal problem type and a unique identification value. The abnormal problem type C1, the abnormal problem type C2 and the abnormal problem type C3 all belong to abnormal problems on the unified hardware or software C, that is, when a statistical result of the abnormal problem type of the mobile terminal is obtained, the abnormal problem type report includes abnormal problem type reports of each hardware and/or software, such as the abnormal problem type A, B, C and other respective occupation ratios, and also includes abnormal problem type reports of each hardware and/or software, such as the abnormal problem subtypes C1, C2, C3 and respective occupation ratios of other abnormal problem types in the abnormal problem type C.
Another embodiment of the present invention is illustrated in fig. 3, and the embodiment takes the problem of mobile phone crash as an example for explanation. Specifically, this embodiment is a specific application corresponding to the above embodiment, and the same parts may be referred to the above embodiment specifically. The method for analyzing the abnormal problems of the mobile terminal comprises the following steps:
s110, obtaining a log generated when the mobile phone is in a dead halt problem, and extracting the log.
When the mobile phone has a dead halt problem, the mobile phone records the dead halt problem in a log mode. The invention extracts the key parts in the log by acquiring the log, namely extracts the contents related to the crash problem in the log. Since the generation rules of the log are known, it is possible for a person skilled in the art to determine how to extract the key parts of the log and which log contents to extract.
In the embodiment, in the preset correspondence between log content and crash problem types, the log types are divided according to the hardware and/or software to which the log types belong, that is, each type of hardware and/or software has a problem belonging to one type of abnormal problem type. For example, the method can be divided into an Android system end crash problem type, a kernel end crash problem type and a modem end crash problem type.
S210, determining the type of the crash problem of the mobile phone based on the extracted log content and the corresponding relation between the preset log content and the type of the crash problem. For example, the type of the crash problem occurring in the mobile phone is determined to be the Android system terminal crash problem type.
The preset correspondence between the log content and the abnormal problem type can be obtained by the following method:
the method includes the steps that logs of mobile phones with crash problems are obtained and analyzed in advance, a large number of logs are generally needed, for example, 100-500 logs, the crash problems of the same type are classified and sorted, and for each class of crash problems which are classified and sorted, a characteristic part corresponding to the crash problems in the logs is determined, the crash problems of the same class may correspond to one characteristic part or multiple characteristic parts, for example, different crashes may be in the same type of crash problems and may not have different characteristic parts. Thus, the corresponding relation between the preset log content and the crash problem type can be obtained, and the characteristic part is the log content to be extracted.
S310, writing the unique identification value corresponding to the crash problem type of the mobile phone into a specific register according to the one-to-one correspondence relationship between the preset crash problem type and the unique identification value.
And each type of the crash problem corresponds to a unique identification value, the unique identification value corresponding to the type of the crash problem of the mobile phone is stored in the characteristic register, and the flag of the int type is stored in the characteristic register. The specific register has a special physical address, and an application processor (CPU) in the mobile phone can perform read and write operations through addressing.
For example: the Android system terminal crash problem type corresponds to a unique identification value of '1', the kernel terminal crash problem type corresponds to a unique identification value of '2', and the modem terminal crash problem type corresponds to a unique identification value of '3'. When the type of the crash problem of the mobile phone is determined to be the Android system end crash problem type, the value written into the specific register is '1'.
And S410, when the equipment is started up next time, reading the specific register to obtain the unique identification value in the specific register, and reporting the unique identification value to the server.
And S510, counting the unique identification values of the mobile phones collected by the server to obtain a statistical result of the mobile phone about the type of the dead halt problem, for example, a statistical report or an analysis chart of the dead halt problem can be obtained. Therefore, research personnel can more visually see the proportion of different types of crash problems, and the follow-up research personnel can conveniently and specially solve the problems. The more the number of different crash problem types of the mobile terminals of different mobile phones are collected, the closer the statistical result is to the actual situation.
An embodiment of the present invention, as shown in fig. 4, is a system for analyzing an abnormal problem of a mobile terminal, including:
the invention provides a system for analyzing abnormal problems of a mobile terminal, which comprises modules: the invention provides a system for analyzing abnormal problems of a mobile terminal, which comprises modules: the log extracting module 100, the type determining module 200, the register writing module 300, the reading and reporting module 400, and the collecting and counting module 500.
The log extracting module 100 is configured to obtain a log generated when the mobile terminal has an abnormal problem, and extract the log.
The mobile terminal can be a mobile phone, an intelligent watch, a tablet personal computer, an e-book and the like, and when the mobile terminal has an abnormal problem, the abnormal problem is recorded in a log mode. The invention extracts the key parts in the logs by acquiring the logs, namely extracts the contents related to the abnormal problems in the logs. Since the generation rules of the log are known, it is possible for a person skilled in the art to determine how to extract the key parts of the log and which log contents to extract.
In the present embodiment, in the preset correspondence between log content and abnormal problem types, the abnormal problem types are divided according to the hardware and/or software to which the abnormal problem types belong, that is, each type of hardware and/or software has a problem belonging to one type of abnormal problem type. For example, a mobile phone is taken as an example, and the mobile phone can be classified into an abnormal problem type a, an abnormal problem type B, and an abnormal problem type C.
The type determining module 200 is configured to determine the abnormal problem type occurring in the mobile terminal based on the extracted log content and a preset correspondence between the log content and the abnormal problem type. For example, the abnormal problem type occurring in the mobile terminal is determined to be abnormal problem type A.
The preset correspondence between the log content and the abnormal problem type can be obtained by the following method:
the method includes the steps of obtaining and analyzing logs of the mobile terminal with abnormal problems in advance, wherein the logs generally need a large number of logs, such as 100-500 logs, classifying and sorting the abnormal problems of the same type, and determining a characteristic part corresponding to the abnormal problems in the logs for each class of abnormal problems classified and sorted, wherein the abnormal problems of the same class may correspond to one characteristic part or multiple characteristic parts, and for example, different mobile terminals may not have different characteristic parts under the same abnormal problem type. Thus, the corresponding relation between the preset log content and the abnormal problem type can be obtained, and the characteristic part is the log content to be extracted.
The register writing module 300 is configured to write the unique identification value corresponding to the abnormal problem type occurring in the mobile terminal into the specific register according to a one-to-one correspondence relationship between preset abnormal problem types and unique identification values.
Each abnormal problem type corresponds to a unique identification value, the module stores the unique identification value corresponding to the abnormal problem type of the mobile terminal into a characteristic register, and the unique identification value is stored as int type flag in the characteristic register. The specific register has a special physical address, and an application processor (CPU) in the mobile terminal can perform read and write operations through addressing.
For example: the abnormal problem type A corresponds to a unique identification value of '1', the abnormal problem type B corresponds to a unique identification value of '2', and the abnormal problem type C corresponds to a unique identification value of '3'. When it is determined that the type of the abnormal problem occurring in the mobile terminal is the abnormal problem type a, the value written to the specific register here is "1".
The reading reporting module 400 is configured to, when the device is powered on next time, read the specific register to obtain the unique identification value in the specific register, and report the unique identification value to the server. The server may be implemented based on a web platform.
The collecting and counting module 500 is configured to count the unique identification values of the mobile terminals collected by the server to obtain a statistical result of the mobile terminal regarding the type of the abnormal problem, for example, a statistical report or an analysis graph of the abnormal problem may be obtained. Therefore, research personnel can more visually see the proportion of different types of crashes, and the subsequent research personnel can conveniently and specially solve the problems.
Referring to fig. 5, this embodiment takes a mobile terminal as an example of an android device, and specifically describes a structure in which an android system is used to report a unique identification value to a server, where the structure specifically includes: a read save unit 401, a data insert unit 402 and a data report unit 403.
A read saving unit 401 for saving the unique identification value read from the specific register to the buffer.
buffer means a buffer area, which is used for reserving a certain space of memory size in the memory, and is mainly used for storing temporary data, so that the memory area is called as a buffer area, and the advantages of this are two: reducing actual physical reading and writing times; secondly, the buffer area is allocated with the memory when being created, and the memory area in the memory area is reused all the time, thereby reducing the times of dynamically allocating and recycling the memory.
The inserting unit 402 is configured to insert the unique identification value in the buffer into the launcher database.
Launchers are commonly called as "HomeScreen", namely the first App seen after being started, and launchers are actually an App and are used for displaying and managing other apps on the mobile phone. There are many third party launchers applications on the market today, such as "millet tabletop", "91 tabletop", etc.
A data reporting unit 403, configured to control the launcher to report the unique identification value to the server through the network.
In the foregoing embodiment, each type of hardware and/or software occurrence problem is classified into one type of abnormal problem type, and in another embodiment of the present invention, the abnormal problem types are divided according to the hardware and/or software to which the abnormal problem types belong, wherein at least one type of hardware or software is further divided into a plurality of abnormal problem types, that is, there is at least one type of hardware or software, and each type of hardware or software is divided into 2 or more abnormal problem types. For example, in the foregoing embodiment, the mobile phone is taken as an example and is divided into an abnormal problem type a, an abnormal problem type B, an abnormal problem type C1, an abnormal problem type C2 and an abnormal problem type C3, each type C1, C2 and C3 obtained by dividing the abnormal problem type C also belongs to one abnormal problem type, and each type C1, C2 and C3 has a corresponding unique identification value in a one-to-one correspondence relationship between a preset abnormal problem type and a unique identification value. The abnormal problem type C1, the abnormal problem type C2 and the abnormal problem type C3 all belong to the abnormal problems on the unified hardware or software, that is, when the statistical result of the abnormal problem type of the mobile terminal is obtained, the abnormal problem type report of each hardware and/or software is included, such as the abnormal problem type A, B, C and other respective occupation ratios, and the abnormal problem type report of each hardware and/or software is also included, such as the occupation ratios of the abnormal problem types C1, C2, C3 and other abnormal problem types in the abnormal problem type C.
Another embodiment of the present invention is illustrated in fig. 6, and the embodiment takes the problem of mobile phone crash as an example for explanation. Specifically, this embodiment is a specific application corresponding to the above embodiment, and the same parts may be referred to the above embodiment specifically. The method for analyzing the abnormal problem of the mobile terminal comprises the following modules: the log extracting module 110, the type determining module 210, the register writing module 310, the reading and reporting module 410, and the collecting and counting module 510.
The log extracting module 110 is configured to obtain a log generated when the mobile phone crashes, and extract the log.
When the mobile phone has a dead halt problem, the mobile phone records the dead halt problem in a log mode. The invention extracts the key parts in the log by acquiring the log, namely extracts the contents related to the crash problem in the log. Since the generation rules of the log are known, it is possible for a person skilled in the art to determine how to extract the key parts of the log and which log contents to extract.
In the embodiment, in the preset correspondence between log content and crash problem types, the log types are divided according to the hardware and/or software to which the log types belong, that is, each type of hardware and/or software has a problem belonging to one type of abnormal problem type. For example, the method can be divided into an Android system end crash problem type, a kernel end crash problem type and a modem end crash problem type.
The type determining module 210 is configured to determine a crash problem type occurring in the mobile phone based on the extracted log content and a preset correspondence between the log content and the crash problem type. For example, the type of the crash problem occurring in the mobile phone is determined to be the Android system terminal crash problem type.
The preset correspondence between the log content and the abnormal problem type can be obtained by the following method:
the method includes the steps that logs of mobile phones with crash problems are obtained and analyzed in advance, a large number of logs are generally needed, for example, 100-500 logs, the crash problems of the same type are classified and sorted, and for each class of crash problems which are classified and sorted, a characteristic part corresponding to the crash problems in the logs is determined, the crash problems of the same class may correspond to one characteristic part or multiple characteristic parts, for example, different crashes may be in the same type of crash problems and may not have different characteristic parts. Thus, the corresponding relation between the preset log content and the crash problem type can be obtained, and the characteristic part is the log content to be extracted.
The register writing module 310 is configured to write the unique identification value corresponding to the type of the crash problem occurring in the mobile phone into the specific register according to a one-to-one correspondence relationship between the preset type of the crash problem and the unique identification value.
Each kind of the crash problem type corresponds to a unique identification value, the module stores the unique identification value corresponding to the type of the crash problem of the mobile phone into a feature register, and the unique identification value is stored as int type flag in the feature register. The specific register has a special physical address, and an application processor (CPU) in the mobile phone can perform read and write operations through addressing.
For example: the Android system terminal crash problem type corresponds to a unique identification value of '1', the kernel terminal crash problem type corresponds to a unique identification value of '2', and the modem terminal crash problem type corresponds to a unique identification value of '3'. When the type of the crash problem of the mobile phone is determined to be the Android system end crash problem type, the value written into the specific register is '1'.
The reading and reporting module 410 is configured to, when the device is powered on next time, read the specific register to obtain the unique identification value in the specific register, and report the unique identification value to the server.
The collecting and counting module 510 is configured to count the unique identification values of the mobile phones collected by the server to obtain a statistical result of the mobile phone about the type of the crash problem, for example, a statistical report or an analysis graph of the crash problem may be obtained. Therefore, research personnel can more visually see the proportion of different types of crash problems, and the follow-up research personnel can conveniently and specially solve the problems. The more the number of different crash problem types of the mobile terminals of different mobile phones are collected, the closer the statistical result is to the actual situation.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of program modules is illustrated, and in practical applications, the above-described distribution of functions may be performed by different program modules, that is, the internal structure of the apparatus may be divided into different program units or modules to perform all or part of the above-described functions. Each program 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 processing unit, and the integrated unit may be implemented in a form of hardware, or may be implemented in a form of software program unit. In addition, the specific names of the program modules are only used for distinguishing the program modules from one another, and are not used for limiting the protection scope of the application.
One embodiment of the present invention, as shown in fig. 7, a terminal device 100, includes a processor 110, a memory 120, wherein the memory 120 is used for storing a computer program; the processor 110 is configured to execute the computer program stored in the memory 120 to implement the method for analyzing the abnormal problem of the mobile terminal in the embodiment of any one of the methods shown in fig. 1 to 3.
The terminal device 100 may be a desktop computer, a notebook, a palm computer, a tablet computer, a mobile phone, a human-computer interaction screen, or the like. The terminal device 100 may include, but is not limited to, a processor 110, a memory 120. Those skilled in the art will appreciate that fig. 7 is merely an example of the terminal device 100, does not constitute a limitation of the terminal device 100, and may include more or less components than those shown, or combine certain components, or different components, such as: the terminal device 100 may also include input/output interfaces, display devices, network access devices, communication buses, communication interfaces, and the like. A communication interface and a communication bus, and may further include an input/output interface, wherein the processor 110, the memory 120, the input/output interface and the communication interface complete communication with each other through the communication bus. The memory 120 stores a computer program, and the processor 110 is configured to execute the computer program stored in the memory 120 to implement the data processing method in the method embodiment corresponding to any one of fig. 1 to 4.
The Processor 110 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 120 may be an internal storage unit of the terminal device 100, such as: hard disk or memory of the terminal device. The memory may also be an external storage device of the terminal device, such as: the terminal equipment is provided with a plug-in hard disk, an intelligent memory Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) and the like. Further, the memory 120 may also include both an internal storage unit and an external storage device of the terminal device 100. The memory 120 is used for storing the computer program and other programs and data required by the terminal device 100. The memory may also be used to temporarily store data that has been output or is to be output.
A communication bus is a circuit that connects the described elements and enables transmission between the elements. For example, the processor 110 receives commands from other elements through the communication bus, decrypts the received commands, and performs calculations or data processing according to the decrypted commands. The memory 120 may include program modules such as a kernel (kernel), middleware (middleware), an Application Programming Interface (API), and applications. The program modules may be comprised of software, firmware or hardware, or at least two of the same. The input/output interface forwards commands or data entered by a user via the input/output interface (e.g., sensor, keyboard, touch screen). The communication interface connects the terminal device 100 with other network devices, user equipment, networks. For example, the communication interface may be connected to a network by wire or wirelessly to connect to external other network devices or user devices. The wireless communication may include at least one of: wireless fidelity (WiFi), Bluetooth (BT), Near Field Communication (NFC), Global Positioning Satellite (GPS) and cellular communications, among others. The wired communication may include at least one of: universal Serial Bus (USB), high-definition multimedia interface (HDMI), asynchronous transfer standard interface (RS-232), and the like. The network may be a telecommunications network and a communications network. The communication network may be a computer network, the internet of things, a telephone network. The terminal device 100 may be connected to the network through a communication interface, and a protocol by which the terminal device 100 communicates with other network devices may be supported by at least one of an application, an Application Programming Interface (API), middleware, a kernel, and a communication interface.
In an embodiment of the present invention, a storage medium stores at least one instruction, and the instruction is loaded and executed by a processor to implement the operations performed by the corresponding embodiments of the data processing method. For example, the computer readable storage medium may be a read-only memory (ROM), a random-access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, and the like.
They may be implemented in program code that is executable by a computing device such that it is executed by the computing device, or separately, or as individual integrated circuit modules, or as a plurality or steps of individual integrated circuit modules. Thus, the present invention is not limited to any specific combination of hardware and software.
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 recited in detail 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 contents 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 of 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 of the method according to the embodiments of the present invention may also be implemented by sending instructions to relevant hardware through a computer program, where the computer program may be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of the method embodiments may be implemented. Wherein the computer program comprises: computer program code which may be in the form of source code, data item code, an executable file or some intermediate form, etc. The computer-readable storage 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 content of the computer-readable storage medium can be increased or decreased according to the requirements of the legislation and patent practice in the jurisdiction, for example: in certain jurisdictions, in accordance with legislation and patent practice, the computer-readable medium does not include electrical carrier signals and telecommunications signals.
It should be noted that the above embodiments can be freely combined as necessary. The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (10)
1. A method for analyzing abnormal problems of a mobile terminal is characterized by comprising the following steps:
acquiring a log generated when the mobile terminal has an abnormal problem, and extracting the log;
determining the abnormal problem type of the mobile terminal based on the extracted log content and the corresponding relation between the preset log content and the abnormal problem type;
writing the unique identification value corresponding to the abnormal problem type appearing in the mobile terminal into a specific register according to the one-to-one correspondence relationship between the preset abnormal problem type and the unique identification value;
when the equipment is started up next time, reading the specific register to obtain the unique identification value in the specific register, and reporting the unique identification value to the server;
and counting the unique identification values of the mobile terminals collected by the server to obtain a comprehensive statistical result of the mobile terminals about the abnormal problem types.
2. The method for analyzing the abnormal problems of the mobile terminal according to claim 1, wherein the mobile terminal is an android device, and the reporting to the server specifically comprises the steps of:
saving the unique identification value read from the specific register to a buffer;
inserting the unique identification value in the buffer into a launcher database;
and the control launcher reports the unique identification value to the server through the network.
3. The method for analyzing the abnormal problems of the mobile terminal according to claim 1, wherein in the corresponding relationship between the preset log content and the abnormal problem types, the abnormal problem types are divided according to the hardware and/or software to which the abnormal problem types belong, wherein at least one of the hardware or software is divided into a plurality of abnormal problem types.
4. The method according to claim 1, wherein the obtaining of the log generated when the mobile terminal has the abnormal problem is to extract the log generated when the mobile terminal crashes or is abnormally restarted; the obtaining of the comprehensive statistical result of the mobile terminal about the abnormal problem type is specifically to obtain a comprehensive statistical result of a crash or an abnormal restart type.
5. The system for analyzing the abnormal problems of the mobile terminal is characterized by comprising the following modules:
the log extraction module is used for acquiring logs generated when the mobile terminal has abnormal problems and extracting the logs;
the type determining module is used for determining the abnormal problem type of the mobile terminal based on the extracted log content and the corresponding relation between the preset log content and the abnormal problem type;
the register writing module is used for writing the unique identification value corresponding to the abnormal problem type appearing in the mobile terminal into the specific register according to the one-to-one correspondence relationship between the preset abnormal problem type and the unique identification value;
the reading and reporting module is used for reading the specific register when the equipment is started next time to obtain the unique identification value in the specific register and reporting the unique identification value to the server;
and the collection counting module is used for counting the unique identification values of the mobile terminals collected by the server to obtain a comprehensive counting result of the mobile terminals about the abnormal problem types.
6. The system for analyzing the abnormal problems of the mobile terminal according to claim 5, wherein the mobile terminal is an android device, and the reporting to the server is specifically realized by adopting the following units:
a read saving unit for saving the unique identification value read from the specific register to the buffer;
the data inserting unit is used for inserting the unique identification value in the buffer into the launcher database;
and the data reporting unit is used for controlling the launcher to report the unique identification value to the server through the network.
7. The system for analyzing abnormal problems of mobile terminals according to claim 5, wherein in the corresponding relationship between the preset log content and the abnormal problem types, the abnormal problem types are divided according to the hardware and/or software to which the abnormal problem types belong, wherein at least one of the hardware or software is divided into a plurality of abnormal problem types.
8. The system for analyzing abnormal problems of mobile terminals according to claim 5, wherein the extracting logs generated when abnormal problems occur in the mobile terminal refers to extracting logs generated when the mobile terminal crashes or is abnormally restarted; the obtaining of the comprehensive statistical result of the mobile terminal about the abnormal problem type is specifically to obtain a comprehensive statistical result of a crash or an abnormal restart type.
9. A terminal device, comprising a processor, a memory and a computer program stored in the memory and operable on the processor, wherein the processor is configured to execute the computer program stored in the memory to implement the operations performed by the method for analyzing abnormal problems of a mobile terminal according to any one of claims 1 to 4.
10. A storage medium having stored therein at least one instruction, which is loaded and executed by a processor to implement the operations performed by the mobile terminal abnormal problem analysis method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010447214.9A CN111625384B (en) | 2020-05-25 | 2020-05-25 | Mobile terminal abnormal problem analysis method, system, terminal equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010447214.9A CN111625384B (en) | 2020-05-25 | 2020-05-25 | Mobile terminal abnormal problem analysis method, system, terminal equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111625384A true CN111625384A (en) | 2020-09-04 |
| CN111625384B CN111625384B (en) | 2024-05-14 |
Family
ID=72259076
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010447214.9A Active CN111625384B (en) | 2020-05-25 | 2020-05-25 | Mobile terminal abnormal problem analysis method, system, terminal equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111625384B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112346897A (en) * | 2020-10-23 | 2021-02-09 | 浪潮电子信息产业股份有限公司 | Method and system for processing computer fault |
| CN112860516A (en) * | 2021-02-04 | 2021-05-28 | 展讯通信（上海）有限公司 | Log saving method, communication device, chip and module equipment |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150113334A1 (en) * | 2013-10-18 | 2015-04-23 | Ashok Raj | Determine when an error log was created |
| KR101753846B1 (en) * | 2015-12-28 | 2017-07-19 | 주식회사 시큐아이 | Method, system and computer-readable recording medium for generating customized log type |
| CN109189612A (en) * | 2018-09-04 | 2019-01-11 | 广东小天才科技有限公司 | Log processing method and electronic device during Linux kernel exception |
| CN109284269A (en) * | 2018-10-17 | 2019-01-29 | Oppo广东移动通信有限公司 | Abnormal log analysis method, device, storage medium and server |
| CN109474483A (en) * | 2019-01-08 | 2019-03-15 | Oppo广东移动通信有限公司 | A kind of detection method, detection device and the terminal device of unit exception situation |
| CN109558261A (en) * | 2018-11-20 | 2019-04-02 | 广东小天才科技有限公司 | Method and system for acquiring abnormal log of wearable device |
| CN110825611A (en) * | 2018-08-14 | 2020-02-21 | 深圳兆日科技股份有限公司 | Abnormal program analysis method and device and computer readable storage medium |
-
2020
- 2020-05-25 CN CN202010447214.9A patent/CN111625384B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150113334A1 (en) * | 2013-10-18 | 2015-04-23 | Ashok Raj | Determine when an error log was created |
| KR101753846B1 (en) * | 2015-12-28 | 2017-07-19 | 주식회사 시큐아이 | Method, system and computer-readable recording medium for generating customized log type |
| CN110825611A (en) * | 2018-08-14 | 2020-02-21 | 深圳兆日科技股份有限公司 | Abnormal program analysis method and device and computer readable storage medium |
| CN109189612A (en) * | 2018-09-04 | 2019-01-11 | 广东小天才科技有限公司 | Log processing method and electronic device during Linux kernel exception |
| CN109284269A (en) * | 2018-10-17 | 2019-01-29 | Oppo广东移动通信有限公司 | Abnormal log analysis method, device, storage medium and server |
| CN109558261A (en) * | 2018-11-20 | 2019-04-02 | 广东小天才科技有限公司 | Method and system for acquiring abnormal log of wearable device |
| CN109474483A (en) * | 2019-01-08 | 2019-03-15 | Oppo广东移动通信有限公司 | A kind of detection method, detection device and the terminal device of unit exception situation |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112346897A (en) * | 2020-10-23 | 2021-02-09 | 浪潮电子信息产业股份有限公司 | Method and system for processing computer fault |
| CN112346897B (en) * | 2020-10-23 | 2022-07-22 | 浪潮电子信息产业股份有限公司 | Method and system for processing computer fault |
| CN112860516A (en) * | 2021-02-04 | 2021-05-28 | 展讯通信（上海）有限公司 | Log saving method, communication device, chip and module equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111625384B (en) | 2024-05-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110909063B (en) | User behavior analysis method and device, application server and storage medium | |
| CN109271411B (en) | Report generation method, report generation device, computer equipment and storage medium | |
| CN107392655B (en) | Coupon pushing method, coupon pushing system, storage medium, electronic equipment and distribution method | |
| CN111597257A (en) | Database synchronization method and device, storage medium and terminal | |
| CN110889134A (en) | Data desensitization method and device and electronic equipment | |
| CN111061922A (en) | Data visualization processing method, system, terminal equipment and storage medium | |
| CN113704243A (en) | Data analysis method, data analysis device, computer device, and storage medium | |
| CN110830437A (en) | Data compression method, device, equipment and storage medium for high-frequency service data | |
| CN111625384B (en) | Mobile terminal abnormal problem analysis method, system, terminal equipment and storage medium | |
| CN111241051A (en) | Batch data processing method and device, terminal equipment and storage medium | |
| US12106171B2 (en) | Method and apparatus for improving reading and writing speed of contactless card and terminal device | |
| CN109471893B (en) | Network data query method, equipment and computer readable storage medium | |
| CN109766271B (en) | Hybrid application automatic testing method and device, electronic equipment and storage medium | |
| CN106162576B (en) | Mobile terminal network flow display method and device | |
| CN112434238A (en) | Webpage quality detection method and device, electronic equipment and storage medium | |
| CN113010116A (en) | Data processing method and device, terminal equipment and readable storage medium | |
| CN112784112A (en) | Message checking method and device | |
| CN115357625A (en) | Structured data comparison method and device, electronic equipment and storage medium | |
| CN108521460B (en) | Information pushing method and device, mobile terminal and computer readable storage medium | |
| CN113709553B (en) | Screen recording method and device, chip and terminal | |
| CN110704404A (en) | Data quality checking method, device and system | |
| CN107391361B (en) | Automatic POS terminal testing method and device | |
| KR20130126012A (en) | Method and apparatusfor providing report of business intelligence | |
| CN111222739B (en) | Nuclear power station task allocation method and nuclear power station task allocation system | |
| CN111061518B (en) | Data processing method, system, terminal equipment and storage medium based on drive node |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |