CN110457154B - Abnormal service processing method and device, storage medium and communication terminal - Google Patents

Abstract

The present disclosure relates to the field of wireless communication technologies, and in particular, to an abnormal service processing method, an abnormal service processing apparatus, a computer readable medium, and a communication terminal. The method comprises the following steps: acquiring abnormal data, and inquiring a call stack according to the abnormal data; when the call stack comprises target method information corresponding to target service, acquiring a target service identifier corresponding to the target service according to the target method information; and acquiring the corresponding function point switch of the target service according to the target service identifier, and closing the function point switch of the target service. According to the technical scheme, when the target service is judged to be abnormal, the corresponding function point switch is inquired, and the switch is closed, so that the abnormal target service is forbidden to continue to operate, the abnormal recurrence is prevented, the normal operation of the system is prevented from being influenced, and the user experience is improved.

Description

Exception service processing method and device, storage medium, communication terminal

Technical field

The present disclosure relates to the field of wireless communication technology, and specifically relates to an exception service processing method, an exception service processing device, a computer-readable medium and a communication terminal.

Background technique

In order to improve the user experience of smart terminal devices and facilitate user operations, programmers can add new system functions based on the native system source code of the Android system. However, due to the large number of users and the complexity of the application environment, some functions may have problems such as instability. New functions may trigger stability problems under certain operating modes of the user. In severe cases, the system may crash repeatedly, or even Causes the system to reboot.

For such abnormal problems, the problem can only be solved through mobile phone OTA (Over the Air Technology, space download technology) upgrade, and the whole cycle is very long. Moreover, during the entire problem solving period, the same exception may be triggered again, affecting the user's use of the smart terminal device.

It should be noted that the information disclosed in the above background section is only used to enhance understanding of the background of the present disclosure, and therefore may include information that does not constitute prior art known to those of ordinary skill in the art.

Contents of the invention

The purpose of this disclosure is to provide an exception service processing method, an exception service processing device, a computer-readable medium, and a wireless communication terminal, thereby providing a processing method for system abnormal functions and reducing the impact of abnormalities on terminal equipment. influence during use, thereby overcoming the limitations and defects of related technologies to a certain extent.

Additional features and advantages of the disclosure will be apparent from the following detailed description, or, in part, may be learned by practice of the disclosure.

According to a first aspect of the present disclosure, an exception service processing method is provided, including:

Obtain exception data and query the call stack according to the exception data;

When the call stack includes target method information corresponding to the target service, obtain the target service identifier corresponding to the target service according to the target method information;

Obtain the corresponding function point switch of the target service according to the target service identifier, and turn off the function point switch of the target service.

According to a second aspect of the present disclosure, an exception service processing device is provided, including:

An abnormal data identification module is used to obtain abnormal data and query the call stack according to the abnormal data;

A target service identification module, configured to obtain the target service identifier corresponding to the target service according to the target method information when the call stack includes target method information corresponding to the target service;

A switch control module is configured to obtain the corresponding function point switch of the target service according to the target service identifier, and turn off the function point switch of the target service.

According to a third aspect of the present disclosure, a computer-readable medium is provided, a computer program is stored thereon, and when the computer program is executed by a processor, the above-mentioned exception service processing method is implemented.

According to a fourth aspect of the present disclosure, a wireless communication terminal is provided, including:

one or more processors;

A storage device is used to store one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the above-mentioned exception service processing method.

In the exception service processing method provided by an embodiment of the present disclosure, when a system exception is detected, the call stack data is queried to determine whether there is a target method corresponding to the target service; thus, whether the target service exists can be determined based on the call stack data. abnormal. If it is determined that the target service is abnormal, you can query the corresponding function point switch and turn off the switch, thereby prohibiting the abnormal target service from continuing to run, preventing the recurrence of abnormalities, avoiding affecting the normal operation of the system, and improving user experience.

It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only, and do not limit the present disclosure.

Description of the drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. Obviously, the drawings in the following description are only some embodiments of the present disclosure. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without exerting creative efforts.

Figure 1 schematically shows a schematic diagram of the flow of an exception service processing method in an exemplary embodiment of the present disclosure;

Figure 2 schematically shows a schematic diagram of a method flow for querying a call stack in an exemplary embodiment of the present disclosure;

Figure 3 schematically shows the composition of an exception service processing device in an exemplary embodiment of the present disclosure;

FIG. 4 schematically shows a structural diagram of a computer system of a wireless communication device in an exemplary embodiment of the present disclosure.

Detailed ways

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in various forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concepts of the example embodiments. To those skilled in the art. The described features, structures or characteristics may be combined in any suitable manner in one or more embodiments.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings represent the same or similar parts, and thus their repeated description will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and/or processor devices and/or microcontroller devices.

In order to improve the user experience and improve the convenience of using smart terminal devices, developers will modify the source code of the Android or iOS native system and add some unique functions. There may be stability issues with these features that were not discovered in early testing. Due to the complex usage environment of users, stability problems may be triggered in certain operating modes or specific environments, such as system abnormalities such as lags, crashes, or restarts. However, users cannot directly find the cause of system anomalies. They can only feedback log data to developers offline through after-sales service, or online through active submission, and then the staff will filter and process the abnormal information and target it. Compile if abnormal problems occur and upgrade through subsequent OTA. However, the cycle of this processing method is too long. During this period, the user may experience an exception again, affecting normal use.

In view of the above-mentioned shortcomings and shortcomings of the existing technology, this example embodiment provides an exception service processing method, which can be applied to smart terminal devices such as mobile phones, tablet computers, and notebook computers. Referring to what is shown in Figure 1, the above-mentioned exception service processing method may include the following steps:

S11, obtain abnormal data and query the call stack according to the abnormal data;

S12. When the call stack includes target method information corresponding to the target service, obtain the target service identifier corresponding to the target service according to the target method information;

S13: Obtain the corresponding function point switch of the target service according to the target service identifier, and turn off the function point switch of the target service.

In the network connection method provided by this example embodiment, on the one hand, real-time monitoring of system exceptions is performed, and when the system exception is monitored, the call stack data is queried to determine whether there is a target method corresponding to the target service; thus, the target method corresponding to the target service can be determined based on The call stack data determines whether there is an exception in the target service. On the other hand, when it is determined that the target service is abnormal, the corresponding function point switch can be queried and the switch is turned off, thereby prohibiting the abnormal target service from continuing to run, preventing the recurrence of abnormalities, and avoiding affecting the normal operation of the system. Improve user experience.

Below, each step of the exception service processing method in this exemplary embodiment will be described in more detail with reference to the accompanying drawings and embodiments.

Step S10, in response to the preset control operation, configure corresponding function point switches for the newly added target service, and establish a mapping relationship between the target service and the corresponding function point switch.

In this example implementation, the above-mentioned target service may be a function point that can implement specified functions. Users can add certain functions to smart terminal devices by updating the system, installing plug-ins, or loading application installation packages. For example, the above-mentioned target service can be a new function point in the system, such as: emergency help function, which can automatically call the police; search function, which can conduct global search of local memory; log collection function, which can automatically collect Bluetooth data , WiFi data packets; etc.

For each function point, the corresponding function point switch can be configured respectively, and a mapping relationship between the function point and the corresponding function point switch can be established. By controlling the function point switch, the function point can be turned off or on. Moreover, each new function point can be configured with a unique identification name, and the corresponding function point switch can be queried through the unique identification name. For the newly added function point, it can have a corresponding executable target method and a calling path corresponding to the target method. A mapping relationship between the function point name, the name of the target method and the calling path can be established, and the mapping relationship can be saved in a preset relationship table. When querying, you can use the mapping relationship in the relationship table to query the corresponding function point name based on the method name in the call stack.

In addition, the above-mentioned function points may also include several sub-function points. Specifically, for a feature newly added to the system, it can contain multiple small sub-function points. Each sub-function point can be independent of each other, implement different functions respectively, and have corresponding executable sub-functions. The target method, calling path, and unique identifying name. Each sub-function point also has a corresponding sub-function point switch. The corresponding sub-function point can be closed or opened through the sub-function point switch. Closing one sub-function point will not affect other sub-function points.

In addition, the function point or sub-function point can also be displayed in the device list, and the corresponding function point switch is displayed at the same time, so that the user can manually control whether to enable the function.

Step S11: Obtain exception data and query the call stack based on the exception data.

In this example implementation, for the terminal device, as shown in Figure 2, system abnormalities can be monitored in real time. Specifically, the above step S11 can include:

Step S111, monitor system abnormal data;

Step S112: When monitoring the existence of system exception data, trigger the dump service to print the call stack, and query the method data in the call stack.

For example, you can use the system's own anomaly detection module to monitor system anomalies in real time; you can also use log data to determine whether there are system anomalies. The above-mentioned system abnormalities can be: freeze, crash or system restart, etc.

When an exception is detected in the system, the dump service can be used to print the call stack, and the name of the target method corresponding to the function point can be used to query.

Step S12: When the call stack includes target method information corresponding to the target service, obtain the target service identifier corresponding to the target service according to the target method information.

In this example implementation, specifically, the call stack may include which functions are used and which processes are executed when a system exception occurs. After obtaining the specific data of the call stack, you can use the method name to query whether the call stack contains the target method. For example, match the target method name with the method name in the call stack. When the query includes a target method, the above-mentioned preset relationship table can be queried according to the name of the target method, thereby further determining the function point corresponding to the target service involved when the exception occurs.

Step S13: Obtain the corresponding function point switch of the target service according to the target service identifier, and turn off the function point switch of the target service.

In this example implementation, when it is determined that the corresponding process when the system exception occurs contains the function point corresponding to the target service. You can also confirm the attributes of the function point. If the function point is a non-core function point, obtain the path of the corresponding function point switch according to the mapping relationship, and turn off the function point switch corresponding to the function point, thereby turning off the target service. In this way, when a serious abnormality occurs in the system, non-core functions will be automatically shut down to prevent repeated crashes, thus improving the user experience. It effectively avoids abnormality caused by the operation of this function point during the use of terminal equipment, and turning off this function point will not affect the normal operation of the system.

Based on the above content, in this example implementation, when a function point includes multiple sub-function points, when an exception occurs and the call stack is traced and it is found that the exception point belongs to the default specific sub-function point, only the sub-function point will be closed. Alternatively, one or more sub-function points can be closed based on the specific process executed or the function called during the system exception, without having to close the entire function point. In this way, the minimal impact on the user experience can be achieved and more refined management and control can be achieved.

The method provided by the embodiment of the present disclosure pre-configures the corresponding function point switch for the function point, establishes a mapping relationship between the function point and the corresponding method name and method path, and stores it to facilitate subsequent query and management. When a serious abnormality occurs in actual use and the corresponding abnormal function point is traced through the call stack, the function point switch can be used to dynamically turn it off and restore it to the default state of the native system. Wait until the terminal device upgrades the system to fix the exception before opening it to prevent users from having problems such as repeated crashes in the same application scenario. Thereby improving user experience.

It should be noted that the above-mentioned drawings are only schematic illustrations of processes included in methods according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal sequence of these processes. In addition, it is also easy to understand that these processes may be executed synchronously or asynchronously in multiple modules, for example.

Further, as shown in FIG. 3 , the embodiment of this example also provides an abnormal service processing device 30 , including: an abnormal data identification module 301 , a target service identification module 302 and a switch control module 303 . in:

The abnormal data identification module 301 can be used to obtain abnormal data and query the call stack according to the abnormal data.

The target service identification module 302 may be configured to obtain the target service identifier corresponding to the target service according to the target method information when the call stack includes target method information corresponding to the target service.

The switch control module 303 may be configured to obtain the corresponding function point switch of the target service according to the target service identifier, and turn off the function point switch of the target service.

In an example of the present disclosure, the abnormal data identification module 301 may include: an exception listening module and a call stack query module (not shown in the figure). in,

The exception monitoring module can be used to monitor system abnormal data.

The call stack query module can be used to trigger the dump service to print the call stack when monitoring system exception data, and query the method data in the call stack.

In an example of the present disclosure, the target service is a non-core service.

In an example of the present disclosure, the device may further include: a mapping relationship establishment module (not shown in the figure).

The mapping relationship establishment module may be configured to configure corresponding function point switches for the newly added target service in response to a preset control operation, and establish a mapping relationship between the target service and the corresponding function point switch.

In an example of the present disclosure, the mapping relationship establishment module may further include: a mapping relationship storage module (not shown in the figure).

The mapping relationship storage module may be used to establish a mapping relationship between the target service, the corresponding target method, and the calling path corresponding to the target method, and save the mapping relationship in a preset relationship table.

In an example of the present disclosure, the target service includes several target sub-services; the target sub-services are configured with corresponding sub-function point switches.

In an example of the present disclosure, each of the target sub-services is independent of each other.

The specific details of each module in the above-mentioned exception service processing device have been described in detail in the corresponding exception service processing method, so they will not be described again here.

It should be noted that although several modules or units of equipment for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to embodiments of the present disclosure, the features and functions of two or more modules or units described above may be embodied in one module or unit. Conversely, the features and functions of one module or unit described above may be further divided into being embodied by multiple modules or units.

FIG. 4 shows a schematic structural diagram of a computer system suitable for implementing a wireless communication device according to an embodiment of the present invention.

It should be noted that the computer system 400 of the electronic device shown in FIG. 4 is only an example, and should not impose any restrictions on the functions and scope of use of the embodiments of the present invention.

As shown in Figure 4, the computer system 400 includes a central processing unit (Central Processing Unit, CPU) 401, which can be loaded into a random computer according to a program stored in a read-only memory (Read-Only Memory, ROM) 402 or from a storage part 408. The program in the memory (Random Access Memory, RAM) 403 is accessed to perform various appropriate actions and processes. In RAM 403, various programs and data required for system operation are also stored. The CPU 401, ROM 402, and RAM 403 are connected to each other through a bus 404. An input/output (I/O) interface 405 is also connected to bus 404.

The following components are connected to the I/O interface 405: an input part 406 including a keyboard, a mouse, etc.; an output part 407 including a cathode ray tube (Cathode Ray Tube, CRT), a liquid crystal display (LCD), etc., and a speaker, etc. ; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 409 performs communication processing via a network such as the Internet. Driver 410 is also connected to I/O interface 405 as needed. Removable media 411, such as magnetic disks, optical disks, magneto-optical disks, semiconductor memories, etc., are installed on the drive 410 as needed, so that a computer program read therefrom is installed into the storage portion 408 as needed.

In particular, according to embodiments of the present invention, the processes described below with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present invention include a computer program product including a computer program carried on a computer-readable medium, the computer program containing program code for performing the method illustrated in the flowchart. In such embodiments, the computer program may be downloaded and installed from the network via communication portion 409 and/or installed from removable media 411 . When the computer program is executed by the central processing unit (CPU) 401, various functions defined in the system of the present application are executed.

It should be noted that the computer-readable medium shown in the embodiment of the present invention may be a computer-readable signal medium or a computer-readable storage medium, or any combination of the above two. The computer-readable storage medium may be, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus or device, or any combination thereof. More specific examples of computer readable storage media may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard drive, random access memory (RAM), read only memory (ROM), removable Erasable Programmable Read Only Memory (EPROM), flash memory, optical fiber, portable compact disk read-only memory (Compact Disc Read-Only Memory, CD-ROM), optical storage device, magnetic storage device, or any of the above suitable The combination. In the present invention, a computer-readable storage medium may be any tangible medium that contains or stores a program for use by or in conjunction with an instruction execution system, apparatus, or device. In the present invention, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, in which computer-readable program code is carried. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device . Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code that contains one or more logic functions that implement the specified executable instructions. It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown one after another may actually execute substantially in parallel, or they may sometimes execute in the reverse order, depending on the functionality involved. It will also be noted that each block in the block diagram or flowchart illustration, and combinations of blocks in the block diagram or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or operations, or may be implemented by special purpose hardware-based systems that perform the specified functions or operations. Achieved by a combination of specialized hardware and computer instructions.

The units involved in the embodiments of the present invention can be implemented in software or hardware, and the described units can also be provided in the processor. Among them, the names of these units do not constitute a limitation on the unit itself under certain circumstances.

As another aspect, this application also provides a computer-readable medium. The computer-readable medium may be included in the electronic device described in the above embodiments; it may also exist independently without being assembled into the electronic device. middle. The computer-readable medium carries one or more programs. When the one or more programs are executed by an electronic device, the electronic device implements the method described in the following embodiments. For example, the electronic device can implement various steps as shown in Figure 1.

Furthermore, the above-mentioned drawings are only schematic illustrations of processes included in methods according to exemplary embodiments of the present invention, and are not intended to be limiting. It is readily understood that the processes shown in the above figures do not indicate or limit the temporal sequence of these processes. In addition, it is also easy to understand that these processes may be executed synchronously or asynchronously in multiple modules, for example.

Other embodiments of the disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure that follow the general principles of the disclosure and include common knowledge or customary technical means in the technical field that are not disclosed in the disclosure. . It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise structures described above and illustrated in the accompanying drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (7)

1. An exception service handling method, characterized by including: In response to the preset control operation, configure the corresponding function point switch for the newly added target service, and establish a mapping relationship between the target service and the corresponding function point switch; establish the target service and the corresponding target method, and The mapping relationship between the calling paths corresponding to the target method, and saving the mapping relationship in a preset relationship table; Obtain exception data and query the call stack according to the exception data; When the call stack includes target method information corresponding to the target service, obtain the target service identifier corresponding to the target service according to the target method information; the target service is a non-core service; Obtain the corresponding function point switch of the target service according to the target service identifier, and turn off the function point switch of the target service, including: when it is determined that the corresponding process contains the function point corresponding to the target service when a system exception occurs, Confirm the attributes of the function point. When the function point is a non-core function point, obtain the path of the corresponding function point switch according to the mapping relationship, turn off the function point switch corresponding to the function point, thereby turning off the target service; and When a function point includes multiple sub-function points, when an exception occurs, tracing the call stack and finding that the exception point belongs to the default specific sub-function point, only this sub-function point will be closed; or, according to the specific process or call executed during the system exception The function determines to close one or more sub-function points. 2. The method according to claim 1, characterized in that said obtaining abnormal data and querying the call stack according to the abnormal data includes: Monitor system abnormal data; When monitoring the presence of system exception data, the dump service is triggered to print the call stack, and the method data in the call stack is queried. 3. The method according to claim 1, characterized in that the target service includes several target sub-services; the target sub-services are configured with corresponding sub-function point switches. 4. The method according to claim 3, characterized in that each of the target sub-services is independent of each other. 5. An exception service processing device, characterized in that it includes: A mapping relationship establishment module, configured to configure corresponding function point switches for the newly added target service in response to the preset control operation, and establish a mapping relationship between the target service and the corresponding function point switch; A mapping relationship storage module, used to establish a mapping relationship between the target service and the corresponding target method, and the calling path corresponding to the target method, and save the mapping relationship in a preset relationship table; An abnormal data identification module is used to obtain abnormal data and query the call stack according to the abnormal data; A target service identification module, configured to obtain the target service identifier corresponding to the target service according to the target method information when the call stack includes target method information corresponding to the target service; A switch control module, configured to obtain the corresponding function point switch of the target service according to the target service identifier, and turn off the function point switch of the target service, including: when determining that a system abnormality occurs, the corresponding process contains the target service corresponding When the function point is a function point, the attributes of the function point are confirmed. When the function point is a non-core function point, the path of the corresponding function point switch is obtained according to the mapping relationship, and the function point switch corresponding to the function point is turned off, so that the target The service is shut down; and, when the function point includes multiple sub-function points, when an exception occurs, tracing the call stack and finding that the exception point belongs to the default specific sub-function point, only the sub-function point is closed; or, according to the execution during the system exception The specific process or function called determines the closure of one or more sub-function points. 6. A computer-readable medium with a computer program stored thereon, characterized in that when the computer program is executed by a processor, the exception service processing method according to any one of claims 1 to 4 is implemented. 7. A wireless communication terminal, characterized by comprising: one or more processors; A storage device configured to store one or more programs, which when the one or more programs are executed by the one or more processors, causes the one or more processors to implement any of claims 1 to 4 The exception service handling method described in one item.