A data processing method and related device

Abstract

Embodiments of the present application disclose a data processing method and related devices. The method includes: when starting a mini-program in a target application, receiving first-type service data returned by a service server corresponding to the mini-program; rendering and outputting the first-type service data to a rendering display interface corresponding to the mini-program, and recording a rendering display duration of rendering the first-type service data in the rendering display interface; when the rendering display duration reaches a delay detection duration, obtaining feature elements on the rendering display interface; and when the feature elements on the rendering display interface meet a white screen detection condition, restarting the mini-program in the target application. By using the present application, the efficiency of restarting the mini-program can be improved.

Description

Technical Field

[0001] This application relates to the field of Internet technologies, and in particular, to a data processing method and related devices. Background Art

[0002] In the prior art, due to the inherent defects in the development process of mini-programs, a white screen phenomenon will occur during the process of loading the mini-program in the target application. However, in the prior art, to solve this white screen phenomenon, it is often necessary to forcefully exit the target application to terminate the white screen loading of the mini-program. As a result, when the user restarts the mini-program next time, they need to first re-access the application interface of the target application, and then trigger the icon of the mini-program in the application interface of the target application to implement the restart function of the mini-program. Thus, it can be seen that the prior art consumes a long human-computer interaction time during the process of restarting the mini-program, resulting in a low cold start efficiency of the mini-program.

[0003] Application Content

[0004] Embodiments of this application provide a data processing method and related devices, which can improve the restart efficiency of mini-programs.

[0005] One aspect of the embodiments of this application provides a data processing method, including:

[0006] When starting a mini-program in a target application, receiving first-type service data returned by a service server corresponding to the mini-program;

[0007] Rendering and outputting the first-type service data to a rendering display interface corresponding to the mini-program, and recording a rendering display duration of rendering the first-type service data in the rendering display interface;

[0008] When the rendering display duration reaches a delay detection duration, obtaining characteristic elements on the rendering display interface;

[0009] When the characteristic elements on the rendering display interface meet a white screen detection condition, restarting the mini-program in the target application.

[0010] Among them, when starting a mini-program in a target application and receiving first-type service data returned by a service server corresponding to the mini-program, it includes:

[0011] Logging in to the target application through the user account information of the target user, and displaying the mini-program in a mini-program display interface of the target application;

[0012] Responding to a trigger operation triggered for the mini-program, starting the mini-program in the target application, and jumping the mini-program display interface to the rendering display interface corresponding to the mini-program;

[0013] Send a data loading request to the business server corresponding to the applet;

[0014] Receive the first type of business data returned by the business server based on the data loading request.

[0015] Wherein, the method further includes:

[0016] When starting the applet in the target application, obtain the white screen detection mechanism associated with the applet;

[0017] Write the white screen detection code information corresponding to the white screen detection mechanism into the applet;

[0018] Trigger the timer corresponding to the applet, and determine the delay detection duration through the timer.

[0019] Wherein, before sending the data loading request to the business server corresponding to the applet, it further includes:

[0020] Use the static loading data corresponding to the applet as the second type of business data, and statically display the second type of business data on the rendering display interface;

[0021] Then the obtaining of the feature elements on the rendering display interface includes:

[0022] Use the pixel points of the first type of business data and the pixel points of the second type of business data on the rendering display interface as the feature elements on the full-screen display area of the rendering display interface.

[0023] Wherein, the feature elements on the rendering display interface include the pixel points of the first type of business data on the local key area; the local key area is located in the rendering display interface;

[0024] The method further includes:

[0025] In the rendering display interface, perform dot reporting on the number of pixel points of the first type of business data on the local key area, and use the number of dot reports as the first number associated with the local key area;

[0026] When the first number does not reach the first rendering threshold corresponding to the local key area, determine that the feature elements on the rendering display interface meet the white screen detection conditions.

[0027] Wherein, the method further includes:

[0028] In the rendering display interface, accumulate the pixel points of the first type of business data on the full-screen display area to obtain a first accumulated value;

[0029] Accumulate the pixel points of the second type of service data on the full-screen display area to obtain a second cumulative value;

[0030] Use the sum of the first cumulative value and the second cumulative value as the second quantity associated with the full-screen display area;

[0031] When the second quantity does not reach the second rendering threshold corresponding to the full-screen display area, determine that the characteristic elements on the rendering display interface meet the white screen detection condition.

[0032] Among them, when the characteristic elements on the rendering display interface meet the white screen detection condition, restarting the applet in the target application includes:

[0033] When the characteristic elements on the rendering display interface meet the white screen detection condition, generate a white screen prompt message corresponding to the applet;

[0034] Output the white screen prompt message to a sub-display interface independent of the rendering display interface;

[0035] Respond to the restart operation triggered for the sub-display interface, and obtain the restart interface corresponding to the applet based on the restart operation;

[0036] Call the restart interface in the target application to restart the applet.

[0037] Among them, the method further includes:

[0038] Obtain the user account information of the target application, and generate restart record information based on the user account information and the call timestamp of the restart interface; at least the following key information associated with the white screen of the applet is included in the restart record information: the version information of the target application, the operation coefficient information of the terminal where the target application is located, and the device type information of the terminal;

[0039] Send the restart record information and the user account information to the development terminal associated with the applet, so that the development terminal analyzes the restart record information.

[0040] Among them, the method further includes:

[0041] Respond to the cancel operation triggered for the sub-display interface, and close the sub-display interface based on the cancel operation;

[0042] Generate feedback information corresponding to the cancel operation based on the user account information of the target application;

[0043] Send the feedback information to the development terminal associated with the applet, so that the development terminal adjusts and analyzes the white screen detection mechanism corresponding to the applet based on the feedback information.

[0044] One aspect of the embodiments of the present application provides a data processing device, including:

[0045] An applet startup module, configured to receive the first type of service data returned by the service server corresponding to the applet when starting the applet in the target application;

[0046] A rendering output module, configured to render and output the first type of service data to the rendering display interface corresponding to the applet, and record the rendering display duration of rendering the first type of service data in the rendering display interface;

[0047] An element acquisition module, configured to acquire the characteristic elements on the rendering display interface when the rendering display duration reaches the delay detection duration;

[0048] An applet restart module, configured to restart the applet in the target application when the characteristic elements on the rendering display interface meet the white screen detection conditions.

[0049] Wherein, the applet startup module includes:

[0050] An application login unit, configured to log in to the target application through the user account information of the target user, and display the applet in the applet display interface of the target application;

[0051] An interface jump unit, configured to start the applet in the target application in response to a trigger operation triggered for the applet, and jump the applet display interface to the rendering display interface corresponding to the applet;

[0052] A request sending unit, configured to send a data loading request to the service server corresponding to the applet;

[0053] A service data receiving unit, configured to receive the first type of service data returned by the service server based on the data loading request.

[0054] Wherein, the applet startup module further includes:

[0055] A detection mechanism acquisition unit, configured to acquire the white screen detection mechanism associated with the applet when starting the applet in the target application;

[0056] A code writing unit, configured to write the white screen detection code information corresponding to the white screen detection mechanism into the applet;

[0057] A timer trigger unit for triggering a timer corresponding to the applet and determining a delay detection duration through the timer.

[0058] Among them, the applet startup module further includes:

[0059] A static loading unit for taking the static loading data corresponding to the applet as the second type of service data and statically displaying the second type of service data on the rendering display interface;

[0060] Then, the element acquisition module is used to, when the rendering display duration reaches the delay detection duration, take the pixel points of the first type of service data and the pixel points of the second type of service data on the rendering display interface as feature elements on the full-screen display area of the rendering display interface.

[0061] Among them, the feature elements on the rendering display interface include the pixel points of the first type of service data in a local key area; the local key area is located in the rendering display interface;

[0062] The device further includes:

[0063] A dot reporting module for dot reporting the number of pixel points of the first type of service data in the local key area in the rendering display interface and taking the dot-reported number as a first number associated with the local key area;

[0064] A first determination module for determining that the feature elements on the rendering display interface meet the white screen detection condition when the first number does not reach a first rendering threshold corresponding to the local key area.

[0065] Among them, the device further includes:

[0066] A first accumulation module for accumulating the pixel points of the first type of service data in the full-screen display area in the rendering display interface to obtain a first accumulation value;

[0067] A second accumulation module for accumulating the pixel points of the second type of service data in the full-screen display area to obtain a second accumulation value;

[0068] A quantity determination module for taking the sum of the first accumulation value and the second accumulation value as a second number associated with the full-screen display area;

[0069] A second determination module for determining that the feature elements on the rendering display interface meet the white screen detection condition when the second number does not reach a second rendering threshold corresponding to the full-screen display area.

[0070] Among them, the applet restart module includes:

[0071] A prompt information generation unit, configured to generate a white screen prompt information corresponding to the applet when a feature element on the rendering display interface meets the white screen detection condition;

[0072] A prompt information output unit, configured to output the white screen prompt information to a sub-display interface independent of the rendering display interface;

[0073] An interface acquisition unit, configured to respond to a restart operation triggered for the sub-display interface, and acquire a restart interface corresponding to the applet based on the restart operation;

[0074] An interface invocation unit, configured to invoke the restart interface in the target application to restart the applet.

[0075] Wherein, the device further includes:

[0076] A restart record generation module, configured to acquire user account information of the target application, and generate restart record information based on the user account information and a call timestamp of the restart interface; at least the following key information associated with the white screen of the applet is included in the restart record information: version information of the target application, operation coefficient information of the terminal where the target application is located, and device type information of the terminal;

[0077] A restart record sending module, configured to send the restart record information and the user account information to a development terminal associated with the applet, so that the development terminal performs data analysis on the restart record information.

[0078] Wherein, the device further includes:

[0079] A sub-interface closing module, configured to respond to a cancellation operation triggered for the sub-display interface, and close the sub-display interface based on the cancellation operation;

[0080] A feedback information generation module, configured to generate feedback information corresponding to the cancellation operation based on the user account information of the target application;

[0081] A feedback information sending module, configured to send the feedback information to a development terminal associated with the applet, so that the development terminal adjusts and analyzes a white screen detection mechanism corresponding to the applet based on the feedback information.

[0082] On the one hand, the present application provides a computer device, including: a processor, a memory, and a network interface;

[0083] The processor is connected to a memory and a network interface. The network interface is used to provide data communication functions. The memory is used to store computer programs. The processor is used to call the computer programs to execute the method in the above-mentioned aspect of the embodiments of the present application.

[0084] In one aspect, the present application provides a computer-readable storage medium storing a computer program, where the computer program includes program instructions, and when the program instructions are executed by a processor, the method in the above-mentioned aspect of the embodiments of the present application is executed.

[0085] In the embodiments of the present application, when starting a mini-program in a target application, the first type of service data returned by the service server corresponding to the mini-program can be received; further, the first type of service data is rendered and output to the rendering display interface corresponding to the mini-program, and the rendering display duration of rendering the first type of service data in the rendering display interface is recorded; further, when the rendering display duration reaches the delay detection duration, the feature elements on the rendering display interface are obtained; further, when the feature elements on the rendering display interface meet the white screen detection conditions, the mini-program is restarted in the target application. It can be seen that the present application can start the white screen detection of the feature elements on the rendering display interface when the current time (i.e., the rendering display duration) reaches the delay detection duration, so as to quickly determine whether the feature elements on the rendering display interface meet the white screen detection conditions. If so, without exiting the target application (such as the WeChat application), the mini-program can be quickly restarted in the target application, so as to quickly implement the restart operation of the mini-program, and thus the restart efficiency of the mini-program can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0086] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0087] Figure 1 It is a schematic structural diagram of a network architecture provided by the embodiments of the present application;

[0088] Figure 2 It is a schematic diagram of a scenario for rendering service data in a rendering display interface provided by the embodiments of the present application;

[0089] Figure 3 It is a schematic flowchart of a data processing method provided by the embodiments of the present application;

[0090] Figure 4It is a schematic diagram of a scenario for obtaining a mini-program display interface provided by an embodiment of the present application;

[0091] Figure 5 It is a timing diagram showing the change of feature elements on the rendered display interface over time provided by an embodiment of the present application;

[0092] Figure 6 It is a schematic diagram of a scenario where a full white screen phenomenon occurs during page loading provided by an embodiment of the present application;

[0093] Figure 7 It is a schematic flowchart of another data processing method provided by an embodiment of the present application;

[0094] Figure 8 It is a schematic diagram of a scenario of a partial white screen phenomenon provided by an embodiment of the present application;

[0095] Figure 9 It is a schematic flowchart of the overall process of white screen detection and white screen recovery provided by an embodiment of the present application;

[0096] Figure 10 It is a schematic diagram of a scenario for restarting a mini-program provided by an embodiment of the present application;

[0097] Figure 11 It is a schematic structural diagram of a data processing device provided by an embodiment of the present application;

[0098] Figure 12 It is a schematic diagram of a computer device provided by an embodiment of the present application. Detailed implementation manners

[0099] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0100] Please refer to Figure 1 , which is a schematic structural diagram of a network architecture provided by an embodiment of the present application. As Figure 1 shown, the network architecture may include a service server 2000 and a user terminal cluster; the user terminal cluster may include multiple user terminals. As Figure 1 shown, specifically, it includes user terminals 3000a, 3000b,..., 3000n; as Figure 1 shown, the user terminals 3000a, 3000b,..., 3000n can all be network-connected to the service server 2000.

[0101] Among them, as Figure 1 shown, each user terminal can be integrally installed with a target application, and one or more mini-programs can be embedded in the target application. In the embodiments of the present application, each mini-program can be collectively referred to as the mini-program of the target application, or the sub-application of the target application.

[0102] Among them, it can be understood that with the development of Internet technology, mini-programs have emerged as the times require. The so-called mini-program (MiniProgram) is an application program that can be used without being downloaded and installed. In order to provide users with more diverse business services, developers can develop corresponding mini-programs for the target application of the terminal (such as instant messaging applications, shopping applications, email applications, etc.). The mini-program can be embedded into the target application of the terminal as a sub-application, and by running the sub-application (i.e., the corresponding mini-program) in the target application, corresponding business services can be provided for users.

[0103] For ease of understanding, in the embodiments of the present application, one user terminal can be selected from the Figure 1 shown multiple user terminals as the target user terminal. For example, the Figure 1 shown user terminal 3000a can be used as the target user terminal. Among them, it can be understood that the target user terminal can specifically include a mobile phone, a tablet computer, a notebook computer, a palm computer, a mobile internet device (MID), a wearable device (such as a smart watch, a smart bracelet, etc.).

[0104] For example, user A can quickly obtain and start a certain mini-program (such as the WeChat Reading mini-program) in the user terminal 3000a (i.e., the target user terminal) running the target application by means of scanning or searching, etc. Thus, when starting the mini-program in the target application, corresponding business data can be further obtained from the business server 2000 associated with the mini-program, and then the obtained business data can be rendered and output to the screen of the user terminal 3000a for display.

[0105] For another example, user A can also quickly obtain the mini-programs most recently used by user A through a pull-down operation on the home page of the target application, so as to quickly switch the home page of the target application to the display interface of the mini-program most recently used by user A. For ease of understanding, in the embodiments of the present application, the display interface where the mini-program is located can be collectively referred to as the mini-program display interface.

[0106] Among them, it can be understood that the business data obtained from the business server 2000 in the embodiments of the present application can be referred to as the first type of business data, and the first type of business data can be business data that needs to be dynamically loaded. Therefore, for different users using the above-mentioned applet, the first type of business data dynamically filled on the rendering display interface can be different. It can be understood that when the user terminal 3000a corresponding to user A (i.e., the target user terminal) starts the above-mentioned applet (i.e., the WeChat Reading applet), it can also load the static loading data corresponding to the applet (for example, the business data that needs to be statically loaded corresponding to the applet, for example, the text and function buttons at specified positions), and these statically loaded business data can be referred to as the second type of business data. Among them, it can be understood that for the data that needs to be statically loaded, it can be directly displayed on the rendering display page corresponding to the applet when starting the applet. The embodiments of the present application can also refer to the rendering display page as the initialization page of the applet. At this time, the user terminal can continuously render and output the business data obtained from the business server on the initialization page.

[0107] Among them, it can be understood that due to the inherent defects in the development process of the applet, it will cause a white screen phenomenon during the loading of the applet. Among them, it can be understood that the white screen of the applet in the embodiments of the present application can be specifically divided into two categories, one is a full white screen, and the other is a partial white screen.

[0108] Among them, a full white screen means that there are no characteristic elements in the specified area corresponding to the applet; in addition, a partial white screen means that there are missing characteristic elements in the specified area corresponding to the applet, which will affect the user's visual experience of the applet. Based on this, the embodiments of the present application provide a white screen detection mechanism, which can start white screen detection when the rendering display duration of the applet reaches the delay detection duration (which can also be referred to as the white screen detection duration), so as to further count the characteristic elements on the rendering display interface (i.e., the above-mentioned initialization page). It can be understood that the specified area described in the embodiments of the present application can be a local key area in the rendering display interface, or a full-screen display area, and no limitation will be imposed here.

[0109] Among them, it can be understood that the feature elements on the rendering display interface may include the pixel points of the first type of service data in the local key area; optionally, the feature elements on the rendering display interface may also include the pixel points of the first type of service data and the pixel points of the second type of service data in the full-screen display area. It should be understood that the embodiments of the present application may collectively refer to the local key area and the full-screen display area as the pixel statistics area (i.e., the above-mentioned specified area). Thus, during the process of counting the feature elements on the above-mentioned rendering display interface, intelligent counting can be performed based on the white screen detection mechanism of the applet, and further, when it is detected that there is a white screen in the specified area on the rendering display interface, the white screen of the applet can be quickly restored through the white screen recovery mechanism, so as to quickly restart the applet without pushing the target application.

[0110] Among them, it can be understood that when the target user terminal counts the feature elements on the above-mentioned rendering display interface under the above-mentioned extended detection duration, it can further determine whether there are missing pixel points in the pixel statistics area, and when it is determined that there are missing pixel points in the pixel statistics area, it can be determined that the feature elements on the rendering display interface meet the white screen detection conditions. Further, without exiting the target application, the applet can be quickly restarted in the target application to improve the efficiency of applet restart.

[0111] For ease of understanding, the embodiments of the present application take the pixel statistics area as the local key area as an example to elaborate on the specific process of white screen detection and white screen recovery in the target user terminal. Further, please refer to Figure 2 , which is a schematic diagram of a scenario for rendering service data in the rendering display interface provided by the embodiments of the present application. As Figure 2 shown, the applet display interface 100a can be Figure 2 a display interface in the target application (for example, WeChat application) shown. The applet display interface 100a may include multiple applets. For example, it may include multiple applets used by the target user before. Among them, the multiple applets may specifically include Figure 2 the applets A1, A2,..., A3 shown. It should be understood that the embodiments of the present application will not limit the specific distribution form of these applets displayed in the applet display interface 100a.

[0112] As Figure 2 shown, the target user can perform a click operation on the applet A3 in the applet display interface 100a, so as to send a data loading request to the service server corresponding to the applet A3 (i.e., Figure 2 the service server shown), and thus can receive Figure 2 the first type of service data returned by the service server shown, and can be inFigure 2 The first type of business data is rendered and displayed in the rendering display interface 200a shown. Figure 2 The first type of business data is displayed in the local key area 10a shown.

[0113] It can be understood that when the above-mentioned applet A3 is run in the target user terminal, the target user terminal can obtain the white screen detection mechanism associated with the applet A3. For example, the white screen detection mechanism is to start the white screen detection when the current time (i.e., the rendering display duration of the current rendering display interface 200a) reaches the white screen detection duration. Figure 2 The number of pixel points of the first type of business data in the local key area 10a is counted (for example, the first number) to determine whether the first number in the local key area 10a reaches the first rendering threshold corresponding to the local key area 10a. It can be understood that the first rendering threshold corresponding to the key area 10a can be the total number of pixel points when the cluster key area 10a is completely rendered and filled. Optionally, the first rendering threshold can also be 80% of the aforementioned total number, which will not be specifically limited here.

[0114] It is understandable that when Figure 2 When the first number in the local key area 10a shown does not reach the first rendering threshold corresponding to the local key area 10a, for example, when the value of the first number is not zero and is less than the first rendering threshold, the target user terminal can determine that the feature elements on the local key area 10a on the rendering display interface are missing. Figure 2 The loading of picture data such as picture 1 in business data 20a, picture 2 in business data 20b, and picture 3 in business data 20c shown in the figure causes the first number of pixel points of the first type of business data loaded in the local key area 10a to fail to reach the above-mentioned first rendering threshold. At this time, the target user terminal can determine that there is a partial white screen phenomenon in the rendering display interface 200a, and then restart the applet A3 in the target application to complete the loading of picture data such as picture 1 in business data 20a, picture 2 in business data 20b, and picture 3 in business data 20c in the new rendering display interface.

[0115] It can be understood that when the mini-program A3 in the target user terminal detects abnormal phenomena such as partial white screen or full white screen in the rendering display interface 200a (for example, the number of feature elements in the aforementioned full-screen display area is zero), a white screen prompt window can be displayed on the floating window (i.e., pop-up window) of the rendering display interface. Thus, a click operation (which can also be referred to as a trigger operation) can be performed on the retry button in the white screen prompt window, and then the restart interface corresponding to the mini-program A3 can be called to restart the mini-program A3. It can be understood that in the embodiment of the present application, when restarting the mini-program A3 in the target application, the restart record information corresponding to the restart operation can also be given to the development terminal associated with the mini-program, so that the development terminal can perform data analysis on the key information associated with the white screen in the restart record information (such as the version information of the target application, the operation coefficient information of the target user terminal, and the device type information of the target user terminal, etc.). For example, when developers find that the proportion of users with white screens in the Android version under a certain device type is relatively large, they can specifically optimize the Android version and the mini-program A3 under this device type to reduce the possibility of white screens occurring, thereby improving the user experience of the mini-program A3.

[0116] It should be understood that for the other mini-programs in the mini-program display interface 100a shown above Figure 2 if there are also abnormal phenomena such as white screens after being started in the target application, the specific process of restarting the mini-program A3 in the target application described above can be uniformly referred to, and details will not be elaborated here. In addition, it can be understood that the specific process of detecting white screens for the running mini-programs in the target application can also be uniformly referred to the description of the specific process of detecting white screens for the mini-program A3 in the target application, and details will not be elaborated here.

[0117] Among them, the specific processes of the target user terminal starting the mini-program, obtaining the feature elements on the rendering display interface, and restarting the mini-program in the target application can be referred to the implementation methods provided in the following Figures 3 to 10 corresponding embodiments.

[0118] Further, please refer to Figure 3 , which is a schematic flowchart of a data processing method provided by an embodiment of the present application. As Figure 3 shown, the method provided by the embodiment of the present application may include:

[0119] Step S101, when starting a mini-program in a target application, receive first-type service data returned by a service server corresponding to the mini-program;

[0120] Specifically, the user terminal can log in to the target application through the user account information of the target user, and display the applet in the applet display interface of the target application; further, the user terminal can respond to the trigger operation triggered for the applet, start the applet in the target application, and jump the applet display interface to the rendering display interface corresponding to the applet; further, the user terminal can send a data loading request to the business server corresponding to the applet; further, the user terminal can receive the first type of business data returned by the business server based on the data loading request.

[0121] Among them, it can be understood that the user terminal in the embodiments of the present application can be the target user terminal in the corresponding embodiments above, and the applet in the embodiments of the present application can be the applet described in the corresponding embodiments above. Figure 2 Among them, it can be understood that the user terminal in the embodiments of the present application can be the target user terminal in the corresponding embodiments above, and the applet in the embodiments of the present application can be the applet described in the corresponding embodiments above. Figure 1 Among them, it can be understood that the user terminal in the embodiments of the present application can be the target user terminal in the corresponding embodiments above, and the applet in the embodiments of the present application can be the applet described in the corresponding embodiments above.

[0122] Among them, the applet described in the embodiments of the present application can specifically include at least one of the following applets, for example, e-reading applets, entertainment application applets, shopping application applets, video application applets, etc., which will not be limited here.

[0123] For ease of understanding, in the embodiments of the present application, taking the target application as the WeChat application as an example, after the target user logs in to the WeChat application through his own account information, he can further quickly obtain the corresponding applet in the target application through functions such as scanning or searching. For example, in a shopping scenario, the target user can use the scanning function in the WeChat application to scan the QR code picture provided by merchant A to quickly start the online mall applet (i.e., the above-mentioned shopping application applet) corresponding to merchant A. Another example is that in a food ordering scenario, the target user can use the scanning function in the WeChat application to quickly start the food ordering and placing order applet corresponding to merchant B. Another example is that in a scenario of mailing express delivery, the target user can quickly start the online form filling applet through the search function.

[0124] It can be understood that after the target user has used the above-mentioned online mall applet, food ordering and placing order applet, and online form filling applet, the user terminal running the target application can output these applets (i.e., applets) in sequence as the applets most recently used by the target user to the historical operation interface of the target application (i.e., the WeChat application) (at this time, this historical operation interface can be called the applet display interface). In this way, when the user needs to use these applets later, he can directly switch the home page of the WeChat application to the applet display interface where these applets are located through the pull-down operation function on the home page of the WeChat application.

[0125] Among them, for ease of understanding, further, please refer toFigure 4 , which is a schematic diagram of a scenario for obtaining a mini-program display interface provided by an embodiment of the present application. As Figure 4 shown in the application display interface 400a, it may include multiple applications. Specifically, the multiple applications may include Application B1, Application B2, Application B3, ..., Application B6. For ease of understanding, in the embodiment of the present application, Figure 4 taking the Application B6 shown as the target application. The target application may be the WeChat application mentioned above. As Figure 4 shown, the target user may perform a trigger operation on the Application B6 (i.e., the target application) in the application display interface 400a, so as to log in to the Application B6 through the user account information of the target user, and thus the Figure 4 shown first operation interface 400b can be presented on the user terminal. It can be understood that the first operation interface 400b may be the home page of the target application. Further, as Figure 4 shown, the target user may perform a trigger operation on the search button in the first operation interface 400b to use the search function in the target application (i.e., the WeChat application) to enter the search page, so as to search for the mini-program to be launched on the search page. It can be understood that when the target user performs a trigger operation on the search button in the first operation interface 400b, the user terminal can Figure 4 adjust the first operation interface 400b shown to another operation interface (i.e., the Figure 4 shown second operation interface 400c, that is, the aforementioned search page).

[0126] As Figure 4 shown, the target user may enter the aforementioned mini-program to be launched in the search area of the second operation interface 400c. For ease of understanding, in the embodiment of the present application, taking the mini-program to be launched as an e-reading application (for example, the WeChat Reading mini-program) as an example, so that the Figure 4 shown mini-program display interface 400d can display the mini-program to be launched (i.e., the Figure 4 shown WeChat Reading mini-program). As Figure 4 shown, the target user may perform a trigger operation on the mini-program displayed in the mini-program display interface 400d to launch the WeChat Reading mini-program in the target application (i.e., the WeChat application). It can be understood that the WeChat Reading mini-program may be the mini-program A3 in the corresponding embodiment mentioned above. Figure 2

[0127] ​It can be understood that when the user terminal starts the WeChat Reading mini-program in the target application, the display interface 400d of the mini-program can be further adjusted to the rendering display interface corresponding to the mini-program. It should be understood that when the WeChat Reading mini-program starts, the user terminal can request the business server corresponding to the mini-program to load the corresponding business data, so that the requested and loaded business data can be rendered and output to the rendering display interface corresponding to the mini-program. At this time, the rendering display interface can be the initialization page of the WeChat Reading mini-program. It can be understood that in the embodiment of the present application, when the current time (i.e., the rendering display duration) reaches the delay detection duration, by counting the characteristic elements in the rendering display interface, white screen detection can be quickly performed, and then it can be quickly determined whether the normal loading of the page of the WeChat Reading mini-program is completed.

[0128] It can be understood that when the user terminal starts the mini-program (i.e., the WeChat Reading mini-program) in the target application, it can also obtain the white screen detection mechanism associated with the mini-program. Further, the user terminal can write the white screen detection code information corresponding to the white screen detection mechanism into the mini-program. Then, the user terminal can trigger the timer corresponding to the mini-program and determine the delay detection duration through the timer.

[0129] In other words, in the embodiment of the present application, the white screen detection mechanism can be registered during the page loading of the mini-program, that is, the white screen detection code information corresponding to the white screen detection mechanism is written into the mini-program, so that the white screen detection can be accurately triggered by the timer during the subsequent page loading process. It should be understood that by introducing the timer in the embodiment of the present application, pixel statistics can be avoided within the delay detection duration (for example, 2s). In addition, since the opening and network loading of the mini-program also require a certain amount of time, but this part of the time is not included in the white screen detection time range. Therefore, through the aforementioned timer, the embodiment of the present application allows the mini-program to perform white screen detection after 2s or 2s, thereby improving the accuracy of counting the characteristic elements on the rendering display interface.

[0130] Among them, the white screen detection is determined based on the white screen detection mechanism. In the embodiment of the present application, when starting the aforementioned WeChat Reading mini-program in the target application, the white screen detection code information corresponding to the white screen detection mechanism can be written into the WeChat Reading mini-program (i.e., the mini-program), so that through the white screen detection mechanism registered in the WeChat Reading mini-program, when the current time reaches the delay detection duration, it can be quickly determined whether there is a white screen phenomenon on the rendering display interface during the page loading process. If it is determined that there is a white screen phenomenon in the WeChat Reading mini-program during the page loading process, the white screen recovery mechanism can be used to quickly recover the white screen of the WeChat Reading mini-program to achieve the quick start of the WeChat Reading mini-program.

[0131] It should be understood that the white screen detection mechanism and the white screen recovery mechanism in the embodiments of the present application are also applicable to other applets embedded in the target application (for example, the above-mentioned shopping application applets), and will not be limited here.

[0132] Step S102: Render and output the first type of service data to the rendering display interface corresponding to the applet, and record the rendering display duration of rendering the first type of service data in the rendering display interface.

[0133] It can be understood that during the process of the user terminal rendering and displaying the first type of service data on the rendering display interface, the rendering display duration of rendering the first type of service data will be recorded, so that when the rendering display duration reaches the delay detection duration corresponding to the white screen detection mechanism in the applet, step S103 can be further executed.

[0134] For ease of understanding, further, please refer to Figure 5 , which is a timing diagram showing the change of characteristic elements on the rendering display interface provided by the embodiments of the present application. As Figure 5 shown, the applet A3 as Figure 5 shown can be the WeChat Reading applet in the corresponding embodiment of the above Figure 4 . It can be understood that as shown in the above Figure 4 , when the target user performs a trigger operation on the WeChat Reading applet in the above-mentioned applet display interface 400d, the WeChat Reading applet can be started in the Figure 4 shown target application. At this time, the user terminal can render and output the first type of service data pulled from the business server corresponding to the WeChat Reading applet to the rendering display interface corresponding to the applet (i.e., the WeChat Reading applet) (for example, at the current moment T1, the first type of service data can be rendered and output to the Figure 5 shown local key area).

[0135] As Figure 5 shown, the display interfaces 600a, 600b, 600c, and 600d can be collectively referred to as the rendering display interfaces of the applet at different times. It can be understood that as the rendering display time progresses, the characteristic elements on the rendering display interface corresponding to the applet will also change continuously. Specifically, please refer to Figure 5Schematic diagrams of changes in characteristic elements on the rendering display interface corresponding to multiple moments (e.g., moment T1, moment T2, moment T3, moment T4) shown. It should be understood that to avoid wasting computing resources, in the embodiments of the present application, when the current time reaches the delay detection duration corresponding to the above timer, white screen detection can be triggered. That is, at this time, the user terminal can count the characteristic elements in the local key area on the rendering display interface when the current time reaches the delay detection duration.

[0136] Among them, as Figure 5 shown, when the current moment is moment T1, the display page 600a corresponding to the applet A3 can be called the initialization display interface (i.e., the above-mentioned initialization page), or the rendering display interface 1. In addition, as Figure 5 shown, when the current moment is moment T2, the display page 600b corresponding to the applet A3 can be called the rendering display interface 2. At this time, the rendering display interface 2 may include some newly loaded characteristic elements. In addition, as Figure 5 shown, when the current moment is moment T3, the display page 600c corresponding to the applet A3 can be called the rendering display interface 3. At this time, compared with the rendering display interface 2, the rendering display interface 3 has additionally loaded some new characteristic elements. In addition, as Figure 5 shown, when the current moment is moment T4, the display page 600d corresponding to the applet A3 can be called the rendering display interface 4. At this time, the rendering display interface 4 can be the rendering display interface when the page loading is completed.

[0137] Among them, it can be understood that when the user terminal renders the first type of service data in each rendering display page (i.e., the above-mentioned rendering display interface 1, rendering display interface 2, rendering display interface 3, rendering display interface 4), the corresponding rendering display duration can be recorded. For example, Figure 5 shown, moment T1 can be the rendering display duration 1 when rendering the first type of service data in the display interface 600a. Another example is that Figure 5 shown, moment T2 can be the rendering display duration 2 when rendering the first type of service data in the display interface 600b, and so on. The user terminal can continuously update the duration of rendering the first type of service data on the rendering display interface.

[0138] Step S103, when the rendering display duration reaches the delay detection duration, obtain the characteristic elements on the rendering display interface;

[0139] Among them, for ease of understanding, in the embodiments of the present application, taking the user terminal determining that when the rendering display duration (for example, moment T3 shown above) reaches the delay detection duration (e.g., 2 seconds) as an example, to elaborate on the above Figure 5 shownFigure 5 The specific process of pixel statistics in the display interface 600c shown above. As described above Figure 5 shown, at this time, the user terminal can obtain the above Figure 5 feature elements in the local key area on the display page 600c shown above. At this time, the feature elements in the local key area can be pixel points of the first type of service data. That is, the feature elements in the local key area can be service data dynamically loaded from the service server.

[0140] Among them, it can be understood that since the Figure 5 feature elements on the local key area in the display page 600c shown above are not fully loaded. Therefore, at this time, the applet A3 in the user terminal can detect that Figure 5 the number of pixel points of the first type of service data on the local key area shown above (i.e., the first number) does not reach the first rendering threshold corresponding to the local key area. That is, the user terminal can determine that there are missing elements in the specified area of the display interface 600c shown above, and thus can further execute step S104. It can be understood that the first rendering threshold in the embodiments of the present application can be the total number counted after fully rendering the pixel points in the Figure 5 local key area shown above. Figure 5 shown local key area.

[0141] It can be understood that before the user terminal determines that the feature elements on the rendering display interface meet the white screen detection conditions, the following steps can also be executed: perform dot reporting on the number of pixel points of the first type of service data on the local key area in the rendering display interface, and use the number of dot reporting as the first number associated with the local key area; when the first number does not reach the first rendering threshold corresponding to the local key area, determine that the feature elements on the rendering display interface meet the white screen detection conditions.

[0142] Among them, it should be understood that in the case of normal page loading, the user terminal can complete the rendering of the feature elements on the rendering display interface when the rendering display duration reaches the delay detection duration. That is, under normal circumstances, the number of feature elements counted on the rendering display interface should reach (for example, can be equal to) the aforementioned first rendering threshold. Therefore, once the user terminal determines that the number of feature elements on the rendering display interface does not reach the first rendering threshold, it can be determined that the feature elements on the rendering display interface meet the white screen detection conditions, and it can be indicated that there is an abnormal loading situation in the local key area on the rendering display interface. For example, there is a white screen phenomenon, and then step S104 needs to be continued to quickly implement the applet (for example, the above Figure 5Restart operation of the small program A3) shown above.

[0143] Optionally, it can be understood that, as shown in the timing diagram of the characteristic elements on the rendering display interface changing over time above, the local key area in the above display page 600a can be used to display the dynamically loaded data obtained from the business server (i.e., the dynamically loaded business data, which can also be called the first type of business data). In addition, as shown above Figure 5 According to the timing diagram of the characteristic elements on the rendering display interface corresponding to each moment shown above, it can be known that the characteristic elements in the local key area on the rendering display interface can be the first type of business data obtained from the business server. In addition, the first type of business data obtained from the business server can also exist outside this local key area. Figure 5 As shown in the display interface 600a described above, there can also be statically loaded business data (i.e., the second type of business data) in this display interface 600a, that is, there can be statically loaded business data before the local key area. In addition, according to Figure 5 the dynamic change diagrams of the characteristic elements on the rendering display interface corresponding to each moment shown above, it can be known that the characteristic elements in the local key area on the rendering display interface can be the first type of business data obtained from the business server. In addition, the first type of business data obtained from the business server can also exist outside this local key area.

[0144] Step S104, when the characteristic elements on the rendering display interface meet the white screen detection condition, restart the small program in the target application.

[0145] Specifically, the user terminal can generate the white screen prompt information corresponding to the small program when the characteristic elements on the rendering display interface meet the white screen detection condition; further, the user terminal can output the white screen prompt information to a sub-display interface independent of the rendering display interface; further, the user terminal can respond to the restart operation triggered for the sub-display interface, obtain the restart interface corresponding to the small program based on the restart operation; further, the user terminal can call the restart interface in the target application to restart the small program.

[0146] It can be understood that if the rendering display interface when the rendering display duration reaches the delay detection duration is the display interface 600c shown above Figure 5 then it can be quickly determined based on the white screen detection rule that the characteristic elements in the local key area of this display interface 600c are missing, that is, there is a local white screen phenomenon in the above small program A3. At this time, the target application in this user terminal can simulate restarting the small program A3 in this target application (i.e., the WeChat application) based on the restart interface corresponding to the small program A3.

[0147] Optionally, it should be understood that due to compatibility and other issues between the version information of this small program A3 and the target application in this user terminal, when starting the small program A3 in the target application, a full white screen phenomenon may also occur. For ease of understanding, further, please refer to Figure 6, is a schematic diagram of a scenario in which a full white screen phenomenon occurs during page loading provided by an embodiment of the present application. Figure 6 The display interface 700a shown may include Figure 6 Because there are compatibility issues between the version information of the target application and the aforementioned small program A3, when the small program A3 is started in the target application, the page loading cannot be completed, so that Figure 6 When the rendering display time of the display interface 700a shown in FIG. 1 reaches the extended detection time, the rendering of the characteristic elements on the display interface 700a still cannot be completed. In view of this, when the rendering display time reaches the delayed detection time, the rendering display interface is Figure 6 When the display interface 700a is shown, the sub-display interface 700a can be output on a sub-display interface independent of the display interface 700a. Figure 6 The white screen prompt information shown. Among them, the sub-display interface where the white screen prompt information is located can be Figure 6 It can be understood that when the rendering display interface has a completely white screen phenomenon, there are no characteristic elements in the entire area (full screen display area) of the rendering display interface, that is, the value of the second quantity counted on the rendering display interface is zero.

[0148] It should be understood that the partial white screen phenomenon on the rendering display interface may include the absence of local feature elements in the above-mentioned local key area, and may also include the absence of local feature elements in the above-mentioned full-screen display area. This embodiment of the application will not limit it.

[0149] The embodiment of the present application can receive the first type of business data returned by the business server corresponding to the mini program when the mini program is started in the target application; further, render and output the first type of business data to the rendering display interface corresponding to the mini program, and record the rendering display time of rendering the first type of business data in the rendering display interface; further, when the rendering display time reaches the delay detection time, obtain the characteristic elements on the rendering display interface; further, when the characteristic elements on the rendering display interface meet the white screen detection condition, restart the mini program in the target application. It can be seen from this that the present application can start white screen detection for the characteristic elements on the rendering display interface when the current time (i.e., the rendering display time) reaches the delay detection time, so as to quickly determine whether the characteristic elements on the rendering display interface meet the white screen detection condition. If so, the mini program can be quickly simulated to be restarted in the target application without exiting the target application (e.g., WeChat application) to quickly implement the restart operation of the mini program, thereby improving the restart efficiency of the mini program.

[0150] For further information, see Figure 7, which is a schematic flowchart of another data processing method provided by an embodiment of the present application. As Figure 7 shown, the method may at least include:

[0151] Step S201, log in to the target application through the user account information of the target user, and display the applet in the applet display interface of the target application;

[0152] Step S202, in response to a trigger operation triggered for the applet, start the applet in the target application, and jump the applet display interface to the rendering display interface corresponding to the applet;

[0153] Step S203, send a data loading request to the business server corresponding to the applet;

[0154] It can be understood that before the user terminal executes step S203, the static loading data corresponding to the applet may also be used as the second type of service data, and the second type of service data is statically displayed on the rendering display interface. In this way, when the user terminal subsequently obtains the characteristic elements on the rendering display interface, specifically, the pixel points of the first type of service data and the pixel points of the second type of service data on the rendering display interface may be used as the characteristic elements on the full-screen display area of the rendering display interface.

[0155] Step S204, receive the first type of service data returned by the business server based on the data loading request.

[0156] Among them, for the specific implementation manners of steps S201 - S204, reference may be made to the description of step S101 in the corresponding embodiment above, and details will not be elaborated here. Figure 3 The description will not be continued here.

[0157] Step S205, render and output the first type of service data to the rendering display interface corresponding to the applet, and record the rendering display duration of rendering the first type of service data in the rendering display interface;

[0158] Step S206, when the rendering display duration reaches the delay detection duration, obtain the characteristic elements on the rendering display interface;

[0159] Among them, it can be understood that the characteristic elements on the rendering display interface in the embodiment of the present application may include the pixel points of the first type of service data in the local key area, where the local key area is located in the rendering display interface. Then, after the user terminal executes step S206, the following steps S207 - S208 may be further executed.

[0160] Optionally, the feature elements on the rendering display interface in the embodiments of the present application may further include the feature elements on the full-screen display area of the rendering display interface. That is, the feature elements on the full-screen display area may specifically include the pixel points of the first type of service data and the pixel points of the second type of service data. It can be understood that the first type of service data on the full-screen display area in the embodiments of the present application may include the first type of service data pulled from the service server in the foregoing local key area, and may also include the first type of service data rendered and output in the remaining display area except the local global area in the full-screen display area. Then, after the user terminal executes step S206, the following steps S209 to S212 may be further executed. In other words, the local white screen described in the embodiments of the present application may include the white screen phenomenon on the local key area, and may also include the local white screen phenomenon on the full-screen display area. In addition, for the full-screen display area, there may also be a phenomenon of full white screen, that is, there are no any feature elements on the entire rendering display interface.

[0161] Step S207: Dot-report the number of pixel points of the first type of service data on the local key area in the rendering display interface, and use the dot-reported number as the first number associated with the local key area;

[0162] Step S208: When the first number does not reach the first rendering threshold corresponding to the local key area, determine that the feature elements on the rendering display interface meet the white screen detection condition.

[0163] Among them, for the specific implementation manners of steps S207 to S208, reference may be made to the description of the pixel points of the first type of service data in the local key area in the corresponding embodiments above, and details will not be elaborated here. Figure 3 The description of the pixel points of the first type of service data in the local key area in the corresponding embodiments above will not be repeated here.

[0164] Optionally, in step S209, accumulate the pixel points of the first type of service data on the full-screen display area in the rendering display interface to obtain a first cumulative value;

[0165] Step S210: Accumulate the pixel points of the second type of service data on the full-screen display area to obtain a second cumulative value;

[0166] Step S211: Use the sum of the first cumulative value and the second cumulative value as the second number associated with the full-screen display area;

[0167] Step S212: When the second number does not reach the second rendering threshold corresponding to the full-screen display area, determine that the feature elements on the rendering display interface meet the white screen detection condition.

[0168] For ease of understanding, further, please refer toFigure 8 , which is a schematic diagram of a scenario of the local white screen phenomenon provided by an embodiment of the present application. As Figure 8 shown, the display interface 800a can be the rendered display interface when the rendered display duration reaches the delay detection duration. As Figure 8 shown, the second type of service data is the static loading data corresponding to the applet. When the user terminal performs white screen detection, the number of pixel points of the first type of service data counted in the Figure 8 full-screen display area shown can be referred to as the first cumulative value (for example, 200 pixel points), and the number of pixel points of the second type of service data counted in the full-screen display area can be referred to as the second cumulative value (for example, 40 pixel points). It can be understood that for any user of applet A3, under normal loading conditions, the same static loading data (i.e., the second type of service data) can be seen on the rendered display interface corresponding to the applet. However, for the service data that needs to be dynamically loaded, the corresponding service data can be dynamically requested from the service server according to each user's personal historical behavior information and presented to the user.

[0169] For example, taking the WeChat Reading applet as an example, when user A and user B access the WeChat Reading applet respectively, different service data can be personalized and loaded intelligently according to the personal historical behavior information of user A and user B, so that different first type of service data can be presented to user A and user B respectively. For example, e-book A can be dynamically loaded in the user terminal used by user A, and e-book B can be dynamically loaded in the user terminal used by user B, etc. However, the second type of service data seen by these two users in the rendered display interface is the same, that is, the second type of service data does not need to be dynamically loaded.

[0170] Step S213, when the feature elements on the rendered display interface meet the white screen detection conditions, restart the applet in the target application.

[0171] Specifically, when the feature elements on the rendered display interface meet the white screen detection conditions, the user terminal can generate white screen prompt information corresponding to the applet; further, the user terminal can output the white screen prompt information to a sub-display interface independent of the rendered display interface; further, the user terminal can respond to a restart operation triggered for the sub-display interface, obtain a restart interface corresponding to the applet based on the restart operation; further, the user terminal can call the restart interface in the target application to restart the applet. It can be seen that the embodiment of the present application can simulate restarting the applet in the target application without exiting the target application when detecting the white screen phenomenon, so as to quickly restore the white screen of the applet.

[0172] It can be understood that, after the above step S208 is executed, the embodiment of the present application can further jump to execute S213, that is, when there is an element missing in the local key area corresponding to the small program (for example, there is a local white screen or a full white screen in the local key area), the restart operation of the small program can be quickly implemented without exiting the target application.

[0173] Of course, optionally, it can also be understood that, after the above step S212 is executed, the embodiment of the present application can further jump to execute S213, that is, when there is an element missing in the full-screen display area corresponding to the small program (that is, there is a full white screen or a local white screen in the full-screen display area), the restart operation of the small program can be simulated in the target application to quickly recover the white screen of the small program.

[0174] For ease of understanding, further, please refer to Figure 9 , which is a schematic diagram of the overall process for white screen detection and white screen recovery provided by the embodiment of the present application. As Figure 9 shown, when the target user starts a small program (for example, the above small program A3) on the user terminal, step 10 shown in Figure 9 can be executed. In other words, when the target user performs a cold start on a small program (such as the WeChat Reading small program) in the WeChat application (i.e., the above target application), the small program can be run in the WeChat application, and then page initialization can be implemented to obtain the rendered display page corresponding to the small program. As Figure 9 shown, at this time, the small program on the user terminal can execute step 70, that is, a data pull request can be sent to the background server (i.e., the business server corresponding to the WeChat Reading small program), so that the background server can return the business data corresponding to the WeChat Reading small program to the WeChat Reading small program, and step 80 can be executed on the received business data in the above rendered display page to perform page rendering.

[0175] It should be understood that within a preset delay detection duration (e.g., 2 s), the user terminal can run the WeChat Reading applet and can pull service data from the above-mentioned service server through the network for data loading. To improve the accuracy of white screen detection, the embodiments of the present application do not include the time within 2 s in the white screen detection scope because there will be some statically loaded service data on the rendering display page of the WeChat Reading applet (i.e., service data that does not require dynamic loading can be called the second type of service data). Therefore, when the WeChat Reading applet is started in the target application, these service data that need to be statically loaded (i.e., the second type of service data) will be quickly loaded and displayed on the rendering display page during this time. Therefore, under normal circumstances, each user using the WeChat Reading applet can see the same statically loaded service data when accessing the WeChat Reading applet. However, for some service data that requires dynamic loading (i.e., the first type of service data), it needs to be pulled from the above-mentioned service server through the network, so that the pulled service data can be output on the rendering display page for page rendering.

[0176] Among them, as Figure 9 shown, the user terminal can execute step 20 to start a timer for white screen detection, and this timer is used to trigger white screen detection at the delay detection duration. In addition, it should be understood that while the user terminal is performing page rendering, it can also count the rendering display duration. Therefore, if the page rendering is completed before the rendering display duration (e.g., 1.5 s) reaches the delay detection duration (2 s), the rendering display duration within these 2 s can be defaulted to the normal loading duration. On the contrary, if the page rendering is not completed when the rendering display duration reaches the aforementioned delay detection duration, then the embodiments of the present application can regard the duration after 2 s and 2 s as the abnormal loading duration.

[0177] It can be seen that during the page rendering process, the embodiments of the present application can determine whether there is a lack of feature elements on the rendering display interface when the current time (i.e., the page rendering duration) reaches the preset time (i.e., the delay detection duration) by executing step 30-step 40. It can be understood that the feature elements here can be the feature elements in the aforementioned local key area; they can also be the feature elements on the entire page (i.e., the aforementioned full-screen display area), and no limitation will be imposed here.

[0178] Among them, it can be understood that, in the process of executing step 40, the user terminal can specifically determine whether the characteristic elements on the designated area (i.e., the local key area or the full-screen display area) reach the preset threshold. If the preset threshold is not reached, it is determined that the characteristic elements on the current page meet the white screen detection conditions, and then the process can jump to execute step 50 to quickly restart the WeChat reading applet without exiting the target application; otherwise, step 60 can be executed to report the white screen prompt information in a prompt window independent of the rendering display interface to help the target user complete the white screen detection.

[0179] Among them, it can be understood that when the WeChat Reading Mini Program determines that the characteristic elements on the current page (i.e., the current rendering display interface) do not meet the preset conditions (i.e., the white screen detection conditions), it can be disguised as the absence of elements in the specified area on the current page, for example, there is a white screen phenomenon in the local key area.

[0180] For further information, see Figure 10 , is a schematic diagram of a scenario of restarting a mini-program provided in an embodiment of the present application. Figure 10 As shown, when the applet (applet A3) in the user terminal finds that the current page (i.e., the rendering display interface when the rendering display duration reaches the delay detection duration) has a white screen, it can be opened independently of the rendering display page (i.e. Figure 10 The sub-display interface of the display interface 800b) shown in the figure displays a white screen prompt message. Figure 10 The sub-display interface shown can be called a pop-up window of the rendering display interface, or a white screen prompt window. Figure 10 As shown, the target user can perform a trigger operation on the area where the retry button is located in the sub-display interface to determine to simulate restarting the mini program in the target application. It should be understood that if the target user confirms that the white screen of the mini program A3 needs to be restored, the restart operation can be performed, so that the mini program restart function can be quickly realized without exiting the WeChat application (i.e., the target application). Figure 10 As shown in the figure, when a pop-up window pops up on the current display page of the applet (i.e. applet A3), the user information corresponding to the white screen (for example, the user account information of the applet) will be given to the development terminal, so that the development terminal can count how many people encounter such a white screen problem every day. Figure 10 As shown, the target user can generate restart record information based on the user account information of the target user and the call timestamp of calling the restart interface, so as to send the restart record information to the development terminal that develops the mini program A3, thereby helping the developer to understand the frequency of the white screen problem occurring in the user terminal, and the number of times the white screen phenomenon occurs per capita in the user group using the mini program A3.

[0181] In addition, the embodiments of the present application can also help developers understand whether there are problems with the newly released version of the mini program by observing the statistical trend of the white screen phenomenon in different user terminals; in addition, the correlation between the white screen and the user device brand, operating system (iOS / Android), operating system version, and WeChat version can also be understood. In this way, if the developer finds that the white screen problem accounts for a large proportion of users of a certain Android version, subsequent optimization can be carried out in a targeted manner to reduce the possibility of white screen occurrence and improve the user experience.

[0182] Optionally, the user terminal can also respond to a cancel operation triggered on the sub-display interface, and close the sub-display interface based on the cancel operation; further, the user terminal can generate feedback information corresponding to the cancel operation based on the user account information of the target application; further, the user terminal can send the feedback information to the development terminal associated with the mini program, so that the development terminal adjusts and analyzes the white screen detection mechanism corresponding to the mini program based on the feedback information.

[0183] For further understanding, please refer to the above Figure 10 , as mentioned above Figure 10 As shown, the target user can also choose to trigger the cancel button in the pop-up window that pops up in the above display interface 800b to indicate that the white screen detection mechanism registered in the applet in the user terminal may have a false alarm phenomenon. At this time, the user terminal may also give the feedback information of the false alarm to the development end. In other words, if the user chooses to cancel, it is possible that the white screen problem is mistakenly detected when there is no white screen. At this time, the developer can debug the cause of the white screen detection based on the user's feedback information (i.e., the information when canceling and restarting the applet). For example, it may be a false alarm caused by the lax detection rules set by the developer, and the applet can be targeted for repair through feedback information.

[0184] When starting a mini-program in a target application in an embodiment of the present application, the first type of service data returned by the service server corresponding to the mini-program is received; further, the first type of service data is rendered and output to the rendering display interface corresponding to the mini-program, and the rendering display duration of rendering the first type of service data in the rendering display interface is recorded; further, when the rendering display duration reaches the delay detection duration, the feature elements on the rendering display interface are obtained; further, when the feature elements on the rendering display interface meet the white screen detection condition, the mini-program is restarted in the target application. It can be seen that in the present application, when the current time (i.e., the rendering display duration) reaches the delay detection duration, the white screen detection is performed on the feature elements on the rendering display interface to quickly determine whether the feature elements on the rendering display interface meet the white screen detection condition. If so, the mini-program can be quickly restarted in the target application without exiting the target application (such as the WeChat application), so as to quickly implement the restart operation of the mini-program, and thus the restart efficiency of the mini-program can be improved.

[0185] Further, please refer to Figure 11 , which is a schematic structural diagram of a data processing device provided by an embodiment of the present application. As Figure 11 shown, the data processing device 1 can be applied to the target user terminal in the corresponding embodiment of the above Figure 2 . The data processing device 1 may include: a mini-program start module 10, a rendering output module 20, an element acquisition module 30, a mini-program restart module 40; further, the data processing device 1 may further include a dot reporting module 50, a first determination module 60, a first accumulation module 70, a second accumulation module 80, a quantity determination module 90, a second determination module 100, a restart record generation module 110, a restart record sending module 120, a sub-interface closing module 130, a feedback information generation module 140, and a feedback information sending module 150;

[0186] The mini-program start module 10 is configured to receive the first type of service data returned by the service server corresponding to the mini-program when starting the mini-program in the target application;

[0187] Among them, the mini-program start module 10 includes: an application login unit 101, an interface jump unit 102, a request sending unit 103, and a service data receiving unit 104; further, the mini-program start module 10 may further include a detection mechanism acquisition unit 105, a code writing unit 106, a timer trigger unit 107, and a static loading unit 108;

[0188] The application login unit 101 is configured to log in to the target application through the user account information of the target user and display the mini-program in the mini-program display interface of the target application;

[0189] The interface jump unit 102 is configured to respond to a trigger operation triggered for the mini-program, start the mini-program in the target application, and jump the display interface of the mini-program to the rendering display interface corresponding to the mini-program;

[0190] The request sending unit 103 is configured to send a data loading request to the business server corresponding to the mini-program;

[0191] The business data receiving unit 104 is configured to receive the first type of business data returned by the business server based on the data loading request.

[0192] Among them, for the specific implementation manners of the application login unit 101, the interface jump unit 102, the request sending unit 103, and the business data receiving unit 104, reference may be made to the description of step S101 in the corresponding embodiments above, and details will not be elaborated here. Figure 3 The corresponding description of step S101 in the corresponding embodiments will not be elaborated here.

[0193] Optionally, the detection mechanism acquisition unit 105 is configured to acquire the white screen detection mechanism associated with the mini-program when starting the mini-program in the target application;

[0194] The code writing unit 106 is configured to write the white screen detection code information corresponding to the white screen detection mechanism into the mini-program;

[0195] The timer trigger unit 107 is configured to trigger the timer corresponding to the mini-program, and determine the delay detection duration through the timer.

[0196] Optionally, the static loading unit 108 is configured to use the static loading data corresponding to the mini-program as the second type of business data, and statically display the second type of business data on the rendering display interface;

[0197] Then, the element acquisition module 30 is configured to use the pixel points of the first type of business data and the pixel points of the second type of business data on the rendering display interface as the feature elements on the full-screen display area of the rendering display interface when the rendering display duration reaches the delay detection duration.

[0198] The rendering output module 20 is configured to render and output the first type of business data to the rendering display interface corresponding to the mini-program, and record the rendering display duration of rendering the first type of business data in the rendering display interface;

[0199] The element acquisition module 30 is configured to acquire the feature elements on the rendering display interface when the rendering display duration reaches the delay detection duration;

[0200] The applet restart module 40 is used to restart the applet in the target application when the characteristic elements on the rendering display interface meet the white screen detection conditions.

[0201] Among them, the applet restart module 40 includes: a prompt information generation unit 401, a prompt information output unit 402, an interface acquisition unit 403, and an interface call unit 404;

[0202] The prompt information generation unit 401 is used to generate white screen prompt information corresponding to the applet when the characteristic elements on the rendering display interface meet the white screen detection conditions;

[0203] The prompt information output unit 402 is used to output the white screen prompt information to a sub-display interface independent of the rendering display interface;

[0204] The interface acquisition unit 403 is used to respond to a restart operation triggered for the sub-display interface and obtain a restart interface corresponding to the applet based on the restart operation;

[0205] The interface call unit 404 is used to call the restart interface in the target application to restart the applet.

[0206] Among them, for the specific implementation manners of the prompt information generation unit 401, the prompt information output unit 402, the interface acquisition unit 403, and the interface call unit 404, reference can be made to the description of step S104 in the corresponding embodiment above, and details will not be elaborated here. Figure 3 For the specific implementation manners of the applet start module 10, the rendering output module 20, the element acquisition module 30, and the applet restart module 40, reference can be made to the description of steps S101 - S104 in the corresponding embodiment above, and details will not be elaborated here.

[0207] Among them, for the specific implementation manners of the applet start module 10, the rendering output module 20, the element acquisition module 30, and the applet restart module 40, reference can be made to the description of steps S101 - S104 in the corresponding embodiment above, and details will not be elaborated here. Figure 3 For the specific implementation manners of the applet start module 10, the rendering output module 20, the element acquisition module 30, and the applet restart module 40, reference can be made to the description of steps S101 - S104 in the corresponding embodiment above, and details will not be elaborated here.

[0208] Optionally, the characteristic elements on the rendering display interface include pixel points of the first type of service data in a local key area; the local key area is located in the rendering display interface;

[0209] The dot reporting module 50 is used to perform dot reporting on the number of pixel points of the first type of service data in the local key area in the rendering display interface, and use the reported number as a first number associated with the local key area;

[0210] The first determination module 60 is used to determine that the characteristic elements on the rendering display interface meet the white screen detection conditions when the first number does not reach the first rendering threshold corresponding to the local key area.

[0211] Among them, for the specific implementation manners of the dot reporting module 50 and the first determination module 60, reference can be made to the description of the local key area in the corresponding embodiments above, and details will not be elaborated here. Figure 7

[0212] Optionally, a first accumulation module 70 is configured to accumulate pixel points of first-type service data on the full-screen display area in the rendering display interface to obtain a first accumulation value;

[0213] A second accumulation module 80 is configured to accumulate pixel points of second-type service data on the full-screen display area to obtain a second accumulation value;

[0214] A quantity determination module 90 is configured to use the sum of the first accumulation value and the second accumulation value as a second quantity associated with the full-screen display area;

[0215] A second determination module 100 is configured to determine that the feature elements on the rendering display interface meet the white screen detection condition when the second quantity does not reach a second rendering threshold corresponding to the full-screen display area.

[0216] Among them, for the specific implementation manners of the first accumulation module 70, the second accumulation module 80, the quantity determination module 90, and the second determination module 100, reference can be made to the description of the full-screen display area in the corresponding embodiments above, and details will not be elaborated here. Figure 7

[0217] Optionally, a restart record generation module 110 is configured to obtain user account information of the target application and generate restart record information based on the user account information and the call timestamp of the restart interface; at least the following key information associated with the white screen of the applet is included in the restart record information: version information of the target application, operation coefficient information of the terminal where the target application is located, and device type information of the terminal;

[0218] A restart record sending module 120 is configured to send the restart record information and the user account information to a development terminal associated with the applet so that the development terminal performs data analysis on the restart record information.

[0219] Optionally, a sub-interface closing module 130 is configured to respond to a cancellation operation triggered for the sub-display interface and close the sub-display interface based on the cancellation operation;

[0220] A feedback information generation module 140 is configured to generate feedback information corresponding to the cancellation operation based on the user account information of the target application;

[0221] A feedback information sending module 150 is configured to send the feedback information to a development terminal associated with the applet, so that the development terminal adjusts and analyzes a white screen detection mechanism corresponding to the applet based on the feedback information.

[0222] Among them, for the specific implementation manners of the restart record generation module 110, the restart record sending module 120, the sub-interface closing module 130, the feedback information generation module 140, and the feedback information sending module 150, reference can be made to the descriptions of the restart record information and the feedback information in the corresponding embodiments above. Figure 10 Details will not be elaborated here.

[0223] In an embodiment of the present application, when starting an applet in a target application, first-class service data returned by a service server corresponding to the applet can be received; further, the first-class service data is rendered and output to a rendering display interface corresponding to the applet, and a rendering display duration for rendering the first-class service data in the rendering display interface is recorded; further, when the rendering display duration reaches a delay detection duration, characteristic elements on the rendering display interface are obtained; further, when the characteristic elements on the rendering display interface meet the white screen detection conditions, the applet is restarted in the target application. It can be seen that in the present application, when the current time (i.e., the rendering display duration) reaches the delay detection duration, white screen detection is performed on the characteristic elements on the rendering display interface to determine whether the characteristic elements on the rendering display interface meet the white screen detection conditions. If so, the applet can be quickly restarted in the target application without exiting the target application (such as, the WeChat application), so as to quickly implement the restart operation of the applet, thereby improving the restart efficiency of the applet.

[0224] Further, please refer to Figure 12 , which is a schematic diagram of a computer device provided by an embodiment of the present application. As Figure 12 shown, the computer device 1000 may be the above Figure 2For the target user terminal in the corresponding embodiment, the computer device 1000 may include: at least one processor 1001, such as a CPU, at least one network interface 1004, a user interface 1003, a memory 1005, and at least one communication bus 1002. Among them, the communication bus 1002 is used to implement the connection and communication between these components. Among them, the user interface 1003 may include a display screen (Display) and a keyboard (Keyboard). Optionally, the network interface 1004 may include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory, such as at least one disk memory. Optionally, the memory 1005 may also be at least one storage device located far from the aforementioned processor 1001. As Figure 12 shown, in the memory 1005 as a computer storage medium, there may be included an operating system, a network communication module, a user interface module, and a device control application program.

[0225] In Figure 12 the computer device 1000 shown, the network interface 1004 is mainly used for network communication with the service server; while the user interface 1003 is mainly used to provide an input interface for the user; and the processor 1001 may be used to call the device control application program stored in the memory 1005 to implement:

[0226] When starting a mini-program in the target application, receiving the first type of service data returned by the service server corresponding to the mini-program;

[0227] Rendering and outputting the first type of service data to the rendering display interface corresponding to the mini-program, and recording the rendering display duration of rendering the first type of service data in the rendering display interface;

[0228] When the rendering display duration reaches the delay detection duration, obtaining the characteristic elements on the rendering display interface;

[0229] When the characteristic elements on the rendering display interface meet the white screen detection condition, restarting the mini-program in the target application.

[0230] It should be understood that the computer device 1000 described in the embodiments of the present application can execute the descriptions of the data processing method in the corresponding embodiments described above Figure 3 and Figure 7 and can also execute the descriptions of the data processing device 1 in the corresponding embodiments described above Figure 11 , which will not be elaborated here. In addition, the description of the beneficial effects of adopting the same method will not be elaborated either.

[0231] In addition, it should be noted here that: The embodiments of the present application also provide a computer-readable storage medium, and the computer-readable storage medium stores the computer program executed by the aforementioned data processing device 1, and the computer program includes program instructions. When the processor executes the program instructions, it can execute the description of the video data processing method in the corresponding embodiments mentioned above. Therefore, it will not be elaborated here. In addition, the description of the beneficial effects of using the same method will not be elaborated either. For the technical details not disclosed in the embodiments of the computer-readable storage medium involved in the present application, please refer to the description of the method embodiments of the present application. Figure 3 or Figure 7 The description of the corresponding embodiments of the video data processing method will not be repeated here. In addition, the description of the beneficial effects of using the same method will not be repeated either. For the technical details not disclosed in the embodiments of the computer-readable storage medium involved in the present application, please refer to the description of the method embodiments of the present application.

[0232] Those of ordinary skill in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. The above program can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above methods. Among them, the above storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM), etc.

[0233] The foregoing disclosure is only the preferred embodiments of the present application, and of course, it cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application still fall within the scope covered by the present application.

Claims

1. A data processing method, characterized in that, comprising: When starting a small program in a target application, taking the static loading data corresponding to the small program as the second type of service data, statically displaying the second type of service data on a rendering display interface, receiving the first type of service data returned by the service server corresponding to the small program and obtaining the white screen detection mechanism associated with the small program, and writing the white screen detection code information corresponding to the white screen detection mechanism into the small program, where the first type of service data is the corresponding service data obtained from the service server based on the user's personal historical behavior information; Rendering and outputting the first type of service data to multiple rendering display interfaces corresponding to the small program, and recording the rendering display duration of rendering the first type of service data in the multiple rendering display interfaces; different rendering display interfaces correspond to the rendering display durations of different rendering stages; When the rendering display duration reaches the delay detection duration, taking the pixel points of the first type of service data and the pixel points of the second type of service data on the rendering display interface as characteristic elements on the full-screen display area of the rendering display interface; Accumulating the pixel points of the first type of service data on the full-screen display area in the rendering display interface to obtain a first cumulative value, accumulating the pixel points of the second type of service data on the full-screen display area to obtain a second cumulative value, taking the sum of the first cumulative value and the second cumulative value as the second quantity associated with the full-screen display area, and when the second quantity does not reach the second rendering threshold corresponding to the full-screen display area, determining that the characteristic elements on the rendering display interface meet the white screen detection conditions; When the characteristic elements on the rendering display interface meet the white screen detection conditions, generating a white screen prompt message corresponding to the small program; Outputting the white screen prompt message to a sub-display interface independent of the rendering display interface; Responding to a restart operation triggered for the sub-display interface, and obtaining the restart interface corresponding to the small program based on the restart operation; Invoking the restart interface in the target application to restart the small program; Responding to a cancellation operation triggered for the sub-display interface, and closing the sub-display interface based on the cancellation operation; Generating feedback information corresponding to the cancellation operation based on the user account information of the target application, where the feedback information is used to indicate that the rendering display interface does not have a white screen; Sending the feedback information to a development terminal associated with the small program, so that the development terminal adjusts and analyzes the white screen detection mechanism corresponding to the small program based on the feedback information.

2. The method according to claim 1, characterized in that, The receiving the first type of service data returned by the service server corresponding to the small program when starting the small program in the target application includes: Logging in to the target application through the user account information of the target user, and displaying the small program in the small program display interface of the target application; Responding to a trigger operation triggered for the small program, starting the small program in the target application, and jumping the small program display interface to the rendering display interface corresponding to the small program; After using the static loading data corresponding to the applet as the second type of service data and statically displaying the second type of service data on the rendering display interface, send a data loading request to the service server corresponding to the applet; Receive the first type of service data returned by the service server based on the data loading request.

3. The method according to claim 2, wherein, after writing the white screen detection code information corresponding to the white screen detection mechanism into the applet, further comprising: Trigger the timer corresponding to the applet, and determine the delay detection duration through the timer.

4. The method according to claim 1, wherein, the characteristic elements on the rendering display interface include the pixel points of the first type of service data in the local key area; the local key area is located in the rendering display interface; the method further comprises: In the rendering display interface, perform dot reporting on the number of pixel points of the first type of service data in the local key area, and use the number of dot reporting as the first number associated with the local key area; When the first number does not reach the first rendering threshold corresponding to the local key area, determine that the characteristic elements on the rendering display interface meet the white screen detection condition.

5. The method according to claim 1, wherein, further comprising: Obtain the user account information of the target application, and generate restart record information based on the user account information and the call timestamp of the restart interface; The restart record information at least includes the following key information associated with the white screen of the applet: the version information of the target application, the operation coefficient information of the terminal where the target application is located, and the device type information of the terminal; Send the restart record information and the user account information to the development terminal associated with the applet, so that the development terminal performs data analysis on the restart record information.

6. A data processing device, wherein, comprising: An applet startup module, configured to, when starting an applet in a target application, use the static loading data corresponding to the applet as the second type of service data, statically display the second type of service data on the rendering display interface, receive the first type of service data returned by the service server corresponding to the applet, and obtain the white screen detection mechanism associated with the applet, and write the white screen detection code information corresponding to the white screen detection mechanism into the applet. The first type of service data is the corresponding service data obtained from the service server based on the user's personal historical behavior information; A rendering output module, configured to render and output the first type of service data to multiple rendering display interfaces corresponding to the applet, and record the rendering display duration of rendering the first type of service data in the multiple rendering display interfaces; different rendering display interfaces correspond to the rendering display durations of different rendering stages; An element acquisition module, configured to, when the rendering display duration reaches the delay detection duration, use the pixel points of the first type of service data and the pixel points of the second type of service data on the rendering display interface as feature elements on the full-screen display area of the rendering display interface; The applet restart module includes: a prompt information generation unit, a prompt information output unit, an interface acquisition unit, and an interface call unit. The prompt information generation unit is configured to generate a white screen prompt information corresponding to the applet when the feature elements on the rendering display interface meet the white screen detection condition; the prompt information output unit is configured to output the white screen prompt information to a sub-display interface independent of the rendering display interface; the interface acquisition unit is configured to, in response to a restart operation triggered for the sub-display interface, acquire a restart interface corresponding to the applet based on the restart operation; the interface call unit is configured to call the restart interface in the target application to restart the applet; A sub-interface closing module, configured to, in response to a cancellation operation triggered for the sub-display interface, close the sub-display interface based on the cancellation operation; A feedback information generation module, configured to generate feedback information corresponding to the cancellation operation based on the user account information of the target application, where the feedback information is used to indicate that the rendering display interface does not have a white screen; A feedback information sending module, configured to send the feedback information to a development terminal associated with the applet, so that the development terminal adjusts and analyzes the white screen detection mechanism corresponding to the applet based on the feedback information; A first accumulation module, configured to accumulate the pixel points of the first type of service data on the full-screen display area in the rendering display interface to obtain a first accumulated value; A second accumulation module, configured to accumulate the pixel points of the second type of service data on the full-screen display area to obtain a second accumulated value; A quantity determination module, configured to use the sum of the first accumulated value and the second accumulated value as a second quantity associated with the full-screen display area; A second determination module, configured to determine that the feature elements on the rendering display interface meet the white screen detection condition when the second quantity does not reach a second rendering threshold corresponding to the full-screen display area.

7. A computer device Characterized in that It includes: A processor, a memory, and a network interface; The processor is connected to the memory and the network interface. Among them, the network interface is used to provide a data communication function, the memory is used to store program code, and the processor is used to call the program code to execute the method according to any one of claims 1-5.

8. A computer-readable storage medium Characterized in that The computer-readable storage medium stores a computer program, the computer program includes program instructions, and when the program instructions are executed by a processor, the method according to any one of claims 1-5 is executed.

Images