CN102238057B - Ethernet-tree realization method, system, device and network equipment - Google Patents
Ethernet-tree realization method, system, device and network equipment Download PDFInfo
- Publication number
- CN102238057B CN102238057B CN2011101202702A CN201110120270A CN102238057B CN 102238057 B CN102238057 B CN 102238057B CN 2011101202702 A CN2011101202702 A CN 2011101202702A CN 201110120270 A CN201110120270 A CN 201110120270A CN 102238057 B CN102238057 B CN 102238057B
- Authority
- CN
- China
- Prior art keywords
- node
- update message
- routing update
- configuration
- node type
- 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.)
- Expired - Fee Related
Links
Images
Abstract
The invention discloses an Ethernet-tree realization method, an Ethernet-tree realization system, an Ethernet-tree realization device and network equipment. The method comprises that: a first provider edge (PE) transmits a reachable route updating message carrying the node type of a first connected customer edge (CE) to a second PE, wherein the node type comprises a leaf node and a root node; and when receiving the route updating message, the second PE judges whether the first CE is the leaf node or the root node according to the node type carried in the route updating message, traverses each second CE connected with the second PE, and for each second CE, does not establish a pseudo wire between the first and second CEs between the second PE and the first PE if the first and second CEs are both the leaf nodes, otherwise tries to establish the pseudo wire between the first and second CEs between the second PE and the first PE. The node type is announced by the route updating message, and the leaf nodes are isolated so as to avoid the establishment of the pseudo wire between the leaf nodes and simply and conveniently realize an Ethernet-tree.
Description
Technical field
The present invention relates to network communications technology field, espespecially a kind of Ethernet foundation multipoint service implementation method, system, device and network equipment based on virtual special local area network.
Background technology
(MEF) 10.1 of Metro Ethernet Forum and MEF6.1 have defined three kinds of Ethernet services: point-to-point ether circuit (E-line, Ethernet line), multi-multipoint ethernet local area network (E-LAN, Ethernet LAN) and the foundation multipoint service of point-to-multipoint (E-tree, Ethernet Tree).E-TREE is E-LAN and the hybrid technology of E-LINE: in the E-TREE example, both may exist multi-multipoint (E-LAN) to be connected, and also may exist point-to-point (E-LINE) to connect.From this angle, E-LAN is a special E-TREE, and its all node is all root node, there is no the restriction of communication.
The E-TREE technology can be the user services such as internet access, IPTV (Internet Protocol Television, IPTV), the clock distribution of movable signal tunnel is provided.As Fig. 1 is the principle schematic of a typical E-TREE application scenarios.In Fig. 1, provider edge equipment PE1, PE2, PE3, PE4 belong to same Virtual Switch Instance (Virtual Forwarding Instance, VFI), PE1 is by access link (Attachment Circuit, AC) " root 1 ", " leaf 1 " provides two layers of service for CE 1 and CE 2; PE2 provides two layers of service by access link " leaf 2 " for CE 3; PE3 provides two layers of service by access link " leaf 3 " for CE4; PE4 is CE5, by access link " leaf 4 ", for CE6, provides two layers of service by access link " root 2 ".
As the customer edge devices (CE) by root access link access in Fig. 1 can be referred to as root node, can with example in all CE devices communicatings; CE equipment by leaf access link access can be referred to as leaf node, can only with example in pass through the CE devices communicating that the root access link accesses.That is: root node CE1, CE5 can with all devices communicatings, but can not communicate by letter between leaf node CE2, CE3, CE4, CE6.
To realize that at present above-mentioned E-TREE technology has two kinds of implementations, the individual draft that these two kinds of Internet Engineering task groups Layer 2 virtual private network IETF L2VPN working groups propose is all based on VPLS (Virtual Private LAN Service, VPLS) expansion realizes the E-TREE function, wherein:
Scheme one: the tag distribution protocol (Label Distribution Protocol, LDP) of take is expanded as signaling generates VPLS.
Specifically based on Request for Comment (Request for Comment, RFC) 4762 solutions that realize E-TREE, with 2 VPLSs of pseudo-line expansion based on tag distribution protocol, realize, specifically referring to the associated description of draft-ram-l2vpn-ldp-vpls-etree-2pw-00.txt, this mode is by tag distribution protocol (Label Distribution Protocol, LDP) signaling is set up the bi-directional pseudo circuit and is realized between root node.And consult the access link type by signaling root AC and leaf AC are distinguished, this mode is limited to the LDP mode that adopts.
Scheme two: the control word field at two layer message is carried the AC type, and the information of carrying according to the control word field at receiving terminal PE place judges whether to forward to the own leaf node connected.
Particularly, this scheme need to realize by control word, carry AC Type Control word in the message sent, when receiving terminal PE receives this message, determine whether that according to the control word of carrying in message the leaf node that will connect to oneself E-Packets, if the AC type of the control word of carrying in message indication is leaf access link type, what can determine the transmission message is leaf node, the leaf node no longer connected to self E-Packets, but by packet loss.Because be is just processed message according to control word after receiving terminal PE receives message, this makes some originally not need the message sent to be sent out, and these unnecessary message repeatings will inevitably cause the waste of network bandwidth resources.
The above-mentioned implementation that realizes that foundation multiple spot (E-TREE) is served all can not realize the communication isolating between leaf node simply and easily, and can cause the waste of Internet resources.
Summary of the invention
The embodiment of the present invention provides a kind of Ethernet foundation multipoint service implementation method, system, device and the network equipment, in order to solve in prior art the communication isolating that can not realize simply and easily between leaf node, the problem that causes network resources waste of existing.
A kind of Ethernet foundation multipoint service implementation method comprises:
The first provider edge equipment PE sends two PE of the routing update message reached of the node type of carrying the first connected customer edge devices CE to opposite end; Described node type comprises leaf node and root node;
When the 2nd PE receives described routing update message, according to the node type of carrying in described routing update message, judge that a described CE is leaf node or root node; And travel through each the 2nd CE self connected, for each the 2nd CE, if when a described CE and the 2nd CE are leaf node, between self and a PE, do not set up the pseudo-circuit between a CE and the 2nd CE; Otherwise attempt setting up the pseudo-circuit between a CE and the 2nd CE between self and a PE.
A kind of Ethernet foundation multipoint service implement device comprises:
Receiver module, for receiving the routing update message reached of the node type of carrying the first connected customer edge devices CE that the first provider edge equipment PE sends; Described node type comprises leaf node and root node;
Judge module, when receiving the routing update message that a PE sends, according to the node type of carrying in the routing update message received, judge that a described CE is leaf node or root node;
Set up module, for traveling through each the 2nd CE self connected, for each the 2nd CE, if when a described CE and the 2nd CE are leaf node, between self and a PE, do not set up the pseudo-circuit between a CE and the 2nd CE; Otherwise attempt setting up the pseudo-circuit between a CE and the 2nd CE between self and a PE.
A kind of provider edge equipment comprises: above-mentioned Ethernet foundation multipoint service implement device.
A kind of Ethernet foundation multipoint service is realized system, comprising: the customer edge devices that the customer edge devices that node type is leaf node, some node types are root node and at least two above-mentioned provider edge equipments;
The customer edge devices that described node type is leaf node is connected with affiliated provider edge equipment by the leaf access link, and the customer edge devices that described node type is root node is connected with affiliated provider edge equipment by the root access link.
Beneficial effect of the present invention is as follows:
Ethernet foundation multipoint service implementation method, system, device and the network equipment that the embodiment of the present invention provides, the node type that the one PE carries a connected CE in the routing update message reached sent, the 2nd PE is according to the node type of the node type of carrying in routing update message and the 2nd CE that self connects, determine between a CE and the 2nd CE and whether can set up pseudo-circuit, realize communication connection, realized easily the isolation to leaf node.The method realizes Ethernet foundation multipoint service by the negotiation of two ends PE, does not need existing protocol is done to more improvement, has reduced as much as possible the improvement to existing signaling, and has not needed to improve network configuration, without extra cost, drops into.
The accompanying drawing explanation
The principle schematic that Fig. 1 is E-TREE application scenarios in prior art;
The flow chart that Fig. 2 is Ethernet foundation multipoint service implementation method in the embodiment of the present invention;
The handling process schematic diagram that Fig. 3 is receiving terminal PE in the embodiment of the present invention;
The handling process schematic diagram that Fig. 4 is transmitting terminal PE in the embodiment of the present invention;
The structural representation that Fig. 5 is Ethernet foundation multipoint service implement device in the embodiment of the present invention.
Embodiment
Owing to can not facilitating in prior art, simply realizing, according to the pseudo-circuit of multipoint service, set up, the embodiment of the present invention provides a kind of Ethernet foundation multipoint service implementation method, on the RFC4761 basis, realize the identification of node type by routing update message, realize the solution of E-TREE based on existing VPLS technological expansion.
The Ethernet foundation multipoint service implementation method that the embodiment of the present invention provides, its flow process as shown in Figure 2, performs step as follows:
Step S101: the first provider edge equipment PE sends two PE of the routing update message reached of the node type of carrying the first connected customer edge devices CE to opposite end.
The one PE to neighbours' the 2nd PE announcement the time carry multi-protocols and can reach (MP_REACH, Multi-Protocol REACH) routing update of information (UPDATE) message, the node type that specifically can in two layers of extended community attribute of routing update message, carry a CE.
Transmission is carried the routing update message of node type of a connected CE to before the PE of opposite end, is a CE configuration node attribute, and the nodal community of configuration comprises node type, and wherein, node type comprises leaf node and root node.
It is the label radix that the nodal community of a CE configuration also comprises customer edge devices ID, customer edge devices ID block offset, customer edge devices ID block size and tag control module assignment.Wherein, the parameters such as the customer edge devices ID that provider edge equipment PE is each node configuration, customer edge devices ID block offset, customer edge devices ID block size, label radix, send to the 2nd PE of opposite end by Network Layer Reachable Information (Network Layer Reach Information, NLRI).Preferably, the routing update message that sends the node type carry a connected CE is during to the 2nd PE of opposite end, and in the routing update message sent, carrying is the Network Layer Reachable Information of a CE configuration.
For example: as shown in Figure 1, set up the VPLS example between PE1, PE2, PE3, PE4, wherein, root node CE1 is connected with PE1 by the root access link, and leaf node CE2 is connected with PE1 by the leaf access link; Leaf node CE3 is connected with PE2 by the leaf access link; Leaf node CE4 is connected with PE3 by the leaf access link; Root node CE5 is connected with PE4 by the root access link with leaf node CE6.
Step S102: the 2nd PE receives the routing update message that a PE sends.
When the 2nd PE receives the routing update message of a PE transmission, the routing update message received is resolved, parsed the information such as node type of wherein carrying.
When the 2nd PE receives routing update message, by its preservation and can check local configuration, find that there is the routing update message received and belong to the configuration information in same E-TREE, start follow-up negotiations process, simultaneously, differentiate whether can set up pseudo-circuit.
Step S103: according to the node type of carrying in routing update message, judge that a CE is leaf node or root node.
The 2nd PE is according to the node type of carrying in the routing update message parsed, and the node type that judges a CE is leaf node or root node.
In order to realize the isolation between leaf node, carry node type information by routing update message, make recipient's the 2nd PE can get the node type of an announced CE.
Continue to use the example of top, after PE1, PE2, PE3, PE4, PE5 are the CE configuration node attribute that connected separately, the routing update message that announcement comprises node type, for example PE1 is CE1 configuration node attribute, carry the routing update message that node type is root node, PE1 is CE2 configuration node attribute, carries the routing update message that node type is leaf node; Other PE are also similar while sending routing update message.
Step S104: travel through each the 2nd CE self connected, for each the 2nd CE, if when a CE and the 2nd CE are leaf node, between self and a PE, do not set up the pseudo-circuit between a CE and the 2nd CE; Otherwise attempt setting up the pseudo-circuit between a CE and the 2nd CE between self and a PE.
The 2nd PE can travel through connected all the 2nd CE, according to the node type of carrying in routing update message, judge whether the 2nd CE that the related CE of routing update message of a PE bulletin is connected with self is all leaf node, realize differentiation successively respectively the 2nd CE whether can set up pseudo-circuit with a CE; When judging while all being leaf node, can not set up pseudo-circuit, otherwise attempt setting up pseudo-circuit.
When attempting setting up pseudo-circuit, the Network Layer Reachable Information that comprises a CE of a PE announcement in the routing update message received due to the 2nd PE, the 2nd PE calculates label according to receiving the Network Layer Reachable Information carried in routing update message, and calculates into label according to the Network Layer Reachable Information from as the 2nd CE configuration.Can calculate label and enter label by the existing protocol regulation, realize the configuration of forwarding face.
Continue to use the example of top, PE1 is the CE2 configuration attribute, and sends the routing update message that comprises the node type leaf node, and when node PE4 receives this routing update message, judging CE2 is leaf node.And travel through CE5 and the CE6 self connected, for CE5, because CE5 is root node, can connect with leaf node CE2, thus PE4 self with PE1 between set up the pseudo-circuit of associated CE2 and CE5; For CE6, because CE6 is leaf node, can not connect with leaf node CE2, so PE4 not self with PE1 between set up the pseudo-circuit of associated CE2 and CE5.
Above-mentioned Ethernet foundation multipoint service implementation method also comprises:
Step S105: when a PE or the 2nd PE generation nodal community configuration variation, the routing update message that transmission can reach is to the 2nd PE or a PE.Nodal community configuration variation by a PE or the 2nd PE triggers.
The 2nd PE or a PE, according to the routing update message received, determine whether to maintain the pseudo-circuit of having set up, and when not needing to maintain, delete pseudo-circuit.
Above-mentioned Ethernet foundation multipoint service implementation method also comprises:
Step S106: the configuration that the CE that connects occurs as a PE or the 2nd PE delete or other while causing the event of pseudo-line disconnections of connected CE, send and carry the routing update message of the connected unreachable information of CE to the 2nd PE or a PE.
Step S105 and 106 execution sequence in no particular order, are also not necessarily carried out after step S104, but are triggered by the nodal community configuration variation of a PE or the 2nd PE.
Continue to use the example of top, an equipment is for example arranged in PE1 or PE4, suppose it is PE4, occur that configuration is deleted or other are while causing pseudo-line disconnection, send the routing update message message with unreachable (MP_UNREACH) information to neighbours PE4 or PE1, realize removing pseudo-circuit.
Each PE all can be according to local decision-making, and whether the configuration of monitoring local CE changes, and when causing the variation of pseudo-line disconnection, sends inaccessible routing update message.
Handling process when wherein PE receives inaccessible routing update message is same as the prior art.
The above-mentioned Ethernet foundation multipoint service implementation method that the embodiment of the present invention provides, when provider edge equipment PE sends routing update message as a PE, its realization flow as shown in Figure 3, comprises the steps:
Step S201: while finding that a CE who self connects needs configuration attribute, the configuration routing update message.
It is generally now the routing update message that configuration can reach, carry node type in two layers of extended community attribute in routing update message, specifically utilize one of them control mark byte to carry node type, as following table 1 is two layers of form in extended community attribute:
Table 1
| ? | Explanation | Byte number | |
| ?Extended?community?type | The extended |
2 bytes | |
| ?Encaps?Type | Encapsulated type | 1 byte | |
| ?Control?Flags | Control mark | 1 byte | |
| ?Layer-2MTU | Two layers of |
2 bytes | |
| ? | Reserve bytes | 2 bytes |
Wherein, being described as follows of control mark field:
Wherein, MBZ=MUST Be Zero, front 5 bytes are 0.L be in the present invention to the extension of control mark, carry node type information.If CE is the leaf website must be set to 1, otherwise is set to 0; Generally can be defaulted as 0, represent the root website.The control word information that C is the existing standard definition.The sequence number information that S is the existing standard definition.
The acquiescence node type configured due to PE is root node, therefore when the CE that needs the configuration node attribute is the root website, without the configuration node type; When the CE that needs the configuration node attribute is leaf node, the bit 5 in two layers of extended community attribute in routing update message is set to 1.
Except comprising two layers of extended community attribute, also be included as the Network Layer Reachable Information of CE configuration in the configuration routing update message.
Step S202: the 2nd PE to opposite end sends routing update message.
The coding such as node type and Network Layer Reachable Information is formed to routing update message, the routing update message that can reach to neighbours' the 2nd PE announcement.
Make and follow-uply can consult to realize the communication isolating between leaf node by node type.
The above-mentioned Ethernet foundation multipoint service implementation method that the embodiment of the present invention provides, when provider edge equipment PE receives routing update message as the 2nd PE, its realization flow as shown in Figure 4, comprises the steps:
Step S301: the routing update message reached that receives a CE of a PE transmission.
According to above-mentioned steps S102, the route updating message is resolved and preserved.
Step S302: determine that a CE is root node or leaf node.
Root node or leaf node while according to the node type in routing update message, determining a CE, with reference to step S103.
Step S303: travel through locally-attached the 2nd CE information.
The route target (Route Target, RT) of take is the major key of E-TREE example, searches the CE information under this major key RT.
Step S304: judge whether a CE and current the 2nd CE found are all leaf nodes.
Obtain the node type of a CE in two layers of extended community attribute from the routing update message reached of a PE announcement, and check the node type of the 2nd local CE, if a CE is leaf node with the 2nd local CE, execution step S306; Otherwise, execution step S305.
Step S305: the pseudo-circuit of setting up a CE and the 2nd CE between self and a PE.
After the pseudo-circuit of RFC4761 normalization, the Network Layer Reachable Information of a CE who announces in the routing update message reached sent according to a PE, with this locality Network Layer Reachable Information that is the 2nd CE configuration, regulation according to existing RFC 4761 standards is calculated into label and outgoing label, and be issued to forwarding face, realize the communication connection of a CE and the 2nd CE.
Step S306: whether traveled through locally-attached all the 2nd CE.
When all being leaf node, can not set up pseudo-circuit.Start to process next CE.
If, execution step S307; Otherwise, return and continue execution step S303.
Step S307: finish.
While having traveled through all websites in the E-TREE example, process ends.
Above-mentioned Ethernet foundation multipoint service implementation method, expanded Ethernet foundation multipoint service to the VPLS realization of RFC 4761, negotiates both sides' type of site by signaling, at the MPLS network, realizing the E-TREE function.
The Ethernet foundation multipoint service implementation method provided based on the embodiment of the present invention, the embodiment of the present invention also provides a kind of Ethernet foundation multipoint service implement device, this device can be arranged in provider edge equipment, its structure as shown in Figure 5, comprising: receiver module 101, judge module 102 and set up module 103.
Set up module 103, for traveling through each the 2nd CE self connected, for each the 2nd CE, if when a CE and the 2nd CE are leaf node, between self and a PE, do not set up the pseudo-circuit between a CE and the 2nd CE; Otherwise attempt setting up the pseudo-circuit between a CE and the 2nd CE between self and a PE.
Preferably, above-mentioned Ethernet foundation multipoint service implement device also comprises: sending module 104, the routing update message of the node type of the 2nd CE that the 2nd PE under carrying for transmission connects is to a PE of opposite end.
Preferably, above-mentioned sending module 104, send to a PE of opposite end specifically for the node type of carrying described the 2nd CE in two layers of extended community attribute of described routing update message.
Preferably, above-mentioned sending module 104, also for: when the nodal community configuration variation occurs the 2nd PE, the routing update message that transmission can reach is to a PE; The configuration that the CE that connects occurs as affiliated the 2nd PE is deleted or other while causing the event of pseudo-line disconnections of connected CE, send and carry the routing update message of the connected unreachable information of CE to a described PE.
Preferably, above-mentioned Ethernet foundation multipoint service implement device also comprises:
Preferably, above-mentioned Ethernet foundation multipoint service implement device also comprises:
Configuration module 107, the 2nd CE configuration node attribute that the 2nd PE under being used to connects; The nodal community of configuration comprises node type, also comprises customer edge devices ID, customer edge devices ID block offset, customer edge devices ID block size and from the label radix of the tag set of tag control module 106 applications.
When above-mentioned provider edge equipment can be used as the first provider edge equipment, at least comprise sending module 104, tag control module 106 and configuration module 107; While using as the second provider edge equipment, at least comprise receiver module 101, judge module 102, set up module 103 and tag computation module 105.When comprising receiver module 101, judge module 102, set up module 103, when sending module 104, tag computation module 105, tag control module 106 and configuration module 107, whether both can be used as the first provider edge equipment and also can be used as the second provider edge equipment, according to this provider edge equipment,, being specifically configuration node attribute the PE that sends the routing update message that can reach determines as the first provider edge equipment or as the second provider edge equipment.
Above-mentioned Ethernet foundation multipoint service implement device, BGPd (BGP Daemon that can be in the network equipment, the Border Gateway Protocol program) module realizes, by command line interface (Command Line Interface, CLI) module, user's configuration information is announced to the module to BGPd.
The Ethernet foundation multipoint service implementation method provided based on the invention described above embodiment, can also build a kind of Ethernet foundation multipoint service and realize system, and the structure of this system can be shown in Figure 1.This system comprises: the customer edge devices that the customer edge devices that some node types are leaf node, some node types are root node and at least two provider edge equipments; When realizing Ethernet foundation multipoint service, the conduct of at least one provider edge equipment sends the first provider edge equipment of routing update message, and the conduct of at least one provider edge equipment receives the second provider edge equipment of routing update message.
Wherein, the customer edge devices that node type is leaf node is connected with affiliated provider edge equipment by the leaf access link, and the customer edge devices that node type is root node is connected with affiliated provider edge equipment by the root access link.
Ethernet foundation multipoint service implementation method, system and device that the embodiment of the present invention provides, can very easily provide the E-TREE function by the expansion to existing standard.Specifically, by carry the node type of customer edge devices in routing update message, judged by PE whether the CE equipment at two ends is all leaf node, realize leaf node or say the mutual isolation between the leaf link.Utilize the spare field in two layers of extended community attribute in routing update message to carry the information such as node type, based on existing RFC 4761 standards, processed, reduced as much as possible the improvement to existing signaling, and do not need to improve network configuration, drop into without extra cost, realize simple, convenient.
Obviously, those skilled in the art can carry out various changes and modification and not break away from the spirit and scope of the present invention the present invention.Like this, if within of the present invention these are revised and modification belongs to the scope of the claims in the present invention and equivalent technologies thereof, the present invention also is intended to comprise these changes and modification interior.
Claims (13)
1. an Ethernet foundation multipoint service implementation method, is characterized in that, comprising:
The first provider edge equipment PE sends two PE of the routing update message reached of the node type of carrying the first connected customer edge devices CE to opposite end; Described node type comprises leaf node and root node;
When the 2nd PE receives described routing update message, according to the node type of carrying in described routing update message, judge that a described CE is leaf node or root node; And travel through each the 2nd CE self connected, for each the 2nd CE, if when a described CE and the 2nd CE are leaf node, between self and a PE, do not set up the pseudo-circuit between a CE and the 2nd CE; Otherwise attempt setting up the pseudo-circuit between a CE and the 2nd CE between self and a PE.
2. the method for claim 1, is characterized in that, the node type of in two layers of extended community attribute of described routing update message, carrying a described CE.
3. the method for claim 1, is characterized in that, described transmission is carried the routing update message reached of node type of a connected CE to before the PE of opposite end, also comprises:
For a described CE configuration node attribute, the nodal community of configuration comprises node type, also comprises customer edge devices ID, customer edge devices ID block offset, customer edge devices ID block size and from the label radix of the tag set of tag control module application.
4. the method for claim 1, is characterized in that, in described routing update message, also is included as the Network Layer Reachable Information of a CE configuration;
When described the 2nd PE attempts setting up pseudo-circuit, also comprise: the 2nd PE calculates label according to receiving the Network Layer Reachable Information carried in routing update message, and calculates into label according to the Network Layer Reachable Information from as the 2nd CE configuration.
5. described method as arbitrary as claim 1-4, is characterized in that, also comprises:
When a PE or the 2nd PE generation nodal community configuration variation, the routing update message that transmission can reach is to the 2nd PE or a PE; Or
The configuration that the CE that connects occurs as a PE or the 2nd PE delete or other while causing the event of pseudo-line disconnections of connected CE, send and carry the routing update message of described the connected unreachable information of CE to the 2nd PE or a PE.
6. an Ethernet foundation multipoint service implement device, is characterized in that, comprising:
Receiver module, for receiving the routing update message reached of the node type of carrying the first connected customer edge devices CE that the first provider edge equipment PE sends; Described node type comprises leaf node and root node;
Judge module, when receiving the routing update message that a PE sends, according to the node type of carrying in the routing update message received, judge that a described CE is leaf node or root node;
Set up module, for traveling through each the 2nd CE self connected, for each the 2nd CE, if when a described CE and the 2nd CE are leaf node, between self and a PE, do not set up the pseudo-circuit between a CE and the 2nd CE; Otherwise attempt setting up the pseudo-circuit between a CE and the 2nd CE between self and a PE.
7. device as claimed in claim 6, is characterized in that, also comprises:
Sending module, carry the routing update message reached of node type of the 2nd CE that the 2nd PE under described device connects to a PE of opposite end for transmission.
8. device as claimed in claim 7, is characterized in that, described sending module sends to a PE of opposite end specifically for the node type of carrying described the 2nd CE in two layers of extended community attribute of described routing update message.
9. device as claimed in claim 7, is characterized in that, described sending module, also for:
When the nodal community configuration variation occurs described the 2nd PE, the routing update message that transmission can reach is to a PE; Or
The configuration that the CE connect occurs as described the 2nd PE delete or other while causing the event of pseudo-line disconnections of connected CE, send and carry the routing update message of described the connected unreachable information of CE to a described PE.
10. device as claimed in claim 6, is characterized in that, also comprises: the tag computation module, for:
Described when setting up module and attempting setting up pseudo-circuit, be that the Network Layer Reachable Information of a CE configuration calculates label according to receiving what carry in routing update message, and calculate into label according to the Network Layer Reachable Information from as the 2nd CE configuration.
11. described device as arbitrary as claim 6-10, is characterized in that, also comprises:
The tag control module, can be for the label of application for management;
Configuration module, the 2nd CE configuration node attribute that is used to the 2nd affiliated PE of described device to connect; The nodal community of configuration comprises node type, also comprises customer edge devices ID, customer edge devices ID block offset, customer edge devices ID block size and from the label radix of the tag set of tag control module application.
12. a provider edge equipment, is characterized in that, comprising: described Ethernet foundation multipoint service implement device as arbitrary as claim 6-11.
13. an Ethernet foundation multipoint service is realized system, it is characterized in that, comprising: the customer edge devices that the customer edge devices that node type is leaf node, some node types are root node and at least two provider edge equipments as claimed in claim 12;
The customer edge devices that described node type is leaf node is connected with affiliated provider edge equipment by the leaf access link, and the customer edge devices that described node type is root node is connected with affiliated provider edge equipment by the root access link.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011101202702A CN102238057B (en) | 2011-05-10 | 2011-05-10 | Ethernet-tree realization method, system, device and network equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2011101202702A CN102238057B (en) | 2011-05-10 | 2011-05-10 | Ethernet-tree realization method, system, device and network equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102238057A CN102238057A (en) | 2011-11-09 |
| CN102238057B true CN102238057B (en) | 2013-07-24 |
Family
ID=44888300
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2011101202702A Expired - Fee Related CN102238057B (en) | 2011-05-10 | 2011-05-10 | Ethernet-tree realization method, system, device and network equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102238057B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102571521A (en) * | 2011-12-30 | 2012-07-11 | 中兴通讯股份有限公司 | Method and device capable of realizing forwarding of VPLS |
| WO2013123676A1 (en) * | 2012-02-24 | 2013-08-29 | 华为技术有限公司 | Method and device for determining establishment of multi-protocol label switching traffic engineering tunnel |
| CN102594647B (en) * | 2012-03-15 | 2014-08-27 | 福建星网锐捷网络有限公司 | Method, system, device and network device for realizing E-TREE service |
| CN102739519B (en) * | 2012-05-30 | 2015-01-21 | 福建星网锐捷网络有限公司 | Rooted multipoint service implementation method, device and system, and provider edge equipment |
| CN102710428B (en) * | 2012-06-04 | 2016-05-25 | 福建星网锐捷网络有限公司 | Ethernet foundation multipoint service implementation method, system, device and the network equipment |
| CN102780631B (en) * | 2012-08-06 | 2015-04-22 | 福建星网锐捷网络有限公司 | Pseudo-wire (PW) establishing method and device and network device |
| CN104253736B (en) | 2013-06-29 | 2017-11-24 | 华为技术有限公司 | Notice the method and PE equipment of the information of PE equipment |
| CN106411732B (en) * | 2016-09-07 | 2020-11-20 | 新华三技术有限公司 | Message forwarding method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101505227A (en) * | 2009-03-11 | 2009-08-12 | 华为技术有限公司 | Method, device and system for implementing point to multi-point pseudowire |
| US20100074098A1 (en) * | 2007-04-03 | 2010-03-25 | Huawei Technologies Co., Ltd. | Method and device for protecting ethernet tree services |
| CN101977123A (en) * | 2010-10-28 | 2011-02-16 | 北京星网锐捷网络技术有限公司 | Method, system and device for generating virtual private local area network site ID |
| CN102045232A (en) * | 2009-10-19 | 2011-05-04 | 中兴通讯股份有限公司 | System and method for acquiring link information in bilayer VPN (Virtual Private Network) |
-
2011
- 2011-05-10 CN CN2011101202702A patent/CN102238057B/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100074098A1 (en) * | 2007-04-03 | 2010-03-25 | Huawei Technologies Co., Ltd. | Method and device for protecting ethernet tree services |
| CN101505227A (en) * | 2009-03-11 | 2009-08-12 | 华为技术有限公司 | Method, device and system for implementing point to multi-point pseudowire |
| CN102045232A (en) * | 2009-10-19 | 2011-05-04 | 中兴通讯股份有限公司 | System and method for acquiring link information in bilayer VPN (Virtual Private Network) |
| CN101977123A (en) * | 2010-10-28 | 2011-02-16 | 北京星网锐捷网络技术有限公司 | Method, system and device for generating virtual private local area network site ID |
Non-Patent Citations (3)
| Title |
|---|
| K.Kompella.Layer 2 VPNs Over Tunnels.《Layer 2 VPNs Over Tunnels,draft-kompella-l2vpn-l2vpn-00》.2004,全文. * |
| K.Kompella等.Virtual Private LAN Service(VPLS) Using BGP for Atuo-Discovery and Signaling.《RFC4761》.2007,全文. * |
| Raymond Key等.Extension to VPLS for E-Tree.《Extension to VPLS for E-Tree,draft-key-l2vpn-vpls-etree-02》.2010,全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102238057A (en) | 2011-11-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102238057B (en) | Ethernet-tree realization method, system, device and network equipment | |
| CN102035729B (en) | Multicast data forwarding method | |
| CN105379197B (en) | It establishes the method in tunnel, distribute method, equipment and the network system of label | |
| CN101401083B (en) | Technique for preventing routing loops by disseminating BGP attribute information in an ospf-configured network | |
| CN101616014B (en) | Method for realizing cross-virtual private local area network multicast | |
| CN104253759A (en) | Method, device and system for forwarding messages | |
| CN102098202B (en) | Virtual private topology control method, device and system | |
| WO2013026384A1 (en) | Service data transmission method, network node and system | |
| CN112422398B (en) | Message transmission method and communication device | |
| CN101160862B (en) | Method and system for realizing the consistency of the virtual circuit status | |
| CN102045250B (en) | Forwarding method for multicast message in VPLS, and service provider edge equipment | |
| CN107888493B (en) | Method and device for establishing label switching path | |
| CN103209125B (en) | A kind of transmission method of label information and equipment | |
| CN103795630A (en) | Message transmitting method and device of label switching network | |
| CN102710495B (en) | Method and device for establishing routing information of user host computer in monitoring network | |
| CN102045239B (en) | Implementation method and device of point-to-multipoint pseudowire protective network | |
| CN102724126A (en) | Method, device and equipment for forwarding Ethernet tree (E-tree) service message | |
| CN102238028B (en) | Ethernet-tree realization method, system, device and network equipment | |
| CN102238040B (en) | Method for monitoring CE (Customer Edge router) and routing device | |
| CN102739519B (en) | Rooted multipoint service implementation method, device and system, and provider edge equipment | |
| CN102801618B (en) | A kind of method and device determining three layer data paths in ethernet ring network | |
| CN113328943B (en) | Route matching method, information sending method and device | |
| CN102055719A (en) | Method and device for protecting point-to-multipoint pseudo-wire | |
| CN105515999B (en) | Quick convergence method and device for end system address distribution information protocol | |
| CN103095507B (en) | Based on message transmitting method and the edge device of Ethernet virtualization internet network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 350002 19 Building, Citrus Industrial Park, 618 Jinshan Road, Cangshan District, Fuzhou, Fujian. Patentee after: RUIJIE NETWORKS Co.,Ltd. Address before: 350002 19 Building, Citrus Industrial Park, 618 Jinshan Road, Cangshan District, Fuzhou, Fujian. Patentee before: Fujian Star Network Ruijie Networks Co.,Ltd. |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130724 Termination date: 20210510 |