CN103856403A - Message control method and apparatus - Google Patents

Abstract

An embodiment of the present invention provides a packet control method, the method comprising: a first PE in a backbone operator network determines a first LSP between a first node in a first customer operator and the first PE Whether it is available, the first LSP ends at the first node; when it is determined that the first LSP is unavailable, the first PE sends a message indicating that the first LSP is unavailable to the second PE in the backbone operator the first notification message, so that the second PE stops establishing the LSP with the second customer operator. Through this solution, unnecessary establishment of LSPs can be controlled, and system overhead on LSPs can be reduced.

Description

Message control method and device

technical field

The present invention relates to the communication field, in particular to a message control method and device.

Background technique

As shown in Figure 1, in the carrier's carrier (carrier's carrier) solution in the prior art, the customer equipment (Customer Edge, CE) of the backbone operator and the provider edge device (Provider Edge, PE) of the backbone operator ) using Internal Gateway Protocol (Internal Gateway Protocol, IGP) + Label Distribution Protocol (Label Distribution Protocol, LDP). The PEs within the backbone operator use the Border Gateway Protocol (BGP) to publish the routes and labels of the customer operator. The PE equipment of the customer operator, that is, the customer provider edge (C-PE) equipment in Figure 1, in order to provide its customers with virtual private network (Virtual Private Network, VPN) services , it is necessary to establish a label switching path (LabelSwitch Path, LSP) from the upstream C-PE2 of the second customer operator to the downstream C-PE1 of the first customer operator.

The internal network of the backbone operator and the IGP+LDP protocol run between the customer equipment CE1 and the backbone operator PE1. On PE1, both protocols belong to a Virtual Routing and Forwarding (VRF). An LSP from PE1 to C-PE1 is established through LDP. PE1 learns the route to C-PE1 through IGP.

The VRF instance on the PE1 device of the backbone operator imports the IGP route in the VRF instance into the BGP VPN, and uses BGP to advertise the route of the customer operator (the route from CE1 to C-PE1) to PE2 of the remote backbone operator equipment. When BGP advertises private network routes, it assigns a label to each route in the label-per-route manner, and advertises the route and the label assigned to the route to PE2 through BGP. PE1 performs label exchange between the label of the route allocated by CE1 to PE1 through LDP and the label locally allocated by PE1 for the route.

On PE2, after receiving the VPN route of PE1, it will import the route into IGP, trigger LDP to distribute labels to the CE2 device of the second upstream customer operator, and at the same time combine the distributed label with the route received from PE1 through BGP tags for tag switching. Finally, an end-to-end LSP from C-PE2 to C-PE1 is formed.

When C-PE2 needs to iterate VPN services to a certain tunnel, if the downstream LDP is interrupted, C-PE2 on the upstream side cannot perceive that the tunnel is unavailable, cannot perform route convergence, and cannot switch traffic to other normal tunnels, which will cause traffic interruption. Moreover, when the downstream only needs to establish LSPs for a small number of prefixes, label and LSP resources will be wasted because the upstream cannot distinguish them.

Contents of the invention

The present invention provides a message control method to solve the problem that in the prior art, the provider edge device of the downstream customer operator cannot perceive whether the upstream customer operator's route is available, so that unnecessary LSP establishment cannot be controlled, and the system's impact on the system is reduced. The problem of LSP overhead.

In a first aspect, an embodiment of the present invention provides a message control method, the method comprising:

The first PE in the backbone operator's network determines whether a first LSP between a first node in a first customer operator and the first PE is available, and the first LSP terminates at the first node;

When it is determined that the first LSP is unavailable, the first PE sends a first notification message indicating that the first LSP is unavailable to the second PE in the backbone operator, so that the second PE stops communicating with the first LSP. An LSP between two customer operators is established.

In a first possible implementation manner of the first aspect, the first PE in the backbone operator network determines the first LSP between the first node in the first customer operator and the first PE Availability includes:

When the first PE does not receive the label used to establish the first LSP within a predetermined time, determine that the first LSP is unavailable.

In the second possible implementation manner of the first aspect, a second possible implementation manner of the first aspect is also provided, the first notification message includes a The identity of the label assigned to establish the first LSP.

In a third possible implementation of the first aspect according to the first aspect or the first possible implementation of the first aspect or the second possible implementation of the first aspect , the first notification message is used to notify the second PE to avoid allocating labels for establishing a second LSP to equipment in the second customer operator connected to the second PE, and the second LSP is An LSP starting from the second node in the second customer operator, ending at the first node and passing through the first LSP.

In the fourth possible implementation manner of the first aspect according to any one of the first possible implementation manner of the first aspect to the third possible implementation manner of the first aspect, the The first PE receives the label used to establish the first LSP through a label distribution protocol LDP.

In the fifth possible implementation of the first aspect according to any one of the first possible implementation of the first aspect to the third possible implementation of the first aspect, when it is determined When the first LSP is unavailable, the first PE sends a first notification message that the first LSP is unavailable to the second PE in the backbone operator, specifically including:

The first PE imports the route corresponding to the first LSP into the border gateway protocol BGP, and uses the attributes of the BGP to identify that the first customer operator has not assigned to the first PE to establish the first label of the LSP, and publish the first notification message to the second PE through the multi-protocol gateway protocol MP-BGP.

In a sixth possible implementation manner of the first aspect, the first PE in the backbone operator network determines the first LSP between the first node in the first customer operator and the first PE Availability includes:

When the first PE receives the label used to establish the first LSP, and the first LSP has a connectivity fault, determine that the first LSP is unavailable.

In the seventh possible implementation manner of the first aspect according to the first aspect or the sixth possible implementation manner of the first aspect, the first notification message includes:

An identifier used to indicate that the first PE has been assigned a label for establishing the first LSP but the first LSP has a connectivity failure.

In the eighth possible implementation manner of the first aspect according to the first aspect or the sixth possible implementation manner of the first aspect or the seventh possible implementation manner of the first aspect , the first notification message is used to notify the second PE to revoke the label used to establish the second LSP that the second PE has allocated for the equipment in the second customer operator connected to the second PE, so The second LSP is an LSP starting from the second node in the second customer operator, ending at the first node and passing through the first LSP.

In the ninth possible implementation manner of the first aspect according to any one of the sixth possible implementation manner of the first aspect to the eighth possible implementation manner of the first aspect, when When determining that the first LSP is unavailable, the first PE sends a first notification message that the first LSP is unavailable to a second PE in the backbone operator, specifically including:

The first PE imports the route corresponding to the first LSP into the border gateway protocol BGP, and uses the attribute of the BGP to identify that the first customer operator has allocated the first PE to the first PE for Establishing the label of the first LSP but the first LSP has a connectivity failure, and publishing the first notification message to the second PE through the MP-BGP protocol.

In a second aspect, an embodiment of the present invention provides a message control device, wherein the device includes:

a determining unit, configured to determine whether a first LSP between a first node in a first customer operator and the first PE is available, and the first LSP terminates at the first node;

A control unit, configured to, when the determination unit determines that the first LSP is unavailable, send a first notification message that the first LSP is unavailable to the second PE in the backbone operator.

In a first possible implementation manner of the second aspect, the determining unit:

When the first PE does not receive the label used to establish the first LSP within a predetermined time, determine that the first LSP is unavailable.

In the second possible implementation manner of the second aspect, a second possible implementation manner of the second aspect is also provided, the first notification message includes a The identity of the label assigned to establish the first LSP.

In a third possible implementation of the second aspect according to the second aspect or the first possible implementation of the second aspect or the second possible implementation of the second aspect , the first notification message is used to notify the second PE to avoid allocating labels for establishing a second LSP to equipment in the second customer operator connected to the second PE, and the second LSP is An LSP starting from the second node in the second customer operator, ending at the first node and passing through the first LSP.

In the fourth possible implementation manner of the second aspect according to any one of the first possible implementation manner of the second aspect to the third possible implementation manner of the second aspect, further It includes: a receiving unit, configured to receive the label used to establish the first LSP through a label distribution protocol LDP.

In the fifth possible implementation manner of the second aspect according to any one of the first possible implementation manner of the first aspect to the third possible implementation manner of the first aspect, the The control unit is used in particular for:

importing the route corresponding to the first LSP into Border Gateway Protocol BGP, using the attributes of the BGP to identify that the first customer operator has not allocated a label for establishing the first LSP to the first PE, and Publishing the first notification message to the second PE through a multi-protocol gateway protocol MP-BGP.

In a sixth possible implementation manner of the second aspect, the determining unit is specifically configured to:

When the first PE receives the label used to establish the first LSP, and the first LSP has a connectivity fault, determine that the first LSP is unavailable.

In the seventh possible implementation manner of the second aspect according to the second aspect or the sixth possible implementation manner of the second aspect, the first notification message includes:

An identifier used to indicate that the first PE has been assigned a label for establishing the first LSP but the first LSP has a connectivity failure.

In the eighth possible implementation of the second aspect according to the second aspect or the sixth possible implementation of the second aspect or the seventh possible implementation of the second aspect , the first notification message is used to notify the second PE to revoke the label used to establish the second LSP that the second PE has allocated for the equipment in the second customer operator connected to the second PE, so The second LSP is an LSP starting from the second node in the second customer operator, ending at the first node and passing through the first LSP.

In the ninth possible implementation manner of the second aspect according to any one of the sixth possible implementation manner of the second aspect to the eighth possible implementation manner of the second aspect, the The control unit described above is used in particular for:

importing the route corresponding to the first LSP into Border Gateway Protocol BGP, and using the attributes of the BGP to identify that the first customer operator has allocated the first PE to the first PE to establish the first label of the LSP and the first LSP has a connectivity fault, and publishes the first notification message to the second PE through the MP-BGP protocol.

Through the method provided by the embodiment of the present invention, the PE equipment of the backbone operator publishes the information of the label corresponding to the route of the customer operator received in the VRF instance to other PE equipment of the backbone operator through the first notification message, so that When other PE devices determine that the label corresponding to the route of the downstream customer operator is not available, they avoid allocating labels to the upstream customer operator. Through this solution, unnecessary establishment of LSPs can be controlled, and system overhead on LSPs can be reduced.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following will briefly introduce the accompanying drawings that need to be used in the descriptions of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only of the present invention. For some embodiments, those of ordinary skill in the art can also obtain other drawings based on these drawings without paying creative efforts.

Figure 1 is a system architecture diagram for LSP establishment;

FIG. 2 is a diagram of an operator system architecture of an operator;

FIG. 3 is a flowchart of a message control method provided by an embodiment of the present invention;

Fig. 4 is the flowchart of the method for establishing LSP in the embodiment of the present invention;

FIG. 5 is a structural diagram of a message control device provided by an embodiment of the present invention;

Fig. 6 is a structural diagram of a message control device provided by another embodiment of the present invention.

Detailed ways

The technical solutions of the present invention will be described in further detail below with reference to the accompanying drawings and embodiments.

Multiple Protocol Label Switching (Multiple Protocol Label Switch, MPLS) is located between the link layer and the network layer in the TCP/IP protocol stack, and is used to provide connection services to the IP layer and obtain services from the link layer at the same time. MPLS is not limited to any specific link layer protocol, and can use any layer-2 medium to transmit network packets. MPLS is not a kind of service or application, it is actually a kind of tunnel technology. This technology not only supports multiple high-level protocols and services, but also ensures the security of information transmission to a certain extent. In this technology, MPLS replaces IP forwarding with label switching, where the label is a short and fixed-length connection identifier that only has local significance and is encapsulated between the link layer and the network layer.

Label Distribution Protocol (Label Distribution Protocol, LDP) is a control protocol of MPLS, which is equivalent to the signaling protocol in the traditional network. Label Switched Path (LSP) establishment and maintenance operations. LDP specifies various messages and related processing procedures in the label distribution process.

MPLS supports multi-layer labels, and the forwarding plane is connection-oriented, so it has good scalability, making it possible to provide customers with various services on the unified MPLS/IP basic network architecture. Through the LDP protocol, the Label Switched Router (LSR) can directly map the routing information of the network layer to the switching path of the data link layer, and establish the LSP of the network layer. Currently, LDP is widely used in VPN services. It has the advantages of simple networking and configuration, support for establishing LSPs driven by routing topology, and support for large-capacity LSPs.

VPN is a virtual private communication network established in a public network by Internet Service Provider (Internet Service Provider, ISP) and Network Service Provider (Network Service Provider, NSP). The basic principle of VPN is to use tunnel technology to encapsulate VPN packets in the tunnel, and use the VPN backbone network to establish a dedicated data transmission channel to realize transparent transmission of packets.

Tunnel technology uses one protocol to encapsulate another protocol message, and the encapsulation protocol itself can also be encapsulated or carried by other encapsulation protocols.

BGP/MPLS IP VPN is a Layer 3 Virtual Private Network (L3VPN). It uses Border Gateway Protocol (BGP) to advertise VPN routes on the service provider backbone network, and uses MPLS to forward VPN packets on the service provider backbone network. The IP here means that the VPN bears IP packets.

A user of a BGP/MPLS IP VPN service provider may also be a service provider itself. In this case, the former is called provider carrier or first carrier, and the latter is called customer carrier or second carrier, as shown in Figure 2 Show. This networking model is called carriers'carriers (carriers'carrier), and the low-level service provider SP (Service Provider) acts as the VPN client of the higher-level SP.

In order to maintain good scalability, the second-tier operators use the CEs of the first-tier operators to only advertise the internal routes of the second-tier operators to the PEs of the first-tier operators, and do not advertise the routes of their own customers. In the description of this article, the internal routes of the second-tier carrier are called internal routes, and the routes of customers of the second-tier carrier are called external routes.

Among them, the difference between internal routing and external routing is: internal routing refers to the route of the secondary operator switching path SP site, which needs to be exchanged between the relevant primary operator PEs through BGP; external routing refers to the secondary operator customer The route of the site, that is, the VPN route of the secondary carrier. The external routes are not advertised to the PE devices of the first-level carrier, but are only exchanged between PEs of the related second-level carrier through BGP.

The VPN-IPv4 routes of the customer BGP/MPLS VPN service provider (that is, the second-tier carrier) are regarded as external routes, and the backbone BGP/MPLS VPN service provider (that is, the first-tier carrier) does not import these routes into the Its own VPN routing and forwarding table, it only imports the internal routing of the customer's BGP/MPLS VPN service provider. In this way, the number of routes that need to be maintained in the first-level carrier network is reduced. Secondary carriers need to maintain internal and external routes.

Because, in MPLS technology, when the provider edge equipment C-PE2 of the customer operator needs to iterate the VPN service to a certain tunnel, if the LDP on the downstream customer operator side is interrupted, the provider edge equipment C-PE2 on the upstream customer operator side It cannot detect that the tunnel is unavailable, cannot perform route convergence, and cannot switch traffic to other normal tunnels, which will cause service interruption. And when the downstream customer operator only needs to establish LSPs for a small number of prefixes, because the upstream customer operator side cannot distinguish, label and LSP resources will be wasted.

To this end, an embodiment of the present invention provides a packet control method. Fig. 3 is a flowchart of an embodiment of a packet control method provided by an embodiment of the present invention. In this embodiment, the executor is the upstream provider edge device of the backbone operator, that is, PE1 in the background art FIG. 1 . It can be seen from the figure that the method includes the following contents.

Step 301, the first PE in the backbone operator's network determines whether a first LSP between the first node in the first customer operator and the first PE is available, and the first LSP takes the first node as end;

Specifically, the first PE of the backbone operator, for example, PE1 in FIG. 1 creates a first VRF for the customer operator at the site 1 (site1) side. That is to generate a route to the PE equipment C-PE1 of the customer operator. The specific generation method can be dynamic learning through the IGP protocol or static configuration. Embodiments of the present invention include but are not limited to the above methods.

PE1 receives the first LSP from the provider edge device C-PE1 of the first customer operator in the first customer operator to the first PE through the first VRF instance, and C-PE1 serves as the end point of the first LSP. Preferably, PE1 receives the label used to establish the first LSP through the label distribution protocol (LDP). The method for the customer operator to issue the label to the backbone operator is usually to use LDP, and other methods are also possible. The present invention only lists Exemplary common methods are not limited to the above methods.

PE1 may receive the label used to establish the first LSP, or may not receive the above label.

When the PE1 does not receive the label used to establish the first LSP within a predetermined time, or when the first LSP receives the label used to establish the first LSP, but the first LSP has connectivity When a failure occurs, it is determined that the first LSP is unavailable.

Step 302, when it is determined that the first LSP is unavailable, the first PE sends a first notification message that the first LSP is unavailable to a second PE in the backbone operator.

Through the method provided by the embodiment of the present invention, the PE equipment of the backbone operator sends the information on whether the label corresponding to the route of the downstream customer operator received in the VRF exists to other PE equipment of the backbone operator through a signaling message, so that Other PE devices can determine whether to allocate labels to upstream customer operators according to the situation, thereby saving labels and reducing the system's overhead on LSPs.

In one embodiment, PE1 sends a first notification to PE2 when the first PE determines that the first LSP is unavailable because the first PE has not received the label used to establish the first LSP within a predetermined time message, where the first notification message includes an identifier used to indicate that the first PE is not allocated a label for establishing the first LSP. The first notification message is used to notify the PE2 to avoid allocating the label used for establishing the second LSP to the equipment in the second customer operator connected to the PE2. Optionally, the second LSP is an LSP starting from the second node in the second customer operator, ending at the first node and passing through the first LSP. The first node may be C-PE1 shown in FIG. 1 , the second node may be C-PE2 shown in FIG. 1 , and the first node and the second node may also be other nodes. The second LSP can be regarded as an extension of the first LSP, and the first LSP can be regarded as a part of the second LSP.

More specifically, the backbone operator's first PE device imports the route to the first customer operator in the first VRF into BGP, and uses BGP attributes to identify that the first customer operator does not allocate a route to the first PE. Labels for establishing the first LSP, and publish them to other PE devices of the backbone operator, such as PE2, through the MP-BGP protocol. The BGP attribute adopted above is the extended community attribute of BGP in one embodiment, and other methods may also be used. The embodiment of the present invention only lists exemplary commonly used methods, and is not limited to the above methods.

Other PE devices of the backbone operator, such as PE2, judge whether it is necessary to trigger the second VRF instance to allocate a label for establishing the second LSP to the second customer operator according to the first notification message.

Through the above embodiments, the PE2 device can judge whether to assign labels to the upstream customer operator according to whether the downstream customer operator has assigned labels to the routes of the corresponding customer operators, thereby saving labels and reducing system overhead for LSPs.

In another implementation manner, PE1, that is, the first PE, determines that the first LSP is unavailable when receiving the label used to establish the first LSP, and the first LSP has a connectivity fault, And send a first notification message to PE2, that is, the second PE, which includes a label used to indicate that the first PE has been allocated for establishing the first LSP but the first Indicates that the LSP has a connectivity fault. The first notification message is used to notify the PE2 to revoke the label that the PE2 has allocated for the equipment in the second customer operator connected to the second PE to establish a second LSP, and the second LSP is An LSP starting from the second node C-PE2 in the second customer operator, ending at the first node C-PE1 and passing through the first LSP, that is, the second LSP.

More specifically, the first PE device of the backbone operator imports the route to the first customer operator in the first VRF into BGP, uses the BGP attribute for identification, and uses the BGP attribute to identify the first customer operator The provider has allocated the first PE to the first PE to establish the label of the first LSP, but the first LSP has a connectivity failure, and advertises it to other PE devices of the backbone operator through the MP-BGP protocol, For example PE2. The BGP attribute adopted above is the extended community attribute of BGP in one embodiment, and other methods may also be used. The embodiment of the present invention only lists exemplary commonly used methods, and is not limited to the above methods.

Other PE devices of the backbone operator, such as PE2, revoke the allocated label for establishing the second LSP according to the first notification message, so as to revoke the second LSP.

The above implementation method is also applicable to the situation where the LSP from C-PE2 to C-PE1 has been established, that is, PE1 finds that the first LSP between PE1 and C-PE1 is faulty, and then notifies PE2 to cancel the connection from PE2 to C-PE1. label between PE2.

Through the method provided in this embodiment, other PE devices of the backbone operator except PE1 can be informed of LSP interruption information in time, so that other PEs can avoid continuing to establish an interrupted LSP or make other PEs cancel the interrupted LSP , Avoid resource waste and business loss.

Preferably, in another implementation manner, when PE1 determines that the first LSP is available, the first PE sends a second notification message that the first LSP is available to a second PE in the backbone operator, so that the second PE allocates a label for establishing a second LSP to a device in a second customer operator connected to the second PE according to the second notification message, and the second LSP is in the form of An LSP starting from the second node in the second customer operator, ending at the first node and passing through the first LSP. Actually, the second LSP includes the first LSP, the first LSP can be regarded as a part of the second LSP, and the second LSP can be regarded as an extension of the first LSP.

In addition, no matter whether the first LSP is available or not, the first PE can assign a label for establishing the second LSP to the second PE.

Specifically, the availability of the first LSP refers to when PE1 receives a label for establishing the first LSP, and there is no connectivity fault in the first LSP.

In this case, PE1 may choose to send a second notification message to inform PE2 that the first LSP is available.

PE2 can create a second virtual routing and switching VRF instance for the customer operator after receiving the second notification message; PE2 is similar to PE1, and also creates a VRF for the C-PE2 of the second customer operator connected to PE2, We call it VRF2. The generated method can be dynamic learning through the IGP protocol, or static configuration. Only the most common methods are listed here, and the present invention is not limited to the above two methods.

PE2 learns that the first LSP is available through the second notification message, then triggers the second VRF instance to assign labels to the second customer operator, establishes the third LSP, that is, the LSP from C-PE2 to PE2, and further establishes LSP from C-PE2 to C-PE1.

For example, PE2 may perform processing according to the flow described in FIG. 4 .

Step 401, receiving the route published by MP-BGP, and importing the route into the IGP corresponding to the second VRF;

Step 402, analyzing the attribute carried by the BGP, if there is a specified attribute added by the first PE, then perform step 403, otherwise, end;

Specifically, the existence of the specified attribute added by the first PE indicates that the first LSP is available, and if it does not exist, it proves that the first LSP is unavailable.

Step 403, triggering the LDP in the second VRF instance to assign a label to the second customer operator for the route.

Through the above-mentioned embodiment, other PE devices except PE1 of the backbone operator can learn the information of LSP interruption in time, so as to stop establishing an interrupted LSP or a side-by-side interrupted LSP. The starting point of this LSP can be found that the LSP cannot be established or the LSP is revoked, so that there is an opportunity to take measures for the affected services to avoid waste of resources and loss of services.

Correspondingly, please refer to FIG. 5. The embodiment of the present invention also provides a packet control device, such as the PE device in the backbone operator in the foregoing embodiment, including:

A determining unit 501, configured to determine whether a first LSP between a first node in a first customer operator and the first PE is available, and the first LSP terminates at the first node;

The control unit 502 is configured to, when the determining unit 501 determines that the first LSP is unavailable, send a first notification message indicating that the first LSP is unavailable to the second PE in the backbone operator.

The determining unit 501 may be implemented by at least one control circuit, and the control unit 502 may be implemented by at least one control circuit.

The determining unit 501: when the first PE does not receive the label used to establish the first LSP within a predetermined time, or receives the label used to establish the first LSP, but the first LSP is faulty In the case of , it is determined that the first LSP is unavailable.

In a preferred implementation manner, the apparatus further includes a receiving unit 503, configured to receive the label used to establish the first LSP through a label distribution protocol LDP. The receiving unit 503 may be realized by at least one receiving circuit.

The first notification message sent by the control unit 502 includes an identifier indicating that the first PE has not been allocated a label for establishing the first LSP, and notifies the second PE to avoid communicating with the first LSP. The equipment in the second customer operator connected to the two PEs allocates a label for establishing a second LSP, and the second LSP starts from the second node in the second customer operator and ends with the first node LSP that is the end point and passes through the first LSP.

Preferably, the control unit 502 imports the route corresponding to the first LSP into the border gateway protocol BGP, and uses the attributes of the BGP to identify that the first customer operator has not allocated the first PE to the first PE for establishing the second route. label of an LSP, and publish the first notification message to the second PE through a multi-protocol gateway protocol MP-BGP.

In another embodiment, the determining unit 501 determines that the first LSP is unavailable when first receiving the label used to establish the first LSP, and the first LSP has a connectivity fault.

The first notification message sent by the control unit 502 includes an identifier indicating that the first PE has been allocated a label for establishing the first LSP but the first LSP has a connectivity failure, and the first The notification message is used to notify the second PE to revoke the label used to establish the second LSP that the second PE has assigned to the equipment in the second customer operator connected to the second PE, and the second LSP is An LSP starting from the second node in the second customer operator, ending at the first node and passing through the first LSP.

Preferably, the control unit 502 imports the route corresponding to the first LSP into Border Gateway Protocol BGP, and identifies that the first customer operator has allocated the first PE to the first PE with the attribute of the BGP. Allocating a label for establishing the first LSP and the first LSP has a connectivity failure, and publishing the first notification message to the second PE through the MP-BGP protocol.

Optionally, in another implementation manner, the control unit 502 is further configured to, when the determination unit determines that the first LSP is available, send the first LSP to the second PE in the backbone operator An available second notification message, so that the second PE assigns a label for establishing a second LSP to a device in a second customer operator connected to the second PE according to the second notification message , the second LSP is an LSP starting from the second node in the second customer operator, ending at the first node and passing through the first LSP.

It is worth noting that each module in the foregoing embodiments is a functional module for implementing the method shown in FIG. 3 . In fact, the PE device is likely to have the function of implementing the method shown in FIGS. 3-4 at the same time, so Each module in the above two embodiments can be fully integrated in the same PE device, which should not be construed as a limitation to the embodiments of the present invention.

FIG. 6 is a schematic diagram of a message control device according to an embodiment of the present invention. As shown in the figure, this embodiment includes a network interface 61 , a processor 62 and a memory 63 . The system bus 64 is used to connect the network interface 61 , the processor 62 and the memory 63 .

The network interface 61 is used to communicate with other devices.

The memory 63 can be a permanent memory, such as a hard disk drive and a flash memory, and has software modules and device drivers in the memory 63 . The software modules can execute various functional modules of the above method of the present invention; the device driver can be a network and interface driver.

At startup, these software components are loaded into memory 63, then accessed by processor 62 and execute the following instructions:

The first PE in the backbone operator's network determines whether a first LSP between a first node in a first customer operator and the first PE is available, and the first LSP terminates at the first node;

When it is determined that the first LSP is unavailable, the first PE sends a first notification message indicating that the first LSP is unavailable to the second PE in the backbone operator.

The message control device shown in FIG. 6 can be used to execute the message control methods shown in FIGS. 3-4 , and only needs to make corresponding configurations in the memory or processor, and details will not be repeated here.

Professionals should further realize that the units and algorithm steps described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the relationship between hardware and software Interchangeability. In the above description, the composition and steps of each example have been generally described according to their functions. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present invention.

The steps of the methods or algorithms described in connection with the embodiments disclosed herein may be implemented by hardware, software modules executed by a processor, or a combination of both. Software modules can be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other Any other known storage medium.

The specific embodiments described above have further described the purpose, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above descriptions are only specific embodiments of the present invention and are not intended to limit the scope of the present invention. Protection scope, within the spirit and principles of the present invention, any modification, equivalent replacement, improvement, etc., shall be included in the protection scope of the present invention.

Claims (20)

1. A message control method, characterized in that the method comprises: The first PE in the backbone operator's network determines whether a first LSP between a first node in a first customer operator and the first PE is available, and the first LSP terminates at the first node; When it is determined that the first LSP is unavailable, the first PE sends a first notification message indicating that the first LSP is unavailable to the second PE in the backbone operator. 2. The method according to claim 1, wherein the first PE in the backbone operator network determines whether the first LSP between the first node in the first customer operator and the first PE Available include: When the first PE does not receive the label used to establish the first LSP within a predetermined time, determine that the first LSP is unavailable. 3. The method according to claim 2, wherein the first notification message includes an identifier for indicating that the first PE is not allocated a label for establishing the first LSP. 4. The method according to claim 1, 2 or 3, characterized in that, The first notification message is used to notify the second PE to avoid allocating the label used to establish the second LSP to the equipment in the second customer operator connected to the second PE, and the second LSP is based on An LSP starting from the second node in the second customer operator, ending at the first node and passing through the first LSP. 5. The method according to any one of claims 2-4, wherein the first PE receives the label used to establish the first LSP through a label distribution protocol (LDP). 6. The method according to claim 2-4, wherein when it is determined that the first LSP is unavailable, the first PE sends a message indicating that the first LSP is unavailable to the second PE in the backbone operator. The first notification message, specifically including: The first PE imports the route corresponding to the first LSP into the border gateway protocol BGP, and uses the attributes of the BGP to identify that the first customer operator has not assigned to the first PE to establish the first label of the LSP, and publish the first notification message to the second PE through the multi-protocol gateway protocol MP-BGP. 7. The method according to claim 1, wherein the first PE in the backbone operator network determines whether the first LSP between the first node in the first customer operator and the first PE Available include: When the first PE receives the label used to establish the first LSP, and the first LSP has a connectivity fault, determine that the first LSP is unavailable. 8. The method according to claim 1 or 7, wherein the first notification message comprises: An identifier used to indicate that the first PE has been allocated a label for establishing the first LSP but the first LSP has a connectivity failure. 9. The method of claim 1, 7 or 8, wherein The first notification message is used to notify the second PE to revoke the label used to establish the second LSP that the second PE has allocated for the equipment in the second customer operator connected to the second PE, and the The second LSP is an LSP starting from the second node in the second customer operator, ending at the first node and passing through the first LSP. 10. The method according to any one of claims 7-9, wherein when it is determined that the first LSP is unavailable, the first PE sends a message indicating the first LSP to the second PE in the backbone operator. The first notification message that the LSP is unavailable, specifically includes: The first PE imports the route corresponding to the first LSP into the border gateway protocol BGP, and uses the attribute of the BGP to identify that the first customer operator has allocated the first PE to the first PE for Establishing the label of the first LSP but the first LSP has a connectivity failure, and publishing the first notification message to the second PE through the MP-BGP protocol. 11. A message control device, characterized in that the device comprises: a determining unit, configured to determine whether a first LSP between a first node in a first customer operator and the first PE is available, and the first LSP terminates at the first node; A control unit, configured to, when the determination unit determines that the first LSP is unavailable, send a first notification message indicating that the first LSP is unavailable to the second PE in the backbone operator. 12. The device according to claim 11, wherein the determining unit: When the first PE does not receive the label used to establish the first LSP within a predetermined time, determine that the first LSP is unavailable. 13. The apparatus according to claim 12, wherein the first notification message includes an identifier for indicating that the first PE is not allocated a label for establishing the first LSP. 14. Apparatus according to claim 11, 12 or 13, characterized in that, The first notification message is used to notify the second PE to avoid allocating the label used to establish the second LSP to the equipment in the second customer operator connected to the second PE, and the second LSP is based on An LSP starting from the second node in the second customer operator, ending at the first node and passing through the first LSP. 15. The device according to any one of claims 12-14, further comprising: a receiving unit, configured to receive the label used to establish the first LSP through a label distribution protocol (LDP). 16. The method according to claims 12-14, characterized in that the control unit is specifically used for: importing the route corresponding to the first LSP into Border Gateway Protocol BGP, using the attributes of the BGP to identify that the first customer operator has not allocated a label for establishing the first LSP to the first PE, and Publishing the first notification message to the second PE through a multi-protocol gateway protocol MP-BGP. 17. The device according to claim 11, wherein the determining unit is specifically used for: When the first PE receives the label used to establish the first LSP, and the first LSP has a connectivity fault, it is determined that the first LSP is unavailable. 18. The method according to claim 11 or 17, wherein the first notification message includes: An identifier used to indicate that the first PE has been allocated a label for establishing the first LSP but the first LSP has a connectivity failure. 19. Apparatus according to claim 11, 17 or 18, characterized in that, The first notification message is used to notify the second PE to revoke the label used to establish the second LSP that the second PE has allocated for the equipment in the second customer operator connected to the second PE, and the The second LSP is an LSP starting from the second node in the second customer operator, ending at the first node and passing through the first LSP. 20. The device according to any one of claims 11-19, wherein the control unit is specifically used for: importing the route corresponding to the first LSP into Border Gateway Protocol BGP, and using the attributes of the BGP to identify that the first customer operator has allocated the first PE to the first PE to establish the first label of the LSP and the first LSP has a connectivity fault, and publishes the first notification message to the second PE through the MP-BGP protocol.

Images