Cross-node file transmission method and device based on TIPC protocol and medium

Abstract

The invention discloses a cross-node file transmission method and device based on a TIPC protocol and a medium, and the method comprises the steps: determining a TIPC address corresponding to each communication node in a TIPC cluster, and determining a service address corresponding to the communication node according to the TIPC address; creating a client and a server for TIPC file transmission based on a specified TIPC file transmission command, and setting TIPC configuration parameters and fragment transmission parameters; segmenting the to-be-transmitted file into a plurality of data packets according to a preset fragment transmission mode, and adjusting the data packets into a preset file transmission data packet frame format; and realizing cross-node file transmission of the data packet in the data packet frame format according to the service addresses corresponding to the client and the server and based on the TIPC file transmission command. According to the method, the resource overhead is reduced, the development cost is reduced, and the remote file transmission efficiency is improved.

Description

Technical Field

[0001] The present application relates to the technical field of data transmission, and in particular to a cross-node file transmission method, device and medium based on the TIPC protocol. Background Art

[0002] At present, in computer network technology, cluster networks are widely used in various large-scale computing systems and data centers as an efficient data processing and storage architecture. In cluster networks, file transfer between nodes is the basis of data sharing and exchange, and is crucial to the overall performance and stability of the system. Traditional file transfer methods mostly rely on the TCP / IP protocol stack, which addresses and communicates through IP addresses and port numbers. However, with the continuous development of network technology, the resource overhead and performance bottleneck of the TCP / IP protocol stack are gradually emerging in certain specific scenarios, such as Transparent Inter-Process Communication (TIPC) cluster networks.

[0003] As an inter-process communication protocol designed for cluster environments, TIPC has unique advantages such as link state awareness and service publishing, which can significantly improve the communication efficiency and reliability between nodes. However, in the existing TIPC cluster network, file transfer still uses the traditional TCP / IP protocol-based method, which not only increases network resource overhead, but also limits the full use of TIPC protocol features.

[0004] As a simple remote file transfer protocol, the Trivial File Transfer Protocol (TFTP) has the advantages of being simple to implement and easy to deploy, but it has obvious deficiencies in transmission efficiency, security, and reliability. Especially when transmitting large files, the length of each packet in the TFTP protocol is fixed at 512 bytes, resulting in low transmission efficiency; at the same time, due to the lack of encryption and verification mechanisms, there is a risk of files being tampered with during transmission; in addition, the TFTP protocol does not support a retransmission mechanism. Once data is lost or erroneous, manual intervention is required to resolve it, further reducing the reliability of file transmission. Summary of the invention

[0005] The embodiments of the present application provide a cross-node file transmission method, device and medium based on the TIPC protocol to solve the above technical problems.

[0006] On the one hand, an embodiment of the present application provides a cross-node file transmission method based on the TIPC protocol, including:

[0007] Determine a TIPC address corresponding to each communication node in the TIPC cluster, and determine a service address corresponding to the communication node based on the TIPC address;

[0008] Based on the specified TIPC file transfer command, create the TIPC file transfer client and server, and set the TIPC configuration parameters and fragment transmission parameters;

[0009] According to a preset fragment transmission mode, the file to be transmitted is divided into multiple data packets, and the data packets are adjusted to a preset file transmission data packet frame format;

[0010] According to the service addresses corresponding to the client and the server, and based on the TIPC file transfer command, cross-node file transfer of data packets in the data packet frame format is implemented.

[0011] In one implementation of the present application, the file to be transmitted is divided into multiple data packets according to a preset fragment transmission method, specifically including:

[0012] Determining the file size of the file to be transmitted, and calculating the number of data packets to be divided according to the file size and a preset data packet fragment size;

[0013] According to the preset fragmentation strategy, the file content in the to-be-transmitted file is segmented into data packets of a corresponding number of data packets, and a corresponding unique serial number is assigned to each data packet.

[0014] In one implementation of the present application, adjusting the data packet to a preset file transmission data packet frame format specifically includes:

[0015] Define the structure corresponding to the data packet frame format of file transfer; wherein the data packet frame format is the data packet sequence number, data packet type, data length, check code, reserved part and transmission file data content;

[0016] Each segmented data packet is encapsulated according to the defined data packet frame format, and the encapsulated data packet frame format is passed to the TIPC protocol layer.

[0017] In one implementation of the present application, each segmented data packet is encapsulated according to a defined data packet frame format, specifically including:

[0018] For each divided data packet, a data packet sequence number is filled in the front part of the data packet, and the data packet is uniquely identified by the data packet sequence number;

[0019] Fill in the data packet type corresponding to the data packet after the data packet sequence number, and fill in the data length field corresponding to the data packet after the data packet type according to the actual length of the data content in the data packet;

[0020] Calculate the check code corresponding to the data packet, and fill the check code field after the data length field;

[0021] A reserved portion is set after the check code field, a default value is filled in the reserved portion, and data content corresponding to the data packet is filled after the reserved portion.

[0022] In one implementation of the present application, determining the TIPC address corresponding to each communication node in the TIPC cluster specifically includes:

[0023] Query the configuration information of each communication node in the TIPC cluster; the configuration information includes the TIPC address, network ID and node ID;

[0024] According to the TIPC address corresponding to the communication node in the configuration information, a mapping relationship table between the TIPC address and the communication node is constructed.

[0025] In one implementation of the present application, determining the service address corresponding to the communication node according to the TIPC address specifically includes:

[0026] Querying the registration information of each communication node in the TIPC cluster when running a service, and querying the service address corresponding to the communication node according to the registration information of the communication node and the TIPC address;

[0027] The service address is associated with the communication node, and a corresponding relationship table between the service address and the communication node is generated.

[0028] In one implementation of the present application, based on a specified TIPC file transfer command, a TIPC file transfer client and a server are created, specifically including:

[0029] Acquire a number of historical TIPC file transfer records, and set a number of TIPC file transfer commands according to the number of historical TIPC file transfer records to generate a corresponding TIPC file transfer command set;

[0030] According to the specified TIPC file transfer command in the TIPC file transfer command set, a client and a server for TIPC file transfer are created.

[0031] In one implementation of the present application, according to the service addresses corresponding to the client and the server, and based on the TIPC file transfer command, cross-node file transmission of a data packet in a data packet frame format is implemented, specifically including:

[0032] Determine the service address corresponding to the communication node of the client and the service address corresponding to the communication node of the server;

[0033] Based on the service addresses corresponding to the client and the server, the client sends a TIPC file transfer command to the server, so that the server replies to the client with a corresponding file transfer confirmation command;

[0034] Based on the file transfer confirmation command, the client transmits the data packet in the data packet frame format to the server to achieve cross-node file transfer.

[0035] On the other hand, an embodiment of the present application further provides a cross-node file transfer device based on the TIPC protocol, the device comprising:

[0036] at least one processor;

[0037] and, a memory communicatively coupled to the at least one processor;

[0038] The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the above-mentioned cross-node file transfer method based on the TIPC protocol.

[0039] On the other hand, an embodiment of the present application further provides a non-volatile computer storage medium storing computer executable instructions, which, when executed, implement a cross-node file transfer method based on the TIPC protocol as described above.

[0040] The embodiments of the present application provide a cross-node file transmission method, device and medium based on the TIPC protocol, which at least have the following beneficial effects:

[0041] By determining the TIPC address of each communication node in the TIPC cluster and further mapping it to the corresponding service address, efficient resolution and precise positioning between communication nodes are achieved, which helps to reduce communication delays and improve the accuracy and speed of data transmission; based on the specified TIPC file transfer command, the client and server are created, and the TIPC configuration parameters and fragmentation transmission parameters are flexibly set, so that the file transfer system can be customized and optimized according to actual needs, which not only meets the file transfer needs in different scenarios, but also improves the adaptability and scalability of the system; using the preset fragmentation transmission method, the file to be transferred is divided into multiple data packets and adjusted to a specific file transfer data packet frame format, which effectively reduces the amount of data transmitted in a single time and reduces the error rate during the transmission process. At the same time, through the optimization of the frame format, the efficiency and stability of data transmission are further improved; according to the service addresses corresponding to the client and server of the TIPC file transfer, combined with the TIPC file transfer command, the seamless transmission of data packets in the data packet frame format between different communication nodes in the cluster is achieved. This cross-node file transfer capability not only enhances the distributed processing capability of the system, but also provides strong support for achieving efficient data sharing and collaborative work. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0043] Figure 1 A schematic diagram of a cross-node file transmission method based on the TIPC protocol provided in an embodiment of the present application;

[0044] Figure 2 A schematic diagram of the internal structure of a cross-node file transfer device based on the TIPC protocol provided in an embodiment of the present application. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0046] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0047] Figure 1 A flowchart of a cross-node file transfer method based on the TIPC protocol provided in an embodiment of the present application.

[0048] The analysis method involved in the embodiments of the present application can be implemented by a terminal device or a server, and the present application does not impose any special restrictions on this. For the convenience of understanding and description, the following embodiments are described in detail by taking a server as an example.

[0049] It should be noted that the server may be a single device or a system consisting of multiple devices, that is, a distributed server, and this application does not make any specific limitation on this.

[0050] like Figure 1 As shown, an embodiment of the present application provides a cross-node file transmission method based on the TIPC protocol, including:

[0051] 101. Determine a TIPC address corresponding to each communication node in the TIPC cluster, and determine a service address corresponding to the communication node according to the TIPC address.

[0052] The communication nodes in the TIPC cluster support addressing communication using service addresses. The TIPC service address consists of two parts: service type number: [service type]; service instance number: [service instance]. The TIPC used in this application supports identifying different sockets by service type and instance, thereby achieving isolation between services.

[0053] For TIPC-based remote file transfer services, a dedicated service type number, such as 1023, is agreed upon, and the service instance number uses the NODE field value in the TIPC address, which ensures the uniqueness of the service address of each cluster node.

[0054] For the convenience of description, the TIPC addresses of the three devices are agreed to be <1.10.1><1.10.2><1.10.3>. After each node goes online, it starts the pre-agreed service address: the service type number is 1023, and the service instance number is the NODE field value of each TIPC address. Based on this service, using the corresponding file transfer client, providing the service type and service instance number parameters, cross-node remote file transfer can be achieved.

[0055] Specifically, in one embodiment of the present application, determining the TIPC address corresponding to each communication node in the TIPC cluster specifically includes:

[0056] Query the configuration information of each communication node in the TIPC cluster; the configuration information includes the TIPC address, network ID and node ID;

[0057] According to the TIPC address corresponding to the communication node in the configuration information, a mapping relationship table between the TIPC address and the communication node is constructed.

[0058] In one embodiment, a query request is first sent to the TIPC cluster through a cluster management tool or command line interface to obtain the configuration information of each communication node. This configuration information is usually stored in the configuration file or database of the cluster and can be accessed through a specific query command or API. After receiving the configuration information, it is parsed to extract the TIPC address, network ID, and node ID of each communication node. This information is usually presented in a structured format (such as JSON, XML, or a table) to facilitate our parsing and processing.

[0059] Next, based on the parsed configuration information, a mapping table between TIPC addresses and communication nodes is constructed. This table can be a simple two-dimensional array or hash table, with the TIPC address as the key and the communication node (including its network ID and node ID) as the value. In this way, the corresponding communication node can be quickly found by the TIPC address. Finally, we verify the constructed mapping table to ensure its correctness and completeness. This can be achieved by sending a test message to the communication node in the cluster and checking whether it can be correctly routed to the target node according to the mapping table.

[0060] In one embodiment of the present application, determining the service address corresponding to the communication node according to the TIPC address specifically includes:

[0061] Query the registration information of each communication node in the TIPC cluster when running the service, and query the service address corresponding to the communication node based on the registration information and TIPC address of the communication node;

[0062] The service address is associated with the communication node, and a corresponding relationship table between the service address and the communication node is generated.

[0063] In one embodiment, in a TIPC cluster, a service running on each communication node will register a unique service address, which is associated with the TIPC address. Therefore, the service registration mechanism provided by the TIPC cluster is used to query the registration information of each communication node when running the service. This information usually includes the service name, service type, service status, and service address.

[0064] After obtaining the registration information, match the TIPC address therein with the TIPC address in the previously obtained communication node configuration information to determine the communication node corresponding to each service. Based on the matching results, extract the service address corresponding to each communication node from the registration information. This service address may be a combination of an IP address and a port, or another form of network address used to identify the access point of the service. Finally, associate the communication node with the service address and generate a correspondence table. This table can be a simple list or hash table that contains the identifier of the communication node (such as TIPC address, network ID, and node ID) and the corresponding service address.

[0065] The adopted TIPC optimizes the communication efficiency between nodes, increases the frequency of information exchange between nodes and reduces the waiting time between nodes by reducing the steps of establishing communication connections and the operations of addressing the target address.

[0066] 102. Based on the specified TIPC file transfer command, create a TIPC file transfer client and server, and set TIPC configuration parameters and fragment transmission parameters.

[0067] Specifically, in one embodiment of the present application, based on the specified TIPC file transfer command, creating a TIPC file transfer client and server includes:

[0068] Acquire a number of historical TIPC file transfer records, and set a number of TIPC file transfer commands according to the number of historical TIPC file transfer records to generate a corresponding TIPC file transfer command set;

[0069] Create the TIPC file transfer client and server according to the specified TIPC file transfer command in the TIPC file transfer command set.

[0070] In one embodiment, a feature-rich TIPC file transfer command is designed to support the creation of a TIPC file transfer client and server using the command.

[0071] First, we obtained several historical TIPC file transfer records from the log system of the TIPC cluster. These records include information such as the file name, size, transfer time, source node, and target node of the transfer. Through in-depth analysis of these historical records, we identified common transfer modes, such as regular backup, data migration, and real-time synchronization. At the same time, we also counted key indicators such as the transfer frequency, file size, and transfer duration of each mode.

[0072] Based on the analysis results, a series of TIPC file transfer commands are set up to meet different transmission requirements and optimize transmission performance. For example, for regular backup tasks, a scheduled transmission command is set; for data migration tasks, a batch transmission command is set. The above transmission commands are integrated to generate a TIPC file transfer command set. This command set contains a variety of transmission commands, each of which corresponds to a specific transmission scenario and requirement. Therefore, according to actual needs, the specified TIPC file transfer command is selected from the command set, and the TIPC file transfer client and server are created based on these commands. The client is responsible for initiating transmission requests, while the server is responsible for receiving and processing these requests.

[0073] 103. According to a preset fragment transmission mode, the file to be transmitted is divided into a plurality of data packets, and the data packets are adjusted to a preset file transmission data packet frame format.

[0074] Specifically, in one embodiment of the present application, according to a preset fragment transmission mode, the file to be transmitted is divided into multiple data packets, specifically including:

[0075] Determine the file size of the file to be transmitted, and calculate the number of data packets to be divided according to the file size and a preset data packet fragment size;

[0076] According to the preset fragmentation strategy, the file content in the file to be transmitted is segmented into a corresponding number of data packets, and a corresponding unique serial number is assigned to each data packet.

[0077] In one embodiment, first, the actual size of the file to be transmitted is obtained through the API of the file system, which is the basis for the subsequent fragmentation process. Then, according to the preset data packet fragment size (for example, the size of each data packet is 1MB), the number of data packets to be divided is calculated. This ensures that the size of each data packet is within a controllable range, which is convenient for network transmission.

[0078] An efficient fragmentation strategy is designed, which takes into account the internal structure of the file (such as file header, data segment, file tail, etc.) to ensure that each data packet contains a complete and meaningful data fragment. According to the fragmentation strategy, the file content in the file to be transmitted is segmented into the corresponding number of data packets using file read and write operations. Each data packet contains a part of the file content.

[0079] In order to ensure the order and integrity of the data packets, a unique sequence number is assigned to each data packet. This sequence number can be an increasing integer or other unique identifier. During the transmission process, the data packets are sent in the order of the sequence numbers. The receiving end receives and reassembles the data packets according to the sequence numbers to restore the original file.

[0080] By adopting the slice transmission method, the length of the data packet is not fixed. Users can customize the appropriate length according to the actual transmission efficiency, and the transmission efficiency is also greatly improved.

[0081] In one embodiment of the present application, adjusting the data packet to a preset file transmission data packet frame format specifically includes:

[0082] Define the structure corresponding to the data packet frame format of file transfer; wherein the data packet frame format includes the data packet sequence number, data packet type, data length, check code, reserved part and the data content of the transferred file;

[0083] Each segmented data packet is encapsulated according to the defined data packet frame format, and the encapsulated data packet frame format is passed to the TIPC protocol layer.

[0084] In one embodiment, in a large-scale file transmission system, in order to ensure that files can be transmitted efficiently and accurately, the following data packet frame format structure is defined:

[0085] Data packet sequence number: used to uniquely identify each data packet and plays a key role in file reassembly;

[0086] Data packet type: indicates which part of the file data the data packet is, such as the file header, file body, or file tail;

[0087] Data length: indicates the length of the file data content actually carried in the data packet;

[0088] Checksum: used to verify the integrity of the data packet to prevent data loss or tampering during transmission;

[0089] Reserved part: space reserved for possible future expansion or specific use;

[0090] Transfer file data content: the actual file data to be transferred.

[0091] Before file transmission, the large file is first divided into multiple data packets according to the preset fragmentation strategy. Then, each data packet is encapsulated according to the frame format defined above, including adding data packet sequence number, data packet type, data length, checksum and other information, and the encapsulated data packet is passed to the TIPC protocol layer for transmission.

[0092] In one embodiment of the present application, each segmented data packet is encapsulated according to a defined data packet frame format, specifically including:

[0093] For each divided data packet, fill in the data packet sequence number in the front part of the data packet, and uniquely identify the data packet by the data packet sequence number;

[0094] Fill in the data packet type corresponding to the data packet after the data packet sequence number, and fill in the data length field corresponding to the data packet after the data packet type according to the actual length of the data content in the data packet;

[0095] Calculate the checksum corresponding to the data packet and fill in the checksum field after the data length field;

[0096] A reserved part is set after the check code field, a default value is filled in the reserved part, and data content corresponding to the data packet is filled after the reserved part.

[0097] In one embodiment, in a file transmission system, an efficient data packet encapsulation method is adopted. For each segmented data packet, the data packet sequence number is filled in the front part thereof, and this sequence number is a unique identifier used to track and identify the data packet during the transmission and reception process. Following the data packet sequence number, the data packet type is filled in, which indicates the nature of the content carried by the data packet, such as a file header, a file body, or a file tail. According to the actual length of the data content in the data packet, the data length field is filled in after the data packet type to ensure that the receiving end can accurately parse and reassemble the file. Subsequently, the check code of the data packet is calculated and filled in the check code field to verify the integrity of the data packet. After the check code field, a reserved part is set and filled in with a default value for future expansion. Finally, the data content corresponding to the data packet is filled in after the reserved part to complete the encapsulation of the data packet.

[0098] Design a slicing transmission method to split a large file into multiple smaller data packets for transmission. Use a custom designed data packet frame format, where the front part of the data packet contains the data packet sequence number, type, data length and check code, and the back part is the transmitted file data content.

[0099] The data packet of the present invention adopts a self-defined frame format. Each data packet consists of a data header and data content. The data header contains the length of the data content of this transmission, MD5 check code, data packet sequence number and other information. The client will calculate and fill the length and MD5 value of the current data packet before sending the file. The server will parse and check the length and MD5 value of the current packet after receiving the data packet. Therefore, if an error occurs or the file is tampered with during the transmission process, it will be discovered in time after the server receives it and an error code will be returned through a response message.

[0100] 104. According to the service addresses corresponding to the client and the server, and based on the TIPC file transfer command, implement cross-node file transfer of the data packet in the data packet frame format.

[0101] Specifically, in one embodiment of the present application, according to the service addresses corresponding to the client and the server, and based on the TIPC file transfer command, cross-node file transfer of a data packet in a data packet frame format is implemented, specifically including:

[0102] Determine the service address corresponding to the communication node of the client and the service address corresponding to the communication node of the server;

[0103] Based on the service addresses corresponding to the client and the server, the client sends a TIPC file transfer command to the server, so that the server replies with a corresponding file transfer confirmation command to the client;

[0104] Based on the file transfer confirmation command, the client transmits the data packet in the data packet frame format to the server to realize cross-node file transfer.

[0105] In one embodiment, in a distributed file system, the client and the server are deployed on different communication nodes respectively. First, the system determines the service addresses of the client and the server respectively. Then, based on these address information, the client sends a TIPC file transfer command to the server, requesting the transfer of a specific file. After receiving the command, the server makes corresponding preparations and replies with a file transfer confirmation command to the client. Then, the client divides the file into multiple data packets according to the data packet frame format, and transmits them to the server in sequence. After receiving all the data packets, the server reorganizes and verifies them, and finally completes the cross-node transmission of the file.

[0106] In one embodiment, the present application supports a file retransmission mechanism. During the transmission process, if a slice data packet is lost or damaged due to network problems, the server will send a response message to the client after verification fails. After the client receives the response message, it only needs to retransmit the slice data packet according to the message error code, without retransmitting the entire file, which greatly improves the reliability and stability of file transmission.

[0107] The above is an embodiment of the method proposed in this application. Based on the same inventive concept, the embodiment of this application also provides a cross-node file transmission device based on the TIPC protocol, and its structure is as follows: Figure 2 shown.

[0108] Figure 2 The internal structure diagram of a cross-node file transfer device based on the TIPC protocol provided in an embodiment of the present application is shown in FIG. Figure 2 As shown, the device includes:

[0109] at least one processor;

[0110] and, a memory communicatively coupled to the at least one processor;

[0111] The memory stores instructions that can be executed by at least one processor, and the instructions are executed by at least one processor to enable the at least one processor to:

[0112] Determine the TIPC address corresponding to each communication node in the TIPC cluster, and determine the service address corresponding to the communication node based on the TIPC address;

[0113] Based on the specified TIPC file transfer command, create the TIPC file transfer client and server, and set the TIPC configuration parameters and fragment transmission parameters;

[0114] According to a preset fragment transmission mode, the file to be transmitted is divided into multiple data packets, and the data packets are adjusted to a preset file transmission data packet frame format;

[0115] According to the service addresses corresponding to the client and the server, and based on the TIPC file transfer command, cross-node file transfer of data packets in the data packet frame format is implemented.

[0116] The present application also provides a non-volatile computer storage medium storing computer executable instructions. When the computer executable instructions are executed, they can:

[0117] Determine the TIPC address corresponding to each communication node in the TIPC cluster, and determine the service address corresponding to the communication node based on the TIPC address;

[0118] Based on the specified TIPC file transfer command, create the TIPC file transfer client and server, and set the TIPC configuration parameters and fragment transmission parameters;

[0119] According to a preset fragment transmission mode, the file to be transmitted is divided into multiple data packets, and the data packets are adjusted to a preset file transmission data packet frame format;

[0120] According to the service addresses corresponding to the client and the server, and based on the TIPC file transfer command, cross-node file transfer of data packets in the data packet frame format is implemented.

[0121] Each embodiment in this application is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0122] The above describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the accompanying drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0123] The devices and media provided in the embodiments of the present application correspond one-to-one to the methods. Therefore, the devices and media also have similar beneficial technical effects as the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0124] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0125] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0126] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0127] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0128] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0129] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0130] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0131] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0132] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A cross-node file transmission method based on the TIPC protocol, characterized in that: The method comprises: Determine a TIPC address corresponding to each communication node in the TIPC cluster, and determine a service address corresponding to the communication node based on the TIPC address; Based on the specified TIPC file transfer command, create the TIPC file transfer client and server, and set the TIPC configuration parameters and fragment transmission parameters; According to a preset fragment transmission mode, the file to be transmitted is divided into multiple data packets, and the data packets are adjusted to a preset file transmission data packet frame format; According to the service addresses corresponding to the client and the server, and based on the TIPC file transfer command, cross-node file transfer of data packets in the data packet frame format is implemented.

2. According to the TIPC protocol-based cross-node file transmission method of claim 1, it is characterized in that: According to the preset fragment transmission mode, the file to be transmitted is divided into multiple data packets, including: Determining the file size of the file to be transmitted, and calculating the number of data packets to be divided according to the file size and a preset data packet fragment size; According to the preset fragmentation strategy, the file content in the to-be-transmitted file is segmented into data packets of a corresponding number of data packets, and a corresponding unique serial number is assigned to each data packet.

3. A cross-node file transmission method based on the TIPC protocol according to claim 1, characterized in that: The data packet is adjusted to the preset file transfer data packet frame format, including: Define the structure corresponding to the data packet frame format of file transfer; wherein the data packet frame format is the data packet sequence number, data packet type, data length, check code, reserved part and transmission file data content; Each segmented data packet is encapsulated according to the defined data packet frame format, and the encapsulated data packet frame format is passed to the TIPC protocol layer.

4. A cross-node file transmission method based on the TIPC protocol according to claim 3, characterized in that: Each segmented data packet is encapsulated according to the defined data packet frame format, including: For each divided data packet, a data packet sequence number is filled in the front part of the data packet, and the data packet is uniquely identified by the data packet sequence number; Fill in the data packet type corresponding to the data packet after the data packet sequence number, and fill in the data length field corresponding to the data packet after the data packet type according to the actual length of the data content in the data packet; Calculate the check code corresponding to the data packet, and fill the check code field after the data length field; A reserved portion is set after the check code field, a default value is filled in the reserved portion, and data content corresponding to the data packet is filled after the reserved portion.

5. The cross-node file transmission method based on the TIPC protocol according to claim 1, characterized in that: Determine the TIPC address corresponding to each communication node in the TIPC cluster, including: Query the configuration information of each communication node in the TIPC cluster; the configuration information includes the TIPC address, network ID and node ID; According to the TIPC address corresponding to the communication node in the configuration information, a mapping relationship table between the TIPC address and the communication node is constructed.

6. A cross-node file transmission method based on TIPC protocol according to claim 1, characterized in that: Determining, according to the TIPC address, a service address corresponding to the communication node, specifically includes: Querying the registration information of each communication node in the TIPC cluster when running a service, and querying the service address corresponding to the communication node according to the registration information of the communication node and the TIPC address; The service address is associated with the communication node, and a corresponding relationship table between the service address and the communication node is generated.

7. A cross-node file transmission method based on TIPC protocol according to claim 1, characterized in that: Based on the specified TIPC file transfer command, create the TIPC file transfer client and server, including: Acquire a number of historical TIPC file transfer records, and set a number of TIPC file transfer commands according to the number of historical TIPC file transfer records to generate a corresponding TIPC file transfer command set; According to the specified TIPC file transfer command in the TIPC file transfer command set, a client and a server for TIPC file transfer are created.

8. The cross-node file transmission method based on the TIPC protocol according to claim 1, characterized in that: According to the service addresses corresponding to the client and the server, and based on the TIPC file transfer command, cross-node file transfer of a data packet in a data packet frame format is implemented, specifically including: Determine the service address corresponding to the communication node of the client and the service address corresponding to the communication node of the server; Based on the service addresses corresponding to the client and the server, the client sends a TIPC file transfer command to the server, so that the server replies to the client with a corresponding file transfer confirmation command; Based on the file transfer confirmation command, the client transmits the data packet in the data packet frame format to the server to achieve cross-node file transfer.

9. A cross-node file transfer device based on the TIPC protocol, characterized in that: The device comprises: at least one processor; and, a memory communicatively coupled to the at least one processor; The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute a cross-node file transfer method based on the TIPC protocol as described in any one of claims 1-8.

10. A non-volatile computer storage medium storing computer executable instructions, characterized in that: When the computer executable instructions are executed, a cross-node file transmission method based on the TIPC protocol as described in any one of claims 1 to 8 is implemented.

Images