EP3528438A1 - Paketweiterleitung - Google Patents

Paketweiterleitung Download PDF

Info

Publication number
EP3528438A1
EP3528438A1 EP17871799.7A EP17871799A EP3528438A1 EP 3528438 A1 EP3528438 A1 EP 3528438A1 EP 17871799 A EP17871799 A EP 17871799A EP 3528438 A1 EP3528438 A1 EP 3528438A1
Authority
EP
European Patent Office
Prior art keywords
tunnel
notification message
network device
received
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
Application number
EP17871799.7A
Other languages
English (en)
French (fr)
Other versions
EP3528438B1 (de
EP3528438A4 (de
Inventor
Wen Wu
Liang Wang
Yuelei CHAO
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
New H3C Technologies Co Ltd
Original Assignee
New H3C Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by New H3C Technologies Co Ltd filed Critical New H3C Technologies Co Ltd
Publication of EP3528438A1 publication Critical patent/EP3528438A1/de
Publication of EP3528438A4 publication Critical patent/EP3528438A4/de
Application granted granted Critical
Publication of EP3528438B1 publication Critical patent/EP3528438B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/90—Buffering arrangements
    • H04L49/9057—Arrangements for supporting packet reassembly or resequencing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • 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/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/825—Involving tunnels, e.g. MPLS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • H04L47/82—Miscellaneous aspects
    • H04L47/826—Involving periods of time

Definitions

  • a Generic Routing Encapsulation (GRE) protocol serves to encapsulate data packets of a certain protocol (such as Internet Protocol (IP), Multiprotocol Label Switching (MPLS), Ethernet and the like) so that the encapsulated data packets can be transmitted via another network layer protocol.
  • IP Internet Protocol
  • MPLS Multiprotocol Label Switching
  • a path used for transmitting encapsulated data packets in a network is referred to as a GRE tunnel.
  • the GRE tunnel is a virtual point-to-point connection, and devices at two ends of the tunnel may perform GRE encapsulation and decapsulation on the data packets, respectively.
  • first, second, third, etc. in the present disclosure, the information should not be limited to these terms. These terms are used only to distinguish the same type of information from each other.
  • first information may also be referred to as the second information without departing from the scope of the present disclosure, and similarly, the second information may also be referred to as the first information.
  • word “if' as used herein may be interpreted as "when” or “as” or "determining in response to”.
  • a process of GRE encapsulation is to be described as below.
  • a raw packet may include a layer-2 header of 14 bytes, an original IP header of 20 bytes, and a payload of 30 bytes.
  • a GRE header of 4 bytes and a new IP header of 20 bytes may be added to the raw packet.
  • the length of the GRE-encapsulated packet is increased by 24 bytes compared to that of the raw packet.
  • the data traffic of each link over a GRE tunnel is increased and more link bandwidth is occupied.
  • a method of forwarding a packet and a network device to which the method is applied are provided according to the following examples of the present disclosure.
  • the method in an example of the present disclosure may be executed by a network device such as a router.
  • a network device such as a router.
  • the network device which executes the method according to the example of the present disclosure is hereinafter referred to as a first device.
  • a method of forwarding a packet executed by the first device may include the following blocks.
  • the first device may receive a first notification message from a destination device of a first tunnel, where information relating the first tunnel is carried in the first notification message, and the first device serves as a previous-hop device of the destination device of the first tunnel.
  • the information relating the first tunnel may include: an IP address of a source device of the first tunnel, an IP address of a destination device of the first tunnel, and an Identifier (ID) of a protocol to which the first tunnel conforms.
  • ID Identifier
  • the first tunnel may be a GRE tunnel, a Point-to-Point Protocol over Ethernet (PPPoE) tunnel, a Layer-2 Tunneling Protocol (L2TP) or the like, which is not limited in the example of the present disclosure.
  • PPPoE Point-to-Point Protocol over Ethernet
  • L2TP Layer-2 Tunneling Protocol
  • the first device may configure a forwarding entry, where a match domain of the forwarding entry includes the information relating the first tunnel.
  • the first device may configure the above forwarding entry on a software plane or a hardware plane, and also configure the match domain of the forwarding entry on the software plane and an action domain of the forwarding entry on the hardware plane, or configure the match domain on the hardware plane and the action domain on the software plane, which is not limited in the example of the present disclosure.
  • the first device may configure a forwarding entry as shown in table 1 after obtaining the information relating the first tunnel from the first notification message: Table 1 Match Actions
  • Source IP address an IP address of the source device of the first tunnel Decapsulating a packet and then forwarding it to the destination device of the first tunnel
  • Destination IP address an IP address of the destination device of the first tunnel Protocol ID: an ID of the protocol to which the first tunnel conforms
  • the first device may match the data packet with the forwarding entry as shown in table 1, and if they are matched, the first device may decapsulate the data packet to obtain a decapsulated data packet and then forward the decapsulated data packet to the destination device of the first tunnel.
  • the first device when receiving the encapsulated data packet, may match the data packet with the match domain of the forwarding entry located on the software plane or the hardware plane, and if they are matched, the first device may decapsulate the data packet to obtain a raw data packet and forward the raw data packet to the destination device of the first tunnel based on the action domain of the forwarding entry.
  • the destination device of a tunnel may transmit a notification message to a previous-hop device of the destination device, where the information relating the tunnel is carried in the notification message.
  • the previous-hop device may configure a forwarding entry in which the match domain includes the information relating the tunnel.
  • the previous-hop device may decapsulate the encapsulated data packet, and if the encapsulated data packet matches the forwarding entry, then the previous-hop device may forward the decapsulated data packet to the destination device of the tunnel.
  • the previous-hop device of the destination device of the tunnel may decapsulate the data packet to obtain a raw data packet in advance and forward the raw data packet to the destination device.
  • the decapsulation processing pressure of the destination device can be relieved, and when a plurality of tunnels are established between the source device and the destination device, the packet decapsulation processing work for a part of the tunnels can be shifted to the previous-hop device.
  • the data traffic of the link can be reduced and the bandwidth of the link can be saved.
  • an aging mechanism may be provided for a forwarding entry. For example, if the first notification message from the destination device of the first tunnel is not received within a predetermined time, the first device may delete the forwarding entry as shown in table 1. Therefore, when an encapsulated data packet is received from the source device of the first tunnel, the first device may directly forward the data packet to the destination device of the first tunnel instead of decapsulating the data packet. Subsequently, when receiving the first notification message from the destination device again, the first device may execute the method as shown in Fig. 1 to reconfigure the forwarding entry and perform the operation of decapsulating a packet and forwarding it to the destination device of the first tunnel according to the forwarding entry.
  • a tunnel keepalive mechanism may be employed in an example of the present disclosure. For example, based on the keepalive mechanism of a GRE tunnel, when the GRE keepalive function is enabled, a source device may periodically transmit a keepalive request packet to a destination device over the GRE tunnel. If the source device has not received a keepalive response packet returned by the destination device after continuously transmitting a predetermined number of keepalive request packets, the source device may set the GRE tunnel in a down status.
  • the source device may switch the status of the GRE tunnel into an up status if a keepalive response packet returned by the destination device is received, or otherwise maintain the GRE tunnel in the down status.
  • such tunnels as a PPPoE tunnel and an L2TP tunnel are adapted to similar keepalive mechanisms.
  • the destination device of the first tunnel may transmit the first notification message carrying the information relating the first tunnel to the previous-hop device (i.e., the first device) transmitting the keepalive request packet.
  • the first device is allowed to perform the operation blocks as shown in Fig. 1 .
  • commands may be configured, and according to the commands, the first device may configure a forwarding entry on the first device after receiving the first notification message from the destination device of the first tunnel.
  • corresponding provisions may be set based on a protocol standard, which is not limited in the example of the present disclosure.
  • the first device may also serve as a destination device of a particular tunnel.
  • the first device may receive a keepalive request packet from a source device over the second tunnel, and then transmit a second notification message to a previous-hop device transmitting the keepalive request packet.
  • Information relating the second tunnel is carried in the second notification message.
  • the information relating the second tunnel may include an IP address of the first device, an IP address of the source device, and an ID of a protocol to which the second tunnel conforms.
  • the second tunnel may be a GRE tunnel, a PPPoE tunnel, an L2TP tunnel or the like, which is not limited in the example of the present disclosure.
  • the protocols and packet formats of the above-mentioned notification messages are not limited as long as they can carry the information relating a tunnel and can serve as a notification.
  • the notification message may be a keepalive response packet with Time To Live (TTL) being 1.
  • TTL indicates the maximum hops by which a data packet can be forwarded in a network.
  • the first device may receive a keepalive request packet from the source device, and then return a keepalive response packet to the source device according to the tunnel keepalive mechanism.
  • the previous-hop device may perform the operation blocks as shown in FIG. 1 .
  • the tunnel keepalive mechanism may be employed.
  • a GRE tunnel may be established between a device R_A 201 and a device R_D 204, where the device R_A 201 is a source device of the GRE tunnel, and the device R_D 204 is a destination device of the GRE tunnel, and a device R_C 203 is a previous-hop device of the destination device.
  • the device R_A 201 has an IP address as IP-A and an MAC address as MAC-A; the IP address of the device R_C 203 is IP-C and its MAC address is MAC- C; and the IP address of the device R_D 204 is IP- D and its MAC address is MAC- D.
  • the method of forwarding a packet in this case is as shown in FIG. 3 , which specifically includes the following blocks.
  • the device R_A 201 may transmit a keepalive request packet to the device R_D 204 over a GRE tunnel.
  • the format of the keepalive request packet is as shown in FIG. 4 , including: a layer-2 header, an outer layer IP header, an outer layer GRE header, an inner layer IP header, and an inner layer GRE header.
  • the source IP address of the outer layer IP header of the keepalive request packet is IP-A and its destination IP address is IP-D
  • the source IP address of the inner layer IP header is IP-D and its destination IP address is IP-A.
  • the device R_D 204 may decapsulate the keepalive request packet and then construct two keepalive response packets: a keepalive response packet 1 and a keepalive response packet 2.
  • the device R_D 204 may record an ingress port of the keepalive request packet as Port21 and parse the keepalive request packet to determine a source MAC address in the layer-2 header as MAC-C and a destination MAC address as MAC-D. Then, the device R_D 204 may pop out the outer layer IP header and the outer layer GRE header of the keepalive request packet to obtain the remaining layer-2 header, inner layer IP header and inner layer GRE header, and construct the keepalive response packet 1 and the keepalive response packet 2 with these obtained headers.
  • the process of constructing the keepalive response packet 1 is as follows: setting the TTL in the IP header to 1, and interchanging the source MAC address MAC-C and the destination MAC address MAC-D in the layer-2 header, i.e., taking MAC-D as the source MAC address and MAC-C as the destination MAC address.
  • the source MAC address of the layer-2 header of the constructed keepalive response packet 1 is MAC-D and its destination MAC address is MAC-C and the TTL in the IP header is 1.
  • the keepalive response packet 1 is a notification message.
  • the keepalive response packet 2 is a keepalive response packet with the TTL not being 1, and the source MAC address in the layer-2 header of the packet is MAC-D and the destination MAC address is the MAC address of a next-hop device to which the keepalive response packet 2 is forwarded and the TTL in the IP header is 254.
  • Such information as an egress port of the keepalive response packet 2 and an MAC address of a next-hop device may be obtained by searching an IP route table for corresponding next-hop information based on the IP address IP-A of the device R_A 201.
  • the device R_D 204 may transmit the keepalive response packet 1 to the device R_C 203 through a Port21.
  • the keepalive response packet 1 may be transmitted through the ingress port Port21 of the keepalive request packet rather than an egress port obtained by searching in the IP route table. Thus, it can be ensured that the keepalive response packet 1 may be transmitted to the device R_C 203.
  • the device R_D 204 may transmit the keepalive response packet 2 to the device R_A 201 through the egress port obtained by searching in the IP route table.
  • the TTL values in the IP headers of the keepalive response packet 1 and the keepalive response packet 2 are different, and the manners of determining the egress ports are different.
  • the egress port of the keepalive response packet 1 may be determined as the ingress port Port21 of the keepalive request packet.
  • the keepalive response packet 1 is to be transmitted back to the second-to-last-hop device, i.e., the device R_C 203, in a forwarding path (i.e., device R_A 201 ⁇ device R_B 202 ⁇ device R_C 203 ⁇ device R_D 204) of the keepalive request packet, therefore, the keepalive response packet 1 must be transmitted from the ingress port of the keepalive request packet.
  • the keepalive response packet 2 is to be transmitted to the device R_A 201; therefore, according to the GRE tunnel keepalive mechanism, a corresponding egress port may be obtained by searching the IP route table based on the IP address IP-A of the device R_A 201, and the keepalive response packet 2 may be forwarded to the device R_A 201 through the obtained egress port.
  • the order of transmitting the keepalive response packet 1 and the keepalive response packet 2 may not be specified.
  • the keepalive response packet 1 is a functional notification message for notifying the device R_C 203 of configuring a forwarding entry so as to decapsulate a packet in advance
  • the keepalive response packet 2 is a keepalive maintenance message.
  • it may be such an order in which block S303 is performed first and block S304 is then performed.
  • it may also be such an order in which block S304 is performed first and block S303 is then performed.
  • the device R_A 201 may maintain the GRE tunnel in an up status after receiving the keepalive response packet 2.
  • the device R_A 201 may perform block S301 again when a predetermined transmitting time interval expires.
  • the device R_C 203 may parse the packet to determine TTL in the IP header being 1, and directly transmit the packet to a CPU for process.
  • the CPU may obtain the source IP address IP-D, the destination IP address IP-A and the protocol ID from the IP header of the keepalive response packet 1 and then configure a forwarding entry as shown in table 2 at the hardware plane: Table 2 Match Actions
  • the device R_C 203 may start a timer to start timing from 0. Subsequently, the timer may be restarted every time the above keepalive response packet 1 is received, such that the timer restarts timing from 0. If the time of the timer reaches predetermined time T and the device R_C 203 does not receive a new keepalive response packet 1, the forwarding entry may be deleted.
  • the device R_C 203 may match the GRE-encapsulated data packet with the forwarding entry as shown in table 2, and when the forwarding entry is hit, the device R_C 203 may decapsulate the GRE-encapsulated data packet according to the action domain of the forwarding entry and then forward it to the device R_D 204.
  • the keepalive mechanism of the GRE tunnel is employed.
  • the previous-hop device R_C 203 may configure a forwarding entry. According to the forwarding entry, an encapsulated data packet from the device R_A 201 may be decapsulated in advance and then forwarded to the device R_D 204. As a result, the decapsulation processing pressure of the destination device R_D 204 of the tunnel is reduced and the link overhead of the GRE tunnel is reduced.
  • the device R_C 203 may also support security authentication processing of the tunnel when decapsulating the encapsulated data packet according to the forwarding entry as shown in table 2.
  • the GRE tunnel may support two security authentication mechanisms: verification by key identification and end-to-end check.
  • the device R_C 203 may obtain and store a Key of the GRE tunnel from the device R_D 204. Alternatively, when a Key is carried in the keepalive response packet 1, the device R_C 203 may directly obtain the key from the keepalive response packet 1 and store it.
  • the device R_C 203 may configure the forwarding entry.
  • the action domain of the forwarding entry may be: decapsulating the encapsulated data packet and then forwarding it to the device R_D 204 when determining that the Key carried in the encapsulated data packet is consistent with the locally stored Key.
  • the device R_C 203 may match the GRE-encapsulated data packet with the forwarding entry, and when the forwarding entry is hit, the device R_C 203 may determine whether the Key carried in the GRE-encapsulated data packet is consistent with the locally stored Key according to the action domain of the forwarding entry. If the two keys are consistent, the device R_C 203 may decapsulate the GRE-encapsulated data packet and forwards the data packet to the device R_D 204.
  • a check indication mark such as a checksum may be carried in the keepalive response packet 1.
  • the device R_C 203 may configure the forwarding entry according to the check indication mark.
  • the action domain of the forwarding entry may be: calculating the checksum of an encapsulated data packet, and decapsulating the encapsulated data packet and then forwarding it to the device R_D 204 when determining that the calculated checksum is consistent with the checksum carried in the encapsulated data packet.
  • the device R_C 203 may match the GRE-encapsulated data packet with the forwarding entry.
  • the device R_C 203 may calculate the checksum of the GRE-encapsulated data packet and determine whether the calculated checksum is consistent with the checksum carried in the GRE-encapsulated data packet according to the action domain of the forwarding entry. If the two checksums are consistent, the device R_C 203 may decapsulate the GRE-encapsulated data packet and then forwards it to the device R_D 204.
  • the method as shown in FIG. 3 is also applicable to other tunnels supporting the keepalive mechanism, such as a PPPoE tunnel and an L2TP tunnel, which is not limited in the example of the present disclosure.
  • the present disclosure also provides an example of a network device.
  • the network device includes the following modules: a receiving unit 501, a configuring unit 502 and a transmitting unit 503, where:
  • the receiving unit 501 is configured to receive a first notification message from a destination device of a first tunnel, where the network device serves as a previous-hop device of the destination device of the first tunnel, and information relating the first tunnel is carried in the first notification message;
  • the configuring unit 502 is configured to configure a forwarding entry after the receiving unit 501 receives the first notification message, where a match domain of the forwarding entry includes the information relating the first tunnel;
  • the transmitting unit 503 is configured to decapsulate an encapsulated data packet to obtain a decapsulated data packet when the encapsulated data packet matches the forwarding entry after the receiving unit 501 receives the encapsulated data packet over the first tunnel, and forward the decapsulated data packet to the destination device of the first tunnel.
  • the receiving unit 501 is further configured to receive a keepalive request packet transmitted from a source device of a second tunnel over the second tunnel when the network device serves as a destination device of the second tunnel.
  • the transmitting unit 503 is further configured to transmit a second notification message to the previous-hop device transmitting the keepalive request packet after the receiving unit 501 receives the keepalive request packet, where information relating the second tunnel is carried in the second notification message.
  • the above-mentioned network device also includes: a deleting unit 504.
  • the receiving unit 501 determines whether a third notification message from the destination device of the first tunnel is received within a predetermined time after receiving the first notification message, where the third notification message carries information relating the first tunnel. If the receiving unit 501 does not receive the third notification message within the predetermined time, the deleting unit 504 deletes the forwarding entry from the network device.
  • the receiving unit 501 starts a timer to start timing when receiving the first notification message from the destination device of the first tunnel; and the receiving unit 501 may determine that the third notification message from the destination device of the first tunnel is not received within the predetermined time if the third notification message is still not received when the time of the timer reaches the predetermined time.
  • the first notification message received by the receiving unit 501 and the second notification message transmitted by the transmitting unit 503 are keepalive response packets with Time to Live (TTL) being 1.
  • TTL Time to Live
  • the information relating the first tunnel includes: IP addresses of devices at two ends of the first tunnel and an Identifier (ID) of a protocol to which the first tunnel conforms.
  • the information relating the second tunnel includes: IP addresses of devices at two ends of the second tunnel and an Identifier (ID) of a protocol to which the second tunnel conforms.
  • the devices at the two ends of the first tunnel are the source device and the destination device of the first tunnel
  • the devices at the two ends of the second tunnel are the network device and the source device of the second tunnel.
  • the above-mentioned first tunnel or second tunnel is one of a GRE tunnel, a PPPoE tunnel and an L2TP tunnel.
  • FIG. 7 illustrates a schematic diagram of a hardware structure of a network device according to an example of the present disclosure.
  • the network device includes a processor 701 and a machine-readable storage medium 702 that stores machine-executable instructions.
  • the processor 701 may communicate with the machine readable storage medium 702 via a system bus 703. Moreover, by reading and executing the machine-executable instructions on the machine-readable storage medium 702, the processor 701 may execute the method of forwarding a packet as described above.
  • the network device may also include other hardware according to the actual functions of the network device, which will not be redundantly described herein.
  • the machine readable storage medium 702 mentioned herein may be: any electronic, magnetic, optical or other physical storage device and may contain or store information such as executable instructions, data and so on.
  • the machine-readable storage medium may be a Read-Only Memory (ROM), a volatile memory, a nonvolatile memory, a flash memory, a storage drive (e.g. hard disk drive), a solid state harddisk, or any type of storage disk.
  • the processor 701 when reading and executing the machine-executable instructions on the machine-readable storage medium 702, the processor 701 is caused to perform the following operations:
  • processor 701 is also caused by the machine-executable instructions to:
  • processor 701 is also caused by the machine-executable instructions to:
  • processor 701 is also caused by the machine-executable instructions to:
  • the first notification message and the second notification message are keepalive response packets with Time to Live (TTL) being 1.
  • TTL Time to Live
  • the information relating the first tunnel includes: Internet Protocol (IP) addresses of devices at two ends of the first tunnel and an Identifier (ID) of a protocol to which the first tunnel conforms; and the information relating the second tunnel includes: Internet Protocol (IP) addresses of devices at two ends of the second tunnel and an Identifier (ID) of a protocol to which the second tunnel conforms.
  • IP Internet Protocol
  • ID Identifier
  • the device examples substantially correspond to the method examples, a reference may be made to part of the descriptions of the method examples for the related part.
  • the device examples described above are merely illustrative, where the units described as separate members may be or not be physically separated, and the members displayed as units may be or not be physical units, i.e., may be located in one place, or may be distributed to a plurality of network units. Part or all of the modules may be selected according to actual requirements to implement the objectives of the solutions in the examples. Those of ordinary skill in the art may understand and carry out them without creative work.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
EP17871799.7A 2016-11-18 2017-11-17 Paketweiterleitung Active EP3528438B1 (de)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611034213.1A CN108075991B (zh) 2016-11-18 2016-11-18 报文转发方法及装置
PCT/CN2017/111667 WO2018090980A1 (zh) 2016-11-18 2017-11-17 报文转发

Publications (3)

Publication Number Publication Date
EP3528438A1 true EP3528438A1 (de) 2019-08-21
EP3528438A4 EP3528438A4 (de) 2019-08-21
EP3528438B1 EP3528438B1 (de) 2021-08-11

Family

ID=62146178

Family Applications (1)

Application Number Title Priority Date Filing Date
EP17871799.7A Active EP3528438B1 (de) 2016-11-18 2017-11-17 Paketweiterleitung

Country Status (5)

Country Link
US (1) US10880122B2 (de)
EP (1) EP3528438B1 (de)
JP (1) JP6812549B2 (de)
CN (1) CN108075991B (de)
WO (1) WO2018090980A1 (de)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114125910A (zh) * 2020-08-31 2022-03-01 华为技术有限公司 隧道保活方法、网络设备、系统及存储介质

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110324165B (zh) * 2018-03-30 2021-05-11 华为技术有限公司 网络设备的管理方法、装置及系统
CN112448912B (zh) * 2019-08-27 2023-08-01 中兴通讯股份有限公司 一种防报文攻击方法、装置及存储介质
CN114301737B (zh) * 2021-12-29 2023-10-24 迈普通信技术股份有限公司 网络配置方法、装置、网络设备及计算机可读存储介质

Family Cites Families (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7801021B1 (en) * 2002-07-01 2010-09-21 Cisco Technology, Inc. Generic routing encapsulation tunnel keepalives
JP4093125B2 (ja) 2003-06-17 2008-06-04 株式会社日立製作所 Ｍｐｌｓ経路管理システム
JP4947430B2 (ja) * 2005-08-18 2012-06-06 日本電気株式会社 無線マルチホップネットワークにおける通信経路制御方法および通信端末
US8526331B2 (en) * 2008-05-23 2013-09-03 Telefonaktiebolaget L M Ericsson (Publ) Maintaining distributed hash tables in an overlay network
CN101695053B (zh) * 2009-09-30 2012-05-23 清华大学 一种改善域内路由ospf算法的ip快速重路由方法
US20120099602A1 (en) 2010-10-25 2012-04-26 Brocade Communications Systems, Inc. End-to-end virtualization
US8458344B2 (en) * 2011-05-05 2013-06-04 Blue Coat Systems, Inc. Establishing tunnels between selective endpoint devices along communication paths
US20130022041A1 (en) 2011-07-18 2013-01-24 Sriganesh Kini Signaling a label switched path (lsp) tunneling model
US9769116B2 (en) * 2011-09-16 2017-09-19 Wilmerding Communications Llc Encapsulating traffic while preserving packet characteristics
US9338050B2 (en) * 2012-03-27 2016-05-10 Telefonaktiebolaget Lm Ericsson (Publ) Shared keep-alive and failure detection mechanism in distributed network
EP2853066B1 (de) * 2012-05-23 2017-02-22 Brocade Communications Systems, Inc. Layer-3-überlagerungs-gateways
CN102739521B (zh) 2012-06-04 2016-03-02 杭州华三通信技术有限公司 一种组播业务实现方法及其设备
US8989192B2 (en) 2012-08-15 2015-03-24 Futurewei Technologies, Inc. Method and system for creating software defined ordered service patterns in a communications network
US9872321B2 (en) * 2012-10-09 2018-01-16 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for establishing and using PDN connections
US9036639B2 (en) * 2012-11-29 2015-05-19 Futurewei Technologies, Inc. System and method for VXLAN inter-domain communications
US9621460B2 (en) * 2013-01-14 2017-04-11 Versa Networks, Inc. Connecting multiple customer sites over a wide area network using an overlay network
CN104348759B (zh) * 2013-07-23 2019-04-02 中兴通讯股份有限公司 Gre报文的封装方法、解封装方法及对应的装置
US9548873B2 (en) * 2014-02-10 2017-01-17 Brocade Communications Systems, Inc. Virtual extensible LAN tunnel keepalives
US10063473B2 (en) 2014-04-30 2018-08-28 Brocade Communications Systems LLC Method and system for facilitating switch virtualization in a network of interconnected switches
CN105337881B (zh) 2014-06-27 2019-10-01 华为技术有限公司 一种数据报文的处理方法、业务节点以及引流点

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114125910A (zh) * 2020-08-31 2022-03-01 华为技术有限公司 隧道保活方法、网络设备、系统及存储介质
EP4192085A4 (de) * 2020-08-31 2024-02-21 Huawei Technologies Co., Ltd. Tunnel-keepalive-verfahren, netzwerkvorrichtung, system und speichermedium

Also Published As

Publication number Publication date
EP3528438B1 (de) 2021-08-11
JP6812549B2 (ja) 2021-01-13
CN108075991A (zh) 2018-05-25
JP2019536364A (ja) 2019-12-12
WO2018090980A1 (zh) 2018-05-24
US20190305987A1 (en) 2019-10-03
CN108075991B (zh) 2020-09-08
US10880122B2 (en) 2020-12-29
EP3528438A4 (de) 2019-08-21

Similar Documents

Publication Publication Date Title
EP3451595B1 (de) Verfahren, vorrichtung und system zur datenübertragung
EP3713162A1 (de) Verfahren und vorrichtung zur routenverarbeitung und datenübertragungsverfahren und vorrichtung
EP3958521A1 (de) Verfahren und vorrichtung zur bereitstellung eines dienstes für einen dienstfluss
EP3528438B1 (de) Paketweiterleitung
EP3076612B1 (de) Paketverarbeitungsverfahren und -knoten
US8351352B1 (en) Methods and apparatus for RBridge hop-by-hop compression and frame aggregation
CN105591982B (zh) 一种报文传输的方法和装置
EP3528441B1 (de) Weiterleitung von nachrichten
CN107872332B (zh) 一种报文转发路径的探测方法及相关装置
EP3979576A1 (de) Paketweiterleitungsverfahren, vorrichtung und computerlesbares speichermedium
EP3767898A1 (de) Verfahren und vorrichtung zur paketweiterleitung
WO2016124049A1 (zh) 用于获取端口路径的方法及装置
CN112737954B (zh) 报文处理方法、装置、系统、设备及存储介质
CN111130982B (zh) 报文转发方法、装置、网关设备及可读存储介质
US9531564B2 (en) Single hop overlay architecture for line rate performance in campus networks
US20190394055A1 (en) Bit index explicit replication (bier) penultimate hop popping
WO2017219868A1 (zh) Arp条目的处理方法及装置
WO2016101582A1 (zh) 一种操作维护管理功能的配置、实现方法及转发设备
CN112929193B (zh) 用于配置介质访问控制地址老化时间的方法和装置
WO2021047317A1 (zh) 报文处理方法及装置
CN115913820A (zh) 网络传输方法和设备
US8891509B2 (en) Proxy networking device for a router
EP4436113A1 (de) Konfiguration von netzwerktunneln zwischen vorrichtungen
KR100912299B1 (ko) ＩＰｖ4 /ＩＰｖ6 통합망에서의 데이터 포워딩 방법
US9548889B2 (en) Methods and apparatuses for automated TDM-ethernet provisioning

Legal Events

Date Code Title Description
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE INTERNATIONAL PUBLICATION HAS BEEN MADE

PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: REQUEST FOR EXAMINATION WAS MADE

17P Request for examination filed

Effective date: 20190517

A4 Supplementary search report drawn up and despatched

Effective date: 20190710

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20200703

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20210317

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602017044038

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Ref country code: AT

Ref legal event code: REF

Ref document number: 1420524

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210915

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG9D

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20210811

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1420524

Country of ref document: AT

Kind code of ref document: T

Effective date: 20210811

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211111

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211111

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211213

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20211112

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602017044038

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

26N No opposition filed

Effective date: 20220512

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211117

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211130

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20211130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211130

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211130

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20211117

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230424

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20171117

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20231026

Year of fee payment: 7

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20231026

Year of fee payment: 7

Ref country code: DE

Payment date: 20231129

Year of fee payment: 7

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20210811