CN102970231B - Multicast data flow forwards implementation method and route-bridge(RB) - Google Patents

Multicast data flow forwards implementation method and route-bridge(RB) Download PDF

Info

Publication number
CN102970231B
CN102970231B CN201210470320.4A CN201210470320A CN102970231B CN 102970231 B CN102970231 B CN 102970231B CN 201210470320 A CN201210470320 A CN 201210470320A CN 102970231 B CN102970231 B CN 102970231B
Authority
CN
China
Prior art keywords
multicast
multicast tree
bridge
route
tree
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201210470320.4A
Other languages
Chinese (zh)
Other versions
CN102970231A (en
Inventor
翟洪军
代雪会
廖婷
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to CN201210470320.4A priority Critical patent/CN102970231B/en
Publication of CN102970231A publication Critical patent/CN102970231A/en
Priority to PCT/CN2013/082327 priority patent/WO2014079246A1/en
Application granted granted Critical
Publication of CN102970231B publication Critical patent/CN102970231B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4604LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462LAN interconnection over a bridge based backbone
    • H04L12/4625Single bridge functionality, e.g. connection of two networks over a single bridge

Abstract

The present invention relates to a kind of multicast data flow forwarding implementation method and route-bridge(RB), each route-bridge (RB) according to the upstream or downstream multicast data flow that receives of the distribution information of multicast tree forwarding, distributed respectively by up direction and down direction by the multicast tree in the distribution information of the multicast tree.When down direction breaks down, the multicast data flow forwarding of up direction is not interfered with.

Description

Multicast data flow forwards implementation method and route-bridge(RB)
Technical field
The present invention relates to network communication technology, more specifically, being a kind of multicast data flow forwarding implementation method and route-bridge (RB)。
Background technology
TRILL is multi-link transparent interconnection (Transparent Interconnection over Lots of Links) English abbreviation, (or be L2MP (2 Multiple of Layer for solving the multipath in the big double layer network of data center Path)) problem.By by IS-IS (Intermediate System to Intermediate System, intermediate system pair Intermediate system) Routing Protocol introduce double layer network realize L2MP.In TRILL networks, the equipment for running TRILL protocol claims For RBridge (route-bridge, hereinafter also referred to as " RB "), and by one RBridge of Nickname (alias) unique mark. The entrance of TRILL network, is responsible for the initial data frame of end equipment (End Station) being packaged into TRILL forms (i.e. original TRILL and exterior frame head are added before data frame, mainly include TRILL network entrance and exit route-bridge in TRILL Nickname and hop count) and inject the route-bridge of TRILL network and be known as Ingress;In the outlet of TRILL network, it is responsible for The deblocking of TRILL data frames for initial data frame and is transmitted to the route-bridge of end equipment and is known as Egress, while Egress is also It is which Ingress imports TRILL and forms MAC information tables { D_MAC, Ingress_ that can learn the frame Nickname ... }.Because Ingress and Egress route-bridges are in marginal position in TRILL network, therefore again It is referred to as edge route-bridge (Edge RBridge).
In order to avoid loop, on the border of TRILL network, in any one VLAN (Virtual Local Area Network, virtual LAN) in can only provide service by a RBridge for an end system, this RBridge is known as this The ISP of a end system, such as on shared link, VLAN specified forwarding unit (Appointed Forwarder, AF).Although this can effectively be avoided loop, some problems are also result in, such as:AF switching after, on the Egress of distal end certain Generation Ingress_Nickname changes in a little MAC address entries;In end system by belonging to (Multi- point-to-point link more Homing, such as:Pass through link aggregation group (Link Aggregation Group, LAG)) on multiple RBridge when, RB Load sharing on link can cause the Ingress_Nickname frequent fluctuations of some MAC address entries on the RBridge of distal end (to claim For flip-flop), so as to cause the out of order and report lost for the flow returned, cause conversation.
For this reason, TRILL working groups propose route-bridge group (RBridge Group, RBG) or are virtual flow-line bridge The concept of (Virtual RBridge, RBv).In a RBv, group member shares a Nickname, referred to as organizes Nickname, RB in RBv, with a group Nickname encapsulation of data frames, solves above-mentioned flip-flop when data frame is imported TRILL network Problem.
Temporary loop in being forwarded in order to avoid multicast message, must when TRILL protocol regulation RBridge receives multicast frame RPF (Reverse Path Forwarding, reverse path forwarding) must be to check.RPF inspection requirements is in any multicast Any route-bridge on tree, is only capable of the multicast frame for receiving another RBridge from an interface and being sent along the tree, checks Failure must abandon the frame.Working group manuscript draft-ietf-trill-cmt-01.txt (abbreviation CMT, Coordinated Multi-Destination Tree, demarcate multicast tree) multicast tree can be used by being distributed between the RB in RBv, pay close attention to And solves the problems, such as existing RPF when the RB in multiple RBv imports (up direction) multicast packet frame.For by RBv RB leave the multicast packet frame of (down direction) TRILL network, CMT provides that RB in any RBv can only will be along distributing to The flow export TRILL network of its multicast tree distribution, avoids the risk that end system receives more parts of multicast messages.Such as Fig. 1 institutes Show, it is assumed that have 5 multicast trees, RB1, RB2 and RB3 have advertised respectively { RB1, RBv, T1, T4 }, { RB2, RBv, T2, T5 } and { RB1, RBv, T3 }, it is assumed that RB4 sends flux of multicast along T1 (multicast tree as shown in heavy line in Fig. 1), then at this In RBv, multicast data flow can only be exported into TRILL network by RB1, RB2 and RB3 abandon the multicast data flow.But this mechanism is in RB Or during access link fault, it may appear that problems with.
First, when some RB failure, can cause to redistribute between RB of the multicast tree in RBv, in the meantime, multicast Stream recipient can not receive desired data flow;In addition, after the completion of multicast tree is redistributed, distal end RB (RB4 in such as Fig. 1) Another multicast tree may be reselected, so causes the time of service disconnection longer.
Secondly, when the RB links of the LAG1 under the flow for being issued along T1, RB1 are all normal (during fault-free), Customer edge (Customer Edge, CE) equipment CE1 and CE2 can receive the flow;But work as RBs of the RB1-CE1 under LAG1 During link failure, if reselecting an other multicast tree on RB4, it is assumed that if being T2, then according to existing CMT texts Original text, RB2 can export multicast data flow.The problem so brought is exactly, because the RB link failures of LAG1, and causes on LAG2 Recipient also will from other one tree up receive flow.That is, when having multiple LAG under a RBv, if only The RB links of one of LAG break down, and the flow for also resulting in other LAG is also affected.
The content of the invention
The technical problem to be solved in the present invention is to provide a kind of multicast data flow to forward implementation method and route-bridge (RB), with When solving existing failure, multicast data flow forwards the problem of impacted larger.
In order to solve the above technical problems, the present invention provides a kind of multicast data flow to forward implementation method, each route-bridge (RB) According to the upstream or downstream multicast data flow that receives of the distribution information of the multicast tree of storage forwarding, in the distribution information of the multicast tree Multicast tree distributed respectively by up direction and down direction.
In order to solve the above technical problems, present invention also offers a kind of route-bridge (RB), which includes:
Assignment information storage unit, for storing the distribution information of multicast tree, the multicast tree be by up direction and under What line direction distributed respectively;
Multicast data flow retransmission unit, for forwarding uplink and/or downstream multicast stream according to the distribution information of multicast tree.
The method of the present invention and route-bridge, the multicast tree in the distribution information of the multicast tree is by up direction and downlink What direction was distributed respectively, therefore, when down direction breaks down, do not interfere with the multicast data flow forwarding of up direction, Jin Ershi Show end system to access the high reliability of TRILL network.
Brief description of the drawings
Fig. 1 is distribution schematic diagram of the existing CMT documents to multicast tree;
Fig. 2 is the flow diagram of multicast data flow forwarding implementation method embodiment 1 of the present invention;
Fig. 3 is the flow diagram of multicast data flow forwarding implementation method embodiment 2 of the present invention;
Fig. 4 is the flow diagram of multicast data flow forwarding implementation method embodiment 3 of the present invention;
Fig. 5 is the process schematic that multicast data flow forwards in multicast data flow forwarding implementation method embodiment 3 of the present invention;
Fig. 6 is the flow diagram of multicast data flow forwarding implementation method embodiment 4 of the present invention;
Fig. 7,8 are that application example one to four of the present invention uses multicast tree to distribute schematic diagram;
Fig. 9-11 is the modular structure schematic diagram of route-bridge of the present invention (RB) embodiment.
Embodiment
Technical solution of the present invention is described in further detail with specific embodiment below in conjunction with the accompanying drawings, so that this The technical staff in field can be better understood from the present invention and can be practiced, but illustrated embodiment is not as the limit to the present invention It is fixed.It should be noted that in the case where there is no conflict, the feature in embodiment and embodiment in the application can be mutual group Close.
Embodiment 1
As shown in Fig. 2, 1 multicast data flow of the embodiment of the present invention forwards implementation method, each route-bridge (RB) is according to multicast tree The upstream or downstream multicast data flow that receives of distribution information forwarding, the multicast tree in the distribution information of the multicast tree is by uplink side To what is distributed respectively with down direction, specifically, this method includes:
Step 201:Route-bridge (RB) obtains and stores the distribution information of the multicast tree of route-bridge group (RBv), described Multicast tree in the distribution information of multicast tree is distributed respectively by up direction and down direction;
The distribution information of the multicast tree can specifically use configuration mode generation or each route-bridge based on identical distribution Algorithm obtains, it is preferable that can be allocated based on load balancing.
The present invention obtains route-bridge (RB) specific method of the distribution information of the multicast tree of route-bridge group (RBv) not Limit.In up direction, the distribution of multicast tree can be carried out according to existing CMT mechanism.
Understandably, the mapping relations between route-bridge and multicast tree are mainly established, it can be described as multicast Tree distributes to route-bridge, also can be described as route-bridge distributing to multicast tree, the two is without essential difference.
The route-bridge for being assigned with some multicast tree is the forwarding unit of the multicast tree.
Step 202:Each route-bridge (RB) carries out uplink according to the distribution information of multicast tree and/or downlink multicast circulates Hair.
The process that each RB carries out uplink and/or downstream multicast stream forwarding according to the distribution information of multicast tree includes:
Receive the multicast data flow along multicast tree upstream or downstream direction;
Judge whether it is the forwarding unit of the multicast tree in the corresponding direction according to distribution information;
If so, then forwarding the multicast data flow, the multicast data flow is otherwise abandoned.
In above example, by multicast tree between the route-bridge (RB) of route-bridge group (RBv) by up direction and Down direction distributes respectively, so as to may be such that, when the route-bridge of downlink or its corresponding link break down, does not interfere with The forwarding of uplink multicast stream.
Embodiment 2
As shown in figure 3,2 multicast data flow of the embodiment of the present invention forwards implementation method, each route-bridge (RB) is according to multicast tree The upstream or downstream multicast data flow that receives of distribution information forwarding, the multicast tree in the distribution information of the multicast tree is by uplink side To what is distributed respectively with down direction, specifically, including:
Step 301:Route-bridge (RB) obtains and stores the distribution information of the multicast tree of route-bridge group (RBv), described Multicast tree in the distribution information of multicast tree is distributed respectively by up direction and down direction, and multicast tree is in down direction The distribution in each link aggregation group (LAG) or local area network (Local Area Network, LAN);
For example there are 6 multicast trees, 3 LAG, then 6 multicast trees are distributed in 3 LAG.
The distribution information of the multicast tree can specifically use configuration mode generation or each route-bridge based on identical distribution Algorithm obtains, it is preferable that the number that can be responsible for the corresponding multicast tree of multicast data flow of forwarding based on each RB carries out equilibrium assignment.
The present invention obtains route-bridge (RB) specific method of the distribution information of the multicast tree of route-bridge group (RBv) not Limit.
Understandably, the mapping relations between route-bridge and multicast tree are mainly established, it can be described as multicast Tree distributes to route-bridge, also can be described as route-bridge distributing to multicast tree, the two is without essential difference.
The route-bridge for being assigned with some multicast tree is the forwarding unit of the multicast tree.
Step 302:Each route-bridge (RB) carries out uplink according to the distribution information of multicast tree and/or downlink multicast circulates Hair.
The process that the multicast tree that each RB is distributed according to down direction carries out downstream multicast stream forwarding includes:
Receive the multicast data flow along multicast tree down direction;
Judge whether it is the multicast tree under link aggregation group (LAG) or local area network (LAN) according to distribution information Forwarding unit on line direction;
If so, then forwarding the multicast data flow, the multicast data flow is otherwise abandoned.
In above example, by multicast tree between the route-bridge (RB) of route-bridge group (RBv) by up direction and Down direction distributes respectively, so as to may be such that, when the route-bridge of downlink or its corresponding link break down, does not interfere with The forwarding of uplink multicast stream, in addition, multicast tree in down direction in each link aggregation group (LAG) or local area network (LAN) Interior distribution, when may be such that the link of wherein a certain LAG or LAN breaks down, does not interfere with the multicast circulation of other LAG or LAN Hair.
Embodiment 3
The embodiment of the present invention 3 emphatically illustrates the forwarding of down direction multicast data flow, and each route-bridge (RB) is according to multicast The upstream or downstream multicast data flow that receives of distribution information forwarding of tree, the multicast tree in the distribution information of the multicast tree is by upper What line direction and down direction distributed respectively, specifically, as shown in figure 4, multicast data flow forwarding implementation method includes:
Step 401:Route-bridge (RB) obtains and stores point of the multicast tree of route-bridge group (RBv) in the downstream direction With information, multicast tree distribution in each link aggregation group (LAG) or local area network (LAN) in down direction, one The route-bridge (RB) that multicast tree is distributed in down direction includes a primary forwarding unit and a spare forwarding unit;
The distribution information of the multicast tree can specifically use configuration mode generation or each route-bridge based on identical distribution Algorithm obtains, it is preferable that can be allocated based on load balancing.
The present invention obtains route-bridge (RB) specific method of the distribution information of the multicast tree of route-bridge group (RBv) not Limit.
Understandably, the mapping relations between route-bridge and multicast tree are mainly established, it can be described as multicast Tree distributes to route-bridge, also can be described as route-bridge distributing to multicast tree, the two is without essential difference.
The route-bridge for being assigned with some multicast tree is the forwarding unit of the multicast tree.In the embodiment, in downlink side Partly or entirely multicast tree distributes a primary forwarding unit and a spare forwarding unit upwards.In primary forwarding unit and its When corresponding link is normal, the multicast data flow for realizing corresponding multicast tree by primary forwarding unit forwards, only when primary forwarding unit or Its corresponding link breaks down when can not realize normal multicast data flow forwarding, just enables the multicast data flow forwarding of spare forwarding unit Function.
Step 402:Each route-bridge (RB) carries out downstream multicast stream according to the distribution information of multicast tree in the downstream direction Forwarding.
As shown in figure 5, the multicast tree that each route-bridge (RB) is distributed according to down direction carries out downstream multicast stream forwarding Process includes:
Step 501:Receive the multicast data flow along multicast tree down direction;
Step 502:Judge whether it is the primary forwarding unit of multicast tree in the downstream direction according to distribution information;
Specifically, route-bridge can be by establishing flag bit, for showing current road to each multicast tree distributed for it It is the primary forwarding unit of the multicast tree or spare forwarding unit by bridge.
Step 503:If so, then forwarding the multicast data flow, the multicast data flow is otherwise abandoned.
In above example, although being illustrated to down direction emphatically, but still can be by multicast tree in route-bridge group (RBv) distributed respectively by up direction and down direction between route-bridge (RB), so as to may be such that, in the routing network of downlink When bridge or its corresponding link break down, do not interfere with the forwarding of uplink multicast stream, in addition, multicast tree in down direction each Distribution, may be such that the link of wherein a certain LAG or LAN breaks down in a link aggregation group (LAG) or local area network (LAN) When, do not interfere with the multicast data flow forwarding of other LAG or LAN;Route-bridge (RB) bag that same multicast tree is distributed in down direction A primary forwarding unit and a spare forwarding unit are included, may be such that and event occurs in primary forwarding unit or its corresponding link During barrier, the primary forwarding unit for upgrading to the multicast tree by the spare forwarding unit of impacted multicast tree realizes that multicast circulates Hair, so as to fulfill the quick protection of route-bridge group (RBv).
Specifically, a multicast tree is in one spare forwarding unit of down direction explicit allocation, route-bridge (RB) or its When corresponding link breaks down, other all route-bridges (RB) of the relevant node of failure into place RBv send failure Information;The spare forwarding unit of impacted multicast tree upgrades to the primary forwarding unit of the multicast tree.
Specifically, if RB failures, then CE is the relevant node of failure;If RB link failures, link are corresponding RB and CE perceives failure, then the relevant point of failure can be RB and/or CE.
For the distribution information generating mode of different multicast trees, the content of fault message is different, such as:
According to configuration mode, and each RB only configures the distribution information of itself (i.e. current RB), i.e. each route-bridge (RB) The distribution information for obtaining and storing only includes the distribution information of the multicast tree of itself, and in this case, fault message needs to carry Impacted multicast tree information, if being distributed in LAG or LAN, it is also necessary to carry the information of relevant LAG or LAN, so receive Spare forwarding unit to the fault message of multicast just can determine that its needs switchs to the primary forwarding unit for being affected multicast tree;If Using configuration mode, and each RB is not only configured with the distribution information of itself and is also configured with the distribution information of other each RB (configuration is same Step), or each RB using identical allocation algorithm (algorithm is synchronous), then each RB not only understands the distribution information of itself, is also aware that it The distribution information of his each RB, or each RB only configure the distribution information of itself, by the synchronization (interaction that distribution information is realized after interaction Synchronously), in the case of this three kinds, the distribution information of each RB is synchronous, i.e., each route-bridge (RB) in described RBv is obtained and deposited The distribution information of the multicast tree of storage includes the distribution information of the multicast tree of itself and other each RB, even if the then fault message of multicast Impacted multicast tree information and/or LAG, LAN information are not carried, and the spare forwarding unit of impacted multicast tree also can be smooth Switch to the forwarding that primary forwarding unit performs corresponding multicast data flow.
Above fault message notifies other all route-bridges (RB) in RBv by the way of multicast, alternatively, if The distribution information for the multicast tree that each route-bridge (RB) of same RBv is obtained and stored includes the multicast tree of itself and other each RB Distribution information, specifically can pass through above-mentioned synchronisation or configuration synchronization or algorithm is synchronous;Route-bridge (RB) or its is corresponding When link breaks down, the relevant node of failure is set according to spare forwarding of the distribution information of multicast tree to impacted multicast tree Preparation send fault message;The spare forwarding unit for receiving fault message upgrades to the primary forwarding unit of the multicast tree.
Embodiment 4
The upstream or downstream multicast data flow that each route-bridge (RB) receives according to the forwarding of the distribution information of multicast tree, described group The multicast tree broadcast in the distribution information of tree is distributed respectively by up direction and down direction, the embodiment of the present invention 4 emphatically pair The forwarding of down direction multicast data flow illustrates, specifically, as shown in fig. 6, multicast data flow forwarding implementation method includes:
Step 601:Route-bridge (RB) obtains and stores point of the multicast tree of route-bridge group (RBv) in the downstream direction With information, the multicast tree in down direction distribution is divided in each link aggregation group (LAG) or local area network (LAN) Match somebody with somebody, and a multicast tree includes a primary forwarding unit and several spare turn in the distribution route-bridge (RB) of down direction Send out equipment;
In the embodiment, the distribution information for the multicast tree that each route-bridge (RB) in the RBv is obtained and stored includes The distribution information of the multicast tree of itself and other each RB.
The distribution information of the multicast tree can specifically use configuration mode generation or each route-bridge based on identical distribution Algorithm obtains, it is preferable that can be allocated based on load balancing.
The present invention obtains route-bridge (RB) specific method of the distribution information of the multicast tree of route-bridge group (RBv) not Limit.
Understandably, the mapping relations between route-bridge and multicast tree are mainly established, it can be described as multicast Tree distributes to route-bridge, also can be described as route-bridge distributing to multicast tree, the two is without essential difference.
Specifically, a multicast tree explicitly or implicitly distributes several spare forwarding units in down direction, such as, it is spare Forwarding unit can be all route-bridges outside primary forwarding unit.
Step 602:Each route-bridge (RB) carries out downstream multicast stream according to the distribution information of multicast tree in the downstream direction Forwarding.
In above example, by multicast tree between the route-bridge (RB) of route-bridge group (RBv) by up direction and Down direction distributes respectively, so as to may be such that, when the route-bridge of downlink or its corresponding link break down, does not interfere with The forwarding of uplink multicast stream, in addition, multicast tree in down direction in each link aggregation group (LAG) or local area network (LAN) Interior distribution, when may be such that the link of wherein a certain LAG or LAN breaks down, does not interfere with the multicast circulation of other LAG or LAN Hair;The route-bridge (RB) that one multicast tree is distributed in down direction includes a primary forwarding unit and several spare forwardings Equipment, may be such that when primary forwarding unit or its corresponding link break down, by one of them impacted multicast tree The primary forwarding unit that spare forwarding unit upgrades to the multicast tree realizes that multicast data flow forwards, so as to fulfill route-bridge group (RBv) quick protection.
In the embodiment, when route-bridge (RB) or its corresponding link break down, the relevant node of failure is to place One spare forwarding unit of the impacted multicast tree in RBv sends fault message;The spare forwarding for receiving the fault message is set The standby primary forwarding unit for upgrading to impacted multicast tree.
Because a multicast tree is assigned with multiple spare forwarding units, therefore above fault message is notified by the way of unicast One of them spare forwarding unit upgrades to the primary forwarding unit of the multicast tree.The relevant node of failure is according to the multicast tree Distribution information determine to upgrade to the spare forwarding unit of primary forwarding unit based on load balancing.
In various embodiments above, current primary forwarding unit receives former primary forwarding unit or the failure of its corresponding link After recovering information, switch to spare forwarding unit again.
One of ordinary skill in the art will appreciate that all or part of step in the above method can be instructed by program Related hardware is completed, and described program can be stored in computer-readable recording medium, such as read-only storage, disk or CD Deng.Alternatively, all or part of step of above-described embodiment can also be realized using one or more integrated circuits.Accordingly Ground, each module/unit in above-described embodiment can be realized in the form of hardware, can also use the shape of software function module Formula is realized.The present invention is not restricted to the combination of the hardware and software of any particular form.
Further inventive embodiments are illustrated with application example below in conjunction with the accompanying drawings.
Application example one
By taking Fig. 7 as an example, two LAG are deployed under a RBv, whole TRILL network calculates 5 trees, is denoted as respectively T1, T2, T3, T4 and T5.
For up direction, multicast tree is distributed between the RB of RBv, it is assumed that RB1 is distributed according to the mechanism of existing CMT manuscripts Result be { T1, T4 }, the result of RB2 distribution be { T2, T5 }, and the result that RB3 is distributed is { T3 };
For down direction, multicast tree is allocated in the LAG of RBv.If all RB of RBv are also RBv at the same time The RB of some LAG, then can use the allocation result identical with uplink assignment, a certain RB multicast trees in each LAG for the LAG Primary forwarding unit in the downstream direction, can also be directed to each LAG and distribute different multicast tree forwardings in the downstream direction Role;When RBv receives downstream multicast stream from certain multicast tree, for multicast tree on multicast tree on up direction and down direction The identical situation of allocation result, the processing on RB follow existing CMT manuscripts;And for the different situation of allocation result, RB On whether need to forward the traffic to downlink and need to make a little changes, i.e., according to the multicast tree distributed in each LAG under The forwarding role of line direction decides whether to forward.It for details, reference can be made to latter two application example of this document.
Each RB gives the multicast tree information announcement of distribution to other RBs, realizes the synchronizing information between the RB in RBv.This ESADI (End Station Address Distribution Information, end system address distribution letter can be passed through Breath) agreement is come synchronously, but is not limited solely to the mode of ESADI.
Application example 2
In the application example 2, under the scene that RB or RB link fault announcings are carried out by multicast mode.Because pass through group Notice failure is broadcast, so having multiple RB receives notice.In order to avoid multiple RB are set in the forwarding as a multicast tree at the same time It is standby, so when multicast tree is distributed in the downstream direction, a RB can only be assigned as the spare of multicast tree and turn originator.
Specifically, Explicit designation is the primary of which multicast tree and is the spare forwarding of which multicast tree on each RB Equipment, the distribution information of the multicast tree of uplink and downlink as shown in Figure 3, in LAG1, RB1 is the primary forwarding of T1 and T4, It is the spare forwarding unit of T3;In LAG2, RB1 is the primary forwarding unit of T2 and T3, is the spare forwarding unit of T1.
In this approach, it is the primary and backup forwarding unit that needs some multicast tree of Explicit designation, for each multicast Tree, under certain LAG of RB v, it is its primary forwarding unit and spare forwarding unit that can only have a RB.So when RB receives group After the notice message broadcast, according to the fault message carried in the information and notice message locally preserved, it is possible to judge be It is no to need to forward received multicast data flow.
When certain RB receives the multicast data flow along multicast tree down direction, judge whether the RB is the multicast tree at certain Primary forwarding unit on LAG down directions, if so, then exporting the flow from corresponding LAG interfaces;Otherwise, the flow is abandoned;
If Fig. 7 is when the stream that RB4 is forwarded along T1 multicast trees reaches RBv, RB1, RB2 and RB3 can receive the stream, But since RB1 is the primary forwarding unit of T1 under LAG1, then the stream can be peeled off connecing by LAG1 after TRILL by RB1 Mouth is forwarded to CE1, and RB2 and RB3 will not forward the stream by the interface of LAG1;While RB2 is primary turn of the T1 under LAG2 Send out equipment, then the stream can also be peeled off after TRILL and be forwarded to CE2 by the interface of LAG2 by RB2, and RB1 and RB3 will not The stream is forwarded by the interface of LAG2.
It is related to the failure when corresponding RB links break down under the RB failures or certain LAG for each RB Node (specifically, if RB failures, then send notice message by CE;If RB link failures, the corresponding RB of link All perceive failure with CE, then can be that RB or CE or both send notice) by multicast message (can be control Face message processed either data surface OAM message etc.) fault message is flooded in RBv, it is which RB exists to be specified in the message Interface under which LAG breaks down.In other words, that is, the stream in the multicast tree using the RB as primary forwarding unit can not CE is forwarded to by interfaces of the RB in the LAG.After other RB receive notice message, according to the multicast tree locally preserved Information and received notice message are distributed, judges whether oneself is that the multicast tree indicated in the message is standby under the LAG With forwarding unit, if it is, the RB is upgraded to primary forwarding unit of the multicast tree under the LAG, and pass through Corresponding LAG interfaces forwarding multicasting stream;Otherwise, received multicast data flow is abandoned.
Such as Fig. 7, when the RB links between RB1-CE1 in LAG1 break down, the multicast data flow influenced be subject to failure be T1 and Forwardings of the T4 in LAG1 interfaces.So RB2 and RB3 is received after the multicast message learns the failure, and RB2 judges that oneself is The spare forwarding unit of T1s and T4 of the RB1 under LAG1, then RB2 itself will upgrade to primary turn of T1 under LAG1 and T4 Equipment is sent out, and the circulation on T1 and T4 is dealt into by CE1 by the interface under LAG1, RB3 judges oneself not being RB1 under LAG1 The spare forwarding unit of the primary multicast tree T1 and T4 of distribution, then will not be gone down received stream by the interface forwarding of LAG1. Each RB down forwarding on the interface belonging to LAG2 is unaffected.
Application example 3
Only on each RB specify be which multicast tree primary forwarding unit
Under the scene for carrying out RB or RB link fault announcings in application example 3 using mode of unicast.In this case, An only RB can receive the failure of failure RB notices, be not in multiple RB while the primary forwarding as a multicast tree is set Standby, which can show that setting or remaining multiple or all RB of implicit default set for the spare forwarding of a multicast tree It is standby, and then whichever RB breaks down, and can quickly realize the quick protection in RBv.
The distribution information of the multicast tree of the uplink and downlink of distribution as shown in Figure 8, in LAG1, is assigned with for RB1 The binding relationship of { LAG1, T1, T4 }, then it is the forwarding unit of T1 and T4 in LAG1 that can learn RB1, can be used as T2, T3 With the spare forwarding unit of T5;In addition also it is assigned with { LAG1, T2, T5 } for RB2, then it is that T2 and T5 exist that can learn RB2 Forwarding unit in LAG1, can be as the spare forwarding unit for being T1, T3 and T4.{ LAG1, T3 } is assigned with for RB3, can be obtained It is primary forwarding units of the T3 in LAG1 to know RB3, can be as the spare forwarding unit of T1, T2, T4 and T5, it is possible thereby to see Go out, there are two spare forwarding unit RB1 and RB2 under LAG1 for T3, then when the primary forwarding unit failure of T3, need RB1 or RB2 is informed by the fault notification mode of unicast, be forwarded by one of protection.I.e. in this manner, when During some RB link failure, the relevant node of the failure (RB of such as faulty link) can it is random from the remaining RB of place RBv or Based on load balancing principle automatically select one of equipment as the multicast tree influenced by the failure forwarding unit simultaneously Unicast fault message.The equipment for receiving unicast fault message, oneself will upgrade to the multicast tree that is influenced by the failure automatically Primary forwarding unit.Without according to the information and received notice message locally preserved judging to be as application example two It is no to need to forward.
When certain RB receives the multicast data flow along multicast tree down direction, judge whether the RB is the multicast tree at certain Primary forwarding unit on LAG down directions, if so, then exporting the flow from corresponding LAG interfaces;Otherwise, the flow is abandoned;
If Fig. 8 is when the stream that RB4 is forwarded along T3 multicast trees reaches RBv, RB1, RB2 and RB3 can receive the stream, But since RB3 is the primary forwarding unit of T3 under LAG1, then the stream can be peeled off connecing by LAG1 after TRILL by RB3 Mouth is forwarded to CE1, and RB1 and RB2 will not forward the stream by the interface of LAG1;While RB1 is primary turn of the T3 under LAG2 Send out equipment, then the stream can also be peeled off after TRILL and be forwarded to CE2 by the interface of LAG2 by RB1, and RB2 and RB3 will not The stream is forwarded by the interface of LAG2.
For each RB, when RB the or RB links of certain LAG of the RB break down, the relevant node of failure passes through list The mode broadcast sends notice message to one of remaining RB, after the RB receives the message, is known that needs as by the event Hinder the primary forwarding unit of the multicast tree influenced.
Such as Fig. 8, when the RB links between RB3-CE1 in LAG1 break down, then RB3 selections are by the failure message unicast Inform that RB2, RB2 oneself will upgrade to the primary forwarding unit of the multicast tree T3 distributed under LAG1, when RB2 is received from T3 Multicast data flow, then can export the multicast data flow from the interface of LAG1.Each RB down forwarding from shadow on the interface belonging to LAG2 Ring.
Application example four
The application example stresses the flow after fault recovery:
By taking Fig. 7 as an example, after RB1-CE1 is in the link-recovery on LAG1, RB1 or CE1 notice Troubleshooting information To other RB.Here can be ESADI to notice the either mode such as OAM message.
RB2 receives notice message described above, and in conjunction with the information locally preserved, it is T1 and T4 in LAG1 to judge RB1 Primary forwarding unit, then RB2 is retracted for the spare forwarding unit of T1 and T4 in LAG1, and by information announcement to RB1.
RB1 receives the notice of RB2 transmissions, and RB1 is assigned as to the primary forwarding unit of T1 and T4 in LAG1.
Corresponding to preceding method, present invention also offers a kind of route-bridge (RB), as shown in figure 9, the route-bridge bag Include:
Assignment information storage unit, for storing the distribution information of multicast tree, the multicast tree be by up direction and under What line direction distributed respectively;
Multicast data flow retransmission unit, the distribution information for multicast tree forward uplink and/or downstream multicast stream.
Alternatively, the multicast data flow retransmission unit includes:
Multicast data flow receiving module, for receiving the multicast data flow along multicast tree upstream or downstream direction;
Multicast data flow judgment module, for judging whether it is the forwarding of the multicast tree in the corresponding direction according to distribution information Equipment;
Multicast data flow forwarding module, for when being judged as the forwarding unit of multicast tree, forwarding the multicast data flow, otherwise abandoning should Multicast data flow.
Preferably, the multicast tree is divided in down direction in each link aggregation group (LAG) or local area network (LAN) Match somebody with somebody.
Preferably, a multicast tree includes a primary forwarding unit and one or several in the RB that down direction distributes Spare forwarding unit, the multicast data flow judgment module judge the primary forwarding unit of its multicast tree in the downstream direction, described group Stream forwarding module is broadcast when being judged as the primary forwarding unit of multicast tree, the multicast data flow is forwarded, otherwise abandons the multicast data flow.
As shown in Figure 10, the route-bridge (RB) further includes:
Information receiving unit, for when the route-bridge (RB) or its corresponding link break down, receiving failure letter Breath;
State updating unit, is receiving spare turn of fault message and route-bridge (RB) the unaffected multicast tree Equipment is sent out, is updated to the primary forwarding unit of the multicast tree.
Specifically, the multicast tree includes a primary forwarding unit and a spare forwarding in the RB that down direction distributes Equipment, the fault message are sent by the relevant node of failure by way of multicast.
The distribution information of the assignment information storage unit storage only includes the distribution information of the multicast tree of itself, a group Broadcast tree and multicast is passed through by the relevant node of failure in one spare forwarding unit of down direction explicit allocation, the fault message Mode is sent, the fault message of the multicast include LAG where impacted multicast tree information or impacted multicast tree or LAN information;Or,
The distribution information of the multicast tree of the assignment information storage unit storage includes the multicast tree of itself and other each RB Distribution information, a multicast tree is in one spare forwarding unit of down direction explicit allocation, and the fault message is by failure phase The node of pass is sent to spare forwarding unit by way of unicast.
Alternatively, a multicast tree explicitly or implicitly distributes several spare forwarding units, the distribution in down direction The distribution information of the multicast tree of information memory cell storage includes the distribution information of the multicast tree of itself and other each RB, described former Barrier information is sent by way of unicast, and the RB for receiving the fault message is one of them spare turn of impacted multicast tree Send out equipment.
Preferably, as shown in figure 11, the route-bridge further includes fault information generation unit, for according to the multicast The distribution information of tree is randomly or based on load balancing and determines the unicast object that fault message is sent.
Specifically, the assignment information storage unit obtains itself and other using same multicast tree allocation algorithm or configuration The distribution information of the multicast tree of each RB, or configuration obtain the distribution information of the multicast tree of itself, and interaction obtains other each RB's Multicast tree information.
Understandably, as described above, when RB breaks down, fault message is sent by CE.
Preferably, information receiving unit, is additionally operable to, when the route-bridge is current primary forwarding unit, receive former main With forwarding unit or the Troubleshooting information of its corresponding link;
State updating unit, after Troubleshooting information is received, is updated to the spare forwarding unit of the multicast tree.
The method of the present invention and route-bridge, the multicast tree in the distribution information of the multicast tree is by up direction and downlink What direction was distributed respectively, therefore, when down direction breaks down, the multicast data flow forwarding of up direction is not interfered with, in addition, should Scheme of the invention is under RBv scenes, when access link or access RB failures, it is not necessary to which distal end RB perceives failure, by RBv Interior RB quickly protects the multicast packet of down direction, it is ensured that end system normally receives service traffics.In addition, the invention Scheme is not only supported only to dispose the scene of a LAG under a RBv, also supports to dispose the scene of multiple LAG under a RBv, i.e., Forwarding distribution of the multicast tree in down direction on RBv is in the granularity in LAG, when certain RB is belonging to the RB interfaces event of certain LAG During barrier, the multicast data flow only influenced by the failure just can be gone to forward by spare forwarding unit, and then realize end system to TRILL The high reliability access of network.
Units/modules described in the embodiment of the present invention are only a kind of examples divided according to its function, can be managed Xie Di, in the case where realizing identical function, those skilled in the art can provide other one or more function dividing modes, Wherein any one or more function modules can be realized using a functional entity device or unit during concrete application, could not Recognize ground, above mapping mode is within the application protection domain.
Embodiment described herein is only part of the embodiment of the present invention, and not all embodiment.Based on this hair Embodiment in bright, the every other reality that those of ordinary skill in the art are obtained on the premise of creative work is not made Example is applied, belongs to the scope of protection of the invention.

Claims (19)

1. a kind of multicast data flow forwards implementation method, it is characterised in that:Each route-bridge (RB) turns according to the distribution information of multicast tree The upstream or downstream multicast data flow received is sent out, the multicast tree is distributed respectively by up direction and down direction;One group The route-bridge (RB) that tree is broadcast in down direction distribution is set including a primary forwarding unit and one or several spare forwardings Standby, the route-bridge (RB) forwards the multicast data flow of the multicast tree when judging it for the primary forwarding unit of multicast tree, otherwise Abandon the multicast data flow.
2. the method as described in claim 1, it is characterised in that:Each route-bridge (RB) is according to the distribution information of multicast tree Forwarding the process of the upstream or downstream multicast data flow received includes:
Receive the multicast data flow in multicast tree upstream or downstream direction;
Judge whether it is forwarding unit of the multicast tree on corresponding direction according to distribution information;
If so, then forwarding the multicast data flow, the multicast data flow is otherwise abandoned.
3. the method as described in claim 1, it is characterised in that:The multicast tree is in each link aggregation group in down direction (LAG) or in local area network (LAN) distribute.
4. the method as described in claim 1, it is characterised in that:The distribution information of the multicast tree only includes the multicast of current RB The distribution information of tree, one spare forwarding unit of a multicast tree explicit allocation in the downstream direction, route-bridge (RB) or its Corresponding link breaks down, other all route-bridge (RB) the multicast failure letters of the relevant node of failure into place RBv Breath;The fault message of the multicast includes the LAG or LAN where impacted multicast tree information or/and impacted multicast tree Information;Receive fault message and the spare forwarding unit for impacted multicast tree upgrades to the primary forwarding of the multicast tree and sets It is standby.
5. the method as described in claim 1, it is characterised in that:The distribution information of the multicast tree includes current RB and other are each The distribution information of the multicast tree of RB, in the downstream direction one spare forwarding unit of a multicast tree explicit allocation, route-bridge (RB) or its corresponding link breaks down, and the relevant node of failure sends failure to the spare forwarding unit of impacted multicast tree Information;The spare forwarding unit for receiving fault message upgrades to the primary forwarding unit of the multicast tree.
6. the method as described in claim 1, it is characterised in that:The distribution information of the multicast tree includes current RB and other are each The distribution information of the multicast tree of RB, in the downstream direction a multicast tree explicitly or implicitly distribute several spare forwarding units When, when route-bridge (RB) or its corresponding link break down, impacted multicast of the relevant node of failure into place RBv A spare forwarding unit for tree sends fault message;The spare forwarding unit for receiving the fault message upgrades to impacted multicast The primary forwarding unit of tree.
7. method as claimed in claim 6, it is characterised in that:The relevant node of failure is according to the distribution information of the multicast tree Load balancing is randomly or based on to determine to upgrade to the spare forwarding unit of primary forwarding unit.
8. the method as described in claim 5 or 6, it is characterised in that:Each route-bridge (RB) is calculated using the distribution of same multicast tree Method or configuration obtain the distribution information of the multicast tree, or are obtained after configuring the distribution information for obtaining the multicast tree of itself by interaction Take the multicast tree information of other each RB.
9. method as claimed in claim 4, it is characterised in that:Current primary forwarding unit receive former primary forwarding unit or its After the Troubleshooting information of corresponding link, switch to spare forwarding unit again.
A kind of 10. route-bridge (RB), it is characterised in that:The route-bridge includes:
Assignment information storage unit, for storing the distribution information of multicast tree, the multicast tree is by up direction and downlink side To what is distributed respectively;
Multicast data flow retransmission unit, for forwarding uplink and/or downstream multicast stream according to the distribution information of multicast tree;
One multicast tree includes a primary forwarding unit in the RB that down direction distributes and one or several spare forwardings are set Standby, the multicast data flow judgment module judges whether it is the primary forwarding unit of multicast tree in the downstream direction, the multicast data flow Forwarding module forwards the multicast data flow when being judged as the primary forwarding unit of multicast tree, otherwise abandons the multicast data flow.
11. route-bridge (RB) as claimed in claim 10, it is characterised in that:The multicast data flow retransmission unit includes:
Multicast data flow receiving module, for receiving the multicast data flow in the upstream or downstream direction in multicast tree;
Multicast data flow judgment module, for judging whether it is that the forwarding of the multicast tree in the corresponding direction is set according to distribution information It is standby;
Multicast data flow forwarding module, in the forwarding unit on being judged as multicast tree, forwarding the multicast data flow, otherwise abandons the group Broadcast stream.
12. route-bridge (RB) as claimed in claim 10, it is characterised in that:The multicast tree is in down direction in each chain Distribution in road aggregation group (LAG) or local area network (LAN).
13. route-bridge (RB) as claimed in claim 10, it is characterised in that the route-bridge (RB) further includes:
Information receiving unit, for when the route-bridge (RB) or its corresponding link break down, receiving fault message;
State updating unit, sets in the spare forwarding for receiving fault message and route-bridge (RB) the unaffected multicast tree It is standby, it is updated to the primary forwarding unit of the multicast tree.
14. route-bridge (RB) as claimed in claim 13, it is characterised in that:Point of the assignment information storage unit storage Only include the distribution information of the multicast tree of itself with information, in the downstream direction the one spare forwarding of a multicast tree explicit allocation Equipment, the fault message are sent by the relevant node of failure by way of multicast, the fault message of the multicast include by LAG or LAN information where the multicast tree information or impacted multicast tree of influence;Or, the assignment information storage unit is deposited The distribution information of the multicast tree of storage includes the distribution information of the multicast tree of itself and other each RB, in the downstream direction a multicast One spare forwarding unit of explicit allocation is set, the fault message is sent to standby by the relevant node of failure by way of unicast Use forwarding unit.
15. route-bridge (RB) as claimed in claim 13, it is characterised in that:The group of the assignment information storage unit storage Broadcasting the distribution information of tree includes the distribution information of multicast tree of itself and other each RB, and a multicast tree is explicit in the downstream direction Or implicit assignment several spare forwarding units, the fault message are sent by way of unicast, receive the fault message RB be impacted multicast tree one of them spare forwarding unit.
16. route-bridge (RB) as claimed in claim 13, it is characterised in that:The route-bridge (RB) further includes:
Information synchronizing unit is distributed, the distribution information for the synchronous respective multicast trees of the RB with same RBv;
The fault message is sent by the relevant node of failure according to synchronous distribution information by way of unicast.
17. route-bridge (RB) as claimed in claim 15, it is characterised in that:The route-bridge further includes fault message hair Send unit, for according to the distribution information of the multicast tree be randomly or based on load balancing determine fault message send list Broadcast object.
18. the route-bridge as described in claims 14 or 15, it is characterised in that:The assignment information storage unit utilizes same The distribution information of multicast tree allocation algorithm or the multicast tree of configuration acquisition itself and other each RB, or configuration obtain the multicast of itself The distribution information of tree, and interaction obtains the multicast tree information of other each RB.
19. route-bridge (RB) as claimed in claim 13, it is characterised in that:Information receiving unit, is additionally operable on the road When by bridge being current primary forwarding unit, former primary forwarding unit or the Troubleshooting information of its corresponding link are received;
State updating unit, after Troubleshooting information is received, is updated to the spare forwarding unit of the multicast tree.
CN201210470320.4A 2012-11-20 2012-11-20 Multicast data flow forwards implementation method and route-bridge(RB) Active CN102970231B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201210470320.4A CN102970231B (en) 2012-11-20 2012-11-20 Multicast data flow forwards implementation method and route-bridge(RB)
PCT/CN2013/082327 WO2014079246A1 (en) 2012-11-20 2013-08-27 Multicast flow forwarding implementation method and routing bridge (rb)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201210470320.4A CN102970231B (en) 2012-11-20 2012-11-20 Multicast data flow forwards implementation method and route-bridge(RB)

Publications (2)

Publication Number Publication Date
CN102970231A CN102970231A (en) 2013-03-13
CN102970231B true CN102970231B (en) 2018-05-01

Family

ID=47800118

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201210470320.4A Active CN102970231B (en) 2012-11-20 2012-11-20 Multicast data flow forwards implementation method and route-bridge(RB)

Country Status (2)

Country Link
CN (1) CN102970231B (en)
WO (1) WO2014079246A1 (en)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102970231B (en) * 2012-11-20 2018-05-01 中兴通讯股份有限公司 Multicast data flow forwards implementation method and route-bridge(RB)
CN103973471B (en) * 2013-01-31 2018-11-02 中兴通讯股份有限公司 A kind of notifying method and device of TRILL distribution trees failure
CN104426777B (en) * 2013-09-03 2018-07-13 华为技术有限公司 Route renewing method and routing device
CN104601477B (en) * 2013-10-31 2018-08-21 华为技术有限公司 The cut-in method and route bridging equipment of TRILL network
CN104702506B (en) * 2013-12-09 2018-10-19 华为技术有限公司 A kind of message transmitting method, network node and message transfer system
CN104717140B (en) * 2013-12-11 2018-03-09 华为技术有限公司 The fault handling method and device of edge route bridge device in TRILL network
CN110120906B (en) * 2014-05-13 2021-04-20 华为技术有限公司 Method and device for realizing dual active access TRILL park edge
CN106330703A (en) * 2015-06-16 2017-01-11 中兴通讯股份有限公司 Route selection method and device, routing bridge and network
CN112822097A (en) * 2019-11-15 2021-05-18 华为技术有限公司 Message forwarding method, first network device and first device group
CN111988220B (en) * 2020-08-14 2021-05-28 山东大学 Multi-target disaster backup method and system among data centers based on reinforcement learning

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101170503A (en) * 2007-11-23 2008-04-30 中兴通讯股份有限公司 An optimization method for multicast route ant group algorithm
CN101459596A (en) * 2007-12-14 2009-06-17 华为技术有限公司 Method, system and equipment for multicast data transmission

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005244319A (en) * 2004-02-24 2005-09-08 Casio Comput Co Ltd Information distribution system and information distribution method
US7653075B2 (en) * 2005-05-23 2010-01-26 Juniper Networks, Inc. Processing communication flows in asymmetrically routed networks
CN102025541B (en) * 2010-12-08 2014-12-10 中兴通讯股份有限公司 Method and system for realizing multicast protection
CN102970231B (en) * 2012-11-20 2018-05-01 中兴通讯股份有限公司 Multicast data flow forwards implementation method and route-bridge(RB)

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101170503A (en) * 2007-11-23 2008-04-30 中兴通讯股份有限公司 An optimization method for multicast route ant group algorithm
CN101459596A (en) * 2007-12-14 2009-06-17 华为技术有限公司 Method, system and equipment for multicast data transmission

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Coordinated Multicast Trees (CMT) for TRILL;Tissa Senevirathne,等;《TRILL Working Group Internet Draft》;20121108;1-14页 *
组播技术在FTTHEPON系统中的应用;喻文学;《电信网技术》;20111215;26-27页 *

Also Published As

Publication number Publication date
WO2014079246A1 (en) 2014-05-30
CN102970231A (en) 2013-03-13

Similar Documents

Publication Publication Date Title
CN102970231B (en) Multicast data flow forwards implementation method and route-bridge(RB)
US9197583B2 (en) Signaling of attachment circuit status and automatic discovery of inter-chassis communication peers
US8964531B2 (en) Resilient attachment to provider link state bridging (PLSB) networks
US8953590B1 (en) Layer two virtual private network having control plane address learning supporting multi-homed customer networks
US8694664B2 (en) Active-active multi-homing support for overlay transport protocol
EP2498454B1 (en) Method, device and system for processing service traffic based on pseudo wires
CN109660442B (en) Method and device for multicast replication in Overlay network
EP3340550B1 (en) Service message multicast method and device
US7876673B2 (en) Prevention of frame duplication in interconnected ring networks
KR20070005654A (en) Differential forwarding in address-based carrier networks
CN101577719B (en) A kind of double hot standby method, device and system
CN111935013B (en) Flow forwarding control method and device, flow forwarding method and chip, and switch
CN102638389A (en) Redundancy backup method and system of TRILL (Transparent Interconnection over Lots of Links) network
CN107040441B (en) Cross-data-center data transmission method, device and system
US20160014032A1 (en) Method and Device for Flow Path Negotiation in Link Aggregation Group
US11546267B2 (en) Method for determining designated forwarder (DF) of multicast flow, device, and system
CN108964940A (en) Message method and device, storage medium
WO2018058639A1 (en) Pseudo wire load sharing method and apparatus
US10225091B2 (en) Method for implementing point-to-multipoint multicast, network node, and system
US9008118B2 (en) Multicast data delivery over mixed multicast and non-multicast networks
CN105490937B (en) Ether virtual network gateway switching method and service provider's edge node devices
CN104009903A (en) Flow forwarding method and device for RPR network
WO2015027736A1 (en) Method and device for implementing hierarchical virtual private lan service
CN107547347B (en) VNI-based path adjustment method and device
US9548887B2 (en) Proactive creation of multicast state in an overlay transport network to achieve fast convergence on failover

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant