CN117201510A - File synchronization method, device, equipment and storage medium - Google Patents

Abstract

Embodiments of the present application provide a file synchronization method, device, equipment and storage medium. The method is applied to a first device and includes: obtaining subnet information of the device to be synchronized and file information to be synchronized; and obtaining records of synchronized files. information, and determine whether there is subnet information of the second device and file information that has been synchronized based on the subnet information of the device to be synchronized and the file information to be synchronized in the synchronization file. Among them, the subnet information of the second device and the file information that has been synchronized are the same as the subnet information of the device to be synchronized and the file information to be synchronized; the record information of the synchronization file is used to record the subnet information of the device that has completed file synchronization. and file information that has been synchronized. If it exists, a synchronization control instruction is sent to the second device; the synchronization control instruction is used to instruct the second device to transmit the file to be synchronized to the device to be synchronized. In this way, the efficiency of file synchronization can be improved.

Description

A file synchronization method, device, equipment and storage medium

Technical field

The present application relates to the field of data synchronization technology, and specifically to a file synchronization method, device, equipment and storage medium.

Background technique

Currently, in the field of coal mining industry, various equipment required for coal mining are managed through centralized control center equipment. Take hydraulic support equipment as an example. Hydraulic support equipment is a device that uses hydraulic pressure to achieve lifting, forward movement, etc., and perform roof support. It is a key equipment for comprehensive mechanized mining of coal mines and is of great significance to modern coal mine production. During the use of hydraulic support equipment, the centralized control center equipment can synchronize files to multiple hydraulic support equipment. For example, when a software upgrade package for the hydraulic support equipment is developed or model configuration of the hydraulic support equipment needs to be performed, the centralized control center equipment It is necessary to send software upgrade packages or model configuration files to multiple hydraulic support equipment to realize the upgrade and configuration of multiple hydraulic support equipment. Of course, the centralized control center equipment can also synchronize other files to the hydraulic support equipment. Among them, for multiple hydraulic support equipment of the same model, the files that need to be synchronized are the same.

In the existing technology, the coal mine industrial network contains multiple subnets. Usually, the centralized control center equipment and multiple hydraulic support equipment are in different subnets. For example, the centralized control center equipment is in subnet 1, and multiple hydraulic support equipment are in subnet 1. The rack device is in subnet 2. Therefore, when the centralized control center equipment synchronizes files to the hydraulic support equipment, it needs to transmit the files that need to be synchronized across subnets to multiple hydraulic support equipment. In the process of transferring files that need to be synchronized across subnets, the transferred data packets (files that need to be synchronized) need to pass through multiple routing nodes. Each time they pass through a routing node, the routing node needs to process the transmitted data packets, for example addressing, data encapsulation and data decapsulation, etc., so transferring files that need to be synchronized across subnets takes a long time and is inefficient. Moreover, when the centralized control center equipment needs to synchronize the same file to multiple hydraulic support equipment, the centralized control center equipment needs to send the files that need to be synchronized to each hydraulic support equipment, resulting in a larger load on the centralized control center equipment, further increasing This reduces the time required for file synchronization and reduces the efficiency of file synchronization.

Contents of the invention

In view of this, the present application provides a file synchronization method, device, equipment and storage medium to help solve the problem of low file synchronization efficiency in the prior art.

In a first aspect, embodiments of the present application provide a file synchronization method, which is applied to a first device. The method includes:

Obtain the subnet information of the device to be synchronized and the file information to be synchronized;

Obtain the record information of the synchronization file, and determine whether there is the subnet information of the second device and the file information that has been synchronized based on the subnet information of the device to be synchronized and the file information to be synchronized in the synchronization file; Wherein, the subnet information and synchronized file information of the second device are the same as the subnet information and file information to be synchronized of the device to be synchronized; the record information of the synchronized file is used to record the completed file synchronization. The subnet information of the device and the file information that has been synchronized;

If there is, a synchronization control instruction is sent to the second device; the synchronization control instruction is used to instruct the second device to transmit the file to be synchronized to the device to be synchronized.

A possible implementation method for the first aspect also includes:

Receive a synchronization completion response message returned by the second device;

The record information of the synchronized file is updated according to the subnet information of the device to be synchronized and the file information to be synchronized.

In a possible implementation of the first aspect, before obtaining the subnet information of the device to be synchronized and the file information to be synchronized, the method further includes:

Receive a synchronization file request message sent by the device to be synchronized; the synchronization file request message carries subnet information and file information to be synchronized;

Send a synchronization file response message to the device to be synchronized;

The obtaining the subnet information of the device to be synchronized and the file information to be synchronized includes:

Obtain the subnet information of the device to be synchronized and the file information to be synchronized from the synchronization file request message.

Preferably, the synchronization file request message also carries file transfer port information of the device to be synchronized; the file transfer port information is used to indicate the port used by the device to be synchronized for file transmission.

A possible implementation manner of the first aspect, before sending the synchronization control instruction to the second device, further includes:

Send a synchronization file notification message to the device to be synchronized;

Receive a synchronization file response message sent by the device to be synchronized, where the synchronization file response message carries file transfer port information of the device to be synchronized.

In a possible implementation manner of the first aspect, the synchronization control instruction carries file transfer port information of the device to be synchronized.

A possible implementation of the first aspect, if it exists, sending a synchronization control instruction to the second device includes:

If there is, and there are at least two second devices whose subnet information and synchronized file information are the same as the subnet information and file information to be synchronized of the device to be synchronized, obtain the at least two second devices. load information;

Determine a target second device according to the load information of the at least two second devices, and send a synchronization control instruction to the target second device.

In a possible implementation of the first aspect, the devices to be synchronized include at least two;

Determining the target second device based on the load information of the at least two second devices includes:

For each device to be synchronized among the at least two devices to be synchronized, a target second device corresponding to each device to be synchronized is determined based on the load information of the at least two second devices.

In a possible implementation manner of the first aspect, the first device and the device to be synchronized belong to different subnets.

A possible implementation method for the first aspect also includes:

If it does not exist, obtain the file to be synchronized according to the file information to be synchronized, and send the file to be synchronized to the device to be synchronized;

The record information of the synchronized file is updated according to the subnet information of the device to be synchronized and the file information to be synchronized.

In a second aspect, embodiments of the present application provide a file synchronization method, applied to a second device, and the method includes:

Receive a synchronization control instruction; the synchronization control instruction is used to instruct the second device to transmit the file to be synchronized to the device to be synchronized;

According to the synchronization control instruction, determine the file information to be synchronized and the device to be synchronized;

Obtain the file to be synchronized according to the file information to be synchronized, and send the file to be synchronized to the device to be synchronized.

A possible implementation method for the second aspect also includes:

Send a synchronization completion response message to the first device.

In a possible implementation of the second aspect, the synchronization control instruction carries file transfer port information of the device to be synchronized; the file transfer port information is used to indicate the port used by the device to be synchronized for file transmission;

Sending the file to be synchronized to the device to be synchronized includes:

Send the file to be synchronized to the device to be synchronized through the port indicated by the file transfer port information.

In the third aspect, embodiments of the present application provide a file synchronization method, including:

Receive files to be synchronized;

Update the corresponding file according to the file to be synchronized.

A possible implementation of the third aspect, before receiving the file to be synchronized, also includes:

Send a synchronization file request message to the first device; the synchronization file request message carries subnet information and file information to be synchronized;

Receive a synchronization file response message sent by the first device.

In a possible implementation of the third aspect, the synchronization file request message also carries file transfer port information of the device to be synchronized; the file transfer port information is used to indicate the port used by the device to be synchronized for file transmission.

A possible implementation of the third aspect, before receiving the file to be synchronized, also includes:

Receive a synchronization file notification message sent by the first device;

Send a synchronization file response message to the first device, where the synchronization file response message carries file transfer port information of the device to be synchronized.

In a possible implementation of the third aspect, receiving files to be synchronized includes:

The file to be synchronized is received through the port indicated by the file transfer port information.

In the fourth aspect, embodiments of the present application provide a file synchronization device, including:

The acquisition unit is used to obtain the subnet information of the device to be synchronized and the file information to be synchronized;

A processing unit configured to obtain the record information of the synchronization file, and determine whether the subnet information of the second device exists and has been completed based on the subnet information of the device to be synchronized and the file information to be synchronized in the synchronization file. Synchronized file information; wherein the subnet information of the second device and the synchronized file information are the same as the subnet information of the device to be synchronized and the file information to be synchronized; the record information of the synchronized file is used for Record the subnet information of the device that has completed file synchronization and the file information that has completed synchronization;

The processing unit is further configured to, if present, send a synchronization control instruction to the second device; the synchronization control instruction is used to instruct the second device to transmit the file to be synchronized to the device to be synchronized.

In a possible implementation of the fourth aspect, the file synchronization device further includes:

A receiving unit configured to receive a synchronization completion response message returned by the second device;

The processing unit is also configured to update the record information of the synchronization file according to the subnet information of the device to be synchronized and the file information to be synchronized.

In a possible implementation of the fourth aspect, the receiving unit is further configured to receive a synchronization file request message sent by the device to be synchronized; the synchronization file request message carries subnet information and file information to be synchronized;

The processing unit is also configured to send a synchronization file response message to the device to be synchronized;

The obtaining unit is specifically configured to obtain the subnet information of the device to be synchronized and the file information to be synchronized from the synchronization file request message.

In a possible implementation of the fourth aspect, the processing unit is further configured to send a synchronization file notification message to the device to be synchronized;

The receiving unit is also configured to receive a synchronization file response message sent by the device to be synchronized; the synchronization file response message carries the file transmission port information of the device to be synchronized.

In a possible implementation of the fourth aspect, the processing unit is specifically configured to, if there is one, subnet information of at least two second devices and file information that has been synchronized and subnet information of the device to be synchronized. and the file information to be synchronized are the same, then obtain the load information of the at least two second devices;

Determine a target second device according to the load information of the at least two second devices, and send a synchronization control instruction to the target second device.

In a possible implementation of the fourth aspect, the processing unit is specifically configured to determine, for each of the at least two devices to be synchronized, based on the load information of the at least two second devices, each device to be synchronized. The target second device corresponding to the synchronization device.

In a possible implementation of the fourth aspect, the processing unit is further configured to, if it does not exist, obtain the file to be synchronized based on the file information to be synchronized, and send the file to be synchronized to the device to be synchronized;

The processing unit is also configured to update the record information of the synchronization file according to the subnet information of the device to be synchronized and the file information to be synchronized.

In the fifth aspect, embodiments of the present application provide a file synchronization device, including:

A receiving unit, configured to receive a synchronization control instruction; the synchronization control instruction is used to instruct the second device to transmit the file to be synchronized to the device to be synchronized;

A processing unit, configured to determine the file information to be synchronized and the device to be synchronized according to the synchronization control instruction;

The processing unit is also configured to obtain the file to be synchronized according to the file information to be synchronized, and send the file to be synchronized to the device to be synchronized.

The processing unit is also configured to send a synchronization completion response message to the first device.

In a possible implementation manner of the fifth aspect, the processing unit is specifically configured to send the file to be synchronized to the device to be synchronized through a port indicated by the file transfer port information.

In a sixth aspect, embodiments of the present application provide a file synchronization device, including:

The receiving unit is used to receive files to be synchronized;

A processing unit, configured to update corresponding files according to the files to be synchronized.

In a possible implementation of the sixth aspect, the processing unit is further configured to send a synchronization file request message to the first device; the synchronization file request message carries subnet information and file information to be synchronized;

The receiving unit is also configured to receive a synchronization file response message sent by the first device.

In a possible implementation of the sixth aspect, the receiving unit is further configured to receive a synchronization file notification message sent by the first device;

The processing unit is further configured to send a synchronization file response message to the first device, where the synchronization file response message carries file transfer port information of the device to be synchronized.

In a possible implementation manner of the sixth aspect, the processing unit is specifically configured to receive the file to be synchronized through the port indicated by the file transfer port information.

In a seventh aspect, embodiments of the present application provide an electronic device, including:

A processor and a memory. The memory stores a computer program. When the computer program is executed, the electronic device causes the electronic device to execute any one of the first aspect, any one of the second aspect, or any one of the third aspect. method described.

In an eighth aspect, embodiments of the present application provide a storage medium. The storage medium includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute any one of the first aspect or the second aspect. The method described in any one of the aspects or any one of the third aspect.

Using the solution provided by the embodiment of this application, when the first device needs to synchronize a file to the device to be synchronized, the first device obtains the subnet information of the device to be synchronized and the file information to be synchronized; obtains the record information of the synchronized file, and based on Whether the subnet information of the device to be synchronized and the file information to be synchronized include the subnet information of the second device and the file information that has been synchronized when determining the record information of the synchronized file; among them, the subnet information of the second device and the file information that has been synchronized have been completed. The synchronized file information is the same as the subnet information of the device to be synchronized and the file information to be synchronized; the record information of the synchronized file is used to record the subnet information of the device that has completed file synchronization and the file information that has completed the synchronization. If it exists, a synchronization control instruction is sent to the second device; the synchronization control instruction is used to instruct the second device to transmit the file to be synchronized to the device to be synchronized. That is to say, the record information of the synchronization file records the subnet information of the device that has completed the file synchronization and the file information that has completed the synchronization. When it is necessary to synchronize the file to the device to be synchronized, the first device can obtain the subnet of the device to be synchronized. Network information and file information to be synchronized, and obtain record information of synchronized files. Then, according to the subnet information of the device to be synchronized and the file information to be synchronized, in the record information of the synchronized file, it is detected whether there is the subnet information of the second device and the file information that has completed synchronization. The subnet information of the second device and The file information that has been synchronized is the same as the subnet information of the device to be synchronized and the file information to be synchronized. If it exists, it means that the second device and the device to be synchronized are in the same subnet, and the second device stores files that need to be synchronized by the device to be synchronized. Therefore, the first device can send a synchronization control instruction to the second device, so that the second device The second device transmits the file to be synchronized to the device to be synchronized. In this way, when the first device needs to synchronize files to the device to be synchronized, if the subnet to which the first device belongs is different from the subnet to which the device to be synchronized belongs, and the subnet to which the second device and the device to be synchronized belong are the same, and the second device The files that need to be synchronized by the device to be synchronized have been synchronized, and the first device can schedule the second device to send the files to be synchronized to the device to be synchronized. Since the subnet to which the second device belongs is the same as the subnet to which the device to be synchronized belongs, compared to the first device directly transmitting the file to be synchronized across subnets to the device to be synchronized, the speed of the second device to transmit the file to be synchronized to the device to be synchronized is faster. Faster and more efficient.

Description of the drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required to be used in the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without exerting any creative effort.

Figure 1 is a schematic diagram of a file synchronization scenario provided by an embodiment of the present application;

Figure 2 is a schematic flow chart of another file synchronization method provided by an embodiment of the present application;

Figure 3 is a schematic flow chart of another file synchronization method provided by an embodiment of the present application;

Figure 4 is a schematic flow chart of another file synchronization method provided by an embodiment of the present application;

Figure 5 is a schematic flow chart of another file synchronization method provided by an embodiment of the present application;

Figure 6 is a schematic diagram of another file synchronization scenario provided by an embodiment of the present application;

Figure 7 is a schematic flow chart of another file synchronization method provided by an embodiment of the present application;

Figure 8 is a schematic structural diagram of a file synchronization device provided by an embodiment of the present application;

Figure 9 is a schematic structural diagram of another file synchronization device provided by an embodiment of the present application;

Figure 10 is a schematic structural diagram of another file synchronization device provided by an embodiment of the present application;

Figure 11 is a schematic structural diagram of another file synchronization device provided by an embodiment of the present application;

Figure 12 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

In order to better understand the technical solution of the present application, the embodiments of the present application will be described in detail below with reference to the accompanying drawings.

It should be clear that the described embodiments are only some of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without making creative efforts fall within the scope of protection of this application.

The terminology used in the embodiments of the present application is only for the purpose of describing specific embodiments and is not intended to limit the present application. As used in the embodiments and the appended claims, the singular forms "a," "the" and "the" are intended to include the plural forms as well, unless the context clearly dictates otherwise.

It should be understood that the term "and/or" used in this article is only an association relationship describing related objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A alone exists, and A and A exist simultaneously. B, there are three situations of B alone. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship.

Before giving a detailed introduction to the embodiments of the present application, terminology that is or may be applied in the embodiments of the present application is first explained.

Peer-to-Peer (P2P): Also known as peer-to-peer Internet technology, it is a new network technology that relies on the computing power and bandwidth of participants in the network, rather than relying on a few computers. on the server. P2P network is a peer-to-peer network that does not have a central server and relies on user group nodes for information exchange. Different from the traditional central server structure, each user node in the P2P network is both a client and a server, and can serve as a server to provide services to other nodes at the same time. Data can be shared between any two devices in a P2P network.

Network Address Translation (NAT): When some hosts within the private network have been assigned local IP (Internet Protocol, Internet Protocol) addresses (that is, private addresses used only within this private network), but they are When you want to communicate with a host on the Internet (without encryption), you can use the NAT method. This method requires installing NAT software on the router connecting the private network (private network IP) to the Internet (public network IP). A router equipped with NAT software is called a NAT router, and it has at least one valid external global IP address (public IP address). In this way, when all hosts using local addresses (private IP addresses) communicate with the outside world, their local addresses must be converted into global IP addresses on the NAT router before they can connect to the Internet.

NAT traversal: NAT traversal involves a common problem in TCP/IP networks, that is, the problem of establishing connections between hosts in a private TCP/IP network using NAT devices.

Router: It is a hardware device that connects two or more networks. It acts as a gateway between networks. It is a network device that reads the address in each data packet and then decides how to transmit it. It can understand different protocols, such as the Ethernet protocol used by a certain local area network, and the TCP (Transmission Control Protocol)/IP protocol used by the Internet. In this way, the router can analyze the destination addresses of data packets from various types of networks, convert the addresses of non-TCP/IP networks into TCP/IP addresses, or vice versa; and then route each data packet according to the selected routing algorithm. Deliver the best route to the specified location. So the router can connect non-TCP/IP networks to the Internet.

Switch: Switch means "switch" and is a network device used for forwarding electrical (optical) signals. It can provide an exclusive electrical signal path for any two network nodes connected to the switch. The most common switch is an Ethernet switch.

Among related technologies, in the field of coal mining industry, various equipment required for coal mining are managed through centralized control center equipment. Take hydraulic support equipment as an example. Hydraulic support equipment is a device that uses hydraulic pressure to achieve lifting, forward movement, etc., and perform roof support. It is a key equipment for comprehensive mechanized mining of coal mines and is of great significance to modern coal mine production. During the use of hydraulic support equipment, the centralized control center equipment can synchronize files to multiple hydraulic support equipment. For example, when a software upgrade package for the hydraulic support equipment is developed or model configuration of the hydraulic support equipment needs to be performed, the centralized control center equipment It is necessary to send software upgrade packages or model configuration files to multiple hydraulic support equipment to realize the upgrade and configuration of multiple hydraulic support equipment. Of course, the centralized control center equipment can also synchronize other files to the hydraulic support equipment. For multiple hydraulic support equipment of the same model, the files that need to be synchronized are the same.

In the existing technology, the coal mine industrial network contains multiple subnets, as shown in Figure 1. Usually, the centralized control center equipment and multiple hydraulic support equipment are in different subnets. For example, the centralized control center equipment is in a subnet. In 1, multiple hydraulic support equipment are located in subnet 2. Therefore, when the centralized control center equipment synchronizes files to the hydraulic support equipment, it needs to transmit the files that need to be synchronized across subnets to multiple hydraulic support equipment. In the process of transferring files that need to be synchronized across subnets, the transferred data packets (files that need to be synchronized) need to pass through multiple routing nodes. Each time they pass through a routing node, the routing node needs to process the transmitted data packets, for example addressing, data encapsulation and data decapsulation, etc., as shown in Figure 1, when the centralized control center device synchronizes files to the hydraulic support device 1, the data packet will arrive from the centralized control center device to the switch in subnet 1, and then to the router. The router then forwards the data packet to the switch in subnet 2, and the switch in subnet 2 transmits the data packet to hydraulic support device 1. Therefore, file synchronization across subnets takes a long time and is inefficient. Moreover, when the centralized control center equipment needs to synchronize the same file to hydraulic support equipment 1, hydraulic support equipment 2...hydraulic support equipment n, the centralized control center equipment needs to send the files that need to be synchronized to each hydraulic support equipment separately, resulting in centralized control The load on the central device is relatively large, which further increases the time required for file synchronization and reduces the efficiency of file synchronization.

In some technologies, file synchronization is achieved through peer-to-peer technology (Peer-to-Peer, P2P). P2P technology can be used to directly share content and distribute data between computers without going through a server, allowing data to be shared between any two machines on the Internet. become possible. In the coal mining industry scenario, it is assumed that the centralized control center equipment and the equipment required for coal mining are all equipment in the P2P network. P2P is usually used for communication between two devices across subnets. Since there is usually NAT between cross-subnet devices, Isolation, so it is necessary to obtain the NAT type through NAT detection, and then implement NAT traversal based on the results of the NAT detection to establish a connection path between devices for file transfer. However, the process of NAT traversal is complex and time-consuming, resulting in low efficiency in establishing connection paths between devices, thus making file transfer efficiency low. In addition, NAT detection may fail, resulting in NAT traversal being unable to be achieved, which in turn causes the connection path between devices to be unable to be established, and thus file transfer cannot be performed. Moreover, in a P2P network, if the two devices that need to transfer files are in the same subnet, then using P2P technology cannot achieve Layer 2 transmission between the two devices in the same subnet. NAT gateway is still required to intervene, resulting in transmission efficiency reduce. Therefore, for the method of using P2P technology to achieve file synchronization, NAT traversal between devices will affect the efficiency of file synchronization, and even cause file transfer failure when NAT detection fails. Moreover, for two devices in the same subnet, it is also necessary to NAT traversal cannot communicate directly, thus affecting the efficiency of file transfer between devices in the same subnet.

In response to the above problems, embodiments of the present application provide a file synchronization method, which is applied to the first device. The method includes: obtaining the subnet information of the device to be synchronized and the file information to be synchronized; obtaining the record information of the synchronized file, and Determine whether there is subnet information of the second device and completed synchronized file information based on the subnet information of the device to be synchronized and the file information to be synchronized in the synchronized file; wherein, the subnet information of the second device and the completed synchronized file information are The synchronized file information is the same as the subnet information of the device to be synchronized and the file information to be synchronized; the record information of the synchronized file is used to record the subnet information of the device that has completed file synchronization and the file information that has completed the synchronization. If it exists, a synchronization control instruction is sent to the second device; the synchronization control instruction is used to instruct the second device to transmit the file to be synchronized to the device to be synchronized. That is to say, the record information of the synchronization file records the subnet information of the device that has completed the file synchronization and the file information that has completed the synchronization. When it is necessary to synchronize the file to the device to be synchronized, the first device can obtain the subnet of the device to be synchronized. Network information and file information to be synchronized, and obtain record information of synchronized files. Then, according to the subnet information of the device to be synchronized and the file information to be synchronized, in the record information of the synchronized file, it is detected whether there is the subnet information of the second device and the file information that has completed synchronization. The subnet of the second device The information and the file information that has been synchronized are the same as the subnet information of the device to be synchronized and the file information to be synchronized. If it exists, it means that the second device and the first device are in the same subnet, and the second device stores files that need to be synchronized by the device to be synchronized. Therefore, the first device can send a synchronization control instruction to the second device, so that the second device can The second device transmits the file to be synchronized to the device to be synchronized.

In this way, when the first device needs to synchronize files to the device to be synchronized, if the subnet to which the first device belongs is different from the subnet to which the device to be synchronized belongs, and the subnet to which the second device and the device to be synchronized belong are the same, and the second device The files that need to be synchronized by the device to be synchronized have been synchronized, and the first device can schedule the second device to send the files to be synchronized to the device to be synchronized. Since the subnet to which the second device belongs is the same as the subnet to which the device to be synchronized belongs, compared to the first device directly transmitting the file to be synchronized across subnets to the device to be synchronized, the speed at which the second device transmits the file to be synchronized to the device to be synchronized is faster. Faster and more efficient. The details are explained below.

Refer to Figure 2, which is a schematic flow chart of a file synchronization method provided by an embodiment of the present application. The method is applied to the first device and includes the following steps:

Step S201: Obtain the subnet information of the device to be synchronized and the file information to be synchronized.

In this embodiment of the present application, the first device manages the devices in each subnet. For example, the first device manages the files configured in each device in each subnet, and is responsible for upgrading the files configured in each device. Updates etc. When technicians develop update files such as software upgrade packages and device model configuration files, these update files need to be synchronized to the corresponding devices so that the corresponding devices can update the files saved in them. Technical personnel cannot directly synchronize the update files to the corresponding devices. The first device that manages the devices in each subnet needs to be synchronized. In this embodiment of the present application, a file that needs to be updated by a device can be called a file to be synchronized, and a device that needs to be updated with a file can be called a device that needs to be synchronized. When the first device obtains the update file of the device to be synchronized, it can actively synchronize the update file to each device configured with the update file. Each device configured with the update file may also request the first device to synchronize the update file. That is, when the first device obtains the file to be synchronized, it can actively send the file to be synchronized to each device to be synchronized that is configured with the file to be synchronized. Each device configured with the file to be synchronized may also request the first device to synchronize the file to be synchronized.

When the first device determines that it needs to synchronize the file to be synchronized with the device to be synchronized, in order to improve the synchronization efficiency, a device that is located in the same subnet as the device to be synchronized and has completed synchronization of the file to be synchronized can perform the synchronization for the device to be synchronized. Synchronize. Based on this, the first device needs to obtain the subnet information of the device to be synchronized and the file information to be synchronized. That is, you need to first obtain the subnet in which the device to be synchronized is located, and which file needs to be synchronized by the device to be synchronized.

In some embodiments, when other devices are connected to the first device, the other devices need to report device-related information such as files configured in the other devices, identification information of the other devices, and subnet information to which the other devices belong, to the first device, so that The first device manages other devices. At this time, the first device can store device-related information reported by other devices. When the first device actively synchronizes files to be synchronized with other devices, first the first device can obtain the files to be synchronized from other devices or can receive files to be synchronized sent by technicians. The file information of the file to be synchronized can be determined, such as the file name, file size and other information of the file to be synchronized. Secondly, the first device can determine the device to be synchronized corresponding to the file to be synchronized based on the configuration files in other devices recorded in the stored device-related information, and determine the subnet information of the device to be synchronized based on the device-related information. That is, the first device obtains the subnet information of the device to be synchronized and the file information of the file to be synchronized.

When other devices request the first device to synchronize a file to be synchronized, the other device can carry its subnet information and the file information of the file to be synchronized in the request message, and the first device can obtain the file information of the device to be synchronized from the request message of the other device. Subnet information and file information to be synchronized.

Of course, the subnet information of the device to be synchronized and the file information to be synchronized can also be obtained through other methods, and this application does not limit this. For example, the first device may obtain the subnet information of the device to be synchronized through the third device based on the obtained file information to be synchronized. The third device may store the subnet information of each device, or the third device may obtain the subnet information from the device to be synchronized and return it to the first device.

As an example, take the first device actively synchronizing files to the device to be synchronized, assuming that the file to be synchronized is the configuration file of the hydraulic support device. When the first device obtains the file of the software configuration upgrade package of the hydraulic support device, for example, the first device may receive the file of the software configuration upgrade package of the hydraulic support device sent by other devices, and the first device may determine that the file to be synchronized is the hydraulic support. The device's configuration file. At this time, the first device can determine from the stored device-related information that the device to be synchronized corresponding to the file to be synchronized (software upgrade package of the hydraulic support device) is the hydraulic support device 1, and can also determine the subnet of the hydraulic support device 1 Information, for example, the subnet information of the hydraulic support equipment 1 may be that the subnet to which the hydraulic support equipment belongs is subnet 2. In this way, the first device can obtain the subnet information of the device to be synchronized and the file information to be synchronized.

As a possible implementation manner, the first device and the device to be synchronized belong to different subnets.

Specifically, a network can be divided into multiple subnets. The first device is a device that centrally manages other devices in each subnet. The subnet to which the first device belongs is different from the subnet to which the device managed by the first device belongs. At the same time, the first device needs to transmit the files to be synchronized across subnets to the device to be synchronized, resulting in low file synchronization efficiency. For example, the subnet to which the first device belongs is subnet 1, the subnet to which device A belongs is subnet 2, and the subnet to which device B belongs is subnet 3. If the first device directly synchronizes files to device A or device B, it needs to cross Subnet file transfer, but the process of file transfer across subnets is more complicated and the transfer efficiency is low.

Step S202: Obtain the record information of the synchronization file, and determine whether there is subnet information of the second device and synchronized file information in the record information of the synchronization file based on the subnet information of the device to be synchronized and the file information to be synchronized.

Among them, the subnet information of the second device and the file information that has been synchronized are the same as the subnet information of the device to be synchronized and the file information to be synchronized. The record information of synchronized files is used to record the subnet information of the device that has completed file synchronization and the file information that has completed synchronization.

In this embodiment of the present application, each time the first device completes file synchronization, it will record the subnet information of the synchronized device and the synchronized file information into the record information of the synchronized file, which is the record of the synchronized file. The information includes the subnet information of the device that has completed file synchronization and the file information that has completed synchronization. When the first device needs to synchronize a file to the device to be synchronized, since the first device and the device to be synchronized belong to different subnets, therefore, if the first device directly sends the file to be synchronized to the device to be synchronized, cross-subnet file transfer is required. Transmission, the cross-subnet transmission process is more complicated and less efficient. In this embodiment of the present application, the first device can find a second device that is in the same subnet as the device to be synchronized and has completed synchronization of the same file as the file to be synchronized, and the second device performs the file synchronization for the device to be synchronized. synchronization to achieve file synchronization within the same subnet and improve the efficiency of file synchronization. Based on this, the first device can obtain the recorded information of the recorded synchronization file. Among them, the record information of the synchronized file includes the subnet information of the device that has completed the file synchronization and the file information that has completed the synchronization. That is, the first device can obtain the record information of the synchronization file that records the subnet information of the device that has completed file synchronization and the file information of the file that the device has completed synchronization. The first device determines whether the subnet information of the second device and the file information that has been synchronized exist in the record information of the synchronization file based on the subnet information of the device to be synchronized and the file information to be synchronized. That is to say, the first device can determine whether there is subnet information that is the same as the subnet information of the device to be synchronized in the record information of the synchronization file based on the subnet information of the device to be synchronized and the file information to be synchronized, and the synchronization has been completed. The file information of the second device is the same as the file information of the file to be synchronized of the device to be synchronized, and the file information of the second device that has been synchronized has been completed. Wherein, the subnet information of the second device and the subnet information of the device to be synchronized are the same, that is, the second device and the device to be synchronized are in the same subnet.

Step S203: If it exists, send a synchronization control instruction to the second device.

Wherein, the synchronization control instruction is used to instruct the second device to transmit the file to be synchronized to the device to be synchronized.

In the embodiment of this application, if the first device determines that the subnet information of the second device and the file information that has completed synchronization exist in the record information of the synchronization file, it means that the subnet to which the second device belongs and the subnet to which the device to be synchronized belong The same means that the second device and the first device are in the same subnet, and the second device has synchronized the files to be synchronized with the device to be synchronized. At this time, the first device may send a synchronization control instruction to the second device. For example, the synchronization control instruction may include identification information of the device to be synchronized and file information to be synchronized, so that when the second device receives the synchronization control instruction, Transmit files to be synchronized to the device to be synchronized according to the synchronization control instructions. That is to say, when the first device needs to synchronize a file to be synchronized with the device to be synchronized, if the first device determines through the record information of the synchronization file that the subnet to which the second device belongs is the same as the subnet to which the device to be synchronized belongs, and the second device The file to be synchronized has been synchronized, then the first device can send a synchronization control instruction to the second device. Since the file to be synchronized has been stored in the second device, when the second device receives the synchronization control instruction, it can directly send the synchronization control instruction to the device to be synchronized. Transfer files to be synchronized. In this way, after the first device determines that the subnet to which the second device belongs is the same as the subnet to which the device to be synchronized belongs, and the second device has synchronized the file to be synchronized, it sends a synchronization control instruction to the second device, so that the second device The device transmits the files to be synchronized to the device to be synchronized, thereby completing file synchronization. Since the subnet information of the second device is the same as the subnet information of the device to be synchronized, that is, the second device and the device to be synchronized are in the same subnet, and files can be transferred directly between devices in the same subnet without going through multiple routes. , the transmission speed is faster, and the first device and the device to be synchronized belong to different subnets, and the process of cross-subnet file transfer is more complicated. Therefore, transferring the file to be synchronized from the second device to the device to be synchronized can improve the efficiency of file synchronization.

For example, assume that in a coal mining industry scenario, the first device is a centralized control center device, and the subnet to which the first device belongs is subnet 1. At this time, the first device obtains the software upgrade package of the hydraulic support equipment. The software upgrade package of the hydraulic support equipment is the file to be synchronized. It is assumed that the file information of the file to be synchronized is file B. Since the device-related information stored by the first device includes identification information of each device, subnet information of the device, identification information of files in the device, etc., for example, hydraulic support device C, the file configured in it is file B, which belongs to The subnet is subnet 2; the file configured in transport machine D is file E, and the subnet it belongs to is subnet 3. Therefore, based on the stored device-related information and the file information to be synchronized, the first device can determine that the device to be synchronized corresponding to the file information to be synchronized is the hydraulic support device C, and the subnet information of the hydraulic support device C is subnet 2. In this way, the first device can obtain that the subnet information of the device to be synchronized is subnet 2, and the file information to be synchronized is file B. Then, the first device can obtain the record information of the synchronization file. It is assumed that the record information of the synchronization file contains: hydraulic support equipment F, the subnet to which it belongs is subnet 2, and the file that has completed synchronization is file B; the transport machine G, to which the subnet belongs The network is subnet 3, and the file that has been synchronized is file E. According to the subnet information of the device to be synchronized and the file information to be synchronized, determine whether there is the subnet information of the second device and the file information that has completed synchronization in the record information of the synchronization file. Since the record information of the synchronization file records hydraulic pressure The subnet to which bracket device F belongs is subnet 2, and the file that has been synchronized is file B. At this time, the first device can determine that the subnet information of the second device and the file information that has been synchronized exist. The second device is It is hydraulic support equipment F. The first device sends a synchronization control instruction to the second device, so that after receiving the synchronization control instruction, the second device transmits the file to be synchronized to the device to be synchronized.

As a possible implementation manner, if the above exists, sending a synchronization control instruction to the second device includes:

If there is, and the subnet information and synchronized file information of at least two second devices are the same as the subnet information and file information of the device to be synchronized, obtain the load information of at least two second devices;

Determine a target second device based on the load information of at least two second devices, and send a synchronization control instruction to the target second device.

In the embodiment of the present application, the record information of the synchronization file records the subnet information of the device on which the first device has completed the file and the file information of the completed synchronization. Therefore, the first device searches the record information of the synchronization inquiry based on the subnet information of the device to be synchronized and the file information to be synchronized to see whether there is a second device that is the same as the subnet information of the device to be synchronized and the file information to be synchronized. When the subnet information and synchronized file information are obtained, there may be at least two second devices whose subnet information and synchronized file information are the same as those of the device to be synchronized and the file information to be synchronized. At this time, when there are subnet information of the second device and file information that has been synchronized, and there are at least two of them, it means that there are at least two second devices whose subnet information is the same as the subnet information of the device to be synchronized. And when the synchronized file information of at least two second devices is the same as the file information of the files to be synchronized of the device to be synchronized, the first device can obtain the load information of the at least two second devices. At this time, the first device may respectively send request messages to obtain the load information of the at least two second devices, and the at least two second devices inform the first device of the respective load information of the at least two second devices. The first device can also record the number of synchronization tasks assigned to each other device each time it controls other devices to synchronize files with the device to be synchronized, and obtain the number of synchronization tasks assigned to each second device. Obtain load information of at least two second devices. After obtaining the load information of each second device, the first device can determine the target second device corresponding to the device to be synchronized according to the load balancing principle based on the load information of each second device. That is, after obtaining the load information of each second device, the first device can determine the second device with a smaller number of loads recorded in the load information as the target second device corresponding to the device to be synchronized, realizing each The second device is load balanced to improve synchronization efficiency. After determining the target second device, the first device may send a synchronization control instruction to the target second device to control the target second device to synchronize files to be synchronized for the device to be synchronized.

It should be understood that the load information of the second device may be information on the number of synchronization tasks that the second device needs to perform file synchronization for other devices.

As a possible implementation, the devices to be synchronized include at least two. At this time, determining the target second device based on the load information of at least two second devices includes:

For each device to be synchronized among the at least two devices to be synchronized, a target second device corresponding to each device to be synchronized is determined based on the load information of the at least two second devices.

In this embodiment of the present application, when the first device needs to synchronize files to be synchronized for at least two devices to be synchronized, and it is determined that at least two second devices can synchronize files to be synchronized for at least two devices to be synchronized. , the first device can determine its corresponding target second device for each file to be synchronized. That is, for each of the at least two devices to be synchronized, the first device determines the target second device corresponding to each device to be synchronized based on the load information of the at least two second devices. In this way, it is possible The at least two second devices are load-balanced to synchronize files to be synchronized for at least two synchronization devices.

In this way, when the first device needs to synchronize files to the device to be synchronized, if the subnet to which the first device belongs is different from the subnet to which the device to be synchronized belongs, and the subnet to which the second device and the device to be synchronized belong are the same, and the second device The files that need to be synchronized by the device to be synchronized have been synchronized, and the first device can schedule the second device to send the files to be synchronized to the device to be synchronized. Since the second device and the device to be synchronized belong to the same subnet, compared with the first device directly transmitting the file to be synchronized across subnets to the device to be synchronized, the transmission of the file to be synchronized from the second device to the device to be synchronized is faster and more efficient. higher.

As a possible implementation manner, when the subnet information of the first device and the device to be synchronized is the same, file synchronization between the first device and the device to be synchronized can also be implemented through the above method. Although when the subnet information of the first device and the device to be synchronized is the same, the first device directly sends the file to be synchronized to the device to be synchronized without causing the problem of low file synchronization efficiency caused by cross-subnet file transfer. However, when there is When there are multiple devices to be synchronized, sending the files to be synchronized by the first device to multiple devices to be synchronized will cause the operating load of the first device to increase sharply, resulting in slower file synchronization, and also reducing the file synchronization efficiency to a certain extent. When using the above file synchronization method, the operating load of the first device can be reduced, thereby improving the efficiency of file synchronization.

Figure 3 is a schematic flowchart of another file synchronization method provided by an embodiment of the present application. The method is applied to the second device and specifically includes the following steps:

Step S301: Receive synchronization control instructions.

Wherein, the synchronization control instruction is used to instruct the second device to transmit the file to be synchronized to the device to be synchronized.

Specifically, when the first device determines that the subnet information and synchronized file information of the second device are the same as the subnet information and file information of the device to be synchronized, the first device will send a synchronization control to the second device. The synchronization control instruction may include the identification information of the device to be synchronized and the file information to be synchronized. The second device receives the synchronization control instruction and learns that it needs to transmit the file to be synchronized to the device to be synchronized.

Step S302: Determine the file information to be synchronized and the device to be synchronized according to the synchronization control instruction.

In this embodiment of the present application, the synchronization control instruction is used to instruct the second device to transmit the file to be synchronized to the device to be synchronized. By parsing the synchronization control instruction, the second device can obtain the file information to be synchronized and the device to be synchronized.

Step S303: Obtain the file to be synchronized according to the file information to be synchronized, and send the file to be synchronized to the device to be synchronized.

In this embodiment of the present application, after the second device parses the synchronization control instructions and obtains the file information to be synchronized, it can search for its own files based on the file information to be synchronized, and determine the files whose file information is the same as the file information to be synchronized. Treat it as a file to be synchronized. After obtaining the file to be synchronized, the second device can send the file to be synchronized to the determined device to be synchronized.

It should be understood that the second device is a device that has completed the file identified by the file information of the file to be synchronized, and the subnet information of the second device is the same as the subnet information of the device to be synchronized, so the second device and the device to be synchronized are in within the same subnet. Therefore, when the second device transmits the files to be synchronized to the device to be synchronized, the files are synchronized within the same subnet, and the file synchronization efficiency is high.

Figure 4 is a schematic flowchart of another file synchronization method provided by an embodiment of the present application. The method is applied to the device to be synchronized, and specifically includes the following steps:

Step S401: Receive files to be synchronized.

Specifically, when the device to be synchronized needs to synchronize a file, the first device may directly send the file to be synchronized to the device to be synchronized, or it may be a second device that belongs to the same subnet as the device to be synchronized and has already synchronized the file to be synchronized. Send the file to be synchronized to the device to be synchronized. At this time, the device to be synchronized may receive the file to be synchronized sent by the first device or the second device.

Step S402: Update the corresponding file according to the file to be synchronized.

Specifically, after receiving the file to be synchronized, the device to be synchronized can update the corresponding file in the device to be synchronized according to the file to be synchronized to complete the file synchronization.

In the embodiment of this application, there are two ways: the first device actively sends files to be synchronized to the device to be synchronized, and the device to be synchronized actively requests the first device for file synchronization. To explain more clearly, the first device and the second device and information interaction between devices to be synchronized. In this embodiment, the first device actively sends a file to be synchronized to the device to be synchronized as an example. Figure 5 is a schematic flow chart of another file synchronization method provided by an embodiment of the present application. . Specifically, it includes the following steps:

Step S501: The first device obtains the subnet information of the device to be synchronized and the file information to be synchronized.

For details, reference may be made to step S201, which will not be described again here.

As a possible implementation method, there may be a situation where at least two devices to be synchronized perform file synchronization. The device to be synchronized needs to determine the subnet information of at least two devices to be synchronized and the file information of the file to be synchronized. When at least two devices to be synchronized are of the same type, their files to be synchronized are the same.

Taking the hydraulic support equipment in the coal mine industry scenario as an example, multiple hydraulic support equipment need to upgrade file 1. When the types of multiple hydraulic support equipment are the same, the file 1 that needs to be upgraded for multiple hydraulic support equipment is the same, which is File 1 that needs to be updated is the same. Therefore, assuming that the first device obtains the software upgrade package file of file 1 of the hydraulic support device, the first device can determine that file 1 needs to be upgraded to multiple hydraulic support devices. At this time, the first device may determine the hydraulic support device that needs to upgrade file 1 as the device to be synchronized, and determine the software upgrade package file of file 1 as the file to be synchronized. At this time, the first device can determine multiple devices to be synchronized. By detecting the recorded device-related information, you can determine the subnet information of the device to be synchronized. Assume that the subnet information of multiple hydraulic support equipment is the same and they all belong to subnet 1. At this time, the first device can determine that the subnet information of the multiple devices to be synchronized belongs to subnet 1, assuming that the file information of the file to be synchronized is the file name of the file to be synchronized. At this time, the first device may determine that the file information of the files to be synchronized in the multiple devices to be synchronized is file 1.

Step S502: The first device sends a synchronization file notification message to the device to be synchronized, and the device to be synchronized receives the synchronization file notification message.

Specifically, before performing file synchronization, the first device needs to notify the device to be synchronized to perform file synchronization of file 1. At this time, the first device sends a synchronization file notification message to the device to be synchronized to inform the device to be synchronized that it needs to perform file synchronization. In one possible implementation, the synchronization file notification message carries file information of the files to be synchronized, so as to inform the device to be synchronized which files need to be synchronized. The device to be synchronized receives the synchronization file notification message sent by the first device, thereby learning that the first device needs to perform file synchronization on it, and can learn which files the first device needs to synchronize through the file information of the file to be synchronized carried in the synchronization file notification message. files are synchronized.

As a possible implementation manner, if there are at least two devices to be synchronized, the first device needs to send synchronization file notification messages to the at least two devices to be synchronized respectively.

Step S503: The device to be synchronized sends a synchronization file response message to the first device, and the first device receives the synchronization file response message sent by the device to be synchronized.

The synchronization file response message carries the file transfer port information of the device to be synchronized.

In the embodiment of this application, after receiving the synchronization file notification message, the device to be synchronized learns that the file needs to be synchronized. Since the device to be synchronized needs to perform file transmission through a specific port, the device to be synchronized will transfer the file of the device to be synchronized. The transmission port information is added to the synchronization file response message, and the synchronization file response message is sent to the first device. The first device receives the synchronization file response message sent by the device to be synchronized, and by parsing the synchronization file response message, learns the file transfer port information used by the device to be synchronized for file transmission.

As a possible implementation, when there are at least two devices to be synchronized, each device to be synchronized will return a synchronization file response message to the first device, and the first device receives the synchronization file response message sent by at least two devices to be synchronized. , and obtain the file transfer port information of each device to be synchronized by respectively parsing the synchronization file response messages sent by at least two devices to be synchronized.

Step S504: The first device obtains the record information of the synchronization file, and determines whether there is the subnet information of the second device and the completed synchronization in the record information of the synchronization file based on the subnet information of the device to be synchronized and the file information to be synchronized. File information.

For details, reference may be made to step S202, which will not be described again here.

It should be noted that when the first device determines whether the subnet information of the second device and the synchronized file information exist in the record information of the synchronization file, the following steps are different depending on the determination result. When it is determined that the subnet information of the second device and the file information that has been synchronized exist, steps S505a to S507a, step S508, step S509a and step S510 are executed; when it is determined that the subnet information of the second device does not exist and the synchronization has been completed. When the file information is obtained, step S505b, step S508 and step S510 are executed.

Step S505a: If it exists, the first device sends a synchronization control instruction to the second device, and the second device receives the synchronization control instruction.

The synchronization control instruction carries file transfer port information of the device to be synchronized.

Specifically, if it is determined that the subnet information of the second device and the file information that has been synchronized exist, it means that the subnet information of the second device and the file information that has been synchronized are the same as the subnet information of the device to be synchronized and the file to be synchronized. The information is the same, that is, the second device has completed synchronization with the device to be synchronized, and the second device and the device to be synchronized belong to the same subnet. At this time, the synchronization file can be transmitted from the second device to the device to be synchronized. After the first device receives the synchronization file response message sent by the device to be synchronized, it can learn the file transfer port information of the device to be synchronized by parsing the synchronization file response message, and adds the file transfer port information of the device to be synchronized to the synchronization control instruction. . The first device sends a synchronization control instruction to the second device, and the second device receives the synchronization control instruction. The second device can obtain the file transfer port information of the device to be synchronized by parsing the synchronization control instruction.

As a possible implementation method, if there are at least two second devices whose subnet information and synchronized file information are the same as those of the device to be synchronized and file information to be synchronized, then at least two second devices are obtained. Load information of the two devices; determine the target second device based on the load information of at least two second devices, and send a synchronization control instruction to the target second device.

Specifically, since there may be at least two second devices in the same subnet as the device to be synchronized, and the synchronization of the file to be synchronized has been completed, the subnets of at least two second devices will be recorded in the record information of the synchronization file. information and synchronized file information, so the first device will determine the subnet information and synchronized file information of at least two second devices in the record information of the synchronized file. When there are at least two second devices whose subnet information and synchronized file information are the same as those of the device to be synchronized and file information to be synchronized, a target second device needs to be selected among the at least two second devices. Device, used to synchronize files to be synchronized to the device to be synchronized.

At this time, the first device may obtain load information of at least two second devices, where the load information of the second device may be the number of file synchronization tasks that the second device needs to perform. For example, the first device may obtain the identification information of at least two second devices from the record information of the synchronization file, and send load information acquisition request messages to the at least two second devices respectively based on the identification information of the at least two second devices, After receiving the load information acquisition request message, each of the at least two second devices sends its own load information to the first device. Alternatively, the devices in each subnet can periodically actively send their own load information to the first device. When receiving the device load information, the first device can record the identification information of each device and the load information corresponding to each device. The first device may determine the load information corresponding to each of the at least two second devices in the recorded device load information based on the identification information of the at least two second devices. Alternatively, the first device may record the load information of each device, and the initial value of the load information of each device is zero. Since the file synchronization tasks of the device are all sent to it by the first device, the first device can Sending a file synchronization task once will update the load information of the device corresponding to the file synchronization task. The first device can obtain the load corresponding to each of at least two second devices from the recorded load information of the device. information. Of course, the load information corresponding to the second device can also be obtained through other methods, and this application does not limit this.

After obtaining the load information of at least two second devices, the target second device may be determined based on the load information of the at least two second devices. At this time, the first device can obtain the number of file synchronization tasks that each second device needs to perform based on the load information of at least two second devices. In order to achieve load balancing between at least two second devices, the required The second device that performs file synchronization with a smaller number is determined as the target second device, thereby achieving load balancing between at least two second devices. When the load information of at least two second devices is the same, one second device may be randomly selected as the target second device from the at least two second devices with the same load information. After the target second device is determined, a synchronization control instruction is sent to the target second device.

As a possible implementation manner, when there are at least two devices to be synchronized, determining the target second device based on the load information of the at least two second devices includes: for each of the at least two devices to be synchronized, The device determines the target second device corresponding to each device to be synchronized based on the load information of at least two second devices.

In the embodiment of this application, since there may be multiple devices of the same type in each subnet, for example, subnet 2 includes multiple hydraulic support devices, and multiple devices of the same type need to synchronize the same files, so the first device obtains After the file is synchronized, there will be multiple devices that need to synchronize the file to be synchronized. The first device determines at least two devices to be synchronized based on the stored device-related information. And if the first device determines at least two second devices, for each of the at least two devices to be synchronized, the first device can use load balancing as a criterion based on the load information of the at least two second devices. , determine the target second device corresponding to each device to be synchronized. That is, if there are at least two devices to be synchronized and at least two second devices, then for each device to be synchronized in the at least two devices to be synchronized, each device can be determined based on the load information of the at least two second devices. The number of file synchronization tasks that the second device needs to perform is based on the principle of achieving load balancing of at least two second devices, and the target second device corresponding to each device to be synchronized is determined. The load balancing of at least two second devices means that the number of file synchronization tasks to be performed by at least two second devices is relatively balanced.

For example, assume that the subnet to which the first device belongs is subnet 1, and there are two devices to be synchronized: device 1 and device 2. The first device determines the two devices based on the subnet information of the device to be synchronized and the file information to be synchronized. Two devices: device 3 and device 4. The subnets to which device 1, device 2, device 3 and device 4 belong are all subnet 2. The load information of device 3 obtained by the first device includes the number of file synchronization tasks that need to be executed, which is 2, and the load information of device 4 includes the number of file synchronization tasks that need to be executed, which is 4. When determining the target second device corresponding to two devices to be synchronized: device 1 and device 2, in order to achieve load balancing between the two second devices, the target second device corresponding to the first device to be synchronized (device 1) can be The device is determined as device 3, and the target second device corresponding to the second device to be synchronized (device 2) is also determined as device 3. In this way, the number of file synchronization tasks that need to be executed by device 3 and the files that need to be executed by device 4 The number of synchronization tasks is 4, so that load balancing between device 3 and device 4 can be achieved. Assume that the load information of device 3 includes the number of file synchronization tasks that need to be executed, which is 2, and the load information of device 4 includes that the number of file synchronization tasks that need to be executed is 3. In order to achieve load balancing between the two second devices, the second device can be The target second device corresponding to a device to be synchronized (device 1) is determined to be device 3. At this time, the number of file synchronization tasks that device 3 needs to perform and the number of file synchronization tasks that device 4 needs to perform will both be 3. When determining the target second device corresponding to the second device to be synchronized (device 2), one of device 3 and device 4 may be randomly selected as the target second device of the second device to be synchronized.

Step S505b: If it does not exist, the first device obtains the file to be synchronized based on the file information to be synchronized, and sends the file to be synchronized to the device to be synchronized, and the device to be synchronized receives the file to be synchronized.

Specifically, if the subnet information of the second device and the synchronized file information do not exist in the record information of the synchronized file, it means that the first device has not synchronized the file to be synchronized with other devices that have the same subnet information as the device to be synchronized. , the first device cannot synchronize the file to be synchronized to the device to be synchronized through a device in the same subnet as the device to be synchronized. At this time, the first device needs to directly synchronize the file to be synchronized with the device to be synchronized. The first device can obtain the file to be synchronized according to the file information to be synchronized, and send the file to be synchronized to the device to be synchronized.

For example, the first device may obtain and store multiple files that need to be synchronized from other devices or through other methods. The first device may determine the files to be synchronized among the multiple files that need to be synchronized based on the file information to be synchronized.

As a possible implementation manner, since the synchronization file response message returned by the device to be synchronized to the first device carries the file transfer port information of the device to be synchronized, therefore, it is determined that the record information of the synchronization file does not include the second device's sub-register. When the network information and the synchronized file information are obtained, the first device can send the file to be synchronized to the device to be synchronized through the file transfer port indicated by the obtained file transfer port information of the device to be synchronized, and the device to be synchronized receives the file to be synchronized through the file transfer port. document.

Step S506a: The second device determines the file information to be synchronized and the device to be synchronized according to the synchronization control instruction.

For details, reference may be made to step S302, which will not be described again here.

Step S507a: The second device sends the file to be synchronized to the device to be synchronized through the port indicated by the file transfer port information, and the device to be synchronized receives the file to be synchronized through the port indicated by the file transfer port information.

Specifically, the synchronization control command sent by the first device to the second device will carry the file transfer port information of the device to be synchronized. By parsing the synchronization control command, the second device can obtain the device to be synchronized carried in the synchronization control command for file transfer. The port used. When the second device sends the file to be synchronized to the device to be synchronized, it can send the file to be synchronized to the device to be synchronized through the port indicated by the file transfer port information, and the device to be synchronized receives the file sent by the second device through the port indicated by the file transfer port information. Files to be synchronized.

Assume that, as shown in Figure 6, the subnet to which the first device belongs is subnet 1. The first device obtains the file to be synchronized. For example, the file to be synchronized is file 1. According to the file information to be synchronized (file 1), it stores From the device-related information, it is determined that two devices to be synchronized (device 1 and device 2) are configured with file 1, and the subnet information of device 1 and device 2 is both subnet 2. That is to say, the first device can determine that both devices to be synchronized need to synchronize the file to be synchronized. The first device sends synchronization file notification messages to the two devices to be synchronized (device 1 and device 2) respectively to inform device 1 and device 2 that the files to be synchronized need to be transmitted to them. Then device 1 returns a synchronization file response message to the first device, and the synchronization file response message returned by device 1 carries the file transfer port information of device 1. At the same time, device 2 returns a synchronization file response message to the first device, and the synchronization file response message returned by device 2 carries the file transfer port information of device 2. By parsing the received synchronization file response messages returned by the two devices to be synchronized, the first device can learn the ports used by the two devices to be synchronized for file transmission.

Then, based on the subnet information of the device to be synchronized (subnet 2) and the file information to be synchronized (file 1), the first device determines that there are two second devices (device 3, device 4) in the record information of the synchronization file. ), that is to say, both device 3 and device 4 have completed synchronizing file 1, and both belong to subnet 2, which is the same as the subnet to which the device to be synchronized belongs. Since there are two second devices, the first device can send request messages to obtain their load information to device 3 and device 4 respectively, and receive the respective load information returned by device 3 and device 4. Assume that the load information of device 3 includes the number of file synchronization tasks that need to be executed, which is 3, and the load information of device 4 includes that the number of file synchronization tasks that need to be executed is 3. Therefore, in order to achieve load balancing between the two second devices, the target second device corresponding to the first device to be synchronized (device 1) can be determined as device 3, and the target second device corresponding to the second device to be synchronized (device 2) can be determined. The target second device is determined to be device 4. In this way, the number of file synchronization tasks that device 3 needs to perform and the number of file synchronization tasks that device 4 needs to perform are both 4, thus achieving load balancing between device 3 and device 4. . Then, the first device sends a synchronization control instruction to device 3, where the synchronization control instruction includes that the device to be synchronized is device 1, the file transfer port information of device 1, and the file information to be synchronized is file 1; at the same time, the first device sends Device 4 sends a synchronization control instruction, where the synchronization control instruction includes that the device to be synchronized is device 2, the file transmission port information of device 2 and the file information to be synchronized is file 1. After receiving the synchronization control instruction, device 3 obtains the stored file to be synchronized based on the file information to be synchronized carried in the synchronization control instruction, and transmits the file to the device to be synchronized ( Device 1) transmits the file to be synchronized, and device 1 receives the file to be synchronized through the port indicated by the file transfer port information. In the same way, after receiving the synchronization control command, device 4 obtains the stored file to be synchronized based on the file information to be synchronized carried in the synchronization control command, and transmits the file to the file to be synchronized through the file transfer port of device 2 carried in the synchronization control command. The synchronization device (device 2) transmits the file to be synchronized, and device 2 receives the file to be synchronized through the port indicated by the file transfer port information.

Step S508: The device to be synchronized updates the corresponding file according to the file to be synchronized.

For details, reference may be made to step S402, which will not be described again here.

Step S509a: The second device sends a synchronization completion response message to the first device, and the first device receives the synchronization completion response message returned by the second device.

Specifically, after the second device completes transmitting the file to be synchronized to the device to be synchronized, the second device may return a synchronization completion response message to the first device to inform the first device to complete synchronization of the file to be synchronized to the device to be synchronized. The first device receives the synchronization completion response message, and can learn based on the synchronization completion response message that the second device has completed transmitting the file to be synchronized to the device to be synchronized, and the file synchronization is completed.

Step S510: The first device updates the record information of the synchronization file according to the subnet information of the device to be synchronized and the file information to be synchronized.

In this embodiment of the present application, the first device will record the subnet information of the device and the file information that has been synchronized each time the file is synchronized, that is, the subnet information of the device and the synchronized file information that has been completed each time the file is synchronized. The record information of the synchronized file can be updated when the file information is obtained. After receiving the synchronization completion response message returned by the second device, the first device determines that file synchronization has been completed. At this time, the record information of the synchronized file is updated according to the subnet information of the device to be synchronized and the file information to be synchronized. For example, the identification information of the device to be synchronized, the subnet information of the device to be synchronized, and the file information to be synchronized can be added to the record information of the synchronization file.

In this embodiment of the present application, the device to be synchronized actively requests the first device for file synchronization as an example. As shown in Figure 7, it is a schematic flow chart of another file synchronization method provided by this embodiment of the present application. Specifically, it includes the following steps:

Step S701: The device to be synchronized sends a synchronization file request message to the first device, and the first device receives the synchronization file request message.

The synchronization file request message carries subnet information and file information to be synchronized.

In this embodiment of the present application, the device to be synchronized can actively request synchronization files from the first device. At this time, the device to be synchronized can send a synchronization file request message to the first device, and the first device receives the synchronization file request message sent by the device to be synchronized. .

As a possible implementation method, the synchronization file request message also carries the file transfer port information of the device to be synchronized.

The file transfer port information is used to indicate the port used by the device to be synchronized for file transfer.

In some embodiments, since the device to be synchronized needs to perform file transfer through a specified port, the device to be synchronized can add the file transfer port information to the synchronization file request message and send the synchronization file request message to the first device to Inform the first device of the file transfer port of the device to be synchronized.

Step S702: The first device sends a synchronization file response message to the device to be synchronized, and the device to be synchronized receives the synchronization file response message.

In this embodiment of the present application, after receiving the synchronization file response message sent by the device to be synchronized, if the first device can perform file synchronization for the device to be synchronized, it can send the synchronization file response message to the device to be synchronized, and the device to be synchronized receives the synchronization file response message. Synchronize the file response message, thereby learning that the first device agrees to perform file synchronization for it.

Step S703: The first device obtains the subnet information of the device to be synchronized and the file information to be synchronized from the synchronization file request message.

In the embodiment of this application, the synchronization file request message carries subnet information and file information to be synchronized. By parsing the synchronization file request message, the first device can learn the subnet information of the device to be synchronized carried in the synchronization file request message. and file information to be synchronized.

As a possible implementation, when the synchronization file request message sent by the device to be synchronized also carries the file transfer port information of the device to be synchronized, the first device can learn the device to be synchronized by parsing the synchronization file request message sent by the device to be synchronized. The port to use for file transfers.

Step S704: The first device obtains the record information of the synchronization file, and determines whether there is the subnet information of the second device and the completed synchronization in the record information of the synchronization file based on the subnet information of the device to be synchronized and the file information to be synchronized. File information.

For details, reference may be made to step S202, which will not be described again here. When it is determined that the subnet information of the second device and the file information that have been synchronized exist, perform steps S705a to S707a, step S708, step S709a and step S710; when it is determined that the subnet information of the second device does not exist and the synchronization has been completed. When the file information is obtained, execute step S705b, step S708 and step S710.

Step S705a: If it exists, send the synchronization control instruction to the second device, and the second device receives the synchronization control instruction.

For details, reference may be made to step S505a, which will not be described again here.

It should be noted that when the device to be synchronized actively requests the first device for file synchronization, there may also be at least two second devices. When there are at least two second devices, the specific execution steps may refer to step S505a.

Step S705b: If it does not exist, the first device obtains the file to be synchronized based on the file information to be synchronized, and sends the file to be synchronized to the device to be synchronized, and the device to be synchronized receives the file to be synchronized.

For details, please refer to step S505b, which will not be described again here.

Step S706a: The second device determines the file information to be synchronized and the device to be synchronized according to the synchronization control instruction.

For details, reference may be made to step S302, which will not be described again here.

Step S707a: The second device sends the file to be synchronized to the device to be synchronized through the port indicated by the file transfer port information, and the device to be synchronized receives the file to be synchronized through the port indicated by the file transfer port information.

For details, reference may be made to step S507a, which will not be described again here.

Step S708: The device to be synchronized updates the corresponding file according to the file to be synchronized.

For details, reference may be made to step S402, which will not be described again here.

Step S709a: The second device sends a synchronization completion response message to the first device, and the first device receives the synchronization completion response message returned by the second device.

For details, reference may be made to step S509a, which will not be described again here.

Step S710: The first device updates the record information of the synchronization file according to the subnet information of the device to be synchronized and the file information to be synchronized.

For details, reference may be made to step S510, which will not be described again here.

In this way, according to the method described in Figure 5 or Figure 7 above, when the first device needs to synchronize files with the device to be synchronized, if the subnet to which the first device belongs is different from the subnet to which the device to be synchronized belongs, and the second device is different from the subnet to which the device to be synchronized belongs. If the devices to be synchronized belong to the same subnet, and the second device has synchronized the files that the device to be synchronized needs to synchronize, then the first device can schedule the second device to send the files to be synchronized to the device to be synchronized. Since the subnet to which the second device belongs is the same as the subnet to which the device to be synchronized belongs, compared to the first device directly transmitting the file to be synchronized across subnets to the device to be synchronized, the speed at which the second device transmits the file to be synchronized to the device to be synchronized is faster. Faster and more efficient. Moreover, compared with P2P technology, the method described in the above embodiment does not require NAT detection and NAT traversal, and can reduce the complexity of file synchronization. At the same time, for the second device under the same subnet and the device to be synchronized, the second device can directly send the file to be synchronized to the device to be synchronized, and file transfer between devices under the same subnet can be realized without NAT traversal.

Figure 8 is a schematic structural diagram of a file synchronization device provided by an embodiment of the present application. As shown in Figure 8, the device includes:

The obtaining unit 801 is used to obtain the subnet information of the device to be synchronized and the file information to be synchronized.

The processing unit 802 is used to obtain the record information of the synchronization file, and determine whether there is subnet information of the second device and the files that have been synchronized based on the subnet information of the device to be synchronized and the file information to be synchronized in the synchronization file. information.

Among them, the subnet information of the second device and the file information that has completed synchronization are the same as the subnet information and file information of the device to be synchronized. The record information of the synchronization file is used to record the subnet information of the device that has completed file synchronization. and file information that has been synchronized.

The processing unit 802 is also configured to, if present, send a synchronization control instruction to the second device. The synchronization control instruction is used to instruct the second device to transmit the file to be synchronized to the device to be synchronized.

As a possible implementation, as shown in Figure 9, the file synchronization device further includes:

The receiving unit 803 is configured to receive the synchronization completion response message returned by the second device.

The processing unit 802 is also configured to update the record information of the synchronization file according to the subnet information of the device to be synchronized and the file information to be synchronized.

As a possible implementation, the receiving unit 803 is also used to receive a synchronization file request message sent by the device to be synchronized; the synchronization file request message carries subnet information and file information to be synchronized;

The processing unit 802 is also configured to send a synchronization file response message to the device to be synchronized.

The obtaining unit 801 is specifically configured to obtain the subnet information of the device to be synchronized and the file information to be synchronized from the synchronization file request message.

As a possible implementation, the processing unit 802 is also configured to send a synchronization file notification message to the device to be synchronized;

The receiving unit 803 is also configured to receive a synchronization file response message sent by the device to be synchronized; the synchronization file response message carries the file transfer port information of the device to be synchronized.

As a possible implementation, the processing unit 802 is specifically configured to, if there is, at least two subnet information and synchronized file information of the second device and subnet information of the device to be synchronized and files to be synchronized. If the information is the same, the load information of at least two second devices is obtained.

Determine a target second device according to the load information of the at least two second devices, and send a synchronization control instruction to the target second device.

As a possible implementation, the processing unit 802 is specifically configured to determine, for each of the at least two devices to be synchronized, a target corresponding to each device to be synchronized based on the load information of at least two second devices. Secondary device.

As a possible implementation manner, the processing unit 802 is also configured to obtain the file to be synchronized according to the file information to be synchronized if it does not exist, and send the file to be synchronized to the device to be synchronized.

The processing unit 802 is also configured to update the record information of the synchronization file according to the subnet information of the device to be synchronized and the file information to be synchronized.

Figure 10 is a schematic structural diagram of another file synchronization device provided by an embodiment of the present application. As shown in Figure 10, the device includes:

The receiving unit 1001 is used to receive synchronization control instructions. The synchronization control instruction is used to instruct the second device to transmit the file to be synchronized to the device to be synchronized.

The processing unit 1002 is configured to determine the file information to be synchronized and the device to be synchronized according to the synchronization control instruction.

The processing unit 1002 is also configured to obtain the file to be synchronized according to the file information to be synchronized, and send the file to be synchronized to the device to be synchronized.

The processing unit 1002 is also configured to send a synchronization completion response message to the first device.

As a possible implementation manner, the processing unit 1002 is specifically configured to send the file to be synchronized to the device to be synchronized through the port indicated by the file transfer port information.

Figure 11 is a schematic structural diagram of another file synchronization device provided by an embodiment of the present application. As shown in Figure 11, the device includes:

The receiving unit 1101 is used to receive files to be synchronized.

The processing unit 1102 is used to update the corresponding files according to the files to be synchronized.

As a possible implementation manner, the processing unit 1102 is also configured to send a synchronization file request message to the first device. The synchronization file request message carries subnet information and file information to be synchronized.

The receiving unit 1101 is also configured to receive a synchronization file response message sent by the first device.

As a possible implementation manner, the receiving unit 1101 is also configured to receive a synchronization file notification message sent by the first device.

The processing unit 1102 is also configured to send a synchronization file response message to the first device, where the synchronization file response message carries file transfer port information of the device to be synchronized.

As a possible implementation manner, the processing unit 1102 is specifically configured to receive the file to be synchronized through the port indicated by the file transfer port information.

Corresponding to the above embodiments, this application also provides an electronic device. FIG. 12 is a schematic structural diagram of an electronic device provided by an embodiment of the present invention. The electronic device 1200 may include: a processor 1201, a memory 1202, and a communication unit 1703. These components communicate through one or more buses. Those skilled in the art can understand that the structure of the server shown in the figure does not constitute a limitation on the embodiment of the present invention. It can be either a bus structure or a star structure. , may also include more or fewer components than shown, or combinations of certain components, or different component arrangements.

The communication unit 1203 is used to establish a communication channel so that the electronic device can communicate with other devices. Receive user data from other devices or send user data to other devices.

The processor 1201 is the control center of the electronic device, using various interfaces and lines to connect various parts of the entire electronic device, by running or executing software programs and/or modules stored in the memory 1202, and calling the software programs stored in the memory 1202. data to perform various functions of the electronic device and/or process data. The processor may be composed of an integrated circuit (IC), for example, it may be composed of a single packaged IC, or it may be composed of multiple packaged ICs connected with the same function or different functions. For example, the processor 1201 may only include a central processing unit (CPU). In the embodiment of the present invention, the CPU may be a single computing core or may include multiple computing cores.

The memory 1202 is used to store execution instructions of the processor 1201. The memory 1202 can be implemented by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically Erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

When the execution instructions in the memory 1202 are executed by the processor 1201, the electronic device 1200 is enabled to execute some or all of the steps in the embodiment shown in FIG. 2 or FIG. 3 or FIG. 4.

In specific implementation, the present invention also provides a storage medium, wherein the storage medium can store a program, and when executed, the program can include some or all of the steps in each embodiment of the file synchronization method provided by the present invention. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM) or a random access memory (RAM), etc.

Those skilled in the art can clearly understand that the technology in the embodiments of the present invention can be implemented by means of software plus the necessary general hardware platform. Based on this understanding, the technical solutions in the embodiments of the present invention can be embodied in the form of software products in essence or those that contribute to the existing technology. The computer software products can be stored in storage media, such as ROM/RAM. , magnetic disk, optical disk, etc., including a number of instructions to cause a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in various embodiments or certain parts of the embodiments of the present invention.

The same and similar parts among the various embodiments in this specification can be referred to each other. In particular, for the device embodiment and the terminal embodiment, since they are basically similar to the method embodiment, the description is relatively simple. For relevant details, please refer to the description in the method embodiment.

Claims (23)

1. A method of file synchronization, for use with a first device, the method comprising:

acquiring subnet information of equipment to be synchronized and file information to be synchronized;

acquiring record information of a synchronous file, and determining whether subnet information of a second device and file information which is synchronized are present in the record information of the synchronous file according to the subnet information of the device to be synchronized and the file information to be synchronized; the subnet information of the second equipment and the file information which is synchronized are the same as the subnet information of the equipment to be synchronized and the file information to be synchronized; the recording information of the synchronous file is used for recording the subnet information of the equipment which completes the file synchronization and the file information which completes the synchronization;

if yes, a synchronous control instruction is sent to the second equipment; the synchronization control instruction is used for indicating the second equipment to transmit the file to be synchronized to the equipment to be synchronized.

2. The method as recited in claim 1, further comprising:

receiving a synchronization completion response message returned by the second equipment;

and updating the record information of the synchronous file according to the subnet information of the equipment to be synchronized and the file information to be synchronized.

3. The method according to claim 1, further comprising, before the acquiring the subnet information of the device to be synchronized and the file information to be synchronized:

receiving a synchronous file request message sent by the equipment to be synchronized; the synchronous file request message carries subnet information and file information to be synchronized;

sending a synchronous file response message to the equipment to be synchronized;

the acquiring the subnet information of the equipment to be synchronized and the file information to be synchronized comprises the following steps:

and acquiring the subnet information of the equipment to be synchronized and the file information to be synchronized from the synchronous file request message.

4. A method according to claim 3, wherein the synchronization file request message also carries file transfer port information of the device to be synchronized; the file transmission port information is used for indicating a port used when the device to be synchronized performs file transmission.

5. The method of claim 1, further comprising, prior to said sending the synchronization control instruction to the second device:

sending a synchronous file notification message to the equipment to be synchronized;

receiving a synchronous file response message sent by the equipment to be synchronized; and the synchronous file response message carries the file transmission port information of the equipment to be synchronized.

6. The method according to claim 3 or 4, wherein the synchronization control instruction carries file transfer port information of the device to be synchronized.

7. The method of claim 1, wherein the sending a synchronization control instruction to the second device, if any, comprises:

if the information exists, and the subnet information and the file information which are synchronized are the same as the subnet information and the file information to be synchronized of the equipment to be synchronized, the load information of the at least two second equipment is obtained;

and determining a target second device according to the load information of the at least two second devices, and sending a synchronous control instruction to the target second device.

8. The method according to claim 7, wherein the device to be synchronized comprises at least two;

The determining the target second device according to the load information of the at least two second devices comprises:

and determining a target second device corresponding to each device to be synchronized according to the load information of the at least two second devices aiming at each device to be synchronized in the at least two devices to be synchronized.

9. The method of claim 1, wherein the first device is different from a subnet to which the device to be synchronized belongs.

10. The method as recited in claim 1, further comprising:

if the file information to be synchronized does not exist, acquiring a file to be synchronized according to the file information to be synchronized, and sending the file to be synchronized to the equipment to be synchronized;

and updating the record information of the synchronous file according to the subnet information of the equipment to be synchronized and the file information to be synchronized.

11. A method of file synchronization, for use with a second device, the method comprising:

receiving a synchronous control instruction; the synchronization control instruction is used for indicating the second equipment to transmit a file to be synchronized to the equipment to be synchronized;

determining file information to be synchronized and equipment to be synchronized according to the synchronization control instruction;

and acquiring a file to be synchronized according to the file information to be synchronized, and sending the file to be synchronized to the equipment to be synchronized.

12. The method as recited in claim 11, further comprising:

and sending a synchronization completion response message to the first device.

13. The method of claim 11, wherein the synchronization control instruction carries file transfer port information of the device to be synchronized; the file transmission port information is used for indicating a port used when the equipment to be synchronized performs file transmission;

the sending the file to be synchronized to the device to be synchronized includes:

and sending the file to be synchronized to the equipment to be synchronized through the port indicated by the file transmission port information.

14. A method for synchronizing files, comprising:

receiving a file to be synchronized;

and updating the corresponding file according to the file to be synchronized.

15. The method of claim 14, further comprising, prior to said receiving the file to be synchronized:

sending a synchronous file request message to a first device; the synchronous file request message carries subnet information and file information to be synchronized;

and receiving a synchronous file response message sent by the first equipment.

16. The method according to claim 15, wherein the synchronization file request message further carries file transfer port information of the device to be synchronized; the file transmission port information is used for indicating a port used when the device to be synchronized performs file transmission.

17. The method of claim 14, further comprising, prior to said receiving the file to be synchronized:

receiving a synchronous file notification message sent by the first equipment;

and sending a synchronous file response message to the first device, wherein the synchronous file response message carries the file transmission port information of the device to be synchronized.

18. The method according to claim 16 or 17, wherein receiving the file to be synchronized comprises:

and receiving the file to be synchronized through the port indicated by the file transmission port information.

19. A document synchronization apparatus, comprising:

the acquisition unit is used for acquiring the subnet information of the equipment to be synchronized and the file information to be synchronized;

the processing unit is used for acquiring the record information of the synchronous file, and determining whether the subnet information of the second equipment and the file information which is synchronized exist according to the subnet information of the equipment to be synchronized and the record information of the file information to be synchronized in the synchronous file; the subnet information of the second equipment and the file information which is synchronized are the same as the subnet information of the equipment to be synchronized and the file information to be synchronized; the recording information of the synchronous file is used for recording the subnet information of the equipment which completes the file synchronization and the file information which completes the synchronization;

The processing unit is further configured to send a synchronization control instruction to the second device if the synchronization control instruction exists; the synchronization control instruction is used for indicating the second equipment to transmit the file to be synchronized to the equipment to be synchronized.

20. A document synchronization apparatus, comprising:

the receiving unit is used for receiving the synchronous control instruction; the synchronization control instruction is used for indicating the second equipment to transmit a file to be synchronized to the equipment to be synchronized;

the processing unit is used for determining file information to be synchronized and equipment to be synchronized according to the synchronization control instruction;

the processing unit is further configured to obtain a file to be synchronized according to the file information to be synchronized, and send the file to be synchronized to the device to be synchronized.

21. A document synchronization apparatus, comprising:

the acquisition unit is used for receiving the file to be synchronized;

and the processing unit is used for updating the corresponding file according to the file to be synchronized.

22. An electronic device, comprising: a processor and a memory storing a computer program that, when executed, causes the electronic device to perform the method of any one of claims 1-10 or 11-13 or 14-18.

23. A storage medium comprising a stored program, wherein the program, when run, controls a device in which the storage medium is located to perform the method of any one of claims 1-10 or 11-13 or 14-18.