WO2024016799A1 - 数据传输方法、运营商边缘设备、计算机可读存储介质 - Google Patents

数据传输方法、运营商边缘设备、计算机可读存储介质 Download PDF

Info

Publication number
WO2024016799A1
WO2024016799A1 PCT/CN2023/093826 CN2023093826W WO2024016799A1 WO 2024016799 A1 WO2024016799 A1 WO 2024016799A1 CN 2023093826 W CN2023093826 W CN 2023093826W WO 2024016799 A1 WO2024016799 A1 WO 2024016799A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
data transmission
transmission method
entry
formal
Prior art date
Application number
PCT/CN2023/093826
Other languages
English (en)
French (fr)
Inventor
王国文
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2024016799A1 publication Critical patent/WO2024016799A1/zh

Links

Classifications

    • 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
    • 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/54—Organization of routing tables
    • 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
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H04L61/5014—Internet protocol [IP] addresses using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP]
    • 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/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a data transmission method, an operator edge device, and a computer-readable storage medium.
  • Virtual Private Lan Service is an early Multi-Protocol Label Switching (MPLS) virtual private network (Virtual Private Network, VPN) technology for interconnecting user data centers. Problems exposed in aspects such as scalability, bandwidth utilization, and operation and maintenance have become increasingly prominent, and it can no longer adapt to the development needs of the data center.
  • MPLS Multi-Protocol Label Switching
  • EVPN Ethernet Virtual Private Network
  • EVPN inherits the advantages of Multi-Protocol Border Gateway Protocol (MP-BGP) and Virtual Extensible Local Area Network (VXLAN), and implements VXLAN Tunnel End Point (VTEP) through MP-BGP ) automatic discovery, automatic establishment of VXLAN tunnels, and automatic association of VXLAN tunnels with VXLAN, eliminating the need for manual configuration by users, reducing the difficulty of network deployment.
  • EVPN technology separates the control plane from the data plane. The control plane is responsible for publishing routing information, and the data plane is responsible for forwarding messages.
  • EVPN's multi-homing technology means that users (devices or networks) connect to multiple VTEPs in the EVPN network through multiple links (Provider Edge in Figure 1, PE) equipment), as shown in Figure 1, in the Ethernet Segment Identifier (ESI) dual-homing access scenario, the VTEP in the redundant backup group will advertise to the remote VTEP device through MP-BGP Information on the same Ethernet Segment (ES) automatically realizes active and backup backup of traffic between different VTEPs, and introduces a Designated Forwarder (DF) election filtering mechanism to avoid loops and unknown users.
  • DF Designated Forwarder
  • IP Internet Protocol
  • the present disclosure provides a data transmission method, an operator edge device, and a computer-readable storage medium.
  • the present disclosure provides a data transmission method, including: receiving a request message sent by a client, and generating a temporary entry corresponding to the client; wherein the client is connected to the current first operator edge PE The device is connected to the second PE device; and the request message is forwarded to the second PE device.
  • the present disclosure provides a data transmission method, including: receiving a request message forwarded by a first PE device and generating a temporary entry corresponding to a client; wherein the client, the first PE device and the current The second PE device is connected; and the request message is sent to the server.
  • the present disclosure provides a data transmission method, including: receiving a response message from a server in response to a request message sent by a client; wherein the client is connected to the current first PE device and the second PE device. ; If the formal entry cannot be generated, forward the response message to the second PE device.
  • the present disclosure provides a PE device, including: one or more processors; a memory having one or more computer programs stored thereon, and the one or more computer programs are processed by the one or more processors.
  • the processor is executed, so that the one or more processors implement any of the above data transmission methods.
  • the present disclosure provides a computer-readable medium having computer data stored thereon.
  • a machine program which is executed by the processor to implement any of the above data transmission methods.
  • Figure 1 is a schematic diagram of a network architecture
  • Figure 2 is a schematic diagram of the working principle of binding table generation
  • Figure 3 is a flow chart of a data transmission method in an embodiment of the present disclosure
  • Figure 4 is a flow chart of some steps in another data transmission method in an embodiment of the present disclosure.
  • Figure 5 is a flow chart of a data transmission method in an embodiment of the present disclosure.
  • Figure 6 is a flow chart of some steps in another data transmission method in an embodiment of the present disclosure.
  • Figure 7 is a flow chart of a data transmission method in an embodiment of the present disclosure.
  • Figure 8 is a flow chart of some steps in another data transmission method in an embodiment of the present disclosure.
  • Figure 9 is a block diagram of an operator edge device in an embodiment of the present disclosure.
  • Figure 10 is a block diagram of a computer-readable medium in an embodiment of the present disclosure.
  • Figure 11 is a block diagram of a binding table generation device in an embodiment of the present disclosure.
  • Figure 12 is a block diagram of a binding table generation system in an embodiment of the present disclosure.
  • words such as “first” and “second” are used to distinguish the same or similar items with basically the same functions and effects. Those skilled in the art can understand that words such as “first” and “second” do not limit the number and execution order, and words such as “first” and “second” do not limit the number and execution order.
  • Dynamic Host Configuration Protocol (Dynamic Host Configuration Protocol, DHCP) snooping (Snooping) is a security feature of DHCP, which can ensure that the client only obtains an IP address from a legitimate server, and also uses Media Access Control (MAC) Verification, control of the number of access users, and combined use with IP source filtering functions can effectively prevent attacks.
  • DHCP Dynamic Host Configuration Protocol
  • MAC Media Access Control
  • the device After enabling the DHCP Snooping protocol module on the device, the device will redirect all DHCP protocol packets to the local device for snooping and processing.
  • the client is dual-homed to the PE device through the Smart Group (SG) port of the Customer Edge (CE) device, and the dual-homing PE device is a cross-device link aggregation group (Multi-Chassis Link Aggregation Group, MC-LAG) equipment.
  • MC-LAG Multi-Chassis Link Aggregation Group
  • the client's request packet may randomly arrive at any one of the dual-homing PE devices; if the server's response packet arrives at the PE device that is different from the client's request packet, If the PE device to which the message arrives is different, the formal entry of the binding table cannot be generated correctly, and the client cannot apply for an IP address.
  • the formal entry of the binding table can be generated.
  • the official entries in the binding tables of the two dual-homed PE devices are inconsistent, it will also cause the user to be unable to use the applied IP address normally.
  • an embodiment of the present disclosure provides a data transmission method, including the following steps S11 to S12.
  • step S11 the request message sent by the client is received, and a temporary entry corresponding to the client is generated; the client is connected to the current first operator edge PE device and the second PE device.
  • step S12 the request message is forwarded to the second PE device.
  • the client is connected to the first PE device and the second PE device, which means that the client is connected to the first PE device and the second PE device through the CE device, and the CE device is dual-homed to the first PE device. and second PE equipment.
  • the PE device accessed by the client is an MC-LAG device.
  • the first PE device receives the request message sent by the client from the MC-LAG port.
  • a temporary entry corresponding to the client when generating a temporary entry for a client, if the entry corresponding to the client exists in the first PE device, the entry is updated and a temporary entry corresponding to the client is generated; if the first PE device When the entry corresponding to the client does not exist in the PE device, a temporary entry corresponding to the client is created.
  • the request message is a DHCP request message.
  • the first PE device after receiving the request message sent by the client and generating a temporary entry corresponding to the client, the first PE device forwards the request message to the second PE device, so that each client connected The temporary entry corresponding to the client can be generated in the PE device.
  • any PE device receives the response message from the server in response to the request message, it can generate a formal entry to ensure that the client can apply for the request normally. IP address.
  • the first PE device and the second PE device are used to distinguish different PE devices; different PE devices are equivalent, and the request message sent by the client can randomly arrive at the first PE device.
  • the PE device or the second PE device, and the response message sent by the server can also randomly arrive at the first PE device or the second PE device.
  • PE1 and PE2 are also used to distinguish different PE devices.
  • the first PE device corresponds to PE1 in Figure 1
  • the second PE device corresponds to PE2 in Figure 1 as an example.
  • the client is connected to the PE devices PE1 and PE2 through the CE device.
  • PE1 and PE2 are MC-LAG devices, and the SG is in load sharing mode.
  • the request message sent by the client may randomly reach any of PE1 and PE2.
  • the server's response message in response to the request message may randomly arrive at either PE1 or PE2.
  • PE1 receives the request message sent by the client, generates a temporary entry corresponding to the client, and then forwards the request message to PE2;
  • PE2 also generates a temporary entry corresponding to the client after receiving the request message. That is, there are temporary entries corresponding to the client in both PE1 and PE2.
  • the response message sent by the server randomly arrives at PE1 or PE2, the temporary entries corresponding to the client can be queried in PE1 or PE2, thereby generating a formal table. item so that the client can apply for an IP address normally.
  • the embodiment of this disclosure does not place any special restrictions on how the first PE device forwards the request message to the second PE device.
  • the first PE device forwards the request message to the second PE by sending the first exchange message.
  • the first PE device Encapsulate the request message and packet receiving port information into a Type Length Value (TLV) and carry it in the first switching message through the Layer 2 or Layer 3 channel configured between the first PE device and the second PE device. Forwarded to the second PE device.
  • TLV Type Length Value
  • forwarding the request message to the second PE device includes the following steps S121 to S122.
  • step S121 it is determined whether the packet receiving port that receives the request message is the MC-LAG port.
  • step S122 when the packet receiving port that receives the request message is the MC-LAG port, the request message is forwarded to the second PE device.
  • the MC-LAG ports are in load sharing mode.
  • a first exchange message for exchanging request messages between the first PE device and the second PE device is defined, and a first exchange message is deployed between the first PE device and the second PE device to transmit the first
  • a message switching channel is used to exchange messages. The first PE device sends the first switching message through the message switching channel and sends the request message to the second PE device.
  • forwarding the request message to the second PE device includes: generating a first exchange message, the first exchange message carrying the request message and the first PE device. MC-LAG port information in the device; sending the first switching message to the second PE device through the message switching channel configured between the first PE device and the second PE device.
  • the method when forwarding the request message to the second PE device, the method further includes: configuring a message switching channel between the first PE device and the second PE device.
  • a Layer 2 channel is configured between the first PE device and the second PE device as a packet switching channel.
  • a Layer 3 channel is configured between the first PE device and the second PE device as a packet switching channel.
  • the embodiment of the present disclosure does not have any special limitations on the first exchange message.
  • the first PE device encapsulates the request message and the packet receiving port information of the first PE into a TLV and carries it in the first switching message, thereby generating the first switching message.
  • generating the first exchange message includes: composing the request message and the MAC-LAG port information in the first PE device into the TLV of the first exchange message, to obtain The first exchange message.
  • forwarding the request message to the second PE device includes: excluding the network-side tunnel port of the first PE device and forwarding the request message.
  • the second PE device after the second PE device receives the request message forwarded by the first PE device and generates a temporary entry corresponding to the client, the second PE device sends the request message to the server on the network side.
  • the first PE device excluding the network side port of the first PE device from forwarding the request message can prevent the first PE device from sending the request message to the server on the network side, causing the server to The sent response message reaches the second PE device before a temporary entry is generated in the second PE device.
  • the first PE device excludes the network side port of the first PE device from forwarding the request message, and the second PE device sends the request message to the server after generating a temporary entry, which can ensure that the request message sent by the server is
  • the response message reaches the PE device connected to the client, a temporary entry for the client has been generated in the PE device, ensuring that the client can normally apply for an IP address.
  • the data transmission method further includes the following steps S131 to S133.
  • step S131 a response message from the server in response to the request message is received.
  • step S132 a formal entry is generated based on the response message and the temporary entry.
  • step S133 synchronize the official entry to the second PE device.
  • the response message received in step S131 may be a response message directly sent by the server to the first PE device, or may be a response message sent by the server to the second PE device.
  • the second PE device forwards the response packet to the first PE device.
  • the first PE device after performing steps S11 and S12, can query the temporary entry corresponding to the client, and therefore can generate a formal entry. After generating the formal entries, the first PE device synchronizes the formal entries to the second PE device, which ensures that the formal entries in each PE device connected to the client are consistent, so that the client can correctly use the requested IP address.
  • PE1 receives the response message of the server's response request message, locally queries the temporary entry corresponding to the client, generates the formal entry, and then synchronizes the formal entry to PE2, so that PE1 It is consistent with the official entry in PE2, so that the client can apply for an IP address normally and use the applied IP address correctly.
  • a synchronization message for synchronizing formal entries is defined, and a synchronization channel for transmitting the synchronization message is deployed between the first PE device and the second PE device.
  • the first PE device sends the synchronization message through the synchronization channel.
  • the synchronization message synchronizes the official entry to the second PE device.
  • synchronizing the formal entry to the second PE device includes: generating a synchronization message, the synchronization message carrying the information of the formal entry; and through the first The synchronization channel configured between the PE device and the second PE device sends the synchronization message to the second PE device.
  • when synchronizing the official entry to the second PE device it also includes: configuring a synchronization channel between the first PE and the second PE.
  • a Layer 2 channel is configured between the first PE and the second PE as a synchronization channel.
  • a Layer 3 channel is configured between the first PE and the second PE as a synchronization channel.
  • the embodiment of the present disclosure does not impose any special restrictions on synchronization messages.
  • the first PE device encapsulates the information of the formal entry into a type length value (Type Length Value, TLV) and carries it in the synchronization message, thereby generating a synchronization message.
  • TLV Type Length Value
  • generating a synchronization message includes: encapsulating the information of the formal entry into a type length value TLV of the synchronization message to obtain the synchronization message.
  • receiving a response message from the server in response to the request message includes: receiving the response message sent by the server; or receiving the response message forwarded by the second PE device.
  • the server responds to the request message sent by the client with a response message.
  • a response message may arrive at PE1 or PE2 randomly.
  • the response message sent by the server reaches PE1
  • PE2 if the temporary entry corresponding to the client is not found in PE2 , PE2 forwards the response message to PE1, which means that the first PE device receives the response message forwarded by the second PE device.
  • the data transmission method when receiving a response message forwarded by the second PE device, after the first PE device generates a formal entry based on the response message and the temporary entry, the data transmission method further includes : Exclude the tunnel port between the first PE device and the second PE device, and forward the response message.
  • the first PE device when the response message is a response message forwarded by the second PE device, the first PE device excludes the tunnel port between the first PE device and the second PE device after generating the formal entry, Further forwarding the response message can prevent the response message from being sent back to the second PE device again.
  • the tunnel port between the first PE device and the second PE device is excluded, the response message is forwarded, and the response message is forwarded to the client.
  • the data transmission method further includes the following step S14.
  • step S14 the formal entry synchronized from the second PE device is received, and the formal entry is generated in the first PE device.
  • the temporary entry corresponding to the client can be queried in the second PE device, and therefore the formal entry can be generated.
  • the second PE device synchronizes the formal entries to the first PE device, which ensures that the formal entries in each PE device accessed by the client are consistent, so that the client can correctly use the requested IP address.
  • PE1 receives the response message from the server in response to the request message sent by the client. If the temporary entry corresponding to the client is not found locally, it forwards the received response message to PE2; PE2 locally queries the temporary entry corresponding to the client, generates a formal entry, and then synchronizes the formal entry to PE1; PE1 receives the formal entry synchronized from PE2 and generates a formal entry, so that PE1 and PE2 The formal entries remain consistent, allowing the client to apply for an IP address normally and use the applied IP address correctly. IP address.
  • PE2 receives the response message from the server in response to the request message sent by the client, locally queries the temporary entry corresponding to the client, generates the formal entry, and then synchronizes the formal entry to PE1 ;
  • PE1 receives the formal entries synchronized from PE2 and generates formal entries, so that the formal entries in PE1 and PE2 are consistent, so that the client can apply for an IP address normally and use the applied IP address correctly.
  • the embodiment of the present disclosure does not place special restrictions on how the second PE device synchronizes the official entry to the first PE device.
  • the second PE device synchronizes the official entry to the first PE device by sending a synchronization message.
  • the second PE device encapsulates the formal entry into a TLV and carries it in the synchronization message, and forwards it to the first PE device through the Layer 2 or Layer 3 channel configured between the PE devices.
  • the first PE device parses the synchronization message to obtain the official entry.
  • receiving a formal entry synchronized from the second PE device and generating a formal entry in the first PE device includes: receiving a synchronization report sent by the second PE device.
  • the synchronization message sent by the second PE device carries the information of the formal entry, and the information of the formal entry includes the formal entry and the cross-device link aggregation group MC- in the second PE device.
  • LAG port information replace the MC-LAG port in the second PE device with the corresponding MC-LAG port in the first PE device, and generate a formal entry in the first PE device.
  • the data transmission method further includes the following steps S151 to S152.
  • step S151 a response message from the server in response to the request message is received.
  • step S152 if the formal entry cannot be generated, the response message is forwarded to the second PE device.
  • the response message received in step S151 may be a response message directly sent by the server to the first PE device, or may be a response message sent by the server to the second PE device.
  • the second PE device forwards the response packet to the first PE device.
  • the first PE device when the first PE device cannot generate a formal entry, it forwards the response message to the second PE device, aiming to send the response message to the existing client.
  • PE device corresponding to the temporary entry to ensure that the formal entry can be generated normally.
  • PE1 receives the response message from the server in response to the request message sent by the client. If the temporary entry corresponding to the client is not found locally, it forwards the received response message to PE2; PE2 locally queries the temporary entry corresponding to the client and generates a formal entry to ensure that the client can normally apply for an IP address.
  • a second exchange message for exchanging response messages between the first PE device and the second PE device is defined, and a second exchange message is deployed between the first PE device and the second PE device.
  • a message switching channel is used to exchange messages. The first PE device sends a second switching message and a response message to the second PE device through the message switching channel.
  • forwarding the response message to the second PE device includes: generating a second exchange message, the second exchange message carrying the response message and the third PE device.
  • MC-LAG port information in a PE device sending the second exchange message to the second PE device through the message exchange channel configured between the first PE device and the second PE device .
  • the method when forwarding the response packet to the second PE device, the method further includes: configuring a message switching channel between the first PE device and the second PE device.
  • a Layer 2 channel is configured between the first PE device and the second PE device as a packet switching channel.
  • a Layer 3 channel is configured between the first PE device and the second PE device as a packet switching channel.
  • the embodiment of the present disclosure does not have any special limitations on the second exchange message.
  • the first PE device encapsulates the response message and the packet receiving port information of the first PE into a TLV and carries it in the second switching message, thereby generating the second switching message.
  • generating the second exchange message includes: converting the The response message and the MC-LAG port information in the first PE device are encapsulated into the TLV of the second switching message to obtain the second switching message.
  • an embodiment of the present disclosure provides a data transmission method, including the following steps S21 to S22.
  • step S21 the request message forwarded by the first PE device is received, and a temporary entry corresponding to the client is generated; the client is connected to the first PE device and the current second PE device.
  • step S22 the request message is sent to the server.
  • the first PE device after receiving the request message sent by the client and generating a temporary entry corresponding to the client, the first PE device forwards the request message to the second PE device; the second PE device receives the After the first PE device forwards the request message, it also generates a temporary entry corresponding to the client, so that each PE device connected to the client can generate a temporary entry for the client.
  • any PE device receives the service
  • the client responds to the response message of the request message, it can generate a formal entry, thereby ensuring that the client can normally apply for an IP address.
  • the client is connected to the PE devices PE1 and PE2 through the CE device.
  • PE1 and PE2 are MC-LAG devices, and the SG is in load sharing mode.
  • the client's request message may randomly arrive at either PE1 or PE2.
  • the server's response message may also randomly arrive at either PE1 or PE2.
  • PE1 receives the request message sent by the client, generates a temporary entry corresponding to the client, and then forwards the request message to PE2;
  • PE2 also generates a temporary entry corresponding to the client after receiving the request message. That is, there are temporary entries corresponding to the client in both PE1 and PE2.
  • the response message from the server randomly arrives at PE1 or PE2, the temporary entries of the client can be queried in PE1 or PE2, thereby generating formal entries, so that the client The client can apply for an IP address normally.
  • the embodiment of this disclosure does not place any special restrictions on how the first PE device forwards the request message to the second PE device.
  • the first PE device forwards the request message to the second PE device by sending the first exchange message.
  • the first PE device encapsulates the request message and the packet receiving port information into a TLV and carries it in the first switching message through the Layer 2 or Layer 3 configured between the first PE device and the second PE device. The channel is forwarded to the second PE device.
  • the second PE device obtains the request message by parsing the first exchange message. arts.
  • receiving the request message forwarded by the first PE device and generating a temporary entry corresponding to the client includes: receiving the first exchange message sent by the first PE device, and the first The exchange message carries the request message and the MC-LAG port information in the first PE device; replace the MC-LAG port in the first PE device with the corresponding MC-LAG port in the second PE device. LAG port to generate the temporary entry.
  • sending the request message to the server includes: excluding the tunnel port between the second PE device and the first PE device, and forwarding the request message.
  • the port between the second PE device and the first PE device is excluded, and the request message is sent to the server, which can prevent the request message from being sent back to the first PE device again.
  • PE equipment in the embodiment of the present disclosure, the port between the second PE device and the first PE device is excluded, and the request message is sent to the server, which can prevent the request message from being sent back to the first PE device again.
  • the data transmission method further includes the following steps S231 to S233.
  • step S231 a response message from the server in response to the request message is received.
  • step S232 a formal entry is generated based on the response message and the temporary entry.
  • step S233 synchronize the official entry to the first PE device.
  • the temporary entry corresponding to the client can be queried in the second PE device, and therefore the formal entry can be generated.
  • the second PE device synchronizes the formal entries to the first PE device, which ensures that the formal entries in each PE device accessed by the client are consistent, so that the client can correctly use the requested IP address.
  • a synchronization message for synchronizing formal entries is defined, and a synchronization channel for transmitting the synchronization message is deployed between the second PE device and the first PE device, and the second PE device sends the synchronization message through the synchronization channel.
  • the synchronization message synchronizes the official entry to the first PE device.
  • synchronizing the formal entry to the first PE device includes: generating a synchronization message, the synchronization message carrying the information of the formal entry; The synchronization message is sent to the first PE device through the synchronization channel configured between the second PE device and the first PE device.
  • when synchronizing the official entry to the first PE device it also includes: configuring a synchronization channel between the second PE and the first PE.
  • a Layer 2 channel is configured between the second PE and the first PE as a synchronization channel.
  • a Layer 3 channel is configured between the second PE and the first PE as a synchronization channel.
  • the embodiment of the present disclosure does not impose any special restrictions on synchronization messages.
  • the second PE device encapsulates the formal entry into a type length value (Type Length Value, TLV) and carries it in the synchronization message, thereby generating a synchronization message.
  • TLV Type Length Value
  • generating a synchronization message includes: encapsulating the information of the formal entry into the TLV of the synchronization message to obtain the synchronization message.
  • the response message received in step S231 may be a response message directly sent by the server to the second PE device, or may be a response message sent by the server to the first PE device.
  • the first PE device forwards the response packet to the second PE device.
  • receiving a response message from the server in response to the request message includes: receiving the response message sent by the server; or receiving the response message forwarded by the first PE device. arts.
  • the data transmission method when receiving the response message forwarded by the first PE device, after the second PE device generates a formal entry based on the response message and the temporary entry, the data transmission method It also includes: excluding the tunnel port between the second PE device and the first PE device, and forwarding the response message.
  • the second PE device when the response message is a response message forwarded by the first PE device, the second PE device, after generating the formal entry, excludes the port between the second PE device and the first PE device, and further Forwarding the response message can prevent the response message from being sent back to the first PE device again.
  • the port between the second PE device and the first PE device is excluded, the response message is forwarded, and the response message is forwarded to the client.
  • the data transmission method further includes the following step S24.
  • step S24 the formal entry synchronized from the first PE device is received, and the formal entry is generated in the second PE device.
  • the first PE device after performing steps S21 and S22, can query the temporary entry corresponding to the client, and therefore can generate a formal entry. After generating the formal entries, the first PE device synchronizes the formal entries to the second PE device, which ensures that the formal entries in multiple PE devices connected to the client are consistent, so that the client can correctly use the requested IP address.
  • the embodiment of the present disclosure does not place special restrictions on how the first PE device synchronizes the official entry to the first PE device.
  • the first PE device synchronizes the official entry to the second PE device by sending a synchronization message.
  • the first PE device encapsulates the formal entry into a TLV and carries it in the synchronization message, and forwards it to the second PE device through the Layer 2 or Layer 3 channel configured between the PE devices.
  • the second PE device parses the synchronization message to obtain the official entry.
  • receiving a formal entry synchronized from the first PE device and generating a formal entry in the first PE device includes: receiving a synchronization report sent by the first PE device.
  • the synchronization message sent by the first PE device carries the information of the formal entry, and the information of the formal entry includes the formal entry and the MC-LAG port information in the first PE device;
  • the MC-LAG port in the first PE device is replaced with the corresponding MC-LAG port in the second PE device, and a formal entry is generated in the second PE device.
  • the data transmission method further includes the following steps S251 to S252.
  • step S251 a response message from the server in response to the request message is received.
  • step S252 if the formal entry cannot be generated, the response message is forwarded to the first PE device.
  • the second PE device when the second PE device cannot generate a formal entry, it forwards the response message to the first PE device, aiming to send the response message to the client where the temporary entry corresponding to the client exists.
  • PE equipment to ensure that formal entries can be generated normally.
  • a third exchange message for exchanging response messages between the second PE device and the first PE device is defined, and a third exchange message is deployed between the second PE device and the first PE device to transmit the third exchange message.
  • a message switching channel is used to exchange messages. The second PE device sends a third switching message and a response message to the first PE device through the message switching channel.
  • forwarding the response message to the first PE device includes: generating a third exchange message, the third exchange message carrying the response message and the third exchange message. MC-LAG port information in the second PE device; sending the third exchange message to the first PE device through the message exchange channel configured between the second PE device and the first PE device.
  • the method when forwarding the response message to the first PE device, the method further includes: configuring a message exchange channel between the second PE device and the first PE device.
  • a Layer 2 channel is configured between the second PE device and the first PE device as a packet switching channel.
  • a Layer 3 channel is configured between the second PE device and the first PE device as a packet switching channel.
  • the embodiment of the present disclosure does not have any special limitations on the third exchange message.
  • the second PE device encapsulates the response message and the packet receiving port information of the second PE into a TLV and carries it in the third switching message, thereby generating the third switching message.
  • generating a third switching message includes: encapsulating the response message and the MC-LAG port information in the second PE device into the TLV of the third switching message, The third exchange message is obtained.
  • an embodiment of the present disclosure provides a data transmission method, including the following steps S31 to S32.
  • step S31 receive the server's response to the request message sent by the client. message; the client is connected to the current first PE device and the second PE device.
  • step S32 if the formal entry cannot be generated, the response message is forwarded to the second PE device.
  • the first PE device when the first PE device cannot generate a formal entry, it forwards the response message to the second PE device, aiming to send the response message to the client where the temporary entry corresponding to the client exists.
  • PE equipment so that formal entries can be generated normally, thereby ensuring that the client can normally apply for an IP address.
  • PE1 receives the response message sent by the server and does not query the temporary entry corresponding to the client locally, so it forwards the received response message to PE2; PE2 queries the client locally.
  • the corresponding temporary entry is generated into a formal entry to ensure that the client can normally apply for an IP address.
  • a second exchange message for exchanging response messages between the first PE device and the second PE device is defined, and a second exchange message is deployed between the first PE device and the second PE device.
  • a message switching channel is used to exchange messages. The first PE device sends a second switching message and a response message to the second PE device through the message switching channel.
  • forwarding the response message to the second PE device includes: generating a second exchange message, the second exchange message carrying the response message and the third PE device.
  • MC-LAG port information in a PE device sending the second exchange message to the second PE device through the message exchange channel configured between the first PE device and the second PE device .
  • the method when forwarding the response packet to the second PE device, the method further includes: configuring a message switching channel between the first PE device and the second PE device.
  • a Layer 2 channel is configured between the first PE device and the second PE device as a packet switching channel.
  • a Layer 3 channel is configured between the first PE device and the second PE device as a packet switching channel.
  • the embodiment of the present disclosure does not have any special limitations on the second exchange message.
  • the first PE device combines the response message and the received data of the first PE device.
  • the packet port information is encapsulated into a TLV and carried in the second switching message, thereby generating a second switching message.
  • generating the second switching message includes: encapsulating the response message and the MC-LAG port information in the first PE device into the TLV of the second switching message, The second exchange message is obtained.
  • the data transmission method further includes the following step S33.
  • step S33 the formal entry synchronized from the second PE device is received, and the formal entry is generated in the first PE device.
  • the embodiment of the present disclosure does not place special restrictions on how the second PE device synchronizes the official entry to the first PE device.
  • the second PE device synchronizes the official entry to the first PE by sending a synchronization message.
  • the second PE device encapsulates the formal entry into a TLV and carries it in the synchronization message, and forwards it to the first PE device through the Layer 2 or Layer 3 channel configured between the PE devices.
  • the first PE device parses the synchronization message to obtain the official entry.
  • receiving a formal entry synchronized from the second PE device and generating a formal entry in the first PE device includes: receiving a synchronization report sent by the second PE device.
  • the synchronization message sent by the second PE device carries the information of the formal entry, and the information of the formal entry includes the formal entry and the MC-LAG port information in the second PE device;
  • the MC-LAG port in the second PE device is replaced with the corresponding MC-LAG port in the first PE device, and a formal entry is generated in the first PE device.
  • the data transmission method further includes the following steps S341 to S342.
  • step S341 if a formal entry can be generated, the formal entry is generated.
  • step S342 synchronize the official entry to the second PE device.
  • a synchronization message for synchronizing formal entries is defined, and a synchronization channel for transmitting the synchronization message is deployed between the first PE device and the second PE device.
  • the first PE device sends the synchronization message through the synchronization channel.
  • the synchronization message synchronizes the official entry to the second PE device.
  • synchronizing the formal entry to the second PE device includes: generating a synchronization message, the synchronization message carrying the information of the formal entry; and through the first PE device The synchronization channel configured with the second PE device sends the synchronization message to the second PE device.
  • when synchronizing the official entry to the second PE device it also includes: configuring a synchronization channel between the first PE device and the second PE device.
  • a Layer 2 channel is configured between the first PE device and the second PE device as a synchronization channel.
  • a Layer 3 channel is configured between the first PE device and the second PE device as a synchronization channel.
  • the embodiment of the present disclosure does not impose any special restrictions on synchronization messages.
  • the first PE device encapsulates the formal entry into a type length value (Type Length Value, TLV) and carries it in the synchronization message, thereby generating a synchronization message.
  • TLV Type Length Value
  • generating a synchronization message includes: encapsulating the information of the formal entry into the TLV of the synchronization message to obtain the synchronization message.
  • the data transmission method further includes the following steps S351 to S353.
  • step S351 receive the response message forwarded by the second PE device.
  • step S352 if a formal entry can be generated, a formal entry is generated according to the response message, and the communication between the first PE device and the second PE device is eliminated.
  • the tunnel port forwards the response message.
  • step S353 if the formal entry cannot be generated, the response message is discarded.
  • the data transmission method further includes the following steps S361 to S362.
  • step S361 the request message sent by the client is received, and a temporary entry corresponding to the client is generated.
  • step S362 the request message is forwarded to the second PE device.
  • the first PE device after receiving the request message sent by the client and generating a temporary entry corresponding to the client, the first PE device forwards the request message to the second PE device, so that each client connected The temporary entry corresponding to the client can be generated in the PE device.
  • any PE device receives the response message sent by the server in response to the request message, combined with steps S31 to S32, it can ensure that the formal entry is generated, thus Make sure the client can apply for an IP address normally.
  • a first exchange message for exchanging request messages between the first PE device and the second PE device is defined, and a first exchange message is deployed between the first PE device and the second PE device to transmit the first
  • a message switching channel is used to exchange messages. The first PE device sends the first switching message through the message switching channel and sends the request message to the second PE device.
  • forwarding the request message to the second PE device includes: generating a first exchange message, the first exchange message carrying the request message and the third PE device.
  • MC-LAG port information in a PE device sending the first exchange message to the second PE device through a message exchange channel configured between the first PE device and the second PE device .
  • the method when forwarding the request packet to the second PE device, the method further includes: configuring a packet switching channel between the first PE and the second PE device.
  • a Layer 2 channel is configured between the first PE and the second PE as a packet switching channel.
  • between the first PE and the second PE Configure a Layer 3 channel between them as a message switching channel.
  • the embodiment of the present disclosure does not have any special limitations on the first exchange message.
  • the first PE device encapsulates the request message and the packet receiving port information of the first PE into a TLV and carries it in the first switching message, thereby generating the first switching message.
  • generating the first exchange message includes: composing the request message and the MC-LAG port information in the first PE device into the TLV of the first exchange message, to obtain The first exchange message.
  • the data transmission method further includes the following steps S371 to S372.
  • step S371 the request message forwarded by the second PE device is received, and a temporary entry corresponding to the client is generated.
  • step S372 the request message is sent to the server.
  • the second PE device after receiving the request message sent by the client and generating a temporary entry corresponding to the client, the second PE device forwards the request message to the first PE device; the first PE device receives After the second PE device forwards the request message, it also generates a temporary entry corresponding to the client, so that each PE device connected to the client can generate a temporary entry corresponding to the client.
  • any PE device receives
  • the server sends a response message in response to the request message, combined with steps S31 to S32, it is ensured that a formal entry is generated, thereby ensuring that the client can normally apply for an IP address.
  • an embodiment of the present disclosure provides a PE device, which includes: one or more processors 101; a memory 102, on which one or more computer programs are stored, and the one or more computer programs are One or more processors execute, causing the one or more processors to implement any one of the above data transmission methods.
  • One or more I/O interfaces 103 are connected between the processor and the memory, and are configured to implement information exchange between the processor and the memory.
  • the processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU), etc.; the memory 102 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically such as SDRAM). , DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH); the I/O interface (read-write interface) 103 is connected between the processor 101 and the memory 102, and can Reality
  • the information exchange between the processor 101 and the memory 102 includes but is not limited to a data bus (Bus), etc.
  • processor 101 memory 102, and I/O interface 103 are connected to each other and, in turn, to other components of the computing device via bus 104.
  • an embodiment of the present disclosure provides a computer-readable storage medium on which a computer program is stored, and the computer program is executed by a processor to implement any one of the above data transmission methods.
  • generating formal entries of the binding table includes the following steps 401 to 405.
  • one of the dual-homed PE devices receives the client's DHCP request message from the MC-LAG port. After passing the message validity check, it queries whether there is a local entry corresponding to the client's MAC address. If so, If not, create a temporary entry containing client MAC address, packet receiving port, EVPN and other information, then encapsulate the packet and exchange the packet to the peer dual-homed PE device PE2 by sending a message. ;At the same time, PE1 also excludes the network-side tunnel port from forwarding packets normally.
  • the purpose of excluding tunnel port forwarding on the network side is to prevent the server on the network side from sending a unicast response message immediately after receiving the request message, and the response message reaches PE2 through load sharing.
  • PE1 The request packet processed by the switching module may not have reached PE2 yet, causing the response packet to fail to be processed and discarded because the corresponding client MAC entry cannot be found. If PE1 receives the request message from a non-MC-LAG port, it will process the forwarding normally. It will not be synchronized to PE2, and there is no need to exclude network-side tunnel port forwarding.
  • step 402 after PE2 receives the request message, it replaces the packet receiving port with the MC-LAG port of the device and processes it normally. It establishes or updates the temporary entry and then forwards it; when forwarding, the tunnel between the dual-homed devices needs to be excluded. It should be noted that the reason why the tunnel between dual-homed PE devices is excluded from forwarding is that the packet is sent from PE1 and should not be forwarded back to PE1.
  • one of the dual-homed PE devices receives the DHCP response message from the server from the MC-LAG port. If PE1 does not find the temporary entry through the corresponding client MAC address, the response message cannot be processed normally. Encapsulate the message and send the response message to the peer PE2 for processing. At the same time, the response message is discarded locally and will not be forwarded. If the temporary entry is queried on PE1, the response message is processed normally and the temporary table is The IP address bound to the entry and the lease renewal period are converted into formal entries, and the response packet is forwarded locally normally. If PE1 receives the response message from a non-MC-LAG port, it will process and forward it normally. If the entry cannot be queried, it does not need to be synchronized to PE2, and it can be discarded locally.
  • PE2 replaces the packet receiving port with the MC-LAG port of the device and processes it normally; when forwarding, the tunnel between dual-homing devices is excluded.
  • step 405 the formal entry of the MC-LAG port is synchronized to the opposite dual-homed PE device by sending a message.
  • processing the request message includes the following steps 501 to 505.
  • PE1 receives the request message, processes it locally, and generates or updates temporary entries.
  • step 502 it is determined whether the packet receiving port is an MC-LAG port. If so, step 504 is executed; otherwise, step 503 is executed.
  • step 503 the request message is forwarded normally locally.
  • step 504 the request packet is exchanged to PE2; while the request packet is exchanged to PE2, the network side tunnel port is locally excluded for forwarding.
  • PE2 receives the exchanged request packet and switches the packet receiving port to the local MC-LAG port to continue processing.
  • PE2 receives the exchanged request message and switches the packet receiving port to the local MC-LAG port to continue processing, which further includes the following steps 5051 to 5053.
  • step 5051 replace the packet receiving port of the request message with the local MC-LAG port.
  • step 5052 a temporary entry corresponding to the local client MAC address is generated or updated.
  • step 5053 after excluding the tunnel between the dual-homed PE devices, the packet is forwarded.
  • processing the response message includes the following steps 601 to 608.
  • PE1 or PE2 receives the response message and processes it locally to determine whether the packet receiving port is configured as a trusted port. If so, step 603 is executed; otherwise, step 602 is executed.
  • step 602 the response message is discarded and the process ends.
  • step 603 query whether the entry corresponding to the client's MAC address exists. If so, perform step 604; otherwise, perform step 605.
  • step 604 the message is processed and forwarded normally.
  • step 605 it is further determined whether the packet receiving port is an MC-LAG port. If so, step 607 is executed. Otherwise, step 606 is executed.
  • step 606 the response message is discarded and the process ends.
  • step 607 the response message is exchanged to the opposite PE device through the message switching module and discarded locally.
  • PE1 or PE2 receives the exchanged response packet and switches the packet receiving port to the local MC-LAG port to continue processing.
  • step 604 the message is processed and forwarded normally, which further includes the following steps 6041 to 6042.
  • step 6041 bind the IP to the table entry and update the table entry lease.
  • step 6042 the response message is forwarded normally.
  • PE1 or PE2 receives the exchanged response message and switches the packet receiving port to the local MC-LAG port to continue processing, which further includes the following steps 6081 to 6085.
  • step 6081 replace the packet receiving port of the response message with the local MC-LAG port.
  • step 6082 query whether the entry corresponding to the client's MAC address exists. If so, perform step 6084; otherwise, perform step 6083.
  • step 6083 the response message is discarded and the process ends.
  • step 6084 bind the IP to the table entry and update the table entry lease.
  • step 6085 after excluding the tunnel between the dual-homed PE devices, the packet is forwarded.
  • the binding table generating device in this embodiment is shown in Figure 11.
  • the binding table generation device includes: a message processing module configured to process the received protocol message. If the message is an exchange message, replace it with the MC-LAG port corresponding to the device for processing. If it is a request message, a temporary entry is generated, or the formal entry is updated for lease renewal. If it is a response message, a formal entry is generated based on the temporary entry, or the formal entry is updated directly.
  • the message switching module is configured to exchange protocol messages. It encapsulates the protocol messages received from the MC-LAG port and the packet receiving port and other information into TLVs and puts them in the messages, through the Layer 2 configured between the two PE devices. Or a Layer 3 channel, forwarded to the DHCP Snooping message switching module of the peer dual-homed PE device. The message switching module receives the message, unpacks it, and passes it to the message processing module.
  • the information synchronization module is configured to encapsulate the formal entry information of the MC-LAG port into the TLV in the message, and forward it to the opposite end dual-homing PE device DHCP Snooping through the Layer 2 or Layer 3 channel configured between the two PE devices. Information synchronization module.
  • the information synchronization module receives the message and unpacks it, generates a user binding entry, and replaces the user port with the MC-LAG port corresponding to the device.
  • dual-homing PE devices can receive the same request message from the MC-LAG port, and the response message from the MC-LAG port that cannot be processed normally can be exchanged to the opposite device. Processing is performed to ensure the correct generation of binding entries on dual-homed PE devices, and the formal entries corresponding to MC-LAG ports are synchronized through the information synchronization module to ensure the consistency of MC-LAG entries on dual-homed PE devices.
  • this embodiment also provides a binding table generation system, including: device A, including a component message processing module, a message exchange module and an information synchronization module, configured to process and exchange protocol messages, and generate Official entry and synchronize the entry.
  • device B including a component message processing module, a message exchange module, and an information synchronization module, is configured to process and exchange protocol messages, generate formal entries, and synchronize the entries.
  • the two devices exchange messages with each other through the message switching module and message processing module, so that the MC-LAG port receives and processes the same request message, and the response message from the MC-LAG port that cannot be processed normally can be exchanged to
  • the peer device processes and synchronizes the official MC-LAG port entries through the information synchronization module to ensure the consistency of the MC-LAG entries on dual-homed PE devices. From the perspective of dual-homing CE devices, the dual-homing PE devices are Virtualize into one The device is not affected by the load sharing mode of SG and the redundant working mode of ESI, ensuring the correct and stable generation of binding table entries.
  • 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).
  • computer storage media includes volatile and nonvolatile media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. removable, removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disk (DVD) or other optical disk storage, magnetic cassettes, tapes, disk storage or other magnetic storage devices, or may Any other medium used to store desired information and that can be accessed by a computer.
  • 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 may include any information delivery media .
  • Example embodiments have been disclosed herein, and although specific terms are employed, they are used and should be interpreted in a general illustrative sense only and not for purpose of limitation. In some instances, it will be apparent to those skilled in the art that, unless expressly stated otherwise, features, characteristics, and/or elements described in connection with a particular embodiment may be used alone, or may be combined with features, characteristics, and/or elements described in connection with other embodiments. and/or used in combination with components. Accordingly, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the scope of the present disclosure as set forth in the appended claims.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本公开提供一种数据传输方法、运营商边缘设备、计算机可读介质。客户端通过CE设备与第一PE设备和第二PE设备连接，客户端发送的请求报文可以随机到达第一PE设备或第二PE设备；当第一PE设备接收到请求报文时生成临时表项，并将请求报文转发到第二PE设备；第二PE设备接收到第一PE设备转发的请求报文，生成临时表项，并将请求报文发送到服务端；服务端发送的应答报文也可以随机到达第一PE设备或第二PE设备；当第一PE设备接收到应答报文时，若无法生成正式表项，则将该应答报文转发到第二PE设备；第一PE设备和第二PE设备任意一者生成了正式表项，会将正式表项同步到对端的PE设备。本公开能够确保正式表项的正确生成，以及各PE设备中正式表项保持一致。

Description

数据传输方法、运营商边缘设备、计算机可读存储介质
相关申请的交叉引用
本申请要求于2022年7月19日提交的中国专利申请NO.202210847353.X的优先权，该中国专利申请的内容通过引用的方式整体合并于此。
技术领域
本公开涉及通信技术领域，特别涉及一种数据传输方法、一种运营商边缘设备、一种计算机可读存储介质。
背景技术
虚拟专用局域网业务(Virtual Private Lan Service，VPLS)是一种早期出现的用户数据中心互连的多协议标签交换(Multi-Protocol Label Switching，MPLS)虚拟专用网络(Virtual Private Network，VPN)技术，其在可扩展性、带宽利用率、运维等方面暴露出来的问题日渐突出，已无法适应数据中心的发展需求。在此背景下，基于Overlay技术的以太虚拟专用网络(Ethernet Virtual Private Network，EVPN)技术应运而生。
EVPN继承了多协议边界网关协议(Multi Protocol Border Gateway Protocol，MP-BGP)和虚拟扩展局域网(Virtual Extensible Local Area Network，VXLAN)的优势，通过MP-BGP实现VXLAN隧道端点(VXLAN Tunnel End Point，VTEP)自动发现、VXLAN隧道自动建立、VXLAN隧道与VXLAN自动关联，无需用户手工配置，降低了网络部署难度。EVPN技术将控制平面与数据平面分离，控制平面负责发布路由信息，数据平面负责转发报文。
EVPN的多归技术是指用户(设备或网络)通过多条链路连接到EVPN网络中的多台VTEP(如图1中的运营商边缘(Provider Edge， PE)设备)设备上，如图1所示，在以太网段标识(Ethernet Segment Identifier，ESI)双归接入场景中，冗余备份组中的VTEP会通过MP-BGP向远端VTEP设备通告同一以太网段(Ethernet Segment，ES)的信息以自动实现流量在不同VTEP之间的主备备份，同时引入指定转发器(Designated Forwarder，DF)选举过滤机制，能够避免环路以及避免用户未知单播和组播(Broadcast,Unknown unicast and Multicast，BUM)流量的重复接收。
但是，用户在EVPN场景中申请网际互连协议(Internet Protocol，IP)地址的体验有待进一步提升。
发明内容
本公开提供一种数据传输方法、一种运营商边缘设备、一种计算机可读存储介质。
第一方面，本公开提供一种数据传输方法，包括：接收客户端发送的请求报文，生成所述客户端对应的临时表项；其中，所述客户端与当前的第一运营商边缘PE设备和第二PE设备连接；将所述请求报文转发到所述第二PE设备。
第二方面，本公开提供一种数据传输方法，包括：接收第一PE设备转发的请求报文，生成客户端对应的临时表项；其中，所述客户端与所述第一PE设备和当前的第二PE设备连接；将所述请求报文发送到服务端。
第三方面，本公开提供一种数据传输方法，包括：接收服务端应答客户端发送的请求报文的应答报文；其中，所述客户端与当前的第一PE设备和第二PE设备连接；在无法生成正式表项的情况下，将所述应答报文转发到所述第二PE设备。
第四方面，本公开提供一种PE设备，包括：一个或多个处理器；存储器，其上存储有一个或多个计算机程序，所述一个或多个计算机程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现上述任意一种数据传输方法。
第五方面，本公开提供一种计算机可读介质，其上存储有计算 机程序，所述程序被处理器执行，以实现上述任意一种数据传输方法。
附图说明
图1是一种网络架构的示意图；
图2是绑定表生成的工作原理示意图；
图3是本公开实施方式中一种数据传输方法的流程图；
图4是本公开实施方式中另一种数据传输方法中部分步骤的流程图；
图5是本公开实施方式中一种数据传输方法的流程图；
图6是本公开实施方式中另一种数据传输方法中部分步骤的流程图；
图7是本公开实施方式中一种数据传输方法的流程图；
图8是本公开实施方式中另一种数据传输方法中部分步骤的流程图；
图9是本公开实施方式中一种运营商边缘设备的组成框图；
图10是本公开实施方式中一种计算机可读介质的组成框图；
图11是本公开实施方式中一种绑定表生成装置的组成框图；以及
图12是本公开实施方式中一种绑定表生成系统的组成框图。
具体实施方式
为使本领域的技术人员更好地理解本公开的技术方案，下面结合附图对本公开提供的数据传输方法、运营商边缘设备、计算机可读介质进行详细描述。
在下文中将参考附图更充分地描述示例实施例，但是所述示例实施例可以以不同形式来体现且不应当被解释为限于本文阐述的实施例。提供这些实施例的目的在于使本公开更加透彻和完整，并使本领域技术人员充分理解本公开的范围。
在不冲突的情况下，本公开各实施例及实施例中的各特征可相互组合。
如本文所使用的，术语“和/或”包括一个或多个相关列举条目的任何和所有组合。
本文所使用的术语仅用于描述特定实施例，且不意欲限制本公开。如本文所使用的，单数形式“一个”和“该”也意欲包括复数形式，除非上下文另外清楚指出。还将理解的是，当本说明书中使用术语“包括”和/或“由……制成”时，指定存在特定特征、整体、步骤、操作、元件和/或组件，但不排除存在或可添加一个或多个其它特征、整体、步骤、操作、元件、组件和/或其群组。
为了便于清楚描述技术方案，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。
除非另外限定，否则本文所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解，诸如在常用字典中限定的那些术语应当被解释为具有与其在相关技术以及本公开的背景下的含义一致的含义，且将不解释为具有理想化或过度形式上的含义，除非本文明确如此限定。
动态主机配置协议(Dynamic Host Configuration Protocol，DHCP)侦听(Snooping)是DHCP的一种安全特性，能够保证客户端只从合法的服务器获取IP地址，同时通过媒体访问控制(Media Access Control，MAC)校验、接入用户数量控制、与IP源过滤功能等结合使用，可以有效的预防攻击。
在一些相关技术中，DHCP Snooping绑定表生成的基本工作原理如图2所示。
在设备上使能DHCP Snooping协议模块后，设备会将所有DHCP协议报文重定向到本地进行侦听处理。
(1)对于接收到的DHCP请求报文，首先检查其合法性，对不合法的DHCP请求报文进行丢弃处理；对于合法的DHCP请求报文，如果本地无该客户端信息，则建立包含收包端口和客户端MAC地址等信息的临时表项；如果本地有该客户端信息，则更新对应临时表项，报 文处理后正常转发；
(2)对于接收到的DHCP应答报文，首先检查其合法性，不合法的DHCP应答报文被丢弃处理；对于合法的DHCP应答报文，进一步判断收包端口是否配置为信任端口，如果不是信任端口，则也将DHCP应答报文进行丢弃处理；如果收包端口是信任端口，且查询到本地有相同客户端MAC地址对应的临时表项，则添加服务端分配的IP地址到临时表项并转成正式绑定表项，同时，根据DHCP应答报文携带的租期选项，设置表项的租期；如果未查询到本地表项，则也将DHCP应答报文进行丢弃处理；未丢弃处理的DHCP应答报文在本地正常转发。
在EVPN VXLAN ESI场景下，假设客户端通过用户边缘(Customer Edge，CE)设备的智能组(Smart Group，SG)端口双归接入到PE设备上，双归PE设备为跨设备链路聚合组(Multi-Chassis Link Aggregation Group，MC-LAG)设备。在一些相关技术中，当MC-LAG端口为负荷分担模式时，客户端的请求报文可能随机到达双归PE设备中的任意一者；如果服务端的应答报文到达的PE设备与客户端的请求报文到达的PE设备不相同，则绑定表的正式表项无法正确生成，客户端无法申请到IP地址；如果请求报文和应答报文在同一PE设备处理，可以生成绑定表的正式表项，但两台双归PE设备的绑定表的正式表项不一致，也会导致用户无法正常使用申请到的IP地址。
有鉴于此，第一方面，参照图3，本公开实施例提供一种数据传输方法，包括如下步骤S11至S12。
在步骤S11中，接收客户端发送的请求报文，生成所述客户端对应的临时表项；所述客户端与当前的第一运营商边缘PE设备和第二PE设备连接。
在步骤S12中，将所述请求报文转发到所述第二PE设备。
在本公开实施例中，客户端与第一PE设备和第二PE设备连接，是指客户端通过CE设备与第一PE设备和第二PE设备连接，CE设备双归接入第一PE设备和第二PE设备。
在一些实施例中，客户端接入的PE设备为MC-LAG设备。在一 些实施例中，第一PE设备从MC-LAG端口接收客户端发送的请求报文。
在本公开实施例中，生成客户端的临时表项时，若第一PE设备中存在该客户端对应的表项时，则更新该表项，生成该客户端对应的临时表项；若第一PE设备中不存在该客户端对应的表项时，则新建该客户端对应的临时表项。
在一些实施例中，请求报文为DHCP请求报文。
在本公开实施例中，第一PE设备在接收到客户端发送的请求报文、并生成客户端对应的临时表项之后，将请求报文转发到第二PE设备，使得客户端连接的各个PE设备中都能生成该客户端对应的临时表项，当任意一个PE设备接收到服务端应答该请求报文的应答报文时，都能生成正式表项，从而确保客户端能够正常申请到IP地址。
需要说明的是，在本公开实施例中，第一PE设备、第二PE设备是为了区分不同的PE设备；不同的PE设备是等价的，客户端发送的请求报文可以随机到达第一PE设备或第二PE设备，服务端发送的应答报文也可以随机到达第一PE设备或第二PE设备。在图1中，PE1、PE2也是为了区分不同的PE设备。为了方便说明，在下文中以第一PE设备对应图1中的PE1，第二PE设备对应图1中的PE2为例进行说明。
如图1所示，客户端通过CE设备与PE设备PE1、PE2连接，PE1、PE2为MC-LAG设备，且SG为负荷分担模式，客户端发送的请求报文可能随机到达PE1、PE2的任意一者，服务端应答该请求报文的应答报文也可能随机到达PE1、PE2的任意一者。PE1接收到客户端发送的请求报文，生成客户端对应的临时表项，然后将请求报文转发到PE2；PE2接收到请求报文后也生成客户端对应的临时表项。即PE1、PE2中都存在客户端对应的临时表项，当服务端发送的应答报文随机到达PE1或PE2时，PE1或PE2中都能查询到客户端对应的临时表项，从而生成正式表项，使得客户端能够正常申请到IP地址。
本公开实施例对于第一PE设备如何将请求报文转发到第二PE设备不做特殊限定。在一些实施例中，第一PE设备通过发送第一交换报文，将请求报文转发到第二PE。在一些实施例中，第一PE设备 将请求报文，收包端口信息封装成类型长度值(Type Length Value，TLV)携带在第一交换报文中，通过第一PE设备与第二PE设备之间配置的二层或三层通道转发到第二PE设备。
在一些实施例中，参照图4，将所述请求报文转发到所述第二PE设备，包括如下步骤S121至S122。
在步骤S121中，判断接收所述请求报文的收包端口是否为MC-LAG端口。
在步骤S122中，当接收所述请求报文的收包端口为MC-LAG端口时，将所述请求报文转发到所述第二PE设备。
在一些实施例中，MC-LAG端口为负荷分担模式。
本公开实施例对于第一PE设备如何将请求报文转发到第二PE设备不做特殊限定。在一些实施例中，定义了用于第一PE设备与第二PE设备之间交换请求报文的第一交换报文，并在第一PE设备和第二PE设备之间部署了传输第一交换报文的报文交换通道，第一PE设备通过报文交换通道发送第一交换报文将请求报文发送到第二PE设备。
相应地，在一些实施例中，将所述请求报文转发到第二PE设备，包括：生成第一交换报文，所述第一交换报文携带所述请求报文和所述第一PE设备中的MC-LAG端口信息；通过所述第一PE设备与所述第二PE设备之间配置的报文交换通道，将所述第一交换报文发送到所述第二PE设备。
在一些实施例中，在将请求报文转发到第二PE设备时，还包括：在第一PE设备和第二PE设备之间配置报文交换通道。
本公开实施例对如何在第一PE设备和第二PE设备之间配置报文交换通道不做特殊限定。在一些实施例中，在第一PE设备和第二PE设备之间配置二层通道，作为报文交换通道。在一些实施例中，在第一PE设备和第二PE设备之间配置三层通道，作为报文交换通道。
本公开实施例对于第一交换报文也不做特殊限定。
在一些实施例中，第一PE设备将请求报文和第一PE的收包端口信息封装成TLV携带在第一交换报文中，从而生成第一交换报文。
相应地，在一些实施例中，生成第一交换报文，包括：将所述请求报文和所述第一PE设备中的MAC-LAG端口信息组成所述第一交换报文的TLV，得到所述第一交换报文。
在一些实施例中，将所述请求报文转发到第二PE设备，包括：排除所述第一PE设备的网络侧隧道端口，转发所述请求报文。
在本公开实施例中，第二PE设备接收到第一PE设备转发的请求报文生成客户端对应的临时表项后，由第二PE设备将请求报文发送到网络侧的服务端。在第一PE设备中，排除第一PE设备的网络侧端口转发请求报文，能够避免第一PE设备向网络侧的服务端发送请求报文，导致服务端收到请求报文后，服务端发送的应答报文在第二PE设备中生成临时表项之前，到达第二PE设备。也就是说，第一PE设备排除第一PE设备的网络侧端口转发请求报文，并由第二PE设备在生成临时表项之后，将请求报文发送到服务端，能够确保服务端发送的应答报文到达客户端连接的PE设备时，PE设备中已经生成了该客户端的临时表项，从而确保客户端能够正常申请到IP地址。
在一些实施例中，参照图4，所述数据传输方法还包括如下步骤S131至S133。
在步骤S131中，接收服务端应答所述请求报文的应答报文。
在步骤S132中，根据所述应答报文和所述临时表项，生成正式表项。
在步骤S133中，将所述正式表项同步到所述第二PE设备。
在本公开实施例中，对于第一PE设备来说，通过步骤S131接收到的应答报文可以是服务端直接发送到第一PE设备的应答报文，也可以是服务端发送到第二PE设备并由第二PE设备转发到第一PE设备的应答报文。本公开实施例对此不做特殊限定。
在本公开实施例中，在执行了步骤S11和S12的基础上，第一PE设备中能够查询到客户端对应的临时表项，故而能够生成正式表项。在生成正式表项之后，第一PE设备将正式表项同步到第二PE设备，能够确保客户端接入的各个PE设备中的正式表项保持一致，从而使得客户端能够正确使用申请到的IP地址。
例如，如图1所示，PE1接收到服务端应答请求报文的应答报文，在本地查询到客户端对应的临时表项，生成正式表项，然后将正式表项同步到PE2，使得PE1和PE2中的正式表项保持一致，从而使得客户端能够正常申请到IP地址，并能够正确使用申请到的IP地址。
本公开实施例对于第一PE设备如何将正式表项同步到第二PE设备不做特殊限定。在一些实施例中，定义了用于同步正式表项的同步报文，并在第一PE设备和第二PE设备之间部署了传输同步报文的同步通道，第一PE设备通过同步通道发送同步报文将正式表项同步到第二PE设备。
相应地，在一些实施例中，将所述正式表项同步到所述第二PE设备，包括：生成同步报文，所述同步报文携带所述正式表项的信息；通过所述第一PE设备与所述第二PE设备之间配置的同步通道，将所述同步报文发送到所述第二PE设备。
在一些实施例中，在将正式表项同步到第二PE设备时，还包括：在第一PE和第二PE之间配置同步通道。
本公开实施例对如何在第一PE和第二PE之间配置同步通道不做特殊限定。在一些实施例中，在第一PE和第二PE之间配置二层通道，作为同步通道。在一些实施例中，在第一PE和第二PE之间配置三层通道，作为同步通道。
本公开实施例对于同步报文也不做特殊限定。
在一些实施例中，第一PE设备将正式表项的信息封装成类型长度值(Type Length Value，TLV)携带在同步报文中，从而生成同步报文。
相应地，在一些实施例中，生成同步报文，包括：将所述正式表项的信息封装成所述同步报文的类型长度值TLV，得到所述同步报文。
在一些实施例中，接收服务端应答所述请求报文的应答报文，包括：接收服务端发送的所述应答报文；或接收所述第二PE设备转发的所述应答报文。
如图1所示，服务端应答客户端发送的请求报文发送的应答报 文，可能随机到达PE1或PE2。服务端发送的应答报文到达PE1时，则表示第一PE设备接收服务端发送的应答报文；服务端发送的应答报文到达PE2时，若PE2中未查询到客户端对应的临时表项时，PE2则将应答报文转发到PE1，则表示第一PE设备接收第二PE设备转发的应答报文。
在一些实施例中，当接收第二PE设备转发的应答报文时，第一PE设备在根据所述应答报文和所述临时表项，生成正式表项之后，所述数据传输方法还包括：排除所述第一PE设备与所述第二PE设备之间的隧道端口，转发所述应答报文。
在本公开实施例中，当应答报文是第二PE设备转发的应答报文时，第一PE设备在生成正式表项之后，排除第一PE设备与第二PE设备之间的隧道端口，进一步转发应答报文，能够避免应答报文再重新发回到第二PE设备。
在一些实施例中，排除第一PE设备与第二PE设备之间的隧道端口，转发应答报文，将应答报文转发到客户端。
在一些实施例中，参照图4，所述数据传输方法还包括如下步骤S14。
在步骤S14中，接收从所述第二PE设备处同步的正式表项，在所述第一PE设备中生成正式表项。
在本公开实施例中，在执行了步骤S11和S12的基础上，第二PE设备中能够查询到客户端对应的临时表项，故而能够生成正式表项。在生成正式表项之后，第二PE设备将正式表项同步到第一PE设备，能够确保客户端接入的各个PE设备中的正式表项保持一致，从而使得客户端能够正确使用申请到的IP地址。
如图1所示，PE1接收到服务端应答客户端发送的请求报文的应答报文，在本地未查询到该客户端对应的临时表项，则将接收到的应答报文转发到PE2；PE2在本地查询到该客户端对应的临时表项，生成正式表项，然后将正式表项同步到PE1；PE1接收到从PE2处同步的正式表项生成正式表项，使得PE1和PE2中的正式表项保持一致，从而使得客户端能够正常申请到IP地址，并能够正确使用申请到的 IP地址。
如图1所示，PE2接收到服务端应答客户端发送的请求报文的应答报文，在本地查询到该客户端对应的临时表项，生成正式表项，然后将正式表项同步到PE1；PE1接收到从PE2处同步的正式表项生成正式表项，使得PE1和PE2中的正式表项保持一致，从而使得客户端能够正常申请到IP地址，并能够正确使用申请到的IP地址。
本公开实施例对于第二PE设备如何将正式表项同步到第一PE设备不做特殊限定。在一些实施例中，第二PE设备通过发送同步报文，将正式表项同步到第一PE设备。在一些实施例中，第二PE设备将正式表项封装成TLV携带在同步报文中，通过PE设备之间配置的二层或三层通道转发到第一PE设备。相应地，第一PE设备解析同步报文获取正式表项。
相应地，在一些实施例中，接收从所述第二PE设备处同步的正式表项，在所述第一PE设备中生成正式表项，包括：接收所述第二PE设备发送的同步报文，所述第二PE设备发送的同步报文携带正式表项的信息，所述正式表项的信息包括所述正式表项和所述第二PE设备中的跨设备链路聚合组MC-LAG端口信息；将所述第二PE设备中的MC-LAG端口替换为所述第一PE设备中对应的MC-LAG端口，在所述第一PE设备中生成正式表项。
在一些实施例中，参照图4，所述数据传输方法还包括如下步骤S151至S152。
在步骤S151中，接收服务端应答所述请求报文的应答报文。
在步骤S152中，在无法生成正式表项的情况下，将所述应答报文转发到所述第二PE设备。
在本公开实施例中，对于第一PE设备来说，通过步骤S151接收到的应答报文可以是服务端直接发送到第一PE设备的应答报文，也可以是服务端发送到第二PE设备并由第二PE设备转发到第一PE设备的应答报文。本公开实施例对此不做特殊限定。
在本公开实施例中，第一PE设备在无法生成正式表项的情况下，将应答报文转发到第二PE设备，旨在将应答报文发送到存在客户端 对应的临时表项的PE设备，从而确保能够正常生成正式表项。
如图1所示，PE1接收到服务端应答客户端发送的请求报文的应答报文，在本地未查询到该客户端对应的临时表项，则将接收到的应答报文转发到PE2；PE2在本地查询到该客户端对应的临时表项，生成正式表项，从而确保客户端能够正常申请到IP地址。
需要说明的是，在执行步骤S151至S 152将应答报文转发到第二PE设备之后，第二PE设备生成正式表项后，也会将正式表项同步到第一PE设备，使得客户端连接的各个PE设备中的正式表项保持一致，从而确保客户端能够正确使用申请到的IP地址。
本公开实施例对于第一PE设备如何将应答报文转发到第二PE设备不做特殊限定。在一些实施例中，定义了用于第一PE设备与第二PE设备之间交换应答报文的第二交换报文，并在第一PE设备和第二PE设备之间部署了传输第二交换报文的报文交换通道，第一PE设备通过报文交换通道发送第二交换报文将应答报文发送到第二PE设备。
相应地，在一些实施例中，将所述应答报文转发到所述第二PE设备，包括：生成第二交换报文，所述第二交换报文携带所述应答报文和所述第一PE设备中的MC-LAG端口信息；通过所述第一PE设备与所述第二PE设备之间配置的报文交换通道，将所述第二交换报文发送到所述第二PE设备。
在一些实施例中，在将应答报文转发到第二PE设备时，还包括：在第一PE设备和第二PE设备之间配置报文交换通道。
本公开实施例对如何在第一PE设备和第二PE设备之间配置报文交换通道不做特殊限定。在一些实施例中，在第一PE设备和第二PE设备之间配置二层通道，作为报文交换通道。在一些实施例中，在第一PE设备和第二PE设备之间配置三层通道，作为报文交换通道。
本公开实施例对于第二交换报文也不做特殊限定。
在一些实施例中，第一PE设备将应答报文和第一PE的收包端口信息封装成TLV携带在第二交换报文中，从而生成第二交换报文。
相应地，在一些实施例中，生成第二交换报文，包括：将所述 应答报文和所述第一PE设备中的MC-LAG端口信息封装成所述第二交换报文的TLV，得到所述第二交换报文。
第二方面，参照图5，本公开实施例提供一种数据传输方法，包括如下步骤S21至S22。
在步骤S21中，接收第一PE设备转发的请求报文，生成客户端对应的临时表项；所述客户端与所述第一PE设备和当前的第二PE设备连接。
在步骤S22中，将所述请求报文发送到服务端。
在本公开实施例中，第一PE设备在接收到客户端发送的请求报文，并生成客户端对应的临时表项之后，将请求报文转发到第二PE设备；第二PE设备接收到第一PE设备转发的请求报文之后，也生成该客户端对应的临时表项，从而使得客户端连接的各个PE设备中都能生成该客户端的临时表项，当任意一个PE设备接收到服务端应答该请求报文的应答报文时，都能生成正式表项，从而确保客户端能够正常申请到IP地址。
如图1所示，客户端通过CE设备与PE设备PE1、PE2连接，PE1、PE2为MC-LAG设备，且SG为负荷分担模式，客户端的请求报文可能随机到达PE1、PE2的任意一者，服务端的应答报文也可能随机到达PE1、PE2的任意一者。PE1接收到客户端发送的请求报文，生成客户端对应的临时表项，然后将请求报文转发到PE2；PE2接收到请求报文后也生成客户端对应的临时表项。即PE1、PE2中都存在客户端对应的临时表项，当服务端的应答报文随机到达PE1或PE2时，PE1或PE2中都能查询到客户端的临时表项，从而生成正式表项，使得客户端能够正常申请到IP地址。
本公开实施例对于第一PE设备如何将请求报文转发到第二PE设备不做特殊限定。在一些实施例中，第一PE设备通过发送第一交换报文，将请求报文转发到第二PE设备。在一些实施例中，第一PE设备将请求报文，收包端口信息封装成TLV携带在第一交换报文中，通过第一PE设备与第二PE设备之间配置的二层或三层通道转发到第二PE设备。相应地，第二PE设备通过解析第一交换报文获取请求报 文。
相应地，在一些实施例中，接收第一PE设备转发的请求报文，生成客户端对应的临时表项，包括：接收所述第一PE设备发送的第一交换报文，所述第一交换报文携带所述请求报文和所述第一PE设备中的MC-LAG端口信息；将所述第一PE设备中的MC-LAG端口替换为所述第二PE设备中对应的MC-LAG端口，生成所述临时表项。
在一些实施例中，将所述请求报文发送到服务端，包括：排除所述第二PE设备与所述第一PE设备之间的隧道端口，转发所述请求报文。
在本公开实施例中，在第二PE设备中，排除第二PE设备与第一PE设备之间的端口，将请求报文发送到服务端，能够避免请求报文再重新发回到第一PE设备。
在一些实施例中，参照图6，所述数据传输方法还包括如下步骤S231至S233。
在步骤S231中，接收服务端应答所述请求报文的应答报文。
在步骤S232中，根据所述应答报文和所述临时表项，生成正式表项。
在步骤S233中，将所述正式表项同步到所述第一PE设备。
在本公开实施例中，在执行了步骤S21和S22的基础上，第二PE设备中能够查询到客户端对应的临时表项，故而能够生成正式表项。在生成正式表项之后，第二PE设备将正式表项同步到第一PE设备，能够确保客户端接入的各个PE设备中的正式表项保持一致，从而使得客户端能够正确使用申请到的IP地址。
本公开实施例对于第二PE设备如何将正式表项同步到第一PE设备不做特殊限定。在一些实施例中，定义了用于同步正式表项的同步报文，并在第二PE设备和第一PE设备之间部署了传输同步报文的同步通道，第二PE设备通过同步通道发送同步报文将正式表项同步到第一PE设备。
相应地，在一些实施例中，将所述正式表项同步到所述第一PE设备，包括：生成同步报文，所述同步报文携带所述正式表项的信息； 通过所述第二PE设备与所述第一PE之间配置的同步通道，将所述同步报文发送到所述第一PE设备。
在一些实施例中，在将正式表项同步到第一PE设备时，还包括：在第二PE和第一PE之间配置同步通道。
本公开实施例对如何在第二PE和第一PE之间配置同步通道不做特殊限定。在一些实施例中，在第二PE和第一PE之间配置二层通道，作为同步通道。在一些实施例中，在第二PE和第一PE之间配置三层通道，作为同步通道。
本公开实施例对于同步报文也不做特殊限定。
在一些实施例中，第二PE设备将正式表项封装成类型长度值(Type Length Value，TLV)携带在同步报文中，从而生成同步报文。
相应地，在一些实施例中，生成同步报文，包括：将所述正式表项的信息封装成所述同步报文的TLV，得到所述同步报文。
在本公开实施例中，对于第二PE设备来说，通过步骤S231接收到的应答报文可以是服务端直接发送到第二PE设备的应答报文，也可以是服务端发送到第一PE设备并由第一PE设备转发到第二PE设备的应答报文。本公开实施例对此不做特殊限定。
相应地，在一些实施例中，接收服务端应答所述请求报文的应答报文，包括：接收服务端发送的所述应答报文；或接收所述第一PE设备转发的所述应答报文。
在一些实施例中，当接收第一PE设备转发的所述应答报文时，第二PE设备在根据所述应答报文和所述临时表项，生成正式表项之后，所述数据传输方法还包括：排除所述第二PE设备与所述第一PE设备之间的隧道端口，转发所述应答报文。
在本公开实施例中，当应答报文是第一PE设备转发的应答报文时，第二PE设备在生成正式表项之后，排除第二PE设备与第一PE设备之间的端口，进一步转发应答报文，能够避免应答报文再重新发回到第一PE设备。
在一些实施例中，排除第二PE设备与第一PE设备之间的端口，转发应答报文，将应答报文转发到客户端。
在一些实施例中，参照图6，所述数据传输方法还包括如下步骤S24。
在步骤S24中，接收从所述第一PE设备处同步的正式表项，在所述第二PE设备中生成正式表项。
在本公开实施例中，在执行了步骤S21和S22的基础上，第一PE设备中能够查询到客户端对应的临时表项，故而能够生成正式表项。在生成正式表项之后，第一PE设备将正式表项同步到第二PE设备，能够确保客户端接入的多个PE设备中的正式表项保持一致，从而使得客户端能够正确使用申请到的IP地址。
本公开实施例对于第一PE设备如何将正式表项同步到第一PE设备不做特殊限定。在一些实施例中，第一PE设备通过发送同步报文，将正式表项同步到第二PE设备。在一些实施例中，第一PE设备将正式表项封装成TLV携带在同步报文中，通过PE设备之间配置的二层或三层通道转发到第二PE设备。相应地，第二PE设备解析同步报文获取正式表项。
相应地，在一些实施例中，接收从所述第一PE设备处同步的正式表项，在所述第一PE设备中生成正式表项，包括：接收所述第一PE设备发送的同步报文，所述第一PE设备发送的同步报文携带正式表项的信息，所述正式表项的信息包括所述正式表项和所述第一PE设备中MC-LAG端口信息；将所述第一PE设备中的MC-LAG端口替换为所述第二PE设备中对应的MC-LAG端口，在所述第二PE设备中生成正式表项。
在一些实施例中，参照图6，所述数据传输方法还包括如下步骤S251至S252。
在步骤S251中，接收服务端应答所述请求报文的应答报文。
在步骤S252中，在无法生成正式表项的情况下，将所述应答报文转发到所述第一PE设备。
在本公开实施例中，第二PE设备在无法生成正式表项的情况下，将应答报文转发到第一PE设备，旨在将应答报文发送到存在该客户端对应的临时表项的PE设备，从而确保能够正常生成正式表项。
需要说明的是，在执行步骤S251至S252将应答报文转发到第一PE设备之后，第一PE设备生成正式表项后，也会将正式表项同步到第二PE设备，使得客户端连接的各个PE设备中的正式表项保持一致，从而确保客户端能够正确使用申请到的IP地址。
本公开实施例对于第二PE设备如何将应答报文转发到第一PE设备不做特殊限定。在一些实施例中，定义了用于第二PE设备与第一PE设备之间交换应答报文的第三交换报文，并在第二PE设备和第一PE设备之间部署了传输第三交换报文的报文交换通道，第二PE设备通过报文交换通道发送第三交换报文将应答报文发送到第一PE设备。
相应地，在一些实施例中，将所述应答报文转发到所述第一PE设备，包括：生成第三交换报文，所述第三交换报文携带所述应答报文和所述第二PE中的MC-LAG端口信息；通过所述第二PE设备与所述第一PE设备之间配置的报文交换通道，将所述第三交换报文发送到所述第一PE设备。在一些实施例中，在将应答报文转发到第一PE设备时，还包括：在第二PE设备和第一PE设备之间配置报文交换通道。
本公开实施例对如何在第二PE设备和第一PE设备之间配置报文交换通道不做特殊限定。在一些实施例中，在第二PE设备和第一PE设备之间配置二层通道，作为报文交换通道。在一些实施例中，在第二PE设备和第一PE设备之间配置三层通道，作为报文交换通道。
本公开实施例对于第三交换报文也不做特殊限定。
在一些实施例中，第二PE设备将应答报文和第二PE的收包端口信息封装成TLV携带在第三交换报文中，从而生成第三交换报文。
相应地，在一些实施例中，生成第三交换报文，包括：将所述应答报文和所述第二PE设备中的MC-LAG端口信息封装成所述第三交换报文的TLV，得到所述第三交换报文。
第三方面，参照图7，本公开实施例提供一种数据传输方法，包括如下步骤S31至S32。
在步骤S31中，接收服务端应答客户端发送的请求报文的应答 报文；所述客户端与当前的第一PE设备和第二PE设备连接。
在步骤S32中，在无法生成正式表项的情况下，将所述应答报文转发到所述第二PE设备。
在本公开实施例中，第一PE设备在无法生成正式表项的情况下，将应答报文转发到第二PE设备，旨在将应答报文发送到存在该客户端对应的临时表项的PE设备，从而能够正常生成正式表项，进而确保客户端能够正常申请到IP地址。
如图1所示，PE1接收到服务端发送的应答报文，在本地未查询到客户端对应的临时表项，则将接收到的应答报文转发到PE2；PE2在本地查询到该客户端对应的临时表项，生成正式表项，从而确保客户端能够正常申请到IP地址。
本公开实施例对于第一PE设备如何将应答报文转发到第二PE设备不做特殊限定。在一些实施例中，定义了用于第一PE设备与第二PE设备之间交换应答报文的第二交换报文，并在第一PE设备和第二PE设备之间部署了传输第二交换报文的报文交换通道，第一PE设备通过报文交换通道发送第二交换报文将应答报文发送到第二PE设备。
相应地，在一些实施例中，将所述应答报文转发到所述第二PE设备，包括：生成第二交换报文，所述第二交换报文携带所述应答报文和所述第一PE设备中的MC-LAG端口信息；通过所述第一PE设备与所述第二PE设备之间配置的报文交换通道，将所述第二交换报文发送到所述第二PE设备。
在一些实施例中，在将应答报文转发到第二PE设备时，还包括：在第一PE设备和第二PE设备之间配置报文交换通道。
本公开实施例对如何在第一PE设备和第二PE设备之间配置报文交换通道不做特殊限定。在一些实施例中，在第一PE设备和第二PE设备之间配置二层通道，作为报文交换通道。在一些实施例中，在第一PE设备和第二PE设备之间配置三层通道，作为报文交换通道。
本公开实施例对于第二交换报文也不做特殊限定。
在一些实施例中，第一PE设备将应答报文和第一PE设备的收 包端口信息封装成TLV携带在第二交换报文中，从而生成第二交换报文。
相应地，在一些实施例中，生成第二交换报文，包括：将所述应答报文和所述第一PE设备中的MC-LAG端口信息封装成所述第二交换报文的TLV，得到所述第二交换报文。
在一些实施例中，参照图8，所述数据传输方法还包括如下步骤S33。
在步骤S33中，接收从所述第二PE设备处同步的正式表项，在所述第一PE设备中生成正式表项。
在本公开实施例中，在执行步骤S31至S32将应答报文转发到第二PE设备之后，第二PE设备生成正式表项后，也会将正式表项同步到第一PE设备，使得客户端连接的各个PE设备中的正式表项保持一致，从而确保客户端能够正确使用申请到的IP地址。
本公开实施例对于第二PE设备如何将正式表项同步到第一PE设备不做特殊限定。在一些实施例中，第二PE设备通过发送同步报文，将正式表项同步到第一PE。在一些实施例中，第二PE设备将正式表项封装成TLV携带在同步报文中，通过PE设备之间配置的二层或三层通道转发到第一PE设备。相应地，第一PE设备解析同步报文获取正式表项。
相应地，在一些实施例中，接收从所述第二PE设备处同步的正式表项，在所述第一PE设备中生成正式表项，包括：接收所述第二PE设备发送的同步报文，所述第二PE设备发送的同步报文携带正式表项的信息，所述正式表项的信息包括所述正式表项和所述第二PE设备中的MC-LAG端口信息；将所述第二PE设备中的MC-LAG端口替换为所述第一PE设备中对应的MC-LAG端口，在所述第一PE设备中生成正式表项。
在一些实施例中，参照图8，所述数据传输方法还包括如下步骤S341至S342。
在步骤S341中，在能够生成正式表项的情况下，生成所述正式表项。
在步骤S342中，将所述正式表项同步到所述第二PE设备。
在本公开实施例中，若第一PE设备中查询到客户端对应的临时表项，则生成正式表项，然后将正式表项同步到第二PE设备，使得客户端连接的各个PE设备中的正式表项保持一致，从而确保客户端能够正确使用申请到的IP地址。
本公开实施例对于第一PE设备如何将正式表项同步到第二PE设备不做特殊限定。在一些实施例中，定义了用于同步正式表项的同步报文，并在第一PE设备和第二PE设备之间部署了传输同步报文的同步通道，第一PE设备通过同步通道发送同步报文将正式表项同步到第二PE设备。
相应地，在一些实施例中，将所述正式表项同步到所述第二PE设备，包括：生成同步报文，所述同步报文携带正式表项的信息；通过所述第一PE设备与所述第二PE设备之间配置的同步通道，将所述同步报文发送到所述第二PE设备。
在一些实施例中，在将正式表项同步到第二PE设备时，还包括：在第一PE设备和第二PE之间配置同步通道。
本公开实施例对如何在第一PE设备和第二PE设备之间配置同步通道不做特殊限定。在一些实施例中，在第一PE设备和第二PE设备之间配置二层通道，作为同步通道。在一些实施例中，在第一PE设备和第二PE设备之间配置三层通道，作为同步通道。
本公开实施例对于同步报文也不做特殊限定。
在一些实施例中，第一PE设备将正式表项封装成类型长度值(Type Length Value，TLV)携带在同步报文中，从而生成同步报文。
相应地，在一些实施例中，生成同步报文，包括：将所述正式表项的信息封装成所述同步报文的TLV，得到所述同步报文。
在一些实施例中，参照图8，所述数据传输方法还包括如下步骤S351至S353。
在步骤S351中，接收所述第二PE设备转发的应答报文。
在步骤S352中，在能够生成正式表项的情况下，根据所述应答报文生成正式表项，排除所述第一PE设备与所述第二PE设备之间的 隧道端口，转发所述应答报文。
在步骤S353中，在不能生成正式表项的情况下，丢弃所述应答报文。
在一些实施例中，参照图8，所述数据传输方法还包括如下步骤S361至S362。
在步骤S361中，接收所述客户端发送的请求报文，生成所述客户端对应的临时表项。
在步骤S362中，将所述请求报文转发到所述第二PE设备。
在本公开实施例中，第一PE设备在接收到客户端发送的请求报文，并生成客户端对应的临时表项之后，将请求报文转发到第二PE设备，使得客户端连接的各个PE设备中都能生成该客户端对应的临时表项，当任意一个PE设备接收到服务端应答该请求报文发送的应答报文时，结合步骤S31至S32，能够确保生成正式表项，从而确保客户端能够正常申请到IP地址。
本公开实施例对于第一PE设备如何将请求报文转发到第二PE设备不做特殊限定。在一些实施例中，定义了用于第一PE设备与第二PE设备之间交换请求报文的第一交换报文，并在第一PE设备和第二PE设备之间部署了传输第一交换报文的报文交换通道，第一PE设备通过报文交换通道发送第一交换报文将请求报文发送到第二PE设备。
相应地，在一些实施例中，将所述请求报文转发到所述第二PE设备，包括：生成第一交换报文，所述第一交换报文携带所述请求报文和所述第一PE设备中的MC-LAG端口信息；通过所述第一PE设备与所述第二PE设备之间配置的报文交换通道，将所述第一交换报文发送到所述第二PE设备。
在一些实施例中，在将请求报文转发到第二PE设备时，还包括：在第一PE和第二PE之间配置报文交换通道。
本公开实施例对如何在第一PE和第二PE之间配置报文交换通道不做特殊限定。在一些实施例中，在第一PE和第二PE之间配置二层通道，作为报文交换通道。在一些实施例中，在第一PE和第二PE 之间配置三层通道，作为报文交换通道。
本公开实施例对于第一交换报文也不做特殊限定。
在一些实施例中，第一PE设备将请求报文和第一PE的收包端口信息封装成TLV携带在第一交换报文中，从而生成第一交换报文。
相应地，在一些实施例中，生成第一交换报文，包括：将所述请求报文和所述第一PE设备中的MC-LAG端口信息组成所述第一交换报文的TLV，得到所述第一交换报文。
在一些实施例中，参照图8，所述数据传输方法还包括如下步骤S371至S372。
在步骤S371中，接收所述第二PE设备转发的请求报文，生成所述客户端对应的临时表项。
在步骤S372中，将所述请求报文发送到服务端。
在本公开实施例中，第二PE设备在接收到客户端发送的请求报文、并生成客户端对应的临时表项之后，将请求报文转发到第一PE设备；第一PE设备接收到第二PE设备转发的请求报文之后，也生成该客户端对应的临时表项，从而使得客户端连接的各个PE设备中都能生成该客户端对应的临时表项，当任意一个PE设备接收到服务端响应于该请求报文发送的应答报文时，结合步骤S31至S32，能够确保生成正式表项，从而确保客户端能够正常申请到IP地址。
第四方面，参照图9，本公开实施例提供一种PE设备，其包括：一个或多个处理器101；存储器102，其上存储有一个或多个计算机程序，一个或多个计算机程序被一个或多个处理器执行，使得一个或多个处理器实现上述任意一项的数据传输方法。一个或多个I/O接口103，连接在处理器与存储器之间，配置为实现处理器与存储器的信息交互。
处理器101为具有数据处理能力的器件，其包括但不限于中央处理器(CPU)等；存储器102为具有数据存储能力的器件，其包括但不限于随机存取存储器(RAM，更具体如SDRAM、DDR等)、只读存储器(ROM)、带电可擦可编程只读存储器(EEPROM)、闪存(FLASH)；I/O接口(读写接口)103连接在处理器101与存储器102间，能实 现处理器101与存储器102的信息交互，其包括但不限于数据总线(Bus)等。
在一些实施例中，处理器101、存储器102和I/O接口103通过总线104相互连接，进而与计算设备的其它组件连接。
第五方面，参照图10，本公开实施例提供一种计算机可读存储介质，其上存储有计算机程序，该计算机程序被处理器执行以实现上述任意一项的数据传输方法。
为了使本领域技术人员能够更清楚地理解本公开实施例提供的技术方案，下面通过具体的实施例，对本公开实施例提供的技术方案进行详细说明。
实施例一
在本实施例中，基于图1所示的网络架构，生成绑定表的正式表项包括以下步骤401至405。
在步骤401中，双归PE设备之一PE1从MC-LAG端口收到客户端的DHCP请求报文，通过报文合法性检查后，查询本地是否已有对应客户端MAC地址的表项，如果有则更新表项，没有则建立包含客户端MAC地址、收包端口、所属EVPN等信息的临时表项，然后封装报文，以发消息的方式，将报文交换到对端双归PE设备PE2；同时还在PE1上排除网络侧隧道端口正常转发报文。需要说明的是，排除网络侧隧道端口转发的目的是，避免网络侧的服务器收到请求报文后立刻发送单播应答报文，且应答报文通过负荷分担的方式到达PE2，而此时PE1通过交换模块处理的请求报文可能尚未到达PE2，导致应答报文因查不到对应客户端MAC表项从而处理失败被丢弃。PE1如果是从非MC-LAG口收到的请求报文，则正常处理转发，既不会同步到PE2，也不需要排除网络侧隧道口转发。
在步骤402中，PE2收到请求报文后，将收包端口替换为本设备MC-LAG端口后正常处理，建立或更新临时表项后进行转发；转发时需要排除双归设备间的隧道。需要说明的是，转发排除双归PE设备间的隧道的原因是，该报文是从PE1发送过来的，不应该再转发回PE1。
在步骤403中，双归PE设备之一PE1从MC-LAG端口收到服务端的DHCP应答报文，如果PE1上通过对应客户端MAC地址未查询到临时表项，应答报文无法正常处理，则封装报文，以发消息的方式，将应答报文交换到对端PE2处理，同时本地将应答报文丢弃不再转发；如果PE1上查询到临时表项，则应答报文正常处理，临时表项绑定IP地址及更新租期转换为正式表项，同时应答报文在本地正常转发。PE1如果是从非MC-LAG口收到的应答报文，则正常处理转发，如查询不到表项，不需要同步到PE2，本地丢弃处理即可。
在步骤404中，PE2收到应答报文后将收包端口替换为本设备MC-LAG端口后正常处理；转发时排除双归设备间的隧道。
在步骤405中，MC-LAG端口的正式表项以发消息的方式，同步到对端双归PE设备。
实施例二
在本实施例中，基于图1所示的网络架构，对请求报文的处理包括以下步骤501至505。
在步骤501中，PE1接收到请求报文，在本地处理，生成或更新临时表项。
在步骤502中，判断收包端口是否为MC-LAG端口，若是，则执行步骤504，否则执行步骤503。
在步骤503中，请求报文在本地正常转发。
在步骤504中，将请求报文交换到PE2；在将请求报文交换到PE2的同时，在本地排除网络侧隧道端口，进行转发。
在步骤505中，PE2收到交换过来的请求报文，将收包端口转为本地MC-LAG端口继续处理。
PE2收到交换过来的请求报文，将收包端口转为本地MC-LAG端口继续处理，进一步包括如下步骤5051至5053。
在步骤5051中，将请求报文的收包端口替换为本地MC-LAG端口。
在步骤5052中，生成或者更新本地客户端MAC地址对应的临时表项。
在步骤5053中，排除双归PE设备间的隧道后，转发报文。
实施例三
在本实施例中，基于图1所示的网络架构，对应答报文的处理包括以下步骤601至608。
在步骤601中，PE1或PE2接收到应答报文在本地处理，判断收包端口是否配置为信任口，若是，则执行步骤603，否则执行步骤602。
在步骤602中，丢弃应答报文，处理结束。
在步骤603中，查询客户端MAC地址对应表项是否存在，若是，则执行步骤604，否则执行步骤605。
在步骤604中，报文正常处理转发。
在步骤605中，进一步判断收包端口是否为MC-LAG端口，若是，则执行步骤607，否则执行步骤606。
在步骤606中，丢弃应答报文，处理结束。
在步骤607中，将应答报文通过报文交换模块交换到对端PE设备，本地丢弃处理。
在步骤608中，PE1或PE2收到交换过来的应答报文，将收包端口转为本地MC-LAG端口继续处理。
步骤604中，报文正常处理转发，进一步包括如下步骤6041至6042。
在步骤6041中，绑定IP到表项，同时更新表项租期。
在步骤6042中，将应答报文正常转发。
步骤608中，PE1或PE2收到交换的应答报文，将收包端口转为本地MC-LAG端口继续处理，进一步包括如下步骤6081至6085。
在步骤6081中，将应答报文的收包端口替换为本地MC-LAG口。
在步骤6082中，查询客户端MAC地址对应的表项是否存在，若是，则执行步骤6084，否则执行步骤6083。
在步骤6083中，丢弃应答报文，处理结束。
在步骤6084中，绑定IP到表项，同时更新表项租期。
在步骤6085中，排除双归PE设备间的隧道后，转发报文。
实施例四
本实施例中绑定表生成装置如图11所示。绑定表生成装置包括：报文处理模块，配置为对接收到的协议报文进行处理，如果是交换报文，则替换为本设备对应的MC-LAG端口进行处理。如果是请求报文，则生成临时表项，或续租更新正式表项，如果是应答报文，则根据临时表项生成正式表项，或直接更新正式表项。
报文交换模块，配置为交换协议报文，将从MC-LAG端口收到的协议报文以及收包端口等信息封装成TLV放在在消息中，通过在两台PE设备间配置的二层或三层通道，转发到对端双归PE设备DHCP Snooping报文交换模块。报文交换模块收到消息进行解包，传递给报文处理模块。
信息同步模块，配置为将MC-LAG端口的正式表项信息，封装成消息中的TLV，通过在两台PE设备间配置的二层或三层通道，转发到对端双归PE设备DHCP Snooping信息同步模块。信息同步模块收到消息进行解包，生成用户绑定表项，并将用户端口替换为本设备对应的MC-LAG端口。
通过报文处理模块和报文交换模块，双归PE设备都能从MC-LAG端口收到相同的请求报文，对于不能正常处理的来自MC-LAG端口的应答报文能交换到对端设备进行处理，保证了双归PE设备上绑定表项的正确生成，通过信息同步模块同步MC-LAG端口对应正式表项，保证了双归PE设备的MC-LAG表项的一致性。
如图12所示，本实施例还提供一种绑定表生成系统，包括：设备A，包括组件报文处理模块、报文交换模块以及信息同步模块，配置为处理并交换协议报文，生成正式表项并同步该表项。设备B，包括组件报文处理模块、报文交换模块以及信息同步模块，配置为处理并交换协议报文，生成正式表项并同步该表项。
两台设备通过报文交换模块和报文处理模块，互相交换报文，从而使MC-LAG端口接收处理相同的请求报文，对于不能正常处理的来自MC-LAG端口的应答报文能交换到对端设备处理，通过信息同步模块同步MC-LAG端口正式表项，保证了双归PE设备上MC-LAG表项的一致性，从双归接入的CE设备来看，双归PE设备被虚拟化为一台 设备，不受SG的负荷分担模式、ESI的冗余工作模式影响，确保了绑定表项的正确稳定生成。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器(如中央处理器、数字信号处理器或微处理器)执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其它数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其它存储器技术、CD-ROM、数字多功能盘(DVD)或其它光盘存储、磁盒、磁带、磁盘存储或其它磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其它的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其它传输机制之类的调制数据信号中的其它数据，并且可包括任何信息递送介质。
本文已经公开了示例实施例，并且虽然采用了具体术语，但它们仅用于并仅应当被解释为一般说明性含义，并且不用于限制的目的。在一些实例中，对本领域技术人员显而易见的是，除非另外明确指出，否则与特定实施例相结合描述的特征、特性和/或元素可单独使用，或可与结合其它实施例描述的特征、特性和/或元件组合使用。因此，本领域技术人员将理解，在不脱离由所附的权利要求阐明的本公开的范围的情况下，可进行各种形式和细节上的改变。

Claims (43)

  1. 一种数据传输方法，包括：
    接收客户端发送的请求报文，生成所述客户端对应的临时表项；其中，所述客户端与当前的第一运营商边缘PE设备和第二PE设备连接；以及
    将所述请求报文转发到所述第二PE设备。
  2. 根据权利要求1所述的数据传输方法，其中，所述数据传输方法还包括：
    接收服务端应答所述请求报文的应答报文；
    根据所述应答报文和所述临时表项，生成正式表项；以及
    将所述正式表项同步到所述第二PE设备。
  3. 根据权利要求2所述的数据传输方法，其中，将所述正式表项同步到所述第二PE设备，包括：
    生成同步报文，所述同步报文携带所述正式表项的信息；以及
    通过所述第一PE设备与所述第二PE设备之间配置的同步通道，将所述同步报文发送到所述第二PE设备。
  4. 根据权利要求3所述的数据传输方法，其中，生成同步报文，包括：
    将所述正式表项的信息封装成所述同步报文的类型长度值TLV，得到所述同步报文。
  5. 根据权利要求2所述的数据传输方法，其中，接收服务端应答所述请求报文的应答报文，包括：
    接收服务端发送的所述应答报文；或
    接收所述第二PE设备转发的所述应答报文。
  6. 根据权利要求5所述的数据传输方法，其中，所述数据传输方法还包括：
    当接收所述第二PE设备转发的所述应答报文时，所述第一PE设备在根据所述应答报文和所述临时表项，生成正式表项之后，排除所述第一PE设备与所述第二PE设备之间的隧道端口，转发所述应答报文。
  7. 根据权利要求1所述的数据传输方法，其中，所述数据传输方法还包括：
    接收从所述第二PE设备处同步的正式表项，在所述第一PE设备中生成正式表项。
  8. 根据权利要求7所述的数据传输方法，其中，接收从所述第二PE设备处同步的正式表项，在所述第一PE设备中生成正式表项，包括：
    接收所述第二PE设备发送的同步报文，所述第二PE设备发送的同步报文携带正式表项的信息，其中，所述正式表项的信息包括所述正式表项和所述第二PE设备中的跨设备链路聚合组MC-LAG端口信息；以及
    将所述第二PE设备中的MC-LAG端口替换为所述第一PE设备中对应的MC-LAG端口，在所述第一PE设备中生成正式表项。
  9. 根据权利要求1至8中任意一项所述的数据传输方法，其中，所述数据传输方法还包括：
    接收服务端应答所述请求报文的应答报文；以及
    在无法生成正式表项的情况下，将所述应答报文转发到所述第二PE设备。
  10. 根据权利要求9所述的数据传输方法，其中，将所述应答报文转发到所述第二PE设备，包括：
    生成第二交换报文，所述第二交换报文携带所述应答报文和所述第一PE设备中的MC-LAG端口信息；以及
    通过所述第一PE设备与所述第二PE设备之间配置的报文交换通道，将所述第二交换报文发送到所述第二PE设备。
  11. 根据权利要求10所述的数据传输方法，其中，生成第二交换报文，包括：
    将所述应答报文和所述第一PE中的MC-LAG端口信息封装成所述第二交换报文的TLV，得到所述第二交换报文。
  12. 根据权利要求1至8中任意一项所述的数据传输方法，其中，将所述请求报文转发到所述第二PE设备，包括：
    判断接收所述请求报文的收包端口是否为MC-LAG端口；以及
    当接收所述请求报文的收包端口为MC-LAG端口时，将所述请求报文转发到所述第二PE设备。
  13. 根据权利要求1至8中任意一项所述的数据传输方法，其中，将所述请求报文转发到所述第二PE设备，包括：
    生成第一交换报文，所述第一交换报文携带所述请求报文和所述第一PE设备中的MC-LAG端口信息；以及
    通过所述第一PE设备与所述第二PE设备之间配置的报文交换通道，将所述第一交换报文发送到所述第二PE设备。
  14. 根据权利要求13所述的数据传输方法，其中，生成第一交换报文，包括：
    将所述请求报文和所述第一PE设备中的MAC-LAG端口信息组成所述第一交换报文的TLV，得到所述第一交换报文。
  15. 根据权利要求1至8中任意一项所述的数据传输方法，其中，将所述请求报文转发到所述第二PE设备，包括：
    排除所述第一PE设备的网络侧隧道端口，转发所述请求报文。
  16. 一种数据传输方法，包括：
    接收第一PE设备转发的请求报文，生成客户端对应的临时表项；其中，所述客户端与所述第一PE设备和当前的第二PE设备连接；以及
    将所述请求报文发送到服务端。
  17. 根据权利要求16所述的数据传输方法，其中，所述数据传输方法还包括：
    接收服务端应答所述请求报文的应答报文；
    根据所述应答报文和所述临时表项，生成正式表项；以及
    将所述正式表项同步到所述第一PE设备。
  18. 根据权利要求17所述的数据传输方法，其中，将所述正式表项同步到所述第一PE设备，包括：
    生成同步报文，所述同步报文携带所述正式表项的信息；以及
    通过所述第二PE设备与所述第一PE之间配置的同步通道，将所述同步报文发送到所述第一PE设备。
  19. 根据权利要求18所述的数据传输方法，其中，生成同步报文，包括：
    将所述正式表项的信息封装成所述同步报文的TLV，得到所述同步报文。
  20. 根据权利要求17所述的数据传输方法，其中，接收服务端应答所述请求报文的应答报文，包括：
    接收服务端发送的所述应答报文；或
    接收所述第一PE设备转发的所述应答报文。
  21. 根据权利要求20所述的数据传输方法，其中，所述数据传输方法还包括：
    当接收所述第一PE设备转发的所述应答报文时，所述第二PE设备在根据所述应答报文和所述临时表项，生成正式表项之后，排除所述第二PE设备与所述第一PE设备之间的隧道端口，转发所述应答报文。
  22. 根据权利要求16所述的数据传输方法，其中，所述数据传输方法还包括：
    接收从所述第一PE设备处同步的正式表项，在所述第二PE设备中生成正式表项。
  23. 根据权利要求22所述的数据传输方法，其中，接收从所述第一PE设备处同步的正式表项，在所述第一PE设备中生成正式表项，包括：
    接收所述第一PE设备发送的同步报文，所述第一PE设备发送的同步报文携带正式表项的信息，其中，所述正式表项的信息包括所述正式表项和所述第一PE设备中MC-LAG端口信息；以及
    将所述第一PE设备中的MC-LAG端口替换为所述第二PE设备中对应的MC-LAG端口，在所述第二PE设备中生成正式表项。
  24. 根据权利要求16至23中任意一项所述的数据传输方法，其中，所述数据传输方法还包括：
    接收服务端应答所述请求报文的应答报文；以及
    在无法生成正式表项的情况下，将所述应答报文转发到所述第一PE设备。
  25. 根据权利要求24所述的数据传输方法，其中，将所述应答报文转发到所述第一PE设备，包括：
    生成第三交换报文，所述第三交换报文携带所述应答报文和所 述第二PE中的MC-LAG端口信息；以及
    通过所述第二PE设备与所述第一PE设备之间配置的报文交换通道，将所述第三交换报文发送到所述第一PE设备。
  26. 根据权利要求25所述的数据传输方法，其中，生成第三交换报文，包括：
    将所述应答报文和所述第二PE设备中的MC-LAG端口信息封装成所述第三交换报文的TLV，得到所述第三交换报文。
  27. 根据权利要求16至23中任意一项所述的数据传输方法，其中，接收第一PE设备转发的请求报文，生成客户端对应的临时表项，包括：
    接收所述第一PE设备发送的第一交换报文，所述第一交换报文携带所述请求报文和所述第一PE设备中的MC-LAG端口信息；
    将所述第一PE设备中的MC-LAG端口替换为所述第二PE设备中对应的MC-LAG端口，生成所述临时表项。
  28. 根据权利要求16至23中任意一项所述的数据传输方法，其中，将所述请求报文发送到服务端，包括：
    排除所述第二PE设备与所述第一PE设备之间的隧道端口，转发所述请求报文。
  29. 一种数据传输方法，包括：
    接收服务端应答客户端发送的请求报文的应答报文；其中，所述客户端与当前的第一PE设备和第二PE设备连接；以及
    在无法生成正式表项的情况下，将所述应答报文转发到所述第二PE设备。
  30. 根据权利要求29所述的数据传输方法，其中，所述数据传输方法还包括：
    接收从所述第二PE设备处同步的正式表项，在所述第一PE设备中生成正式表项。
  31. 根据权利要求30所述的数据传输方法，其中，接收从所述第二PE设备处同步的正式表项，在所述第一PE设备中生成正式表项，包括：
    接收所述第二PE设备发送的同步报文，所述第二PE设备发送的同步报文携带正式表项的信息，其中，所述正式表项的信息包括所述正式表项和所述第二PE设备中的MC-LAG端口信息；以及
    将所述第二PE设备中的MC-LAG端口替换为所述第一PE设备中对应的MC-LAG端口，在所述第一PE设备中生成正式表项。
  32. 根据权利要求29所述的数据传输方法，其中，将所述应答报文转发到所述第二PE设备，包括：
    生成第二交换报文，所述第二交换报文携带所述应答报文和所述第一PE设备中的MC-LAG端口信息；以及
    通过所述第一PE设备与所述第二PE设备之间配置的报文交换通道，将所述第二交换报文发送到所述第二PE设备。
  33. 根据权利要求32所述的数据传输方法，其中，生成第二交换报文，包括：
    将所述应答报文和所述第一PE中的MC-LAG端口信息封装成所述第二交换报文的TLV，得到所述第二交换报文。
  34. 根据权利要求29至33中任意一项所述的数据传输方法，其中，所述数据传输方法还包括：
    在能够生成正式表项的情况下，生成所述正式表项；以及
    将所述正式表项同步到所述第二PE设备。
  35. 根据权利要求34所述的数据传输方法，其中，将所述正式 表项同步到所述第二PE设备，包括：
    生成同步报文，所述同步报文携带正式表项的信息；以及
    通过所述第一PE设备与所述第二PE设备之间配置的同步通道，将所述同步报文发送到所述第二PE设备。
  36. 根据权利要求35所述的数据传输方法，其中，生成同步报文，包括：
    将所述正式表项的信息封装成所述同步报文的TLV，得到所述同步报文。
  37. 根据权利要求29至33中任意一项所述的数据传输方法，其中，所述数据传输方法还包括：
    接收所述第二PE设备转发的应答报文；
    在能够生成正式表项的情况下，根据所述应答报文生成正式表项，排除所述第一PE设备与所述第二PE设备之间的隧道端口，转发所述应答报文；以及
    在不能生成正式表项的情况下，丢弃所述应答报文。
  38. 根据权利要求29至33中任意一项所述的数据传输方法，其中，所述数据传输方法还包括：
    接收所述客户端发送的请求报文，生成所述客户端对应的临时表项；以及
    将所述请求报文转发到所述第二PE设备。
  39. 根据权利要求38所述的数据传输方法，其中，将所述请求报文转发到所述第二PE设备，包括：
    生成第一交换报文，所述第一交换报文携带所述请求报文和所述第一PE设备中的MC-LAG端口信息；以及
    通过所述第一PE设备与所述第二PE设备之间配置的报文交换通道，将所述第一交换报文发送到所述第二PE设备。
  40. 根据权利要求39所述的数据传输方法，其中，生成第一交换报文，包括：
    将所述请求报文和所述第一PE设备中的MC-LAG端口信息组成所述第一交换报文的TLV，得到所述第一交换报文。
  41. 根据权利要求29至33中任意一项所述的数据传输方法，其中，所述数据传输方法还包括：
    接收所述第二PE设备转发的请求报文，生成所述客户端对应的临时表项；以及
    将所述请求报文发送到服务端。
  42. 一种PE设备，包括：
    一个或多个处理器；
    存储器，其上存储有一个或多个计算机程序，所述一个或多个计算机程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现根据权利要求1至41中任意一项所述的数据传输方法。
  43. 一种计算机可读介质，其上存储有计算机程序，所述计算机程序被处理器执行，以实现根据权利要求1至41中任意一项所述的数据传输方法。
PCT/CN2023/093826 2022-07-19 2023-05-12 数据传输方法、运营商边缘设备、计算机可读存储介质 WO2024016799A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210847353.X 2022-07-19
CN202210847353.XA CN117459453A (zh) 2022-07-19 2022-07-19 数据传输方法、运营商边缘设备、计算机可读介质

Publications (1)

Publication Number Publication Date
WO2024016799A1 true WO2024016799A1 (zh) 2024-01-25

Family

ID=89584222

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/093826 WO2024016799A1 (zh) 2022-07-19 2023-05-12 数据传输方法、运营商边缘设备、计算机可读存储介质

Country Status (2)

Country Link
CN (1) CN117459453A (zh)
WO (1) WO2024016799A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102387225A (zh) * 2011-11-14 2012-03-21 中兴通讯股份有限公司 数据流发送方法及装置
CN108696416A (zh) * 2017-04-12 2018-10-23 中兴通讯股份有限公司 一种vxlan单归和双归混合接入方法、装置和pe设备
US20190089627A1 (en) * 2016-03-15 2019-03-21 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for supporting bidirectional forwarding (bfd) over multi-chassis link aggregation group (mc-lag) in internet protocol (ip) multiprotocol label switching (mpls) networks
WO2019056239A1 (zh) * 2017-09-21 2019-03-28 华为技术有限公司 报文同步方法和装置
CN112422713A (zh) * 2020-11-18 2021-02-26 中国联合网络通信集团有限公司 一种ip地址获取方法及vtep节点

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102387225A (zh) * 2011-11-14 2012-03-21 中兴通讯股份有限公司 数据流发送方法及装置
US20190089627A1 (en) * 2016-03-15 2019-03-21 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for supporting bidirectional forwarding (bfd) over multi-chassis link aggregation group (mc-lag) in internet protocol (ip) multiprotocol label switching (mpls) networks
CN108696416A (zh) * 2017-04-12 2018-10-23 中兴通讯股份有限公司 一种vxlan单归和双归混合接入方法、装置和pe设备
WO2019056239A1 (zh) * 2017-09-21 2019-03-28 华为技术有限公司 报文同步方法和装置
CN112422713A (zh) * 2020-11-18 2021-02-26 中国联合网络通信集团有限公司 一种ip地址获取方法及vtep节点

Also Published As

Publication number Publication date
CN117459453A (zh) 2024-01-26

Similar Documents

Publication Publication Date Title
US11677720B2 (en) Method and system of establishing a virtual private network in a cloud service for branch networking
US11374904B2 (en) Method and system of a cloud-based multipath routing protocol
CN109218178B (zh) 一种报文处理方法及网络设备
CN108574616B (zh) 一种处理路由的方法、设备及系统
US10637889B2 (en) Systems, methods, and devices for smart mapping and VPN policy enforcement
US8537816B2 (en) Multicast VPN support for IP-VPN lite
US9485147B2 (en) Method and device thereof for automatically finding and configuring virtual network
US11374857B2 (en) Network device management method and apparatus, and system for indicating a network device to perform management operation
US10079781B2 (en) Forwarding table synchronization method, network device, and system
US10033539B1 (en) Replicating multicast state information between multi-homed EVPN routing devices
CN112565046B (zh) 同步多播路由器能力
US20130103836A1 (en) Centralized Configuration with Dynamic Distributed Address Management
US9712649B2 (en) CCN fragmentation gateway
EP3732845B1 (en) Method and apparatus for dynamic discovery of a blockchain component in a cloud computing system
WO2022001669A1 (zh) 建立vxlan隧道的方法及相关设备
WO2018184496A1 (zh) 多归接入方法、装置及多归属节点
US20170078115A1 (en) Multi-homed access
WO2019042303A1 (zh) 报文转发
US9008118B2 (en) Multicast data delivery over mixed multicast and non-multicast networks
EP3817285A1 (en) Method and device for monitoring forwarding table entry
US20230283589A1 (en) Synchronizing dynamic host configuration protocol snoop information
US9219688B2 (en) Method and system for network load balancing
WO2024016799A1 (zh) 数据传输方法、运营商边缘设备、计算机可读存储介质
US11855792B2 (en) Multicast rendezvous point deployment in a virtual gateway of a distributed tunnel fabric
US20240031266A1 (en) Remote reachability checks in a distributed tunnel fabric

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23841868

Country of ref document: EP

Kind code of ref document: A1