WO2009140873A1 - Configuration method of link attribute information, communication device and communication system - Google Patents

Abstract

A configuration method of Link Attribute Information, communication device and communication system, wherein, the configuration method involves that: according to network topological information in the second network and Forwarding Adjacency Label Switch Path (FA-LSP), a node of the second network generates Link Attribute Information of Forwarding Adjacency Label Switch Path. The node of the second network transmits the Link Attribute Information to the first node and/or the second node of the first network, so the first node adjoins the second node in the first network by Forwarding Adjacency Label Switch Path. In the embodiment of the invention, the automatic configuration of Link Attribute Information is realized, and it is not necessary to inquire the Link Attribute Information from the second network and configures it to the node of the first network manually, thereby, the speed and efficiency of configuration of Link Attribute Information is raised, and the error caused by manual configuration of Link Attribute Information for FA-LSP is avoided.

Description

 Method for configuring link attribute information, communication device and communication system The application is submitted to the Chinese Patent Office on May 19, 2008, and the application number is 200810093289.0, and the invention name is "configuration method of link attribute information, communication device and communication system" The priority of the Chinese Patent Application, the entire contents of which is incorporated herein by reference. Technical field

 Embodiments of the present invention relate to communication technologies, and in particular, to a method for configuring link attribute information, a communication device, and a communication system. Background technique

 In a Multi-Protocol Label Switching Traffic Engineering (MPLS-TE) network with traffic engineering, a signaling protocol can be used, for example: Resource Reservation Protocol with Traffic Engineering Protocol with TE, the following cylinder is called: RSVP-TE, to automatically establish a Label Switch Path (hereinafter referred to as LSP) to transfer user service data from one node to another. Different user service data have different requirements for LSP parameters. For example, for real-time service data such as Voice over Internet Protocol (VoIP) and video, the delay of the LSP should not be too long. For important service data, the quality of the data transmission needs to be guaranteed. The LSPs separated by the shared risk link group (the following is called: SRLG) provide data transmission services for the same service. Since the probability of simultaneous failure of two separate LSPs is small, the SRLG can be used. When a fault occurs somewhere in the network, the secure transmission of user service data is effectively guaranteed.

SRLG refers to links that share certain physical resources in an optical network. For example, physical resources such as physical nodes and optical cables are shared. This sharing means that once a shared resource fails, this These links will fail at the same time. For example: If there are K fiber links that pass through the same bridge and K is an integer greater than 1, then the K fiber links will be affected when the bridge is broken.

 In a multi-layer or multi-domain network, the client-side network may request the service-side network to provide a connection of the service-side network, by which adjacencies may be formed between the two ends of the client-side network. The connection that the client side network endpoint uses to establish a general MPLS RSVP-TE (Generalized RSVP-TE, Gigabit RSVP-TE) is called a Forwarding Adjacency LSP (hereinafter referred to as FA-LSP).

 After the FA-LSP is established, when the LSP is established in the client-side network, the FA-LSP can be used as a link between two adjacent nodes in the client-side network, according to the delay of the link, SRLG, and the like. The link attribute information calculates an LSP that satisfies certain constraints. However, since the FA-LSP is a connection provided by the service-side network, the client-side network does not have the service-side network topology information, and thus the delay of the FA-LSP and the link attribute information of the SRLG cannot be known. In the prior art, after the FA-LSP is established, the administrator manually queries the service-side network for the delay information of the FA-LSP and the link attribute information of the SRLG, and manually configures the two neighbors in the client-side network. On the first node in the node, a link from the first node to the last node of the two adjacent nodes is posted to the client side network by the FA-LSP. If the FA-LSP is bidirectional, the administrator also needs to manually configure the delay profile of the FA-LSP and the link attribute information of the SRLG on the last node in the client-side network, so that the end node can also use the FA-LSP as the A link from the last node to the head node is published to the client side network.

In the process of implementing the present invention, the inventors have found that the prior art has at least the following problems: Since the administrator needs to manually query the delay of the FA-LSP, link attribute information such as SRLG, and configure it to the node in the client side network, the efficiency Lower, slower, and more prone to human error. Summary of the invention The technical problem to be solved by the embodiments of the present invention is: In a multi-layer or multi-domain network, after the FA-LSP in one of the networks is established, the link attribute information of the FA-LSP can be automatically sent to the nodes in other networks. Therefore, the configuration speed and efficiency of the link attribute information are improved, and errors caused by artificially configuring the link attribute information of the FA-LSP are avoided.

 An aspect of the embodiments of the present invention provides a method for configuring link attribute information, including:

 The node in the second network generates the link attribute information of the forwarding adjacency label switching path according to the network topology information of the second network and the forwarding adjacency label switching path; the node in the second network connects the link The attribute information is sent to the first node and/or the second node in the first network, so that the first node and the second node in the first network are contiguous through the forwarding adjacency label switching path.

 Another aspect of the embodiments of the present invention provides a communication device, located in a first network, including:

 a receiving module, configured to receive link attribute information of a forwarding adjacency label switching path sent by a node in the second network, where the communication device is established with another communication device in the first network according to the link attribute information Adjacent to the exchange path.

 According to still another aspect of the embodiments of the present invention, another communication device is provided, where the second network is located, including:

 An information generating module, configured to generate link attribute information of the forwarding adjacency label switching path according to the forwarding adjacency label switching path and the pre-stored network topology information of the second network;

An information sending module, configured to send link attribute information of the forwarding adjacency label switching path generated by the information generating module to the first node and/or the second node in the first network, so that the first in the first network The node and the second node abut through the forwarding adjacency label switching path. According to still another aspect of the embodiments of the present invention, a communication system includes: a first communication device in a first network, and a second communication device in a second network,

 And generating, by the second communications device, the link attribute information of the forwarding adjacency label switching path according to the network topology information of the second network and the forwarding adjacency label switching path;

 The second communication device sends the link attribute information to the first communication device or the third communication device; according to the link attribute information, the first communication device and the third communication device pass the forwarding Adjacent label switching paths are contiguous.

 In the embodiment of the present invention, after the FA-LSP is established, the node in the second network may generate the FA-LSP according to the network topology information and the FA-LSP information of the second network. The link attribute information is actively sent to the first node or the second node in the first network, and the link attribute information is automatically configured, and the link attribute information is not manually queried from the second network and configured to the first The nodes in the network improve the configuration speed and efficiency of the link attribute information, and avoid the errors caused by manually configuring the link attribute information of the FA-LSP. The technical solutions of the embodiments of the present invention are further described in detail below through the accompanying drawings and embodiments. DRAWINGS

 FIG. 1 is a flowchart of an embodiment of a method for configuring link attribute information according to the present invention. FIG. 2 is a flowchart of another embodiment of a method for configuring link attribute information according to the present invention. FIG. 3 is a schematic structural diagram of an application scenario networking according to an embodiment of the present invention.

 FIG. 4 is a flow chart of an application embodiment of a method for configuring link attribute information according to the present invention.

 FIG. 5 is a flowchart of another application embodiment of a method for configuring link attribute information according to the present invention.

FIG. 6 is a schematic structural diagram of another application scenario networking according to an embodiment of the present invention. FIG. 7 is a schematic structural diagram of Embodiment 1 of a communication device according to the present invention.

 FIG. 8 is a schematic structural diagram of Embodiment 2 of a communication device according to the present invention.

 FIG. 9 is a schematic structural diagram of Embodiment 3 of a communication device according to the present invention.

 FIG. 10 is a schematic structural diagram of Embodiment 4 of a communication device according to the present invention. detailed description

 In the embodiment of the present invention, after the FA-LSP is established, the node in the second network generates the link attribute information of the FA-LSP according to the network topology information and the FA-LSP information of the second network, and actively The link attribute information of the FA-LSP is sent to the first node or the second node in the first network. The first node in the first network is contiguous with the second node through the FA-LSP.

 Among them, the first node is also called the first node, and the second node is also called the last node. The first network and the second network are two different networks in a multi-layer or multi-domain network. When two nodes in the first network are not connected by a direct link, the links provided by the second network are connected, and the second network may provide a connection for any two nodes in the first network, two of the first networks. The node can form adjacency between the two nodes of the first network through the connection. The first network is a client side network, and the second network is a service side network. The link attribute information of the FA-LSP may specifically include one or more of all the information indicating the link attributes, such as the delay of the link and the SRLG information.

 After the establishment of the FA-LSP, the node in the second network may generate the link attribute information of the FA-LSP according to the network topology information of the second network and the FA-LSP, and actively send the information to the first network. A node or a second node implements automatic configuration of link attribute information, and does not need to manually query link attribute information from the second network and configure it to a node in the first network, thereby improving configuration of link attribute information. Speed and efficiency, and avoids the error caused by artificially configuring the link attribute information of the FA-LSP.

As shown in FIG. 1, a flow of an embodiment of a method for configuring link attribute information according to the present invention is shown. The plan includes the following steps:

 Step 101: The first node in the first network sends an acquisition request to the ingress node in the second network, where the obtaining request is used to obtain link attribute information of the FA-LSP, and the first node and the last node in the first network pass the FA- LSP adjacency.

 Specifically, the first node in the first network may send the acquisition request in a Path Request message to the ingress node in the second network.

 Step 102: The head node receives link attribute information of the FA-LSP returned by the ingress node or the outbound node in the second network.

 Specifically, the first node may receive the link attribute information of the FA-LSP carried by the ingress node in the second network by using a notify message or a path reply (Reservation, the following container: Resv) message, from the notify message or the Resv message. The link attribute information of the FA-LSP is parsed out, or the link attribute information of the FA-LSP carried by the outbound node in the second network through the notify message is received, and the link attribute of the FA-LSP is parsed from the notify message. information.

 For the bidirectional FA-LSP, the last node in the first network also sends an acquisition request for acquiring the link attribute information of the FA-LSP to the egress node in the second network, and receives the ingress node or the egress node in the second network. Link attribute information of the returned FA-LSP. Specifically, the last node in the first network may send an acquisition request to the egress node in the second network by using the Resv message, and receive the incoming message in the second network through the notify message, or the egress node returns through the notify message or the Resv message. Link attribute information of the FA-LSP. In the following embodiments of the present invention, the acquisition request for acquiring the link attribute information of the FA-LSP is also referred to as the link attribute information acquisition request of the FA-LSP.

 As shown in FIG. 2, it is a flowchart of another embodiment of a method for configuring link attribute information according to the present invention, which includes the following steps:

Step 201: The ingress node in the second network receives the first node sent in the first network. Obtaining a request for obtaining link attribute information of the FA-LSP, where the first node and the last node in the first network are adjacent to each other through the FA-LSP.

 Specifically, the ingress node in the second network may receive the Path message sent by the first node in the first network, and parse the link attribute information obtaining request of the FA-LSP from the Path message.

 Step 202: The ingress node generates link attribute information of the FA-LSP according to the network topology information of the second network and the FA-LSP, and sends the link attribute information of the FA-LSP to the first node in the first network, so that the first node and the end in the first network The nodes are contiguous through the FA-LSP.

 Specifically, the ingress node may generate a notify message or a Resv message according to the network topology information of the second network and the FA-LSP, and send the link attribute information of the FA-LSP to the notify node or the Resv message to the first node.

 Correspondingly, for the bidirectional FA-LSP, the egress node in the second network further receives the link attribute information acquisition request of the FA-LSP sent by the last node in the first network, and sends the FA to the last node in the first network. Link attribute information of the LSP. Specifically, the egress node in the second network may receive the link attribute information acquisition request of the FA-LSP carried by the last node in the first network by using the Resv message, parse the acquisition request from the Resv message, and generate the generated FA. The link attribute information of the LSP is carried in the notify message or the Resv message is sent to the last node in the first network.

As shown in FIG. 3, it is a schematic diagram of a network structure of an application scenario according to an embodiment of the present invention. The embodiment includes a client side network 1 and a service side network 2. The client-side network 1 can serve as the first network in the embodiment of the present invention, and the service-side network 2 can serve as the second network in the embodiment of the present invention. The client side network 1 is composed of a client side first node 11, a client side second node 12, and a client side third node 13. The service side network 2 is composed of a service side first node 21, a service side second node 22, and a service side third node 23. An interface is provided on each node, the interface on the first node 11 on the client side is K and A, and the interface on the second node 12 on the client side is B. With N, the interfaces on the third node 13 on the client side are L and M; the interfaces on the first node 21 on the service side are C, G and E; the interfaces on the second node 22 on the service side are F, J and D, services. The interfaces on the side third node 23 are H and I. The interfaces between the two nodes can be connected through a link. In an embodiment of the present invention, in the client side network 1, the client side first node 11 and the client side third node 13, and the client side second node 12 and the client side third node 13 have direct The links are connected, and the FA-LSPs provided by the client-side first node 11 and the client-side second node 12 are connected by the service-side network 2.

 Each network can run a routing protocol, for example: Open the Shortest Path First with TE (hereinafter referred to as OSPF-TE) protocol to publish node and link information. In this way, each node in the network can get the link information of all nodes in the respective network. For example, the first node 11 on the client side can advertise a link information to the second node 12 on the client side through a routing protocol. The local interface of the link is K, the remote interface is L, and information such as total bandwidth and remaining bandwidth. The first node 21 can advertise a link information to the second node 22 on the service side through a routing protocol. The local interface of the link is E, the remote interface is F, the length is n meters, and the SRLG information is (1, 2). .

The FA-LSP between the client side first node 11 and the client side second node 12 can be established by a continuous signaling mode or a nested/spliced signaling mode. The path of the FA-LSP on the service side may be calculated by the service side ingress node, for example: by the service side first node 21, or by the service side ingress node requesting the centralized path calculation server in the network for calculation, assuming the calculated service The side path is the service side first node 21 → the service side third node 23 → the service side second node 22. If the continuous signaling mode is adopted, there is only one LSP between the first node 11 on the client side and the second node 12 on the client side, that is, the above FA-LSP, and the path is A→C→G→H→I→J→D→ B. If the nested/spliced signaling mode is adopted, the tunnel of the service side first node 21→the service side second node 22 may be established to carry the FA-LSP. After the tunnel is established, the FA-LSP continues to be established. At this time, there are two LSPs between the first node 11 on the client side and the second node 12 on the client side: - the strip is an FA-LSP, the path is A→C→tunnel→D→B, and the other is completely belonging to the service side network. The tunnel LSP of 2, the path is G→H→I→J. After the ingress node in the service side network obtains the path on the service side, the connection between the client side first node 11 and the client side second node 12 can be established according to the path.

 The client-side first node 11 and the client-side second node 12 are used as the first and last nodes, respectively, and the service-side first node 21 and the service-side second node 22 are used as the ingress and egress nodes. It is assumed that the path of the FA-LSP on the service side is the service side first node 21 (G) → the service side third node 23 (H) → the service side third node 23 (I) → the service side second node 22 (J). An example of an application embodiment of the method for configuring link attribute information of the present invention is as shown in FIG. 4, which includes the following steps:

 Step 301: The first node 11 on the client side sends a Path message to the first node 21 on the service side, requesting to establish a connection to the second node 12 on the client side. The Path message carries the link attribute information acquisition request of the FA-LSP, requesting to acquire. Link attribute information of the FA-LSP.

Specifically, the Notify Request object in the Resource Reservation Protocol with TE (hereinafter referred to as: RSVP-TE) may be extended to indicate a signaling message (for example, a Path message). In the Resv message, the Notify message, the link attribute information such as the delay of returning the FA-LSP and the SRLG is indicated. You can add a flag field to the Notify Request object of the fourth version of the Internet Protocol (hereinafter referred to as: IP) and the sixth version (hereinafter referred to as: IPv6), through the flag field. The S flag bit in the setting returns the SRLG information, and the return delay information is set by the T flag bit in the flag field. In addition, other flag bits may be set in the flag field for returning other link attribute information. Further, an F flag bit for performing fault notification may also be set in the flag field. Can Pre-set, when the flag is 1, you need to return the corresponding parameter information to the node specified in the address field in the Notify Request object.

 As shown in Table 1 and Table 2 below, they are a specific format example of the extended Notify Request object in IPv4.

 Table 1 Format of the IPv4 Notify Request object

 0 1 2 3

□ 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +- +- +- +- +- +-- +- +- +- +- +- +- +- +- +- +- +- +- +- +- +- +-- +- +- +- +- +- +- +-- +- +-- +- +

I Length I Cla_ss H"iim I C-Ty e I

I IPv4 Notify Uode Address I

I Reserved Fl&gs I T I S I F I Table 2 Format of IPv6 Notify Request Object

□ 1 2 3 G 1 2 3 4 5 6 7 S 9 0 1 2 3 4 5 6 7 S 9 0 1 2 3 4 5 6 7 S 9 0 1

+- +- +- +- +- +- +- +- +- +- +- +- +- +-- +- +- +- +---- +- +- +-- +- +- +-- +- +- +- +- +- +- +- +

I Length I C丄 sss—Mimi I C-Type I

+- +- +- +- +- +- +- +- +- +- +- +- +- +-- +- +- +- +---- +- +- +-- +- +- +-- +- +- +- +- +- +- +- + III IPv6 Notify Node Address I

I Reserved Flags I I S I F I

+- +- +- +- +- +- +- +- +- +- +- +- +- +-- +- +- +- +---- +- +- +-- +- +- +-- +- +- +- +- +- +- +- + Step 302, after receiving the Path message, the first node 21 on the service side parses the link attribute information acquisition request of the FA-LSP from the Path message, according to the service side. The first node 21 or the service side path calculated by the path calculation server fills in the display route object (Explicit Route Object, below: ERO): {service side first node 21, service side third node 23, service side second node 22}, and fill in the Record Route Object (Record Route Object, RRO), write the link index of the first node 21 (G) on the service side to the RRO, and then send the ERO and RRO to the Path message to send To the service side third node 23. The Path message will be transmitted along the specified route to the downstream node up to the egress client side second node 22. In this step, the service side first node 21 can remove the Notify Request. Object.

 Step 303: After receiving the Path message, the service-side third node 23 establishes a connection according to the ERO, and writes the link index of the service-side third node 23(I) to the RRO, and then sends the processed Path message to the service side. The second node 22.

 Step 304: After receiving the Path message, the serving-side second node 22 obtains the path information of the recorded FA-LSP from the RRO, that is, the FA-LSP, and the process of recording the path information of the FA-LSP, that is, the FA- The process of the LSP, because the path information in the different networks needs to be kept secret, removes the service side path information in the RRO from the Path message, and then sends the Path message to the second node 12 on the client side.

 Step 305: After receiving the Path message, the second node 12 on the client side returns a Resv message to the second node 22 on the service side. The Resv message carries the link attribute information acquisition request of the FA-LSP, and requests to obtain the link of the FA-LSP. Attribute information.

 Step 306, after receiving the Resv message, the service-side second node 22 fills in the RRO, and writes the RRO into the Resv message and sends it to the service-side third node 23; in addition, according to the recorded FA-LSP and the pre-stored service side The network topology information of the network 2, the delay information of the FA-LSP, and the link attribute information of the SRLG are generated, and the link attribute information is carried in the Notify message and sent to the second node 12 on the client side. The second node 12 on the client side can store the link attribute information for subsequent selection of LSP usage. In this step, the first node 21 on the service side can remove the Notify Request object.

 Specifically, a forwarding adjacency parameter can be added ( Forwarding Adj acency

Parameter, the following is called: FA Parameter) object, used to indicate the delay of the FA-LSP and the link attribute information of the SRLG through signaling messages (such as: Path message, Resv message, Notify message). As shown in Table 3 and Table 4 below, there is a specific format example of the delay FA Parameter object and the SRLGFA Parameter object.

Table 3 Format of the Delay FA Parameter Object +—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+— +—+—+—+—+—+—+—+ I Length IC丄sss—Uum I C-Type ( 1) I

+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+—+— +—+—+—+—+—+—+—+ IT me Delay (niilisecond) |

+ one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one + one +

+ + +

 1

 +

 1

 +

 1

 + + + ■

 1

 1

 1

 +

 Table 4 Format of the SRLG FA Paramet 1er object

 1

 □ 1 2 + + 3

 +

 G 1 2 3 4 5 6 7 8 9 G 1 2 3 4 5 6 7 3 9 G 11 2 3 4 5 6 7 3 9 G 1 +- 1 + + + I Length I Clsss—N m 1 I C-Type [2) I

+- +- +- +- +- +- +- +- +- ■+-+-+-+-+- ■+-+-+- ■+- ■+- ■+- ■+- ■+ - ■+- ■+- ■+- ■+

1 Shaued Risk Link Vs丄 us 1

+- +- +- +- +- +- +- +- +- ■+- ■+- ■+- ■+- ■+- ■+- ■+- ■+- ■+

1 1 1 1

+- +- +- +- +- +- +- +- +- ■+-+-+-+-+- ■+-+-+- ■+- ■+- ■+- ■+- ■+ - ■+- ■+- ■+- ■ +

1 Shaued Risk Link Gro 1

+- +- +- +- +- +- +- +- +- ■+-+-+-+-+- ■+-+-+- ■+- ■+- ■+- ■+- ■+ - ■ + - ■ + - ■ + - ■ + Step 307, after receiving the Resv message, the service-side third node 23 fills in the RRO, and writes the RRO into the Resv message and sends it to the service-side first node 21.

Step 308: After receiving the Resv message, the first node 21 on the service side needs to keep the path information in different networks, and removes the service side path information in the RRO from the Resv message, and then sends the Resv message to the first node on the client side. In addition, the first node 21 on the service side further generates the link attribute information of the delay of the FA-LSP, the SRLG, etc. according to the recorded FA-LSP and the network topology information of the pre-stored service-side network 2, and the chain attribute information The path attribute information is sent to the first node 11 on the client side in the Notify message. The first node 11 on the client side can parse the link attribute information from the Notify message and store it for subsequent selection of the LSP. In addition, the service-side first node 21 may also generate the FA-LSP delay, SRLG and other link attribute information according to the recorded FA-LSP and the network topology information of the pre-stored service-side network 2, and carry the RRO removal. In the subsequent Resv message, the delay information of the FA-LSP and the link attribute information of the SRLG are sent to the first node 11 on the client side through the Resv message, and the FA-LSP is parsed by the first node 11 on the client side from the Resv message. The link attribute information of the extension, the SRLG, and the like are not separately carried by the Notify message to carry the link attribute information of the FA-LSP and sent to the first node 11 on the client side.

 In step 306 and step 308, the service side first node 21 and the service side second node 22 may specifically generate the FA-LSP delay, SRLG and other link attribute information by using the following method: If the service side network 2 nodes are released The link information includes the length or delay of the corresponding link, and link attribute information such as SRLG, and the network topology information of the service side first node 21 and the service side second node 22 service side network 2 is issued by each node. The link attribute information included in the link information is used to calculate the delay of the service side path and the link attribute information of the SRLG. If the nodes in the service side network 2 release the link information, the link attribute of the corresponding link is not included. The information, the service side first node 21 and the service side second node 22 may use signaling to collect link attribute information of each link in the service side path, for example: when using the RRO to record the service side node interface information, The interface is also recorded in the RRO as the length or delay of the link corresponding to the link, and the link attribute information such as SRLG, so that the delay of the entire path on the service side, SRLG, etc. can be obtained. Link attribute information.

If the service side network 2 fails, for example, the link between the service side third node 23 and the service side second node 22 is broken, the service side third node 23 or the service side second node 22 can use signaling The FA-LSP of the first node 11 on the first node of the FA-LSP is faulty. The first node 11 on the client side re-initiates the signaling process to the first node 21 on the service side, that is, in step 301, the FA-LSP is re-routed, and the resources of the original FA-LSP can be used in the process of re-routing. After receiving the Path message, the first node 21 on the service side recalculates The service side path reroutes the FA-LSP according to the recalculated service side new path, and records the new path information using the RRO object. After the re-routing is completed, the Notify message is used to notify the link attribute information of the new FA-LSP as the client-side first node 11 and the client-side second node 12 as the two-node nodes of the FA-LSP. After receiving the link attribute information of the new FA-LSP, the first node 11 on the client side and the second node 12 on the client side may delete the link attribute information of the FA-LSP in which the link is faulty, or according to the new FA-LSP. The link attribute information is added or modified to the link attribute information of the FA-LSP in which the link is faulty. It is noted that although the link attribute information of the FA-LSP where the link failure occurs has changed, the client side The link between the first node 11 and the client side second node 12 does not change.

 In the embodiment shown in FIG. 4, the service side first node 21, which is the ingress node of the service side network 2, notifies the link attribute information of the FA-LSP as the first node 11 of the FA-LSP head node. The service side second node 22, which is the outbound node of the service side network 2, notifies the link attribute information of the FA-LSP as the client side second node 12 of the FA-LSP end node. In addition, any other node in the service side network 2, for example, the service side first node 21, obtains the address of the first node 11 on the client side from the Notify Request object in the received Path message. The address of the second node 12 on the client side is obtained from the Notify Request object in the received Resv message, and the other node notifies the first or last node of the FA-LSP of the link attribute information or the new link of the FA-LSP. Attribute information. Alternatively, the address of the first node 11 on the client side is obtained from the Notify Request object in the received Path message by any other node in the network 2, for example, the second node 22 on the service side, from the received Resv message. The address of the second node 12 on the client side is obtained from the Notify Request object, and the other node notifies the link attribute information or the new link attribute information of the FA-LSP of the first and last nodes of the FA-LSP.

An example of another application example of the method for configuring link attribute information of the present invention is as shown in FIG. 5, which includes the following, as an example of establishing a bidirectional FA-LSP in a nested/spliced signaling mode. Steps:

 Step 401: The first node 11 on the client side sends a Path message to the first node 21 on the service side, requesting to establish a connection to the second node 12 on the client side. The Path message carries the link attribute information acquisition request of the FA-LSP, requesting acquisition. Link attribute information of the FA-LSP.

 Step 402: After receiving the Path message, the first node 21 on the service side parses the link attribute information acquisition request of the FA-LSP from the Path message, and fills in the service side path calculated by the service side first node 21 or the path calculation server. ERO: {service side first node 21, service side third node 23, service side second node 22}, and use RRO to record tunnel path information, and write the link index of the service side first node 21 (G) to RRO Then, the ERO and the RRO are written into the Path message and sent to the service side third node 23 to request to establish a service side tunnel. The Path message will be transmitted to the downstream node along the specified route up to the second node 22 on the egress service side.

 Step 403: After receiving the Path message, the service-side third node 23 establishes a connection according to the ERO, and writes the link index of the service-side third node 23(I) to the RRO, and then sends the processed Path message to the service side. The second node 22.

 Step 404: After receiving the Path message, the second node 22 on the service side writes the link index of the second node 22 ( J ) on the service side to the RRO, and writes the RRO to the Resv message and returns it to the third node 23 on the service side.

 Step 405: After receiving the Resv message, the service-side third node 23 uses the RRO to record the tunnel path information, and then sends the Resv message to the service-side first node 21.

 Step 406: After receiving the Resv message, the first node 21 on the service side establishes a tunnel of the first node 21 on the service side according to the recorded tunnel path information, and sends a Path message to the second node 22 on the service side, and negotiates with the second node 22 on the service side. The service side first node 21 → the service side second node 22 is used to tunnel the FA-LSP.

Step 407, after receiving the Path message, the second node 22 on the service side sends a second message to the client side. The node 12 forwards the Path message and establishes the FA-LSP of the first node 11 on the client side to the second node 12 on the client side.

 Step 408: After receiving the Path message, the second node 12 on the client side returns a Resv message to the second node 22 on the service side. The Resv message carries the link attribute information acquisition request of the FA-LSP, and requests to obtain the link of the FA-LSP. Attribute information.

 Step 409: After receiving the Resv message, the second node 22 on the service side parses the link attribute information acquisition request of the FA-LSP from the Resv message, and generates the FA according to the path information of the tunnel and the network topology information of the service side network 2. - LSP delay, SRLG and other link attribute information, and the link attribute information is carried in the Notify message and sent to the client side second node 12. The client-side second node 12 may store the link attribute information for subsequent selection of the LSP to use; in addition, the service-side second node 22 sends a Resv message to the service-side third node 23, and negotiates with the service-side first node 21 to use the service. The side second node 22→the service side first node 21 tunnels the FA-LSP.

 Step 410: After receiving the Resv message, the first node 21 on the service side forwards the Resv message to the first node 11 on the client side. In addition, the first node 21 on the service side further uses the path information of the tunnel and the path of the service side network 2 The network topology information is generated, and the link attribute information such as the delay of the FA-LSP and the SRLG is generated, and the link attribute information is carried in the Notify message and sent to the first node 11 on the client side. The first node 11 on the client side can parse the link attribute information of the FA-LSP from the Notify message and store it for later selection of the LSP.

 Similar to the embodiment shown in FIG. 4, the service-side first node 21 may also carry the link attribute information of the FA-LSP in the Resv message to the first node 11 on the client side, without separately carrying the FA-LSP through the Notify message. And other link attribute information.

If the service side network 2 fails, the link between the service side third node 23 and the service side second node 11 is broken, then the service side third node 23 or the service side second node 22 can signal the service side using signaling. The first node 21 has the fault information. Service side first quarter Point 21 may initiate a signaling procedure, i.e., performing step 402, rerouting the tunnel to the service side first node 21 (E) - the service side second node 22 (F). After the re-routing is completed, the service-side first node 21 or the service-side second node 22 can look up the relevant FA-LSP using the tunnel, and notify the client-side first node 11 and the client as the two-node nodes of the FA-LSP by using the Notify message. The second second node 12 links attribute information of the new FA-LSP. After receiving the link attribute information of the new FA-LSP, the first node 11 on the client side and the second node 12 on the client side may delete the link attribute information of the FA-LSP in which the link is faulty, or according to the new FA-LSP. The link attribute information is added or modified to the link attribute information of the FA-LSP in which the link is faulty. It is noted that although the link attribute information of the FA-LSP where the link failure occurs has changed, the client side The link between the first node 11 and the client side second node 12 does not change.

 Similar to the embodiment shown in FIG. 4, the link attribute of the FA-LSP of the first and last nodes of the FA-LSP may also be notified by any other node in the service side network 2, for example, the service side first node 21. Information or new link attribute information; or, by any other node in the service side network 2, for example, the monthly service side second node 22, notifying the first and last nodes of the FA-LSP of the FA-LSP link Attribute information or new link attribute information.

The two first and last nodes in the client-side network 1 may be adjacent to each other by multiple service-side networks 2. The FA-LSP between the client-side and the last-end node is formed by splicing multiple service-side tunnels, and each service-side tunnel is formed. For the establishment, reference may be made to the embodiment shown in FIG. FIG. 6 is a schematic diagram of another application scenario networking structure according to an embodiment of the present invention. This embodiment takes two service-side networks as an example, and the method is also applicable to multiple layers including any multiple service-side networks. Multi-domain network. The FA-LSP between the first node 11 on the client side and the second node 12 on the client side passes through two service side networks, and the first service side network 1 provides a connection between the first node 21 on the service side and the second node 22 on the service side. The second service side network 2 provides a connection between the service side fourth node 24 and the service side fifth node 25. On the service side fourth node 24 The interface is 0, S, and P; the interfaces on the fifth node 25 on the service side are Q, T, and R, and the interfaces on the sixth node 26 on the service side are U and V. Usually, the two service side networks do not know each other's network topology information. Therefore, only the nodes in the corresponding service-side network can obtain the link delay information of the link in the service-side network, and link attribute information such as SRLG. That is, the service side first node 21 can obtain the link attribute information of the link between the service side first node 21 and the service side second node 22, and the service side fourth node 24 can obtain the service side fourth node 24 and the service side. Link attribute information of the link between five nodes 25. The link attribute information of the link between the service side second node 11 and the service side fourth node 24 is known by both the service side second node 22 or the service side fourth node 24 according to a preset setting. Specifically, It can be set in advance by a node with a large boundary node identifier (ID), or by an ingress node of the network.

 In a multi-layer/multi-domain network, a head node in a client-side network may send a link attribute information acquisition request of an FA-LSP to an ingress node in one of the service-side networks, and receive the first one along the direction of the FA-LSP. The link attribute information of the FA-LSP returned by the ingress node in the service-side network or the egress node in the last service-side network; or the ingress node or the egress node in each service-side network through which the head node receives the FA-LSP respectively The returned link attribute information of the path in each service side network constituting the FA-LSP, and the link attribute information of the entire FA-LSP is obtained according to the link attribute information of the path in each service side network.

In the networking structure shown in FIG. 6, the client-side first node 11 and the client-side second node 12, which are respectively the FA-LSP first and last nodes, can obtain the link attribute information of the FA-LSP in two ways: One way is to send the link attribute information of the entire FA-LSP to the client side first node 11 or the client side second node 12 by one of the nodes in the service side network 2; the second way is, by different services The node in the side network 2 transmits the link attribute information of the different path segment to one of the client side first node 11 and the client side second node 12, and the client side first node 11 or the client side second node 12 according to each Path segment The link attribute information obtains the link attribute information of the entire FA-LSP.

 According to the first mode, the service side first node 21 modifies the address field in the Notify Request object to the service side in the Path message sent to the downstream node for requesting the splicing of the service side tunnels and establishing the FA-LSP. One node 21, while other nodes transparently transmit the Notify Request object in the Path message. In this way, in the process of establishing the FA-LSP, the fourth node 24 of the ingress node in the second service-side network 2 may occupy the address specified in the Notify Request object in the Path message, and the path in the service-side network 2 The link attribute information is carried in the Notify message and sent to the first node 21 on the service side. In this way, the first node 21 on the service side can collect the link attribute information of the entire FA-LSP. The first node 21 of the service side may send the link attribute information of the entire FA-LSP to the first node 11 of the client side in a Notify message. Similarly, the service side fifth node 25 may modify the address field in the Notify Request object to the service side fifth node 25 in the Resv message sent to the upstream for requesting the splicing of the service side tunnels and establishing the FA-LSP. Other nodes transparently pass the Notify Request object in the Resv message. In this way, in the process of establishing the FA-LSP, the ingress node service side first node 21 in the first service side network 2 can set the path in the first service side network 2 according to the address specified in the Notify Request object in the Resv message. The link attribute information, which is carried in the Notify message, is sent to the fifth node 25 on the service side. In this way, the fifth node 25 on the service side can collect the link attribute information of the entire FA-LSP. The service side fifth node 25 can send the link attribute information of the entire FA-LSP to the second node 12 on the client side.

According to the second mode, the service side first node 21 does not modify the address field in the Notify Request object in the Path message sent to the downstream node for requesting the splicing of the service side tunnels and establishing the FA-LSP, that is, the address field remains unchanged. The client side first node 11. Then, the ingress node of each of the service side networks 2, that is, the service side first node 21 and the service side fourth node 24, can respectively transmit the link attribute information of each segment path to the client side first node 11. Customer side first quarter Point 11 can process the link attribute information of each segment to obtain the delay information of the entire FA-LSP and the link attribute information such as SRLG. Similarly, the service side fifth node 25 does not modify the address field in the Notify Request object in the Resv message sent to the upstream for requesting the splicing of the service side tunnels and establishing the FA-LSP, that is, remains the second on the client side. Node 12. Then, the ingress node of each of the service side networks 2, that is, the service side first node 21 and the service side fourth node 24, can transmit the link delay information of each segment path and link attribute information such as SRLG to the client side second node 12. The second node 12 on the client side processes the link attribute information of each segment to obtain the delay information of the entire FA-LSP and the link attribute information of the SRLG.

After the re-routing of a certain tunnel, the ingress node of each service-side network 2, that is, the service-side first node 21 and the service-side fourth node 24 may pass the delay information of the new tunnel after re-routing, and the link attribute information of the SRLG through the Notify message. The node that informs the FA-LSP, that is, the node indicated by the address field carried in the Notify Request object in the signaling message of the FA-LSP. If the node indicated by the address field carried in the Notify Request object is the service side first node 21, and the tunnel between the service side fourth node 24 and the service side fifth node 25 is rerouted, the service side fourth node 24 The delay of the new tunnel after the rerouting, the link attribute information such as SRLG, and the information of the FA-LSP using the new tunnel may be sent to the service side first node 21, and the service side first node 21 updates the FA based thereon. The link delay information of the LSP and the link fault information of the SRLG are sent to the first node of the FA-LSP, that is, the first node 11 on the client side. If the node indicated by the address field carried in the Notify Request object is the client-side first node 11, and the tunnel between the service-side fourth node 24 and the service-side fifth node 25 is re-routed, the service-side fourth node 24 The new tunnel delay after rerouting, the link attribute information of the SRLG, and the information of the FA-LSP using the tunnel may be sent to the first node 11 on the client side, and the first node 11 on the client side updates the FA-LSP accordingly. Link fault information such as delay and SRLG. In the foregoing manner that the client-side first node 11 and the client-side second node 12 acquire the link attribute information of the FA-LSP, the ingress nodes in the different service-side networks 2 notify the corresponding node of each tunnel path by using the Notify message. The delay information, the SRLG and other link information may be set in advance, and other nodes in the service side network 2, for example, the outbound nodes of the different service side networks 2, notify the corresponding node of each tunnel path by using the Notify message. Link attribute information such as extension and SRLG; in addition, the ingress node in the different service side network 2 may notify the first node of the FA-LSP and the egress node in the different monthly service side network 2 to notify the end of the FA-LSP. The link attribute information of the node FA-LSP only needs to ensure that only one node of each service side network 2 is responsible for notifying the corresponding node of each tunnel path delay, SRLG and other link attribute information.

 Since the service side path information can be obtained when the first node 21 on the service side calculates the service side path, the service side first node 21 may not use the path of the RRO record service side in the above embodiments of the present invention. Information, and directly use the calculated service side path information to obtain link delay information of the FA-LSP and link attribute information such as SRLG.

 The communication device provided by the embodiment of the present invention is located in the first network, and includes a receiving module, configured to receive a node in the second network, for example, an ingress node or an egress node, and link attribute information of the sent FA-LSP, According to the link attribute information, the communication device acts as the first node, and establishes adjacency switching path through the FA-LSP with another communication device as the last node in the first network.

FIG. 7 is a schematic structural diagram of Embodiment 1 of a communication device according to the present invention. The communication device of this embodiment includes a sending module and a receiving module. The sending module is configured to send, according to the pre-stored link information, a link attribute information acquisition request of the FA-LSP to the node in the second network, where the communication device acts as the first node and the last node in the first network passes the FA- The LSP is adjacency; the receiving module is configured to receive link attribute information of the FA-LSP returned by the node in the second network. Referring to FIG. 7, the communications device may further include a first storage module, configured to store link information and link attribute information of the FA-LSP; and the sending module sends the link information stored in the first storage module to the second network. The ingress node sends a link attribute information acquisition request of the FA-LSP; the receiving module receives the link attribute information of the FA-LSP returned by the node in the second network, and stores the link attribute information of the FA-LSP in the first In the storage module.

 In the communication device of the embodiment shown in Fig. 7, the transmitting module may include a generating unit and a transmitting unit. The generating unit is configured to generate a Path message carrying a link attribute information acquiring request of the FA-LSP; the sending unit is configured to send, according to the link information stored in the first storage module, a bearer link attribute to a node in the second network. The Path message of the information acquisition request. FIG. 8 is a schematic structural diagram of Embodiment 2 of a communication device according to the present invention.

 Further, in the communication device of the embodiment shown in Fig. 7, the receiving module may include a receiving unit, an obtaining unit, and a storage executing unit. The receiving unit is configured to receive a Notify message or a Resv message that includes the link attribute information sent by the node in the second network; the acquiring unit is configured to obtain the link attribute information from the Notify message or the Resv message; the storage execution unit is configured to: The link attribute information acquired by the obtaining unit is stored in the first storage module, as shown in FIG. 8.

 The communication device of the embodiment shown in FIG. 7 and FIG. 8 can be used as the first node in the first network to implement the foregoing embodiment of the link attribute information configuration method and the corresponding functions shown in the application embodiment. The function of the first node 11 on the customer side. In addition, the communication device can also implement the corresponding functions of the last node in the embodiment of the configuration method of the link attribute information according to the present invention or the application node in the first embodiment, such as the function of the second node 12 on the client side.

The communication device provided by another embodiment of the present invention is located in the second network, and includes: an information generating module, configured to generate a chain for forwarding the FA-LSP according to the forwarding FA-LSP and the pre-stored network topology information of the second network. Road attribute information, the first in the first network The node and the last node are adjacent to each other through the forwarding FA-LSP;

 The information sending module is configured to send, to the first node and/or the last node in the first network, link attribute information of the forwarding FA-LSP generated by the information generating module, so that the first node and the last node in the first network pass the FA - LSP adjacency.

 As shown in FIG. 9, it is a schematic structural diagram of Embodiment 3 of a communication device according to the present invention. The communication device of the embodiment includes an information receiving module, an information generating module, and an information sending module. The information receiving module is configured to receive a link attribute information obtaining request of the FA-LSP sent by the first node or the last node in the first network, where the information generating module is configured to generate the module according to the FA-LSP and the pre-stored information. The network topology information of the second network generates the link attribute information of the FA-LSP. The first node and the last node in the first network are adjacent to each other through the FA-LSP. The information sending module is configured to send the FA-LSP generated by the information generating module. Link attribute information.

 Referring again to Figure 9, the above communication device may further include a second storage module and/or a path information generating module. The second storage module is configured to store the network topology information of the second network; the path information generating module is configured to generate the FA-LSP; and the information generating module stores the FA-LSP generated by the path information generating module and the second storage module. The network topology information of the second network generates link attribute information of the FA-LSP.

 Further, in the communication device of the embodiment shown in Fig. 9, the information receiving module may include an information receiving unit and an information acquiring unit. The information receiving unit is configured to receive a Path message, where the Path message carries a link attribute information acquisition request of the FA-LSP, and the information acquiring unit is configured to parse the link attribute information acquisition request of the FA-LSP from the Path message, and The Path message is sent to the path information generating module. The path information generating module generates the FA-LSP according to the Path message. FIG. 10 is a schematic structural diagram of Embodiment 4 of a communication device according to the present invention.

Further, in the communication device of the embodiment shown in FIG. 9, the information sending module may include The information generating unit and the information transmitting unit are included. Wherein, the information generating unit is used to generate

The Notify message or the Resv message, the Notify message or the Resv message carries the link attribute information of the FA-LSP generated by the information generating module; the information sending unit is configured to send a Notify message or a Resv message carrying the link attribute information of the FA-LSP. , as shown in Figure 10.

 The communication device of the embodiment shown in FIG. 9 and FIG. 10 can be used as an ingress node in the second network, and implements the corresponding functions shown in the foregoing embodiment of the method for configuring link attribute information according to the present invention or an application embodiment thereof, such as The function of the first node 21 on the service side. In addition, the communication device can also be used as an egress node in the second network, and implements the corresponding function of the egress node in the embodiment of the foregoing method for configuring link attribute information according to the present invention, such as the second node 22 of the service side. Features. A communication system provided by an embodiment of the present invention includes a first communication device located in a first network, and a second communication device located in a second network. The second communication device generates link attribute information of the FA-LSP according to the network topology information of the second network and the FA-LSP; the second communication device sends the link attribute information of the FA-LSP to the first communication device or the first The third communication device; the first communication device and the third communication device are adjacent to each other by the FA-LSP according to the link attribute information.

 The first communication device can be used as the first node or the last node in the first network, that is, the first node 11 on the client side or the second node 12 on the client side, and the communication is performed in any embodiment as shown in FIG. 7 or FIG. The device, correspondingly implements the corresponding function of the first node or the last node in the embodiment of the configuration method of the link attribute information according to the present invention or the application embodiment thereof. The second communication device can serve as an ingress node or an egress node in the second network, that is, the first node on the service side

21 or the service side second node 22, using the communication device of any of the embodiments shown in FIG. 9 or FIG. 10, correspondingly implementing the foregoing configuration method of the link attribute information according to the present invention or an application embodiment thereof, the ingress node Or the corresponding function of the node.

Specifically, the receiving module in the first communications device performs information interaction with the information sending module in the second communications device, and receives the link attribute of the FA-LSP sent by the information sending module. Information.

 In addition, the sending module in the first communications device further performs information interaction with the information receiving module in the second communications device, and sends an obtaining request to the information receiving module, where the obtaining request is used to obtain link attribute information of the FA-LSP. Based on the foregoing embodiment of the present invention, after the FA-LSP is established, the node in the second network may generate the link attribute information of the FA-LSP according to the network topology information and the FA-LSP information of the second network, and actively Sending to the first node or the second node in the first network does not need to manually query the link attribute information from the second network and configure it to the node in the first network, thereby realizing the automatic configuration of the link attribute information, thereby The configuration speed and efficiency of the link attribute information are improved, and the error caused by manually configuring the link attribute information of the FA-LSP is avoided.

 Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by hardware, or can be implemented by means of software plus necessary general hardware platform, and the technical solution of the present invention. It can be embodied in the form of a software product that can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.), including a number of instructions for making a computer device (may It is a personal computer, a server, or a network device, etc.) that performs the methods described in various embodiments of the present invention.

 In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request

A method for configuring link attribute information, comprising: generating, by a node in a second network, a forwarding adjacency label switching path according to network topology information of the second network and forwarding adjacency label switching path Link attribute information: the node in the second network sends the link attribute information to the first node and/or the second node in the first network, so that the first node and the first node in the first network The two nodes abut through the forwarding adjacency label switching path.

 The method according to claim 1, wherein the node in the second network generates the chain of the forwarded label switching path according to the network topology information of the second network and the forwarding adjacent label switching path. Before the road attribute information, it also includes:

 The node in the second network receives the path request message sent by the first node in the first network, and parses the obtaining request from the path request message, where the obtaining request is used to obtain the forwarding adjacency label switching path. Link attribute information; or

 The node in the second network receives the path reply message sent by the second node in the first network, and parses the obtaining request from the path reply message, where the obtaining request is used to obtain the forwarding adjacency label switching Link attribute information of the path.

 The method according to claim 1, wherein the link attribute information of the forwarding adjacency label switching path is generated, and the node in the second network sends the link attribute information to the first network. Between the first node and/or the second node, the method further includes: carrying the link attribute information of the forwarding adjacency label switching path in a notification message or a path reply message;

The node in the second network sends the link attribute information to the first network The first node and/or the second node includes: sending a notification message or a path reply message carrying the link attribute information to the first node and/or the second node in the first network; The first node and/or the second node in the network parses the link attribute information from the notification message or the path reply message.

 The method according to any one of claims 1 to 3, further comprising:

 When the forwarding adjacency label switching path in the second network fails, the node in the second network sends a rerouted new forwarding adjacency label switching path to the first node and/or the second node in the first network. Link attribute information.

 The method according to claim 2, wherein the second network is configured to receive, by the node in the second network, a path request message sent by the first node or the second node in the first network. And: the ingress node in the first second network that forwards the direction of the adjacent label switching path receives the path request message sent by the first node in the first network; and/or, in the second network The receiving, by the node, the path reply message sent by the second node in the first network is: sending, by the egress node in the last second network in the direction of forwarding the adjacency label switching path, the second node in the first network The path replies to the message.

 The method according to claim 5, wherein the sending, by the node in the second network, the link attribute information to the first node and/or the second node in the first network includes:

An entry node in the first second network or an out node in the last second network Pointing, sending the link attribute information to the first node and/or the second node in the first network;

 Or the node in the second network that is adjacent to the label switching path sends the link attribute information of the path in each second network that constitutes the adjacent label switching path to the first network. a node and/or a second node;

 The first node and/or the second node in the first network obtain link attribute information of the adjacency label switching path according to link attribute information of the path in each second network.

 The method according to any one of claims 1 to 3, wherein the link attribute information is a link delay and/or a shared risk link group information.

 A communication device, located in the first network, the method includes: a receiving module, configured to receive link attribute information of a forwarding adjacent label switching path sent by a node in the second network, according to the link attribute information And the communication device establishes an adjacency switching path with another communication device in the first network.

 The communication device according to claim 8, further comprising: a sending module, configured to send, according to the pre-stored link information, a path request message carrying a request for acquisition to a node in the second network or A path reply message is used to obtain link attribute information of the forwarding adjacency label switching path.

 The communication device according to claim 9, further comprising: a first storage module, configured to store link information and forward link attribute information of the adjacent label switching path;

Transmitting, by the sending module, a path request message or a path reply cancellation requesting a bearer acquisition request to a node in the second network according to the link information stored in the first storage module Interest rate

 Receiving, by the receiving module, the link attribute information of the forwarding adjacency label switching path returned by the node in the second network, and storing the link attribute information of the forwarding adjacency label switching path in the first storage module in.

 A communication device, located in the second network, is characterized in that: the information generating module is configured to generate the forwarding adjacency according to the forwarding adjacency label switching path and the pre-stored network topology information of the second network Link attribute information of the label switching path;

 An information sending module, configured to send, to the first node and/or the second node in the first network, link attribute information of the forwarding adjacency label switching path generated by the information generating module, so that the first network A node and the second node are contiguous by the forwarding adjacency label switching path.

 The communication device according to claim 11, further comprising: an information receiving module, configured to receive a path request message or a path reply message sent by the first node or the second node in the first network, And obtaining an acquisition request from the path request message or the path reply message, where the obtaining request is used to obtain link attribute information of the forwarding adjacency label switching path.

The communication device according to claim 12, further comprising: a second storage module, configured to store network topology information of the second network; and/or a path information generating module, configured to generate forwarding Adjacency label switching path; the information generating module according to the forwarding adjacency label switching path generated by the path information generating module, and the network of the second network stored in the second storage module The topology information is generated, and the link attribute information of the forwarding adjacency label switching path is generated.

The communication device according to claim 13, wherein the information receiving module comprises:

 An information receiving unit, configured to receive a path request message;

 An information obtaining unit, configured to parse the obtaining request from the path request message, and send the path request message to the path information generating module;

 The path information generating module generates the forwarding adjacent label switching path according to the path request message.

 The communication device according to any one of claims 11 to 14, wherein the information transmitting module comprises:

 An information generating unit, configured to generate a notification message or a path reply message, and carry the link attribute information of the forwarding adjacent label switching path in the notification message or the path reply message, or forward the adjacency label switching path The link attribute information is carried in the received path request message.

 And an information sending unit, configured to send a notification message or a path reply message or a path request message that carries the link attribute information.

 16. A communication system, comprising: a first communication device in a first network, and a second communication device in a second network,

 And generating, by the second communications device, the link attribute information of the forwarding adjacency label switching path according to the network topology information of the second network and the forwarding adjacency label switching path;

The second communication device sends the link attribute information to the first communication device or the third communication device; according to the link attribute information, the first communication device and the third communication device pass the forwarding Adjacent label switching paths are contiguous.

The communication system according to claim 16, wherein the second communication device comprises: an information generating module, configured to: forward a neighboring label switching path and pre-stored network topology information of the second network according to And generating, by the information sending module, the forwarding adjacency label switching path generated by the information generating module to the first communications device or the third communications device; The first communication device includes: a receiving module, configured to receive link attribute information of the forwarding adjacency label switching path sent by the information sending module.

The communication system according to claim 17, wherein the first communication device further comprises: a sending module, configured to send a bearer acquisition request to the second communication device according to the pre-stored link information. a path request message or a path reply message, where the obtaining request is used to acquire the link attribute information of the forwarding adjacency label switching path to the second communications device; the second communications device further includes:

 The information receiving module is configured to receive a path request message or a path reply message sent by the sending module, and parse the obtaining request from the path request message or the path reply message.