CN106161244B

CN106161244B - Node equipment and method for establishing label forwarding table

Info

Publication number: CN106161244B
Application number: CN201510180751.0A
Authority: CN
Inventors: 宋兵
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2015-04-16
Filing date: 2015-04-16
Publication date: 2020-05-22
Anticipated expiration: 2035-04-16
Also published as: WO2016165299A1; CN106161244A

Abstract

The invention discloses a method for node equipment to establish a label forwarding table, which comprises the following steps: the node equipment binds a corresponding forwarding equivalence class FEC according to a network application scene where the node equipment is located; determining a configuration mode required by a label to be configured to the FEC according to a network application scene where node equipment is located, and configuring a corresponding label for the FEC according to the configuration mode; the configuration mode is as follows: a static configuration mode and/or a dynamic configuration mode; the label includes: entering a label and exiting the label; and establishing a label forwarding table of the node equipment according to the label configured to the FEC. The invention also discloses node equipment. The node equipment and the method for establishing the label forwarding table thereof provided by the invention can establish the label forwarding table for the network application scene where the node equipment suitable for statically and/or dynamically configuring out and in labels is positioned, thereby expanding the network application scene where the node equipment is positioned and improving the flexibility of the label forwarding table in the network deployment.

Description

Node equipment and method for establishing label forwarding table

Technical Field

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.

Background

MPLS (Multi-Protocol Label Switching) technology has become an important deployment means of current core networks. At the core of MPLS, LSPs are established by Label Switch Path (Label Switch Path). The LSP is classified into two categories, i.e., a static LSP and a dynamic LSP, where the dynamic LSP is established by a downstream node device and an upstream node device through a dynamic LDP (Label Distribution Protocol). Static LSPs are established by configuring and establishing LSRs (Label Switch routers) along the LSPs accordingly, so that the LSPs satisfy the characteristics of MPLS forwarding. Static LSPs and dynamic LSPs have wide application in MPLS-L2VPN and MPLS-L3VPN networks.

In the prior art, the whole label switching path of each node device is established either by dynamic LDP or by means of static configuration. However, for some network application scenarios, the outgoing and incoming labels in the label forwarding table of the node device may be configured in a manner suitable for dynamic LDP, and the other part of the outgoing and incoming labels is configured in a static manner. That is, the existing establishment method of the label forwarding table cannot establish the label forwarding table aiming at the network application scene where the node device with the part of outgoing labels and incoming labels in the label forwarding table is suitable for dynamic configuration and the other part of outgoing labels and incoming labels is suitable for static configuration.

Disclosure of Invention

The invention mainly aims to solve the technical problem of establishing a label forwarding table aiming at a network application scene where node equipment with partial outgoing labels and incoming labels suitable for dynamic configuration and partial outgoing labels and incoming labels suitable for static configuration in the label forwarding table are positioned in the prior art.

In order to achieve the above object, the present invention provides a method for a node device to establish a label forwarding table, wherein the method for the node device to establish the label forwarding table comprises the following steps:

the node equipment binds corresponding FEC (Forwarding equivalence class) according to the network application scene where the node equipment is located;

determining a configuration mode required by a label to be configured to the FEC according to a network application scene where node equipment is located, and configuring a corresponding label for the FEC according to the configuration mode; the configuration mode is as follows: a static configuration mode and/or a dynamic configuration mode; the label includes: entering a label and exiting the label;

and establishing a label forwarding table of the node equipment according to the label configured to the FEC.

Preferably, the determining, according to a network application scenario in which the node device is located, a configuration manner required by a label to be configured to the FEC, and the step of configuring, according to the configuration manner, a corresponding label for the FEC includes:

the node equipment determines each label type to be configured to the FEC and a configuration mode required by each label according to a network application scene where the node equipment is located;

and when a first incoming label needing to be configured in a static configuration mode exists and a second incoming and outgoing label needing to be allocated in a dynamic configuration mode exists, configuring a corresponding first incoming label for the FEC in the static configuration mode, allocating a corresponding second incoming and outgoing label for the FEC in the dynamic configuration mode, and taking the first incoming label and the second incoming and outgoing label as labels configured for the FEC.

Preferably, the determining, by the node device according to the network application scenario in which the node device is located, each label type to be configured to the FEC and a configuration mode required for each label further includes:

when a first outgoing label and a first incoming label which need to be configured in a static configuration mode exist, and a second incoming label which needs to be allocated in a dynamic configuration mode exist, corresponding first outgoing labels and corresponding first incoming labels are configured for the FEC in the static configuration mode, corresponding second incoming labels are allocated for the FEC in the dynamic configuration mode, and the first outgoing labels, the corresponding first incoming labels and the corresponding second incoming labels are used as labels configured for the FEC.

and when only a first outgoing label and a first incoming label which need to be configured in a static configuration mode exist, configuring the corresponding first outgoing label and first incoming label for the FEC in the static configuration mode, and taking the first outgoing label and the first incoming label as the labels configured for the FEC.

and when only a second outgoing label and a second incoming label which need to be allocated in a dynamic configuration mode exist, allocating the corresponding second outgoing label and second incoming label for the FEC in the dynamic configuration mode, and using the second outgoing label and the second incoming label as the labels allocated to the FEC.

In addition, to achieve the above object, the present invention further provides a node device, where the node device includes:

the binding module is used for binding the corresponding forwarding equivalence class FEC according to the network application scene where the node equipment is located;

a configuration module, configured to determine a configuration mode required by a label to be configured to the FEC according to a network application scenario in which a node device is located, and configure a corresponding label for the FEC according to the configuration mode; the configuration mode is as follows: a static configuration mode and/or a dynamic configuration mode; the label includes: entering a label and exiting the label;

and the establishing module is used for establishing a label forwarding table of the node equipment according to the label configured to the FEC.

Preferably, the configuration module comprises:

a determining unit, configured to determine, according to a network application scenario in which the node device is located, each label type to be configured to the FEC and a configuration mode required by each label;

a first configuration unit, configured to configure, when there is a first incoming label that needs to be configured in a static configuration manner and there is a second incoming and outgoing label that needs to be allocated in a dynamic configuration manner, a corresponding first incoming label for the FEC in the static configuration manner, and allocate a corresponding second incoming and outgoing label for the FEC in the dynamic configuration manner, and use the first incoming label and the second incoming and outgoing label as labels configured for the FEC.

Preferably, the configuration module further comprises:

and a second configuration unit, configured to configure, when there is a first outgoing label and an incoming label that need to be configured in a static configuration manner and a second incoming label that needs to be allocated in a dynamic configuration manner, a corresponding first outgoing label and a corresponding first incoming label for the FEC in the static configuration manner, and allocate a corresponding second incoming label for the FEC in the dynamic configuration manner, and use the first outgoing label, the first incoming label, and the second incoming label as labels configured for the FEC.

Preferably, the configuration module further comprises:

and the third configuration unit is further configured to configure, when only the first outgoing label and the first incoming label that need to be configured in the static configuration manner exist, the corresponding first outgoing label and first incoming label for the FEC in the static configuration manner, and use the first outgoing label and the first incoming label as the labels configured to the FEC.

Preferably, the configuration module further comprises:

and a fourth configuration unit, configured to, when only a second outgoing label and a second incoming label that need to be allocated in a dynamic configuration manner exist, allocate the corresponding second outgoing label and second incoming label to the FEC in the dynamic configuration manner, and use the second outgoing label and the second incoming label as a label configured to the FEC.

The node equipment and the method for establishing the label forwarding table thereof bind the corresponding FEC according to the network application scene of the node equipment; determining a configuration mode required by the node equipment for the label to be configured of the FEC according to a network application scene where the node equipment is located, and selecting the required configuration mode according to a determination result to configure the corresponding label for the FEC by the node equipment; the configuration mode is as follows: a static configuration mode and/or a dynamic configuration mode; the label includes: entering a label and exiting the label; according to the method for establishing the label forwarding table of the node equipment aiming at the label configured by the FEC, the label forwarding table can be established for the network application scene where the node equipment suitable for static and/or dynamic configuration of the out-label and in-label is located, the network application scene where the node equipment is located is expanded, and the flexibility of the deployment of the label forwarding table in the network is improved.

Drawings

Fig. 1 is a flowchart illustrating an embodiment of a method for a node device to establish a label forwarding table according to the present invention;

FIG. 2 is a detailed flowchart of step S20 in FIG. 1;

FIG. 3 is a functional block diagram of a node device according to the present invention;

FIG. 4 is a detailed functional block diagram of the configuration block of FIG. 3;

FIG. 5 is a block diagram of another detailed functional block of the configuration block of FIG. 3;

FIG. 6 is a block diagram of another detailed functional block of the configuration block of FIG. 3;

FIG. 7 is a block diagram of another detailed functional block of the configuration block of FIG. 3;

FIG. 8 is a schematic diagram of a network application scenario in which a node device according to the present invention is located;

FIG. 9 is a schematic diagram of another network application scenario in which the node device of the present invention is located;

FIG. 10 is a schematic diagram of another network application scenario in which the node device of the present invention is located;

fig. 11 is a schematic view of another network application scenario in which the node device of the present invention is located.

The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The invention provides a method for node equipment to establish a label forwarding table. Referring to fig. 1, fig. 1 is a flowchart illustrating an embodiment of a method for a node device to establish a label forwarding table according to the present invention. In this embodiment, the method for establishing the label forwarding table by the node device includes:

step S10, the node device binds a corresponding FEC (forwarding equivalence Class) according to the network application scenario where the node device is located.

Step S20, determining a configuration mode required by the label to be configured to the FEC according to the network application scenario where the node device is located, and configuring a corresponding label for the FEC according to the configuration mode.

In this embodiment, the configuration manner is as follows: a static configuration mode and/or a dynamic configuration mode; the label includes: label in and label out.

Referring to fig. 2, fig. 2 is a detailed flowchart of step S20 in fig. 1. The step S20 specifically includes:

step S21, the node device determines each label type to be configured to the FEC and a configuration mode required by each label according to the network application scenario where the node device is located.

Step S22, when only the first outgoing label and the first incoming label that need to be configured in the static configuration mode exist, configuring the corresponding first outgoing label and first incoming label for the FEC in the static configuration mode, and using the first outgoing label and the first incoming label as the labels configured for the FEC.

In this embodiment, when only the first label that needs to be configured in the static configuration manner exists, the static LSP instance is configured in the static configuration manner, where the static LSP instance configuration command format is:

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]。

in the static LSP instance configuration command, the "mpls static-LSP < LSP-name >" is a configuration command of the static LSP instance name, wherein "LSP-name" is the static LSP instance name.

The "bind ipv4 < prefix > < mask > [ force-inverse ]" is a configuration command for binding the static LSP instance with the corresponding FEC, where "prefix" represents an address prefix, "mask" represents an address mask, and "force-inverse" represents that an ingress label configured in the static LSP instance is bound to the FEC and then is forced to take effect.

The "embodiment in label { < in-label > | explicit-null | explicit

Null is a configuration command to configure in-labels for static LSP instances, where "in-label" is a normal type in-label, "explicit-null" indicates an explicit null label, and "explicit-null" is an implicit null label.

The "outsegment { out-if < interface-name > [ nexthop < A.B.C.D > ], | outlabel { < out-label > | explicit-null } [ force-valid ]" is a configuration command that configures a label for the egress of a static LSP instance. The interface-name represents an interface name, the A.B.C.D represents a next hop address, the out-label represents a common type outgoing label, the explicit null label represents an explicit null label, the implicit null label represents an implicit null label, and the force-valid represents the configured outgoing label to be forced to take effect.

Step S23, when there is a first incoming label that needs to be configured in a static configuration manner and there is a second outgoing label and incoming label that needs to be allocated in a dynamic configuration manner, configuring a corresponding first incoming label for the FEC in the static configuration manner, allocating a corresponding second outgoing label and incoming label for the FEC in the dynamic configuration manner, and using the first incoming label and the second outgoing label and incoming label as labels configured for the FEC.

In this embodiment, when there is a first incoming label that needs to be configured in a static configuration manner and there is a second incoming label that needs to be allocated in a dynamic configuration manner, the specific process of configuring, for the FEC, a corresponding first incoming label for the node device in the static configuration manner is basically the same as that in step S22, except that: the configured configuration commands of the configured outgoing and incoming labels do not have forced effective commands. Because the node device may configure multiple ingress labels for the same FEC, and the node device may only configure one egress label for the same egress direction of the same FEC, when the embodiment allocates a corresponding second egress label for the node device for the same egress direction of the same FEC through a dynamic configuration manner, and the first egress label and the first ingress label configured for the same FEC for the node device in the static LSP instance are not compulsorily effective, and the first ingress label and the second ingress label are different, the first egress label is discarded, and the first ingress label and the second egress label are retained as labels configured for the FEC by the node device.

Step S24, when there are first outgoing label and incoming label that need to be configured in a static configuration manner and second incoming label that need to be allocated in a dynamic configuration manner, configuring corresponding first outgoing label and incoming label for FEC in the static configuration manner, allocating corresponding second incoming label for FEC in the dynamic configuration manner, and using the first outgoing label, the first incoming label and the second incoming label as labels configured for FEC.

In this embodiment, when there is a first outgoing label and a first incoming label that need to be configured in a static configuration manner and there is a second incoming label that needs to be allocated in a dynamic configuration manner, the specific process of configuring, for the FEC, the corresponding first outgoing label and the corresponding first incoming label for the node device in the static configuration manner is basically the same as step S22, except that: the configuration commands of the static configuration in and out tags have no forced effective instruction. In this example, although statically configured outgoing and incoming labels are not forced to be valid, since the second outgoing label is not allocated in a dynamic configuration manner, the first outgoing label, the first incoming label and the second incoming label may be used as labels configured by the node device for the FEC.

And step S25, when only the second outgoing label and the second incoming label which need to be allocated through the dynamic configuration mode exist, allocating the corresponding second outgoing label and the corresponding second incoming label for the FEC through the dynamic configuration mode, and using the second outgoing label and the second incoming label as the labels allocated to the FEC.

In this embodiment, the manner in which the node device allocates ingress and egress for the bound FEC for the node device in a dynamic configuration manner is the prior art, and a description thereof is not further provided herein.

And step S30, establishing a label forwarding table of the node device according to the label configured to the FEC.

Step S30 specifically includes: and integrating an outgoing label and/or an incoming label distributed to the node equipment for the FEC in a dynamic configuration mode and an outgoing label and/or an incoming label configured to the FEC for the node equipment in a static configuration mode to form an FEC label forwarding table bound by the node equipment, so that the node equipment realizes the forwarding of the message according to the label forwarding table after receiving the message.

In addition, in this embodiment, the following processing is further included after the step S20: and reporting the label configured for the FEC by the node equipment to the upstream node equipment so as to realize dynamic distribution of the label by the upstream node equipment.

In the embodiment of the method for establishing the label forwarding table by the node device, the node device binds the corresponding FEC according to the network application scene in which the node device is located; determining a configuration mode required by the node equipment for the label to be configured of the FEC according to a network application scene where the node equipment is located, and selecting the required configuration mode according to a determination result to configure the corresponding label for the FEC by the node equipment; the configuration mode is as follows: a static configuration mode and/or a dynamic configuration mode; the label includes: entering a label and exiting the label; according to the method for establishing the label forwarding table of the node equipment aiming at the label configured by the FEC, the label forwarding table can be established for the network application scene where the node equipment suitable for static and/or dynamic configuration of the out-label and in-label is located, the network application scene where the node equipment is located is expanded, and the flexibility of the deployment of the label forwarding table in the network is improved.

The invention further provides a node device. Referring to fig. 3, fig. 3 is a functional module diagram of a node device according to the present invention. In this embodiment, the node apparatus 100 includes: binding module 110, configuration module 120, and establishment module 130. The binding module 110 is configured to bind the corresponding FEC according to a network application scenario in which the node device is located. The configuration module 120 is configured to determine, according to a network application scenario in which the node device is located, a configuration mode required by a label to be configured to the FEC, and configure, according to the configuration mode, a corresponding label for the FEC; the configuration mode is as follows: a static configuration mode and/or a dynamic configuration mode; the label includes: label in and label out. The establishing module 130 is configured to establish a label forwarding table of the node device according to the label configured to the FEC.

In this embodiment, the establishing module 130 specifically integrates the outgoing label and/or the incoming label allocated to the FEC by the node device in a dynamic configuration manner and the outgoing label and/or the incoming label configured to the FEC in a static configuration manner to form a label forwarding table of the FEC bound to the node device, so that the node device, after receiving the packet, implements forwarding of the packet according to the label forwarding table.

In addition, in this embodiment, the following processing is further included after the step S20: and reporting the label input configured by the node equipment for the FEC to the upstream node equipment so as to realize dynamic distribution of the label by the upstream node equipment.

Referring to fig. 4, fig. 4 is a schematic diagram of detailed functional modules of the configuration module in fig. 3. In this embodiment, the configuration module 120 includes: a determining unit 121, a first configuration unit. The determining unit 121 is configured to determine, according to a network application scenario in which the node device is located, each label type to be configured to the FEC and a configuration mode required by each label. The first configuration unit 122 is configured to, when there is a first incoming label that needs to be configured in a static configuration manner and there is a second incoming and outgoing label that needs to be allocated in a dynamic configuration manner, configure a corresponding first incoming label for the FEC in the static configuration manner, allocate a corresponding second incoming and outgoing label for the FEC in the dynamic configuration manner, and use the first incoming label and the second incoming and outgoing label as labels configured for the FEC.

In this embodiment, when there is a first incoming label that needs to be configured in a static configuration manner and there is a second incoming and outgoing label that needs to be allocated in a dynamic configuration manner, the specific process of configuring the corresponding first incoming label for the FEC in the static configuration manner by using the first configuration unit 122 is substantially the same as the following manner of configuring the first incoming and outgoing label by using the third configuration unit 124, except that: the configuration commands of the static configuration in and out tags do not have forced effective commands. Because multiple ingress labels can be configured for the same FEC, and only one egress label can be configured for the same egress direction of the same FEC, when the node device in this embodiment allocates a second egress label to the same egress direction of the same FEC through a dynamic configuration manner, the first egress label and the first ingress label configured for the same FEC for the node device in the static LSP instance are not forced to take effect, and the first ingress label and the second ingress label are different, the first egress label is discarded, and the first ingress label and the second egress label are retained as labels configured for the FEC for the node device.

Referring to fig. 5, fig. 5 is a schematic diagram of another detailed functional module of the configuration module in fig. 3. In this embodiment, the configuration module 120 further includes a second configuration unit 123. The second configuring unit 123 is configured to, when there are first outgoing labels and incoming labels that need to be configured in a static configuring manner and second incoming labels that need to be allocated in a dynamic configuring manner, configure corresponding first outgoing labels and corresponding first incoming labels for the FEC in the static configuring manner, allocate corresponding second incoming labels for the FEC in the dynamic configuring manner, and use the first outgoing labels, the corresponding first incoming labels, and the corresponding second incoming labels as labels configured for the FEC.

In this embodiment, when there is a first outgoing label and a first incoming label that need to be configured in a static configuration manner and a second incoming label that needs to be allocated in a dynamic configuration manner, the specific process of configuring, by the node device, the corresponding first outgoing label and the corresponding first incoming label for the FEC in a static configuration manner through the second configuration unit 123 is substantially the same as the following manner of configuring the first outgoing label and the first incoming label by the third configuration unit 124, where the difference is that: the configuration commands of the static configuration in and out tags have no forced effective instruction. In this example, although statically configured outgoing and incoming labels are not forced to be valid, since the second outgoing label is not allocated in a dynamic configuration manner, the first outgoing label, the first incoming label and the second incoming label may be used as labels configured by the node device for the FEC.

Referring to fig. 6, fig. 6 is a schematic diagram of another detailed functional module of the configuration module in fig. 3. In this embodiment, the configuration module 120 further includes a third configuration unit 124. The third configuring unit 124 is configured to configure, when only the first outgoing label and the first incoming label that need to be configured in the static configuration manner exist, the corresponding first outgoing label and first incoming label for the FEC in the static configuration manner, and use the first outgoing label and the first incoming label as the labels configured for the FEC.

In this embodiment, when only the first label that needs to be configured in the static configuration manner exists, the static LSP instance is configured in the static configuration manner through the third configuration unit 124, where the static LSP instance configuration command format is:

mpls static-lsp＜lsp-name＞；

bind ipv4＜prefix＞＜mask＞[force-advertise]；

insegment inlabel{＜in-label＞|explicit-null|implicit-null}；

The "inertia _ label { < in-label > | explicit-null | Implicit

Referring to fig. 7, fig. 7 is a schematic diagram of another detailed functional module of the configuration module in fig. 3. In this embodiment, the configuration module 120 further includes a fourth configuration unit 125. The fourth configuration unit 125 is configured to, when only a second outgoing label and a second incoming label that need to be allocated in a dynamic configuration manner exist, allocate the corresponding second outgoing label and second incoming label to the FEC in the dynamic configuration manner, and use the second outgoing label and the second incoming label as a label configured to the FEC.

In the above embodiments, the manner in which the node device allocates ingress and egress for the bound FEC by using a dynamic configuration manner is the prior art, and a description thereof is not further provided herein.

In the embodiment of the node equipment provided by the invention, the corresponding FEC is bound according to the network application scene where the node equipment is positioned; determining a configuration mode required by the node equipment for the label to be configured of the FEC according to a network application scene where the node equipment is located, and selecting the required configuration mode according to a determination result to configure the corresponding label for the FEC by the node equipment; the configuration mode is as follows: a static configuration mode and/or a dynamic configuration mode; the label includes: entering a label and exiting the label; according to the method for establishing the label forwarding table of the node equipment aiming at the label configured by the FEC, the label forwarding table can be established for the network application scene where the node equipment suitable for static and/or dynamic configuration of the out-label and in-label is located, the network application scene where the node equipment is located is expanded, and the flexibility of the deployment of the label forwarding table in the network is improved.

The following describes the node device and the method for establishing a label forwarding table thereof in further detail through four network application scenario examples.

Example one: referring to fig. 8, fig. 8 is a schematic view of a network application scenario in which the node device of the present invention is located. In fig. 8, downstream node LSR3 of node LSR2 configures label 1 and label 2 for FEC by means of static configuration; node device LSR2 configures local static outgoing label 2 from incoming label 2. The node device LSR2 configures the ingress label 3 for FEC by means of static configuration, enables enforcement, and reports the ingress label 3 to the node device LSR 1. The node device LSR1 matches out the label 3 for FEC in a dynamic manner according to the in-label 3 reported by the node device LSR 2. Node device LSR2 builds its own label forwarding table from out label 2 and in label 3 configured for FEC.

Example two: referring to fig. 9, fig. 9 is a schematic view of another network application scenario in which the node device of the present invention is located. In fig. 9, a downstream node device LSR3 of the node device LSR2 allocates a label 1 and an ingress label 2 to the bound FEC in a dynamic allocation manner, and reports the ingress label 2 to an upstream node device LSR 2. The node device LSR2 allocates label 2 for the bound FEC in a dynamic configuration manner according to label 2 reported by the node device LSR3, and allocates label 3 for the bound FEC in a static configuration manner. Node device LSR1 configures out label 3 and in label 4 for the bound FEC in a static configuration manner. Node device LSR2 builds its own label forwarding table from out label 2 and in label 3 configured for FEC.

Example three: referring to fig. 10, fig. 10 is a schematic view of another network application scenario in which the node device of the present invention is located. In fig. 10, the node device LSR3 configures an ingress label 1 for the bound FEC through a static configuration mode, allocates an ingress label 2 for the FEC through a dynamic configuration mode, and reports the ingress label 2 to the upstream node device LSR1, that is, the ingress label 1 statically configured and the ingress label 2 dynamically allocated in the node device LSR3 take effect at the same time. Downstream node device LSR4 of node device LSR3 configures label 3 for the bound FEC through static configuration; or dynamically configure bound FEC to assign incoming label 4 and report incoming label 4 to upstream device LSR 3. The same egress direction for bound FEC in node device LSR3 configures either a local static egress label 3 from ingress label 3 statically configured by downstream node device LSR4 or dynamically allocates egress label 4 from ingress label 4 reported by downstream node device LSR 4. The node device LSR1 dynamically allocates label 2 according to the label 2 reported by the downstream node device LSR 3. Node device LSR2 configures local static outgoing label 1 from incoming label 1 statically configured by downstream node device LSR 3. The node device LSR3 establishes its own label forwarding table according to the label in 1, 2 and label out 3 configured for the bound FEC; or self label forwarding tables are established for the ingress labels 1, 2 and the egress labels 4 configured for the bound FEC. In the present network application scenario, the node device LSR3 includes two node devices LSR1 and LSR2 at the upstream, and a downstream node device LSR4, so that two in-labels and one out-label need to be configured for bound FEC on the node device LSR 3. Compared with a network application scene comprising one upstream node device and one downstream node device, the method has the advantages that the upstream node device is added to deploy a static or dynamic label forwarding table, and the label forwarding table corresponding to the bound FEC is prolonged. Although the label forwarding table corresponding to the bound FEC is extended in the application scenario of the node device LSR3 in the present network, the forwarding traffic of the original label forwarding table is not affected.

Example four: referring to fig. 11, fig. 11 is a schematic view of another network application scenario in which the node device of the present invention is located. In fig. 10, downstream node device LSR3 of node device LSR2 dynamically configures label 1 for bound FEC and reports label 1 to upstream node device LSR 2. Downstream of node device LSR2, node device LSR4 configures label 2 for bound FEC in a static manner. The node equipment LSR2 dynamically allocates a label 1 for the egress direction of the node equipment LSR3 of the FEC bound by the node equipment LSR2 according to the ingress label 1 reported by the downstream equipment LSR 3; and the label 2 is statically configured according to the label 2 statically configured by the downstream equipment LSR4 and is the label 2 of the self-bound FEC node equipment LSR 4; meanwhile, the incoming label 3 is configured in a static configuration mode, or the incoming label 4 is distributed in a dynamic configuration mode, and the incoming labels 3 and 4 establish own label forwarding tables according to the outgoing labels 1 and 2. In addition, the outgoing labels 1, 2 form a load sharing or FRR relationship on node device LSR 2.

The node device of the invention is a label switching router device.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. A method for node equipment to establish a label forwarding table is characterized in that the method for node equipment to establish the label forwarding table comprises the following steps:

the node equipment binds a corresponding forwarding equivalence class FEC according to a network application scene where the node equipment is located;

2. The method for establishing a label forwarding table by a node device according to claim 1, wherein the step of determining a configuration mode required by a label to be configured to 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 mode includes:

3. The method for establishing a label forwarding table by a node device according to claim 2, wherein the step of determining, by the node device according to a network application scenario in which the node device is located, each label type to be configured to the FEC and a configuration mode required by each label further includes:

and when a first outgoing label and a first incoming label which need to be configured in a static configuration mode exist and a second incoming label which needs to be allocated in a dynamic configuration mode exist, configuring the corresponding first outgoing label and the corresponding first incoming label for the FEC in the static configuration mode, allocating the corresponding second incoming label for the FEC in the dynamic configuration mode, and taking the first outgoing label, the corresponding first incoming label and the corresponding second incoming label as labels configured for the FEC.

4. The method for establishing a label forwarding table by a node device according to claim 2, wherein the step of determining, by the node device, each label type to be configured to the FEC and a configuration mode required by each label according to a network application scenario in which the node device is located further comprises:

5. The method for establishing a label forwarding table by a node device according to claim 2, wherein the step of determining, by the node device, each label type to be configured to the FEC and a configuration mode required by each label according to a network application scenario in which the node device is located further comprises:

6. A node apparatus, characterized in that the node apparatus comprises:

7. The node device of claim 6, wherein the configuration module comprises:

8. The node device of claim 7, wherein the configuration module further comprises:

9. The node device of claim 7, wherein the configuration module further comprises:

10. The node device of any of claims 6 to 9, wherein the configuration module further comprises: