CN117707639B - Application start acceleration method, electronic device and storage medium - Google Patents

Abstract

The present application provides an application startup acceleration method, an electronic device, and a storage medium. In the method, before the application is started, the L2P mapping of the application startup-related files is loaded into the host memory, so that during the application startup process, the file can be read from the UFS device based on the L2P mapping of the file cached in the host memory, without having to query the L2P mapping of the related file in the UFS device, thereby improving the file reading speed, thereby achieving the effect of accelerating the application startup, and at the same time will not add too much pressure to the host memory.

Description

Application startup acceleration method, electronic device and storage medium

Technical Field

The present application relates to the field of smart terminal technology, and in particular to an application startup acceleration method, an electronic device, and a storage medium.

Background technique

Electronic devices such as smartphones and tablets have become an important part of people's lives. Users can use various applications (hereinafter referred to as applications) provided in electronic devices such as smartphones and tablets to listen to music, play games, etc. to relieve the stress brought by modern fast-paced life.

When users use electronic devices such as smartphones and tablets, they may open applications multiple times. Among them, the startup speed of applications is an important factor in improving user experience. Therefore, how to improve the startup speed of applications is a problem that needs to be solved.

Summary of the invention

The present application provides an application startup acceleration method, an electronic device, and a storage medium. In the method, before the application is started, the L2P mapping of the application startup-related files is loaded into the host memory, so that during the application startup process, the file can be read from the UFS device based on the file L2P mapping cached in the host memory, without having to query the related file L2P mapping in the UFS device, thereby improving the file reading speed and achieving the effect of accelerating the application startup.

In the first aspect, an embodiment of the present application provides an application startup acceleration method. The method is applied to an electronic device, the electronic device includes a host and a UFS device, including: the electronic device monitors that a first application is about to be started; before the first application is started, the electronic device obtains a first file LBA list, reads a first file L2P mapping corresponding to the first file LBA list in the UFS device, and caches the first file L2P mapping to the HPB memory area of the host memory; wherein the first file LBA list is generated based on the first file list, and the files in the first file list are application files corresponding to the first application that affect the performance of the application process; the HPB memory area also caches a second file L2P mapping corresponding to the second file LBA list, the second file LBA list is generated based on the second file list, and the files in the second file list are system files that affect the performance of the application process; the first application is started; wherein, during the process of starting the first application, the relevant files are read in the UFS device based on the first file L2P mapping and the second file L2P mapping cached in the HPB memory area.

Exemplarily, the first application may refer to a hot application obtained based on user usage data statistics. The first file list is an application hot file list corresponding to the first application.

Exemplarily, the second file list refers to a system hotspot file list.

In this way, before the application is started, the L2P mapping of the files related to the application startup is loaded into the host memory in a targeted manner, so that during the application startup process, the file can be read from the UFS device based on the L2P mapping of the file cached in the host memory, without having to query the L2P mapping of the related file in the UFS device, thereby improving the file reading speed and thus achieving the effect of accelerating the application startup. Since the L2P mapping of the file loaded into the host memory is targeted, it will not add too much pressure to the host memory, and during the application startup process, the probability of querying the PBA of the related file based on the L2P mapping of the file cached in the host memory is quite large.

According to the first aspect, the method also includes: during the power-on phase of the electronic device, the electronic device obtains a second file list and generates a second file LBA list based on the second file list; the electronic device reads a second file L2P mapping corresponding to the second file LBA list in a UFS device, and caches the second file L2P mapping to an HPB memory area.

In this way, during the startup phase of the electronic device, the L2P mapping of the system hotspot file is preloaded into the host memory, so that each application can query the relevant file PBA based on the system file L2P mapping cached in the host memory during the startup process, thereby accelerating the reading speed of the relevant system files.

According to the first aspect, or any implementation of the first aspect above, the method further includes:

The electronic device monitors the installation of the first application; after the first application is installed, the electronic device obtains a first file list corresponding to the first application; the electronic device generates a first file LBA list according to the first file list.

In this way, during the installation phase of each application (or each hot application), a corresponding application common file LBA list is generated, so that the corresponding file L2P mapping can be loaded into the host memory before the application is started.

According to the first aspect, or any implementation of the first aspect above, the method further includes:

The electronic device monitors the update or compilation optimization of the first application; after the first application is updated or compiled and optimized, the electronic device updates the first file list corresponding to the first application; the electronic device updates the first file LBA list according to the updated first file list.

In this way, when an application is updated or compiled and optimized, the corresponding common file LBA list is updated to ensure the accuracy of loading the corresponding file L2P mapping according to the file LBA list, thereby increasing the probability of querying the file PBA in the host memory.

According to the first aspect, or any implementation of the first aspect above, the method further includes:

The electronic device obtains a third file list; the third file list is generated by updating the first file list based on the usage scenario of the first application; the electronic device updates the first file LBA list according to the third file list.

In this way, according to the usage scenario of the application, the corresponding common file LBA list is updated to ensure the accuracy of loading the corresponding file L2P mapping according to the file LBA list, thereby increasing the probability of querying the file PBA in the host memory.

According to the first aspect, or any implementation of the first aspect above, the method further includes:

The electronic device monitors that the first application is uninstalled; after the first application is uninstalled, the electronic device deletes the first file LBA list; if the first file L2P mapping corresponding to the first file LBA list is cached in the HPB memory area, the first file L2P mapping is cleared in the HPB memory area.

In this way, when an application is uninstalled, the corresponding common file LBA list is deleted, and then the corresponding file L2P mapping in the host memory is cleared, thereby avoiding wasting the host memory.

According to the first aspect, or any implementation of the first aspect above, the method further includes:

The electronic device detects that a second application is about to be started; before the second application is started, the electronic device obtains a third file LBA list, reads a third file L2P mapping corresponding to the third file LBA list in a UFS device, and caches the third file L2P mapping to an HPB memory area of a host memory; wherein the third file LBA list is generated based on a fourth file list, and the files in the fourth file list are application files corresponding to the second application that affect the performance of the application process; the second application is started; wherein, during the process of starting the second application, relevant files are read in the UFS device based on the third file L2P mapping and the second file L2P mapping cached in the HPB memory area.

In this way, for any application (or hot application), the L2P mapping of files related to application startup can be loaded into the host memory before it is started, so that files can be read from the UFS device based on the L2P mapping of files cached in the host memory during application startup.

According to the first aspect, or any implementation of the first aspect above, the method further includes:

After the second application is started, the electronic device monitors that the first application is about to be started; the electronic device determines that the first file L2P mapping is cached in the HPB memory area; the first application is started; wherein, during the process of starting the first application, based on the first file L2P mapping and the second file L2P mapping cached in the HPB memory area, the relevant files are read in the UFS device.

In this way, the HPB memory area can cache the application file L2P mappings corresponding to multiple applications at the same time. Even if the foreground application switches back and forth between these multiple applications, each application switch can read the relevant files based on the file L2P mapping cached by the host, thereby improving the speed of application switching startup. Moreover, the application file L2P mapping corresponding to each application will not be too much in the host memory, which will not cause pressure on the host memory.

Considering that the more the HPB memory area occupies the host DRAM memory, the greater the pressure on the host DRAM memory, this embodiment can set the upper limit of the application file L2P mapping cached in the HPB memory area, for example, the application file L2P mapping corresponding to n (for example, 10) hot applications can be cached in the HPB memory area at the same time. When the application file L2P mapping corresponding to n hot applications has been cached in the HPB memory area, if the user starts another hot application, the electronic device can first clear the application file L2P mapping corresponding to a hot application cached in the HPB memory area based on the preset refresh policy, and then write the file L2P mapping corresponding to another hot application into the corresponding HPB memory area. For example, the electronic device can clear the application file L2P mapping corresponding to one or more hot applications with a low file LBA query frequency in the HPB memory area. Alternatively, the electronic device can determine the HPB memory area that can be covered based on the preset refresh policy, and write the file L2P mapping corresponding to another hot application into this HPB memory area that can be covered, so as to achieve the effect of file L2P mapping replacement. Exemplarily, the electronic device may use the HPB memory area of the cache and application file L2P mapping corresponding to one or more hot applications with a low file LBA query frequency as the HPB memory area that can be covered.

According to the first aspect, or any implementation of the first aspect above, after the electronic device determines that the L2P mapping of the first file is cached in the HPB memory area, the method further includes:

If the first file LBA list is updated after the first file L2P mapping is cached, the electronic device reacquires the first file LBA list, reads the fourth file L2P mapping corresponding to the first file LBA list in the UFS device, and updates the first file L2P mapping cached in the HPB memory area with the fourth file L2P mapping.

In this way, the accuracy of loading the corresponding application file L2P mapping according to the application file LBA list can be ensured, thereby improving the probability of querying the file PBA in the host memory.

According to the first aspect, or any implementation of the first aspect above, the method further includes:

The electronic device obtains a fifth file list; the fifth file list is generated by updating the second file list based on the usage scenarios of multiple applications; a fourth file LBA list is generated according to the fifth file list; the electronic device reads a fifth file L2P mapping corresponding to the fourth file LBA list in the UFS device, and updates the second file L2P mapping cached in the HPB memory area according to the fifth file L2P mapping.

In this way, the system hotspot file LBA list is updated according to the application usage scenario to ensure the accuracy of loading the corresponding system file L2P mapping according to the file LBA list, thereby increasing the probability of querying the relevant system file PBA in the host memory.

According to the first aspect, or any implementation of the first aspect above, the method further includes:

During the startup process of the first application, if the PBA corresponding to the first target file LBA cannot be found according to the first file L2P mapping and the second file L2P mapping cached in the HPB memory area, the electronic device adds the first target file LBA to the first file LBA list and updates the first file LBA list; wherein the file corresponding to the first target file LBA is not a system file.

In this way, according to the result of querying the file PBA based on the file L2P mapping cached in the HPB memory area, the application hot file LBA list is updated to ensure the accuracy of loading the corresponding application file L2P mapping according to the file LBA list, thereby increasing the probability of querying the relevant application file PBA in the host memory.

According to the first aspect, or any implementation of the first aspect above, the method further includes:

During the startup process of any application, if the PBA corresponding to the second target file LBA cannot be found according to the second file L2P mapping cached in the HPB memory area, the electronic device adds the second target file LBA to the second file LBA list and updates the second file LBA list; wherein the file corresponding to the second target file LBA is a system file.

In this way, according to the result of querying the system file PBA based on the file L2P mapping cached in the HPB memory area, the system hot file LBA list is updated to ensure the accuracy of loading the corresponding system file L2P mapping according to the file LBA list, thereby improving the probability of querying the relevant system file PBA in the host memory.

In a second aspect, an embodiment of the present application provides an electronic device. The electronic device includes: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and when the computer programs are executed by the one or more processors, the electronic device executes the first aspect and the application startup acceleration method of any one of the first aspects.

The second aspect and any implementation of the second aspect correspond to the first aspect and any implementation of the first aspect respectively. The technical effects corresponding to the second aspect and any implementation of the second aspect can refer to the technical effects corresponding to the first aspect and any implementation of the first aspect, which will not be repeated here.

In a third aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium includes a computer program, and when the computer program is executed on an electronic device, the electronic device executes the application startup acceleration method of the first aspect and any one of the first aspects.

The third aspect and any implementation of the third aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the third aspect and any implementation of the third aspect can refer to the technical effects corresponding to the first aspect and any implementation of the first aspect, which will not be repeated here.

In a fourth aspect, an embodiment of the present application provides a computer program product, including a computer program, which, when executed, enables a computer to execute an application startup acceleration method as in the first aspect or any one of the first aspects.

The fourth aspect and any implementation of the fourth aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the fourth aspect and any implementation of the fourth aspect can refer to the technical effects corresponding to the above-mentioned first aspect and any implementation of the first aspect, which will not be repeated here.

In a fifth aspect, the present application provides a chip, the chip comprising a processing circuit and a transceiver pin, wherein the transceiver pin and the processing circuit communicate with each other through an internal connection path, and the processing circuit executes the application startup acceleration method as in the first aspect or any one of the first aspects to control the receiving pin to receive a signal, and to control the sending pin to send a signal.

The fifth aspect and any implementation of the fifth aspect correspond to the first aspect and any implementation of the first aspect, respectively. The technical effects corresponding to the fifth aspect and any implementation of the fifth aspect can refer to the technical effects corresponding to the first aspect and any implementation of the first aspect, which will not be repeated here.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1a is a schematic diagram of an exemplary application scenario;

FIG1b is a schematic diagram of an exemplary application scenario;

FIG2 is a schematic diagram showing an exemplary HPB mechanism;

FIG. 3a is a schematic diagram showing an exemplary method of reading data in a UFS device using L2P mapping based on HPB cache;

FIG3 b is a schematic diagram showing an exemplary method of reading data in a UFS device based on L2P mapping of an SRAM cache of the UFS device;

FIG. 3 c is a schematic diagram exemplarily showing reading data in a UFS device based on L2P mapping in a flash memory of the UFS device;

FIG3 d is a schematic diagram showing a comparison of delays when reading data in a UFS device in different ways;

FIG4 is a schematic diagram showing an exemplary hardware structure of an electronic device;

FIG5 is a schematic diagram showing an exemplary software structure of an electronic device;

FIG6a is a schematic diagram showing exemplary module interaction;

FIG6 b is a schematic diagram showing an exemplary cache L2P mapping in the HPB memory area of the host memory;

FIG6c is a schematic diagram showing exemplary module interactions;

FIG6d is a schematic diagram showing an exemplary change of cache L2P mapping in the HPB memory area of the host memory;

FIG6e is a schematic diagram showing exemplary module interactions;

FIG6f is a schematic diagram showing an exemplary change of cache L2P mapping in the HPB memory area of the host memory;

FIG6g is a schematic diagram showing exemplary module interaction;

FIG7a is a schematic diagram showing exemplary module interaction;

FIG. 7 b is a schematic diagram showing an exemplary change of cache L2P mapping in the HPB memory area of the host memory;

FIG8a is a schematic diagram showing exemplary module interaction;

FIG. 8 b is a schematic diagram showing an exemplary change of cache L2P mapping in the HPB memory area of the host memory.

Detailed ways

The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

The term "and/or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B can mean: A exists alone, A and B exist at the same time, and B exists alone.

The terms "first" and "second" in the description and claims of the embodiments of the present application are used to distinguish different objects rather than to describe a specific order of objects. For example, a first target object and a second target object are used to distinguish different target objects rather than to describe a specific order of target objects.

In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

In the description of the embodiments of the present application, unless otherwise specified, the meaning of "multiple" refers to two or more than two. For example, multiple processing units refer to two or more processing units; multiple systems refer to two or more systems.

With the continuous development of science and technology, electronic technology has also developed rapidly, and the types of electronic products have increased. People have also enjoyed the convenience brought by the development of science and technology. Now people can enjoy the comfortable life brought by the development of science and technology through various types of electronic devices. For example, electronic devices such as smart phones and tablets have become an important part of people's lives. Users can use various applications (hereinafter referred to as applications) provided in electronic devices such as smart phones and tablets to listen to music, play games, etc., to relieve the pressure brought by modern fast-paced life.

When a user uses an electronic device such as a smart phone or a tablet computer, the application program in the electronic device may be started multiple times. For an application program in the electronic device, the startup may include a cold startup and a hot startup.

When the application is started, there is no process of the application in the background of the electronic device. At this time, the system will recreate a new process and assign it to the application. This application startup method is called application cold start (the process of the application does not exist in the background). When the application is cold started, because the system will recreate a new process and assign it to the application, it will first create and initialize the Application class, then create and initialize the MainActivity class (including a series of measurements, layouts, and drawing), and finally display it on the electronic device interface. For example, when a user opens an application for the first time in an electronic device, or when the user opens an application in an electronic device after clearing the current application cache data, the application is started in a cold start mode. Exemplarily, as shown in Figure 1a, when there is no camera application process in the background of the electronic device, the user clicks the icon of the camera application. In response to the user's operation, the electronic device starts the camera application and displays the interface of the camera application. At this time, the camera application is started in a cold start mode.

When the application has been opened, but the user presses the back key, Home key, etc. to make the electronic device display the desktop or other application interface, if the user reopens the application at this time, this application startup method is called application hot start (the process of the application already exists in the background). When the application is hot started, because the system starts the application from the existing process, the system will no longer perform operations corresponding to the Application class, but directly execute operations corresponding to the MainActivity class. That is, when the application is hot started, the system only needs to create and initialize the MainActivity class, without having to create and initialize the Application class. Exemplarily, as shown in Figure 1b, the camera application in the electronic device has been started, that is, when there is a process of the camera application in the background of the electronic device, the user can reopen the camera application to make the camera application run again in the foreground of the electronic device. At this time, the startup method of the camera application is hot start.

Whether it is a cold start or a hot start, the startup speed of an application is an important factor in improving the user experience. Most users want to start the application as quickly as possible. As applications provide more and more functions, more and more resources need to be loaded when starting the application, making the application startup slower and slower. Therefore, how to improve the startup speed of the application is a problem that needs to be solved.

During the application startup process, usually after the application starts to start, the relevant files are read first, then the application process is loaded based on the relevant files, and then the application process is waited for to layout and display the interface. Among them, the files that affect the performance of the application process (specifically, IO block files) can be divided into two categories, one is the general system files, which can be accessed by each application, and the other is the files involved in the application itself, and the files involved in application A itself are only needed to be accessed by application A. It can be understood that whether it is a general system file or a file used by a certain application, it is stored on the storage device of the electronic device.

UFS (Univeral Flash Storage), as a storage technology for non-volatile memory (NVM), is gradually replacing MMC (Multi Media Card) and eMMC (embedded Multi Media Card) to become the main storage standard for electronic devices such as smartphones. UFS can bring higher read and write speeds and more reliable stability to electronic devices such as smartphones. Among them, in the embodiment of the present application, the storage device used to store file data in the electronic device is a UFS device (or UFS device).

HPB (Host Performance Booster) management mechanism is a feature of UFS. It was introduced in the UFS3.1 protocol. It uses the memory (such as DRAM (Dynamic Random Access Memory)) on the host side of electronic devices (such as smartphones, tablets, etc.) to cache the L2P (Logical address to Physical address) mapping table of the UFS device controller (UFSDevice Controller) to improve the read performance of UFS devices, especially the random read performance of UFS devices after long-term use.

For a file, the file system will allocate several logical blocks for storing file data. The file data will eventually be stored on the storage device, that is, the logical blocks corresponding to the file will be written to the flash physical blocks of the storage device.

For UFS devices, since the data of an LBA (Logical Block Adress) may be stored in any physical location of the flash memory, the UFS device needs to maintain a mapping table from the logical block address to the PBA (Physical Block Adress), namely the L2P mapping table (also referred to as the L2P table). The L2P mapping table is a large array: the index is LBA, and the content is the PBA of the LBA in the flash memory. When the storage device reads data according to a certain LBA, it first searches the L2P mapping table to obtain the PBA corresponding to the LBA, and then reads the storage data corresponding to the LBA according to the PBA.

As shown in Figure 2, for UFS devices, DRAM is generally not set, only a small capacity SRAM (Static Random-Access Memory) is set. Therefore, the L2P mapping table is mostly stored in a flash memory device (such as a NAND or NOR-based flash memory device), and the UFS device firmware can also load part of the L2P mapping relationship into the SRAM of the UFS device on demand. The L2P mapping table of the UFS device is cached in multiple levels.

Continuing with reference to FIG. 2 , based on the HPB feature, the L2P (Logical address to Physical address) mapping table of the UFS device can be cached in the memory (such as DRAM) on the host side of the electronic device (such as a smartphone, tablet computer, etc.) to improve the read performance of the UFS device.

For electronic devices that support the HPB feature, the host can read relevant data in the UFS device based on the L2P mapping table of the host-side memory cache, and when the PBA corresponding to the LBA cannot be found based on the L2P mapping table of the host-side memory cache, the host can continue to read relevant data in the UFS device based on the L2P mapping table of the SRAM cache of the UFS device, and when the PBA corresponding to the LBA cannot be found based on the L2P mapping table of the SRAM cache of the UFS device, the host can continue to read relevant data in the UFS device based on the L2P mapping table stored in the flash memory device of the UFS device.

For electronic devices that support the HPB feature, the host can read relevant data in the UFS device based on the L2P mapping table cached in the SRAM of the UFS device, and when the PBA corresponding to the LBA cannot be found in the L2P mapping table cached in the SRAM of the UFS device, the host continues to read relevant data in the UFS device based on the L2P mapping table stored in the flash memory device of the UFS device.

As shown in Figure 3a, when the host reads file data according to the LBA of the file, if the PBA corresponding to the LBA is queried in the L2P mapping table of the host DRAM cache, the PBA can be sent to the address conversion module in the UFS device storage system for address conversion, and then the corresponding file data can be read in the flash storage device according to the converted address.

As shown in Figure 3b, when the host reads file data according to the LBA of the file, if the PBA corresponding to the LBA is queried in the L2P mapping table of the SRAM cache in the UFS device, the PBA can be sent to the address conversion module in the UFS device storage system for address conversion, and then the corresponding file data can be read in the flash storage device according to the converted address.

As shown in Figure 3c, when the host reads file data according to the LBA of the file, if the PBA corresponding to the LBA is not found in the L2P mapping table cached in the SRAM of the UFS device, the PBA corresponding to the LBA will continue to be queried in the L2P mapping table stored in the flash storage device of the UFS device, and after the PBA corresponding to the LBA is found, the PBA is sent to the address conversion module in the storage system of the UFS device for address conversion, and then the corresponding file data can be read in the flash storage device according to the converted address.

For the LBA query hit mode shown in Figures 3a, 3b, and 3c, Figure 3d shows a comparative schematic diagram of the corresponding file read delay. As shown in Figure 3d, the delay when the host reads the relevant data in the UFS device based on the L2P mapping table of the host-side memory cache (that is, the LBA queried by the host hits the L2P mapping table of the host-side memory cache) is roughly the same as the delay when the host reads the relevant data in the UFS device based on the L2P mapping table of the SRAM cache of the UFS device (that is, the LBA queried by the host hits the L2P mapping table of the SRAM cache of the UFS device), and the delay duration is relatively short, that is, the user-perceived delay is relatively short, and the delay is mainly generated by reading data in the flash storage device of the UFS device. However, when the host fails to query the PBA based on the L2P mapping table of the SRAM cache of the UFS device (that is, the LBA queried by the host does not hit the L2P mapping table of the SRAM cache of the UFS device), and then reads related data in the UFS device based on the L2P mapping table stored in the flash memory device of the UFS device (that is, the LBA queried by the host hits the L2P mapping table stored in the flash storage device of the UFS device), the delay will increase. At this time, the user will feel a longer delay, and the delay mainly comes from querying the L2P mapping table in the flash storage device of the UFS device and reading data in the flash storage device of the UFS device.

As for the HPB feature, not many device manufacturers use it at present, because the HPB feature consumes a large amount of host memory (such as DRAM memory). For example, if a UFS device with a capacity of 512G caches the L2P mapping table corresponding to half of its physical addresses on the host side, it will need to occupy 512M of host memory. Moreover, in this case, the theoretical probability that the host will query the PBA corresponding to the LBA based on the L2P mapping table cached in its memory is only 50%. If the host does not query the PBA corresponding to the LBA based on the L2P mapping table cached in its memory, the host needs to re-query the PBA corresponding to the LBA based on the L2P mapping table in the SRAM or flash storage device on the UFS device side. Compared with the host directly re-querying the PBA corresponding to the LBA based on the L2P mapping table in the SRAM or flash storage device on the UFS device side, this situation will also increase the latency caused by "the host queries based on the L2P mapping table cached in its memory but misses". As the capacity of the UFS device increases, the HPB feature will consume more host memory, which will undoubtedly increase the memory pressure on the host side. Once the L2P mapping table of the host-side memory cache misses the LBA queried by the host, the read performance of the UFS device will be further reduced.

The embodiment of the present application provides an application startup acceleration method. In this method, a user experience-oriented HBP management mechanism is adopted to improve the speed at which the electronic device reads related files when the application is started, thereby achieving the beneficial effect of accelerating the startup of the application. Among them, the user experience-oriented HBP management mechanism adopted by the embodiment of the present application not only only requires less host-side memory (such as DRAM memory), but also reduces the probability of not being able to query the LBA of the related file in the L2P mapping table of the host-side memory cache.

As shown in FIG. 4 , a schematic diagram of the structure of the electronic device 100 is shown. Optionally, the electronic device 100 may be a terminal, which may also be referred to as a terminal device. The terminal may be a device with a camera such as a cellular phone or a tablet computer (pad), which is not limited in this application. It should be noted that the schematic diagram of the structure of the electronic device 100 may be applicable to the smart phones in FIG. 1a to FIG. 1b. It should be understood that the electronic device 100 shown in FIG. 4 is only an example of an electronic device, and the electronic device 100 may have more or fewer components than those shown in the figure, may combine two or more components, or may have different component configurations. The various components shown in FIG. 4 may 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 electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor, a gyroscope sensor, an acceleration sensor, a temperature sensor, a motion sensor, an air pressure sensor, a magnetic sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and/or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory.

The electronic device 100 implements the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. In some embodiments, the electronic device 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

The external memory interface 120 can be used to connect an external memory card, such as a UFS memory card, to expand the storage capacity of the electronic device 100. The external memory card (UFS memory card) communicates with the processor 110 through the external memory interface 120 to implement a data storage function. In this embodiment, the UFS memory card supports the HPB feature.

The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121, such as enabling the electronic device 100 to implement the application startup acceleration method in the embodiment of the present application. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

The software system of the electronic device 100 may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system of the layered architecture as an example to exemplify the software structure of the electronic device 100.

FIG. 5 is a software structure block diagram of the electronic device 100 according to an embodiment of the present application.

The layered architecture of the electronic device 100 divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom, namely, the application layer, the application framework layer, the Android runtime (Android Runtime) and the system library, and the kernel layer.

The application layer can include a series of application packages.

As shown in FIG. 5 , the application package may include applications such as call, calendar, map, navigation, music, video, short message, camera, gallery, etc.

The application framework layer provides an application programming interface (API) and a programming framework for the applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 5, the application framework layer may include an HPB management agent (HPB Management Agent), a package manager (or Package Manager Service (PMS)), an activity manager (or Activity Manager Service (AMS)), a window manager (or Window Manager Service (WMS)), a view system, a resource manager, a notification manager, and the like.

The HPB management agent refers to the agent service of the HPB management module in the kernel layer, which can call the HPB management module to perform operations related to the HPB.

In the Android system, AMS, PMS and WMS are three important system services, which are responsible for managing the life cycle of applications, handling the installation and uninstallation of applications, and managing the window views of applications.

As an activity manager service, AMS is mainly responsible for managing and tracking the activity tasks and life cycles of all applications. When an application is opened, AMS starts the process of the application and allocates processor resources and memory to the application. When the application is no longer in the foreground or background, or when the system memory is insufficient, AMS terminates or kills the process of the application.

As a package manager service, PMS is mainly responsible for installing, managing, and uninstalling applications on Android devices. When a new application is installed, PMS will identify all components of the application (such as Activity, Service, and Broadcast Receiver, etc.) and assign corresponding permissions to these components. At the same time, PMS also monitors the status of installed applications to ensure the integrity and security of the applications.

As a window manager service, WMS is mainly responsible for managing the window view on the Android device and controlling the application interface and the correct display and input. WMS is responsible for managing the position, size and layout of the application window, taking care of multitasking and switching between applications, thus ensuring a stable, smooth and consistent user interface.

The power management module can be understood as a functional module located in the application framework layer corresponding to the power management system, which can be used to detect whether the electronic device has entered the shutdown process, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. A display interface can be composed of one or more views. For example, a display interface including a text notification icon can include a view for displaying text and a view for displaying images.

The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

The notification manager enables applications to display notification information in the status bar, which can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, notification information is used to inform the completion of downloads, message reminders, etc. Notification information can also appear in the system top status bar in the form of icons or scroll bar text, such as notifications of applications running in the background, or in the form of dialog windows on the screen. For example, notification information can be a text message in the status bar, a prompt sound, a vibration of an electronic device, a flashing indicator light, etc.

Android Runtime includes core libraries and virtual machines. Android Runtime is responsible for scheduling and management of the Android system.

The core library consists of two parts: one part is the function that needs to be called by the Java language, and the other part is the Android core library.

The application layer and the application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

The system library may include multiple functional modules, such as surface manager, media library, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), etc.

The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as static image files, etc. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

A 2D graphics engine is a drawing engine for 2D drawings.

The kernel layer is the layer between hardware and software. As shown in Figure 5, the kernel layer at least includes the HPB management module, UFS host driver module, file system module, power management module, display driver, sensor driver, etc. Among them, the hardware at least includes the processor, display screen, sensor, UFS device, etc.

In this embodiment, the HPB management module can be used to implement file list management, LBA list management, and HPB memory region management, etc. The HPB memory region can be understood as a memory region (such as a DRAM region) where the host caches the UFP device L2P mapping table based on the HPB protocol.

In this embodiment, the UFS host driver module can be used to refresh the HPB memory area.

The file system module can be understood as a functional module located in the kernel layer corresponding to the file system, which can be used to implement file management, such as allocating logical blocks to each file.

It is understandable that the layers in the software structure shown in FIG5 and the components contained in each layer do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer layers than shown in the figure, and each layer may include more or fewer components, which is not limited in the present application.

It is understandable that in order to implement the application startup acceleration method in the embodiment of the present application, the electronic device includes hardware and/or software modules corresponding to the execution of each function. In combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to be beyond the scope of the present application.

The application startup acceleration method provided in the embodiment of the present application can be applied to the startup process of any application of an electronic device (such as a smart phone, etc.). Optionally, a whitelist can also be set in the electronic device so that the application startup acceleration method provided in the embodiment of the present application can be applied to the startup process of any application in the whitelist. Exemplarily, the application in the whitelist is a hot application.

Considering that the files that affect the performance of the application process can be divided into two categories, one is the general system files, which can be accessed by each application, and the other is the files involved in the application itself. The files involved in application A itself are only needed to be accessed by application A. Accordingly, in the embodiment of the present application, the HPB management module manages two types of file LBA lists, one is the system hotspot file LBA list, which is generated according to the system hotspot file list during the application startup process, and the other is the application file LBA list (or application hotspot file LBA list), which is generated according to the application file list (or application hotspot file list) used during the application startup process. Among them, different applications correspond to different application file LBA lists.

In this way, before an application is started, the HPB memory area in the host memory is pre-refreshed according to the application file LBA list corresponding to the application, that is, the file L2P mapping corresponding to the application file LBA list is refreshed to the HPB memory area, which can reduce the delay in reading related files during the startup of the application and subsequent use, and try to avoid IO page fault problems.

The following uses several scenarios as examples to explain the application startup acceleration method provided in the embodiments of the present application.

scene one

In this scenario, taking the example of a user using a hot application in an electronic device alone, the relevant processing procedures for application installation, application update, application compilation optimization, application startup, and powering on and off the electronic device are explained.

Figures 6a, 6c, 6e and 6g are schematic diagrams of the interaction of the modules. Referring to Figure 6a, the process of the application startup acceleration method provided in the embodiment of the present application specifically includes:

S201, during the initialization phase of the electronic device, the HPB management module applies for an HPB memory area in the host DRAM.

The HPB memory area is used to cache L2P mappings of files related to application startup or operation.

It can be understood that the electronic device initialization phase may be a power-on phase of the electronic device.

Optionally, after the HPB management module applies for the HPB memory area in the host DRAM, if there is no system hotspot file LBA list, the UFS Host driver module can be instructed to first load part of the L2P mapping of the UFS device to the HPB memory area.

S202, the HPB management agent obtains a system hot file list.

Among them, system hot files may refer to system files with high access frequency, which do not change with application switching.

The system hotspot file list refers to a file list composed of common system hotspot files. Exemplarily, the system hotspot file list includes but is not limited to the system file name, the starting page number, the number of pages, etc.

The file pages used by a specific version of an application during startup are basically the same, so the file list used during the application startup process can be monitored to obtain a system hotspot file list during the application startup process and a list of commonly used application files corresponding to each application. For methods of identifying system hotspot files and methods of identifying commonly used application file lists, please refer to the existing technology and will not be repeated here.

S203, the HPB management agent calls the HPB management module to generate a system hotspot file LBA list.

The system hotspot file LBA list refers to an LBA list composed of the LBAs of the system hotspot file. Exemplarily, the system hotspot file LBA list includes but is not limited to the system file name, logical block, and LBA, etc. A system file can correspond to one or more logical blocks, and each logical block corresponds to an LBA.

Exemplarily, the HPB management agent calls a related function provided by the HPB management module to generate a system hotspot file LBA list corresponding to the system hotspot file list through the HPB management module.

S204, the HPB management module generates a system hotspot file LBA list according to the system hotspot file list, and returns the generation result to the HPB management Agent.

Exemplarily, the HPB management module queries the logical blocks allocated by the file system for each system file in the system hot file list, obtains the LBA list corresponding to each system file, and then obtains the system hot file LBA list corresponding to the system hot file list.

For example, the system hotspot file list includes N1 system files, and the system hotspot file LBA list corresponding to the system hotspot file list includes LBAs corresponding to the N1 system files, respectively. One system file corresponds to one or more LBAs.

The generation result returned by the HPB management module to the HPB management agent is used to indicate whether the system hotspot file LBA list has been generated. After the HPB management module generates the system hotspot file LBA list, the generation result indicating that the system hotspot file LBA list has been generated is returned to the HPB management agent.

S205, the HPB management agent calls the HPB management module to refresh the HPB memory area.

Exemplarily, the HPB management agent calls the relevant function provided by the HPB management module to refresh the file L2P mapping in the HPB memory area through the HPB management module. Specifically, in this step, the HPB management agent calls the HPB management module to write the L2P mapping corresponding to the system hotspot file LBA list into the HPB memory area in the host memory.

S206: The HPB management module sends an HPB memory area refresh instruction to the UFS Host driver module.

In this step, the HPB memory area refresh instruction is used to instruct the UFS Host driver module to write the L2P mapping corresponding to the system hotspot file LBA list into the HPB memory area in the host memory.

S207, the UFS Host driver module writes the file L2P mapping corresponding to the system hot file LBA list into the HPB memory area in the host memory according to the HPB memory area refresh instruction, and returns the refresh result to the HPB management module, and the HPB management module returns the refresh result to the HPB management Agent.

For each LBA in the system hotspot file LBA list, the UFS Host driver module queries the UFS device for the corresponding L2P mapping. For example, if the system hotspot file LBAlist includes M1 LBAs, the file L2P mapping corresponding to the system hotspot file LBAlist includes L2P mappings corresponding to the M1 LBAs.

S208: The package manager monitors the installation of application 1 and sends instruction information 1 to the HPB management agent.

The package manager can detect whether an application is installed at the first time through its monitoring interface. When the package manager monitors the installation of an application, it sends corresponding indication information to the HPB management agent to inform the HPB management agent that an application is currently being installed.

Exemplarily, the indication information may include but is not limited to an application package name and an indication type. In indication information 1, the application package name is the package name of application 1, and the indication type is an application installation indication.

S209 , the HPB management agent obtains the file list1 corresponding to the application 1 according to the instruction information 1 .

The file list corresponding to the application refers to a file list consisting of common application files and application hot files (non-system files) during the startup process and/or running process of the application. Exemplarily, the file list corresponding to a certain application includes but is not limited to the file name, the starting page number, the number of pages, etc.

For example, when application 1 is installed, the HPB management agent may traverse the directory of the application installation package name to obtain a file list corresponding to application 1.

The HPB management agent determines, according to the indication information 1 , that the application 1 is being installed, and needs to obtain the file list 1 corresponding to the application 1 , and calls the HPB management module to generate the file LBA list 1 corresponding to the application 1 .

S210 , the HPB management agent calls the HPB management module to generate a file LBA list1 corresponding to the application 1 .

The file LBA list corresponding to the application refers to an LBA list composed of LBAs of commonly used files of the application during the application startup process and/or running process. Exemplarily, the file LBA list corresponding to the application includes but is not limited to the application file name, logical block, and LBA, etc. An application file can correspond to one or more logical blocks, and each logical block corresponds to an LBA.

Exemplarily, the HPB management agent calls a related function provided by the HPB management module to generate a file LBA list 1 corresponding to the application 1 through the HPB management module.

S211, the HPB management module generates a file LBA list 1 corresponding to the application 1, and returns the generation result to the HPB management Agent.

Exemplarily, the HPB management module queries the logical blocks allocated by the file system for each application file in file list1 corresponding to application 1, obtains the LBA list corresponding to each application file, and then obtains the file LBA list1 corresponding to file list1, that is, the file LBA list1 corresponding to application 1.

For example, the file list1 corresponding to application 1 includes N2 application files, and the file LBAlist1 corresponding to application 1 includes LBAs corresponding to the N2 application files respectively, and one application file corresponds to one or more LBAs.

The generation result returned by the HPB management module to the HPB management agent indicates whether the file LBA list1 corresponding to application 1 has been generated. After the HPB management module generates the file LBA list1 corresponding to application 1, the generation result indicating that the file LBA list1 corresponding to application 1 has been generated is returned to the HPB management agent.

S212: The activity manager monitors that application 1 is about to start, and sends indication information 2 to the HPB management agent.

The activity manager can detect whether an application is about to be started through its monitoring interface at the first time. When the activity manager monitors that an application is about to be started, it sends corresponding indication information to the HPB management agent to inform the HPB management agent that an application is currently being installed. Among them, application startup can refer to application cold start or application hot start (such as switching from background operation to foreground operation).

Exemplarily, the indication information may include but is not limited to an application package name and an indication type. In indication information 2, the application package name is the package name of application 1, and the indication type is an application start indication.

S213, the HPB management agent determines whether there is a file LBA list corresponding to the application 1 according to the indication information 2, and if so, executes S214.

When the HPB management agent learns that application 1 is about to be started, it determines whether there is a file LBAlist corresponding to application 1. If not, the startup process of application 1 cannot be accelerated according to the method provided by this embodiment, but the startup process of application 1 is implemented according to the existing technology. In this case, the HPB management agent can re-acquire the file list1 corresponding to application 1 and call the HPB management module to generate the file LBA list1 corresponding to application 1 (that is, execute S209 to S211). In this way, when application 1 is started next time, the startup process of application 1 can be accelerated according to the method provided by this embodiment.

S214, the HPB management agent determines whether the file L2P mapping corresponding to the application 1 is loaded into the HPB memory area, if not, executing S215.

If the file L2P mapping corresponding to application 1 is not loaded into the HPB memory area, the HPB management agent calls the HPB management module to refresh the HPB memory area to check whether the file L2P mapping corresponding to application 1 is loaded into the HPB memory area. Otherwise, the HPB memory area is not refreshed (the process can jump to S218 at this time).

S215, the HPB management agent calls the HPB management module to refresh the HPB memory area.

Exemplarily, the HPB management agent calls the relevant function provided by the HPB management module to refresh the file L2P mapping in the HPB memory area through the HPB management module. Specifically, in this step, the HPB management agent calls the HPB management module to write the L2P mapping corresponding to the application 1 file LBA list1 into the HPB memory area in the host memory.

S216: The HPB management module sends an HPB memory area refresh instruction to the UFS Host driver module.

In this step, the HPB memory area refresh instruction is used to instruct the UFS Host driver module to write the file L2P mapping corresponding to the application 1 file LBA list1 into the HPB memory area in the host memory.

S217, the UFS Host driver module writes the file L2P mapping corresponding to the file LBA list1 into the HPB memory area in the host memory according to the HPB memory area refresh instruction, and returns the refresh result to the HPB management module, and the HPB management module returns the refresh result to the HPB management Agent.

For each LBA in the file LBA list1 corresponding to application 1, the UFS Host driver module queries the UFS device for the corresponding file L2P mapping, and writes these file L2P mappings into the HPB memory area as the file L2P mappings corresponding to application 1. For example, if the file LBA list1 corresponding to application 1 includes M2 LBAs, the file L2P mapping corresponding to application 1 (that is, corresponding to the file LBA list1) includes L2P mappings corresponding to the M2 LBAs.

S218, application 1 is started. During the process of starting application 1, the system reads relevant files in the UFS device based on the L2P mapping of the files cached in the HPB memory area.

Exemplarily, as shown in FIG6b, the HPB memory area of the host DRAM includes a system hotspot file L2P mapping cache and a file L2P mapping cache corresponding to application 1. In this way, when application 1 is started, the system can read the relevant system hotspot files in the UFS device based on the system hotspot file L2P mapping cached in the HPB memory area, and read the common application files corresponding to application 1 in the UFS device based on the file L2P mapping corresponding to application 1 cached in the HPB memory area. It is no longer necessary to read the relevant file L2P mapping from the UFS device, thereby improving the file reading speed, and then achieving the effect of accelerating the startup or operation of application 1.

In an optional implementation, before application 1 is started, the electronic device may also preload the service file corresponding to application 1. When the electronic device preloads the file, the relevant file may be read in the UFS device based on the L2P mapping of the relevant file cached in the HPB memory area, thereby improving the file reading speed and achieving the effect of accelerating file preloading.

Continuing to refer to FIG. 6c , the process of the application startup acceleration method provided in the embodiment of the present application further includes:

S301, the package manager monitors that application 1 is updated or compiled for optimization, and sends instruction information 3 to the HBP management Agent.

Exemplarily, the indication information may include but is not limited to an application package name and an indication type. In indication information 3, the application package name is the package name of application 1, and the indication type is application update or application compilation optimization.

S302, the HBP management Agent updates the file list1 corresponding to the application 1.

After application 1 is updated or compiled and optimized, the HBP management agent re-acquires the file list corresponding to application 1 as file list1.

S303 , the HBP management Agent calls the HBP management module to update the file LBA list1 corresponding to the application 1 .

Exemplarily, the HPB management agent calls a related function provided by the HPB management module to update a file LBA list corresponding to a certain application through the HPB management module.

S304, the HBP management module updates the file LBA list1 corresponding to the application 1 according to the updated file list1, and returns the update result to the HBP management Agent.

The HBP management module regenerates the file LBA list corresponding to the application 1 as the file LBA list 1 according to the updated file list 1, and returns an update result indicating the completion of the update to the HBP management Agent.

S305: The activity manager monitors that application 1 is about to start, and sends indication information 4 to the HBP management Agent.

Exemplarily, the indication information may include but is not limited to an application package name and an indication type. In indication information 4, the application package name is the package name of application 1, and the indication type is application startup.

S306, the HPB management agent determines whether there is a file LBA list corresponding to the application 1 according to the indication information 4, and if so, executes S307.

S307, the HPB management agent determines whether the file L2P mapping corresponding to the application 1 is loaded into the HPB memory area, and if so, executes S308.

S308, the HPB management agent determines whether the file LBA list1 corresponding to the application 1 is updated, and if so, executes S309.

If the file LBA list1 corresponding to application 1 is not updated after the file L2P mapping corresponding to file LBA list1 is cached in the HPB memory area, the HPB management agent does not need to call the HPB management module to refresh the HPB memory area. If the file LBA list1 corresponding to application 1 is updated after the file L2P mapping corresponding to file LBA list1 is cached in the HPB memory area, the HPB management agent needs to call the HPB management module to refresh the HPB memory area to ensure the accuracy of the file L2P mapping corresponding to application 1 cached in the HPB memory area, and to improve the probability of being able to query the relevant file LBA in the HPB memory area.

S309, the HPB management agent calls the HPB management module to refresh the HPB memory area.

S310, the HPB management module sends an HPB memory area refresh instruction to the UFS Host driver module.

In this step, the HPB memory area refresh instruction can be used to instruct the UFS Host driver module to update the file L2P mapping corresponding to application 1 in the HPB memory area. For example, the HPB memory area refresh instruction can be used to instruct the UFS Host driver module to clear the file L2P mapping corresponding to application 1 in the HPB memory area, and then rewrite the file L2P mapping corresponding to the application 1 file LBA list1 (updated) to the HPB memory area in the host memory. For another example, the HPB memory area refresh instruction can be used to instruct the UFS Host driver module to use the file L2P mapping corresponding to the file LBA list after the application 1 is updated, and replace or overwrite the file L2P mapping corresponding to the file LBA list before the application 1 is updated in the HPB memory area.

S311, the UFS Host driver module updates the L2P mapping of the file corresponding to the application 1 cached in the HPB memory area according to the HPB memory area refresh instruction, and returns the memory refresh result to the HPB management module, and the HPB management module returns the memory refresh result to the HPB management Agent.

Exemplarily, the UFS Host driver module clears the file L2P mapping corresponding to application 1 in the HPB memory area according to the HPB memory area refresh instruction, then reads the file L2P mapping corresponding to application 1 file LBA list1 (updated) from the UFS device, and rewrites these file L2P mappings as the file L2P mappings corresponding to application 1 to the HPB memory area in the host memory.

As shown in FIG6d, before the UFS Host driver module refreshes the HPB memory area according to the HPB memory area refresh instruction, the HPB memory area includes the system hotspot file L2P mapping cache and the file L2P mapping cache corresponding to the file LBA list before the application 1 is updated; when the UFS Host driver module refreshes the HPB memory area according to the HPB memory area refresh instruction, the file L2P mapping cache corresponding to the file LBA list before the application 1 is updated is first cleared, and then the file L2P mapping corresponding to the file LBA list after the application 1 is updated is written into the HPB memory area (or, the file L2P mapping corresponding to the file LBA list after the application 1 is updated is first written into the HPB memory area, and then the file L2P mapping cache corresponding to the file LBA list before the application 1 is updated is cleared). That is, after the UFS Host driver module refreshes the HPB memory area according to the HPB memory area refresh instruction, the HPB memory area includes the system hotspot file L2P mapping cache and the file L2P mapping cache corresponding to the file LBA list after the application 1 is updated.

As another example, the UFS Host driver module uses the file L2P mapping corresponding to the file LBA list after application 1 updates according to the HPB memory area refresh instruction to replace or overwrite the file L2P mapping corresponding to the file LBA list before application 1 updates in the HPB memory area.

S312, application 1 is started. During the process of starting application 1, the system reads relevant files in the UFS device based on the L2P mapping of the files cached in the HPB memory area.

For details not explained in this process, please refer to the previous text and will not be repeated here.

In this way, when the application is updated or compiled and optimized, the file LBA list corresponding to the application is updated, and the file L2P mapping corresponding to the application in the HPB memory area is refreshed based on the updated file LBA list, so as to ensure the accuracy of the file L2P mapping corresponding to application 1 cached in the HPB memory area, and improve the probability of querying the file LBA related to the startup or operation of application 1 in the HPB memory area.

Continuing to refer to FIG. 6e , the process of the application startup acceleration method provided in the embodiment of the present application further includes:

S401, the package manager monitors that application 1 is uninstalled, and sends instruction information 5 to the HPB management agent.

Exemplarily, the indication information may include but is not limited to an application package name and an indication type. In indication information 5, the application package name is the package name of application 1, and the indication type is application uninstallation.

S402 , the HPB management agent deletes the file list1 corresponding to the application 1 according to the instruction information 5 .

S403 , the HPB management agent calls the HPB management module to delete the file LBA list1 corresponding to the application 1 .

The HPB management agent determines whether there is a file LBA list corresponding to application 1, and if so, calls the HPB management module to delete the file LBA list corresponding to application 1.

Exemplarily, the HPB management agent calls a related function provided by the HPB management module to delete the file LBA list corresponding to a certain application through the HPB management module.

S404, the HPB management module deletes the file LBA list1 corresponding to the application 1, and sends the deletion result to the HPB management Agent.

S405, the HPB management agent calls the HPB management module to refresh the HPB memory area.

S406: The HPB management module sends an HPB memory area refresh instruction to the UFS Host driver module.

S407, the UFS Host driver module clears the L2P mapping of the file corresponding to the application 1 cached in the HPB memory area according to the refresh instruction, and returns the memory refresh result to the HPB management module, and the HPB management module returns the memory refresh result to the HPB management Agent.

As shown in FIG6f , before the UFS Host driver module refreshes the HPB memory area according to the HPB memory area refresh instruction (that is, before application 1 is uninstalled), the HPB memory area includes the system hotspot file L2P mapping cache and the file L2P mapping cache corresponding to the file LBA list of application 1; after application 1 is uninstalled, when the UFS Host driver module refreshes the HPB memory area according to the HPB memory area refresh instruction, the file L2P mapping cache corresponding to the file LBA list of application 1 in the HPB memory area is cleared.

For details not explained in this process, please refer to the previous text and will not be repeated here.

In this way, when the application is uninstalled, the file LBA list corresponding to the application is deleted, and then the file L2P mapping corresponding to the file LBA list in the HPB memory area is cleared to avoid wasting the HPB memory space of the host DRAM.

Continuing to refer to FIG. 6g , the process of the application startup acceleration method provided in the embodiment of the present application further includes:

S501: The power management module monitors that the electronic device is about to shut down, and sends an instruction message 6 to the HPB management Agent.

Among them, indication information 6 is used to indicate that the electronic device is about to be shut down.

S502: The HPB management agent stores a list of hot files in the system and a list of files corresponding to each application.

When the electronic device is about to shut down, the HPB management agent stores the system hotspot file list and the file list corresponding to each application in the UFS device, so that the electronic device can read them in the UFS device when it is turned on next time.

S503, the HPB management agent calls the HPB management module to store the file LBA list.

Exemplarily, the HPB management agent calls a related function provided by the HPB management module to store the file LBA list through the HPB management module.

S504, the HPB management module stores the system hotspot file LBA list and the file LBAlist corresponding to each application, and returns the storage result to the HPB management Agent.

The HPB management module stores the system hotspot file LBA list and the file LBA list corresponding to each application in the UFS device, so that the electronic device can read it in the UFS device when it is turned on next time.

S505: The power management module detects that the electronic device is turned on and sends instruction information 7 to the HPB management Agent.

The indication information 7 is used to instruct the electronic device to turn on.

S506, during the initialization phase of the electronic device, the HPB management module applies for an HPB memory area in the host DRAM.

S507, after receiving the instruction information 7, the HPB management agent determines whether there is a system hotspot file LBAlist, and if so, executes S508.

If the system hotspot file LBA list does not exist, S202 to S207 as shown in FIG. 6a may be executed to generate a system hotspot file LBA list, and then the HPB memory area is refreshed based on the system hotspot file LBA list, which will not be described in detail here.

S508, the HPB management agent calls the HPB management module to refresh the HPB memory area.

S509: The HPB management module sends an HPB memory area refresh instruction to the UFS Host driver module.

In this step, the HPB memory area refresh instruction is used to instruct the UFS Host driver module to write the file L2P mapping corresponding to the system hot file LBA list into the HPB memory area.

S510, the UFS Host driver module reads the file L2P mapping corresponding to the system hotspot file LBA list, writes it into the HPB memory area, and returns the refresh result to the HPB management module, and the HPB management module returns the refresh result to the HPB management Agent.

The UFS Host driver module reads the file L2P mapping corresponding to the system hot file LBA list in the UFS device according to the HPB memory area refresh instruction, and writes the file L2P mapping corresponding to the system hot file LBA list into the HPB memory area.

For details not explained in this process, please refer to the previous text and will not be repeated here.

In this way, during the subsequent application startup process, the system can read the relevant system hot files in the UFS device based on the L2P mapping of the system hot files cached in the HPB memory area, thereby improving the file reading speed and achieving the effect of accelerating application startup.

After the electronic device is restarted, the activation of any hotspot application in the electronic device may be described in S212 to S218 shown in FIG. 6 a , which will not be described in detail herein.

Scene 2

In this scenario, the application startup acceleration method provided by the embodiment of the present application is explained by taking the case that a user uses multiple hot applications in an electronic device at the same time as an example. In the following process, the user switches the foreground application of the electronic device between application 1 and application 2 as an example for explanation.

FIG7a is a schematic diagram of the interaction between the modules. Referring to FIG7a , the process of the application startup acceleration method provided in the embodiment of the present application specifically includes:

S601, after application 1 in the electronic device is started, application 1 is switched to background operation or closed.

After application 1 is started, the user exits application 1 in the foreground, application 1 is switched to run in the background, or the user closes application 1.

S602: The activity manager monitors that application 2 is about to start, and sends an indication message 8 to the HPB management agent.

Exemplarily, the indication information may include but is not limited to an application package name and an indication type. In indication information 8, the application package name is the package name of application 2, and the indication type is an application start indication.

S603, the HPB management agent determines whether there is a file LBA list corresponding to the application 2 according to the indication information 8, and if so, executes S604.

The LBA list of the file corresponding to the application 2 may be generated when the application 2 is installed, or may be generated when the application 2 is started for a certain time, and is stored in the UFS device when the computer is shut down.

S604, the HPB management agent determines whether the file L2P mapping corresponding to the application 2 is loaded into the HPB memory area, if not, executing S605.

S605, the HPB management agent calls the HPB management module to refresh the HPB memory area.

S606: The HPB management module sends an HPB memory area refresh instruction to the UFS Host driver module.

In this step, the HPB memory area refresh instruction is used to instruct to write the file L2P mapping corresponding to the application 2 into the HPB memory area.

S607, the UFS Host driver module writes the file L2P mapping corresponding to the file LBA list of application 2 into the HPB memory area in the host memory according to the HPB memory area refresh instruction, and returns the refresh result to the HPB management module, and the HPB management module returns the refresh result to the HPB management Agent.

For each LBA in the file LBA list2 corresponding to application 2, the UFS Host driver module queries the UFS device for the corresponding file L2P mapping, and writes these file L2P mappings as the file L2P mappings corresponding to application 2 into the HPB memory area.

As shown in FIG7b , before application 2 is started, the HPB memory area of the host DRAM includes the system hotspot file L2P mapping cache and the file L2P mapping cache corresponding to application 1. When application 2 is about to be started, the HPB memory area is refreshed, and the refreshed HPB memory area includes the system hotspot file L2P mapping cache, the file L2P mapping cache corresponding to application 1, and the file L2P mapping cache corresponding to application 2.

S608, application 2 is started. During the process of starting application 2, the system reads relevant files in the UFS device based on the L2P mapping of the files cached in the HPB memory area.

S609: After application 2 is switched to background operation or closed, the activity manager monitors that application 1 is about to start, and sends indication information 9 to the HPB management agent.

In indication information 9, the application package name is the package name of application 1, and the indication type is an application start indication.

S610, the HPB management agent determines whether there is a file LBA list corresponding to the application 1 according to the indication information 9, and if so, executes S611.

The LBA list of the file corresponding to the application 1 may be generated when the application 1 is installed, or may be generated when the application 1 is started for a certain time, and is stored in the UFS device when the computer is shut down.

S611, the HPB management agent determines whether the file L2P mapping corresponding to the application 1 is loaded into the HPB memory area, and if so, executes S612.

S612, application 1 is started. During the process of starting application 1, the system reads relevant files in the UFS device based on the L2P mapping of the files cached in the HPB memory area.

For details not explained in this process, please refer to the previous text and will not be repeated here.

Since the HPB memory area includes the system hotspot file L2P mapping cache, the file L2P mapping cache corresponding to application 1, and the file L2P mapping cache corresponding to application 2, when the user switches between application 1 and application 2, no matter which application is about to be started, the file in the UFS device can be read based on the file L2P mapping cached in the HPB memory area, thereby improving the file reading speed and accelerating the application startup.

Considering that the more the HPB memory area occupies the host DRAM memory, the greater the pressure on the host DRAM memory, this embodiment can set the upper limit of the application file L2P mapping cached in the HPB memory area, for example, the application file L2P mapping corresponding to n (for example, 10) hot applications can be cached in the HPB memory area at the same time. When the application file L2P mapping corresponding to n hot applications has been cached in the HPB memory area, if the user starts another hot application, the electronic device can first clear the application file L2P mapping corresponding to a hot application cached in the HPB memory area based on the preset refresh policy, and then write the file L2P mapping corresponding to another hot application into the corresponding HPB memory area. For example, the electronic device can clear the application file L2P mapping corresponding to one or more hot applications with a low file LBA query frequency in the HPB memory area. Alternatively, the electronic device can determine the HPB memory area that can be covered based on the preset refresh policy, and write the file L2P mapping corresponding to another hot application into this HPB memory area that can be covered, so as to achieve the effect of file L2P mapping replacement. Exemplarily, the electronic device may use the HPB memory area of the cache and application file L2P mapping corresponding to one or more hot applications with a low file LBA query frequency as the HPB memory area that can be covered.

Scene 3

In this scenario, the electronic device dynamically updates the system hot file list and the application file list corresponding to each application, and then dynamically updates the corresponding system hot file LBA list and the application file LBA list corresponding to each application. In this way, after refreshing the HPB memory area according to the system hot file LBA list and the application file LBA list, the accuracy of the L2P mapping of the files cached in the HPB memory area can be ensured, avoiding waste of HPB memory resources, and increasing the probability of querying the relevant file LBA in the HPB memory area.

FIG8a is a schematic diagram of the interaction between the modules. Referring to FIG8a, the process of the application startup acceleration method provided in the embodiment of the present application specifically includes:

S701, the HPB management agent obtains an updated system hotspot file list.

As the device system is updated or user behavior changes, hot applications may change, system hot files may change, and common files corresponding to each application may also change. Therefore, in the embodiment of the present application, the HPB management agent dynamically updates the system hot file list and the application file list corresponding to each hot application.

In an embodiment of the present application, statistics can be collected for system files and application files involved in the startup and operation process of each application, and the system hot file list and the application file list corresponding to each application can be dynamically updated according to the statistical results. For example, system files with a usage frequency exceeding threshold 1 are used as system hot files. For another example, for files used by each hot application itself, if the file usage frequency exceeds threshold 2, the file is used as an application hot file corresponding to the corresponding hot application.

Exemplarily, the HPB management agent can obtain the updated system hotspot file list on the cloud server side, or on the relevant functional block side of the electronic device, or generate the updated system hotspot file list based on relevant statistical results, which is not limited in this embodiment.

S702, the HPB management agent updates the system hot file list.

The HPB management agent can use the updated system hot file list to replace the existing system hot file list, thereby achieving the effect of updating the system hot file list.

S703, the HPB management agent calls the HPB management module to update the system hotspot file LBA list.

S704, the HPB management module updates the system hot file LBA list according to the system hot file list, and returns the update result to the HPB management Agent.

The HBP management module regenerates the system hotspot file LBA list according to the updated system hotspot file list to replace the existing system hotspot file LBA list, and returns an update result indicating the completion of the update to the HBP management Agent.

As an optional implementation, the events in which the file LBA is not queried in the HPB memory area (or the file LBA miss event) involved in the startup and operation process of each application can also be counted, and the file LBA corresponding to the LBAmiss event is updated to the corresponding file LBA list. For example, during the startup process of a certain application, when the LBA of a certain system file is queried in the HPB memory area, if the corresponding file L2P mapping is not queried, it is determined that a file LBA miss event occurs, and the LBA of the system file is added to the system hotspot file LBA list, and the system hotspot file LBA list is updated.

S705, the HPB management agent calls the HPB management module to refresh the HPB memory area.

S706: The HPB management module sends an HPB memory area refresh instruction to the UFS Host driver module.

In this step, the HPB memory area refresh instruction can be used to instruct the UFS Host driver module to update the file L2P mapping corresponding to the system hotspot file LBAlist in the HPB memory area. For example, the HPB memory area refresh instruction can be used to instruct the UFS Host driver module to clear the file L2P mapping corresponding to the system hotspot file LBA list in the HPB memory area, and then rewrite the file L2P mapping corresponding to the system hotspot file LBA list (updated) to the HPB memory area in the host memory. For another example, the HPB memory area refresh instruction can be used to instruct the UFS Host driver module to use the file L2P mapping corresponding to the updated system hotspot file LBA list to replace or overwrite the file L2P mapping corresponding to the system hotspot file LBA list before the update in the HPB memory area.

S707, the UFS Host driver module updates the file L2P mapping corresponding to the system hot file LBA list cached in the HPB memory area according to the HPB memory area refresh instruction, and returns the memory refresh result to the HPB management module, and the HPB management module returns the memory refresh result to the HPB management Agent.

Exemplarily, the UFS Host driver module clears the file L2P mapping corresponding to the system hot file LBA list in the HPB memory area according to the HPB memory area refresh instruction, then reads the file L2P mapping corresponding to the system hot file LBA list (updated) from the UFS device, and rewrites these file L2P mappings as the file L2P mappings corresponding to the system hot file LBA list to the HPB memory area in the host memory.

As shown in FIG8b, before the UFS Host driver module refreshes the HPB memory area according to the HPB memory area refresh instruction, the HPB memory area includes a system hot file L2P mapping cache corresponding to the system hot file LBA list before the update; when the UFS Host driver module refreshes the HPB memory area according to the HPB memory area refresh instruction, the system hot file L2P mapping cache corresponding to the system hot file LBA list before the update is first cleared, and then the system hot file L2P mapping corresponding to the updated system hot file LBA list is written into the HPB memory area (or, the system hot file L2P mapping corresponding to the updated system hot file LBA list is first written into the HPB memory area, and then the system hot file L2P mapping cache corresponding to the system hot file LBA list before the update is cleared). That is, after the UFS Host driver module refreshes the HPB memory area according to the HPB memory area refresh instruction, the HPB memory area includes a system hot file L2P mapping cache corresponding to the updated system hot file LBA list.

In another exemplary embodiment, the UFS Host driver module uses the file L2P mapping corresponding to the updated system hot file LBA list to replace or overwrite the file L2P mapping corresponding to the system hot file LBA list before the update in the HPB memory area according to the HPB memory area refresh instruction.

In this way, the system hotspot file LBA list is dynamically updated, and the system hotspot file L2P mapping in the HPB memory area is refreshed based on the updated system hotspot file LBA list, so as to ensure the accuracy of the system hotspot file L2P mapping cached in the HPB memory area and improve the probability of querying the system hotspot file LBA related to application startup or operation in the HPB memory area.

S708 , the HPB management agent obtains the updated application file list corresponding to application 3 .

Exemplarily, the HPB management agent can obtain the updated application file list corresponding to application 3 on the cloud server side, or obtain the updated application file list corresponding to application 3 on the relevant functional block side of the electronic device, or generate the updated application file list corresponding to application 3 based on relevant statistical results. This embodiment does not limit this.

S709, the HPB management agent updates the application file list corresponding to the application 3.

The HPB management agent can use the updated application file list to replace the existing application file list, thereby achieving the effect of updating the application file list corresponding to application 3.

S710 , the HPB management agent calls the HBP management module to update the file LBA list corresponding to application 3 .

S711, the HBP management module updates the file LBA list corresponding to the application 3 according to the updated file list, and returns the update result to the HBP management Agent.

The HBP management module regenerates the file LBA list corresponding to the application 3 according to the updated file list to replace the existing file LBA list corresponding to the application 3, and returns an update result indicating the completion of the update to the HBP management Agent.

As an optional implementation, the events in which the file LBA is not queried in the HPB memory area (or the file LBA miss event) involved in the startup and operation process of each application can also be counted, and the file LBA corresponding to the LBAmiss event is updated to the corresponding file LBA list. For example, during the startup process of a certain application, when the LBA of a certain application file is queried in the HPB memory area, if the corresponding file L2P mapping is not queried, it is determined that a file LBA miss event occurs, and the LBA of the application file is added to the application file LBAlist corresponding to this application, and the application file LBA list corresponding to this application is updated.

For details not explained in this process, please refer to the previous text and will not be repeated here.

In this way, the file LBA list corresponding to each hot application is dynamically updated. Before the hot application is started, the application hot file L2P mapping in the HPB memory area is refreshed according to the currently updated file LBA list, so as to ensure the accuracy of the application hot file L2P mapping cached in the HPB memory area, and improve the probability of querying the application hot file LBA related to the application startup or operation in the HPB memory area, so as to improve the file reading speed and achieve the effect of accelerating the application startup.

This embodiment also provides a computer storage medium, in which computer instructions are stored. When the computer instructions are executed on an electronic device, the electronic device executes the above-mentioned related method steps to implement the application startup acceleration method in the above-mentioned embodiment.

This embodiment also provides a computer program product. When the computer program product runs on a computer, it enables the computer to execute the above-mentioned related steps to implement the application startup acceleration method in the above-mentioned embodiment.

In addition, an embodiment of the present application also provides a device, which can specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer execution instructions, and when the device is running, the processor can execute the computer execution instructions stored in the memory so that the chip executes the application startup acceleration method in the above-mentioned method embodiments.

Among them, the electronic device (such as a mobile phone, etc.), computer storage medium, computer program product or chip provided in this embodiment is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be repeated here.

Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims (14)

1. A method for accelerating application startup, characterized in that it is applied to an electronic device, wherein the electronic device includes a host and a universal flash storage UFS device, comprising: It is detected that the first application is about to be started; Before the first application is started, a first file logical block address LBA list is obtained, a first file logical block address to physical block address L2P mapping corresponding to the first file LBA list is read in the UFS device, and the first file L2P mapping is cached in a host performance enhancer HPB memory area of the host memory; wherein the first file LBA list is generated based on the first file list, and the files in the first file list are application files corresponding to the first application that affect the application process performance; the HPB memory area also caches a second file L2P mapping corresponding to the second file LBA list, the second file LBA list is generated based on the second file list, and the files in the second file list are system files that affect the application process performance; The first application is started; wherein, during the process of starting the first application, based on the first file L2P mapping and the second file L2P mapping cached in the HPB memory area, relevant files are read in the UFS device. 2. The method according to claim 1, further comprising: During the power-on phase of the electronic device, acquiring the second file list, and generating the second file LBA list according to the second file list; A second file L2P mapping corresponding to the second file LBA list is read in the UFS device, and the second file L2P mapping is cached in the HPB memory area. 3. The method according to claim 1, further comprising: Monitoring the installation of the first application; After the first application is installed, obtaining the first file list corresponding to the first application; The first file LBA list is generated according to the first file list. 4. The method according to claim 1, further comprising: Monitoring the update or compilation optimization of the first application; After the first application is updated or compiled and optimized, updating the first file list corresponding to the first application; The first file LBA list is updated according to the updated first file list. 5. The method according to claim 1, further comprising: Acquire a third file list; the third file list is generated by updating the first file list based on the usage scenario of the first application; The first file LBA list is updated according to the third file list. 6. The method according to claim 1, further comprising: Monitoring that the first application is uninstalled; After the first application is uninstalled, deleting the first file LBA list; If the first file L2P mapping corresponding to the first file LBA list is cached in the HPB memory area, the first file L2P mapping in the HPB memory area is cleared. 7. The method according to any one of claims 1 to 6, further comprising: It is detected that the second application is about to be started; Before the second application is started, a third file LBA list is obtained, a third file L2P mapping corresponding to the third file LBA list is read in the UFS device, and the third file L2P mapping is cached to the HPB memory area of the host memory; wherein the third file LBA list is generated based on a fourth file list, and the files in the fourth file list are application files corresponding to the second application that affect the performance of the application process; The second application is started; wherein, during the process of starting the second application, based on the third file L2P mapping and the second file L2P mapping cached in the HPB memory area, the relevant file is read in the UFS device. 8. The method according to claim 7, further comprising: After the second application is started, monitoring that the first application is about to be started; Determining that the first file L2P mapping is cached in the HPB memory area; The first application is started; wherein, during the process of starting the first application, based on the first file L2P mapping and the second file L2P mapping cached in the HPB memory area, relevant files are read in the UFS device. 9. The method according to claim 8, characterized in that after determining that the first file L2P mapping is cached in the HPB memory area, it also includes: If the first file LBA list is updated after the first file L2P mapping is cached, the first file LBA list is reacquired, the fourth file L2P mapping corresponding to the first file LBA list is read in the UFS device, and the first file L2P mapping cached in the HPB memory area is updated with the fourth file L2P mapping. 10. The method according to any one of claims 1 to 6, further comprising: Acquire a fifth file list; the fifth file list is generated by updating the second file list based on usage scenarios of multiple applications; Generate a fourth file LBA list according to the fifth file list; A fifth file L2P mapping corresponding to the fourth file LBA list is read in the UFS device, and the second file L2P mapping cached in the HPB memory area is updated according to the fifth file L2P mapping. 11. The method according to any one of claims 1 to 6, further comprising: During the startup of the first application, if the PBA corresponding to the first target file LBA cannot be found according to the first file L2P mapping and the second file L2P mapping cached in the HPB memory area, the first target file LBA is added to the first file LBA list, and the first file LBA list is updated; The file corresponding to the first target file LBA is not a system file. 12. The method according to any one of claims 1 to 6, further comprising: During the startup of any application, if the PBA corresponding to the second target file LBA cannot be found according to the second file L2P mapping cached in the HPB memory area, the second target file LBA is added to the second file LBA list, and the second file LBA list is updated; The file corresponding to the second target file LBA is a system file. 13. An electronic device, comprising: one or more processors; Memory; And one or more computer programs, wherein the one or more computer programs are stored in the memory, and when the computer programs are executed by the one or more processors, the electronic device executes the application startup acceleration method as described in any one of claims 1-12. 14. A computer-readable storage medium, comprising a computer program, characterized in that when the computer program is executed on an electronic device, the electronic device executes the application startup acceleration method as described in any one of claims 1 to 12.