CN116527503A - Method and device for determining upgrade strategy, storage medium and electronic device - Google Patents

Abstract

The application discloses a method and a device for determining an upgrade strategy, a storage medium and an electronic device, and relates to the technical field of smart families, wherein the method for determining the upgrade strategy comprises the following steps: determining a target upgrading task to be configured; configuring upgrade times for the target upgrade task, wherein the upgrade times are the maximum times of the target upgrade task allowed to execute upgrade operation; and under the condition that the target upgrading task is started, controlling the upgrading strategy of the target upgrading task according to the upgrading times. The problem that an upgrading scheme in the related technology, the upgrading safety and reliability are controlled manually, and an abnormal upgrading task cannot be found and terminated in time, so that the upgrading task is caused to continuously influence more user equipment is solved.

Description

Method and device for determining upgrade strategy, storage medium and electronic device

technical field

The present application relates to the technical field of smart home, and in particular, relates to a method and device for determining an upgrade strategy, a storage medium, and an electronic device.

Background technique

When the device OTA (Over-the-Air Technology, over-the-air technology) upgrade is based on the applicable version, once the upgrade task is started, it will take effect for the matching devices on the entire network. Specifically, when the device is online, if there is a matching and For upgrade tasks that take effect, the platform will issue upgrade instructions. The device that receives the instruction will automatically upgrade or pop up the window and upgrade after the user confirms. In this process, unless the task is artificially suspended, within the effective execution period of the upgrade task, the matching equipment can be matched and upgraded. Once an abnormality occurs and is not discovered in time, abnormal upgrades may continue to occur in the future. Among them, the reasons for the abnormality are various. It may be due to device differentiation, or there may be bugs in firmware packages or platforms. If the upgrade fails, if the device is still available, it will only affect the user experience. If it fails and causes the equipment to be unavailable, it will directly cause damage to the customer's property, and the consequences are quite serious. When such unpredictable problems occur, in order to reduce the impact of accidents, more refined configuration and control restrictions should be implemented in high-risk upgrade scenarios.

However, the current upgrade task is valid for all matching devices, and the range of upgrade tasks performed by different production lines is different, and the number of user devices involved is also different. Therefore, the current upgrade task cannot be finely differentiated and controlled; When abnormalities occur and the upgrade failure rate is high, the platform for issuing the upgrade task does not have the ability to automatically terminate the upgrade; nor does it follow the "flow" upgrade control method, which is not flexible enough.

In the related technologies, in the existing upgrade scheme, the safety and reliability of the upgrade depends on human control, and the upgrade task may not be detected and terminated in time if an abnormality occurs, which will cause the upgrade task to continue to affect more user equipment. No effective solution has been proposed yet. s solution.

Therefore, it is necessary to improve the related technology to overcome the above-mentioned defects in the related technology.

Contents of the invention

The embodiment of the present application provides a method and device for determining an upgrade strategy, a storage medium, and an electronic device, so as to at least solve the upgrade scheme in related technologies. The safety and reliability of the upgrade depends on human control, and the upgrade task may not be discovered in time if an abnormality occurs. , which in turn leads to the problem that the upgrade task continues to affect more user devices.

According to an aspect of an embodiment of the present application, a method for determining an upgrade strategy is provided, including: determining a target upgrade task to be configured; configuring an upgrade count for the target upgrade task, wherein the upgrade count is the target upgrade task The maximum number of upgrade operations allowed; when the target upgrade task is started, the upgrade policy of the target upgrade task is controlled according to the upgrade times.

In an exemplary embodiment, controlling the upgrade policy of the target upgrade task according to the upgrade times includes: determining the current upgrade times of the target upgrade task on the specified device; when the current upgrade times are less than or equal to the In the case of the above upgrade times, it is determined that the target upgrade task is allowed to continue to upgrade on the designated device; when the current upgrade times are greater than the upgrade times, suspend the upgrade of the target upgrade task on the designated device operate.

In an exemplary embodiment, after controlling the upgrade policy of the target upgrade task according to the upgrade times, the method further includes: acquiring the upgrade success rate of the target upgrade task in the first historical time period; When the upgrade success rate is greater than the first threshold, the upgrade times are increased according to the upgrade increment index; when the upgrade success rate is less than or equal to the first threshold, the upgrade times are decreased according to the upgrade decrement index.

In an exemplary embodiment, expanding the number of upgrades according to the upgrade increment index includes: obtaining the historical upgrade success rate of the upgrade task in a second historical time period, wherein the second historical time period is in the Before the first historical time period; determine the upgrade success rate and the average upgrade success rate of the historical upgrade success rate, and expand the upgrade times according to the average upgrade success rate and the upgrade increment index.

In an exemplary embodiment, after the target upgrade task to be configured is determined, the method further includes: configuring an upgrade exception whitelist for the target upgrade task, wherein the upgrade exception whitelist includes a plurality of target upgrade tasks The identification of the task, the maximum number of upgrade operations allowed by the multiple target upgrade tasks is not configured; when the number of upgrade operations performed by the target upgrade task exceeds the second threshold, the target upgrade task is being executed Any device in the system will send out an alarm prompt.

In an exemplary embodiment, after determining the target upgrade task to be configured, the method further includes: configuring an upgrade exception blacklist for the target upgrade task, wherein the upgrade exception blacklist includes: one or more Abnormal types; obtain the number of occurrences of the one or more abnormal types in the process of performing the upgrade operation of the target upgrade task; in the case that the occurrence times of the target abnormal type is greater than the third threshold, suspend execution of the target upgrade task .

In an exemplary embodiment, after controlling the upgrade strategy of the target upgrade task according to the upgrade times, the method further includes: when detecting that the target upgrade task is terminated abnormally, executing an abnormal alarm event, In order to notify the target object to check again the running state of the target upgrade task.

According to another aspect of the embodiment of the present application, there is also provided a device for determining an upgrade strategy, including: a determination module, configured to determine a target upgrade task to be configured; a configuration module, configured to configure the number of upgrades for the target upgrade task , wherein, the number of upgrades is the maximum number of upgrade operations allowed by the target upgrade task; the control module is configured to control the number of upgrades of the target upgrade task according to the number of upgrades when the target upgrade task is started Upgrade strategy.

According to yet another aspect of the embodiments of the present application, there is also provided a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, wherein the computer program is set to execute the above-mentioned upgrade strategy when running. Determine the method.

According to still another aspect of the embodiments of the present application, there is also provided an electronic device, including a memory, a processor, and a computer program stored on the memory and operable on the processor, wherein the above-mentioned processor executes the above-mentioned upgrade through the computer program How to determine the strategy.

Through this application, the target upgrade task to be configured is determined; the upgrade times are configured for the target upgrade task, wherein the upgrade times are the maximum number of upgrade operations allowed by the target upgrade task; when the target upgrade task is started In the case of , the upgrade policy of the target upgrade task is controlled according to the upgrade times. That is to say, by configuring the maximum number of upgrade operations allowed by the target upgrade task, and then controlling the upgrade strategy of the target upgrade task according to the maximum number of upgrade operations allowed, the above technical solution solves the problem of upgrade solutions in related technologies, and the security of the upgrade Reliability depends on human control, and the upgrade task may not be discovered and terminated in time if an abnormality occurs, which will cause the upgrade task to continue to affect more user equipment; the impact of abnormalities can be controlled within a certain range, thereby improving system stability and product quality. Experienced technical effects.

Description of drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description serve to explain the principles of the application.

In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, In other words, other drawings can also be obtained from these drawings without paying creative labor.

FIG. 1 is a schematic diagram of a hardware environment according to an optional method for determining an upgrade strategy according to an embodiment of the present application;

FIG. 2 is a flow chart of an optional method for determining an upgrade strategy according to an embodiment of the present application;

FIG. 3 is a schematic flowchart of an optional method for determining an upgrade strategy according to an embodiment of the present application;

FIG. 4 is a structural block diagram of an optional device for determining an upgrade strategy according to an embodiment of the present application;

Fig. 5 is another structural block diagram of an apparatus for determining an optional upgrade strategy according to an embodiment of the present application.

Detailed ways

In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiment of the application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiment of the application. Obviously, the described embodiment is only It is an embodiment of a part of the application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by persons of ordinary skill in the art without creative efforts shall fall within the scope of protection of this application.

It should be noted that the terms "first" and "second" in the description and claims of the present application and the above drawings are used to distinguish similar objects, but not necessarily used to describe a specific sequence or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances such that the embodiments of the application described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having", as well as any variations thereof, are intended to cover a non-exclusive inclusion, for example, a process, method, system, product or device comprising a sequence of steps or elements is not necessarily limited to the expressly listed instead, may include other steps or elements not explicitly listed or inherent to the process, method, product or apparatus.

According to an aspect of the embodiments of the present application, a method for determining an upgrade policy is provided. The method for determining the upgrade strategy is widely used in smart home (Smart Home), smart home, smart home device ecology, smart house (Intelligence House) ecology and other intelligent digital control application scenarios in the whole house. Optionally, in this embodiment, the above method for determining an upgrade policy may be applied to a hardware environment composed of multiple terminal devices 102 and servers 104 as shown in FIG. 1 . As shown in Figure 1, the server 104 is connected to a plurality of terminal devices 102 through the network, and can be used to provide services (such as application services, etc.) To provide data storage services for the server 104 , cloud computing and/or edge computing services may be configured on the server or independently of the server to provide data computing services for the server 104 .

The foregoing network may include but not limited to at least one of the following: a wired network and a wireless network. The above-mentioned wired network may include but not limited to at least one of the following: wide area network, metropolitan area network, and local area network, and the above-mentioned wireless network may include but not limited to at least one of the following: WIFI (Wireless Fidelity, Wireless Fidelity), Bluetooth. The terminal device 102 is not limited to PC, mobile phone, tablet computer, smart air conditioner, smart hood, smart refrigerator, smart oven, smart stove, smart washing machine, smart water heater, smart washing device, smart dishwasher, smart projection device , smart TV, smart drying rack, smart curtain, smart video, smart socket, smart audio, smart speaker, smart fresh air equipment, smart kitchen and bathroom equipment, smart bathroom equipment, smart sweeping robot, smart window cleaning robot, smart mopping robot, Smart air purification equipment, smart steamer, smart microwave oven, smart kitchen treasure, smart purifier, smart water dispenser, smart door lock, etc.

In this embodiment, a method for determining an upgrade strategy is provided, including but not limited to being applied to a computer terminal. FIG. 2 is a flow chart of a method for determining an upgrade strategy according to an embodiment of the present application. The process includes the following steps:

Step S202: Determine the target upgrade task to be configured;

Step S204: configuring the number of upgrades for the target upgrade task, wherein the number of upgrades is the maximum number of upgrade operations allowed by the target upgrade task;

Optionally, the number of upgrades can be configured for the target upgrade task through the upgrade policy configuration platform, or the number of upgrades can be remotely configured for the target upgrade task through the terminal, and sent to the upgrade strategy configuration platform through the cloud.

Step S206: When the target upgrade task is started, control the upgrade policy of the target upgrade task according to the upgrade times.

Through the above steps, determine the target upgrade task to be configured; configure the number of upgrades for the target upgrade task, wherein the upgrade times are the maximum number of upgrade operations allowed by the target upgrade task; when the target upgrade task is started In the case of , the upgrade policy of the target upgrade task is controlled according to the upgrade times. That is to say, by configuring the maximum number of upgrade operations allowed by the target upgrade task, and then controlling the upgrade strategy of the target upgrade task according to the maximum number of upgrade operations allowed, the above technical solution solves the problem of upgrade solutions in related technologies, and the security of the upgrade Reliability depends on human control, and the upgrade task may not be discovered and terminated in time if an abnormality occurs, which will cause the upgrade task to continue to affect more user equipment; the impact of abnormalities can be controlled within a certain range, thereby improving system stability and product quality. Experienced technical effects.

In an exemplary embodiment, controlling the upgrade policy of the target upgrade task according to the upgrade times includes: determining the current upgrade times of the target upgrade task on the specified device; when the current upgrade times are less than or equal to the In the case of the above upgrade times, it is determined that the target upgrade task is allowed to continue to upgrade on the designated device; when the current upgrade times are greater than the upgrade times, suspend the upgrade of the target upgrade task on the designated device operate.

Optionally, the number of devices to be upgraded (which may be an estimation result) is determined, and the number of upgrades configured for the target upgrade task is determined according to the number of devices to be upgraded. In order to ensure that the possible impact is minimized in the event of abnormal upgrades, when the number of devices to be upgraded is extremely large, one thousandth, one ten thousandth, etc. of the number can be selected as the upgrade times, or a smaller number within the number of devices to be upgraded can also be selected as the number of upgrades.

Exemplarily, if there are 10,000 devices to be upgraded, the number of upgrades configured for the target upgrade task may be one-thousandth of the number of devices to be upgraded, that is, 10 times; the number of upgrades may also be directly set to 50 times. Now set the number of upgrades to 50, and then when the specified device is executed, it is determined that the specified device is the Nth device on which the upgrade task is performed (that is, the upgrade task has been executed for the Nth time when the upgrade task is executed to the specified device) ), and then when N is less than or equal to 50, it is determined that the target upgrade task can be executed on the designated device; when N is greater than 50, it is determined that the target upgrade task cannot be executed on the designated device, and it is determined to suspend the target upgrade task at Upgrade operations on all remaining devices to be upgraded. It should be noted that the designated device may be any device among the devices to be upgraded.

In an exemplary embodiment, after controlling the upgrade policy of the target upgrade task according to the upgrade times, the method further includes: acquiring the upgrade success rate of the target upgrade task in the first historical time period; When the upgrade success rate is greater than the first threshold, the upgrade times are increased according to the upgrade increment index; when the upgrade success rate is less than or equal to the first threshold, the upgrade times are decreased according to the upgrade decrement index.

It can be understood that, after the upgrade task of the control target upgrades the devices to be upgraded with the number of upgrades, the number of successfully upgraded devices among the devices to be upgraded with the number of upgrades is obtained, and the success rate of the upgrade is calculated based on the set number of upgrades. Optionally, the first threshold can be set to 80%, then when the upgrade success rate is greater than 80%, the number of upgrades will be expanded according to the upgrade increment index. Optionally, the upgrade increment index can be set as a multiple, a percentage, etc., the present application The embodiment does not limit this. When the upgrade success rate is less than or equal to the first threshold, it is further determined whether the upgrade success rate is less than half of the first threshold, and if it is less than half of the first threshold, it is determined whether the corresponding relationship between the upgrade task and the device to be upgraded is set Errors (such as errors in the device identification and the version number of the upgrade task); it is also possible to reduce the number of upgrades according to the upgrade decrement index, and re-determine the success rate of the upgrade.

In an exemplary embodiment, expanding the number of upgrades according to the upgrade increment index includes: obtaining the historical upgrade success rate of the upgrade task in a second historical time period, wherein the second historical time period is in the Before the first historical time period; determine the upgrade success rate and the average upgrade success rate of the historical upgrade success rate, and expand the upgrade times according to the average upgrade success rate and the upgrade increment index.

Optionally, after the upgrade times are expanded according to the upgrade increment index, the upgrade success rate is used as the historical upgrade success rate and used to determine the next upgrade times. Optionally, in the case that the number of upgrades of the target upgrade task is expanded multiple times, determine multiple upgrade success rates corresponding to multiple historical time periods, determine the average upgrade success rate of the multiple upgrade success rates, and according to the The average upgrade success rate and the upgrade incremental index expand the number of upgrades. It can be understood that expanding the upgrade times according to the average upgrade success rate and the upgrade incremental index includes: expanding the upgrade times according to the product of the average upgrade success rate, the upgrade incremental index and the upgrade times.

In an exemplary embodiment, after the target upgrade task to be configured is determined, the method further includes: configuring an upgrade exception whitelist for the target upgrade task, wherein the upgrade exception whitelist includes a plurality of target upgrade tasks The identification of the task, the maximum number of upgrade operations allowed by the multiple target upgrade tasks is not configured; when the number of upgrade operations performed by the target upgrade task exceeds the second threshold, the target upgrade task is being executed Any device in the system will send out an alarm prompt.

It is understandable that there are target upgrade tasks with low upgrade risks, and target upgrade tasks with low risk are generally upgrade tasks that do not involve the main program of the device or device firmware. make an impact. Therefore, an upgrade exception whitelist can be set for multiple target upgrade tasks with low risk, and the identifiers generated or assigned to multiple target upgrade tasks when the target upgrade tasks are generated are recorded in the upgrade exception whitelist. Optionally, a second threshold can also be set for a low-risk target upgrade task, and the second threshold can be set as the number of devices to be upgraded, and then when the number of upgrades of the target upgrade task in the upgrade exception whitelist exceeds the second threshold In this case, it can be determined that the upgrade process is repeatedly executed, or that an error occurs in the upgrade process, and then an alarm prompt is executed.

In an exemplary embodiment, after determining the target upgrade task to be configured, the method further includes: configuring an upgrade exception blacklist for the target upgrade task, wherein the upgrade exception blacklist includes: one or more Abnormal types; obtain the number of occurrences of the one or more abnormal types in the process of performing the upgrade operation of the target upgrade task; in the case that the occurrence times of the target abnormal type is greater than the third threshold, suspend execution of the target upgrade task .

Optionally, record the target upgrade task in the upgrade exception blacklist, and then count it in the upgrade times The number of occurrences of any abnormal type, and in the case that the number of occurrences of the target abnormal type is greater than the third threshold, suspend execution of the target upgrade task.

In an exemplary embodiment, after controlling the upgrade strategy of the target upgrade task according to the upgrade times, the method further includes: when detecting that the target upgrade task is terminated abnormally, executing an abnormal alarm event, In order to notify the target object to check again the running state of the target upgrade task.

Optionally, executing the abnormal alarm event includes: sending abnormal alarm information to the terminal of the target object, or broadcasting the abnormal alarm event by voice.

Apparently, the above-described embodiments are only some of the embodiments of the present application, rather than all the embodiments. In order to better understand the method for determining the above-mentioned upgrade strategy, the above-mentioned process is described below in conjunction with an embodiment, but it is not used to limit the technical solution of the embodiment of the present application, specifically:

Equipment upgrade is a high-risk operation, in order to enhance the process control of the OTA (Over-the-Air Technology, air download technology) process, improve the security of equipment upgrades, improve user experience, and enhance product competitiveness. Problems in equipment upgrades lead to unusable customer equipment, which in turn causes property losses to customers and the company, and affects product experience and brand image. Improving the reliability and security of the OTA process is very important. Therefore, it is necessary to pay attention to details and strengthen process control in the configuration and control links.

Therefore, in the implementation of the upgrade task, especially when the customer equipment is upgraded with high risk or large-scale upgrade, in order to prevent unexpected and unpredictable problems from causing large batches of abnormal equipment upgrades and causing serious production accidents, this application can be implemented as an option. For example, you can configure and limit the number of upgrades according to different scenarios. Configuring and limiting the number of upgrades includes: configuring the number of upgrades to be executed and configuring the number of abnormal upgrades, so as to gradually upgrade customer devices, detect problems in time, and terminate the upgrade task in time to prevent further spread of problems Effect.

Optionally, FIG. 3 is a schematic flowchart of an optional method for determining an upgrade strategy according to an embodiment of the present application. As shown in FIG. 3 , it has the following steps:

Step S301: Updating task configuration.

Step S301 also includes: step S3011: normally configure related configurations of the upgrade task; step S3012: limit the upgradeable times of the upgrade task; step S3013: configure a white list of upgrade exceptions.

Step S302: the task starts.

Step S303: Perform an upgrade operation on the device to be upgraded according to the upgrade task.

Step S304: Updating records.

Step S305: Determine whether there is an upgrade restriction, and if there is an upgrade restriction, proceed to step S306 and step S309 at the same time; if there is no upgrade restriction, the upgrade task ends.

It should be noted that the upgrade restriction includes the limit on the number of upgrades, upgrade exceptions, and the like.

Step S306: Monitoring the upgrade task by the controller for limiting the number of upgrade times.

Step S307: Determine whether the upgrade times limit controller in step S306 is triggered, if it is triggered, go to step S308; if it is not triggered, the upgrade task ends.

Step S308: the task is suspended.

Step S309: Monitor the upgrade task through the upgrade exception controller.

Step S310: Determine whether the upgrade abnormal controller in step S309 is triggered, if it is triggered, go to step S311; if not, the upgrade task ends.

Step S308: The task is suspended and an alarm is issued.

After performing step S308 and/or step S311, the upgrade task ends.

Based on the above steps, it can be understood that the platform provides and executes the configuration of limiting the number of upgrades. In the upgrade task configuration stage, the configurator can configure a fixed limit number of upgrade times for the upgrade task. After each task is started, the number of devices allowed to be upgraded is the number corresponding to the limit number of upgrade times (for example, if the limit number of upgrade times is 50, then The number of devices performing the upgrade task is 50), and the upgrade task will be automatically suspended after the number of upgrade times exceeds the limit, waiting for further confirmation by the configurator and restarting the task to continue the upgrade. If the configurator does not configure the upgrade task, it means that the task does not limit the number of upgrades. Generally speaking, the upgrade task that is not configured is a low-risk upgrade task, and a reminder needs to be given if the risk is high.

Further, 1) the platform also provides an upgrade times incremental configuration strategy, and in the upgrade task configuration stage, set the initial upgrade times, the qualified upgrade rate index, and the upgrade times incremental index. When the number of upgrades in the first stage is reached and the success rate of the upgrade reaches the standard, the number of upgrades will be automatically expanded according to the upgrade increment index to continue to upgrade efficiently.

2) The platform can configure an upgrade exception blacklist for the upgrade task, which is used to limit the number of abnormal upgrades. Once certain specific exceptions occur n times during the execution of the upgrade task, the upgrade task will be automatically suspended to facilitate manual follow-up analysis and processing.

3) The platform also provides an upgrade termination alarm. Once the task is terminated abnormally in the above steps, an OTA upgrade abnormal alarm will be triggered to notify relevant personnel to deal with it in a timely manner.

Furthermore, the embodiment of this application has the following key points: OTA is a high-risk operation. Once the upgrade task is started, it will be effective for all matching devices in the entire network. Therefore, it is necessary to refine the upgrade process for different scenarios. The optional embodiment of this application will upgrade The number of upgrade times for tasks is limited, including the control of the number of execution upgrades and the number of abnormal upgrades. Among them, the control of the number of upgrades is used to finely control the upgrade task, control the progress and process of the upgrade, find and deal with problems in time, and prevent problems before they happen; the control of the number of abnormal upgrades is used to automatically start the protection when the system upgrades abnormally The mechanism suspends the upgrade task and triggers an alarm to prevent the further spread of the problem caused by the abnormality, and to control the impact within a certain range.

Furthermore, if the OTA device upgrade does not control the number of upgrades, but finds and solves the problem artificially, the timeliness of problem handling will be poor. If there are too many abnormal failures during the upgrade execution, the user experience will be poor. Once the user equipment is upgraded and unavailable, it will endanger bigger. Based on this, an optional embodiment of the present application strictly controls the upgrade process, limits the number of upgrades, first upgrades the user equipment in a small area, and then upgrades the equipment in a large area or comprehensively after it is stable and correct. The optional embodiment of this application can also detect abnormalities in advance, monitor the abnormality in advance according to the configurable abnormality upgrade limit, trigger the critical value to automatically terminate the upgrade task, facilitate subsequent personnel to deal with, control the impact of abnormalities and accidents within a certain range, and improve the system Stability and product experience.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or the part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to make a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) execute the method of each embodiment of the present application.

This embodiment also provides a device for determining an upgrade strategy, which is used to implement the above embodiments and preferred implementation modes, and those that have already been described will not be described again. As used below, the term "module" may be a combination of software and/or hardware that realizes a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.

Fig. 4 is a structural block diagram of an optional device for determining an upgrade strategy according to an embodiment of the present application, and the device includes:

A determining module 42, configured to determine the target upgrade task to be configured;

The configuration module 44 is configured to configure the number of upgrades for the target upgrade task, wherein the number of upgrades is the maximum number of upgrade operations allowed by the target upgrade task;

The control module 46 is configured to control the upgrade strategy of the target upgrade task according to the upgrade times when the target upgrade task is started.

Through the above-mentioned device, determine the target upgrade task to be configured; configure the upgrade times for the target upgrade task, wherein the upgrade times are the maximum number of upgrade operations allowed by the target upgrade task; when the target upgrade task is started In the case of , the upgrade policy of the target upgrade task is controlled according to the upgrade times. That is to say, by configuring the maximum number of upgrade operations allowed by the target upgrade task, and then controlling the upgrade strategy of the target upgrade task according to the maximum number of upgrade operations allowed, the above technical solution solves the problem of upgrade solutions in related technologies, and the security of the upgrade Reliability depends on human control, and the upgrade task may not be discovered and terminated in time if an abnormality occurs, which will cause the upgrade task to continue to affect more user equipment; the impact of abnormalities can be controlled within a certain range, thereby improving system stability and product quality. Experienced technical effects.

In an exemplary embodiment, the control module 46 is further configured to determine the current upgrade times of the target upgrade task on the designated device; when the current upgrade times are less than or equal to the upgrade times, determine the The target upgrade task is allowed to continue the upgrade on the designated device; in the case that the current upgrade times are greater than the upgrade times, the upgrade operation of the target upgrade task on the designated device is suspended.

Optionally, the number of devices to be upgraded (which may be an estimation result) is determined, and the number of upgrades configured for the target upgrade task is determined according to the number of devices to be upgraded. In order to ensure that the possible impact is minimized in the event of abnormal upgrades, when the number of devices to be upgraded is extremely large, one thousandth, one ten thousandth, etc. of the number can be selected as the upgrade times, or a smaller number within the number of devices to be upgraded can also be selected as the number of upgrades.

Exemplarily, if there are 10,000 devices to be upgraded, the number of upgrades configured for the target upgrade task may be one-thousandth of the number of devices to be upgraded, that is, 10 times; the number of upgrades may also be directly set to 50 times. Now set the number of upgrades to 50, and then when the specified device is executed, it is determined that the specified device is the Nth device on which the upgrade task is performed (that is, the upgrade task has been executed for the Nth time when the upgrade task is executed to the specified device) ), and then when N is less than or equal to 50, it is determined that the target upgrade task can be executed on the designated device; when N is greater than 50, it is determined that the target upgrade task cannot be executed on the designated device, and it is determined to suspend the target upgrade task at Upgrade operations on all remaining devices to be upgraded. It should be noted that the designated device may be any device among the devices to be upgraded.

In an exemplary embodiment, as shown in FIG. 5 , the above-mentioned device further includes an expansion module 58, configured to acquire the upgrade success rate of the target upgrade task in the first historical time period; In the case of a threshold, the number of upgrades is increased according to the upgrade increment index; when the success rate of the upgrade is less than or equal to the first threshold, the number of upgrades is decreased according to the upgrade decrement index.

It can be understood that, after the upgrade task of the control target upgrades the devices to be upgraded with the number of upgrades, the number of successfully upgraded devices among the devices to be upgraded with the number of upgrades is obtained, and the success rate of the upgrade is calculated based on the set number of upgrades. Optionally, the first threshold can be set to 80%, then when the upgrade success rate is greater than 80%, the number of upgrades will be expanded according to the upgrade increment index. Optionally, the upgrade increment index can be set as a multiple, a percentage, etc., the present application The embodiment does not limit this. When the upgrade success rate is less than or equal to the first threshold, it is further determined whether the upgrade success rate is less than half of the first threshold, and if it is less than half of the first threshold, it is determined whether the corresponding relationship between the upgrade task and the device to be upgraded is set Errors (such as errors in the device identification and the version number of the upgrade task); it is also possible to reduce the number of upgrades according to the upgrade decrement index, and re-determine the success rate of the upgrade.

In an exemplary embodiment, the expansion module 58 is further configured to obtain the historical upgrade success rate of the upgrade task in the second historical time period, wherein the second historical time period is within the first historical time period Before: determining the upgrade success rate and the average upgrade success rate of the historical upgrade success rate, expanding the number of upgrades according to the average upgrade success rate and the upgrade increment index.

Optionally, after the upgrade times are expanded according to the upgrade increment index, the upgrade success rate is used as the historical upgrade success rate and used to determine the next upgrade times. Optionally, in the case that the number of upgrades of the target upgrade task is expanded multiple times, determine multiple upgrade success rates corresponding to multiple historical time periods, determine the average upgrade success rate of the multiple upgrade success rates, and according to the The average upgrade success rate and the upgrade incremental index expand the number of upgrades. It can be understood that expanding the upgrade times according to the average upgrade success rate and the upgrade incremental index includes: expanding the upgrade times according to the product of the average upgrade success rate, the upgrade incremental index and the upgrade times.

In an exemplary embodiment, after determining the target upgrade task to be configured, the configuration module 44 is further configured to configure an upgrade exception whitelist for the target upgrade task, wherein the upgrade exception whitelist includes multiple targets The identification of the upgrade task, the maximum number of upgrade operations allowed by the multiple target upgrade tasks is not configured; when the number of upgrade operations performed by the target upgrade task exceeds the second threshold, the target upgrade is being executed Any device in the task sends out an alarm prompt.

It is understandable that there are target upgrade tasks with low upgrade risk, and target upgrade tasks with low risk generally do not involve the upgrade tasks of the main program of the device and the device firmware. That is to say, such upgrade tasks will not affect the running make an impact. Therefore, an upgrade exception whitelist can be set for multiple target upgrade tasks with low risk, and the identifiers generated or assigned to multiple target upgrade tasks when the target upgrade tasks are generated are recorded in the upgrade exception whitelist. Optionally, a second threshold can also be set for a low-risk target upgrade task, and the second threshold can be set as the number of devices to be upgraded, and then when the number of upgrades of the target upgrade task in the upgrade exception whitelist exceeds the second threshold In this case, it can be determined that the upgrade process is repeatedly executed, or that an error occurs in the upgrade process, and then an alarm prompt is executed.

In an exemplary embodiment, after determining the target upgrade task to be configured, the configuration module 44 is further configured to configure an upgrade exception blacklist for the target upgrade task, wherein the upgrade exception blacklist includes: one or A plurality of exception types; obtaining the number of occurrences of the one or more exception types during the upgrade operation of the target upgrade task; when the number of occurrences of the target exception type is greater than a third threshold, suspending the execution of the target upgrade Task.

Optionally, record the target upgrade task in the upgrade exception blacklist, and then count it in the upgrade times The number of occurrences of any abnormal type, and in the case that the number of occurrences of the target abnormal type is greater than the third threshold, suspend execution of the target upgrade task.

In an exemplary embodiment, after controlling the upgrade strategy of the target upgrade task according to the upgrade times, the control module 46 is further configured to execute an abnormal alarm event when detecting that the target upgrade task terminates abnormally , to notify the target object to check again the running status of the target upgrade task.

Optionally, executing the abnormal alarm event includes: sending abnormal alarm information to the terminal of the target object, or broadcasting the abnormal alarm event by voice.

Embodiments of the present application also provide a computer-readable storage medium, in which a computer program is stored, wherein the computer program is set to execute the steps in any one of the above method embodiments when running.

Optionally, in this embodiment, the above-mentioned storage medium may be configured to store a computer program for performing the following steps:

S1. Determine the target upgrade task to be configured;

S2. Configure an upgrade count for the target upgrade task, where the upgrade count is the maximum number of upgrade operations allowed by the target upgrade task;

S3. When the target upgrade task is started, control the upgrade policy of the target upgrade task according to the upgrade times.

In an exemplary embodiment, the above-mentioned computer-readable storage medium may include but not limited to: U disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM) , mobile hard disk, magnetic disk or optical disk and other media that can store computer programs.

For specific examples in this embodiment, reference may be made to the examples described in the foregoing embodiments and exemplary implementation manners, and details will not be repeated here in this embodiment.

An embodiment of the present application also provides an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments.

Optionally, in this embodiment, the above-mentioned processor may be configured to execute the following steps through a computer program:

S1. Determine the target upgrade task to be configured;

S2. Configure an upgrade count for the target upgrade task, where the upgrade count is the maximum number of upgrade operations allowed by the target upgrade task;

S3. When the target upgrade task is started, control the upgrade policy of the target upgrade task according to the upgrade times.

In an exemplary embodiment, the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.

For specific examples in this embodiment, reference may be made to the examples described in the foregoing embodiments and exemplary implementation manners, and details will not be repeated here in this embodiment.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned application can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network composed of multiple computing devices In fact, they can be implemented in program code executable by a computing device, and thus, they can be stored in a storage device to be executed by a computing device, and in some cases, can be executed in an order different from that shown here. Or described steps, or they are fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present application is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present application. It should be pointed out that for those of ordinary skill in the art, without departing from the principle of the present application, some improvements and modifications can also be made. These improvements and modifications are also It should be regarded as the protection scope of this application.

Claims (10)

1. A method for determining an upgrade policy, comprising:

determining a target upgrading task to be configured;

Configuring upgrade times for the target upgrade task, wherein the upgrade times are the maximum times of the target upgrade task allowed to execute upgrade operation;

and under the condition that the target upgrading task is started, controlling the upgrading strategy of the target upgrading task according to the upgrading times.

2. The method according to claim 1, wherein controlling the upgrade policy of the target upgrade task according to the number of upgrades comprises:

determining the current upgrading times of the target upgrading task in the appointed equipment;

determining that the target upgrading task allows the designated equipment to continue upgrading under the condition that the current upgrading frequency is smaller than or equal to the upgrading frequency;

and under the condition that the current upgrading times are larger than the upgrading times, suspending the upgrading operation of the target upgrading task on the appointed equipment.

3. The method according to claim 1, wherein after controlling the upgrade policy of the target upgrade task according to the number of upgrades, the method further comprises:

acquiring the upgrading success rate of the target upgrading task in a first historical time period;

Under the condition that the upgrade success rate is greater than a first threshold value, expanding the upgrade times according to an upgrade increment index;

and under the condition that the upgrade success rate is smaller than or equal to a first threshold value, reducing the upgrade times according to the upgrade decremental index.

4. The method of claim 3, wherein expanding the number of upgrades according to an upgrade increment index comprises:

acquiring a historical upgrade success rate of the upgrade task in a second historical time period, wherein the second historical time period is before the first historical time period;

and determining the average upgrading success rate of the upgrading success rate and the historical upgrading success rate, and expanding the upgrading times according to the average upgrading success rate and the upgrading increment index.

5. The method for determining an upgrade policy according to claim 1, wherein after determining a target upgrade task to be configured, the method further comprises:

configuring an upgrade exception white list for the target upgrade task, wherein the upgrade exception white list comprises identifiers of a plurality of target upgrade tasks, and the maximum number of times that the plurality of target upgrade tasks allow to execute upgrade operations is not configured;

And under the condition that the upgrading times of the target upgrading task for executing the upgrading operation exceeds a second threshold value, sending out an alarm prompt through any device which is executing the target upgrading task.

6. The method of determining an upgrade policy according to claim 4, wherein after determining a target upgrade task to be configured, the method further comprises:

configuring an upgrade exception blacklist for the target upgrade task, wherein the upgrade exception blacklist comprises: one or more exception types;

acquiring the occurrence times of the one or more abnormal types in the process of executing the upgrading operation by the target upgrading task;

and if the occurrence number of the target abnormal type is greater than a third threshold value, suspending executing the target upgrading task.

7. The method according to claim 1, wherein after controlling the upgrade policy of the target upgrade task according to the number of upgrades, the method further comprises:

and under the condition that the abnormal termination of the target upgrading task is detected, executing an abnormal alarm event to inform a target object to detect the running state of the target upgrading task again.

8. An upgrade policy determination apparatus, comprising:

the determining module is used for determining a target upgrading task to be configured;

the configuration module is used for configuring the upgrade times for the target upgrade task, wherein the upgrade times are the maximum times of the target upgrade task allowed to execute upgrade operation;

and the control module is used for controlling the upgrading strategy of the target upgrading task according to the upgrading times under the condition that the target upgrading task is started.

9. A computer-readable storage medium, characterized in that the computer-readable storage medium comprises a stored program, wherein the program when run performs the method of any one of claims 1 to 7.

10. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to execute the method according to any of claims 1 to 7 by means of the computer program.