WO2016165299A1 - 节点设备及其建立标签转发表的方法 - Google Patents

节点设备及其建立标签转发表的方法 Download PDF

Info

Publication number
WO2016165299A1
WO2016165299A1 PCT/CN2015/092225 CN2015092225W WO2016165299A1 WO 2016165299 A1 WO2016165299 A1 WO 2016165299A1 CN 2015092225 W CN2015092225 W CN 2015092225W WO 2016165299 A1 WO2016165299 A1 WO 2016165299A1
Authority
WO
WIPO (PCT)
Prior art keywords
label
fec
node device
configuration
inbound
Prior art date
Application number
PCT/CN2015/092225
Other languages
English (en)
French (fr)
Inventor
宋兵
Original Assignee
中兴通讯股份有限公司
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 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2016165299A1 publication Critical patent/WO2016165299A1/zh

Links

Images

Definitions

  • the present invention relates to the field of label switching technologies, and in particular, to a node device and a method for establishing a label forwarding table.
  • MPLS Multi-Protocol Label Switching
  • LSP Label Switch Path
  • An LSP is classified into two types: a static LSP and a dynamic LSP.
  • the dynamic LSP is established by the downstream node device and the upstream node device through a dynamic LDP (Label Distribution Protocol).
  • a static LSP is set up by configuring an LSR (Label Switch Router) along the LSP to ensure that the LSP meets the MPLS forwarding characteristics.
  • Static LSPs and dynamic LSPs are widely used in MPLS-L2VPN and MPLS-L3VPN networks.
  • each node device in the prior art is established by dynamic LDP or by static configuration.
  • the label forwarding table of the node device may be configured such that the inbound label is suitable for dynamic LDP, and the other part of the label is suitable for static configuration. That is, the existing label forwarding table cannot be configured to establish a label forwarding table for the network application scenario in which the part of the label forwarding table is suitable for dynamic configuration, and the other part of the outgoing and incoming labels are suitable for static configuration.
  • the main purpose of the present invention is to solve the problem of establishing a label forwarding table in a network application scenario in which a node device in a label forwarding table is suitable for dynamic configuration, and another node is in a static configuration. problem.
  • the present invention provides a method for a node device to establish a label forwarding table, and the method for the node device to establish a label forwarding table includes the following steps:
  • the node device is bound to the corresponding FEC (Forwarding Equivalence Class) according to the network application scenario in which it is located;
  • the configuration mode is: static configuration mode and/or Or dynamically configured
  • the label includes: an inbound label and an outgoing label
  • the step of determining a configuration manner of a label to be configured for the FEC according to a network application scenario in which the node device is located, and configuring a corresponding label for the FEC according to the configuration manner includes:
  • each label type to be configured to the FEC Determining, by the node device, each label type to be configured to the FEC and a required configuration manner of each label according to the network application scenario in which the node device is located;
  • the configuration manner is that the FEC is allocated a corresponding second outgoing and incoming label, and the first incoming label and the second outgoing label are configured as labels for the FEC.
  • the determining, by the node device, each label type to be configured to the FEC and the required configuration manner of each label according to the network application scenario in which the node device is located further includes:
  • the first outbound and inbound labels are configured for the FEC by static configuration, and The FEC is allocated a corresponding second ingress label by using a dynamic configuration mode, and the first outgoing label, the second incoming label, and the second incoming label are used as labels configured to the FEC.
  • the determining, by the node device, each label type to be configured to the FEC and the required configuration manner of each label according to the network application scenario in which the node device is located further includes:
  • the first outgoing and incoming labels are configured for the FEC in a static configuration manner, and the first outgoing and incoming labels are configured as configurations.
  • the determining, by the node device, each label type to be configured to the FEC and the required configuration manner of each label according to the network application scenario in which the node device is located further includes:
  • the FEC When there is only a second outbound and inbound label that needs to be allocated by the dynamic configuration mode, the FEC is allocated a corresponding second outgoing and incoming label by using a dynamic configuration manner, and the second outgoing and incoming labels are configured as a configuration.
  • the label of the FEC is allocated a corresponding second outgoing and incoming label by using a dynamic configuration manner, and the second outgoing and incoming labels are configured as a configuration.
  • the present invention further provides a node device, where the node device includes:
  • the binding module is configured to bind the corresponding forwarding equivalence class FEC according to the network application scenario where the node device is located;
  • the configuration module is configured to determine a configuration mode to be configured for the label of the FEC according to the network application scenario in which the node device is located, and configure a corresponding label for the FEC according to the configuration manner;
  • the configuration manner is: Static configuration mode and/or dynamic configuration mode;
  • the label includes: an inbound label and an outgoing label;
  • the configuration module includes:
  • a determining unit configured to determine, according to a network application scenario in which the node device is located, each tag type to be configured to the FEC and a required configuration manner of each tag;
  • the first configuration unit is configured to have a first ingress label that needs to be configured through static configuration, and needs to exist
  • the second inbound and outbound labels are allocated in the dynamic configuration mode, and the corresponding first inbound label is configured for the FEC in a static configuration manner, and the corresponding second inbound and outbound labels are allocated to the FEC in a dynamic configuration manner, and The first ingress label and the second inbound and outbound label are used as labels assigned to the FEC.
  • the configuration module further includes:
  • the second configuration unit is configured to: when there is a first inbound and outbound label that needs to be configured through the static configuration mode, and a second inbound label that needs to be allocated through the dynamic configuration manner, configure the corresponding part for the FEC by using a static configuration manner. And outputting a corresponding second ingress label to the FEC by using a dynamic configuration manner, and using the first outgoing label, the second incoming label, and the second incoming label as labels configured to the FEC.
  • the configuration module further includes:
  • the third configuration unit is further configured to configure a first outbound and inbound label for the FEC in a static configuration manner, and configure the first outbound and inbound labels in the static configuration manner.
  • the outgoing and incoming labels serve as labels for the FEC.
  • the configuration module further includes:
  • the fourth configuration unit is configured to allocate a corresponding second outgoing and incoming label to the FEC by using a dynamically configured manner, and the second outgoing The inbound label acts as a label assigned to the FEC.
  • the node device provided by the present invention and the method for establishing the label forwarding table are configured to bind the corresponding FEC according to the network application scenario in which the node device is located; and determine the node device for the FEC according to the network application scenario in which the node device is located.
  • the configuration of the label to be configured is as follows: The configuration mode is selected according to the determination result, and the node device configures a corresponding label for the FEC; the configuration mode is: static configuration mode and/or dynamic configuration mode; the label includes: The label forwarding table is set up according to the manner in which the label forwarding table of the node device is established according to the label configured for the FEC, and the label forwarding table can be established for the network application scenario where the node device that is configured to be statically and/or dynamically configured to be in and out of the label is configured.
  • the network application scenario in which the node device is located is extended, and the flexibility of the label forwarding table deployed in the network is improved.
  • FIG. 1 is a schematic flowchart of a method for establishing a label forwarding table by a node device according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of a refinement process of step S20 in FIG. 1;
  • FIG. 3 is a schematic diagram of functional modules of a node device according to the present invention.
  • FIG. 4 is a schematic diagram of a specific refinement function module of the configuration module in FIG. 3;
  • FIG. 5 is a schematic diagram of another specific refinement function module of the configuration module in FIG. 3;
  • FIG. 5 is a schematic diagram of another specific refinement function module of the configuration module in FIG. 3;
  • FIG. 6 is a schematic diagram of another specific refinement function module of the configuration module in FIG. 3;
  • FIG. 7 is a schematic diagram of another specific refinement function module of the configuration module in FIG. 3;
  • FIG. 8 is a schematic diagram of a network application scenario of a node device according to the present invention.
  • FIG. 9 is a schematic diagram of another network application scenario of a node device according to the present invention.
  • FIG. 10 is a schematic diagram of another network application scenario of a node device according to the present invention.
  • FIG. 11 is a schematic diagram of another network application scenario of a node device according to the present invention.
  • FIG. 1 is a schematic flowchart diagram of a method for establishing a label forwarding table by a node device according to an embodiment of the present invention.
  • the method for the node device to establish a label forwarding table includes:
  • step S10 the node device binds the corresponding FEC (Forwarding Equivalence Class) according to the network application scenario.
  • FEC Forming Equivalence Class
  • the configuration mode of the label to be configured for the FEC is determined according to the network application scenario in which the node device is located, and the corresponding label is configured for the FEC according to the configuration mode.
  • the configuration mode is: a static configuration mode and/or a dynamic configuration mode;
  • the label includes: an inbound label and an outgoing label.
  • FIG. 2 is a schematic diagram of the refinement process of step S20 in FIG.
  • the step S20 specifically includes:
  • step S21 the node device determines each label type to be configured for the FEC and the required configuration manner of each label according to the network application scenario in which the node device is located.
  • step S22 when there is only a first outgoing and incoming label that needs to be configured in the static configuration mode, the corresponding first outgoing and incoming labels are configured for the FEC in a static configuration manner, and the first outgoing and incoming labels are configured as FEC label.
  • the static LSP instance is configured in the static configuration mode.
  • the static LSP instance configuration command format is as follows:
  • the mpls static-lsp ⁇ lsp-name> command is used to configure the static LSP instance name.
  • the lsp-name argument is the static LSP instance name.
  • the bind ipv4 ⁇ prefix> ⁇ mask>[force-advertise] command is used to bind the static LSP instance to the corresponding FEC.
  • the prefix is the address prefix and the mask is the address mask.
  • -advertise is mandatory after the inbound label configured in the static LSP instance is bound to the FEC.
  • -null ⁇ is a configuration command for configuring an inbound label for a static LSP instance.
  • In-label is an ordinary type inbound label
  • explicit-null is an explicit null label
  • implanticit-null is an implicit null label.
  • step S23 when there is a first inbound label that needs to be configured in the static configuration mode, and a second inbound and outbound label that needs to be allocated through the dynamic configuration mode, the corresponding first inbound label is configured for the FEC through the static configuration mode, and the The dynamic configuration mode allocates a corresponding second outgoing and incoming label to the FEC, and uses the first incoming label and the second outgoing label as the label configured for the FEC.
  • the node device when there is a first inbound label that needs to be configured in the static configuration mode, and a second inbound and outbound label that needs to be allocated through the dynamic configuration mode, the node device configures the corresponding FEC for the FEC through the static configuration mode.
  • the specific process of the first inbound label is basically the same as that in step S22. The difference is that there is no mandatory effective command in the configuration command of the outgoing and incoming labels.
  • the node device can be configured with multiple inbound labels for the same FEC, and the node device can only allocate one label for the same FEC in the same FEC. Therefore, in this embodiment, the node device allocates corresponding information for the same FEC in the same direction.
  • the second outgoing label in the static LSP instance, the first outgoing label of the node device configured for the same FEC is inactive, and the first incoming label and the second incoming label are different, and the first outgoing label is discarded.
  • the first ingress label and the second inbound and inbound label are reserved as labels configured by the node device for the FEC.
  • step S24 when there is a first inbound and outbound label that needs to be configured in the static configuration mode, and a second inbound label that needs to be allocated through the dynamic configuration mode, the corresponding first inbound and outbound labels are configured for the FEC through the static configuration mode. And assigning, by the dynamic configuration manner, the corresponding second ingress label to the FEC, and using the first outgoing label, the incoming label, and the second incoming label as labels configured to the FEC.
  • the node device when there is a first inbound and outbound label that needs to be configured through the static configuration, and a second inbound label that needs to be allocated through the dynamic configuration, the node device configures the corresponding FEC for the FEC through the static configuration.
  • the specific process of the first outgoing and incoming labels is basically the same as that of step S22. The difference is that there is no mandatory effective command in the configuration command of the statically configured outgoing and incoming labels.
  • the statically configured outgoing and incoming labels are not mandatory, the first outgoing label, the second incoming label, and the second incoming label may be used as the section because the second outgoing label is not allocated by dynamic configuration.
  • the label that the point device configures for the FEC is not mandatory
  • Step S25 When there is only a second outgoing and incoming label that needs to be allocated through the dynamic configuration mode, the corresponding second outgoing and incoming labels are allocated to the FEC through dynamic configuration, and the second outgoing and incoming labels are configured as FECs. label.
  • the manner in which the node device allocates the inbound and outbound for the bound FEC in the manner of the node device in the dynamic configuration mode is the prior art, and the description is not provided herein.
  • Step S30 Establish a label forwarding table of the node device according to the label configured for the FEC.
  • the step S30 includes: the outbound label and/or the inbound label allocated to the FEC by the node device in a dynamically configured manner, and the outgoing label and/or input configured by the node device for the FEC in a manner of static configuration.
  • the label is integrated with the label forwarding table of the FEC that is bound to the node device, so that the node device forwards the packet according to the label forwarding table after receiving the packet.
  • the method further includes the following steps: the upstream node device that is reported to the ingress label configured by the node device for the FEC, so that the upstream node device dynamically allocates the label.
  • the node device In the method for establishing the label forwarding table by the node device, the node device binds the corresponding FEC according to the network application scenario in which the node device is located; and determines, according to the network application scenario where the node device is located, the node device to be configured for the FEC.
  • the configuration of the label is as follows: the required configuration mode is selected according to the determination result, and the node device configures a corresponding label for the FEC; the configuration manner is: static configuration mode and/or dynamic configuration mode;
  • the label forwarding table can be established according to the manner in which the label forwarding table of the node device is established according to the label configured for the FEC, and the label forwarding table can be established for the network application scenario where the node device that is configured to be statically and/or dynamically configured to enter and enter the label, and the node is expanded.
  • the network application scenario in which the device is located improves the flexibility of the label forwarding table deployed in the network.
  • FIG. 3 is a schematic diagram of functional modules of a node device according to the present invention.
  • the node device 100 includes a binding module 110, a configuration module 120, and an establishing module 130.
  • the binding module 110 is configured to bind the corresponding FEC according to the network application scenario in which the node device is located.
  • the configuration module 120 is configured to determine, according to the network application scenario in which the node device is located, a configuration manner required to be configured for the label of the FEC, and configure a corresponding label for the FEC according to the configuration manner;
  • the method is: static configuration mode and/or dynamic configuration mode; the label includes: an inbound label and an outgoing label.
  • the establishing module 130 is configured to establish a label forwarding table of the node device according to the label configured to the FEC.
  • the establishing module 130 in the embodiment specifically integrates the outgoing label and/or the incoming label allocated by the node device into the FEC in a dynamically configured manner, and the outgoing label and/or the incoming label configured for the FEC through the static configuration manner, and is integrated and formed.
  • the label forwarding table of the FEC bound to the node device, so that the node device forwards the packet according to the label forwarding table after receiving the packet.
  • the method further includes the following steps: the node device is an upstream node device that is reported by the FEC-configured inbound label, so that the upstream node device dynamically allocates the label.
  • FIG. 4 is a schematic diagram of a specific refinement function module of the configuration module in FIG.
  • the configuration module 120 includes: a determining unit 121 and a first configuration unit.
  • the determining unit 121 is configured to determine, according to the network application scenario in which the node device is located, each tag type to be configured to the FEC and a required configuration manner of each tag.
  • the first configuration unit 122 is configured to: when there is a first inbound label that needs to be configured in a static configuration manner, and a second inbound and outbound label that needs to be allocated through a dynamic configuration manner, configure the corresponding FEC in a static configuration manner.
  • the first inbound label is configured, and the corresponding second inbound and outbound labels are allocated to the FEC by dynamic configuration, and the first inbound label and the second inbound and inbound label are used as labels configured to the FEC.
  • the first configuration unit 121 adopts a static configuration mode to configure the corresponding FEC.
  • the specific process of the first inbound label is the same as the method of configuring the first inbound and inbound labels in the third configuration unit 124 described below. The difference is that there is no mandatory command in the configuration command of the inbound and outbound labels of the static configuration. .
  • a plurality of inbound labels can be configured for the same FEC, and only one outbound label can be configured for the same outgoing direction of the same FEC.
  • the node device allocates corresponding second outgoing labels to the same outgoing direction of the same FEC through dynamic configuration.
  • the first outgoing label and the inbound label configured for the same FEC in the static LSP instance are not mandatory. If the first incoming label and the second incoming label are different, the first outgoing label is discarded, and the first incoming label is retained.
  • the tag and the second outgoing tag are the tags configured by the node device for the FEC.
  • FIG. 5 is a schematic diagram of another specific refinement function module of the configuration module in FIG.
  • the configuration module 120 further includes a second configuration unit 123.
  • the second configuration unit 123 is configured to configure the FEC in a static configuration manner when there is a first inbound and outbound label that needs to be configured in a static configuration manner and a second inbound label that needs to be allocated through a dynamic configuration manner.
  • Corresponding first inbound and outbound labels, and a corresponding second inbound label is allocated to the FEC by dynamic configuration, and the first outgoing inbound label and the second inbound label are used as labels configured to the FEC.
  • the node device when there is a first inbound and outbound label that needs to be configured in a static configuration manner, and a second inbound label that needs to be allocated through a dynamic configuration manner, the node device adopts a static configuration manner by using the second configuration unit 12
  • the specific process of configuring the first outgoing and incoming labels for the FEC is the same as the configuration of the first outgoing and incoming labels by the third configuration unit 124 described below, except that the statically configured outgoing and incoming labels are configured. There is no mandatory order in the command. In this example, although the statically configured outgoing and incoming labels are not mandatory, the first outgoing label, the second incoming label, and the second incoming label may be used as node devices because the second outgoing label is not dynamically configured.
  • the label of the FEC configuration is the same as the configuration of the first outgoing and incoming labels by the third configuration unit 124 described below, except that the statically configured outgoing and incoming labels are configured. There is no mandatory order in the command. In this example, although the
  • FIG. 6 is a schematic diagram of another specific refinement function module of the configuration module in FIG.
  • the configuration module 120 further includes a third configuration unit 124.
  • the third configuration unit 124 is configured to configure a corresponding first inbound and outbound label for the FEC in a static configuration manner, and configure the first outbound and inbound labels in the static configuration mode.
  • the outgoing and incoming labels serve as labels for the FEC.
  • the third configuration unit 124 configures a static LSP instance in a static configuration mode.
  • the static LSP instance configuration command format is:
  • the mpls static-lsp ⁇ lsp-name> command is used to configure the static LSP instance name.
  • the lsp-name argument is the static LSP instance name.
  • the bind ipv4 ⁇ prefix> ⁇ mask>[force-advertise] command is used to bind the static LSP instance to the corresponding FEC.
  • the prefix is the address prefix and the mask is the address mask.
  • -advertise is mandatory after the inbound label configured in the static LSP instance is bound to the FEC.
  • -null ⁇ is a configuration command for configuring an inbound label for a static LSP instance.
  • In-label is an ordinary type inbound label
  • explicit-null is an explicit null label
  • implanticit-null is an implicit null label.
  • FIG. 7 is a schematic diagram of another specific refinement function module of the configuration module in FIG.
  • the configuration module 120 further includes a fourth configuration unit 125.
  • the fourth configuration unit 125 is configured to allocate a corresponding second outgoing and incoming label to the FEC by using a dynamically configured manner when there is only a second outgoing and incoming label that needs to be allocated by using a dynamic configuration manner, and the The second outgoing and incoming labels serve as labels for the FEC.
  • the manner in which the node device allocates the inbound and outbound for the bound FEC in the manner that the node device is dynamically configured is the prior art, and the description is not further described herein.
  • the node device provided by the present invention binds the corresponding FEC according to the network application scenario in which the node device is located; and determines the configuration of the label to be configured by the node device for the FEC according to the network application scenario in which the node device is located.
  • the node device configures a corresponding label for the FEC according to the determination result; the configuration manner is: a static configuration mode and/or a dynamic configuration mode; the label includes: an inbound label and an outgoing label;
  • the method for establishing a label forwarding table of the node device by using the label configured by the FEC can establish a label forwarding table for the network application scenario where the node device that is configured to be statically and/or dynamically configured to enter and receive the label, and expand the node forwarding table.
  • the network application scenario improves the flexibility of the label forwarding table deployed in the network.
  • the node device of the present invention and the method for establishing the label forwarding table thereof are further described in detail below through four network application scenario examples.
  • FIG. 8 is a schematic diagram of a network application scenario of a node device according to the present invention.
  • the downstream node device LSR3 of the node device LSR2 in FIG. 8 configures the label 1 and the ingress label 2 for the FEC in a static configuration manner; the node device LSR2 configures the local static outgoing label 2 according to the inbound label 2.
  • the node device LSR2 configures the inbound label 3 for the FEC in the static configuration mode, and enables the ingress to be valid.
  • the ingress label 3 is reported to the node device LSR1.
  • the node device LSR1 matches the label 3 to the FEC in a dynamic manner according to the ingress label 3 reported by the node device LSR2.
  • the node device LSR2 establishes its own label forwarding table according to the outgoing label 2 and the incoming label 3 configured for the FEC.
  • FIG. 9 is a schematic diagram of another network application scenario of a node device according to the present invention.
  • the downstream node device LSR3 of the node device LSR2 in FIG. 9 allocates the label 1 and the inbound label 2 to the bound FEC in a dynamically allocated manner, and reports the incoming label 2 to the upstream node device LSR2.
  • the node device LSR2 allocates the label 2 to the bound FEC according to the inbound label 2 reported by the node device LSR3, and configures the label 3 for the bound FEC in a static configuration manner.
  • the node device LSR1 configures the label 3 and the inbound label 4 for the bound FEC in a static configuration manner.
  • the node device LSR2 establishes its own label forwarding table according to the outgoing label 2 and the incoming label 3 configured for the FEC.
  • FIG. 10 is a schematic diagram of another network application scenario of a node device according to the present invention.
  • the node device LSR3 configures the inbound label for the bound FEC in the static configuration mode, and assigns the inbound label 2 to the FEC in the dynamic configuration mode, and reports the inbound label 2 to the upstream node device LSR1, that is, static in the node device LSR3.
  • the configured inbound label 1 and the dynamically assigned inbound label 2 take effect at the same time.
  • the downstream node device LSR4 of the node device LSR3 configures the inbound label 3 for the bound FEC in the static configuration mode, or assigns the inbound label 4 to the bound FEC in the dynamic configuration mode, and reports the inbound label 4 to the upstream device LSR3.
  • the same outgoing direction for the bound FEC is configured by the local static outgoing label 3 according to the inbound label 3 statically configured by the downstream node device LSR4, or dynamically according to the incoming label 4 reported by the downstream node device LSR4.
  • the node device LSR1 dynamically allocates the label 2 according to the incoming label 2 reported by the downstream node device LSR3.
  • the node device LSR2 configures the local static outgoing label 1 according to the inbound label 1 statically configured by the downstream node device LSR3.
  • the node device LSR3 establishes its own label forwarding table according to the inbound labels 1 and 2 and the outgoing label 3 configured for the bound FEC, or establishes its own label forwarding for the inbound labels 1 and 2 of the bound FEC. Published.
  • the upstream of the node device LSR3 includes two node devices LSR1 and LSR2, and one downstream node device LSR4. Therefore, two inbound labels and one outgoing label need to be configured for the bound FEC on the node device LSR3.
  • an upstream node device is configured to deploy a static or dynamic label forwarding table to extend the label forwarding table corresponding to the bound FEC.
  • the node device LSR3 is in the network application scenario, although the label forwarding table corresponding to the FEC is extended, but the forwarding traffic of the original label forwarding table is not affected.
  • FIG. 11 is a schematic diagram of another network application scenario of a node device according to the present invention.
  • the downstream node device LSR3 of the node device LSR2 configures the inbound label 1 for the bound FEC in the dynamic configuration mode, and reports the inbound label 1 to the upstream node device LSR2.
  • the downstream node device LSR4 of the node device LSR2 configures the label 2 into the bound FEC in a static manner.
  • the node device LSR2 dynamically allocates the label 1 to the FEC node device LSR3 that is bound by the downstream device LSR3, and the ingress label 2 that is statically configured by the downstream device LSR4 is the node device of the FEC that is bound by itself.
  • the LSR4 is configured to statically configure the label 2; the inbound label 3 is configured in a static configuration manner, or the label 4 is assigned through dynamic configuration, and the label is rotated according to the label 1 and 2, and the label 3 and 4 are set. Published.
  • the labels 1 and 2 are formed on the node device LSR2 to form a load sharing or FRR relationship.
  • the node device described above in the present invention is a label switching router device.
  • the node device binds the corresponding FEC according to the network application scenario in which the node device is located; and determines, according to the network application scenario where the node device is located, the label device to be configured by the node device for the FEC.
  • the configuration mode is as follows: the required configuration mode is selected according to the determination result, and the node device configures a corresponding label for the FEC; the configuration mode is: static configuration mode and/or dynamic configuration mode; the label includes: an inbound label and an outbound label.
  • the method of establishing a label forwarding table of the node device according to the label configured for the FEC can establish a label forwarding table for a network application scenario in which the node device that is configured to be statically and/or dynamically configured to enter and enter the label, and expand the node device.
  • the network application scenario improves the flexibility of the label forwarding table deployed in the network.

Abstract

本发明公开了一种节点设备建立标签转发表的方法，方法为：节点设备根据自身所处网络应用场景绑定相应的转发等价类FEC（S10）；根据节点设备所处的网络应用场景，确定待配置给所述FEC的标签所需的配置方式，根据所述配置方式为所述FEC配置相应的标签（S20）；所述配置方式为：静态配置方式和/或动态配置方式；所述标签包括：入标签和出标签；根据配置给所述FEC的标签建立节点设备的标签转发表（S30）。本发明还公开了一种节点设备。本发明所提供的节点设备及其建立标签转发表的方法，能够为适合静态和/或动态配置出、入标签的节点设备所处网络应用场景建立标签转发表，扩展了节点设备所处的网络应用场景，提高了标签转发表在网络中部署的灵活性。

Description

节点设备及其建立标签转发表的方法 技术领域
本发明涉及标签交换技术领域，尤其涉及一种节点设备及其建立标签转发表的方法。
背景技术
MPLS(Multi-Protocol Label Switching,多协议标签交换)技术已成为当前核心网络的重要部署手段。MPLS的核心是通过标签分发建立LSP(Label Switch Path,标签交换路径)。LSP分为静态LSP和动态LSP两大类，其中动态LSP由下游节点设备和上游节点设备通过动态LDP(Label Distribution Protocol,标签分发协议)建立。静态LSP是通过对LSP沿途的LSR(Label Switch Router,标签交换路由器)进行相应的配置建立，使LSP满足MPLS转发的特性。静态LSP和动态LSP在MPLS-L2VPN和MPLS-L3VPN网络中有着广泛的应用。
现有技术中每个节点设备的整个标签转换路径要么通过动态LDP建立，要么通过静态配置的方式建立。然而对于某些网络应用场景中节点设备的标签转发表中可能出、入标签适合动态LDP的方式配置，另一部分出、入标签适合静态配置。即现有的标签转发表的建立方式无法实现针对标签转发表中部分出、入标签适合动态配置，另一部分出、入标签适合静态配置的节点设备所处的网络应用场景建立标签转发表。
发明内容
本发明的主要目的在于解决现有技术中实现针对标签转发表中部分出、入标签适合动态配置，另一部分出、入标签适合静态配置的节点设备所处的网络应用场景建立标签转发表的技术问题。
为实现上述目的，本发明提供一种节点设备建立标签转发表的方法，所述节点设备建立标签转发表的方法包括以下步骤：
节点设备根据自身所处网络应用场景绑定相应的FEC(Forwarding Equivalence Class，转发等价类)；
根据节点设备所处的网络应用场景，确定待配置给所述FEC的标签所需的配置方式，根据所述配置方式为所述FEC配置相应的标签；所述配置方式为：静态配置方式和/或动态配置方式；所述标签包括：入标签和出标签；
根据配置给所述FEC的标签建立节点设备的标签转发表。
在本发明的实施例中，所述根据节点设备所处的网络应用场景，确定待配置给所述FEC的标签所需的配置方式，根据所述配置方式为所述FEC配置相应的标签的步骤包括：
节点设备根据自身所处的网络应用场景，确定待配置给所述FEC的每个标签类型以及每个标签所需配置方式；
当存在需要通过静态配置方式配置的第一入标签，以及存在需要通过动态配置方式分配的第二出、入标签，则通过静态配置方式为所述FEC配置相应的第一入标签，以及通过动态配置方式为所述FEC分配相应的第二出、入标签，并将所述第一入标签和第二出、入标签作为配置给所述FEC的标签。
在本发明的实施例中，所述节点设备根据自身所处的网络应用场景，确定待配置给所述FEC的每个标签类型以及每个标签所需配置方式之后还包括：
当存在需要通过静态配置方式配置的第一出、入标签，以及存在需要通过动态配置方式分配的第二入标签，则通过静态配置方式为所述FEC配置相应的第一出、入标签，以及通过动态配置方式为所述FEC分配相应的第二入标签，并将所述第一出、入标签和第二入标签作为配置给所述FEC的标签。
在本发明的实施例中，所述节点设备根据自身所处的网络应用场景，确定待配置给所述FEC的每个标签类型以及每个标签所需配置方式之后还包括：
当只存在需要通过静态配置方式配置的第一出、入标签，则通过静态配置方式为所述FEC配置相应的第一出、入标签，并将所述第一出、入标签作为配置给所述FEC的标签。
在本发明的实施例中，所述节点设备根据自身所处的网络应用场景，确定待配置给所述FEC的每个标签类型以及每个标签所需配置方式之后还包括：
当只存在需要通过动态配置方式分配的第二出、入标签，则通过动态配置方式为所述FEC分配相应的第二出、入标签，并将所述第二出、入标签作为配置给所述FEC的标签。
此外，为实现上述目的，本发明还提供一种节点设备，其所述节点设备包括：
绑定模块，设置为根据节点设备所处网络应用场景绑定相应的转发等价类FEC；
配置模块，设置为根据节点设备所处的网络应用场景，确定待配置给所述FEC的标签所需的配置方式，根据所述配置方式为所述FEC配置相应的标签；所述配置方式为：静态配置方式和/或动态配置方式；所述标签包括：入标签和出标签；
建立模块，设置为根据配置给所述FEC的标签建立节点设备的标签转发表。
在本发明的实施例中，所述配置模块包括：
确定单元，设置为根据节点设备所处的网络应用场景，确定待配置给所述FEC的每个标签类型以及每个标签所需配置方式；
第一配置单元，设置为当存在需要通过静态配置方式配置的第一入标签，以及存在需要 通过动态配置方式分配的第二出、入标签，则通过静态配置方式为所述FEC配置相应的第一入标签，以及通过动态配置方式为所述FEC分配相应的第二出、入标签，并将所述第一入标签和第二出、入标签作为配置给所述FEC的标签。
在本发明的实施例中，所述配置模块还包括：
第二配置单元，设置为当存在需要通过静态配置方式配置的第一出、入标签，以及存在需要通过动态配置方式分配的第二入标签，则通过静态配置方式为所述FEC配置相应的第一出、入标签，以及通过动态配置方式为所述FEC分配相应的第二入标签，并将所述第一出、入标签和第二入标签作为配置给所述FEC的标签。
在本发明的实施例中，所述配置模块还包括：
第三配置单元，还设置为当只存在需要通过静态配置方式配置的第一出、入标签，则通过静态配置方式为所述FEC配置相应的第一出、入标签，并将所述第一出、入标签作为配置给所述FEC的标签。
在本发明的实施例中，所述配置模块还包括：
第四配置单元，设置为当只存在需要通过动态配置方式分配的第二出、入标签，则通过动态配置方式为所述FEC分配相应的第二出、入标签，并将所述第二出、入标签作为配置给所述FEC的标签。
本发明所提供的节点设备及其建立标签转发表的方法，通过节点设备根据自身所处的网络应用场景绑定相应的FEC；根据节点设备所处的网络应用场景，确定节点设备针对所述FEC待配置的标签所需配置方式，根据确定结果选择所需配置方式为节点设备针对所述FEC配置相应的标签；所述配置方式为：静态配置方式和/或动态配置方式；所述标签包括：入标签和出标签；根据针对所述FEC配置的标签建立节点设备的标签转发表的方式，能够为适合静态和/或动态配置出、入标签的节点设备所处网络应用场景建立标签转发表，扩展了节点设备所处的网络应用场景，提高了标签转发表在网络中部署的灵活性。
附图说明
图1为本发明的节点设备建立标签转发表的方法一实施例的流程示意图；
图2为图1中步骤S20的细化流程示意图；
图3为本发明的节点设备的功能模块示意图；
图4为图3中配置模块的具体细化功能模块示意图；
图5为图3中配置模块的另一具体细化功能模块示意图；
图6为图3中配置模块的另一具体细化功能模块示意图；
图7为图3中配置模块的另一具体细化功能模块示意图；
图8为本发明的节点设备所处网络应用场景示意图；
图9为本发明的节点设备另一所处网络应用场景示意图；
图10为本发明的节点设备另一所处网络应用场景示意图；
图11为本发明的节点设备另一所处网络应用场景示意图。
本发明目的的实现、功能特点及优点将结合实施例，参照附图做进一步说明。
具体实施方式
应当理解，此处所描述的具体实施例仅仅用以解释本发明，并不用于限定本发明。
本发明提供一种节点设备建立标签转发表的方法。参照图1，图1为本发明的节点设备建立标签转发表的方法一实施例的流程示意图。在该实施例中，所述节点设备建立标签转发表的方法包括：
步骤S10、节点设备根据自身所处网络应用场景绑定相应的FEC(Forwarding Equivalence Class，转发等价类)。
步骤S20、根据节点设备所处的网络应用场景，确定待配置给FEC的标签所需的配置方式，根据配置方式为FEC配置相应的标签。
本实施例中，所述配置方式为：静态配置方式和/或动态配置方式；所述标签包括：入标签和出标签。
参见图2，图2为图1中步骤S20的细化流程示意图。所述步骤S20具体包括：
步骤S21、节点设备根据自身所处的网络应用场景，确定待配置给FEC的每个标签类型以及每个标签所需配置方式。
步骤S22、当只存在需要通过静态配置方式配置的第一出、入标签，则通过静态配置方式为FEC配置相应的第一出、入标签，并将所述第一出、入标签作为配置给FEC的标签。
本实施例中，当只存在需要通过静态配置方式配置的第一标签，则通过静态配置方式配置静态LSP实例，其中，静态LSP实例配置命令格式为：
mpls static-lsp＜lsp-name＞；
bind ipv4＜prefix＞＜mask＞[force-advertise]；
insegment inlabel{＜in-label＞|explicit-null|implicit-null}；
outsegment{out-if＜interface-name＞[nexthop＜A.B.C.D＞]|nexthop＜A.B.C.D＞}outlabel{＜out-label＞|explicit-null|implicit-null}[force-valid]。
上述静态LSP实例配置命令中，所述“mpls static-lsp＜lsp-name＞”为静态LSP实例名称的配置命令，其中，“lsp-name”为静态LSP实例名称。
所述“bind ipv4＜prefix＞＜mask＞[force-advertise]”为将静态LSP实例与对应的FEC绑定的配置命令，其中“prefix”代表地址前缀，“mask”代表地址掩码，“force-advertise”代表静态LSP实例中配置的入标签绑定到该FEC后强制生效。
所述“insegment inlabel{＜in-label＞|explicit-null|implicit
-null}”是为静态LSP实例配置入标签的配置命令，其中“in-label”为普通类型入标签，“explicit-null”表示显式空标签，“implicit-null”为隐式空标签。
所述“outsegment{out-if＜interface-name＞[nexthop＜A.B.C.D＞]|nexthop＜A.B.C.D＞}outlabel{＜out-label＞|explicit-null|implicit-null}[force-valid]”是为静态LSP实例的出向配置出标签的配置命令。其中，“interface-name”代表出接口名称，“A.B.C.D”代表下一跳地址，“out-label”代表普通类型出标签，“explicit-null”代表显式空标签，“implicit-null”代表隐式空标签，“force-valid”代表配置的出标签强制生效。
步骤S23、当存在需要通过静态配置方式配置的第一入标签，以及存在需要通过动态配置方式分配的第二出、入标签，则通过静态配置方式为FEC配置相应的第一入标签，以及通过动态配置方式为FEC分配相应的第二出、入标签，并将第一入标签和第二出、入标签作为配置给FEC的标签。
本实施例中，当存在需要通过静态配置方式配置的第一入标签，以及存在需要通过动态配置方式分配的第二出、入标签时，通过静态配置方式为节点设备针对所述FEC配置相应的第一入标签的具体过程如步骤S22基本相同，不同之处在于：配置的出、入标签的配置命令中没有强制生效命令。由于节点设备针对同一FEC可以配置多个入标签，而节点设备针对同一FEC的同一出向只能配置一个出标签，因此当本实施例通过动态配置方式为节点设备针对同一FEC的相同出向分配了相应的第二出标签，静态LSP实例中为节点设备针对同一FEC配置的第一出、入标签为非强制生效，且所述第一入标签和第二入标签不同时，则丢弃第一出标签，保留第一入标签和第二出、入标签作为节点设备针对所述FEC配置的标签。
步骤S24、当存在需要通过静态配置方式配置的第一出、入标签，以及存在需要通过动态配置方式分配的第二入标签，则通过静态配置方式为FEC配置相应的第一出、入标签，以及通过动态配置方式为所述FEC分配相应的第二入标签，并将第一出、入标签和第二入标签作为配置给FEC的标签。
本实施例中，当存在需要通过静态配置方式配置的第一出、入标签，以及存在需要通过动态配置方式分配的第二入标签时，通过静态配置方式为节点设备针对所述FEC配置相应的第一出、入标签的具体过程如步骤S22基本相同，不同之处在于：静态配置的出、入标签的配置命令中没有强制生效指令。本实例中虽然静态配置的出、入标签未强制生效，但由于未通过动态配置的方式分配第二出标签，因此可以将所述第一出、入标签和第二入标签作为节 点设备针对所述FEC配置的标签。
步骤S25、当只存在需要通过动态配置方式分配的第二出、入标签，则通过动态配置方式为FEC分配相应的第二出、入标签，并将第二出、入标签作为配置给FEC的标签。
本实施例在节点设备通过动态配置的方式为节点设备针对绑定的FEC分配出、入的方式为现有技术，在此不再展开描述。
步骤S30、根据配置给FEC的标签建立节点设备的标签转发表。
本步骤S30具体包括：将通过动态配置的方式为节点设备针对所述FEC分配的出标签和/或入标签，以及通静态配置的方式为节点设备针对所述FEC配置的出标签和/或入标签，整合形成节点设备绑定的FEC的标签转发表，以使节点设备在收到报文后根据所述标签转发表实现对所述报文的转发。
另外本实施例中，在上述步骤S20之后还包括如下处理：将为节点设备针对所述FEC配置的入标签上报给的上游节点设备，以供上游节点设备实现动态分配出标签。
上述节点设备建立标签转发表的方法实施例中，通过节点设备根据自身所处的网络应用场景绑定相应的FEC；根据节点设备所处的网络应用场景，确定节点设备针对所述FEC待配置的标签所需配置方式，根据确定结果选择所需配置方式为节点设备针对所述FEC配置相应的标签；所述配置方式为：静态配置方式和/或动态配置方式；所述标签包括：入标签和出标签；根据针对所述FEC配置的标签建立节点设备的标签转发表的方式，能够为适合静态和/或动态配置出、入标签的节点设备所处网络应用场景建立标签转发表，扩展了节点设备所处的网络应用场景，提高了标签转发表在网络中部署的灵活性。
本发明进一步提供一种节点设备。参照图3，图3为本发明的节点设备的功能模块示意图。在该实施例中，所述节点设备100包括：绑定模块110、配置模块120、建立模块130。其中所述绑定模块110，设置为根据节点设备所处的网络应用场景绑定相应的FEC。所述配置模块120，设置为根据节点设备所处的网络应用场景，确定待配置给所述FEC的标签所需的配置方式，根据所述配置方式为所述FEC配置相应的标签；所述配置方式为：静态配置方式和/或动态配置方式；所述标签包括：入标签和出标签。所述建立模块130，设置为根据配置给所述FEC的标签建立节点设备的标签转发表。
本实施例中所述建立模块130具体将节点设备通过动态配置的方式为FEC分配的出标签和/或入标签，以及通过静态配置的方式为FEC配置的出标签和/或入标签，整合形成节点设备绑定的所述FEC的标签转发表，以使节点设备在收到报文后根据所述标签转发表实现对所述报文的转发。
另外本实施例中，在上述步骤S20之后还包括如下处理：将节点设备为FEC配置的入标签上报给的上游节点设备，以供上游节点设备实现动态分配出标签。
参见图4，图4为图3中配置模块的具体细化功能模块示意图。本实施例中，所述配置模块120包括：确定单元121、第一配置单元。其中所述确定单元121，设置为根据节点设备所处的网络应用场景，确定待配置给所述FEC的每个标签类型以及每个标签所需配置方式。所述第一配置单元122，设置为当存在需要通过静态配置方式配置的第一入标签，以及存在需要通过动态配置方式分配的第二出、入标签，则通过静态配置方式为FEC配置相应的第一入标签，以及通过动态配置方式为FEC分配相应的第二出、入标签，并将所述第一入标签和第二出、入标签作为配置给所述FEC的标签。
本实施例中，当存在需要通过静态配置方式配置的第一入标签，以及存在需要通过动态配置方式分配的第二出、入标签时，通过第一配置单元121采用静态配置方式为FEC配置相应的第一入标签的具体过程与以下所描述的第三配置单元124配置第一出、入标签的方式基本相同，不同之处在于：静态配置的出、入标签的配置命令中没有强制生效命令。由于对应同一FEC可以配置多个入标签，而对应同一FEC的同一出向只能配置一个出标签，因此当本实施例节点设备通过动态配置方式为同一FEC的相同出向分配了相应的第二出标签，静态LSP实例中为节点设备针对同一FEC配置的第一出、入标签为非强制生效，且所述第一入标签和第二入标签不同时，则丢弃第一出标签，保留第一入标签和第二出、入标签作为节点设备针对所述FEC配置的标签。
参见图5，图5为图3中配置模块的另一具体细化功能模块示意图。本实施例中，所述配置模块120还包括第二配置单元123。所述第二配置单元123，设置为当存在需要通过静态配置方式配置的第一出、入标签，以及存在需要通过动态配置方式分配的第二入标签，则通过静态配置方式为所述FEC配置相应的第一出、入标签，以及通过动态配置方式为所述FEC分配相应的第二入标签，并将所述第一出、入标签和第二入标签作为配置给FEC的标签。
本实施例中，当存在需要通过静态配置方式配置的第一出、入标签，以及存在需要通过动态配置方式分配的第二入标签时，节点设备通过所述第二配置单元12采用静态配置方式为FEC配置相应的第一出、入标签的具体过程与以下所描述的第三配置单元124配置第一出、入标签的方式基本相同，不同之处在于：静态配置的出、入标签的配置命令中没有强制生效指令。本实例中虽然静态配置的出、入标签未强制生效，但由于未通过动态配置的方式分配第二出标签，因此可以将所述第一出、入标签和第二入标签作为节点设备针对所述FEC配置的标签。
参见图6，图6为图3中配置模块的另一具体细化功能模块示意图。本实施例中，所述配置模块120还包括第三配置单元124。所述第三配置单元124，设置为当只存在需要通过静态配置方式配置的第一出、入标签，则通过静态配置方式为FEC配置相应的第一出、入标签，并将所述第一出、入标签作为配置给FEC的标签。
本实施例中，当只存在需要通过静态配置方式配置的第一标签，则通过第三配置单元124采用静态配置方式配置静态LSP实例，其中，静态LSP实例配置命令格式为：
mpls static-lsp＜lsp-name＞；
bind ipv4＜prefix＞＜mask＞[force-advertise]；
insegment inlabel{＜in-label＞|explicit-null|implicit-null}；
outsegment{out-if＜interface-name＞[nexthop＜A.B.C.D＞]|nexthop＜A.B.C.D＞}outlabel{＜out-label＞|explicit-null|implicit-null}[force-valid]。
上述静态LSP实例配置命令中，所述“mpls static-lsp＜lsp-name＞”为静态LSP实例名称的配置命令，其中，“lsp-name”为静态LSP实例名称。
所述“bind ipv4＜prefix＞＜mask＞[force-advertise]”为将静态LSP实例与对应的FEC绑定的配置命令，其中“prefix”代表地址前缀，“mask”代表地址掩码，“force-advertise”代表静态LSP实例中配置的入标签绑定到该FEC后强制生效。
所述“insegment inlabel{＜in-label＞|explicit-null|implicit
-null}”是为静态LSP实例配置入标签的配置命令，其中“in-label”为普通类型入标签，“explicit-null”表示显式空标签，“implicit-null”为隐式空标签。
所述“outsegment{out-if＜interface-name＞[nexthop＜A.B.C.D＞]|nexthop＜A.B.C.D＞}outlabel{＜out-label＞|explicit-null|implicit-null}[force-valid]”是为静态LSP实例的出向配置出标签的配置命令。其中，“interface-name”代表出接口名称，“A.B.C.D”代表下一跳地址，“out-label”代表普通类型出标签，“explicit-null”代表显式空标签，“implicit-null”代表隐式空标签，“force-valid”代表配置的出标签强制生效。
参见图7，图7为图3中配置模块的另一具体细化功能模块示意图。本实施例中，所述配置模块120还包括第四配置单元125。所述第四配置单元125，设置为当只存在需要通过动态配置方式分配的第二出、入标签，则通过动态配置方式为所述FEC分配相应的第二出、入标签，并将所述第二出、入标签作为配置给FEC的标签。
以上实施例中在节点设备通过动态配置的方式为节点设备针对绑定的FEC分配出、入的方式为现有技术，在此不再展开描述。
本发明所提供的节点设备实施例，通过根据节点设备所处的网络应用场景绑定相应的FEC；根据节点设备所处的网络应用场景，确定节点设备针对所述FEC待配置的标签所需配置方式，根据确定结果选择所需配置方式为节点设备针对所述FEC配置相应的标签；所述配置方式为：静态配置方式和/或动态配置方式；所述标签包括：入标签和出标签；根据针对所述FEC配置的标签建立节点设备的标签转发表的方式，能够为适合静态和/或动态配置出、入标签的节点设备所处网络应用场景建立标签转发表，扩展了节点设备所处的网络应用场景，提高了标签转发表在网络中部署的灵活性。
以下通过四个网络应用场景实例对本发明的节点设备及其建立标签转发表的方法进行进一步详细的描述。
实例一：参见图8，图8为本发明的节点设备所处网络应用场景示意图。图8中节点设备LSR2的下游节点设备LSR3通过静态配置的方式为FEC配置出标签1、入标签2；节点设备LSR2根据入标签2配置本地静态出标签2。节点设备LSR2通过静态配置的方式为FEC配置入标签3，并使能强制生效，并将入标签3上报给节点设备LSR1。节点设备LSR1根据节点设备LSR2上报的入标签3，通过动态方式为FEC匹配出标签3。节点设备LSR2根据为FEC配置的出标签2、入标签3建立自身的标签转发表。
实例二：参见图9，图9为本发明的节点设备另一所处网络应用场景示意图。图9中节点设备LSR2的下游节点设备LSR3通过动态分配的方式为绑定的FEC分配出标签1、入标签2，并将入标签2上报给上游节点设备LSR2。节点设备LSR2根据节点设备LSR3上报的入标签2，通过动态配置的方式为绑定的FEC分配出标签2，并通过静态配置的方式为绑定的FEC配置入标签3。节点设备LSR1通过静态配置的方式为绑定的FEC配置出标签3、入标签4。节点设备LSR2根据为FEC配置的出标签2、入标签3建立自身的标签转发表。
实例三：参见图10，图10为本发明的节点设备另一所处网络应用场景示意图。图10中节点设备LSR3通过静态配置方式为绑定的FEC配置入标签1、通动态配置方式为FEC分配入标签2，并将入标签2上报给上游节点设备LSR1，即在节点设备LSR3中静态配置的入标签1和动态分配的入标签2同时生效。节点设备LSR3的下游节点设备LSR4通过静态配置方式为绑定的FEC配置入标签3；或通过动态配置方式为绑定的FEC分配入标签4，并将入标签4上报给上游设备LSR3。在节点设备LSR3中针对绑定的FEC的相同出向要么根据下游节点设备LSR4静态配置的入标签3配置本地静态出标签3，要么根据下游节点设备LSR4上报的入标签4动态分配出标签4。节点设备LSR1根据下游节点设备LSR3上报的入标签2动态分配出标签2。节点设备LSR2根据下游节点设备LSR3静态配置的入标签1配置本地静态出标签1。其中节点设备LSR3根据为绑定的FEC配置的入标签1、2、出标签3建立自身的标签转发表；或者为绑定的FEC配置的入标签1、2、出标签4建立自身的标签转发表。本网络应用场景中节点设备LSR3上游包括节点设备LSR1和LSR2两个，一个下游节点设备LSR4，因此在节点设备LSR3上针对绑定的FEC需要配置两个入标签和一个出标签。相比包括一个上游节点设备、一个下游节点设备的网络应用场景，增加了一个上游节点设备部署静态或动态标签转发表，延长所绑定的FEC对应的标签转发表。节点设备LSR3处于本网络应用场景中虽然延长了所绑定的FEC对应的标签转发表，但并不不影响原有的标签转发表的转发流量。
实例四：参见图11，图11为本发明的节点设备另一所处网络应用场景示意图。图10中，节点设备LSR2的下游节点设备LSR3通过动态配置的方式为绑定的FEC配置入标签1，并将入标签1上报给上游节点设备LSR2。节点设备LSR2的下游节点设备LSR4通过静态的方式为绑定的FEC配置入标签2。节点设备LSR2根据下游设备LSR3上报的入标签1，为自身绑定的FEC的节点设备LSR3出向动态分配出标签1；并根据下游设备LSR4静态配置的入标签2为自身绑定的FEC的节点设备LSR4出向静态配置出标签2；同时通过静态配置的方式配置入标签3，或者通过动态配置的方式分配入标签4，并根据所述出标签1、2，入标签3、4建立自身的标签转发表。另外在节点设备LSR2上所述出标签1、2形成负荷分担或FRR关系。
本发明以上所述的节点设备为标签交换路由器设备。
以上仅为本发明的优选实施例，并非因此限制本发明的专利范围，凡是利用本发明说明书及附图内容所作的等效结构或等效流程变换，或直接或间接运用在其他相关的技术领域，均同理包括在本发明的专利保护范围内。
工业实用性
基于本发明实施例提供的上述技术方案，通过节点设备根据自身所处的网络应用场景绑定相应的FEC；根据节点设备所处的网络应用场景，确定节点设备针对所述FEC待配置的标签所需配置方式，根据确定结果选择所需配置方式为节点设备针对所述FEC配置相应的标签；所述配置方式为：静态配置方式和/或动态配置方式；所述标签包括：入标签和出标签；根据针对所述FEC配置的标签建立节点设备的标签转发表的方式，能够为适合静态和/或动态配置出、入标签的节点设备所处网络应用场景建立标签转发表，扩展了节点设备所处的网络应用场景，提高了标签转发表在网络中部署的灵活性。

Claims (10)

  1. 一种节点设备建立标签转发表的方法，所述节点设备建立标签转发表的方法包括以下步骤：
    节点设备根据自身所处网络应用场景绑定相应的转发等价类FEC；
    根据节点设备所处的网络应用场景，确定待配置给所述FEC的标签所需的配置方式，根据所述配置方式为所述FEC配置相应的标签；所述配置方式为：静态配置方式和/或动态配置方式；所述标签包括：入标签和出标签；
    根据配置给所述FEC的标签建立节点设备的标签转发表。
  2. 如权利要求1所述的节点设备建立标签转发表的方法，其中，所述根据节点设备所处的网络应用场景，确定待配置给所述FEC的标签所需的配置方式，根据所述配置方式为所述FEC配置相应的标签的步骤包括：
    节点设备根据自身所处的网络应用场景，确定待配置给所述FEC的每个标签类型以及每个标签所需配置方式；
    当存在需要通过静态配置方式配置的第一入标签，以及存在需要通过动态配置方式分配的第二出、入标签，则通过静态配置方式为所述FEC配置相应的第一入标签，以及通过动态配置方式为所述FEC分配相应的第二出、入标签，并将所述第一入标签和第二出、入标签作为配置给所述FEC的标签。
  3. 根据权利要求2所述的节点设备建立标签转发表的方法，其中，所述节点设备根据自身所处的网络应用场景，确定待配置给所述FEC的每个标签类型以及每个标签所需配置方式之后还包括：
    当存在需要通过静态配置方式配置的第一出、入标签，以及存在需要通过动态配置方式分配的第二入标签，则通过静态配置方式为所述FEC配置相应的第一出、入标签，以及通过动态配置方式为所述FEC分配相应的第二入标签，并将第一出、入标签和第二入标签作为配置给所述FEC的标签。
  4. 如权利要求2所述的节点设备建立标签转发表的方法，其中，所述节点设备根据自身所处的网络应用场景，确定待配置给所述FEC的每个标签类型以及每个标签所需配置方式之后还包括：
    当只存在需要通过静态配置方式配置的第一出、入标签，则通过静态配置方式为所述FEC配置相应的第一出、入标签，并将所述第一出、入标签作为配置给所述FEC的标签。
  5. 如权利要求2所述的节点设备建立标签转发表的方法，其中，所述节点设备根据自身所处的网络应用场景，确定待配置给所述FEC的每个标签类型以及每个标签所需配置方式之后还包括：
    当只存在需要通过动态配置方式分配的第二出、入标签，则通过动态配置方式为所 述FEC分配相应的第二出、入标签，并将所述第二出、入标签作为配置给所述FEC的标签。
  6. 一种节点设备，所述节点设备包括：
    绑定模块，设置为根据节点设备所处网络应用场景绑定相应的转发等价类FEC；
    配置模块，设置为根据节点设备所处的网络应用场景，确定待配置给所述FEC的标签所需的配置方式，根据所述配置方式为所述FEC配置相应的标签；所述配置方式为：静态配置方式和/或动态配置方式；所述标签包括：入标签和出标签；
    建立模块，设置为根据配置给所述FEC的标签建立节点设备的标签转发表。
  7. 如权利要求6所述的节点设备，其中，所述配置模块包括：
    确定单元，设置为根据节点设备所处的网络应用场景，确定待配置给所述FEC的每个标签类型以及每个标签所需配置方式；
    第一配置单元，设置为当存在需要通过静态配置方式配置的第一入标签，以及存在需要通过动态配置方式分配的第二出、入标签，则通过静态配置方式为所述FEC配置相应的第一入标签，以及通过动态配置方式为所述FEC分配相应的第二出、入标签，并将所述第一入标签和第二出、入标签作为配置给所述FEC的标签。
  8. 如权利要求7所述的节点设备，其中，所述配置模块还包括：
    第二配置单元，设置为当存在需要通过静态配置方式配置的第一出、入标签，以及存在需要通过动态配置方式分配的第二入标签，则通过静态配置方式为所述FEC配置相应的第一出、入标签，以及通过动态配置方式为所述FEC分配相应的第二入标签，并将所述第一出、入标签和第二入标签作为配置给所述FEC的标签。
  9. 如权利要求7所述的节点设备，其中，所述配置模块还包括：
    第三配置单元，还设置为当只存在需要通过静态配置方式配置的第一出、入标签，则通过静态配置方式为所述FEC配置相应的第一出、入标签，并将所述第一出、入标签作为配置给所述FEC的标签。
  10. 根据权利要求6至9任一项所述的节点设备，其中，所述配置模块还包括：
    第四配置单元，设置为当只存在需要通过动态配置方式分配的第二出、入标签，则通过动态配置方式为所述FEC分配相应的第二出、入标签，并将所述第二出、入标签作为配置给所述FEC的标签。
PCT/CN2015/092225 2015-04-16 2015-10-19 节点设备及其建立标签转发表的方法 WO2016165299A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510180751.0A CN106161244B (zh) 2015-04-16 2015-04-16 节点设备及其建立标签转发表的方法
CN201510180751.0 2015-04-16

Publications (1)

Publication Number Publication Date
WO2016165299A1 true WO2016165299A1 (zh) 2016-10-20

Family

ID=57127121

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/092225 WO2016165299A1 (zh) 2015-04-16 2015-10-19 节点设备及其建立标签转发表的方法

Country Status (2)

Country Link
CN (1) CN106161244B (zh)
WO (1) WO2016165299A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107888493B (zh) * 2017-11-30 2020-04-21 迈普通信技术股份有限公司 一种标签交换路径的建立方法及装置
CN110932895B (zh) * 2019-11-26 2022-07-15 中国联合网络通信集团有限公司 一种网络切片的报文转发方法和装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1921453A (zh) * 2006-09-25 2007-02-28 杭州华为三康技术有限公司 Mpls有序方式下lsp中间节点标签分配方法及装置
CN101073226A (zh) * 2004-10-08 2007-11-14 法国电信公司 在标签交换的通信网络中创建隧道的方法和设备
CN101692669A (zh) * 2009-07-23 2010-04-07 中兴通讯股份有限公司 虚拟私有网的路由标签分配方法与装置
CN103916303A (zh) * 2014-04-18 2014-07-09 杭州华三通信技术有限公司 一种mpls te隧道配置装置和方法
US20150003283A1 (en) * 2013-06-28 2015-01-01 Cisco Technology, Inc. A multi-layer stateful path computation element architecture

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100452755C (zh) * 2004-05-18 2009-01-14 华为技术有限公司 一种实现静态标签转发路径的方法
JP4514648B2 (ja) * 2005-05-18 2010-07-28 富士通株式会社 管理サーバによる情報処理方法及びルータ
US7885259B2 (en) * 2007-11-30 2011-02-08 Cisco Technology, Inc. Deterministic multiprotocol label switching (MPLS) labels
CN101707566B (zh) * 2009-11-30 2011-09-07 成都市华为赛门铁克科技有限公司 标签分配方法和处理装置
US8891553B2 (en) * 2009-12-16 2014-11-18 Cisco Technology, Inc. Selective label retention in a label switching network
CN102594712A (zh) * 2012-03-28 2012-07-18 北京星网锐捷网络技术有限公司 一种标签交换路径的确定方法以及装置
CN104144122B (zh) * 2013-05-10 2019-06-21 华为技术有限公司 建立标签交换路径的方法、设备及系统
US10708182B2 (en) * 2013-07-26 2020-07-07 Cisco Technology, Inc. MPLS LSP connectivity test when the initiator address is unknown
CN103986654B (zh) * 2014-05-05 2017-11-28 新华三技术有限公司 一种lsp生成方法和设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101073226A (zh) * 2004-10-08 2007-11-14 法国电信公司 在标签交换的通信网络中创建隧道的方法和设备
CN1921453A (zh) * 2006-09-25 2007-02-28 杭州华为三康技术有限公司 Mpls有序方式下lsp中间节点标签分配方法及装置
CN101692669A (zh) * 2009-07-23 2010-04-07 中兴通讯股份有限公司 虚拟私有网的路由标签分配方法与装置
US20150003283A1 (en) * 2013-06-28 2015-01-01 Cisco Technology, Inc. A multi-layer stateful path computation element architecture
CN103916303A (zh) * 2014-04-18 2014-07-09 杭州华三通信技术有限公司 一种mpls te隧道配置装置和方法

Also Published As

Publication number Publication date
CN106161244B (zh) 2020-05-22
CN106161244A (zh) 2016-11-23

Similar Documents

Publication Publication Date Title
CN111385206B (zh) 报文转发的方法、网络系统、相关设备及计算机存储介质
EP3200402B1 (en) Segment routing information obtainment method and segment routing network establishment method
US9178811B2 (en) Method, apparatus and system for generating label forwarding table on ring topology
US11805010B2 (en) Signaling IP path tunnels for traffic engineering
CN106549871B (zh) 一种报文处理的方法、设备和系统
US20120057505A1 (en) Method, apparatus, and system for setting up bidirectional point-to-multipoint label switched path
US10313234B2 (en) RSVP make-before-break label reuse
US20110188509A1 (en) Ethernet frame broadcast emulation
EP2961117B1 (en) Method, device and system for establishing label switched path
WO2019007316A1 (zh) 实现双向segment routing隧道的方法及装置、存储介质及设备
US8824451B2 (en) Method and system for establishing an associated bidirectional label-switched path
EP2676412B1 (en) Signaling extension for a label switched path over a composite link
JP2009519666A (ja) ネットワーク・トンネル間の資源共有
EP3493492B1 (en) Rsvp make-before-break label reuse
US9781030B1 (en) Fast re-route protection using GRE over MPLS
WO2016165299A1 (zh) 节点设备及其建立标签转发表的方法
CN106330701B (zh) 环形组网的快速重路由方法及装置
US20140161124A1 (en) Enhanced Upstream Label Assignment (ULA) Mechanism For Point To Multi-Point (P2MP) and/or Multi-Point To Multi-Point (MP2MP) Facility Protection
US8995304B2 (en) Enhanced upstream label assignment (ULA) mechanism for point to multi-point (P2MP) and/or multi-point to multi-point (MP2MP) facility protection
CN111641561B (zh) 报文转发方法、装置、隧道创建方法、装置及网络设备
JP5211956B2 (ja) ルータ装置及びそれに用いるスケーラビリティ拡大方法
Liu et al. Internet Engineering Task Force H. Chen Internet-Draft Huawei Technologies Intended status: Standards Track N. So Expires: August 14, 2014 Tata Communications

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: 15888995

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: 15888995

Country of ref document: EP

Kind code of ref document: A1