Software upgrading method, system and device, electronic equipment and storage medium

Abstract

The embodiment of the invention discloses a software upgrading method, system and device, electronic equipment and a storage medium. The method is applied to an upgrading management platform and comprises the steps that an upgrading task of target software and an exception label are created, and the exception label is used for marking terminal equipment with target software upgrading exception; receiving an upgrading request of the terminal equipment for the target software; and performing issuing management of the upgrade task based on the upgrade request and the abnormal tag. According to the method, the issuing management of the upgrading task can be optimized by setting the abnormal tag.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a software upgrading method, system, device, electronic device and storage medium. Background Art

[0002] When terminal devices obtain upgrade tasks and try to install new versions of applications, they often encounter various abnormal problems, such as network interruption, insufficient storage, or compatibility issues, which lead to installation failures. After the current version fails to install, if the terminal device detects an upgrade task next time and there is no updated version released, it will still detect the current version and try to download and install it again, resulting in a cycle of repeated downloads and installation failures. This not only wastes network resources and storage space, but also affects the user experience. Summary of the invention

[0003] The embodiments of the present application provide a software upgrade method, system, device, electronic device and storage medium, which can optimize the distribution management of upgrade tasks by setting exception tags.

[0004] In a first aspect, an embodiment of the present application provides a software upgrade method, which is applied to an upgrade management platform, including: creating an upgrade task and an exception label for the target software, wherein the exception label is used to mark terminal devices with target software upgrade exceptions; receiving an upgrade request from the terminal device for the target software; and managing the issuance of upgrade tasks based on the upgrade request and the exception label.

[0005] In some implementations, the upgrade task is managed based on the upgrade request and the exception tag, including: obtaining the device tag of the terminal device based on the upgrade request; and managing the upgrade task based on the device tag.

[0006] In some implementations, the issuance of upgrade tasks is managed based on device tags, including: when the device tag contains an abnormal tag, determining not to issue the upgrade task to the terminal device; or when the device tag does not contain an abnormal tag, determining to issue the upgrade task to the terminal device.

[0007] In a second aspect, an embodiment of the present application provides a software upgrade method, which is applied to a data management system, including: receiving a label creation request for an upgrade task from an upgrade management platform; and creating an exception label associated with the upgrade task based on the label creation request.

[0008] In some implementations, the method further includes: receiving a message from a terminal device indicating that the upgrade task has failed to execute; and adding an abnormal tag to a device tag of the terminal device.

[0009] On the third aspect, an embodiment of the present application provides a software upgrade system, including: an upgrade management platform and a data management system, wherein the upgrade management platform is configured to create upgrade tasks and exception labels for target software, wherein the exception label is used to mark terminal devices with target software upgrade exceptions, receive upgrade requests from terminal devices for the target software, and manage the issuance of upgrade tasks based on the upgrade requests and the exception labels; and the data management system is configured to receive label creation requests from the upgrade management platform for upgrade tasks, and create exception labels based on the label creation requests.

[0010] In a fourth aspect, an embodiment of the present application provides a software upgrade device, which is applied to an upgrade management platform, including: a first creation module, used to create an upgrade task and an exception label for the target software, wherein the exception label is used to mark the terminal device with the target software upgrade exception; a first receiving module, used to receive an upgrade request from the terminal device for the target software; and a task issuance management module, used to manage the issuance of upgrade tasks based on the upgrade request and the exception label.

[0011] In the fifth aspect, an embodiment of the present application provides a software upgrade device, applied to a data management system, including: a second receiving module, used to receive a label creation request for an upgrade task from an upgrade management platform; and a second creation module, used to create an exception label associated with the upgrade task based on the label creation request.

[0012] In a sixth aspect, an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the operations in the method described in any one of the first to third aspects are implemented.

[0013] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the operations in the method described in any one of the first to third aspects are implemented.

[0014] In summary, the embodiments of the present application disclose a software upgrade method, system, device, electronic device and storage medium. The method is applied to an upgrade management platform, including: creating an upgrade task and an exception tag for the target software, wherein the exception tag is used to mark the terminal device with abnormal target software upgrade; receiving an upgrade request for the target software from the terminal device; and performing the distribution management of the upgrade task based on the upgrade request and the exception tag. The method can optimize the distribution management of the upgrade task by setting the exception tag. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of this specification, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0016] Figure 1 A schematic diagram showing an application scenario of a software upgrade method provided by some embodiments of the present application is shown;

[0017] Figure 2 A schematic diagram showing a flow chart of a software upgrade method provided by some embodiments of the present application;

[0018] Figure 3 A schematic diagram showing a flow chart of a software upgrade method provided by some embodiments of the present application;

[0019] Figure 4 A schematic diagram showing a flow chart of a software upgrade method provided by other embodiments of the present application;

[0020] Figure 5 An example flowchart of a software upgrade provided by some embodiments of the present application is shown;

[0021] Figure 6 A schematic diagram showing the structure of a software upgrade device provided in some embodiments of the present application is shown;

[0022] Figure 7 A schematic diagram showing the structure of a software upgrade device provided in some embodiments of the present application is shown;

[0023] Figure 8 A schematic diagram of the structure of an electronic device provided in some embodiments of the present application is shown. DETAILED DESCRIPTION

[0024] The following will be combined with the drawings in this application to clearly and completely describe the technical solutions in this application. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of them. Based on the embodiments in the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0025] Figure 1 The following is a schematic diagram showing an application scenario of the software upgrade method provided by some embodiments of the present application. Figure 1 As shown, the application scenario may include a terminal device 101 , an upgrade management platform 102 , and a data management system 103 .

[0026] Among them, the terminal device 101 can be a device that is connected to the upgrade management platform 102 and the data management system 103 for communication. The terminal device 101 can send an upgrade request of the target software to the upgrade management platform 102, and obtain an upgrade task, including an upgrade package of the target software, through the upgrade management platform 102. The terminal device 101 can report a message that the upgrade task execution failed to the data management system 103. In some embodiments, the terminal device 101 may include a hardware device with a data information processing function and an application necessary to drive the hardware device to work. The application can provide users with the ability and interface to interact with the outside world through the network.

[0027] In some embodiments, the terminal device 101 may include a mobile device, a server, a built-in device of a motor vehicle, or the like, or any combination thereof. In some embodiments, the mobile device may include a tablet computer, a laptop computer, a smart home device, a smart mobile device, a virtual reality device, an augmented reality device, or the like, or any combination thereof. In some embodiments, the smart home device may include a smart TV, a desktop computer, or the like, or any combination thereof. In some embodiments, the smart mobile device may include a smart phone, a personal digital assistant, a gaming device, a navigation device, or the like, or any combination thereof. In some embodiments, the built-in device in the motor vehicle may include an onboard computer, an onboard TV, or the like.

[0028] The upgrade management platform 102 can be connected to the terminal device 101 and the data management system 103. The upgrade management platform 102 can be used for software version control management and software release and upgrade. In some embodiments, the upgrade management platform 102 can create an upgrade task and an exception tag for the target software, receive an upgrade request from the terminal device 101 for the target software, and manage the distribution of the upgrade task based on the upgrade request and the exception tag. The exception tag is used to mark the terminal device with abnormal target software upgrade.

[0029] Among them, the data management system 103 can be used to perform data management related to the upgrade task and the terminal device 101, including the management of abnormal tags related to the upgrade task and the device tags related to the terminal device 101. For example, the data management system 103 can be used for the storage and query of abnormal tags related to the upgrade task and the device tags related to the terminal device 101. The data management system 103 may include one or more databases for data storage. The database may be one or more of a relational database, a non-relational database, or a data warehouse. The database can be used to persistently store the data required by the upgrade management platform 102. In the database, the data can be organized according to a certain structure (such as a table, a collection, or a document, etc.), and can be managed by a database management system. In some embodiments, the data management system 103 can receive a tag creation request for the upgrade task from the upgrade management platform, and based on the tag creation request, create an abnormal tag associated with the upgrade task.

[0030] The upgrade management platform 102 or the data management system 103 can be a single computing device or a cluster system composed of multiple computing devices. The upgrade management platform 102 or the data management system 103 can adopt any form of system architecture. For example, a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture, etc. It should be noted that Figure 1 The numbers of the upgrade management platform 102 and the data management system 103 shown in the figure are examples only and any number may be provided according to implementation requirements.

[0031] It should also be noted that Figure 1 The application scenario diagram of the software upgrade method shown is only an example, and the application scenario example is to more clearly illustrate the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution of the present application. For example, in some embodiments, the upgrade management platform 102 and the data management system 103 can also be the same computing device.

[0032] Figure 2 The flowchart of the software upgrade method provided by some embodiments of the present application is shown. Although the logical order is shown in the flowchart, in some cases, the operations shown or described may be performed in an order different from that shown in the accompanying drawings. Specifically, the software upgrade method can be applied to the upgrade management platform, and the process can be as follows:

[0033] S201. Create an upgrade task and an exception label for the target software.

[0034] The upgrade management platform can be used to manage the upgrade of the target software, including version management of the target software, software package updates, and upgrade task issuance. Among them, creating an upgrade task for the target software may include preparing the updated software package, configuring the update policy, and issuing the upgrade task. Among them, the configuration update policy may include version number requirements, device type restrictions, etc. When requesting an upgrade of the target software, the terminal device may make a request according to the latest version number detected. As mentioned above, after the current version fails to be installed, if the terminal device does not release an updated version when it detects an upgrade task next time, it will still detect the current version according to the latest version number and try to download and install it again, resulting in a cycle of repeated download and installation failures. This not only wastes network resources and storage space, but also affects the user experience.

[0035] Among them, the abnormal label can be used to mark the terminal device with abnormal target software upgrade. When the terminal device containing the abnormal label sends a request for the same upgrade task again, the upgrade management platform can manage the issuance of the upgrade task according to the abnormal upgrade strategy. For example, the upgrade management platform can refuse to issue the upgrade task again to avoid repeated downloads and installation failures. For another example, the upgrade management platform can set an attempt number threshold. The upgrade task can be issued within the attempt number threshold, and it will not be issued if the attempt number threshold is exceeded.

[0036] The upgrade management platform can create an exception tag associated with the upgrade task when creating an upgrade task for the target software. The exception tag and the association relationship with the upgrade task can be stored in the upgrade management platform, or in another system, such as a specific data management system.

[0037] S202: Receive a request from a terminal device to upgrade the target software.

[0038] The terminal device's request for upgrading the target software may include the version number of the target software and relevant information of the terminal device. The version number of the target software may be used to determine the corresponding upgrade package of the target software. The relevant information of the terminal device may be used to determine whether the terminal device has the authority to obtain the target software upgrade task, or may be used to determine the software package that is compatible with the system of the terminal device, etc.

[0039] S203: Based on the upgrade request and the exception tag, manage the issuance of the upgrade task.

[0040] In some embodiments, operation S203 may include: based on the upgrade request, obtaining a device tag of the terminal device, and managing the issuance of the upgrade task based on the device tag.

[0041] Among them, the device tag of the terminal device may include one or more of the basic information, hardware information, software information, and network information of the terminal device. Among them, the basic information may include information such as the device model, operating system, and firmware version. The hardware information may include information such as the device's processor and storage space. The software information may include information such as an application list, regional equipment, and system language. The network information may include network connection status, operator information, etc. In some embodiments, the device tag may include an abnormal tag. For terminal devices including abnormal tags, the issuance and management of upgrade tasks may be performed according to the corresponding abnormal upgrade strategy.

[0042] The exception tag is associated with a specific upgrade task, and the exception tag can be a digital ID or a string. For example, in the upgrade task for version 1.2.21 of the target software A, the exception tag associated with the upgrade task is set to 35469827354. If a terminal device fails to install this version of the target software A, an exception tag is added to mark the terminal device where the installation failed. For example, the tag 35469827354 can be added to the device tag of the terminal device. If the terminal device again initiates an upgrade request for version 1.2.21 of the target software A to the upgrade management platform, the upgrade management platform can detect whether the terminal device contains the exception tag 35469827354 associated with the upgrade task of this version of the target software A, and then manage the task issuance based on the judgment result.

[0043] In other embodiments, after an upgrade exception occurs, the terminal device can store an exception tag related to the upgrade task locally, and when an upgrade request is issued again, the exception tag is actively added to the upgrade request and sent to the upgrade management platform. After receiving the upgrade request, the upgrade management platform parses the exception tag and learns that the terminal device previously failed to execute the upgrade task. Afterwards, the upgrade task can be issued and managed according to the corresponding abnormal upgrade strategy.

[0044] Some embodiments of the present application provide a software upgrade method, which is applied to an upgrade management platform, including: creating an upgrade task and an exception tag for a target software, wherein the exception tag is used to mark a terminal device with an abnormal target software upgrade; receiving an upgrade request for the target software from the terminal device; and performing distribution management of the upgrade task based on the upgrade request and the exception tag. The method can optimize the distribution management of the upgrade task by setting the exception tag.

[0045] Figure 3The flowchart of the software upgrade method provided by some embodiments of the present application is shown. Although the logical order is shown in the flowchart, in some cases, the operations shown or described may be performed in an order different from that shown in the accompanying drawings. Specifically, the software upgrade method can be applied to the upgrade management platform, and the process can be as follows:

[0046] S301: Create an upgrade task and an exception label for the target software.

[0047] S302: Receive a request from a terminal device to upgrade the target software.

[0048] S303: Based on the upgrade request, obtain the device tag of the terminal device.

[0049] As mentioned above, in some embodiments, the device tag of the terminal device can be used to indicate the identity, status, and other information of the terminal device. Among them, the terminal device that fails to execute the upgrade task of the target software can be marked with an abnormal tag, and the presence of the abnormal tag in the detection device can determine whether the terminal device has executed the upgrade task and whether the execution failed.

[0050] In some embodiments, the device ID can be obtained according to the upgrade request, and then the corresponding device tag can be queried in the data management system according to the device ID. The data management system can store the device tag corresponding to the device ID, and the device tag can be queried through the device ID.

[0051] In some embodiments, the management of issuing upgrade tasks based on device tags may include:

[0052] S304: Determine whether the device tag contains an abnormal tag. If the device tag contains an abnormal tag, perform operation S305; or, if the device tag does not contain an abnormal tag, perform operation S306.

[0053] S305: Determine not to send the upgrade task to the terminal device. When the device tag contains an abnormal tag, it means that the terminal device has executed the upgrade task and failed. Not sending the upgrade task again can avoid the terminal device from repeatedly downloading the software installation package and repeatedly installing it, thereby avoiding wasting traffic resources and affecting user experience.

[0054] S306: Determine to send the upgrade task to the terminal device. If the device tag does not include the abnormal tag, it means that the terminal device has not executed the upgrade task, and the upgrade task can be sent to the terminal device.

[0055] The software upgrade method provided in some embodiments of the present application can obtain the device tag according to the upgrade request, and further determine whether the device tag contains abnormal tags related to the upgrade task. If so, the task will not be issued, which can avoid the terminal device repeatedly downloading the software installation package and repeatedly installing it, thereby avoiding wasting traffic resources and affecting the user experience.

[0056] Figure 4 The flowchart of the software upgrade method provided by some other embodiments of the present application is shown. Although the logical order is shown in the flowchart, in some cases, the operations shown or described may be performed in an order different from that shown in the drawings. Specifically, the software upgrade method can be applied to a data management system, and the process can be as follows:

[0057] S401: Receive a label creation request for an upgrade task from an upgrade management platform.

[0058] As previously mentioned, the upgrade management platform can create an upgrade task for the target software. The data management system can manage the relevant data of the upgrade task and / or the device data related to the upgrade task. After the upgrade management platform creates the upgrade task, it can create an exception tag related to the upgrade task, wherein the exception tag can be used to mark the terminal device with abnormal target software upgrade. In some embodiments, the upgrade management platform can create an exception tag by sending a tag creation request to the data management system, and the data management system creates an exception tag after receiving the request.

[0059] S402: Create an abnormal tag associated with the upgrade task based on the tag creation request.

[0060] The tag creation request may include information related to the upgrade task, for example, an upgrade task ID uniquely corresponding to the upgrade task. The data management system may assign an abnormal tag corresponding to the upgrade task. The abnormal tag may be used to determine which upgrade task the marked terminal device failed to execute.

[0061] In some embodiments, the software upgrade method may further include:

[0062] S403: Receive a message from a terminal device indicating that the upgrade task execution has failed.

[0063] After the terminal device fails to perform a certain upgrade task, the terminal device can report this message to the data management system. The reported message may include the device information of the terminal device, such as the device ID, and the relevant information of the upgrade task, such as the upgrade task ID. Further, a field tag can be obtained according to the upgrade task ID. It is understandable that the identification information of the terminal device and the identification information of the upgrade task can be reported in other ways, and this application does not limit this.

[0064] S404: Add an abnormal tag to the device tag of the terminal device.

[0065] After the exception tag is created, when the data management system receives the message that the upgrade task execution failed reported by the terminal device, the exception tag corresponding to the upgrade task can be queried, and then the exception tag is added to the device tag corresponding to the device ID according to the device ID of the terminal device.

[0066] Some embodiments of the present application provide a software upgrade method, which is applied to a data management system, and includes: receiving a label creation request for an upgrade task from an upgrade management platform, and creating an abnormal label associated with the upgrade task based on the label creation request. The software upgrade method can optimize the management of issuing upgrade tasks by setting abnormal labels.

[0067] Figure 5 FIG. 1 shows an example flow chart of software upgrade provided by some embodiments of the present application. Figure 5 As shown, the software upgrade process can be as follows:

[0068] The upgrade management platform creates an upgrade task for the target software.

[0069] The upgrade management platform sends a tag creation request to the data management system, requesting the creation of an exception tag related to the upgrade task.

[0070] The data management system creates an exception tag associated with the upgrade task according to the tag creation request of the upgrade management platform, and returns a message indicating that the exception tag is created successfully.

[0071] The terminal device can send an upgrade request for the target software to the upgrade management platform.

[0072] After receiving the upgrade request, the upgrade management platform obtains the device ID of the terminal device according to the upgrade request, and queries the data management system for the device tag according to the device ID.

[0073] After the data management system queries the device tag based on the device ID, it returns the device tag to the upgrade management platform.

[0074] The upgrade management platform determines whether the device tag contains abnormal tags. If not, the upgrade task is issued; if contained, the upgrade task is not issued.

[0075] For the terminal device that receives the upgrade task, if the upgrade fails, a message of the upgrade failure can be sent to the data management system, and the data management system can add an abnormal tag related to the upgrade task to the device tag of the terminal device.

[0076] When the terminal device with the abnormal tag added initiates the request for the upgrade task again, since its device tag contains the abnormal tag, the upgrade management system may choose not to issue the upgrade task again.

[0077] Figure 6 The schematic diagram of the structure of the software upgrade device provided in some embodiments of the present application is shown. The software upgrade device 600 is applied to the upgrade management platform and may specifically include:

[0078] The first creation module 601 is used to create an upgrade task and an abnormality tag of the target software, wherein the abnormality tag is used to mark the terminal device with abnormal target software upgrade.

[0079] The first receiving module 602 is used to receive a request from a terminal device to upgrade the target software.

[0080] The task delivery management module 603 is used to manage the delivery of upgrade tasks based on the upgrade request and the exception tag.

[0081] The software upgrade device 600 provided in some embodiments of the present application can create an upgrade task and an exception label of the target software by a first creation module 601. Among them, the exception label is used to mark the terminal device with abnormal target software upgrade. Next, the software upgrade device 600 can receive the upgrade request of the terminal device for the target software by a first receiving module 602. Next, the software upgrade device 600 can manage the issuance of the upgrade task based on the upgrade request and the exception label by a task issuance management module 603. The software upgrade device 600 provided in some embodiments of the present application can optimize the issuance management of the upgrade task by setting the exception label.

[0082] In some embodiments, the task delivery management module 603 may include a tag acquisition unit and a task delivery management unit. The tag acquisition unit may be used to acquire the device tag of the terminal device based on the upgrade request. The task delivery management unit may be used to manage the delivery of the upgrade task based on the device tag.

[0083] In some embodiments, the task delivery management unit may include a first management subunit and a second management subunit. The first management subunit may be used to determine not to deliver the upgrade task to the terminal device when the device tag contains an abnormal tag. Alternatively, the second management subunit may be used to determine to deliver the upgrade task to the terminal device when the device tag does not contain an abnormal tag.

[0084] Figure 7 The schematic diagram of the structure of the software upgrade device provided in some embodiments of the present application is shown. The software upgrade device 700 is applied to a data management system and may specifically include:

[0085] The second receiving module 701 is used to receive a label creation request for an upgrade task from the upgrade management platform.

[0086] The second creation module 702 is used to create an abnormal tag associated with the upgrade task based on the tag creation request.

[0087] The software upgrade device 700 provided in some embodiments of the present application may first receive a label creation request for an upgrade task from the upgrade management platform by the second receiving module 701, and then create an abnormal label associated with the upgrade task based on the label creation request by the second creating module 702. The software upgrade device 700 provided in some embodiments of the present application can optimize the management of issuing upgrade tasks by setting abnormal labels.

[0088] In some embodiments, the software upgrade device 700 may further include a third receiving module and a tag adding module. The third receiving module may be used to receive a message of a failed upgrade task execution reported by a terminal device. The tag adding module may be used to add an abnormal tag to a device tag of the terminal device.

[0089] In addition, the present application also provides an electronic device, Figure 8 The following is a schematic diagram of the structure of an electronic device provided by some embodiments of the present application, specifically:

[0090] The electronic device 800 may include one or more processors 801 of processing cores, one or more computer-readable storage media memories 802 and other components. Those skilled in the art will appreciate that Figure 8 The structure of the electronic device 800 shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0091] The processor 801 is the control center of the electronic device 800. It uses various interfaces and lines to connect various parts of the entire electronic device 800. By running or executing software programs and / or modules stored in the memory 802 and calling data stored in the memory 802, it executes various functions of the electronic device 800 and processes data, thereby monitoring the electronic device 800 as a whole. Optionally, the processor 801 may include one or more processing cores; preferably, the processor 801 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface and application programs, etc., and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 801.

[0092] The memory 802 can be used to store software programs and modules. The processor 801 executes various functional applications and data processing by running the software programs and modules stored in the memory 802. The memory 802 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function, etc.; the data storage area may store data created according to the use of the electronic device 800, etc. In addition, the memory 802 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 802 may also include a memory controller to provide the processor 801 with access to the memory 802.

[0093] Specifically in this embodiment, the processor 801 in the electronic device 800 will load the executable files corresponding to the processes of one or more applications into the memory 802 according to the following instructions, and the processor 801 will run the applications stored in the memory 802, thereby implementing the operations in any software upgrade method provided in the embodiments of the present application.

[0094] The specific process of the electronic device 800 executing the software upgrade method can be referred to Figures 2 to 5 The description in , this application will not be repeated here.

[0095] Those skilled in the art will appreciate that all or part of the operations in the various methods of the above embodiments may be accomplished through instructions, or through instruction-controlled related hardware. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0096] To this end, the present application provides a computer-readable storage medium, on which a computer program is stored. The computer program can be loaded by a processor to execute the operations in any software upgrade method provided in the present application.

[0097] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.

[0098] The computer-readable storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0099] Since the instructions stored in the computer-readable storage medium can execute the operations in any software upgrade method provided in the present application, the beneficial effects that can be achieved by any software upgrade method provided in the present application can be achieved. Please refer to the previous embodiments for details and will not be repeated here.

[0100] The above is a detailed introduction to a software upgrade method, system, device, electronic device and storage medium provided by the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea. At the same time, for technical personnel in this field, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A software upgrade method, applied to an upgrade management platform, characterized in that: include: Creating an upgrade task and an exception label for the target software, wherein the exception label is used to mark the terminal device with the target software upgrade exception; receiving a request from a terminal device to upgrade the target software; and Based on the upgrade request and the exception tag, the upgrade task is managed.

2. The method according to claim 1, characterized in that The managing the issuance of the upgrade task based on the upgrade request and the abnormal tag includes: Based on the upgrade request, obtaining a device tag of the terminal device; and Based on the device tag, the upgrade task is managed.

3. The method according to claim 2, characterized in that The managing the distribution of the upgrade task based on the device tag includes: In a case where the device tag includes the abnormal tag, determining not to send the upgrade task to the terminal device; or In a case where the device tag does not include the abnormal tag, it is determined to send the upgrade task to the terminal device.

4. A software upgrade method, applied to a data management system, characterized in that: include: Receive a label creation request for an upgrade task from the upgrade management platform; as well as Based on the tag creation request, an exception tag associated with the upgrade task is created.

5. The method according to claim 4, characterized in that Also includes: Receiving a message from a terminal device indicating that the upgrade task has failed to execute; as well as The abnormal tag is added to the device tag of the terminal device.

6. A software upgrade system, characterized in that: include: Upgrade the management platform and data management system, including: The upgrade management platform is configured to create an upgrade task and an exception label for the target software, wherein the exception label is used to mark the terminal device with the target software upgrade exception, receive an upgrade request for the target software from the terminal device, and perform distribution management of the upgrade task based on the upgrade request and the exception label; and The data management system is configured to receive a label creation request for the upgrade task from the upgrade management platform, and to create the exception label based on the label creation request.

7. A software upgrade device, applied to an upgrade management platform, characterized in that: include: A first creation module is used to create an upgrade task and an exception label of the target software, wherein the exception label is used to mark the terminal device with the target software upgrade exception; A first receiving module is used to receive a request from a terminal device to upgrade the target software; and The task delivery management module is used to manage the delivery of the upgrade task based on the upgrade request and the exception tag.

8. A software upgrade device, applied to a data management system, characterized in that: include: A second receiving module is used to receive a label creation request for an upgrade task from the upgrade management platform; as well as The second creation module is used to create an abnormal tag associated with the upgrade task based on the tag creation request.

9. An electronic device, characterized in that: The method comprises a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the operations in the method according to any one of claims 1 to 3 or claims 4 to 5 when executing the computer program.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the operations in the method according to any one of claims 1 to 3 or claims 4 to 5 are implemented.

Images