WO2012126264A1 - 一种对微码表项进行层次化处理的方法和装置 - Google Patents
一种对微码表项进行层次化处理的方法和装置 Download PDFInfo
- Publication number
- WO2012126264A1 WO2012126264A1 PCT/CN2011/083809 CN2011083809W WO2012126264A1 WO 2012126264 A1 WO2012126264 A1 WO 2012126264A1 CN 2011083809 W CN2011083809 W CN 2011083809W WO 2012126264 A1 WO2012126264 A1 WO 2012126264A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- level
- microcode
- index
- primary
- microcode table
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/30—Peripheral units, e.g. input or output ports
- H04L49/3009—Header conversion, routing tables or routing tags
Definitions
- the present invention relates to the field of communications, and in particular, to a method and apparatus for hierarchical processing of microcode entries. Background technique
- the telecom carrier requires the metropolitan area transmission network to provide a more flexible network topology including point-to-point and point-to-multipoint, and provides multi-service bearer capability to achieve heterogeneous interworking, providing carrier-grade protection switching, in order to meet long-term Evolution (Long Term Evolution, referred to as "LTE") of 7
- LTE Long Term Evolution
- L2 VPN Layer 2 virtual private network
- L3VPN Layer 3 virtual private network
- the device needs to support common Layer 2 routing, common Layer 3 routing, L2VPN, L3VPN, Pseudo Wire Emulation Edge-to-Edge (PWE3), and label distribution protocol.
- Label Distribution Protocol referred to as "LDP”
- RSVP-TE Resource Reservation Protocol-Traffic Engineering
- IP FRR IP Fast Reroute
- LDP FRR LDP Fast Reroute
- TE FRR TE Fast Reroute
- VPN FRR VPN Fast Reroute
- PW pseudowire
- the first-level microcode table performs fast switching on the protection group by querying its primary fast re-routing table. Since there is only one fast re-routing table, in multi-level protection.
- the switch can only be implemented by the method of updating the first-level micro-code table.
- the driver-level update cannot achieve 50ms of carrier-level protection. Protection and replacement requirements. Summary of the invention
- a method for hierarchically processing a microcode entry includes:
- step A further includes:
- a primary fast reroute table for driving the update level one microcode table and a secondary fast reroute table for driving the update secondary microcode table are set.
- step B is specifically:
- the search result of the first-level micro-code table includes a first-level micro-code table related information, a first-level fast re-routing table index, and a second-level micro-code table index
- the second-level micro-code table search result includes a second-level micro Code table related information, secondary fast reroute table index and third level microcode table index.
- step C is specifically:
- the export and encapsulation information is found according to the information about the first-level microcode table obtained by searching the first-level microcode table. Further, the step C is specifically:
- the third-level microcode table is searched for the export and package information.
- step C is specifically:
- the third-level microcode table is searched for the export and package information.
- the step C further includes the step C1 of searching for the primary fast reroute table and/or the step C2 of finding the secondary fast reroute table;
- the step C1 is specifically:
- Finding the primary fast rerouting table according to the primary fast rerouting table index, obtaining the primary spare flag, determining the primary or secondary primary microcode table information, and the primary or secondary secondary microcode table index; C2 is specifically:
- the secondary fast rerouting table is searched according to the index of the secondary fast rerouting table, and the primary and secondary flag bits are obtained, and the primary or secondary secondary microcode table information and the primary or secondary tertiary microcode table index are determined.
- the method further includes the step D, specifically:
- the first-level microcode table index or the second-level microcode table index is not found, and the first-level microcode entry dedicated to the multicast replication service is available! Or secondary microcode expression! Find the first-level microcode table or the second-level microcode table, and obtain the multicast ID to obtain the export and encapsulation information.
- the first level microcode table is a forwarding instance table
- the second level microcode table is a path table
- the third level microcode table is a next hop table
- the forwarding instance table includes an egress and encapsulation information, or includes a private network label, a path table index, and a fast rerouting table index, or includes local access link information and egress and encapsulation information; and the path table includes three levels of microcode.
- Table index and fast reroute table index or include tunnels Label, next hop table index, and fast reroute table index.
- the next hop table includes a route next hop or a label switched path next hop.
- an apparatus for hierarchically processing a microcode entry provided by the present invention includes:
- a setting module configured to set a first-level microcode table, a second-level microcode table, and a third-level microcode table applicable to different services in the network;
- a first searching module configured to search for a first-level microcode table or a second-level microcode table according to a forwarding table result of different services during a forwarding entry search process
- the second searching module is configured to determine the lookup of the next-level entry according to the search result of the first-level microcode table or the second-level microcode table, until the export and the package information are found.
- the present invention makes various service update operations simple and realizes fast service switching by hierarchical processing of microcode entries.
- FIG. 2 is a flowchart of a method for hierarchically processing a microcode entry according to an embodiment of the present invention
- FIG. 3 is a schematic diagram of a microcode hierarchical forwarding entry provided by an embodiment of the present invention
- FIG. 4 is a main table content of a first-level microcode table, a second-level microcode table, and a third-level microcode table according to an embodiment of the present invention
- FIG. 5 is an embodiment of a service provided by the present invention associated with a hierarchical microcode entry
- FIG. 6 is a flowchart of a lookup of a forwarding entry when a 1:1 multi-level protection is provided according to an embodiment of the present invention
- FIG. 7 is a flowchart of an entry search when a multicast replication is required according to an embodiment of the present invention
- a device structure diagram for hierarchically processing a microcode entry provided by an embodiment. detailed description
- FIG. 2 is a flowchart of a method for hierarchically processing a microcode entry according to an embodiment of the present invention. As shown in FIG. 2, the method includes:
- Step 201 Set a first-level microcode table, a second-level microcode table, and a third-level microcode table applicable to different services in the network;
- Step 202 In the process of searching for a forwarding entry, searching for a primary microcode table or a secondary microcode table according to a forwarding table result of different services;
- Step 203 Determine, according to the search result of the first-level microcode table or the second-level microcode table, the search for the next-level entry until the export and package information is found.
- the above step 201 further includes:
- a primary fast reroute table for driving the update level one microcode table and a secondary fast reroute table for driving the update secondary microcode table are set.
- step 202 is specifically as follows:
- first-level microcode table index or a second-level microcode table index Obtaining a first-level microcode table index or a second-level microcode table index according to forwarding entries of different services; searching for a first-level microcode table or a second-level microcode table according to the first-level microcode table index or the second-level microcode table index, Obtaining the search result of the first-level micro code table or the second level micro code table;
- the search result of the first-level microcode table includes a first-level micro-code table related information, a first-level fast re-routing table index, and a second-level micro-code table index
- the second-level micro-code table search result includes a second-level micro-code table.
- the export and encapsulation information can be found by taking different entry flows for different services. In other words, some services can find export and encapsulation information only through the first-level microcode table. Some services need to take the secondary microcode table and the third-level microcode table, and some need to complete three microcode tables. Therefore, according to different entry process, the foregoing step 203 is embodied in the following situations:
- the above step 203 is specifically: The export and encapsulation information is found according to the information about the first-level microcode table obtained by searching the first-level microcode table.
- step 203 is specifically:
- the third-level microcode table is searched for the export and package information.
- step 203 is specifically:
- the third-level microcode table is searched for the export and package information.
- the above step 203 further includes the step 2031 of looking up the primary fast reroute table and/or the step 2032 of searching the secondary fast reroute table. That is, when the service only takes one level of the microcode table, the selection of the primary or backup information needs to be performed through the step 2031.
- the service takes the secondary microcode table and the third level microcode table, the In step 2032, the selection of the primary or secondary information is performed.
- the selection of the primary or secondary information needs to be performed through the steps 2031 and 2032. among them:
- the step 2031 is specifically:
- Finding the primary fast rerouting table according to the primary fast rerouting table index, obtaining the primary spare flag, determining the primary or secondary primary microcode table information, and the primary or secondary secondary microcode table index; 2032 is specifically:
- the secondary fast rerouting table is searched according to the level 2 fast rerouting table index, and the primary and secondary flag bits are obtained, and the primary or secondary secondary microcode table information, the primary or secondary tertiary microcode table index is determined.
- the method further includes the step 204, specifically:
- the first-level microcode table index or the second-level microcode table index is not found.
- the multicast replicates the first-level microcode table index or the second-level microcode table index dedicated to the service, searches for the first-level microcode table or the second-level microcode table, and obtains the multicast ID to obtain the export and package information.
- the first-level microcode table is a forwarding instance table
- the second-level microcode table is a path table
- the third-level microcode table is a next hop table
- the forwarding instance table includes an egress and encapsulation information, or includes a private network label, a path table index, and a fast rerouting table index, or includes local access link information and egress and encapsulation information; and the path table includes three levels of microcode.
- Table index and fast reroute table index or include tunnel label, next hop table index, and fast reroute table index;
- the next hop table includes a route next hop or a label switched path next hop.
- FIG. 3 is a schematic diagram of a microcode hierarchical forwarding entry provided by an embodiment of the present invention. As shown in FIG. 3, according to a corresponding forwarding entry of a service search service, a first-level microcode table index or a second-level microcode table index is obtained. And complete different microcode entries according to different services, in order to find export and package information.
- the specific business process is as follows:
- Step 301 Acquire a first-level microcode table index or a second-level microcode table index according to the corresponding forwarding entry of the service search service.
- the first-level microcode table index is obtained, go to step 302, and obtain the secondary microcode.
- step 304 is performed;
- Step 302 Search for the first-level microcode table according to the first-level microcode table index, and obtain information about the first-level microcode table related information, the first-level fast-re-route table index, and the second-level micro-code table index, and when searching for the first-level fast weight
- step 303 is performed. If the primary fast rerouting table is not required to be searched, if the primary microcode table related information includes the export and encapsulation information, step 307 is performed, otherwise step 304 is performed;
- Step 303 Find a primary fast rerouting table according to the primary fast rerouting table index, and determine whether to use the primary primary microcode table information or the standby primary microcode table information according to the primary standby flag bit in the table lookup result. And using the primary secondary microcode table index or the alternate secondary microcode table index;
- Step 304 Find a secondary microcode table according to the determined secondary microcode table index, and obtain information about the secondary microcode table related information, the secondary fast reroute table index, and the third-level microcode table index.
- Step 305 Search for the second-level fast re-routing table according to the index of the second-level fast re-routing table, and determine whether to use the secondary-level micro-code table information or the secondary second-level micro-code table information according to the primary and backup flag bits in the table lookup result. And the primary three-level microcode table index or the standby three-level microcode table index; step 306: searching for the third-level microcode table according to the determined three-level microcode table index;
- Step 307 Find the exit and package information.
- step 302 it is identified whether a level 1 fast rerouting table needs to be searched by placing a flag bit or a specially assigned index value in the level one microcode table.
- step 304 it is identified whether the secondary fast rerouting table needs to be searched by placing a flag bit or a specially assigned index value in the secondary microcode table.
- the level three microcode table is meaningful, for example, multiple routes or multiple label switching paths are corresponding. The same next hop, therefore, the three-level microcode table can be merged into the secondary microcode table according to the network processor resources.
- the primary microcode table may include N spares.
- the first level microcode table information and the N spare second level microcode table indexes are searched for corresponding fields in the fast reroute table in step 303, obtain the primary standby flag bit, and determine the used level one microcode table information and the second level.
- the micro-code table index; in step 304, the second-level micro-code table may include N spare second-level micro-code table information and N spare three-level micro-code table indexes, and find the second-level fast re-routing in step 305.
- the corresponding field in the table obtain the primary spare flag, determine the secondary microcode table information used and the third-level microcode table index.
- FIG. 4 shows the main table contents of the first-level micro code table, the second level micro code table, and the third level micro code table provided by the embodiment of the present invention, as shown in FIG. 4 .
- the first-level microcode table mainly stores information related to the primary fast-path table index, the primary or secondary primary micro-code table (for example: primary and backup PW labels, primary and backup export information, etc.), Primary or secondary secondary microcode table index, multicast ID, etc.;
- the secondary microcode table mainly stores the secondary fast reroute table index, the primary or secondary secondary microcode table related information (for example: primary or backup tunnel label, etc.), the primary or secondary tertiary microcode table. Index, multicast ID, etc.
- the three-level microcode table mainly stores export and package information.
- FIG. 5 shows an embodiment in which the service provided by the present invention is associated with a hierarchical microcode entry. As shown in FIG. 5, this embodiment analyzes and abstracts all services and considers the extension requirements for new services in advance, which is a service and A preferred embodiment of a hierarchical entry association.
- the first-level microcode table is defined as a forwarding instance table.
- the forwarding instance is a port in the VLAN, and the forwarding instance table stores the export and encapsulation information.
- the forwarding of the L3 VPN to the network side is the virtual route forwarding (VRF) instance of the private network label, and the forwarding instance table stores the private network label, the path table index, and the first-level fast weight. Routing table index, etc.;
- VRF virtual route forwarding
- the forwarding instance is a virtual forwarding instance (Virtual Forwarding Instance, referred to as "VFI") or a virtual leased line (Virtual Leased Line, "VLL").
- VFI Virtual Forwarding Instance
- VLL Virtual Leased Line
- the L2 VPN is forwarded to the user side.
- the example is the local access link (AC), which stores AC information and egress information.
- the secondary microcode table is defined as a path table.
- the path is a route, and the path table stores a next hop index and a secondary fast reroute table index.
- the path is a label switched path.
- the path table stores the tunnel label and the next hop bow! And secondary fast reroute table indexes, etc.;
- the path is a Generalized Routing Encapsulation (GRE) or an IP-in-IP tunnel.
- GRE Generalized Routing Encapsulation
- the path table stores the next hop table index and the second-level fast re-route index.
- the third-level microcode table is defined as the next hop table.
- the forwarding of Layer 3 forwarding and L3VPN to the user side is the next hop of the route
- Forwarding to the P device is the next hop of the label switching path.
- the entry fields can be reused.
- the forwarding of the L2VPN and the L3VPN to the network side in the forwarding instance table, the PW label field corresponding to the L2VPN and the private network label field corresponding to the L3VPN are reused; for example, in the forwarding instance table, the AC information field corresponding to the L2VPN can be associated with the PW. Tag field multiplexing, etc.
- service 1 can be forwarded by the common Layer 2 or L2VPN to the AC, and the egress and encapsulation information of the service 1 is obtained by directly searching the forwarding instance table.
- Service 2 and service 3 can be forwarded to the public network side by L2VPN or L3VPN.
- Service 2 and service 3 correspond to the same path table. If the path is protected, the corresponding path protection group is corresponding; service 4 is ordinary three-layer or P. The device label is switched or the L3VPN is forwarded to the private network. The two paths corresponding to service 4 and service 3 are associated with the same next hop.
- the search result of the multiple primary microcode tables can determine the same secondary microcode table, and the search results of the multiple secondary microcode tables can determine the same tertiary microcode table, that is, due to the microcode table Hierarchicalization of items makes it possible to make microcode entries many-to-one, greatly saving table space and making the driver update operation simple and clear, for example:
- Multiple paths correspond to the same next hop.
- multiple label switching paths correspond to the same next hop.
- entries in this embodiment are hierarchical, different services can go through different entry procedures, and do not need to go through the first, second, and third-level microcode tables. For example, some services only take one level of microcode. Table, some businesses take the secondary microcode table and the third-level microcode table.
- FIG. 6 is a flowchart showing the forwarding entry of the 1:1 multi-level protection provided by the embodiment of the present invention.
- the service 1 is the L2VPN PW FRR over LDP FRR, and the forwarding instance table stores the PW information and path.
- Index because service 1 is a two-level protection, the forwarding instance table stores the primary PW information, the alternate PW information, the primary path table index, and the alternate path table index; the MPLS tunnel information is stored in the path table; 1 is a two-level protection.
- the path table stores the primary path information, the backup path information, and the corresponding next hop index.
- the next hop table stores the next hop information of the MPLS tunnel.
- the process of searching for a microcode entry in the uplink according to the service 1 includes the following steps:
- Step 601 Search the MAC forwarding table according to the service 1 to obtain the forwarding instance table index.
- Step 602 Search the forwarding instance table according to the forwarding instance table index, and obtain the primary fast reroute table index, the primary PW information, and the standby PW information.
- Step 603 Search for the primary fast rerouting table according to the primary fast rerouting table index, obtain the primary standby flag, and determine whether to use the primary or backup PW information according to the primary standby flag, and the primary or backup PW corresponds.
- Path table index Search for the primary fast rerouting table according to the primary fast rerouting table index, obtain the primary standby flag, and determine whether to use the primary or backup PW information according to the primary standby flag, and the primary or backup PW corresponds.
- Step 604 Search the path table according to the path table index corresponding to the PW of the primary or backup PW, obtain the index of the secondary fast reroute table, the primary or backup path information, and the next hop table index corresponding to the active or standby path. ;
- Step 605 Find a secondary fast re-routing table, obtain a primary standby flag, according to the primary standby Determine whether to take the primary path or the alternate path;
- Step 606 Find the next hop table corresponding to the active or standby path according to the next hop table index corresponding to the active or standby path, and obtain the export and encapsulation information.
- Step 607 Search the label forwarding table according to the service 2, and obtain the forwarding instance table index.
- Step 608 Search the forwarding instance table according to the forwarding instance table index, and obtain Path table index;
- Step 609 Search the path table according to the path table index, obtain the index of the second-level fast re-routing table, the path information of the primary or backup, and the index of the next hop table;
- Step 610 Find a secondary fast rerouting table, obtain a primary standby flag, and determine whether to take the primary path or the alternate path according to the primary and secondary flag bits;
- Step 611 Find the next hop table corresponding to the active or standby path, and obtain the export and encapsulation information.
- Step 609 of the above-mentioned search path table, step 610 of searching the second-level fast re-routing table, and step 604 of searching the path table in service 1 respectively, and searching for the second-level fast weight, are performed.
- the step 605 of the routing table is the same, so that when the path protection group is switched, the driver only needs to update the fast re-routing table corresponding to the path protection group to implement switching of multiple services.
- multi-level protection especially when multiple upper-layer protections are associated with a lower-level protection, can be quickly switched to achieve a carrier-class protection switching requirement of 50 ms.
- 1 1 single-level protection (such as TE FRR), forwarding instance 1: 1 protection (such as L2VPN PW FRR or L3VPN FRR) or path 1 : 1 protection is a subset of multi-level protection and will not be described.
- 1 single-level protection such as TE FRR
- 1 protection such as L2VPN PW FRR or L3VPN FRR
- path 1 : 1 protection is a subset of multi-level protection and will not be described.
- FIG. 7 is a flowchart showing an entry search process for a multicast replication according to an embodiment of the present invention.
- service 1 is a common Layer 2 unknown unicast
- service 2 and service 3 are different instances of an L2 VPN.
- Unicast in this embodiment, service 2 and service 3 follow the same path; service 4 is ordinary three-layer multicast.
- Step 701 Search for the corresponding forwarding table according to the service 1, the service 2, the service 3, and the service 4, respectively, and the forwarding entry is not found, that is, the service 1, the service 2, and the service 3 do not find the corresponding forwarding instance table index, and the service 4 does not find the right.
- Step 701 Search for the corresponding forwarding table according to the service 1, the service 2, the service 3, and the service 4, respectively, and the forwarding entry is not found, that is, the service 1, the service 2, and the service 3 do not find the corresponding forwarding instance table index, and the service 4 does not find the right.
- Corresponding path table index Search for the corresponding forwarding table according to the service 1, the service 2, the service 3, and the service 4, respectively, and the forwarding entry is not found, that is, the service 1, the service 2, and the service 3 do not find the corresponding forwarding instance table index, and the service 4 does not find the right.
- Step 702 The service, the service 2, and the service 3 respectively use the forwarding instance index of the forwarding instance index to find the forwarding instance table corresponding to the forwarding instance index, and obtain the multicast ID in the forwarding instance table, so that the downlink ID is based on the multicast ID.
- Service 4 uses the path index corresponding to the path index when the forwarding entry is not found, and obtains the multicast ID in the path table, so that the downlink performs multicast replication according to the multicast ID.
- PW MPLS tunnel corresponding path/subnet 1+1 protection, 1+1 and 1:1 hybrid multi-level protection, Layer 3 and Layer 3 multicast, L2VPN broadcast, etc.
- PW MPLS tunnel corresponding path/subnet 1+1 protection, 1+1 and 1:1 hybrid multi-level protection, Layer 3 and Layer 3 multicast, L2VPN broadcast, etc.
- the service is internally replicated by the downlink and sent to each port under the multicast ID.
- FIG. 8 is a structural diagram of a device for hierarchically processing a microcode entry according to an embodiment of the present invention. As shown in FIG. 8, the device includes a setting module, a first searching module, and a second searching module, where:
- a setting module is configured to set a first-level microcode table, a second-level microcode table, and a third-level microcode table applicable to different services in the network.
- the setting module sets a first-level microcode table, a second-level microcode table, and a third-level microcode table applicable to different services according to services in the network.
- the first-level microcode table is a forwarding instance table
- the second-level microcode table is a path table
- the third-level microcode table is a next hop table
- the forwarding instance table includes an export and encapsulation information, or includes a private network label and a path table.
- Index and fast reroute table index or include local access link information and egress and encapsulation information
- path table includes three-level microcode table index and fast reroute table index, or includes tunnel label, next hop table index, and fast The re-routing table index
- the next hop table includes the next hop of the route or the next hop of the label switched path.
- the setting module is further configured to set a first-level fast re-routing table for driving and updating the first-level microcode table, and A second-level fast reroute table that drives the update of the secondary microcode table.
- the first searching module is configured to search for a level one micro code table or a second level micro code table according to a forwarding table result of different services in the forwarding table item searching process. Specifically, the first searching module obtains the first-level microcode table index or the second-level microcode table index according to the forwarding entry of the different service, and searches for the first-level micro according to the first-level microcode table index or the second-level microcode table index.
- the code table or the second level microcode table obtains the search result of the first level micro code table or the second level micro code table.
- the search result of the first-level microcode table includes the first-level microcode table related information, the first-level fast re-routing table index, and the second-level micro-code table index
- the second-level micro-code table search result includes the second-level micro-code table related information. , two-level fast reroute table index and three-level microcode table index.
- the first lookup module multicasts the first-level microcode table index or the second-level microcode table index dedicated to the service. Find the first-level microcode table or the second-level microcode table, and obtain the multicast ID to get the export and package information.
- the second searching module is configured to determine the lookup of the next-level entry according to the search result of the first-level microcode table or the second-level microcode table, until the export and the package information are found.
- the second searching module may find the export and encapsulation information according to the first-level microcode table related information obtained by searching the first-level microcode table according to different services; or the second searching module obtains the information according to the first-level microcode table.
- First-level microcode table related information and second-level microcode table index find the second-level microcode table, and find the third-level microcode table related information and the third-level microcode table index according to the second-level microcode table.
- the microcode table finds the export and encapsulation information; or the second search module finds the third-level microcode table according to the secondary microcode table related information and the third-level microcode table index obtained by searching the secondary microcode table, and finds the export and package. information.
- the second lookup module In the presence of protection, especially multi-level protection, the second lookup module also needs to look up a level 1 fast reroute table and/or look up a level 2 fast reroute table. among them:
- the second search module searches the first-level fast re-routing table. Specifically, the second search module searches the first-level fast re-routing table according to the first-level fast re-routing table index, obtains the primary standby flag, and determines the primary or standby first-level micro Code table information, primary or secondary secondary microcode table index; The second search module searches for the second-level fast re-routing table. Specifically, the second search module searches the second-level fast re-routing table according to the index of the second-level fast re-routing table, obtains the primary standby flag, and determines the primary or secondary secondary micro- Code table information, primary or alternate three-level microcode table index.
- the present invention makes the various business processes, especially the protection switching process, modularized by the hierarchical layering of the entries, and the driving update operation is simple, and realizes rapid switching when the service is protected, especially multi-level protection.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明公开了一种对微码表项进行层次化处理的方法和装置,涉及通信领域,方法包括以下步骤:设置适用于网络中不同业务的一级微码表、二级微码表和三级微码表;在转发表项查找过程中,根据不同业务的转发表结果,查找一级微码表或二级微码表;根据对一级微码表或二级微码表的查找结果,确定对下一级表项的查找,直至找到出口及封装信息。本发明通过对微码表项进行层次化处理,使微码表项驱动更新操作简单,在业务存在保护尤其是多级保护时,实现快速倒换。
Description
一种对微码表项进行层次化处理的方法和装置 技术领域
本发明涉及通信领域, 尤其涉及一种对微码表项进行层次化处理的方 法和装置。 背景技术
电信运营商要求城域传输网络提供包括点到点、 点到多点等方式的更 为灵活的网络拓朴, 提供多业务承载能力以实现异质互通, 提供电信级的 保护倒换, 为了满足长期演进技术(Long Term Evolution, 简称 " LTE" )的 7|载需求, 需要支持二层虚拟专用网 ( Layer 2 Virtual Private Network, 简 称 " L2 VPN" )桥接三层虚拟专用网 (Layer 3 Virtual Private Network, 简称 "L3VPN" )等等。 为了满足运营商的各种需求, 设备需要支持普通二层路 由、 普通三层路由、 L2VPN、 L3VPN、 端到端伪线仿真 (Pseudo Wire EmulationEdge-to-Edge , 简称 "PWE3" )、 标签分发协议( Label Distribution Protocol, 简称 "LDP" )、 资源预留协议-流量工程( Resource Reservation Protocol-Traffic Engineering, 简称 "RSVP-TE" )、 IP快速重路由 (IP Fast Reroute, 简称 "IP FRR" )、 LDP快速重路由( LDP Fast Reroute , 简称 "LDP FRR" )、 TE快速重路由 (TE Fast Reroute, 简称 "TE FRR" )、 VPN快速重 路由( VPN Fast Reroute,简称 "VPN FRR" ),伪线( Pseudo Wire,简称 "PW" ) 保护、 线性保护、 环网保护及多级保护的叠加等。 现有技术中微码上行转 发表项如图 1 所示, 一级微码表通过查询其一级快速重路由表对保护组进 行快速倒换, 由于只有一个快速重路由表, 在多级保护时, 只能通过驱动 更新一级微码表的方法实现倒换, 在存在大量保护组时, 尤其是大量上层 保护复用一个下层保护时,通过驱动更新的方法无法达到 50ms的电信级保
护倒换要求。 发明内容
本发明的目的在于提供一种对微码表项进行层次化处理的方法和装 置, 能更好的解决快速倒换的问题。
根据本发明的一个方面, 本发明提供的一种对微码表项进行层次化处 理的方法包括:
A )设置适用于网络中不同业务的一级微码表、二级微码表和三级微码 表;
B )在转发表项查找过程中, 根据不同业务的转发表结果, 查找一级微 码表或二级微码表;
C )根据对一级微码表或二级微码表的查找结果, 确定对下一级表项的 查找, 直至找到出口及封装信息。
进一步地, 所述步驟 A还包括:
设置用于驱动更新一级微码表的一级快速重路由表以及用于驱动更新 二级微码表的二级快速重路由表。
进一步地, 所述步驟 B具体为:
根据不同业务的转发表项, 获取一级微码表索引或二级微码表索引; 根据所述一级微码表索引或二级微码表索引查找一级微码表或二级微 码表, 获取一级微码表或二级微码表的查找结果;
其中, 所述一级微码表的查找结果包括一级微码表相关信息、 一级快 速重路由表索引和二级微码表索引, 所述二级微码表的查找结果包括二级 微码表相关信息、 二级快速重路由表索引和三级微码表索引。
进一步地, 所述步驟 C具体为:
根据查找一级微码表得到的所述一级微码表相关信息, 找到出口及封 装信息。
进一步地, 所述步驟 C具体为:
根据查找一级微码表得到的所述一级微码表相关信息和二级微码表索 引, 查找二级微码表;
根据查找二级微码表得到的所述二级微码表相关信息和三级微码表索 引, 查找三级微码表, 找到出口及封装信息。
进一步地, 所述步驟 C具体为:
根据查找二级微码表得到的所述二级微码表相关信息和三级微码表索 引, 查找三级微码表, 找到出口及封装信息。
所述步驟 C还包括查找一级快速重路由表的步驟 C1和 /或查找二级快 速重路由表的步驟 C2;
所述步驟 C1具体为:
根据一级快速重路由表索引查找一级快速重路由表, 获得主备用标志 位, 确定主用或备用的一级微码表信息以及主用或备用的二级微码表索引; 所述步驟 C2具体为:
根据二级快速重路由表索引查找二级快速重路由表, 获得主备用标志 位, 确定主用或备用的二级微码表信息以及主用或备用的三级微码表索引。
所述方法还包括步驟 D, 具体为:
根据业务查找转发表项, 未找到一级微码表索引或二级微码表索引, 组播复制业务专用的一级微码表索 !或二级微码表索 ! , 查找一级微码表 或二级微码表, 并获取组播 ID, 得到出口和封装信息。
优选地, 所述一级微码表是转发实例表, 所述二级微码表是路径表, 所述三级微码表是下一跳表;
所述转发实例表包括出口和封装信息, 或者包括私网标签、 路径表索 引和快速重路由表索引, 或者包括本地接入链路信息以及出口和封装信息; 所述路径表包括三级微码表索引和快速重路由表索引, 或者包括隧道
标签、 下一跳表索引和快速重路由表索引。
所述下一跳表包括路由下一跳或标签交换路径下一跳。
根据本发明的另一个方面, 本发明提供的一种对微码表项进行层次化 处理的装置包括:
设置模块, 用于设置适用于网络中不同业务的一级微码表、 二级微码 表和三级微码表;
第一查找模块, 用于在转发表项查找过程中, 根据不同业务的转发表 结果, 查找一级微码表或二级微码表;
第二查找模块, 用于根据对一级微码表或二级微码表的查找结果, 确 定对下一级表项的查找, 直至找到出口及封装信息。
与现有技术相比, 本发明的有益效果在于: 本发明通过对微码表项的 层次化处理, 使各种业务更新操作简单, 实现业务快速倒换。 附图说明
图 1是现有技术微码上行转发表项;
图 2是本发明实施例提供的对微码表项进行层次化处理的方法流程图; 图 3是本发明实施例提供的微码层次化转发表项示意图;
图 4是本发明实施例提供的一级微码表、 二级微码表和三级微码表的 主要表内容;
图 5是本发明提供的业务与层次化微码表项关联的实施例;
图 6是本发明实施例提供的 1 : 1多级保护时的转发表项查找流程图; 图 7是本发明实施例提供的需要组播复制时的表项查找流程图; 图 8是本发明实施例提供的对微码表项进行层次化处理的装置结构图。 具体实施方式
以下结合附图对本发明的优选实施例进行详细说明, 应当理解, 以下
所说明的优选实施例仅用于说明和解释本发明, 并不用于限制本发明。 图 2显示了本发明实施例提供的对微码表项进行层次化处理的方法流 程图, 如图 2所示, 包括:
步驟 201 : 设置适用于网络中不同业务的一级微码表、二级微码表和三 级微码表;
步驟 202: 在转发表项查找过程中, 根据不同业务的转发表结果, 查找 一级微码表或二级微码表;
步驟 203 : 根据对一级微码表或二级微码表的查找结果,确定对下一级 表项的查找, 直至找到出口及封装信息。
上述步驟 201还包括:
设置用于驱动更新一级微码表的一级快速重路由表以及用于驱动更新 二级微码表的二级快速重路由表。
上述步驟 202具体为:
根据不同业务的转发表项, 获取一级微码表索引或二级微码表索引; 根据一级微码表索引或二级微码表索引查找一级微码表或二级微码 表, 获取一级微码表或二级微码表的查找结果;
其中, 一级微码表的查找结果包括一级微码表相关信息、 一级快速重 路由表索引和二级微码表索引, 所述二级微码表的查找结果包括二级微码 表相关信息、 二级快速重路由表索引和三级微码表索引。
本发明中, 尽管对微码表项进行了层次化处理, 但对于不同的业务可 以通过走不同的表项流程, 找到出口及封装信息。 换句话说, 一些业务可 以仅通过一级微码表找到出口和封装信息, 有的业务需要走二级微码表和 三级微码表, 还有的需要走完三个微码表等。 因此, 根据不同的表项流程, 上述步驟 203具体体现为以下几种情况:
上述步驟 203具体为:
根据查找一级微码表得到的所述一级微码表相关信息, 找到出口及封 装信息。
上述步驟 203具体为:
根据查找一级微码表得到的所述一级微码表相关信息和二级微码表索 引, 查找二级微码表;
根据查找二级微码表得到的所述二级微码表相关信息和三级微码表索 引, 查找三级微码表, 找到出口及封装信息。
上述步驟 203具体为:
根据查找二级微码表得到的所述二级微码表相关信息和三级微码表索 引, 查找三级微码表, 找到出口及封装信息。
在业务存在保护, 尤其是多级保护的情况下, 上述步驟 203还包括查 找一级快速重路由表的步驟 2031和 /或查找二级快速重路由表的步驟 2032。 也就是说, 当业务仅走一级微码表时, 需要通过所述步驟 2031进行主用或 备用信息的选择, 当业务走二级微码表和三级微码表时, 需要通过所述步 驟 2032进行主用或备用信息的选择; 当业务走全部三个微码表项时, 需要 通过所述步驟 2031和步驟 2032进行主用或备用信息的选择。 其中:
所述步驟 2031具体为:
根据一级快速重路由表索引查找一级快速重路由表, 获得主备用标志 位, 确定主用或备用的一级微码表信息以及主用或备用的二级微码表索引; 所述步驟 2032具体为:
根据二级快速重路由表索引查找二级快速重路由表, 获得主备用标志 位, 确定主用或备用的二级微码表信息、 主用或备用的三级微码表索引。
为了在未找到一级微码表索引或二级微码表索引时找到业务的出口和 封装信息, 所述方法还包括步驟 204, 具体为:
根据业务查找转发表项, 未找到一级微码表索引或二级微码表索引,
组播复制该业务专用的一级微码表索引或二级微码表索引, 查找一级微码 表或二级微码表, 并获取组播 ID, 以便得到出口和封装信息。
优选地, 所述一级微码表是转发实例表, 所述二级微码表是路径表, 所述三级微码表是下一跳表, 其中:
所述转发实例表包括出口和封装信息, 或者包括私网标签、 路径表索 引和快速重路由表索引, 或者包括本地接入链路信息以及出口和封装信息; 所述路径表包括三级微码表索引和快速重路由表索引, 或者包括隧道 标签、 下一跳表索引和快速重路由表索引;
所述下一跳表包括路由下一跳或标签交换路径下一跳。
图 3 显示了本发明实施例提供的微码层次化转发表项示意图, 如图 3 所示, 根据业务查找业务相应的转发表项, 得到一级微码表索引或二级微 码表索引, 并根据业务的不同走完不同的微码表项, 以便找到出口及封装 信息。 其具体的业务处理流程如下:
步驟 301 : 根据业务查找业务相应的转发表项, 获取一级微码表索引或 二级微码表索引, 当获取到一级微码表索引时, 执行步驟 302 , 当获取到二 级微码表索引时, 执行步驟 304;
步驟 302: 根据一级微码表索引查找一级微码表, 获取一级微码表相关 信息、 一级快速重路表索引和二级微码表索引等信息, 当需要查找一级快 速重路由表时, 执行步驟 303 , 当不需要查找一级快速重路由表时, 若一级 微码表相关信息内包含出口及封装信息, 则执行步驟 307, 否则执行步驟 304;
步驟 303: 根据一级快速重路由表索引查找一级快速重路由表,根据查 表结果中的主备用标志位, 确定使用主用的一级微码表信息还是备用的一 级微码表信息, 以及使用主用的二级微码表索引还是备用的二级微码表索 引;
步驟 304: 根据确定的二级微码表索引查找二级微码表, 获取二级微码 表相关信息、 二级快速重路表索引和三级微码表索引等信息, 当需要查找 二级快速重路由表时, 执行步驟 305 , 否则, 执行步驟 306;
步驟 305: 根据二级快速重路由表索引查找二级快速重路由表,根据查 表结果中的主备用标志位, 确定使用主用的二级微码表信息还是备用的二 级微码表信息, 以及主用的三级微码表索引还是备用的三级微码表索引; 步驟 306: 根据确定的三级微码表索引查找三级微码表;
步驟 307: 找到出口及封装信息。
上述步驟 302中, 通过在一级微码表中放标志位或特殊分配的索引值, 标识是否需要查找一级快速重路由表。
上述步驟 304中, 通过在二级微码表中放标志位或特殊分配的索引值, 标识是否需要查找二级快速重路由表。
上述步驟 306 中, 在多个业务对应一个三级微码表, 并且业务更新只 需更新三级微码表时, 三级微码表才有意义, 比如多条路由或多个标签交 换路径对应同一个下一跳, 因此, 可以根据网络处理器资源情况将三级微 码表合并到二级微码表中。
需要说明的是, 对 1:N保护, 即一条路由对应一个主用下一跳和 N个 备用下一跳, 例如 IP FRR, 在步驟 302中所述一级微码表可以包含 N个备 用的一级微码表信息和 N个备用的二级微码表索引, 在步驟 303查找快速 重路由表中的对应字段, 获取主备用标志位, 并确定使用的一级微码表信 息和二级微码表索引; 在步驟 304中所述二级微码表可以包含 N个备用的 二级微码表信息和 N个备用的三级微码表索引, 在步驟 305中查找二级快 速重路由表中对应字段, 获取主备用标志位, 确定使用的二级微码表信息 和三级微码表索引。
为便于说明, 以下实施例中以 1:1保护为例。
图 4显示了本发明实施例提供的一级微码表、 二级微码表和三级微码 表的主要表内容, 如图 4所示。
所述一级微码表主要存放一级快速重路表索引、 主用或备用的一级微 码表相关信息(例如: 主用和备用的 PW标签, 主用和备用的出口信息等)、 主用或备用的二级微码表索引、 组播 ID等;
二级微码表主要存放二级快速重路表索引、 主用或备用的二级微码表 相关信息(例如: 主用或备用的隧道标签等)、 主用或备用的三级微码表索 引、 组播 ID等;
三级微码表主要存放出口及封装信息等。
图 5显示了本发明提供的业务与层次化微码表项关联的实施例,如图 5 所示, 本实施例对所有业务进行分析抽象并预先考虑对新业务的扩展要求, 是一个业务与层次化表项关联的优选的实施例。
1、 一级微码表定义为转发实例表。
对普通二层, 转发实例是 VLAN内端口, 转发实例表存放出口和封装 信息等;
对 L3 VPN向网络侧的转发 ,转发实例是私网标签标识的对端虚拟路由 转发(Virtual Route Forwarding, 简称 "VRF" )实例, 转发实例表存放私网 标签、 路径表索引和一级快速重路由表索引等;
对 L2VPN向网络侧的转发,转发实例是用伪线连接的对端虚拟转发实 例( Virtual Forwarding Instance,简称 "VFI" )或虚拟租用线路( Virtual Leased Line, 简称 "VLL" ), 转发实例表存放 PW标签、 路径表索引和一级快速重 路由表索引等;
对 L2 VPN向用户侧的转发, 实例是本地接入链路 ( Attached Circuit , 简称 "AC" ), 该表存放的是 AC信息和出口信息等。
2、 二级微码表定义为路径表。
对普通三层, 路径是路由, 路径表存放下一跳索引和二级快速重路由 表索引等;
对 MPLS隧道, 路径是标签交换路径, 路径表存放的是隧道标签、 下 一跳表索弓!和二级快速重路由表索引等;
对 IP隧道, 路径是通由路由封装隧道( General Routing Encapsulation, 简称 "GRE" )或 IP-in-IP隧道, 路径表存放下一跳表索引和二级快速重路 由表索引等。
3、 三级微码表定义为下一跳表。
对三层转发和 L3VPN向用户侧的转发, 是路由下一跳;
对 P设备(中间转发设备)转发, 是标签交换路径下一跳。
由于不同业务对应不同的表项, 为了节省表空间, 表项字段可以复用。 例如, L2VPN和 L3VPN向网络侧的转发, 转发实例表中, L2VPN对应的 PW标签字段和 L3VPN对应的私网标签字段复用; 又如, 转发实例表中, L2VPN对应的 AC信息字段可以和 PW标签字段复用等。
在图 5中, 业务 1可以是普通二层或 L2VPN向 AC的转发, 直接通过 查找转发实例表获取业务 1的出口及封装信息;
业务 2和业务 3可以是 L2VPN或 L3VPN向公网侧的转发, 业务 2和 业务 3对应同一个路径表, 如果路径有保护, 对应的是同一个路径保护组; 业务 4为普通三层或 P设备标签交换或 L3VPN向私网侧的转发,业务 4和业务 3分别对应的两条路径关联到同一个下一跳。
可见, 多个一级微码表的查找结果可确定同一的二级微码表, 多个二 级微码表的查找结果可确定同一的三级微码表, 也就是说, 由于微码表项 的层次化, 使微码表项多对一成为可能, 极大节省表空间, 使驱动更新操 作简单和清晰, 例如:
多个转发实例对应同一路径, 比如多条伪线承载在同一条标签交换路
径上;
多个路径对应同一个下一跳, 比如多条标签交换路径对应同一个下一 跳。
本实施例的表项虽然是层次化的, 但不同业务可以走不同的表项流程, 而不需要都走完一、 二、 三级微码表, 例如, 有的业务仅走一级微码表, 有的业务走二级微码表和三级微码表等。
图 6显示了本发明实施例提供的 1: 1 多级保护时的转发表项查找流程 图, 如图 6所示, 假设业务 1为 L2VPN PW FRR over LDP FRR, 转发实例 表保存 PW信息和路径索引, 由于业务 1为两级保护, 转发实例表中保存 了主用的 PW信息、 备用的 PW信息、 主用的路径表索引和备用的路径表 索引; 路径表中保存 MPLS隧道信息; 由于业务 1为两级保护, 路径表中 保存了主用路径信息、 备路径信息和对应的下一跳索引; 下一跳表保存 MPLS隧道下一跳信息。 根据业务 1的 (例如: L2VPN PW FRR over LDP FRR )上行查找微码表项的流程包括以下步驟:
步驟 601 : 根据业务 1查找 MAC转发表, 获取转发实例表索引; 步驟 602: 根据转发实例表索引, 查找转发实例表, 获取一级快速重路 由表索引、 主用的 PW信息、 备用的 PW信息、 主用的 PW对应的路径表 索引和备用的 PW对应的路径表索引;
步驟 603: 根据一级快速重路由表索引, 查找一级快速重路由表, 获取 主备用标志位, 根据所述主备用标志位确定使用主用或备用的 PW信息, 主用或备用的 PW对应的路径表索引;
步驟 604: 根据主用或备用的 PW对应的路径表索引, 查找路径表, 获 取二级快速重路由表索引、 主用或备用的路径信息, 以及主用或备用路径 对应的下一跳表索引;
步驟 605: 查找二级快速重路由表, 获取主备用标志位, 根据主备用标
志位确定走主用路径还是备用路径;
步驟 606: 根据主用或备用路径对应的下一跳表索引, 查找主用或备用 路径对应的下一跳表, 获取出口及封装信息。
假设业务 2为 LDP FRR, 上行查找微码表项流程包括以下步驟: 步驟 607: 根据业务 2查找标签转发表, 获取转发实例表索引; 步驟 608: 根据转发实例表索引, 查找转发实例表, 获取路径表索引; 步驟 609: 根据路径表索引查找路径表, 获取二级快速重路由表索引、 主用或备用的路径信息, 以及下一跳表索引;
步驟 610: 查找二级快速重路由表, 获取主备用标志位, 根据主备用标 志位决定走主用路径还是备用路径;
步驟 611 :查找主用或备用路径对应的下一跳表,获取出口及封装信息。 由于业务 1与业务 1走同一个路径保护组, 所以上述查找路径表的步 驟 609、上述查找二级快速重路由表的步驟 610分别与业务 1中查找路径表 的步驟 604、 查找二级快速重路由表的步驟 605是相同的, 这样当路径保护 组发生倒换时, 驱动只需更新该路径保护组对应的快速重路由表即可实现 多条业务的倒换。
由于表项的层次化, 使多级保护尤其是多个上层保护关联到一个下层 保护时能够快速倒换, 达到 50ms的电信级保护倒换要求。
1: 1单级保护(如 TE FRR ), 转发实例 1: 1保护(如 L2VPN PW FRR 或 L3VPN FRR )或路径 1 : 1保护等是多级保护的子集, 不再进行描述。
图 7显示了本发明实施例提供的需要组播复制时的表项查找流程图, 如图 7所示, 假设业务 1为普通二层未知单播, 业务 2和业务 3为不同实 例的 L2VPN未知单播, 本实施例中, 业务 2和业务 3走同一路径; 业务 4 为普通三层组播。
需要组播复制时的微码表项查找流程包括以下步驟:
步驟 701 : 根据业务 1、 业务 2、 业务 3、 业务 4分别查找对应的转发 表, 未找到转发条目, 即业务 1、 业务 2、 业务 3未找到相应的转发实例表 索引, 业务 4未找对相应的路径表索引;
步驟 702: 业务 1、 业务 2、 业务 3分别使用其未找到转发条目时专用 的转发实例索引查找转发实例索引对应的转发实例表, 获取转发实例表中 的组播 ID, 以便下行根据组播 ID进行组播复制; 业务 4使用其未找到转发 条目时专用的路径索引查找路径索引对应的路径表, 获取路径表中的组播 ID, 以便下行根据组播 ID进行组播复制。
对需要组播复制的业务, 由于考虑到节省交换带宽, 都在下行进行复 制, 比如 PW、 MPLS隧道对应的路径 /子网 1+1保护、 1+1与 1: 1混合多级 保护、 二层和三层组播、 L2VPN广播等, 上行需要获取组播 ID, 通过内部 交换头将组播 ID传给下行, 由下行将业务进行板内复制并发送至组播 ID 下的各端口。
图 8显示了本发明实施例提供的对微码表项进行层次化处理的装置结 构图, 如图 8所示, 该装置包括设置模块、 第一查找模块和第二查找模块, 其中:
设置模块, 用于设置适用于网络中不同业务的一级微码表、 二级微码 表和三级微码表。 具体地说, 设置模块根据网络中的业务, 设置适用于不 同业务的一级微码表、 二级微码表和三级微码表。 优选地, 一级微码表是 转发实例表, 二级微码表是路径表, 三级微码表是下一跳表; 转发实例表 包括出口及封装信息, 或者包括私网标签、 路径表索引和快速重路由表索 引, 或者包括本地接入链路信息以及出口及封装信息; 路径表包括三级微 码表索引和快速重路由表索引, 或者包括隧道标签、 下一跳表索引和快速 重路由表索引; 下一跳表包括路由下一跳或标签交换路径下一跳。 此外, 设置模块还用于设置用于驱动更新一级微码表的一级快速重路由表以及用
于驱动更新二级微码表的二级快速重路由表。
第一查找模块, 用于在转发表项查找过程中, 根据不同业务的转发表 结果, 查找一级微码表或二级微码表。 具体地说, 第一查找模块根据不同 业务的转发表项, 获取一级微码表索引或二级微码表索引, 并根据一级微 码表索引或二级微码表索引查找一级微码表或二级微码表, 获取一级微码 表或二级微码表的查找结果。 其中, 一级微码表的查找结果包括一级微码 表相关信息、 一级快速重路由表索引和二级微码表索引, 二级微码表的查 找结果包括二级微码表相关信息、 二级快速重路由表索引和三级微码表索 引。 此外, 根据业务查找转发表项, 未找到一级微码表索引或二级微码表 索引时, 第一查找模块组播复制该业务专用的一级微码表索引或二级微码 表索引, 查找一级微码表或二级微码表, 并获取组播 ID, 以便得到出口和 封装信息。
第二查找模块, 用于根据对一级微码表或二级微码表的查找结果, 确 定对下一级表项的查找, 直至找到出口及封装信息。 具体地说, 第二查找 模块根据不同业务, 可以根据查找一级微码表得到的一级微码表相关信息, 找到出口及封装信息; 或第二查找模块根据查找一级微码表得到的一级微 码表相关信息和二级微码表索引, 查找二级微码表, 并根据查找二级微码 表得到的二级微码表相关信息和三级微码表索引, 查找三级微码表, 找到 出口及封装信息; 或第二查找模块根据查找二级微码表得到的二级微码表 相关信息和三级微码表索引, 查找三级微码表, 找到出口及封装信息。
在存在保护, 尤其是多级保护的情况下, 第二查找模块还需要查找一 级快速重路由表和 /或查找二级快速重路由表。 其中:
第二查找模块查找一级快速重路由表, 具体为, 第二查找模块根据一 级快速重路由表索引查找一级快速重路由表, 获得主备用标志位, 确定主 用或备用的一级微码表信息、 主用或备用的二级微码表索引;
第二查找模块查找二级快速重路由表, 具体为, 第二查找模块根据二 级快速重路由表索引查找二级快速重路由表, 获得主备用标志位, 确定主 用或备用的二级微码表信息、 主用或备用的三级微码表索引。
综上所述, 本发明通过表项的层次化, 使各种业务流程尤其是保护倒 换流程模块化, 驱动更新操作简单, 并在业务存在保护尤其是多级保护时, 实现快速倒换。
尽管上文对本发明进行了详细说明, 但是本发明不限于此, 本技术领 域技术人员可以根据本发明的原理进行各种修改。 因此, 凡按照本发明原 理所作的修改, 都应当理解为落入本发明的保护范围。
Claims
1、 一种对微码表项进行层次化处理的方法, 其特征在于, 包括:
A )设置适用于网络中不同业务的一级微码表、二级微码表和三级微码 表;
B )在转发表项查找过程中, 根据不同业务的转发表结果, 查找一级微 码表或二级微码表;
C )根据对一级微码表或二级微码表的查找结果, 确定对下一级表项的 查找, 直至找到出口及封装信息。
2、 根据权利要求 1所述的方法, 其特征在于, 所述步驟 A还包括: 设置用于驱动更新一级微码表的一级快速重路由表以及用于驱动更新 二级微码表的二级快速重路由表。
3、 根据权利要求 2所述的方法, 其特征在于, 所述步驟 B具体为: 根据不同业务的转发表项, 获取一级微码表索引或二级微码表索引; 根据所述一级微码表索引或二级微码表索引查找一级微码表或二级微 码表, 获取一级微码表或二级微码表的查找结果;
其中, 所述一级微码表的查找结果包括一级微码表相关信息、 一级快 速重路由表索引和二级微码表索引, 所述二级微码表的查找结果包括二级 微码表相关信息、 二级快速重路由表索引和三级微码表索引。
4、 根据权利要求 3所述的方法, 其特征在于, 所述步驟 C具体为: 根据查找一级微码表得到的所述一级微码表相关信息, 找到出口及封 装信息。
5、 根据权利要求 3所述的方法, 其特征在于, 所述步驟 C具体为: 根据查找一级微码表得到的所述一级微码表相关信息和二级微码表索 引, 查找二级微码表;
根据查找二级微码表得到的所述二级微码表相关信息和三级微码表索 引, 查找三级微码表, 找到出口及封装信息。
6、 根据权利要求 3所述的方法, 其特征在于, 所述步驟 C具体为: 根据查找二级微码表得到的所述二级微码表相关信息和三级微码表索 引, 查找三级微码表, 找到出口及封装信息。
7、 根据权利要求 4或 5或 6所述的方法, 其特征在于, 所述步驟 C还 包括查找一级快速重路由表的步驟 C1 和 /或查找二级快速重路由表的步驟 C2;
所述步驟 C1具体为:
根据一级快速重路由表索引查找一级快速重路由表, 获得主备用标志 位, 确定主用或备用的一级微码表信息以及主用或备用的二级微码表索引; 所述步驟 C2具体为:
根据二级快速重路由表索引查找二级快速重路由表, 获得主备用标志 位, 确定主用或备用的二级微码表信息以及主用或备用的三级微码表索引。
8、根据权利要求 1所述的方法, 其特征在于, 所述方法还包括步驟 D, 具体为:
根据业务查找转发表项, 未找到一级微码表索引或二级微码表索引时, 组播复制业务专用的一级微码表索引或二级微码表索引, 查找一级微码表 或二级微码表, 并获取组播 ID, 得到出口和封装信息。
9、 根据权利要求 8所述的方法, 其特征在于, 所述一级微码表是转发 实例表, 所述二级微码表是路径表, 所述三级微码表是下一跳表;
所述转发实例表包括出口和封装信息, 或者包括私网标签、 路径表索 引和快速重路由表索引, 或者包括本地接入链路信息以及出口和封装信息; 所述路径表包括三级微码表索引和快速重路由表索引, 或者包括隧道 标签、 下一跳表索引和快速重路由表索引;
所述下一跳表包括路由下一跳或标签交换路径下一跳。
10、 一种对微码表项进行层次化处理的装置, 其特征在于, 包括: 设置模块, 用于设置适用于网络中不同业务的一级微码表、 二级微码 表和三级微码表;
第一查找模块, 用于在转发表项查找过程中, 根据不同业务的转发表 结果, 查找一级微码表或二级微码表;
第二查找模块, 用于根据对一级微码表或二级微码表的查找结果, 确 定对下一级表项的查找, 直至找到出口及封装信息。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201110068026.6A CN102201979B (zh) | 2011-03-21 | 2011-03-21 | 一种对微码表项进行层次化处理的方法和装置 |
CN201110068026.6 | 2011-03-21 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012126264A1 true WO2012126264A1 (zh) | 2012-09-27 |
Family
ID=44662381
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2011/083809 WO2012126264A1 (zh) | 2011-03-21 | 2011-12-12 | 一种对微码表项进行层次化处理的方法和装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102201979B (zh) |
WO (1) | WO2012126264A1 (zh) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102201979B (zh) * | 2011-03-21 | 2014-12-17 | 中兴通讯股份有限公司 | 一种对微码表项进行层次化处理的方法和装置 |
CN103986660B (zh) * | 2014-05-30 | 2018-01-23 | 华为技术有限公司 | 加载微码的装置以及加载微码的方法 |
US11323369B2 (en) * | 2020-05-18 | 2022-05-03 | Juniper Networks, Inc. | Transforming a multi-level hybrid hierarchical forwarding information base format |
CN112104560B (zh) * | 2020-07-27 | 2022-01-25 | 深圳市风云实业有限公司 | 一种组播路径的定制方法 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101267331A (zh) * | 2008-04-23 | 2008-09-17 | 华为技术有限公司 | 一种组播转发表查找方法和装置 |
CN101425979A (zh) * | 2008-12-10 | 2009-05-06 | 中兴通讯股份有限公司 | 一种以太环网的数据报文转发方法 |
CN101425953A (zh) * | 2008-12-09 | 2009-05-06 | 中兴通讯股份有限公司 | 一种以太环网的地址更新方法和网络节点 |
CN102201979A (zh) * | 2011-03-21 | 2011-09-28 | 中兴通讯股份有限公司 | 一种对微码表项进行层次化处理的方法和装置 |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1309221C (zh) * | 2003-06-08 | 2007-04-04 | 华为技术有限公司 | 基于多协议标签交换的用户设备双归属实现方法 |
CN101697527B (zh) * | 2009-10-26 | 2012-11-14 | 中兴通讯股份有限公司 | 网络处理器实现虚拟私有网络快速重路由的方法及装置 |
-
2011
- 2011-03-21 CN CN201110068026.6A patent/CN102201979B/zh active Active
- 2011-12-12 WO PCT/CN2011/083809 patent/WO2012126264A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101267331A (zh) * | 2008-04-23 | 2008-09-17 | 华为技术有限公司 | 一种组播转发表查找方法和装置 |
CN101425953A (zh) * | 2008-12-09 | 2009-05-06 | 中兴通讯股份有限公司 | 一种以太环网的地址更新方法和网络节点 |
CN101425979A (zh) * | 2008-12-10 | 2009-05-06 | 中兴通讯股份有限公司 | 一种以太环网的数据报文转发方法 |
CN102201979A (zh) * | 2011-03-21 | 2011-09-28 | 中兴通讯股份有限公司 | 一种对微码表项进行层次化处理的方法和装置 |
Also Published As
Publication number | Publication date |
---|---|
CN102201979A (zh) | 2011-09-28 |
CN102201979B (zh) | 2014-12-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111385206B (zh) | 报文转发的方法、网络***、相关设备及计算机存储介质 | |
CN111510379B (zh) | Evpn报文处理方法、设备及*** | |
EP3200402B1 (en) | Segment routing information obtainment method and segment routing network establishment method | |
CN102664788B (zh) | Mpls l3vpn中ce双归链路保护的方法及*** | |
WO2018166253A1 (zh) | Evpn报文处理方法、设备及*** | |
CN101141330B (zh) | 一种为lsp隧道建立bfd检测的方法、***及设备 | |
CN103685022B (zh) | 报文转发方法及服务提供商网络边缘设备 | |
EP2634975A1 (en) | Method and device for sending message | |
WO2020134139A1 (zh) | 一种业务数据的转发方法、网络设备及网络*** | |
US10110397B2 (en) | Method and device for switching tunnels and switch | |
WO2008083590A1 (fr) | Procédé et appareil de convergence rapide d'un service point à point | |
WO2015058019A1 (en) | Scalable edge node protection using ipv6 segment routing extension header | |
WO2006017982A1 (fr) | Procede de reacheminement dans le reseau multiprotocole a commutateur d'etiquettes | |
WO2011060667A1 (zh) | 一种虚拟专用局域网络中链路保护的方法及设备 | |
EP2661847A1 (en) | Pseudo wire switching method and device | |
WO2018058639A1 (zh) | 伪线负载分担的方法和设备 | |
WO2013139270A1 (zh) | 实现三层虚拟专用网络的方法、设备及*** | |
CN102474451B (zh) | 连接内层和外层mpls标签 | |
WO2012126264A1 (zh) | 一种对微码表项进行层次化处理的方法和装置 | |
WO2010045838A1 (zh) | 报文处理的方法和装置 | |
CN102724126A (zh) | 一种E-tree业务报文转发方法、装置和设备 | |
CN109698781B (zh) | 报文转发路径的管理方法和pe设备 | |
CN101232446A (zh) | 报文处理方法及装置 | |
WO2013000384A1 (zh) | 一种网络配置方法、环形网络***和一种节点 | |
CN101557334A (zh) | Mpls vpn、其vpn多实例用户边缘设备及其实现方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11861336 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11861336 Country of ref document: EP Kind code of ref document: A1 |