Method for establishing service path, network device, and system

Abstract

This application provides example methods for establishing a service path in a transport network and example systems. One example method includes, obtaining, by an automatically switched optical network (ASON) first node, a service path computation result path. The service path includes the ASON first node, an ASON last node, and at least one first edge network node. The method also includes sending, by the ASON first node, a path establishment request message to a downstream node. The path establishment request message carries cross-connection configuration information of the ASON last node and the at least one first edge network node. The method further includes receiving, by the ASON first node, a path establishment response message of the downstream node. The path establishment response message indicates that cross-connection configuration for the ASON last node and the at least one first edge network node is complete.

Claims

1. A method for establishing a service path in a transport network, wherein the service path passes through an automatically switched optical network (ASON) and at least one edge network, and wherein the method comprises: obtaining, by an ASON first node, a service path computation result, wherein the service path comprises the ASON first node, an ASON last node, and at least one first edge network node; sending, by the ASON first node, a path establishment request message to a downstream node, wherein the path establishment request message carries cross-connection configuration information of the ASON last node and the at least one first edge network node, wherein cross-connection of the at least one first edge network node is configured by the ASON last node; and receiving, by the ASON first node, a path establishment response message of the downstream node, wherein the path establishment response message indicates that cross-connection configuration for the ASON last node and the at least one first edge network node is complete.

2. The method according to claim 1, wherein the method further comprises: sending, by the ASON first node, respective cross-connection configuration information to each of at least one second edge network node.

3. The method according to claim 2, wherein the method further comprises: sending, by the ASON first node, respective cross-connection configuration information to each of the at least one second edge network node by an edge control protocol, wherein the edge control protocol is a constrained application protocol (COAP).

4. The method according to claim 2, wherein the ASON first node is a node that supports an ASON protocol, the at least one second edge network node is a node that does not support the ASON protocol, and the ASON first node is a control node of the at least one second edge network node.

5. The method according to claim 1, wherein the cross-connection configuration information of the at least one first edge network node is indicated by a sub-type-length-value (TLV) of the ASON last node.

6. The method according to claim 1, wherein the ASON last node is a node that supports an ASON protocol, the at least one first edge network node is a node that does not support the ASON protocol, and the ASON last node is a control node of the at least one first edge network node.

7. A method for establishing a service path in a transport network, wherein the service path passes through an automatically switched optical network (ASON) and at least one edge network, and wherein the method comprises: receiving, by an ASON last node, a path establishment request message from an upstream node, wherein the path establishment request message carries cross-connection configuration information of the ASON last node and at least one edge network node, and the service path comprises an ASON first node, the ASON last node, and the at least one edge network node, wherein cross-connection of the at least one edge network node is configured by the ASON last node; and sending, by the ASON last node, a path establishment response message to the upstream node, wherein the path establishment response message indicates that cross-connection configuration for the ASON last node and the at least one edge network node is complete.

8. The method according to claim 7, wherein the method further comprises: sending, by the ASON last node, respective cross-connection configuration information to each of the at least one edge network node.

9. The method according to claim 7, wherein the method further comprises: sending, by the ASON last node, respective cross-connection configuration information to each of the at least one edge network node by an edge control protocol, wherein the edge control protocol is a constrained application protocol (COAP).

10. The method according to claim 7, wherein the cross-connection configuration information of the at least one edge network node is indicated by a sub-type-length-value (TLV) of the ASON last node.

11. The method according to claim 7, wherein the ASON last node is a node that supports an ASON protocol, the at least one edge network node is a node that does not support the ASON protocol, and the ASON last node is a control node of the at least one edge network node.

12. The method according to claim 11, wherein when the ASON last node is a secondary control node of the at least one edge network node, the method further comprises: sending, by the ASON last node, the cross-connection configuration information of the at least one edge network node to a primary control node of the at least one edge network node.

13. A network system, comprising: an automatically switched optical network (ASON); and at least one edge network, wherein the ASON comprises: an ASON first node; and an ASON last node, wherein the ASON first node comprises:  at least one first node processor;  a non-transitory computer-readable first node storage medium coupled to the at least one first node processor and storing first node programming instructions for execution by the at least one first node processor, wherein the first node programming instructions instruct the at least one first node processor to cause the ASON first node to:  obtain a service path computation result, wherein a service path comprises the ASON first node, the ASON last node, and at least one first edge network node; and  send a path establishment request message to a downstream node, wherein the path establishment request message carries cross-connection configuration information of the ASON last node and the at least one first edge network node, wherein cross-connection of the at least one first edge network node is configured by the ASON last node, wherein the ASON last node comprises:  at least one last node processor;  a non-transitory computer-readable last node storage medium coupled to the at least one last node processor and storing last node programming instructions for execution by the at least one last node processor, wherein the last node programming instructions instruct the at least one last node processor to cause the ASON last node to:  receive the path establishment request message from an upstream node; and  send a path establishment response message to the upstream node, wherein the path establishment response message indicates that cross-connection configuration for the ASON last node and the at least one first edge network node is complete, and wherein the first node programming instructions further instruct the at least one first node processor to cause the ASON first node to: receive the path establishment response message of the downstream node.

14. The network system according to claim 13, wherein the first node programming instructions further instruct the at least one first node processor to cause the ASON first node to: send respective cross-connection configuration information to each of at least one second edge network node.

15. The network system according to claim 14, wherein the ASON first node is a node that supports an ASON protocol, wherein the at least one second edge network node is a node that does not support the ASON protocol, and wherein the ASON first node is a control node of the at least one second edge network node.

16. The network system according to claim 13, wherein the last node programming instructions further instruct the at least one last node processor to cause the ASON last node to: send respective cross-connection configuration information to each of the at least one first edge network node.

17. The network system according to claim 13, wherein the last node programming instructions further instruct the at least one last node processor to cause the ASON last node to: send respective cross-connection configuration information to each of the at least one first edge network node by an edge control protocol, wherein the edge control protocol is a constrained application protocol (COAP).

18. The network system according to claim 13, wherein the cross-connection configuration information of the at least one first edge network node is indicated by a sub-type-length-value (TLV) of the ASON last node.

19. The network system according to claim 13, wherein the ASON last node is a node that supports an ASON protocol, wherein the at least one first edge network node is a node that does not support the ASON protocol, and wherein the ASON last node is a control node of the at least one first edge network node.

20. The network system according to claim 19, wherein when the ASON last node is a secondary control node of the at least one first edge network node, the last node programming instructions further instruct the at least one last node processor to cause the ASON last node to: send the cross-connection configuration information of the at least one first edge network node to a primary control node of the at least one first edge network node.

Description

BRIEF DESCRIPTION OF DRAWINGS

(1) To clearly describe the technical solutions of the embodiments of the present disclosure, the following briefly describes the accompanying drawings used in describing the embodiments.

(2) FIG. 1 is a schematic diagram of a network architecture in the current technology;

(3) FIG. 2 is a schematic diagram of a network architecture according to an embodiment of the present disclosure;

(4) FIG. 3 is a diagram of a network architecture of an application scenario according to an embodiment of the present disclosure;

(5) FIG. 4 is an example flowchart of a method for establishing a service path according to an embodiment of the present disclosure;

(6) FIG. 5 is a schematic diagram of service path configuration performed by using RSVP-TE signaling according to an embodiment of the present disclosure;

(7) FIG. 6 is a schematic diagram of an extended packet format of a path message according to an embodiment of the present disclosure;

(8) FIG. 7 is a diagram of a network architecture of an application scenario according to an embodiment of the present disclosure;

(9) FIG. 8 is an example flowchart of a method for establishing a service path according to an embodiment of the present disclosure;

(10) FIG. 9 is a diagram of a network architecture of an application scenario according to an embodiment of the present disclosure;

(11) FIG. 10 is an example flowchart of a method for establishing a service path according to an embodiment of the present disclosure;

(12) FIG. 11 is a diagram of a network architecture of an application scenario according to an embodiment of the present disclosure;

(13) FIG. 12 is an example flowchart of a method for establishing a service path according to an embodiment of the present disclosure;

(14) FIG. 13 is a diagram of a network architecture of an application scenario according to an embodiment of the present disclosure;

(15) FIG. 14 is an example flowchart of a rerouting method according to an embodiment of the present disclosure; and

(16) FIG. 15 is a schematic diagram of a logical structure of a network device according to an embodiment of the present disclosure.

DESCRIPTION OF EMBODIMENTS

(17) To make the objectives, technical solutions, and advantages of the present disclosure clearer and more comprehensible, the following further describes the present disclosure in detail with reference to the accompanying drawings and embodiments.

(18) FIG. 2 is a schematic diagram of a network architecture according to an embodiment of the present disclosure. As shown in FIG. 2, a network architecture 200 includes a node A, a node 13, a node C, and a node D. The nodes B and C are metropolitan area/core network nodes, and support an ASON/GMPLS protocol. The nodes A and D are edge network nodes, and cannot support the ASON protocol due to insufficient hardware resources. The metropolitan area/core network nodes B and C may also be referred to as ASON nodes. The ASON/GMPLS protocol supported by the metropolitan area/core network nodes B and C includes open shortest path first (OSPF), a constrained shortest path first (CSPF), RSVP-TE, and the like. For example, the ASON node may obtain information, such as resource information such as a node and a link, about another node in an entire network through OSPF. The ASON node may further compute an end-to-end service path through CSPF and establish the end-to-end service path by using RSVP-TE signaling. An edge control agent (ECA) is configured for the edge network nodes A and D, and an edge control unit (ECU) is configured for the ASON nodes B and C. The ECA is mainly configured to collaborate with the ECU to implement an automation capability (including automatic discovery and service configuration) of the edge network node. For example, the ECA may report resource information such as a node and a link of the edge network to the ECU, and collaborate with the ECU to configure a service for the edge network node. The ECU performs centralized control on the edge network to complete topology discovery (automatic discovery of the edge network node) and automatic service configuration of the edge network. The service configuration may include processes such as service establishment, deletion, modification, and recovery. For example, the ECU may discover the edge network node according to an automatic route discovery mechanism, or may collect the resource information such as the node and the link of the edge network through an edge control protocol, and configure a service for the edge network node, and the like. An RSVP control apparatus is further configured for the nodes B and C, to run the RSVP-TE signaling to automatically configure an end-to-end service. In the current technology, because the edge network node cannot support automatic service configuration, configuration can only be manually performed by using a network management system. In the embodiments of the present disclosure, the ECU may automatically configure a service for the edge network node, thereby improving service provisioning efficiency and accuracy. The following describes the technical solutions of the embodiments of the present disclosure by using different application scenarios.

(19) FIG. 3 is a diagram of a network architecture of an application scenario according to an embodiment of the present disclosure. As shown in FIG. 3, a network architecture 300 includes an edge network 301, a metropolitan area/core network 302, and an edge network 303. The edge network 301 and the edge network 303 do not support an ASON protocol, the edge network 301 includes edge network nodes A, B, and C, and the edge network 303 includes edge network nodes J, K, and L. The metropolitan area/core network 302 supports the ASON protocol, and the metropolitan area/core network 302 includes ASON nodes D, E, F, G, H, and I. The metropolitan area/core network 2 is also referred to as an ASON or a GMPLS network. An ECA may be deployed for the edge network node, for example, the ECA is deployed for each of the edge network nodes A, B, C, J, K, and L. An ECU may be deployed for the ASON node, for example, the ECU is deployed for the ASON nodes D and I connected to the edge network. Functions of the ECA and the ECU are similar to those in FIG. 2. Details are not described herein. The edge network nodes A, B, and C are located within a control scope of the ASON node D. As a control node of the edge network nodes A, B, and C, the ASON node D can discover the edge network nodes A, B, and C according to an automatic route discovery mechanism. The edge network nodes J, K, and L are located in a control scope of the ASON node I. As a control node of the edge network nodes J, K, and L, the ASON node I can discover the edge network nodes J, K, and L according to the automatic route discovery mechanism. The ASON nodes D, E, F, G, H, and I can discover each other according to the automatic route discovery mechanism (an OSPF protocol). Optionally, the network architecture 300 may further include a path computation element (PCE) that may be deployed on a network management system or any network device (such as the ASON node). The PCE automatically obtains information such as a node, a link, and a service of an entire network through OSPF or through a path computation element communication protocol (PCEP), to implement centralized service path computation. If there is no PCE in the network architecture, distributed service path computation may be implemented by using a plurality of network nodes or all network nodes. Optionally, the network architecture 300 may further include the network management system, and the network management system may be a server, a controller, or the like. In this embodiment of the present disclosure, a service may be automatically configured through an extended RSVP-TE protocol. The following uses establishment of a service path A-B-D-E-F-I-J-L across the edge network 301, the metropolitan area/core network 302, and the edge network 303 as an example for description. FIG. 4 is an example flowchart of a method for establishing a service path according to an embodiment of the present disclosure. The method includes the following steps.

(20) Step 401: A user requests a network management system to establish a service path from the edge network node A to the edge network node L.

(21) The user may send a service path establishment request message to the network management system. The request message carries a source node A and a sink node L of the service path, and optionally may further carry bandwidth between A and L, a service level agreement (SLA), and the like.

(22) Step 402: The network management system delivers service configuration information to the source node A of the service path to request to establish the service path from A to L.

(23) The service configuration information may include the source node A and the sink node L of the service path, and may further include information such as the bandwidth and the SLA. The edge network node A is configured as an ECA, and does not have a path computation capability. In addition, the edge network node A is located within a management scope of the ASON node D (an ECU), in other words, the node D is a control node of the node A. The node A may request through an edge control protocol, the node D to compute an end-to-end service path from A to L. For example, the node A sends, to the node D through a constrained application protocol (COAP), service configuration information specified by the user, namely, information such as the source node A, the sink node L, and the bandwidth. Optionally, if the node A has the path computation capability, the node A may alternatively directly compute the end-to-end service path from A to L. For example, the node A may compute a service path A-B-D-E-F-I-J-L through CSPF.

(24) Step 403: The node D obtains a path computation result, where the path includes an ASON last node and at least one edge network node.

(25) If the node A (the ECA) does not have the path computation capability, the node D (the ECU) receives a service path request from the node A. If there is a PCE in a network, the node D (the ECU) may request, through a PCEP, the PCE to compute the end-to-end service path from A to L, and obtain a service path computation result A-B-D-E-F-I-J-L from the PCE. Optionally, the path computation result further includes information such as a timeslot and a wavelength. If there is no PCE in the network, the node D (the ECU) may alternatively compute the service path. If the node A (the ECA) has the path computation capability, the node D (the ECU) may receive the path computation result from the node A. In A-B-D-E-F-I-J-L, A-B-D and I-J-L are sub-paths in an edge network, and D-E-F-I is a sub-path in a metropolitan area/core network. Nodes A, B, J, and L are edge network nodes, and nodes D, E, F, and I are ASON nodes. The edge network nodes A and B are within a control scope of the node D (the ECU), and the edge network nodes J and L are within a control scope of the node I (an ECU). In the service path A-B-D-E-F-I-J-L, the node A is a source node of a service, the node L is a sink node of the service, the node D is an ASON first node, and the node I is an ASON last node.

(26) Step 404: The node D sends a path establishment request message to a downstream node, where the path establishment request message carries at least cross-connection configuration information of the ASON last node and at least one edge network node.

(27) After the node D (the ECU) obtains the service path computation result A-B-D-E-F-I-J-L, the node D (the ECU) allocates a service session ID. The session ID is unique on this node and is used to identify the service path.

(28) The sub-path A-B-D belongs to the edge network, and a service of the sub-path A-B-D is directly configured by the node D (the ECU) through the edge control protocol, for example, the node D (the ECU) configures cross-connections for the nodes A and B station by station through the constrained application protocol (COAP). A cross-connection configuration message sent by the node D to the nodes A and B may include inbound interface information and outbound interface information. The inbound interface information may include one or more of a subrack, a slot, a port, a channel (a timeslot or a wavelength), and the like of an inbound interface. The inbound interface information may also include an inbound link identifier, and the inbound link identifier may indicate a subrack, a slot, and a port of the inbound interface. The outbound interface information may include one or more of a subrack, a slot, a port, a channel (a timeslot or a wavelength), and the like of an outbound interface. The outbound interface information may also include an outbound link identifier, and the outbound link identifier may indicate a subrack, a slot, and a port of the outbound interface.

(29) The sub-path D-E-F-I belongs to the metropolitan area/core network (supporting a GMPLS/ASON protocol), and a sub-path J-L belongs to the edge network. Cross-connections may be configured for nodes J and L through an extended RSVP-TE protocol. Cross-connections are configured hop by hop by using the node D as a first node of RSVP-TE signaling (namely, the ASON first node) and the node I as a last node of the RSVP-TE signaling (namely, the ASON last node).

(30) FIG. 5 is a schematic diagram of service path configuration performed by using RSVP-TE signaling according to an embodiment of the present disclosure. The ASON first node D performs forward cross-connection configuration for the ASON last node I hop by hop. As shown in FIG. 5, the node D sends a path message to a downstream node E, and the path message carries at least cross-connection configuration information of the ASON last node I. Optionally, the path message may further carry cross-connection configuration information of each ASON intermediate node, for example, nodes E and F. The cross-connection configuration information of the ASON node may include outbound interface information of the ASON node, for example, an outbound link identifier and an outbound label (namely, a channel number), and may be carried by an explicit route object (ERO). Before sending the path message, the node D may establish a cross-connection from an interface I to an interface 1. Optionally, the path message may further carry cross-connection configuration information of other downstream nodes, for example, the nodes E and F. The node D sends the path message to an interface 2 of the downstream node E by using the interface 1 of the node D. If the path message carries the cross-connection configuration information of the node E, the node E establishes a cross-connection from the interface 2 to an interface 3 based on the cross-connection configuration information in the path message. The node E sends the path message to an interface 4 of the downstream node F by using the interface 3. After receiving the path message, similar to the node E, the node F establishes a cross-connection from the interface 4 to an interface 5, and sends the path message to the node I. After receiving the path message, similar to the node F, the node I establishes a cross-connection from an interface 6 to an interface O. The nodes D, E, and F may establish cross-connections before sending the path message to adjacent downstream nodes, or may establish cross-connections after sending the path message, or may establish cross-connections after receiving Resv messages from adjacent downstream nodes. The node I may establish the cross-connection before sending the Resv message, or may establish the cross-connection after sending the Resv message.

(31) Because the edge network nodes J and L do not support the ASON protocol (in other words, cannot receive or send the path message), cross-connection configuration information of the nodes J and L may be carried in an ERO object of the ASON last node I. In other words, in addition to the cross-connection configuration information of the node I, the cross-connection configuration information of the node I may further include the cross-connection configuration information of the nodes J and L. For example, basic configuration information (for example, outbound interface information of the nodes J and L) of an edge network sub-path I-J-L is carried in the ERO object of the node I as sub-type-length-value (TLV) information. A specific extended TLV format is as follows:

(32) <ASON node E HOP> object;

(33) <ASON node F HOP> object;

(34) <ASON node I HOP> object;

(35) <Edge network node J HOP> object;

(36) <Edge network node L HOP> object.

(37) FIG. 6 is a schematic diagram of an extended packet format of a path message according to an embodiment of the present disclosure. A meaning of a specific field is shown in Table 1.

(38) TABLE-US-00001 TABLE 1 Field name Meaning Value Length A total object length in units of bytes A 16-byte value Class- Identify an object class, where each object An 8-byte value Num class has a name Type An object type, which is unique in Class- An 8-byte value Num, where an extended field value indicates an edge hop type RouterID Node ID address A 32-byte value LinkID Outbound link ID A 32-byte value InLabel An inbound label, indicating a channel/ A 16-byte value wavelength Reserved A reserved byte A 16-byte value OutLabel An outbound label, indicating a channel/ A 16-byte value wavelength Reserved A reserved byte A 16-byte value

(39) As shown in FIG. 6, in a packet format of the path message, an ERO object field of the node I may carry information such as an edge path length (Length), an edge HOP type (Type), an outbound link (LinkID), and an outbound label (OutLabel). The ERO object field of the node I may carry the cross-connection configuration information of the node I, and may further carry the cross-connection configuration information of the network nodes J and L. For example, the cross-connection configuration information of the node I may include outbound interface information, for example, an outbound link identifier and an outbound label (namely, a channel number). The cross-connection configuration information of the nodes J and L may include outbound interface information, such as a node ID, an outbound link, and an outbound label. The outbound link may indicate a subrack, a slot, and a port of an outbound interface, and the outbound label may indicate a channel (a timeslot or a wavelength). In the path message, inbound interface information (an inbound link and an inbound label) of the nodes I, J, and L is optional because the node I can determine the inbound interface information of the nodes I, J, and L based on outbound interface information of respective upstream nodes of the nodes I, J, and L.

(40) The sub-path I-J-L belongs to the edge network, and a service of the sub-path I-J-L is directly configured by the node I (the ECU) by using the edge control protocol. For example, the node I (the ECU) obtains the cross-connection configuration information of the edge network nodes J and L from the path message, and configures cross-connections for the nodes J and L station by station through the COAP. A cross-connection configuration message sent by the node I (the ECU) to the nodes J and L may include inbound interface information and outbound interface information. The inbound interface information and the outbound interface information of the nodes J and L are similar to the inbound interface information and the outbound interface information of the nodes A and B that are sent by the node D.

(41) Step 405: The node D receives a path establishment response message of the downstream node, where the path establishment response message indicates that cross-connection configuration for the ASON last node and the at least one edge network node is complete.

(42) After configuring the cross-connections for the edge network nodes J and L, the ASON last node I performs reverse cross-connection configuration on the ASON first node D hop by hop. For example, as shown in FIG. 5, the ASON last node I forwards a Resv message to the ASON first node D hop by hop. After receiving a Resv message of RSVP-TE signaling, the ASON first node D determines that service configuration for a sub-path D-E-F-I-J-L is complete. In addition, the node D (the ECU) also determines that service configuration for the sub-path A-B-D is complete. In this case, it may be determined that service configuration for the end-to-end service path A-B-D-E-F-I-J-L is complete. In an end-to-end service creation process, a service configuration sequence of the sub-path A-B-D and the sub-path D-E-F-I-J-L is controlled by the node D (the ECU), and the two service paths may be concurrently or successively established. A sequence of the two service paths is not limited.

(43) Step 406: The node D notifies the node A that the end-to-end service path is established.

(44) After receiving, from the node D, the message indicating that the service path is successfully established, the source node A of the service stores service path information and sends, to the network management system, a response message indicating that the service path is successfully established.

(45) In this embodiment of the present disclosure, the ASON node (the ECU) completes service configuration (cross-connection configuration) for the edge network through the extended RSVP-TE protocol and the edge control protocol, and can automatically configure the end-to-end service path across the edge network and the ASON, thereby improving service provisioning efficiency and accuracy.

(46) FIG. 7 is a diagram of a network architecture of an application scenario according to an embodiment of the present disclosure. As shown in FIG. 7, a network architecture 700 includes a metropolitan area/core network 701 and an edge network 702. The edge network on the left in FIG. 3 is absent in FIG. 7. The metropolitan area/core network 701 is similar to the metropolitan area/core network 302 in FIG. 3 and supports an ASON protocol. The metropolitan area/core network 701 includes ASON nodes D, E, F, G, H, and I. The edge network 702 is similar to the edge network 303 in FIG. 3, and does not support the ASON protocol. The edge network 702 includes edge network nodes J, K, and L. An ECU may be deployed for the ASON node, for example, the ECU is deployed for the ASON node I connected to the edge network. An ECA may be deployed for the edge network node, for example, the ECA is deployed for each of the edge network nodes J, K, and L. The edge network nodes J, K, and L are located within a control scope of the ASON node I. As a control node of the edge network nodes J, K, and L, the ASON node I can discover the edge network nodes J, K, and L according to an automatic route discovery mechanism. The ASON nodes D, E, F, G, H, and I can discover each other according to the automatic route discovery mechanism (an OSPF protocol). Optionally, the network architecture 700 may further include a PCE. Similar to FIG. 3, a service may be automatically configured through an extended RSVP-TE protocol. The following uses establishment of a service path D-E-F-I-J-L across the metropolitan area/core network 701 and the edge network 702 as an example for description. FIG. 8 is an example flowchart of a method for establishing a service path according to an embodiment of the present disclosure. The method includes the following steps.

(47) Step 801: A user requests a network management system to establish a service path from the ASON node D to the edge network node L.

(48) This step is different from step 401 in that a source node of the service path is the node D.

(49) Step 802: The network management system delivers service configuration information to the source node D of the service path to request to create the service path from D to L.

(50) This step is different from step 402 in that the node D usually has a path computation capability, and the node D may compute an end-to-end service path D-E-F-I-J-L from D to L or by using a PCE.

(51) Step 803: The node D obtains a path computation result, where the path includes an ASON last node and at least one edge network node.

(52) This step is different from step 403 in that the service path computation result is D-E-F-I-J-L. In this service path, the node D is a source node of a service, and the node L is a sink node of the service.

(53) Step 804: The node D sends a path establishment request message to a downstream node, where the path establishment request message carries at least cross-connection configuration information of the ASON last node and the at least one edge network node.

(54) This step is different from step 404 in that the node D does not need to configure a service for a sub-path A-B-D.

(55) Step 805: The node D receives a path establishment response message of the downstream node, where the path establishment response message indicates that cross-connection configuration for the ASON last node and the at least one edge network node is complete.

(56) This step is different from step 405 in that the node D does not need to confirm whether the service for the sub-path A-B-D is configured.

(57) Step 806: The node D directly stores service path information, and sends a service path success response message to the network management system.

(58) In this embodiment of the present disclosure, the ASON node (an ECU) completes service configuration (cross-connection configuration) for the edge network through an extended RSVP-TE protocol and an edge control protocol, and can automatically configure an end-to-end service path across an ASON and the edge network, thereby improving service provisioning efficiency and accuracy.

(59) FIG. 9 is a diagram of a network architecture of an application scenario according to an embodiment of the present disclosure. As shown in FIG. 9, a network architecture 900 includes an edge network 901 and a metropolitan area/core network 902. The edge network on the right in FIG. 3 is absent in FIG. 9. The edge network 901 is similar to the edge network 301 in FIG. 3, and does not support an ASON protocol. The edge network 901 includes edge network nodes A, B, and C. The metropolitan area/core network 902 is similar to the metropolitan area/core network 302 in FIG. 3, and supports the ASON protocol. The metropolitan area/core network 902 includes ASON nodes D, E, F, G, H, and I. An ECA may be deployed for the edge network node, for example, the ECA is deployed for each of the edge network nodes A, B, and C. An ECU may be deployed for the ASON node, for example, the ECU is deployed for the ASON node D connected to the edge network. The edge network nodes A, B, and C are located within a control scope of the ASON node D. As a control node of the edge network nodes A, B, and C, the ASON node D can discover the edge network nodes A, B, and C according to an automatic route discovery mechanism. The ASON nodes D, E, F, G, H, and I can discover each other according to the automatic route discovery mechanism (an OSPF protocol). Optionally, the network architecture 900 may further include a PCE. Similar to FIG. 3, a service may be automatically configured through an extended RSVP-TE protocol. The following uses establishment of a service path A-B-D-E-F-I across the edge network 901 and the metropolitan area/core network 902 as an example for description. FIG. 10 is an example flowchart of a method for establishing a service path according to an embodiment of the present disclosure. The method includes the following steps.

(60) Step 1001: A user requests a network management system to establish a service path from the edge network node A to the ASON node I.

(61) This step is different from step 401 in that a sink node of a service is the node I.

(62) Step 1002: The network management system delivers service configuration information to the source node A to request to establish the service path from A to I.

(63) This step is different from step 402 in that an end-to-end service path is A-B-D-E-F-I.

(64) Step 1003: The node D obtains a path computation result, where the path includes an ASON last node.

(65) This step is different from step 403 in that the service path computation result is A-B-D-E-F-I. In this service path, the node A is the source node of the service, and the node I is the sink node of the service.

(66) Step 1004: The node D sends a path establishment request message to a downstream node, where the path establishment request message carries at least cross-connection configuration information of the ASON last node.

(67) This step is different from step 404 in that the path establishment request message may not carry cross-connection configuration information of edge network nodes J and L, and the node I does not need to configure a cross-connection for the edge network nodes J and L either.

(68) Step 1005: The node D receives a path establishment response message of the downstream node, where the path establishment response message indicates that cross-connection configuration for the ASON last node is complete.

(69) This step is different from step 405 in that the node I determines that service configuration for a sub-path A-B-D and service configuration for a sub-path D-E-F-I are complete.

(70) Step 1006: The node D notifies the node A that the end-to-end service path is established.

(71) This step is different from step 406 in that an end-to-end service path stored by the node D is A-B-D-E-F-I.

(72) In this embodiment of the present disclosure, the ASON node (an ECU) completes service configuration (cross-connection configuration) for the edge network through an edge control protocol, and can automatically configure an end-to-end service path across an ASON and the edge network, thereby improving service provisioning efficiency and accuracy.

(73) FIG. 11 is a diagram of a network architecture of an application scenario according to an embodiment of the present disclosure. As shown in FIG. 11, a network architecture 1100 includes an edge network 1101, a metropolitan area/core network 1102, and an edge network 1103. The edge network 1101 and the edge network 1103 do not support an ASON protocol, the edge network 1101 includes edge network nodes A, B, and C, and the edge network 1103 includes edge network nodes J, K, and L. The metropolitan area/core network 1102 supports the ASON protocol, and the metropolitan area/core network 1102 includes ASON nodes D, E, F, G, H, I, M, and N. An ECA may be deployed for the edge network node, for example, the ECA is deployed for each of the edge network nodes A, B, C, J, K, and L. Compared with FIG. 3, FIG. 11 has secondary ECUs. A primary ECU is deployed for the ASON node M, and the secondary ECU is deployed for the ASON node D. The ECUs are a primary ECU and a secondary ECU of each other. The primary ECU is deployed for the ASON node N, and the secondary ECU is deployed for the ASON node I. The ECUs are a primary ECU and a secondary ECU of each other. Configuring the primary and secondary ECUs can increase reliability of the edge network. After the primary ECU fails, the secondary ECU can still control the edge network. Topology information and service information of the edge network are synchronized to primary and secondary ECU control nodes through an edge control protocol. However, service configuration may be uniformly controlled by the primary ECU, to prevent conflicts caused when a plurality of edge network services are simultaneously configured. The edge network nodes A, B, and C are located within a control scope of the ASON node M/D. As a control node of the edge network nodes A, B, and C, the ASON node M/D can discover the edge network nodes A, B, and C according to an automatic route discovery mechanism. The edge network nodes J, K, and L are located within a control scope of the ASON node N/I. As a control node of the edge network nodes J, K, and L, the ASON node N/I can discover the edge network nodes J, K, and L according to the automatic route discovery mechanism. The ASON nodes D, E, F, G, H, I, M, and N can discover each other according to the automatic route discovery mechanism (an OSPF protocol). In addition, a primary/secondary ECU relationship of M/D is configured for the edge network nodes A, B, and C, and a primary/secondary ECU relationship of N/I is configured for the edge network nodes J, K, and L. Optionally, the network architecture 1100 may further include a PCE. Similar to FIG. 3, a service may be automatically configured through an extended RSVP-TE protocol. The following uses establishment of a service path A-B-D-E-F-I-J-L across the edge network 1101, the metropolitan area/core network 1102, and the edge network 1103 as an example for description. FIG. 12 is an example flowchart of a method for establishing a service path according to an embodiment of the present disclosure. The method includes the following steps.

(74) Step 1201: A user requests a network management system to establish a service path from the edge network node A to the edge network node L.

(75) This step is the same as step 401.

(76) Step 1202: The network management system delivers service configuration information to the source node A to request to establish the service path from A to L.

(77) This step is different from step 402 in that the node A may request the node M (a primary ECU) to compute an end-to-end service path from A to L.

(78) Step 1203: The node M obtains a path computation result, where the path includes an ASON last node and at least one edge network node.

(79) This step is different from step 403 in that the node M (the primary ECU) may obtain a service path computation result A-B-D-E-F-I-J-L or by using a PCE.

(80) Step 1204: The node D sends a path establishment request message to a downstream node, where the path establishment request message carries at least cross-connection configuration information of the ASON last node and the at least one edge network node.

(81) This step is different from step 404 in that after obtaining the service path computation result, the node M (the primary ECU) allocates a session ID, and configures a cross-connection for the nodes A and B.

(82) For a sub-path D-E-F-I-J-L, the node M (the primary ECU) sends path configuration information of D-E-F-I-J-L (for example, carries at least cross-connection configuration information of an ASON last node I and the at least one edge network node) to the node D (a secondary ECU) through a proprietary protocol, and the node D configures a cross-connection for the nodes J and L through an extended RSVP-TE protocol. The node D sends a path message to the downstream node, and cross-connection configuration information of the nodes J and L (for example, an inbound port timeslot or a wavelength of the nodes J and L, or an outbound port timeslot or a wavelength of the nodes J and L) is carried in an ERO object of the node I as sub-TLV information. When receiving the path message, the node I (a secondary ECU) obtains the cross-connection configuration information of the nodes J and L, sends the information to the node N (a primary ECU) through the proprietary protocol, and the node N (the primary ECU) configures the cross-connection for the nodes J and L. After configuration is complete, the node N (the primary ECU) notifies the node I (the secondary ECU) that the configuration is complete. Optionally, the node D (the secondary ECU) may further configure a cross-connection for the nodes A and B, and the node I (the secondary ECU) may configure a cross-connection for the nodes J and L.

(83) Step 1205: The node D receives a path establishment response message of the downstream node, where the path establishment response message indicates that cross-connection configuration for the ASON last node and the at least one edge network node is complete.

(84) This step is different from step 405 in that after receiving a configuration completion notification of the node N (the primary ECU), the node I (the secondary ECU) performs forward cross-connection configuration to the ASON first node D hop by hop. After receiving a path establishment response message (a Resv message), the node D (the secondary ECU) notifies the node M (the primary ECU) that service configuration for the sub-path D-E-F-I-J-L is complete. In addition, the node M (the primary ECU) also determines that service configuration for a sub-path A-B-D is complete. In this case, it may be determined that service configuration for the end-to-end service path A-B-D-E-F-I-J-L is complete.

(85) Step 1206: The node M notifies the node A that the end-to-end service path is established.

(86) This step is different from step 406 in that the node M (the primary ECU) sends a message indicating that the service path is successfully established to the source node A of the service.

(87) In this embodiment of the present disclosure, in a normal network environment, a primary ECU control node configures a service for the edge network. When the primary ECU control node is faulty, a secondary ECU control node configures the service for the edge network, thereby improving network reliability. Service configuration (cross-connection configuration) for the edge network node is completed through the extended RSVP-TE protocol and the edge control protocol, and an end-to-end service path across the edge network and an ASON can be automatically configured, thereby improving service provisioning efficiency and accuracy.

(88) FIG. 13 is a diagram of a network architecture of an application scenario according to an embodiment of the present disclosure. Based on the established service path A-B-D-E-F-I-J-L in FIG. 3, FIG. 13 shows how to perform rerouting when the service path is faulty. FIG. 14 is an example flowchart of a rerouting method according to an embodiment of the present disclosure. The method includes the following steps.

(89) Step 1401: A node D detects that a service path is faulty, and obtains a computation result of a recovery path, where the recovery path includes an ASON last node and at least one edge network node.

(90) The node D (an ECU) may detect a service path fault, or may detect a service path fault through a fault notification of another node. For example, as shown in FIG. 13, a fiber cut occurs on a link (for example, B-D) in an edge network 1301. After detecting that a port with the fiber cut is faulty, the node B finds an affected service path (for example, A-B-D-E-F-I-J-L) based on an association relationship between the port and a service path. The node B reports information about the faulty port and information about the service path affected by the fault to the control node D of the node B through an edge control protocol (for example, COAP), and requests to recover the service path (in other words, perform rerouting). The node D may compute or request the PCE to compute the recovery path, for example, the recovery path is A-C-D-E-F-I-J-L. In the recovery path, A-B-D and I-J-L are sub-paths in an edge network, and D-E-F-I is a sub-path in a metropolitan area/core network.

(91) If a link (such as E-F) in an ASON 1302 is faulty, the node E reports a fault alarm to the node D through RSVP-TE signaling. If a link (such as J-L) in an edge network 1303 is faulty, the node J notifies the node i (an ECU) of a fault alarm through an edge control protocol, and then the node I reports the fault alarm to the node D through the RSVP-TE signaling.

(92) Step 1402: The node D establishes the recovery path based on the computation result of the recovery path.

(93) When a link B-D in the edge network 1301 is faulty, compared with an original service path A-B-D-E-F-I-J-L, an edge network sub-path A-B-D in the recovery path A-C-D-E-F-I-J-L is changed to A-C-D. Therefore, the node D may reconfigure A-B-D as A-C-D. As described in step 404, a cross-connection for the sub-path A-C-D may be configured through the edge control protocol (for example, COAP). Alternatively, the entire service path A-C-D-E-F-I-J-L may be reconfigured in a same manner in which a new service path is established. For a specific implementation, refer to steps 404 and 405. Details are not described herein.

(94) If a link in the ASON 1302 is faulty, a sub-path D-E-F-I of the ASON may be reconfigured through RSVP-TE signaling in the current technology or extended RSVP-TE signaling in this embodiment of the present disclosure.

(95) If a path in the edge network 1303 is faulty, a sub-path I-J-L in the edge network 1303 may be reconfigured through the extended RSVP-TE signaling in this embodiment of the present disclosure.

(96) Step 1403: The node D notifies the node A that an end-to-end recovery path is established.

(97) In this embodiment of the present disclosure, the ASON node (an ECU) completes service recovery (rerouting) for the edge network through the edge control protocol, and can automatically recover an end-to-end service path across the ASON and the edge network, thereby improving service recovery efficiency and accuracy.

(98) FIG. 15 is a schematic diagram of a logical structure of a network device according to an embodiment of the present disclosure. As shown in FIG. 15, a network device 1500 may be an ASON device, such as a switch or a router. The network device 1500 may include a signaling module 1501, a routing module 1502, a cross-connection management module 1503, and a link management module 1504. These modules may be implemented through software, or may be implemented through a combination of software and hardware. The network device 1500 may further include an inbound interface and an outbound interface. The inbound interface and the outbound interface may be physical, or may be logical. The inbound interface and the outbound interface are relative to a service transmission direction. If a service direction on the network device 1500 is bidirectional, the inbound interface may also be an outbound interface, and the outbound interface may also be an inbound interface.

(99) The signaling module 1501 is configured to complete the following functions through an RSVP-TE protocol: establishing or dismantling a service path based on a service path establishment or dismantling request submitted by a user, and providing a service synchronization and recovery function based on a change in a service status. The signaling module 1501 may be connected to a network management system to receive a service establishment command from the network management system.

(100) The routing module 1502 is configured to: collect and flood traffic engineering (TE) link information through an OSPF-TE protocol, collect and flood control link information of a control plane, and compute a service route based on TE link information of an entire network by using a CSPF protocol.

(101) The cross-connection management module 1503 is configured to: establish a cross-connection and delete the cross-connection, and report information such as a link status and an alarm.

(102) The link management module 1504 is configured to create and maintain a control channel and check a TE link through a link management protocol (LMP).

(103) In this embodiment of the present disclosure, the routing module 1502 obtains a service path computation result, the signaling module 1501 sends a path establishment request message and receives a path establishment response message, the path establishment request message and the path establishment response message are transmitted through a control channel established by the link management module 1504, and the cross-connection management module 1503 configures a cross-connection.

(104) All or some of the foregoing embodiments may be implemented through software, hardware, firmware, or any combination thereof. When software is used to implement the embodiments, the embodiments may be implemented completely or partially in a form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or some of the procedures or functions according to the embodiments of the present disclosure are generated. The computer may be a general-purpose computer, a dedicated computer, a computer network, or another programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or may be transmitted from a computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center in a wired (for example, a coaxial cable, an optical fiber, or a digital subscriber line (DSL)) or wireless (for example, infrared, radio, or microwave) manner. The computer-readable storage medium may be any usable medium accessible by a computer, or a data storage device, such as a server or a data center, integrating one or more usable media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, a DVD), a semiconductor medium (for example, a solid-state drive (SSD)), or the like.

(105) The foregoing descriptions are merely specific implementations of the present disclosure, but are not intended to limit the protection scope of the present disclosure. Any variation or replacement readily figured out by a person skilled in the art within the technical scope disclosed in the present disclosure shall fall within the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.