CN112988213B - Program data updating method, electronic equipment and computer storage medium - Google Patents

Abstract

The application provides a program data updating method, electronic equipment and a computer storage medium, relates to the technical field of Internet, and solves the problem that program flash back occurs during application program updating. The specific scheme is as follows: under the condition that the first application is in a using state and the first program data needs to be updated, placing an upgrading task corresponding to the first program data into a waiting list; acquiring a use state of a first application; taking out the upgrade task from the waiting list under the condition that the first application is in an unused state; under the instruction of an upgrade task, analyzing and installing an update data packet of the first program data; or under the instruction of the upgrade task, updating the first program data according to the second program data; the second program data is obtained by analyzing and installing an update data packet of the first program data in the second storage area; the second storage area is different from the first storage area for storing the first program data.

Description

A program data updating method, electronic device and computer storage medium

Technical field

This application relates to the field of Internet technology, and in particular to a program data update method, electronic equipment and computer storage media.

Background technique

Applications provide users with diverse services through interaction with users, enriching users' lives. With the in-depth development of Internet technology, applications need to be quickly iterated (for example, version updates) to adapt to the changing rhythm of the market.

However, in some scenarios, during the application update process, program crashes may occur, and program crashes may directly interrupt the provision of relevant services to users. Take, for example, upgrading a chat application installed on a mobile phone. As shown in (a) in Figure 1, the mobile phone displays the chat window of the chat application, and the user is chatting with the contact through the chat window. If the chat application is upgraded at this time, there may be a sudden temporary lag, and the chat application If the service provided is interrupted, the chat application will crash, as shown in (b) in Figure 1, and the mobile phone will display the desktop. When the user needs to use the chat application again, he can reopen the chat application, and the mobile phone can re-display the chat window of the chat application, as shown in (c) in Figure 1, but the original edited chat content will be lost.

It can be seen that program crashes during application updates not only affect the user experience, but also affect the user's evaluation of the stability and performance of the system and applications.

Contents of the invention

This application provides a program data updating method, electronic device and computer storage medium. The program updating process avoids the period when the application program is in use. While ensuring program update requirements, it also improves the stability of application operations. Enhance user experience.

In order to achieve the above purpose, this application adopts the following technical solutions:

In a first aspect, embodiments of the present application provide a method for updating program data. The method includes: when the first application is in use and the first program data needs to be updated, updating the first program data The corresponding upgrade task is put into the waiting list; the usage status of the first application is obtained; the first program data is the program file of the first application, or the program file of a common component of the first application; in When the first application is in an unused state, remove the upgrade task from the waiting list; under the instruction of the upgrade task, parse and install the update data package of the first program data to update The first program data; or, under the instruction of the upgrade task, update the first program data according to the second program data; wherein the second program data is parsed and installed in the second storage area. Data obtained after updating the data package of the first program data; the second storage area is different from the first storage area; the first storage area is a storage area used to store the first program data.

In the above embodiment, when the associated application corresponding to the first program data (that is, the first application) is in use, updating the data entity of the first program data is suspended. When all associated applications corresponding to the first program data are in an unused state, the data entity of the first program data is updated. Thus, conflicts between program data upgrade and application usage are avoided. It has also improved the issue of crashes caused by program upgrades during application use. Improve user experience.

For example, when the associated application is in an unused state, the corresponding upgrade task can be removed from the waiting list. However, according to the instructions of the upgrade task, the update data package for installing the first program data is parsed to update the first program data. Avoid closing the application process of the associated application when parsing and installing update data packages.

For example, when the associated application is in an unused state, the first program data in the first storage area can be updated using the second program data already in the second storage area. That is, when the associated application is in an unused state, the existing second program data is directly used to replace the data entity of the first program data to avoid closing the application process of the associated application.

In conjunction with the first aspect, in a possible implementation, the parsing and installing the update data package of the first program data includes: obtaining the update data package of the first program data according to the upgrade task; The update data package of the first program data is parsed and installed in the storage area to replace the first program data.

In conjunction with the first aspect, in another possible implementation manner, when the first application is in use and the first program data needs to be updated, the method further includes: in the second storage area The update data package for installing the first program data is parsed and installed to obtain the second program data.

In the above embodiment, by decompressing the update data packet of the first program data in the second storage area in advance, the time consumption of updating the first program data is shortened. Improve upgrade efficiency.

In conjunction with the first aspect, in another possible implementation manner, when the update data packet is a full data packet, updating the first program data according to the second program data includes: using the third program data. The second program data replaces the first program data.

In conjunction with the first aspect, in another possible implementation manner, when the update data packet is an incremental data packet, updating the first program data according to the second program data includes: converting the The second program data is stored in the first storage area and merged with the first program data.

In conjunction with the first aspect, in another possible implementation, when the update data packet is a full data packet, updating the first program data according to the second program data includes:

The loading address of the first program data is changed from the address of the first storage area to the address of the second storage area.

In the above embodiment, the process of updating the first program data is made simpler and faster. Improved update efficiency to avoid long-term impact on users' use of associated applications.

In conjunction with the first aspect, in another possible implementation manner, when the update data packet is an incremental data packet, updating the first program data according to the second program data includes: converting the The first program data is mirrored to the second storage area and merged with the second program data; the loading address of the first program data is changed from the address of the first storage area to the second storage area the address of.

In conjunction with the first aspect, in another possible implementation, the above method further includes: deleting the first program data in the first storage area.

In the above embodiment, the redundancy of data in the electronic device is effectively reduced.

Combined with the first aspect, in another possible implementation, deleting the first program data in the first storage area includes:

The first application deletes the first program data in the first storage area if no operating abnormality occurs within a preset time period after the loading address is changed.

Combined with the first aspect, in another possible implementation, the method further includes:

If the first application runs abnormally within a preset time period after the loading address is changed, the loading address for loading the first program data is restored to the address of the first storage area; and the second storage is cleared. area.

In the above embodiment, exception rollback protection is implemented, which improves the stability of the application program.

Combined with the first aspect, in another possible implementation, obtaining the usage status of the first application includes:

Periodically restart and obtain the usage status of the first application until all first applications of the first program data are in an unused status.

Combined with the first aspect, in another possible implementation, obtaining the usage status of the first application includes:

When it is detected that any application program switches from the in-use state to the unused state, restart and obtain the use state of the first application.

In conjunction with the first aspect, in another possible implementation, during the process of updating the first program data, the method further includes:

Display prompt information on the desktop icon of the first application; or, after receiving a user's operation on the icon of the first application, display prompt information;

The prompt information is used to prompt at least one of the following information: update status, update progress, update version, and update release time.

In the above embodiment, reminders are used to improve the problem of users misoperating associated applications during the first program upgrade. It also enables users to be more aware of updated information.

In conjunction with the first aspect, in another possible implementation, the method further includes: after completing the upgrade of the first program data, canceling the display of prompt information on the desktop icon of the first application; or, after receiving After the user operates the icon of the first application, the prompt information is canceled.

Combined with the first aspect, in another possible implementation, obtaining the usage status of the first application includes:

Determine the usage status according to the running status of the first application;

Wherein, the running status includes foreground running, background running and stopped running;

When the running state is the foreground running, the use state is the in-use state;

When the operating state is the stopped operation, the use state is an unused state;

When the running state is the background running and a multi-tasking interface is displayed, or the running state is the background running and a user's operation on the interface of the first application in the multi-tasking interface is received, The usage status is the in-use status.

In a second aspect, embodiments of the present application provide an electronic device. The electronic device includes one or more processors and memories; the memory is coupled to the processor, and the memory is used to store computer program code. The computer program code includes computer instructions. When a or multiple processors execute computer instructions, the one or more processors are configured to update the first program data when the first application is in use and the first program data needs to be updated. The corresponding upgrade task is put into the waiting list; the usage status of the first application is obtained; the first program data is the program file of the first application, or the program file of a common component of the first application; in When the first application is in an unused state, remove the upgrade task from the waiting list; under the instruction of the upgrade task, parse and install the update data package of the first program data to update The first program data; or, under the instruction of the upgrade task, update the first program data according to the second program data; wherein the second program data is parsed and installed in the second storage area. Data obtained after updating the data package of the first program data; the second storage area is different from the first storage area; the first storage area is a storage area used to store the first program data.

In conjunction with the second aspect, in a possible implementation, the one or more processors are configured to parse and install an update data package of the first program data, including: obtaining the third program data according to an upgrade task. An update data package of program data; parse and install the update data package of the first program data in the first storage area to replace the first program data.

Combined with the second aspect, in another possible implementation, when the first application is in use and needs to update the first program data, the one or more processors are also used to: The update data package for installing the first program data is parsed in the second storage area to obtain the second program data.

In conjunction with the second aspect, in another possible implementation manner, when the update data packet is a full data packet, the one or more processors are configured to update the update data packet according to the second program data. The first program data includes: using the second program data to replace the first program data.

In conjunction with the second aspect, in another possible implementation, when the update data packet is an incremental data packet, the one or more processors are configured to update the data according to the second program data. The first program data includes: storing the second program data in the first storage area and merging it with the first program data.

In conjunction with the second aspect, in another possible implementation manner, when the update data packet is a full data packet, the one or more processors are configured to update the update data packet according to the second program data. First program data, including:

The loading address of the first program data is changed from the address of the first storage area to the address of the second storage area.

In conjunction with the second aspect, in another possible implementation, when the update data packet is an incremental data packet, the one or more processors are configured to update the data according to the second program data. The first program data includes: mirroring the first program data to the second storage area and merging it with the second program data; changing the loading address of the first program data from the first storage area. The address of the area is changed to the address of the second storage area.

In conjunction with the second aspect, in another possible implementation, the one or more processors are further configured to delete the first program data in the first storage area.

In conjunction with the second aspect, in another possible implementation, the one or more processors are configured to delete the first program data in the first storage area, including:

The first application deletes the first program data in the first storage area if no operating abnormality occurs within a preset time period after the loading address is changed.

Combined with the second aspect, in another possible implementation, the one or more processors are also used to:

If the first application runs abnormally within a preset time period after the loading address is changed, the loading address for loading the first program data is restored to the address of the first storage area; and the second storage is cleared. area.

In conjunction with the second aspect, in another possible implementation, the one or more processors are configured to obtain the usage status of the first application, including:

Periodically restart and obtain the usage status of the first application until all first applications of the first program data are in an unused status.

In conjunction with the second aspect, in another possible implementation, the one or more processors are configured to obtain the usage status of the first application, including:

When it is detected that any application program switches from the in-use state to the unused state, restart and obtain the use state of the first application.

Combined with the second aspect, in another possible implementation, during the process of updating the first program data, the one or more processors are also used to:

Display prompt information on the desktop icon of the first application; or, after receiving a user's operation on the icon of the first application, display prompt information;

The prompt information is used to prompt at least one of the following information: update status, update progress, update version, and update release time.

In conjunction with the second aspect, in another possible implementation, the one or more processors are further configured to: after the first program data is upgraded, cancel the display on the desktop icon of the first application. Prompt information; or, after receiving a user's operation on the icon of the first application, cancel the display of prompt information.

In conjunction with the second aspect, in another possible implementation, the one or more processors are configured to obtain the usage status of the first application, including:

Determine the usage status according to the running status of the first application;

Wherein, the running status includes foreground running, background running and stopped running;

When the running state is the foreground running, the use state is the in-use state;

When the operating state is the stopped operation, the use state is an unused state;

When the running state is the background running and a multi-tasking interface is displayed, or the running state is the background running and a user's operation on the interface of the first application in the multi-tasking interface is received, The usage status is the in-use status.

In a third aspect, embodiments of the present application provide a computer storage medium. The computer storage medium includes computer instructions. When the computer instructions are run on an electronic device, the electronic device causes the electronic device to execute the first aspect and any one thereof. Possible design methods described.

In a fourth aspect, embodiments of the present application provide a computer program product. When the computer program product is run on a computer, it causes the computer to execute the method described in the first aspect and any possible design manner thereof.

It can be understood that the electronic device described in the second aspect and any possible design manner provided above, the computer storage medium described in the third aspect, and the computer program product described in the fourth aspect are all used to execute the above. The corresponding method provided above, therefore, the beneficial effects it can achieve can be referred to the beneficial effects in the corresponding method provided above, and will not be described again here.

Description of the drawings

Figure 1 is an example of a crash during the application update process in related technologies;

Figure 2 is a schematic structural diagram of a mobile phone provided by an embodiment of the present application;

Figure 3 is a software structure block diagram of a mobile phone provided by an embodiment of the present application;

Figure 4 is one of the step flow charts of the program data updating method provided by the embodiment of the present application;

Figure 5 is an example diagram of a single application running in the foreground according to the embodiment of the present application;

Figure 6 is one of the example diagrams of multiple applications running in the foreground provided by the embodiment of the present application;

Figure 7 is the second example diagram of multiple applications running in the foreground provided by the embodiment of the present application;

Figure 8 is an example diagram of a method for triggering the opening of a multi-task interface provided by an embodiment of the present application;

Figure 9 is an example diagram of displaying prompt information through desktop icons provided by an embodiment of the present application;

Figure 10 is the second example diagram of displaying prompt information through desktop icons provided by the embodiment of the present application;

Figure 11 is an example diagram of displaying prompt information after receiving a user's operation on the icon of the first application provided by an embodiment of the present application;

Figure 12 is the second step flow chart of the program data updating method provided by the embodiment of the present application;

Figure 13 is the third step flow chart of the program data updating method provided by the embodiment of the present application;

Figure 14 is a schematic diagram of the composition of a chip system provided by an embodiment of the present application.

Detailed ways

Hereinafter, the terms “first” and “second” are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features. Therefore, features defined as "first" and "second" may explicitly or implicitly include one or more of these features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

The implementation of this embodiment will be described in detail below with reference to the accompanying drawings.

Embodiments of the present application provide a program data updating method, which can be applied in the program updating process in electronic devices.

The above program update may be an update of a program file of an application program (application, APP) in the electronic device. Taking the electronic device as a mobile phone shown in (b) in Figure 1 as an example, the mobile phone is installed with a map APP, a video APP, a taxi APP, etc. Then the above-mentioned program update may refer to updating the program files of the map APP, video APP or taxi-hailing APP.

The above-mentioned program update may also be an update of program files of common components. Wherein, the above-mentioned common component may be a program component that provides service support for different applications in the electronic device. Take common public components: Google Mobile Service (GMS) component, webview component, UnionPay payment component, etc. as examples. The gms component can be the map APP, video APP, etc. in the mobile phone shown in (b) in Figure 1. Many types of applications, such as taxi-hailing apps, provide in-app purchase, payment, location information, push services, advertising, application development and other service support. For another example, the webview component can provide web view loading service support for many types of applications such as map APPs, video APPs, and taxi-hailing APPs on mobile phones. For another example, the UnionPay payment component can provide payment service support for transaction APPs on mobile phones.

The program files of the above-mentioned application programs and public components can all be called program data. It is understandable that the above program data running and updating can affect at least one application program. For example, an application's program files can affect the application itself. For another example, the program files of a common component can affect all applications that use the common component.

For convenience of description, the application affected by the program data may be simply referred to as the associated application of the program data.

Under related technologies, during the program update process, the application process of the associated application will be forcibly closed. Obviously, once the application process of the associated application is closed, the services provided by the associated application to the user will be interrupted. If the user is using the associated application at this time, the application will crash, interrupting the user's use and affecting the user's experience.

In other words, there is a conflict between application usage and program updates.

To resolve conflicts between application usage and program updates. Avoid crashes caused by program updates while users are using the app. The program data update method provided in the embodiment of the present application displaces the "parsing and installation of program data" and the "use of associated applications", thereby reducing the possibility of conflict between program update and application use, and improving the efficiency of the application. Stability of use can also increase users' recognition of the stability of the system and applications.

In some embodiments, the above-mentioned "dislocation" may be a displacement in the time dimension. That is to say, the analysis and installation time period in program updates is staggered with the usage time period of the associated application, so as to avoid conflicts between program updates and application usage from the time dimension.

In other embodiments, the above-mentioned "dislocation process" can also be a displacement of spatial dimensions. The above space may refer to storage space. Separate the storage space operated during the parsing and installation phase of program updates from the storage space of running program data to avoid conflicts caused by file overwriting, thereby achieving misalignment of spatial dimensions.

It can be seen that updating in a staggered manner does not require closing the process of the application that the user is using. Implement program updates while ensuring user experience.

For example, the electronic devices in the embodiments of the present application may be smart speakers, smart TVs, refrigerators, washing machines, air conditioners, air purifiers, kitchen and bathroom appliances and other household devices. The electronic device in the embodiment of the present application can also be a portable computer (such as a mobile phone), a tablet computer, a desktop, a laptop, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), or a netbook. As well as devices such as cellular phones, personal digital assistants (PDAs), augmented reality (AR)/virtual reality (VR) devices, media players, etc., the embodiments of the present application are specific to the electronic devices. There are no special restrictions on the form.

Taking the electronic device as a mobile phone as an example, Figure 2 shows a schematic structural diagram of the mobile phone.

The mobile phone may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, and an audio module 170. Speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, etc.

It can be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the mobile phone. In other embodiments of the present application, the mobile phone may include more or less components than shown in the figures, or some components may be combined, some components may be separated, or some components may be arranged differently. The components illustrated may be implemented in hardware, software, or a combination of software and hardware.

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

The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have been recently used or recycled by processor 110 . If the processor 110 needs to use the instructions or data again, it can be called directly from the memory. Repeated access is avoided and the waiting time of the processor 110 is reduced, thus improving the efficiency of the system.

The wireless communication function of the mobile phone can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in a phone can be used to cover a single or multiple communication bands. Different antennas can also be reused to improve antenna utilization. For example: Antenna 1 can be reused as a diversity antenna for a wireless LAN. In other embodiments, antennas may be used in conjunction with tuning switches.

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G applied to mobile phones. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, perform filtering, amplification and other processing on the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves through the antenna 1 for radiation. In some embodiments, at least part of the functional modules of the mobile communication module 150 may be disposed in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 and at least part of the modules of the processor 110 may be provided in the same device.

The wireless communication module 160 can provide applications on the mobile phone including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (bluetooth, BT), global navigation satellite system (global navigation satellite system). navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves through the antenna 2 for radiation.

In some embodiments, the antenna 1 of the mobile phone is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the mobile phone can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband code Wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and/or IR technology, etc. The GNSS may include global positioning system (GPS), global navigation satellite system (GLONASS), Beidou satellite navigation system (beidounavigation satellite system, BDS), quasi-zenith satellite system (quasi- zenith satellitesystem (QZSS) and/or satellite based augmentation systems (SBAS).

The mobile phone implements display functions through the GPU, display screen 194, and application processor. The GPU is an image processing microprocessor and is connected to the display screen 194 and the application processor. GPUs are used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

The display screen 194 is used to display images, videos, etc. Display 194 includes a display panel. The display panel can use a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active matrix organic light emitting diode or an active matrix organic light emitting diode (active-matrix organic light emitting diode). (AMOLED), flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diodes (QLED), etc. In some embodiments, the mobile phone may include 1 or N display screens 194, where N is a positive integer greater than 1.

The mobile phone can realize the shooting function through the ISP, camera 193, video codec, GPU, display 194 and application processor.

The ISP is used to process the data fed back by the camera 193. For example, when taking a photo, the shutter is opened, the light is transmitted to the camera sensor through the lens, the optical signal is converted into an electrical signal, and the camera sensor passes the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise, brightness, and skin color. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be provided in the camera 193.

Camera 193 is used to capture still images or video. The object passes through the lens to produce an optical image that is projected onto the photosensitive element. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to convert it into a digital image signal. ISP outputs digital image signals to DSP for processing. DSP converts digital image signals into standard RGB, YUV and other format image signals. In some embodiments, the mobile phone may include 1 or N cameras 193, where N is a positive integer greater than 1.

Digital signal processors are used to process digital signals. In addition to digital image signals, they can also process other digital signals. For example, when the mobile phone selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

Video codecs are used to compress or decompress digital video. A mobile phone can support one or more video codecs. In this way, the mobile phone can play or record videos in multiple encoding formats, such as: Moving Picture Experts Group (MPEG)1, MPEG2, MPEG3, MPEG4, etc.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone. The external memory card communicates with the processor 110 through the external memory interface 120 to implement the data storage function. Such as saving music, videos, etc. files in external memory card.

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

The mobile phone can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone interface 170D, and the application processor. Such as music playback, recording, etc.

The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. Audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be provided in the processor 110 , or some functional modules of the audio module 170 may be provided in the processor 110 .

Speaker 170A, also called "speaker", is used to convert audio electrical signals into sound signals. The mobile phone can listen to music through speaker 170A, or listen to hands-free calls.

Receiver 170B, also called "earpiece", is used to convert audio electrical signals into sound signals. When the mobile phone answers a call or voice message, the voice can be heard by bringing the receiver 170B close to the human ear.

Microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak close to the microphone 170C with the human mouth and input the sound signal to the microphone 170C. The mobile phone can be set with at least one microphone 170C. In other embodiments, the mobile phone can be equipped with two microphones 170C, which in addition to collecting sound signals, can also implement noise reduction functions. In other embodiments, the mobile phone can also be equipped with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions, etc.

The headphone interface 170D is used to connect wired headphones. The headphone interface 170D may be a USB interface 130, or may be a 3.5 mm open mobile terminal platform (OMTP) standard interface or a Cellular Telecommunications Industry Association of the USA (CTIA) standard interface.

The sensor module 180 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, etc.

Of course, the mobile phone may also include a charging management module, a power management module, a battery, a button, an indicator, one or more SIM card interfaces, etc. This embodiment of the present application does not impose any restrictions on this.

The software system of the above-mentioned mobile phones can adopt layered architecture, event-driven architecture, micro-core architecture, micro-service architecture, or cloud architecture. The embodiment of this application takes the Android system with a layered architecture as an example to illustrate the software structure of the mobile phone.

Figure 3 is a software structure block diagram of a mobile phone according to an embodiment of the present application.

The layered architecture divides the software into several layers, and each layer has clear roles and division of labor. The layers communicate through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: application layer, application framework layer, Android runtime (Android runtime) and system libraries, and kernel layer.

The application layer can include a series of application packages.

As shown in Figure 3, the application layer can include: calls, memos, browsers, contacts, cameras, galleries, calendars, maps, Bluetooth, music, videos, short messages, desktop and other APPs (applications). Among them, the above-mentioned applications can be system-level applications; they can also be third-party applications.

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

As shown in Figure 3, the application framework layer can include window managers, content providers, view systems, update management services, resource managers, notification managers, etc.

Among them, the above-mentioned window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, capture the screen, etc.

The above content providers are used to store and retrieve data and make this data accessible to applications. Said data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

The above view system can be used to build the display interface of the application. Each display interface can be composed of one or more controls. Generally speaking, controls can include interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

The above update management service is used to manage application upgrades and provide upgrade services for applications installed in electronic devices. The above update management service is a service created based on the program data update method. The above-mentioned update management service works in an independent thread, and the above-mentioned update management service is managed by WorkManger as a background task, that is, it runs in the system process in the background state.

The above resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, etc.

The above notification manager allows the application to display notification information in the status bar, which can be used to convey notification type messages, and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be notifications that appear in the status bar at the top of the system in the form of charts or scroll bar text, such as notifications for applications running in the background, or notifications that appear on the screen in the form of conversation windows. For example, prompt text information in the status bar, sound a beep, vibrate, blink the indicator light, etc.

As shown in Figure 3, the system library can include multiple functional modules. For example: layer integrator (SurfaceFlinger), media libraries (Media Libraries), 3D graphics processing libraries (for example: OpenGL ES), 2D graphics engines (for example: SGL), etc. SurfaceFlinger is used to manage the display subsystem and provides 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 multiple 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, composition, and layer processing. 2D Graphics Engine is a drawing engine for 2D drawing.

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

The core library contains two parts: one is the functional functions that need to be called by the Java language, and the other is the core library of Android.

The application layer and application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and application framework layer into binary files. The virtual machine is used to perform object life cycle management, stack management, thread management, security and exception management, and garbage collection and other functions.

The kernel layer is the layer between hardware and software. The kernel layer at least includes camera drivers, audio drivers, sensor drivers, etc., and the embodiments of this application do not impose any restrictions on this.

The program data updating method provided by the embodiment of the present application can be implemented in an electronic device, for example, by the mobile phone shown in FIG. 2 and FIG. 3 .

Exemplarily, as shown in Figure 4, the above program data updating method may include the following steps:

S101. Obtain the running status of the associated application corresponding to the first program data.

In some embodiments, when the electronic device detects a program update requirement, it may determine the program data (that is, the first program data) that has the update requirement.

For example, when the electronic device detects the upgrade task, it may be determined that a program update requirement occurs. Among them, the upgrade task is a matter used to instruct the update. Included in the upgrade task are tags with program data that require updating. (for example, package name). Different program data correspond to different labels. The first program data can be determined through the labels of the program data carried in the upgrade task.

Of course, multiple upgrade tasks can exist within the electronic device at the same time. Multiple upgrade tasks can also determine multiple first program data. However, the principle of updating the data for each first program is the same. Therefore, for convenience of description, subsequent embodiments mainly take an upgrade task as an example for description.

Usually the generation of upgrade tasks is related to whether the update server publishes update data packages. It can be understood that the above-mentioned update server may be a server used to publish update data packages. For example, the above-mentioned update server may be a cloud server, used to publish update data packages of system-level programs (such as system-level applications, public components). For example, the above update server may also be a third server, used to publish update data packages of third-party program data.

The above-mentioned update data packet is a data packet used to update the first program data. Program update notifications can be broadcast when a new update package is published by the update server. Wherein, the above-mentioned program update notification may include a first identifier, and the first identifier may be a label of the first program data.

In some embodiments, when the automatic upgrade function is enabled on the electronic device and a program update notification issued by the update server is heard, a corresponding upgrade task is created based on the first identifier carried in the program update notification.

In other embodiments, when the electronic device does not turn on the automatic upgrade function, the electronic device may also listen for notifications issued by the update server. If a program update notification is detected, the electronic device displays a program update reminder to inquire whether the user is willing to update. If the user feeds back an instruction to confirm the update to the electronic device through interactive operations, the electronic device can create a corresponding upgrade task according to the first identifier of the program update notification.

For example, in possible embodiments, whether there is a program update requirement may also be determined through other methods.

For example, the upgrade cycle of each program file is preset in the electronic device, and entering each upgrade cycle will automatically trigger the program update requirement. In this way, as long as it is detected that a new upgrade cycle has entered, it can be determined that there is a need for program update. In addition, after determining that there is a need for program update, request an upgrade from the update server. After receiving the update data packet fed back by the update server, the electronic device creates an upgrade task.

For another example, when an electronic device detects that a program file has run abnormally multiple times, it determines that a program update is required. In addition, after determining that there is a program update requirement, the electronic device also needs to send an upgrade request to the update server. The above upgrade request may include exception description information. After receiving the update data packet fed back by the update server in response to the upgrade request, the electronic device creates an upgrade task.

After creating the upgrade task, the electronic device can also obtain the running status of the associated application corresponding to the first program data (also called the first application of the first program data). For example, if the first program data is the program file of the chat APP, then the running status of the chat APP is obtained. For another example, the first program data is the program file of the gms component. Applications using the gms component in the electronic device include map APP, video APP, and taxi APP. Then the electronic device also obtains the running status of the map APP, video APP, and taxi APP.

The above-mentioned running status refers to the actual working status of the application in the electronic device. For example, the above-mentioned running status can be divided into foreground running, background running and stopped running.

Among them, in electronic devices, applications running in the foreground and background running have corresponding application processes, but applications that stop running do not.

Therefore, it can be determined whether the running status of the associated application is stopped by detecting whether the associated application has a process.

In some embodiments, when it is determined that the running status of the associated application is not stopped, it is also necessary to determine whether the associated application is running in the foreground or in the background. To distinguish whether the associated application is running in the foreground or in the background, existing services in the electronic device can be used. For example, through UsageStatsManager.

In addition, applications running in the foreground can directly provide corresponding services to users.

Taking Figure 5 as an example, the electronic device in Figure 5 is shown in the form of a mobile phone. When the video APP in the mobile phone is running in the foreground, the user can directly watch the video playback service provided by the video APP.

For another example, when the electronic device is a smart speaker and the music APP is running in the foreground, the smart speaker can play music to the user through the music APP.

In addition, there may be one or more applications running in the foreground within the electronic device.

For example, in the scene shown in Figure 6, the music APP in the mobile phone is playing music, and at the same time, the display screen of the mobile phone displays the reading content provided by the reading APP. In this scenario, the music APP and reading APP in the mobile phone are both applications running in the foreground.

For another example, in the scenario shown in Figure 7, the chat APP in the mobile phone provides chat services to the user. At the same time, the mobile phone also opens a small window in the display screen to display the video content provided by the video APP. In this scenario, the chat APP and reading APP in the mobile phone are both applications running in the foreground.

Based on the operating characteristics of the foreground operation described above, in other embodiments, when it is determined that the running status of the associated application is not stopped, the output action of the associated application can also be captured and analyzed in combination with the service type provided by the associated application. Whether the associated application is running in the foreground.

For example, by analyzing whether the associated application calls an output driver (for example, audio driver) or output type service (for example, a view system), combined with the service characteristics of the associated application, it is analyzed whether the associated application runs in the foreground.

For example, for screen output applications, such as chat APPs and video APPs, if it is detected that the application calls the view system and renders the application interface on the display screen of the electronic device, then it is determined that the application is in Front desk operation.

For another example, for an application that outputs sound, such as a music APP, if it is detected that the application has called the audio system, it is determined that the application is running in the foreground.

S102: Determine the corresponding usage status according to the running status of the associated application.

In some embodiments, the usage status of the associated application can be obtained by analyzing the running status of the associated application.

Different from the running state, the above-mentioned usage state is a state that represents the service provided by the application to the user. For example, the usage status can be divided into an unused status and an in-use status. When an application is in use, it indicates that the user currently has a need to use the application. When an application is not in use, it means that the user currently has no need to use the application.

It is understandable that applications running in the foreground are actually in a state of providing corresponding services to users. Therefore, the associated application running in the foreground can be determined to be in use.

In addition, when the application is stopped, there is no corresponding application process and the corresponding service cannot be provided to the user. Therefore, the associated application that is stopped can be determined to be in an unused state.

For example, based on the running status, the methods of analyzing the usage status of the associated application may include the following:

Method 1: When the running status of the associated application is stopped, it can be determined that the associated application is in an unused state. When the running status of the associated application is running in the foreground or running in the background, it is determined that the associated application is in use.

Method 2: When the running status of the associated application is stopped or running in the background, it can be determined that the associated application is in an unused state. When the running state of the associated application is running in the foreground, it is determined that the associated application is in use.

Among them, the first method considers that an application running in the background (referred to as: background application) may be switched to the foreground at any time. In the example scenario, while the user is using a game APP on an electronic device, he temporarily switches to the chat APP to view the content of messages sent by his friends. At this time, the game APP will be temporarily switched to the background. After the user has finished reading the information, he will immediately switch back to the game APP, allowing the game APP to resume running in the foreground. During this process, the time consumption between switching the game APP from background running to foreground running is short.

However, Method 2 takes into account that background applications currently do not provide services, and most background applications will be left in the background by users for a long time, resulting in background applications not being used for a long time. In the example scenario, after the user finished using the reading APP in the electronic device, he did not completely close the reading APP, but let him run it in the background. After that, the user uses other APPs on the electronic device, accepts the services provided by other APPs, and does not switch back to the reading APP. As a result, the reading APP will be running in the background for a long time, so that the reading APP will not be used for a long time.

Obviously, Method 1 and Method 2 are judgment rules designed based on different perspectives, and each has its own advantages. Those skilled in the art can make selections based on actual conditions during actual use.

In addition, in order to improve the accurate judgment of the usage status of background applications, the method of analyzing the usage status based on the running status can also include:

Method 3: When the running status of the associated application is stopped, it can be determined that the associated application is in an unused state. When the associated application runs in the background for longer than the specified value, the associated application is determined to be in an unused state. When the duration of the associated application running in the background does not exceed the specified value, the associated application is determined to be in use. When the running state of the associated application is running in the foreground, it is determined that the associated application is in use.

In some embodiments, the above specified value may be a preset empirical value.

Method 4: When the running status of the associated application is stopped, it is determined that the associated application is in an unused state. When the running state of the associated application is running in the foreground, it is determined that the associated application is in use. When the running status of the associated application is running in the background, determine whether the user is viewing the background application. When it is determined that the user is viewing a background application, it is determined that the associated application is in use. Otherwise, it is judged to be in an unused state.

In some embodiments, the way in which the electronic device determines whether the user is viewing a background application may be one of the following or a combination thereof:

(1) When the electronic device receives the background viewing trigger operation, it is determined that the user is viewing the background application. For example, swiping up on the desktop is a background operation. As shown in (a) of Figure 8, after receiving the user's sliding up operation on the desktop, the electronic device can determine that the user is viewing a background application.

(2) While the multi-tasking interface is displayed on the display screen, it is determined that the user is viewing background applications. Multitasking interfaces include interfaces for applications running in the background of electronic devices. The interface of the multi-tasking interface background application can be an interface thumbnail. For example, the interface thumbnail may be the last frame of the interface displayed before the background application enters the background. For example, combined with the example shown in (a) of Figure 8, in response to the slide-up operation, as shown in (b) of Figure 8, the electronic device can display a multi-tasking interface. During this period, it can be determined that the user is viewing background applications.

(3) When the electronic device receives the operation of sliding the interface thumbnail of the background application, it determines that the user is viewing the background application.

The above method of analyzing usage status based on running status can be selected by those skilled in the art according to actual needs.

In addition to analyzing the corresponding usage status based on the running status, in other embodiments, the usage status of the associated application can also be analyzed in combination with the device status of the electronic device.

For example, the above-mentioned device status may include a standby state and a screen-off state. The above-mentioned standby state may be a state in which the electronic device is powered on but does not perform any substantive work (ie, does not perform various operations on files and programs). The above-mentioned screen-off state may be a state in which the display screen of the electronic device does not display any substantial image content. For example, when the display screen displays a black screen interface, a white screen interface, or a screensaver image, it is determined that the electronic device is in a screen-off state.

In some embodiments, if the electronic device is in the standby state and/or the screen-off state, the usage status corresponding to all applications in the electronic device can be set to the unused state, that is, the associated applications are in the unused state. On the contrary, the usage status of the associated application can be determined based on the running status.

In other embodiments, when the first program data needs to be updated, the usage status of the associated application may not be obtained according to the above S101 and S102. Instead, the usage status of the associated application is directly obtained. For example, the user is asked whether to use the associated application to determine the usage status of the associated application. For another example, you can also obtain the usage status of associated applications from other programs. Among them, other programs are programs used to monitor the usage status of applications in the electronic device.

S103: When at least one associated application of the first program data is in use, update and upgrade the first program data according to the misaligned upgrade strategy.

For example, when the first program data is a program file of an application program, the first program data may be updated and upgraded using an update data package according to a staggered upgrade strategy while the application program itself is still in use. For example, the first program data is the program file of the chat APP. When the chat APP is still in use, the first program data is updated and upgraded using the update data package according to the misplaced upgrade strategy.

For example, when the first program data is a program file of a common component, when at least one of the applications using the common component is in use, the update data package may be used to update the first program data according to the staggered upgrade strategy. Program data is updated and upgraded. For example, the first program data is the program file of the gms component, and applications using the gms component in the electronic device include map APPs, video APPs, and taxi hailing APPs. When at least one of the map APP, the video APP, and the taxi-hailing APP is still in use, the first program data is updated and upgraded according to the misplaced upgrade strategy using the update data package.

Wherein, the above update data package may be provided by the update server. In some embodiments, the electronic device can download the corresponding update data package from the update server after creating the upgrade task.

When the associated application is in use and the first program data needs to be updated, if the first program data is directly updated according to relevant technologies, it will affect the user's use of the associated application and cause the associated application to crash. retreat.

In the embodiment of the present application, when the associated application is in use and the first program data needs to be updated, the first program data is updated according to the misaligned upgrade strategy, thereby preventing the associated application in use from being affected. Impact of upgrades.

There are many ways to implement the "dislocation upgrade strategy". Of course, no matter which method is used to implement it, the prerequisite for updating the data entity of the first program data is that it is determined that the associated applications have entered an unused state. Therefore, implementing the "misplaced upgrade strategy" will involve putting the corresponding upgrade tasks into the waiting list and reacquiring the usage status of the associated applications. The data entity of the first program data is updated only when the associated application is in an unused state.

In some embodiments, the above staggered upgrade strategy may be: updating the first program data in a time staggered manner.

For example, the above process of updating the first program data in a time-shifted manner may be: placing the upgrade task corresponding to the first program data into a waiting list. Cache update packets obtained from the update server. When all associated applications corresponding to the first program data become unused, the upgrade task corresponding to the first program data is taken out from the waiting list. According to the instructions of the upgrade task, the cached update data package is obtained and parsed and installed to update the first program data.

Understandably, the upgrade task has a first identifier of the first program data. At the same time, since the update data packet is used to update the first program data, it may also carry the identification of the first program data. It can be seen that there is a correlation between the upgrade task and the update data package. The corresponding update data package can be queried from the electronic device through the first identifier in the upgrade task.

In addition, parsing and installing the update data package may be directly parsing and installing the update data package in storage area 1 (that is, the first storage area).

In addition, during the first program data update period, users need to be reminded not to use associated applications temporarily.

In some embodiments, the desktop can be notified through the broadcast message 1 to refresh the desktop icon of the associated application, so that the refreshed desktop icon can prompt the user to suspend use. That is, the prompt information is displayed through the desktop icon of the associated application.

The broadcast message 1 includes update prompt parameters of the first program data.

In addition, according to the broadcast message 1, the startup triggering interface of the associated application can be closed so that the associated application cannot be clicked to prevent the user from accidentally opening the associated application during the first program data update process.

In some embodiments, the broadcast message 1 can be set with system access rights, so that only the desktop as a system-level application has the permission to read the broadcast message 1 . Avoid broadcast message 1 from affecting other applications.

In addition, for example, the update prompt parameter may be a parameter indicating that the first program data is in an updating state. After the desktop receives the broadcast message 1, an update identifier (that is, a prompt message) will be added to the desktop icon of the associated application. For example, as shown in Figure 9, the chat APP in Figure 9 is an associated application of the first program data. After the desktop receives the broadcast message 1 about the first program data, the desktop icon of the chat APP is refreshed to have an update logo added. homescreen icon.

Exemplarily, the update prompt parameter may also be an update progress including the first program data. The above notification to the desktop through the broadcast message 1 may be: periodically creating the broadcast message 1 according to the update progress of the first program data and broadcasting. Each time the desktop receives a broadcast message 1, the update progress (that is, prompt information) is added to the desktop icon of the associated application according to the broadcast message 1. For example, as shown in Figure 10, the video APP in Figure 10 is an associated application of the first program data. The update progress of the first program data reaches 20% at the first moment. After the desktop receives the broadcast message 1 created at the first moment, the update progress of 20% will be displayed under the desktop icon of the video APP. At the second moment, the update progress of the first program data reaches 80%. After the desktop receives the broadcast message 1 created at the second moment, the update progress will be displayed as 80% under the desktop icon of the video APP.

In other embodiments, after notifying the desktop through the broadcast message 1, the form of the desktop icon may not be changed. After receiving the broadcast message 1, close the startup trigger interface of the associated application so that the associated application cannot be opened. Afterwards, it is detected that the desktop icon of the associated application is clicked by the user, and a notification box can pop up. Display the update prompt parameters in broadcast message 1 to the user through the notification box.

That is, after receiving the user's operation on the icon of the first application, the prompt information is displayed.

The above update prompt parameters may include, but are not limited to, one or a combination of information such as updating status, update progress, update version, update release time, etc. For example, the payment APP shown in (a) in Figure 11 is an associated application of the first program data. After the desktop receives broadcast message 1 and detects that the user clicks on the payment APP, a notification box pops up as shown in (b) in Figure 11, displaying the corresponding update prompt parameters.

Obviously, the update progress in the update prompt parameter is a dynamically changing quantity. The above update progress may be the update progress of the first program data when the user clicks on the associated application. Of course, the collection time point of the update progress of the first program data and the time point when the user clicks on the associated application may not be absolutely aligned. For example, the update progress collection time can be slightly later than the time when the user clicks on the associated application.

Of course, this is also to prevent the associated application from continuing to be affected by broadcast message 1 after the data update of the first program is completed. After the first program data is updated, the desktop can also be notified through the broadcast message 2 to cancel the change to the desktop icon of the associated application. For example, unlink the update logo on the app's desktop icon. For another example, cancel clicking on the associated application to pop up a notification box. Another example is to restore the startup trigger interface of associated applications so that users can start and use associated applications by clicking on the desktop icon.

That is, as shown in Figure 12, based on the program data update method shown in Figure 4, the above S103 may include:

S103-1: Put the upgrade task corresponding to the first program data into the waiting list. The upgrade task corresponding to the first program data is not executed yet.

S103-2: Monitor whether the applications associated with the first program data are in an unused state.

If the applications associated with the first program data are not in use, the process proceeds to S103-3. If not all the associated applications of the first program data are in an unused state, then continue to monitor the usage state of the associated applications of the first program data.

S103-3: When it is determined that the associated application corresponding to the first program data is in an unused state, the upgrade task is removed from the waiting list and executed.

In some embodiments, the process of executing the upgrade task may be: obtaining the update data packet corresponding to the first program data from the cache area according to the first identifier in the upgrade task. And the update data package is parsed and installed in storage area 1 to update the first program data.

In some embodiments, when the execution of the upgrade task is started, the process enters S103-4.

S103-4, notify the desktop to change the desktop icon of the associated application.

In some embodiments, a broadcast message may be used to notify the desktop that the desktop icon of the associated application will be changed. For details, reference may be made to the descriptions in the foregoing embodiments.

Generally speaking, it is divided into two stages according to the time displacement method. Among them, the first stage is to wait for all associated applications to switch to an unused state before parsing and installing the update data package. The second stage is the parsing and installation process of the update data package, which prevents users from using associated applications during parsing and installation.

The key to achieving time dislocation lies in the first stage. That is, before the update data package is parsed and installed, the associated applications corresponding to the first program data need to be in an unused state.

As an implementation method, it can be determined by regular query whether the associated application corresponding to the first program data is in an unused state.

When there are multiple upgrade tasks in the waiting list, you can loop through each upgrade task in the waiting list. During the loop traversal, each time an upgrade task is traversed, the usage status of the corresponding associated application is obtained based on the first program data indicated by the upgrade task. Thereby it is determined whether the associated application corresponding to the first program data is in an unused state.

As another implementation method, applications in use in the electronic device are monitored. When an application program in use is switched to an unused state, it is triggered to detect whether associated applications corresponding to the first program data are all in an unused state.

In addition to updating the first program data in a time-shifted manner, in order to improve the update efficiency, in the embodiment of the present application, the above-mentioned misaligned upgrade strategy may be to update the first program data in a storage space-shifted manner.

For example, the above-mentioned process of updating the first program data in a storage space dislocation manner may be:

Put the upgrade task corresponding to the first program data into the waiting list.

In the storage area 2 (also called the second storage area), the update data package corresponding to the first program data is parsed and installed. Create a temporary installation directory by parsing the installation. Among them, the temporary installation directory stores update program data, also known as second program data. The above updated program data is used to replace the data entity of the first program data.

It should be noted that the above-mentioned storage area 2 is different from the storage area 1 . Among them, storage area 1 is a storage space used to store first program data. In some embodiments, the first program data may be stored in a fixed installation directory in the storage area 1 .

For example, both the fixed installation directory and the temporary installation directory may include subdirectories named "/data/dalvik-cache", "package.xml", "package.list", etc. Among them, the subdirectory /data/dalvik-cache is used to store application code execution files (such as dex and oat files), and the subdirectory package.xml is used to store information such as permissions applied for by the application, signatures, and the location of the code. The subdirectory package.list is used to record information such as application installation location.

In some embodiments, the above-mentioned storage area 2 may be a spare storage area allocated in advance for the first program data. In other embodiments, the above-mentioned storage area 2 may also be a storage area divided from the free storage space for the first program data when performing an upgrade task.

Since storage area 1 and storage area 2 are different storage spaces, there is no need to forcefully close the application process of the associated application when parsing and installing the update data package. Therefore, the parsing and installation process of the update data package is prevented from affecting the user's use of the associated application.

After the update data package is parsed and installed in the storage area 2, the obtained temporary installation directory is associated with the first program data. For example, the temporary installation directory is associated with the first program data through User Identification (UID). In this way, the update program data in the temporary installation directory is also associated with the first program data. At the same time, there is also a corresponding relationship between the upgrade task and the first program data. Therefore, a corresponding relationship is established between the upgrade task and the update program data in the temporary installation directory.

Afterwards, it is also necessary to monitor whether the associated applications corresponding to the first program data are switched to an unused state, that is, to repeatedly obtain the usage status of the associated applications. If the associated applications corresponding to the first program data are switched to an unused state, the corresponding upgrade task is removed from the waiting list. Obtain update program data associated with the first program data according to instructions of the upgrade task. The updated program data is then used to replace the data entity of the first program data. Thus, the update of the first program data is completely completed.

That is, in the embodiment of the present application, the data entity of the first program data may be updated at the moment when the associated applications corresponding to the first program data are switched to an unused state.

In some embodiments, the determination of the usage status of associated applications may be periodically restarted until all associated applications of the first program data are in an unused state.

In other embodiments, it may also be triggered by the occurrence of an application program switching from an in-use state to an unused state in the electronic device, and it may be detected whether the associated applications of the first program data are all in an unused state.

In addition, in some embodiments, the method of replacing the data entity of the first program data with the updated program data may be to store the updated program data in the storage area 1 and overwrite the first program data. In addition, after the update program data is transferred, the storage area 2 is also cleared.

The above overlay update is suitable for scenarios where the update data packet is a full data packet. When the update data packet is an incremental data packet, the update program data can also be obtained after parsing the update data packet. However, the update program data in this scenario can also become incremental program data.

In this case, the above method of replacing the data entity of the first program data may also be: moving the incremental program data to the storage area 1 and integrating it with the first program data to complete the update of the first program data.

Among them, after the full data packet is parsed, updated data that completely replaces the first program data can be obtained. The incremental data packet needs to be merged with the original first program data after parsing to obtain updated data that completely replaces the first program data.

In some embodiments, fusing the incremental program data with the original first program data can be understood as using the incremental program data to perform at least one operation of adding, deleting, and replacing the original first program data. As a conceptual example, if the incremental program data indicates modification of part of the data in the original first program data, then the incremental program data replaces the modified part of the data in the original first program data. If the incremental program data indicates adding the data content of the original first program data, then the incremental program data is merged into the first program data. If the incremental program data indicates deletion of part of the data in the original first program data, then the instructed part of the data is deleted from the first program data.

In the process of updating the data entity of the first program data using the update program data, since the data entity of the first program data needs to be processed, the user also needs to be prompted to suspend use of the associated application during the processing. The method of reminding the user to suspend the use of the associated application may refer to the method of broadcast message notification mentioned in the previous embodiment, which will not be described again here.

In addition, after the first program data is updated, the desktop can also be notified through broadcast message 2 to cancel the suspension prompt for the associated application. For specific implementation, reference may be made to the descriptions in the foregoing embodiments.

Of course, in other embodiments, in order to shorten the time the user needs to wait for the data entity of the first program data to be updated, when the update data packet is a full data packet, after the update data packet is parsed and installed in the storage area 2, Directly replace the loading address of the first program data loaded by the associated application with the address of storage area 2. In this way, the update program data in the storage area 2 can be directly loaded the next time the associated application is started. In other words, when the associated application is started again, the original temporary installation directory becomes the new fixed installation directory.

When the update data packet is an incremental data packet, after the update data packet is parsed and installed in the storage area 2, the first program data also needs to be mirrored to the storage area 2 and merged with the incremental data package. After the data fusion is completed, the loading address of the first program data loaded by the associated application is replaced with the address of storage area 2.

Afterwards, you can also delete the original fixed installation directory to release redundant storage space.

Of course, in some other embodiments, after changing the loading address, the first program data in the original fixed installation directory can also be retained for a specified period of time. Within a specified period of time, continuously monitor whether the associated application is running abnormally.

The above-mentioned running exception may be an exception that occurs when loading the first program data. For example, when the first program data is the program file of an application program, if the associated application fails to start the program or the number of program error reports exceeds a preset value, it will be determined that a running abnormality has occurred. For another example, when the first program data is a program file of a public component, if an exception occurs when the associated application calls the public component, it will be determined that a running exception has occurred.

If there is a problem with abnormal operation of the associated application within the specified period of time, then the loading address of the first program data loaded by the associated application is restored to the address of storage area 1, and the program data in storage area 2 is cleared.

If no operation abnormality occurs in the associated application within a specified period of time, the first program data in the first storage area is deleted.

As an example, as shown in Figure 13, based on the program data update method shown in Figure 4, the above S103 may include:

S103-5, in storage area 2, parse and install the update data package. Obtain update program data by parsing the installation update data package.

S103-6, associate the update program data with the first program data.

S103-7: Monitor the usage status of the associated application of the first program data.

When all associated applications of the first program data are in an unused state, the process proceeds to S103-8. Otherwise, continue to execute S103-7.

S103-8: Update the data entity of the first program data using the associated update program data.

In addition, during the execution of S103-8, S103-9 also needs to be executed.

S103-9, notify the desktop to change the desktop icon of the associated application.

In some embodiments, the principles of S103-8 and S103-4 are the same and will not be described again.

Obviously, no matter what misplaced upgrade strategy is adopted, it is avoided to close the associated applications that are in use. Prevent associated applications from crashing during user use. Thus, conflicts between application usage and program updates are resolved.

S104: When the associated application is in an unused state, directly update the first program data based on the update data package.

In some embodiments, the update data package may be directly parsed and installed into the storage area 1 for updating the first program data in the fixed installation directory. During the parsing and installation period, broadcast message 1 can also be used to remind the user to suspend use of the associated application. Similarly, after the first program data update is completed, the suspension reminder can also be canceled through broadcast message 2.

In addition, whether the first program data is updated according to the misaligned upgrade strategy in S103 or the first program data is directly updated in S104, it is also necessary to consider whether the conditions of the electronic device are suitable for updating.

For example, before performing S103 or S104, it may be checked whether the electronic device has updated storage space requirements. If satisfied, continue to execute S103 or S104. Otherwise, it will not be executed.

For example, before performing S103 or S104, you may also check whether the remaining power of the electronic device supports completing the update. If the remaining power is sufficient to complete the update, continue to perform S103 or S104. Otherwise, it will not be executed. Of course, the way to determine whether the remaining power of the electronic device supports completion of the update may be to compare the remaining power with the lower limit of the upgrade power. If the remaining power is lower than the preset lower limit of power, it is determined that the remaining power does not support completing the update. If the remaining power is not lower than the preset lower limit of power, it is determined that the remaining power supports completion of the update.

For example, before performing S103 and S104, you may also check whether the electronic device is in a charging state. If it is in the charging state, continue to execute S103 or S104. Otherwise, it will not be executed.

An embodiment of the present application also provides an electronic device, which may include a display screen, a memory, and one or more processors. The display, memory and processor are coupled. The memory is used to store computer program code, which includes computer instructions. When the processor executes the computer instructions, the electronic device can be caused to perform various steps performed by the mobile phone in the above embodiments. Of course, the electronic device includes but is not limited to the above-mentioned display screen, memory and one or more processors. For example, the structure of the electronic device may refer to the structure of the mobile phone shown in FIG. 2 .

Embodiments of the present application also provide a chip system, which can be applied to the electronic devices in the foregoing embodiments. As shown in Figure 14, the chip system includes at least one processor 2201 and at least one interface circuit 2202. The processor 2201 may be the processor in the above-mentioned electronic device. The processor 2201 and the interface circuit 2202 may be interconnected via wires. The processor 2201 can receive and execute computer instructions from the memory of the above-mentioned electronic device through the interface circuit 2202. When the computer instructions are executed by the processor 2201, the electronic device can be caused to perform various steps performed by the mobile phone in the above embodiments. Of course, the chip system may also include other discrete devices, which are not specifically limited in the embodiments of this application.

Through the above description of the embodiments, those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above functional modules is used as an example. In actual applications, the above functions can be allocated as needed. It is completed by different functional modules, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. For the specific working processes of the systems, devices and units described above, reference can be made to the corresponding processes in the foregoing method embodiments, which will not be described again here.

Each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above integrated units can be implemented in the form of hardware or software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of the present application are essentially or contribute to the existing technology, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage device. The medium includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other media that can store program codes.

The above are only specific implementation modes of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the embodiments of the present application shall be covered by this application. within the protection scope of the application embodiment. Therefore, the protection scope of the embodiments of the present application should be subject to the protection scope of the claims.

Claims (21)

1. A program data update method, characterized in that the method includes: Obtain the update data package of public components, which include Google mobile service components, webview components, and UnionPay payment components; Determine a plurality of first applications associated with the common component, wherein the associated application refers to an application that calls the common component; Obtain the running status of the plurality of first applications, the running status includes foreground running, background running and stopped running; according to the running status, obtain the usage status of all the first applications; wherein, the usage status Including: an in-use state and an unused state; when the running state is the foreground running, the using state is the in-use state; when the running state is the background running and a multi-task interface is displayed, or When the running state is running in the background and a user's operation on the interface of the first application in the multi-tasking interface is received, the use state is an in-use state; When at least one of the first applications is in use, put the upgrade task corresponding to the public component into a waiting list; Obtain the usage status of all the first applications again; When all the first applications are in an unused state, the public components are upgraded based on the update data package of the public components; the upgrading of the public components includes: parsing and installing the update data of the public components package to update the common component; or to update the common component according to second program data; wherein the second program data is obtained after parsing and installing the update data package of the common component in the second storage area data; the second storage area is different from the first storage area; the first storage area is a storage area used to store the common component. 2. The method of claim 1, wherein the analyzing and installing the update data package of the public component includes: The update data package is parsed and installed in the first storage area to replace the common component. 3. The method of claim 1, wherein when the first application is in use and the update data packet of the public component is obtained, the method further includes: The update data package is parsed and installed in the second storage area to obtain the second program data. 4. The method of claim 1, wherein when the update data packet is a full data packet, updating the common component according to the second program data includes: The second program data is used to replace the common component. 5. The method of claim 1, wherein when the update data packet is an incremental data packet, updating the common component according to the second program data includes: The second program data is stored in the first storage area and merged with the common component. 6. The method of claim 1, wherein when the update data packet is a full data packet, updating the common component according to the second program data includes: The loading address of the common component is changed from the address of the first storage area to the address of the second storage area. 7. The method of claim 1, wherein when the update data packet is an incremental data packet, updating the common component according to the second program data includes: Mirror the common component to the second storage area and merge it with the second program data; The loading address of the common component is changed from the address of the first storage area to the address of the second storage area. 8. The method according to claim 6 or 7, characterized in that the method further comprises: The first application deletes the common component in the first storage area if no running abnormality occurs within a preset time period after the loading address is changed. 9. The method according to claim 6 or 7, characterized in that the method further comprises: If the first application runs abnormally within a preset time period after the loading address is changed, the loading address of the public component is restored to the address of the first storage area; Clear the second storage area. 10. The method according to any one of claims 1 to 7, characterized in that, in the process of updating the common component, the method further includes: Display prompt information on the desktop icon of the first application; or, After receiving a user's operation on the icon of the first application, display prompt information; The prompt information is used to prompt at least one of the following information: update status, update progress, update version, and update release time. 11. An electronic device, characterized in that the electronic device includes one or more processors and a memory; the memory is coupled to the processor, and the memory is used to store computer program code. The computer program code includes computer instructions. When one or more processes When the machine executes computer instructions, The one or more processors are used to obtain update data packets of public components, the public components include Google mobile service components, webview components, and UnionPay payment components; determine multiple first applications associated with the public components , wherein the associated application program refers to an application program that calls the public component; obtaining the running status of the plurality of first applications, the running status includes foreground running, background running and stopping running; according to the Running status: obtain the usage status of all the first applications; wherein, the usage status includes: in use status and unused status; when the running status is the foreground running, the usage status is In-use state; when the running state is running in the background and a multi-tasking interface is displayed, or the running state is running in the background and a user's operation on the interface of the first application in the multi-tasking interface is received When at least one of the first applications is in use, put the upgrade task corresponding to the common component into the waiting list; obtain all the first applications again. The use status of an application; when all the first applications are in an unused state, the public components are upgraded based on the update data package of the public components; the upgrading of the public components includes: parsing and installing the The update data package of the public component is used to update the public component; or, the public component is updated according to the second program data; wherein the second program data is parsed and installed in the second storage area to install the public component. Data obtained after updating the data package; the second storage area is different from the first storage area; the first storage area is a storage area used to store the common component. 12. The electronic device according to claim 11, wherein the one or more processors are configured to parse and install the update data package of the common component, including: An update data package for installing the common component is parsed in the first storage area to replace the common component. 13. The electronic device of claim 11, wherein when the first application is in use and the update data packet of the common component is obtained, the one or more processors further Used for: The update data package for installing the common component is parsed in the second storage area to obtain the second program data. 14. The electronic device of claim 11, wherein when the update data packet is a full data packet, the one or more processors are configured to update the data according to the second program data. The common components described above include: The second program data is used to replace the common component. 15. The electronic device of claim 11, wherein when the update data packet is an incremental data packet, the one or more processors are configured to update the data according to the second program. The common components include: The second program data is stored in the first storage area and merged with the common component. 16. The electronic device of claim 11, wherein when the update data packet is a full data packet, the one or more processors are configured to update the data according to the second program data. The common components described above include: The loading address of the common component is changed from the address of the first storage area to the address of the second storage area. 17. The electronic device of claim 11, wherein when the update data packet is an incremental data packet, the one or more processors are configured to update the data according to the second program. The common components include: Mirror the common component to the second storage area and merge it with the second program data; The loading address of the common component is changed from the address of the first storage area to the address of the second storage area. 18. The electronic device according to claim 16 or 17, characterized in that the one or more processors are also used to: The first application deletes the common component in the first storage area if no running abnormality occurs within a preset time period after the loading address is changed. 19. The electronic device according to claim 16 or 17, characterized in that the one or more processors are also used for: If the first application runs abnormally within a preset time period after the loading address is changed, the loading address of the public component is restored to the address of the first storage area; Clear the second storage area. 20. The electronic device according to any one of claims 11 to 17, characterized in that, in the process of updating the common component, the one or more processors are also used to: Display prompt information on the desktop icon of the first application; or, After receiving a user's operation on the icon of the first application, display prompt information; Wherein, the prompt information is used to prompt at least one of the following information: update status, update progress, update version, and update release time. 21. A computer storage medium, characterized by comprising computer instructions that, when run on an electronic device, cause the electronic device to perform the method according to any one of claims 1-10.