WO2006017982A1 - Procede de reacheminement dans le reseau multiprotocole a commutateur d'etiquettes - Google Patents

Procede de reacheminement dans le reseau multiprotocole a commutateur d'etiquettes Download PDF

Info

Publication number
WO2006017982A1
WO2006017982A1 PCT/CN2005/001264 CN2005001264W WO2006017982A1 WO 2006017982 A1 WO2006017982 A1 WO 2006017982A1 CN 2005001264 W CN2005001264 W CN 2005001264W WO 2006017982 A1 WO2006017982 A1 WO 2006017982A1
Authority
WO
WIPO (PCT)
Prior art keywords
port
label
nhlfe
fec
backup
Prior art date
Application number
PCT/CN2005/001264
Other languages
English (en)
Chinese (zh)
Inventor
Bin Li
Guofeng Xue
Yang Cao
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2006017982A1 publication Critical patent/WO2006017982A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • 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/28—Routing or path finding of packets in data switching networks using route fault recovery
    • 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/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H04L45/507—Label distribution

Definitions

  • the present invention relates to routing techniques in a Multi-Protocol Label Switching (MPLS) network, and more particularly to a method of re-routing in a Multi-Protocol Label Switching (MPLS) network.
  • MPLS Multi-Protocol Label Switching
  • Muxtiprotocol Label Switch was originally proposed to improve the forwarding speed of routers. Because MPLS is very important in traffic IP (Traffic Engeering) and virtual network (VPN) in current IP networks. Performance in two technologies. MPLS has increasingly become an important standard for expanding the scale of IP networks.
  • MPLS classifies packets, uses tags to identify packets that belong to the same forwarding type, and uses labels in the MPLS network as the sole identifier for determining forwarding operations.
  • FIG. 1 is a schematic diagram of the network structure of MPLS.
  • MPLS can be logically divided into a Label Switching Edge Router (LER) and a Label Switching Router (LSR).
  • the ingress LER provides a mapping of the Forwarding Equivalence Class (FEC) and the label
  • the egress LER provides the label removal function
  • the LSR is the core switch of the MPLS network, which provides Label Swapping and label distribution.
  • the MPLS connection is called a Label Switching Path (LSP).
  • LSP Label Switching Path
  • NHLFE Next Hop Label Forwarding Entry
  • LDP Label Distribution Protocol
  • RSVP-TE Resource reSerVe Protocol Traffic Engineer extension
  • the LDP protocol includes a set of messages and procedures for establishing an LSP between LSRs.
  • the LDP protocol directly maps the routing information of the network layer to the LSP established at the data link layer.
  • An LSP may be established between two adjacent LSRs, or may be through an entire routing area (including multiple LSRs).
  • the label is assigned to specify a label to be bound to an FEC, and distribution refers to the process of notifying upstream or downstream of this binding. Label distribution and distribution are done under the control of the LDP protocol.
  • the LSR allocates FEC-label bindings to other LSRs that explicitly propose label requests. This method is called Downstream On Demand label distribution.
  • the MPLS architecture also allows the LSR to actively allocate FEC-label bindings to other LSRs that do not request a label. This method is called Downstream Unsolicited label distribution.
  • the main difference between the downstream autonomous label advertisement and the downstream on-demand label advertisement method is which LSR is responsible for initiating the label mapping request and the label mapping notification process.
  • Tag control also has an orderly and independent 'control mode' two ways:
  • the LSR can send the label mapping message to the upstream only when the LSR receives the specific FEC-label mapping message of the next hop of the specific FEC or the LSR is the egress node of the LSP. If the LSR is neither an egress node for a particular FEC nor a label binding for a particular FEC, then the LSR must wait downstream before receiving a FEC-tag binding for a particular FEC and returning a specific FEC-label binding message upstream. A specific FEC-tag response message for the LSR.
  • each LSR can advertise the label mapping to its associated LSR at any time. For example, when working in an independent downstream on-demand label distribution control mode, the LSR can immediately respond to the upstream label request message without waiting for the label mapping message from the next hop LSR. When working in an independent downstream autonomous label distribution control mode, the LSR can advertise a specific FEC-tag mapping message to the LSR connected to it as long as the LSR is ready for label forwarding for a particular FEC. The use of independent label control allows the LSR to forward the label mapping message upstream before receiving the downstream label mapping message.
  • Label retention also has two modes: conservative label retention and free label retention: In the downstream autonomous label distribution mode, label mapping messages for all routes can be received from any neighboring LSR. When the conservative label hold mode is used, only the FEC-tag binding for data forwarding is retained; that is, the received FEC-tag binding comes from the next hop LSR of the route.
  • downstream on-demand label distribution mode the LSR only sends a label request message to the FEC next hop LSR. Since downstream on-demand label distribution is mainly used in environments with limited label resources, such as ATM switches with limited cross-connect space, downstream on-demand label distribution usually uses conservative label retention. The advantage of conservative label retention is that only tags for data forwarding are assigned and maintained. This is very important for LSRs with limited label resources, such as ATM switches.
  • One disadvantage of the conservative label hold mode is that if the route changes the next hop LSR for a particular FEC, the LSR must wait for a specific FEC-tag mapping message from the new next hop before the packet can continue to forward the label.
  • the LSR can receive label mapping messages for all routes from any neighboring LSR.
  • the LSR retains all tag mappings regardless of whether the sending LSR is the next hop of the particular FEC-label mapping it advertises.
  • the LSR may choose to send a label request message to all neighboring LSRs for all known address prefixes.
  • Downstream on-demand label distribution is typically used for devices such as ATM switches.
  • the main advantage of the free label hold mode is that the LSR can respond quickly to route changes, mainly because tag mapping already exists.
  • the main disadvantage of the free label retention method is that the currently unneeded label mapping also needs to be assigned and maintained.
  • MPLS fast reroute technology can be used to switch the LSP to the previously established local backup LSP. On, protecting the LSP is not affected by link/node failure.
  • Figure 2 is a schematic diagram of the LSP path of the MPLS fast re-routing in the prior art
  • the primary LSP path is A-B-C-D-E.
  • the path AGC is used to protect the node B and related links
  • the path BGD is used to protect the node C and related links
  • the path CFE is used to protect the node D and related links
  • the path DFE is used to link the link DE Protect. For example, when there is a fault at point C, point B will switch the network traffic to B-G-D, thus reducing data loss.
  • Bypass mode a pre-configured LSP is used to protect multiple LSPs.
  • the link fails the primary tunnel LSP is routed to the pre-configured LSP, and the pre-configured LSP reaches the next hop router for protection purposes.
  • the backup LSP needs to be explicitly specified manually.
  • the configuration workload is large and cannot be deployed on a large scale.
  • the backup LSP also has a fault. There is no protection mechanism. When it fails, fast reroute cannot be performed.
  • the backup LSP cannot pass through the protected link or node. The requirements are too strict. Sometimes, even if the destination is reachable, the backup LSP cannot be established. Summary of the invention
  • the main object of the present invention is to provide a multi-protocol label switching.
  • MPLS A method of rerouting in a network that not only enables fast rerouting after a node failure, but also saves equipment overhead.
  • a multi-protocol label switching method for rerouting in an MPLS network comprising the following steps:
  • each router in the network records FEC-tag mapping information received from all ports, and generates each label forwarding information according to each FEC-tag mapping information;
  • the label forwarding information generated by the FEC-tag mapping information received by the primary port is used as the primary label forwarding information
  • the label forwarding information generated by the FEC-tag mapping information received by the standby port is the standby label forwarding information.
  • the router generates a local label forwarding table according to the primary label forwarding information and the alternate label forwarding information.
  • the router During data transmission, if the router detects that the primary port is faulty, it forwards the information to the alternate port according to the alternate label forwarding information in the local label forwarding table.
  • the label distribution protocol running in the network works as follows: downstream autonomous label distribution, ordered label control, and free label retention.
  • the method for determining the alternate port in step B may be: manually selecting; or excluding the active port according to the principle of the shortest path, and running the link state routing protocol to automatically calculate the backup port.
  • the manual selection may be as follows: Specify an alternate port for the primary port, and all the FECs with the primary port as the next hop, and the alternate ports are designated ports.
  • the automatic calculation can be configured as follows: Configure a port to be automatically protected or configure all ports of a device to be automatically protected.
  • the process of automatically calculating the backup port may be performed after the normal route calculation is completed.
  • the router detects that the backup port is faulty, you can recalculate the backup port and use the obtained alternate label forwarding information corresponding to the new backup port to replace the spare label corresponding to the original backup port in the local label forwarding table. Forward the message.
  • the label forwarding information is: a next hop label forwarding item generated by the router according to the FEC-tag mapping information, NHLFE;
  • the primary label forwarding information is: an NHLFE generated by the router according to the FEC-tag mapping information received by the primary port;
  • the standby label forwarding information is: the standby NHLFE generated by the router according to the FEC-tag mapping information received by the backup port.
  • the local label forwarding table includes: FTN and NHLFE;
  • the FTN generation method in step C is: Cl, mapping the FEC with the primary NHLFE and the standby NHLFE to generate an FTN. If the FEC is configured to protect the port with the primary NHLFE and the port is protected, the step C includes:
  • LER traverses the FTN, finds the NHLFE next hop as the protected port entry, adds a backup NHLFE to the FTN, and backs up the next hop corresponding to the NHLFE as the determined backup port.
  • the local label forwarding table includes: an ILM and an NHLFE; If the port is configured to be protected, the method for generating the ILM in the step C is: Cl, mapping the ingress label with the primary HLFE and the standby NHLFE to generate a LIM. If the port is protected after the ILM is generated, the step C includes: C2, the LSR traverses the ILM, finds the entry whose NHLFE next hop is the protected port, adds a backup NHLFE to the ILM, and backs up the NHLFE. The next hop is the determined backup port.
  • the method for routing data to the alternate port to continue to transmit data may be: replacing the original label in the received data with the label corresponding to the standby port, and sending the data to the standby port according to the label.
  • the method for rerouting in the MPLS network of the present invention protects a specific port by selecting a backup port in an MPLS network environment running a label distribution protocol, which is applicable to The port is all LSPs of the outbound interface. When this port fails, the device can quickly switch to the backup port, and MPLS forwarding is performed through the backup port to reach the destination.
  • the method of the present invention does not need to adopt complex MPLS TE technology, and realizes distributed processing of multiple nodes, and the backup port can simultaneously implement link protection, node protection, and path protection, and does not need to separately establish backups for links, nodes, and paths.
  • LSP which saves equipment overhead.
  • the present invention since the present invention is implemented locally, it does not require the support of adjacent devices, and has good compatibility.
  • Figure 1 is a schematic diagram of a network structure of MPLS
  • FIG. 2 is a schematic diagram of an LSP path of a MPLS fast reroute in the prior art
  • FIG. 3 is a schematic structural diagram of an MPLS network according to a preferred embodiment of the present invention.
  • FIG. 4 is a schematic diagram of label distribution of the embodiment shown in FIG. 3; 5 is a schematic diagram of label forwarding of R1 in the embodiment shown in FIG. 3; FIG. 6 is a schematic diagram of label forwarding of R2 in the embodiment shown in FIG.
  • FIG. 7 is a schematic diagram of rerouting after R2 failure in the embodiment shown in FIG. 3. Mode for carrying out the invention
  • the present invention performs protection backup on a specific port by selecting a backup port in an MPLS network environment running the LDP protocol. It is applicable to all LSPs that use the port as the outbound interface. When the port is faulty, the device can quickly switch to Backup port, MPLS forwarding through the backup port to reach the destination.
  • the method for rerouting in the MPLS network of the present invention mainly includes the following steps:
  • each router in the network records FEC-tag mapping information received from all ports, and generates each label forwarding information according to each FEC-tag mapping information;
  • the label forwarding information generated by the FEC-tag mapping information received by the primary port is used as the primary label forwarding information
  • the label forwarding information generated by the FEC-tag mapping information received by the standby port is the standby label forwarding information.
  • the router generates a local label forwarding table according to the primary label forwarding information and the alternate label forwarding information.
  • the router During the data transmission process, if the router detects that the primary port is faulty, it forwards the information according to the alternate label in the local label forwarding table, and directly routes to the alternate port to continue the number of transmissions. According to.
  • FIG. 3 is a schematic structural diagram of an MPLS network according to a preferred embodiment of the present invention.
  • R1 is the ingress LER
  • R2, R3, and R4 are LSRs
  • R5 is the egress LER.
  • the LDP protocol is first run on the MPLS network, and its working mode is downstream autonomous (DU) label distribution, ordered label control, and free label maintenance.
  • DU autonomous
  • the egress LER does not need to make a label assignment request from the upstream LSR, and actively allocates the FEC-tag mapping, that is, the binding, and sends the message to the upstream. Therefore, in this embodiment, each router receives FEC-tag mapping information sent by multiple next hop ports.
  • the LSR can receive the label mapping message for the FEC from any neighboring LSR, regardless of whether the LSR that sent the message is the route corresponding to the FEC in the specific FEC-label mapping it advertises. One hop, the LSR retains all label mappings. Therefore, the router in this embodiment records all received FEC-tag mapping information.
  • FIG. 4 is a schematic diagram of label allocation of the embodiment shown in FIG. Among them, R1 arrives at R5 with two paths R1-R2-R5 and R1-R3-R4-R5, and R5 initiates a multi-label mapping message upstream. R5, R4, R3, and R2 respectively send FEC-tag mapping information to the previous hop, which contains the label allocated by itself for the previous hop.
  • R2 and R3 respectively assign R1 to R5 tags L21 and L31
  • R5 and R3 respectively assign R2 to R5 tags L52 and L32
  • R4 and R2 respectively assign R3 to R5
  • R1 generates two NHLFEs according to the FEC-tag mapping information received from R2 and R3, and R2 also generates the FEC-tag mapping information received from R5 and R3.
  • Two NHLFEs, R3 also generate two NHLFEs based on the FEC-tag mapping information received from R4 and R2, and R4 generates an NHLFEo based on the FEC-tag mapping information received from R5.
  • the router configures the protected port. For each FEC corresponding route that uses this port as the next hop, the backup port is determined. For an FEC (route), the protected port is the primary port.
  • R1-R2-R5 is the route corresponding to the FEC.
  • R1 and R2 it is determined as the primary port.
  • the NHLFE generated based on the FEC-label mapping information sent by R2 is used as the primary NHLFE, and R3 is determined.
  • the standby port the NHLFE generated according to the FEC-label mapping information sent by R3 is the standby NHLFEo.
  • R5 is determined as the primary port.
  • the NHLFE generated according to the FEC-label mapping information sent by R5 is used as the primary NHLFE, and R3 is determined as the standby.
  • Port the NHLFE generated according to the FEC-tag mapping information sent by R3 is the standby NHLFE.
  • the method of determining the alternate port is to specify one device port of the LSR as another device port, that is, the backup port of the protected port.
  • These two ports can be either physical ports or logical ports, provided that LDP runs on this port.
  • the backup port can be selected manually or automatically.
  • the manual selection method can be as follows: Specify an alternate port for the primary port, and all the FECs with the primary port as the next hop, and the backup ports are designated ports.
  • the manually selected port may not be optimal, or the configuration is heavy, so it is recommended to use the automatic calculation method to configure.
  • the automatic calculation method calculates the backup port according to the principle of the shortest path when specifying the port to be protected.
  • Automatic calculation can be implemented by the device running link state routing protocol, such as OSPF, IS-IS, and the protocol does not need to be extended.
  • the existing protocol can be used.
  • the criteria for automatic calculation are: discovery from local to destination, but not through protected
  • the shortest path of the port is to exclude the information of the protected port in the link state database, that is, to simulate the interruption of the protected port and calculate the shortest path.
  • the backup port can always be found for protection. If the calculated backup port fails later, the new backup port can be recalculated. After the new backup port is calculated, the backup label forwarding information corresponding to the obtained new backup port is used instead of the backup label forwarding information corresponding to the original backup port in the local label forwarding table.
  • the automatic calculation of the backup port is performed after the normal route calculation is completed. In this way, the calculation of the backup port is performed when the CPU is idle, and the ordinary SPF algorithm can be used to meet the requirements. It is not necessary to enhance the CPU capability or adopt a complicated algorithm, and the CPU load is low.
  • the backup port can be manually configured or automatically generated.
  • the configuration workload is reduced compared with manually specifying the backup LSP.
  • the automatic generation does not require manual explicit designation, which further reduces the The amount of work deployed.
  • R1-R5 each maintains a local label forwarding table.
  • each label forwarding table has only one FTN/LIM and one NHLFE, and the HLFE is the FEC sent according to the next hop of the FEC route. - Tag mapping information generated.
  • the next hop of a label forwarding table is a protected port, an alternate NHLFE is added to the table. The standby NHLFE is generated based on the FEC-tag mapping information sent by the backup port.
  • the local label forwarding table maintained by the ingress LER and the intermediate LSR is slightly different, and is described in detail below.
  • its label forwarding table consists of two segments, FTN and NHLFE, which is a mapping of FEC to NHLFE. If the FTN is generated after the port backup configuration, the normal next hop of the FTN is determined by the IGP shortest path to the FEC, and the primary NHLFE is generated according to the FEC-tag mapping information sent by the next hop of the FEC route. When a new FTN is created, the FEC is mapped to the primary NHLFE and the backup NHLFE to generate an FTN. Thus, the FTN, the primary NHLFE, and the alternate NHLFE form a local label forwarding table.
  • the FEC is mapped to the primary NHLFE.
  • the LER traverses the FTN table to find the entry whose NHLFE next hop is the protected port, and adds a backup NHLFE to the FTN. Backup The next hop corresponding to NHLFE is the determined backup port.
  • the FTN, the primary NHLFE, and the standby NHLFE form a local label forwarding table.
  • FIG. 5 is a schematic diagram of label forwarding of R1 in the embodiment shown in FIG.
  • the figure shows the main entries in the R1 tag forwarding table: Destination R5, Primary NHLFE R1-R2, L21, Alternate NHLFE R1-R3, L31.
  • the intermediate LSR its label forwarding table consists of two segments: ILM and NHLFE.
  • the ILM is the mapping table between the incoming label and the NHLFE. Since both inbound and outbound tags are assigned to a specific FEC, an ILM has a unique correspondence with this FEC.
  • the inbound label is mapped to the primary NHLFE and the standby NHLFE to generate UM.
  • LIM, primary NHLFE, and standby NHLFE form a local label forwarding table.
  • the ingress label is also mapped to the primary NHLFE to generate the LIM. Then the LSR traverses the LIM table to find the entry whose NHLFE next hop is the protected port, and adds a backup to the LIM. NHLFE, the next hop corresponding to the backup NHLFE is the determined backup port. In this way, LIM, primary NHLFE, and standby NHLFE form a local label forwarding table.
  • FIG. 6 is a schematic diagram of label forwarding of R2 in the embodiment shown in FIG. Shown in the figure
  • the main entries in the R2 label forwarding table are: Incoming label L21, primary NHLFE R2-R5, L52, standby NHLFE R2-R3, U2.
  • R2 is the penultimate hop.
  • the label L52 assigned by the egress LER R5 belongs to a special control label, that is, R5 does not assign a substantial label to the FEC. R2, but the next hop that the backup port R3 arrives is not the LER. On this port, the FEC needs to be assigned a label. Therefore, R3 is still required to be assigned a label when generating a backup NHLFE.
  • R1-R5 In order to reroute after a device failure, R1-R5 also maintains the working status of each port: Normal/Failed. When it is detected that a port is not working properly, such as a physical link failure or manual operation, the port is closed and its status is updated immediately. During the data forwarding process, the label forwarding table can be used to obtain the next-hop primary port of the data. If the status of the packet is invalid, the switch is switched to the backup port, and the corresponding label is set, that is, the label corresponding to the alternate port is replaced. Receive the original label in the data, and send the data to the alternate port according to the label.
  • the data arrives at the alternate port. Since the tag is assigned by itself, there must be a corresponding tag forwarding table in it, so that the data can continue to be forwarded to the destination.
  • FIG. 7 is a schematic diagram of rerouting after R2 failure in the embodiment shown in FIG. It is assumed that the LSP of R1-R5 is protected, the shortest path is R1-R2-R5, and the backup port is Rl-R3. On R3, the shortest path to R5 is R3-R2-R5 and the backup port is R3-R4. If R2 fails, both R1 and R3 sense this change and switch to the backup port respectively, thus forming a new LSP, R1-R3-R4-R5. As long as R1-R5 maintains reachability, multiple nodes work independently. It can protect any link and node failure on the path, that is, it can realize path protection.
  • the method for implementing MPLS network re-routing by port backup of the present invention can protect the LSP established by the LDP protocol and the CR-LSP established by the RSVP-TE/CR-LDP at the same time.
  • the destination of the CR-LSP is the egress LER device.
  • LDP establishes a label forwarding table to reach this LER. After the backup port is manually configured or automatically calculated, the backup next hop is added to the label forwarding table corresponding to the CR-LSP. The port is the backup port.
  • the LDP peer whose label is the backup port is allocated to the egress LER.
  • the method of the present invention can also protect IP traffic.
  • the primary next hop of the forwarding table uses IP forwarding, and the alternate next hop uses MPLS forwarding.
  • the label forwarding table has only FTN/ILM and a standby NHLFE. .
  • the method for rerouting the MPLS network of the present invention adopts a method of simulating link failure and calculating a backup port in advance, thereby eliminating the route calculation time after the fault occurs and the time for reestablishing the LSP. This speeds up the rerouting.
  • the present invention does not require the use of complex MPLS TE technology, has low equipment overhead, can be implemented locally, does not require support from adjacent devices, and has good compatibility.

Landscapes

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

Abstract

La présente invention a trait à un procédé de réacheminement dans le réseau multiprotocole à commutateur d'étiquettes comprenant (a) le fonctionnement du protocole de distribution d'étiquettes au sein du réseau, et l'enregistrement par chaque routeur dans le réseau de l'information de mappage d'étiquettes de contrôle continu reçue en provenance de tous les ports, et la génération de l'information de réacheminement d'étiquettes respectives en fonction de l'information de mappage d'étiquettes de contrôle continu; (B) la configuration par le routeur du port protégé, et la spécification du port auxiliaire pour la route correspondant à chaque contrôle continu qui considère ce port comme le prochain bond; pour la route correspondant à un parmi les contrôles continus, le port protégé est le port principal; (C) la génération par le routeur de la table locale de réacheminement d'étiquettes en fonction de l'information de réacheminement d'étiquettes principale et de l'information de réacheminement d'étiquettes auxiliaire; (D) lors de la transmission des données, si le routeur détecte la faute du port principal, les données sont transmise directement au port auxiliaire pour poursuivre la transmission de données selon l'information de réacheminement auxiliaire dans la table locale de réacheminement d'étiquettes. L'utilisation de l'invention permet de réduire le temps de réacheminement, et comporte peu de frais en matière de dispositifs, et l'invention est également capable de mise en oeuvre locale avec une grande compatibilité.
PCT/CN2005/001264 2004-08-17 2005-08-15 Procede de reacheminement dans le reseau multiprotocole a commutateur d'etiquettes WO2006017982A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200410058216.X 2004-08-17
CNB200410058216XA CN100518135C (zh) 2004-08-17 2004-08-17 一种多协议标签交换网络中重新路由的方法

Publications (1)

Publication Number Publication Date
WO2006017982A1 true WO2006017982A1 (fr) 2006-02-23

Family

ID=35907225

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001264 WO2006017982A1 (fr) 2004-08-17 2005-08-15 Procede de reacheminement dans le reseau multiprotocole a commutateur d'etiquettes

Country Status (2)

Country Link
CN (1) CN100518135C (fr)
WO (1) WO2006017982A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102244602A (zh) * 2010-05-11 2011-11-16 华为技术有限公司 在协议无关组播双重加入下转发数据的方法、装置及系统
US8565098B2 (en) 2007-10-24 2013-10-22 Huawei Technologies Co., Ltd. Method, device, and system for traffic switching in multi-protocol label switching traffic engineering
WO2016014419A1 (fr) 2014-07-21 2016-01-28 Glia, Llc Méthode de traitement de troubles cognitifs ou émotionnels associés à la radiothérapie ou la chimiothérapie au moyen de cannabinoïdes
CN114039905A (zh) * 2021-11-30 2022-02-11 烽火通信科技股份有限公司 节约保护资源的方法及装置

Families Citing this family (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100433721C (zh) * 2006-01-23 2008-11-12 杭州华三通信技术有限公司 一种处理标签绑定的方法
CN100561978C (zh) 2006-04-26 2009-11-18 华为技术有限公司 一种策略路由装置和方法
CN100568831C (zh) * 2006-04-26 2009-12-09 华为技术有限公司 一种提高网络可靠性的方法及系统
CN100546284C (zh) * 2006-09-13 2009-09-30 华为技术有限公司 标签交换路径保护方法及其系统
CN101051884B (zh) * 2007-05-09 2010-10-13 杭州华三通信技术有限公司 一种实现接口备份的方法及装置
CN100583827C (zh) * 2007-05-17 2010-01-20 华为技术有限公司 一种多协议标签交换网络流量切换的方法及设备
CN101051885B (zh) * 2007-05-17 2010-06-02 中兴通讯股份有限公司 接入设备上联业务保护方法及装置
CN101094175B (zh) * 2007-06-14 2011-06-01 华为技术有限公司 一种组播流量保护方法、装置及系统
US8457141B2 (en) * 2007-09-28 2013-06-04 Telefonaktiebolaget Lm Ericsson (Publ) Telecommunication network
CN101163100B (zh) 2007-11-12 2011-08-24 中兴通讯股份有限公司 一种隧道映射的方法
CN101577661B (zh) * 2008-05-09 2013-09-11 华为技术有限公司 一种路径切换的方法和设备
CN101616062B (zh) * 2008-06-26 2012-07-04 中兴通讯股份有限公司 Ip转发实现方法
WO2010145070A1 (fr) * 2009-06-15 2010-12-23 华为技术有限公司 Procédé, dispositif et système d'établissement d'un chemin commuté par étiquette de sauvegarde
CN102437955B (zh) * 2011-12-16 2016-05-04 杭州华三通信技术有限公司 一种lsp保护方法和设备
CN102594712A (zh) * 2012-03-28 2012-07-18 北京星网锐捷网络技术有限公司 一种标签交换路径的确定方法以及装置
CN105743784B (zh) * 2014-12-08 2020-03-17 中兴通讯股份有限公司 一种部署大容量业务时的切换控制方法及装置
CN105991434B (zh) * 2015-02-05 2019-12-06 华为技术有限公司 一种环网中mpls报文转发的方法及网络节点
CN106161246B (zh) * 2016-06-15 2019-09-06 新华三技术有限公司 备用路由的实现方法及装置
CN106385362B (zh) * 2016-08-30 2019-08-27 迈普通信技术股份有限公司 一种非负载均衡路由切换方法及装置
CN107864091B (zh) * 2017-10-31 2020-04-03 新华三技术有限公司 链路故障的处理方法及装置
CN108400936B (zh) * 2018-03-05 2020-09-22 大连大学 基于mpls的空间信息网络路由方法
CN110932895B (zh) * 2019-11-26 2022-07-15 中国联合网络通信集团有限公司 一种网络切片的报文转发方法和装置
CN112398730A (zh) * 2020-10-28 2021-02-23 上海欣诺通信技术股份有限公司 数据中心网络中的报文转发方法、装置、设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030028818A1 (en) * 2001-07-12 2003-02-06 Nec Corporation Communication connection bypass method capable of minimizing traffic loss when failure occurs
CN1433642A (zh) * 1999-12-07 2003-07-30 艾利森电话股份有限公司 将7号信令系统网与使用多协议标记交换的网络集成
US20030212927A1 (en) * 2002-05-08 2003-11-13 Navar Venu Gopal Fault-protection mechanism for protecting multi-protocol-label switching (MPLS) capability within a distributed processor router operating in an MPLS network
CN1496629A (zh) * 2002-01-17 2004-05-12 ƽ 用于快速重路由备份通道的负载平衡

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1433642A (zh) * 1999-12-07 2003-07-30 艾利森电话股份有限公司 将7号信令系统网与使用多协议标记交换的网络集成
US20030028818A1 (en) * 2001-07-12 2003-02-06 Nec Corporation Communication connection bypass method capable of minimizing traffic loss when failure occurs
CN1496629A (zh) * 2002-01-17 2004-05-12 ƽ 用于快速重路由备份通道的负载平衡
US20030212927A1 (en) * 2002-05-08 2003-11-13 Navar Venu Gopal Fault-protection mechanism for protecting multi-protocol-label switching (MPLS) capability within a distributed processor router operating in an MPLS network

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8565098B2 (en) 2007-10-24 2013-10-22 Huawei Technologies Co., Ltd. Method, device, and system for traffic switching in multi-protocol label switching traffic engineering
CN102244602A (zh) * 2010-05-11 2011-11-16 华为技术有限公司 在协议无关组播双重加入下转发数据的方法、装置及系统
WO2011140813A1 (fr) * 2010-05-11 2011-11-17 华为技术有限公司 Procédé, dispositif et système d'acheminement de données sous jonction double de diffusion générale indépendante du protocole (pim)
US9313037B2 (en) 2010-05-11 2016-04-12 Huawei Technologies Co., Ltd. Method, apparatus and system for forwarding data under protocol independent multicast dual join
WO2016014419A1 (fr) 2014-07-21 2016-01-28 Glia, Llc Méthode de traitement de troubles cognitifs ou émotionnels associés à la radiothérapie ou la chimiothérapie au moyen de cannabinoïdes
CN114039905A (zh) * 2021-11-30 2022-02-11 烽火通信科技股份有限公司 节约保护资源的方法及装置

Also Published As

Publication number Publication date
CN100518135C (zh) 2009-07-22
CN1738288A (zh) 2006-02-22

Similar Documents

Publication Publication Date Title
WO2006017982A1 (fr) Procede de reacheminement dans le reseau multiprotocole a commutateur d'etiquettes
EP2878100B1 (fr) Système, procédé et appareil pour signaler et répondre à l'échec de l'expansion de ero dans le domaine inter lsp
EP3041178B1 (fr) Convergence rapide sur une panne de liaison dans des réseaux privés virtuels ethernet à plusieurs connexions
CN102664788B (zh) Mpls l3vpn中ce双归链路保护的方法及系统
CN101741709B (zh) 建立标签交换路径的方法、系统及网络节点
US9781032B1 (en) MPLS label usage in ethernet virtual private networks
US9077561B2 (en) OAM label switched path for fast reroute of protected label switched paths
JP3790655B2 (ja) ラベルスイッチネットワークシステム
US8055791B2 (en) Protecting connection traffic using filters
KR101643911B1 (ko) 원격통신 네트워크에서 링크―다이버스 트래픽 경로들을 확립하기 위한 방법 및 관련 장치
US9571387B1 (en) Forwarding using maximally redundant trees
US9270426B1 (en) Constrained maximally redundant trees for point-to-multipoint LSPs
WO2007016834A1 (fr) Procede rapide de convergence de services de point a point et dispositif associe cote fournisseur de services
US9246838B1 (en) Label switched path setup using fast reroute bypass tunnel
JP5420547B2 (ja) Ｍｐｌｓ−ｆｒｒ帯域幅最適化のためのｒｓｖｐ−ｔｅ強化
WO2008083590A1 (fr) Procédé et appareil de convergence rapide d'un service point à point
WO2011060667A1 (fr) Procédé et dispositif de protection de liaison dans un réseau privé virtuel local
WO2012167516A1 (fr) Procédé, appareil et système de production d'une table de transmission d'étiquette dans une topologie en anneaux
WO2012079375A1 (fr) Procédé et système de protection de liaison dans un réseau privé virtuel
WO2011076029A1 (fr) Procédé et dispositif pour mettre en oeuvre un réacheminement rapide
WO2013029438A1 (fr) Procédé de protection d'interface ethernet et dispositif côté réseau
WO2011140890A1 (fr) Procédé et dispositif de mise en œuvre d'un réacheminement rapide
WO2007069256A2 (fr) Partage de ressources entre des tunnels de réseau
CN101483491A (zh) 共享保护环及其组播源路由保护方法和节点
JP3882626B2 (ja) 二重リングネットワークにおける折り返しプロテクションのためのシグナリング方式

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase