WO2009071022A1

WO2009071022A1 - Method and device for disposing flux engineering tunnel

Info

Publication number: WO2009071022A1
Application number: PCT/CN2008/073030
Authority: WO
Inventors: Hong Lv
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-11-30
Filing date: 2008-11-12
Publication date: 2009-06-11
Also published as: CN101163110A; CN101163110B

Abstract

A method and device are provided, which are used for deploying a traffic engineering tunnel. The method for deploying a traffic engineering tunnel comprises the following steps: the first core apparatus analyzes a path establishing message and obtains a feature message; the second core apparatus is obtained based on the feature message and a topological structure; when the first core apparatus is different from the second core apparatus, the path establishing message is transmitted through the traffic engineering tunnel between the first core apparatus and the second core apparatus. The establishing device of the traffic engineering tunnel comprises an analysis module for analyzing the path establishing message to get the feature message; an inquiry module of the second core device gained based on the feature message and the topological structure; and a transmitting module for transmitting the path establishing message. With the embodiment of the invention, the path establishing message through the first core device and the second core device which is correspondingly same as the first core device can share one traffic engineering tunnel. So the number of the traffic engineering tunnels needed to be maintained by the core apparatus is largely reduced, and the work load of the core apparatus is lightened.

Description

Method and device for deploying traffic engineering tunnel

Technical field

The embodiments of the present invention relate to the field of network communication technologies, and in particular, to a method and an apparatus for deploying a traffic engineering tunnel. Background technique

Network congestion is a major problem affecting the performance of backbone networks. Congestion may be caused by insufficient network resources or local congestion caused by unbalanced network resource load. Congestion caused by unbalanced load can be solved by traffic engineering. Traffic engineering dynamically adjusts network traffic and network unit load, adjusts traffic management parameters, routing parameters and resource constraint parameters in real time, optimizes network resource usage, and avoids load imbalance. Causing congestion.

Multi-Protocol Label Switching (hereinafter referred to as MPLS) Traffic Engineering (hereinafter referred to as TE) is a technology that is scalable and effective in solving traffic problems. It has been applied to many large backbone networks. .

In order to provide a good end-to-end quality of service (QoS) and improve network reliability, all service providers are required to use the MPLS Virtual Private Network (VPN) service. A TE tunnel is set up between the edge routers (the Provider Edges, hereinafter referred to as the PEs). As shown in Figure 1, the PEs in the current network are connected to the core device (Provider, hereinafter referred to as P). Normally, There are only a few P devices, and each P device needs to connect several or more than one PE device. Assume that a TE tunnel is established between PE1 and PE5. The process is: The server calculates the TE tunnel path according to the Constrained Shortest Path First (CSPF) algorithm. Assume that PE1→PI→P2→P4→PE5, the server will The path is displayed as a display route and sent to PE1 along with the other TE tunnel configuration information. PE1 sends a path setup message to the PI. P1 establishes a state machine to maintain the TE P channel of PE1 → P1 and establish P1 → The TE tunnel between P2, and sends the path establishment message to P2, P2 establishes a state machine, and sends the path establishment message to P4, and P4 also establishes a state. After the path is established, the PE5 sends a reservation confirmation message to the PE1. When the PE5 receives the path establishment message and determines the end of the TE tunnel, it sends a reservation confirmation message to the PE1. After receiving the reservation confirmation message, it indicates that this PE1→P1→P2→P4→PE5 has been successfully established.

The above analysis shows that the TE tunnel needs to support a large number of TE tunnels. For example, an operator requires 80 PEs to establish TE tunnels with each other. 6320 (80x79) TE tunnels, which puts a lot of pressure on the core equipment (P equipment). In Figure 1, there are a total of eight PE devices, PE1-PE8, four P, P1-P4, two P devices at the endpoint, P1 and P4 each with four PE devices, and the dotted line indicates a TE tunnel initiated by PE1. . In the case of not considering the backup, each of the P1 or P4 needs to maintain 44 TE tunnels, including 12 tunnels (4x3) under the same equipment, 32 TE tunnels (2x4x4) between different devices, and P devices in the middle (P2). Or P3) Also maintain 32 TE devices. When considering backup, the number of TE tunnels that the P device needs to maintain will increase. Since the P device needs to establish a state machine and establish a timed refresh every time the tunnel is established, the P device will be difficult to maintain when a large number of TE tunnels exist.

One of the existing solutions is to establish a Label Switched Path (hereinafter referred to as LSP), establish a TE tunnel between P devices, and use Forwarding Adjacency LSP (hereinafter referred to as FA-LSP). The technology puts these tunnels into the Open Shortest Path First (OSPF) protocol or the Intermediate System-Intermediate System (ISIS) protocol, which is the TE tunnel. Think of it as a logical link. As shown in Figure 2, if a TE tunnel needs to be established between PE1 and PE5, you need to establish a TE tunnel between P1 and P4 to form a TE tunnel of PE1→P1→P4→PE5. The intermediate device P2 or P3 You do not need to perceive the TE tunnel initiated by the PE. You only need to maintain the TE tunnel established by P.

The inventors have found that such a scheme has at least the following problems in the process of implementing the present invention: This method does not reduce the need for the P device of the TE tunnel head node and the tail node (P1 and P4 in the above example) The number of TE tunnels to be maintained, for example, the number of TE tunnels initiated by PE1 to be maintained by P1 is eight, which is one more than the original seven. At the same time, the FA-LSP technology is introduced into OSPF or ISIS protocol, which will increase the number of TE tunnels. The topology complexity, and the FA-LSP is unstable, and its bandwidth and other parameters often change. Therefore, CSPF is frequently calculated, which increases the burden on the device, and is likely to cause loops during network oscillation. In addition, the bandwidth of the TE tunnel between the P devices is statically configured. The bandwidth cannot be dynamically adjusted according to the needs of the PE device. Summary of the invention

The embodiment of the invention provides a method and a device for deploying a TE tunnel, which is used to solve the problem that the number of TE tunnels to be maintained by the P device is large, and the number of TE tunnels that need to be maintained by the P device is reduced.

The embodiment of the invention provides a method for deploying a TE tunnel, including:

The first core device parses the received path establishment message, and obtains feature information of the path establishment message, where the feature information includes a destination address of the path establishment message;

Obtaining, according to the feature information and the built-in topology, a second core device, where the second core device is connected to a service provider edge router corresponding to the destination address of the path setup message;

Determining whether the first core device and the second core device are the same core device, and if not, transparently transmitting the path establishment message by using a traffic engineering tunnel between the first core device and the second core device.

An embodiment of the present invention provides an apparatus for deploying a TE tunnel, including:

a parsing module, configured to parse a path establishment message received by the first core device, to obtain feature information of the path establishment message;

a querying module, configured to obtain, according to the built-in topology structure and the feature information obtained by the parsing module, the second core device, where the second core device is connected to a service provider edge router corresponding to the destination address of the path setup message;

a transmission module, configured to determine whether the first core device and the second core device are the same core The heart device, when no, transparently transmits the path establishment message through a traffic engineering tunnel between the first core device and the second core device.

The embodiment of the present invention establishes a TE tunnel between the P devices, and establishes a message corresponding to the same path through the first P device and the second P device through the TE corresponding to the same first P device and the second P device. The tunnel is transparently transmitted. When the bandwidth of the TE tunnel is insufficient, the bandwidth is increased instead of re-establishing the TE tunnel. Therefore, the P device only needs to maintain the TE tunnel established between all the P devices, and does not need to maintain the TE tunnel established between the PE devices. The number of P devices provided by the carrier is limited, which is much smaller than that of the PE. The number of devices, therefore, the number of TE tunnels that the P device needs to maintain will be greatly reduced. DRAWINGS

FIG. 1 is a schematic structural diagram of establishing a TE tunnel between PE devices in the prior art;

2 is a schematic structural diagram of establishing a TE tunnel by a LA-LSP in the prior art;

3 is a flowchart of Embodiment 1 of a method for deploying a TE tunnel according to an embodiment of the present invention;

4 is a flowchart of Embodiment 2 of a method for deploying a TE tunnel according to an embodiment of the present invention;

5 is a schematic structural diagram of a method for deploying a TE tunnel according to an embodiment of the present invention; FIG. 6 is a schematic structural diagram of Embodiment 1 of a TE tunnel device according to an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of Embodiment 2 of a TE tunnel device according to an embodiment of the present invention. detailed description

The technical solution of the present invention will be further described below with reference to the accompanying drawings and specific embodiments.

FIG. 3 is a flowchart of Embodiment 1 of a method for deploying a TE tunnel according to an embodiment of the present invention. The embodiment includes: Step 301: A first P device parses a received path establishment message (PATH message), and obtains feature information of the path establishment message. The feature information includes a destination address of the path establishment message;

Step 302: Obtain a second P according to the destination address and a topology built in the first P device. a device, the second P device is connected to the PE device corresponding to the destination address of the path establishment message; Step 303: Determine whether the first P device and the second P device are the same P device, and if not, pass the The TE tunnel between the first P device and the second P device transparently transmits the path establishment message.

In this embodiment, regardless of which PE the PATH is sent, the first P device and the second P device that pass through one PATH message are the same as the first P device and the second P device that the other PATH message passes. The PATH message will pass between the first P device and the second P device.

The TE tunnel is transparently transmitted, which reduces the number of TE tunnels that need to be maintained on the P device.

FIG. 4 is a flowchart of Embodiment 2 of a method for deploying a TE tunnel according to an embodiment of the present invention. The embodiment includes: Step 401: A PE device sends a path establishment message (PATH message) to a first P device connected thereto. Referring to the structural diagram shown in FIG. 5, assuming that PE1 sends a PATH message, the PATH message will be sent to PI, and then PI is the first P device.

Step 402: The first P device parses the received PATH message to obtain feature information of the PATH message, where the feature information includes a destination address and a bandwidth requirement of the PATH message. Referring to the structural diagram shown in FIG. 5, it is assumed that PE1 needs to be established. - TE tunnel between PE5, then the destination address is the address of PE5.

Step 403: Allocate bandwidth to the ingress of the first P device according to the bandwidth requirement, and obtain the P device corresponding to the destination address according to the destination address and the network topology built in the first P device. Referring to the structure diagram shown in Figure 5, if the destination address is the address of PE5, the obtained second P device is P4. If the destination address is the address of PE2, the obtained second P device is P1.

Step 404: Determine whether the first P device and the second P device are the same P device. In the foregoing, if the first P device is P1 and the second P is P1, the process is the same, step 405 is performed; P4, then the two are different, and step 406 is performed.

Step 405: Allocate bandwidth for the exit of the first P device (P1) according to the bandwidth requirement obtained by parsing the PATH message.

Step 406: After obtaining the second P device, for example, P4, if the PATH message carries an explicit route object (ERO), and the ERO includes PI and P4. The intermediate P device (refer to the structural diagram shown in FIG. 5, such as P2) deletes the intermediate P device (P2) from the ERO to obtain the processed PATH message.

Step 407: Determine whether the first P device, that is, the P1 and the second P device, that is, the TE tunnel exists between the P4s (the TE tunnel between P1 and P4 may be pre-established), if yes, execute step 408; otherwise, execute Step 409.

Step 408: Determine whether the bandwidth of the TE tunnel between P1 and P4 meets the bandwidth requirement according to the bandwidth requirement obtained when the PATH message is parsed. If yes, go to step 411. Otherwise, go to step 410.

Step 409: The TE tunnel between P1 and P4 that meets the bandwidth requirement is triggered according to the bandwidth requirement obtained when the PATH message is parsed, and step 411 is performed.

Step 410: Adjust the bandwidth of the TE tunnel to meet the bandwidth requirement.

Step 411: Transparently transmit the PATH message through the TE tunnel that meets the bandwidth requirement.

In this embodiment, referring to the structure diagram shown in FIG. 5, after receiving the PATH message, the PE5 sends a reservation confirmation message to the P4, that is, the RESV message, and after receiving the RESV message, the P4 will upload the RESV message step by step. , complete the establishment of the TE tunnel. If the RESV message is transmitted in the form of IP (not in the TE tunnel), the RESV message is processed according to the IP standard. If the RESV message is transmitted through the TE tunnel (into the TE tunnel), when the first P device receives the PATH message, A P device between a P device and a second P device is added to a Record Route Object (RRO).

In this embodiment, all the P devices establish TE tunnels with each other, which is equivalent to all P devices forming a regional group (shown in dotted line in Figure 5). TE tunnels are established in the regional group. These TE tunnels are not advertised to the area. Outside the group, the PE device will not be advertised to the PE device. The PE device will not be aware of these TE tunnels. The PE device can sense the TE tunnel between the P devices. The PE device can detect the TE tunnel between the P devices. When the bandwidth of the TE tunnels does not meet the requirements, the CSPF needs to recalculate and re-determine the TE tunnel path. This may cause network oscillations, which may cause loops. However, the TE tunnel between the P devices of the present invention is not released. To the PE device, avoid The problem in the above FA-LSP method.

In this embodiment, after the first P device of the TE tunnel receives the PATH message sent by the PE device, the P device parses the PATH message, finds the destination address of the PATH message, and finds the PATH according to the destination address and the built-in network topology. The second P device corresponding to the message, when the first P device is different from the second P device, transparently transmits the PATH through the TE tunnel between the first P device and the second P device, that is, the PATH is encapsulated in the first The TE tunnel between a P device and the second P device is transmitted, and there is no need to establish a state machine. Compared with the prior art method for establishing a state machine, the prior art method for establishing a state machine is to establish a state machine on the P device on the path through which the TE tunnel passes to maintain the upstream TE tunnel and establish a downstream TE tunnel. Take the above-mentioned FA-LSP as an example. A TE tunnel should be established between PE1 and PE5. The TE tunnel between PE1 and PE5 is equivalent to PE1→PI→P4 because the state machine is set up on the PI and P4. → A segmentation tunnel such as PE5. In this embodiment, since the PATH is transparently transmitted, it is not necessary to establish a state machine, which is equivalent to directly establishing a TE tunnel between PE1 and PE5 instead of segment establishment.

When the PE that transmits the PATH message is located under the same P device, the TE tunnel is set up between PE1 and PE2. Since both PE1 and PE2 are located in P1, the TE tunnel between P devices is not required. The PATH message needs to be transparently transmitted after the bandwidth is allocated to the ingress and egress of the P1, so that a segmented TE tunnel such as PE1→P1→PE2 is established, which is different from the prior art. It is equivalent to directly establishing a TE tunnel from PE1 to PE2. Therefore, the TE tunnel between the PEs of the P device and the PEs of the P device does not need to be maintained by the P device. The P device only needs to maintain the TE tunnel in the regional group composed of all P devices. , greatly reducing the number of TE tunnels.

When a TE tunnel exists between the first P device and the second P device, the bandwidth of the originally established TE tunnel can be adjusted according to actual bandwidth requirements. In this way, no matter how many PE devices need to establish a TE tunnel, the TE tunnel will be shared by the same first P device and the second P device in the same group (the bandwidth of the TE tunnel can be adjusted according to actual needs). ), instead of creating a new TE tunnel. For example, based on the establishment of a TE tunnel between PE1 and PE5, it is still fake. Let TE tunnel be established between PE2 and PE5. From the above analysis, TE P-tit 3⁄4it PE 1→ P 1→ P4→ PE5 established between PE1 and PE5, that is, P1→P4 in the regional group Inter-TE tunnel, ^_ is set to resolve at this time (in the resolution of the PATH message, in addition to the resolution of the destination address, the bandwidth requirement will be resolved) The bandwidth required for the TE tunnel between P1 and P4 is 10M; When a TE tunnel is to be established between PE2 and PE5, it must pass through P1→P4 in the group. 4 The bandwidth required for the TE tunnel between P1 and P4 is 20M. If the existing technology is used, Automatic adjustment, so you need to manually expand the bandwidth between the two to 30M (10M+20M), and distribute the bandwidth adjustment information to each PE device and P device, and at the same time, the TE tunnel between PE2 and PE5 on PI and P4. Create a new state machine, or establish a TE tunnel between P 1 and P4. This embodiment does not need to be rebuilt. Instead, the shared TE tunnel technology is used, that is, the PI→P4 established when the TE tunnel is established by using PE1. The TE tunnel between the two, but only when the P1 receives the PE2 and initiates the TE tunnel establishment. The bandwidth configuration of the tunnel is modified, that is, the bandwidth of the TE tunnel between P1 and P4 is adjusted to 30M, and the bandwidth adjustment information does not need to be advertised to other devices, and the state machine is not required to be established. The PATH message (assuming that it is from PE1) establishes a P1→P4 TE tunnel. After the completion, the PATH message is transparently transmitted, or the PATH message received after the PATH message is transparently transmitted through the pre-established TE tunnel of P1 → P4. (including from PE2, PE3, and PE4), as long as the path is PI→P4, you only need to adjust the bandwidth of the originally established P1→P4 TE tunnel according to the bandwidth requirement, and transparently transmit the PATH message. 1. A TE tunnel is sufficient between P4s. According to the above principle, no matter which PE device initiates a PATH message, as long as the PATH messages have the same first P device and second P device, a TE tunnel is transparently transmitted. The PATH message.

In this embodiment, the TE tunnel is established between the P devices, so that the P device only needs to maintain the TE tunnel in the regional group, that is, only the TE tunnel between the P devices needs to be maintained, and the TE tunnel between the PE devices is not required to be maintained. The number of TE tunnels maintained by the P device is limited, which greatly reduces the number of TE tunnels that the P device needs to maintain. The number of P devices in the carrier network is limited, generally 8 devices. In the case of a backup TE tunnel, only 8*7*2 entries need to be established, which is several thousand more than the existing ones. The number is greatly reduced, thus greatly reducing the burden on the P device. Even if the PE device is added later, the TE tunnel that the P device needs to maintain will not change as long as the number of P devices does not change. With this method, even if hundreds of PE devices need to establish TE tunnels with each other, the P device of the carrier can still be used. Meet maintenance needs.

FIG. 6 is a schematic structural diagram of Embodiment 1 of a device for deploying a TE tunnel according to an embodiment of the present invention. The embodiment includes: a parsing module 1, a query module 2, and a transport module 3. The parsing module 1 is configured to parse a path setup message received by the first core device. Obtaining the feature information of the path establishment message; the query module 2 is configured to obtain, according to the built-in topology structure and the feature information obtained by the parsing module, a second core device corresponding to the destination address of the path setup message; the transmission module 3 And determining whether the first core device and the second core device are the same core device, and if not, transparently transmitting the path establishment message by using a traffic engineering tunnel between the first core device and the second core device .

FIG. 7 is a schematic structural diagram of Embodiment 2 of a device for deploying a TE tunnel according to an embodiment of the present invention. The difference from the embodiment shown in FIG. 6 further includes: an ingress allocation module 4, an egress distribution module 5, and a deletion module 6; The distribution module 4 is configured to allocate bandwidth to the entry of the first core device according to the feature information obtained by the parsing module 1; the egress distribution module 5 is configured to determine, by the transmission module 3, the first core device and the second core device When the same core device is the same, the bandwidth is allocated to the egress of the second core device; the deleting module 6 is configured to: when the transmitting module 3 determines that the first core device and the second core device are not the same core device And deleting a core device located between the first core device and the second core device among the explicit routing objects carried in the path establishment message. The transmission module 3 specifically includes: an identity determination sub-module 31, a tunnel determination sub-module 32, a bandwidth determination and adjustment sub-module 33, a tunnel establishment sub-module 34, and a transparent transmission sub-module 35. The identity determination sub-module 31 is configured to determine the Whether the first core device and the second core device obtained by the query module 2 are the same core device; the tunnel determination sub-module 32 is configured to determine that the first core device and the second core device are not the same when the identity determination sub-module 31 determines a core device, determining whether there is a traffic engineering tunnel between the first core device and the second core device, and if yes, outputting the determination result to the bandwidth determination and adjustment sub-module 33; otherwise, outputting the determination result to the tunnel establishment sub-module 34; bandwidth judgment and adjustment sub-module 33 After receiving the judgment result output by the tunnel judging sub-module 32, determining whether the bandwidth of the traffic engineering tunnel meets the requirements according to the feature information obtained by parsing the path setup message, and if so, the traffic engineering tunnel is the traffic that meets the bandwidth requirement. The engineering tunnel, otherwise, adjusts the bandwidth of the traffic engineering tunnel until the bandwidth requirement is met; the tunnel establishment sub-module 34 is configured to: after receiving the judgment result output by the tunnel determination sub-module 32, obtain the message according to the path establishment message Feature information, triggering establishment of a traffic engineering tunnel between the first core device and the second core device that meets the bandwidth requirement; the transparent transmission sub-module 35 is configured to pass the path establishment message to the bandwidth determination and adjustment sub-module 33 And the traffic engineering tunnel that meets the bandwidth requirement obtained by the tunnel establishment sub-module 34 is transparently transmitted to the second core device.

The embodiment may further include an adding module 7 configured to: when the identity determining submodule 31 in the transmitting module 3 determines that the first core device and the second core device are not the same core device, The core device between a core device and the second core device is added to the Record Route Object (RRO).

In this embodiment, the number of TE tunnels maintained by the P device is greatly reduced, and the working load of the P device is reduced.

It should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

Rights request

A method for deploying a traffic engineering tunnel, where the first traffic engineering tunnel between the first core device and the second core device is deployed, and the method includes:

And parsing the path establishment message received by the first core device, and obtaining the feature information of the path establishment message, where the feature information includes a destination address and a bandwidth requirement of the path establishment message;

And obtaining, by the destination address and the built-in topology, a second core device, where the second core device is connected to a service provider edge router corresponding to the destination address of the path setup message;

When the first core device and the second core device are not the same core device, the path establishment message is transparently transmitted through the first traffic engineering tunnel between the first core device and the second core device, where the first The traffic engineering tunnel meets the bandwidth requirements.

The method for deploying a traffic engineering tunnel according to claim 1, wherein the transparently transmitting the path establishment message by using the first traffic engineering tunnel between the first core device and the second core device comprises: :

When there is an existing second traffic engineering tunnel between the first core device and the second core device, determining whether the bandwidth of the second traffic engineering tunnel satisfies the bandwidth requirement;

When the bandwidth of the second traffic engineering tunnel meets the bandwidth requirement, the first traffic engineering tunnel is an existing second traffic engineering tunnel; when the bandwidth of the second traffic engineering tunnel does not meet the bandwidth requirement And adjusting the bandwidth of the second traffic engineering tunnel until the bandwidth requirement is met, where the first traffic engineering tunnel is an adjusted second traffic engineering tunnel that meets the bandwidth requirement.

When there is no existing second traffic engineering tunnel between the first core device and the second core device, triggering establishment of the first traffic between the first core device and the second core device that meet the bandwidth requirement The engineering tunnel, the first traffic engineering tunnel is a traffic engineering tunnel that triggers the establishment of a bandwidth requirement.

The method for deploying a traffic engineering tunnel according to claim 1, wherein after the obtaining the feature information of the path establishment message, the method further comprises: determining, according to the bandwidth requirement, the first core device The entrance allocates bandwidth.

The method for deploying a traffic engineering tunnel according to claim 1, further comprising: when the first core device is the same as the second core device, the second core is according to the bandwidth requirement The device's egress allocates bandwidth.

The method for deploying a traffic engineering tunnel according to claim 1, wherein the path establishment message is transparently transmitted through a first traffic engineering tunnel between the first core device and the second core device. The method further includes: deleting a core device located between the first core device and the second core device among the explicit routing objects carried in the path establishment message.

The method for deploying a traffic engineering tunnel according to claim 1, wherein the channel is established by transparently transmitting the path through the first traffic engineering tunnel between the first core device and the second core device. The method further includes: adding a core device located between the first core device and the second core device into a record routing object.

8. A device for deploying a traffic engineering tunnel, characterized in that:

a parsing module (1), configured to parse a path setup message received by the first core device, to obtain feature information of the path setup message, where the feature information includes a destination address and a bandwidth requirement of the path setup message;

The query module (2) is configured to obtain, according to the built-in topology structure and the destination address obtained by the parsing module, the second core device, where the second core device is connected to the service provider edge router corresponding to the destination address of the path setup message ;

a transmission module (3), configured to: when the first core device and the second core device are not the same core device, transparently transmit the first traffic engineering tunnel between the first core device and the second core device Path establishment message.

The device for deploying a traffic engineering tunnel according to claim 8, further comprising: an ingress allocation module (4), configured to use the feature information obtained by the parsing module (1) The entrance of the first core device allocates bandwidth.

The device for deploying a traffic engineering tunnel according to claim 8, further comprising: an egress distribution module (5), configured to: when the first core device and the second core device are the same core device , allocating bandwidth for the exit of the second core device.

The device for deploying a traffic engineering tunnel according to claim 8 or 9 or 10, wherein the transmission module (3) specifically includes:

The identity determination sub-module (31) is configured to determine whether the first core device and the second core device are the same core device;

The tunnel judging sub-module (32) is configured to determine, when the identity determining sub-module (31), that the first core device and the second core device are not the same core device, determining the first core device and the second core Whether there is a second traffic engineering tunnel between the devices, and if yes, outputting the judgment result to the bandwidth judgment and adjustment sub-module (33), otherwise, outputting the judgment result to the tunnel establishment sub-module (34); bandwidth judgment and adjustment sub-module (33) And determining, according to the feature information obtained by parsing the path establishment message, whether the bandwidth of the second traffic engineering tunnel satisfies the requirement, when the second traffic is used. If the bandwidth of the engineering tunnel meets the bandwidth requirement, the first traffic engineering tunnel is an existing second traffic engineering tunnel; when the bandwidth of the second traffic engineering tunnel does not meet the bandwidth requirement, the first The bandwidth of the second traffic engineering tunnel is up to the bandwidth requirement, and the first traffic engineering tunnel is adjusted to meet the bandwidth requirement. Two traffic engineering tunnel

a tunnel establishment sub-module (34), configured to: after receiving the determination result of the tunnel determination sub-module (32), trigger the establishment of the first core device that meets the bandwidth requirement according to the feature information obtained by parsing the path establishment message a first traffic engineering tunnel between the second core devices;

The transparent transmission sub-module (35) is configured to transparently transmit, by the bandwidth establishment and adjustment sub-module (33) and the tunnel establishment sub-module (34), the first traffic engineering tunnel that meets the bandwidth requirement to the The second core device.

12. The apparatus for deploying a traffic engineering tunnel according to claim 8, wherein The deleting module (6) is configured to delete, when the identity determining sub-module (31) determines that the first core device and the second core device are not the same core device, deleting the path setup message A core device located between the first core device and the second core device among the explicit routing objects.

The device for deploying a traffic engineering tunnel according to claim 8, further comprising: an adding module (7), configured to: when the identity determining submodule (31) determines the first core device When the second core device is not the same core device, the core device located between the first core device and the second core device is added to the record routing object.