WO2024093306A1 - 通信方法及装置 - Google Patents

通信方法及装置 Download PDF

Info

Publication number
WO2024093306A1
WO2024093306A1 PCT/CN2023/103646 CN2023103646W WO2024093306A1 WO 2024093306 A1 WO2024093306 A1 WO 2024093306A1 CN 2023103646 W CN2023103646 W CN 2023103646W WO 2024093306 A1 WO2024093306 A1 WO 2024093306A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication device
leaf
mac address
message
umr
Prior art date
Application number
PCT/CN2023/103646
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 WO2024093306A1 publication Critical patent/WO2024093306A1/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
    • H04L45/74—Address processing for routing
    • H04L45/745—Address table lookup; Address filtering
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • the present application relates to the field of communications, and in particular to a communication method and device.
  • traffic isolation can be performed between devices that do not need to access each other, so as to improve data transmission security and network transmission efficiency.
  • the present application provides a communication method and device for efficiently and conveniently implementing traffic isolation.
  • a communication method comprising: a first communication device receives a first message from a second communication device through a leaf interface. In response to determining to forward the first message through a default MAC address table entry, the first communication device discards the message.
  • the default MAC address table entry includes a leaf identifier and a MAC address of all 0s.
  • the first communication device when the first communication device receives the first message through the leaf interface and determines that the first message needs to be forwarded through the default MAC address table entry including the leaf identifier, the first communication device discards the message.
  • the default MAC address table entry is a MAC address table entry generated according to the UMR.
  • the third communication device when the EVPN instance or AC under the BD of the network device configured with the UMR function (hereinafter referred to as the third communication device) is an AC with a leaf attribute, unicast traffic isolation can be achieved through the above method.
  • the message corresponds to the default MAC address table entry and the default MAC address table entry includes a leaf identifier corresponding to the leaf attribute in the E-tree, it means that the message needs to be subsequently forwarded through the AC with a leaf attribute after being forwarded to the third communication device through the default MAC address table entry (because the AC under the EVPN instance or BD of the third communication device is an AC with a leaf attribute).
  • the above leaf identifier can be at least one bit for indicating a leaf attribute.
  • the leaf identifier can be a value or a string in the E-tree extended group attribute.
  • the value or string is carried in the value field of the E-tree extended group attribute to indicate that the corresponding AC has a leaf attribute.
  • the first communication device receives a message through a leaf interface
  • combining the above two aspects can determine that the message comes from the leaf interface and needs to be subsequently forwarded through the AC with the leaf attribute, so unicast traffic isolation is achieved by discarding the message through the first communication device.
  • the "forwarding through the default MAC address table entry” mentioned in the above method can also be referred to as "forwarding through the UMR".
  • the default MAC address table entry is the forwarding table entry generated based on the UMR. From the perspective of the control plane, the UMR is the routing of the control plane, and when it is sent to the forwarding plane, the UMR corresponds to the default MAC address table entry. Therefore, in this application, "forwarding through the default MAC address table entry” means “forwarding through the UMR". Because the above method is described from the perspective of the forwarding plane, the expression “forwarding through the default MAC address table entry" is adopted. Unless otherwise specified in this application, the relationship between the default MAC address table entry and the UMR can be understood as above.
  • the method further includes: the first communication device receives a UMR from a third communication device, the UMR carries leaf indication information, the leaf indication information indicates that the UMR has a leaf attribute, and the first communication device generates a default MAC address table entry including the leaf identifier according to the UMR.
  • the third communication device can send a UMR carrying leaf indication information to the first communication device, so that after receiving the UMR, the first communication device can establish a default MAC address table entry including a leaf identifier according to the UMR.
  • the EVPN instance of the third communication device configured with the UMR function or the AC under the BD are all leaf attribute ACs, unicast traffic isolation can be achieved through the above method.
  • the UMR carries an E-tree extended community attribute, which includes leaf indicates information.
  • the first communication device can determine, after receiving the UMR, that there is a corresponding relationship between the UMR and the leaf attribute based on the E-tree extended group attribute in the UMR, so that the first communication device can establish a default MAC address table entry including the leaf identifier.
  • the leaf indication information is a leaf identifier.
  • the leaf identifier in the default MAC address table entry and the leaf indication information in the UMR are uniformly used with the same content, so as to facilitate data management.
  • the first communication device can directly copy the content of the leaf indication information of the UMR to the default MAC address table entry as the leaf identifier in the default MAC address table entry. This helps to quickly generate the default MAC address table entry.
  • the first communication device is a Sleaf device
  • the second communication device is a UP device
  • the third communication device is an Aleaf device.
  • the first communication device is used as a Sleaf device
  • the second communication device is used as a UP device
  • the third communication device is used as an Aleaf device, so that unicast traffic isolation can be performed on the Sleaf device when the UMR function is configured on the Aleaf device.
  • the UMR is an EVPN MAC router.
  • the method further includes: the first communication device receives the second message through a leaf interface.
  • the first communication device searches for a matching MAC address entry according to a destination MAC address of the second message, the MAC address entry including a root identifier.
  • the first communication device forwards the second message.
  • the first communication device when the first communication device receives a message through the leaf interface, if it is determined that the address table entry corresponding to the destination MAC address of the message includes a root identifier, the message will continue to be forwarded, thereby ensuring that messages that do not require unicast traffic isolation can be forwarded smoothly.
  • a communication method including: a first communication device receives a UMR from a second communication device, the UMR carrying leaf indication information, the leaf indication information indicating that the UMR has a leaf attribute.
  • the first communication device generates a default MAC address table entry according to the UMR, the default MAC address table entry including a leaf identifier and a MAC address of all 0s.
  • the second communication device sends a UMR carrying leaf indication information to the first communication device, so that after receiving the UMR, the first communication device can establish a default MAC address table entry including a leaf identifier according to the UMR.
  • the first communication device receives a message through the leaf attribute
  • the message corresponds to the above default MAC address table entry (that is, the default MAC address table entry including the leaf identifier)
  • the message needs to be subsequently forwarded through the AC with leaf attributes after being forwarded to the second communication device through the UMR. In this way, unicast traffic isolation can be achieved by discarding the message by the first communication device.
  • the UMR carries an E-tree extended community attribute, wherein the E-tree extended community attribute includes leaf indication information.
  • the first communication device can determine, after receiving the UMR, that there is a corresponding relationship between the UMR and the leaf attribute based on the E-tree extended group attribute in the UMR, so that the first communication device can establish a default MAC address table entry including the leaf identifier.
  • the leaf indication information is a leaf identifier.
  • the leaf identifier in the default MAC address table entry and the leaf indication information in the UMR are uniformly used with the same content, so as to facilitate data management.
  • the first communication device can directly copy the content of the leaf indication information of the UMR to the default MAC address table entry as the leaf identifier in the default MAC address table entry. This helps to quickly generate the default MAC address table entry.
  • the first communication device is a Sleaf device
  • the second communication device is an Aleaf device.
  • the first communication device is used as the Sleaf device
  • the third communication device is used as the Sleaf device, so that unicast traffic isolation can be performed on the Sleaf device when the UMR function is configured on the Aleaf device.
  • the UMR is an EVPN MAC router.
  • a communication method comprising: a second communication device generates a UMR, wherein the UMR carries a leaf indication signal; The leaf indication information is used to indicate that the UMR has a leaf attribute. The second communication device sends the UMR to the first communication device.
  • the second communication device can send a UMR carrying leaf indication information to the first communication device, so that after receiving the UMR, the first communication device can establish a default MAC address table entry including a leaf identifier according to the UMR.
  • the EVPN instance or AC under the BD of the second communication device configured with the UMR function are both ACs with leaf attributes, unicast traffic isolation can be achieved through the above method.
  • the message needs to be subsequently forwarded through the AC with leaf attributes after being forwarded to the second communication device through the UMR (because the EVPN instance or AC under the BD of the second communication device are both ACs with leaf attributes). In this way, unicast traffic isolation can be achieved by discarding the message by the first communication device.
  • the UMR carries an E-tree extended community attribute, wherein the E-tree extended community attribute includes leaf indication information.
  • the first communication device can determine, after receiving the UMR, that there is a corresponding relationship between the UMR and the leaf attribute based on the E-tree extended group attribute in the UMR, so that the first communication device can establish a default MAC address table entry including the leaf identifier.
  • the second communication device is an Aleaf device
  • the first communication device is a Sleaf device.
  • the second communication device is used as the Aleaf device
  • the first communication device is used as the Sleaf device, so that unicast traffic isolation can be performed on the Sleaf device when the UMR function is configured on the Aleaf device.
  • the UMR is an EVPN MAC router.
  • a communication method comprising: a second communication device receives a first message from a first communication device. In response to determining that a first outbound interface in a first MAC address table entry matching a destination media access control MAC address of the first message is a leaf interface, and a second MAC address table entry matching a source MAC address of the first message includes a leaf identifier, the second communication device discards the first message.
  • the first communication device cannot perform unicast traffic isolation because the MAC detailed route on the second communication device is not learned on the first communication device. That is to say, the message forwarded by the first communication device to the second communication device through the UMR may be a message that needs to be isolated from unicast traffic (that is, the message comes from the AC of the leaf attribute, and the message also needs to be subsequently forwarded through the AC of the leaf attribute).
  • the second communication device can filter the received message through the above method, that is, when the second MAC address table entry including the leaf identifier is determined according to the source MAC address of the first message (that is, it indicates that the first message comes from the leaf interface), and it is determined that the first message needs to be forwarded through the leaf interface of the second communication device (that is, the message needs to be sent to the next hop device through the leaf interface on the second communication device), the second communication device discards the message, so that the effect of unicast traffic isolation is achieved.
  • the method further includes: the second communication device receives a MAC route from the first communication device.
  • the MAC route includes a source MAC address of the first message and leaf indication information, and the leaf indication information indicates that the MAC route has a leaf attribute.
  • the second communication device generates the second MAC address table entry including the leaf identifier according to the MAC route.
  • a MAC address table entry including a leaf identifier (and also the source MAC address of the first message) can be generated on the second communication device, so that after receiving the message, the second communication device can determine whether the message comes from the leaf interface on the first communication device according to the MAC address table entry.
  • the second communication device discards the message, so that the effect of unicast traffic isolation can be achieved.
  • the leaf indication information is a leaf identifier.
  • the leaf identifier in the default MAC address table entry and the leaf indication information in the UMR are uniformly used with the same content, so as to facilitate data management.
  • the second communication device can directly copy the content of the leaf indication information of the UMR to the default MAC address table entry as the leaf identifier in the default MAC address table entry. This helps to quickly generate the default MAC address table entry.
  • the method further includes: in response to determining that the second outbound interface in the third MAC address table entry matched by the destination MAC address of the second message is a leaf interface, and the fourth MAC address table entry matched by the source MAC address of the second message
  • the item includes a root identifier.
  • the second communication device forwards the second message through the second outbound interface.
  • the second communication device determines that the message will be forwarded through the leaf interface on the first communication device based on the destination MAC address of the second message, and determines that the message comes from the root interface based on the source MAC address of the second message, it continues to forward the message, thereby ensuring that messages that do not require unicast traffic isolation can be forwarded smoothly.
  • the second communication device is an Aleaf device
  • the first communication device is a Sleaf device.
  • the second communication device is used as an Aleaf device and the first communication device is used as a Sleaf device, so that unicast traffic isolation can be performed on the Aleaf device.
  • a communication device which is applied to a first communication device, comprising: a receiving unit, which is used to receive a first message from a second communication device through a leaf interface; a processing unit, which is used to discard the first message in response to determining to forward the first message through a default media access control MAC address table entry, wherein the default MAC address table entry includes a leaf identifier and a MAC address of all 0s.
  • the receiving unit is further configured to receive an unknown MAC route UMR from a third communication device, the UMR carrying leaf indication information, the leaf indication information indicating that the UMR has a leaf attribute.
  • the processing unit is further configured to generate a default MAC address table entry according to the UMR.
  • the UMR carries Ethernet multicast E-tree extended community attributes; the E-tree extended community attributes include leaf indication information.
  • the leaf indication information is a leaf identifier.
  • the first communication device is a Sleaf device
  • the third communication device is an Aleaf device.
  • the receiving unit is further used to receive a second message through a leaf interface; the processing unit is further used to search for a matching MAC address table entry according to the destination MAC address of the second message, the MAC address table entry including a root identifier; the processing unit is further used to forward the second message.
  • a communication device which is applied to a first communication device, including: a receiving unit, used to receive an unknown media access control route UMR from a second communication device, the UMR carrying leaf indication information, and the leaf indication information indicating that the UMR has a leaf attribute; a processing unit, used to generate a default MAC address table entry according to the UMR, wherein the default MAC address table entry includes a leaf identifier and a MAC address of all 0s.
  • the UMR carries Ethernet multicast E-tree extended community attributes; the E-tree extended community attributes include leaf indication information.
  • the leaf indication information is a leaf identifier.
  • the first communication device is a Sleaf device
  • the second communication device is an Aleaf device.
  • a communication device applied to a first communication device, comprising: a processing unit, used to generate an unknown media access control route UMR, the UMR carrying leaf indication information, the leaf indication information indicating that the UMR has a leaf attribute; a sending unit, used to send the UMR to a second communication device.
  • the UMR carries Ethernet multicast E-tree extended community attributes; the E-tree extended community attributes include leaf indication information.
  • the first communication device is an Aleaf device
  • the second communication device is a Sleaf device.
  • a communication device which is applied to a second communication device, and includes: a receiving unit, used to receive a first message from a first communication device; a processing unit, used to discard the first message in response to determining that the first outgoing interface in a first MAC address table entry matching the destination media access control MAC address of the first message is a leaf interface, and the second MAC address table entry matching the source MAC address of the first message includes a leaf identifier.
  • the receiving unit is further used to receive a MAC route from the first communication device; the MAC route includes a source MAC address of the first message and leaf indication information, and the leaf indication information indicates that the MAC route has a leaf attribute; the processing unit is further used to generate a second MAC address table entry based on the MAC route.
  • the leaf indication information is a leaf identifier.
  • the receiving unit is also used to receive a second message; the processing unit is also used to forward the second message through the second output interface in response to determining that the second output interface in the third MAC address table entry matching the destination MAC address of the second message is a leaf interface, and that the fourth MAC address table entry matching the source MAC address of the second message includes a root identifier.
  • the second communication device is an Aleaf device
  • the first communication device is a Sleaf device.
  • a communication device comprising a processor and a memory, the memory being used to store computer instructions, and the processor being used to call and execute computer instructions from the memory to implement a method as described in the first aspect or any implementation in the first aspect, or the second aspect or any implementation in the second aspect, or the third aspect or any implementation in the third aspect, or the fourth aspect or any implementation in the fourth aspect.
  • a communication system comprising a first communication device and a second communication device.
  • the first communication device is used to implement the method as described in the first aspect or any implementation of the first aspect or the second aspect or any implementation of the second aspect
  • the second communication device is used to implement the method as described in the third aspect or any implementation of the third aspect.
  • a communication system comprising a first communication device and a second communication device, wherein the first communication device or the second communication device is used to implement a method as in the fourth aspect or any one of the implementation modes of the fourth aspect.
  • a computer-readable storage medium in which instructions are stored.
  • the instructions are executed on a processor, a method as described in the first aspect or any implementation in the first aspect or the second aspect or any implementation in the second aspect or the third aspect or any implementation in the third aspect or the fourth aspect or any implementation in the fourth aspect is implemented.
  • a computer program product including a computer program.
  • the computer program runs on a processor, it implements a method as described in the first aspect or any implementation in the first aspect, or the second aspect or any implementation in the second aspect, or the third aspect or any implementation in the third aspect, or the fourth aspect or any implementation in the fourth aspect.
  • FIG1 is a schematic diagram of a structure of a communication system provided in an embodiment of the present application.
  • FIG2 is a flow chart of a communication method according to an embodiment of the present application.
  • FIG3 is a schematic diagram of the structure of an E-tree extended community attribute provided in an embodiment of the present application.
  • FIG4 is a second schematic diagram of the structure of a communication system provided in an embodiment of the present application.
  • FIG5 is a second flow chart of a communication method provided in an embodiment of the present application.
  • FIG6 is a third flow chart of a communication method provided in an embodiment of the present application.
  • FIG7 is a fourth flow chart of a communication method provided in an embodiment of the present application.
  • FIG8 is a fifth flow chart of a communication method provided in an embodiment of the present application.
  • FIG9 is a sixth flow chart of a communication method provided in an embodiment of the present application.
  • FIG10 is a seventh flow chart of a communication method provided in an embodiment of the present application.
  • FIG11 is a schematic diagram of a structure of a communication device provided in an embodiment of the present application.
  • FIG12 is a second schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • FIG. 13 is a third schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • Unknown media access control route also known as “UMR routing” is an alternative to MAC detailed routing.
  • a MAC route includes a specific MAC address so as to indicate the forwarding of a message with the MAC address as the destination address.
  • MAC detailed route Such a MAC route including a specific MAC address is called a "MAC detailed route”.
  • UMR is used to indicate the selection made when there is no address table entry matching the message to be forwarded.
  • device A sends a UMR to device B, so that device B generates a default MAC address table entry based on the UMR.
  • device B receives a message and there is no entry in the MAC address table that matches the destination address of the message, it forwards the message to device A according to the default MAC address table entry.
  • Ethernet multicast is a point-to-multipoint service.
  • the attachment circuit (AC) in the network can be divided into leaf attributes and root attributes. It can also be understood as dividing the interfaces at both ends of the AC into leaf interfaces and root interfaces. The two ends of the AC with leaf attributes are leaf interfaces, and the root interfaces are root interfaces. Both ends of the AC with the attribute are root interfaces.
  • the root interface can communicate with the root interface or the leaf interface, but two leaf interfaces cannot communicate with each other.
  • traffic isolation can be achieved in the network. For example, you can configure the interfaces of two devices that do not need to communicate with each other as leaf interfaces to achieve traffic isolation between the two devices.
  • Segment routing over IPv6 is a SR technology based on the IPv6 forwarding plane. SRv6 combines the source routing advantages of SR with the simplicity and scalability of IPv6, and is increasingly being used in various border gateway protocol (BGP) services.
  • BGP border gateway protocol
  • Route reflector is a route transmission technology.
  • border gateway protocol (BGP) route transmission is considered to be transmitted in a one-hop manner; on the other hand, there are many devices in the actual network, and it is unlikely that internal border gateway protocol (IBGP) connections are established between every two devices in the autonomous system (AS), but the routes need to be passed on.
  • IBGP border gateway protocol
  • a router in an AS can be used as RR, and other routers can be used as clients.
  • An IBGP connection is established between the client and the RR. In this way, the client can send routing information to the RR, and the RR will reflect the routing information to other clients, and there is no need to establish a BGP connection between clients.
  • Ethernet virtual private network is a VPN technology based on Layer 2 network.
  • EVPN is often used to transmit MAC routing information and IP routing information, and is used as the control layer of overlay networks such as VXLAN and SRv6.
  • Virtual Private LAN Service is a point-to-multipoint L2VPN service provided on Multiprotocol Label Switching (MPLS) or IP backbone network.
  • MPLS Multiprotocol Label Switching
  • IP backbone network IP backbone network.
  • Service providers provide VPLS services to user networks by simulating a virtual switch connecting multiple remote sites for a user network on the backbone network.
  • FIG1 it is a schematic diagram of the structure of a communication system 10 provided in an embodiment of the present application.
  • the user equipment 101 for example, optical line terminal (OLT), OLT 1011 and OLT 1012 are taken as examples in FIG1
  • the user equipment 101 is connected to the user plane (UP) device 104 (UP device 1041, UP device 1042 and UP device 1043 are taken as examples in FIG1 ) through the bearer network.
  • the UP device 104 is a device for authenticating and managing the user equipment and responsible for forwarding user messages.
  • the UP device 104 is also connected to the control plane (CP) device 106, which is used to manage the active-standby role switching of the UP device and is responsible for the management and control of the user equipment.
  • CP control plane
  • the bearer network includes a spine device 105 and a leaf device.
  • the leaf device can be divided into an Aleaf device 102 and a Sleaf device 103.
  • the Aleaf device 102 can be connected to the user device 101 to realize the function of the access side provider edge (PE) device.
  • the Sleaf device 103 can be connected to the UP device 104 to realize the function of the gateway side (provider edge, PE) device.
  • Spine device 1051 and Spine device 1052 can act as RR roles for reflecting routes.
  • an active-active mode is adopted in the bearer network to ensure the normal operation of the network.
  • Aleaf device 1021 and Aleaf device 1022 are active-active devices, that is, for other devices in the network, Aleaf device 1021 and Aleaf device 1022 provide access services as a device. In this way, when Aleaf device 1021 or Aleaf device 1022 fails, another device can continue to provide services, realizing uninterrupted switching of services.
  • Spine device 1051 and Spine device 1052, Sleaf device 1031 and Sleaf device 1032 can all be active-active devices.
  • the technical solution provided by the embodiment of the present application will be introduced by taking Aleaf device 1021, Spine device 1051 and Sleaf device 1031 as the main device as an example.
  • the backup devices such as Aleaf device 1022, Spine device 1052 and Sleaf device 1032
  • the introduction to the operation process of Aleaf device 1021, Spine device 1051 and Sleaf device 1031 can be referred to.
  • the EVPN VPLS service (EVPN VPLS over SRv6) can be carried through the SRv6 tunnel.
  • the user equipment 101 can be connected to the virtual local area network (VLAN) or VLAN Nested (802.1Q in 802.1Q, QinQ) is connected to the Aleaf device 102.
  • the UP device 104 can also be connected to the Sleaf device 103 through VLAN or QinQ.
  • E-Tree can be used to isolate traffic between devices that do not need to access each other.
  • the AC between OLT 1011 and Aleaf device 1021 (i.e. link 1), and the AC between Sleaf device 1031 and UP device 1041 (i.e. link 5) can be configured as leaf attributes, that is, the interfaces on the devices corresponding to the above two ACs can be configured as leaf interfaces.
  • the Aleaf device 1021 sends a MAC route (carrying the MAC address 1 and the leaf identifier) to the Sleaf device 1031, and then the Sleaf device 1031 generates a MAC address table entry (including the MAC address 1 and the leaf identifier).
  • the Sleaf device 1031 sends a MAC route (carrying the MAC address 2 and the leaf identifier) to the Aleaf device 1021, and then the Aleaf device 1021 generates a MAC address table entry (including the MAC address 2 and the leaf identifier).
  • UP device 1041 sends a unicast message to OLT 1011:
  • Sleaf device 1031 receives the message through link5
  • Sleaf device 1031 determines that the message comes from the leaf interface.
  • Sleaf device 1031 determines the MAC address table entry corresponding to the leaf attribute according to the destination MAC address of the message (i.e., MAC address 1 of OLT 1011), that is, determines that the message will be sent to the leaf interface.
  • Sleaf device 1031 discards the message, thereby achieving unicast traffic isolation.
  • the Aleaf device 102 since the Aleaf device 102 may be connected to a large number of users, the Aleaf device 102 may learn a large number of MAC routes.
  • the Aleaf device 102 notifies these MAC routes to the Sleaf device 103 through the RR (i.e., the Spine device 105)
  • the Sleaf device 103 since the Sleaf device 103 may be connected to a large number of Aleaf devices, the Sleaf device 103 needs to learn a large number of MAC routes. This results in an excessive load on the Sleaf device 103.
  • the UMR function can be configured on the Aleaf device 102 in the related art. Specifically, take the configuration of the UMR function on the Aleaf device 1021 as an example: after the Aleaf device 1021 sends the UMR to the Sleaf device 1031, the Sleaf device 1031 can generate a default MAC address table entry according to the UMR.
  • the Sleaf device 1031 when the Sleaf device 1031 receives a message sent to the OLT 1011 or OLT 1012, even if there is no entry in the MAC address table that matches the destination address of the message (i.e., the MAC address of the OLT 1011 or OLT 1012), the Sleaf device 1031 can forward the message to the Aleaf device 1021 according to the default MAC address table entry to complete the forwarding of the message.
  • the Aleaf device 102 when the UMR function is configured on the Aleaf device 102, the Aleaf device 102 only notifies the UMR route to the Sleaf device 103, but does not notify the MAC detailed route carrying the leaf attribute to the Sleaf device 103. This results in the Sleaf device 103 being unable to perform unicast traffic isolation.
  • link1 and link5 in FIG1 as leaf attributes as an example, when the Sleaf device 1031 receives a message from link5 (the destination address of the message is MAC address 1), since there is no MAC address table entry for MAC address 1 on the Sleaf device 1031 (only the default MAC address table entry corresponding to UMR forwarding), it is unable to perceive that the message will pass through the leaf interface in the subsequent forwarding process, and therefore the message will not be discarded, that is, unicast traffic isolation cannot be performed.
  • an embodiment of the present application provides a communication method, which can implement unicast traffic isolation in a scenario using UMR.
  • the method provided by the embodiment of the present application is introduced in two implementation modes:
  • the UMR sent by the Aleaf device 1021 may carry leaf indication information, and the indication information indicates that the UMR has a leaf attribute, so that after receiving the UMR, the receiving device (e.g., the Sleaf device 1031 in FIG. 1 ) may generate a default MAC address table entry including a leaf identifier (wherein the leaf identifier may be understood as indicating that the default MAC address table entry corresponds to a leaf attribute).
  • the Sleaf device 1031 receives a message through a leaf interface, if it is determined that the message corresponds to a default MAC address table entry including a leaf identifier, the Sleaf device 1031 discards the message. In this way, unicast traffic isolation can be implemented on the Sleaf device 1031 for messages that come from the leaf interface on the Sleaf device 1031 on the one hand and are transmitted to the next-hop device through the leaf interface on the Aleaf device 1021 on the other hand.
  • the UMR function when configured on a device in the communication system (e.g., the Aleaf device 102 in FIG. 1 ), when the Sleaf device 103 does not discard the message that needs to be isolated for unicast traffic, and forwards the message to the Aleaf device 102 through the UMR forwarding, the Aleaf device 102 receives the message that meets the requirements (the source MAC address of the message corresponds to the MAC address table entry of the leaf identifier, and the message needs to pass through the Aleaf device 102). The leaf interface on the network forwards the packets) and discards them, thereby isolating unicast traffic.
  • the requirements the source MAC address of the message corresponds to the MAC address table entry of the leaf identifier, and the message needs to pass through the Aleaf device 102
  • the leaf interface on the network forwards the packets) and discards them, thereby isolating unicast traffic.
  • the EVPN instance or bridge domain (BD) on the device with the UMR function is configured as an E-tree leaf Node, that is, the AC corresponding to the EVPN instance or BD on the device with the UMR function is configured as a leaf attribute.
  • link1 and link2 correspond to the same EVPN instance on the Aleaf device 1021, then configuring the EVPN instance as an E-tree leaf Node can be specifically understood as configuring both link1 and link2 as leaf attributes.
  • the method provided in the embodiment of the present application is introduced in conjunction with the process of the UP device 1041 sending a message to the OLT 1011.
  • the operation process of the control flow in the method provided in the embodiment of the present application may include:
  • the Aleaf device 1021 generates a UMR (for easy distinction, the UMR is referred to as UMR-1 hereinafter).
  • the UMR-1 may be used to indicate that when there is no MAC address entry matching the message to be forwarded, the message to be forwarded is forwarded to the Aleaf device 1021 .
  • a UMR may be an EVPN route.
  • an EVPN MAC route with a MAC address of all zeros may be used as a UMR.
  • the UMR-1 may be generated by the EVPN instance corresponding to link1 and link2 in the Aleaf device 1021 .
  • UMR-1 carries leaf indication information, which can be used to indicate that UMR-1 has leaf attributes.
  • leaf identifier can be used to indicate that after forwarding the message to Aleaf device 1021 in UMR mode, Aleaf device 1021 will forward the message through the leaf interface in the subsequent forwarding process.
  • the leaf indication information may be carried in an extended community attribute in the UMR-1.
  • the UMR-1 carries an E-tree extended community attribute, which includes leaf indication information.
  • FIG3 is a schematic diagram of the message format of an E-tree extended group attribute carried by a UMR shown in an embodiment of the present application. It mainly includes a 3-byte leaf label field and a 1-byte flags field. In addition, it also includes a 2-byte reserved field, a 1-byte type field, and a 1-byte sub-type field. Among them, the leaf label field carries the above-mentioned leaf indication information, which is used to identify that the device interface sending the E-tree extended group attribute is a leaf interface.
  • the leaf identifier can also be a value or a string carried in other fields in the E-tree extended group attribute, and the value or string is carried in the value field of the E-tree extended group attribute to indicate that the corresponding AC (or the device interface corresponding to the AC) is a leaf attribute.
  • the first 7 bits in the Flags field are all 0.
  • the E-TREE extended community attribute is used to isolate broadcast, unknown unicast, and multicast (BUM) traffic between leaf interfaces
  • the last bit in the Flags field will be 0.
  • the E-TREE extended community attribute is used to isolate known unicast traffic between leaf interfaces, the last bit in the Flags field will be 1.
  • the device that receives the E-TREE extended community attribute isolates known unicast traffic and BUM traffic between leaf interfaces by identifying the leaf indication information and the last bit of the Flags field.
  • the leaf indication information may also be carried in other fields in the UMR-1.
  • the leaf indication information may be carried in other extended group attributes in the UMR-1 except the E-tree extended group attribute. This may not be limited in the embodiment of the present application.
  • the leaf indication information carried by the UMR-1 there is no limitation on the specific form of the leaf indication information carried by the UMR-1.
  • a bit is pre-set in the frame structure of the UMR-1. When the bit is 0, it indicates that the UMR-1 corresponds to the leaf attribute (the bit that is 0 can be understood as the above-mentioned leaf indication information); when the bit is 1, it indicates that the UMR-1 does not correspond to the leaf attribute, or the UMR-1 corresponds to the root attribute (the bit that is 1 can be used as a root indication information.
  • the root indication information can be used to indicate that after the message is forwarded to the Aleaf device 1021 using the UMR method, the Aleaf device 1021 does not necessarily forward the message through the leaf interface in the subsequent forwarding process).
  • a field may be included in the frame structure of UMR-1, and the field is used to indicate whether UMR-1 corresponds to a leaf attribute or a root attribute.
  • the E-tree extended community attribute mentioned above can be used to indicate whether UMR-1 corresponds to a leaf attribute or a root attribute.
  • the field corresponding to the leaf attribute (such as the E-tree extended community attribute mentioned above) can be used as a leaf indicator. Display information.
  • the Aleaf device 1021 sends the UMR- 1 to the Sleaf device 1031 .
  • the Aleaf device 1021 may send the UMR-1 to the Sleaf device 1031 via the Spine device 1051 that serves as the RR.
  • the Sleaf device 1031 generates a default MAC address entry 1 according to the UMR-1.
  • the default MAC address entry 1 may be used to indicate that when there is no MAC address entry matching the message to be forwarded, the message to be forwarded is forwarded to the Aleaf device 1021 .
  • the default MAC address table entry 1 includes a MAC address of all 0s, which is used to indicate that the table entry is a default MAC address table entry.
  • the default MAC address table entry 1 also includes a leaf identifier.
  • the leaf identifier can be used to indicate that when a message is forwarded according to the default MAC address table entry 1, the message needs to be forwarded through a leaf interface in a subsequent forwarding process.
  • the so-called "the default MAC address table entry 1 includes a leaf identifier" in the embodiment of the present application can be understood as an implementation method that makes the default MAC address table entry 1 correspond to the leaf attribute.
  • carrying the leaf identifier in the default MAC address table entry 1 is just a specific form of corresponding the default MAC address table entry 1 and the leaf attribute.
  • the leaf identifier may not be carried in the default MAC address table entry, but it is sufficient as long as the leaf attribute can be determined according to the default MAC address table entry.
  • the default MAC address table entry 1 may include a field, and the field is used to indicate whether the default MAC address table entry 1 corresponds to a leaf attribute or a root attribute. Then, the field corresponding to the leaf attribute can be used as a leaf identifier as a whole.
  • the leaf indication information carried in UMR-1 i.e., the UMR sent by the Aleaf device 1021 to the Sleaf device 1031
  • the leaf identifier carried in the default MAC address table entry 1 i.e., the default MAC address table entry generated by the Sleaf device 1031
  • the leaf indication information carried in the above UMR-1 is the leaf identifier carried in the default MAC address entry 1.
  • the leaf indication information in the UMR-1 may be directly copied to the default MAC address table entry 1 as the leaf identifier in the default MAC address table entry 1. For example, if a bit of 0 is used as the leaf indication information in the UMR-1, "0" may be copied to a pre-set bit in the default MAC address table entry 1 as the leaf identifier.
  • the leaf identifier in the default MAC address table entry 1 and the leaf indication information in the UMR-1 may be in different forms.
  • the E-tree extended community attribute is used as the leaf indication information in the UMR-1
  • a bit preset to 0 is used as the leaf identifier in the default MAC address table entry 1 (it can be understood that after the Sleaf device 1031 determines that the UMR-1 carries the leaf indication information by reading the E-tree extended community attribute in the UMR-1, it generates the default MAC address table entry 1 and sets the preset bit in the default MAC address table entry 1 to "0" to indicate the leaf identifier).
  • the specific forms of the leaf identifier in the default MAC address table entry 1 and the leaf indication information in UMR-1 in the embodiment of the present application may be the same or different, and the embodiment of the present application may not impose any limitation on this.
  • the process may also include the process in which the Aleaf device 1021 learns the MAC address of the OLT, the Sleaf device 1031 learns the MAC addresses of each UP device, and the Sleaf device 1031 sends a MAC route (which carries the MAC address of each UP device) to the Aleaf device 1021.
  • the Aleaf device 1021 learns the MAC address of the OLT
  • the Sleaf device 1031 learns the MAC address of each UP device
  • the Sleaf device 1031 sends a MAC route to the Aleaf device 1021
  • the method further includes:
  • the Sleaf device 1031 receives the message a from the UP device 1041 through the interface (ie, leaf interface) corresponding to link5 (ie, AC of the leaf attribute).
  • OLT 1011 After OLT 1011 accesses the network, OLT 1011 sends a broadcast message to the network.
  • the broadcast message is used to The authentication information of OLT 1011 is sent to each UP device.
  • Aleaf device 1021 After receiving the broadcast message, Aleaf device 1021 will forward the broadcast message to Sleaf device 1031, and Sleaf device 1031 will forward the broadcast message to each UP device after receiving the broadcast message.
  • each UP device will send a feedback message to OLT 1011 to establish a connection between OLT 1011 and the UP device, so as to perform device authentication on OLT 1011 later.
  • Considering that in the authentication process of OLT 1011 only one UP device needs to establish a connection with OLT 1011. Therefore, it is possible to avoid OLT 1011 from establishing a connection with all UP devices by isolating the traffic between OLT 1011 and some UP devices.
  • the UP device 1041 can be understood as a UP device that needs to be isolated from the OLT 1011 in terms of traffic.
  • Message a can be understood as a feedback message sent by the UP device 1041 after receiving the broadcast message sent by the OLT 1011.
  • the method also includes:
  • the Sleaf device 1031 In response to determining to forward the first message through the default MAC address entry 1 , the Sleaf device 1031 discards the first message.
  • the default MAC address table entry 1 includes a leaf identifier and a MAC address of all 0s.
  • the Sleaf device 1031 can search the MAC address table entry according to the destination MAC address of message a (i.e., MAC address 1), and then hit the default MAC address table entry 1 including the leaf identifier. That is to say, on the one hand, it is determined that message a hits the default MAC address table entry 1 including the leaf identifier, and on the other hand, the Sleaf device 1031 can also determine that message a is received through the leaf interface, and then the Sleaf device 1031 discards the message a according to the rules of the E-tree, thereby achieving unicast traffic isolation.
  • MAC address 1 the destination MAC address of message a
  • the Sleaf device 1031 can also determine that message a is received through the leaf interface, and then the Sleaf device 1031 discards the message a according to the rules of the E-tree, thereby achieving unicast traffic isolation.
  • the "forwarding through the default MAC address table entry” mentioned in the above method can also be referred to as "forwarding through the UMR".
  • the default MAC address table entry is the forwarding table entry generated based on the UMR. From the perspective of the control plane, the UMR is the routing of the control plane, and when it is sent to the forwarding plane, the UMR corresponds to the default MAC address table entry. Therefore, in this application, "forwarding through the default MAC address table entry” means “forwarding through the UMR". Because the above method is described from the perspective of the forwarding plane, the expression “forwarding through the default MAC address table entry" is adopted. Unless otherwise specified in this application, the relationship between the default MAC address table entry and the UMR can be understood as above.
  • the Sleaf device 1031 when the Sleaf device 1031 receives a message (referred to as message b) that needs to be forwarded to an AC of other root attributes through a leaf interface, the Sleaf device 1031 forwards the message b (ie, does not discard the message b).
  • message b a message that needs to be forwarded to an AC of other root attributes through a leaf interface
  • the user device 101 also includes an OLT 1013, and the OLT 1013 is connected to the Aleaf device 1021 via link 11, and the OLT 1013 is also connected to the Aleaf device 1022 via link 12.
  • link 11 and link 12 do not belong to the EVPN corresponding to the above link 1-link 4, and link 11 and link 12 are root attributes.
  • the Sleaf device 1031 receives a message b that needs to be forwarded to the OLT 1013 via a leaf interface (such as via an interface corresponding to link 5), as shown in FIG5 , the method may further include:
  • the Sleaf device 1031 receives the message b from the UP device 1041 through the leaf interface.
  • the destination MAC address of message b is the MAC address of OLT 1013 (i.e., MAC address 2 in Figure 4).
  • the Sleaf device 1031 searches for a matching MAC address entry according to the destination MAC address of the message b, and the MAC address entry includes a root identifier, and the Sleaf device 1031 forwards the message b.
  • Aleaf device 1021 can learn the MAC address of OLT 1013 and send a MAC route (carrying MAC address 2 and root indication information) to Sleaf device 1031.
  • Sleaf device 1031 generates a MAC address table entry (including MAC address 2 and root identifier) based on the MAC route.
  • the MAC address table entry can be used to indicate forwarding with a destination address of MAC address 2.
  • the root identifier in the MAC address table entry is used to indicate that unicast traffic isolation is not required for the message.
  • Sleaf device 1031 can forward message b to Aleaf device 1021 based on the above MAC address table entry.
  • the Aleaf device 1021 can forward the message to the OLT 1013 according to the destination MAC address of the message b, thereby completing the forwarding of the message b.
  • the Sleaf device 1031 when the Sleaf device 1031 receives a message through the leaf interface, if it is determined that the MAC address table entry corresponding to the destination MAC address of the message includes a root identifier, the message continues to be forwarded, thereby ensuring that the message that does not require unicast traffic isolation can be forwarded smoothly.
  • FIGS. 2 to 5 mainly show that the Aleaf device 1021 sends a UMR-1 carrying leaf indication information to the Sleaf device 1031.
  • a default MAC address table entry 1 including a leaf identifier is established in the Sleaf device 1031.
  • this implementation method i.e., the first implementation method above of discarding the message a is introduced.
  • the second implementation method above i.e., the Sleaf device 103 does not discard the messages that need to be isolated for unicast traffic, and the received messages that meet the requirements are discarded on the Aleaf device 102, thereby implementing unicast traffic isolation
  • the operation process of the control flow may include:
  • the Aleaf device 1021 generates a UMR (hereinafter referred to as UMR-2).
  • this UMR-2 can be used to indicate that when there is no MAC address table entry matching the message to be forwarded, the message to be forwarded is forwarded to the Aleaf device 1021.
  • UMR-2 can be an EVPN MAC route with a MAC address of all 0s generated by the EVPN instances corresponding to link1 and link2 in the Aleaf device 1021.
  • UMR-2 of S301 does not carry leaf indication information.
  • the Aleaf device 1021 sends the UMR- 2 to the Sleaf device 1031 .
  • the Aleaf device 1021 may send the UMR-2 to the Sleaf device 1031 via the Spine device 1051 serving as the RR.
  • the Sleaf device 1031 generates a default MAC address entry 2 according to UMR-2.
  • the default MAC address entry 2 may be used to indicate that when there is no MAC address entry matching the message to be forwarded, the message to be forwarded is forwarded to the Aleaf device 1021 .
  • the default MAC address table entry 2 does not include a leaf identifier, in other words, the default MAC address table entry 2 may include a root identifier. In this way, the Sleaf device 1031 can only use the default MAC address table entry 2 to determine whether a message needs to be forwarded by UMR, and cannot use the default MAC address table entry 2 to determine whether to discard a message that needs to be forwarded by UMR (i.e., to perform unicast traffic isolation).
  • the Sleaf device 1031 learns the MAC address 2 (ie, the MAC address of the UP device 1041) through link 5 (ie, the AC of the leaf attribute).
  • the Sleaf device 1031 sends the MAC route to the Aleaf device 1021 .
  • the MAC route carries MAC address 2 and leaf indication information.
  • Sleaf device 1031 can send MAC address 2 to other devices in the network (such as Aleaf device 1021) by publishing MAC routes, wherein the MAC routes carry leaf indication information for E-tree traffic isolation.
  • the Aleaf device 1021 generates a MAC address entry a according to the MAC route.
  • the MAC address table entry includes MAC address 2 and a leaf identifier.
  • the MAC address table entry can be used to indicate that the message with the source MAC address being MAC address 2 comes from the AC with the leaf attribute.
  • the Aleaf device 1021 may learn the MAC address of the OLT (for example, in FIG. 6 , the Aleaf device 1021 learns the MAC address 1 of the OLT 1011 and generates a MAC address table entry b.
  • the MAC address table entry b indicates that the message will be forwarded through link 1 (i.e., leaf interface); the Aleaf device 1021 learns the MAC address 3 of the OLT 1013 and generates a MAC address table entry c.
  • the MAC address table entry b indicates that the message will be forwarded through link 1 (i.e., leaf interface)), the Sleaf device 1021 may learn the MAC address 3 of the OLT 1013 and generates a MAC address table entry c.
  • the MAC address table entry b indicates that the message will be forwarded through link 1 (i.e., leaf interface)), 31 learns the MAC addresses of other UP devices (such as UP device 1042, UP device 1043, etc.), and the Sleaf device 1031 sends a MAC route to the Aleaf device 1021 (which carries the MAC address of each UP device, for example, the Sleaf device 1031 sends a MAC route carrying the MAC address 4 of the UP device 1043 to the Aleaf device 1021, assuming that the MAC path carries root indication information.
  • the Aleaf device 1021 generates a MAC address table entry d carrying the root identifier based on the MAC route).
  • the Sleaf device 1031 learning the MAC addresses of other UP devices, and the Sleaf device 1031 sending a MAC route carrying the MAC addresses of other UP devices to the Aleaf device 1021, refer to the description of the relevant technology, which will not be repeated in the embodiments of the present application.
  • the method includes:
  • the Sleaf device 1031 receives the message c from the UP device 1041 through the leaf interface.
  • the Sleaf device 1031 may receive the message c from the UP device 1041 through the interface of link5 (ie, the leaf interface).
  • UP device 1041 can be understood as a UP device that needs to perform traffic isolation with OLT 1011.
  • message c can be understood as a feedback message sent by UP device 1041 after receiving the broadcast message sent by OLT 1011.
  • the Sleaf device 1031 forwards the packet c to the Aleaf device 1021 through the default MAC address entry 2 .
  • the Sleaf device 1031 can search the MAC address table entry according to the destination address of the message c (i.e., MAC address 1), and then hit the default MAC address table entry 2. However, unlike the above S205, since the default MAC address table entry 2 does not have a leaf identifier, the Sleaf device 1031 cannot use the default MAC address table entry 2 to determine whether to discard the message c (i.e., perform unicast traffic isolation). Then, the Sleaf device 1031 forwards the message c to the Aleaf device 1021 through the UMR.
  • the Sleaf device 1031 forwards the message c to the Aleaf device 1021 through the UMR.
  • the Aleaf device 1021 can, on the one hand, determine the leaf attribute corresponding to the source MAC address (i.e., MAC address 2) of the message c according to the MAC address table entry a (including MAC address 2 and leaf identifier) generated by the above S306; on the other hand, according to the destination address of the message c (i.e., MAC address 1), determine the MAC address table entry b (indicating that the message will be forwarded through the leaf interface), and therefore discard the message c according to the rules of the E-tree, thereby achieving unicast traffic isolation.
  • the source MAC address i.e., MAC address 2
  • the destination address of the message c i.e., MAC address 1
  • determine the MAC address table entry b indicating that the message will be forwarded through the leaf interface
  • the method further includes:
  • the Aleaf device 1021 forwards the message d.
  • the Aleaf device 1021 can determine the MAC address table entry b (indicating that the message is forwarded through the leaf interface (i.e., the interface of link1)) according to the destination address of the message d (i.e., MAC address 1). In addition, the Aleaf device 1021 also determines the MAC address table entry c including the root identifier according to the source MAC address of the message d. Therefore, according to the rules of the E-tree, the Aleaf device 1021 continues to forward the message d, thereby ensuring that the messages that do not require unicast traffic isolation can be forwarded smoothly.
  • the ACs corresponding to the same EVPN instance or BD on the device configured with the UMR function include both ACs with leaf attributes and ACs with root attributes.
  • the EVPN instance or BD cannot be configured as an E-tree leaf node.
  • link1 and link2 correspond to the same EVPN instance on the Aleaf device 1021, where link1 is a leaf attribute and link2 is a root attribute.
  • the EVPN instance or BD on the Aleaf device 1021 cannot be configured as an E-tree leaf Node.
  • unicast traffic isolation can be achieved by the implementation method shown in Figure 3 above.
  • link1 in Figure 1 is a leaf attribute
  • link2 is a root attribute
  • link5 is a leaf attribute
  • the process of UP device 1041 sending a message to OLT 1011 can refer to the contents of S301-S309 above, which will not be repeated here.
  • the method includes:
  • a first communication device receives a first message from a second communication device through a leaf interface.
  • the first communication device may specifically be the Sleaf device 1031 in FIG. 2
  • the second communication device may be the UP device 1041 in FIG. 2
  • the message received by the first communication device may be the message a in FIG. 2 .
  • S401 can be implemented through the content of S204 above.
  • the default MAC address entry includes a leaf identifier and a MAC address of all 0s. Specifically, the default MAC address entry may be the default MAC address entry 1 in FIG.
  • S402 can be implemented through the content of S205 above.
  • the method further includes:
  • the first communication device receives a UMR from a third communication device, wherein the UMR carries leaf indication information.
  • the third communication device may be the Aleaf device 1021 in FIG2 .
  • the UMR received by the first communication device may be the UMR-1 in FIG2 .
  • the UMR may be an EVPN MAC route.
  • the UMR may be an EVPN MAC route with a destination MAC address of all zeros.
  • the UMR received by the first communication device carries an E-tree extended group attribute, wherein the E-tree extended group attribute includes leaf indication information.
  • S403 can be implemented through the content of S202 above.
  • the first communication device generates a default MAC address table entry including a leaf identifier according to the UMR.
  • S404 can be implemented through the content of S203 above.
  • the method further includes:
  • the first communication device receives a second message
  • the first communication device searches for a matching MAC address entry according to the destination MAC address of the second message. After the MAC address entry includes a root identifier, the first communication device forwards the second message.
  • the content of S406 can be implemented through the content of S207 above.
  • Figures 8 and 9 respectively introduce the implementation process of the method described in Figure 7 from the perspective of control flow. Specifically, as shown in Figure 8, the method includes:
  • a first communication device receives a UMR from a second communication device.
  • the UMR includes leaf indication information.
  • the first communication device may be the Sleaf device 1031 in FIG2
  • the second communication device may be the Aleaf device 1021 in FIG2
  • the UMR received by the first communication device may be the UMR-1 in FIG2 .
  • the UMR may be an EVPN MAC route.
  • the UMR may be an EVPN MAC route with a destination MAC address of all zeros.
  • the UMR carries an E-tree extended community attribute, wherein the E-tree extended community attribute includes leaf indication information.
  • S501 can be implemented through the content of S202 above.
  • the first communication device generates a default MAC address table entry including a leaf identifier according to the UMR.
  • S502 can be implemented through the content of S203 above.
  • the method provided in the embodiment of the present application includes:
  • a first communication device generates a UMR, wherein the UMR carries leaf indication information.
  • the leaf indication information is used to indicate that the UMR has a leaf attribute. That is, the above UMR can be used to indicate the generation of a default MAC address table entry including a leaf identifier.
  • the first communication device may specifically be the Aleaf device 1021 in FIG2 .
  • the UMR generated by the first communication device may specifically be the UMR-1 in FIG2 .
  • S601 can be implemented through the content of S201 above.
  • S602 The first communication device sends the UMR to the second communication device.
  • the second communication device may specifically be the Sleaf device 1031 in FIG. 2 .
  • the UMR may be an EVPN MAC route.
  • the UMR may be an EVPN MAC route with a destination MAC address of all 0s.
  • the UMR carries an E-tree extended community attribute, which includes leaf indication information.
  • S602 can be implemented through the content of S202 above.
  • the method provided in the embodiment of the present application may further include:
  • a second communication device receives a first message from a first communication device.
  • the first message may be a message forwarded by the first communication device to the second communication device through a default MAC address entry.
  • the second communication device may be the Aleaf device 1021 in Figure 6, and the first communication device may be the Sleaf device 1031 in Figure 6.
  • the message received by the second communication device may be the message c in Figure 6.
  • S701 can be implemented through the content of S308 above.
  • S702 can be implemented through the content of S309 above.
  • the method further includes:
  • the second communication device receives a MAC route from the first communication device.
  • the MAC route includes a source MAC address of the first message and leaf indication information, wherein the leaf indication information indicates that the MAC route has a leaf attribute.
  • S703 can be implemented through the content of S305 above.
  • S704 The second communication device generates a MAC address entry according to the MAC route.
  • the MAC address entry includes a leaf identifier and a source MAC address of the first message. Specifically, the MAC address entry is used to indicate a corresponding relationship between the first MAC address and the leaf attribute.
  • S704 can be implemented through the content of S306 above.
  • the method further includes:
  • S705 The second communication device receives a second message.
  • the second communication device forwards the second message.
  • S705 can be implemented through the content of S310 above.
  • the device provided by the embodiment of the present application is described below.
  • Figure 9 it is a schematic diagram of the structure of a communication device provided by the embodiment of the present application.
  • the communication device 80 can be used to implement the function of the Aleaf device 1021 in Figure 2, Figure 5 or Figure 6, or the communication device 80 can be used to implement the function of the Sleaf device 1031 in Figure 2, Figure 5 or Figure 6, or the communication device 80 can be used to implement the function of the first communication device in Figure 7 or Figure 8, or the communication device 80 can be used to implement the function of the second communication device in Figure 9 or Figure 10.
  • the communication device 80 includes one or more of a receiving unit 801, a processing unit 802, and a sending unit 803. These units can perform the corresponding functions of each device in the above method example.
  • the communication device 80 may implement the function of the first communication device in FIG. 7 .
  • the receiving unit 801 is configured to receive a first message from the second communication device through a leaf interface.
  • the processing unit 802 is configured to discard the first message in response to determining that the first message is forwarded through a default media access control MAC address entry.
  • the default MAC address entry includes a leaf identifier and a MAC address of all 0s.
  • the receiving unit 801 is further configured to receive an unknown MAC route UMR from a third communication device, where the UMR carries leaf indication information, and the leaf indication information indicates that the UMR has a leaf attribute.
  • the processing unit 802 is further configured to generate a default MAC address entry according to the UMR.
  • the UMR carries an Ethernet multicast E-tree extended community attribute, which includes leaf indication information.
  • the leaf indication information is a leaf identifier.
  • the first communication device is a Sleaf device
  • the third communication device is an Aleaf device.
  • the receiving unit 801 is further configured to receive a second message through a leaf interface.
  • the processing unit 802 is further configured to search for a matching MAC address entry according to the destination MAC address of the second message, where the MAC address entry includes a root identifier.
  • the processing unit 802 is further configured to forward the second message.
  • the communication device 80 may implement the function of the first communication device in FIG. 8 .
  • the receiving unit 801 is configured to receive an unknown medium access control route UMR from the second communication device, where the UMR carries leaf indication information, and the leaf indication information indicates that the UMR has a leaf attribute.
  • the processing unit 802 is configured to generate a default MAC address table entry according to the UMR, wherein the default MAC address table entry includes a leaf identifier and a MAC address of all 0s.
  • the UMR carries an Ethernet multicast E-tree extended community attribute, which includes leaf indication information.
  • the leaf indication information is a leaf identifier.
  • the first communication device is a Sleaf device
  • the second communication device is an Aleaf device.
  • the communication device 80 may implement the function of the second communication device in FIG. 9 .
  • the processing unit 802 is configured to generate an unknown medium access control route UMR, where the UMR carries leaf indication information, and the leaf indication information indicates that the UMR has a leaf attribute.
  • the sending unit 803 is configured to send the UMR to the first communication device.
  • the UMR carries Ethernet multicast E-tree extended community attributes; the E-tree extended community attributes include leaf indication information.
  • the second communication device is an Aleaf device
  • the first communication device is a Sleaf device.
  • the communication device 80 may implement the function of the second communication device in FIG. 10 .
  • the receiving unit 801 is configured to receive a first message from a first communication device.
  • the processing unit 802 is configured to discard the first message in response to determining a first MAC address table entry indicating forwarding the message through a leaf interface according to a destination MAC address of the first message, and determining a second MAC address table entry including a leaf identifier according to a source MAC address of the first message.
  • the receiving unit 801 is further configured to receive a MAC route from the first communication device; the MAC route includes a source MAC address and leaf indication information of the message.
  • the processing unit 802 is further configured to generate a second MAC address entry according to the MAC route.
  • the leaf indication information is a leaf identifier.
  • the receiving unit 801 is further configured to receive a second message
  • the processing unit 802 is further configured to determine, according to the destination MAC address of the second message, a first MAC address table entry indicating that the message is forwarded through a leaf interface, and to determine, according to the source MAC address of the second message, a third MAC address table entry including a root identifier;
  • the processing unit 802 is further configured to forward the second message.
  • the second communication device is an Aleaf device
  • the first communication device is a Sleaf device.
  • Fig. 12 is another possible structural diagram of the communication device involved in the above method embodiment.
  • the communication device 90 can be used to implement the function of the Aleaf device 1021 in Fig. 2, Fig. 5 or Fig. 6, or the communication device 90 can be used to implement the function of the Sleaf device 1031 in Fig. 2, Fig. 5 or Fig. 6, or the communication device 90 can be used to implement the function of the first communication device in Fig. 7 or Fig. 8, or the communication device 90 can be used to implement the function of the second communication device in Fig. 9 or Fig. 10.
  • the communication device 90 includes: a processor 901, a communication interface 902, and all or part of the hardware in a memory 903.
  • the number of processors 901 in the communication device 90 may be one or more, and one processor is taken as an example in FIG10 .
  • the processor 901, the communication interface 902, and the memory 903 may be connected via a bus system or other means, and FIG10 takes the connection via a bus system 904 as an example.
  • the processor 901 may be a central processor unit (CPU), a network processor (NP) or a combination of a CPU and a NP.
  • the processor 901 may also include a hardware chip.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof.
  • the PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.
  • the communication interface 902 is used to receive and send data.
  • the communication interface 902 may include a receiving interface and a sending interface.
  • the receiving interface may be used to receive data
  • the sending interface may be used to send data.
  • the number of the communication interface 902 may be one or more.
  • Memory 903 may include volatile memory (volatile memory), such as random-access memory (RAM); memory 3003 may also include non-volatile memory (non-volatile memory), such as flash memory (flash memory), hard disk drive (HDD) or solid-state drive (SSD); memory 3003 may also include a combination of the above-mentioned types of memory.
  • volatile memory such as random-access memory (RAM)
  • non-volatile memory such as flash memory (flash memory), hard disk drive (HDD) or solid-state drive (SSD)
  • flash memory flash memory
  • HDD hard disk drive
  • SSD solid-state drive
  • memory 3003 may also include a combination of the above-mentioned types of memory.
  • the memory 903 stores an operating system and a program, an executable module or a data structure, or a subset thereof, or an extended set thereof, wherein the program may include various operating instructions for implementing various operations.
  • the operating system may include various system programs for implementing various basic services and processing hardware-based tasks.
  • the processor 901 may read the program in the memory 903 to implement the method provided in the embodiment of the present application.
  • the memory 903 may be a storage device in the communication device 90 , or may be a storage device independent of the communication device 90 .
  • the bus system 904 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc.
  • the bus system 3004 may be divided into an address bus, a data bus, a control bus, etc.
  • FIG10 only uses one thick line, but does not mean that there is only one bus or one type of bus.
  • Figure 11 is a structural diagram of another communication device provided in an embodiment of the present application.
  • the communication device 100 can be used to implement the function of the Aleaf device 1021 in Figure 2, Figure 5 or Figure 6, or the communication device 100 can be used to implement the function of the Sleaf device 1031 in Figure 2, Figure 5 or Figure 6, or the communication device 90 can be used to implement the function of the first communication device in Figure 7 or Figure 8, or the communication device 90 can be used to implement the function of the second communication device in Figure 9 or Figure 10.
  • the communication device 100 includes: a main control board 1001 and an interface board 1003 .
  • the main control board 1001 is also called a main processing unit (MPU) or a route processor card.
  • the main control board 1001 controls and manages various components in the communication device 100, including routing calculation, device management, device maintenance, and protocol processing functions.
  • the main control board 1001 includes: a central processing unit 10011 and a memory 10012.
  • the interface board 1003 is also called a line processing unit (LPU), a line card or a service board.
  • the interface board 1003 is used to provide various service interfaces and realize the forwarding of data packets.
  • the service interface includes but is not limited to an Ethernet interface, a POS (Packet over SONET/SDH) interface, etc.
  • the Ethernet interface is, for example, a flexible Ethernet service interface (FlexE Clients).
  • the interface board 1003 includes: a central processor 10031, a network processor 10032, an address table entry memory 10034 and a physical interface card (PIC) 10033.
  • PIC physical interface card
  • the central processor 10031 on the interface board 1003 is used to control and manage the interface board 1003 and communicate with the central processor 10011 on the main control board 1001 .
  • the network processor 10032 is used to implement message forwarding processing.
  • the network processor 10032 may be in the form of a forwarding chip.
  • the processing of uplink messages includes: message inbound interface processing, forwarding table search; the processing of downlink messages includes forwarding table search, etc.
  • the physical interface card 10033 is used to implement the docking function of the physical layer, and the original traffic enters the interface board 1003 from this, and the processed message is sent from the physical interface card 10033.
  • the physical interface card 10033 includes at least one physical interface, which is also called a physical port.
  • the physical interface card 10033 is also called a daughter card, which can be installed on the interface board 1003 and is responsible for converting the optical signal into a message and forwarding the message to the network processor 10032 for processing after checking the legitimacy of the message.
  • the central processor 10031 of the interface board 1103 can also perform the functions of the network processor 10032, such as implementing software forwarding based on a general-purpose CPU, so that the network processor 10032 is not required in the physical interface card 10033.
  • the communication device 100 includes multiple interface boards.
  • the communication device 100 also includes an interface board 1004 .
  • the interface board 1004 includes: a central processor 10041 , a network processor 10042 , an address table entry memory 10044 and a physical interface card 10043 .
  • the communication device 100 further includes a switching fabric board 1002.
  • the switching fabric board 1002 may also be referred to as a switch fabric unit (SFU).
  • SFU switch fabric unit
  • the switching fabric board 1002 is used to complete data exchange between the interface boards.
  • the interface board 1003 and the interface board 1004 may communicate via the switching fabric board 1002.
  • the main control board 1001 and the interface board 1003 are coupled.
  • the main control board 1001, the interface board 1003 and the interface board 1004, and the The network changer boards 1002 are connected to the system backplane via the system bus to achieve intercommunication.
  • an inter-process communication (IPC) channel is established between the main control board 1001 and the interface board 1003, and the main control board 1001 and the interface board 1003 communicate through the IPC channel.
  • IPC inter-process communication
  • the communication device 100 includes a control plane and a forwarding plane.
  • the control plane includes a main control board 1001 and a central processor 10031.
  • the forwarding plane includes various components for performing forwarding, such as an address table entry memory 10034, a physical interface card 10033, and a network processor 10032.
  • the control plane performs functions such as a router, generating a forwarding table, processing signaling and protocol messages, and configuring and maintaining the status of the device.
  • the control plane sends the generated forwarding table to the forwarding plane.
  • the network processor 10032 forwards the message received by the physical interface card 10033 based on the forwarding table sent by the control plane.
  • the forwarding table sent by the control plane can be stored in the address table entry memory 10034. In some embodiments, the control plane and the forwarding plane can be completely separated and not on the same device.
  • processing unit 802 in the communication device 80 may be equivalent to the central processing unit 10011 or the central processing unit 10031 in the communication device 100 .
  • main control boards there may be one or more main control boards, and when there are multiple boards, they may include a primary main control board and a backup main control board.
  • the communication device 100 may have at least one switching network board, and data exchange between multiple interface boards is achieved through the switching network board, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of the communication device 100 with a distributed architecture are greater than those of the device with a centralized architecture.
  • the communication device 100 may have only one board, that is, no switching network board, and the functions of the interface board and the main control board are integrated on the board.
  • the central processor on the interface board and the central processor on the main control board can be combined into one central processor on the board to perform the functions of the two.
  • This type of device has low data exchange and processing capabilities (for example, a low-end switch or router).
  • the specific architecture to be adopted depends on the specific networking deployment scenario.
  • the above-mentioned communication device can be implemented as a virtualized device.
  • the virtualized device can be a virtual machine (VM) running a program for sending message functions, and the virtual machine is deployed on a hardware device (for example, a physical server).
  • a virtual machine refers to a complete computer system with complete hardware system functions simulated by software and running in a completely isolated environment.
  • the virtual machine can be configured as a communication device.
  • the functions of the communication device can be implemented based on a general physical server in combination with network function virtualization (NFV) technology.
  • NFV network function virtualization
  • the communication device mentioned in the embodiments of the present application may be a network device such as a switch or a router, or may be a component of a network device, such as a single board or a line card on the network device, or may be a functional module on the network device, or may be a chip for implementing the method of the present application, and the embodiments of the present application do not make specific limitations.
  • the interface circuit in the chip may be used to perform the receiving or sending operation in the communication device, and the processor in the chip may be used to perform the processing operation.
  • the embodiment of the present application further provides a chip, including a processor and an interface circuit, the interface circuit is used to receive instructions and transmit them to the processor; the processor can be used to execute the operations of each communication device in the above communication method.
  • the processor is coupled to a memory, and the memory is used to store programs or instructions.
  • the chip implements the method in any of the above method embodiments.
  • the processor in the chip may be one or more.
  • the processor may be implemented by hardware and/or software.
  • the processor may be a logic circuit, an integrated circuit, etc.
  • the processor may be a general-purpose processor implemented by reading software code stored in a memory.
  • the memory in the chip may be one or more.
  • the memory may be integrated with the processor or may be separately provided with the processor, which is not limited in the present application.
  • the memory may be a non-transient processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip or may be provided on different chips.
  • the present application does not specifically limit the type of memory and the arrangement of the memory and the processor.
  • the chip can be a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips.
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • SoC system on chip
  • CPU central processor unit
  • NP network processor
  • DSP digital signal processor
  • MCU microcontroller unit
  • PLD programmable logic device
  • An embodiment of the present application also provides a computer-readable storage medium, including instructions or computer programs, which, when executed on a processor, enable the processor to execute the communication method provided in the above embodiment.
  • the embodiments of the present application also provide a computer program product including instructions or a computer program, which, when executed on a processor, enables a communication device to execute the message forwarding method provided in the above embodiments.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of units is only a logical business division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments of the present application.
  • Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another.
  • Storage media can be any available media that a general or special-purpose computer can access.

Landscapes

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

Abstract

本申请提供一种通信方法及装置。该方法包括：第一通信装置通过leaf接口接收来自第二通信装置的第一报文。响应于确定通过缺省MAC地址表项来转发第一报文，第一通信装置丢弃第一报文；其中，缺省MAC地址表项包括leaf标识和全0的MAC地址。本申请用于实现流量隔离。

Description

通信方法及装置
本申请要求于2022年11月1日提交中国专利局、申请号为202211354585.8、申请名称为“通信方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种通信方法及装置。
背景技术
目前，在城域网等大型网络中，可以通过对没有互访需求的设备之间进行流量隔离，以达到提高数据的传输安全性、提高网络的传输效率等效果。
因此，如何高效、便捷地实现流量隔离，这是目前急需解决的问题。
发明内容
本申请提供一种通信方法及装置，用于高效、便捷地实现流量隔离。
第一方面，提供一种通信方法，该方法包括：第一通信装置通过leaf接口接收来自第二通信装置的第一报文。响应于确定通过缺省MAC地址表项来转发第一报文，则第一通信装置丢弃该报文。其中，缺省MAC地址表项包括leaf标识和全0的MAC地址。
上述方法中，当第一通信装置通过leaf接口接收到第一报文，并且确定需要通过包括leaf标识的缺省MAC地址表项来转发第一报文时，则第一通信装置丢弃该报文。其中，缺省MAC地址表项为根据UMR生成的MAC地址表项。这样一来，当配置UMR功能的网络设备(下文称为第三通信装置)的EVPN实例或BD下的AC均为leaf属性的AC时，可以通过上述方法实现单播流量隔离。具体的，一方面若报文对应缺省MAC地址表项并且缺省MAC地址表项包括与E-tree中的leaf属性相对应的leaf标识，则说明该报文在通过缺省MAC地址表项转发至第三通信装置后还需要通过leaf属性的AC进行后续转发(因为第三通信装置的EVPN实例或BD下的AC均为leaf属性的AC)。作为示例，上述的leaf标识可以为用于指示leaf属性的至少一个bit。以1个bit为例，bit为0时表示leaf标识(即指示对应的AC为leaf属性)，bit为1时表示root标识(即指示对应的AC为root属性)。再例如，其中leaf标识可以为E-tree扩展团体属性中的一个值或一个字符串等。一个具体的实现中，该值或字符串携带在E-tree扩展团体属性的value字段中，用于指示对应的AC具有leaf属性。另一方面，第一通信装置是通过leaf接口接收到的报文，那么结合上述两方面可以确定该报文来自于leaf接口并还需要通过leaf属性的AC进行后续转发，因此通过第一通信装置丢弃该报文便实现了单播流量隔离。
另外，可以理解的是，上述方法中所称“通过缺省MAC地址表项转发”也可以称为“通过UMR转发”。其中，缺省MAC地址表项即为基于UMR生成的转发表项。从控制面的角度来讲，UMR是控制面的路由，下发到转发面时UMR就对应缺省MAC地址表项。因此，在本申请中“通过缺省MAC地址表项转发”即就是“通过UMR转发”。因为上述方法中是从转发面角度描述的，因此采用了“通过缺省MAC地址表项转发”这一表述。本申请中若无特别说明，对于缺省MAC地址表项和UMR之间的关系均可做上述理解。
在一种实现方式中，该方法还包括：第一通信装置接收来自第三通信装置的UMR，UMR携带leaf指示信息，该leaf指示信息指示UMR具有leaf属性。第一通信装置根据该UMR，生成包括上述包括leaf标识的缺省MAC地址表项。
上述实现方式中，可以通过第三通信装置向第一通信装置发送携带leaf指示信息的UMR的这一方式，从而使得第一通信装置在接收到该UMR后，可以根据该UMR建立包括leaf标识的缺省MAC地址表项。这样一来，当配置UMR功能的第三通信装置的EVPN实例或BD下的AC均为leaf属性的AC时，可以通过上述方法实现单播流量隔离。
在一种实现方式中，上述UMR中携带E-tree扩展团体属性，该E-tree扩展团体属性中包括 leaf指示信息。
上述实现方式中，通过将leaf指示信息携带在UMR中的E-tree扩展团体属性中，从而使得第一通信装置在接收到该UMR后，可以根据UMR中的E-tree扩展团体属性，确定该UMR与leaf属性存在对应关系，以便第一通信装置建立包括leaf标识的缺省MAC地址表项。
在一种实现方式中，上述leaf指示信息为leaf标识。
上述实现方式中，将缺省MAC地址表项中的leaf标识和UMR中的leaf指示信息，统一使用同样的内容，从而便于数据的管理。例如，第一通信装置在接收到UMR后，可以将UMR的leaf指示信息的内容直接拷贝至缺省MAC地址表项中，作为缺省MAC地址表项中的leaf标识。从而有助于快速生成缺省MAC地址表项。
在一种实现方式中，第一通信装置为Sleaf设备，第二通信装置为UP设备，第三通信装置为Aleaf设备。
上述实现方式中，通过将本申请提供的方法应用在Spine-leaf网络中，将第一通信装置作为Sleaf设备，将第二通信装置作为UP设备，将第三通信装置作为Aleaf设备，从而可以在Aleaf设备上配置UMR功能的情况下，在Sleaf设备上进行单播流量隔离。
在一种实现方式中，上述UMR为EVPN MAC路由。
在一种实现方式中，该方法还包括：第一通信装置通过leaf接口接收第二报文。第一通信装置根据第二报文的目的MAC地址查找匹配的MAC地址表项，该MAC地址表项包括root标识。第一通信装置转发第二报文。
通过上述实现方式，当第一通信装置通过leaf接口接收到报文时，若确定该报文的目的MAC地址对应的地址表项包括root标识时，则继续转发该报文，从而可以保证不需要要进行单播流量隔离的报文能够被顺利转发。
第二方面，提供一种通信方法，包括：第一通信装置接收来自第二通信装置的UMR，该UMR携带leaf指示信息，该leaf指示信息指示UMR具有leaf属性。第一通信装置根据该UMR，生成缺省MAC地址表项，该缺省MAC地址表项包括leaf标识和全0的MAC地址。
上述方法中，通过第二通信装置向第一通信装置发送携带leaf指示信息的UMR的这一方式，从而使得第一通信装置在接收到该UMR后，可以根据该UMR建立包括leaf标识的缺省MAC地址表项。这样一来，当配置UMR功能的第二通信装置的EVPN实例或BD下的AC均为leaf属性的AC时，可以通过上述方法实现单播流量隔离。具体的，第一通信装置通过leaf属性接收到的报文后，若该报文对应上述缺省MAC地址表项(即包括leaf标识的缺省MAC地址表项)，则说该报文在通过UMR转发至第二通信装置后还需要通过leaf属性的AC进行后续转发，这样一来便可以通过由第一通信装置丢弃该报文的方式，实现单播流量隔离。
在一种实现方式中，UMR中携带E-tree扩展团体属性。其中，该E-tree扩展团体属性中包括leaf指示信息。
上述实现方式中，通过将leaf指示信息携带在UMR中的E-tree扩展团体属性中，从而使得第一通信装置在接收到该UMR后，可以根据UMR中的E-tree扩展团体属性，确定该UMR与leaf属性存在对应关系，以便第一通信装置建立包括leaf标识的缺省MAC地址表项。
在一种实现方式中，上述leaf指示信息为leaf标识。
上述实现方式中，将缺省MAC地址表项中的leaf标识和UMR中的leaf指示信息，统一使用同样的内容，从而便于数据的管理。例如，第一通信装置在接收到UMR后，可以将UMR的leaf指示信息的内容直接拷贝至缺省MAC地址表项中，作为缺省MAC地址表项中的leaf标识。从而有助于快速生成缺省MAC地址表项。
在一种实现方式中，第一通信装置为Sleaf设备，第二通信装置为Aleaf设备。
上述实现方式中，通过将本申请提供的方法应用在Spine-leaf网络中，将第一通信装置作为Sleaf设备，将第三通信装置作为Sleaf设备，从而可以在Aleaf设备上配置UMR功能的情况下，在Sleaf设备上进行单播流量隔离。
在一种实现方式中，上述UMR为EVPN MAC路由。
第三方面，提供一种通信方法，包括：第二通信装置生成UMR，该UMR中携带leaf指示信 息；该leaf指示信息用于指示UMR具有leaf属性。第二通信装置将UMR发送至第一通信装置。
上述方法中，可以通过第二通信装置向第一通信装置发送携带leaf指示信息的UMR的这一方式，从而使得第一通信装置在接收到该UMR后，可以根据该UMR建立包括leaf标识的缺省MAC地址表项。这样一来，当配置UMR功能的第二通信装置的EVPN实例或BD下的AC均为leaf属性的AC时，可以通过上述方法实现单播流量隔离。具体的，第一通信装置通过leaf属性接收到的报文后，若该报文对应上述缺省MAC地址表项(即包括leaf标识的缺省MAC地址表项)，则说该报文在通过UMR转发至第二通信装置后还需要通过leaf属性的AC进行后续转发(因为第二通信装置的EVPN实例或BD下的AC均为leaf属性的AC)，这样一来便可以通过由第一通信装置丢弃该报文的方式，实现单播流量隔离。
在一种实现方式中，UMR中携带E-tree扩展团体属性。其中，该E-tree扩展团体属性中包括leaf指示信息。
上述实现方式中，通过将leaf指示信息携带在UMR中的E-tree扩展团体属性中，从而使得第一通信装置在接收到该UMR后，可以根据UMR中的E-tree扩展团体属性，确定该UMR与leaf属性存在对应关系，以便第一通信装置建立包括leaf标识的缺省MAC地址表项。
在一种实现方式中，第二通信装置为Aleaf设备，第一通信装置为Sleaf设备。
上述实现方式中，通过将本申请提供的方法应用在Spine-leaf网络中，将第二通信装置作为Aleaf设备，将第一通信装置作为Sleaf设备，从而可以在Aleaf设备上配置UMR功能的情况下，在Sleaf设备上进行单播流量隔离。
在一种实现方式中，上述UMR为EVPN MAC路由。
第四方面，提供一种通信方法，包括：第二通信装置接收来自第一通信装置的第一报文。响应于确定与第一报文的目的介质访问控制MAC地址匹配的第一MAC地址表项中的第一出接口为叶leaf接口，以及与第一报文的源MAC地址匹配的第二MAC地址表项包括leaf标识，第二通信装置丢弃第一报文。
上述方法中，考虑到当第二通信装置上配置UMR功能时，由于第一通信装置上没有学习第二通信装置上的MAC明细路由，因此导致第一通信装置无法进行单播流量隔离。也就是说，在第一通信装置通过UMR向第二通信装置转发的报文，有可能是需要进行单播流量隔离的报文(即该报文来自于leaf属性的AC，并且该报文还需要通过leaf属性的AC进行后续转发)。这种情况下，可以通过上述方法，由第二通信装置对接收到的报文进行过滤，也就是当根据第一报文的源MAC地址确定出包括leaf标识的第二MAC地址表项(即说明第一报文来自于leaf接口)，并且确定下面需要通过第二通信装置的leaf接口来转发第一报文(即该报文需要通过第二通信装置上leaf接口发送至下一跳设备)时，则第二通信装置丢弃报文，这样一来便达到单播流量隔离的效果。
在一种实现方式中，该方法还包括：第二通信装置接收来自第一通信装置的MAC路由。MAC路由包括第一报文的源MAC地址以及leaf指示信息，leaf指示信息指示MAC路由具有leaf属性。第二通信装置根据MAC路由，生成上文中包括leaf标识的第二MAC地址表项。
通过该实现方式，能够在第二通信装置生成包括leaf标识(另外，还可以包括第一报文的源MAC地址)的MAC地址表项，以便第二通信装置在接收到报文后，根据该MAC地址表项判断该报文是否来自第一通信装置上leaf接口。从而，在确定报文来自第一通信装置上leaf接口，另外确定该报文将通过第二通信装置的叶leaf接口来转发时，由第二通信装置丢弃报文，这样一来便可以达到单播流量隔离的效果。
在一种实现方式中，上述leaf指示信息为leaf标识。
上述实现方式中，将缺省MAC地址表项中的leaf标识和UMR中的leaf指示信息，统一使用同样的内容，从而便于数据的管理。例如，第二通信装置在接收到UMR后，可以将UMR的leaf指示信息的内容直接拷贝至缺省MAC地址表项中，作为缺省MAC地址表项中的leaf标识。从而有助于快速生成缺省MAC地址表项。
在一种实现方式中，该方法还包括：响应于确定第二报文的目的MAC地址所匹配的第三MAC地址表项中的第二出接口为leaf接口，以及与第二报文的源MAC地址所匹配的第四MAC地址表 项包括根root标识。第二通信装置通过第二出接口转发第二报文。
通过上述实现方式，当第二通信装置根据第二报文的目的MAC地址，确定将通过第一通信装置上的leaf接口转发该报文，并且根据第二报文的源MAC地址确定该报文来自root接口时，则继续转发该报文，从而可以保证不需要进行单播流量隔离的报文能够被顺利转发。
在一种实现方式中，第二通信装置为Aleaf设备，第一通信装置Sleaf设备。
上述实现方式中，通过将本申请提供的方法应用在Spine-leaf网络中，将第二通信装置作为Aleaf设备，将第一通信装置作为Sleaf设备，从而可以在Aleaf设备上进行单播流量隔离。
第五方面，提供一种通信装置，应用于第一通信装置，包括：接收单元，用于通过叶leaf接口接收来自第二通信装置的第一报文。处理单元，用于响应于确定通过缺省介质访问控制MAC地址表项来转发第一报文，丢弃第一报文，其中，缺省MAC地址表项包括leaf标识和全0的MAC地址。
在一种实现方式中，接收单元，还用于接收来自第三通信装置的未知MAC路由UMR，UMR携带leaf指示信息，leaf指示信息指示UMR具有leaf属性。处理单元，还用于根据UMR，生成缺省MAC地址表项。
在一种实现方式中，UMR中携带以太网多播E-tree扩展团体属性；E-tree扩展团体属性中包括leaf指示信息。
在一种实现方式中，leaf指示信息为leaf标识。
在一种实现方式中，第一通信装置为Sleaf设备，第三通信装置为Aleaf设备。
在一种实现方式中，接收单元，还用于通过leaf接口接收第二报文；处理单元，还用于根据第二报文的目的MAC地址查找匹配的MAC地址表项，MAC地址表项包括根root标识；处理单元，还用于转发第二报文。
第六方面，提供一种通信装置，应用于第一通信装置，包括：接收单元，用于接收来自第二通信装置的未知介质访问控制路由UMR，UMR携带叶leaf指示信息，leaf指示信息指示UMR具有leaf属性；处理单元，用于根据UMR，生成缺省MAC地址表项，其中，缺省MAC地址表项包括leaf标识和全0的MAC地址。
在一种实现方式中，UMR中携带以太网多播E-tree扩展团体属性；E-tree扩展团体属性中包括leaf指示信息。
在一种实现方式中，leaf指示信息为leaf标识。
在一种实现方式中，第一通信装置为Sleaf设备，第二通信装置为Aleaf设备。
第七方面，提供一种通信装置，应用于第一通信装置，包括：处理单元，用于生成未知介质访问控制路由UMR，UMR中携带叶leaf指示信息，leaf指示信息指示UMR具有leaf属性；发送单元，用于将UMR发送至第二通信装置。
在一种实现方式中，UMR中携带以太网多播E-tree扩展团体属性；E-tree扩展团体属性中包括leaf指示信息。
在一种实现方式中，第一通信装置为Aleaf设备，第二通信装置Sleaf设备。
第八方面，提供一种通信装置，应用于第二通信装置，包括：接收单元，用于接收来自第一通信装置的第一报文；处理单元，用于响应于确定与第一报文的目的介质访问控制MAC地址匹配的第一MAC地址表项中的第一出接口为叶leaf接口，以及与第一报文的源MAC地址匹配的第二MAC地址表项包括leaf标识，丢弃第一报文。
在一种实现方式中，接收单元，还用于接收来自第一通信装置的MAC路由；MAC路由包括第一报文的源MAC地址以及leaf指示信息，leaf指示信息指示MAC路由具有leaf属性；处理单元，还用于根据MAC路由，生成第二MAC地址表项。
在一种实现方式中，leaf指示信息为leaf标识。
在一种实现方式中，接收单元，还用于接收第二报文；处理单元，还用于响应于确定所述第二报文的目的MAC地址所匹配的第三MAC地址表项中的第二出接口为leaf接口，以及与所述第二报文的源MAC地址所匹配的第四MAC地址表项包括根root标识，通过第二出接口转发第二报文。
在一种实现方式中，第二通信装置为Aleaf设备，第一通信装置Sleaf设备。
第九方面，提供一种通信装置，包括处理器和存储器，存储器用于存储计算机指令，处理器用于从存储器中调用并运行计算机指令，以实现如上述第一方面或第一方面中任一实现方式或上述第二方面或第二方面中任一实现方式或上述第三方面或第三方面中任一实现方式或上述第四方面或第四方面中任一实现方式的方法。
第十方面，提供一种通信系统，包括第一通信装置和第二通信装置。其中，第一通信装置用于实现如上述第一方面或第一方面中任一实现方式或上述第二方面或第二方面中任一实现方式的方法，第二通信装置用于实现如上述第三方面或第三方面中任一实现方式的方法。
第十一方面，提供一种通信系统，包括第一通信装置和第二通信装置，第一通信装置或第二通信装置用于实现如上述第四方面或第四方面中任一实现方式的方法。
第十二方面，提供一种计算机可读存储介质，计算机可读存储介质中存储有指令，当指令在处理器上运行时，实现如上述第一方面或第一方面中任一实现方式或上述第二方面或第二方面中任一实现方式或上述第三方面或第三方面中任一实现方式或上述第四方面或第四方面中任一实现方式的方法。
第十三方面，提供一种计算机程序产品，包括计算机程序，当计算机程序在处理器上运行时，实现如上述第一方面或第一方面中任一实现方式或上述第二方面或第二方面中任一实现方式或上述第三方面或第三方面中任一实现方式或上述第四方面或第四方面中任一实现方式的方法。
附图说明
图1为本申请实施例提供的一种通信系统的结构示意图之一；
图2为本申请实施例提供的一种通信方法的流程示意图之一；
图3为本申请实施例提供的一种E-tree扩展团体属性的结构示意图；
图4为本申请实施例提供的一种通信系统的结构示意图之二；
图5为本申请实施例提供的一种通信方法的流程示意图之二；
图6为本申请实施例提供的一种通信方法的流程示意图之三；
图7为本申请实施例提供的一种通信方法的流程示意图之四；
图8为本申请实施例提供的一种通信方法的流程示意图之五；
图9为本申请实施例提供的一种通信方法的流程示意图之六；
图10为本申请实施例提供的一种通信方法的流程示意图之七；
图11本申请实施例提供的一种通信装置的结构示意图之一；
图12为本申请实施例提供的一种通信装置的结构示意图之二；
图13为本申请实施例提供的一种通信装置的结构示意图之三。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。
首先，对本申请实施例涉及的相关技术进行介绍：
1、未知MAC路由(unknown media access control route，UMR)，也可称为“UMR路由”，是一种替代MAC明细路由的方案。
通常情况下，MAC路由中包括有具体的MAC地址，以便用于指示该MAC地址作为目的地址的报文的转发。这种包括具体MAC地址的MAC路由，被称为“MAC明细路由”。
而与MAC明细路由不同的是，UMR用于指示当没有与待转发报文相匹配的地址表项时，所做出的选择。
例如，当在设备A上配置UMR功能后，设备A向设备B发送UMR，以使得设备B根据UMR生成缺省MAC地址表项。之后，当设备B接收到报文，并且MAC地址表项中没有与该报文的目的地址相匹配的表项时，则按照缺省MAC地址表项，将该报文转发至设备A。
2、以太网多播(ethernet-tree，E-Tree)，是一种点到多点的业务。在E-Tree中，可以将网络中的接入线路(Attachment Circuit，AC))分为叶(leaf)属性和根(root)属性两种。也可以理解为将AC两端的接口分为leaf接口和root接口，其中，leaf属性的AC的两端为leaf接口，root 属性的AC的两端为root接口。
其中，root接口可以与root接口或leaf接口联通，但是两个leaf接口之间无法联通。
通过这种方式，可以在网络中实现流量隔离。例如，可以通过将没有互访需求的两个设备的接口配置为leaf接口，从而在这两个设备之间实现流量隔离。
3、基于IPv6的段路由(segment routing over IPv6，SRv6)，是一种基于IPv6转发平面的SR技术。SRv6结合了SR的源路由优势和IPv6简洁易扩展的特点，正越来越多的应用在各种边界网关协议(border gateway protocol，BGP)的服务中。
4、路由反射器(route reflector，RR)，是一种路由传递技术。在相关技术中，一方面，边界网关协议(border gateway protocol，BGP)路由传递被认为是按照只传一跳的方式进行传输；另一方面，在实际网络中设备非常多，不太可能自治域(autonomous system，AS)中的两两设备之间都建立内部边界网关协议(internal border gateway protocol，IBGP)连接，但是路由又需要传递下去。为了解决这一问题，可以将一个AS中的一台路由器作为RR，其他路由器作为客户机(client)。客户机与RR之间建立IBGP连接。这样一来，客户机可以将路由信息发送至RR，由RR将路由信息反射给其他客户机，客户机之间不需要建立BGP连接。
5、以太虚拟专用网络(ethernet virtual private network，EVPN)，是一种基于二层网络的VPN技术。目前，EVPN常被用于传递MAC路由信息和IP路由信息，作为VXLAN、SRv6等覆盖(overlay)网络的控制层使用。
6、虚拟专用局域网服务(Virtual Private LAN Service，VPLS)，是在多协议标签交换(Multiprotocol Label Switching，MPLS)或IP骨干网上提供的一种点到多点的L2VPN业务。服务提供商通过在骨干网上为一个用户网络模拟一台连接多个异地站点的虚拟交换机来为用户网络提供VPLS服务。
下面为便于理解本申请实施例所提供技术方案，对本申请实施例的应用场景进行介绍：
如图1所示，为本申请实施例提供的一种通信系统10的结构示意图。
其中，用户设备101(例如，光线路终端(optical line terminal，OLT)，图1中以OLT 1011和OLT 1012为例)通过承载网络连接至用户面(user plane，UP)设备104(图1中以UP设备1041、UP设备1042和UP设备1043为例)。其中，UP设备104为用于对用户设备进行认证管理、以及负责用户报文转发的设备。另外，UP设备104还和控制面(control plane，CP)设备106连接，CP设备106用于管理UP设备的主备角色切换以及负责用户设备的管理和控制。
在承载网络中，采用叶-脊(Leaf-Spine)网络结构。如图1所示，承载网络中包括脊Spine设备105，以及Leaf设备。其中，Leaf设备可以分为Aleaf设备102和Sleaf设备103。
其中，Aleaf设备102可以与用户设备101连接，用于实现接入侧运营商边缘(provider edge，PE)设备的功能。Sleaf设备103可以与UP设备104连接，用于实现网关侧(provider edge，PE)设备的功能。
其中，Spine设备1051和Spine设备1052可以作为RR角色，用于反射路由。
另外，在图1所示通信系统中，承载网络中采用双活(active-active)方式以保障网络的正常运行。如图1中，Aleaf设备1021和Aleaf设备1022为双活设备，也就是说对于网络中的其他设备而言，Aleaf设备1021和Aleaf设备1022作为一个设备提供接入服务。这样一来，当Aleaf设备1021或Aleaf设备1022出现故障时，可以由另一个设备继续提供服务，实现业务的无中断切换。同理，Spine设备1051和Spine设备1052、Sleaf设备1031和Sleaf设备1032，均可以为双活设备。
需要说明的是，下文中若没有特殊说明，将以Aleaf设备1021、Spine设备1051和Sleaf设备1031为主设备为例，对本申请实施例所提供技术方案进行介绍。对于备用设备(如Aleaf设备1022、Spine设备1052和Sleaf设备1032)的运行过程，可以参照对Aleaf设备1021、Spine设备1051和Sleaf设备1031的运行过程的介绍。
另外，在承载网络中，可以通过SRv6隧道承载EVPN VPLS业务(EVPN VPLS over SRv6)。通信系统10中，用户设备101可以通过虚拟局域网(virtual local area network，VLAN)或VLAN 嵌套(802.1Q in 802.1Q，QinQ)连接至Aleaf设备102。同理，UP设备104也可以通过VLAN或QinQ连接至Sleaf设备103。
在上述通信系统10中，一方面，可以利用E-Tree，对没有互访需求的设备之间进行流量隔离。
以OLT 1011和UP设备1041进行流量隔离为例：可以将OLT 1011和Aleaf设备1021之间的AC(即link1)，和Sleaf设备1031和UP设备1041之间的AC(即link5)，配置为leaf属性，即将上述两条AC对应的设备上的接口配置为leaf接口。
进而，Aleaf设备1021在通过link1学习到OLT 1011的MAC地址1后，向Sleaf设备1031发送MAC路由(携带MAC地址1以及leaf标识)，然后Sleaf设备1031生成MAC地址表项(包括MAC地址1和leaf标识)。另外，Sleaf设备1031在通过link5学习到UP设备1041的MAC地址2后，向Aleaf设备1021发送MAC路由(携带MAC地址2以及leaf标识)，然后Aleaf设备1021生成MAC地址表项(包括MAC地址2和leaf标识)。
进而，当UP设备1041向OLT 1011发送单播报文时：首先，当Sleaf设备1031通过link5接收到该报文时，Sleaf设备1031确定该报文来自leaf接口，另外Sleaf设备1031根据该报文的目的MAC地址(即OLT 1011的MAC地址1)，确定对应leaf属性的MAC地址表项，即确定该报文将发送至leaf接口。进而，Sleaf设备1031丢弃该报文，从而实现单播流量的隔离。
另一方面，在上述通信系统10中，由于Aleaf设备102连接的用户可以非常多，因此Aleaf设备102所学习到的MAC路由可能很多。当Aleaf设备102通过RR(即Spine设备105)将这些MAC路由通告给Sleaf设备103时，由于Sleaf设备103连接的Aleaf设备也可能很多，因此Sleaf设备103需要学习大量的MAC路由。这就导致Sleaf设备103的负荷过大。
为了降低Sleaf设备103的负荷，在相关技术中可以采用在Aleaf设备102上配置UMR功能。具体的，以在Aleaf设备1021上配置UMR功能为例：在Aleaf设备1021向Sleaf设备1031发送UMR后，Sleaf设备1031便可以根据UMR生成缺省MAC地址表项。之后，当Sleaf设备1031接收到发送至OLT 1011或OLT 1012的报文时，即使MAC地址表项中没有与该报文的目的地址(即OLT 1011或OLT 1012的MAC地址)相匹配的表项，Sleaf设备1031也可以按照缺省MAC地址表项将该报文转发至Aleaf设备1021，以完成该报文的转发。
然而，考虑到当采用在Aleaf设备102上配置UMR功能的这一方式时，由于Aleaf设备102只向Sleaf设备103通告UMR路由，而不会向Sleaf设备103通告携带leaf属性的MAC明细路由。这就导致Sleaf设备103无法进行单播流量隔离。依然以图1中link1和link5为leaf属性为例，当Sleaf设备1031接收到来自link5的报文(该报文的目的地址为MAC地址1)时，由于Sleaf设备1031上没有MAC地址1的MAC地址表项(只有UMR转发对应的缺省MAC地址表项)，因此无法感知该报文在后续转发过程中将会经过leaf接口，因此不会丢弃该报文，即无法进行单播流量隔离。
针对上述问题，本申请实施例提供一种通信方法，该通信方法能够在采用UMR的场景中，实现单播流量隔离。下面分两个实现方式，对本申请实施例所提供方法进行介绍：
第一种实现方式，该方法中当在通信系统中一个设备(例如图1中Aleaf设备1021)上配置UMR功能时，该Aleaf设备1021所发出的UMR中可以携带有leaf指示信息，该指示信息指示UMR具有leaf属性，这样一来接收设备(例如图1中Sleaf设备1031)在接收到该UMR后，可以对应生成包括leaf标识的缺省MAC地址表项(其中，leaf标识可以理解为用于指示该缺省MAC地址表项对应leaf属性)。进而，当Sleaf设备1031通过leaf接口接收到报文时，若确定该报文对应包括leaf标识的缺省MAC地址表项，则Sleaf设备1031丢弃该报文。这样一来，便可以对一方面来自Sleaf设备1031上leaf接口，另一方面将通过Aleaf设备1021上的leaf接口传输至下一跳设备的报文，在Sleaf设备1031上实现单播流量隔离。
第二种实现方式，该方法中当在通信系统中一个设备(例如图1中Aleaf设备102)上配置UMR功能时，在Sleaf设备103没有对需要进行单播流量隔离的报文进行丢弃，并且通过UMR转发将该报文转发至Aleaf设备102的情况下，通过在Aleaf设备102上对接收到的满足要求的报文(该报文的源MAC地址对应leaf标识的MAC地址表项，并且该报文需要通过Aleaf设备102 上的leaf接口进行转发)进行丢弃，从而实现单播流量隔离。
下面结合具体场景，对本申请实施例所提供方法进行详细介绍。
第一种场景中，将配置UMR功能的设备上的EVPN实例或桥域(bridge domain，BD)配置为E-tree leaf Node，即将配置UMR功能的设备上EVPN实例或BD对应的AC都配置为leaf属性。例如，link1和link2在Aleaf设备1021上对应同一EVPN实例，则将该EVPN实例配置为E-tree leaf Node具体可以理解为将link1和link2都配置为leaf属性。
具体的，当图1中Aleaf设备1021上link1和link2对应的EVPN实例配置为E-tree leaf Node，并且link5(即Sleaf设备1031和UP设备1041之间的AC)配置为leaf属性的情况下，结合UP设备1041向OLT 1011发送报文的过程，对本申请实施例所提供的方法进行介绍。如图2所示，本申请实施例所提供的方法中控制流的运行过程可以包括：
S201、Aleaf设备1021生成UMR(为便于区分，下文将该UMR称为UMR-1)。
其中，该UMR-1可以用于指示当没有与待转发的报文相匹配的MAC地址表项时，将待转发的报文转发至Aleaf设备1021。
其中，如RFC 7543中的定义，UMR可以为一种EVPN路由。在一种实现方式中，可以将MAC地址为全0的EVPN MAC路由，作为UMR。
其中，该UMR-1可以由Aleaf设备1021中link1和link2对应的EVPN实例生成。
另外，UMR-1中携带leaf指示信息，该leaf指示信息可以用于指示该UMR-1具有leaf属性。具体可以理解为：该leaf标识可以用于指示当采用UMR方式将报文转发至Aleaf设备1021后，Aleaf设备1021在后续转发过程中将通过leaf接口转发该报文。
在一种实现方式中，在本申请实施例中可以将leaf指示信息携带在UMR-1中的扩展团体属性中。
具体的，UMR-1中携带E-tree扩展团体属性。该E-tree扩展团体属性中包括leaf指示信息。
示例性的，图3所示为本申请实施例中示出的一种UMR所携带的E-tree扩展团体属性的报文格式示意图。其中主要包括3个字节的叶标签(leaf label)字段和1个字节的标记(flags)字段，除此之外，还包括2个字节的预留(reserved)字段、1个字节的类型(type)字段、1个字节的子类型(sub-type)字段。其中，leaf label字段中携带有上述leaf指示信息，用于标识发送该E-tree扩展团体属性的设备接口为leaf接口。另外，leaf标识也可以为E-tree扩展团体属性中其他字段中承载的一个值或一个字符串等，该值或字符串携带在E-tree扩展团体属性的value字段中，用于指示对应的AC(或AC对应的设备接口)为leaf属性。另外，Flags字段中的前7位均为0。并且，如果该E-TREE扩展团体属性是为了实现leaf接口之间广播、未知单播、组播流量(Broadcast Unknown-unicast Multicast，BUM)流量的隔离，则Flags字段中最后一位将为0。如果该E-TREE扩展团体属性是为了实现leaf接口之间已知单播流量的隔离，则Flags字段中最后一位将为1。接收到该E-TREE扩展团体属性的设备，通过识别leaf指示信息和Flags字段的最后一位，来实现leaf接口之间的已知单播流量和BUM流量的隔离。
另外，可以理解的是，本申请实施例中也可以将leaf指示信息携带在UMR-1中的其他字段中。例如，可以将leaf指示信息携带在UMR-1中，除E-tree扩展团体属性之外的其他扩展团体属性中。对此本申请实施例中可以不做限制。
另外，可以理解的是，在本申请实施例中，对于UMR-1所携带的leaf指示信息的具体形式可以不做限制。例如，在UMR-1的帧结构中预先设置了一个位(bit)，当该bit为0时表示该UMR-1对应leaf属性(该为0的bit，即可以理解为上述leaf指示信息)；当该bit为1时表示该UMR-1不对应leaf属性，或者说该UMR-1对应root属性(该为1的bit，即可以作为一个root指示信息。该root指示信息可以用于指示当采用UMR方式将报文转发至Aleaf设备1021后，Aleaf设备1021在后续转发过程中不一定通过leaf接口转发该报文)。
再例如，在UMR-1的帧结构中可以包括一个字段，该字段用于指示UMR-1对应leaf属性或是root属性。如上文中的E-tree扩展团体属性，便可以用于指示UMR-1对应leaf属性或是root属性。那么，可以将对应leaf属性的该字段(如上文中的E-tree扩展团体属性)整体作为leaf指 示信息。
S202、Aleaf设备1021将UMR-1发送至Sleaf设备1031。
例如，Aleaf设备1021可以通过作为RR的Spine设备1051，将UMR-1发送至Sleaf设备1031。
S203、Sleaf设备1031根据UMR-1，生成缺省MAC地址表项1。
其中，该缺省MAC地址表项1可以用于指示当没有与待转发的报文相匹配的MAC地址表项时，将待转发的报文转发至Aleaf设备1021。
其中，缺省MAC地址表项1中包括全0的MAC地址，用于指示该表项为缺省MAC地址表项。
另外，缺省MAC地址表项1中还包括leaf标识。该leaf标识可以用于指示当按照缺省MAC地址表项1转发报文时，在后续转发过程中需要通过leaf接口转发该报文。
另外，需要说明的是，本申请实施例中所称“缺省MAC地址表项1中包括leaf标识”，可以理解为是使得缺省MAC地址表项1对应leaf属性的一种实现方式。这样一来，当按照缺省MAC地址表项1转发报文时，则可以确定在后续转发过程中需要通过leaf接口转发该报文。其中，将leaf标识携带在缺省MAC地址表项1中，只是将缺省MAC地址表项1和leaf属性相对应的一种具体表现形式，在实际应用过程中还可以在缺省MAC地址表项中不携带leaf标识，而是只要能够根据缺省MAC地址表项确定leaf属性即可。
另外，可以理解的是，在本申请实施例中，对于缺省MAC地址表项1中所包括的leaf标识的具体形式可以不做限制。例如，在缺省MAC地址表项1中预先设置了一个bit，该bit为0时表示leaf标识；另外，当该bit为1时，则表示root标识。再例如，在缺省MAC地址表项1中可以包括一个字段，该字段用于指示缺省MAC地址表项1对应leaf属性或是root属性。那么，可以将对应leaf属性的该字段整体作为leaf标识。
另外，可以理解的是，上述过程中UMR-1(即Aleaf设备1021向Sleaf设备1031发送的UMR)中所携带的leaf指示信息以及缺省MAC地址表项1(即Sleaf设备1031生成的缺省MAC地址表项)中所携带的leaf标识的作用类似。
因此，在一种实现方式中，上述UMR-1中携带的leaf指示信息，即为缺省MAC地址表项1中所携带的leaf标识。
例如，当Sleaf设备1031生成缺省MAC地址表项1时，可以直接将UMR-1中的leaf指示信息复制到缺省MAC地址表项1中，作为缺省MAC地址表项1中的leaf标识。例如，UMR-1中用为0的一个bit作为leaf指示信息，则可以将“0”复制到缺省MAC地址表项1中预先设置的一个bit中作为leaf标识。
在另一种实现方式中，缺省MAC地址表项1中的leaf标识和UMR-1中的leaf指示信息，可以采用不同形式。例如，UMR-1中用E-tree扩展团体属性作为leaf指示信息，而在缺省MAC地址表项1中采用预先设置的为0的一个bit作为leaf标识(可以理解为Sleaf设备1031在通过读取UMR-1中的E-tree扩展团体属性确定UMR-1中携带有leaf指示信息后，则对应生成缺省MAC地址表项1并将缺省MAC地址表项1中的预先设置的bit置为“0”以表示leaf标识)。
也就是说，在实际应用过程中，本申请实施例中缺省MAC地址表项1中的leaf标识和UMR-1中的leaf指示信息的具体形式可以相同，也可以不同，对此本申请实施例可以不做限制。
另外，在控制流的运行过程中，还可以包括Aleaf设备1021学习OLT的MAC地址、Sleaf设备1031学习各UP设备的MAC地址以及Sleaf设备1031向Aleaf设备1021发送MAC路由(其中携带各UP设备的MAC地址)的过程。对于Aleaf设备1021学习OLT的MAC地址、Sleaf设备1031学习各UP设备的MAC地址，以及Sleaf设备1031向Aleaf设备1021发送MAC路由的过程，可参照相关技术的描述，本申请实施例中不做赘述。
下面结合图2中所示控制流的运行过程，对UP设备1041向OLT 1011发送报文的数据流的运行过程进行介绍。如图2所示，该方法还包括：
S204、Sleaf设备1031通过link5(即leaf属性的AC)对应的接口(即leaf接口)接收来自UP设备1041的报文a。
示例性的，在OLT 1011接入网络后，OLT 1011会向网络中发送广播报文，该广播报文用于 向各UP设备发送OLT 1011的认证信息。Aleaf设备1021在接收到该广播报文后会将该广播报文转发至Sleaf设备1031，Sleaf设备1031在接收到该广播报文后会将该广播报文转发至各个UP设备。各UP设备在接收到该广播报文后会向OLT 1011发送一个反馈报文，用于建立OLT 1011与UP设备之间的连接，以便后续对OLT 1011进行设备认证。考虑到，在OLT 1011的认证过程中，只需要一个UP设备与OLT 1011建立连接即可。因此，可以通过使OLT 1011和部分UP设备之间的流量隔离的方式，避免OLT 1011和所有UP设备都建立连接。
具体的，本申请实施例中，UP设备1041可以理解为需要与OLT 1011进行流量隔离的UP设备。报文a可以理解为UP设备1041接收到OLT 1011发送的广播报文后发送的反馈报文。该方法还包括：
S205、响应于确定通过缺省MAC地址表项1来转发第一报文，Sleaf设备1031丢弃第一报文。
其中，如上文所述，缺省MAC地址表项1中包括leaf标识和全0的MAC地址。
具体的，Sleaf设备1031在接收到报文a后，可以根据报文a的目的MAC地址(即MAC地址1)查找MAC地址表项，进而命中包括leaf标识的缺省MAC地址表项1。也就是说，一方面确定报文a命中了包括leaf标识的缺省MAC地址表项1，另一方面Sleaf设备1031还能够确定报文a是通过leaf接口接收到的，进而Sleaf设备1031按照E-tree的规则丢弃该报文a，从而实现了单播流量隔离。
另外，可以理解的是，上述方法中所称“通过缺省MAC地址表项转发”也可以称为“通过UMR转发”。其中，缺省MAC地址表项即为基于UMR生成的转发表项。从控制面的角度来讲，UMR是控制面的路由，下发到转发面时UMR就对应缺省MAC地址表项。因此，在本申请中“通过缺省MAC地址表项转发”即就是“通过UMR转发”。因为上述方法中是从转发面角度描述的，因此采用了“通过缺省MAC地址表项转发”这一表述。本申请中若无特别说明，对于缺省MAC地址表项和UMR之间的关系均可做上述理解。
在一种实现方式中，本申请实施例中，当Sleaf设备1031通过leaf接口接收到需要转发至其他root属性的AC的报文(称为报文b)时，则Sleaf设备1031则转发该报文b(即不会丢弃该报文b)。
示例性的，如图4所示，用户设备101中还包括OLT 1013，OLT 1013通过link11连接Aleaf设备1021，另外OLT 1013还通过link12连接Aleaf设备1022。其中，link11和link12不属于上述link1-link4所对应的EVPN，并且link11和link12为root属性。当Sleaf设备1031通过leaf接口(如通过对应link5的接口)接收到需要转发至OLT 1013的报文b时，如图5所示，该方法还可以包括：
S206、Sleaf设备1031通过leaf接口接收来自UP设备1041的报文b。
其中，该报文b的目的MAC地址为OLT 1013的MAC地址(即图4中MAC地址2)。
S207、Sleaf设备1031根据报文b的目的MAC地址查找匹配的MAC地址表项，并且该MAC地址表项包括root标识，则Sleaf设备1031转发报文b。
具体的，在OLT 1013接入网络后，Aleaf设备1021可以学习OLT 1013的MAC地址并向Sleaf设备1031发送MAC路由(携带MAC地址2以及root指示信息)。Sleaf设备1031根据该MAC路由，生成MAC地址表项(包括MAC地址2以及root标识)，该MAC地址表项可以用于指示目的地址为MAC地址2的转发，另外MAC地址表项中的root标识用于指示不需要对该报文进行单播流量隔离。进而，Sleaf设备1031在接收到报文b后，可以根据上述MAC地址表项，将报文b转发至Aleaf设备1021。
之后，当Sleaf设备1031将报文b转发至Aleaf设备1021后，Aleaf设备1021可以根据报文b的目的MAC地址将报文转发至OLT 1013，从而完成报文b的转发。
上述实现方式中，当Sleaf设备1031通过leaf接口接收到报文时，若确定该报文的目的MAC地址对应的MAC地址表项包括root标识时，则继续转发该报文，从而可以保证不需要要进行单播流量隔离的报文能够被顺利转发。
上述图2-图5主要是以Aleaf设备1021向Sleaf设备1031发送携带leaf指示信息的UMR-1， 从而在Sleaf设备1031中建立包括leaf标识的缺省MAC地址表项1，进而当Sleaf设备1031通过leaf接口接收到报文a时，在确定需要通过缺省MAC地址表项1(其中包括leaf标识)来转发报文a后，丢弃该报文a的这一实现方式(即上文第一种实现方式)进行介绍。
下面，以图1中Aleaf设备1021上link1和link2对应的EVPN实例配置为E-tree leaf Node，并且link5(即Sleaf设备1031和UP设备1041之间的AC)配置为leaf属性为例，对上文第二种实现方式(即Sleaf设备103没有对需要进行单播流量隔离的报文进行丢弃，通过在Aleaf设备102上对接收到的满足要求的报文进行丢弃，从而实现单播流量隔离)进行介绍。如图6所示，控制流的运行过程可以包括：
S301、Aleaf设备1021生成UMR(下文称为UMR-2)。
其中，与S201中UMR-1类似，该UMR-2可以用于指示当没有与待转发的报文相匹配的MAC地址表项时，将待转发的报文转发至Aleaf设备1021。另外，UMR-2可以为由Aleaf设备1021中link1和link2对应的EVPN实例生成的MAC地址为全0的EVPN MAC路由。
与S201不同的是，S301的UMR-2中没有携带leaf指示信息。
S302、Aleaf设备1021将UMR-2发送至Sleaf设备1031。
例如，Aleaf设备1021可以通过作为RR的Spine设备1051，将UMR-2发送至Sleaf设备1031。
S303、Sleaf设备1031根据UMR-2，生成缺省MAC地址表项2。
其中，与S203中缺省MAC地址表项1类似，缺省MAC地址表项2可以用于指示当没有与待转发的报文相匹配的MAC地址表项时，将待转发的报文转发至Aleaf设备1021。
与S203不同的是，缺省MAC地址表项2没有包括leaf标识，换句话讲缺省MAC地址表项2可以包括root标识。这样一来，Sleaf设备1031只能利用缺省MAC地址表项2确定报文是否需要进行UMR转发，不能利用缺省MAC地址表项2判断对需要进行UMR转发的报文是否丢弃(即进行单播流量隔离)。
S304、Sleaf设备1031通过link5(即leaf属性的AC)学习MAC地址2(即UP设备1041的MAC地址)。
S305、Sleaf设备1031向Aleaf设备1021发送MAC路由。
其中，MAC路由中携带有MAC地址2以及leaf指示信息。
具体的，Sleaf设备1031在学习到MAC地址2后，可以通过发布MAC路由的方式，将MAC地址2发送给网络中其他设备(例如Aleaf设备1021)，其中MAC路由中会携带有leaf指示信息以便进行E-tree的流量隔离。
S306、Aleaf设备1021根据MAC路由，生成MAC地址表项a。
该MAC地址表项中包括MAC地址2以及leaf标识。换句话讲，该MAC地址表项可以用于指示源MAC地址为MAC地址2的报文来自leaf属性的AC。
另外，在控制流的运行过程中，还可以包括Aleaf设备1021学习OLT的MAC地址(例如图6中，Aleaf设备1021学习OLT 1011的MAC地址1，生成MAC地址表项b。该MAC地址表项b指示将通过link1(即leaf接口)转发报文；Aleaf设备1021学习OLT 1013的MAC地址3，生成MAC地址表项c。该MAC地址表项b指示将通过link1(即leaf接口)转发报文)、Sleaf设备1031学习其他UP设备(例如UP设备1042、UP设备1043等)的MAC地址，以及Sleaf设备1031向Aleaf设备1021发送MAC路由(其中携带各UP设备的MAC地址，例如Sleaf设备1031向Aleaf设备1021发送携带UP设备1043的MAC地址4的MAC路由，假设该MAC路径携带root指示信息。另外Aleaf设备1021根据该MAC路由，生成携带root标识的MAC地址表项d)等过程。对于Aleaf设备1021学习OLT的MAC地址、Sleaf设备1031学习其他UP设备的MAC地址，以及Sleaf设备1031向Aleaf设备1021发送携带其他UP设备MAC地址的MAC路由的过程，可参照相关技术的描述，本申请实施例中不做赘述。
下面结合图4中所示控制流的运行过程，对UP设备1041发送目的地址为MAC地址1(即OLT 1011的MAC地址)的报文c的过程进行介绍。如图4所示，该方法包括：
S307、Sleaf设备1031通过leaf接口接收来自UP设备1041的报文c。
例如，Sleaf设备1031可以通过link5的接口(即leaf接口)接收来自UP设备1041的报文c。
与S204中的描述类似，UP设备1041可以理解为需要与OLT 1011进行流量隔离的UP设备，另外报文c可以理解为UP设备1041接收到OLT 1011发送的广播报文后发送的反馈报文。
S308、Sleaf设备1031通过缺省MAC地址表项2将报文c转发至Aleaf设备1021。
具体的，Sleaf设备1031在接收到报文c后，可以根据报文c的目的地址(即MAC地址1)查找MAC地址表项，进而命中缺省MAC地址表项2。其中，与上文S205不同，由于缺省MAC地址表项2没有leaf标识，因此Sleaf设备1031不能利用缺省MAC地址表项2判断对报文c是否丢弃(即进行单播流量隔离)。进而Sleaf设备1031通过UMR转发将报文c至Aleaf设备1021。
S309、响应于确定与报文c的目的MAC地址匹配的MAC地址表项b中的第一出接口为leaf接口，以及与报文c的源MAC地址匹配的MAC地址表项a包括leaf标识，Aleaf设备1021丢弃报文c。
具体的，Aleaf设备1021在接收到报文c后，一方面，根据上述S306生成的MAC地址表项a(其中包括MAC地址2和leaf标识)可以确定报文c的源MAC地址(即MAC地址2)对应leaf属性；另一方面，根据报文c的目的地址(即MAC地址1)可以确定MAC地址表项b(指示将通过leaf接口转发报文)，因此按照E-tree的规则丢弃该报文c，从而实现了单播流量隔离。
在一种实现方式中，当Aleaf设备1021接收到源MAC地址为MAC地址4(MAC地址4UP设备1043的MAC地址)并且目的MAC地址为MAC地址3(即OLT 1013的MAC地址)的报文d时，该方法还包括：
S310、响应于确定报文d的目的MAC地址所匹配的MAC地址表项c中的出接口(即link11对应的接口)为leaf接口，以及与报文d的源MAC地址所匹配的MAC地址表项d包括root标识，则Aleaf设备1021转发该报文d。
具体的，Aleaf设备1021根据报文d的目的地址(即MAC地址1)可以确定MAC地址表项b(指示通过叶leaf接口(即link1的接口)转发报文)，另外Aleaf设备1021根据报文d的源MAC地址还确定出包括root标识的MAC地址表项c，因此按照E-tree的规则，Aleaf设备1021继续转发该报文d，从而可以保证不需要要进行单播流量隔离的报文能够被顺利转发。
第二种场景中，配置UMR功能的设备上同一EVPN实例或BD对应的AC中，既包括leaf属性的AC，也包括root属性的AC。那么，这种情况下则无法将EVPN实例或BD配置为E-tree leaf Node。
例如图1中，link1和link2在Aleaf设备1021上对应同一EVPN实例，其中link1为leaf属性，link2为root属性，此时无法将Aleaf设备1021上EVPN实例或BD配置为E-tree leaf Node。
这样一来，一方面，在第二种场景中无法通过上文图2所示的实现方式(即由Aleaf设备1021向Sleaf设备1031发送携带leaf属性标识的UMR，Sleaf设备1031生成对应leaf属性的缺省MAC地址表项，并根据该缺省MAC地址表项进行丢弃报文)来实现单播流量隔离。
另一方面，在第二种场景中，可以通过上文图3所示的实现方式来实现单播流量隔离。例如，当图1中link1为leaf属性，link2为root属性，并且link5为leaf属性时，UP设备1041向OLT 1011发送报文的过程可参照上文S301-S309的内容，在此不做赘述。
下面结合附图，从单个网络设备的角度，对本申请实施例所提供的方法进行介绍。
具体的，如图7所示，该方法包括：
S401、第一通信装置通过leaf接口接收来自第二通信装置的第一报文。
其中，第一通信装置具体可以为上述图2中Sleaf设备1031，第二通信装置可以为上述图2中UP设备1041，第一通信装置接收的报文可以为图2中的报文a。
具体的，S401具体可以通过上述S204的内容来实现。
S402、响应于确定通过缺省MAC地址表项来转发第一报文，则第一通信装置丢弃第一报文。
其中，缺省MAC地址表项包括leaf标识和全0的MAC地址。具体的，上述缺省MAC地址表项可以为图2中缺省MAC地址表项1。
具体的，S402具体可以通过上述S205的内容来实现。
在一种实现方式中，该方法还包括：
S403、第一通信装置接收来自第三通信装置的UMR。其中，该UMR携带leaf指示信息。
其中，第三通信装置可以为图2中Aleaf设备1021。第一通信装置接收的UMR可以为图2中的UMR-1。
在一种可能的设计中，UMR可以为EVPN MAC路由。例如，UMR可以为目的MAC地址为全0的EVPN MAC路由。
在一种可能的设计中，第一通信装置接收的UMR中携带E-tree扩展团体属性。其中，E-tree扩展团体属性中包括leaf指示信息。
具体的，S403具体可以通过上述S202的内容来实现。
S404、第一通信装置根据UMR，生成包括leaf标识的缺省MAC地址表项。
具体的，S404具体可以通过上述S203的内容来实现。
在一种实现方式中，该方法还包括：
S405、第一通信装置接收第二报文；
S406、第一通信装置根据第二报文的目的MAC地址查找匹配的MAC地址表项，MAC地址表项包括根root标识后，第一通信装置转发第二报文。
具体的，S406的内容可以通过上述S207的内容实现。
下面图8和图9分别从控制流的角度，对图7所描述方法的实现过程进行介绍。具体的，如图8所示，该方法包括：
S501、第一通信装置接收来自第二通信装置的UMR。该UMR包括leaf指示信息。
其中，第一通信装置可以为图2中Sleaf设备1031，第二通信装置可以为图2中Aleaf设备1021。第一通信装置接收的UMR可以为图2中的UMR-1。
在一种可能的设计中，UMR可以为EVPN MAC路由。例如，UMR可以为目的MAC地址为全0的EVPN MAC路由。
在一种实现方式中，UMR中携带E-tree扩展团体属性。其中，E-tree扩展团体属性中包括leaf指示信息。
具体的，S501具体可以通过上述S202的内容来实现。
S502、第一通信装置根据UMR，生成包括leaf标识缺省MAC地址表项。
具体的，S502具体可以通过上述S203的内容来实现。
如图9所示，本申请实施例所提供的方法包括：
S601、第一通信装置生成UMR。其中，UMR中携带leaf指示信息。
其中，leaf指示信息用于指示UMR具有leaf属性。也就是说，上述UMR可以用于指示生成包括leaf标识的缺省MAC地址表项。
其中，第一通信装置具体可以为图2中Aleaf设备1021。第一通信装置所生成的UMR具体可以为图2中UMR-1。
具体的，S601具体可以通过上述S201的内容来实现。
S602、第一通信装置将UMR发送至第二通信装置。
其中，第二通信装置具体可以为图2中Sleaf设备1031。
在一种实现方式中，UMR可以为EVPN MAC路由。例如，UMR可以为目的MAC地址为全0的EVPN MAC路由。
在一种实现方式中，UMR中携带E-tree扩展团体属性。该E-tree扩展团体属性中包括leaf指示信息。
具体的，S602具体可以通过上述S202的内容来实现。
另外，如图10所示，本申请实施例所提供的方法还可以包括：
S701、第二通信装置接收来自第一通信装置的第一报文。
其中，该第一报文可以为第一通信装置通过缺省MAC地址表项转发至第二通信装置的报文。
其中，第二通信装置可以为图6中Aleaf设备1021，第一通信装置可以为图6中Sleaf设备1031。第二通信装置接收的报文可以为图6中报文c。
具体的，S701可以通过上述S308的内容来实现。
S702、响应于确定与第一报文的目的MAC地址匹配的第一MAC地址表项中的第一出接口为叶leaf接口，以及与第一报文的源MAC地址匹配的第二MAC地址表项包括leaf标识，第二通信装置丢弃报文。
具体的，S702可以通过上述S309的内容来实现。
在一种实现方式中，该方法还包括：
S703、第二通信装置接收来自第一通信装置的MAC路由。
其中，MAC路由包括第一报文的源MAC地址以及leaf指示信息。该leaf指示信息指示MAC路由具有leaf属性。
具体的，S703可以通过上述S305的内容来实现。
S704、第二通信装置根据MAC路由，生成MAC地址表项。
其中，该MAC地址表项包括leaf标识和第一报文的源MAC地址。具体的，该MAC地址表项用于指示第一MAC地址与leaf属性的对应关系。
具体的，S704可以通过上述S306的内容来实现。
在一种实现方式中，该方法还包括：
S705、第二通信装置接收第二报文。
S706、响应于确定第二报文的目的MAC地址所匹配的第三MAC地址表项中的第二出接口为leaf接口，以及与第二报文的源MAC地址所匹配的第四MAC地址表项包括根root标识，第二通信装置转发第二报文。
具体的，S705可以通过上述S310的内容来实现。
基于上述方法实施例，下面对本申请实施例所提供的装置进行说明。如图9所示为本申请实施例所提供的一种通信装置的结构示意图。具体的，该通信装置80可以用于实现图图2、图5或图6中Aleaf设备1021的功能，或者该通信装置80可以用于实现图2、图5或图6中Sleaf设备1031的功能，或者该通信装置80可以用于实现图7或图8中第一通信装置的功能，或者该通信装置80可以用于实现图9或图10中第二通信装置的功能。
参照图11，该通信装置80包括接收单元801、处理单元802和发送单元803中的一项或多项。这些单元可以执行上述方法示例中各设备的相应功能。
在一种实现方式中，该通信装置80可以实现图7中第一通信装置的功能。
具体的，接收单元801，用于通过叶leaf接口接收来自第二通信装置的第一报文。
处理单元802，用于响应于确定通过缺省介质访问控制MAC地址表项来转发第一报文，丢弃第一报文。
其中，缺省MAC地址表项包括leaf标识和全0的MAC地址。
可选的，接收单元801，还用于接收来自第三通信装置的未知MAC路由UMR，UMR携带leaf指示信息，leaf指示信息指示UMR具有leaf属性。
处理单元802，还用于根据UMR，生成缺省MAC地址表项。
可选的，UMR中携带以太网多播E-tree扩展团体属性。E-tree扩展团体属性中包括leaf指示信息。
可选的，leaf指示信息为leaf标识。
可选的，第一通信装置为Sleaf设备，第三通信装置为Aleaf设备。
可选的，接收单元801，还用于通过leaf接口接收第二报文。
处理单元802，还用于根据第二报文的目的MAC地址查找匹配的MAC地址表项，MAC地址表项包括根root标识。
处理单元802，还用于转发第二报文。
在另一种实现方式中，该通信装置80可以实现图8中第一通信装置的功能。
具体的，接收单元801，用于接收来自第二通信装置的未知介质访问控制路由UMR，UMR携带叶leaf指示信息，leaf指示信息指示UMR具有leaf属性。
处理单元802，用于根据UMR，生成缺省MAC地址表项，其中，缺省MAC地址表项包括leaf标识和全0的MAC地址。
可选的，UMR中携带以太网多播E-tree扩展团体属性。E-tree扩展团体属性中包括leaf指示信息。
可选的，leaf指示信息为leaf标识。
可选的，第一通信装置为Sleaf设备，第二通信装置为Aleaf设备。
在另一种实现方式中，该通信装置80可以实现图9中第二通信装置的功能。
具体的，处理单元802，用于生成未知介质访问控制路由UMR，UMR中携带叶leaf指示信息，leaf指示信息指示UMR具有leaf属性。
发送单元803，用于将UMR发送至第一通信装置。
可选的，UMR中携带以太网多播E-tree扩展团体属性；E-tree扩展团体属性中包括leaf指示信息。
可选的，第二通信装置为Aleaf设备，第一通信装置Sleaf设备。
在另一种实现方式中，该通信装置80可以实现图10中第二通信装置的功能。
具体的，接收单元801，用于接收来自第一通信装置的第一报文。
处理单元802，用于响应于响应于根据第一报文的目的MAC地址确定指示通过leaf接口转发报文的第一MAC地址表项，并且根据第一报文的源MAC地址确定包括leaf标识的第二MAC地址表项，丢弃第一报文。
可选的，接收单元801，还用于接收来自第一通信装置的MAC路由；MAC路由包括报文的源MAC地址以及leaf指示信息。
处理单元802，还用于根据MAC路由，生成第二MAC地址表项。
可选的，leaf指示信息为leaf标识。
可选的，接收单元801，还用于接收第二报文；
处理单元802，还用于根据第二报文的目的MAC地址确定指示通过叶leaf接口转发报文的第一MAC地址表项，并且根据第二报文的源MAC地址确定包括root标识的第三MAC地址表项；
处理单元802，还用于转发第二报文。
可选的，第二通信装置为Aleaf设备，第一通信装置Sleaf设备。
图12为上述方法实施例中所涉及的通信装置的另一种可能的结构示意图。具体的，该通信装置90可以用于实现图2、图5或图6中Aleaf设备1021的功能，或者该通信装置90可以用于实现图2、图5或图6中Sleaf设备1031的功能，或者该通信装置90可以用于实现图7或图8中第一通信装置的功能，或者该通信装置90可以用于实现图9或图10中第二通信装置的功能。
参照图10，该通信装置90包括：处理器901、通信接口902和存储器903中的全部或部分硬件。其中通信装置90中的处理器901的数量可以一个或多个，图10中以一个处理器为例。本申请实施例中，处理器901、通信接口902和存储器903可通过总线系统或其它方式连接，其中，图10中以通过总线系统904连接为例。
处理器901可以是中央处理器(central processor unit，CPU)、网络处理器(network processor，NP)或者CPU和NP的组合。处理器901还可以包括硬件芯片。上述硬件芯片可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。
通信接口902用于接收和发送数据，具体地，通信接口902可以包括接收接口和发送接口。其中，接收接口可以用于接收数据，发送接口可以用于发送数据。通信接口902的个数可以为一个或多个。
存储器903可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器3003也可以包括非易失性存储器(non-volatile memory)，例如快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器3003还可以包括上述种类的存储器的组合。
可选地，存储器903存储有操作系统和程序、可执行模块或者数据结构，或者它们的子集，或者它们的扩展集，其中，程序可包括各种操作指令，用于实现各种操作。操作系统可包括各种系统程序，用于实现各种基础业务以及处理基于硬件的任务。处理器901可以读取存储器903中的程序，实现本申请实施例提供的方法。
其中，存储器903可以为通信装置90中的存储器件，也可以为独立于通信装置90的存储装置。
总线系统904可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线系统3004可以分为地址总线、数据总线、控制总线等。为便于表示，图10中仅用一条粗线表示，但并不表示仅有一根总线或一种类型的总线。
图11是本申请实施例提供的另一种通信装置的结构示意图，具体的，该通信装置100可以用于实现图2、图5或图6中Aleaf设备1021的功能，或者该通信装置100可以用于实现图2、图5或图6中Sleaf设备1031的功能，或者该通信装置90可以用于实现图7或图8中第一通信装置的功能，或者该通信装置90可以用于实现图9或图10中第二通信装置的功能。
通信装置100包括：主控板1001和接口板1003。
主控板1001也称为主处理单元(main processing unit，MPU)或路由处理卡(route processor card)，主控板1001对通信装置100中各个组件的控制和管理，包括路由计算、设备管理、设备维护、协议处理功能。主控板1001包括：中央处理器10011和存储器10012。
接口板1003也称为线路接口单元卡(line processing unit，LPU)、线卡(line card)或业务板。接口板1003用于提供各种业务接口并实现数据包的转发。业务接口包括而不限于以太网接口、POS(Packet over SONET/SDH)接口等，以太网接口例如是灵活以太网业务接口(flexible Ethernet clients，FlexE Clients)。接口板1003包括：中央处理器10031、网络处理器10032、地址表项存储器10034和物理接口卡(physical interface card，PIC)10033。
接口板1003上的中央处理器10031用于对接口板1003进行控制管理并与主控板1001上的中央处理器10011进行通信。
网络处理器10032用于实现报文的转发处理。网络处理器10032的形态可以是转发芯片。具体而言，上行报文的处理包括：报文入接口的处理，转发表查找；下行报文的处理包括转发表查找等等。
物理接口卡10033用于实现物理层的对接功能，原始的流量由此进入接口板1003，以及处理后的报文从该物理接口卡10033发出。物理接口卡10033包括至少一个物理接口，物理接口也称物理口。物理接口卡10033也称为子卡，可安装在接口板1003上，负责将光电信号转换为报文并对报文进行合法性检查后转发给网络处理器10032处理。在一些实施例中，接口板1103的中央处理器10031也可执行网络处理器10032的功能，比如基于通用CPU实现软件转发，从而物理接口卡10033中不需要网络处理器10032。
可选地，通信装置100包括多个接口板，例如通信装置100还包括接口板1004，接口板1004包括：中央处理器10041、网络处理器10042、地址表项存储器10044和物理接口卡10043。
可选地，通信装置100还包括交换网板1002。交换网板1002也可以称为交换网板单元(switch fabric unit，SFU)。在第一通信装置有多个接口板1003的情况下，交换网板1002用于完成各接口板之间的数据交换。例如，接口板1003和接口板1004之间可以通过交换网板1002通信。
主控板1001和接口板1003耦合。例如。主控板1001、接口板1003和接口板1004，以及交 换网板1002之间通过系统总线与系统背板相连实现互通。在一种可能的实现方式中，主控板1001和接口板1003之间建立进程间通信协议(inter-process communication，IPC)通道，主控板1001和接口板1003之间通过IPC通道进行通信。
在逻辑上，通信装置100包括控制面和转发面，控制面包括主控板1001和中央处理器10031，转发面包括执行转发的各个组件，比如地址表项存储器10034、物理接口卡10033和网络处理器10032。控制面执行路由器、生成转发表、处理信令和协议报文、配置与维护设备的状态等功能，控制面将生成的转发表下发给转发面，在转发面，网络处理器10032基于控制面下发的转发表对物理接口卡10033收到的报文查表转发。控制面下发的转发表可以保存在地址表项存储器10034中。在一些实施例中，控制面和转发面可以完全分离，不在同一设备上。
应理解，通信装置80中的处理单元802可以相当于通信装置100中的中央处理器10011或中央处理器10031。
应理解，本申请实施例中接口板1004上的操作与接口板1003的操作一致，为了简洁，不再赘述。
应理解，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，通信装置100的数据处理能力越强，提供的接口板越多。接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，通信装置100可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，通信装置100可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。所以，分布式架构的通信装置100的数据接入和处理能力要大于集中式架构的设备。可选地，通信装置100的形态也可以是只有一块板卡，即没有交换网板，接口板和主控板的功能集成在该一块板卡上，此时接口板上的中央处理器和主控板上的中央处理器在该一块板卡上可以合并为一个中央处理器，执行两者叠加后的功能，这种形态设备的数据交换和处理能力较低(例如，低端交换机或路由器等)。具体采用哪种架构，取决于具体的组网部署场景。
在一些可能的实施例中，上述通信装置可以实现为虚拟化设备。例如，虚拟化设备可以是运行有用于发送报文功能的程序的虚拟机(virtual machine，VM)，虚拟机部署在硬件设备上(例如，物理服务器)。虚拟机指通过软件模拟的具有完整硬件系统功能的、运行在一个完全隔离环境中的完整计算机系统。可以将虚拟机配置为通信装置。例如，可以基于通用的物理服务器结合网络功能虚拟化(network functions virtualization，NFV)技术来实现通信装置的功能。本领域技术人员通过阅读本申请即可结合NFV技术在通用物理服务器上虚拟出具有上述功能的通信装置，此处不再赘述。
需要说明的是，本申请实施例中提及的通信装置，可以是交换机、路由器等网络设备，也可以是网络设备上的一部分组件，例如是网络设备上的单板，线卡，还可以是网络设备上的一个功能模块，还可以是用于实现本申请方法的芯片，本申请实施例不做具体限定。当通信装置为芯片时，通信装置中用于执行接收或发送操作的可以是芯片中的接口电路，用于执行处理操作的可以是芯片中的处理器。
一个具体的实现中，本申请实施例还提供了一种芯片，包括处理器和接口电路，接口电路，用于接收指令并传输至处理器；处理器，可以用于执行上述通信方法中各通信装置的操作。其中，所述处理器与存储器耦合，所述存储器用于存储程序或指令，当所述程序或指令被所述处理器执行时，使得该芯片实现上述任一方法实施例中的方法。
可选地，该芯片中的处理器可以为一个或多个。该处理器可以通过硬件实现和/或软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现。
可选地，该芯片中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置，本申请并不限定。示例性的，存储器可以是非瞬时性处理器，例如只读存储器ROM，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请对存储器的类型，以及存储器与处理器的设置方式不作具体限定。
示例性的，该芯片可以是现场可编程门阵列(field programmable gate array，FPGA)，可以是专用集成芯片(application-specific integrated circuit，ASIC)，还可以是系统芯片(system on chip，SoC)，还可以是中央处理器(central processor unit，CPU)，还可以是网络处理器(network processor，NP)，还可以是数字信号处理电路(digital signal processor，DSP)，还可以是微控制器(micro controller unit，MCU)，还可以是可编程控制器(programmable logic device，PLD)或其他集成芯片。
本申请实施例还提供了一种计算机可读存储介质，包括指令或计算机程序，当其在处理器上运行时，使得处理器执行以上实施例提供的通信方法。
本申请实施例还提供了一种包含指令或计算机程序的计算机程序产品，当其在处理器上运行时，使得通信装置执行以上实施例提供的报文转发的方法。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的实施例能够以除了在这里图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或单元的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤或单元。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑业务划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本申请所描述的业务可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些业务存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。计算机可读介质包括计算机存储介质和通信介质，其中通信介质包括便于从一个地方向另一个地方传送计算机程序的任何介质。存储介质可以是通用或专用计算机能够存取的任何可用介质。
以上的具体实施方式，对本申请的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上仅为本申请的具体实施方式而已。
以上，以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本申请各实施例技术方案的范围。

Claims (41)

  1. 一种通信方法，其特征在于，包括：
    第一通信装置通过叶leaf接口接收来自第二通信装置的第一报文；
    响应于确定通过缺省介质访问控制MAC地址表项来转发所述第一报文，所述第一通信装置丢弃所述第一报文，其中，所述缺省MAC地址表项包括leaf标识和全0的MAC地址。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述第一通信装置接收来自第三通信装置的未知MAC路由UMR，所述UMR携带leaf指示信息，所述leaf指示信息指示所述UMR具有leaf属性；
    所述第一通信装置根据所述UMR，生成所述缺省MAC地址表项。
  3. 根据权利要求2所述的方法，其特征在于，所述UMR中携带以太网多播E-tree扩展团体属性；所述E-tree扩展团体属性中包括所述leaf指示信息。
  4. 根据权利要求2或3所述的方法，其特征在于，所述leaf指示信息为所述leaf标识。
  5. 根据权利要求2-4任一项所述的方法，其特征在于，所述第一通信装置为Sleaf设备，所述第三通信装置为Aleaf设备。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述方法还包括：
    所述第一通信装置通过所述leaf接口接收第二报文；
    所述第一通信装置根据所述第二报文的目的MAC地址查找匹配的MAC地址表项，所述MAC地址表项包括根root标识；
    所述第一通信装置转发所述第二报文。
  7. 一种通信方法，其特征在于，包括：
    第一通信装置接收来自第二通信装置的未知介质访问控制路由UMR，所述UMR携带叶leaf指示信息，所述leaf指示信息指示所述UMR具有leaf属性；
    所述第一通信装置根据所述UMR，生成缺省MAC地址表项，其中，所述缺省MAC地址表项包括leaf标识和全0的MAC地址。
  8. 根据权利要求7所述的方法，其特征在于，所述UMR中携带以太网多播E-tree扩展团体属性；所述E-tree扩展团体属性中包括所述leaf指示信息。
  9. 根据权利要求7或8所述的方法，其特征在于，所述leaf指示信息为所述leaf标识。
  10. 根据权利要求7-9任一项所述的方法，其特征在于，所述第一通信装置为Sleaf设备，所述第二通信装置为Aleaf设备。
  11. 一种通信方法，其特征在于，包括：
    第二通信装置生成未知介质访问控制路由UMR，所述UMR中携带叶leaf指示信息，所述leaf指示信息指示所述UMR具有leaf属性；
    所述第二通信装置将所述UMR发送至第一通信装置。
  12. 根据权利要求11所述的方法，其特征在于，所述UMR中携带以太网多播E-tree扩展团体属性；所述E-tree扩展团体属性中包括所述leaf指示信息。
  13. 根据权利要求11或12所述的方法，其特征在于，所述第二通信装置为Aleaf设备，所述第一通信装置Sleaf设备。
  14. 一种通信方法，其特征在于，包括：
    第二通信装置接收来自第一通信装置的第一报文；
    响应于确定与所述第一报文的目的介质访问控制MAC地址匹配的第一MAC地址表项中的第一出接口为叶leaf接口，以及与所述第一报文的源MAC地址匹配的第二MAC地址表项包括leaf标识，所述第二通信装置丢弃所述第一报文。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    所述第二通信装置接收来自所述第一通信装置的MAC路由；所述MAC路由包括所述第一报文的源MAC地址以及leaf指示信息，所述leaf指示信息指示所述MAC路由具有leaf属性；
    所述第二通信装置根据所述MAC路由，生成所述第二MAC地址表项。
  16. 根据权利要求15所述的方法，其特征在于，所述leaf指示信息为所述leaf标识。
  17. 根据权利要求14-16任一项所述的方法，其特征在于，所述方法还包括：
    所述第二通信装置接收第二报文；
    所述第二通信装置响应于确定所述第二报文的目的MAC地址所匹配的第三MAC地址表项中的第二出接口为leaf接口，以及与所述第二报文的源MAC地址所匹配的第四MAC地址表项包括根root标识，所述第二通信装置通过所述第二出接口转发所述第二报文。
  18. 根据权利要求14-17任一项所述的方法，其特征在于，所述第一通信装置为Sleaf设备，所述第二通信装置Aleaf设备。
  19. 一种第一通信装置，其特征在于，包括：
    接收单元，用于通过叶leaf接口接收来自第二通信装置的第一报文；
    处理单元，用于响应于确定通过缺省介质访问控制MAC地址表项来转发所述第一报文，丢弃所述第一报文，其中，所述缺省MAC地址表项包括leaf标识和全0的MAC地址。
  20. 根据权利要求19所述的第一通信装置，其特征在于，
    所述接收单元，还用于接收来自第三通信装置的未知MAC路由UMR，所述UMR携带leaf指示信息，所述leaf指示信息指示所述UMR具有leaf属性；
    所述处理单元，还用于根据所述UMR，生成所述缺省MAC地址表项。
  21. 根据权利要求20所述的第一通信装置，其特征在于，所述UMR中携带以太网多播E-tree扩展团体属性；所述E-tree扩展团体属性中包括所述leaf指示信息。
  22. 根据权利要求20或21所述的第一通信装置，其特征在于，所述leaf指示信息为所述leaf标识。
  23. 根据权利要求20-22任一项所述的第一通信装置，其特征在于，所述第一通信装置为Sleaf设备，所述第三通信装置为Aleaf设备。
  24. 根据权利要求19-23任一项所述的第一通信装置，其特征在于，所述接收单元，还用于通过所述leaf接口接收第二报文；
    所述处理单元，还用于根据所述第二报文的目的MAC地址查找匹配的MAC地址表项，所述MAC地址表项包括根root标识；
    所述处理单元，还用于转发所述第二报文。
  25. 一种第一通信装置，其特征在于，包括：
    接收单元，用于接收来自第二通信装置的未知介质访问控制路由UMR，所述UMR携带叶leaf指示信息，所述leaf指示信息指示所述UMR具有leaf属性；
    处理单元，用于根据所述UMR，生成缺省MAC地址表项，其中，所述缺省MAC地址表项包括leaf标识和全0的MAC地址。
  26. 根据权利要求25所述的第一通信装置，其特征在于，所述UMR中携带以太网多播E-tree扩展团体属性；所述E-tree扩展团体属性中包括所述leaf指示信息。
  27. 根据权利要求25或26述的第一通信装置，其特征在于，所述leaf指示信息为所述leaf标识。
  28. 根据权利要求25-27任一项所述的第一通信装置，其特征在于，所述第一通信装置为Sleaf设备，所述第二通信装置为Aleaf设备。
  29. 一种第二通信装置，其特征在于，包括：
    处理单元，用于生成未知介质访问控制路由UMR，所述UMR中携带叶leaf指示信息，所述leaf指示信息指示所述UMR具有leaf属性；
    发送单元，用于将所述UMR发送至第一通信装置。
  30. 根据权利要求29所述的第二通信装置，其特征在于，所述UMR中携带以太网多播E-tree扩展团体属性；所述E-tree扩展团体属性中包括leaf指示信息。
  31. 根据权利要求29或30所述的第二通信装置，其特征在于，所述第一通信装置为Aleaf设备，所述第二通信装置Sleaf设备。
  32. 一种第二通信装置，其特征在于，包括：
    接收单元，用于接收来自第一通信装置的第一报文；
    处理单元，用于响应于确定与所述第一报文的目的介质访问控制MAC地址匹配的第一MAC地址表项中的第一出接口为叶leaf接口，以及与所述第一报文的源MAC地址匹配的第二MAC地址表项包括leaf标识，所述第二通信装置丢弃所述第一报文。
  33. 根据权利要求32所述的第二通信装置，其特征在于，所述接收单元，还用于接收来自所述第一通信装置的MAC路由；所述MAC路由包括所述第一报文的源MAC地址以及leaf指示信息，所述leaf指示信息指示所述MAC路由具有leaf属性；
    所述处理单元，还用于根据所述MAC路由，生成所述第二MAC地址表项。
  34. 根据权利要求32或33所述的第二通信装置，其特征在于，所述leaf指示信息为所述leaf标识。
  35. 根据权利要求32-34任一项所述的第二通信装置，其特征在于，所述接收单元，还用于接收第二报文；
    所述处理单元，还用于响应于确定所述第二报文的目的MAC地址所匹配的第三MAC地址表项中的第二出接口为leaf接口，以及与所述第二报文的源MAC地址所匹配的第四MAC地址表项包括根root标识，所述第二通信装置通过所述第二出接口转发所述第二报文。
  36. 根据权利要求32-35任一项所述的第二通信装置，其特征在于，所述第二通信装置为Aleaf设备，所述第一通信装置Sleaf设备。
  37. 一种通信装置，其特征在于，包括处理器和存储器，所述存储器用于存储计算机指令，当所述计算机指令在所述处理器中运行时，使得所述通信装置实现如权利要求1-6中任一项所述的方法，或者实现如权利要求7-10中任一项所述的方法，或者实现如权利要求11-13中任一项所述的方法，或者实现如权利要求14-18中任一项所述的方法。
  38. 一种通信系统，其特征在于，包括第一通信装置和第二通信装置；
    其中，所述第一通信装置用于实现如权利要求1-10任一项所述的方法，所述第二通信装置用于实现如权利要求11-13任一项所述的方法。
  39. 一种通信系统，其特征在于，包括第一通信装置和第二通信装置，所述第二通信装置用于实现如权利要求14-18任一项所述的方法。
  40. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质中存储有指令，当所述指令在处理器上运行时，实现如权利要求1-6中任一项所述的方法，或者实现如权利要求7-10中任一项所述的方法，或者实现如权利要求11-13中任一项所述的方法，或者实现如权利要求14-18中任一项所述的方法。
  41. 一种计算机程序产品，其特征在于，包括计算机程序，当所述计算机程序在处理器上运行时，实现权利要求如权利要求1-6中任一项所述的方法，或者实现如权利要求7-10中任一项所述的方法，或者实现如权利要求11-13中任一项所述的方法，或者实现如权利要求14-18中任一项所述的方法。
PCT/CN2023/103646 2022-11-01 2023-06-29 通信方法及装置 WO2024093306A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211354585.8A CN117997561A (zh) 2022-11-01 2022-11-01 通信方法及装置
CN202211354585.8 2022-11-01

Publications (1)

Publication Number Publication Date
WO2024093306A1 true WO2024093306A1 (zh) 2024-05-10

Family

ID=90900156

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/103646 WO2024093306A1 (zh) 2022-11-01 2023-06-29 通信方法及装置

Country Status (2)

Country Link
CN (1) CN117997561A (zh)
WO (1) WO2024093306A1 (zh)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104639442A (zh) * 2015-02-16 2015-05-20 杭州华三通信技术有限公司 一种报文处理方法和装置
US10382390B1 (en) * 2017-04-28 2019-08-13 Cisco Technology, Inc. Support for optimized microsegmentation of end points using layer 2 isolation and proxy-ARP within data center
CN116016340A (zh) * 2023-01-03 2023-04-25 中国电信股份有限公司 用于路由实现的方法及装置、存储介质及电子设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104639442A (zh) * 2015-02-16 2015-05-20 杭州华三通信技术有限公司 一种报文处理方法和装置
US10382390B1 (en) * 2017-04-28 2019-08-13 Cisco Technology, Inc. Support for optimized microsegmentation of end points using layer 2 isolation and proxy-ARP within data center
CN116016340A (zh) * 2023-01-03 2023-04-25 中国电信股份有限公司 用于路由实现的方法及装置、存储介质及电子设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
NEW H3C TECHNOLOGIES CO., LTD.: "EVPN VPLS over SRv6", H3C SR8800-F ROUTER SEGMENT ROUTING CONFIGURATION GUIDE, 18 October 2022 (2022-10-18) *
YUANYANG YIN: "Research and Application of UMR Technology for New Metropolitan Area Network", TELECOMMUNICATIONS SCIENCE, no. 2, 20 February 2022 (2022-02-20), pages 149 - 156, XP093168957, DOI: 10.11959/j.issn.1000−0801.2022028 *

Also Published As

Publication number Publication date
CN117997561A (zh) 2024-05-07

Similar Documents

Publication Publication Date Title
CN109218178B (zh) 一种报文处理方法及网络设备
CA3080526C (en) Ip mpls pop virtualization and fault tolerant virtual router
US8792506B2 (en) Inter-domain routing in an n-ary-tree and source-routing based communication framework
US9100213B1 (en) Synchronizing VPLS gateway MAC addresses
US11909556B2 (en) Resilient multiprotocol label switching (MPLS) rings using segment routing
CN112565046B (zh) 同步多播路由器能力
US11349735B2 (en) Faster fault-detection mechanism, for example using bidirectional forwarding detection (BFD), on network nodes and/or hosts multihomed using a link aggregation group (LAG)
EP3820089A1 (en) Controller provided protection paths
WO2021082812A1 (zh) 报文的发送方法和第一网络设备
US11876706B2 (en) Avoiding loops by preventing further fast reroute (FRR) after an earlier FRR
WO2021093463A1 (zh) 报文转发的方法、第一网络设备以及第一设备组
WO2020088379A1 (zh) 一种业务流处理方法及装置
US20110222541A1 (en) Network System, Edge Node, and Relay Node
EP4325777A1 (en) Method and device for electing designated forwarder (df)
WO2024093306A1 (zh) 通信方法及装置
CN114301839B (zh) 一种组播报文传输方法及装置
KR20230057459A (ko) 라우팅 정보 전송 방법 및 장치
US11070468B1 (en) Serverless segment routing (SR)-label distribution protocol (LDP) stitching
Cisco Release Notes for Cisco IOS Release 12.1 E on the Catalyst 6000 and Cisco 7600 Supervisor Engine and MSFC
WO2022061561A1 (zh) 一种报文传输方法及装置
WO2023078275A1 (zh) 一种报文传输方法、装置及设备
WO2022133646A1 (zh) 一种路由传输方法及装置
WO2022161061A1 (zh) 一种故障检测方法、网络设备及系统
US11218406B2 (en) Optimized datapath troubleshooting