CN111490941B

CN111490941B - Multi-protocol label switching MPLS label processing method and network equipment

Info

Publication number: CN111490941B
Application number: CN202010063496.2A
Authority: CN
Inventors: 魏建军
Original assignee: New H3C Security Technologies Co Ltd
Current assignee: New H3C Security Technologies Co Ltd
Priority date: 2020-01-20
Filing date: 2020-01-20
Publication date: 2022-07-12
Anticipated expiration: 2040-01-20
Also published as: CN111490941A

Abstract

The present disclosure provides a method and a network device for processing a label for multi-protocol label switching, so as to reduce the message processing pressure of a penultimate node and a device of an egress node, and simultaneously avoid the waste of the performance of the egress node. In the disclosure, a penultimate hop node acquires a first parameter value related to the bearing capacity of the penultimate hop node; the penultimate hop node determines a first message for executing public network label pop-up by an outgoing node and a second message for executing public network label pop-up by the penultimate hop node according to the first parameter value; when the penultimate node receives a first message carrying a public network label, the penultimate node sends the first message to an egress node so that the egress node executes a public network label pop-up operation on the first message; and when the node of the last but one hop receives a second message, the node of the last but one hop executes public network label pop-up operation on the second message.

Description

Multi-protocol label switching MPLS label processing method and network equipment

Technical Field

The present disclosure relates to network communication technologies, and in particular, to a method for processing a multi-protocol label switching MPLS label and a network device.

Background

In a Multi-Protocol Label Switching (MPLS) network, a network device forwards a packet according to a short and fixed-length Label, thereby omitting a cumbersome process of searching an IP routing table and providing a high-speed and efficient manner for data transmission in a backbone network.

However, when the MPLS technology is used to implement packet forwarding, there is a certain risk. The public network label forwarding table is used as an end device connected with the IP network, namely the output node egress needs to query the public network label forwarding table of the message, and the IP forwarding table also needs to be queried after the public network label is popped up. The two query operations have strong requirements on the performance of the equipment, and simultaneously cause the risk of high-load operation of the equipment.

To solve the above risk, a PHP (peer Hop Popping) mechanism is commonly used, but the PHP mechanism may cause waste of the egress performance.

Disclosure of Invention

The disclosure provides a multiprotocol label switching (MPLS) label processing method and network equipment, which are used for reducing the message processing pressure of a penultimate node and equipment of an output node and avoiding the waste of the performance of the output node.

A first aspect of the present disclosure provides an MPLS label processing method, which is applied to an MPLS network including an Egress node Egress and a penultimate node, and the method includes:

a node of the last but one hop obtains a first parameter value related to the bearing capacity of the node of the last but one hop;

the penultimate hop node determines a first message for executing public network label pop-up by an outgoing node and a second message for executing public network label pop-up by the penultimate hop node according to the first parameter value;

when the penultimate node receives a first message carrying a public network label, the penultimate node sends the first message to an egress node so that the egress node executes a public network label pop-up operation on the first message;

and when the node of the last but one hop receives a second message, the node of the last but one hop executes public network label pop-up operation on the second message.

A second aspect of the present disclosure provides a network device, which is applied to an MPLS network, and includes: the device comprises an acquisition unit, a determination unit, a receiving unit, a sending unit and a label ejection unit;

the acquiring unit is used for acquiring a first parameter value related to the bearing capacity of a node of the last but one hop;

the determining unit is used for determining a first message for executing public network label pop by an egress node and a second message for executing public network label pop by the penultimate hop node according to the first parameter value;

the sending unit is used for sending a first message carrying a public network label to an egress node when the receiving unit receives the first message so as to enable the egress node to execute a public network label pop-up operation on the first message;

and the label popping unit is used for executing public network label popping operation on the second message when the receiving unit receives the second message.

According to the method and the network equipment provided by the disclosure, the label popping is not performed singly, or a PHP mechanism or an outgoing node is adopted to pop the public network label, but the operation of label popping is dynamically shared to different equipment according to the bearing capacity of the equipment, so that the message processing pressure of the penultimate node and the equipment of the outgoing node can be reduced, and the waste of the performance of the outgoing node can be avoided.

Drawings

FIG. 1 is a diagram of an application networking provided by an embodiment of the present disclosure;

FIG. 2 is a flow chart of a method provided by an embodiment of the present disclosure;

FIG. 3 is a flow chart of a method provided by yet another embodiment of the present disclosure;

FIG. 4 is a flow chart of a method provided by yet another embodiment of the present disclosure;

fig. 5 is a block diagram of a network device provided by the present disclosure.

Detailed Description

Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers can indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the subject matter of the present disclosure.

For better understanding of the technical solutions of the present disclosure, the basic concepts of the prior art related to the present disclosure are introduced herein.

(1) A Label Switching Router LSR (LSR) is a device with Label distribution capability and Label Switching capability, and is a basic element in an MPLS network.

(2) An MPLS network includes the following components:

an Ingress node Ingress, LSR, of the message, responsible for adding a label to the message entering the MPLS network;

the intermediate node Transit is an LSR in the MPLS network and transmits a message to an export LSR along a label switching path formed by a series of LSRs according to a label;

and Egress node Egress, namely, an Egress LSR of the message, is responsible for stripping the label in the message and forwarding the label to a destination network.

(3) Forward Equivalence Class FEC (Forwarding Equivalence Class, abbreviated FEC): MPLS classifies packets with the same characteristics into one class, called FEC, and packets belonging to the same FEC will get exactly the same processing in MPLS networks.

(4) In order to solve the high load pressure of the egress node egr device in the MPLS network, a Penultimate Hop pop PHP (short for PHP) mechanism is generally adopted in the prior art.

There are two kinds of labels in PHP mode:

first, an implicit null label takes a value of 3. When an LSR finds that a label announced by a downstream LSR is an implicit empty label, the LSR does not replace the original label at the top of the stack with the value, but directly pops up the label and forwards the message to the downstream LSR (i.e. Egress), and after the Egress receives the message, the Egress directly carries out the forwarding processing of the next layer;

one is an explicit null tag, which takes the value 0. In some cases, Egress needs to determine a Quality of Service (QoS) policy according to information such as a traffic level in a label stack, and at this time, by displaying an empty label, forwarding processing of Egress nodes can be simplified while information of the label stack is retained. After Egress allocates an explicit empty label to FEC and advertises the empty label to the upstream LSR, the upstream LSR replaces the original label at the top of the stack with the value, and forwards the packet to the downstream LSR (i.e., Egress). When the Egress receives the message with the label value of 0, the forwarding table of the label is not searched, and after information such as the traffic level and the like is obtained from the label, the label stack is directly popped up for forwarding processing of the next layer.

(5) The Private Network label is used to indicate which site the message is sent to, and the Network device may determine a Virtual Private Network (VPN) instance to which the message belongs according to the Private Network label, and correctly forward the message to the corresponding site by looking up a routing table of the VPN instance.

Some of the novel concepts to which this disclosure relates will be explained in detail in the following examples.

Example one

In the prior art, on the premise of considering the requirements of actual economic cost and networking performance, generally, the processing performance of an output node is obviously higher than that of an intermediate node. The simple operation of MPLS label popping is performed by the intermediate node, that is, a mechanism of the next to last hop popping is adopted, so that under the condition of huge service, not only the network security may be affected, but also the waste of the processing performance of the egress node may be caused. If the egress node only performs the operation of popping the MPLS label, the risk of high-load operation of the device may also be caused. In the method provided by this embodiment, the label pop of the public network can be shared by the penultimate hop node and the egress node according to the carrying capacity of the penultimate hop node and the egress node, so that the waste of the performance of the egress node can be avoided, and the risk of high-load operation of the egress node can also be avoided.

The method provided by the present disclosure may be applied to an MPLS network, and for better understanding of the method provided by the present disclosure, the present disclosure explains the method by taking the networking of fig. 1 as an example. It should be understood, however, that fig. 1 is merely a simplified schematic illustration of the networking, and that actual networking may be more complex than that of fig. 1, without affecting the implementation of the present method. Fig. 1 is a schematic networking diagram of an MPLS network provided by the present disclosure, and as shown in fig. 1, the MPLS network includes an Egress node Egress and an intermediate node, and a previous-hop node of the Egress node is referred to as a penultimate-hop node in this embodiment. In fig. 1, the egress node includes R1 and R2, where R1 is associated with VPN instance 1 and VPN instance 2, where VPN instance 1 is associated with site1, VPN instance 2 is associated with site2, and VPN instance 10 is associated with site 10.

A sharing mode for label popping may be configured for the penultimate hop node and the egress node, and in the sharing mode, the penultimate node and the egress node may cooperate with each other to execute the method provided in this embodiment, and in an initial state, it is assumed that the penultimate node pops a public network label, as shown in fig. 2, the method includes: step 101-step 104.

In step 101, a node of the last but one hop obtains a first parameter value related to the bearing capacity of the node of the last but one hop.

The parameter related to the carrying capacity may be any one of a Central Processing Unit (CPU) idle rate, a memory idle rate, and a temperature of the CPU. Parameters related to the load-bearing capacity can also be understood in a broad sense as parameters that influence the stability of the device.

The last second hop node may periodically obtain a first parameter value related to the bearer capability of the last second hop node.

In an embodiment, as shown in fig. 2, after the penultimate hop node periodically obtains the first parameter value, step 100 may be executed, and if the first parameter value reaches a preset sharing mode trigger threshold, a sharing request is sent to the egress node to request the egress node to share the pop operation of the public network label.

After receiving the sharing request, the egress node may determine whether to bear the pop-up of the public network label according to a load condition of the egress node, and if so, send a sharing request response to the penultimate hop node.

The egress node may carry label information of the egress node in the sharing request response, so that the penultimate hop node uses the label information of the egress node as an egress label of a packet in which the next hop is the egress node. For example, if the label information of the egress node carried in the sharing request response by the egress node is 50, the penultimate hop node determines that the label is 50, so that the corresponding next-hop device is the egress node.

If the outbound node cannot share the popping of the public network label, no response is made, or the label information of the outbound node carried in the sharing request response is null. Correspondingly, the penultimate hop node does not receive the sharing request response of the egress node in the preset time, or identifies that the tag information of the egress node carried in the sharing request response is null, and then the penultimate hop determines that the corresponding egress node cannot share the popup of the public network tag.

In an optional implementation manner, the penultimate hop node may set a load sharing request field of a hello packet of a Label Distribution Protocol LDP (Label Distribution Protocol, abbreviated as LDP) to 1, so as to trigger the node to determine whether the node can share an pop-up operation of a public network Label. Wherein, the load sharing request field can be implemented by using a custom field in the hello message.

In order to better understand the method proposed by the present disclosure, the parameters related to the bearer capability are described as the CPU idle rate in this embodiment.

In the corresponding relationship between the parameter values in different ranges and the public network label pop-up ratio included in table 1, taking the parameter value related to the carrying capacity as the CPU idle rate as an example for explanation, table 1 may be configured on the node of the last but one hop at the time of initial configuration.

TABLE 1

And 102, determining a first message for executing public network label popup by the node according to the first parameter value and a second message for executing public network label popup by the node according to the node of the last but one hop.

In one embodiment, as shown in fig. 3, step 102 may be implemented by a method from step 1021 to step 1024.

And step 1021, the node of the last but one hop determines an outgoing node which shares the popping of the public network label, and counts the private network label of the message of which the public network label points to the outgoing node.

For step 1021, the penultimate node may send a sharing request to the egress node as introduced in step 101, and determine the egress node popped up by the sharing public network label according to the received sharing request response mode. Details are not repeated in this step. Of course, in another alternative embodiment, the penultimate node may also share the pop-up of the public network label by using a pre-configured fixed outgoing node.

After determining the output node which shares the public network label pop-up, the node of the last but one hop can periodically sample the public network label and the private network label of the public network label message of the received message. Therefore, the penultimate node can establish the corresponding relation between the public network label and the private network label. And the penultimate hop node only acquires the private network label of the message of the outgoing node which is determined by the public network label direction and can be used for popping up and sharing the public network label.

For example, as shown in fig. 1, if the penultimate hop node sends a sharing request to the egress nodes R1 and R2, and if the egress nodes R1 and R2 both send a sharing request response to the penultimate node, R1 carries the public network tag a pointing to R1 in the sharing request response, and R2 carries the public network tag B pointing to R2 in the sharing request response, so that the penultimate node may determine that the egress nodes popped up by the sharing public network tags are R1 and R2.

And when the penultimate node determines that the public network label of the received message is a public network label pointing to R1, acquiring a private network label carried by the message, and further establishing a corresponding relation table of the public network label and the private network label. And when the penultimate node determines that the public network label of the received message is a public network label pointing to R2, acquiring a private network label carried by the message, and further establishing a corresponding relation table of the public network label and the private network label.

For example, if the public network tag pointing to R1 is a, it is determined that the VPN instance to which the message belongs is VPN instance 1 according to private network tag 0001, the private network tag 0002 determines that the VPN instance to which the message belongs is VPN instance 2 … …, the private network tag 0010 determines that the VPN instance to which the message belongs is VPN instance 10, the public network tag pointing to R2 is B, R2 is associated with VPN instance 11 and VPN12 (not shown in fig. 1), VPN instance 11 is associated with site11, and VPN instance 12 is associated with site 12. The penultimate node may establish a table of public network label to private network label correspondence as shown in table 2-1.

Public network label	Private network label
		A	0001
A	0002
		A	……
A	0010
		B	0011
B	0012

TABLE 2-1

It should be noted that, the public network tag pointing to R1 in this embodiment means that, when the penultimate node recognizes that the outgoing label of the packet is the tag, the corresponding next hop is R1, that is, pointing to R1.

And 1022, determining the proportion of the message for executing the public network label popup by the penultimate hop node according to the first parameter value and the corresponding relation by the penultimate hop node, wherein the corresponding relation comprises the corresponding relation between the parameter values in different ranges and the proportion for executing the public network label popup by the equipment on the message.

And 1023, determining a first private network label of the message to be popped up by the penultimate node to bear the public network label according to the proportion of the message and the type quantity of the private network labels.

For steps 1022 and 1023, taking the corresponding relationship in table 1 as an example, the first parameter value that the penultimate hop node can acquire and the corresponding relationship in table 1, for example, determine the proportion of the message that the R1 pops up the public network label.

For example, if the CPU idle rate of the penultimate hop node is 90%, it may be determined according to table 1 that the ratio of the penultimate hop node bearing the public network label pop is maintained in the processing default state, and in the embodiment related to the present disclosure, the penultimate hop node initially bears 100% of the public network label pop by default. If the CPU idle rate of the penultimate hop node is 50%, it can be determined according to table 2-1 that the node performs public network label pop-up by 50%, in the example in step 1021, the types of the private network labels corresponding to the public network label a pointing to R1 are 10, and then the penultimate hop node can undertake pop-up of the public network label corresponding to 5/10 (i.e., 50%) private network labels. The type of the private network label corresponding to the public network label B pointing to R2 is 2, and the penultimate node can undertake the pop-up of the public network label corresponding to the private network label of 1/2.

Specifically, the penultimate hop node may undertake the pop-up of the public network label of a message with a public network label of a, a private network label of 0001-. Here, "corresponding" means that the next hop of the packet with the public network label a is R1, and the packet is correspondingly forwarded to R1, and the next hop of the packet with the public network label B is R2, and the packet is correspondingly forwarded to R2.

Further, step 1022 may be performed before, simultaneously with or after the step of counting the private network labels in step 1011.

Step 1024, when the public network tag carried by the received message is the first public network tag and the private network tag is the first private network tag, determining that the message is the second message, wherein the first public network tag is the public network tag pointing to the outgoing node popped up by the sharing public network tag.

Namely, the public network label is A, the private network label is the message of 0001-0005, the message is a second message, and the second message is the message type to be subjected to public network label pop-up by the penultimate hop node.

In an optional implementation manner, after the second message is determined, a message mark is added to the determined second message in the correspondence between the public network tag and the private network tag. For example, as shown in table 2-2, a message flag is set to 1 to indicate that a message flag is added, and set to 0 to indicate that no message flag is added.

Tables 2 to 2

The purpose of adding the label is to send the message to the output node when the penultimate node recognizes that the public network label and the private network label of the received message are different from the message with the message label in the corresponding relationship (namely, the received message is determined to be the first message), and to modify the public network label of the second message into an implicit null label or a display null label by the penultimate node when the penultimate node recognizes that the public network label and the private network label of the received message are the same as the message with the message label in the corresponding relationship (namely, the received message is determined to be the second message), so that the penultimate node executes public network label pop-up operation on the second message.

103, when the penultimate node receives a first message carrying a public network label, the penultimate node sends the first message to an egress node, and the egress node executes a public network label pop-up operation on the first message.

And 104, when the node of the last but one hop receives a second message, the last but one hop executes public network label pop-up operation on the second message.

For step 103 and step 104, when implemented specifically, the following manner shown in fig. 4 may be employed for implementation:

step 2030, judging whether the received message is a second message, where the public network label of the second message is a public network label of a public network label pointing to the egress node popped up by the sharing public network label, and the private network label is the first private network label; if the message is the second message, execute step 2032, otherwise execute step 2031

Step 2031, the penultimate hop node sends the first message to the outgoing node, and the outgoing node executes public network label pop-up operation on the first message, wherein the first message is the message for which the penultimate hop node is responsible for public network label pop-up operation before load sharing;

step 2032, if the received message is a second message which is not the first message, the penultimate hop node executes the pop-up operation of the public network label.

In the method provided by this embodiment, the label pop-up is no longer a single mechanism, that is, a PHP mechanism or a mechanism for popping up the public network label by using the egress node, but the operation of label pop-up is dynamically shared to different devices according to the carrying capacity of the devices, so that the message processing pressure of the penultimate node and the device of the egress node can be reduced, and the waste of the performance of the egress node can be avoided.

Example two

On the basis of the first embodiment, as shown in fig. 4, the MPLS label processing method provided in this embodiment may further include: step 105 and step 106.

And 105, determining the priority of the node of the second last hop according to the first parameter value and a mapping relation by the node of the second last hop, wherein the mapping relation comprises the mapping relation between the parameter values in different ranges and the priority of the equipment.

Table 3 includes the mapping of different ranges of parameter values to device priorities.

TABLE 3

Wherein Normal denotes the default priority of the initial configuration. Normal has a priority lower than level 1. In this embodiment, the larger the level number is, the larger the priority is. Example (c): level4> level 1.

And 106, sending the priority of the node of the penultimate hop to the output node so that the output node determines whether to send a sharing request response to the node of the penultimate hop according to the priority information.

Specifically, if the egress node determines that the priority of the node of the penultimate hop is greater than the priority of the egress node, it indicates that the CPU idle rate of the node of the penultimate hop is low at this time, that is, the CPU utilization rate is high, and in order to reduce the CPU utilization rate of the node of the penultimate hop, the egress node may send a sharing request response to the node of the penultimate hop.

If the egress node determines that the priority of the node of the second to last hop is lower than the priority of the egress node, the egress node may not send the sharing request response to the node of the second to last hop, or the tag of the egress node carried in the sharing request response is null.

For example, if the CPU idle rate determined by the penultimate node is 15%, at this time, the device priority determined according to the mapping relationship is level4, and the penultimate node may send the priority information to the egress node R1, that is, the egress node R1 determined in step 1021 and capable of sharing the public network label is determined.

The output node R1 may obtain a second parameter value related to the carrying capacity of the output node R1, and the output node determines the device priority corresponding to the output node R1 according to the mapping relationship between the parameter values in different ranges and the device priority.

TABLE 4

If the CPU idle rate of the output node R1 is 80%, the priority of the output node R1 is leave 1l, and the priority of the next to last node is level4, which is higher than the priority of the output node R1. At this time, the egress node may send a sharing request response to the penultimate node.

In the process of load sharing for popping the public network label, because the parameter value related to the bearing capacity of each device is constantly changed, the CPU utilization rate of the node is high, and the operation of popping the public network label needs to be shared to the node of the last but one hop for processing.

For the above situation, an optional implementation:

the penultimate node can receive the priority of the output node sent by the output node;

when the priority of the out-node is greater than the priority of the penultimate node, the penultimate node is triggered to execute step 102.

In order to avoid frequent sharing switching of public network label pop-up by the device, in another optional implementation manner, the penultimate hop node may receive the priority of the egress node sent by the egress node; when the priority of the output node is higher than the priority of the penultimate node by two levels or more, the penultimate node is triggered to execute step 102. The steps following step 102 are further performed.

In this embodiment, the step 102 is triggered to be executed again only when the difference between the priorities of the egress node and the node of the second last hop is greater than or equal to two or more than two, that is, the adjustment of load sharing is triggered again.

In an optional implementation manner, the priority information may be sent between the egress node and the penultimate hop node through a Label Distribution Protocol (LDP) hello packet.

In this embodiment, table 4 may be stored in the same table as table 2-1, and configured in the next to last node in advance. The egress node is also configured with the corresponding relationship and mapping relationship as in tables 2-1 and 4, and the principle is similar, which is not described again in this embodiment.

EXAMPLE III

In order to better explain the technical solution of the present disclosure, the present embodiment describes the above method with a specific implementation manner.

(1) The initial state defaults to the situation that a penultimate hop node performs label pop-up operation on a public network label:

as shown in fig. 1, the egress nodes R1 and R2 receive LDP hello packets sent by a penultimate node, where the priority level of the penultimate device is carried in the hello packet. If the exit node R2 determines that the priority of the penultimate node is lower than its own priority level, it is not necessary to send a response packet to the penultimate node.

If the exit node R1 determines that the priority of the penultimate node is higher than the priority level of the exit node itself, it indicates that the CPU utilization rate of the penultimate node is higher than that of R1, and in order to reduce the CPU utilization rate of the penultimate node, the exit node R1 sets the load sharing request field in the LDP hello packet to 1.

When the load sharing request field in the hello field received by the penultimate node is set to 1, the penultimate node starts to collect the private network label of the message leading to the egress node R1, further determines a second message to be subjected to public network label popup by the penultimate node according to the corresponding relation shown in the table 2-1 and the type number of the private network label, and sends the rest messages to the egress node for public network label decapsulation, wherein the original public network label is reserved for the rest messages.

When the penultimate hop node receives a message with a level higher than the level 2 of the penultimate node and higher than the level 2 of the penultimate node in the LDP hello message sent by the exit node R1, the load sharing adjustment is triggered again, at the moment, the penultimate node actively sets the load sharing request field in the hello message to be 1, after receiving the hello message, the exit node R1 searches the storage mapping relation of the penultimate node, determines the priority level corresponding to the CPU utilization rate of the node R1, and judges the public network label pop-up proportion which can be born according to the corresponding relation stored by the penultimate node.

The egress node R1 may notify the penultimate node through a private protocol packet, and the penultimate node may collect a private network label of a packet leading to the egress node R1, then determine a second packet popped up by the penultimate node of a public network label according to the above-mentioned pop-up ratio, change the public network label of the second packet into an implicit null label or a display null label, and send the rest of the packets to the egress node for public network label decapsulation, while the rest of the packets retain the original public network label.

(2) The initial state defaults that the node of the last but one hop does not carry out the operation of popping the public network label, and under the condition that the node carries out the operation of popping the public network label:

the penultimate node receives hello messages sent by node equipment R1 and R2, and if the level carried in the hello messages sent by R1 is higher than the priority level of the penultimate node, which indicates that the CPU utilization rate of the node R1 is high, the penultimate node actively sets the load sharing request field in the hello messages to be 1.

When the load sharing request field in the hello message received by the egress node R1 is set to 1, the egress node R1 searches for the correspondence stored therein, and determines the public network tag pop-up ratio corresponding to the CPU utilization of the current egress node R1. And the penultimate node collects a private network label leading to the output node R1, then determines a second message subjected to public network label pop by the penultimate node according to the pop proportion, changes the public network label of the second message into an implicit null label or a display null label, and transmits the rest messages to the output node for public network label decapsulation after keeping the original public network label.

When the egress node R1 receives an LDP hello message sent by a penultimate node, the level of the LDP hello message is higher than the level of the egress node R1, the CPU utilization rate of the penultimate node is higher, in order to reduce the CPU utilization rate of the penultimate node, the egress node R1 sets a load sharing request field of the LDP hello message to be 1 and sends the LDP hello message to the penultimate node, after the penultimate node receives the hello message with the load sharing request field set to be 1, the private network label leading to the egress node R1 can be collected, the CPU utilization rate of the egress node is obtained, the penultimate node determines a second message popped up by public network labels of penultimate equipment according to the corresponding relation of the table 2-1 stored in the penultimate node and the mapping relation of the table 4, and the rest messages keep the original public network labels and send the original public network labels to the egress node for public network label decapsulation.

Example four

The present embodiment also provides a network device, which can be used to execute any one of the methods provided in the above-mentioned implementations one to three. Fig. 5 is a schematic structural diagram of a network device according to an embodiment of the present disclosure, where the network device includes a network that can be applied to an MPLS network, and as shown in fig. 5, the network device includes: an acquisition unit 501, a determination unit 502, a reception unit 503, a transmission unit 504, and a label ejection unit 505;

the obtaining unit 501 is configured to obtain a first parameter value related to a bearing capacity of a node of a next to last hop;

the determining unit 502 is configured to determine, according to the first parameter value, a first packet for performing public network label pop by an egress node and a second packet for performing public network label pop by the penultimate node;

the sending unit 504 is configured to send, when the receiving unit 503 receives a first packet carrying a public network label, the first packet to an egress node, so that the egress node performs a public network label pop-up operation on the first packet;

and a label pop-up unit 505, configured to, when the receiving unit receives the second message, perform a public network label pop-up operation on the second message.

In the network device provided by this embodiment, the label pop-up is no longer a single mechanism that pops up the public network label, either by using a PHP mechanism or by using an outgoing node, but dynamically shares the operation of label pop-up to different devices according to the carrying capacity of the devices, so that the message processing pressure of the penultimate node and the outgoing node devices can be reduced, and the waste of the outgoing node performance can be avoided.

The obtaining unit 501 is further configured to determine whether the first parameter value reaches a preset sharing mode trigger threshold according to the first parameter value, and send a sharing request to the sending unit 504 when the first parameter value reaches the trigger threshold; the sending unit 504 is further configured to send a sharing request to the egress node to request the egress node to share the pop-up operation of the public network label;

after receiving the sharing request response sent by the egress node, the receiving unit 503 triggers the determining unit to execute a first packet for determining that the egress node executes public network label pop-up and a second packet for executing public network label pop-up by the penultimate hop node according to the first parameter value.

The determining unit 502 is further configured to determine an egress node that shares the pop-up of the public network label, and count a private network label of a packet of which the public network label points to the egress node; the determining unit 502 determines, according to the first parameter value and a corresponding relationship, a ratio of a message in which the penultimate hop node performs public network label pop-up, where the corresponding relationship includes a corresponding relationship between parameter values in different ranges and a ratio of a device performing public network label pop-up on the message; determining a first private network label of a message to be popped by a penultimate hop node to bear a public network label according to the proportion of the message and the variety number of the private network labels;

the determining unit 502 is further configured to determine that the packet is a second packet when a public network tag carried in the packet received by the receiving unit is a first public network tag and a private network tag is the first private network tag, where the first public network tag is a public network tag pointing to an egress node popped from the shared public network tag.

The determining unit 502 is further configured to determine the priority of the penultimate hop node according to the first parameter value and a mapping relationship, where the mapping relationship includes mapping relationships between parameter values in different ranges and device priorities;

the sending unit 504 is further configured to send the priority of the penultimate hop node to the egress node, so that the egress node determines whether to send a sharing request response to the penultimate hop node according to the priority information.

The receiving unit 503 is further configured to receive the priority of the egress node sent by the egress node; the determining unit 502 is further configured to, when it is determined that the priority of the egress node is greater than the priority of the penultimate hop node, perform determining, according to the first parameter value, a first packet in which the egress node performs public network label pop and a second packet in which the penultimate node performs public network label pop.

It should be noted that the basic principle and the generated technical effect of the network device provided in the embodiment of the present disclosure are the same as those of the methods in the first to third embodiments, and for brief description, reference may be made to the description contents of the methods mentioned above for the parts that are not mentioned in this embodiment.

In the embodiments provided in the present disclosure, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus embodiments described above are merely illustrative, and for example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In addition, functional modules in the embodiments of the present disclosure may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

The functions, if implemented in the form of software functional modules and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solution of the present disclosure or portions thereof that contribute to the prior art in essence can be embodied in the form of a software product, which is stored in a readable storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method described in the embodiments of the present disclosure. And the aforementioned readable storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above description is only exemplary of the present disclosure and should not be taken as limiting the disclosure, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present disclosure should be included in the scope of the present disclosure.

Claims

1. A multiprotocol label switching (MPLS) label processing method is applied to an MPLS network, and is characterized in that the MPLS network comprises an Egress node Egress and a penultimate node, and the method comprises the following steps:

when the node of the last but one hop receives a second message, the node of the last but one hop executes public network label pop-up operation to the second message;

when the penultimate node receives a first message carrying a public network label, the penultimate node sends the first message to a corresponding outgoing node so that the outgoing node executes a public network label pop-up operation on the first message.

2. The method of claim 1, further comprising:

the penultimate hop node determines that the first parameter value reaches a preset sharing mode trigger threshold according to the first parameter value, and then sends a sharing request to the output node to request the output node to share the popping operation of the public network label;

and after receiving a sharing request response sent by the output node, the penultimate hop node triggers and executes the steps of determining a first message for executing public network label popup by the output node and a second message for executing the public network label popup by the penultimate hop node according to the first parameter value.

3. The method according to claim 1 or 2, wherein the determining, by the penultimate hop node, the second packet for performing public network label pop by the penultimate hop node according to the first parameter value comprises:

the penultimate node determines an output node which shares the public network label pop-up, and counts a private network label of a message of which the public network label points to the output node;

the penultimate hop node determines the proportion of the message for executing the public network label pop-up by the penultimate hop node according to the first parameter value and the corresponding relation, wherein the corresponding relation comprises the corresponding relation between the parameter values in different ranges and the proportion for executing the public network label pop-up by the equipment on the message;

determining a first private network label of a message to be popped by a penultimate hop node to bear a public network label according to the proportion of the message and the type number of the private network labels;

and when the public network label carried by the received message is a first public network label and the private network label is the first private network label, determining that the message is a second message, wherein the first public network label is a public network label pointing to the output node popped up by the sharing public network label.

4. The method according to claim 1 or 2, characterized in that the method further comprises:

the penultimate node determines the priority of the penultimate node according to the first parameter value and a mapping relation, wherein the mapping relation comprises the mapping relation between parameter values in different ranges and equipment priority;

and sending the priority of the node of the last but one hop to the output node so that the output node determines whether to send a sharing request response to the node of the last but one hop according to the priority information.

5. The method of claim 4, further comprising:

receiving the priority of the output node sent by the output node by the node with the second last hop;

and when the priority of the exit node is greater than that of the penultimate hop node, triggering the penultimate hop node to execute a step that the penultimate hop node determines a first message for executing public network label popup by the exit node and a second message for executing public network label popup by the penultimate hop node according to the first parameter value.

6. A network device, wherein the network device is a network device applied to an MPLS network, and the network device comprises: the device comprises an acquisition unit, a determination unit, a receiving unit, a sending unit and a label ejection unit;

7. The network device of claim 6,

the obtaining unit is further configured to determine whether the first parameter value reaches a preset sharing mode trigger threshold according to the first parameter value, and send a sharing request to the sending unit when the first parameter value reaches the trigger threshold; the sending unit is further configured to send a sharing request to the egress node to request the egress node to share the pop-up operation of the public network label;

and after receiving a sharing request response sent by an egress node, the receiving unit triggers the determining unit to execute a first message for determining that the egress node executes public network label pop-up and a second message for executing the public network label pop-up by the penultimate hop node according to the first parameter value.

8. The network device of claim 6 or 7,

the determining unit is also used for determining an output node for sharing the public network label ejection, and counting the private network label of the message of the public network label pointing to the output node; the determining unit determines the proportion of the message for executing the public network label popup by the penultimate hop node according to the first parameter value and a corresponding relation, wherein the corresponding relation comprises the corresponding relation between parameter values in different ranges and the proportion of the equipment executing the public network label popup on the message; determining a first private network label of a message to be popped by a penultimate hop node to bear a public network label according to the proportion of the message and the type number of the private network labels;

the determining unit is further configured to determine that the packet is a second packet when the public network tag carried in the packet received by the receiving unit is a first public network tag and the private network tag is the first private network tag, where the first public network tag is a public network tag pointing to an egress node popped up by the sharing public network tag.

9. The network device of claim 6 or 7,

the determining unit is further configured to determine a priority of a penultimate hop node according to the first parameter value and a mapping relationship, where the mapping relationship includes mapping relationships between parameter values in different ranges and device priorities;

the sending unit is further configured to send the priority of the penultimate hop node to the egress node, so that the egress node determines whether to send a sharing request response to the penultimate hop node according to the priority information.

10. The network device of claim 9,

the receiving unit is further configured to receive a priority of the egress node sent by the egress node;

the determining unit is further configured to determine, according to the first parameter value, a first packet for performing public network label pop by the egress node and a second packet for performing public network label pop by the penultimate hop node when it is determined that the priority of the egress node is greater than the priority of the penultimate hop node.