An IPC firmware file upgrade control method and device, a terminal and a medium

Abstract

The application discloses an IPC firmware file upgrade control method and device, a terminal and a medium. The scheme provided by the application first distributes the received IPC firmware upgrade file according to a storage node network topology architecture and preset file distribution configuration information, stores the IPC firmware upgrade file in storage service nodes in different geographical positions, and determines the download source node of each IPC device based on the geographical position and network environment of each IPC device when a firmware upgrade instruction is received, so as to trigger the IPC device to download the firmware upgrade file from the suitable storage node based on the download address, thereby completing the upgrade, and solving the technical problem of low upgrade success rate caused by the poor download effect of the IPC firmware in different geographical positions and different network environments in the prior art.

Description

TECHNICAL FIELD

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

[0002] The current IPC (Internet Protocol Camera) is a new generation of camera generated by combining a traditional camera with network technology. It can transmit video, audio, alarm and control signals through a network, accept the management of a network monitoring host (NVR or monitoring management platform), and is an important tool for assisting public security departments to combat crime and maintain social stability. Due to different actual application scenarios, customized development needs to be performed with various IPC manufacturers, and customized firmware installation files need to be developed.

[0003] Due to different business scenarios, there are differences in geographical locations of different IPCs (different provinces, cities and counties) and network environments (public network environment, industry private network), resulting in differences in installation package download methods and network links required for automatic upgrade of the IPC, and finally causing problems such as long download time and even frequent interruption due to too long geographical distance between the location where the firmware file is stored and the IPC. SUMMARY

[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 the existing IPC equipment.

[0005] To solve the above technical problem, the first aspect of the present application provides an IPC firmware file upgrade control method, comprising:

[0006] receiving an IPC firmware upgrade file;

[0007] distributing the IPC firmware upgrade file to a plurality of storage nodes according to a storage node network topology architecture and preset file distribution configuration information;

[0008] when receiving a firmware upgrade instruction, determining a target storage node corresponding to an IPC device to be upgraded according to file distribution records of the IPC firmware upgrade file and geographical attributes and network attributes of the IPC device;

[0009] downloading the IPC firmware upgrade file from the target storage node for upgrading according to the download address of the target storage node.

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

[0011] The IPC firmware upgrade file is distributed to the plurality of storage nodes through a multi-thread asynchronous distribution mode according to the storage node network topology architecture and preset file distribution configuration information.

[0012] Preferably, the method further comprises:

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

[0014] Redistributing the IPC firmware upgrade file in the retry queue, and if the IPC firmware upgrade file is still not successfully distributed and the number of distribution failures of the IPC firmware upgrade file does not reach a preset number threshold, then the IPC firmware upgrade file is written into the retry queue again until the IPC firmware upgrade file is successfully distributed or the number of distribution failures reaches the number threshold.

[0015] Preferably, the target storage node corresponding to the IPC device is determined according to the file distribution record of the IPC firmware upgrade file and geographical attributes and network attributes of the IPC device, and specifically comprises:

[0016] A first target storage node receiving the IPC firmware upgrade file is determined according to the file distribution record of the IPC firmware upgrade file.

[0017] A second target storage node corresponding to the IPC device is determined from the first target storage node according to geographical attributes and network attributes of the IPC device.

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

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

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

[0021] The IPC firmware upgrade file is distributed to the regional public network storage node, so that a distribution service sub-node matched with the private network storage node downloads the IPC firmware upgrade file from the regional public network storage node and then uploads the IPC firmware upgrade file to the private network storage node.

[0022] Meanwhile, the second aspect of the present application provides an IPC firmware file upgrade control device, comprising:

[0023] a file receiving unit configured to receive an IPC firmware upgrade file;

[0024] a file distribution unit configured to distribute the IPC firmware upgrade file to a plurality of storage nodes according to a storage node network topology architecture and preset file distribution configuration information;

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

[0026] a download address issuing unit configured to issue a 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, the device further comprises a distribution retry control unit configured to:

[0028] record an IPC firmware upgrade file that fails to be distributed successfully, and write the IPC firmware upgrade file that fails to be distributed successfully into a preset retry queue;

[0029] redistribute the IPC firmware upgrade file in the retry queue, and if the IPC firmware upgrade file still fails to be distributed successfully and a distribution failure number of the IPC firmware upgrade file does not reach a preset number threshold, then the IPC firmware upgrade file is written into the retry queue again until the IPC firmware upgrade file is distributed successfully or the distribution failure number reaches the number threshold.

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

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

[0032] The processor is configured to read and execute 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 has program code saved therein, and the program code is configured to be read and executed by a processor to implement the IPC firmware file upgrade control method provided in the first aspect of the present application.

[0034] As can be seen from the above technical solutions, the present application has the following advantages:

[0035] The scheme provided by the application is first based on the received IPC firmware upgrade file, and the IPC firmware upgrade file is distributed 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 different geographical position storage service nodes, complete the preparation process before the firmware upgrade execution, and when receiving the firmware upgrade instruction for triggering the upgrade action, the download source node of each IPC device is determined based on the geographical position and network environment of each IPC device, and finally the download address of the storage node as the download source is respectively sent to the corresponding IPC device, so as to trigger the IPC device to download the firmware upgrade file from the suitable storage node based on the download address, thereby completing the upgrade, and solving the technical problem of low upgrade success rate caused by the poor download effect of the IPC firmware in different geographical positions and different network environments in the prior art. BRIEF DESCRIPTION OF DRAWINGS

[0036] In order to more clearly illustrate the technical solutions in the embodiments of the application or the prior art, the drawings needed to be used in the embodiments or the prior art description will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the application, and other drawings can be obtained by those skilled in the art without creative labor under the premise of the drawings.

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

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

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

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

[0041] The embodiments of the 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 the existing IPC device.

[0042] In order to make the purposes, characteristics and advantages of the present application more obvious and easy to understand, the technical solutions in the embodiments of the present application will be described clearly and completely below in combination with the drawings in the embodiments of the present application. Obviously, the embodiments described below are only some of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor fall within the scope of protection of the present application.

[0043] As shown in Figure 1 The embodiment system of the IPC firmware file upgrade control method provided by the present application has the architecture including a central service platform, a plurality of storage nodes and IPC device nodes.

[0044] The central service platform is the main execution subject of the IPC firmware file upgrade control method provided by the present application, and can include a general public network storage node, which can be used to store the IPC new version firmware file uploaded by each IPC manufacturer and the upgrade result feedback record of the firmware file and the like; a configuration center node, which is used to configure the distribution rule of the firmware upgrade file; a distribution service node, which can be used to execute the task of distributing the firmware upgrade file from the central service platform to the storage nodes under it, so as to ensure the subsequent firmware download of the IPC; and a firmware upgrade service node, which is used to communicate with the signaling service of the IPC device, and can implement the functions of issuing an upgrade instruction and receiving the upgrade report information fed back by the IPC device and the like.

[0045] The storage nodes include edge nodes and public network nodes, which are responsible for implementing the file storage and download service, specifically including common S3 storage, NAS storage and the like, and can also include a CDN edge node, which is responsible for the network file caching service and can implement the file download acceleration. The CDN used in the 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 of the IPC firmware file upgrade control method provided by the present application, and the following is a detailed description of an embodiment process of the IPC firmware file upgrade control method provided by the present application, which is specifically as follows:

[0047] Please refer to Figure 1 and Figure 2 The IPC firmware file upgrade control method provided by the present application includes the following steps.

[0048] Step 101, receiving an IPC firmware upgrade file.

[0049] Step 102, distributing the IPC firmware upgrade file to a plurality of storage nodes according to the storage node network topology architecture and the preset file distribution configuration information.

[0050] It should be noted that when it is necessary to upgrade the inventory IPC, the manufacturer can upload the verified IPC firmware upgrade file to the central service platform, so that the central service platform distributes the received IPC firmware upgrade file to a plurality of storage nodes according to the storage node network topology architecture under the central service platform and the file distribution configuration information generated by the user through the configuration center node.

[0051] Step 103, when receiving the firmware upgrade instruction, 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 attribute and network attribute of the IPC device to be upgraded.

[0052] Step 104, issuing 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 the pre-preparation of the IPC device upgrade is completed 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, according to the file distribution record of the IPC firmware upgrade file and the geographical attribute and network attribute of the IPC device to be upgraded, a target storage node corresponding to the IPC device is determined as the upgrade file download source of the IPC device. The geographical attribute of the IPC device records the network location of the IPC device, which can be used to filter the storage nodes near the IPC device, and the network attribute records the network type of the IPC device, which can be used to filter the storage nodes of the same or compatible network type. Since the IPC and the signaling belong to a binding relationship, the network location and the 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 the embodiment adopts a 1+n deployment mode of a center node + a provincial edge node, including: a regional public network storage node and a private network storage node. The regional public network storage node can be divided into a provincial public network storage node and a prefectural public network storage node according to the administrative level.

[0055] The central distribution service downloads the firmware file to the local, obtains the distribution rule from the configuration center (Apollo configuration center), and uploads the file to the provincial node storage resource pool in China through multi-threading and other ways.

[0056] For the city edge node, according to the rule configured by the configuration center, the file is uploaded to the city edge storage node supporting the public network through multi-threading and other ways.

[0057] For the private network storage node which does not expose public network, the distribution service sub-node is deployed by using the province node as a stepping stone, and the sub-node downloads the source file and uploads it to the private network storage pool through the central distribution sub-task.

[0058] According to the configured rules, the province node or city node with CDN acceleration pre-warms the firmware file to the corresponding site through the api interface of the acceleration site.

[0059] Each distributed node identifies the respective network type and geographical attribute, and when the upgrade task is issued, each download address indicates the corresponding administrative code and network type for the management background to identify.

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

[0061] According to the file distribution record of the IPC firmware upgrade file, the first target storage node receiving the IPC firmware upgrade file is determined.

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

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

[0064] Further, as shown in Figure 2 The scheme provided by the embodiment can further include the following steps in the file distribution stage:

[0065] Step 1001, record the IPC firmware upgrade file which is not successfully distributed, and write the IPC firmware upgrade file which is not successfully distributed into a preset retry queue;

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

[0067] It should be noted that in the distribution process, if the storage pool write fails or the response times out, the retry queue is joined, and the central service re-consumes the retry distribution task.

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

[0069] For tasks that fail to retry, they can be re-placed in the retry queue. When the number of retries reaches a specified number (configured by the configuration center), the retry ends.

[0070] For successful and failed distribution tasks, they can be recorded to the database, and a query interface is provided for firmware management background query. The failed sub-tasks can be re-tried 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 scheme of the embodiment stores the firmware file used for upgrading in advance in each province and edge node according to the specified distribution rule through the file distribution capability, bypasses the network type barrier, realizes the IPC firmware upgrade of multiple network types, and at the same time, according to the principle of proximity distribution, the network link for downloading the IPC firmware can be shortened, and the success rate of firmware upgrade can be increased. By using the fixed correspondence between the IPC and the signaling service to label the signaling service, the IPC network and geographical information can be identified through the signaling network and geographical attributes. In addition to being distributed to each province and edge node, the distribution capability can also preheat each CDN acceleration node. Through the pre-storage mechanism of the CDN, there is no need to store, and the firmware file download and acceleration of the edge node IPC can be realized.

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

[0073] Please refer to Figure 3 The IPC firmware file upgrade control device provided by the embodiment comprises:

[0074] The file receiving unit 201 is configured to receive the IPC firmware upgrade file.

[0075] The file distribution unit 202 is configured to distribute the IPC firmware upgrade file to a plurality of storage nodes according to the storage node network topology architecture and the preset file distribution configuration information.

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

[0077] The download address issuing unit 204 is configured to issue a download address of the target storage node to the IPC device, so that the IPC device downloads the IPC firmware upgrading file from the target storage node according to the download address for upgrading.

[0078] Further, the distribution retry control unit 200 is further configured to:

[0079] record the IPC firmware upgrading file that fails in distribution, and write the IPC firmware upgrading file that fails in distribution into a preset retry queue;

[0080] redistribute the IPC firmware upgrading file in the retry queue, and if the IPC firmware upgrading file still fails in distribution and a distribution failure number of the IPC firmware upgrading file does not reach a preset number threshold, then the IPC firmware upgrading file is written into the retry queue again until the IPC firmware upgrading file succeeds in distribution or the distribution failure number reaches the number threshold.

[0081] In addition, as shown in Figure 4 the application further provides an IPC firmware file upgrading control terminal embodiment, and the implementation types of the terminal include but are not limited to: a personal computer, an industrial computer, a server and an embedded intelligent device, and the main components of the terminal include: a memory 33 and a processor 31, and the memory 33 and the processor 31 can be connected through a communication bus 34.

[0082] The memory 33 is configured to store program code, and the program code is configured to implement the IPC firmware file upgrading control method provided in the above embodiment.

[0083] The processor 31 is configured to read and execute the program code.

[0084] Finally, the application further provides a computer readable storage medium embodiment, and the computer readable storage medium stores program code, and the program code is configured to be read and executed by the processor to implement the IPC firmware file upgrading 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 terminal, the device and the unit described above can refer to the corresponding processes in the foregoing method embodiments, and will not be described herein.

[0086] In several embodiments provided in the present application, it should be understood that the disclosed terminal, device and method can be implemented in other manners. For example, the described device embodiments are merely schematic. For example, the division of the units is merely a logical function division. There can be another division manner for the actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections between the units can be indirect couplings or communication connections through some interfaces, devices or units, and can be electrical, mechanical or in other forms.

[0087] The terms "first", "second", "third", "fourth" and the like in the description of the specification and the above drawings (if any) are used to distinguish similar objects, and are not necessarily used to describe a particular order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in other than the order shown or described herein. In addition, the terms "comprise" and "have" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a list of steps or units as an element does not necessarily limit those steps or units to the clearly listed ones, but can include other steps or units that are not clearly listed or inherent to such processes, methods, products or devices.

[0088] It should be understood that in the present application, "at least one" means one or more, and "multiple" means two or more. "And / or" is used to describe the association relationship of the associated objects, which means that there can be three relationships, for example, "A and / or B" can mean that there are three cases of only A, only B and A and B at the same time, where A and B can be singular or plural. The character " / " generally represents that the associated objects before and after are in an "or" relationship. "At least one of the following" or similar expressions means any combination of these items, including any combination of single or multiple 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, and c can be single or multiple.

[0089] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, i.e., they can be located in one place, or can be distributed on multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the embodiments.

[0090] In addition, each function unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software function unit.

[0091] When the integrated unit is realized in the form of a software function 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 solutions of the present application or the entire or part of the technical solutions that essentially contribute to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various program code storage media.

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

Claims

1. A method for controlling an IPC firmware file upgrade, characterized in that: include: Receive IPC firmware upgrade file; 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, determining a 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; 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. The IPC firmware file upgrade control method according to claim 1, wherein: 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, wherein: 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 successfully distributed or the number of distribution failures reaches the number threshold.

4. The IPC firmware file upgrade control method according to claim 1, wherein: Determining a 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: Determining, 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, wherein: 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 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 that the distribution service sub-node supporting the private network storage node can be used 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 IPC firmware upgrade files; A file distribution unit, configured to distribute the IPC firmware upgrade file to multiple storage nodes according to a storage node network topology architecture and preset file distribution configuration information; an upgrade instruction response unit, configured to, upon receiving a firmware upgrade instruction, determine a target storage node corresponding to the IPC device based on a file distribution record of the IPC firmware upgrade file and geographical and network attributes 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: Distribution retry control unit, used to: 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 successfully distributed 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 code, and the program code is used to implement an IPC firmware file upgrade control method according to any one of claims 1 to 6; The processor is configured to read and execute 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 according to any one of claims 1 to 6.

Images