CN107704363B - Screen freezing monitoring method, mobile terminal and computer readable storage medium - Google Patents
Screen freezing monitoring method, mobile terminal and computer readable storage medium Download PDFInfo
- Publication number
- CN107704363B CN107704363B CN201710916337.0A CN201710916337A CN107704363B CN 107704363 B CN107704363 B CN 107704363B CN 201710916337 A CN201710916337 A CN 201710916337A CN 107704363 B CN107704363 B CN 107704363B
- Authority
- CN
- China
- Prior art keywords
- preset
- current process
- thread
- created
- threads
- 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.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
Landscapes
- Engineering & Computer Science (AREA)
- Computing Systems (AREA)
- Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Mathematical Physics (AREA)
- Quality & Reliability (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Telephone Function (AREA)
Abstract
The invention discloses a frozen screen monitoring method, a mobile terminal and a computer readable storage medium, wherein the frozen screen monitoring method comprises the following steps: when the inter-process data communication is monitored, acquiring basic process information of a current process for carrying out the inter-process data communication; judging whether the current process has a creation condition of a preset thread according to the basic process information; when the current process does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are in a blocking state or not; and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file. According to the invention, when the mobile terminal has a frozen screen, a maintenance worker can read the characteristic log file, so that the reason for the frozen screen is quickly positioned, and the labor cost and the time cost are greatly reduced.
Description
Technical Field
The invention relates to the technical field of mobile terminals, in particular to a frozen screen monitoring method, a mobile terminal and a computer readable storage medium.
Background
With the development of mobile terminal technology, the hardware configuration of the mobile terminal is better and better, the functions that can be realized are more and more, and integrated APPs (applications) are more and more. At present, application programs based on different scenes of a mobile terminal are thousands of, and with the increasing quantity of third-party applications and service software installed on the mobile terminal by a user, people always encounter the problem of picture freezing when using the mobile terminal daily.
When the screen appears freezing in mobile terminal, the user restarts mobile terminal under general conditions to make it resume normal, and freezes the screen at every turn and all needs the user manual restart, and user experience is not good, and simultaneously, also can not make it resume normal through restarting mobile terminal, need return the manufacturer maintenance with mobile terminal, when the maintenance, need spend more time and manpower location appear freezing the reason of screen, and cost of maintenance is higher. Therefore, how to quickly locate and query the freeze screen reason and reduce the time cost and the labor cost are problems to be solved urgently at present.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a frozen screen monitoring method, a mobile terminal and a computer readable storage medium, and aims to solve the technical problems of how to quickly locate and inquire the frozen screen reason and reduce the time cost and the labor cost.
In order to achieve the above object, the present invention provides a freeze-shielding monitoring method, comprising the steps of:
when the inter-process data communication is monitored, acquiring basic process information of a current process for carrying out the inter-process data communication;
judging whether the current process has a creation condition of a preset thread according to the basic process information;
when the current process does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are in a blocking state or not;
and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
Optionally, the step of determining whether the current process has a creation condition of a preset thread according to the basic process information includes:
extracting the created number and the maximum created number of the preset thread of the current process from the basic process information, and judging whether the created number is smaller than the maximum created number;
if the created number is smaller than the maximum created number, judging that the current process has a creation condition of a preset thread;
and if the created number is equal to the maximum created number, judging that the current process does not have the creating condition of the preset thread.
Optionally, the step of determining whether all created preset threads of the current process are in a blocking state includes:
judging whether the thread state value of each established preset thread of the current process is in a preset thread state value set or not;
if the thread state value of each created preset thread of the current process is in a preset thread state value set, judging that the created preset threads of the current process are in a blocking state;
and if the thread state value of each created preset thread of the current process is unevenly in a preset thread state value set, judging that the created preset thread of the current process is unevenly in a blocking state.
Optionally, the step of determining whether all created preset threads of the current process are in a blocking state further includes:
judging whether state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values;
if the state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values, judging that the established preset threads of the current process are all in a blocking state;
and if the state return value of each created preset thread of the current process, which is acquired based on the preset operation, is not uniform and is a preset state return value, judging that the created preset thread of the current process is not uniformly in a blocking state.
Optionally, after the step of determining whether all created preset threads of the current process are in a blocked state, the freeze-screen monitoring method further includes:
and deleting the preset process when the established preset threads of the current process are all in the blocking state.
Optionally, after the step of outputting the stack call information and the thread interaction information to a feature log file, the freeze-screen monitoring method further includes:
when a characteristic log file export request is monitored, acquiring a characteristic log file from a preset storage area;
exporting the characteristic log file to the terminal equipment in the characteristic log file export request, so that the terminal equipment can store the characteristic log file.
In addition, to achieve the above object, the present invention also provides a mobile terminal, including: a memory, a processor, and a freeze screen monitoring program stored on the memory and executable on the processor, the freeze screen monitoring program when executed by the processor implementing the steps of:
when the inter-process data communication is monitored, acquiring basic process information of a current process for carrying out the inter-process data communication;
judging whether the current process has a creation condition of a preset thread according to the basic process information;
when the current process does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are in a blocking state or not;
and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
The present invention also provides a computer-readable storage medium having a freeze screen monitoring program stored thereon, the freeze screen monitoring program when executed by a processor implementing the steps of:
when the inter-process data communication is monitored, acquiring basic process information of a current process for carrying out the inter-process data communication;
judging whether the current process has a creation condition of a preset thread according to the basic process information;
when the current process does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are in a blocking state or not;
and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
The invention provides a frozen screen monitoring method, a mobile terminal and a computer readable storage medium, when inter-process data communication is monitored, basic process information of a current process for the inter-process data communication is acquired, whether the current process has a creating condition of a preset thread is judged according to the basic process information, whether the created preset threads of the current process are in a blocking state is judged if the current process does not have the creating condition of the preset thread, stack calling information and thread interaction information of the current process are acquired if the created preset threads of the current process are in the blocking state, and the stack calling information and the thread interaction information are output to a characteristic log file, the scheme can perform blocking judgment on the preset thread in the current process for the inter-process data communication when the inter-process data communication is monitored, thereby confirm whether the mobile terminal appears freezing the screen to can freeze the screen information when the mobile terminal appears freezing the screen, the information is called to the storehouse promptly and this thread mutual information, exports to characteristic log file, be convenient for when the mobile terminal appears freezing the screen, maintenance personal can read characteristic log file, thereby freeze the screen reason in quick location, very big reduction human cost and time cost.
Drawings
Fig. 1 is a schematic diagram of a hardware structure of a mobile terminal implementing various embodiments of the present invention;
FIG. 2 is a level diagram of an operating system of the mobile terminal according to the present invention;
FIG. 3 is a schematic flow chart of a first embodiment of a freeze screen monitoring method according to the present invention;
FIG. 4 is a detailed flowchart of the step of determining whether the current process has a condition for creating a preset thread according to the basic process information in FIG. 3;
FIG. 5 is a schematic view of a detailed flow of the step of determining whether all the created preset threads of the current process are in a blocking state shown in FIG. 3;
fig. 6 is a flowchart illustrating a third embodiment of a freeze-screen monitoring method according to the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
In the following description, suffixes such as "module", "component", or "unit" used to denote elements are used only for facilitating the explanation of the present invention, and have no specific meaning in itself. Thus, "module", "component" or "unit" may be used mixedly.
The terminal may be implemented in various forms. For example, the terminal described in the present invention may include a mobile terminal such as a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a Personal Digital Assistant (PDA), a Portable Media Player (PMP), a navigation device, a wearable device, a smart band, a pedometer, and the like, and a fixed terminal such as a Digital TV, a desktop computer, and the like.
The following description will be given by way of example of a mobile terminal, and it will be understood by those skilled in the art that the construction according to the embodiment of the present invention can be applied to a fixed type terminal, in addition to elements particularly used for mobile purposes.
Referring to fig. 1, which is a schematic diagram of a hardware structure of a mobile terminal for implementing various embodiments of the present invention, the mobile terminal 100 may include: RF (Radio Frequency) unit 101, WiFi module 102, audio output unit 103, a/V (audio/video) input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, processor 110, and power supply 111. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 1 is not intended to be limiting of mobile terminals, which may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
The following describes each component of the mobile terminal in detail with reference to fig. 1:
the radio frequency unit 101 may be configured to receive and transmit signals during information transmission and reception or during a call, and specifically, receive downlink information of a base station and then process the downlink information to the processor 110; in addition, the uplink data is transmitted to the base station. Typically, radio frequency unit 101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 101 can also communicate with a network and other devices through wireless communication. The wireless communication may use any communication standard or protocol, including but not limited to GSM (Global System for Mobile communications), GPRS (General Packet Radio Service), CDMA2000(Code Division Multiple Access 2000), WCDMA (Wideband Code Division Multiple Access), TD-SCDMA (Time Division-Synchronous Code Division Multiple Access), FDD-LTE (Frequency Division duplex Long Term Evolution), and TDD-LTE (Time Division duplex Long Term Evolution).
WiFi belongs to short-distance wireless transmission technology, and the mobile terminal can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 102, and provides wireless broadband internet access for the user. Although fig. 1 shows the WiFi module 102, it is understood that it does not belong to the essential constitution of the mobile terminal, and may be omitted entirely as needed within the scope not changing the essence of the invention.
The audio output unit 103 may convert audio data received by the radio frequency unit 101 or the WiFi module 102 or stored in the memory 109 into an audio signal and output as sound when the mobile terminal 100 is in a call signal reception mode, a call mode, a recording mode, a voice recognition mode, a broadcast reception mode, or the like. Also, the audio output unit 103 may also provide audio output related to a specific function performed by the mobile terminal 100 (e.g., a call signal reception sound, a message reception sound, etc.). The audio output unit 103 may include a speaker, a buzzer, and the like.
The a/V input unit 104 is used to receive audio or video signals. The a/V input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, the Graphics processor 1041 Processing image data of still pictures or video obtained by an image capturing device (e.g., a camera) in a video capturing mode or an image capturing mode. The processed image frames may be displayed on the display unit 106. The image frames processed by the graphic processor 1041 may be stored in the memory 109 (or other storage medium) or transmitted via the radio frequency unit 101 or the WiFi module 102. The microphone 1042 may receive sounds (audio data) via the microphone 1042 in a phone call mode, a recording mode, a voice recognition mode, or the like, and may be capable of processing such sounds into audio data. The processed audio (voice) data may be converted into a format output transmittable to a mobile communication base station via the radio frequency unit 101 in case of a phone call mode. The microphone 1042 may implement various types of noise cancellation (or suppression) algorithms to cancel (or suppress) noise or interference generated in the course of receiving and transmitting audio signals.
The mobile terminal 100 also includes at least one sensor 105, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor that can adjust the brightness of the display panel 1061 according to the brightness of ambient light, and a proximity sensor that can turn off the display panel 1061 and/or a backlight when the mobile terminal 100 is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), can detect the magnitude and direction of gravity when stationary, and can be used for applications of recognizing the posture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer and tapping), and the like; as for other sensors such as a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile phone, further description is omitted here.
The display unit 106 is used to display information input by a user or information provided to the user. The Display unit 106 may include a Display panel 1061, and the Display panel 1061 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like.
The user input unit 107 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the mobile terminal. Specifically, the user input unit 107 may include a touch panel 1071 and other input devices 1072. The touch panel 1071, also referred to as a touch screen, may collect a touch operation performed by a user on or near the touch panel 1071 (e.g., an operation performed by the user on or near the touch panel 1071 using a finger, a stylus, or any other suitable object or accessory), and drive a corresponding connection device according to a predetermined program. The touch panel 1071 may include two parts of a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 110, and can receive and execute commands sent by the processor 110. In addition, the touch panel 1071 may be implemented in various types, such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. In addition to the touch panel 1071, the user input unit 107 may include other input devices 1072. In particular, other input devices 1072 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like, and are not limited to these specific examples.
Further, the touch panel 1071 may cover the display panel 1061, and when the touch panel 1071 detects a touch operation thereon or nearby, the touch panel 1071 transmits the touch operation to the processor 110 to determine the type of the touch event, and then the processor 110 provides a corresponding visual output on the display panel 1061 according to the type of the touch event. Although the touch panel 1071 and the display panel 1061 are shown in fig. 1 as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 1071 and the display panel 1061 may be integrated to implement the input and output functions of the mobile terminal, and is not limited herein.
The interface unit 108 serves as an interface through which at least one external device is connected to the mobile terminal 100. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device having an identification module, an audio input/output (I/O) port, a video I/O port, an earphone port, and the like. The interface unit 108 may be used to receive input (e.g., data information, power, etc.) from external devices and transmit the received input to one or more elements within the mobile terminal 100 or may be used to transmit data between the mobile terminal 100 and external devices.
The memory 109 may be used to store software programs as well as various data. The memory 109 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. Further, the memory 109 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
Referring to fig. 2, which is a schematic hierarchical diagram of an operating system stored in a storage program area, as shown in fig. 2, the operating system includes a Loader layer, a Kernel layer, a Native layer, a Framework layer (including a C + + Framework layer and a Java Framework layer), and an App layer, where an HAL layer (hardware abstraction layer) also exists between the Kernel layer and the Native layer, a JNI layer also exists between the C + + Framework layer and the Java Framework layer, and a SysCall layer also exists between the HAL layer and the Kernel layer.
The Loader layer comprises a Boot ROM (Boot service) and a Boot Loader (Boot initialization program), wherein the Boot ROM is mainly used for booting by pressing a Power (Boot) key for a long time when the mobile terminal is in a Power-off state, and a Boot chip starts to execute from a preset code solidified in the ROM. The Boot Loader is a Boot program before starting the operating system, and mainly has the functions of checking the RAM, initializing hardware parameters and the like.
The Kernel layer is mainly used for performing related work such as initialization process management, memory management, Display loading, Camera Driver (Camera Driver), Binder Driver (Binder Driver) and the like, and is used for creating Kernel daemon processes such as Kernel worker threads kworkder, soft interrupt threads ksofirqd and soft interrupt threads thermal.
The Native layer mainly comprises a daemon process of a user space hatched by init, a HAL layer, startup animation and the like. User daemon processes, User Daemons, such as ueven, logd, health, installd, adbd, and lmkd, can hatch out from the Init process (a User-level process started by a kernel); the init process also starts important services such as servicemanager and bootanim; the init process hatches a Zygote process, the Zygote process is the first Java process of the operating system, the Zygote process is the parent process of all the Java processes, and the Zygote process is hatched from the init process.
The Framework layer comprises a Zygote process, a System Server (System service) process and a Media Server (multimedia service) process, wherein the Zygote process is generated by an init process through analysis of an init.rc file and then fork, and mainly comprises loading Zygote init classes, registering Zygote Socket service end sockets, loading virtual machines, preloadClasses, preloadResouces and the like; the System Server process is derived from a Zygote process fork, the System Server is the first process of Zygote incubation, and the System Server is responsible for starting and managing the whole Java Framework and comprises services such as an ActivitiManager (application program component), a PowerManager (power supply management component) and a WindowManagerServer (window management component); the Media Server process, which is derived from the init process fork, is responsible for starting and managing the whole C + + frame, and includes services such as audio pointer (afofinger), Camera Service (Camera Service), and MediaPlayServer (multimedia Service).
The APP layer comprises APP processes, each APP process is generated by a Zygote process fork, the first APP process hatched by the Zygote process is a Launcher (desktop Launcher), desktop APPs seen by a user are created by the Zygote process, the App processes such as a Browser, a Phone and an Email are also created by the Zygote process, and each App runs on at least one process.
The processor 110 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by operating or executing software programs and/or modules stored in the memory 109 and calling data stored in the memory 109, thereby performing overall monitoring of the mobile terminal. Processor 110 may include one or more processing units; preferably, the processor 110 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 110.
The mobile terminal 100 may further include a power supply 111 (e.g., a battery) for supplying power to various components, and preferably, the power supply 111 may be logically connected to the processor 110 via a power management system, so as to manage charging, discharging, and power consumption management functions via the power management system.
Although not shown in fig. 1, the mobile terminal 100 may further include a bluetooth module or the like, which is not described in detail herein.
Based on the above mobile terminal hardware structure, various embodiments of the mobile terminal of the present invention are provided.
Referring to fig. 1, in a first embodiment of the mobile terminal of the present invention, the mobile terminal includes: a memory, a processor, and a freeze screen monitoring program stored on the memory and executable on the processor, the freeze screen monitoring program when executed by the processor implementing the steps of:
when the inter-process data communication is monitored, acquiring basic process information of a current process for carrying out the inter-process data communication;
judging whether the current process has a creation condition of a preset thread according to the basic process information;
when the current process does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are in a blocking state or not;
and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
extracting the created number and the maximum created number of the preset thread of the current process from the basic process information, and judging whether the created number is smaller than the maximum created number;
if the created number is smaller than the maximum created number, judging that the current process has a creation condition of a preset thread;
and if the created number is equal to the maximum created number, judging that the current process does not have the creating condition of the preset thread.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
judging whether the thread state value of each established preset thread of the current process is in a preset thread state value set or not;
if the thread state value of each created preset thread of the current process is in a preset thread state value set, judging that the created preset threads of the current process are in a blocking state;
and if the thread state value of each created preset thread of the current process is unevenly in a preset thread state value set, judging that the created preset thread of the current process is unevenly in a blocking state.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
judging whether state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values;
if the state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values, judging that the established preset threads of the current process are all in a blocking state;
and if the state return value of each created preset thread of the current process, which is acquired based on the preset operation, is not uniform and is a preset state return value, judging that the created preset thread of the current process is not uniformly in a blocking state.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
and deleting the preset process when the established preset threads of the current process are all in the blocking state.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
when a characteristic log file export request is monitored, acquiring a characteristic log file from a preset storage area;
exporting the characteristic log file to the terminal equipment in the characteristic log file export request, so that the terminal equipment can store the characteristic log file.
The specific embodiment of the mobile terminal of the present invention is substantially the same as the specific embodiments of the freeze screen monitoring method described below, and will not be described herein again.
Further, the present invention also provides a freeze-screen monitoring method applied to the mobile terminal shown in fig. 1, referring to fig. 3, and fig. 3 is a flowchart illustrating a first embodiment of the freeze-screen monitoring method according to the present invention.
In this embodiment, the freeze screen monitoring method includes:
step S101, when monitoring the data communication between the processes, obtaining the basic process information of the current process for carrying out the data communication between the processes;
the frozen screen monitoring method is applied to the mobile terminal shown in fig. 1, and the mobile terminal comprises a smart phone, a tablet computer and the like. Known by an operating system of the mobile terminal, data communication between different processes needs to be realized through a Binder driver of an operating system kernel space, the operating system is an Android system, and the Android system specifies that a SystemServer process can create 16 Binder threads at most for data communication between the processes; the SurfaceFlinger process can create 4 Binder threads at most for interprocess data communication; the program application process can create up to 8 Binder threads for interprocess data communication. And loading a Binder drive when the Binder thread is established and initialized, and then allocating a virtual address space to the Binder thread for receiving a transaction by adopting a memory mapping function. And each SystemServer process, the SurfaceFlinger process and the program application process only allow one Binder main thread to be created, and Binder sub-threads in the rest Binder thread pools are controlled and created by a Binder driver. Because the number of the Binder threads which can be created by the SystemServer process, the SurfaceFlinger process and the program application process is limited, when the creatable Binder threads are all in a blocking state, the inter-process data communication cannot be carried out, so that the program application of the APP layer cannot carry out the data communication with the system core process, and the mobile terminal is frozen.
Specifically, the mobile terminal receives a display request triggered by a user based on an installed program application, transmits the display request to a system core process, and performs inter-process data communication, and when monitoring the inter-process data communication, the mobile terminal acquires basic process information of a current process performing the inter-process data communication, where the basic process information includes a process name, a process identifier, a number of Binder threads allowed to be created at most, a number of Binder threads created already, and the like. For example, if the current process is a SystemServer process, the corresponding base progress information includes the name and identifier of the SystemServer process, the number of Binder threads allowed to be created at most is 16, the number of created Binder threads is 8, and the like, and if the current process is a surfefinger process, the corresponding base progress information includes the name and identifier of the surfefinger process, the number of Binder threads allowed to be created at most is 4, the number of created Binder threads is 2, and the like.
Step S102, judging whether the current process has the creating condition of a preset thread according to the basic process information;
after acquiring the basic process information of the current process for performing the inter-process data communication, the mobile terminal judges whether the current process has the creation condition of the preset thread according to the basic process information, namely judges whether the current process can also create a Binder thread.
Specifically, referring to fig. 4, fig. 4 is a detailed flowchart of the step S102 in fig. 3, where the step S102 includes:
step S1021, extracting the created number and the maximum created number of the preset thread of the current process from the basic process information, and judging whether the created number is smaller than the maximum created number;
step S1022, if the created number is smaller than the maximum created number, it is determined that the current process has a creation condition of a preset thread;
in step S1023, if the created number is equal to the maximum created number, it is determined that the current process does not have a creation condition of a preset thread.
After acquiring basic process information of a current process for carrying out data communication among the processes, the mobile terminal extracts the created number and the maximum created number of preset threads of the current process from the basic process information, judges whether the created number is smaller than the maximum created number, namely extracts the created number of Binder threads of the current process and the maximum created number of Binder threads from the basic process information, judges whether the created number of Binder threads is smaller than the maximum created number of Binder threads, if the created number of Binder threads is smaller than the maximum created number of Binder threads, the current process can create the Binder threads, judges that the current process has the creating conditions of the preset threads, namely the current process has the creating conditions of the Binder threads, if the created number of Binder threads is equal to the maximum created number of Binder threads, the current process cannot create the Binder threads, and judges that the current process has no creating conditions of the preset threads, i.e. the current process does not have the creation condition of the Binder thread.
Step S103, when the current process does not have the creating condition of the preset thread, judging whether the created preset threads of the current process are all in a blocking state;
when the current process does not have the creating condition of the preset thread, namely the creating condition of the Binder thread, the mobile terminal judges whether the created preset threads of the current process are all in the blocking state, namely judges whether the created Binder threads of the current process are all in the blocking state.
Specifically, referring to fig. 5, fig. 5 is a detailed flowchart of the step S103 in fig. 3, where the step S103 includes:
step S1031, determining whether the thread state value of each created preset thread of the current process is in a preset thread state value set;
step S1032, if the thread state value of each created preset thread of the current process is in a preset thread state value set, determining that the created preset threads of the current process are in a blocking state;
step S1033, if the uneven thread state value of each created preset thread of the current process is in the preset thread state value set, determining that the uneven created preset thread of the current process is in the blocking state.
The method comprises the steps that when a current process does not have a creating condition of a preset thread, namely the creating condition of a Binder thread, a thread state value of each created preset thread of the current process is obtained, whether the thread state value of each created preset thread is in a preset thread state value set or not is judged, if the thread state value of each created preset thread of the current process is in the preset thread state value set, the created preset threads of the current process can be judged to be in a blocking state, if the thread state value of each created preset thread of the current process is not uniform and is in the preset thread state value set, the created preset threads of the current process can be judged to be in the blocking state unevenly, and when the created preset threads of the current process are in the blocking state, screen freezing of the mobile terminal is shown. The thread state values include Blocked, Active, and Waiting Timeout, and the preset thread state value set includes Blocked, Waiting Timeout, and the like, that is, when the thread state values of each created preset thread of the current process are both Blocked or Waiting Timeout, it may be determined that all the created preset threads are in a blocking state. It should be noted that the preset thread state value set and the thread state value may be set by those skilled in the art according to practical situations, and the embodiment does not specifically limit this.
And step S104, when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
The mobile terminal acquires stack calling information and thread interaction information of a current process when all established preset threads of the current process are in a blocking state, and outputs the stack calling information and the thread interaction information to a feature log file. The stack call information is the stack call relation of the process, the thread and the process interacting with the process to perform data communication, and the thread interaction information comprises information of the blocked Binder thread and the specific Binder thread of which process has data transmission, whether synchronization is completed, whether blocking is suspended, the size of transmission data, the type of transmission data and the like.
In this embodiment, when the inter-process data communication is monitored, the present invention obtains basic process information of a current process performing the inter-process data communication, and determines whether the current process has a creation condition of a preset thread according to the basic process information, determines whether all the created preset threads of the current process are in a blocking state if the current process does not have the creation condition of the preset thread, and obtains stack calling information and thread interaction information of the current process and outputs the stack calling information and the thread interaction information to a feature log file if all the created preset threads of the current process are in the blocking state, and when the inter-process data communication is monitored, the present invention can perform blocking determination on the preset threads in the current process performing the inter-process data communication, thereby determining whether the mobile terminal has a frozen screen, and when the mobile terminal has a frozen screen, the information of the frozen screen, namely the stack calling information and the thread interaction information, is output to the characteristic log file, so that when the frozen screen appears on the mobile terminal, maintenance personnel can read the characteristic log file, the reason for the frozen screen is rapidly positioned, and the labor cost and the time cost are greatly reduced.
Further, a second embodiment of the freeze screen monitoring method according to the present invention is proposed based on the mobile terminal shown in fig. 1 and the first embodiment, and is different from the foregoing embodiment in that the step S103 further includes:
judging whether state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values;
if the state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values, judging that the established preset threads of the current process are all in a blocking state;
and if the state return value of each created preset thread of the current process, which is acquired based on the preset operation, is not uniform and is a preset state return value, judging that the created preset thread of the current process is not uniformly in a blocking state.
It should be noted that, based on the foregoing embodiments, the present invention provides a specific way to determine whether a preset thread is in a blocking state.
When the current process does not have the condition of creating the preset thread, the mobile terminal judges whether the state return values acquired by each created preset thread of the current process based on the preset operation are all preset state return values, specifically, pings each created preset thread of the current process (Packet Internet Groper, Internet Packet searchers) to acquire the ping operation return value of each created preset thread of the current process and judge whether the ping operation return value of each created preset thread of the current process is the preset ping operation return value, if the ping operation return value of each created preset thread of the current process is all the preset ping operation return values, namely the state return values acquired by each created preset thread of the current process based on the preset operation are all the preset state return values, the created preset threads of the current process can be judged to be in the blocking state, if the ping operation return value of each created preset thread of the current process is not uniform to be the preset ping operation return value, that is, the state return value of each created preset thread of the current process, which is obtained based on the preset operation, is not uniform to be the preset state return value, it can be determined that the created preset thread of the current process is not uniformly in the blocking state. The ping operation return value, that is, the state return value, corresponds to the state of the created preset thread one by one, and the current state of the created preset thread can be determined according to the ping operation return value, that is, the state return value, and the states of the created preset thread include a busy state, an idle state, a suspended state, a blocked state, a timeout waiting state, and the like. The preset thread is a Binder thread.
In this embodiment, by performing ping operation on the created preset thread, the present invention can determine whether the current state of the created preset thread is in the blocking state based on the ping operation return value, and effectively improve the monitoring accuracy of the current state of the created preset thread.
Further, referring to fig. 6, based on the mobile terminal shown in fig. 1 and the first or second embodiment, a third embodiment of the freeze screen monitoring method of the present invention is provided, which is different from the previous embodiment in that after step S103, the freeze screen monitoring method further includes:
and step S105, deleting the preset process when the established preset threads of the current process are all in a blocking state.
It should be noted that the present invention provides a specific way to solve the freeze-shielding problem based on the foregoing embodiments, and only this will be described below, and other embodiments can be referred to.
When the current process does not have the creating condition of the preset thread and the created preset threads of the current process are all in the blocking state, the mobile terminal deletes the preset process, namely deletes the SystemServer process, so that the operating system is restarted.
In this embodiment, the method and the device can delete the systemServer process when the current process does not have the creating condition of the preset thread and the created preset threads of the current process are all in a blocking state, namely, the mobile terminal is frozen, so that the problem of frozen screen is solved, the mobile terminal does not need to be returned to a manufacturer for maintenance, and the maintenance time and the labor cost are saved.
Further, based on the mobile terminal shown in fig. 1 and the first, second or third embodiments, a fourth embodiment of the freeze screen monitoring method of the present invention is proposed, which is different from the foregoing embodiments in that after the step S104, the freeze screen monitoring method further includes:
when a characteristic log file export request is monitored, acquiring a characteristic log file from a preset storage area;
exporting the characteristic log file to the terminal equipment in the characteristic log file export request, so that the terminal equipment can store the characteristic log file.
It should be noted that the present invention proposes a specific export method of the feature log file based on the foregoing embodiment, and only this will be described below, and other embodiments can be referred to.
When monitoring a characteristic log file export request, the mobile terminal acquires the characteristic log file from a preset storage area and exports the characteristic log file to the terminal equipment in the characteristic log file export request.
In this embodiment, the present invention can export the feature log file to other terminal devices for storage when the storage space of the mobile terminal is insufficient.
In addition, an embodiment of the present invention further provides a computer-readable storage medium, where a freeze-screen monitoring program is stored on the computer-readable storage medium, and when executed by a processor, the freeze-screen monitoring program implements the following steps:
when the inter-process data communication is monitored, acquiring basic process information of a current process for carrying out the inter-process data communication;
judging whether the current process has a creation condition of a preset thread according to the basic process information;
when the current process does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are in a blocking state or not;
and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
extracting the created number and the maximum created number of the preset thread of the current process from the basic process information, and judging whether the created number is smaller than the maximum created number;
if the created number is smaller than the maximum created number, judging that the current process has a creation condition of a preset thread;
and if the created number is equal to the maximum created number, judging that the current process does not have the creating condition of the preset thread.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
judging whether the thread state value of each established preset thread of the current process is in a preset thread state value set or not;
if the thread state value of each created preset thread of the current process is in a preset thread state value set, judging that the created preset threads of the current process are in a blocking state;
and if the thread state value of each created preset thread of the current process is unevenly in a preset thread state value set, judging that the created preset thread of the current process is unevenly in a blocking state.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
judging whether state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values;
if the state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values, judging that the established preset threads of the current process are all in a blocking state;
and if the state return value of each created preset thread of the current process, which is acquired based on the preset operation, is not uniform and is a preset state return value, judging that the created preset thread of the current process is not uniformly in a blocking state.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
and deleting the preset process when the established preset threads of the current process are all in the blocking state.
Further, the freeze screen monitoring program when executed by the processor further implements the steps of:
when a characteristic log file export request is monitored, acquiring a characteristic log file from a preset storage area;
exporting the characteristic log file to the terminal equipment in the characteristic log file export request, so that the terminal equipment can store the characteristic log file.
The specific embodiment of the computer-readable storage medium of the present invention is substantially the same as the specific embodiments of the freeze screen monitoring method described above, and will not be described herein again.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. A screen freezing monitoring method is characterized by comprising the following steps:
when the inter-process data communication is monitored, acquiring basic process information of a current process for carrying out the inter-process data communication;
judging whether the current process has a creation condition of a preset thread according to the basic process information;
when the current process does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are in a blocking state or not, wherein the preset threads comprise Binder threads;
and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
2. The freeze screen monitoring method of claim 1, wherein the step of determining whether the current process has a creation condition of a preset thread according to the base process information comprises:
extracting the created number and the maximum created number of the preset thread of the current process from the basic process information, and judging whether the created number is smaller than the maximum created number;
if the created number is smaller than the maximum created number, judging that the current process has a creation condition of a preset thread;
and if the created number is equal to the maximum created number, judging that the current process does not have the creating condition of the preset thread.
3. The freeze screen monitoring method of claim 1, wherein the step of determining whether all of the created preset threads of the current process are in a blocked state comprises:
judging whether the thread state value of each established preset thread of the current process is in a preset thread state value set or not;
if the thread state value of each created preset thread of the current process is in a preset thread state value set, judging that the created preset threads of the current process are in a blocking state;
and if the thread state value of each created preset thread of the current process is unevenly in a preset thread state value set, judging that the created preset thread of the current process is unevenly in a blocking state.
4. The freeze screen monitoring method of claim 1, wherein the step of determining whether all of the created preset threads of the current process are in a blocked state further comprises:
judging whether state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values;
if the state return values obtained by each established preset thread of the current process based on preset operation are all preset state return values, judging that the established preset threads of the current process are all in a blocking state;
and if the state return value of each created preset thread of the current process, which is acquired based on the preset operation, is not uniform and is a preset state return value, judging that the created preset thread of the current process is not uniformly in a blocking state.
5. The freeze screen monitoring method of claim 1, wherein after the step of determining whether all of the created preset threads of the current process are in a blocked state, the freeze screen monitoring method further comprises:
and deleting the preset process when the established preset threads of the current process are all in the blocking state.
6. The freeze screen monitoring method of any of claims 1-5, wherein after the step of outputting the stack call information and the thread interaction information to a feature log file, the freeze screen monitoring method further comprises:
when a characteristic log file export request is monitored, acquiring a characteristic log file from a preset storage area;
exporting the characteristic log file to the terminal equipment in the characteristic log file export request, so that the terminal equipment can store the characteristic log file.
7. A mobile terminal, characterized in that the mobile terminal comprises: a memory, a processor, and a freeze screen monitoring program stored on the memory and executable on the processor, the freeze screen monitoring program when executed by the processor implementing the steps of:
when the inter-process data communication is monitored, acquiring basic process information of a current process for carrying out the inter-process data communication;
judging whether the current process has a creation condition of a preset thread according to the basic process information;
when the current process does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are in a blocking state or not, wherein the preset threads comprise Binder threads;
and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
8. The mobile terminal of claim 7, wherein the freeze monitor program, when executed by the processor, further performs the steps of:
extracting the created number and the maximum created number of the preset thread of the current process from the basic process information, and judging whether the created number is smaller than the maximum created number;
if the created number is smaller than the maximum created number, judging that the current process has a creation condition of a preset thread;
and if the created number is equal to the maximum created number, judging that the current process does not have the creating condition of the preset thread.
9. The mobile terminal of claim 7, wherein the freeze monitor program, when executed by the processor, further performs the steps of:
judging whether the thread state value of each established preset thread of the current process is in a preset thread state value set or not;
if the thread state value of each created preset thread of the current process is in a preset thread state value set, judging that the created preset threads of the current process are in a blocking state;
and if the thread state value of each created preset thread of the current process is unevenly in a preset thread state value set, judging that the created preset thread of the current process is unevenly in a blocking state.
10. A computer-readable storage medium having a freeze screen monitoring program stored thereon, the freeze screen monitoring program when executed by a processor implementing the steps of:
when the inter-process data communication is monitored, acquiring basic process information of a current process for carrying out the inter-process data communication;
judging whether the current process has a creation condition of a preset thread according to the basic process information;
when the current process does not have the creating condition of the preset threads, judging whether the created preset threads of the current process are in a blocking state or not, wherein the preset threads comprise Binder threads;
and when the created preset threads of the current process are all in a blocking state, acquiring stack calling information and thread interaction information of the current process, and outputting the stack calling information and the thread interaction information to a feature log file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710916337.0A CN107704363B (en) | 2017-09-28 | 2017-09-28 | Screen freezing monitoring method, mobile terminal and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710916337.0A CN107704363B (en) | 2017-09-28 | 2017-09-28 | Screen freezing monitoring method, mobile terminal and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107704363A CN107704363A (en) | 2018-02-16 |
| CN107704363B true CN107704363B (en) | 2021-07-23 |
Family
ID=61183935
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710916337.0A Active CN107704363B (en) | 2017-09-28 | 2017-09-28 | Screen freezing monitoring method, mobile terminal and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107704363B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111061410B (en) * | 2018-10-16 | 2021-08-13 | 华为技术有限公司 | Screen freezing processing method and terminal |
| CN112673354B (en) * | 2018-10-26 | 2024-04-19 | 深圳市欢太科技有限公司 | System state detection method, system state device and terminal equipment |
| CN111966472B (en) * | 2020-07-02 | 2023-09-26 | 佛山科学技术学院 | Process scheduling method and system of industrial real-time operating system |
| CN112416584B (en) * | 2020-11-18 | 2023-12-19 | 捷开通讯(深圳)有限公司 | Process communication method and device, storage medium and mobile terminal |
| CN112860363A (en) * | 2021-02-07 | 2021-05-28 | 麒麟软件有限公司 | Linux system based Android application window state dynamic updating method |
| CN116701320B (en) * | 2022-12-01 | 2024-05-14 | 荣耀终端有限公司 | Log generation method and related device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101599027A (en) * | 2009-06-30 | 2009-12-09 | 中兴通讯股份有限公司 | A kind of thread pool management method and system thereof |
| US9104860B2 (en) * | 2012-05-29 | 2015-08-11 | Appsense Limited | Systems, methods and media for managing process image hijacks |
| CN107153583A (en) * | 2017-05-24 | 2017-09-12 | 努比亚技术有限公司 | A kind of striding course interaction processing method, mobile terminal and computer-readable recording medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7676675B2 (en) * | 2003-06-06 | 2010-03-09 | Microsoft Corporation | Architecture for connecting a remote client to a local client desktop |
-
2017
- 2017-09-28 CN CN201710916337.0A patent/CN107704363B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101599027A (en) * | 2009-06-30 | 2009-12-09 | 中兴通讯股份有限公司 | A kind of thread pool management method and system thereof |
| US9104860B2 (en) * | 2012-05-29 | 2015-08-11 | Appsense Limited | Systems, methods and media for managing process image hijacks |
| CN107153583A (en) * | 2017-05-24 | 2017-09-12 | 努比亚技术有限公司 | A kind of striding course interaction processing method, mobile terminal and computer-readable recording medium |
Non-Patent Citations (1)
| Title |
|---|
| 基于Android平台的移动终端设计与实现;舒俊;《中国优秀硕士学位论文全文数据库》;20140815;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107704363A (en) | 2018-02-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107590057B (en) | Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium | |
| CN107704363B (en) | Screen freezing monitoring method, mobile terminal and computer readable storage medium | |
| CN107861817B (en) | Thread blocking-based memory optimization method, mobile terminal and readable storage medium | |
| CN107678876B (en) | Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium | |
| CN107704133B (en) | Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium | |
| CN108052390B (en) | Thread blocking-based memory cleaning method, mobile terminal and readable storage medium | |
| CN107807861B (en) | Screen freezing solution method, mobile terminal and computer readable storage medium | |
| WO2018077041A1 (en) | Method and apparatus for running application | |
| CN107967177B (en) | Memory optimization method based on core process, mobile terminal and readable storage medium | |
| CN109471690B (en) | Message display method and terminal equipment | |
| CN108073458B (en) | Memory recovery method, mobile terminal and computer-readable storage medium | |
| CN109284144B (en) | Fast application processing method and mobile terminal | |
| CN107908491B (en) | Card screen detection and solution method, mobile terminal and computer readable storage medium | |
| CN107765922B (en) | Card screen detection and solution method, mobile terminal and computer readable storage medium | |
| CN107908492B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107766222B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107704332B (en) | Screen freezing solution method, mobile terminal and computer readable storage medium | |
| CN107861826B (en) | Screen freezing monitoring and solving method, mobile terminal and computer readable storage medium | |
| US11418945B2 (en) | Information processing method for RF device and mobile terminal | |
| CN107818036B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107832191B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107872367B (en) | Black screen detection method, mobile terminal and computer readable storage medium | |
| CN107908478B (en) | Memory cleaning method, mobile terminal and computer readable storage medium | |
| CN108089935B (en) | Application program management method and mobile terminal | |
| CN107943590B (en) | Memory optimization method based on associated starting application, mobile terminal 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |