CN113067825A - Method for multi-endpoint data backup based on SRV6 network protocol - Google Patents
Method for multi-endpoint data backup based on SRV6 network protocol Download PDFInfo
- Publication number
- CN113067825A CN113067825A CN202110312776.7A CN202110312776A CN113067825A CN 113067825 A CN113067825 A CN 113067825A CN 202110312776 A CN202110312776 A CN 202110312776A CN 113067825 A CN113067825 A CN 113067825A
- Authority
- CN
- China
- Prior art keywords
- data
- backup
- endpoint
- file
- packet
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/34—Source routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/26—Special purpose or proprietary protocols or architectures
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Computer Security & Cryptography (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to a method for backing up multi-endpoint data based on SRV6 network protocol, comprising a negotiation control stage and a data transmission stage, wherein a source endpoint sends a data backup request packet to a backup endpoint; the backup endpoint sends a data backup response packet to the source endpoint; the source end point sends a data transmission packet to the backup end point; the backup endpoint accepts the data transport packets. The multi-endpoint data backup is carried out based on the SRV6 network protocol, so that the network bandwidth resource can be greatly saved, and especially, the advantage of bandwidth saving is greater when the number of backup endpoints is greater; the multi-endpoint data backup based on the SRV6 network protocol can greatly save local resources of a source endpoint, such as a CPU (central processing unit), a memory and the like; especially when the number of backup endpoints is larger, the advantage of local resource saving is larger.
Description
Technical Field
The invention relates to a method for multi-endpoint data backup based on an SRV6 network protocol.
Background
SRv6 technique is based on RFC8754 adding SRH (segment Routing header) header in IPv6 message, used for storing SRv6 SID (segment ID) list of a group of IPv6 address format; SRv6 Segment is a 128-bit IPv6 address, SRV6 network packet through one SRv6 SID end node, SRH route header Segment Left field is reduced by 1, meanwhile, destination address of the IPv6 header is updated to SID corresponding to current Segment Left in Segment list, and data packet is forwarded out following conventional IPv6 route.
At present, a multi-endpoint backup data scheme needs to repeatedly send backup data in a network, so that the bandwidth occupation of a public network is increased, and more CPU resources of a source endpoint are consumed; it is therefore desirable to devise a more friendly approach to improve multi-endpoint data backup, and SRV6 technology just addresses this issue.
Disclosure of Invention
The invention aims to overcome the defects in the prior art and provides a method for performing multi-endpoint data backup based on an SRV6 network protocol.
The purpose of the invention is realized by the following technical scheme:
a method for multi-endpoint data backup based on an SRV6 network protocol is characterized in that: the method comprises a negotiation control stage and a data transmission stage, and comprises the following steps:
1) the source end point sends a data backup request packet to the backup end point;
2) the backup endpoint sends a data backup response packet to the source endpoint;
3) the source end point sends a data transmission packet to the backup end point;
4) the backup endpoint accepts the data transport packets.
Further, in the above method for performing multi-endpoint data backup based on SRV6 network protocol, in step 1), the source endpoint sequentially sends a data backup request packet to the backup endpoint, where the request packet includes the following contents:
the method comprises the following steps of firstly, backing up a file name, a file size and a data transmission block size of data, wherein the data transmission block size represents the number of data bytes contained in each data packet during data transmission;
and secondly, backing up file marks in the data transmission stage, wherein each backup endpoint is mapped to an actual file during data transmission.
Further, in the above method for performing multi-endpoint data backup based on SRV6 network protocol, the file name is 128 bytes, the file size is 4 bytes, the data transfer block size is 2 bytes, and the file flag is 4 bytes.
Further, in the above method for performing multi-endpoint data backup based on SRV6 network protocol, when the backup endpoint receives the control message from the source endpoint,
s21) checking whether enough resources are available for receiving the file, wherein the resources refer to whether the storage space of the hard disk is enough, and if not, jumping to S24) for further processing;
s22) recording the file name, the file mark and the file block size information to a local database for the next data transmission;
s23), sending a response packet to the source endpoint, the response containing the following information:
response field (1), 4 bytes in length, indicates that the data is accepted;
the IPV6 address is 8 bytes in length and is used for informing the source node to organize a SRV6 address list when data are transmitted next;
s24), sending a response packet to the source endpoint, the response containing the following information:
the response field (0), 4 bytes long, indicates a refusal to accept the data.
Further, the above method for performing multi-endpoint data backup based on SRV6 network protocol, wherein data transmission of multi-endpoint data backup, the source endpoint sending data packets to the backup endpoint, comprises the steps of:
s31) the source terminal collects the IPV6 address of the backup terminal agreeing to accept the data, if the IPV6 address list is empty, the data backup negotiation fails, and the process is ended;
s32) the source endpoint padding the sending packet, the packet content containing:
firstly, an SRH head sequentially contains IPV6 addresses of all backup endpoints;
file marking, length 4 bytes;
BLOCK ID of data BLOCK, length 4 bytes, starting value 0, increasing by 1 after each data BLOCK is transmitted;
fourthly, marking the end of the data block, wherein the length is 2 bytes, if the value is not 0, the data is the last data block, and the byte number of the data block is indicated;
s33) the source endpoint sends S32) the prepared packet to the last IP address in the IPV6 address list until the packet sending is finished.
Further, in the method for performing multi-endpoint data backup based on the SRV6 network protocol, after the backup endpoint receives the data packet sent by the source endpoint,
s41), acquiring a file mark, searching a local database, and checking a real file name corresponding to the file mark; if the file is not created, immediately creating the file;
s42) obtaining the BLOCK ID, and matching whether the BLOCK ID is in a recorded state; if the data is not in the recorded state, the data is the repeated data, no further operation is needed, and the return is finished; otherwise, updating the BLCOK ID of the local record;
s43) acquiring a data block and adding the data block to a local file;
s44), acquiring a data end mark, if the current data package is the last data package, finishing file backup, and closing the file;
s45) checks the SRH IPV6 list and forwards the packet to the next IPV6 address if there is a next IPV6 address.
Compared with the prior art, the invention has obvious advantages and beneficial effects, and is embodied in the following aspects:
the invention carries out multi-endpoint data backup based on the SRV6 network protocol, thus greatly saving network bandwidth resources, and especially when the number of backup endpoints is more, the advantage of bandwidth saving is more;
the multi-endpoint data backup based on the SRV6 network protocol can greatly save local resources of a source endpoint, such as a CPU (central processing unit), a memory and the like; especially when the number of backup endpoints is larger, the advantage of local resource saving is larger.
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 the 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.
Drawings
FIG. 1: the flow chart of the invention is schematic;
FIG. 2: a source endpoint data backup request message;
FIG. 3: the standby endpoint agrees to accept the message;
FIG. 4: the standby endpoint refuses to accept the message;
FIG. 5: and sending a message by the source endpoint data.
Detailed Description
In order to more clearly understand the technical features, objects, and effects of the present invention, specific embodiments will now be described in detail.
With the linux OS platform, the current network topology environment is assumed as follows:
1) the source end point A is that the IPV6 addresses are 2001: D8AE: 1; the file needing multi-endpoint backup is ITIBIA _ NETCORE, and the size of the file is 1 GB;
2) backup endpoint B, IPV6 addresses 2001: D8AE: 2;
3) the backup endpoint C has the IPV6 address of 2001: D8AE: 3;
4) the backup endpoint D has the IPV6 address of 2001: D8AE: 4;
in addition, the port for data negotiation and data transmission is set to TCP9123/9124 for the source endpoint and the backup endpoint.
If a node in the network only supports conventional IPv6 and not SRv6, when the node receives SRv6 data packets, the node does not process SRH extension headers, and only performs IPv6 forwarding according to destination addresses of the data packets. This means SRv6 can seamlessly interoperate with existing IPv6 networks.
Network topology, endpoint a needs to simultaneously backup local data to endpoint B, C, D; for simplicity in description, it is assumed that the network distances of adjacent endpoints are all 1; then, the network distance passed by the endpoint a data backup is counted and compared with the difference between the two:
1) the original data backup method, the backup data of the endpoint A is to the endpoint B, the distance is 1; the endpoint A backs up data to the endpoint C, and the distance is 2; the endpoint A backs up data to the endpoint D, and the distance is 3; therefore, the distance required by the endpoint a to simultaneously backup data to the endpoints B, C and D is 1+2+3 to 6, and three data transmission channels need to be established.
2) The method comprises the steps that multi-endpoint data backup is carried out by adopting an SRV 6-based network protocol, an endpoint A can record an IPV6 address provided by a backup endpoint BCD into data packet SRH header information, so that the endpoint A can only establish a data transmission channel, and the endpoint BCD can receive data at the same time; therefore, the distance required for the endpoint a to simultaneously backup data to the endpoints B, C and D is 1+1+1 to 3.
Therefore, after the SRV6 network protocol is adopted to perform multi-endpoint data backup, the endpoint A can send data to a plurality of backup endpoints at the same time only by establishing a data channel, so that network bandwidth resources are greatly saved, and CPU resources on the endpoint A are saved.
In the negotiation control stage of multi-endpoint data backup, before a source endpoint needs to perform multi-endpoint data backup, the source endpoint first needs to start the preliminary preparation of negotiation data backup with each backup endpoint, and information needing to be communicated includes the following contents:
file names, file sizes and data transmission block sizes of backup data;
the file mark in the backup data transmission stage is used for mapping each backup endpoint to an actual file in the next data transmission;
when the backup endpoint receives the negotiation control packet of the source endpoint, the backup node needs to respond to the following content of the source endpoint:
when the backup end point has enough resource to receive file, the resource is the hard disk storage space, the backup end point records file name and file mark, then responds the source end point agrees to receive backup request, and informs the source end point data transmission stage of the address of IPV 6;
when the backup end point has no enough resource to receive the file, responding to the source end point to refuse to accept the backup request;
finally, the source endpoint sorts all the backup endpoint IPV6 address information agreed to be accepted, and prepares to start the next stage of data transmission.
In the data transmission stage of multi-endpoint data backup, a source endpoint starts to transmit data to a backup endpoint by taking the size of a data transmission block as a unit, and each data comprises the following contents:
firstly, an SRH head sequentially contains IPV6 addresses of all backup endpoints;
marking the file;
BLOCK ID of data BLOCK, and whether it is the last data BLOCK flag; if the data block is the last data block, indicating the actual size of the data block;
fourthly, the data BLOCK corresponding to the BLOCK ID;
when each backup endpoint receives the data, the actions taken are as follows:
firstly, acquiring a file mark, and checking a real file corresponding to the file mark; if the file is not created, the real file is created, and the file name is the file name recorded in the negotiation control stage;
acquiring a BLOCK ID, and matching whether the BLOCK ID is in a recorded state; if the status is not the recorded status, acquiring the corresponding data block, writing the opened file, and updating the BLCOK ID;
if the obtained BLOCK ID is the last BLOCK, the file backup is finished;
if the end point is not at the last of the list of the IPV6 at the head of the SRH, the data is forwarded to the next backup end point.
When the source end point sends the last data block and each backup end point receives the data block, the multi-end point data backup action is completed.
As shown in fig. 1, the method for performing multi-endpoint data backup based on SRV6 network protocol includes a negotiation control stage and a data transmission stage, and includes the steps of:
1) the source end point sends a data backup request packet to the backup end point;
2) the backup endpoint sends a data backup response packet to the source endpoint;
3) the source end point sends a data transmission packet to the backup end point;
4) the backup endpoint accepts the data transport packets.
The specific flow is that, first, the source endpoint a sequentially sends a data backup request packet to the backup endpoint BCD, as shown in fig. 2, the request packet adopts a TCP protocol, the destination port is 9123, and the request packet includes the following contents:
file name ITIBIIA _ NETCORE, file size (1073741824) and data transfer block size (1024) of the backup data; the data transmission block size represents the number of data bytes contained in each data packet during the next data transmission;
file marks (such as 7527) in the data transmission stage of the backup are used for mapping each backup endpoint to an actual file in the following data transmission;
next, each backup endpoint BCD listens to the TCP port 9123, and when receiving the control packet of the source endpoint, the following processing is required:
s21) checking whether there is enough resource receiving files, the backup endpoint BD has enough resource receiving files, and continues to execute downwards; the backup endpoint C has no resource shortage and directly jumps to S24);
s22) the backup endpoint BD records the file name ITIBIA _ NETCORE, the file mark (7527) and the file block size (1024) information to a local database for the next data transmission;
s23) the backup end BD sends a response packet to the source end, the response content contains the following information, and the process is finished;
response field (1), 4 bytes in length, indicates that the data is accepted; as shown in FIG. 3;
the IPV6 address is 8 bytes in length and is used for informing the source node to organize a SRV6 address list when data are transmitted next; backup endpoint B fills in IPV6 address 2001: D8AE:2, backup endpoint D fills in IPV6 address 2001: D8AE: 4;
s24) the backup terminal C sends a response packet to the source terminal, the response content contains the following information, and the processing is finished;
response field (0), length 4 bytes, indicates refusal to accept data; as shown in FIG. 4;
next, entering a data transmission phase of multi-endpoint data backup, the source endpoint sends a data transmission packet to the backup endpoint as follows, as shown in fig. 5;
s31) the source end point A collects backup end point IPV6 addresses agreeing to accept data, and the current IPV6 addresses list is 2001: D8AE:2, 2001: D8AE: 4;
s32) the source endpoint fills and sends the data packet, the data packet adopts the TCP protocol, the destination port is 9124, and the content of the data packet is as follows:
the head of the SRH sequentially comprises IPV6 addresses of all backup endpoints, wherein the addresses are 2001: D8AE:2, 2001: D8AE: 4;
file marker (7527), length 4 bytes;
BLOCK ID of data BLOCK, length 4 bytes, starting value 0, increasing by 1 after each data BLOCK is transmitted;
fourthly, marking the end of the data BLOCK, wherein the length of the data BLOCK is 2 bytes, if the value is not 0, the data is the last data BLOCK, the BLOCK ID of the last data BLOCK is 1048575, the byte number of the data BLOCK is indicated, and the length of the last data BLOCK is 1024;
s33) the source end point sends S32) the prepared data packet to the last IP address with the destination address being IPV6 address list, wherein the current address is 2001: D8AE:4, until the data packet sending is finished;
next, the backup endpoint BD listens to the TCP port 9124, and after receiving the data transmission packet sent by the source endpoint, the steps are as follows:
s41), acquiring a file mark (7527 at present), searching a local database, and checking that the real file name corresponding to the file mark is ITIBIA _ NETCORE; if the file is not created, immediately creating the file;
s42) obtaining the BLOCK ID, and matching whether the BLOCK ID is in a recorded state; if the data is not in the recorded state, the data is the repeated data, no further operation is needed, and the return is finished; otherwise, updating the BLCOK ID of the local record;
s43) acquiring a data block and adding the data block to a local file;
s44), acquiring a data end mark, if the found value is not 0 (the current value is 1024), indicating that the data packet is the last data packet, completing file backup, and closing the file;
s45) backup endpoint BD checks the SRH IPV6 list and backup endpoint B has the next IPV6 address 2001:: D8AE:4 forwarding the packet to backup endpoint D (2001:: D8AE: 4).
At this point, the flow of multi-endpoint data backup from negotiation to data transmission ends.
In summary, the invention performs multi-endpoint data backup based on the SRV6 network protocol, which can greatly save network bandwidth resources, especially when the number of backup endpoints is more, the advantage of bandwidth saving is greater;
the multi-endpoint data backup based on the SRV6 network protocol can greatly save local resources of a source endpoint, such as a CPU (central processing unit), a memory and the like; especially when the number of backup endpoints is larger, the advantage of local resource saving is larger.
It should be noted that: the above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention; while the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.
Claims (6)
1. The method for multi-endpoint data backup based on the SRV6 network protocol is characterized in that: the method comprises a negotiation control stage and a data transmission stage, and comprises the following steps:
1) the source end point sends a data backup request packet to the backup end point;
2) the backup endpoint sends a data backup response packet to the source endpoint;
3) the source end point sends a data transmission packet to the backup end point;
4) the backup endpoint accepts the data transport packets.
2. The method for multi-endpoint data backup based on SRV6 network protocol as claimed in claim 1, wherein: step 1), the source terminal sends a data backup request packet to the backup terminal in sequence, wherein the request packet comprises the following contents:
the method comprises the following steps of firstly, backing up a file name, a file size and a data transmission block size of data, wherein the data transmission block size represents the number of data bytes contained in each data packet during data transmission;
and secondly, backing up file marks in the data transmission stage, wherein each backup endpoint is mapped to an actual file during data transmission.
3. The method for multi-endpoint data backup based on SRV6 network protocol as claimed in claim 2, wherein: the file name is 128 bytes, the file size is 4 bytes, the data transfer block size is 2 bytes, and the file flag is 4 bytes.
4. The method for multi-endpoint data backup based on SRV6 network protocol as claimed in claim 1, wherein: when the backup endpoint receives the control message of the source endpoint,
s21) checking whether enough resources are available for receiving the file, wherein the resources refer to whether the storage space of the hard disk is enough, and if not, jumping to S24) for further processing;
s22) recording the file name, the file mark and the file block size information to a local database for the next data transmission;
s23), sending a response packet to the source endpoint, the response containing the following information:
response field (1), 4 bytes in length, indicates that the data is accepted;
the IPV6 address is 8 bytes in length and is used for informing the source node to organize a SRV6 address list when data are transmitted next;
s24), sending a response packet to the source endpoint, the response containing the following information:
the response field (0), 4 bytes long, indicates a refusal to accept the data.
5. The method for multi-endpoint data backup based on SRV6 network protocol as claimed in claim 1, wherein: data transmission of multi-endpoint data backup, wherein a source endpoint sends a data packet to a backup endpoint, and the steps are as follows:
s31) the source terminal collects the IPV6 address of the backup terminal agreeing to accept the data, if the IPV6 address list is empty, the data backup negotiation fails, and the process is ended;
s32) the source endpoint padding the sending packet, the packet content containing:
firstly, an SRH head sequentially contains IPV6 addresses of all backup endpoints;
file marking, length 4 bytes;
BLOCK ID of data BLOCK, length 4 bytes, starting value 0, increasing by 1 after each data BLOCK is transmitted;
fourthly, marking the end of the data block, wherein the length is 2 bytes, if the value is not 0, the data is the last data block, and the byte number of the data block is indicated;
s33) the source endpoint sends S32) the prepared packet to the last IP address in the IPV6 address list until the packet sending is finished.
6. The method for multi-endpoint data backup based on SRV6 network protocol as claimed in claim 1, wherein: after the backup endpoint receives the packet sent by the source endpoint,
s41), acquiring a file mark, searching a local database, and checking a real file name corresponding to the file mark; if the file is not created, immediately creating the file;
s42) obtaining the BLOCK ID, and matching whether the BLOCK ID is in a recorded state; if the data is not in the recorded state, the data is the repeated data, no further operation is needed, and the return is finished; otherwise, updating the BLCOK ID of the local record;
s43) acquiring a data block and adding the data block to a local file;
s44), acquiring a data end mark, if the current data package is the last data package, finishing file backup, and closing the file;
s45) checks the SRH IPV6 list and forwards the packet to the next IPV6 address if there is a next IPV6 address.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110312776.7A CN113067825B (en) | 2021-03-24 | 2021-03-24 | Method for multi-endpoint data backup based on SRV6 network protocol |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110312776.7A CN113067825B (en) | 2021-03-24 | 2021-03-24 | Method for multi-endpoint data backup based on SRV6 network protocol |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113067825A true CN113067825A (en) | 2021-07-02 |
| CN113067825B CN113067825B (en) | 2022-08-26 |
Family
ID=76561698
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110312776.7A Active CN113067825B (en) | 2021-03-24 | 2021-03-24 | Method for multi-endpoint data backup based on SRV6 network protocol |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113067825B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024000136A1 (en) * | 2022-06-28 | 2024-01-04 | 新华三技术有限公司 | Message sending |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8837470B1 (en) * | 2012-01-26 | 2014-09-16 | Google Inc. | Multi-stage switching topology |
| CN109525492A (en) * | 2018-10-26 | 2019-03-26 | 重庆金美通信有限责任公司 | A kind of IP data backup transmission method not depending on Routing Protocol or algorithm |
| CN110535766A (en) * | 2018-05-25 | 2019-12-03 | 华为技术有限公司 | A kind of method and apparatus generating routing |
| CN110851303A (en) * | 2019-11-12 | 2020-02-28 | 北京天华星航科技有限公司 | Data backup method, system and equipment |
| CN112422435A (en) * | 2020-11-13 | 2021-02-26 | 新华三技术有限公司合肥分公司 | Message forwarding control method and device and electronic equipment |
-
2021
- 2021-03-24 CN CN202110312776.7A patent/CN113067825B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8837470B1 (en) * | 2012-01-26 | 2014-09-16 | Google Inc. | Multi-stage switching topology |
| CN110535766A (en) * | 2018-05-25 | 2019-12-03 | 华为技术有限公司 | A kind of method and apparatus generating routing |
| CN109525492A (en) * | 2018-10-26 | 2019-03-26 | 重庆金美通信有限责任公司 | A kind of IP data backup transmission method not depending on Routing Protocol or algorithm |
| CN110851303A (en) * | 2019-11-12 | 2020-02-28 | 北京天华星航科技有限公司 | Data backup method, system and equipment |
| CN112422435A (en) * | 2020-11-13 | 2021-02-26 | 新华三技术有限公司合肥分公司 | Message forwarding control method and device and electronic equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024000136A1 (en) * | 2022-06-28 | 2024-01-04 | 新华三技术有限公司 | Message sending |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113067825B (en) | 2022-08-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4248546B2 (en) | Apparatus and method for transferring MPLS multicast packet via Ethernet | |
| US20020099856A1 (en) | Information processing device and method thereof, recording medium and program | |
| CN105723674A (en) | Methods for dynamically binding header field identifiers in a network control protocol | |
| CN111212089A (en) | Protocol conversion method for EtherCAT and IPv6 network | |
| CN1929497B (en) | Method and system for obtaining moving nodes local proxy information | |
| CN101360046B (en) | Bandwidth resource saving method | |
| US20180248932A1 (en) | Method and apparatus for sending target data to and acquiring target data from network | |
| CN113067825B (en) | Method for multi-endpoint data backup based on SRV6 network protocol | |
| CN114500633B (en) | Data forwarding method, related device, program product and data transmission system | |
| US20100260203A1 (en) | TUNNELING IPv6 PACKET THROUGH IPv4 NETWORK USING A TUNNEL ENTRY BASED ON IPv6 PREFIX AND TUNNELING IPv4 PACKET USING A TUNNEL ENTRY BASED ON IPv4 PREFIX | |
| CN112261054B (en) | Ethernet/IP and IPv6 protocol conversion system and method based on application service quality of service | |
| US20010006518A1 (en) | Information transfer method radio terminal and radio gateway device using datalink layer signaling of protocol identifier | |
| CN115941127B (en) | Message protocol timeout retransmission management method based on hash table | |
| CN102065013B (en) | Locator information optimal selection system based on ID (Identity) and Locator separation | |
| CN103227982A (en) | Straight through data processing method, equipment and system | |
| CN101527670A (en) | Configuration method and device for full header information message | |
| US20070041376A1 (en) | Method and apparatus for performing tunnel signaling over IP tunneling path | |
| CN109802900B (en) | Message caching method, message reading method, message caching device, message reading device and computer readable storage medium | |
| WO2003079612A1 (en) | Method and apparatus for direct data placement over tcp/ip | |
| CN103209128A (en) | Datagram and virtual circuit simultaneously supporting data forwarding method and router | |
| CN112367413A (en) | Method for embedding MAC address into DHCPv6 stateful address allocation | |
| CN101272319B (en) | Feedback and processing method and system for routing failure reason | |
| CN104822140A (en) | Data query method and network communication system | |
| CN100574253C (en) | A kind of method of fragment data message transmissions | |
| CN116668405B (en) | Method, system, medium and equipment for implementing multi-service message notification mechanism |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |