CN111416857A - Client crash processing method, device, system, equipment and storage medium - Google Patents
Client crash processing method, device, system, equipment and storage medium Download PDFInfo
- Publication number
- CN111416857A CN111416857A CN202010183705.7A CN202010183705A CN111416857A CN 111416857 A CN111416857 A CN 111416857A CN 202010183705 A CN202010183705 A CN 202010183705A CN 111416857 A CN111416857 A CN 111416857A
- Authority
- CN
- China
- Prior art keywords
- crash
- client
- configuration file
- information
- event
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims abstract description 33
- 238000012545 processing Methods 0.000 claims abstract description 81
- 238000012544 monitoring process Methods 0.000 claims abstract description 80
- 238000000034 method Methods 0.000 claims abstract description 65
- 230000008569 process Effects 0.000 claims abstract description 29
- 238000004458 analytical method Methods 0.000 claims description 46
- 230000006870 function Effects 0.000 claims description 45
- 238000004590 computer program Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 11
- 230000000694 effects Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 5
- 230000009286 beneficial effect Effects 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 3
- 239000000284 extract Substances 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 230000008439 repair process Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 238000009434 installation Methods 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000008447 perception Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000002035 prolonged effect Effects 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L67/025—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention discloses a client crash processing method, a device, a system, equipment and a storage medium, wherein the method comprises the following steps: when monitoring a crash event in the operation process of a client, determining whether a configuration file for the crash event is acquired; if yes, processing a crash event of the client according to the configuration file; if not, acquiring the crash information of the crash event; the method comprises the steps that crash information is sent to a monitoring server, the monitoring server generates a configuration file of a client according to the crash information and sends the configuration file to the configuration server, so that the client can request the configuration file of a crash event from the configuration server, the problem that a user cannot use the service of the client due to the fact that the client is subjected to flash quitting when the crash event occurs is avoided, the crash event can be processed through the configuration file before the client sends a edition again, the crash rate of the user using the client is effectively reduced in time, the user can use the service provided by the client, and the use time, the stability and the use experience of the user using the client are.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a client crash processing method, device, system, equipment and storage medium.
Background
In recent years, with the development of intelligent terminal devices and mobile communication network technologies, the intelligent terminal devices can be installed with various clients like personal computers, so that applications of the intelligent terminal devices are enriched through the various clients, and wireless network access can be realized through the mobile communication network.
After the client is released, the client of each version has a problem of crash in a certain proportion more or less, and although a try catch crash capture mode is also adopted in the current client development to avoid a part of code blocks which may have risks in the running process of the client code so as to avoid the client crash from having obvious perception to a user and causing the client crash to flash back, the code cannot be spread over the whole client code, and the client still has a certain probability of crash flash back in the use process. At present, when a client crashes and flashes, a common processing mode is to close a currently released version of the client through an application market developer control platform, so that more users are prevented from being installed in the crashed version through application updating, meanwhile, a development team is required to emergently repair the crash problem, and then the tested and repaired new version is released in the application market, so that the repair time is long.
However, for the user who has installed the version that has crashed, there is a very high probability that the application market will not update the client in a short time, and this part of users will continue to use the version that has crashed before updating to the latest version, and the client crash will occur again inevitably, resulting in interruption of the client task that the user is executing, and the user cannot normally use the service provided by the client, which seriously affects the user experience.
Disclosure of Invention
Embodiments of the present invention provide a client crash processing method, apparatus, system, device, and storage medium, so as to solve the problem in the prior art that a user cannot use a client service due to a client crash, and the user experience of the user is affected.
In a first aspect, an embodiment of the present invention provides a client crash processing method, including:
when a crash event is monitored in the operation process of a client, determining whether a configuration file for the crash event is acquired;
if yes, processing a crash event of the client according to the configuration file;
if not, acquiring the crash information of the crash event;
and sending the crash information to a monitoring server, wherein the monitoring server is used for generating a configuration file of the client according to the crash information and sending the configuration file to a configuration server.
In a second aspect, an embodiment of the present invention provides a client crash processing method, including:
the monitoring server receives crash information sent by the client;
generating a crash analysis report of the client according to the crash information;
generating a configuration file of the client according to the crash analysis report;
and sending the configuration file to a configuration server, wherein the configuration server is used for sending the configuration file to the client when receiving a configuration file request of the client.
In a third aspect, an embodiment of the present invention provides a client crash processing method, including:
a configuration server receives a configuration file of a client sent by a monitoring server, wherein the configuration file is a file generated by the monitoring server according to crash information sent by the client;
receiving a configuration file request of the client;
and sending the configuration file to the client, wherein the client is used for processing a crash event according to the configuration file.
In a fourth aspect, an embodiment of the present invention provides a client crash processing apparatus, including:
the judging module is used for determining whether a configuration file aiming at a crash event is acquired or not when the crash event is monitored in the operation process of the client;
the crash event processing module is used for processing the crash event of the client according to the configuration file;
the crash information acquisition module is used for acquiring crash information of the crash event;
and the crash information sending module is used for sending the crash information to a monitoring server, and the monitoring server is used for generating a configuration file of the client according to the crash information and sending the configuration file to a configuration server.
In a fifth aspect, an embodiment of the present invention provides a client crash processing apparatus, including:
the crash information receiving module is used for monitoring the crash information sent by the server receiving client;
the crash analysis report generation module is used for generating a crash analysis report of the client according to the crash information;
the configuration file generation module is used for generating the configuration file of the client according to the crash analysis report;
the first configuration file sending module is used for sending the configuration file to a configuration server, and the configuration server is used for sending the configuration file to the client when receiving a configuration file request of the client.
In a sixth aspect, an embodiment of the present invention provides a client crash processing apparatus, including:
the configuration file receiving module is used for receiving a configuration file of a client side sent by a monitoring server by a configuration server, wherein the configuration file is a file generated by the monitoring server according to the crash information sent by the client side;
the configuration file request module is used for receiving a configuration file request of the client;
and the second configuration file sending module is used for sending the configuration file to the client, and the client is used for processing a crash event according to the configuration file.
A seventh aspect of the present invention provides a client crash processing system, including a client, a monitoring server and a configuration server, where the client communicates with the monitoring server and the configuration server respectively, and the monitoring server communicates with the configuration server;
the client is configured to execute the client crash processing method provided by the first aspect of the embodiment of the present invention, the monitoring server is configured to execute the client crash processing method provided by the second aspect of the embodiment of the present invention, and the configuration server is configured to execute the client crash processing method provided by the third aspect of the embodiment of the present invention.
In an eighth aspect, an embodiment of the present invention provides an apparatus, where the apparatus includes:
one or more processors;
a storage device for storing 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 client crash handling method according to any embodiment of the present invention.
In a ninth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a client crash processing method according to any embodiment of the present invention.
When a crash event is monitored in the operation process of the client, determining whether a configuration file for the crash event is acquired, if so, processing the crash event of the client according to the configuration file; if not, acquiring the crash information of the crash event, and sending the crash information to the monitoring server, wherein the monitoring server is used for generating a configuration file of the client according to the crash information and sending the configuration file to the configuration server, so that the client can request to process the configuration file of the crash event from the configuration server, the problem that the user cannot normally use the service provided by the client due to flash quit when the client generates the crash event and the user use experience is influenced is avoided, the current crash event can be processed through the configuration file before the client updates the version again, the crash rate of the client used by the online user can be timely and effectively reduced, the user can use the service provided by the client, and the use duration, the stability and the use experience of the client used by the user are improved.
Drawings
Fig. 1 is a flowchart illustrating steps of a method for handling a client crash according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating steps of a method for handling a client crash according to a second embodiment of the present invention;
fig. 3 is a flowchart illustrating steps of a method for handling a client crash according to a third embodiment of the present invention;
fig. 4A is a flowchart illustrating steps of a method for handling a client crash according to a fourth embodiment of the present invention;
FIG. 4B is a schematic diagram of a processing flow of a crash event in the android system in an embodiment of the present invention;
fig. 5 is a flowchart illustrating steps of a method for handling a client crash according to a fifth embodiment of the present invention;
fig. 6 is a block diagram illustrating a structure of a client crash processing apparatus according to a sixth embodiment of the present invention;
fig. 7 is a block diagram illustrating a structure of a client crash processing apparatus according to a seventh embodiment of the present invention;
fig. 8 is a block diagram illustrating a structure of a client crash processing apparatus according to an eighth embodiment of the present invention;
FIG. 9 is a block diagram illustrating a system for handling a client crash according to a ninth embodiment of the present invention;
fig. 10 is a block diagram of a device according to a tenth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a flowchart of steps of a client crash processing method according to an embodiment of the present invention, where the method according to an embodiment of the present invention is applicable to a situation where a client crashes, and the method may be executed by a client crash processing apparatus implemented by the present invention, where the client crash processing apparatus may be implemented by hardware or software and integrated in a client provided by an embodiment of the present invention, and specifically, as shown in fig. 1, the client crash processing method according to an embodiment of the present invention may include the following steps:
s101, when a crash event is monitored in the operation process of a client, whether a configuration file for the crash event is acquired or not is determined.
In the embodiment of the present invention, the client may be an application installed and running on various terminal devices, the terminal devices may be electronic devices such as a personal PC, a server, and a mobile terminal, the terminal devices may be installed with operating systems such as Windows, UNIX, linux, Android, and IOS, and for one client, versions of the client on each terminal device may be the same or different.
The crash event may refer to various exceptions occurring in the client running process, for example, the exception may be a client flash back, a page has no response, a last page is returned in a non-operational manner, and the like.
After capturing a crash event, the client may determine whether a configuration file is stored locally, where the configuration file is a processing policy for the crash event, the configuration file is stored in the configuration server, the client may intermittently request the configuration file from the configuration server according to a certain period and store the configuration file in the local memory, and after the crash event occurs, if the configuration file exists, S102 is executed, otherwise S103 is executed.
And S102, processing the crash event of the client according to the configuration file.
Specifically, the configuration file can be analyzed to obtain the crash identification codes and the corresponding crash processing strategies of various types of crash events of the clients of various versions, the clients are matched in the analyzed configuration file according to the current version and the generated crash events to obtain the crash processing strategies of the crash events of the current version, and the crash processing strategies are adopted to process the currently generated crash events, so that abnormal flash back of the clients, no response of pages or abnormal return to the previous page and the like are avoided, users can use other services of the clients, the problem that the clients flash back and even the clients need to be uninstalled is avoided, the use experience of the users is improved, and the user can be guaranteed not to have the crash events before the clients are updated.
S103, obtaining the crash information of the crash event.
In the embodiment of the present invention, the crash information may be version information of the client, running environment information of the client, description information of the crash event, and the like, where the running environment information may be an operating system of a terminal device on which the client is installed, hardware resource information, a use condition of a hardware resource, and the like, and the description information of the crash event may be description of the crash event, for example, insufficient memory, stack overflow, an error in call function return, and the like. When a crash event occurs and there is no related configuration file, the crash information of the crash event can be obtained in the client through a crash event capture function, and the specific crash event capture function is different in different operating systems, which is not limited herein.
And S104, sending the crash information to a monitoring server, wherein the monitoring server is used for generating a configuration file of the client according to the crash information and sending the configuration file to a configuration server.
Specifically, the crash information can be packaged and then transmitted to the monitoring server through HTTP POST, the monitoring server generates a configuration file of the client after receiving the crash information, and transmits the configuration file to the configuration server, so that the client can request the configuration file from the configuration server in time after restarting, and the crash event can be solved according to the configuration file.
When a crash event is monitored in the operation process of the client, determining whether a configuration file for the crash event is acquired, if so, processing the crash event of the client according to the configuration file; if not, acquiring the crash information of the crash event, and sending the crash information to the monitoring server, wherein the monitoring server is used for generating a configuration file of the client according to the crash information and sending the configuration file to the configuration server, so that the client can request the configuration file of the crash event to the configuration server, the problem that the user cannot normally use the service provided by the client due to flash quit when the client generates the crash event and the user use experience is influenced is solved, the current crash event can be processed through the configuration file before the client updates the version again, the crash rate of the client used by the online user can be timely and effectively reduced, the user can use the service provided by the client, and the use duration, the stability and the use experience of the client used by the user are improved.
Example two
Fig. 2 is a flowchart of steps of a client crash processing method according to a second embodiment of the present invention, where the embodiment of the present invention performs optimization based on the first embodiment, specifically, as shown in fig. 2, the client crash processing method according to the embodiment of the present invention may include the following steps:
s201, sending a configuration file request to the configuration server according to a preset period.
In the embodiment of the present invention, the client is in communication connection with the configuration server storing the configuration file, and the client may request the configuration file from the configuration server at preset periodic intervals, for example, the client may send a configuration file request to the configuration server every 0.5 hour, or the client sends a configuration file request to the server when starting, and the like, and after receiving the configuration file request, the configuration server sends the latest configuration file to the client.
S202, after receiving the configuration file returned by the configuration server, storing the configuration file in a local memory.
Specifically, the client may store the configuration file returned by the configuration server in a specified storage directory, and optionally, may store the configuration file in a folder established for the configuration file in the client installation directory.
S203, determining a crash identification code of the crash event, wherein the crash identification code is the only identification code of the client side for the crash event.
Specifically, the client may have different stack information when each different crash event occurs, and the stack information may be encoded, for example using encoding such as Base64, to convert the lengthy stack information into a unique string of finite (perhaps 24-bit) length characters, the character string is the only identification code of the client terminal when the crash event happens, the crash identification code can be uploaded to a monitoring server to generate a corresponding configuration file together with the version information of the client terminal as crash information, therefore, different configuration files can be generated aiming at the crash events of the clients with different versions, so that the configuration files are matched according to the crash identification code when the subsequent client generates the crash event, and determining a solution for the crash event that matches the version information of the client from the parsed configuration file.
S204, determining whether a configuration file matched with the crash identification code is stored in the local memory.
In the embodiment of the present invention, the crash identification code is the unique identification code of the client that has a crash event, and it may be determined whether the configuration file matching the crash identification code is stored in the local storage, for example, whether the configuration file corresponding to the crash identification code is stored in the local storage may be searched by using the crash identification code as an index, if so, S205-S206 is executed, otherwise, S207-S209 is executed.
S205, analyzing the configuration file to obtain a crash processing strategy corresponding to the version of the client.
In the embodiment of the invention, the configuration file can be firstly analyzed to obtain the analyzed configuration file, and then a solution for the crash event of the client of the current version is determined from the analyzed configuration file, wherein the solution is generated when the monitoring server receives crash information containing the crash identification code and the client version information.
S206, processing the crash event of the client by adopting the crash processing strategy.
Specifically, the crash processing policy may include a code for solving a crash event, and the client may execute the code to solve the crash event occurring at the client, and in practical application, different clients may customize the crash event to the crash event under different operating systems, which is not limited in the embodiment of the present invention.
S207, when the client calls the crash event capture function, hooking the crash event capture function through a hook function.
The crash event capturing function may be a function for monitoring a crash event occurring in the client, and the crash event capturing function may be pre-injected into the client, and when the client calls the crash event capturing function, the crash event capturing function may be hooked through a hook function, so as to obtain crash information of the crash event through the crash event capturing function.
Taking the Android system as an example, Activity is one of four most basic and most commonly used components in the Android components, and Activity is an application component, and provides a screen which can be used by a user to interactively complete a certain task. In an Android system client, an Activity is usually a separate screen on which controls can be displayed and events of a user can be monitored and processed to respond, and a client at least contains one Activity.
In an Android system, the crash event capture function may be an uncaughtectvision function, where the uncaughtectvision function is a function for acquiring crash information when a client crashes, and in practical applications, the crash information may include information such as a cause causing the client to crash, a location of the crash event in the client, and a version of the client.
In the embodiment of the invention, whether the window start of the Activity of the client calls the crash event capture function uncaughtexeception or not can be monitored by taking the Activity as a unit, if so, the uncaughtexeception function can be hooked by using the hook function hook, and when the fact that the Activity window of the client calls the crash event capture function uncaugentation is monitored, the crash event capture function uncaugumentation of the client is described to be crashed, and the hook function hook can be triggered to obtain crash information.
The process of acquiring the crash information is described by the Android system, in practical application, different functions can be adopted according to different operating systems to acquire the crash information, and the crash event capture function and the hook function are not limited in the embodiment of the invention.
And S208, acquiring the crash information through the crash event capture function.
Specifically, version information of the client, running environment information of the client, and description information of the crash event may be acquired through the crash event capture function, where the description information may be information of a location of a window where the crash event occurs in the client, a crash reason, and the like.
S209, sending the crash information to a monitoring server, wherein the monitoring server is used for generating a configuration file of the client according to the crash information and sending the configuration file to a configuration server.
In an optional embodiment of the present invention, the crash information may be packaged and then transmitted to the monitoring server through http post, so as to reduce the data volume of the crash information. The monitoring server generates a configuration file of the client after receiving the crash information and sends the configuration file to the configuration server, so that the client can request the configuration file from the configuration server in time after restarting and solve the crash event according to the configuration file.
The client terminal of the embodiment of the invention can request the configuration file from the configuration server according to the preset period and store the configuration file into the local memory, determines the crash processing strategy matched with the crash identification code in the configuration file according to the crash identification code after determining the crash identification code of the crash event, processes the crash event according to the crash processing strategy, hooks the crash event capture function through the hook function to obtain the crash information and sends the crash information to the monitoring server when determining that the crash identification code of the crash event has no matched crash processing strategy in the configuration file, so that the monitoring server generates the configuration file according to the crash information and sends the configuration file to the configuration server, the client terminal can obtain the configuration file from the configuration server in time to process the crash event, and the problem that the user cannot normally use the service provided by the client terminal due to flash back when the crash event occurs in the client terminal is avoided, the problem of influencing the user experience can be solved by processing the current crash event through the configuration file before the client updates the version again, so that the crash rate of the online user using the client can be effectively reduced in time, the user can use the service provided by the client, and the use duration, stability and use experience of the user using the client are improved.
Furthermore, after the configuration files are matched through the crash identification codes, the configuration files are analyzed to obtain a crash processing strategy corresponding to the version of the client, namely different configuration files can be configured for different versions, each version of the client can be accurately obtained, the client of each version can be guaranteed to effectively process the crash event when sending the crash event, and the old version can be traced and managed.
EXAMPLE III
Fig. 3 is a flowchart of steps of a client crash processing method according to a third embodiment of the present invention, where the method according to the third embodiment of the present invention is applicable to a case of handling a client crash event, and the method may be executed by a client crash processing apparatus implemented by the present invention, and the client crash processing apparatus may be implemented by hardware or software and integrated in a monitoring server according to the third embodiment of the present invention, and specifically, as shown in fig. 3, the client crash processing method according to the third embodiment of the present invention may include the following steps:
s301, the monitoring server receives the crash information sent by the client.
The crash information may be version information of the client, running environment information of the client, description information of the crash event, a crash identification code of the crash event, and the like, where the running environment information may be an operating system of a terminal device on which the client is installed, hardware resource information, a use condition of the hardware resource, and the like, the description information of the crash event may be description of the crash event, such as insufficient memory, stack overflow, an error returned by a calling function, and the like, and the crash identification code is a unique identification code of each crash event occurring at the client.
In the embodiment of the invention, the monitoring server is communicated with the client, when the client has a crash event and has no related configuration file, the client acquires crash information of the crash event through the crash event capture function and sends the crash information to the monitoring server, and then the monitoring server can receive the crash information sent by the client through the receiving interface.
S302, generating a crash analysis report form of the client according to the crash information.
Specifically, the crash analysis reports of the clients of the respective versions may be generated according to the versions of the clients, each crash analysis report may be the number, probability, and the like of various crash events occurring on the clients of the respective versions, may also be the probability of a certain crash event occurring on the clients of the respective versions, or the crash level distribution of various crash events, and may also be a crash analysis report generated according to the input conditions of the client developer, and in practical applications, the rule for generating the relevant crash analysis report may be set according to different requirements.
S303, generating the configuration file of the client according to the crash analysis report.
In an alternative embodiment of the present invention, the configuration file is a processing policy for the crash event, and for example, may be a flow for the configuration client to process the crash event. The monitoring server can display a query interface of the crash analysis report to the client developer, so that the client developer can input the query condition of the crash analysis report to query the relevant crash analysis report, and after the query condition of the crash analysis report is displayed to the client developer, the configuration file of the client is generated based on the crash processing strategy input by the client developer, of course, the corresponding configuration file can be automatically generated based on the rule preset by the client developer, for example, when the occurrence probability of a certain crash event is greater than the preset value, the processing strategy for closing the version of the client service is generated, or for the same type of crash event, the processing strategy is generated based on the processing rule set by the prior experience to obtain the configuration file, different configuration files can be generated according to different crash events in the actual application, the embodiment of the present invention does not limit the manner of generating the configuration file.
S304, sending the configuration file to a configuration server, wherein the configuration server is used for sending the configuration file to the client when receiving a configuration file request of the client.
Specifically, the monitoring server communicates with the configuration server, and may encode the configuration file according to a preset encoding rule and send the encoded configuration file to the configuration server, so that the configuration server can send the configuration file to the client when receiving a configuration file request from the client, and the client can process a crash event according to the configuration file.
The monitoring server of the embodiment of the invention generates the crash analysis report of the client after receiving the crash information sent by the client, and the crash analysis report generates the configuration file of the client and sends the configuration file to the configuration server, so that the configuration server can send the configuration file to the client when receiving the configuration file request of the client, so that the client can process the crash event according to the configuration file, the problem that the user cannot normally use the service provided by the client due to flash back when the client crashes and the user experience is influenced is avoided, the current crash event can be processed by the configuration file before the client updates the version again, the crash rate of the client used by the online user can be effectively reduced, the service provided by the client can be used by the user, the use time of the client used by the user is prolonged, and the crash analysis report of the client is sent to the configuration server, the client, Stability and use experience.
Example four
Fig. 4A is a flowchart of steps of a client crash processing method according to a fourth embodiment of the present invention, where the embodiment of the present invention performs optimization based on the third embodiment, specifically, as shown in fig. 4A, the client crash processing method according to the embodiment of the present invention may include the following steps:
s401, the monitoring server receives the crash information sent by the client.
In the embodiment of the invention, the monitoring server is communicated with the client, when the client has a crash event and has no related configuration file, the client acquires crash information of the crash event through the crash event capture function and sends the crash information to the monitoring server, and then the monitoring server can receive the crash information sent by the client through the receiving interface.
S402, extracting version information of the client from the crash information.
Optionally, the client may obtain information including a client version as the crash information when obtaining the crash information, the monitoring server decompresses the crash information after receiving the crash information, and decompresses and extracts the version information of the client in each piece of crash information from the decompressed crash information, for example, extracts a version number of the client.
And S403, generating crash analysis reports of the clients of all versions.
Specifically, the crash analysis report of each version of the client may be generated by counting the crash events occurring at the clients of each version based on the version to obtain the types, probabilities, levels, reasons, and the like of the crash events occurring at the clients of each version, and of course, the probability, number, reasons, and the like of the crash events occurring at the clients of each version may also be generated based on a certain crash event to generate a crash analysis report, or a corresponding crash analysis report is generated based on the query condition of the client developer.
S404, generating a configuration file of each crash event according to the input information of the crash event in the crash analysis report form by the user.
Specifically, the embodiment of the present invention may display a crash analysis report to a client developer on a display device, where the client developer inputs a processing policy for a crash event occurring on a client of each version into a monitoring server after viewing the crash analysis report, and the monitoring server generates a configuration file for the client of each version, where, for example, each crash event has a unique crash identification code, and the crash identification code is an identification code of each crash event occurring on the client.
Fig. 4B shows a processing strategy for a crash event (crash) in the Android system:
the first method is to determine whether the lifecycle of the system component is broken, if so, the component of the Android system has no response in the lifecycle and cannot work normally, the component instance needs to be closed, but the client crash flash cannot be caused, the client may show that the client returns to the last page due to some abnormality, only a certain small function in the client is affected and cannot be used normally, the user can normally continue to use other service function modules, and in this case, only the component of the Android system with the abnormality (finish this) is closed.
The second type is code crash (specific _ case) of a service layer, for example, code crash of a certain client, that is, if not Android system component lifecycle crash, it is determined whether a captured crash event is a crash of the client, if so, it may be caused by data error or improper processing of abnormal boundary conditions, in this case, it may affect that a certain data request cannot be returned normally, or a certain UI component cannot be refreshed normally, or a certain interactive operation has no response, and when such an acceptable error occurs, the event may be captured (catch) and directly ignored, so that the client continues to operate subsequent operations.
The third is system crash (normal _ exception), that is, when judging that the specific _ case crash is not the second case crash, determining whether the system crash is normal _ exception crash, where the normal _ exception crash is a predefined error or exception which happens to the system, or a crash caused by Android operation exception, and in this case, the client developer cannot generally solve the problem after checking, but the crash in this case has no influence on the user using the client, and can capture (catch) the event and then ignore the event, so as to allow the error.
The fourth is a crash event other than the above three cases, when a crash event is not the above three cases, the crash will be left unprocessed by the client crash flash and will be thrown upwards (throw our), and the user needs to restart the client to be able to use the client.
The above description takes a crash event (crash happy) occurring in the Android system as an example to illustrate a processing flow of the client to the crash event, and a client developer may compile a corresponding execution code according to the processing flow to generate a configuration file for executing the processing flow, and input the configuration file into the monitoring server.
Of course, for different operating systems and different crash events, the client developer may define a corresponding processing flow according to an actual situation to generate a corresponding configuration file, which is not limited in the embodiment of the present invention.
S405, collecting and coding the configuration files of all the crash events to obtain the configuration file of the client.
In the embodiment of the present invention, the configuration file may be generated according to the version of the client, that is, the configuration files of various crash events of the client of a certain version are collected and encoded to obtain the configuration file of the client of the version, and of course, the configuration files of the clients of all versions may also be collected to obtain the configuration file of the client, which may be set according to actual needs in actual applications, which is not limited in the embodiment of the present invention.
S406, sending the configuration file to a configuration server, wherein the configuration server is used for sending the configuration file to the client when receiving a configuration file request of the client.
Specifically, the monitoring server communicates with the configuration server, and may encode the configuration file according to a preset encoding rule and send the encoded configuration file to the configuration server, so that the configuration server can send the configuration file to the client when receiving a configuration file request from the client, and the client can process a crash event according to the configuration file.
The monitoring server of the embodiment of the invention extracts the version information of the client after receiving the crash information sent by the client, generates the crash analysis report of each version of the client, generates the configuration file of each version of the client according to the input information of the crash event in the crash analysis report of each version of the client by a user, and sends the configuration file to the configuration server, so that the configuration server can send the configuration file to the client when receiving the configuration file request of the client, the client can process the generated crash event according to the configuration file, the problem that the user cannot normally use the service provided by the client and the user use experience is influenced due to the flash back when the client generates the crash event is avoided, the current crash event can be processed by the configuration file before the client updates the version again, the collapse rate of the online user using the client can be timely and effectively reduced, so that the user can use the service provided by the client, and the use time, the stability and the use experience of the user using the client are improved.
Furthermore, different configuration files can be generated according to clients of different versions, each version of the client can be accurately obtained, the client of each version can be guaranteed to effectively process the crash event when sending the crash event, and the old version can be subjected to tracing management.
EXAMPLE five
Fig. 5 is a flowchart of steps of a client crash processing method according to a fifth embodiment of the present invention, where the method according to the fifth embodiment of the present invention is applicable to a case of handling a client crash event, and the method may be executed by a client crash processing apparatus implemented by the present invention, and the client crash processing apparatus may be implemented by hardware or software and integrated in a configuration server according to the embodiment of the present invention, and specifically, as shown in fig. 5, the client crash processing method according to the fifth embodiment of the present invention may include the following steps:
s501, a configuration server receives a configuration file of a client side sent by a monitoring server, wherein the configuration file is generated by the monitoring server according to collapse information sent by the client side.
In the embodiment of the invention, the configuration server is respectively communicated with the monitoring server and the client, and after the monitoring server generates the configuration file according to the crash information sent by the client and sends the configuration file to the configuration server, the configuration server can receive the configuration file, and certainly, the configuration server can request the configuration file from the monitoring server according to a certain period.
S502, receiving a configuration file request of the client.
In the embodiment of the present invention, the client sends the configuration file request to the configuration server according to the set period, and then the configuration server may receive the configuration file request from the client, where the configuration file request may include a client identifier, such as a client name or a code number, and may further include operating system information installed in the client, a version number of the client, and the like, so that the configuration server may send the configuration file of the client of a specific version under a corresponding operating system to the client, and certainly, in an actual application, the configuration file request may not include the operating system information and the version number of the client.
S503, sending the configuration file to the client, wherein the client is used for processing a crash event according to the configuration file.
Specifically, the configuration file may be packaged and sent to the client, for example, the configuration file of the specified version under the specified operating system is sent to the client with the specified version installed under the specified operating system. Of course, all operating systems and all versions of configuration files may also be packaged and sent to the client, so that after the client parses the configuration files, the configuration files of corresponding versions are matched from the parsed configuration files to process the crash event.
The configuration server receives the configuration file of the client sent by the monitoring server, sends the configuration file to the client after receiving the configuration file request of the client, enables the client to process the crash event according to the configuration file, avoids the problem that the user cannot normally use the service provided by the client due to flash back when the client generates the crash event and influences the user experience, can process the current crash event through the configuration file before the client updates the version again, can timely and effectively reduce the crash rate of the client used by the online user, enables the user to use the service provided by the client, and improves the use duration, stability and use experience of the client used by the user.
EXAMPLE six
Fig. 6 is a block diagram of a client crash processing apparatus according to a sixth embodiment of the present invention, and as shown in fig. 6, the client crash processing apparatus according to the sixth embodiment of the present invention may specifically include the following modules:
the determining module 601 is configured to determine whether a configuration file for a crash event is acquired when the crash event is monitored in an operation process of a client;
a crash event processing module 602, configured to process a crash event of the client according to the configuration file;
a crash information obtaining module 603, configured to obtain crash information of the crash event;
a crash information sending module 604, configured to send the crash information to a monitoring server, where the monitoring server is configured to generate a configuration file of the client according to the crash information, and send the configuration file to a configuration server.
Optionally, the method further comprises:
the configuration file request module is used for sending a configuration file request to the configuration server according to a preset period;
and the configuration file storage module is used for storing the configuration file into a local memory after receiving the configuration file returned by the configuration server.
Optionally, the determining module 601 includes:
a crash identification code determining submodule, configured to determine a crash identification code of the crash event, where the crash identification code is a unique identification code of the client in the crash event;
and the matching submodule is used for determining whether a configuration file matched with the crash identification code is stored in the local memory.
Optionally, the crash event processing module 602 includes:
the analysis submodule is used for analyzing the configuration file to obtain a crash processing strategy corresponding to the version information of the client;
and the crash event processing submodule is used for processing the crash event of the client by adopting the crash processing strategy.
Optionally, the crash information obtaining module 603 includes:
the crash event capturing function hooking submodule is used for hooking the crash event capturing function through a hook function when the client calls the crash event capturing function;
and the crash information capturing submodule is used for acquiring crash information through the crash event capturing function.
Optionally, the crash information comprises at least one of:
version information of a client, operating environment information of the client, and description information of the crash event.
The client crash processing device provided by the embodiment of the invention can execute the client crash processing method provided by the first embodiment and the second embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
EXAMPLE seven
Fig. 7 is a block diagram of a client crash processing apparatus according to a seventh embodiment of the present invention, and as shown in fig. 7, the client crash processing apparatus according to the seventh embodiment of the present invention may specifically include the following modules:
a crash information receiving module 701, configured to receive crash information sent by a client through a monitoring server;
a crash analysis report generation module 702, configured to generate a crash analysis report of the client according to the crash information;
a configuration file generating module 703, configured to generate a configuration file of the client according to the crash analysis report;
a first configuration file sending module 704, configured to send the configuration file to a configuration server, where the configuration server is configured to send the configuration file to the client when receiving a configuration file request of the client.
Optionally, the crash analysis report generation module 702 includes:
the version information extraction submodule is used for extracting the version information of the client from the crash information;
and the crash analysis report generation submodule is used for generating crash analysis reports of the clients of all versions.
Optionally, the crash analysis report includes at least one of:
version information of the client, crash event type, crash probability, and crash level.
Optionally, the configuration file generating module 703 includes:
the configuration file generation submodule is used for generating a configuration file of each crash event according to the input information of the user aiming at the crash events in the crash analysis report;
and the configuration file summarizing and coding submodule is used for summarizing and coding the configuration files of all the crash events to obtain the configuration file of the client.
The client crash processing device provided by the embodiment of the present invention can execute the client crash processing method provided by the third embodiment and the fourth embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example eight
Fig. 8 is a block diagram of a structure of a client crash processing apparatus according to an eighth embodiment of the present invention, and as shown in fig. 8, the client crash processing apparatus according to the eighth embodiment of the present invention may specifically include the following modules:
a configuration file receiving module 801, configured to receive, by a configuration server, a configuration file of a client sent by a monitoring server, where the configuration file is a file generated by the monitoring server according to crash information sent by the client;
a profile request module 802, configured to receive a profile request of the client;
a second configuration file sending module 803, configured to send the configuration file to the client, where the client is configured to process a crash event according to the configuration file.
The client crash processing device provided by the embodiment of the invention can execute the client crash processing method provided by the fifth embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example nine
Fig. 9 is a block diagram of a client crash processing system according to a ninth embodiment of the present invention, and as shown in fig. 9, the client crash processing system according to the ninth embodiment of the present invention may specifically include a client 901, a monitoring server 902, and a configuration server 903, where the client 901 is respectively in communication with the monitoring server 902 and the configuration server 903, and the monitoring server 902 is in communication with the configuration server 903.
The client 901 is configured to execute the client crash processing method provided in the first embodiment or the second embodiment of the present invention, the monitoring server 902 is configured to execute the client crash processing method provided in the third embodiment or the fourth embodiment of the present invention, and the configuration server 903 is configured to execute the client crash processing method provided in the fifth embodiment of the present invention.
The client crash processing system provided by the embodiment of the invention can execute the client crash processing method provided by the embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
Example nine
Referring to fig. 10, a schematic diagram of the structure of an apparatus in one example of the invention is shown. As shown in fig. 10, the apparatus may specifically include: a processor 1000, a memory 1001, a display 1002 with a touch function, an input device 1003, an output device 1004, and a communication device 1005. The number of the processors 1000 in the device may be one or more, and one processor 1000 is taken as an example in fig. 10. The processor 1000, the memory 1001, the display 1002, the input device 1003, the output device 1004, and the communication device 1005 of the apparatus may be connected by a bus or by other means, and the bus connection is exemplified in fig. 1000.
An embodiment of the present invention further provides a computer-readable storage medium, where instructions in the storage medium, when executed by a processor of a device, enable the device to perform the client crash processing method according to the foregoing method embodiment.
It should be noted that, as for the apparatus, system, device, and storage medium embodiments, since they are substantially similar to the method embodiments, the description is simple, and in the relevant places, reference may be made to the partial description of the method embodiments.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (17)
1. A client crash processing method is characterized by comprising the following steps:
when a crash event is monitored in the operation process of a client, determining whether a configuration file for the crash event is acquired;
if yes, processing a crash event of the client according to the configuration file;
if not, acquiring the crash information of the crash event;
and sending the crash information to a monitoring server, wherein the monitoring server is used for generating a configuration file of the client according to the crash information and sending the configuration file to a configuration server.
2. The method of claim 1, wherein when a crash event is monitored during the operation of the client, before determining whether to acquire a configuration file for the crash event, further comprising:
sending a configuration file request to the configuration server according to a preset period;
and after receiving the configuration file returned by the configuration server, storing the configuration file into a local memory.
3. The method of claim 1, wherein determining whether to obtain a configuration file for a crash event when the crash event is monitored during operation of the client comprises:
determining a crash identification code of the crash event, wherein the crash identification code is a unique identification code of the client side when the crash event occurs;
determining whether a configuration file matching the crash identification code is stored in a local memory.
4. The method of claim 3, wherein processing the crash event of the client according to the configuration file comprises:
analyzing the configuration file to obtain a crash processing strategy corresponding to the version of the client;
and processing the crash event of the client by adopting the crash processing strategy.
5. The method of any of claims 1-4, wherein obtaining crash information for the crash event comprises:
when the client calls a crash event capture function, hooking the crash event capture function through a hook function;
and acquiring crash information through the crash event capture function.
6. The method of any of claims 1-4, wherein the crash information comprises at least one of:
version information of a client, operating environment information of the client, and description information of the crash event.
7. A client crash processing method is characterized by comprising the following steps:
the monitoring server receives crash information sent by the client;
generating a crash analysis report of the client according to the crash information;
generating a configuration file of the client according to the crash analysis report;
and sending the configuration file to a configuration server, wherein the configuration server is used for sending the configuration file to the client when receiving a configuration file request of the client.
8. The method of claim 7, wherein generating a crash analysis report for the client based on the crash information comprises:
extracting version information of the client from the crash information;
and generating crash analysis reports of the clients of all versions.
9. The method of claim 7 or 8, wherein the crash analysis report comprises at least one of:
version information of the client, crash event type, crash probability, and crash level.
10. The method of claim 7 or 8, wherein generating the configuration file of the client according to the crash analysis report comprises:
generating a configuration file of each crash event according to the input information of the crash event in the crash analysis report form by the user;
and summarizing and coding the configuration files of all the crash events to obtain the configuration file of the client.
11. A client crash processing method is characterized by comprising the following steps:
a configuration server receives a configuration file of a client sent by a monitoring server, wherein the configuration file is a file generated by the monitoring server according to crash information sent by the client;
receiving a configuration file request of the client;
and sending the configuration file to the client, wherein the client is used for processing a crash event according to the configuration file.
12. A client crash processing apparatus, comprising:
the judging module is used for determining whether a configuration file aiming at a crash event is acquired or not when the crash event is monitored in the operation process of the client;
the crash event processing module is used for processing the crash event of the client according to the configuration file;
the crash information acquisition module is used for acquiring crash information of the crash event;
and the crash information sending module is used for sending the crash information to a monitoring server, and the monitoring server is used for generating a configuration file of the client according to the crash information and sending the configuration file to a configuration server.
13. A client crash processing apparatus, comprising:
the crash information receiving module is used for monitoring the crash information sent by the server receiving client;
the crash analysis report generation module is used for generating a crash analysis report of the client according to the crash information;
the configuration file generation module is used for generating the configuration file of the client according to the crash analysis report;
the first configuration file sending module is used for sending the configuration file to a configuration server, and the configuration server is used for sending the configuration file to the client when receiving a configuration file request of the client.
14. A client crash processing apparatus, comprising:
the configuration file receiving module is used for receiving a configuration file of a client side sent by a monitoring server by a configuration server, wherein the configuration file is a file generated by the monitoring server according to the crash information sent by the client side;
the configuration file request module is used for receiving a configuration file request of the client;
and the second configuration file sending module is used for sending the configuration file to the client, and the client is used for processing a crash event according to the configuration file.
15. A client crash processing system is characterized by comprising a client, a monitoring server and a configuration server, wherein the client is respectively communicated with the monitoring server and the configuration server;
the client is configured to execute the client crash handling method according to any one of claims 1 to 6, the monitoring server is configured to execute the client crash handling method according to any one of claims 7 to 10, and the configuration server is configured to execute the client crash handling method according to claim 11.
16. An apparatus, characterized in that the apparatus comprises:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the client crash handling method of any of claims 1-11.
17. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, implements a client crash handling method according to any one of claims 1-11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010183705.7A CN111416857A (en) | 2020-03-16 | 2020-03-16 | Client crash processing method, device, system, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010183705.7A CN111416857A (en) | 2020-03-16 | 2020-03-16 | Client crash processing method, device, system, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111416857A true CN111416857A (en) | 2020-07-14 |
Family
ID=71493069
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010183705.7A Pending CN111416857A (en) | 2020-03-16 | 2020-03-16 | Client crash processing method, device, system, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111416857A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112437152A (en) * | 2020-11-20 | 2021-03-02 | 北京百度网讯科技有限公司 | Crash processing method and device, electronic equipment and storage medium |
| CN112527543A (en) * | 2020-10-27 | 2021-03-19 | 百果园技术(新加坡)有限公司 | Client starting exception handling method and device, electronic equipment and storage medium |
| CN112965942A (en) * | 2021-03-29 | 2021-06-15 | 深圳市广和通无线股份有限公司 | Memory dump file analysis method, device and equipment and computer storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103246578A (en) * | 2013-05-23 | 2013-08-14 | 北京奇虎科技有限公司 | Method and browser for processing collapse of application software |
| CN110445632A (en) * | 2018-05-04 | 2019-11-12 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus for preventing client collapse |
-
2020
- 2020-03-16 CN CN202010183705.7A patent/CN111416857A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103246578A (en) * | 2013-05-23 | 2013-08-14 | 北京奇虎科技有限公司 | Method and browser for processing collapse of application software |
| CN110445632A (en) * | 2018-05-04 | 2019-11-12 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus for preventing client collapse |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112527543A (en) * | 2020-10-27 | 2021-03-19 | 百果园技术(新加坡)有限公司 | Client starting exception handling method and device, electronic equipment and storage medium |
| CN112437152A (en) * | 2020-11-20 | 2021-03-02 | 北京百度网讯科技有限公司 | Crash processing method and device, electronic equipment and storage medium |
| CN112965942A (en) * | 2021-03-29 | 2021-06-15 | 深圳市广和通无线股份有限公司 | Memory dump file analysis method, device and equipment and computer storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110647438B (en) | Event monitoring method and device, computer equipment and storage medium | |
| CN107704360B (en) | Monitoring data processing method, equipment, server and storage medium | |
| CN107451040B (en) | Method and device for positioning fault reason and computer readable storage medium | |
| CN111416857A (en) | Client crash processing method, device, system, equipment and storage medium | |
| CN109672580B (en) | Full link monitoring method, device, terminal equipment and storage medium | |
| CN108804215B (en) | Task processing method and device and electronic equipment | |
| CN111193609B (en) | Application abnormity feedback method and device and application abnormity monitoring system | |
| CN111459770A (en) | Server operation state warning method and device, server and storage medium | |
| CN110674440A (en) | Buried point data processing method, system, computer device and readable storage medium | |
| CN111158715B (en) | Gray release control method and system | |
| CN110851159B (en) | Business rule updating method and device, computer equipment and storage medium | |
| CN109543891B (en) | Method and apparatus for establishing capacity prediction model, and computer-readable storage medium | |
| CN108415998B (en) | Application dependency relationship updating method, terminal, device and storage medium | |
| CN110569222A (en) | link tracking method and device, computer equipment and readable storage medium | |
| CN111190573A (en) | Application program point burying method and device and electronic equipment | |
| CN112799925A (en) | Data acquisition method and device, electronic equipment and readable storage medium | |
| CN111680104B (en) | Data synchronization method, device, computer equipment and readable storage medium | |
| CN108509322B (en) | Method for avoiding excessive return visit, electronic device and computer readable storage medium | |
| CN113254217A (en) | Service message processing method and device and electronic equipment | |
| CN115543827A (en) | Buried point data display method and device | |
| CN115001967A (en) | Data acquisition method and device, electronic equipment and storage medium | |
| CN113238815A (en) | Interface access control method, device, equipment and storage medium | |
| CN112667272A (en) | Ammeter upgrading method and system, intelligent ammeter and storage medium | |
| CN109298928B (en) | Service processing method and device | |
| CN114385457A (en) | Application program data acquisition method, device, equipment 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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200714 |