WO2007012223A1

WO2007012223A1 - A method for automatically switched optical network hierarchy routing calculating and connection establishing

Info

Publication number: WO2007012223A1
Application number: PCT/CN2005/001140
Authority: WO
Inventors: Peng Gao
Original assignee: Zte Corporation
Priority date: 2005-07-28
Filing date: 2005-07-28
Publication date: 2007-02-01
Also published as: CN101147348A; CN101147348B

Abstract

A method for automatically switched optical network hierarchy routing calculating and connection establishing, comprises the steps: a), configures each routing area of the optical network and its speaker, forms hierarchy topological relation that can calculate routing by the interaction between the various hierarchies and broadcasting within the routing areas; b) after the entrance network element receives the connection establishing request, sends it to the entrance connection controller CC1 of the routing area RA1;c) each routing area which receives the connection request searches the routing in the routing area by the entrance connection controller, and originates connection establishing, if it is bottom hierarchy routing area, completes the establishment of the optical mark channel in the routing area, proceeds step e), or else, proceeds step d);d) each node connection controller on the routing in the area sends sub network connection establishing request to the corresponding connection controller of the next hierarchy routing area speaker, returns to step c); e) each routing area returns the connection establishing result hierarchy and hierarchy to the entrance network element. The method of the invention makes the signaling interaction process of the routing calculating and the connection establishing hierarchically and consecutively, and is beneficial to complete the connection establishing rapidly.

Description

Automatic exchange optical network hierarchical route calculation and connection establishment method

The present invention relates to the field of Intelligently Switched Optical Network (ASON), and particularly relates to a method for routing calculation and connection establishment in a hierarchical optical network. Background technique

In recent years, communication services such as voice, data, and video have further developed toward integration. The total amount of Internet services has exploded at an exponential rate every year, becoming the main force to swallow the backbone network bandwidth. According to statistics, the annual growth rate of voice traffic worldwide is only 10%, while the annual growth rate of data services reaches 40%. The annual growth rate of data services in China exceeds 400%, and the development is extremely rapid. The continuous growth of traffic, coupled with the sudden, self-similarity and imbalance of Internet services, means that the current SDH/SONET transport network system for voice design and circuit switching needs to The center's next-generation optical network is upgraded and updated as a whole.

In order to adapt to the rapid rise of data services, people realize that the development of optical networks can not only be limited to improving transmission capacity, but more importantly, how to make full use of the networking flexibility brought by the migration of routing and switching into the optical layer. By providing optical network intelligence in a protocol that adds automatic control, this network combines IP efficiency, DWDM capacity, and SDH/SONET robustness with advanced control software to give optical networks unprecedented flexibility and Upgradeability. ASON is one of the best solutions.

After the emergence of ASON network technology, the distributed connection establishment in the ASON network replaces the centralized connection establishment in the traditional optical network. Each node has the connection routing calculation and selection capability, which requires the use of routing protocols to propagate network topology information. . In order to solve the problem that the network topology information propagated in the routing area (RA: Routing Area) increases sharply and seriously affects the network performance after the network scale is expanded, a hierarchical routing scheme is proposed, that is, the network is divided into different levels of routing domains. To limit the scope of routing information exchange through "flooding", G.8080 drafted by ITU-T gives the relationship between routing domain hierarchy and subnet point pool (SNPP), and G.7715 illustrates the path of ASON. By structural requirements.

Currently, the Optical Interconnection Forum (OIF) proposes a draft hierarchical routing using OSPF (Open Shortest Path First) protocol extension, which describes the basic framework of hierarchical routing. However, the automatic exchange optical network hierarchical routing calculation and connection establishment require distributed routing calculation and connection establishment request signaling interaction within the layer and between layers, which does not specify corresponding interaction methods in standard recommendations and protocols. There are no existing methods available.

Summary of the invention

The technical problem to be solved by the present invention is to provide a method for automatically calculating the hierarchical routing calculation and connection establishment of an optical network, and calculating a route in a hierarchical manner for an optical network having a hierarchical structure, and establishing an optical marking channel.

For the sake of clarity and accuracy, the following concepts are defined by combining the ASON hierarchical routing standard recommendations and embodying the features of the method of the present invention:

Node: Control point with control plane routing controller (RC), connection controller (CC), and more. Ingress node: A node in a domain that receives connection establishment requests from users, other routing domains, or other nodes in the domain to complete intra-domain routing calculations. The ingress node corresponds to a specific connection establishment request, and different services may have different ingress nodes.

Speaker: A special node specified in the routing domain for communication with the upper node. The routing controller (RC) of the endorsement point is responsible for the general routing protocol tasks in addition to other nodes. Corresponding routing controller communication at a routing level. At the same time, the connection controller (CC) of the endorsement point is responsible for receiving the upper layer connection request and returning the connection establishment result. If the endorsement point is not the ingress node of the connection request, it needs to be received. The connection request of the upper domain is sent to the corresponding ingress node of the domain.

In order to solve the above technical problem, the present invention provides a method for automatically routing optical network hierarchical routing calculation and connection establishment, which is applied to an optical network having a hierarchical structure, including the following steps:

(a) Configuring each routing domain in the optical network and its endorsement point, and forming a complete layer capable of routing calculation by using the endorsement point to exchange routing information between layers and routing the routing within the domain. Sub-topological relationship;

(b) After receiving the connection establishment request of the user, the ingress network element sends the connection controller CC1 corresponding to the ingress node in the routing domain RA1, and the domain RA1 includes the routing domain in which the service source network element and the destination network element are located;

(c) Each routing domain that receives the connection request queries the routing controller of the ingress node to obtain the intra-domain route, and initiates the connection establishment process in the domain. If the domain is the underlying domain, the establishment of the intra-area optical marking channel is completed. Perform step (e), if the domain also contains the underlying domain, perform step (d);

(d) The connection controller of each node on the route in the domain sends a connection establishment request of the subnet to the connection controller of the end point of the corresponding next layer domain, and returns to step (c);

(e) Each routing domain that receives the connection request returns the connection establishment result to the connection controller CC1 of the routing domain RA1 through the connection controller of its end point, and then returns to the ingress network element that initiated the connection establishment. .

Further, the foregoing method may further have the following features: In the step (a), the interaction of the inter-layer routing information is performed by a routing controller of the endorsement point in each domain and a routing controller of the corresponding node of the upper layer domain, the layer The routing controller understands the network topology in the domain through the "flooding" process in the domain, so that the routing controllers of each node in the routing domain have the routing information of the local domain and all the lower routing domains included in the domain.

Further, the above method may further have the following features: In the step (b), the ingress network element determines the routing domain RA1 to which the connection request should be sent according to the domain inclusion relationship obtained from the directory server.

Further, the above method may further have the following features: In the step (a), for each of the endorsement points, a corresponding routing controller is configured in the upper layer domain. Further, the foregoing method may further have the following features: Step (c) In the connection establishment process in the routing domain, after the connection controller of the node on the route receives the connection establishment message, negotiates to allocate the link connection, and then goes to the domain. The connection controller of the next node sends a connection establishment message, if the routing controller of the node corresponds to a next layer domain and the next layer domain is covered by the subnet connection In the routing domain, the connection controller of the node also sends a subnet connection establishment request to the connection controller of the next layer domain endorsement point.

Further, the foregoing method may also have the following features: The connection establishment process in the routing domain adopts an RS VP signaling process.

Further, the above method may further have the following features: the node in the step (d) is connected to the controller of the next layer domain, and the routing controller of the same node as the connection controller is configured. The corresponding end point of the next level domain.

Further, the foregoing method may further have the following features: in the step (d), after the connection controller of the endorsement point receives the subnet connection establishment request, if the endorsement point is not the ingress node of the connection request, the The subnet connection establishment request is sent to the ingress node corresponding to the domain.

Further, the foregoing method may further have the following features: in the step (e), the connection controller of each node in each intra-domain route receives the connection establishment result returned by the next node on the route, and corresponds to the next layer domain. When the next layer domain is the routing domain covered by the subnet connection, the connection establishment result returned by the domain end point connection controller is also received, and then the connection establishment result is returned to the previous node, and the connection is received. When the result of the establishment is successful, the result of the successful connection establishment is returned. Otherwise, the result of the failure is returned, and the resource release processing is performed on the established connection.

Further, the foregoing method may also have the following features: In the method, the signaling interaction process between different routing domains without a relationship is a parallel process.

It can be seen that, by using the method of hierarchical routing calculation and connection establishment of the automatic switched optical network of the present invention, the interaction process of the route calculation and the connection establishment signaling can be hierarchical and organized, and the hierarchical route connection establishment is performed in parallel for fast connection. The establishment provides the foundation. BRIEF abstract

FIG. 1 is a schematic structural diagram of a hierarchical optical network according to an embodiment of the present invention.

2 is a corresponding diagram of a routing controller and a lower layer network domain according to an embodiment of the present invention.

FIG. 3 is a schematic diagram of signaling interaction of connection establishment in an embodiment of the present invention. BEST MODE FOR CARRYING OUT THE INVENTION

The hierarchical optical network structure of this embodiment will be described below with reference to FIG.

As shown in Figure 1, the network consists of four layers, each layer consisting of a number of routing domains. Each routing domain consists of a control plane component and a transport plane resource, and is physically associated with a certain number of network elements including a control plane logic processing board, each control plane logic processing board including a connection controller (CC), routing control Control plane processing functions such as RC and Link Resource Management (LRM) logically refer to control points with functions such as control plane routing controller (RC) and connection controller (CC) as nodes. The routing controllers and connection controllers of the same number mentioned below refer to different control function modules of the same node at the physical level. For example, the routing controller N123 and the connection controller N123 refer to different control functions of the same node. Only some of the nodes in the domain are shown in the figure.

The bottom layer of the hierarchical optical network structure of Figure 1 contains seven routing domains: L1RAK L1RA2, L1RA3, L1RA4, L3RA2, L2RA3, L2RA4, where the bottom layer refers to the layer closest to the transport plane, and L3RA2 and L2RA3, L2RA4 are logically three. Layer and second layer, but belong to the bottom layer. The network element nodes N1 ll, N112, N121, N122, N13, N132, N141, N142, N321, N322, N23, N232, N241, and N242 are transport layer network elements that physically have optical connections, and the routing domain L1RA1 is composed of network elements N111. N112 and control plane logic processing functions are implemented, and other underlying routing domains are similar to routing domain L1RA1.

The routing domain L2 A1, L2RA2, L2RA3, and L2RA4 form a logical second layer. The routing domains L3RA1, L3RA2, and L3 A3 form a logical third layer, and the routing domain L4RA constitutes a logical fourth layer.

Relationship between routing domain L4RA and routing domains L3RA1, L3RA2, L3RA3, relationship between routing domain L3RA1 and routing domain L2RA1, L2RA2, relationship between routing domain L3RA3 and routing domain L2RA3. L2RA4, routing domain L2RA1 and routing domain The relationship between L1RA1 and L1RA2 and the relationship between the routing domain L2RA2 and the routing domains L1RA3 and L1RA4 satisfy the inclusion policy recommended by ITU-T G.8080. Hereinafter, the routing domains L3RA1, L3RA2, and L3RA3 are referred to as the routing domain L4RA. The next layer domain, the next layer domain L2RA1, L2RA2 included in the domain L3RA1 is referred to as the routing domain included in the upper layer domain L4RA, and so on. The user first configures the optical network hierarchy and domain endorsement points through the management plane. The black filled network element node in Figure 1 is the endorsement point specified by the management plane. For each endorsement point, a corresponding routing controller is configured in the upper layer routing domain.

In Figure 1, nodes N111, N12, N131, and N141 are the endorsement points of the routing domains L1RA1, L1RA2, L1RA3, and L1RA4, respectively. Nodes N211, N212, N221, and N222 are the endorsement points N1ll, N121, N131, and N141, respectively. The node where the corresponding routing controller is located on the layer. Nodes N212 and N221 are the endorsement points of the routing domains L2RA1 and L2RA2, respectively. Nodes N311 and N312 are the nodes where the corresponding routing controllers on the third layer are the endorsement points N212 and N221, respectively. Node N311 is the end point of the routing domain L3RA1, and node N411 is the node where the routing controller corresponding to the N311 on the fourth layer is located. Node N321 is the end point of the routing domain L3RA2, and node N412 is the node where the corresponding routing controller of the third layer on the fourth layer. The nodes N231 and N241 are the endorsement points of the routing domains L2RA3 and L2RA4, respectively, and the nodes N331 and N332 are the nodes where the routing controllers corresponding to the third layer and the N231 and N241 are respectively located. Node N331 is the end point of the routing domain L3RA3, and node N413 is the node where the routing controller N331 corresponds to the routing controller on the fourth layer. The L4RA domain is the top-level routing control domain and has no endorsement points.

The routing controller of the local layer learns the network topology in the domain through the "flooding" process in the domain. Some routing controllers in the local domain are also responsible for communicating with the corresponding lower-layer routing domain, and knowing the routing information of the corresponding lower-layer routing domain. And distributed in the routing domain "flooding", forming a stable hierarchical relationship that can be used for routing calculation. The routing controller of each node in each routing domain has this routing domain and all the lower-layer routes included in the routing domain. The routing information of the domain, each node can respond to the routing query request and calculate the intra-domain route. Figure 2 shows the correspondence between the routing controller and the routing control domain of the underlying network. For example, the routing controller of node N211 corresponds to routing control domain L1RA1, the routing controller of node N212 corresponds to routing control domain L1RA2, and so on.

The flow of the embodiment of the present invention will be described below with reference to Figs. 1, 2 and 3. FIG. 3 is a schematic diagram of signaling interaction for establishing a hierarchical routing connection in the embodiment. A line marked with S+ digits indicates a forwarding process of signaling, and hundreds and ten digits of the number indicate a sequence number of the process, and the number of digits indicates Different processing examples. The single digits of the signaling procedure within the same domain indicate the order of the signaling procedures, excluding the processing time of the connection setup signaling. It should be noted that although the following process involves signaling interaction between different domains. The process is written in one step, but only for the sake of simplicity. The signaling interaction process between different domains is a parallel process, and there is no order relationship.

As shown in FIG. 2, it is assumed that the user requests the optical network to establish a connection from the network element Ni1 to the network element N242. The user specifies the label of the network element N111 and the outgoing label of the network element N242, where The tag "refers to the point of the upper and lower business, the corresponding physical concept, which can be a port on the device. This process is shown in process 11 in Figure 3.

Step 1: The ingress network element N111 receives the connection request of the user, and according to the domain inclusion relationship, determines to directly send the connection establishment request to the corresponding ingress connection controller N411 in the fourth layer routing domain L4RA, and the process is in FIG. S11 shows;

Here, if the source and destination of the service need to be resolved across layers, the connection establishment request needs to be sent to the upper routing domain, which needs to span several layers, and the domain inclusion relationship can be obtained according to various methods such as "directory server". To determine that the upper-layer domain needs to include the domain where the network elements at both ends of the service are located.

Step 2: The connection controller N411 queries the routing controller of the node, and the routing controller N411 calculates the routing result in the domain L4RA as N411<→N412<->N413, and then connects the controller N411 to the connection controller N412, and the connection control The device N412 sequentially initiates a connection establishment process to the connection controller N413, which is illustrated in FIG. 3 by process S21 and process S22;

The specific method for calculating the intra-domain route is not limited in the present invention. The connection establishment process in the domain may adopt the RSVP signaling process. After receiving the Path message, the connection controller of the node N412 negotiates to allocate the link connection, and sends a Path message to the connection controller of the next node N413 in the domain, if the route control of the node The device (or other corresponding routing controller) corresponds to the included lower layer domain, and the connection controller also needs to send a subnet connection establishment request to the connection controller of the next layer domain end point.

Step 3: After receiving the connection establishment request, the connection controllers N411, N412, and N413 in the domain L4RA determine the inbound and outbound NEs of the next-layer routing domain covered by the subnet connection based on the inclusion relationship of the routing domain, and establish the subnet connection. The request is sent to the endorsement points N311, N321, and N331 of the lower layer network corresponding to the routing controller of the same node (which can also be specifically designated). This process is shown in FIG. The processes S31, S32 and S33 show that if the routing controller of the node on the route does not have a corresponding routing layer of the next layer or the routing domain of the next layer is not covered by the subnet connection, there is no need to send a subnet connection establishment request. ;

Step 4: The end points N311 and N331 of the domain L3RA1 and L3RA3 are also the ingress nodes of the connection. After receiving the subnet connection establishment request, the intra-domain routes are respectively calculated in the domains L3RA1 and L3RA3, and the endorsement point N311 is calculated in the domain L3RA1. The routing result is N311<->N312, and the routing result calculated by the end point N331 in the domain L3RA3 is N331<->N332, and the end point N311 and the endorsement point N331 respectively initiate a connection establishment process to N312 and N332 according to the routing calculation result. This process is illustrated in Figure 3 by process S41 and process S42;

Step 5: The connection controllers N311 and N312 in the domain L3RA1 send the subnet connection establishment request to the endorsement points N212 and N221 of the lower layer network corresponding to the routing controller of the same node according to the inclusion relationship of the routing domain; likewise, in the domain L3RA3 The connection controllers N331 and N332 send subnet connection establishment requests to the endorsement points N231 and N241 of the lower layer network corresponding to the routing controller of the same node. This process is illustrated in Figure 3 by processes S51, S52, S53 and S54;

Step 6, after the domain L2RA1 and L2RA2 endorsement points N212 and N221 receive the subnet connection establishment request, in the domain L2RA1, the endorsement point N212 is not the ingress node of the subnet connection, and the subnet connection establishment request needs to be sent to the domain. The ingress node N211, the process is shown in the process S55 in FIG. 3; the end point (also the ingress node) N221 in the node N211 and the domain L2RA2 in the domain L2RA1 respectively calculate the intra-domain route, and the route result calculated by the node N211 in the domain L2RA1 is N211<->N212, the routing result calculated by the end point N221 in the domain L2RA2 is N221<→N222, and the node N211 and the endorsement point N221 initiate a connection establishment process to N212 and N222 according to the routing calculation result. This process is illustrated in Figure 3 by process S61 and process S62;

Step 7, according to the inclusion relationship of the routing domain, the connection controllers N211 and N212 in the domain L2RA1 send the subnet connection establishment request to the endorsement points N1 11 and N121 of the lower layer network corresponding to the routing controller of the same node; likewise, the domain L2RA2 The connection controllers N221 and N222 send the subnet connection establishment request to the endorsement points N131 and N141 of the lower layer network corresponding to the routing controller of the same node, and the process is shown in FIG. 3 by processes S71, S72, S73, and S74;

Step 8, the underlying routing domains L1RA1, L1RA2, L1RA3, L1RA4, L3RA2, L2RA3, The connection controllers Nl ll, N12 N131, N141, N321, and N23 N241 of the L2RA4 end point (also the ingress node) calculate the routes in their respective domains after receiving the subnet connection request, and the calculation results are as follows: N111<->N112, N121 <—>N122, N131<—>N132, N141<—>N142, N32K—>N322, N231<— >232 N24K→N242, perform the connection establishment process in each domain as shown by the dashed line in Fig. 3, and perform intra-area optical marking The establishment of a path (data transmission channel). The underlying domain performs the actual data path establishment process. Each of the underlying domains is successfully established, and the entire service is successfully created. The data flow will pass through the ingress NE N111 through the NEs N112, N12 N122, N13 N132, N141 of each underlying domain. N142, N32 N322, N23 N232, and N241 arrive at the egress network element N242.

The connection controller of each intra-domain node returns the connection establishment result to the connection controller of the endorsement point in the domain (if the endorsement point is not the ingress node, each node first returns the connection establishment result to the connection controller of the ingress node, and then sends it to the connection controller The connection controller of the domain end point, the connection controller of the endorsement points N1 ll, N12K N13 N141, N321, N23 N241 returns the connection establishment result to the upper layer routing domain nodes N211, N212 to which the connection establishment request is sent. , N22 N222, N412, N331, N332 connection controller. This process is illustrated in Figure 3 by processes S81, S82, S83, S84, S85, S86, S87;

Step 9. The connection controllers N212 and N222 that receive the connection establishment result returned by the next layer in the domain L2RA1 and L2RA2 respectively return the connection establishment result to the connection controllers of the local node entry nodes N211 and N221, and the process is as follows: Processes S88 and S92 in 3. Since the N211 is not an endorsement point, the connection establishment result is sent to the connection controller of the domain end point N212, and the process is as shown in process S91 in FIG. 3;

Step 10: The connection controllers of the domains L2RA1 and L2RA2 The connection controllers of N212 and N221 return the connection establishment result to the connection controller of the upper-layer routing domain nodes N311 and N312 to which the connection establishment request is sent. This process is shown in processes S101 and S102 in FIG. 3;

Step 11: The connection controllers N311 and N312 that receive the connection establishment result in the next layer of the domain L3RA1 and L3RA3 respectively return the connection establishment result to the connection controller of the local access nodes N311 and N331, as shown in FIG. Processes S11, S112;

Step 12: The connection controllers of the end points N311 and N331 of the domains L3RA1 and L3RA3 return the connection establishment result to the upper-layer routing domain nodes N411 and N413 to which the connection establishment request is sent. Connection controller. As shown in processes S121 and S122 in FIG. 3;

In step 13, the connection controller N413 in the domain L4RA that receives the connection establishment result of the next layer returns the connection establishment result to the connection controller of the N412, and the connection controller of the N412 returns the connection establishment result to the local node. a connection controller of the N411, as shown in processes S131 and S132 in FIG. 3;

Step 14. After receiving the connection establishment result in the intra-domain and the inter-layer, the connection controller of the node N411 returns the result to the node Nl l l that initially initiates the connection establishment. As shown in process N141 in Figure 3.

In an embodiment, the inter-layer subnet connection establishment request is a connection controller sent to the next layer domain end point. If the endorsement point is not an ingress node of the subnet connection, the subnet connection establishment request is also forwarded to the domain. The connection controller of the ingress node performs route calculation and initiates the connection establishment process. The calculation by the ingress node is a "source route" mode, which can simplify the signaling interaction process.

The connection controller of each node on the intra-domain route receives the connection establishment result returned by the next node on the route, and corresponds to the next-layer domain, and also receives the connection establishment result returned by the domain end point connection controller. And return the connection establishment result to the previous node. When the received connection establishment result is successful, the result of the successful connection establishment is returned. Otherwise, the failed result is returned. In this way, as long as the route calculation or connection establishment failure of any routing domain that receives the connection establishment request fails, the entire connection establishment failure is considered, the failure information is returned to the entry network element, and the resource release processing is performed on the established connection.

In summary, the interaction process of the hierarchical routing query information used by the present invention provides a hierarchically well-defined route calculation query method when the network scale is large.

Industrial applicability

The method for hierarchical routing calculation and connection establishment of the automatic switched optical network of the present invention can be applied to an intelligent optical network, so that the interaction process of the route calculation and the connection establishment signaling is hierarchical and organized, and the hierarchical route connection establishment is performed in parallel for fast connection. The establishment provides the foundation.

Claims

Claim

A method for automatically switching optical network hierarchical route calculation and connection establishment, applied to an optical network having a hierarchical structure, comprising the following steps:

(a) configuring each routing domain in the optical network and its endorsement point, and forming a complete hierarchical topology relationship that can perform route calculation by using the end point to exchange routing information between the layers and broadcasting the routes in the domain;

(c) The routing domain that receives the connection request is queried by the connection controller of the ingress node to obtain the intra-domain route, and initiates the connection establishment process in the domain. If the domain is the underlying domain, the establishment of the intra-area optical marking channel is completed. Step (e), if the domain also has a lower domain included, perform step (d);

(e) Each routing domain that receives the connection request returns the connection establishment result to the connection controller CC1 of the routing domain RA1 through the connection controller of its endorsement point, and then returns to the ingress network element that initiated the connection establishment. .

2. The method according to claim 1, wherein in the step (a), the interaction of the inter-layer routing information is performed by a routing controller of the endorsement point in each domain and a routing controller of the corresponding node of the upper layer domain. The routing controller of the local layer understands the network topology in the domain through the "flooding" process in the domain, so that the routing controllers of each node in the routing domain have the routing information of the local domain and all the lower routing domains included in the domain.

The method according to claim 1, wherein in the step (b), the ingress network element determines, according to a domain inclusion relationship obtained from a directory server, a routing domain RA1 to which a connection request should be sent. .

4. The method according to claim 1, wherein in the step (a), each The endorsement point is configured with a corresponding routing controller in its upper layer domain.

The method according to claim 4, wherein in the step (c) of establishing a connection in the routing domain, the connection controller of the node on the route receives the connection establishment message and negotiates to allocate the link connection. And sending a connection establishment message to the connection controller of the next node in the domain. If the routing controller of the node corresponds to a lower layer domain and the next layer domain is a routing domain covered by the subnet connection, the node is The connection controller also sends a subnet connection establishment request to the connection controller of the next layer domain endorsement point.

6. The method according to claim 5, wherein the connection establishment process in the routing domain adopts an RS VP signaling process.

The method according to claim 4, wherein the node in the step (d) is connected to the controller of the next layer corresponding to the controller, and refers to the routing controller of the same node as the connection controller. The endorsement point of the next level domain corresponding to the configuration.

8. The method according to claim 1, wherein in the step (d), after the connection controller of the endorsement point receives the subnet connection establishment request, if the endorsement point is not the entry node of the connection request, The subnet connection establishment request needs to be sent to the corresponding ingress node of the domain.

The method according to claim 4, wherein in the step (e), the connection controller of each node on each intra-domain route receives the connection establishment result returned by the next node on the route, corresponding to the next When the one-layer domain and the next-layer domain are the routing domains covered by the subnet connection, the connection establishment result returned by the domain endpoint connection controller is also received, and then the connection establishment result is returned to the previous node. When the received connection establishment result is successful, the result of the successful connection establishment is returned. Otherwise, the result of the failure is returned, and the resource release processing is performed on the established connection.

10. The method according to claim 1, wherein in the method, the signaling interaction process between different routing domains not including the relationship is a parallel process.