IPC firmware file upgrading control method and device, terminal and medium

Abstract

The invention discloses an IPC firmware file upgrading control method and device, a terminal and a medium, and the method comprises the steps: firstly, based on a received IPC firmware upgrading file, carrying out the distribution processing of the IPC firmware upgrading file according to a storage node network topology architecture and preset file distribution configuration information, and carrying out the upgrading processing of the IPC firmware file; the method comprises the following steps: storing an IPC firmware upgrading file in storage service nodes at different geographic positions, after receiving a firmware upgrading instruction, determining a downloading source node of each IPC device by each IPC device based on the respective geographic position and network environment, and respectively issuing downloading addresses of the storage nodes to the IPC devices, and triggering the IPC equipment to download the firmware upgrading file from the proper storage node based on the downloading address so as to finish upgrading, thereby solving the technical problem of low upgrading success rate caused by different downloading effects of the IPC firmware at different geographic positions and in different network environments in the existing upgrading mode.

Description

Technical Field

[0001] The present application relates to the field of Internet of Things technology, and in particular to an IPC firmware file upgrade control method, device, terminal and medium. Background Art

[0002] The current IPC (Internet Protocol Camera) is a new generation of cameras that combines traditional cameras with network technology. It can transmit video, audio, alarm and control signals through the network and accept the management of the network monitoring host (NVR or monitoring management platform). It is an important tool to assist public security departments in combating crime and maintaining social stability. Due to different actual application scenarios, it is necessary to carry out customized development with various IPC manufacturers and formulate customized firmware installation files.

[0003] Due to different business scenarios, there are differences in the geographical locations of different IPCs (different provinces, cities, and counties), as well as differences in network environments (public network environment, industry-specific network), which leads to differences in the installation package download methods and network links required for automatic IPC upgrades. This ultimately causes the firmware file storage location to be too far away from the IPC, resulting in long download times and even frequent interruptions. Summary of the invention

[0004] The present application provides an IPC firmware file upgrade control method, device, terminal and medium, which are used to solve the technical problem of low upgrade success rate of existing IPC devices.

[0005] In order to solve the above technical problems, the first aspect of the present application provides an IPC firmware file upgrade control method, comprising:

[0006] Receive IPC firmware upgrade files;

[0007] Distribute the IPC firmware upgrade file to multiple storage nodes according to the storage node network topology architecture and preset file distribution configuration information;

[0008] When a firmware upgrade instruction is received, a target storage node corresponding to the IPC device is determined according to the file distribution record of the IPC firmware upgrade file and the geographical attributes and network attributes of the IPC device to be upgraded;

[0009] The download address of the target storage node is sent to the IPC device, so that the IPC device downloads the IPC firmware upgrade file from the target storage node for upgrading according to the download address.

[0010] Preferably, distributing the IPC firmware upgrade file to multiple storage nodes according to the storage node network topology architecture and preset file distribution configuration information includes:

[0011] According to the storage node network topology architecture and preset file distribution configuration information, the IPC firmware upgrade file is distributed to multiple storage nodes respectively through a multi-threaded asynchronous distribution method.

[0012] Preferably, it also includes:

[0013] Recording the IPC firmware upgrade file that was not successfully distributed, and writing the IPC firmware upgrade file that was not successfully distributed into a preset retry queue;

[0014] The IPC firmware upgrade file in the retry queue is redistributed. If the distribution is still unsuccessful and the number of distribution failures of the IPC firmware upgrade file does not reach a preset number threshold, the IPC firmware upgrade file is rewritten into the retry queue until the IPC firmware upgrade file is distributed successfully or the number of distribution failures reaches the number threshold.

[0015] Preferably, according to the file distribution record of the IPC firmware upgrade file, and the geographical attributes and network attributes of the IPC device to be upgraded, determining the target storage node corresponding to the IPC device specifically includes:

[0016] Determine, according to the file distribution record of the IPC firmware upgrade file, a first target storage node that receives the IPC firmware upgrade file;

[0017] According to the geographical attributes and network attributes of the IPC device to be upgraded, a second target storage node corresponding to the IPC device is determined from the first target storage nodes.

[0018] Preferably, the storage nodes include: regional public network storage nodes and private network storage nodes.

[0019] Preferably, distributing the IPC firmware upgrade file to multiple storage nodes according to the storage node network topology architecture and preset file distribution configuration information further includes:

[0020] When the storage node is a private network storage node, determining the regional public network storage node to which the private network storage node belongs;

[0021] The IPC firmware upgrade file is distributed to the regional public network storage node, so as to utilize the distribution service sub-node supporting the private network storage node to download the IPC firmware upgrade file from the regional public network storage node and then upload it to the private network storage node.

[0022] At the same time, the second aspect of the present application provides an IPC firmware file upgrade control device, including:

[0023] A file receiving unit, used for receiving an IPC firmware upgrade file;

[0024] A file distribution unit, used to distribute the IPC firmware upgrade file to multiple storage nodes according to the storage node network topology architecture and preset file distribution configuration information;

[0025] An upgrade instruction response unit, configured to determine, when receiving a firmware upgrade instruction, a target storage node corresponding to the IPC device according to a file distribution record of the IPC firmware upgrade file and a geographical attribute and a network attribute of the IPC device to be upgraded;

[0026] The download address sending unit is used to send the download address of the target storage node to the IPC device, so that the IPC device downloads the IPC firmware upgrade file from the target storage node for upgrading according to the download address.

[0027] Preferably, it also includes: a distribution retry control unit, which is used to:

[0028] Recording the IPC firmware upgrade file that was not successfully distributed, and writing the IPC firmware upgrade file that was not successfully distributed into a preset retry queue;

[0029] The IPC firmware upgrade file in the retry queue is redistributed. If the distribution is still unsuccessful and the number of distribution failures of the IPC firmware upgrade file does not reach a preset number threshold, the IPC firmware upgrade file is rewritten into the retry queue until the IPC firmware upgrade file is distributed successfully or the number of distribution failures reaches the number threshold.

[0030] A third aspect of the present application provides an IPC firmware file upgrade control terminal, comprising: a memory and a processor;

[0031] The memory is used to store program code, and the program code is used to implement an IPC firmware file upgrade control method provided in the first aspect of the present application;

[0032] The processor is used for reading and executing the program code.

[0033] The fourth aspect of the present application provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores program code, and the program code is used to be read and executed by a processor to implement an IPC firmware file upgrade control method as provided in the first aspect of the present application.

[0034] It can be seen from the above technical solutions that this application has the following advantages:

[0035] The solution provided in the present application is first based on the received IPC firmware upgrade file, and distributes and processes the IPC firmware upgrade file according to the storage node network topology architecture and the preset file distribution configuration information, so as to store the IPC firmware upgrade file in the storage service nodes in different geographical locations, and complete the preparatory process before the firmware upgrade is executed. After receiving the firmware upgrade instruction for triggering the upgrade action, each IPC device determines the download source node of each IPC device based on its own geographical location and network environment, and finally sends the download addresses of these storage nodes to the corresponding IPC devices according to the storage node as the download source, so as to trigger the IPC device to download the firmware upgrade file from the appropriate storage node based on the download address, thereby completing the upgrade, and solving the technical problem of low upgrade success rate caused by the difference in the download effect of the existing upgrade method on the IPC firmware in different geographical locations and different network environments. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0037] Figure 1 A schematic diagram of the implementation system framework of an IPC firmware file upgrade control method provided in this application.

[0038] Figure 2 A flowchart of an IPC firmware file upgrade control method embodiment provided in the present application.

[0039] Figure 3 A schematic diagram of the structure of an IPC firmware file upgrade control device embodiment provided in the present application.

[0040] Figure 4 A structural schematic diagram of an IPC firmware file upgrade control terminal embodiment provided by the present application. DETAILED DESCRIPTION

[0041] The embodiments of the present application provide an IPC firmware file upgrade control method, device, terminal and medium, which are used to solve the technical problem of low upgrade success rate of existing IPC devices.

[0042] In order to make the purpose, features, and advantages of the invention of this application more obvious and easy to understand, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the embodiments described below are only part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0043] like Figure 1 As shown, the implementation system of the IPC firmware file upgrade control method provided by the present application has an architecture including: a central service platform, multiple storage nodes and IPC device nodes.

[0044] Among them, the central service platform is the main executor of the IPC firmware file upgrade control method provided in this application, and may include: ordinary public network storage nodes, which can be used to store data such as new IPC firmware files uploaded by various IPC manufacturers and firmware file upgrade result feedback records; configuration center nodes, which are used to configure the distribution rules of firmware upgrade files; distribution service nodes, which can be used to execute the task of the central service platform to distribute firmware upgrade files to its storage nodes to ensure subsequent IPC firmware downloads; firmware upgrade service nodes, which are used to communicate with the signaling service of the IPC device, and can realize the issuance of upgrade instructions and the reception of upgrade report information fed back by the IPC device.

[0045] Storage nodes include: edge nodes and public network nodes, which are responsible for implementing file storage and download services, including common S3 storage, NAS storage, etc. They may also include CDN edge nodes, which are responsible for network file caching services and can accelerate file downloads. The CDN used in this embodiment can be a common acceleration site on the market, or a self-built acceleration site as needed.

[0046] The above is a system architecture description for implementing the IPC firmware file upgrade control method of the present application. The following is a detailed description of the IPC firmware file upgrade control method embodiment process provided by the present application, which is as follows:

[0047] See also Figure 1 and Figure 2 , this embodiment provides an IPC firmware file upgrade control method, including:

[0048] Step 101: Receive an IPC firmware upgrade file.

[0049] Step 102: Distribute the IPC firmware upgrade file to multiple storage nodes according to the storage node network topology architecture and preset file distribution configuration information.

[0050] It should be noted that when the firmware of the existing IPC needs to be upgraded, the manufacturer can upload the verified IPC firmware upgrade file to the central service platform so that the central service platform can distribute the received IPC firmware upgrade file to multiple storage nodes based on its storage node network topology architecture and the file distribution configuration information generated by the user by configuring the central node.

[0051] Step 103: When a firmware upgrade instruction is received, a target storage node corresponding to the IPC device is determined according to the file distribution record of the IPC firmware upgrade file and the geographical attributes and network attributes of the IPC device to be upgraded.

[0052] Step 104: Send the download address of the target storage node to the IPC device, so that the IPC device downloads the IPC firmware upgrade file from the target storage node for upgrading according to the download address.

[0053] It should be noted that after completing the preliminary preparations for the IPC device upgrade through steps 101 and 102, when the central service platform receives the firmware upgrade instruction, the upgrade action of the IPC device is triggered. Specifically, based on the file distribution record of the IPC firmware upgrade file and the geographical attributes and network attributes of the IPC device to be upgraded, a target storage node corresponding to the IPC device is determined as the download source of the upgrade file for the IPC device. The geographical attributes of the IPC device record the network location of the IPC device, which can be used to filter storage nodes near the IPC device. The network attributes record the network type of the IPC device, which can be used to filter storage nodes with the same or compatible network types. Since IPC and signaling are bound to each other, the network location and network type of the IPC can be identified through the signaling service.

[0054] More specifically, regarding the storage node architecture and distribution rule configuration, the distribution service of this embodiment adopts a 1+n deployment method of central node + provincial edge node, including: regional public network storage nodes and private network storage nodes. The regional public network storage nodes can be divided into provincial public network storage nodes and prefecture-level public network storage nodes according to the administrative level.

[0055] The central distribution service downloads the firmware file locally, obtains the distribution rules from the configuration center (Apollo configuration center), and asynchronously uploads the file to the domestic provincial node storage resource pool through multi-threading and other methods.

[0056] For edge nodes in cities and counties, according to the rules configured by the configuration center, multi-threading and other methods are also used to asynchronously upload files to edge storage nodes in cities and counties that support the public network.

[0057] For private network storage nodes that are not exposed to the public network, provincial nodes are used as springboards to deploy distribution service sub-nodes. The distribution sub-tasks are issued by the center, and the sub-nodes download the source files and upload them to the private network storage pool.

[0058] According to the configured rules, provincial nodes or municipal nodes equipped with CDN acceleration pre-cache the firmware files to the corresponding site through the API interface of the acceleration site.

[0059] Each distributed node is identified with its own network type and geographical attributes. When issuing upgrade tasks, each download address is marked with the corresponding administrative code and network type for identification by the management background.

[0060] More specifically, the specific steps of determining the target storage node mentioned in step 103 can refer to the following specific examples:

[0061] Determine, according to the file distribution record of the IPC firmware upgrade file, a first target storage node that receives the IPC firmware upgrade file;

[0062] According to the geographical attributes and network attributes of the IPC device to be upgraded, a second target storage node corresponding to the IPC device is determined from the first target storage nodes.

[0063] The download address of the target storage node is sent to the IPC device, so that the IPC device can download the IPC firmware upgrade file from the target storage node for upgrading according to the download address. After the IPC device obtains the firmware upgrade instruction, it downloads the firmware file from the corresponding node through the download address, and reports the download progress and status of the firmware file in real time through the established socket link. After the upgrade, the device is automatically restarted and the socket link is re-established with the signaling service.

[0064] Furthermore, if Figure 2 As shown, the solution provided by this embodiment may further include the following in the file distribution stage:

[0065] Step 1001, record the IPC firmware upgrade files that have not been successfully distributed, and write the IPC firmware upgrade files that have not been successfully distributed into a preset retry queue;

[0066] Step 1002: redistribute the IPC firmware upgrade file in the retry queue. If the distribution is still unsuccessful and the number of distribution failures of the IPC firmware upgrade file does not reach the preset number threshold, the IPC firmware upgrade file is rewritten into the retry queue until the IPC firmware upgrade file is distributed successfully or the number of distribution failures reaches the number threshold.

[0067] It should be noted that during the distribution process, if the storage pool fails to write or the response times out, it will be added to the retry queue and the central service will re-consume and retry the distribution task.

[0068] When retrying, the distribution service can obtain the file information through S3GetObjectMetaData. If the file information can be obtained successfully and the returned file MD5 information is consistent with the MD5 information corresponding to the distribution task, it means that the file has been uploaded normally.

[0069] For tasks that have failed to be retried, they can be put back into the retry queue. When the number of retries reaches the specified number (configured by the configuration center), the retry ends.

[0070] Both successful and failed distribution tasks can be recorded in the database, and a query interface is provided for the firmware management background to query. Failed subtasks can be retried separately or other decisions can be made.

[0071] The above is a detailed description of an embodiment of an IPC firmware file upgrade control method provided by the present application. The solution of this embodiment uses file distribution capabilities to store the firmware files used for upgrading in advance to various provinces and edge nodes according to specified distribution rules, bypassing network type barriers and realizing IPC firmware upgrades of multiple network types. At the same time, distribution according to the principle of proximity can shorten the IPC firmware download network link and increase the success rate of firmware upgrades. By utilizing the fixed correspondence between IPC and signaling services, signaling services are labeled, and IPC networks and geographic information can be identified through signaling networks and geographic attributes. In addition to targeted distribution to various provinces and edge nodes, the distribution capability can also be preheated to each CDN acceleration node in advance. Through the CDN pre-storage mechanism, firmware file downloads and acceleration of edge node IPCs are realized without storage.

[0072] The following is a detailed description of an embodiment of an IPC firmware file upgrade control device provided by the present application.

[0073] See also Figure 3 , this embodiment provides an IPC firmware file upgrade control device, including:

[0074] The file receiving unit 201 is used to receive the IPC firmware upgrade file;

[0075] The file distribution unit 202 is used to distribute the IPC firmware upgrade file to multiple storage nodes according to the storage node network topology architecture and preset file distribution configuration information;

[0076] The upgrade instruction response unit 203 is used to determine the target storage node corresponding to the IPC device according to the file distribution record of the IPC firmware upgrade file and the geographical attributes and network attributes of the IPC device to be upgraded when receiving the firmware upgrade instruction;

[0077] The download address sending unit 204 is used to send the download address of the target storage node to the IPC device, so that the IPC device downloads the IPC firmware upgrade file from the target storage node for upgrading according to the download address.

[0078] Furthermore, it also includes: a distribution retry control unit 200, which is used to:

[0079] Record the IPC firmware upgrade files that have not been successfully distributed, and write the IPC firmware upgrade files that have not been successfully distributed into a preset retry queue;

[0080] Redistribute the IPC firmware upgrade file in the retry queue. If the distribution is still unsuccessful and the number of distribution failures of the IPC firmware upgrade file has not reached the preset number threshold, then rewrite the IPC firmware upgrade file into the retry queue until the IPC firmware upgrade file is distributed successfully or the number of distribution failures reaches the number threshold.

[0081] In addition, if Figure 4 As shown, the present application also provides an IPC firmware file upgrade control terminal embodiment, the implementation types of the terminal include but are not limited to: personal computers, industrial computers, servers and embedded intelligent devices, the main components of the terminal include: a memory 33 and a processor 31, the memory 33 and the processor 31 can be connected via a communication bus 34;

[0082] The memory 33 is used to store program codes, and the program codes are used to implement an IPC firmware file upgrade control method provided in the above embodiment;

[0083] The processor 31 is used to read and execute program codes.

[0084] Finally, the present application also provides a computer-readable storage medium embodiment, in which program code is stored, and the program code is used to be read and executed by a processor to implement an IPC firmware file upgrade control method provided in the above embodiment.

[0085] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the terminals, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0086] In the several embodiments provided in the present application, it should be understood that the disclosed terminals, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0087] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described herein can, for example, be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0088] It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0089] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0090] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0091] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable 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. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0092] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. An IPC firmware file upgrade control method, characterized in that: include: Receive IPC firmware upgrade files; Distribute the IPC firmware upgrade file to multiple storage nodes according to the storage node network topology architecture and preset file distribution configuration information; When a firmware upgrade instruction is received, a target storage node corresponding to the IPC device is determined according to the file distribution record of the IPC firmware upgrade file and the geographical attributes and network attributes of the IPC device to be upgraded; The download address of the target storage node is sent to the IPC device, so that the IPC device downloads the IPC firmware upgrade file from the target storage node for upgrading according to the download address.

2. An IPC firmware file upgrade control method according to claim 1, characterized in that: The distributing the IPC firmware upgrade file to multiple storage nodes according to the storage node network topology architecture and preset file distribution configuration information includes: According to the storage node network topology architecture and preset file distribution configuration information, the IPC firmware upgrade file is distributed to multiple storage nodes respectively through a multi-threaded asynchronous distribution method.

3. The IPC firmware file upgrade control method according to claim 1, characterized in that: Also includes: Recording the IPC firmware upgrade file that was not successfully distributed, and writing the IPC firmware upgrade file that was not successfully distributed into a preset retry queue; The IPC firmware upgrade file in the retry queue is redistributed. If the distribution is still unsuccessful and the number of distribution failures of the IPC firmware upgrade file does not reach a preset number threshold, the IPC firmware upgrade file is rewritten into the retry queue until the IPC firmware upgrade file is distributed successfully or the number of distribution failures reaches the number threshold.

4. The IPC firmware file upgrade control method according to claim 1, characterized in that: Determining the target storage node corresponding to the IPC device according to the file distribution record of the IPC firmware upgrade file and the geographical attributes and network attributes of the IPC device to be upgraded specifically includes: Determine, according to the file distribution record of the IPC firmware upgrade file, a first target storage node that receives the IPC firmware upgrade file; According to the geographical attributes and network attributes of the IPC device to be upgraded, a second target storage node corresponding to the IPC device is determined from the first target storage nodes.

5. The IPC firmware file upgrade control method according to claim 1, characterized in that: The storage nodes include: regional public network storage nodes and private network storage nodes.

6. The IPC firmware file upgrade control method according to claim 5, characterized in that: The step of distributing the IPC firmware upgrade file to multiple storage nodes according to the storage node network topology architecture and preset file distribution configuration information further includes: When the storage node is a private network storage node, determining the regional public network storage node to which the private network storage node belongs; The IPC firmware upgrade file is distributed to the regional public network storage node, so as to utilize the distribution service sub-node supporting the private network storage node to download the IPC firmware upgrade file from the regional public network storage node and then upload it to the private network storage node.

7. An IPC firmware file upgrade control device, characterized in that: include: A file receiving unit, used for receiving an IPC firmware upgrade file; A file distribution unit, used to distribute the IPC firmware upgrade file to multiple storage nodes according to the storage node network topology architecture and preset file distribution configuration information; An upgrade instruction response unit, configured to determine, when receiving a firmware upgrade instruction, a target storage node corresponding to the IPC device according to a file distribution record of the IPC firmware upgrade file and a geographical attribute and a network attribute of the IPC device to be upgraded; The download address sending unit is used to send the download address of the target storage node to the IPC device, so that the IPC device downloads the IPC firmware upgrade file from the target storage node for upgrading according to the download address.

8. An IPC firmware file upgrade control device according to claim 7, characterized in that: Also includes: Distribute retry control unit for: Recording the IPC firmware upgrade file that was not successfully distributed, and writing the IPC firmware upgrade file that was not successfully distributed into a preset retry queue; The IPC firmware upgrade file in the retry queue is redistributed. If the distribution is still unsuccessful and the number of distribution failures of the IPC firmware upgrade file does not reach a preset number threshold, the IPC firmware upgrade file is rewritten into the retry queue until the IPC firmware upgrade file is distributed successfully or the number of distribution failures reaches the number threshold.

9. An IPC firmware file upgrade control terminal, characterized in that: include: Memory and processor; The memory is used to store program codes, and the program codes are used to implement an IPC firmware file upgrade control method according to any one of claims 1 to 6; The processor is used for reading and executing the program code.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores program code, and the program code is used to be read and executed by a processor to implement an IPC firmware file upgrade control method as described in any one of claims 1 to 6.

Images