CN115987975A - File transmission method, system and computer readable storage medium - Google Patents
File transmission method, system and computer readable storage medium Download PDFInfo
- Publication number
- CN115987975A CN115987975A CN202211729701.XA CN202211729701A CN115987975A CN 115987975 A CN115987975 A CN 115987975A CN 202211729701 A CN202211729701 A CN 202211729701A CN 115987975 A CN115987975 A CN 115987975A
- Authority
- CN
- China
- Prior art keywords
- file
- transmitted
- transmission
- identifier
- data packets
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Abstract
The invention provides a file transmission method, a file transmission system and a computer readable storage medium, wherein the method comprises the following steps: opening a file to be transmitted through a unified extensible firmware interface; slicing a file to be transmitted to obtain a plurality of slices; preprocessing each slice to obtain a plurality of data packets; and sequentially transmitting each data packet to a receiving end according to a transmission control protocol. According to the method, the function of file transmission can be realized on the basis of unifying the extensible firmware interface, and files with any size can be transmitted, so that the efficiency of data transmission is improved.
Description
Technical Field
The present invention relates to the field of data transmission technologies, and in particular, to a file transmission method, a file transmission system, and a computer-readable storage medium.
Background
UEFI (Unified Extensible Firmware Interface) is a personal computer System specification, which is used to define a software Interface between an operating System and System Firmware, and is used as an alternative to BIOS (Basic Input Output System). The extensible firmware interface is responsible for power-on self-test, contacting the operating system, and providing an interface to connect the operating system to the hardware. The system specification of the personal computer is used for defining a software interface between an operating system and system firmware as a replacement scheme of a BIOS. The extensible firmware interface is responsible for power-on self-test, contacting the operating system, and providing an interface to connect the operating system to the hardware. UEFI is a TSL (Transient System Load) phase that runs between the time after the personal computer and server are powered on for hardware initialization and loading of driver services and the start of the operating System.
In the related art, when communication is performed with an operating system under UEFI, data Transmission is generally performed using TCP (Transmission Control Protocol) and UDP (User Datagram Protocol). However, this transmission method still only can perform data transmission in the form of character strings, which brings inconvenience to the requirement of massive data interaction during actual communication.
Disclosure of Invention
The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.
Embodiments of the present invention provide a file transmission method, a file transmission system, and a computer-readable storage medium, which can transmit data in a file format of any size, and improve data transmission efficiency.
In a first aspect, an embodiment of the present invention provides a file transmission method, including:
opening a file to be transmitted through a unified extensible firmware interface;
slicing the file to be transmitted to obtain a plurality of slices;
preprocessing each slice to obtain a plurality of data packets;
and sequentially transmitting each data packet to a receiving end according to a transmission control protocol.
In some embodiments, the opening the file to be transferred through the unified extensible firmware interface includes: acquiring a first identifier through the unified extensible firmware interface, wherein the first identifier is used for representing the global uniqueness of the file to be transmitted; obtaining a transmission protocol of the file to be transmitted according to the first identifier; and opening the file to be transmitted according to the transmission protocol.
In some embodiments, the opening the file to be transmitted according to the transmission protocol includes: obtaining a second identifier according to the transmission protocol, wherein the second identifier is used for identifying the file to be transmitted; and reading the file to be transmitted according to the second identifier.
In some embodiments, the second identifier is a handle.
In some embodiments, the slicing the file to be transmitted to obtain a plurality of slices includes: and slicing the file to be transmitted according to a preset value to obtain a plurality of slices with the same size.
In some embodiments, the preprocessing each slice to obtain a plurality of data packets includes: and adding packet headers for the slices one by one to obtain a plurality of data packets.
In some embodiments, said sequentially transmitting each of said data packets to a receiving end according to a transmission control protocol includes: reading the data packets to a buffer area one by one; and sequentially transmitting the data packets in the buffer area to a receiving end according to the transmission control protocol.
In some embodiments, the method further comprises: when a receiving end receives a plurality of data packets, the packet head of each data packet is obtained according to the data packets; and packaging the data packet according to the packet head to obtain the file to be transmitted.
In some embodiments, the first identifier is a globally unique identifier.
In a second aspect, an embodiment of the present invention provides a file transfer system, including:
the reading module is used for opening the file to be transmitted through the unified extensible firmware interface;
the slicing module is used for slicing the file to be transmitted to obtain a plurality of slices;
the preprocessing module is used for preprocessing each slice to obtain a plurality of data packets;
and the transmission module is used for sequentially transmitting each data packet to a receiving end according to a transmission control protocol.
In a third aspect, an embodiment of the present invention provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the computer program implements the file transfer method according to the first aspect.
The embodiment of the invention comprises the following steps: the method comprises the steps of opening a file to be transmitted through a unified extensible firmware interface, and slicing the file to be transmitted. After the plurality of slices are obtained, each slice is preprocessed to obtain a plurality of data packets, and finally, each data packet is sequentially sent to a receiving end according to a transmission control protocol. According to the scheme provided by the embodiment of the invention, the function of file transmission can be realized on the basis of unifying the extensible firmware interface, and files with any size can be transmitted, so that the data transmission efficiency is improved.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and drawings.
Drawings
The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the example serve to explain the principles of the invention and not to limit the invention.
Fig. 1 is a flowchart of a file transfer method according to an embodiment of the present invention;
FIG. 2 is a flow chart of obtaining a first identifier according to an embodiment of the present invention;
FIG. 3 is a flowchart of obtaining a second identifier according to an embodiment of the present invention;
FIG. 4 is a flow chart of caching data packets according to an embodiment of the present invention;
fig. 5 is a flowchart of a receiving end processing procedure provided in the embodiment of the present invention;
FIG. 6 is a flowchart of a file transfer process provided by an embodiment of the invention;
fig. 7 is a block diagram of a file transfer system according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and do not limit the invention.
It should be noted that although functional block partitions are illustrated in block diagrams and logical sequences are illustrated in flowcharts, in some cases, steps shown or described may be performed in a different block partition or sequence in flowcharts. The terms first, second and the like in the description and in the claims, and the drawings described above, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order.
The file transmission method and the application scenario described in the embodiments of the present invention are for more clearly illustrating the technical solution of the embodiments of the present invention, and do not constitute a limitation on the technical solution provided in the embodiments of the present invention, and it is known to those skilled in the art that, with the evolution of the file transmission field and the occurrence of a new application scenario, the technical solution provided in the embodiments of the present invention is also applicable to similar technical problems.
As shown in fig. 1, fig. 1 is a flowchart of a file transmission method according to an embodiment of the present invention. It is understood that the present invention provides a file transmission method, which includes, but is not limited to, step S100, step S200, step S300 and step S400.
And step S100, opening the file to be transmitted through the unified extensible firmware interface.
And S200, slicing the file to be transmitted to obtain a plurality of slices.
Step S300, each slice is preprocessed to obtain a plurality of data packets.
Step S400, each data packet is transmitted to the receiving end in sequence according to the transmission control protocol.
It can be understood that, in the method, the file to be transmitted is first opened through the unified extensible firmware interface, and the file to be transmitted is sliced. After the plurality of slices are obtained, each slice is preprocessed to obtain a plurality of data packets, and finally, each data packet is sequentially sent to a receiving end according to a transmission control protocol. According to the scheme provided by the embodiment of the invention, the function of file transmission can be realized on the basis of unifying the extensible firmware interface, and files with any size can be transmitted, so that the data transmission efficiency is improved.
It should be noted that the transmission control protocol TCP is a connection-oriented, reliable transport layer communication protocol based on byte streams. TCP aims to accommodate a layered protocol hierarchy that supports multiple network applications. Reliable communication services are provided by means of TCP between pairs of processes in host computers connected to different but interconnected computer communication networks. TCP assumes that it can obtain simple, possibly unreliable, datagram service from lower level protocols. In principle, TCP should be able to operate over a variety of communication systems connected from hard wire to packet switched or circuit switched networks.
It is understood that, in step S200 in the embodiment shown in fig. 1, the file to be transmitted is sliced and a plurality of slices are obtained, including but not limited to: and slicing the file to be transmitted according to a preset value. The preset value provided in this embodiment refers to a size value of a slice set according to actual requirements, and the file to be transmitted is divided into multiple slices with the same size according to the preset value, so as to uniformly transmit the file.
As shown in fig. 2, fig. 2 is a flowchart for acquiring a first identifier according to an embodiment of the present invention. It is understood that step S100 in the embodiment shown in fig. 1 further includes, but is not limited to, step S110, step S120, and step S130.
Step S110, a first identifier is obtained through the unified extensible firmware interface, and the first identifier is used for representing the global uniqueness of the file to be transmitted.
And step S120, obtaining the transmission protocol of the file to be transmitted according to the first identifier.
Step S130, opening the file to be transmitted according to the transmission protocol.
It can be understood that before the file to be transmitted is opened, the file to be transmitted can be opened according to the transmission protocol by obtaining the globally unique first identifier for representing the file to be transmitted through the unified extensible firmware interface and then obtaining the transmission protocol of the file to be transmitted through the first identifier.
It should be noted that the first Identifier proposed in the present invention is a Globally Unique Identifier (GUID), which is a numeric Identifier with a binary length of 128 bits generated by an algorithm. GUIDs are used primarily in networks or systems having multiple nodes, multiple computers. Ideally, no computer or cluster of computers will generate two identical GUIDs. The total number of GUIDs reaches 2^128 (3.4 x 10^ 38), so the probability of randomly generating two identical GUIDs is very small, but not 0. Therefore, the algorithm used to generate the GUID typically adds a non-random parameter (e.g., time) to ensure that such duplication does not occur. Therefore, the global unique identifier is used as an identification tool in the invention, so that the system can accurately inquire the file to be transmitted.
As shown in fig. 3, fig. 3 is a flowchart for obtaining the second identifier according to an embodiment of the present invention. It is understood that step S130 in the embodiment shown in fig. 2 further includes, but is not limited to, step S131 and step S132.
Step S131, according to the transmission protocol, a second identifier is obtained, and the second identifier is used for identifying the file to be transmitted.
And step S132, reading the file to be transmitted according to the second identifier.
It can be understood that after the transmission protocol of the file to be transmitted is obtained, the second identifier for representing the file to be transmitted still needs to be obtained, and then the file to be transmitted is read according to the second identifier.
It should be noted that the second identifier proposed in the present invention is a handle. A handle is an identifier used to identify an object or item, and may be used to describe information such as a form, a file, etc. Since the address of the data needs to be changed and a person is required to record and manage the change after the change, the system records the change of the data address by using a handle. In programming, a handle is a special smart pointer, and is used when an application references a memory block or object managed by another system (e.g., a database, an operating system).
As shown in fig. 4, fig. 4 is a flowchart of buffering a data packet according to an embodiment of the present invention. It is understood that step S400 in the embodiment shown in fig. 1 specifically includes, but is not limited to, step S410 and step S420.
Step S410, reading the data packets to the buffer one by one.
Step S420, sequentially transmitting the data packets in the buffer to the receiving end according to the transmission control protocol.
It can be understood that, when the data packets are transmitted to the receiving end, the data packets need to be read one by one and placed in the buffer area, and then each data packet in the buffer area is sequentially sent to the receiving end according to the transmission control protocol. When the system receives the command of reading and writing the file data, the file data is not read or written immediately, but the data is temporarily stored in the cache. The magnetic head will read the data in the next cluster or clusters of the cluster being read into the buffer memory, and when the data in the next cluster or clusters needs to be read, the hard disk does not need to read the data again, but the data in the buffer memory is directly transmitted to the memory to complete the data transmission. The speed of the buffer memory is far higher than the speed of the read-write of the magnetic head, so the setting of the buffer memory area improves the transmission performance of the file.
It is understood that a data packet is a unit of data in a transmission control protocol communication transmission. In the file transfer method proposed by the present invention, a single file is divided into a plurality of data blocks, which are called packets, containing address information of a sender and a receiver. These packets are then transmitted along different paths in one or more networks and repackaged and combined at the receiving end. The data packet mainly comprises a destination IP address, a source IP address, payload data and the like, and comprises a packet header and a packet body.
It should be noted that, before the data packets are read to the buffer one by one in step S410, each slice needs to be preprocessed to obtain a plurality of data packets. Specifically, the packet headers are added to the slices one by one. Specifically, the header of the data packet refers to a special reserved field defining a bit length that is attached to the front of the data packet for carrying and transmitting control information in network protocol communication. When the packet arrives at the receiving end, the field will be separated and discarded because the packet is processed and unpacked in the corresponding reverse order of each protocol layer.
As shown in fig. 5, fig. 5 is a flowchart of a receiving end processing procedure according to an embodiment of the present invention. It is understood that the file transmission method proposed by the present invention further includes, but is not limited to, step S510 and step S520.
Step S510, after the receiving end receives a plurality of data packets, the header of each data packet is obtained according to the data packets.
Step S520, the data packet is encapsulated according to the packet head to obtain the file to be transmitted.
It can be understood that, after the receiving end receives the data packets, the header of each data packet needs to be obtained according to the data packets, and then the data packets are encapsulated according to the information in the header, so as to obtain a complete file to be transmitted.
As shown in fig. 6, fig. 6 is a flowchart of a file transfer processing procedure provided in an embodiment of the present invention. It is understood that the file transmission method provided by the present invention further includes, but is not limited to, step S610, step S620, step S630, step S640, step S650, step S660 and step S670.
Step S610, obtaining the globally unique identifier of the file to be transmitted through the unified extensible firmware interface.
And step S620, acquiring a transmission protocol corresponding to the file to be transmitted according to the global unique identifier.
Step S630, a handle of the file to be transmitted is obtained through the transmission protocol.
Step S640, the file to be transmitted is read through the handle, and the size of the file to be transmitted is obtained.
And step S650, slicing the file to be transmitted according to a preset value, and adding a packet header to each slice to obtain a plurality of data packets.
And step S660, reading the data packets into the buffer area in sequence, and sending the data packets to a receiving end according to a transmission control protocol.
And step S670, the receiving end receives the data packets in sequence and encapsulates the data packets according to the packet headers to obtain the file to be transmitted.
It can be understood that during the file transmission process, the globally unique identifier of the file to be transmitted needs to be acquired through the unified extensible firmware interface first. Then, a transmission protocol corresponding to the file to be transmitted is obtained according to the global unique identifier, and then a handle of the file to be transmitted is obtained through the transmission protocol. And after the handle is obtained, reading the file to be transmitted according to the handle information, and obtaining the file size of the file to be transmitted. After that, the file to be transmitted is divided into a plurality of slices according to the preset value, and a packet header is added to each slice to obtain a plurality of data packets. And then, sequentially reading the data packets into the buffer area, and sending the data packets to a receiving end according to a transmission control protocol. And after the receiving end sequentially receives the data packets, encapsulating the data packets according to the information in the packet header to obtain the file to be transmitted. By the file transfer method, the function of file transfer under UEFI can be realized, and files with any size can be transferred.
As shown in fig. 7, fig. 7 is a block diagram of a file transfer system according to an embodiment of the present invention. The present invention further provides a file transmission system 100, which includes, but is not limited to, a reading module 110, a slicing module 120, a preprocessing module 130, and a transmission module 140. The reading module 110 is configured to open a file to be transmitted through a unified extensible firmware interface; the slicing module 120 is configured to slice a file to be transmitted to obtain multiple slices; a preprocessing module 130, configured to preprocess each slice to obtain a plurality of data packets; the transmission module 140 is configured to sequentially transmit each data packet to the receiving end according to the transmission control protocol. The device can realize the function of file transmission on the basis of unifying the extensible firmware interface, and can transmit files with any size, thereby improving the efficiency of data transmission.
In addition, the file transmission system provided by the embodiment of the invention can also comprise terminal equipment and an HTTP server. The file transfer system comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, and the processor executes the computer program to realize the file transfer method in the embodiment.
The memory, which is a non-transitory computer readable storage medium, may be used to store non-transitory software programs and non-transitory computer executable programs, such as the file transfer method in the above embodiments of the present invention. The processor implements the file transfer method in the above embodiment of the present invention by running the non-transitory software program and the instructions stored in the memory.
The memory may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data and the like necessary to execute the file transfer method in the above-described embodiments. Further, the memory may include high speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid state storage device. It should be noted that the memory may alternatively comprise memory located remotely from the processor, and that such remote memory may be coupled to the terminal via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The non-transitory software programs and instructions required to implement the file transfer method in the above-described embodiments are stored in a memory, and when executed by one or more processors, perform the file transfer method in the above-described embodiments, for example, perform at least one of the method steps S100 to S400 in fig. 1, the method steps S110 to S130 in fig. 2, the method steps S131 to S132 in fig. 3, the method steps S410 to S420 in fig. 4, the method steps S510 to S520 in fig. 5, and the method steps S610 to S670 in fig. 6 described above.
The present invention also provides a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the file transfer method as in the above-described embodiments, for example, at least one of the method steps S100 to S400 in fig. 1, the method steps S110 to S130 in fig. 2, the method steps S131 to S132 in fig. 3, the method steps S410 to S420 in fig. 4, the method steps S510 to S520 in fig. 5, and the method steps S610 to S670 in fig. 6 described above.
The above described embodiments of the apparatus are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, may be located in one place, or may be distributed over a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
One of ordinary skill in the art will appreciate that all or some of the steps, systems, and methods disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those skilled in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
The embodiments of the present invention are described in detail with reference to the drawings, but the present invention is not limited to the embodiments, and various changes can be made within the knowledge of those skilled in the art without departing from the gist of the present invention.
Claims (11)
1. A method for file transfer, the method comprising:
opening a file to be transmitted through a unified extensible firmware interface;
slicing the file to be transmitted to obtain a plurality of slices;
preprocessing each slice to obtain a plurality of data packets;
and sequentially transmitting each data packet to a receiving end according to a transmission control protocol.
2. The file transmission method according to claim 1, wherein the opening the file to be transmitted through the unified extensible firmware interface comprises:
acquiring a first identifier through the unified extensible firmware interface, wherein the first identifier is used for representing the global uniqueness of the file to be transmitted;
obtaining a transmission protocol of the file to be transmitted according to the first identifier;
and opening the file to be transmitted according to the transmission protocol.
3. The file transmission method according to claim 2, wherein the opening the file to be transmitted according to the transmission protocol comprises:
obtaining a second identifier according to the transmission protocol, wherein the second identifier is used for identifying the file to be transmitted;
and reading the file to be transmitted according to the second identifier.
4. The file transfer method according to claim 3, wherein the second identifier is a handle.
5. The file transmission method according to claim 1, wherein the slicing processing of the file to be transmitted to obtain a plurality of slices includes:
and slicing the file to be transmitted according to a preset value to obtain a plurality of slices with the same size.
6. The file transmission method according to claim 5, wherein said preprocessing each of the slices to obtain a plurality of data packets comprises:
and adding packet headers for the slices one by one to obtain a plurality of data packets.
7. The method according to claim 6, wherein said transmitting each data packet to a receiving end in turn according to a transmission control protocol comprises:
reading the data packets to a buffer area one by one;
and sequentially transmitting the data packets in the buffer area to a receiving end according to the transmission control protocol.
8. The file transfer method according to claim 7, further comprising:
after a receiving end receives a plurality of data packets, the packet head of each data packet is obtained according to the data packets;
and packaging the data packet according to the packet head to obtain the file to be transmitted.
9. The file transfer method according to claim 2, wherein the first identifier is a globally unique identifier.
10. A file transfer system, comprising:
the reading module is used for opening the file to be transmitted through the unified extensible firmware interface;
the slicing module is used for slicing the file to be transmitted to obtain a plurality of slices;
the preprocessing module is used for preprocessing each slice to obtain a plurality of data packets;
and the transmission module is used for sequentially transmitting each data packet to a receiving end according to a transmission control protocol.
11. A computer-readable storage medium, characterized in that a computer program is stored which, when executed by a processor, implements the file transfer method according to any one of claims 1 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211729701.XA CN115987975A (en) | 2022-12-30 | 2022-12-30 | File transmission method, system and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211729701.XA CN115987975A (en) | 2022-12-30 | 2022-12-30 | File transmission method, system and computer readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115987975A true CN115987975A (en) | 2023-04-18 |
Family
ID=85957725
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211729701.XA Pending CN115987975A (en) | 2022-12-30 | 2022-12-30 | File transmission method, system and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115987975A (en) |
-
2022
- 2022-12-30 CN CN202211729701.XA patent/CN115987975A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9483188B2 (en) | Multiple I/O request processing in a storage system | |
| US7502826B2 (en) | Atomic operations | |
| US6012085A (en) | Apparatus and method for increased data access in a network file object oriented caching system | |
| US6522654B1 (en) | Method for hosting the internet protocol suite on the IEEE-1394 high speed serial bus | |
| US7212527B2 (en) | Method and apparatus for communicating using labeled data packets in a network | |
| US7917578B1 (en) | Managing state information in a computing environment | |
| US6427151B1 (en) | Method, computer program product, system and data structure for formatting transaction results data | |
| US9356863B2 (en) | Communications over multiple protocol interfaces in a computing environment | |
| CN111758090B (en) | System and method for accessing and managing key-value data over a network | |
| US20080301311A1 (en) | Method and system for extended steering tags (stags) to minimize memory bandwidth for content delivery servers | |
| US6898638B2 (en) | Method and apparatus for grouping data for transfer according to recipient buffer size | |
| KR20130046540A (en) | Data transmitting apparatus and method | |
| US20060224759A1 (en) | System and method for a peer-to-peer streaming content operation by a browser plug-in | |
| US20090303999A1 (en) | Method And Device For Transmitting Data Packets | |
| US7526574B2 (en) | Method for communicating data transfer requests between data transfer protocols | |
| US7420991B2 (en) | TCP time stamp processing in hardware based TCP offload | |
| CN115987975A (en) | File transmission method, system and computer readable storage medium | |
| CN109413142B (en) | Method for realizing iSCSI virtual agent under L inux | |
| US7010548B2 (en) | Sparse and non-sparse data management method and system | |
| CN110417860A (en) | File transfer management method, apparatus, equipment and storage medium | |
| CN104205079B (en) | The efficient distribution of subnet management data on RDMA networks | |
| US20040267967A1 (en) | Method, system, and program for managing requests to a network adaptor | |
| US7266614B1 (en) | Embedded channel adapter having link layer configured for concurrent retrieval of payload data during packet transmission | |
| US11330032B2 (en) | Method and system for content proxying between formats | |
| CN114978950B (en) | Network algorithm calling method and system based on FPGA and CPU cooperation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |