CN116775084B - System upgrade methods and electronic equipment - Google Patents

Abstract

The application provides a system upgrading method and electronic equipment, and relates to the field of computers. The application provides a system upgrading method, when an OUC detects a system upgrading instruction, a first connection is allocated for the current time, a first service module receives the installation state of an upgrading engine service through the first connection, the first service module indicates the upgrading engine service to install a target system upgrading installation package according to the installation state and a target installation mark in the current life cycle, and the first connection is disconnected after the installation is finished and the life cycle of the installation is finished. By adopting the method, the electronic equipment can be normally installed when the system upgrade installation package of the parameter type and the system upgrade installation package of the patch type (or the hota type) are installed at the same time, so that the problem of disordered installation is avoided, and the electronic equipment can also be timely installed with the system upgrade installation package of the parameter type.

Description

System upgrade methods and electronic equipment

Technical field

The present application relates to the field of computer technology, and in particular, to a system upgrade method and electronic equipment.

Background technique

Terminal devices usually need to install a system before they can be used by users. For example, mobile phones are equipped with Android systems, iOS systems, etc. The terminal device can send a packet search request to the server. The server responds to the packet search request, searches for whether there is a system upgrade installation package of parameter, hota or patch type, and returns the packet search result to the terminal device. The terminal device receives the packet search result. If the terminal device determines that the packet search is successful based on the packet search result, the terminal device can obtain the searched system upgrade installation package from the server and install a new version of the system upgrade installation package.

However, if the terminal device installs the parametric version of the system upgrade installation package and the hota version of the system upgrade installation package at the same time, or installs the parametric version of the system upgrade installation package and the patch version of the system upgrade installation package at the same time, installation conflicts will occur, for example During the process of installing a patch-type system upgrade installation package on a terminal device, the terminal device will receive a message indicating whether the installation of the parameter version of the system upgrade installation package is successful or failed, and the decompression interface corresponding to the parameter in the terminal device is called multiple times.

Contents of the invention

In order to solve the above technical problems, this application provides a system upgrade method and electronic equipment, so that when the electronic equipment simultaneously installs a parameter type system upgrade installation package and a patch type (or hota type) system upgrade installation package, installation can be avoided. To solve the problem of confusion, electronic equipment can promptly install parameter-type system upgrade installation packages to improve the performance of electronic equipment.

In a first aspect, this application provides a system upgrade method, which includes: a system update application detects a system upgrade instruction, and allocates a first connection to the target system upgrade installation package to be installed this time. The first connection is used for the system update application. The first business module communicates with the upgrade engine service; the first business module receives the status of the upgrade engine service sent by the upgrade engine service in real time through the first connection; within the life cycle of this installation, the first business module allows the use of the received upgrade engine The status of the service; if the status of the upgrade engine service is available, the first business module generates an installation instruction based on the status of the upgrade engine service and the target installation ID and sends it to the upgrade engine service. The target installation ID is used to indicate whether the current business module Call the target installation interface in the upgrade engine service. The target installation interface is the installation interface corresponding to the type of the target system upgrade installation package; the upgrade engine service responds to the installation instructions and installs the target system upgrade installation package; if the first business module determines that this The installation ends, marking the end of the life cycle of this installation and disconnecting the first connection.

In this way, the system update application allocates a corresponding connection (i.e., the first connection) to the target system upgrade installation package to be installed this time. When the first connection is established, the first business module receives the status sent by the upgrade engine service in real time, and this In the example, the first business module is allowed to use the status of the upgrade engine service during the life cycle of this installation, which can avoid the period from when the first business module performs the operation of disconnecting the first connection to when the first connection is disconnected. The first business module uses the received status of the upgrade engine service, which causes installation errors and confusion; because the target installation identification can indicate whether the current business module calls the target installation interface in the upgrade engine service, by adding a new target installation identification , can enrich the information of the first business module to determine whether to instruct the upgrade engine service to install the target system upgrade installation package this time, so that the first business module can accurately determine whether the installation process of the upgrade engine service is occupied, and install the target system upgrade in a timely manner Installation packages (such as parameter type, patch type or hota type) to avoid upgrading the engine service while installing parameter type system upgrade installation packages and other system upgrade installation packages (i.e. patch type system upgrade installation packages or hota type system upgrade installation packages) package) causing installation conflicts. At the same time, the upgrade engine service promptly installs the target system upgrade installation package (such as a parameter-type system upgrade installation package), which can improve the performance of electronic equipment.

According to the first aspect, within the life cycle of this installation, the first business module allows the use of the received status of the upgrade engine service, including: the first business module obtains the first identification information, and the first identification information is used for Indicates whether the life cycle of this installation has ended, wherein the initial first identification information indicates that the life cycle of this installation has not ended; if the first business module detects the first identification information indicating that the life cycle of this installation has not ended, the first business module A business module allows the use of the status of the upgrade engine service; if the first business module detects the first identification information indicating that the life cycle of this installation is over, the first business module discards the status of the upgrade engine service.

In this way, the first business module can quickly determine the end of the life cycle of this installation through the first identification information, so that when the first business module disconnects the first connection operation, it can no longer use the status of the upgrade engine service to avoid Due to the long time it takes to disconnect the first connection, the first business module is still using the upgrade engine service.

According to the first aspect, the system update application detects the system upgrade instruction and allocates the first business module to the target system upgrade installation package to be installed this time; the first business module sends a service request to the upgrade engine service, and the service request is used to request the upgrade engine The service installs the target system upgrade installation package; the upgrade engine service responds to the service request, binds the interface definition language AIDL interface with the first business module, and establishes the first connection. In this way, the first business module binds the AIDL interface so that the first connection corresponds to the target system upgrade installation package of this installation, ensuring that each connection is used to transmit data related to the target system upgrade installation package, ensuring the accuracy of the installation. sex.

According to the first aspect, marking the end of the life cycle of this installation includes: the first business module updating the first identification information to indicate that the life cycle of this installation has ended. In this way, the first business module marks the end of the life cycle of this installation by modifying the first identification information. This method is simple, fast and short in time.

According to the first aspect, the first business module generates an installation instruction according to the status of the upgrade engine service and the target installation identification, including: if the first business module detects that the status of the upgrade engine service is idle and detects that the target installation identification indicates the first If the business module does not call the target installation interface, the first business module determines that the installation instruction instructs the upgrade engine service to install the target system upgrade installation package, and updates the target installation identification to indicate that the first business module has called the target installation interface; where, the initial The target installation identification indicates that the first business module has not called the target installation interface. In this way, the first business module can quickly determine whether the upgrade engine service has installed the target system upgrade installation package by determining whether the first business module calls the target installation interface in the idle state.

According to the first aspect, the method further includes: in response to the installation instruction, the upgrade engine service updates the status of the upgrade engine service to a busy status. In this way, the upgrade engine service updates its own installation status (that is, the status of the upgrade engine service) in a timely manner.

According to the first aspect, the method also includes: if the first business module detects that the status of the upgrade engine service is a busy state, detect whether the establishment time of the first connection has exceeded the preset time; if it is detected that the preset time has been exceeded, detect the target Whether the installation identification indicates that the first business module has called the target installation interface; if not, the first business module determines the next installation of the target system upgrade installation package. In this way, the first business module detects that the first connection establishment times out and does not call the target installation interface, which indicates that the upgrade engine service is installing other system upgrade installation packages. For example, the target system upgrade installation package is a parameter type installation package, and other system upgrade installation packages The package can be a patch package or hota. Since the upgrade engine service is installing other system upgrade installation packages, the first business module determines to wait for the next installation, which can avoid installation conflicts. When the first business module detects that the first connection establishment has timed out and the target installation interface has been called, it determines that the installation of the target system upgrade installation package has failed, and disconnects the first connection to avoid the upgrade engine service failing to install the target system upgrade installation package for a long time.

According to the first aspect, the method also includes: if the first business module determines that the target system upgrade installation package will be installed next time, it determines that this installation is over; after marking the end of the life cycle of this installation and disconnecting the first connection, the first business module The method also includes: after the first business module disconnects the first connection for a second preset period of time, the system update application re-allocates the second connection to the target system upgrade installation package to be installed this time to re-install the target system upgrade installation package. . In this way, the first business module re-establishes the second connection to try to install the target system upgrade installation package, so that the target system upgrade installation package can be installed in time and the performance of the electronic device can be improved.

According to the first aspect, the method further includes: if the first business module detects that the target installation identifier indicates that the first business module has called the target installation interface, the first business module determines that the current installation of the target system upgrade installation package has failed, and marks this time. The installation's life cycle ends and the first connection is disconnected. In this way, when the first business module detects that the installation of the target system upgrade installation package fails this time, it disconnects the first connection and marks the end of the life cycle of this installation, so that the first business module can no longer use the received upgrade engine service. status, and also avoids the upgrade engine service from occupying the installation process for a long time after the installation fails.

According to the first aspect, the first business module generates an installation instruction according to the status of the upgrade engine service and the target installation identification, including: if the detected status of the first business module is the end state and the detected target installation identification indicates that the first business module has not When the target installation interface is called, the first business module determines that the installation instruction instructs the upgrade engine service to install the target system upgrade installation package, and updates the target installation identification to indicate that the first business module has called the target installation interface; wherein, the initial target installation identification Indicates that the first business module has not called the target installation interface. In this way, when the first business module detects the end state and does not call the target installation interface, it means that the current installation is not the target system upgrade installation package. That is, the first business module identifies that the current installation end state is not the target of this installation through the target installation identifier. The installation results of the system upgrade installation package further avoid the interference caused by the installation results of other system upgrade installation packages on this target system upgrade installation package.

According to the first aspect, the method further includes: if the detected state of the first business module is the end state and the detected target installation identifier indicates that the first business module has called the target installation interface, the first business module determines that the target is successfully installed this time. System upgrade installation package; mark the end of the life cycle of this installation and disconnect the first connection. In this way, when the first business module determines that the installation is successful, it disconnects the first connection, which can avoid receiving the installation results of other system upgrade installation packages, causing installation confusion.

According to the first aspect, the method also includes: if the first business module detects that the status of the upgrade engine service is unavailable, marking the end of the life cycle of this installation and disconnecting the first connection; disconnecting the first business module After the second preset duration of the first connection, the system update application re-allocates the second connection to the target system upgrade installation package to be installed this time, so as to re-install the target system upgrade installation package. In this way, when the upgrade engine service is unavailable, the first business module directly tries the next installation, which can reduce the judgment steps and shorten the time to install the target system upgrade installation package.

According to the first aspect, the type of target system upgrade installation package includes: parameter package, hota or patch package.

According to the first aspect, before the system update application detects the system upgrade instruction and allocates a first connection to the target system upgrade installation package to be installed this time, the method further includes: the system update application receives the installation target system upgrade installation input by the user. System upgrade instructions for the package; or, the system update application detects that the electronic device is in a screen-off state and generates system upgrade instructions for installing the target system upgrade installation package. In this way, the electronic device provides two ways to trigger the installation of the target system upgrade installation package, which provides convenience for users to use the installation method.

In a second aspect, the present application provides an electronic device, including: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored on the memory, and when the computer program is processed by one or more When executed by multiple processors, the electronic device is caused to execute the first aspect and the system upgrade method corresponding to any implementation of the first aspect.

The second aspect and any implementation manner of the second aspect respectively correspond to the first aspect and any implementation manner of the first aspect. The technical effects corresponding to the second aspect and any implementation manner of the second aspect may be referred to the technical effects corresponding to the above-mentioned first aspect and any implementation manner of the first aspect, which will not be described again here.

In a third aspect, the present application provides a computer-readable medium for storing a computer program. When the computer program is run on an electronic device, the electronic device causes the electronic device to execute any one of the above first aspect and the first aspect. The system upgrade method corresponding to the implementation method.

Description of drawings

In order to explain the technical solutions of the embodiments of the present application more clearly, the drawings needed to be used in the description of the embodiments of the present application will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. , for those of ordinary skill in the art, other drawings can also be obtained based on these drawings without exerting creative labor.

Figure 1 is a schematic diagram illustrating a conflict in the installation of a system upgrade package on a mobile phone;

Figure 2 is a schematic structural diagram of an exemplary electronic device;

Figure 3 is a software structure block diagram of an exemplary electronic device;

Figure 4 is an exemplary flow chart of a system upgrade;

Figure 5 is an exemplary interaction diagram between OUC and the upgrade engine service;

FIG. 6 is a schematic diagram illustrating an installation method for setting up a system upgrade installation package.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts fall within the scope of protection of this application.

The term "and/or" in this article is just an association relationship that describes related objects, indicating that three relationships can exist. For example, A and/or B can mean: A exists alone, A and B exist simultaneously, and they exist alone. B these three situations.

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

In the embodiments of this application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "such as" in the embodiments of the present application is not to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the words "exemplary" or "such as" is intended to present the concept in a concrete manner.

In the description of the embodiments of this application, unless otherwise specified, the meaning of “plurality” refers to two or more. For example, multiple processing units refer to two or more processing units; multiple systems refer to two or more systems.

Before describing the technical solutions of the embodiments of the present application, the system upgrade of the embodiments of the present application will first be described with reference to the drawings.

OTA (Over-the-Air Technology) upgrade is a standard software upgrade method provided by the Android system. It is a technology for remote management of SIM card data and applications through the air interface of mobile communications (GSM or CDMA). The OTA Update Client ("OUC") in the terminal device can send a packet search request to the server. The server responds to the packet search request, searches for whether there is a system upgrade installation package with parameters, hota or patch version, and sends it to the server. The terminal device returns the packet search results. The OUC of the terminal device receives the packet search result. If the OUC determines that the packet search is successful, the OUC can obtain the searched system upgrade installation package from the server and download the new version of the system upgrade installation package.

OUC in the terminal device can download multiple types of system upgrade installation packages at the same time. The types of system upgrade installation packages include: patches, hota or parameters. OUC can also download different types of system upgrade installation packages at different times. OUC can install the system upgrade installation package according to the priority of the system upgrade installation package type. Usually, the priority of patch and hota type system upgrade installation packages is higher than the priority of parameter type system upgrade installation packages. Patch and hota type system upgrade installation packages occupy a large capacity, and it takes a long time for terminal devices to install patches or hota type system upgrade installation packages. As a result, parameter type system upgrade installation packages cannot be updated in time, affecting the terminal equipment. performance. In order to prevent the terminal device from being unable to update the system upgrade installation package of the parameter type in time, the terminal device increases the priority of the system upgrade installation package of the parameter type so that the priority of the system upgrade installation package of the parameter type is the same as that of the patch or hota type. The system upgrade installation packages have the same priority, that is, after the terminal device downloads the system upgrade installation package of the parameter type, it will immediately trigger the terminal device to install the system upgrade installation package of the parameter type without the need to install patches or hota types on the terminal device. Install the system upgrade installation package of this parameter type after the system upgrade installation package, thereby improving the system performance of the terminal device.

However, since the priority of the parameter type system upgrade installation package is the same as the priority of the patch and hota type system upgrade installation package, the OUC may also instruct the upgrade engine service (UpdateEngineService) of the terminal device to install the parameter type system upgrade installation package. Package and patch type system upgrade installation packages, or install parameter type system upgrade installation packages and hota type system upgrade installation packages at the same time. Since there is only one installation process for upgrading the engine service, installation conflicts will occur. Installation conflicts will lead to confusing installation results and installation packages being installed multiple times. Figure 1 is a schematic diagram illustrating a conflict when a mobile phone installs a system upgrade package. As shown in Figure 1, the terminal device takes a mobile phone as an example. The mobile phone has downloaded a patch type system upgrade installation package and is installing the patch type system upgrade installation package. When the OUC of the mobile phone detects that the packet search result indicates that there is a system upgrade installation package with a new version of the parameter type, the mobile phone can prompt the user to update the parameters on the display interface. As shown in the display interface 101 shown in Figure 1, a prompt window 102 is displayed. The prompt window 102 can display first prompt information. The first prompt information is used to instruct the user to update the device optimization parameters. The prompt window 102 can also display second prompt information 103, which is used to instruct the user to start the automatic update function. If the user turns on the automatic update function, when the terminal device detects that the packet search result indicates that there is a system upgrade installation package of a new version of the parameter type, the interface will no longer display the prompt window 102. The terminal device will automatically download the new version of the parameter type system upgrade installation package, and when detecting that the terminal device is in the screen-off state, install the new version of the parameter type system upgrade installation package.

In this example, as shown in 1a in Figure 1, the user clicks the download and update control in the prompt window 102, and the OUC in the terminal device responds to the instructions entered by the user (i.e., download the system upgrade installation package and install the system upgrade installation package), download the system upgrade installation package of this parameter type from the server. After downloading the system upgrade installation package of this parameter type, the OUC instructs the upgrade engine service to install the system upgrade installation package of this parameter type. If the upgrade engine service fails to install the system upgrade package of the patch type at this time, and returns the status information to OUC, after OUC obtains the status, it instructs the upgrade engine service to end the installation of the system upgrade package of this parameter type. A notification 105 of software update failure is displayed on the display interface 104 of the mobile phone.

In this example, because the upgrade engine service is installing a patch type system upgrade installation package and a parameter type system upgrade installation package at the same time, when installing the parameter type system upgrade installation package, OUC receives the patch type system upgrade installation package. The installation result (such as successful installation, installation failure) causes OUC to no longer install the system upgrade installation package of this parameter type, or calls the decompression interface of this parameter type multiple times, that is, installs the system upgrade installation of this parameter type multiple times. Bag. In the same way, it may also happen that when the upgrade engine service is installing a patch type (or hota type) system upgrade installation package, OUC receives the installation result of the installation parameter type system upgrade installation package (such as successful installation, installation failure), resulting in OUC The system upgrade installation package of this patch type (or hota type) will no longer be installed, or the decompression interface of this patch type (or hota type) will be called multiple times.

Embodiments of the present application provide a system upgrade method, which is run by an electronic device. The system upgrade application in the electronic device detects the system upgrade instruction and allocates a first connection to the target system upgrade installation package to be installed this time. A connection is used for the first business module of the system update application to communicate with the upgrade engine service; the first business module receives the status of the upgrade engine service sent by the upgrade engine service in real time through the first connection; within the life cycle of this installation, the first The business module is allowed to use the status of the received upgrade engine service; if the status of the upgrade engine service is available, the first business module generates an installation instruction based on the status of the upgrade engine service and the target installation ID and sends it to the upgrade engine service and the target installation ID. Used to indicate whether the current business module calls the target installation interface in the upgrade engine service. The target installation interface is the installation interface corresponding to the type of the target system upgrade installation package; the upgrade engine service responds to the installation instructions and installs the target system upgrade installation package; If the first business module determines that this installation is over, it marks the end of the life cycle of this installation and disconnects the first connection.

In this example, the first business module of the system upgrade application is only allowed to use the status of the upgrade engine service during the life cycle of this installation. This can avoid the first business module also using the upgrade engine service during the process of disconnecting the first connection. status to instruct the upgrade engine service to install the target system upgrade installation package, causing installation confusion. In this example, the status of the upgrade service engine and the target installation identification can be used to accurately determine whether the target system upgrade installation package can be installed, preventing the installation process of the upgrade engine service from simultaneously installing the target system upgrade installation package and other system upgrade installation packages. An installation conflict has occurred. At the same time, this system upgrade method allows parameter-type system upgrade installation packages to be updated in time to improve the performance of electronic equipment.

FIG. 2 is a schematic structural diagram of an electronic device 100 according to an embodiment of the present application. It should be understood that the electronic device 100 shown in FIG. 2 is only an example of an electronic device, and the electronic device 100 may have more or fewer components than shown in the figure, and two or more components may be combined. parts, or can have different part configurations. The various components shown in Figure 2 may be implemented in hardware, software, or a combination of hardware and software including one or more signal processing and/or application specific integrated circuits.

The electronic device 100 may include: a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2. Mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone interface 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, And subscriber identification module (subscriber identification module, SIM) card interface 195, etc. 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.

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

The layered architecture of the electronic device 100 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 three layers, from top to bottom: application layer, application framework layer, and kernel layer. It can be understood that the layers in the software structure of FIG. 3 and the components included in each layer do not constitute specific limitations on the electronic device 100 . In other embodiments of the present application, the electronic device 100 may include more or fewer layers than shown in the figures, and each layer may include more or fewer components, which is not limited by this application.

As shown in Figure 3, the application layer can include a series of application packages. Application packages can include system update applications, camera, gallery, calendar, short message, calling, navigation, Bluetooth and other 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.

The system update application (ie, OUC) can send search requests to the server in real time and obtain the packet search results returned by the server. If the OUC detects that the packet search result indicates that a new version of the system upgrade installation package exists, the OUC can download the new version of the system upgrade installation package from the server. If the OUC receives the upgrade instruction input by the user or detects that the upgrade conditions are met, the OUC executes the system upgrade method in this application.

As shown in Figure 3, the application framework layer can include the upgrade engine service, window manager, resource manager, content provider, view system, phone manager, notification manager, etc.

The upgrade engine service is used to install the system upgrade installation package to be upgraded.

A 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 resource manager provides various resources to applications, such as localized strings, icons, pictures, layout files, video files, etc.

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 view system includes visual controls, such as controls that display text, controls that display pictures, etc. A view system can be used to build applications. The display interface can be composed of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide communication functions of the electronic device 100 . For example, call status management (including connected, hung up, etc.).

The notification manager allows applications 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.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, audio driver, and sensor driver.

Figure 4 is an exemplary flow chart of a system upgrade. The system upgrade process is described in detail below:

Electronic devices can be mobile phones, tablets, vehicle-mounted devices, smart bracelets, smart watches, laptops, etc. In this example, the electronic device is a mobile phone. The mobile phone application includes a system update application (ie, OUC), which can obtain a new version of the system upgrade installation package and instruct the upgrade engine service to install the new version of the system upgrade installation package. The OUC receives the packet search result returned by the server. If the packet search result indicates that there is a new parameter version (ie, a system upgrade installation package of parameter type), the OUC can display a prompt window 102 as shown in 1a in Figure 1, and the user clicks "Download and update" button, the OUC generates system upgrade instructions in response to the user's click operation.

In another example, as shown in 6a in Figure 6, the user can click the "More" button 601 in the software setting interface, and the mobile phone displays a pop-up box 602 in response to the user's operation of clicking the button 601. The pop-up box 602 may include two options, the first option is used to jump to the update setting page of patches and hota, and the second option is used to jump to the update setting page of parameters. In this example, as shown in 6a in Figure 6, the user clicks the second option, and the display page of the mobile phone jumps to the parameter update setting page 603. The user can click button 604 to enable the automatic download and update function. After being turned on, when the OUC of the mobile phone detects that the electronic device is in a screen-off state, it can generate a system upgrade instruction to install a new parameter version.

Similarly, as shown in 6a of Figure 6, if the user clicks the first option, the display page of the mobile phone jumps to the patch and hota update setting page 605. The user can click button 606 to enable the automatic download and update function. After the function is turned on, when the OUC of the mobile phone detects that the electronic device is in a screen-off state, it can generate an upgrade instruction to install a new patch or hota version. Optionally, the user can click button 607, and the mobile phone generates a system upgrade instruction when it detects that the screen is off and in the preset installation period. If button 606 and button 607 are both turned on, the mobile phone can automatically download a new version of the system upgrade installation package under WLAN or mobile network. When it is detected that the screen is in the off-screen state and is in the preset installation period (such as 02:00~04 :00), generate an upgrade command.

When the OUC of the mobile phone generates a system upgrade instruction, the OUC can allocate the first business module to the target system upgrade installation package to be installed this time. In this example, the type of the target system upgrade installation package to be installed can be parameter, patch or hota.

If the system upgrade instruction instructs the installation of a system upgrade installation package of parameter type, the system upgrade installation package of this parameter type is used as the target system upgrade installation package. If the system upgrade instruction instructs the installation of a system upgrade installation package of patch type, the system upgrade installation package of this patch type is installed. package as the target system upgrade installation package.

It should be noted that OUC can allocate different business modules to different system upgrade installation packages to establish different connections. That is to say, in this example, different business modules of OUC can establish their corresponding connections at the same time to install their corresponding target system upgrade installation packages. For example, the first business module may establish a first connection to install a parameter-type system upgrade installation package, and the second business module may establish a third connection to install a patch-type system upgrade installation package.

Step 401: The first business module binds the UpdateEngine service and establishes a connection.

For example, the first business module may send a service request to install the target system upgrade installation package to the upgrade engine (UpdateEngine) service. In response to the service request, the upgrade engine (UpdateEngine) service binds an interface definition language (Android Interface Definition Language, "AIDL") interface with the first business module to establish a first connection. The first connection is used to transmit data related to this installation. For example, the first connection can transmit the installation status of the upgrade engine service, and can also transmit the target system upgrade installation package to be installed. It can be understood that the first connection created by the first business module matches this installation.

Optionally, when the first service module successfully establishes the first connection, the timer may be started. If the first service module disconnects the first connection, the timer is destroyed. In other words, each connection has its own corresponding timer.

Step 402: The first business module receives the status of the upgrade engine service.

For example, after the first business module successfully establishes the first connection, the upgrade engine service can obtain the current installation status (that is, the status of the upgrade engine service) in real time, and transmit the obtained installation status to the first connection through the first connection. Business module. The first business module receives the installation status sent by the upgrade engine service in real time. The installation status received by the first service module may include: idle status, busy status, end status, and unavailable status. Among them, idle state, busy state and end state are available states.

The idle state is used to indicate that the installation process in the upgrade engine service is not occupied. The busy status is used to indicate that the installation process of the upgrade engine service is installing the system upgrade installation package. The end status is used to indicate whether the installation process of the upgrade engine service succeeds or fails in installing the system upgrade installation package. The unavailable state is an abnormal state.

It should be noted that if OUC establishes multiple connections at the same time, the upgrade engine service will transmit the status of the upgrade engine service to each business module in OUC through each connection in real time.

Step 403: The first business module determines whether the first identification information indicates whether the life cycle of this installation is over. If so, end the process. If not, execute step 404.

For example, after receiving the installation status sent by the upgrade engine service, the first business module obtains the stored first identification information, and determines whether the first identification information indicates the end of the life cycle of this installation. If the first business module detects that the first identification information indicates that the life cycle of this installation has not ended, the first business module allows the use of the received installation status. If the first business module detects that the first identification information indicates that the life cycle of this installation is over, it may discard the received installation status or directly end the process. In this example, when the first business module detects that the first identification information indicates the end of the life cycle of this installation, the process is directly terminated as an example.

When the first connection is successfully created, the first identification information is set to indicate that the life cycle of this installation has not ended. The life cycle of this installation is used to indicate the period during which the received installation status is allowed to be used during the current installation of the target system upgrade installation package. In this example, the first business module can set the initial value of the first identification information when the first connection is successfully established. For example, when the first connection is established, the first business module sets isClosed=false, and the first identification information is " isClosed", when the value of isClosed is "false", it indicates that the current first connection has been established, which indicates that the life cycle of this installation has not ended. If the value of isClosed is "true", it means that the current first connection is disconnected, which indicates that the life cycle of this installation has ended. It should be noted that when the value of isClosed is "true", the first connection may still be in the connected state. For example, when the first business module performs the operation of disconnecting the first connection, the value of isClosed is set to "true". But the first connection has not yet been disconnected.

When the first business module successfully establishes the first connection and sets (or marks) the first identification information to indicate that the life cycle of this installation has not ended, it is regarded as the start time of the life cycle of this installation. The first business module sets (or marks) the first identification information to indicate that the life cycle of this installation has ended as the end time of the life cycle of this installation. The first business module is allowed to use the received installation status during the life cycle of this installation.

Since the upgrade engine service sends the installation status of the upgrade engine service to the first business module in real time, the first business module can execute step 403 when receiving the installation status of the upgrade engine service until the process ends.

Step 404: The first business module allows the current installation status of the upgrade engine service to be used.

For example, if the first business module detects that the first identification information indicates that the life cycle of this installation has not ended, it determines that the first business module can use the current installation status of the upgrade engine service.

Step 405: The first business module detects that the installation state is idle, and detects whether the target installation identifier indicates that the first business module has called the target installation interface. If not, execute step 406.

In one example, the first business module obtains an installation status that is allowed to be used. If the installation status is an idle state, the first business module can detect whether the target installation identifier indicates that the first business module has called the target installation interface. Optionally, when the first service module successfully establishes the first connection, the initial value of the target installation identifier may be set to indicate that the first service module does not call the target installation interface. Optionally, when sending a service request to install the target system upgrade and installation to the upgrade engine service, the first business module may set the initial value of the target installation identifier to indicate that the first business module does not call the target installation interface.

For example, if the target system upgrade installation package is the parameter package of version 6.1.0, the first business module installs the parameter package of version 6.1.0, establishes the first connection, and sets the first identification information to indicate this installation. If the life cycle has not ended (such as isClosed=false), set the value of the target installation identifier (such as "isCalledStartUpdatePara") to false. The upgrade engine service feeds back the installation status of the upgrade engine service to the first business module in real time through the first connection. When receiving the installation status of the upgrade engine service (for example, the installation status is idle), the first business module detects that the value of isClosed is false and determines that the installation status of the upgrade engine service is allowed. The first business module detects that the installation state is idle, and detects whether the value of isCalledStartUpdatePara is true. In this example, when the first business module establishes the first connection, it sets the initial value of isCalledStartUpdatePara to fasle. Currently, the first business module detects that the value of isCalledStartUpdatePara is fasle, that is, the first business module can determine the current upgrade engine. The service is in an idle state and the parameter package of version 6.1.0 is not installed. The first business module instructs the upgrade engine service to install the parameter package of version 6.1.0. At this time, the first business module calls the parameter package corresponding to the type of the parameter package. To install the interface, you can set isCalledStartUpdatePara to true. Optionally, the first business module can also set isCalledStartUpdatePara to true (ie, step 407), and then instruct the upgrade engine service to install the parameter package of version 6.1.0. The upgrade engine service installs the target system according to the instructions of the first business module. Upgrade the installation package (step 406).

Optionally, the first business module may also update the target installation identification to indicate that the first business module has called the target installation interface while instructing the upgrade engine service to install the target system upgrade installation package.

Step 406: The upgrade engine service installs the target system upgrade installation package according to the instructions of the first business module.

For example, the first business module generates an installation instruction, which is used to instruct the upgrade engine service to install the target system upgrade installation package. The upgrade engine service responds to the installation instruction and installs the target system upgrade installation package. At the same time, the upgrade engine service updates the installation status of the upgrade engine service (also called the status of the upgrade engine service) from the idle state to the busy state.

Step 407: The first business module updates the target installation identification to indicate that the first business module has called the target installation interface.

Step 408: The first service module detects that the installation status is a busy status, and detects whether the timer times out. If yes, step 409 is executed.

For example, if the first business module detects that the current installation status of the upgrade engine service is in a busy state, it detects whether the time recorded by the timer exceeds a first preset time length. The first preset time length can be set in advance, for example, the first preset time length. Let the duration be 1 minute, 45 seconds, 30 seconds, etc. If the first service module detects that the time recorded by the timer exceeds the first preset time period, it determines that the timer has timed out and executes step 409.

If the first business module detects that the time recorded by the timer does not exceed the first preset time, the first business module does not perform further processing, and the upgrade engine service continues to install the system upgrade installation package currently being installed. Optionally, the system upgrade installation package being installed by the upgrade engine service may be a target system upgrade installation package or other system upgrade installation packages.

For example, referring to the example in step 406, the first business module instructs the upgrade engine service to install the parameter package of version 6.1.0. When the upgrade engine service installs the target system upgrade installation package according to the instructions of the first business module, the installation status Update from idle to busy. The upgrade engine service sends the current installation status (ie, busy status) to the first business module. The first business module detects isClosed=false and allows the installation status (ie, busy status) to be used. The first business module detects that the installation status is busy and obtains the duration recorded by the timer (such as 30 seconds). Assume that the first preset duration is 45 seconds. The first business module detects that the duration recorded by the timer is less than the first preset duration. For a set time, the first business module does not perform operations, and the upgrade engine service continues to install the parameter package of version 6.1.0. If the upgrade engine service successfully installs the parameter package of version 6.1.0, the installation status of the upgrade engine service can be updated to the completed status.

For another example, the upgrade engine service is currently installing a patch package (i.e., a patch-type system upgrade installation package). The upgrade engine service sends the current installation status (i.e., busy status) to the first business module, and the first business module detects to isClosed=false to allow this installation state (i.e. busy state) to be used. The first business module detects that the installation status is busy and obtains the duration recorded by the timer (such as 50 seconds). Assume that the first preset duration is 45 seconds. The first business module detects that the duration recorded by the timer is greater than the first preset duration. Assuming the duration, the first service module determines that the timer has timed out, detects whether the target installation identifier indicates that the first service module has called the target installation interface, and then executes step 409.

Step 409: The first business module detects whether the target installation identifier indicates that the first business module has called the target installation interface. If yes, perform step 410; if not, perform step 415.

For example, if the first business module detects that the target installation identifier indicates that the first business module has not called the target installation interface, it determines to wait for the next installation of the target system upgrade installation package, the first business module disconnects the first connection, and The first identification information is updated to indicate the end of the life cycle of this installation, that is, step 415 is executed. Since the target system upgrade installation package has not been installed this time, you can wait for the next installation of the target system upgrade installation package. That is, the first business module can wait (or delay) for the second preset time to re-establish a new installation with the upgrade engine service. connection to retry installing the target system upgrade installation package.

If the first business module detects that the target installation identifier indicates that the first business module has called the target installation interface, it determines that the installation of the target system upgrade installation package failed this time (ie, step 410), and executes step 411.

Step 410: The first business module determines that the installation of the target system upgrade installation package failed.

Optionally, the first business module may determine that the installation of the target system upgrade installation package fails, and perform step 411.

Step 411: The first service module disconnects and updates the first identification information to indicate the end of the life cycle of this installation.

Illustratively, the first business module disconnects the first connection (ie, unbinds the AIDL interface), and updates the first identification information to indicate the end of the life cycle of this installation. For example, the first business module sets the value of isClosed to true. When the first business module receives the installation status sent by the upgrade engine service, the first business module detects that the value of isClosed is true and ends the process.

After the first business module performs the operation of disconnecting the first connection, the first connection will not be disconnected immediately. During the period from when the first business module performs the operation of disconnecting the first connection to the time when the first connection is disconnected, the upgrade engine The service still returns the installation status of the upgrade engine service to the first business module. In this example, when the first business module disconnects the first connection, it also updates the first identification information (updated to indicate the end of the life cycle of this installation), so that the first business module disconnects the first connection. During the period from the operation of connecting to the disconnection of the first connection, the first business module is no longer allowed to use the received installation status, thereby preventing the first business module from performing the operation of disconnecting the first connection to the first connection. Installation errors and confusion may occur during the disconnection period.

Step 412: The first business module detects that the installation status is the completion status, and detects whether the target installation identifier indicates that the first business module has called the target installation interface. If yes, perform step 413; if not, perform step 406.

Exemplarily, the first business module detects that the installation status is the end state, and also detects whether the target installation identifier indicates that the first business module has called the target installation interface. If so, it is determined that the current installation of the target system upgrade installation package is completed. Disconnect the first connection. If not, it indicates that the currently installed other system upgrade installation packages have ended, and the target system upgrade installation package can be installed, that is, step 406 is performed.

For example, if the upgrade engine service fails or succeeds in installing a patch package, the installation status is updated to the completed status. It is assumed that the target system installation package is the parameter package of version 6.1.0. The upgrade engine service sends the current installation status (ie, the end status) to the first business module. The first business module detects isClosed=false and allows the use of the installation status (ie, the end status). The first business module detects that the installation status is the completed state and detects that the value of the target installation identifier (such as "isCalledStartUpdatePara") is false, then instructs the upgrade engine service to start installing the parameter package of version 6.1.0 and changes the value of the target installation identifier. Updated to true. When the upgrade engine service starts to install the parameter package of version 6.1.0, the installation status is updated from the completed status to the busy status.

Step 413: The first business module determines that the installation is completed.

The first business module determines that the installation is completed, and the first business module can process the installation result, such as displaying the result of installing the current system upgrade installation package on the display interface.

Step 414: The first service module disconnects and updates the first identification information to indicate the end of the life cycle of this installation.

This step is similar to step 411. For related description, please refer to the description in step 411, which will not be described again here.

Step 415: The first business module detects that the installation status is unavailable, disconnects the connection, and updates the first identification information to indicate the end of the life cycle of this installation.

For example, when the first business module detects that the installation status is unavailable, it performs the operation of disconnecting the first connection, and updates the first identification information to indicate the end of the life cycle of this installation.

Step 416: After delaying the second preset time period, the first business module rebinds the UpdateEngine service and establishes a connection.

For example, the first module can delay the second preset time period, rebind the UpdateEngine service, and establish a new connection (such as a second connection) to try to install the target system upgrade installation package next time, that is, re-execute 401. Optionally, the second preset time length may be 3 seconds, 5 seconds, 10 seconds, 15 seconds, etc. In this example, the second preset time is 5 seconds.

It should be noted that the installation status of the upgrade engine service changes according to the installation process. For example, at time T1, the installation status of the upgrade engine service is idle. When the target system upgrade installation package starts to be installed, the installation status of the upgrade engine service is updated. is in busy status. If the upgrade engine service fails or succeeds in installing the target system upgrade installation package, the installation status of the upgrade engine service is updated to the completed status.

The system update application allocates a corresponding connection (i.e., the first connection) to the target system upgrade installation package to be installed this time, and allows the use of the status of the upgrade engine service during the life cycle of this installation, which can avoid the first business interruption. During the period from when the module performs the operation of disconnecting the first connection to when the first connection is disconnected, the first business module uses the received status of the upgrade engine service to cause installation errors and confusion; because the target installation identifier can indicate the current Whether the business module calls the target installation interface in the upgrade engine service. By adding a target installation identifier, the first business module can enrich the information of whether to instruct the upgrade engine service to install the target system upgrade installation package this time, so that the first business module can It can accurately determine whether the installation process of the upgrade engine service is occupied, and promptly install the target system upgrade installation package (such as parameter type, patch type or hota type), thereby avoiding the upgrade engine service from installing parameter type system upgrade installation packages and other types at the same time. Installation conflicts caused by system upgrade installation packages (i.e. patch type system upgrade installation packages or hota type system upgrade installation packages). At the same time, the upgrade engine service promptly installs the target system upgrade installation package (such as a parameter-type system upgrade installation package), which can improve the performance of electronic equipment.

Figure 5 is an exemplary interaction diagram between the OUC and the upgrade engine service. As shown in Figure 5, it includes:

Step 501: The first business module of OUC sends a service request to install the target system upgrade installation package to the upgrade engine service.

Step 502: The first service module binds the AIDL interface and establishes the first connection.

For steps 501 and 502, reference may be made to the relevant description in step 401, which will not be described again here.

Step 503: Upgrade the engine service to obtain the current installation status.

Step 504: The upgrade engine service sends the current installation status of the upgrade engine service to the first business module through the AIDL interface.

Step 505: The first business module determines whether the first identification information indicates the end of the life cycle of this installation. If yes, the process ends, if not, step 506 is executed.

Step 506: The first business module allows the current installation status of the upgrade engine service to be used.

For steps 503 to 506, reference may be made to the relevant descriptions in steps 402 to 404, which will not be described again here.

Step 507: If the first business module detects that the installation state is idle, detect whether the target installation identifier indicates that the first business module has called the target installation interface. If no is detected, step 508 is executed.

Step 508: The first business module updates the target installation identification to indicate that the first business module has called the target installation interface.

Step 509: The first business module instructs the upgrade engine service to install the target system upgrade installation package.

Step 510: The upgrade engine service installs the target system upgrade installation package.

Step 511: The first business module detects that the installation status is busy, and detects whether the time recorded by the timer has timed out. If yes, step 512 is executed; if no, the first business module does not need to perform the operation.

Step 512: The first business module detects whether the target installation identifier indicates that the first business module has called the target installation interface. If yes is detected, step 513 is executed. If no is detected, step 514 is executed.

Step 513: The first business module determines that the installation fails, disconnects the first connection, and updates the first identification information to indicate the end of the life cycle of this installation.

Step 514: The first business module determines the next installation, disconnects the first connection, and updates the first identification information to indicate the end of the life cycle of this installation. After this step, step 518 is performed, that is, the first business module delays for a second preset time period and re-establishes a new connection with the upgrade engine service to try to install the target system upgrade installation package next time.

Step 515: The first business module detects that the installation status is the completion state, and detects whether the target installation identifier indicates that the first business module has called the target installation interface. If yes is detected, step 516 is executed. If no is detected, step 508 is executed.

Step 516: The first business module determines that the installation is completed, disconnects the first connection, and updates the first identification information to indicate the end of the life cycle of this installation.

Step 517: The first business module detects that the installation status is unavailable, disconnects the first connection, and updates the first identification information to indicate the end of the life cycle of this installation. This step is followed by step 518.

Step 518: The first business module delays for a second preset time and establishes a new connection with the upgrade engine service to try to install the target system upgrade installation package next time.

For the above steps 507 to 518, reference can be made to the relevant descriptions in steps 405 to 416, and will not be described again here.

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

This embodiment also provides a computer storage medium that stores computer instructions. When the computer instructions are run on an electronic device, the electronic device causes the electronic device to execute the above related method steps to implement the system upgrade method in the above embodiment. . Storage media include: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code.

This embodiment also provides a computer program product. When the computer program product is run on a computer, it causes the computer to perform the above related steps to implement the system upgrade method in the above embodiment.

Among them, the electronic equipment, computer storage media, computer program products or chips provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the corresponding methods provided above. The beneficial effects of the method will not be repeated here.

Any contents of various embodiments of this application, as well as any contents of the same embodiment, can be freely combined. Any combination of the above is within the scope of this application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above-mentioned specific implementations. The above-mentioned specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art will Inspired by this application, many forms can be made without departing from the purpose of this application and the scope protected by the claims, all of which fall within the protection of this application.

Claims (15)

1. A system upgrade method, characterized by including: The system update application detects the system upgrade instruction and allocates a first connection to the target system upgrade installation package to be installed this time. The first connection is used for communication between the first business module of the system update application and the upgrade engine service; The first business module receives the status of the upgrade engine service sent by the upgrade engine service in real time through the first connection; During the life cycle of this installation, the first business module allows the use of the received status of the upgrade engine service; If the status of the upgrade engine service is an available status, the first business module determines whether to instruct the upgrade engine service to install the target system upgrade package based on the status of the upgrade engine service and the target installation identifier. The state includes idle state and end state. The target installation identifier is used to indicate whether the current business module calls the target installation interface in the upgrade engine service. The target installation interface corresponds to the type of the target system upgrade installation package. The installation interface, the type of the target system upgrade installation package includes: parameter package, hota or patch package, wherein the priority of parameter package installation is the same as the priority of patch package or hota installation; If it is determined that the upgrade engine service is instructed to install the target system upgrade package, an installation instruction is generated and sent to the upgrade engine service; the upgrade engine service responds to the installation instruction and installs the target system upgrade installation package; If the first business module determines that this installation is completed, it marks the end of the life cycle of this installation and disconnects the first connection. 2. The method according to claim 1, characterized in that, within the life cycle of this installation, the first business module allows the use of the status of the received upgrade engine service, including: The first business module obtains first identification information. The first identification information is used to indicate whether the life cycle of this installation is over. The initial first identification information indicates the life cycle of this installation. The cycle is not over; If the first business module detects that the first identification information indicates that the life cycle of this installation has not ended, the first business module allows the use of the status of the upgrade engine service; If the first business module detects that the first identification information indicates that the life cycle of this installation is over, the first business module discards the status of the upgrade engine service. 3. The method according to claim 2, characterized in that the system update application detects the system upgrade instruction and allocates the first connection to the target system upgrade installation package to be installed this time, including: The system update application detects the system upgrade instruction and allocates the first business module to the target system upgrade installation package to be installed this time; The first business module sends a service request to the upgrade engine service, where the service request is used to request the upgrade engine service to install the target system upgrade installation package; In response to the service request, the upgrade engine service binds an interface definition language AIDL interface to the first service module to establish the first connection. 4. The method according to claim 2, characterized in that marking the end of the life cycle of this installation includes: The first business module updates the first identification information to indicate that the life cycle of the current installation has ended. 5. The method according to any one of claims 1 to 4, characterized in that the first business module determines whether to instruct the upgrade engine service to install the target according to the status of the upgrade engine service and the target installation identifier. The target system upgrade package includes: If the first service module detects that the status of the upgrade engine service is idle and detects that the target installation identifier indicates that the first service module has not called the target installation interface, the first service module determines that the instruction indicates The upgrade engine service installs the target system upgrade installation package, and updates the target installation identification to indicate that the first business module has called the target installation interface; wherein the initial target installation identification indicates that the first business module has not Call the target installation interface. 6. The method according to claim 5, characterized in that, the method further comprises: In response to the installation instruction, the upgrade engine service updates the status of the upgrade engine service to a busy status. 7. The method according to any one of claims 1-4, characterized in that the method further includes: If the first business module detects that the status of the upgrade engine service is a busy state, it detects whether the establishment time of the first connection has exceeded the preset time; If it is detected that the preset time period has exceeded, detect whether the target installation identifier indicates that the first business module has called the target installation interface; If no is detected, the first service module determines to install the target system upgrade installation package next time. 8. The method according to claim 7, characterized in that the method further comprises: If the first business module determines that the target system upgrade installation package will be installed next time, it determines that this installation is completed; After marking the end of the life cycle of this installation and disconnecting the first connection, the method further includes: After the first business module disconnects the first connection for a second preset period of time, the system update application re-allocates a second connection to the target system upgrade installation package to be installed this time to re-install the target. System upgrade installation package. 9. The method according to claim 7, characterized in that, the method further comprises: If the first business module detects that the target installation identifier indicates that the first business module has called the target installation interface, the first business module determines that the installation of the target system upgrade installation package failed this time, and marks The life cycle of this installation ends and the first connection is disconnected. 10. The method according to any one of claims 1 to 4, characterized in that the first business module determines whether to instruct the upgrade engine service to install the target according to the status of the upgrade engine service and the target installation identifier. The target system upgrade package includes: If the detected state of the first business module is the end state and the detection of the target installation identifier indicates that the first business module has not called the target installation interface, the first business module determines to instruct the upgrade engine The service installs the target system upgrade installation package, and updates the target installation identification to indicate that the first business module has called the target installation interface; wherein the initial target installation identification indicates that the first business module has not called the Target installation interface. 11. The method according to claim 10, characterized in that the method further comprises: If the detected state of the first business module is the end state and the detection of the target installation identifier indicates that the first business module has called the target installation interface, the first business module determines that the successful installation this time The above target system upgrade installation package; Mark the end of the life cycle of this installation and disconnect the first connection. 12. The method of claim 1, further comprising: If the first business module detects that the status of the upgrade engine service is unavailable, it marks the end of the life cycle of this installation and disconnects the first connection; After the first business module disconnects the first connection for a second preset period of time, the system update application re-allocates a second connection to the target system upgrade installation package to be installed this time to re-install the target. System upgrade installation package. 13. The method according to claim 1, characterized in that, before the system update application detects the system upgrade instruction and allocates the first connection to the target system upgrade installation package to be installed this time, the method further includes: The system update application receives a system upgrade instruction input by the user to install the target system upgrade installation package; or, The system update application detects that the electronic device is in a screen-off state, and generates a system upgrade instruction for installing the target system upgrade installation package. 14. An electronic device, characterized in that it includes: a memory and a processor, the memory coupled to the processor; The memory stores program instructions that, when executed by the processor, cause the electronic device to perform the system upgrade method described in any one of claims 1 to 13. 15. A computer-readable storage medium, comprising a computer program, characterized in that, when the computer program is run on an electronic device, it causes the electronic device to perform the system upgrade described in any one of claims 1 to 13 Methods.