Anti-congestion remote upgrading method and device, computer device and storage medium

Abstract

Embodiments of the present application disclose a congestion prevention remote upgrading method and device, computer equipment and a storage medium. The method comprises: obtaining a cell ID to be upgraded; determining whether the cell ID to be upgraded is the first time to set the queue number of the day; if the cell ID to be upgraded is the first time to set the queue number of the day, then adaptively adjusting the queue number according to the congestion situation; when it is necessary to remotely upgrade the equipment in the cell to be upgraded, determining whether the equipment of the cell to be upgraded is offline; if the equipment of the cell to be upgraded is not offline, then obtaining the queue state corresponding to the cell to be upgraded; determining whether the queue state is an idle state; if the queue state is an idle state, then dispatching the upgrading task to the queue, and remotely upgrading the equipment of the cell to be upgraded through the queue. By implementing the method of the embodiments of the present application, the problem that a large number of devices in the same cell simultaneously issue upgrading tasks, exceed the air interface paging capability, and cause network congestion or even avalanche can be prevented.

Description

Technical Field

[0001] This invention relates to the Internet of Things, and more specifically to a method, apparatus, computer equipment, and storage medium for remote congestion prevention upgrades. Background Technology

[0002] When users remotely upgrade NB (Narrow Band Internet of Things) devices, simultaneously sending upgrade tasks to multiple devices connected to the same NB base station in the same cell can exceed the air interface paging capacity, causing network congestion and packet loss, thus reducing the success rate of remote upgrades. To avoid congestion, users need to manually distribute the upgrade task creation operations, which is labor-intensive, lacks precision, and results in a poor user experience. Furthermore, upgrade tasks fail to be sent when the device is offline; once the device is online, the upgrade task needs to be manually created and executed again, leading to a severely poor user experience, ineffective upgrades, and wasted resources.

[0003] Therefore, it is necessary to design a new method to prevent a large number of devices in the same cell from simultaneously issuing upgrade tasks, exceeding the air interface paging capacity, and causing network congestion or even a cascading failure. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of the prior art and provide a method, apparatus, computer equipment and storage medium for remote upgrades to prevent congestion.

[0005] To achieve the above objectives, the present invention adopts the following technical solution: a congestion-prevention remote upgrade method, comprising:

[0006] Obtain the ID of the community to be upgraded;

[0007] Determine whether the cell ID to be upgraded is the first queue set for that day;

[0008] If the cell ID to be upgraded is the first time the queue number is set on that day, the queue number will be adaptively adjusted according to the congestion situation.

[0009] When it is necessary to remotely upgrade the equipment in the community to be upgraded, it is determined whether the equipment in the community to be upgraded is offline;

[0010] If the devices in the cell to be upgraded are not offline, then obtain the queue status corresponding to the cell to be upgraded;

[0011] Determine whether the queue is in an idle state;

[0012] If the queue is in an idle state, upgrade tasks are assigned to the queue, and the equipment in the cell to be upgraded is remotely upgraded through the queue.

[0013] The further technical solution is as follows: after determining whether the cell ID to be upgraded is the first time the queue number is set on that day, it also includes:

[0014] If the ID of the cell to be upgraded is not the first time the queue number is set on that day, then the already set queue number is used for queue management, and the step of determining whether the device in the cell to be upgraded is offline is executed when remote upgrade of the device in the cell to be upgraded is required.

[0015] The further technical solution is as follows: the congestion situation refers to the failure rate of the coap instruction within a 244s window period.

[0016] The further technical solution is as follows: the adaptive adjustment of the queue number according to the congestion situation includes:

[0017] Set the number of queues based on the congestion situation.

[0018] A further technical solution is as follows: setting the queue number according to the congestion situation includes:

[0019] Based on the congestion situation, the number of queues is set as int((1-coap instruction failure rate))*5+1, where the coap instruction failure rate refers to the failure rate of coap instructions within a 244s window period.

[0020] A further technical solution is as follows: setting the queue number according to the congestion situation includes:

[0021] When the failure rate of the coap instruction is less than 20% within a 244s window, the number of queues is set to 5; when the failure rate of the coap instruction is not less than 20% but less than 40% within a 244s window, the number of queues is set to 4; when the failure rate of the coap instruction is not less than 40% but less than 60% within a 244s window, the number of queues is set to 3; when the failure rate of the coap instruction is not less than 60% but less than 80% within a 244s window, the number of queues is set to 2; and when the failure rate of the coap instruction is not less than 80% within a 244s window, the number of queues is set to 1.

[0022] The further technical solution is as follows: after determining whether the device in the cell to be upgraded is offline, it also includes:

[0023] If the equipment in the cell to be upgraded is offline, then offline upgrade processing is performed, and the determination of whether the equipment in the cell to be upgraded is offline is executed.

[0024] The present invention also provides a congestion-prevention remote upgrade device, comprising:

[0025] The ID acquisition unit is used to obtain the ID of the cell to be upgraded.

[0026] The first judgment unit is used to determine whether the cell ID to be upgraded is the first time the queue number is set on that day;

[0027] An adjustment unit is used to adaptively adjust the queue number based on congestion if the ID of the cell to be upgraded is the first time the queue number is set on that day.

[0028] The second judgment unit is used to determine whether the equipment in the cell to be upgraded is offline when it is necessary to remotely upgrade the equipment in the cell to be upgraded.

[0029] The status acquisition unit is used to acquire the queue status corresponding to the cell to be upgraded if the device in the cell to be upgraded is not offline.

[0030] The third judgment unit is used to determine whether the queue state is an idle state;

[0031] The upgrade unit is used to assign upgrade tasks to the queue if the queue status is idle, and to remotely upgrade the equipment of the cell to be upgraded through the queue.

[0032] The present invention also provides a computer device, the computer device including a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the above-described method.

[0033] The present invention also provides a storage medium storing a computer program that, when executed by a processor, implements the above-described method.

[0034] The beneficial effects of this invention compared with the prior art are as follows: This invention determines whether the ID of the cell to be upgraded is the first time the queue number is set on the same day, and adaptively adjusts the queue number according to the congestion situation. For the device that needs to be upgraded, it determines whether its online status and whether to perform the upgrade operation based on whether the queue is idle. When the device is offline, it can set an offline upgrade operation and perform remote upgrades in an orderly manner. This prevents a large number of devices in the same cell from simultaneously issuing upgrade tasks, exceeding the air interface paging capacity, and causing network congestion or even avalanche.

[0035] The present invention will be further described below with reference to the accompanying drawings and specific embodiments. Attached Figure Description

[0036] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0037] Figure 1 This is a schematic diagram illustrating an application scenario of the anti-congestion remote upgrade method provided in this embodiment of the invention.

[0038] Figure 2 A flowchart illustrating the congestion prevention remote upgrade method provided in an embodiment of the present invention;

[0039] Figure 3 A schematic block diagram of the anti-congestion remote upgrade device provided in an embodiment of the present invention;

[0040] Figure 4 A schematic block diagram of a computer device provided for an embodiment of the present invention. Detailed Implementation

[0041] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0042] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0043] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the invention. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0044] It should also be further understood that the term "and / or" as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0045] Please see Figure 1 and Figure 2 , Figure 1 This is a schematic diagram illustrating an application scenario of the anti-congestion remote upgrade method provided in an embodiment of the present invention. Figure 2 This is a schematic flowchart illustrating the congestion prevention remote upgrade method provided in an embodiment of the present invention. This congestion prevention remote upgrade method is applied to a server. The server interacts with the NB device, specifically as follows... Figure 1As shown, intelligent discrete implementation of adaptive queues is used for batch remote upgrade tasks; at the same time, for offline devices, the upgrade task is automatically triggered when the device comes online, ultimately improving the success rate of upgrade tasks and the utilization rate of platform resources.

[0046] Figure 2 This is a flowchart illustrating the congestion-prevention remote upgrade method provided in an embodiment of the present invention. Figure 2 As shown, the method includes the following steps S110 to S200.

[0047] S110, Obtain the ID of the cell to be upgraded.

[0048] In this embodiment, the cell ID to be upgraded refers to the identifier number corresponding to the unit formed by dividing the cell into one dimension.

[0049] For devices accessing NB cellular networks, upgrading tasks are managed at the cell level, which can solve the problem of low success rate of upgrading tasks under NB narrowband conditions.

[0050] S120. Determine whether the ID of the cell to be upgraded is the first time the queue number is set on that day.

[0051] In this embodiment, operations such as whether to set the number of queues for each cell are recorded in the queue setting management table. The table can be used to determine whether the number of queues for a cell has been set on that day or has not yet been set.

[0052] S130. If the cell ID to be upgraded is the first time the queue number is set on the same day, the queue number will be adaptively adjusted according to the congestion situation.

[0053] In this embodiment, congestion is determined based on the failure rate of coap commands within a 244-second window. The reason for choosing 244 seconds is that the platform uses a 122-second window to determine if a device's coap command has timed out.

[0054] Each cell can adaptively set the number of active queues instead of setting a static value; this allows for better utilization of bandwidth and control over the success rate of upgrade tasks.

[0055] In this embodiment, the number of queues is set according to the congestion situation.

[0056] Specifically, the number of queues is set according to the congestion situation using the formula: queue number = int((1-coap instruction failure rate))*5+1, where the coap instruction failure rate refers to the coap instruction failure rate within a 244s window period.

[0057] Preferably, when the failure rate of the coap instruction within a 244s window is less than 20%, the number of queues is set to 5; when the failure rate of the coap instruction within a 244s window is not less than 20% but less than 40%, the number of queues is set to 4; when the failure rate of the coap instruction within a 244s window is not less than 40% but less than 60%, the number of queues is set to 3; when the failure rate of the coap instruction within a 244s window is not less than 60% but less than 80%, the number of queues is set to 2; and when the failure rate of the coap instruction within a 244s window is not less than 80%, the number of queues is set to 1.

[0058] The default queue size for remote upgrades is 5; it can be adaptively set between 5 and 1, where queue size = int((1 - coap instruction failure rate)) * 5 + 1. In this embodiment, the coap instruction failure rate is between 0-20%, so the active queue size is set to 5. After the device upgrade task starts, the cell ID corresponding to the device is obtained. Based on the cell ID, the queue size setting management table is queried to determine if this is the first time the queue size has been set that day. If this cell ID is undergoing its first device upgrade, there will be no record in the queue size setting management table, and the queue size will be the default value of 5. If this cell ID has already been used for device upgrades, it will be determined again whether this is the first time the queue size has been set that day. If so, the queue size needs to be adaptively adjusted according to the congestion situation; otherwise, the queue size will not be adjusted. The adaptive adjustment of the queue size is currently based on a daily unit to control performance and resources.

[0059] S140. When it is necessary to remotely upgrade the equipment in the cell to be upgraded, determine whether the equipment in the cell to be upgraded is offline.

[0060] In this embodiment, when a remote upgrade operation is issued to a certain area, the queue status is checked. If the queue is idle, the upgrade operation is issued directly; otherwise, a queuing operation is performed. Once the ongoing upgrade task is completed, it is dequeued, and the next task in the queue is automatically started.

[0061] S150. If the device in the cell to be upgraded is not offline, then obtain the queue status corresponding to the cell to be upgraded.

[0062] In this embodiment, the queue status corresponding to the cell to be upgraded can be obtained from the queue setting management table. The queue setting management table records the queue status. When one element in the queue switches from a busy state to a waiting state, its current status will be recorded in the table. Once the upgrade task in progress is completed, it will be dequeued and the next task in the queue will be automatically started.

[0063] S160. Determine whether the queue status is idle.

[0064] S170. If the queue is in an idle state, then the queue is assigned an upgrade task, and the equipment of the cell to be upgraded is remotely upgraded through the queue.

[0065] In this embodiment, when performing a remote upgrade, the device information is first checked. If the device information is complete and the device is functioning normally, an upgrade task can be assigned to the queue, and the device in the cell to be upgraded can be remotely upgraded using the queue. After the upgrade is completed, the device version is obtained, and the relevant resources in the queue are released. If the remote upgrade fails, or the device information does not meet the requirements, or the task assignment fails, a retry can be performed. In this embodiment, automatic retry can be set when the device information does not meet the requirements or the task assignment fails.

[0066] S180. If the ID of the cell to be upgraded is not the first time the queue number is set on the same day, then the already set queue number is used for queue management, and step S140 is executed.

[0067] In this embodiment, the number of queues is adaptively adjusted according to the congestion situation.

[0068] S190. If the queue state is not idle, then a waiting operation is performed, and step S150 is executed.

[0069] S200. If the equipment in the cell to be upgraded is offline, then perform offline upgrade processing and execute step S140.

[0070] When a remote upgrade is initiated, it checks if the device is offline. If offline, it performs offline pending upgrade processing. When the device comes online, the offline pending upgrade task is triggered. Offline pending upgrade processing refers to setting the execution of step S15 when the device meets the conditions for coming online.

[0071] For offline device upgrade tasks, the upgrade task can be automatically triggered when the device goes online, which can reduce the waste of platform resources.

[0072] The aforementioned anti-congestion remote upgrade method determines whether the cell ID to be upgraded is setting the queue number for the first time that day, and adaptively adjusts the queue number according to the congestion situation. For the device that needs to be upgraded, it determines whether its online status and whether to perform the upgrade operation based on the queue's idle status. When the device is offline, it can set an offline upgrade operation and perform remote upgrades in an orderly manner. This prevents a large number of devices in the same cell from simultaneously issuing upgrade tasks, exceeding the air interface paging capacity, and causing network congestion or even avalanche.

[0073] Figure 3 This is a schematic block diagram of a congestion prevention remote upgrade device 300 provided in an embodiment of the present invention. Figure 3As shown, corresponding to the above-described anti-congestion remote upgrade method, the present invention also provides an anti-congestion remote upgrade device 300. This anti-congestion remote upgrade device 300 includes a unit for performing the above-described anti-congestion remote upgrade method, and the device can be configured in a server. Specifically, please refer to... Figure 3 The anti-congestion remote upgrade device 300 includes an ID acquisition unit 301, a first judgment unit 302, an adjustment unit 303, a second judgment unit 304, a status acquisition unit 305, a third judgment unit 306, and an upgrade unit 307.

[0074] ID acquisition unit 301 is used to acquire the ID of the cell to be upgraded; first judgment unit 302 is used to judge whether the ID of the cell to be upgraded is the first time the queue number is set on the same day; adjustment unit 303 is used to adaptively adjust the queue number according to the congestion situation if the ID of the cell to be upgraded is the first time the queue number is set on the same day; second judgment unit 304 is used to judge whether the equipment in the cell to be upgraded is offline when remote upgrade of the equipment in the cell to be upgraded is required; status acquisition unit 305 is used to acquire the queue status corresponding to the cell to be upgraded if the equipment in the cell to be upgraded is not offline; third judgment unit 306 is used to judge whether the queue status is idle; if the queue status is not idle, a waiting operation is performed, and the acquisition of the queue status corresponding to the cell to be upgraded is performed. Upgrade unit 307 is used to assign upgrade tasks to the queue if the queue status is idle, and remotely upgrade the equipment in the cell to be upgraded through the queue.

[0075] In one embodiment, the congestion-prevention remote upgrade method further includes:

[0076] The management unit 308 is used to manage queues by using the already set queue number if the ID of the cell to be upgraded is not the first time the queue number is set on the same day, and to determine whether the device in the cell to be upgraded is offline when remote upgrade of the device in the cell to be upgraded is required.

[0077] The offline setting unit 309 is used to perform offline upgrade processing if the equipment of the cell to be upgraded is offline, and to perform the determination of whether the equipment of the cell to be upgraded is offline.

[0078] In one embodiment, the adjustment unit 303 is used to set the number of queues according to the congestion situation.

[0079] In one embodiment, the adjustment unit 303 is used to set the number of queues according to the congestion situation using the formula: queue number = int((1-coap instruction failure rate))*5+1, where the coap instruction failure rate refers to the coap instruction failure rate within a 244s window period.

[0080] In one embodiment, the adjustment unit 303 is configured to set the queue number to 5 when the failure rate of the coap instruction within a 244s window period is less than 20%; set the queue number to 4 when the failure rate of the coap instruction within a 244s window period is not less than 20% but less than 40%; set the queue number to 3 when the failure rate of the coap instruction within a 244s window period is not less than 40% but less than 60%; set the queue number to 2 when the failure rate of the coap instruction within a 244s window period is not less than 60% but less than 80%; and set the queue number to 1 when the failure rate of the coap instruction within a 244s window period is not less than 80%.

[0081] It should be noted that those skilled in the art can clearly understand that the specific implementation process of the above-mentioned anti-congestion remote upgrade device 300 and each unit can be referred to the corresponding description in the foregoing method embodiments. For the sake of convenience and brevity, it will not be repeated here.

[0082] The aforementioned anti-congestion remote upgrade device 300 can be implemented as a computer program, which can, for example... Figure 4 It runs on the computer device shown.

[0083] Please see Figure 4 , Figure 4 This is a schematic block diagram of a computer device provided in an embodiment of this application. The computer device 500 can be a server, wherein the server can be a standalone server or a server cluster composed of multiple servers.

[0084] See Figure 4 The computer device 500 includes a processor 502, a memory, and a network interface 505 connected via a system bus 501. The memory may include a non-volatile storage medium 503 and internal memory 504.

[0085] The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. The computer program 5032 includes program instructions that, when executed, cause the processor 502 to perform a congestion-resistant remote upgrade method.

[0086] The processor 502 provides computing and control capabilities to support the operation of the entire computer device 500.

[0087] The internal memory 504 provides an environment for the execution of the computer program 5032 in the non-volatile storage medium 503. When the computer program 5032 is executed by the processor 502, the processor 502 can execute a congestion-resistant remote upgrade method.

[0088] This network interface 505 is used for network communication with other devices. Those skilled in the art will understand that... Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device 500 to which the present application is applied. The specific computer device 500 may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0089] The processor 502 is used to run a computer program 5032 stored in the memory to perform the following steps:

[0090] Obtain the ID of the cell to be upgraded; determine if the ID of the cell to be upgraded is the first time the queue number has been set for the day; if the ID of the cell to be upgraded is the first time the queue number has been set for the day, then adaptively adjust the queue number according to the congestion situation; when it is necessary to remotely upgrade the equipment in the cell to be upgraded, determine if the equipment in the cell to be upgraded is offline; if the equipment in the cell to be upgraded is not offline, obtain the queue status corresponding to the cell to be upgraded; determine if the queue status is idle; if the queue status is idle, then assign upgrade tasks to the queue and remotely upgrade the equipment in the cell to be upgraded through the queue.

[0091] The congestion situation refers to the failure rate of coap instructions within a 244s window period.

[0092] In one embodiment, after determining whether the cell ID to be upgraded is the first time the queue number is set that day, the processor 502 further implements the following steps:

[0093] If the ID of the cell to be upgraded is not the first time the queue number is set on that day, then the already set queue number is used for queue management, and the step of determining whether the device in the cell to be upgraded is offline is executed when remote upgrade of the device in the cell to be upgraded is required.

[0094] In one embodiment, when implementing the step of adaptively adjusting the number of queues based on congestion, the processor 502 specifically implements the following steps:

[0095] Set the number of queues based on the congestion situation.

[0096] In one embodiment, when implementing the step of setting the number of queues according to the congestion situation, the processor 502 specifically implements the following steps:

[0097] Based on the congestion situation, the number of queues is set as int((1-coap instruction failure rate))*5+1, where the coap instruction failure rate refers to the failure rate of coap instructions within a 244s window period.

[0098] In one embodiment, when implementing the step of setting the number of queues according to the congestion situation, the processor 502 specifically implements the following steps:

[0099] When the failure rate of the coap instruction is less than 20% within a 244s window, the number of queues is set to 5; when the failure rate of the coap instruction is not less than 20% but less than 40% within a 244s window, the number of queues is set to 4; when the failure rate of the coap instruction is not less than 40% but less than 60% within a 244s window, the number of queues is set to 3; when the failure rate of the coap instruction is not less than 60% but less than 80% within a 244s window, the number of queues is set to 2; and when the failure rate of the coap instruction is not less than 80% within a 244s window, the number of queues is set to 1.

[0100] In one embodiment, after performing the step of determining whether the device in the cell to be upgraded is offline, the processor 502 further performs the following steps:

[0101] If the equipment in the cell to be upgraded is offline, then offline upgrade processing is performed, and the determination of whether the equipment in the cell to be upgraded is offline is executed.

[0102] It should be understood that in the embodiments of this application, the processor 502 may be a central processing unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor.

[0103] It will be understood by those skilled in the art that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program includes program instructions and can be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the process steps of the embodiments of the above methods.

[0104] Therefore, the present invention also provides a storage medium. This storage medium can be a computer-readable storage medium. The storage medium stores a computer program, wherein when executed by a processor, the computer program causes the processor to perform the following steps:

[0105] Obtain the ID of the cell to be upgraded; determine if the ID of the cell to be upgraded is the first time the queue number has been set for the day; if the ID of the cell to be upgraded is the first time the queue number has been set for the day, then adaptively adjust the queue number according to the congestion situation; when it is necessary to remotely upgrade the equipment in the cell to be upgraded, determine if the equipment in the cell to be upgraded is offline; if the equipment in the cell to be upgraded is not offline, obtain the queue status corresponding to the cell to be upgraded; determine if the queue status is idle; if the queue status is idle, then assign upgrade tasks to the queue and remotely upgrade the equipment in the cell to be upgraded through the queue.

[0106] The congestion situation refers to the failure rate of coap instructions within a 244s window period.

[0107] In one embodiment, after executing the computer program to determine whether the cell ID to be upgraded is the first time the queue number is set that day, the processor further implements the following steps:

[0108] If the ID of the cell to be upgraded is not the first time the queue number is set on that day, then the already set queue number is used for queue management, and the step of determining whether the device in the cell to be upgraded is offline is executed when remote upgrade of the device in the cell to be upgraded is required.

[0109] In one embodiment, when the processor executes the computer program to implement the step of adaptively adjusting the queue number according to congestion, it specifically implements the following steps:

[0110] Set the number of queues based on the congestion situation.

[0111] In one embodiment, when the processor executes the computer program to implement the step of setting the queue number according to the congestion situation, it specifically implements the following steps:

[0112] Based on the congestion situation, the number of queues is set as int((1-coap instruction failure rate))*5+1, where the coap instruction failure rate refers to the failure rate of coap instructions within a 244s window period.

[0113] In one embodiment, when the processor executes the computer program to implement the step of setting the queue number according to the congestion situation, it specifically implements the following steps:

[0114] When the failure rate of the coap instruction is less than 20% within a 244s window, the number of queues is set to 5; when the failure rate of the coap instruction is not less than 20% but less than 40% within a 244s window, the number of queues is set to 4; when the failure rate of the coap instruction is not less than 40% but less than 60% within a 244s window, the number of queues is set to 3; when the failure rate of the coap instruction is not less than 60% but less than 80% within a 244s window, the number of queues is set to 2; and when the failure rate of the coap instruction is not less than 80% within a 244s window, the number of queues is set to 1.

[0115] In one embodiment, after executing the computer program to implement the step of determining whether the device in the cell to be upgraded is offline, the processor further implements the following steps:

[0116] If the equipment in the cell to be upgraded is offline, then offline upgrade processing is performed, and the determination of whether the equipment in the cell to be upgraded is offline is executed.

[0117] The storage medium can be any computer-readable storage medium capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory (ROM), magnetic disk, or optical disk.

[0118] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementations should not be considered beyond the scope of this invention.

[0119] In the several embodiments provided by this invention, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For example, the division of each unit is merely a logical functional division, and there may be other division methods in actual implementation. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed.

[0120] The steps in the method of this invention can be adjusted, merged, or reduced in order according to actual needs. The units in the device of this invention can be merged, divided, or reduced according to actual needs. Furthermore, the functional units in the various embodiments of this invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0121] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0122] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A congestion-prevention remote upgrade method, characterized in that, include: Obtain the ID of the community to be upgraded; Determine whether the cell ID to be upgraded is the first queue set for that day; If the cell ID to be upgraded is the first time the queue number is set on that day, the queue number will be adaptively adjusted according to the congestion situation. When it is necessary to remotely upgrade the equipment in the community to be upgraded, it is determined whether the equipment in the community to be upgraded is offline; If the devices in the cell to be upgraded are not offline, then obtain the queue status corresponding to the cell to be upgraded; Determine whether the queue is in an idle state; If the queue is in an idle state, an upgrade task is assigned to the queue, and the equipment in the cell to be upgraded is remotely upgraded through the queue. After determining whether the cell ID to be upgraded is the first time the queue number has been set that day, the process also includes: If the ID of the cell to be upgraded is not the first time the queue number is set on the same day, then the already set queue number is used for queue management, and the step of determining whether the device in the cell to be upgraded is offline is executed when remote upgrade of the device in the cell to be upgraded is required. The congestion situation refers to the failure rate of coap instructions within a 244s window period; The adaptive adjustment of the queue number based on congestion includes: Set the number of queues according to the congestion situation; Setting the queue number based on the congestion situation includes: Based on the congestion situation, the queue number is set as int((1-coap instruction failure rate))*5+1, where the coap instruction failure rate refers to the coap instruction failure rate within a 244s window period.

2. The congestion-prevention remote upgrade method according to claim 1, characterized in that, Setting the queue number based on the congestion situation includes: When the failure rate of the coap instruction is less than 20% within a 244s window, the number of queues is set to 5; when the failure rate of the coap instruction is not less than 20% but less than 40% within a 244s window, the number of queues is set to 4; when the failure rate of the coap instruction is not less than 40% but less than 60% within a 244s window, the number of queues is set to 3; when the failure rate of the coap instruction is not less than 60% but less than 80% within a 244s window, the number of queues is set to 2; and when the failure rate of the coap instruction is not less than 80% within a 244s window, the number of queues is set to 1.

3. The congestion-prevention remote upgrade method according to claim 1, characterized in that, After determining whether the device in the cell to be upgraded is offline, the process further includes: If the equipment in the cell to be upgraded is offline, then offline upgrade processing is performed, and the determination of whether the equipment in the cell to be upgraded is offline is executed.

4. A congestion-prevention remote upgrade device, characterized in that, include: The ID acquisition unit is used to obtain the ID of the cell to be upgraded. The first judgment unit is used to determine whether the cell ID to be upgraded is the first time the queue number is set on that day; An adjustment unit is used to adaptively adjust the queue number based on congestion if the ID of the cell to be upgraded is the first time the queue number is set on that day. The second judgment unit is used to determine whether the equipment in the cell to be upgraded is offline when it is necessary to remotely upgrade the equipment in the cell to be upgraded. The status acquisition unit is used to acquire the queue status corresponding to the cell to be upgraded if the device in the cell to be upgraded is not offline. The third judgment unit is used to determine whether the queue state is an idle state; An upgrade unit is used to assign upgrade tasks to the queue if the queue status is idle, and to remotely upgrade the equipment of the cell to be upgraded through the queue. The anti-congestion remote upgrade device further includes: a management unit, used to manage queues by using the already set queue number if the ID of the cell to be upgraded is not the first time the queue number is set on the same day, and to determine whether the equipment in the cell to be upgraded is offline when remote upgrade of the equipment in the cell to be upgraded is required. The congestion situation refers to the failure rate of coap instructions within a 244s window period; The adjustment unit is used to set the number of queues according to the congestion situation; The adjustment unit is used to set the number of queues according to the congestion situation using the formula: queue number = int((1 - coap instruction failure rate)) * 5 + 1, where the coap instruction failure rate refers to the coap instruction failure rate within a 244s window period.

5. A computer device, characterized in that, The computer device includes a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method as described in any one of claims 1 to 3.

6. A storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, implements the method as described in any one of claims 1 to 3.

Images