Mobile terminal upgrading method and device, mobile terminal, storage medium and product

Abstract

The invention provides a mobile terminal upgrading method and device, a mobile terminal, a storage medium and a product, and belongs to the technical field of cloud channels. Comprising the steps that based on an OTA client side on the mobile terminal, an upgrade package set sent by an OTA server is received, the upgrade package set comprises first upgrade packages of multiple to-be-upgraded components in the mobile terminal, and the first upgrade packages of the multiple to-be-upgraded components are synchronized to the OTA server by a component total server; on the basis of the first upgrade packages of the multiple to-be-upgraded components, upgrade clients corresponding to the first upgrade packages of the multiple to-be-upgraded components are determined in the mobile terminal; and based on the first upgrade packages of the plurality of to-be-upgraded components, respectively carrying out upgrade operation through the plurality of determined upgrade clients. According to the method, the OTA server can package a plurality of to-be-upgraded first upgrade packages together and issue the first upgrade packages to the OTA client, and the OTA client issues the first upgrade packages at one time, so that the power consumption of the mobile terminal can be reduced, and the performance can be improved.

Description

Technical Field

[0001] This application relates to the technical field of cloud channels, and particularly to a method and device for upgrading a mobile terminal, a mobile terminal, a storage medium, and a product. Background Art

[0002] Since the Over The Air (OTA) technology can remotely manage mobile terminals through the air interface of mobile communications without connecting to the cloud server via a wire; therefore, more and more mobile terminals are based on the OTA technology to achieve system upgrades of mobile terminals. The process can be as follows: An OTA client is installed on the mobile terminal, and the mobile terminal obtains the first OTA upgrade package from the OTA server based on the OTA client, and performs an upgrade operation on the system of the mobile terminal based on the first OTA upgrade package. In addition, applications are also installed on the mobile terminal. When the functions of the applications are updated or the functions of the application plugins in the applications are updated, upgrade operations need to be performed on the applications or the plugins in the applications. Summary of the Invention

[0003] Embodiments of this application provide a method and device for upgrading a mobile terminal, a mobile terminal, a storage medium, and a product, which can reduce the power consumption of the mobile terminal and improve the performance of the mobile terminal. The technical solutions are as follows:

[0004] On the one hand, a method for upgrading a mobile terminal is provided. The method includes:

[0005] Based on the Over The Air (OTA) client on the mobile terminal, receive an upgrade package set sent by the OTA server. The upgrade package set includes the first upgrade packages of multiple components to be upgraded in the mobile terminal, and the first upgrade packages of the multiple components to be upgraded are synchronized from the component master server to the OTA server;

[0006] Based on the first upgrade packages of the multiple components to be upgraded, determine the upgrade clients corresponding to the first upgrade packages of the multiple components to be upgraded in the mobile terminal;

[0007] Based on the first upgrade packages of the multiple components to be upgraded, perform upgrade operations respectively through the determined multiple upgrade clients.

[0008] On the other hand, a device for upgrading a mobile terminal is provided. The device includes:

[0009] A receiving module, configured to receive, based on the Over The Air (OTA) client on the mobile terminal, an upgrade package set sent by the OTA server. The upgrade package set includes the first upgrade packages of multiple components to be upgraded in the mobile terminal, and the first upgrade packages of the multiple components to be upgraded are synchronized from the component master server to the OTA server;

[0010] A first determination module, configured to determine, in the mobile terminal, an upgrade client corresponding to a first upgrade package of the multiple components to be upgraded based on the first upgrade package of the multiple components to be upgraded;

[0011] A first upgrade module, configured to perform upgrade operations respectively through the determined multiple upgrade clients based on the first upgrade package of the multiple components to be upgraded.

[0012] On the other hand, a mobile terminal is provided. The mobile terminal includes a processor and a memory. At least one program code is stored in the memory and is loaded and executed by the processor to implement the mobile terminal upgrade method described above.

[0013] On the other hand, a computer-readable storage medium is provided. At least one program code is stored in the storage medium and is loaded and executed by a processor to implement the mobile terminal upgrade method described above.

[0014] On the other hand, a computer program product is provided. The computer program product stores at least one program code, and the at least one program code is used to be executed by a processor to implement the mobile terminal upgrade method described above.

[0015] In an embodiment of the present application, the OTA server can package multiple first upgrade packages to be upgraded together and send them to the OTA client for one-time sending. Compared with sending each first upgrade package separately, it can reduce the power consumption of the mobile terminal and improve the performance of the mobile terminal. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 A schematic diagram showing an implementation environment of a mobile terminal upgrade method shown in an exemplary embodiment of the present application;

[0017] Figure 2 A flowchart showing a mobile terminal upgrade method shown in an exemplary embodiment of the present application;

[0018] Figure 3 A flowchart showing a mobile terminal upgrade method shown in an exemplary embodiment of the present application;

[0019] Figure 4 A flowchart showing a mobile terminal upgrade method shown in an exemplary embodiment of the present application;

[0020] Figure 5 A flowchart showing a mobile terminal upgrade method shown in an exemplary embodiment of the present application;

[0021] Figure 6The flowchart of the mobile terminal upgrade method shown in an exemplary embodiment of the present application is shown;

[0022] Figure 7 The block diagram of the mobile terminal upgrade device shown in an exemplary embodiment of the present application is shown;

[0023] Figure 8 The block diagram of the mobile terminal shown in an exemplary embodiment of the present application is shown. Detailed implementation manners

[0024] To make the objectives, technical solutions, and advantages of the present application clearer, the following will further describe the embodiments of the present application in detail with reference to the accompanying drawings.

[0025] As used herein, "a plurality of" means two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after.

[0026] It should be noted that the information (including but not limited to user device information, user personal information, etc.), data (including but not limited to data for analysis, stored data, displayed data, etc.), and signals involved in the present application are all authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with the relevant laws, regulations, and standards of relevant countries and regions. For example, the upgrade package set, version identifier of the OTA client, second upgrade package, and upgrade operation involved in the present application are all obtained under full authorization.

[0027] Please refer to Figure 1 , which shows a schematic diagram of the implementation environment of the mobile terminal upgrade method shown in an exemplary embodiment of the present application. Refer to Figure 1 , this implementation environment includes: a mobile terminal and a cloud server; the mobile terminal includes an OTA client and an upgrade client, the OTA client is a client for upgrading the operating system of the mobile terminal, and the upgrade client is a client for the component to be upgraded; for example, the upgrade client includes at least two of a Special Administration Unit (SAU) client of the intelligent network, an Operational Expenditure (OPEX) client, and a plugin client; in the embodiments of the present application, an example will be given with the upgrade client including three clients: an SAU client, an OPEX client, and a plugin client.

[0028] The cloud server includes an OTA server and a component master server; the OTA server is the backend server for the OTA client; the component master server is the integration of the backend servers corresponding to multiple upgrade clients. In some scenarios, the component master server can also be referred to as a shelf server. For example, if the multiple upgrade clients include an SAU client, an OPEX client, and a plugin client, then the component master server is the integration of the backend servers corresponding to the SAU client, the OPEX client, and the plugin client respectively. That is, the component master server can provide the application upgrade package corresponding to the SAU client, the mainline upgrade package corresponding to the OPEX client, and the application plugin upgrade package corresponding to the plugin client.

[0029] In some embodiments, the cloud server further includes multiple upgrade servers corresponding to multiple upgrade clients. The multiple upgrade servers are module servers split from the component master server (or referred to as the shelf server). For example, if the multiple upgrade clients include an SAU client, an OPEX client, and a plugin client, then the cloud server further includes an SAU server, an OPEX server, and a plugin server; the SAU server is used to provide the application upgrade package for the SAU client, the OPEX server is used to provide the mainline upgrade package for the OPEX client, and the SAU client is used to provide the application plugin upgrade package for the plugin server.

[0030] In some embodiments, for any upgrade server, the upgrade package provided by the upgrade server for the upgrade client is the same as the upgrade package provided by the component master server for the upgrade client; for example, if the upgrade client is an SAU client and the upgrade server is an SAU server, then the SAU server provides the application upgrade package for the first function for the SAU client, and the component master server also provides the application upgrade package for the first function for the SAU client. In this way, the component master server periodically obtains the latest upgrade packages of multiple upgrade clients, and then through the OTA server, synchronizes the upgrade packages of multiple upgrade clients to the OTA client at one time, and the OTA client notifies each upgrade client to download and install; and when the upgrade client needs to be upgraded at other times, it can obtain the upgrade package from the upgrade server corresponding to the upgrade client and perform the upgrade operation based on the upgrade package.

[0031] In some other embodiments, for any upgrade server, the upgrade package provided by the upgrade server for the upgrade client is different from the upgrade package provided by the component master server for the upgrade client. For example, if the upgrade client is an SAU client and the upgrade server is an SAU server, the component master server provides an application upgrade package for the first function for the SAU client, while the SAU server provides an application upgrade package for the second function for the SAU client. The priority level of the first function is higher than that of the second function. That is, the component master server provides application upgrade packages for those functions that are more important (or have a higher user perception), such as upgrade packages for functions with relatively serious defects; while the SAU server provides application upgrade packages for those functions that are less important (or have a lower user perception); for example, defect fix versions or requirements with insignificant user perception, etc.

[0032] In some other embodiments, for any upgrade server, the upgrade package provided by the upgrade server for the upgrade client is partially the same as the upgrade package provided by the component server for the upgrade client. For example, if the upgrade client is an SAU client and the upgrade server is an SAU server, the component master server provides an application upgrade package for the first function for the SAU client, while the SAU server provides an application upgrade package for the first function and an application upgrade package for the second function for the SAU client. The priority level of the first function is higher than that of the second function. That is, the component master server provides application upgrade packages for those functions that are more important (or have a higher user perception), such as upgrade packages for functions with relatively serious defects; while the SAU server provides application upgrade packages for those functions that are less important (or have a lower user perception); for example, defect fix versions or requirements with insignificant user perception, etc.

[0033] In some embodiments, the mobile terminal may be a smart phone, a tablet computer, or a smart wearable device, etc., but is not limited thereto. The OTA client may be a COTA client, the corresponding OTA server may be a COTA server, and the OTA upgrade package may be a COTA upgrade package. COTA refers to the over-the-air download technology customized for enterprises.

[0034] Please refer to Figure 2 , which shows a flowchart of a mobile terminal upgrade method shown in an exemplary embodiment of the present application. The execution subject of the embodiment of the present application may be a mobile terminal. Refer to Figure 2 , the method includes:

[0035] Step 201: Based on the OTA client on the mobile terminal, receive the upgrade package set sent by the OTA server. The upgrade package set includes the first upgrade packages of multiple components to be upgraded in the mobile terminal, and the first upgrade packages of the multiple components to be upgraded are synchronized by the component master server to the OTA server.

[0036] The OTA client receives the upgrade package set sent by the OTA server through the cloud channel between the OTA client and the OTA server. The upgrade package set includes the first upgrade packages of multiple upgrade components. The multiple components to be upgraded include at least two of applications, mainline, and plugins. Correspondingly, the upgrade package set includes at least two of the first upgrade package of the application, the first upgrade package of the mainline, and the first upgrade package of the plugin. In the embodiments of the present application, an example is given with multiple components to be upgraded including three components: applications, mainline, and plugins. Correspondingly, the upgrade package set includes the first upgrade package of the application, the first upgrade package of the mainline, and the first upgrade package of the plugin.

[0037] Developers set the first upgrade packages of multiple components to be upgraded in the component master server. The first upgrade packages of the multiple components to be upgraded can be set simultaneously or at different times. After the component master server receives the set first upgrade packages of the components to be upgraded, it sets the status of the first upgrade package of the component to be upgraded to the unsynchronized state. In some embodiments, the component master server actively triggers the upgrade operation every preset upgrade cycle. Correspondingly, the process can be as follows: The component master server obtains the first upgrade packages of multiple components to be upgraded that are set and in the unsynchronized state within the current preset upgrade cycle every preset upgrade cycle, and synchronizes the first upgrade packages of the multiple components to be upgraded to the OTA server. The OTA server receives the first upgrade packages of the multiple components to be upgraded, packages the first upgrade packages of the multiple components to be upgraded into an upgrade package set, and sends the upgrade package set to the OTA client of the mobile terminal. The mobile terminal receives the upgrade package set sent by the OTA server based on the OTA client on the mobile terminal.

[0038] In some other embodiments, the OTA client actively triggers an upgrade operation every preset upgrade cycle; correspondingly, the process may be as follows: the OTA client of the mobile terminal sends a first upgrade request to the OTA server every preset upgrade cycle. The OTA server receives the first upgrade request sent by the OTA client and forwards the first upgrade request to the component general server. The component general server receives the first upgrade request forwarded by the OTA server, obtains the first upgrade packages of multiple to-be-upgraded components that are set and in an unsynchronized state within the current preset upgrade cycle, and sends the first upgrade packages of the multiple to-be-upgraded components to the OTA server; the OTA server receives the first upgrade packages of the multiple to-be-upgraded components, packs the first upgrade packages of the multiple to-be-upgraded components into an upgrade package set, and sends the upgrade package set to the OTA client of the mobile terminal; the mobile terminal receives the upgrade package set sent by the OTA server based on the OTA client on the mobile terminal.

[0039] In some other embodiments, the user can manually trigger an upgrade operation through the OTA client; correspondingly, the process may be as follows: the OTA client receives an upgrade instruction triggered by the user, and based on the upgrade instruction, sends a second upgrade request to the OTA server. The OTA server receives the second upgrade request sent by the OTA client and forwards the second upgrade request to the component general server. The component general server receives the second upgrade request forwarded by the OTA server, obtains the first upgrade packages of multiple to-be-upgraded components that are set and in an unsynchronized state within the current preset upgrade cycle, and sends the first upgrade packages of the multiple to-be-upgraded components to the OTA server; the OTA server receives the first upgrade packages of the multiple to-be-upgraded components, packs the first upgrade packages of the multiple to-be-upgraded components into an upgrade package set, and sends the upgrade package set to the OTA client of the mobile terminal; the mobile terminal receives the upgrade package set sent by the OTA server based on the OTA client on the mobile terminal.

[0040] Step 202: Based on the first upgrade packages of the multiple to-be-upgraded components, determine the upgrade clients corresponding to the first upgrade packages of the multiple to-be-upgraded components in the mobile terminal.

[0041] For any first upgrade package of a to-be-upgraded component included in the upgrade package set, the mobile terminal obtains the attribution information of the first upgrade package from the first upgrade package; based on the attribution information of the first upgrade package, determine the upgrade client corresponding to the first upgrade package in the mobile terminal. For example, the attribution information of the first upgrade package includes the identification information of the upgrade client to which the first upgrade package belongs.

[0042] For example, if multiple components to be upgraded include the first upgrade package of an application, the first upgrade package of mainline, and the first upgrade package of a plugin, the mobile terminal determines, based on the first upgrade package of the application, the first upgrade package of mainline, and the first upgrade package of the plugin, that the multiple upgrade clients in the mobile terminal are respectively an SAU client, an OPEX client, and a plugin client.

[0043] Step 203: Based on the first upgrade packages of the multiple components to be upgraded, perform upgrade operations respectively through the determined multiple upgrade clients.

[0044] For the first upgrade package of any component to be upgraded included in the upgrade package set, send the first upgrade package to the upgrade client corresponding to the first upgrade package of the component to be upgraded, so that the upgrade client performs an upgrade operation based on the first upgrade package. This process can be that the mobile terminal, based on the OTA client, sends the first upgrade package to the upgrade client corresponding to the first upgrade package of the component to be upgraded; the upgrade client receives the first upgrade package of the component to be upgraded and performs an upgrade operation based on the first upgrade package, thereby enabling the OTA server to implement the OTA download service and perform overall download control.

[0045] In some embodiments, the OTA client directly sends the first upgrade package to the upgrade client corresponding to the first upgrade package of the component to be upgraded; in other embodiments, the OTA client sends a notification message to the upgrade client corresponding to the first upgrade package of the component to be upgraded, and the notification message is used to notify the upgrade client to pull the first upgrade package of the component to be upgraded from the OTA client; the upgrade client receives the notification message and pulls the first upgrade package of the component to be upgraded from the OTA client based on the notification message. Among them, the upgrade client can pull the first upgrade package of the component to be upgraded from the OTA client when receiving the notification message and then perform an upgrade operation, thereby improving the upgrade efficiency. The upgrade client can also pull the first upgrade package of the upgrade component from the OTA client only when the mobile terminal is in a target state, and the target state is a state that meets the resources required for the upgrade; for example, the target state is a state where the remaining battery level is greater than a preset battery level and the currently connected network is a Wireless Fidelity (WiFi) network, so as to ensure the success of the upgrade.

[0046] For example, if multiple components to be upgraded include the first upgrade package of an application, the first upgrade package of mainline, and the first upgrade package of a plugin, and the multiple upgrade clients are respectively an SAU client, an OPEX client, and a plugin client, then the mobile terminal upgrades the application through the SAU client based on the first upgrade package of the application, upgrades mainline through the OPEX client based on the first upgrade package of mainline, and upgrades the plugin through the plugin client based on the first upgrade package of the plugin.

[0047] In an embodiment of the present application, the OTA server can package the first upgrade packages of multiple components to be upgraded together and send them to the OTA client for a one-time distribution. Compared with the individual distribution of each first upgrade package, it can reduce the power consumption of the mobile terminal and improve the performance of the mobile terminal.

[0048] In the related art, when there are multiple upgrade clients, multiple upgrade clients need to make multiple network requests to complete the upgrade of multiple components to be upgraded. There are many network requests, which not only increases the power consumption of the mobile terminal but also increases the load on the server. In the embodiment of the present application, the OTA server packages the first upgrade packages of multiple components to be upgraded together and sends them to the OTA client, thus saving the number of network requests, which can not only reduce the power consumption of the mobile terminal but also reduce the load on the server.

[0049] Moreover, in the related art, multiple upgrade clients respectively request their corresponding upgrade servers to pull the corresponding first upgrade packages. Due to reasons such as traffic restrictions or network anomalies, it cannot be guaranteed that all network requests can succeed, resulting in the possibility that the multiple first upgrade packages obtained may be incomplete, and it may be necessary to perform multiple upgrades to obtain all the upgrade packages of multiple components to be upgraded. In the embodiment of the present application, all the upgrade packages of multiple first components to be upgraded can be obtained through only one upgrade, improving the reliability of the upgrade.

[0050] Moreover, in the related art, when the user manually triggers an upgrade, since multiple upgrades may require the user to manually trigger the upgrade separately, the response time of the upgrade becomes longer, reducing the user experience. In the embodiment of the present application, the user only needs to trigger an upgrade once to complete the upgrade of multiple components to be upgraded, reducing the response time of the upgrade and improving the user experience.

[0051] Please refer to Figure 3 , which shows a flowchart of a mobile terminal upgrade method shown in an exemplary embodiment of the present application. Refer to Figure 3 , the method includes:

[0052] Step 301: The component master server synchronizes the first upgrade packages of multiple components to be upgraded to the OTA server.

[0053] The developer sets the first upgrade packages of multiple components to be upgraded in the component master server. The first upgrade packages of multiple components to be upgraded can be set simultaneously or at different times; after the component master server receives the set first upgrade packages of the components to be upgraded, it sets the status of the first upgrade packages of the components to be upgraded to the unsynchronized state.

[0054] In some embodiments, the component master server obtains the first upgrade packages of multiple components to be upgraded that are set and in an unsynchronized state during the current preset upgrade cycle every preset upgrade cycle, and synchronizes the first upgrade packages of the multiple components to be upgraded to the OTA server. In some other embodiments, the OTA client of the mobile terminal sends a first upgrade request to the OTA server every preset upgrade cycle. The OTA server receives the first upgrade request sent by the OTA client, forwards the first upgrade request to the component master server. The component master server receives the first upgrade request forwarded by the OTA server, obtains the first upgrade packages of multiple components to be upgraded that are set and in an unsynchronized state during the current preset upgrade cycle, and sends the first upgrade packages of the multiple components to be upgraded to the OTA server. In some other embodiments, the user can manually trigger an upgrade operation through the OTA client; correspondingly, the process can be: the OTA client receives the upgrade instruction triggered by the user, and based on the upgrade instruction, sends a second upgrade request to the OTA server. The OTA server receives the second upgrade request sent by the OTA client, forwards the second upgrade request to the component master server. The component master server receives the second upgrade request forwarded by the OTA server, obtains the first upgrade packages of multiple components to be upgraded that are set and in an unsynchronized state during the current preset upgrade cycle, and sends the first upgrade packages of the multiple components to be upgraded to the OTA server.

[0055] Step 302: The OTA server packages the first upgrade packages of the multiple components to be upgraded into an upgrade package set.

[0056] Step 303: The OTA server sends the upgrade package set to the OTA client.

[0057] The OTA server sends the upgrade package set to the OTA client through the cloud channel between the OTA client and the OTA server.

[0058] Step 304: The OTA client receives the upgrade package set sent by the OTA server. The upgrade package set includes the first upgrade package of the application, the first upgrade package of the mainline, and the first upgrade package of the application plug-in.

[0059] The OTA client receives the upgrade package set sent by the OTA server through the cloud channel between the OTA client and the OTA server.

[0060] Step 305: The OTA client determines the SAU client, the OPEX client, and the plug-in client based on the first upgrade package of the application, the first upgrade package of the mainline, and the first upgrade package of the application plug-in.

[0061] In some embodiments, the execution order of steps 306 - 308 in the embodiments of the present application is not specifically limited; it may be executed in the order of steps 306 - 307 - 308, or in the order of steps 306 - 308 - 307, or in the order of steps 307 - 308 - 306, or in the order of steps 307 - 306 - 308, or in the order of steps 308 - 307 - 306, or in the order of steps 308 - 306 - 307. In other embodiments, steps 306 - 308 may be performed simultaneously.

[0062] Step 306: The OTA client sends the first upgrade package of the application to the SAU client, so that the SAU client upgrades the application based on the first upgrade package of the application.

[0063] The SAU client receives the first upgrade package of the application sent by the OTA client and upgrades the application based on the first upgrade package of the application. In some embodiments, the OTA client directly sends the first upgrade package of the application to the SAU client; in other embodiments, the OTA client sends a notification message to the SAU client, and the notification message is used to notify the SAU client to pull the first upgrade package of the application from the OTA client; the SAU client receives the notification message and pulls the first upgrade package of the application from the OTA client based on the notification message. Among them, the SAU client may pull the first upgrade package of the application from the OTA client when receiving the notification message and then perform the upgrade operation, thereby improving the upgrade efficiency. The upgrade client may also pull the first upgrade package of the application from the OTA client only when the mobile terminal is in the target state, and the target state is the state that meets the resources required for the upgrade; for example, the target state is the state where the remaining battery power value is greater than the preset power value and the currently connected network is a WiFi network, so as to ensure the success of the upgrade.

[0064] Step 307: The OTA client sends the first upgrade package of the mainline to the OPEX client, so that the OPEX client upgrades the mainline based on the first upgrade package of the mainline.

[0065] The OPEX client receives the first upgrade package of the mainline sent by the OTA client and performs a mainline upgrade based on the first upgrade package of the mainline. In some embodiments, the OTA client directly sends the first upgrade package of the mainline to the OPEX client; in other embodiments, the OTA client sends a notification message to the OPEX client, and the notification message is used to notify the OPEX client to pull the first upgrade package of the mainline from the OTA client; the OPEX client receives the notification message and pulls the first upgrade package of the mainline from the OTA client based on the notification message. Among them, the OPEX client can pull the first upgrade package of the mainline from the OTA client when receiving the notification message, and then perform an upgrade operation, thereby improving the upgrade efficiency. The upgrade client can also pull the first upgrade package of the mainline from the OTA client only when the mobile terminal is in a target state, and the target state is a state that meets the resources required for the upgrade; for example, the target state is a state where the remaining battery level is greater than a preset battery level and the currently connected network is a WiFi network, so as to ensure the success of the upgrade.

[0066] Step 308: The OTA client sends the first upgrade package of the application plug-in to the plug-in client, so that the plug-in client performs a plug-in upgrade based on the first upgrade package of the application plug-in.

[0067] The plug-in client receives the first upgrade package of the application plug-in sent by the OTA client and performs a plug-in upgrade based on the first upgrade package of the application plug-in. In some embodiments, the OTA client directly sends the first upgrade package of the application plug-in to the application plug-in client; in other embodiments, the OTA client sends a notification message to the application plug-in client, and the notification message is used to notify the application plug-in client to pull the first upgrade package of the application plug-in from the OTA client; the application plug-in client receives the notification message and pulls the first upgrade package of the application plug-in from the OTA client based on the notification message. Among them, the application plug-in client can pull the first upgrade package of the application plug-in from the OTA client when receiving the notification message, and then perform an upgrade operation, thereby improving the upgrade efficiency. The upgrade client can also pull the first upgrade package of the application plug-in from the OTA client only when the mobile terminal is in a target state, and the target state is a state that meets the resources required for the upgrade; for example, the target state is a state where the remaining battery level is greater than a preset battery level and the currently connected network is a WiFi network, so as to ensure the success of the upgrade.

[0068] In the embodiments of the present application, the OTA server may package the first upgrade package of the application, the mainline upgrade package, and the first upgrade package of the application plug-in together and send them to the OTA client for one-time distribution. Compared with the individual distribution of each first upgrade package, it can reduce the power consumption of the mobile terminal and improve the performance of the mobile terminal.

[0069] Please refer to Figure 4 , which shows the flowchart of the mobile terminal upgrade method shown in an exemplary embodiment of the present application. Refer to Figure 4 , the method includes:

[0070] Step 401: The component general server synchronizes the first upgrade packages of multiple components to be upgraded to the OTA server.

[0071] In some embodiments, this step is the same as step 301 and will not be elaborated here.

[0072] Step 402: The OTA server packages the first upgrade packages of multiple components to be upgraded and the first OTA upgrade package into an upgrade package set.

[0073] The OTA server obtains the first OTA upgrade package of the OTA client and packages the first upgrade packages of multiple components to be upgraded and the first OTA upgrade package into an upgrade package set. In some embodiments, before the OTA server obtains the first OTA upgrade package of the OTA client, it first determines the version identifier of the OTA client. If the version identifier of the OTA client is used to indicate that the OTA client is not the latest version, the first OTA upgrade package of the OTA client is obtained. If the version identifier of the OTA client is used to indicate that the OTA client is the latest version, the first OTA upgrade package of the OTA client is not obtained. At this time, the execution process can refer to steps 201-203 or can refer to steps 301-308.

[0074] Step 403: The OTA server sends the upgrade package set to the OTA client.

[0075] In some embodiments, this step is the same as step 303 and will not be elaborated here.

[0076] Step 404: The OTA client receives the upgrade package set sent by the OTA server. The upgrade package set includes the first upgrade package of the application, the first upgrade package of the mainline, the first upgrade package of the application plug-in, and the first OTA upgrade package.

[0077] Before OTA receives the upgrade package set sent by the OTA server, it also judges the OTA client version. Only when the OTA client is not the latest version, it receives the upgrade package set sent by the OTA server. The process can be: the OTA client determines the version identifier of the OTA client; when the version identifier of the OTA client is used to identify that the OTA client is not the latest version, execute the step of receiving the upgrade package set sent by the OTA server based on the OTA client on the mobile terminal, thereby realizing double verification of the OTA client version and improving the reliability of the upgrade.

[0078] In some embodiments, when the version identifier of the OTA client is used to identify that the OTA client is the latest version, the OTA client does not receive the upgrade package set sent by the OTA server, or after receiving the upgrade package set sent by the OTA server, does not execute steps 405-409 but discards the upgrade package set.

[0079] In other embodiments, when the OTA server upgrades the OTA client, that is, when the OTA server sends the second OTA upgrade package to the OTA client, it will also send the fourth upgrade package of multiple components to be upgraded in the component main server; and the OTA client receives the second OTA upgrade package and the fourth upgrade package of multiple components to be upgraded, and upgrades the operating system of the mobile terminal based on the second OTA upgrade package, and based on the fourth upgrade package of multiple components to be upgraded, determines in the mobile terminal the upgrade clients corresponding to the fourth upgrade packages of multiple components to be upgraded through the fourth upgrade packages of multiple components to be upgraded, and based on the fourth upgrade package of multiple components to be upgraded, performs upgrade operations respectively through the determined multiple upgrade clients. This process is similar to the process in which the mobile terminal determines in the mobile terminal based on the first upgrade package of multiple components to be upgraded, through the first upgrade package of multiple components to be upgraded, the upgrade clients corresponding to the first upgrade packages of multiple components to be upgraded, and based on the first upgrade package of multiple components to be upgraded, performs upgrade operations respectively through the determined multiple upgrade clients, and will not be repeated here.

[0080] Step 405: The OTA client performs an upgrade operation on the operating system of the mobile terminal based on the first OTA upgrade package.

[0081] Step 406: The OTA client determines the SAU client, the OPEX client, and the plug-in client based on the first upgrade package of the application, the first upgrade package of the mainline, and the first upgrade package of the application plug-in.

[0082] In some embodiments, this step is the same as step 305 and will not be repeated here.

[0083] Step 407: The OTA client sends the first upgrade package of the application to the SAU client, so that the SAU client upgrades the application based on the first upgrade package of the application.

[0084] In some embodiments, this step is the same as step 306 and will not be elaborated here.

[0085] Step 408: The OTA client sends the first upgrade package of the mainline to the OPEX client, so that the OPEX client upgrades the mainline based on the first upgrade package of the mainline.

[0086] In some embodiments, this step is the same as step 307 and will not be elaborated here.

[0087] Step 409: The OTA client sends the first upgrade package of the application plug-in to the plug-in client, so that the plug-in client upgrades the plug-in based on the first upgrade package of the application plug-in.

[0088] In some embodiments, this step is the same as step 308 and will not be elaborated here.

[0089] In the embodiments of the present application, the OTA client and the first upgrade packages of multiple components to be upgraded can be upgraded simultaneously, which not only improves the upgrade efficiency but also avoids disturbing the user repeatedly.

[0090] Please refer to Figure 5 , which shows the flowchart of the mobile terminal upgrade method shown in an exemplary embodiment of the present application. Refer to Figure 5 , the method includes:

[0091] Step 501: The mobile terminal, based on the OTA client on the mobile terminal, receives the upgrade package set sent by the OTA server. The upgrade package set includes the first upgrade packages of multiple components to be upgraded in the mobile terminal, and the first upgrade packages of the multiple components to be upgraded are synchronized to the OTA server by the component total server.

[0092] In some embodiments, this step is the same as step 201; alternatively, this step can be implemented through 301-304 and will not be elaborated here.

[0093] Step 502: The mobile terminal determines the upgrade clients corresponding to the first upgrade packages of the multiple components to be upgraded in the mobile terminal based on the first upgrade packages of the multiple components to be upgraded.

[0094] In some embodiments, this step is the same as step 202; alternatively, this step can be implemented through 305 and will not be elaborated here.

[0095] Step 503: The mobile terminal performs upgrade operations respectively through the determined multiple upgrade clients based on the first upgrade packages of the multiple components to be upgraded.

[0096] In some embodiments, this step is the same as step 203; alternatively, this step can be implemented through 306 - 308, which will not be elaborated here.

[0097] Step 504: For any first upgrade package, the first upgrade package is the upgrade package for the first function of the upgrade client corresponding to the first upgrade package; the mobile terminal receives, based on the upgrade client, a second upgrade package sent by the upgrade server corresponding to the upgrade client, where the second upgrade package is the upgrade package for the second function of the upgrade client, and the priority level of the second function is lower than that of the first function.

[0098] For any upgrade client, when a developer sets the upgrade package for the second function of the upgrade client in the component total server, that is, for the second upgrade, the component total server sends the second upgrade package to the upgrade server corresponding to the upgrade client. The upgrade server receives the second upgrade package and sends the second upgrade package to the upgrade client, and the upgrade client receives the second upgrade package sent by the upgrade server, thereby enabling the mobile terminal to receive, based on the upgrade client, the second upgrade package sent by the upgrade server corresponding to the upgrade client.

[0099] In some embodiments, after the component total server receives the second upgrade package, it sends the second upgrade package to the upgrade client, thereby improving the upgrade of the second function of the upgrade client; in other embodiments, after the component total server receives the second upgrade package, it stores the second upgrade package and sets the status of the second upgrade package to the un-upgraded state. When the upgrade server receives a third upgrade request sent by the upgrade client, it sends the second upgrade package to the upgrade client; and the third upgrade request is sent by the upgrade client when it receives a user-triggered upgrade instruction, or the third upgrade request is sent by the upgrade client when it is in a target state, where the target state is a state that meets the resources required for the upgrade; for example, the target state is a state where the remaining battery level is greater than a preset battery level and the currently connected network is a WiFi network, so as to ensure the success of the upgrade.

[0100] Step 505: The mobile terminal performs an upgrade operation for the second function based on the second upgrade package through the upgrade client.

[0101] For example, if the client is upgraded to an SAU client, the SAU client can upgrade the second function of the application based on the SAU server. Another example is that if the client is upgraded to an OPEX client, the OPEX client can upgrade the second function of the mainline based on the OPEX server. Still another example is that if the client is upgraded to an application plug-in client, the application plug-in client can upgrade the second function of the application plug-in based on the application plug-in server.

[0102] In the embodiment of the present application, the OTA server can package the first upgrade packages of the first functions with higher priorities of multiple components to be upgraded together and send them to the OTA client for one-time distribution, thereby reducing the power consumption of the mobile terminal and improving the performance of the mobile terminal. And the second upgrade packages of the second functions with lower priorities are separately sent through the upgrade servers corresponding to the upgrade clients, so as to realize the separate upgrade of the second upgrade packages of the second functions with less obvious user perception requirements.

[0103] Please refer to Figure 6 , which shows a flowchart of a mobile terminal upgrade method shown in an exemplary embodiment of the present application. Refer to Figure 6 , the method includes:

[0104] Step 601: Based on the OTA client on the mobile terminal, the mobile terminal receives, in each preset upgrade cycle, an upgrade package set sent by the OTA server. The upgrade package set includes the first upgrade packages of multiple components to be upgraded in the mobile terminal, and the first upgrade packages of the multiple components to be upgraded are synchronized from the component total server to the OTA server.

[0105] The OTA client receives the upgrade package set sent by the OTA server through the cloud channel between the OTA client and the OTA server. The upgrade package set includes the first upgrade packages of multiple upgrade package components. The multiple components to be upgraded include at least two of an application, a mainline, and a plug-in. Correspondingly, the upgrade package set includes at least two of the first upgrade package of the application, the first upgrade package of the mainline, and the first upgrade package of the plug-in. In the embodiment of the present application, an example in which the multiple components to be upgraded include an application, a mainline, and a plug-in is used for illustration. Correspondingly, the upgrade package set includes the first upgrade package of the application, the first upgrade package of the mainline, and the first upgrade package of the plug-in.

[0106] Developers set the first upgrade packages of multiple components to be upgraded in the component master server. The first upgrade packages of multiple components to be upgraded can be set simultaneously or at different times. After receiving the set first upgrade packages of the components to be upgraded, the component master server sets the status of the first upgrade packages of the components to be upgraded to unsynchronized status. In some embodiments, the component master server actively triggers an upgrade operation every preset upgrade cycle. Correspondingly, this process can be: the component master server obtains the first upgrade packages of multiple components to be upgraded that are set and have an unsynchronized status within the current preset upgrade cycle every preset upgrade cycle, and synchronizes the first upgrade packages of multiple components to be upgraded to the OTA server. The OTA server receives the first upgrade packages of multiple components to be upgraded, packages the first upgrade packages of multiple components to be upgraded into an upgrade package set, and sends the upgrade package set to the OTA client of the mobile terminal. The mobile terminal receives the upgrade package set sent by the OTA server based on the OTA client on the mobile terminal.

[0107] In some other embodiments, the OTA client actively triggers an upgrade operation every preset upgrade cycle. Correspondingly, this process can be: the OTA client of the mobile terminal sends a first upgrade request to the OTA server every preset upgrade cycle. The OTA server receives the first upgrade request sent by the OTA client and forwards the first upgrade request to the component master server. The component master server receives the first upgrade request forwarded by the OTA server, obtains the first upgrade packages of multiple components to be upgraded that are set and have an unsynchronized status within the current preset upgrade cycle, and sends the first upgrade packages of multiple components to be upgraded to the OTA server. The OTA server receives the first upgrade packages of multiple components to be upgraded, packages the first upgrade packages of multiple components to be upgraded into an upgrade package set, and sends the upgrade package set to the OTA client of the mobile terminal. The mobile terminal receives the upgrade package set sent by the OTA server based on the OTA client on the mobile terminal.

[0108] Step 602: The mobile terminal determines the upgrade clients corresponding to the first upgrade packages of multiple components to be upgraded in the mobile terminal based on the first upgrade packages of multiple components to be upgraded.

[0109] In some embodiments, this step is the same as step 202; alternatively, this step can be implemented through 305, which will not be elaborated here.

[0110] Step 603: The mobile terminal performs upgrade operations respectively through the determined multiple upgrade clients based on the first upgrade packages of multiple components to be upgraded.

[0111] In some embodiments, this step is the same as step 203; alternatively, this step can be implemented through 306 - 308, which will not be elaborated here.

[0112] Step 604: When the next upgrade cycle is not reached, the mobile terminal, based on the upgrade client on the mobile terminal, receives a third upgrade package sent by the upgrade server corresponding to the upgrade client, and the third upgrade package is synchronized from the component master server to the upgrade server.

[0113] When the next upgrade cycle is not reached, the user can trigger an upgrade instruction to the mobile terminal. Based on the upgrade instruction, the mobile terminal sends a fourth upgrade request to the upgrade server through the upgrade client. After receiving the fourth upgrade request, the upgrade server sends a third upgrade package to the upgrade client. The third upgrade package can be the same as the first upgrade package or different from the first upgrade package. The upgrade client receives the third upgrade package, thereby enabling the mobile terminal to receive the third upgrade package sent by the upgrade server based on the upgrade client.

[0114] In some embodiments, for the upgraded third upgrade package, after the upgrade client downloads the third upgrade package from the upgrade server, the upgrade server can notify the component master server to delete the third upgrade package, thereby avoiding the component master server sending the third upgrade package to the upgrade client through the OTA server and the OTA client when the preset upgrade cycle is reached subsequently, resulting in repeated upgrades of the upgrade client.

[0115] Step 605: The mobile terminal performs an upgrade operation based on the third upgrade package through the upgrade client.

[0116] In some embodiments, this step is similar to step 505 and will not be elaborated here.

[0117] In the embodiments of the present application, the OTA server can periodically pack the first upgrade packages of multiple components to be upgraded together and send them to the OTA client for a one-time download, thereby reducing the power consumption of the mobile terminal and improving the performance of the mobile terminal. Moreover, when the next upgrade cycle is not reached, the upgrade client can also achieve independent upgrades through the corresponding upgrade server, thereby meeting the user's needs.

[0118] Please refer to Figure 7 , which shows a mobile terminal upgrade device shown in an exemplary embodiment of the present application. The device includes:

[0119] A receiving module 701, configured to receive an upgrade package set sent by an OTA server based on an Over-the-Air (OTA) client on the mobile terminal. The upgrade package set includes the first upgrade packages of multiple components to be upgraded in the mobile terminal, and the first upgrade packages of the multiple components to be upgraded are synchronized from a component master server to the OTA server;

[0120] A first determination module 702, configured to determine, in the mobile terminal, an upgrade client corresponding to the first upgrade packages of the multiple components to be upgraded based on the first upgrade packages of the multiple components to be upgraded;

[0121] The first upgrade module 703 is used to perform upgrade operations respectively through multiple determined upgrade clients based on the first upgrade packages of multiple components to be upgraded.

[0122] In some embodiments, the first upgrade module 703 is used to send the first upgrade package of any component to be upgraded included in the upgrade package set to the upgrade client corresponding to the first upgrade package of the component to be upgraded, so that the upgrade client performs an upgrade operation based on the first upgrade package.

[0123] In some embodiments, the upgrade package set includes the first upgrade package of the application, the first upgrade package of the mainstream mainline, and the first upgrade package of the application plug-in;

[0124] The first upgrade module 703 is used to send the first upgrade package of the application to the SAU client, so that the SAU client performs application upgrade based on the first upgrade package of the application;

[0125] The first upgrade module 703 is used to send the first upgrade package of the mainline to the OPEX client, so that the OPEX client performs mainline upgrade based on the first upgrade package of the mainline;

[0126] The first upgrade module 703 is used to send the first upgrade package of the application plug-in to the plug-in client, so that the plug-in client performs plug-in upgrade based on the first upgrade package of the application plug-in.

[0127] In some embodiments, the first determination module 702 is used to obtain the attribution information of the first upgrade package from the first upgrade package for any first upgrade package of the components to be upgraded included in the upgrade package set; based on the attribution information of the first upgrade package, determine the upgrade client corresponding to the first upgrade package in the mobile terminal.

[0128] In some embodiments, the upgrade package set further includes an OTA upgrade package;

[0129] The device further includes:

[0130] The second upgrade module is used to perform an upgrade operation on the operating system of the mobile terminal through the OTA client based on the first OTA upgrade package.

[0131] In some embodiments, the device further includes:

[0132] The second determination module is used to determine the version identifier of the OTA client;

[0133] A receiving module 701, configured to, when the version identifier of the OTA client is used to indicate that the OTA client is not the latest version, receive an upgrade package set sent by an OTA server based on the over-the-air (OTA) client on the mobile terminal.

[0134] In some embodiments, for any first upgrade package, the first upgrade package is an upgrade package for a first function of an upgrade client corresponding to the first upgrade package;

[0135] The receiving module 701 is further configured to receive a second upgrade package sent by an upgrade server corresponding to the upgrade client based on the upgrade client, where the second upgrade package is an upgrade package for a second function of the upgrade client, and the priority level of the second function is lower than that of the first function;

[0136] A first upgrade module 703 is further configured to perform an upgrade operation on the second function through the upgrade client based on the second upgrade package.

[0137] In some embodiments, the apparatus further includes:

[0138] The receiving module 701 is configured to receive an upgrade package set sent by an OTA server based on the over-the-air (OTA) client on the mobile terminal every preset upgrade period;

[0139] The receiving module 701 is further configured to, when the next upgrade period is not reached, receive a third upgrade package sent by an upgrade server corresponding to the upgrade client based on the upgrade client on the mobile terminal, where the third upgrade package is synchronized from a component master server to the upgrade server;

[0140] The first upgrade module 703 is further configured to perform an upgrade operation through the upgrade client based on the third upgrade package.

[0141] In the embodiments of the present application, the OTA server may pack multiple first upgrade packages to be upgraded together and send them to the OTA client for one-time distribution. Compared with separate distribution of each first upgrade package, it can reduce the power consumption of the mobile terminal and improve the performance of the mobile terminal.

[0142] It should be noted that when the mobile terminal upgrade apparatus provided in the above embodiments performs mobile terminal upgrade, only the above-mentioned division of each functional module is used for illustration. In practical applications, the above functions may be allocated to different functional modules according to needs, that is, the internal structure of the terminal is divided into different functional modules to complete all or part of the functions described above. In addition, the mobile terminal upgrade apparatus provided in the above embodiments and the embodiments of the mobile terminal upgrade method belong to the same concept, and the specific implementation process is detailed in the method embodiments and will not be elaborated here.

[0143] Please refer to Figure 8, which shows a block diagram of a mobile terminal 800 shown in an exemplary embodiment of the present application. The mobile terminal 800 in the present application may include one or more of the following components: a processor 810, a memory 820, and a touch screen 830.

[0144] The processor 810 may include one or more processing cores. The processor 810 connects various parts within the entire mobile terminal 800 using various interfaces and lines, and by running or executing instructions, programs, code sets, or instruction sets stored in the memory 820, as well as calling data stored in the memory 820, it performs various functions of the mobile terminal 800 and processes data. Optionally, the processor 810 may be implemented in at least one hardware form of digital signal processing (DSP), field-programmable gate array (FPGA), or programmable logic array (PLA). The processor 810 may integrate one or several combinations of a central processing unit (CPU), a graphics processing unit (GPU), a neural-network processing unit (NPU), and a modem, etc. Among them, the CPU mainly processes the operating system, user interface, and application programs, etc.; the GPU is responsible for the rendering and drawing of the content required to be displayed on the touch screen 830; the NPU is used to implement artificial intelligence (AI) functions; the modem is used to process wireless communications. It can be understood that the above modem may not be integrated into the processor 810 and may be implemented separately by a single chip.

[0145] The memory 820 may include a Random Access Memory (RAM), and may also include a Read-Only Memory (ROM). Optionally, the memory 820 includes a non-transitory computer-readable storage medium. The memory 820 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 820 may include a program storage area and a data storage area. Among them, the program storage area can store instructions for implementing the operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the following various method embodiments, etc.; the data storage area can store data created according to the use of the mobile terminal 800 (such as audio data, phone book), etc.

[0146] The touch screen 830 is a display component for displaying a user interface. Optionally, the touch screen 830 is a display screen with a touch function. Through the touch function, the user can use a finger, a stylus, or any suitable object to perform touch operations on the touch screen 830.

[0147] The touch screen 830 is usually arranged on the front panel of the mobile terminal 800. The touch screen 830 can be designed as a full-screen, curved-screen, irregular-shaped screen, double-sided screen, or foldable screen. The touch screen 830 can also be designed as a combination of a full-screen and a curved-screen, a combination of an irregular-shaped screen and a curved-screen, etc. This embodiment does not limit this.

[0148] In addition, those skilled in the art can understand that the structure of the mobile terminal 800 shown in the above drawings does not limit the mobile terminal 800. The mobile terminal 800 may include more or fewer components than shown in the drawings, or combine some components, or have different component arrangements. For example, the mobile terminal 800 also includes components such as an audio acquisition device, a speaker, a radio frequency circuit, an input unit, a sensor, an audio circuit, a Wireless Fidelity (WiFi) module, a power supply, a Bluetooth module, etc., which will not be elaborated here.

[0149] The embodiment of the present application also provides a computer-readable medium. The computer-readable medium stores at least one program code, and the at least one program code is loaded and executed by a processor to implement the mobile terminal upgrade method shown in the above various embodiments.

[0150] The embodiment of the present application also provides a computer program product. The computer program product stores at least one program code, and the at least one program code is loaded and executed by a processor to implement the mobile terminal upgrade method shown in the above various embodiments.

[0151] In some embodiments, the computer program product involved in the embodiments of the present application can be deployed to be executed on a mobile terminal, or on multiple mobile terminals located at one place, or on multiple mobile terminals distributed at multiple places and interconnected through a communication network. The multiple mobile terminals distributed at multiple places and interconnected through a communication network can form a blockchain system.

[0152] Those skilled in the art should be able to realize that in the above one or more examples, the functions described in the embodiments of the present application can be implemented by hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. The computer-readable medium includes computer storage media and communication media, where the communication media includes any medium that facilitates the transmission of a computer program from one place to another. The storage media can be any available medium accessible by a general-purpose or special-purpose computer.

[0153] The above are only alternative embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included within the protection scope of the present application.

Claims

1. A mobile terminal upgrade method, characterized in that, The method includes: Based on the Over-the-Air (OTA) client on the mobile terminal, receiving an upgrade package set sent by the OTA server, where the upgrade package set includes first upgrade packages of multiple components to be upgraded in the mobile terminal, and the first upgrade packages of the multiple components to be upgraded are synchronized from the component master server to the OTA server; Based on the first upgrade packages of the multiple components to be upgraded, determining, in the mobile terminal, upgrade clients corresponding to the first upgrade packages of the multiple components to be upgraded; Based on the first upgrade packages of the multiple components to be upgraded, performing upgrade operations respectively through the determined multiple upgrade clients.

2. The method according to claim 1, wherein The performing upgrade operations respectively through the determined multiple upgrade clients based on the first upgrade packages of the multiple components to be upgraded includes: For any first upgrade package of a component to be upgraded included in the upgrade package set, sending the first upgrade package to the upgrade client corresponding to the first upgrade package of the component to be upgraded, so that the upgrade client performs an upgrade operation based on the first upgrade package.

3. The method according to claim 2, wherein The upgrade package set includes a first upgrade package of an application, a first upgrade package of the mainstream mainline, and a first upgrade package of an application plug-in; The sending the first upgrade package to the upgrade client corresponding to the first upgrade package of the component to be upgraded, so that the upgrade client performs an upgrade operation based on the first upgrade package includes: Sending the first upgrade package of the application to the Serviceability Agent Unit (SAU) client of the intelligent network, so that the SAU client performs application upgrade based on the first upgrade package of the application; Sending the first upgrade package of the mainline to the Operational Excellence (OPEX) client, so that the OPEX client performs mainline upgrade based on the first upgrade package of the mainline; Sending the first upgrade package of the application plug-in to the plug-in client, so that the plug-in client performs plug-in upgrade based on the first upgrade package of the application plug-in.

4. The method according to claim 1, wherein The determining, in the mobile terminal, upgrade clients corresponding to the first upgrade packages of the multiple components to be upgraded based on the first upgrade packages of the multiple components to be upgraded includes: For any first upgrade package of a component to be upgraded included in the upgrade package set, obtaining the attribution information of the first upgrade package from the first upgrade package; Based on the attribution information of the first upgrade package, determining, in the mobile terminal, the upgrade client corresponding to the first upgrade package.

5. The method according to claim 1, characterized in that, The upgrade package set further includes an OTA upgrade package; The method further includes: Based on the first OTA upgrade package, performing an upgrade operation on the operating system of the mobile terminal through the OTA client.

6. The method according to claim 5, characterized in that, The method further includes: Determining the version identifier of the OTA client; In the case where the version identifier of the OTA client is used to indicate that the OTA client is not the latest version, performing the step of receiving the upgrade package set sent by the OTA server based on the Over-the-Air (OTA) client on the mobile terminal.

7. The method according to claim 1, characterized in that The method further includes: For any first upgrade package, the first upgrade package is an upgrade package for the first function of the upgrade client corresponding to the first upgrade package; based on the upgrade client, receive a second upgrade package sent by the upgrade server corresponding to the upgrade client, where the second upgrade package is an upgrade package for the second function of the upgrade client, and the priority level of the second function is lower than that of the first function; Based on the second upgrade package, perform an upgrade operation for the second function through the upgrade client.

8. The method according to claim 1, characterized in that, The method further includes: Every preset upgrade period, execute the step of receiving an upgrade package set sent by an OTA server based on the over-the-air (OTA) client on the mobile terminal; When the next upgrade period has not been reached, based on the upgrade client on the mobile terminal, receive a third upgrade package sent by the upgrade server corresponding to the upgrade client, where the third upgrade package is synchronized from the component master server to the upgrade server; Based on the third upgrade package, perform an upgrade operation through the upgrade client.

9. A mobile terminal upgrade device, characterized in that, The device includes: A receiving module, configured to receive an upgrade package set sent by an OTA server based on the over-the-air (OTA) client on the mobile terminal, where the upgrade package set includes first upgrade packages of a plurality of components to be upgraded in the mobile terminal, and the first upgrade packages of the plurality of components to be upgraded are synchronized from the component master server to the OTA server; A first determination module, configured to determine, in the mobile terminal, an upgrade client corresponding to the first upgrade packages of the plurality of components to be upgraded based on the first upgrade packages of the plurality of components to be upgraded; A first upgrade module, configured to perform upgrade operations respectively through the determined plurality of upgrade clients based on the first upgrade packages of the plurality of components to be upgraded.

10. A mobile terminal, characterized in that, The mobile terminal includes a processor and a memory, and at least one program code is stored in the memory and is loaded and executed by the processor to implement the mobile terminal upgrade method according to any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that, At least one program code is stored in the storage medium and is loaded and executed by a processor to implement the mobile terminal upgrade method according to any one of claims 1 to 8.

12. A computer program product, characterized in that, The computer program product stores at least one program code, and the at least one program code is used to be executed by a processor to implement the mobile terminal upgrade method according to any one of claims 1 to 8.

Images