CN102377637A - Multi-segment pseudo wire shared bandwidth method, system thereof and provider edge node - Google Patents
Multi-segment pseudo wire shared bandwidth method, system thereof and provider edge node Download PDFInfo
- Publication number
- CN102377637A CN102377637A CN2010102489156A CN201010248915A CN102377637A CN 102377637 A CN102377637 A CN 102377637A CN 2010102489156 A CN2010102489156 A CN 2010102489156A CN 201010248915 A CN201010248915 A CN 201010248915A CN 102377637 A CN102377637 A CN 102377637A
- Authority
- CN
- China
- Prior art keywords
- label mapping
- node
- information
- mapping message
- unit
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000013507 mapping Methods 0.000 claims abstract description 198
- 238000004088 simulation Methods 0.000 claims abstract description 8
- 230000008569 process Effects 0.000 claims description 7
- 238000012217 deletion Methods 0.000 claims 1
- 230000037430 deletion Effects 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 19
- 101100366322 Arabidopsis thaliana ADC1 gene Proteins 0.000 description 17
- 101150032645 SPE1 gene Proteins 0.000 description 17
- 101100478264 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) SPE4 gene Proteins 0.000 description 13
- 101100366397 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) SPE3 gene Proteins 0.000 description 10
- 101100028962 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) PDR1 gene Proteins 0.000 description 9
- 230000007246 mechanism Effects 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 230000003068 static effect Effects 0.000 description 5
- 101000984710 Homo sapiens Lymphocyte-specific protein 1 Proteins 0.000 description 4
- 102100027105 Lymphocyte-specific protein 1 Human genes 0.000 description 4
- 238000004891 communication Methods 0.000 description 4
- 101100478118 Caenorhabditis elegans spe-4 gene Proteins 0.000 description 2
- 101100442582 Neurospora crassa (strain ATCC 24698 / 74-OR23-1A / CBS 708.71 / DSM 1257 / FGSC 987) spe-1 gene Proteins 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 101100150045 Neurospora crassa (strain ATCC 24698 / 74-OR23-1A / CBS 708.71 / DSM 1257 / FGSC 987) spe-3 gene Proteins 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 239000000470 constituent Substances 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000007727 signaling mechanism Effects 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
- H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/68—Pseudowire emulation, e.g. IETF WG PWE3
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a multi-segment pseudo wire shared bandwidth method, and sets a same bandwidth sharing identifier for pseudo wires sharing a same tunnel. The method comprises the following steps: a PE (provider edge) node sends a label mapping message for the pseudo wires capable of sharing the same tunnel, and the label mapping message carries the bandwidth shared identifier. The invention simultaneously discloses the PE node which is applied to an edge-to-edge pseudo wire simulation system which sets the same bandwidth shared identifier for the pseudo wires sharing the same tunnel. The PE node comprises a sending unit used for sending the label mapping message for the pseudo wires sharing the same tunnel and other PE nodes, wherein the label mapping message carries the bandwidth sharing identifier. The invention discloses a multi-segment pseudo wire shared bandwidth system which comprises PE nodes which are connected through the pseudo wires, and the PE nodes are the above mentioned PE nodes. A technical scheme in the invention has the characteristics of easy realization, low cost and strong versatility.
Description
Technical Field
The invention relates to a Multi-Segment Pseudo Wire (MS-PW) technology, in particular to a method and a system for sharing bandwidth of Multi-Segment Pseudo wires and Provider Edge (PE) nodes.
Background
With the development of the IP data network, the IP network itself has very strong expandability, upgradability, compatibility and intercommunication capabilities, while the flexibility of the traditional communication network for upgrading, expanding and intercommunication is relatively poor, limited by the transmission mode and the service type, and the newly-built network has poor sharing performance and is not suitable for intercommunication management. Therefore, in the process of upgrading and expanding the application of the traditional communication network, repeated networks are respectively established, the purposes of upgrading the network and expanding the application are achieved by fully utilizing the existing or public resources, and how to achieve the purpose is a problem which is considered.
The Pseudo Wire (PW) technology is a solution proposed for future converged communication networks, and is a technology for providing a simulation of traditional layer 1 and layer 2 network services on the basis of a packet switching network. The pseudo wire technology is almost suitable for all networks, and can enable the Multi-Protocol label switching (MPLS) technology to realize the real convergence of the access network and the metropolitan area network. The pseudowire is a point-to-point connection between PE nodes, a pseudowire establishing mechanism is defined in RFC4447 of Internet Engineering Task Force (IETF), a Label Distribution Protocol (LDP) is adopted as a signaling mechanism to establish the pseudowire, and Label switching and parameter negotiation of the pseudowire are carried out. Among them, Pseudo Wire Emulation Edge-to-Edge (PWE 3) is just one of the methods proposed for solving the problem of combining the conventional communication network with the existing packet network.
Pseudowires defined by IETF PWE3 include Single Segment pseudowires (SS-PW) and Multi-Segment pseudowires (MS-PW).
Fig. 1 is a schematic structural diagram of an existing SS-PW, and as shown in fig. 1, the SS-PW refers to directly establishing a pseudowire between two PEs without passing through other PE nodes in the middle.
MS-PW is formed by additionally arranging exchange operator Edge equipment (S-PE, Switch Provider Edge) between two terminal operator Edge equipment (T-PE, Terminating Provider Edge), is different from SS-PW, is connected in a multi-section way instead of being directly established between the two PEs, and is switched together through the S-PE (the number of the S-PE is not limited in the standard); fig. 2 is a schematic structural diagram of establishing an MS-PW using dynamic routing, and as shown in fig. 2, at T-PE1 and T-PE2, connections are respectively established with an S-PE, and the S-PE connects two segments of PW together to form an MS-PW.
Make-Before-break (mbb) refers to a mechanism that changes the transmission path of a data packet on the premise of not losing data as much as possible and not occupying extra bandwidth; fig. 3 is a schematic structural diagram of implementing that part of two multi-segment pseudowires share the same Label Switched Path (LSP) by using an MBB mechanism in an MS-PW static configuration or a predetermined routing scenario, and as shown in fig. 3, assuming that a multi-segment pseudowire MS-PW1 already exists currently, a multi-segment pseudowire MS-PW2 is newly established for the MBB requirement, so that part of pseudowires between a primary pseudowire MS-PW1 and a standby pseudowire MS-PW2 can share the same lower layer tunnel. For example, one PW1 segment 1 of the MS-PW1 needs to reserve a bandwidth of 100M, and an LSP1 of the lower layer is also 100M, a MBB mechanism is adopted, a PW2 segment 1 of a newly established MS-PW2 can share the bandwidth of an original path LSP1, after an MS-PW2 is successfully established, the flow is switched to an MS-PW2, and then the MS-PW1 is removed.
As shown in fig. 3, in the MS-PW static configuration scenario, it can be implemented that a part of pseudo-wire segments of the standby MS-PW and a part of pseudo-wire segments of the primary MS-PW share the same LSP through static configuration at the PE node; the configuration information on T-PE1, S-PE1, and S-PE3 is schematically shown in FIG. 3 for illustrative purposes.
However, in a scenario where the MS-PW displays routing or dynamic routing, the existing mechanism cannot ensure that part of pseudo-segments for the standby MS-PW and the active MS-PW of the MBB share the same LSP.
Disclosure of Invention
In view of the above, the present invention provides a method and a system for sharing bandwidth among multiple pseudowires, and a provider edge node, where a PE can quickly identify pseudowires sharing the same LSP and bind the pseudowires to the same LSP.
In order to achieve the purpose, the technical scheme of the invention is realized as follows:
a method for sharing bandwidth of multi-segment pseudo wires sets the same bandwidth sharing identifier for pseudo wires which can share the same tunnel; the method comprises the following steps:
establishing a pseudo wire sharing bandwidth between PE nodes through label mapping information; wherein the label mapping message carries the bandwidth sharing identifier.
Preferably, the method further comprises:
in the label mapping messages received by the PE node, determining that more than two label mapping messages have the same bandwidth sharing identifier, and binding the pseudo wires corresponding to the more than two label mapping messages to the same tunnel when the origin end PE and the termination end PE of the pseudo wires corresponding to the more than two label mapping messages are respectively the same.
Preferably, the method further comprises:
and determining that the label mapping message received by the PE node is different from the origin end PE or the termination end PE of the pseudo wire corresponding to the rest label mapping messages or different from the bandwidth sharing identifiers of the rest label mapping messages, allocating a tunnel for bearing the pseudo wire corresponding to the received label mapping message, or establishing a tunnel for bearing the pseudo wire corresponding to the received label mapping message.
Preferably, the label mapping message includes AGI information, SAII information, TAII information, pseudowire bandwidth information, and pseudowire label; or, the label mapping message includes AGI information, SAII information, TAII information, pseudowire bandwidth information, routing information list information, and pseudowire label.
Preferably, the method further comprises:
when the PE node determines that the received label mapping message does not contain routing information list information, the TAII information in the label mapping message is matched with the self identification, and when the TAII information is not matched, the next hop address is searched in a self pseudo wire routing table by taking the TAII as an index, and the label mapping message is continuously sent; establishing a pseudo wire reversely when matching;
or when determining that the label mapping message contains routing information list information, the PE node matches a first specific identifier AII in the routing information list with the self identifier, and when the label mapping message does not match the self identifier, the PE node searches a next hop address in a self pseudo wire routing table by taking the first AII as an index, and continuously sends the label mapping message; and when the pseudo wire address is matched with the label mapping information, searching the next hop address in the pseudo wire routing table of the pseudo wire by using the second AII index in the routing information list, and continuously sending the label mapping information.
Preferably, the method further comprises:
and when the PE node takes the TAII or the AII as an index to find out no matched routing entry in the pseudowire routing table of the PE node, discarding the label mapping message.
Preferably, when the first AII in the routing information list matches the identity of the PE node; the method further comprises the following steps:
and when the routing information list information does not contain a second AII, searching a next hop address in a pseudo wire routing table of the PE node by taking the TAII as an index, and continuously sending a label mapping message.
Preferably, the method further comprises:
and when the first AII in the routing information list is matched with the identifier of the PE node, deleting the information matched with the first AII from the routing information list information in the label mapping message sent by the next hop address.
Preferably, the PE node is an S-PE node or a T-PE node; the pseudowire is a multi-segment pseudowire.
A PE node is applied to an edge-to-edge pseudo wire simulation system, and the edge-to-edge pseudo wire simulation system sets the same bandwidth sharing identifier for pseudo wires which can share the same tunnel; the PE node comprises:
the sending unit is used for sending label mapping information to other PE nodes when establishing the pseudo wires capable of sharing the bandwidth; wherein the label mapping message carries the bandwidth sharing identifier.
Preferably, the PE node further comprises a receiving unit, a determining unit, and a binding unit; wherein,
a receiving unit for receiving a tag mapping message;
a determining unit, configured to determine that more than two label mapping messages have the same bandwidth sharing identifier, and that an origin PE and a terminating PE of a pseudo wire corresponding to the more than two label mapping messages are also the same, respectively, and trigger the binding unit;
and the binding unit is used for binding the pseudo wires corresponding to the more than two label mapping messages to the same tunnel.
Preferably, the PE node further comprises an allocation unit and/or a tunnel establishment unit;
the determining unit determines that the label mapping message received by the receiving unit is different from the origin end PE or the termination end PE of the pseudo wire corresponding to the rest label mapping messages or different from the bandwidth sharing identifiers of the rest label mapping messages, and triggers the allocating unit or the tunnel establishing unit;
the distribution unit is used for distributing a tunnel for bearing a pseudo wire corresponding to the received label mapping message;
and the tunnel establishing unit is used for newly establishing a tunnel to bear the pseudo wire corresponding to the received label mapping message.
Preferably, the label mapping message includes access group identity AGI information, source specific identifier SAII information, target specific identifier TAII information, pseudowire bandwidth information, and pseudowire label; or, the label mapping message includes AGI information, SAII information, TAII information, pseudowire bandwidth information, routing information list information, and pseudowire label.
Preferably, the PE node further comprises a matching unit; wherein,
a matching unit, configured to match a TAII information in the label mapping message with the PE identifier when the determining unit further determines that the label mapping message does not include routing information list information, and look up a next hop address in a pseudowire routing table of the self using the TAII as an index when the label mapping message is not matched with the PE identifier, and trigger the sending unit to continue sending the label mapping message to the next hop; triggering the sending unit to reversely establish the pseudo wire when matching;
when the determining unit further determines that the label mapping message contains routing information list information, the matching unit matches the first AII in the routing information list with the PE identifier, and when the first AII is not matched with the PE identifier, the matching unit searches a next hop address in the pseudo wire routing table by taking the first AII as an index, and triggers the sending unit to continue sending the label mapping message; when matching, searching the next hop address in the pseudo wire routing table of the PE by using the second AII index in the routing information list, and triggering the sending unit to continue sending the label mapping message;
preferably, the PE node further includes a discarding unit configured to discard the label mapping message when the matching unit finds no matching routing entry in the pseudowire routing table of the PE node using the TAII/AII as an index.
Preferably, in the process of matching the first AII in the routing information list with the identifier of the PE node, when the routing information list information does not include the second AII, the matching unit searches for the next hop address in the pseudowire routing table of the PE node by using the TAII as an index, and triggers the sending unit to continue sending the label mapping message.
Preferably, the PE node further includes a deleting unit, configured to delete, when the matching unit determines that the first AII in the routing information list matches the identifier of the PE node, information matching the first AII in the routing information list information in the label mapping message sent by the sending unit according to the next hop address.
Preferably, the pseudowire is a multi-segment pseudowire.
A system for multi-segment pseudowires to share bandwidth comprising the PE nodes connected by pseudowires; establishing a pseudo wire sharing bandwidth between the PE nodes through a label mapping message; wherein the label mapping message carries the bandwidth sharing identifier.
In the invention, the same bandwidth sharing identifier is set for the pseudo wires sharing the same tunnel, and when the PE node sends the label mapping message, if the currently utilized pseudo wires are the pseudo wires sharing the same tunnel, the bandwidth sharing identifier is inserted into the label mapping message. And the PE node receiving the label mapping message determines a plurality of pseudo wires sharing the same tunnel according to the bandwidth sharing identifier in the label mapping message and binds the pseudo wires to the same tunnel. The technical scheme of the invention can switch to the standby multi-segment pseudo wires in time when the main multi-segment pseudo wires in the main multi-segment pseudo wires and the standby multi-segment pseudo wires fail, thereby greatly facilitating the data switching among the PE nodes. The technical scheme of the invention is simple to realize, has less change to the existing protocol, has stronger universality and lower realization cost.
Drawings
FIG. 1 is a schematic diagram of a conventional SS-PW structure;
FIG. 2 is a schematic diagram of a structure for establishing MS-PW by using dynamic routing;
FIG. 3 is a schematic structural diagram of an MS-PW static configuration or a predetermined routing scenario in which an MBB mechanism is used to implement that part of two multi-segment pseudo wires share the same LSP;
FIG. 4 is a schematic diagram showing a structure in which part of pseudowire segments of two multi-segment pseudowires share the same LSP in a routing scenario;
FIG. 5 is a flowchart of a first embodiment of a method for sharing bandwidth among multi-segment pseudowires according to the scenario shown in FIG. 4;
FIG. 6 is a schematic structural diagram of two multi-segment pseudowires sharing the same LSP with partial pseudowire segments in a dynamic routing scenario;
FIG. 7 is a flowchart of a second embodiment of a method for sharing bandwidth among multi-segment pseudowires according to the scenario shown in FIG. 6;
FIG. 8 is a schematic diagram of a first component structure of a PE node according to the present invention;
FIG. 9 is a schematic diagram of a second exemplary embodiment of a PE node;
FIG. 10 is a schematic diagram of a third exemplary embodiment of a PE node;
FIG. 11 is a diagram illustrating a fourth exemplary embodiment of a PE node.
Detailed Description
The basic idea of the invention is as follows: by setting the same bandwidth sharing identifier for pseudowires that can share the same tunnel, when a PE node sends a label mapping message, if a new pseudowire needs to be established for MBB, the bandwidth sharing identifier is inserted in the label mapping message. And the PE node receiving the label mapping message determines a plurality of pseudo wires sharing the same tunnel according to the bandwidth sharing identifier in the label mapping message and binds the pseudo wires to the same tunnel.
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail below with reference to the accompanying drawings by way of examples.
The invention carries the bandwidth sharing identifier when sending the label mapping message of the pseudo wire for the pseudo wire needing to share the bandwidth with the pseudo wire with the same bandwidth sharing identifier. And when the SPE/TPE node finds that the plurality of label mapping messages meet the following conditions in the received label mapping messages, the SPE/TPE node binds the same tunnel for the plurality of pseudo wires corresponding to the plurality of label mapping messages respectively and shares the bandwidth of the tunnel. The conditions are as follows: having the same originating PE and terminating PE, while having the same bandwidth sharing identifier.
The following describes in detail the implementation of the embodiments of the present invention with reference to examples.
Example one
In this embodiment, an existing pseudowire is assumed to be called a primary pseudowire, now, for the MBB, a multi-segment pseudowire needs to be newly established in a display routing manner, and when a primary MS-PW fails, the flow is switched to the newly established MS-PW, which is called a standby pseudowire. Fig. 4 is a schematic structural diagram showing that part of pseudowire segments in two multi-segment pseudowires share the same LSP in a routing scenario, and as shown in fig. 4, PW segments of a main/standby MS-PW between TPE1 and SPE1 may share the same LSP, where MS-PW1 is the main MS-PW and MS-PW1 is the standby MS-PW; similarly, the PW segments of the main/standby MS-PW between SPE3 and TPE2 may share the same LSP. An Access Group Identity (AGI), a Source access specific Identifier (SAII), and a Target access specific Identifier (TAII) are configured at TPE1 and TPE2, respectively. The content carried in the label mapping message sent between PEs comprises AGI, SAII and TAII; when the PWs share the same LSP, the label mapping message also carries the bandwidth identifier information. The label mapping message also generally carries information for displaying a routing list. Fig. 4 illustrates part of information carried in a label mapping message sent between PEs. The essence of the technical solution of the present invention will be explained in detail below based on the structural diagram shown in fig. 4.
Fig. 5 is a flowchart of a first embodiment of a method for sharing bandwidth by a multi-segment pseudowire according to the scenario shown in fig. 4, where as shown in fig. 5, the method for sharing bandwidth by a multi-segment pseudowire of this example includes the following steps:
and step 501, configuring MS-PW related information by the TPE.
As shown in fig. 4, AGI, SAII, and TAII may be configured at TPE1 and TPE2, respectively.
In this example, the content carried by the label mapping message is AGI, sai, TAII, display route list information, and shared bandwidth identifier. When the PE device receiving the label mapping message determines that the label mapping message carries information of the display route list, first further determines whether the first access specific Identifier (AII) information in the display route list matches with the local AII, if not, finds the next hop sending label mapping message by using the first AII in the display route list as an index to search the PW route table, if so, finds the next hop sending label mapping message by using the second AII in the display route list as an index to search the route table, and when no other AII information (or no second AII) exists in the display route list, searches the PW route table by using the TAII as an index, and when the sent label mapping message needs to delete the AII information matching with the local AII in the display route list, that is, when sending the next hop label mapping message, the display route list is empty or no longer contained.
If the label mapping message does not contain the information of the display routing list, the PE equipment receiving the label mapping message determines whether the TAII is matched with the local AII information, and if not, the PE equipment checks the PW routing table by taking the TAII as an index to find the next hop and continues to send the label mapping message. If the matching is confirmed, the TPE equipment is indicated, and the MS-PW is reversely established.
As shown in fig. 4, the active TPE1 looks up its local PW routing table with the first AII information in the routing list, AII3, as an index, and looks up the next hop to reach the destination AII3 as SPE1, and then TPE1 sends a label mapping message to SPE 1.
As shown in fig. 4, SPE1 checks that SAII, TAII and the bandwidth sharing identifier carried in the label mapping message are identical to those carried in the label mapping message for establishing the active MS-PW1 segment 1, then step 505 is executed.
After receiving the label mapping message, the TPE2 checks that the bandwidth sharing identifier carried in the label mapping message is the same as the bandwidth sharing identifier carried in the label mapping message for establishing the active MS-PW1 segment 4, and then executes step 505.
In step 504, the PE selects an appropriate LSP to carry a PW segment of MS-PW 2. If no suitable LSP is currently used for carrying the PW section of the MS-PW2, an LSP is newly established for carrying the PW section of the MS-PW 2.
As shown in fig. 4, after receiving the label mapping message sent by SPE1, SPE4 selects an appropriate LSP to carry the MS-PW2 segment according to the pseudowire bandwidth requirement in the label mapping message.
After receiving the label mapping message sent by SPE4, SPE3 selects a suitable LSP to carry the MS-PW2 segment according to the pseudowire bandwidth requirement in the label mapping message. If no suitable LSP is currently used for carrying the PW section of the MS-PW2, an LSP is newly established for carrying the PW section of the MS-PW 2.
In step 505, the PE selects the LSP carrying the active MS-PW segment to carry the PW segment of the corresponding MS-PW 2.
As shown in fig. 4, SPE1 selects LSP1 carrying MS-PW1 segment 1 to carry MS-PW2 segment 1.
TPE2 selects an LSP carrying MS-PW1 segment to carry MS-PW2 segment.
In step 506, the PE checks whether there is a display route list in the label mapping message, if so, performs step 508, otherwise, performs step 513.
As shown in fig. 4, SPE1 checks that there is display route list information in the label mapping message, then performs step 508.
In step 507, it is checked whether the first AII information in the routing list is matched with the local AII information, if yes, step 509 is executed, otherwise, step 508 is executed.
As shown in fig. 4, SPE1 checks that the AII value in the display routing list is AII2 and does not match the local AII information, then step 508 is performed.
As shown in fig. 4, SPE4 detects that the AII value in the display routing list is AII2 that matches the local AII information, then step 509 is performed.
In step 508, the PE looks up the local PW routing table with the first AII information in the display routing list as an index, finds the next hop of the pseudowire to the destination, and then performs step 511.
As shown in fig. 4, SPE1 looks up the PW routing table using AII2 as an index, finds the next hop to AII2 as SPE4, and then performs step 511.
In step 509, the PE checks to see if there are any other AII messages in the routing list, if so, performs step 510, otherwise, performs step 512.
As shown in FIG. 4, SPE4 checks to show that there is no other AII information in the routing list, so step 512 is performed.
In step 510, the PE searches for the local PW route using the next AII information in the display route list as an index, finds the next hop of the pseudowire to reach the destination, and executes step 511.
As shown in fig. 4, SPE1 sends a tag mapping message carrying the bandwidth sharing identifier allocated by the T-PE to SPE 4. After the SPE4 deletes the information in the display route list that matches the AII2, it continues to send the SPE3 a label mapping message carrying the bandwidth sharing identifier. SPE3 sends a label mapping message carrying a bandwidth sharing identifier to TPE 2.
In step 512, the PE checks whether the TAII information in the label mapping message matches the local AII information, if so, performs step 513, otherwise performs step 514.
As shown in fig. 4, SPE4 checks the TAII information in the label mapping message: AII3 since with local AII information: the AII2 does not match, so step 514 is performed.
As shown in fig. 4, TPE2 establishes the MS-PW in reverse. The procedure for establishing the MS-PW in the reverse direction is similar to the procedure for establishing the MS-PW in the forward direction, and will not be described in too much.
In step 514, the PE searches for the local PW route using the TAII as an index, searches for the next hop of the pseudowire to reach the destination, and executes step 511.
As shown in fig. 4, SPE4 looks up the PW routing table with AII3 as an index, and finds that the next hop is the SPE3 node.
Example two
In this embodiment, an existing pseudowire is assumed to be called a primary pseudowire, now, for the MBB, a multi-segment pseudowire needs to be newly established in a dynamic routing manner, and when a failure occurs in the primary MS-PW, the flow is switched to the newly established MS-PW, which is called a standby pseudowire. Fig. 6 is a schematic structural diagram of a dynamic routing scenario in which partial pseudowire segments of two multi-segment pseudowires share the same LSP, and as shown in fig. 6, PW segments from TPE1 to SPE1 may share the same LSP, and PW segments between the same SPE3 and the same TPE2 may also share the same LSP. The application scenario shown in fig. 6 is substantially the same as the application scenario shown in fig. 4, except for the routing scheme on which they are based. As can be understood with reference to the description relating to fig. 4.
Fig. 7 is a flowchart of a second embodiment of a method for sharing bandwidth by a multi-segment pseudowire according to the scenario shown in fig. 6, where as shown in fig. 7, the method for sharing bandwidth by a multi-segment pseudowire of this example includes the following steps:
and step 701, configuring MS-PW related information by the TPE.
As shown in fig. 6, AGI, SAII, and TAII are provided at TPE1 and TPE2, respectively.
In step 702, the active TPE node searches the local PW routing table to send a label mapping message carrying the locally allocated bandwidth sharing identifier and the pseudowire bandwidth information to the next hop.
Here, the selection of the active TPE can be realized through static configuration, and also can be realized through comparing router IDs.
As shown in fig. 6, the active TPE1 looks up its local PW routing table with TAII information, AII3 as an index, and looks up the next hop to reach the destination AII3 as SPE1, then TPE1 sends a label mapping message to SPE 1.
In step 703, after receiving the mapping message, the next-hop PE determines whether all the SAII, TAII, and bandwidth sharing identifiers in the mapping message initiated by establishing the active/standby pseudo wires are the same, if yes, step 705 is executed, otherwise, step 704 is executed.
As shown in fig. 6, SPE1 checks that SAII, TAII and the bandwidth sharing identifier carried in the label mapping message are identical to those carried in the label mapping message for establishing the active MS-PW1 segment, then step 705 is performed.
After receiving the label mapping message, TPE2 checks that the SAII, TAII and bandwidth sharing identifier carried in the label mapping message are completely the same as the bandwidth sharing identifier carried in the label mapping message for establishing the active MS-PW1 segment, then step 705 is executed.
In step 704, the PE selects an appropriate LSP to carry the PW segment of MS-PW 2. If no suitable LSP is currently used for carrying the PW section of the MS-PW2, an LSP is newly established for carrying the PW section of the MS-PW 2.
As shown in fig. 6, after receiving the label mapping message sent by SPE1, SPE4 selects an appropriate LSP to carry the MS-PW2 segment according to the pseudowire bandwidth requirement in the label mapping message.
After receiving the label mapping message sent by SPE4, SPE3 selects a suitable LSP to carry the MS-PW2 segment according to the pseudowire bandwidth requirement in the label mapping message. If no suitable LSP is currently used for carrying the PW section of the MS-PW2, an LSP is newly established for carrying the PW section of the MS-PW 2.
As shown in fig. 6, SPE1 selects LSP1 carrying MS-PW1 segment to carry MS-PW2 segment 1.
TPE2 selects an LSP carrying MS-PW1 segment to carry MS-PW2 segment.
In step 706, the PE checks whether the TAII in the label mapping message matches the local AII, if so, performs step 707, otherwise, performs step 708.
As shown in fig. 6, SPE1 checks that the TAII in the label mapping message does not match the local AII information, then step 708 is performed. TPE2 checks that the TAII in the label mapping message matches the local AII information, then step 707 is performed.
As shown in fig. 6, TPE2 establishes the MS-PW in reverse. The procedure for establishing the MS-PW in the reverse direction is similar to the procedure for establishing the MS-PW in the forward direction, and will not be described in too much.
In step 708, the PE searches for the local PW route using the TAII information as an index, finds the next hop of the pseudowire to reach the destination, and executes step 709.
As shown in fig. 6, SPE1 looks up the PW routing table with AII3 as an index, and finds the next hop for the standby MS-PW to be SPE 4.
SPE4 looks up the PW routing table with AII3 as an index, and finds the next hop to be SPE 3.
SPE3 looks up the PW routing table with AII3 as an index to find the next hop is TPE 2.
In step 709, the PE sends a label mapping message carrying the bandwidth sharing identifier and the pseudowire bandwidth to the next hop, and returns to step 703.
As shown in fig. 6, SPE1 sends a packet carrying bandwidth sharing identifier to next-hop SPE4 as: 1 and pseudowire bandwidth: 100M tag mapping message. Step 703 is performed.
SPE4 sends a packet carrying bandwidth sharing identifier to next-hop SPE3 as: 1 and pseudowire bandwidth: 100M tag mapping message. Step 703 is performed.
SPE3 sends a next hop TPE2 with a bandwidth sharing identifier of: 1 and pseudowire bandwidth: 100M tag mapping message. Step 703 is performed.
The PE node is applied to a pseudo wire simulation system from edge to edge, and the pseudo wire simulation system from edge to edge sets the same bandwidth sharing identifier for pseudo wires sharing the same tunnel; fig. 8 is a schematic diagram of a first structure of the PE node of the present invention, and as shown in fig. 8, the PE node of the present invention includes:
a sending unit 80, configured to send a label mapping message to other PE nodes for pseudowires sharing the same tunnel; wherein the label mapping message carries the bandwidth sharing identifier.
Fig. 9 is a schematic diagram of a second structure of the PE node of the present invention, and as shown in fig. 9, the PE node of the present invention may also be a structure including the following processing units:
a receiving unit 81 configured to receive a tag mapping message;
a determining unit 82, configured to determine that more than two label mapping messages have the same bandwidth sharing identifier, and that an origin PE and a terminating PE of a pseudo wire corresponding to the more than two label mapping messages are also the same, respectively, trigger a binding unit 83;
a binding unit 83, configured to bind the pseudowires corresponding to the more than two label mapping messages to the same tunnel.
In the invention, for a source T-PE node, a sending unit and a receiving unit are two independent processes, wherein only a sending unit 80 is used in the forward MS-PW establishing process, and only a receiving unit 81, a determining unit 82 and a binding unit 83 are used in the reverse MS-PW establishing process;
fig. 10 is a schematic diagram of a third component structure of the PE node of the present invention, as shown in fig. 9, the PE node of the present invention includes a receiving unit 81, a determining unit 82, a binding unit 83, and a sending unit 80;
in the present invention, for the S-PE node and the target T-PE node, the receiving unit 81 directly triggers the sending unit 80 to send the label mapping message.
On the basis of the structure shown in fig. 10, the PE node of the present invention further includes an allocation unit (not shown) and/or a tunnel establishment unit (not shown);
the determining unit 82 determines that the label mapping message received by the receiving unit 81 is different from the origin end PE or the termination end PE of the pseudo wire corresponding to the rest of the label mapping messages, or different from the bandwidth sharing identifier of the rest of the label mapping messages, and triggers the allocating unit or the tunnel establishing unit;
the distribution unit is used for distributing a tunnel for bearing a pseudo wire corresponding to the received label mapping message;
and the tunnel establishing unit is used for establishing a new tunnel to bear the pseudo wire corresponding to the received label mapping message when the distribution unit fails to distribute the tunnel.
In the present invention, when the determining unit 82 determines that the source end PE or the terminating end PE is different, or the bandwidth sharing identifier of the remaining label mapping message is different, the tunnel establishing unit may be directly triggered to establish the tunnel without first performing tunnel allocation by the allocating unit.
Fig. 11 is a schematic diagram of a fourth constituent structure of the PE node of the present invention, as shown in fig. 10, on the basis of the structure shown in fig. 9 or fig. 10 (this example shows that the structure shown in fig. 10 is taken as the basis), the PE node of the present invention further includes a matching unit 84; wherein,
a matching unit 84, configured to, when the determining unit 82 further determines that the label mapping message does not include the routing information list information, match the TAII information in the label mapping message with the PE identifier, and when the label mapping message is not matched, look up a next hop address in a pseudowire routing table of the self using the TAII as an index, and trigger the sending unit 80 to continue sending the label mapping message to the next hop; triggering the sending unit 80 to reversely establish the pseudo wire when matching;
when the determining unit 82 further determines that the label mapping message includes routing information list information, the matching unit 84 matches the first AII in the routing information list with the PE identifier, and when the first AII is not matched, looks up a next hop address in the pseudo wire routing table by using the first AII as an index, and triggers the sending unit 80 to continue sending the label mapping message; when matching, searching the next hop address in the pseudowire routing table of the PE by using the second AII index in the routing information list, and triggering the sending unit 80 to continue sending the label mapping message;
in the process of matching the first AII in the routing information list with the identifier of the PE node, when the routing information list information does not include the second AII, the matching unit 84 searches for the next hop address in the pseudowire routing table of the PE node by using the TAII as an index, and triggers the sending unit 80 to continue sending the label mapping message.
On the basis of the structure shown in fig. 10, the PE node of the present invention further includes a discarding unit (not shown) for discarding the label mapping message when the matching unit 84 does not find a matching routing entry in the pseudowire routing table of the PE node using the TAII/AII as an index.
On the basis of the structure shown in fig. 10, the PE node of the present invention further includes a deleting unit (not shown) configured to delete, when the matching unit 84 determines that the first AII in the routing information list matches the identifier of the PE node, information matching the first AII from the routing information list information in the label mapping message sent by the sending unit 80 according to the next hop address.
The label mapping message comprises AGI information, SAII information, TAII information, pseudo wire bandwidth information and pseudo wire label; or, the label mapping message includes AGI information, SAII information, TAII information, pseudowire bandwidth information, routing information list information, and pseudowire label.
The PE node of the invention is an S-PE node or a T-PE node. The pseudowire is a multi-segment pseudowire; the tunnel is an LSP.
Those skilled in the art should understand that the PE node of the present invention is designed to implement the aforementioned method for sharing bandwidth of multi-segment pseudowires, and the implementation functions of the aforementioned units can be understood by referring to the related description of the aforementioned method. The application scene of the PE node of the invention is the same as the prior PE node, but the realized function is different from the prior PE node.
The invention also discloses a system for sharing bandwidth by the multi-segment pseudo wires, which comprises the PE nodes connected by the pseudo wires; establishing a pseudo wire sharing bandwidth between the PE nodes through a label mapping message; wherein the label mapping message carries the bandwidth sharing identifier. The PE node is the PE node shown in fig. 8 to 11.
The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.
Claims (19)
1. A method for sharing bandwidth of multi-segment pseudo wires is characterized in that the same bandwidth sharing identifier is set for the pseudo wires which can share the same tunnel; the method comprises the following steps:
establishing a pseudo wire sharing bandwidth between provider edge PE nodes through label mapping information; wherein the label mapping message carries the bandwidth sharing identifier.
2. The method of claim 1, further comprising:
in the label mapping messages received by the PE node, determining that more than two label mapping messages have the same bandwidth sharing identifier, and binding the pseudo wires corresponding to the more than two label mapping messages to the same tunnel when the origin end PE and the termination end PE of the pseudo wires corresponding to the more than two label mapping messages are respectively the same.
3. The method of claim 1, further comprising:
in the label mapping messages received by the PE node, determining that the label mapping messages received by the PE node are different from the origin end PE or the termination end PE of the pseudo wires corresponding to the rest label mapping messages or different from the bandwidth sharing identifiers of the rest label mapping messages, allocating tunnels for bearing the pseudo wires corresponding to the received label mapping messages, or establishing a tunnel for bearing the pseudo wires corresponding to the received label mapping messages.
4. The method of claim 1, wherein the label mapping message comprises Access Group Identification (AGI) information, source specific identifier (SAII) information, target specific identifier (TAII) information, pseudowire bandwidth information, and pseudowire label; or, the label mapping message includes AGI information, SAII information, TAII information, pseudowire bandwidth information, routing information list information, and pseudowire label.
5. The method of claim 4, further comprising:
when the PE node determines that the received label mapping message does not contain routing information list information, the TAII information in the label mapping message is matched with the self identification, and when the TAII information is not matched, the next hop address is searched in a self pseudo wire routing table by taking the TAII as an index, and the label mapping message is continuously sent; establishing a pseudo wire reversely when matching;
or when determining that the label mapping message contains routing information list information, the PE node matches a first specific identifier AII in the routing information list with the self identifier, and when the label mapping message does not match the self identifier, the PE node searches a next hop address in a self pseudo wire routing table by taking the first AII as an index, and continuously sends the label mapping message; and when the pseudo wire address is matched with the label mapping information, searching the next hop address in the pseudo wire routing table of the pseudo wire by using the second AII index in the routing information list, and continuously sending the label mapping information.
6. The method of claim 5, further comprising:
and when the PE node takes the TAII or the AII as an index to find out no matched routing entry in the pseudowire routing table of the PE node, discarding the label mapping message.
7. The method of claim 5, wherein the first AII in the routing information list matches the identity of the PE node; the method further comprises the following steps:
and when the routing information list information does not contain a second AII, searching a next hop address in a pseudo wire routing table of the PE node by taking the TAII as an index, and continuously sending a label mapping message.
8. The method of claim 7, further comprising:
and when the first AII in the routing information list is matched with the identifier of the PE node, deleting the information matched with the first AII from the routing information list information in the label mapping message sent by the next hop address.
9. The method according to any of claims 1 to 8, wherein the PE node is a switching operator edge device, S-PE, node or a terminating operator edge device, T-PE, node; the pseudowire is a multi-segment pseudowire.
10. A PE node is applied to an edge-to-edge pseudo wire simulation system, and is characterized in that the edge-to-edge pseudo wire simulation system sets the same bandwidth sharing identifier for pseudo wires which can share the same tunnel; the PE node comprises:
the sending unit is used for sending label mapping information to other PE nodes when establishing the pseudo wires capable of sharing the bandwidth; wherein the label mapping message carries the bandwidth sharing identifier.
11. The PE node of claim 10, further comprising a receiving unit, a determining unit, and a binding unit; wherein,
a receiving unit for receiving a tag mapping message;
a determining unit, configured to determine that more than two label mapping messages have the same bandwidth sharing identifier, and that an origin PE and a terminating PE of a pseudo wire corresponding to the more than two label mapping messages are also the same, respectively, and trigger the binding unit;
and the binding unit is used for binding the pseudo wires corresponding to the more than two label mapping messages to the same tunnel.
12. The PE node according to claim 11, characterized in that the PE node further comprises an allocation unit and/or a tunnel establishment unit;
the determining unit determines that the label mapping message received by the receiving unit is different from the origin end PE or the termination end PE of the pseudo wire corresponding to the rest label mapping messages or different from the bandwidth sharing identifiers of the rest label mapping messages, and triggers the allocating unit or the tunnel establishing unit;
the distribution unit is used for distributing a tunnel for bearing a pseudo wire corresponding to the received label mapping message;
and the tunnel establishing unit is used for newly establishing a tunnel to bear the pseudo wire corresponding to the received label mapping message.
13. The PE node of claim 11, wherein the label mapping message includes access group identity, AGI, source specific identifier, SAII, target specific identifier, TAII, pseudowire bandwidth information, and pseudowire label; or, the label mapping message includes AGI information, SAII information, TAII information, pseudowire bandwidth information, routing information list information, and pseudowire label.
14. The PE node of claim 13, wherein the PE node further comprises a matching unit; wherein,
a matching unit, configured to match a TAII information in the label mapping message with the PE identifier when the determining unit further determines that the label mapping message does not include routing information list information, and look up a next hop address in a pseudowire routing table of the self using the TAII as an index when the label mapping message is not matched with the PE identifier, and trigger the sending unit to continue sending the label mapping message to the next hop; triggering the sending unit to reversely establish the pseudo wire when matching;
when the determining unit further determines that the label mapping message contains routing information list information, the matching unit matches the first AII in the routing information list with the PE identifier, and when the first AII is not matched with the PE identifier, the matching unit searches a next hop address in the pseudo wire routing table by taking the first AII as an index, and triggers the sending unit to continue sending the label mapping message; and when the two paths are matched, searching a next hop address in a pseudo wire routing table of the PE by using a second AII index in the routing information list, and triggering the sending unit to continue sending the label mapping message.
15. The PE node of claim 14, further comprising a discard unit that discards the label mapping message when the matching unit does not find a matching routing entry in the pseudowire routing table of the PE node indexed by the TAII/AII.
16. The PE node of claim 14, wherein the matching unit, in the process of matching a first AII in a routing information list with the identity of the PE node, looks up a next hop address in a pseudowire routing table of the PE node using the TAII as an index when no second AII is included in the routing information list information, and triggers the sending unit to continue sending label mapping messages.
17. The PE node of claim 16, wherein the PE node further includes a deletion unit, configured to delete, when the matching unit determines that the first AII in the routing information list matches the identity of the PE node, information matching the first AII from the routing information list information in the label mapping message sent by the sending unit according to the next hop address.
18. The PE node of any of claims 10 through 17, wherein the pseudowire is a multi-segment pseudowire.
19. A system for multi-segment pseudowires to share bandwidth comprising the PE nodes connected by pseudowires; establishing a pseudo wire sharing bandwidth between the PE nodes through a label mapping message; wherein the label mapping message carries the bandwidth sharing identifier.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010248915.6A CN102377637B (en) | 2010-08-05 | The method and system of Multi-segment pseudo wire shared bandwidth, provider's fringe node | |
| PCT/CN2010/077315 WO2012016392A1 (en) | 2010-08-05 | 2010-09-26 | Method and system for multi-segment pseudo wire sharing bandwidth and provider edge node thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010248915.6A CN102377637B (en) | 2010-08-05 | The method and system of Multi-segment pseudo wire shared bandwidth, provider's fringe node |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102377637A true CN102377637A (en) | 2012-03-14 |
| CN102377637B CN102377637B (en) | 2016-12-14 |
Family
ID=
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106301852A (en) * | 2015-06-04 | 2017-01-04 | 中兴通讯股份有限公司 | A kind of method and device of Packet Transport Network equipment pseudo-wire dual-homing protection |
| CN106411543A (en) * | 2015-07-27 | 2017-02-15 | 中兴通讯股份有限公司 | Method and device of dismounting multiple segments of pseudo-wires |
| CN106470159A (en) * | 2015-08-18 | 2017-03-01 | 中兴通讯股份有限公司 | The method and device of tunnel convergence |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101141330A (en) * | 2007-10-23 | 2008-03-12 | 华为技术有限公司 | Method, system and equipment to establish BFD detection for LSP tunnel |
| US20090154453A1 (en) * | 2007-12-18 | 2009-06-18 | Himanshu Shah | Systems and methods for pseudowire-in-pseudowire to transport pseudowire payload across packet switched networks |
| CN101505227A (en) * | 2009-03-11 | 2009-08-12 | 华为技术有限公司 | Method, device and system for implementing point to multi-point pseudowire |
| CN101552711A (en) * | 2008-04-03 | 2009-10-07 | 华为技术有限公司 | Method and device for establishing pseudowire mapping |
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101141330A (en) * | 2007-10-23 | 2008-03-12 | 华为技术有限公司 | Method, system and equipment to establish BFD detection for LSP tunnel |
| US20090154453A1 (en) * | 2007-12-18 | 2009-06-18 | Himanshu Shah | Systems and methods for pseudowire-in-pseudowire to transport pseudowire payload across packet switched networks |
| CN101552711A (en) * | 2008-04-03 | 2009-10-07 | 华为技术有限公司 | Method and device for establishing pseudowire mapping |
| CN101505227A (en) * | 2009-03-11 | 2009-08-12 | 华为技术有限公司 | Method, device and system for implementing point to multi-point pseudowire |
Non-Patent Citations (1)
| Title |
|---|
| G. LIU ET AL: "Multiprotocol Label Switching Transport Profile P2MP Share Protection", 《WWW.IETF.ORG/ARCHIVE/ID/DRAFT-LIU-MPLS-TP-P2MP-SHARE-PROTECTION-00.TXT》 * |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106301852A (en) * | 2015-06-04 | 2017-01-04 | 中兴通讯股份有限公司 | A kind of method and device of Packet Transport Network equipment pseudo-wire dual-homing protection |
| CN106411543A (en) * | 2015-07-27 | 2017-02-15 | 中兴通讯股份有限公司 | Method and device of dismounting multiple segments of pseudo-wires |
| CN106411543B (en) * | 2015-07-27 | 2020-06-05 | 中兴通讯股份有限公司 | Method and device for removing multi-segment pseudo wires |
| CN106470159A (en) * | 2015-08-18 | 2017-03-01 | 中兴通讯股份有限公司 | The method and device of tunnel convergence |
| CN106470159B (en) * | 2015-08-18 | 2020-09-15 | 中兴通讯股份有限公司 | Tunnel convergence method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2012016392A1 (en) | 2012-02-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108574630B (en) | EVPN message processing method, device and system | |
| CN111510379B (en) | EVPN message processing method, device and system | |
| CN110635935B (en) | Using multiple EVPN routes for respective service interfaces of a user interface | |
| US9516118B2 (en) | Scalable segment identifier allocation in segment routing | |
| US9912586B2 (en) | Method, system, and device for establishing pseudo wire | |
| CN110912796B (en) | Communication method, device and system | |
| WO2015165311A1 (en) | Method for transmitting data packet and provider edge device | |
| US9813332B2 (en) | Method, device and system for establishing label switched path | |
| WO2018103099A1 (en) | Method, device and system for sending and receiving message | |
| CN112511418A (en) | Message indicating method, device, equipment and storage medium | |
| CN113132235B (en) | Data message processing method based on virtual circuit and construction method of forwarding table item | |
| KR102245989B1 (en) | Redundancy Administrating Method for a Virtual Private Network and Network Switching Apparatus with the method implemented on it | |
| CN113904981B (en) | Routing information processing method and device, electronic equipment and storage medium | |
| US20090245263A1 (en) | Apparatus and method for transmitting packets in a packet switched network | |
| US10218609B2 (en) | Method and device for synchronizing interface parameter | |
| CN102710519A (en) | Method, system and device for establishing and removing cross-domain LSP (Label Switching Path) | |
| CN102377637B (en) | The method and system of Multi-segment pseudo wire shared bandwidth, provider's fringe node | |
| CN102377637A (en) | Multi-segment pseudo wire shared bandwidth method, system thereof and provider edge node | |
| CN113114553B (en) | Method and device for realizing butt joint of different networks under EVPN | |
| CN115037677A (en) | Method and device for protecting frr scene |
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 | ||
| 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: 20161214 Termination date: 20200805 |