WO2019214475A1

WO2019214475A1 - Application preloading method, device, storage medium, and mobile terminal

Info

Publication number: WO2019214475A1
Application number: PCT/CN2019/084779
Authority: WO
Inventors: 韩世广; 陈岩
Original assignee: 上海瑾盛通信科技有限公司
Priority date: 2018-05-10
Filing date: 2019-04-28
Publication date: 2019-11-14
Also published as: CN108664285A

Abstract

Disclosed are an application preloading method, a device, a storage medium, and a mobile terminal. The method comprises: detecting an application preloading event being triggered; determining a target application to be preloaded; employing a low power consumption core in a multicore processor to preload an application interface corresponding to the target application.

Description

Application preloading method and device, storage medium and mobile terminal

The present application claims priority to Chinese Patent Application No. 201810443422.4, filed on May 10, 2011, the entire disclosure of which is hereby incorporated by reference.

Technical field

The embodiments of the present application relate to the field of application loading technologies, for example, to an application preloading method and apparatus, a storage medium, and a mobile terminal.

Background technique

At present, mobile terminals such as smart phones, tablets, notebook computers, and smart home appliances have become indispensable electronic devices in people's daily lives. As mobile terminal devices continue to be intelligent, most mobile terminal devices are loaded with an operating system, so that the mobile terminal device can install a variety of applications to meet different needs of users.

As the configuration of mobile terminal devices continues to increase, dozens or even hundreds of applications can be installed in most mobile terminal devices, and as applications become more and more abundant, applications need to load more resources while running. . When the user chooses to start an application, the mobile terminal loads the resources required for starting the application, and after loading, enters the initial interface of the application, and the whole process usually takes several seconds or even ten seconds, resulting in The startup of the application is less efficient and needs to be improved.

Summary of the invention

The embodiment of the present application provides an application preloading method and device, a storage medium, and a mobile terminal, which can optimize an application loading scheme.

In a first aspect, an embodiment of the present application provides an application preloading method, including:

An application preload event is detected to be triggered;

Determining the target application to be preloaded;

The application interface corresponding to the target application is preloaded with a low power core in the multi-core processor.

In a second aspect, an embodiment of the present application provides an application preloading apparatus, including:

An event trigger detection module configured to detect whether an application preload event is triggered;

An application determining module, configured to determine a target application to be preloaded when detecting that an application preloading event is triggered;

The preloading module is configured to preload the application interface corresponding to the target application by using a low power core in the multi-core processor.

In a third aspect, the embodiment of the present application provides a computer readable storage medium, where a computer program is stored, and when the program is executed by the processor, the application preloading method is implemented as described in the embodiment of the present application.

In a fourth aspect, an embodiment of the present application provides a mobile terminal, including a memory, a processor, and a computer program stored in the memory and executable by the processor, where the processor executes the computer program to implement the implementation of the present application. The application preloading method described in the example.

BRIEF abstract

1 is a schematic flowchart of an application preloading method according to an embodiment of the present application;

2 is a schematic diagram of a relative position relationship between a preloaded active window stack and a display screen display area according to an embodiment of the present application;

FIG. 3 is a schematic diagram of a relative positional relationship between a preloaded active window stack and a display screen display area according to an embodiment of the present application;

4 is a schematic flowchart of still another application preloading method according to an embodiment of the present application;

FIG. 5 is a schematic flowchart of another application preloading method according to an embodiment of the present disclosure;

FIG. 6 is a structural block diagram of an application preloading apparatus according to an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application;

FIG. 8 is a schematic structural diagram of still another mobile terminal according to an embodiment of the present application.

detailed description

It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting. In addition, it should be noted that, for the convenience of description, only some but not all of the structures related to the present application are shown in the drawings.

Before discussing the exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as a process or method depicted as a flowchart. Although the flowcharts describe the various steps as a sequential process, many of the steps can be implemented in parallel, concurrently, or concurrently. In addition, the order of the steps can be rearranged. The process may be terminated when its operation is completed, but may also have additional steps not included in the figures. The processing may correspond to methods, functions, procedures, subroutines, subroutines, and the like.

1 is a schematic flowchart of an application preloading method according to an embodiment of the present application. The method may be performed by an application preloading device, where the device may be implemented by software and/or hardware, and may be integrated into a mobile terminal. As shown in FIG. 1, the method includes: step 101, step 102, and step 103.

In step 101, it is detected that an application preload event is triggered.

Illustratively, the mobile terminal in the embodiment of the present application may include a mobile device such as a mobile phone, a tablet computer, and a notebook computer. The mobile terminal is loaded with an operating system.

For example, the triggering condition of the application pre-loading event may be set according to an actual situation, which is not specifically limited in this embodiment. For example, the application preload event may be triggered when it is detected that the user's action satisfies a preset condition (such as picking up the mobile terminal, inputting a screen unlocking operation, or inputting a mobile terminal unlocking operation, etc.); or may detect a change in the foreground application. The application preload event is triggered; or the application preload event can be triggered immediately (or after a preset duration) after the pre-loading application's prediction process ends; or it can be triggered at regular intervals. After the application preloading event is triggered, the system may detect that the application preloading event has been triggered by reading the flag bit or receiving the triggering instruction. The specific detection mode is not limited in the embodiment of the present application.

In step 102, a target application to be preloaded is determined.

Exemplarily, the application to be preloaded can be understood as an application that the user may open soon, or may be a fixed application that is preset, or an application that is predicted in a certain manner. The application to be preloaded may include one or more. The target application can be understood as the application to be preloaded that currently needs to be preloaded. The target application can also include one or more. When there is only one application to be preloaded, there is only one corresponding target application; when there are multiple applications to be preloaded, the target application can be one (ie, multiple applications to be preloaded) Determined as the target application one by one, and preloaded in turn), or multiple (it is more than 2 applications to be preloaded as the target application, and at the same time preloading, that is, multiple targets The application's preloading process can be done in parallel).

In an embodiment, a predictive model can be used to predict the preloaded application. The prediction model may be a machine learning model, and the algorithms used may include Recurrent neural networks (RNN), Long Short-Term Memory (LSTM) networks, threshold loop units, simple loop units, and automatic coding. , decision tree, random forest, feature mean classification, classification regression tree, hidden Markov, K-Nearest Neighbor (KNN) algorithm, logistic regression model, Bayesian model, Gaussian model, and KL divergence (Kullback) –Leibler divergence) and so on.

In an embodiment, during the process of using the mobile terminal by the user, the training samples are collected, and the preset initial model is trained by using the training samples, and finally the prediction model for predicting the application to be preloaded is obtained. Illustratively, the elements included in the training sample may include a time series or sequence of sequences in which the application is opened; may include the time, location, and frequency of the application being opened, etc.; may include the operational status of the mobile terminal, such as a mobile data network. Switch status, connection status of the wireless hotspot, identity information of the connected wireless hotspot, currently running application, last foreground application, duration of the current application staying in the background, time when the current application was last switched to the background , plug-in status of the headphone jack, charging status, battery power information, and screen display duration, etc.; may also include data collected by sensors integrated in the mobile terminal, such as motion sensors, light sensors, temperature sensors, humidity sensors, etc. .

Illustratively, the appropriate sample elements can be selected according to the selected machine learning model, and the selected machine learning model can be determined according to the selected sample elements, and can also be combined with the requirements for prediction accuracy and preset speed. The selection of the model and the sample elements and the like are not limited in the embodiment of the present application.

In the embodiment of the present application, determining the target application to be preloaded may include determining a target application to be preloaded according to an output result before the prediction model, or including using the prediction model to perform prediction, and determining a current output result of the prediction model. Preloaded target application.

In step 103, the application interface corresponding to the target application is preloaded with a low power core in the multi-core processor.

Exemplarily, when the multi-core processor is a large-scale core processor (a processor based on a big.LITTLE model), the low-power core is a small core. After the introduction of the Cortex-A15, ARM's market feedback power consumption is a bit too large, so the concept of large and small cores, namely the big.LITTLE model, and the big.LITTLE model can be called heterogeneous multiprocessor (Heterogeneous Multi- in computer terminology). Processing, HMP). In the size core processing, any core can wake up first, or the last one, and can be online at the same time. The working power of the small core is less than the working power of the large core. The number of small cores and large cores are not limited. . In addition, when each core of the multi-core processor is the same, the low-power core may be the core with lower current operating power; or the low-power core may be a core group with fewer cores, for example, an 8-core processor The first six cores can be used to process the foreground application task, and the latter two cores are used for preloading the application interface. At this time, the core group composed of the latter two cores can be regarded as the low power consumption core in the embodiment of the present application.

During the application preloading process, for example, the preloading process of the application interface may involve multiple core work. For example, a large and small core processor may use a large core, which may result in a preloading process. More power consumption may cause the mobile terminal to generate heat or less standby time, which affects the user's use. In addition, if the core resources are occupied during the pre-loading process, it may affect the operation of the foreground application, such as the card. Don't wait. Therefore, in the embodiment of the present application, when the application interface of the target application is preloaded, the use of the processor resource by the mobile terminal is restricted, and only the right to use the low power core is granted, thereby achieving low power preloading. purpose.

The application preloading method provided in the embodiment of the present application detects that an application preloading event is triggered, determines a target application to be preloaded, and preloads the target application corresponding to the low power core in the multicore processor. Application interface. By adopting the above technical solution, the use of system resources for preloading can be restricted during the application preloading process, and the preloading process is prevented from generating excessive power consumption.

In some embodiments, after the application interface corresponding to the target application is preloaded by the low-power core in the multi-core processor, the method further includes: setting a visibility attribute of the pre-loaded application interface to be invisible, The invisibility includes being invisible to the system. The advantage of this setup is that it controls the power consumed by the preloaded application after the application interface is preloaded. The application interface loading process of the preloaded application needs to be completed without the user being visible, and the system needs to perform operations such as interface drawing or rendering, so it needs to be visible to the system, and only the system can be seen to be covered or applied by the foreground application. Off-screen display, etc. After pre-loading, the application interface is still invisible to the user because the user does not actually launch the target application, but it is visible to the system at this time, which will bring some The additional power consumption, for example, when the user has not started the target application for a long time, the application interface of the pre-loaded application is visible to the system for a long time, which increases the system burden and generates excessive unnecessary power consumption. Therefore, the present application In an embodiment, after the application interface preloading is completed, the visible attribute of the application interface is set to be invisible.

In some embodiments, after the pre-loading the application interface corresponding to the target application by the low-power core in the multi-core processor, the method further includes: suspending the target application. The advantage of this setup is that it can further reduce the power consumption that the preloaded application waits for during the actual boot process.

In an embodiment, the suspending the target application comprises: suspending an active window at the top of the task stack corresponding to the target application. The active window can be understood as an independent interface that provides interaction and operation directly to the user. Different interfaces may be used to name the interface in different operating systems. For ease of understanding, the following is an example of an Android operating system.

In the Android system, the active window is called Activity. An Activity is a component responsible for interacting with a user, providing a screen (which can be understood as a screen interface rather than a physical display screen) for the user to interact with a task. In an android application, an Activity is usually a separate screen that can display some controls and listen and handle user events. In the management of the Activity, there are two concepts: Task (task stack) and Stack (active window stack). Task corresponds to an application, Task is used to store Activity, and a Task can store one or more Activity, and these activities follow the principle of "advanced, last in, first out". Stack is used to manage the Task. Usually, a Stack manages the Tasks to which each Activity needs to be displayed on a screen. A Stack can manage one or more Tasks. Of course, Stack also follows the basic management principles of the stack. . The screen described here is not necessarily a completely separate display. Taking "two screens" as an example, these two screens may be just two areas in a complete display that independently display their respective display contents. Of course, if the terminal has two or even more than two independent displays, the "two screens" can also be two separate displays.

In the embodiment of the present application, the Activity at the top of the Task corresponding to the target application is suspended, so that the Activity will enter the operation of onPause->onStop->onDestroy in the Android application life cycle, so that the application will no longer work. Select the top Activity of the Task because the top Activity is the Activity that the application is working on. Pausing the Activity can suspend the application.

In some embodiments, after the application of the target application corresponding to the low-power core in the multi-core processor is preloaded, the method further includes: freezing the process of the target application. The advantage of this setup is that after the process is frozen, the processor resources occupied can be released more completely, further reducing the power consumption of the preloaded application waiting to be actually started.

In an embodiment, the process of freezing the target application includes: writing a process identifier of a process of the target application to a node in a kernel layer corresponding to a frozen attribute in a preset freeze group. Illustratively, using the freezer cgroup of the Linux kernel (freeze group), the process that needs to be frozen is frozen.

In some embodiments, after the freezing the process of the target application, the method further includes: waking up the process of the target application when detecting, by the kernel layer, that the receiver is a preset message of the target application After the preset duration, the process of the target application is re-frozen. The advantage of this setting is to ensure that the frozen target application can be briefly awakened when needed, and communicate with the outside world in time to ensure low power consumption. Take the Android system as an example. The default message can be a binder or a socket. The preset duration may be a preset fixed value, such as 5 seconds, or may be a dynamically changed value, which may be dynamically determined according to the type or content of the received message, which is not limited in this embodiment.

In some embodiments, the preloading the application interface corresponding to the target application by using a low power core in the multi-core processor comprises: adopting a low power core in the multi-core processor, based on a pre-created preloading activity The window stack preloads an application interface corresponding to the target application, wherein the boundary coordinates corresponding to the preloaded active window stack are outside the coordinate range of the display screen. The advantage of this setting is that the application interface of the application that needs to be preloaded can be preloaded based on the preloaded active window stack created outside the display screen, which can complete the preparation work before the application is started to a large extent. , to improve the startup speed of the target application, and does not affect the display content of the foreground application on the display screen.

In the Android system, multi-window mode is supported, which can include split screen mode, picture in picture mode, and free mode (FreeForm). In multi-window mode, the Stack on which the application resides can have its own size, which can include the top, bottom, left, and right coordinates in the coordinate system with the top left corner of the terminal screen as the origin. For example, (a, b, c, d), generally describes the boundary of a rectangle, which can be represented by the coordinates of the upper left corner of the rectangle and the coordinates of the lower right corner, that is, the coordinates of the upper left corner of the rectangle are (a, b), right. The lower corner coordinates are (c, d), and such a rectangular area corresponds to the size of the Stack. The in-app layout in the Stack is based on the size of the Stack, which means that the application interface corresponding to the Activity is displayed within the bounds of the size.

In multi-window mode, multiple applications can be allowed to be visible, both system and user visible and only system visible. Both the system and the user are visible to display on the display screen, and the user can see; only the system visible means that the operating system is visible, and the user is invisible, may be blocked by the application of the foreground or as implemented in the application. Display off-screen display.

In the embodiment of the present application, pre-loading the application interface of the target application outside the display screen may be implemented based on a multi-window mechanism of the operating system, and the size corresponding to the application is set outside the display screen through the multi-window mechanism to achieve The purpose of the user's invisibility is such that it does not affect the display of the foreground application's display content on the display screen.

Generally, in the multi-window mode, there may be multiple types of stacks, such as the Home Stack indicating the stack displayed by the desktop application, the App Stack indicating the Stack displayed by the third-party application, and other split screen stacks, etc., in the above three stacks. The included content can be displayed on the display screen, which is collectively referred to as an application active window stack in the embodiment of the present application. In the embodiment of the present application, a preloaded active window stack (preloaded stack) is added, which is used to represent the stack displayed by the preloaded application, and the boundary coordinates of the preloaded stack are set outside the coordinate range of the display screen, and are to be preloaded. The app can be displayed on the stack. For the Android system, a new stack dedicated to displaying preloaded applications can be created based on the multi-window mechanism of the Android system. In the embodiment of the present application, the new stack is created because the newly created preloaded stack can have its own size and visibility, thereby achieving pre-loading on the display screen.

In the embodiment of the present application, the creation time of the preloaded stack is not limited, and the preloaded stack is in the resident state by default, that is, the preloaded stack is always present; or the terminal is successfully unlocked when the terminal is powered on or the terminal is successfully unlocked. Post-create; can also be created after the application preload event is triggered (can be determined before the target application is determined). In an embodiment, the pre-creating a preloaded active window stack preloading an application interface corresponding to the target application comprises: determining whether there is a pre-created preloaded active window stack; if not, according to the pre Setting a rule to create a preloaded active window stack and preloading an application interface corresponding to the target application based on the created preloaded active window stack; if present, preloading the stack based on the pre-created preloaded active window stack The application interface corresponding to the target application. The advantage of this setting is that after determining the target application to be preloaded, it is determined whether the preloaded stack exists. If it exists, no new configuration is needed, and if it does not exist, the creation is performed, which can save system resources. Understandably, when the target application contains more than one, that is, when multiple applications need to be preloaded continuously in a short time, the preloaded stack is created before the first target application starts loading, then the first Before the two target applications start loading, the preloaded stack exists, and it is not necessary to make the above judgment.

In the embodiment of the present application, the specific process of the application interface corresponding to the preloading of the target application is not limited. For example, the application interface may be drawn and displayed based on the size of the preloaded stack.

In some embodiments, the pre-creating a preloaded active window stack preloading an application interface corresponding to the target application, including: creating a target process corresponding to the target application; pre-creating a pre-loaded active window Creating a task stack corresponding to the target application in the stack; starting an active window corresponding to the target application in the task stack based on the target process; drawing and displaying the target application corresponding to the activated active window Application interface. The advantage of this setting is that the application interface of the target application can be drawn and displayed based on the preloaded active window stack outside the screen coordinate range, without interfering with the operation and display of the foreground application, ensuring system stability and effectively improving The speed at which the target application starts. The creation process of the target process can also include the initialization process of the target process. During the execution of the foregoing steps, the preloading of other resources may be involved, such as application service startup, memory allocation, file content reading, and network data acquisition. The preloading process of other resources is not limited in this embodiment.

In some embodiments, the method further includes: transmitting a forged focus notification to the target application, and maintaining a continuous rendering of the application interface corresponding to the target application and displaying an update for a preset time period based on the forged focus notification. The advantage of this setting is that the application interface can be drawn and displayed while the target application is in focus and visible to the system, improving the completion of the preload without affecting the focus of the foreground application. The focus in the embodiment of the present application is also referred to as an input focus, and the forged focus is independent of the focus corresponding to the foreground application. Generally, for the current Android system, the focus is unique. For example, the input operation such as touch is only effective for the focus. For the input focus information, the system side and the application end are consistent, and once the system side modifies the input focus information, Sending information that the input focus information changes to the application, so as to ensure that the input information of the system end and the application end are consistent. In the embodiment of the present application, the purpose of forging the focus on the application end is achieved by separating the manner in which the system side and the application end input the focus information. In the embodiment of the present application, the pre-loading application is forged focus notification, so that the pre-loading application has the focus information, and the focus information of the system is still correct, so that the pre-loading application can be normally drawn to achieve the purpose of full loading. The focus exists on the system side and the application side. It can be regarded as the server (server) and the client (client). The system side records the application with the focus, and the application saves the flag (flag) to identify whether it has focus. The timing of forging the input focus may be that when the window system of Android adds a window and needs to update the focus, a fake focus notification is generated and sent. The method of forging the focus may be a method of calling the client side of the window to change the focus of the window, so that the window acquires the focus. In an embodiment, the sending of the forged focus notification may be performed based on the Binder mechanism, which is the most common way of inter-process communication of the Android system, adopting the c/s architecture, that is, the client/service architecture.

In the embodiment of the present application, the preset time period may be designed according to actual conditions, for example, may be within a fixed duration range after starting preloading, or may be a period from the start of preloading to the completion of preloading. In some embodiments, the length of the preset time period includes a play duration in which the advertisement is launched or the animation is activated in the target application. Some applications usually play some advertisements or animations during the startup process. The duration of the advertisement or animation is usually from 3 seconds to ten seconds. During the advertisement or animation, the user may not be able to perform any operations. Can wait for the playback to complete, wasting the user's valuable time. The advantage of the setting of the embodiment of the present application is that the startup advertisement or the startup animation can be played out of the screen before the target application is started, and when the target application is started, the main page of the application or other user can be directly operated. Interface to further advance the target time point of the target application and reduce waiting time.

In some embodiments, the method further includes: migrating the preloaded application interface to the display screen for display when receiving the running instruction of the target application. The advantage of this setting is that when the target application really needs to be started, the already-drawn application interface is directly migrated to the display screen for display, which can achieve fast switching of the application interface and improve the startup speed. In addition, when receiving the running instruction of the target application, the method further includes: processing the target application by using the high-power core, restoring the running of the target application, or unfreezing the process of the target application.

In some embodiments, the migrating the application interface corresponding to the target application included in the preloaded active window stack to the display screen for display comprises: including the preloaded active window stack The task stack corresponding to the target application is migrated to the top of the application active window stack; the size information, the configuration information, and the visibility of the task stack are updated, so that the application interface corresponding to the target application is implemented on the display screen. display. The advantage of this setting is that the stability of the interface migration process can be ensured, and the recovery process does not cause problems such as a card screen, a black screen, or a slow migration speed.

For some terminals, such as mobile phones and tablet computers, in order to facilitate the use of the user, the display mode of the display screen usually includes vertical screen display and horizontal screen display, and many applications use the vertical screen mode for display by default, and some applications. The program defaults to display in landscape mode (such as some online games). During the use of the terminal, some applications also switch between horizontal and vertical display as the user holds the direction of the terminal. In some embodiments of the present application, the boundary coordinates corresponding to the preloaded active window stack are (H, 0, 2H, H), the coordinate system corresponding to the boundary coordinates is system coordinates, and the origin of the system coordinates is In the upper left corner of the display screen, H is the length of the long side of the display area of the display screen. That is to say, the edge corresponding to H is the largest side of the display area of the display screen, which is the height of the display screen when the vertical screen is displayed, and the width of the display screen when the horizontal screen is displayed. The purpose of this setting is to take into account the horizontal screen of the display screen, the horizontal display of the preloaded application, and the normal display of some applications. FIG. 2 is a schematic diagram of a relative position relationship between a preloaded active window stack and a display screen display area according to an embodiment of the present application. As shown in FIG. 2, the display screen is in the vertical screen mode, and the origin of the terminal system coordinates is the left vertex (0, 0) of the display screen 201. The width direction of the display screen 201 is the X axis, and the height direction is the Y axis. The boundary coordinates of the loaded Stack 202 are (H, 0, 2H, H), H is the screen height, that is, the area within the solid line rectangle on the left side is the main screen display area, and the area within the rectangular area of the right dashed line is the preloaded display area. FIG. 3 is a schematic diagram of a relative positional relationship between a preloaded active window stack and a display screen display area according to an embodiment of the present application. As shown in FIG. 3, the display screen is in the horizontal screen mode, and the origin of the terminal system coordinates is the left vertex (0, 0) of the display screen 301. The height direction of the display screen 301 is the X axis, and the width direction is the Y axis. The boundary coordinates of the loaded Stack 202 are (H, 0, 2H, H), H is the screen height, that is, the area within the solid line rectangle on the left side is the main screen display area, and the area within the rectangular area of the right dashed line is the preloaded display area.

The reason for pre-loading the various boundaries of the Stack is this:

The horizontal coordinate of the upper left corner is H, which is to prevent the display screen (also called the main screen) from being displayed to the interface of the preloaded application when the horizontal screen is used, because the main screen has the horizontal screen mode and the horizontal screen mode when the main screen is horizontal screen. In order to prevent the main screen display area from displaying the part of the preloaded application, the horizontal coordinate of the upper left corner of the rectangular area corresponding to the preloaded stack is set to the screen height.

The ordinate of the upper left corner is 0, in order to preload the application to correctly calculate the status bar height. In order to better design the user interface (UI), the Android application will customize the top status bar. If the corresponding ordinate of the upper side is not equal to 0, the height of the status bar may be wrong.

The horizontal coordinate of the lower right corner is 2H (2 times the screen height), that is, the width of the rectangle corresponding to the preloaded stack = the screen height, in order to preload the size of the stack to include the horizontal screen application at the time of preloading (ie, the application interface is a horizontal screen) Display mode application).

The ordinate of the lower right corner is H, that is, the height of the rectangle corresponding to the preloaded stack = the height of the screen, in order to preload the size of the stack to include the vertical screen application at the time of preloading.

For the above reasons, the inventor sets the size of the preloaded stack to (H, 0, 2H, H).

FIG. 4 is a schematic flowchart of still another application preloading method according to an embodiment of the present disclosure, where the method includes the following steps: Step 401 to Step 406.

In step 401, it is detected that an application preload event is triggered.

In step 402, a target application to be preloaded is determined.

In step 403, the small core in the large and small core processor is used to preload the application interface corresponding to the target application based on the pre-created preloaded active window stack.

In step 404, the visibility attribute of the pre-loaded application interface is set to be invisible.

In step 405, the active window at the top of the task stack corresponding to the target application is suspended.

It can be understood that there may be multiple application interfaces that need to be preloaded in the target application, and the visibility property of the application interface may be set to be invisible each time an application interface is drawn (or rendered). After all the application interfaces that need to be preloaded are drawn (or when the target application's preload time reaches the preset time threshold), the active window at the top of the task stack is paused.

In step 406, upon receiving the running instruction of the target application, the active window is restored, and the application interface corresponding to the active window is migrated to the display screen for display.

The application preloading method provided by the embodiment of the present application preloads the application interface of the preloaded application on the offscreen by using a small core in the large and small core processor. After the application interface is drawn, the visibility attribute is set to Invisible, and suspend the active window at the top of its corresponding task stack to reduce the power consumption of the target application waiting for startup. When the user actually launches the target application, the active window is restored and its corresponding application interface is migrated to display. The screen is displayed to effectively increase the startup speed of the target application.

FIG. 5 is a schematic flowchart of another application preloading method according to an embodiment of the present disclosure. As shown in FIG. 5, the method includes: Step 501 to Step 507.

In step 501, it is detected that an application preload event is triggered.

In step 502, a target application to be preloaded is determined.

In step 503, the small core in the large and small core processor is used to preload the application interface corresponding to the target application based on the pre-created preloaded active window stack.

In step 504, the visibility attribute of the pre-loaded application interface is set to be invisible.

In step 505, the process identifier of the process of the target application is written to the node in the kernel layer corresponding to the frozen attribute in the preset freeze group.

For example, in the case of the Android system, the freezer cgroup of the Linux kernel can be used to freeze the process. In an embodiment, a freezer CGroup can be created at boot time or at other times, and the FROZEN typeface is written to the freezer.state node (can be understood as a control file, and the FROZEN typeface is written to the control file for the freezer CGroup. The cgroup.procs node sets the freeze attribute), and writes the pid (process ID) of one or more processes included in the target application to the frozen cgroup.procs node of the cgroup, thereby freezing the process of the target application, thereby Implement the freezing of the target application.

After freezing, when the target application that has been frozen by the kernel monitors has a binder or socket message, the frozen target application is briefly awakened and then re-entered.

In step 506, it is determined whether a running instruction of the target application is received, and if so, step 507 is performed; otherwise, step 506 is repeatedly executed.

In step 507, the process of the target application is thawed, and the current application interface corresponding to the target application included in the preloaded active window stack is migrated to the display screen for display.

Exemplarily, a frozen subdirectory can be set under the root directory, the process in the root directory is an unfrozen process, and the process in the frozen subdirectory is a freeze process. When the process of the target application needs to be frozen, the corresponding process ID can be written to the file node in the frozen subdirectory; when thawed, the process ID can be written into the root directory to complete the thaw.

In an embodiment, for example, /dev/freezer/ is the root directory, there is no freezer.state node in the root directory, and the root directory may include the subdirectory /dev/freezer/elsa_freezing2 (equivalent to the newly created freezer CGroup). This subdirectory contains the file node freezer.state, and the content of freezer.state is FROZEN. When the process needs to be frozen, the pid of the process is written to the cgroup.procs node in the subdirectory. When the process needs to be thawed, the pid of the process is written to the root directory. Since there is no freezer.state node in the root directory, it can be implemented. Thaw, at this point, the pid of the thawed process will be automatically deleted in the cgroup.procs node.

The application preloading method provided by the embodiment of the present application preloads the application interface of the preloaded application on the offscreen by using a small core in the large and small core processor. After the application interface is drawn, the visibility attribute is set to Invisible, freezing the process of the target application to reduce the power consumption of the target application waiting for the startup process. When the user actually starts the target application, the application process is thawed, and the corresponding application interface is migrated to the display screen for display. Effectively increase the startup speed of the target application.

FIG. 6 is a structural block diagram of an application preloading apparatus according to an embodiment of the present disclosure. The apparatus may be implemented by software and/or hardware, and is generally integrated in a mobile terminal, and may execute an application preloading method. Preloading. As shown in FIG. 6, the device includes an event trigger detection module 601, an application determination module 602, and a preload module 603.

The event trigger detection module 601 is configured to detect whether an application preload event is triggered;

An application determining module 602, configured to determine a target application to be preloaded when detecting that an application preloading event is triggered;

The preloading module 603 is configured to preload an application interface corresponding to the target application by using a low power core in the multi-core processor.

The application preloading device provided in the embodiment of the present application detects that an application preload event is triggered, determines a target application to be preloaded, and preloads the target application corresponding to the low power core in the multicore processor. Application interface. By adopting the above technical solution, the use of system resources for preloading can be restricted during the application preloading process, and the preloading process is prevented from generating excessive power consumption.

In an embodiment, the apparatus further comprises:

a visibility setting module, configured to set a visibility attribute of the pre-loaded application interface to be invisible after the application interface corresponding to the target application is preloaded by the low-power core in the multi-core processor, Not visible includes not visible to the system.

In an embodiment, the apparatus further comprises:

The application suspending module is configured to suspend the target application after the application interface corresponding to the target application is preloaded by the low-power core in the multi-core processor;

The application freeze module is configured to freeze the process of the target application after the application interface corresponding to the target application is preloaded by the low power core in the multi-core processor.

In an embodiment, the suspending the target application comprises:

Suspending an active window at the top of the task stack corresponding to the target application;

The process of freezing the target application includes:

Write the process identifier of the process of the target application to the node in the kernel layer corresponding to the frozen attribute in the preset frozen group.

In an embodiment, the apparatus further comprises:

Applying a defrosting module, configured to, after the process of freezing the target application, thaw the process of the target application when detecting, by the kernel layer, that the receiver is a preset message of the target application;

The application freezing module is further configured to: after the process of the target application is thawed, after the preset duration, the process of the target application is re-frozen.

In an embodiment, the low-power core in the multi-core processor preloads an application interface corresponding to the target application, including:

Using a low-power core in the multi-core processor, pre-loading the application interface corresponding to the target application based on the pre-created preload active window stack, wherein the boundary coordinates of the preloaded active window stack are located at the coordinates of the display screen Outside the scope.

In an embodiment, the preloading module is further configured to:

Determining whether there is a pre-created preloaded active window stack; in response to the absence of a pre-created preloaded active window stack, creating a preloaded active window stack according to a preset rule, and preloading the stack based on the created preloaded active window stack An application interface corresponding to the target application; in response to the pre-created preloaded active window stack, preloading an application interface corresponding to the target application based on the pre-created preloaded active window stack.

In an embodiment, the preloading module is further configured to:

Creating a target process corresponding to the target application; creating a task stack corresponding to the target application in a pre-created preload active window stack; and starting the target application corresponding to the target process in the task stack based on the target process An active window; draws and displays an application interface corresponding to the target application based on the activated active window.

In an embodiment, the apparatus further comprises:

The interface migration module is configured to, when receiving the running instruction of the target application, migrate the pre-loaded application interface to the display screen for display.

The embodiment of the present application further provides a storage medium including computer executable instructions for executing an application preloading method when executed by a computer processor, the method comprising:

An application preload event is detected to be triggered;

Determining the target application to be preloaded;

Storage media - any of a variety of types of memory devices or storage devices. The term "storage medium" is intended to include: a mounting medium such as a CD-ROM, a floppy disk or a tape device; a computer system memory or a random access memory such as DRAM, DDRRAM, SRAM, EDORAM, Rambus RAM, etc.; Volatile memory, such as flash memory, magnetic media (such as hard disk or optical storage); registers or other similar types of memory elements, and the like. The storage medium may also include other types of memory or a combination thereof. Additionally, the storage medium may be located in a first computer system in which the program is executed, or may be located in a different second computer system, the second computer system being coupled to the first computer system via a network, such as the Internet. The second computer system can provide program instructions to the first computer for execution. The term "storage medium" can include two or more storage media that can reside in different locations (eg, in different computer systems connected through a network). A storage medium may store program instructions (eg, embodied as a computer program) executable by one or more processors.

Of course, the storage medium containing the computer executable instructions provided by the embodiment of the present application is not limited to the application preloading operation as described above, and may also execute the application provided by any embodiment of the present application. Related operations in the preload method.

The embodiment of the present application provides a mobile terminal, where the application preloading device provided by the embodiment of the present application can be integrated. FIG. 7 is a schematic structural diagram of a mobile terminal according to an embodiment of the present application. The mobile terminal 700 can include a memory 701, a processor 702, and a computer program stored on the memory and executable by the processor, and the processor 702 executes the computer program to implement the application program as described in the embodiment of the present application. Load method.

The mobile terminal provided by the embodiment of the present application can limit the use of system resources for preloading in the application preloading process, and avoid excessive power consumption in the preloading process.

FIG. 8 is a schematic structural diagram of another mobile terminal according to an embodiment of the present disclosure. The mobile terminal may include: a housing (not shown), a memory 801, and a central processing unit (CPU) 802 (again The processor is referred to as a CPU, a circuit board (not shown), and a power supply circuit (not shown). The circuit board is disposed inside a space enclosed by the casing; the CPU 802 and the memory 801 are disposed on the circuit board; and the power circuit is configured to supply power to each circuit or device of the mobile terminal The memory 801 is configured to store executable program code; the CPU 802 runs a computer program corresponding to the executable program code by reading executable program code stored in the memory 801 to implement the following steps:

An application preload event is detected to be triggered;

Determining the target application to be preloaded;

The mobile terminal further includes: a peripheral interface 803, a radio frequency (RF) circuit 805, an audio circuit 806, a speaker 811, a power management chip 808, an input/output (I/O) subsystem 809, and other inputs/controls. Device 810, touch screen 812, other input/control devices 810, and external port 804 are communicated via one or more communication buses or signal lines 807.

It should be understood that the illustrated mobile terminal 800 is merely one example of a mobile terminal, and that the mobile terminal 800 may have more or fewer components than those shown in the figures, and two or more components may be combined. Or it can have different component configurations. The various components shown in the figures can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and/or application specific integrated circuits.

The mobile terminal for applying preloading provided in this embodiment is described in detail below. The mobile terminal takes a mobile phone as an example.

The memory 801 can be accessed by the CPU 802, the peripheral interface 803, etc., and the memory 801 can include a high speed random access memory, and can also include a non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices. Or other volatile solid-state storage devices.

Peripheral interface 803, which can connect the input and output peripherals of the device to CPU 802 and memory 801.

I/O subsystem 809, which can connect input and output peripherals on the device, such as touch screen 812 and other input/control devices 810, to peripheral interface 803. The I/O subsystem 809 can include a display controller 8091 and one or more input controllers 8092 for controlling other input/control devices 810. Wherein, one or more input controllers 8092 receive electrical signals from other input/control devices 810 or transmit electrical signals to other input/control devices 810, and other input/control devices 810 may include physical buttons (press buttons, rocker buttons, etc.) ), dial, slide switch, joystick, click wheel. It is worth noting that the input controller 8092 can be connected to any of the following: a keyboard, an infrared port, a USB interface, and a pointing device such as a mouse.

The touch screen 812 is an input interface and an output interface between the user mobile terminal and the user, and displays the visual output to the user. The visual output may include graphics, text, icons, videos, and the like.

Display controller 8091 in I/O subsystem 809 receives an electrical signal from touch screen 812 or an electrical signal to touch screen 812. The touch screen 812 detects the contact on the touch screen, and the display controller 8091 converts the detected contact into an interaction with the user interface object displayed on the touch screen 812, that is, realizes human-computer interaction, and the user interface object displayed on the touch screen 812 may be running. The icon of the game, the icon of the network to the corresponding network, and the like. It is worth noting that the device may also include a light mouse, which is a touch sensitive surface that does not display a visual output, or an extension of a touch sensitive surface formed by the touch screen.

The RF circuit 805 is mainly configured to establish communication between the mobile phone and the wireless network (ie, the network side), and implement data reception and transmission between the mobile phone and the wireless network. For example, sending and receiving short messages, emails, and the like. Specifically, the RF circuit 805 receives and transmits an RF signal, which is also referred to as an electromagnetic signal, and the RF circuit 805 converts the electrical signal into an electromagnetic signal or converts the electromagnetic signal into an electrical signal, and through the electromagnetic signal and communication network and other devices Communicate. RF circuitry 805 may include known circuitry for performing these functions including, but not limited to, an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec CODER-DECoder (CODEC) chipset, Subscriber Identity Module (SIM), etc.

The audio circuit 806 is primarily configured to receive audio data from the peripheral interface 803, convert the audio data into an electrical signal, and transmit the electrical signal to the speaker 811.

The speaker 811 is arranged to restore the voice signal received by the mobile phone from the wireless network through the RF circuit 805 to sound and play the sound to the user.

The power management chip 808 is configured to provide power and power management for the hardware connected to the CPU 802, the I/O subsystem, and the peripheral interface.

The application preloading device, the storage medium, and the mobile terminal provided in the foregoing embodiments may perform the application preloading method provided by any embodiment of the present application, and have corresponding functional modules and beneficial effects for executing the method. For technical details that are not described in detail in the above embodiments, reference may be made to the application preloading method provided by any embodiment of the present application.

Claims

An application preloading method, including:

An application preload event is detected to be triggered;

Determining the target application to be preloaded;

The application interface corresponding to the target application is preloaded with a low power core in the multi-core processor.
The method of claim 1, after the application of the application interface corresponding to the target application by the low-power core in the multi-core processor, the method further includes:

The visibility attribute of the pre-loaded application interface is set to be invisible, and the invisibility includes invisibility to the system.
The method of claim 1, after the application of the application interface corresponding to the target application by the low-power core in the multi-core processor, the method further includes:

Pausing the target application, or freezing the process of the target application.
The method of claim 3, wherein

The suspending the target application includes:

Suspending an active window at the top of the task stack corresponding to the target application;

The process of freezing the target application includes:

Write the process identifier of the process of the target application to the node in the kernel layer corresponding to the frozen attribute in the preset frozen group.
The method of claim 3, after the freezing the process of the target application, further comprising:

Thawing the process of the target application when detecting, by the kernel layer, that the recipient is a preset message of the target application;

After the preset duration, the process of the target application is re-frozen.
The method according to any one of claims 1-5, wherein the application interface corresponding to the target application is preloaded by using a low-power core in the multi-core processor, including:

Using a low-power core in the multi-core processor, pre-loading the application interface corresponding to the target application based on the pre-created preload active window stack, wherein the boundary coordinates of the preloaded active window stack are located at the coordinates of the display screen Outside the scope.
The method of claim 6, wherein the pre-creating a preloaded active window stack preloads an application interface corresponding to the target application, comprising:

Determine whether there is a pre-created preloaded active window stack;

Responding to the absence of a pre-created preloaded active window stack, creating a preloaded active window stack according to a preset rule, and preloading an application interface corresponding to the target application based on the created preloaded active window stack;

In response to the pre-created preloaded active window stack, an application interface corresponding to the target application is preloaded based on the pre-created preloaded active window stack.
The method of claim 6, wherein the pre-creating a preloaded active window stack preloads an application interface corresponding to the target application, comprising:

Creating a target process corresponding to the target application;

Creating a task stack corresponding to the target application in a pre-created preloaded active window stack;

And launching, according to the target process, an activity window corresponding to the target application in the task stack; and drawing and displaying an application interface corresponding to the target application based on the activated activity window.
The method of claim 6 further comprising:

Upon receiving the running instruction of the target application, the preloaded application interface is migrated to the display screen for display.
An application preloading device comprising:

An event trigger detection module configured to detect whether an application preload event is triggered;

An application determining module, configured to determine a target application to be preloaded when detecting that an application preloading event is triggered;

The preloading module is configured to preload the application interface corresponding to the target application by using a low power core in the multi-core processor.
The apparatus of claim 10 further comprising:

The visibility setting module is set to set the visibility property of the pre-loaded application interface to be invisible, and the invisibility includes invisibility to the system.
The apparatus of claim 10 further comprising:

Applying a pause module, set to pause the target application;

The application freeze module is set to freeze the process of the target application.
The device according to claim 12, wherein

The application suspension module is further configured to: suspend an active window at the top of the task stack corresponding to the target application;

The application freezing module is further configured to: write the process identifier of the process of the target application to a node in the kernel layer that is corresponding to the frozen attribute in the preset frozen group.
The apparatus of claim 12, further comprising:

Applying a defrosting module, configured to thaw the process of the target application after detecting, by the kernel layer, that the recipient is the preset message time of the target application;

The application freezing module is further configured to: after the preset duration, re-freeze the process of the target application.
The device according to any one of claims 10-14, wherein the preloading module is further configured to:

Using a low-power core in the multi-core processor, pre-loading the application interface corresponding to the target application based on the pre-created preload active window stack, wherein the boundary coordinates of the preloaded active window stack are located at the coordinates of the display screen Outside the scope.
The apparatus of claim 15 wherein said preloading module is further configured to:

Determine whether there is a pre-created preloaded active window stack;

Responding to the absence of a pre-created preloaded active window stack, creating a preloaded active window stack according to a preset rule, and preloading an application interface corresponding to the target application based on the created preloaded active window stack;

In response to the pre-created preloaded active window stack, an application interface corresponding to the target application is preloaded based on the pre-created preloaded active window stack.
The apparatus of claim 15 wherein said preloading module is further configured to:

Creating a target process corresponding to the target application;

Creating a task stack corresponding to the target application in a pre-created preloaded active window stack;

And launching, according to the target process, an activity window corresponding to the target application in the task stack; and drawing and displaying an application interface corresponding to the target application based on the activated activity window.
The apparatus of claim 15 further comprising:

The interface migration module is configured to, when receiving the running instruction of the target application, migrate the pre-loaded application interface to the display screen for display.
A computer readable storage medium having stored thereon a computer program, wherein the program is executed by a processor to implement the application preloading method of any of claims 1-9.
A mobile terminal, comprising: a memory, a processor, and a computer program stored on the memory and operable by the processor, the processor executing the computer program to implement the application according to any one of claims 1-9 Program preload method.