WO2017066923A1

WO2017066923A1 - Method, network controller, and system for establishing service path

Info

Publication number: WO2017066923A1
Application number: PCT/CN2015/092319
Authority: WO
Inventors: 张弦; 林毅
Original assignee: 华为技术有限公司
Priority date: 2015-10-20
Filing date: 2015-10-20
Publication date: 2017-04-27

Abstract

An embodiment of the present invention discloses a method for establishing a service path, comprising: a network controller computes a service path comprising multiple nodes; the network controller sends to each of the multiple nodes a cross-connection establishment command instructing said node to establish a cross-connection; and the network controller receives from each of the multiple nodes a message of successful cross-connection establishment, and then establishes connections of the service path via respective established cross-connections of the multiple nodes. By employing the above technical solution, the present invention establishes, via a network controller, an end-to-end service path, thus improving the efficiency of establishing a service path.

Description

Method, network controller and system for establishing business path

Technical field

The present invention relates to the field of communications, and in particular, to a method, a network controller, and a system for establishing a service path.

Background technique

A conventional optical transport network includes a management plane and a transport plane. The traditional optical transport network architecture is shown in Figure 1a. The transport plane is used to transmit service data, complete multiplexing/demultiplexing, transmission and exchange of optical signals, and implement protection switching of service data. The management plane is used to manage and control the transport plane. In the international communication standard defined by the ITU-T (International Telecommunication Union-Telecommunication Sector), the concept of a control plane is introduced in a conventional optical transport network. As shown in FIG. 1b, the optical transmission network including the control plane is an ASON (Automatically Switched Optical Network). The primary function of the control plane is to support the ability to establish, tear down, and maintain end-to-end connections through signaling, and to determine the most appropriate path through routing. The Internet Engineering Task Force (IETF) defines the GMPLS (Generalized Multi-Protocol Label Switching) protocol family to support the implementation of control plane functions in the ASON architecture. The GMPLS protocol suite includes distributed control protocols, such as routing protocols and signaling protocols, to support distributed path computation and path establishment. A routing protocol such as OSPF-TE (Open Shortest Path First Traffic Engineering) is an open shortest path first protocol that supports traffic engineering. Signaling protocols such as RSVP-TE (Resource Reservation Protocol-Traffic) Engineering, a resource reservation protocol that supports traffic engineering).

In order to achieve efficient path calculation, the IETF has introduced a new functional entity PCE (Path Computation Element). The PCE can be deployed in a network controller, which is a functional unit in the control plane. The PCE needs to operate under distributed control protocols (such as OSPF-TE, RSVP-TE) in the GMPLS protocol suite. However, many operators do not support the GMPLS protocol or the PCE in the optical network. The end-to-end path is established for the optical network through the management plane. There are also heterogeneous networks, that is, multiple domains in the network, including network domains supporting the GMPLS protocol, such as the core network, and network domains that do not support the GMPLS protocol, such as optical access networks. In a heterogeneous network, a control plane and a management plane are required to implement end-to-end path establishment. Since the end-to-end path is established through the management plane, manual configuration is required, resulting in low efficiency, poor real-time performance, and error proneness. Therefore, in the prior art, in a network that does not support the GMPLS protocol, or in a heterogeneous network in which a part of the network domain does not support the GMPLS protocol, the service path establishment efficiency is low.

Summary of the invention

In view of this, the embodiments of the present invention provide a method, a network controller, and a system for establishing a service path, which can be solved in a network that does not support the GMPLS protocol, or in a heterogeneous network that does not support the GMPLS protocol in a part of the network domain. The problem of low path establishment efficiency.

In a first aspect, an embodiment of the present invention provides a method for establishing a service path, including: a network controller calculating a service path, where the service path includes multiple nodes; and the network controller is to each of the multiple nodes Each of the nodes sends a cross-connection establishment command, the cross-connection establishment command instructing each of the plurality of nodes to establish a cross-connection; The network controller receives a message that the cross-connection establishment success is successful from each of the plurality of nodes, and establishes a connection of the service path through a cross-connection established by each of the plurality of nodes.

With reference to the implementation of the first aspect, in a first possible implementation manner of the first aspect, after the network controller calculates the service path, the method further includes: the network controller determining each of the multiple nodes Neither general-purpose multi-protocol label switching GMPLS protocol is supported.

With reference to the first aspect, or the first possible implementation manner of the first aspect, in the second possible implementation manner of the first aspect, the service path further includes multiple nodes supporting the GMPLS protocol, and the multiple supports GMPLS. The node of the protocol constitutes a sub-service path, the method further includes: the network controller sending a sub-service path establishment command to the source node of the sub-service path, where the sub-service path establishment command instructs the source node to establish Determining a sub-service path; the network controller receives a message that the sub-service path from the source node is successfully established, and establishes a connection of the service path by using a sub-service path established by the source node.

With reference to the first aspect, or any one of the first to the second possible implementations of the first aspect, in the third possible implementation manner of the first aspect, after the service path is successfully established, the method further includes: when When the service path fails, the network controller performs re-routing calculation on the service path, the service path after the re-routing passes through the first node, and the first node needs to modify the cross-connection; the network controller sends Transmitting, by the first node, a cross-connection modification command, where the cross-connection modification command instructs the first node to modify the cross-connection; and the network controller receives a message that the cross-connection modification succeeds from the first node, After the modified cross-connection of the first node is established, the re-routing is established. The connection to the business path.

With reference to the first aspect, or any one of the first to third possible implementations of the first aspect, in the fourth possible implementation manner of the first aspect, after the service path is successfully established, the method further includes: when When the service path fails, the network controller performs re-routing calculation on the service path, the service path after the re-routing passes through the second node, and the second node needs to establish a cross-connection; the network controller sends The second node sends a second cross-connection establishment command, the second cross-connection establishment command instructs the second node to establish a second cross-connection; the network controller receives a second cross-connection establishment from the second node A successful message is that the connection of the service path after the rerouting is established by the second cross connection established by the second node.

With reference to the first aspect, or any one of the first to fourth aspects of the first aspect, in the fifth possible implementation manner of the first aspect, after the service path is successfully established, the method further includes: when When the service path fails, the network controller performs re-routing calculation on the service path, the service path before the re-routing passes through the third node, and the third node needs to delete the cross-connection; the network controller sends The third node sends a cross-connection deletion command, the third cross-connection deletion command instructs the third node to delete the cross-connection; and the network controller receives a message that the cross-connection deletion is successful from the third node.

With reference to the first aspect, or any one of the first to fifth possible implementation manners of the first aspect, in the sixth possible implementation manner of the first aspect, the cross connection establishment command is implemented by the path calculation unit protocol PCEP.

In combination with the first aspect, or any of the first to sixth possible implementations of the first aspect, In a seventh possible implementation manner of the first aspect, the network controller determines that each of the multiple nodes does not support the general GMPLS protocol, and reports whether the node supports the network controller by using the node. The GMPLS protocol is implemented, or is implemented by whether the each node pre-configured in the network controller supports information of the GMPLS protocol.

In a second aspect, an embodiment of the present invention provides a network controller, including: a calculating unit, configured to calculate a service path, where the service path includes multiple nodes, and a sending unit, configured to each of the multiple nodes Each of the nodes sends a cross-connection establishment command, the cross-connection establishment command instructing each of the plurality of nodes to establish a cross-connection; and a receiving unit, configured to receive a cross-connection establishment from each of the plurality of nodes A successful message establishes a connection of the service path through a cross-connection established by each of the plurality of nodes.

With reference to the implementation of the second aspect, in a first possible implementation manner of the second aspect, the network controller further includes: a determining unit, configured to determine that each of the multiple nodes does not support universal Protocol label switching GMPLS protocol.

With reference to the second aspect, or the first possible implementation manner of the second aspect, in the second possible implementation manner of the second aspect, the service path further includes multiple nodes supporting the GMPLS protocol, and the multiple supports GMPLS. The node of the protocol constitutes a sub-service path, and the sending unit is further configured to send a sub-service path establishment command to the source node of the sub-service path, where the sub-service path establishment command instructs the source node to establish the sub-service a receiving unit, configured to receive a message that the sub-service path from the source node is successfully established, and establish a connection of the service path by using a sub-service path established by the source node. Pick up.

With reference to the second aspect, or any one of the first to the second possible implementation manners of the second aspect, in the third possible implementation manner of the second aspect, the calculating unit is further configured to: when the service path When a fault occurs, the network controller performs re-routing calculation on the service path, the service path after the re-routing passes through the first node, and the first node needs to modify the cross-connection; the sending unit is further used to Sending a cross-connection modification command to the first node, the cross-connection modification command instructing the first node to modify the cross-connection; the receiving unit is further configured to receive a cross-connection modification success from the first node The message establishes a connection of the service path after the rerouting by the modified cross connection of the first node.

With reference to the second aspect, or any one of the first to third possible implementation manners of the second aspect, in the fourth possible implementation manner of the second aspect, the calculating unit is further configured to: when the service path When a fault occurs, the network controller performs re-routing calculation on the service path, the service path after the re-routing passes through the second node, and the second node needs to establish a cross-connection; the sending unit is further used to Sending a second cross-connection establishment command to the second node, where the second cross-connection establishment command instructs the second node to establish a second cross-connection; the receiving unit is further configured to receive the second node from the second node The second cross-connection establishes a successful message, and establishes a connection of the service path after the re-routing through the second cross-connection established by the second node.

With reference to the second aspect, or any one of the first to fourth possible implementation manners of the second aspect, in the fifth possible implementation manner of the second aspect, the calculating unit is further configured to: when the service path The network controller reroutes the service path when a failure occurs Calculating that the service path before the rerouting passes through the third node, and the third node needs to delete the cross connection; the sending unit is further configured to send a cross connection delete command to the third node, where the third cross The connection deletion command instructs the third node to delete the cross-connection; the receiving unit is further configured to receive a message that the cross-connection deletion is successful from the third node.

With reference to the second aspect, or any one of the first to fifth possible implementation manners of the second aspect, in the sixth possible implementation manner of the second aspect, the sending unit is used to implement the path calculation unit protocol PCEP The cross connect setup command.

With reference to the second aspect, or any one of the first to fifth possible implementation manners of the second aspect, in the sixth possible implementation manner of the second aspect, the determining unit, by using each of the nodes, to the network The controller reports whether the GMPLS protocol implementation is supported, or is implemented by whether the pre-configured node in the network controller supports the information of the GMPLS protocol.

In a third aspect, an embodiment of the present invention provides a network system, including at least: a network controller and a plurality of nodes, where the network controller is configured to calculate a service path, where the service path includes the multiple nodes; The network controller is further configured to separately send a cross-connection establishment command to each of the plurality of nodes, the cross-connection establishment command instructing each of the plurality of nodes to establish a cross-connection; the network The controller is further configured to receive a message that the cross-connection establishment success is successful from each of the plurality of nodes, and establish a connection of the service path by a cross-connection established by each of the plurality of nodes.

In conjunction with the implementation of the third aspect, in a first possible implementation manner of the third aspect, The network controller is further configured to determine that each of the multiple nodes does not support the universal multi-protocol label switching GMPLS protocol.

With reference to the third aspect, or the first possible implementation manner of the third aspect, in the second possible implementation manner of the third aspect, the service path further includes multiple nodes supporting the GMPLS protocol, and the multiple supports GMPLS. The node of the protocol constitutes a sub-service path, and the network controller is configured to send a sub-service path establishment command to the source node of the sub-service path, where the sub-service path establishment command instructs the source node to establish the sub-service The network controller is further configured to receive a message that the sub-service path from the source node is successfully established, and establish a connection of the service path by using a sub-service path established by the source node.

In a fourth aspect, an embodiment of the present invention provides a network controller, including: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer execution instruction, and the processor and the memory are connected through a bus, and when the computer is running, processing The computer executes the memory-stored computer-executable instructions to cause the computer to perform the method as described in the first aspect and any one of the possible implementations of the first aspect.

According to the technical solution provided by the embodiment of the present invention, the network controller calculates a service path, where the service path includes multiple nodes, and the network controller separately sends a cross-connection establishment command to each of the multiple nodes. The cross-connection establishment command instructs each of the plurality of nodes to establish a cross-connection; the network controller receives a message from each of the plurality of nodes that the cross-connection is successfully established, through the plurality of nodes A cross-connection established by each of the nodes establishes a connection of the service path. When each node that the service path passes does not support the GMPLS protocol, the network controller is used to provide services. Each node on the path sends a cross-connection establishment command, which can implement end-to-end service path establishment and improve the efficiency of service path establishment. When the service path passes through a node that does not support the GMPLS protocol and also passes through a node that supports the GMPLS protocol, the network controller sends a cross-connection establishment command to each node that does not support the GMPLS protocol, and forms a sub-service path to the node supporting the GMPLS protocol. The source node sends a sub-service path establishment command, which can implement end-to-end service path establishment and improve the efficiency of service path establishment. The technical solution provided by the present invention can support multiple network architectures, including a network architecture that does not support the GMPLS protocol, a network structure that supports the GMPLS protocol, and a heterogeneous network that does not support the GMPLS protocol in some network domains, which can improve the efficiency of the service path establishment. .

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the prior art, the drawings used in the description of the background and the embodiments will be briefly described below. Obviously, only a part of the embodiments of the present invention are described in the following drawings, and other drawings or drawings may be obtained according to the drawings and descriptions without any creative work by those skilled in the art. The embodiments are intended to cover all such derived figures or embodiments.

1a is a schematic diagram of a conventional optical transport network architecture of the prior art;

1b is a schematic diagram of a prior art ASON network architecture;

2 is a schematic diagram of a network architecture according to an embodiment of the present invention;

FIG. 3 is an exemplary signaling diagram of a method for establishing a service path according to an embodiment of the present invention; FIG.

4 is a schematic structural diagram of a node according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a network architecture according to an embodiment of the present invention;

FIG. 6 is a schematic diagram of a network architecture according to an embodiment of the present invention;

FIG. 7 is an exemplary signaling diagram of a method for establishing a service path according to an embodiment of the present invention;

FIG. 8 is an exemplary flowchart of a method for establishing a service path according to an embodiment of the present invention;

9 is a schematic diagram of a logical structure of a network controller according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a computer device according to an embodiment of the present invention.

detailed description

The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. It is apparent that the described embodiments are only a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The embodiments of the present invention can be applied to a network that does not support GMPLS, and can also be applied to a heterogeneous network in which a part of the network domain does not support the GMPLS protocol, and can also be applied to a network that supports the GMPLS, which is not limited by the present invention. For example, the embodiment of the present invention can be applied to the traditional optical transport network shown in FIG. 1a, and can also be applied to the ASON network architecture shown in FIG. 1b, and can also be applied to a heterogeneous network in which two network architectures are mixed.

The network structure shown in Figure 1a includes a transport plane and a management plane. In the network architecture shown in Figure 1b, a control plane is added to the network architecture of Figure 1a. Take Figure 1b as an example The architecture is described in detail. The transport plane and management plane in the network architecture of Figure 1a are similar to those in Figure 1b. The transport plane consists of a series of transport entities, such as physical links between individual nodes and nodes. The transport plane is the channel through which traffic is transmitted, providing end-to-end one-way or two-way data transmission to client devices. The client device accesses a certain node (for example, node 2) of the transport plane through the UNI (User Network Interface). The client device dynamically requests to acquire, revoke, and modify the optical bandwidth connection resources with certain characteristics through the UNI. The management plane, that is, the platform used by the network management personnel to manage the network, can be connected to the control plane and the transport plane through the NMI (Network Management Interface) to implement management of the control plane and the transport plane. The control plane can be composed of a separate network controller, can also be composed of multiple control plane components, and can also be composed of a separate network controller and multiple control plane components. The network controller and control plane components, or different control plane components, are connected by signaling channels. The control plane and the transfer plane are connected by CCI (Connection Control Interface). The control plane sends an exchange control command to the transmission plane through the CCI, or the transmission plane sends resource status information to the control plane through the CCI.

When the embodiment of the present invention is applied to the network architecture shown in FIG. 1a, a network controller may be added to the network architecture. When the embodiment of the present invention is applied to the network architecture shown in FIG. 1b, it can be implemented by using a network controller in the control plane.

A PCE is integrated into the network controller in the control plane to efficiently solve complex path computation problems. The PCE stores resource information of the network, such as network topology information and resource usage of the network. The PCE can receive a path calculation request from the PCC (Path Computation Client) and calculate a request based on the available resources of the current network. One or more available paths and return the calculated available path to the PCC. The PCC may be located in each node of the transport plane or as a separate functional unit for initiating path computation requests. The IETF standard organization has extended the functions of the PCE to enable the PCE to have the following functions: 1. The PCE can obtain the information of the LSP (Label Switched Path), such as the link through which the LSP passes, the node information, and the bandwidth information. This type of PCE is called passive stateful PCE (Passive Stateful PCE). 2. LSP Delegation (authorization) function, that is, after the PCC grants the modification right of an LSP to the PCE, the PCE can modify the LSP, such as the node sequence and path through which the LSP passes. Moreover, the PCE notifies the LSP corresponding to the PCC that the LSP has been updated. This type of PCE is called active stateful PCE (active stateful PCE). 3. PCE initiation capability, that is, the ability of the PCE to trigger the first node to establish an LSP. For this type of PCE, the path computation request is not obtained by the node in the network but by the PCE through the proxy device of the client device.

In the embodiment of the present invention, a cross-connection establishment command is sent to each node on the service path by the network controller/PCE, and a cross-connection is established on each node, and the cross-connections of the nodes form a complete LSP that satisfies the customer's requirements. The network controller/PCE is directly established to establish an end-to-end service path.

FIG. 2 is a schematic diagram of a network architecture according to an embodiment of the present invention. as shown in picture 2. The network controller can be deployed anywhere in the network. The PCE can be integrated into the network controller, and the PCE can also be a separate physical device. The network controller can be a standalone device, specifically a server or a computer. The PCE can be an application software, or a hardware component, or a combination of software and hardware. In the embodiment of the present invention, each in the network Nodes, such as nodes A, B, C, D, E, and F, do not support the GMPLS protocol, but support the PCE protocol, PCEP (PCE Protocol). The network controller/PCE performs end-to-end service path calculation and establishment in a network that does not support the GMPLS protocol. The specific signaling interaction process is shown in Figure 3. The specific process is as follows:

S301: The client device requests the network controller to establish a service path.

In a specific implementation process, the client device may be connected to the network controller to send a service path establishment request message to the PCE in the network controller. The service path setup request message may carry a source and a sink node, and may also carry bandwidth information, cost information, and the like. In this embodiment, the service path establishment request message carries the source and sink node information, for example, the source node is A, and the sink node is D, that is, the service path between A and D is established.

S302: The node reports to the network controller whether the GMPLS protocol is supported.

In the specific implementation process, S302 is an optional step, and the network controller does not need to know whether the node supports the GMPLS protocol, and directly adopts the method of S303 to S307 to establish a service path.

Specifically, each node in the network can report whether the GMPLS protocol is supported by the network controller through the extended PCEP. Each node in the network can deploy a PCC, which can be an application software, or a hardware component, or a combination of software and hardware. Specifically, when the PCE and the PCC establish a session, a bit is added to the open object defined by the PCEP, for example, the bit is G. The PCC uses the value of the bit G to indicate whether the node where the PCC is located supports the GMPLS protocol. For example, when G=0, it indicates that the node corresponding to the PCC does not support the GMPLS protocol, and when G=1 or G is empty, it indicates that the node corresponding to the PCC supports the GMPLS protocol. Optionally, the nodes in the network can also be pre-configured on the network controller. Whether the information of the GMPLS protocol is supported does not need to report to the network controller whether the GMPLS protocol is supported.

In this embodiment, all the nodes in the network do not support the GMPLS protocol, and each node reports to the network controller that the GMPLS protocol is not supported. Alternatively, the network controller is pre-configured with information that all nodes in the network do not support the GMPLS protocol.

S303: The network controller calculates a service path.

The network controller calculates that the service path between A-Ds is A-B-C-D and identifies it as LSP1. LSP1 includes four cross-connections, which are LSP1-Cross Connecttion 1 corresponding to node A, which can be abbreviated as LSP1-1; LSP1-Cross Connecttion 2 corresponding to node B, which can be abbreviated as LSP1-2; LSP1 corresponding to node C. -Cross Connecttion 3, which can be abbreviated as LSP1-3; LSP1-Cross Connecttion 4 corresponding to node D, which can be abbreviated as LSP1-4. LSP1 can be composed of LSP1-1, LSP1-2, LSP1-3, and LSP1-4.

S304: The network controller sends a cross-connection establishment command to the node.

Specifically, the network controller sends a cross-connection establishment command to the nodes A, B, C, and D, respectively, and the cross-connection establishment command may respectively carry the cross-connection identifier and the cross-connection information corresponding to each node, and may further include an LSP identifier. In a specific implementation process, the cross-connection establishment command may be a PCInitiate/PCInit (Path Computation Initiate) message. The cross-connection establishment command is used to instruct nodes A, B, C, and D to establish corresponding cross-connections.

Specifically, the node B is taken as an example for description. 4 is a schematic structural diagram of a node B. As shown in Figure 4, Node B contains three ports, namely Port 1, Port 2, and Port 3. The internet The cross-connection identifier LSP1-2 corresponding to the node B carried in the cross-connection establishment command sent by the controller to the node B indicates that the cross-connection of the LSP1 on the node B is the second cross-connection of the LSP1. The cross-connection information may include a node identifier, an ingress port identifier, and an egress port identifier. The node identifier and the inbound label information, the outbound label information, or the node identifier, the inbound port identifier, the inbound label information, the outbound port identifier, and the outbound label information. For example, the cross-connection information on Node B may be: Node B+Port 1, Node B+Port 3; or Node B+Ingress Label 201, Node B+Out Label 203; or Node B+Port 1+Inbound Label 201, Node B+Port 3+ Out Label 203. The LSP identifier carried in the cross-connection establishment command sent by the network controller to the Node B is LSP1.

Specifically, the cross-connection establishment command may send a PCInitiate message to the Node B through the PCE on the network controller, instructing the Node B to establish a cross-connection between the port 1 and the port 3. Specifically, the LSP identifier and the cross-connection identifier carried in the PCInitiate message can be carried by the LSP object defined by the PCEP. The cross-connection information established by the Node B carried in the PCInitiate message can be carried by an ERP (Explicit Route Object) defined by the PCEP. Specifically, the node identifier, the ingress port identifier, and the egress port identifier may be represented by an IPv4 or IPv6 address. The indication of the inbound label information and the outbound label information depends on the corresponding network type, such as the label format in the Optical Transport Network (OTN) or the WSON (Wavelength-Switched Optical Network). Label format.

S305: The node returns a cross-connection establishment result to the network controller.

Specifically, after receiving the cross-connection establishment command of the network controller, the node establishes a cross-connection according to the cross-connection information carried in the cross-connection establishment command, and controls the network Returns the result of the cross-connection establishment. Specifically, the cross-connection establishment result may be success or failure. Optionally, if the node establishes a cross-connection success, the successful establishment result may not be returned to the network controller. If the node fails to establish a cross-connection, the result of the establishment failure may be returned to the network controller. The network controller sets a timer. If the message that the cross-connection establishment failure sent by the node fails to be received within a certain period of time, it can be determined that the node successfully establishes a cross-connection.

S306: The network controller updates the network resource information.

After receiving the cross-connection establishment success message fed back by each node, the network controller updates the network resource information in the TED (Traffic Engineering Database) and the LSPDB (LSP Database) on the network controller. When the network controller calculates the service path, each node is configured with network resources that need to be occupied, and each node establishes a cross-connection according to the network resources configured by the network controller. Therefore, after receiving the message that the cross-connection establishment successfully fed back by each node is successful, the network controller can determine that each node occupies the configured network resource.

Specifically, the used network resource is identified as occupied in the TED, or the used network resource is deleted from the available network resource list in the TED. For example, after the cross-connection established by the node B is successfully established, the port 1 and the port 3 on the node B are the used network resources, and need to be identified as occupied or deleted from the list of available network resources.

In the LSPDB, the established LSP information is recorded separately. The LSP information may include service path information and cross-connection information. For example, in this embodiment, the service path information includes the node and the link resource occupied by the LSP1, and the cross-connection information includes the node and link resources occupied by LSP1-1, LSP1-2, LSP1-3, and LSP1-4. And, LSP1 It is composed of LSP1-1, LSP1-2, LSP1-3, and LSP1-4 in order.

S307: The network controller returns a service path establishment result to the client device.

After the network controller receives the successful result of the cross-connection establishment returned by each node, the service path that the client device requests to establish is successfully established. The network controller returns a message that the service path establishment is successful to the client device.

In the embodiment of the present invention, the network controller calculates a service path that satisfies the customer's requirement, and each node in the service path corresponds to a cross-connection, and the network controller sends a cross-connection establishment command to each node through which the service path passes, so that each node A corresponding cross-connection is established to establish a service path. In a network that does not support the GMPLS protocol, an end-to-end service path is established through the network controller, which improves the efficiency of establishing a service path.

It should be noted that the embodiment of the present invention may also be implemented in a network supporting GMPLS. In a network that supports GMPLS, nodes A, B, C, D, E, and F support the GMPLS protocol. The specific implementation process is similar to the above.

FIG. 5 is a schematic diagram of a network architecture according to an embodiment of the present invention. The network architecture shown in Figure 5 is a heterogeneous network, that is, some nodes support the GMPLS protocol, and some nodes do not support the GMPLS protocol. The network architecture shown in FIG. 5 differs from the network architecture shown in FIG. 2 in that nodes A, B, and E do not support the GMPLS protocol, and nodes C, D, and F support the GMPLS protocol. In this embodiment, the steps that are different from the signaling interaction process shown in FIG. 3 are mainly described, and the same or similar steps are not described again.

S501 is similar to S301 and will not be described again.

In S502, the node reports to the network controller whether the GMPLS protocol is supported. Specific The GMPLS protocol is not supported by the nodes A, B, and E, and the GMPLS protocol is supported by the nodes C, D, and F. The network controller can be managed in units of network domains. For example, nodes A, B, and E form a network domain that does not support the GMPLS protocol, and nodes C, D, and F form a network domain that supports the GMPLS protocol. Alternatively, the network controller may also be managed in units of nodes. For example, nodes A, B, and E do not support the GMPLS protocol, and nodes C, D, and F support the GMPLS protocol. Optionally, the network controller may also pre-configure that the nodes A, B, and E do not support the GMPLS protocol, and the nodes C, D, and F support the information of the GMPLS protocol.

In S503, the network controller calculates that the service path between A-Ds is A-B-C-D, and includes two cross-connections: LSP1-1 corresponding to node A and LSP1-2 corresponding to node B. The service path between A-Ds also includes sub-service paths: node C and LSP1-3 corresponding to node D. LSP1-1 and LSP1-2 are similar to LSP1-1, LSP1-2, LSP1-3, and LSP1-4 in S303, and are cross-connected. LSP1-3 is a sub-service path (e.g., a sub-LSP) from node C to node D. That is, LSP1 is composed of the cross-connection LSP1-1, LSP1-2, and the sub-service path LSP1-3.

In S504, for the nodes A, B, the cross-connection establishment command sent by the network controller to the node is similar to that of S303, and a cross-connection is established on the nodes A, B. Node C and LSP 1-3 corresponding to node D establish a sub-service path between node C and node D. For LSP1-3, node C can be regarded as a source node of the service path, and node D can be regarded as a sink node of the sub-service path.

The sub-service path setup command sent by the network controller to the node C may carry the LSP identifier, the source node information, and the sink node information. For example, the LSP identifier is LSP1-3, the source node is C, and the sink node is D. The sub-service path establishment command sent to the node C may also carry the node C, The inbound port ID and the outbound port ID of the D; or the inbound label information and the outbound label information of the nodes C and D; or the inbound port identifier, the inbound label information, the outbound port identifier, and the outbound label information of the nodes C and D.

In S505, the cross-connection establishment result returned by the nodes A, B to the network controller is similar to that of S305. Node B returns the sub-service path establishment result to the network controller.

In S506, the network resource information update of nodes A and B is similar to S306. Since the network controller may only configure the sub-service path connection relationship from the node C to the node D, and the actual occupied network resources are not configured, the network resource information update of the node C is implemented by the GMPLS protocol. For example, for resource updates of TED, the network controller is obtained from node C through the OSPF protocol. For the LSPDB resource update, the node C reports to the network controller through a PCR pt (Path Computation Report) message.

S507 is similar to S307.

In the embodiment of the present invention, the service path that meets the customer's requirement is calculated by the network controller, and the service path includes a cross-connection corresponding to each node that does not support the GMPLS protocol, and a sub-service path corresponding to the node that supports the GMPLS protocol. The network controller sends a cross-connection establishment command to each node of the service path that does not support the GMPLS protocol, so that each node establishes a corresponding cross-connection, and the sub-service path establishment command is sent to the node that supports the GMPLS protocol. Thereby establishing a business path. In a heterogeneous network in which some network domains do not support GMPLS, an end-to-end service path is established through the network controller, which improves the efficiency of establishing a service path.

FIG. 6 is a schematic diagram of a network architecture according to an embodiment of the present invention. In this embodiment, Assume that link B-C on LSP1 is faulty and LSP1 is affected by the fault. The network controller/PCE needs to perform re-route calculation on LSP1. The specific signaling interaction process is shown in Figure 7. The specific process is as follows:

S701: The node affected by the fault reports the fault information to the network controller.

Specifically, when the link B-C fails, the node B and the node C are affected by the fault, and the node B and/or the node C reports the fault alarm information to the network controller. The network controller determines that LSP1-2 and LSP1-3 in LSP1 are affected by the fault.

S702: The network controller performs re-routing calculation on the LSP1.

Specifically, the network controller performs re-routing calculation on the cross-connections affected by the fault in LSP1, such as LSP1-2 and LSP1-3. The re-routing service path can be A-B-E-F-C-D. The cross-connection information of LSP1-2 and LSP1-3 needs to be modified. At the same time, new cross-connections LSP1-5 and LSP1-6 are established at nodes E and F respectively.

S703: The network controller sends a cross-connection update command to the re-routing node.

Specifically, the re-routing node includes a node that needs to modify the cross-connect, a node that adds a cross-connect, or a node that deletes the cross-connect. The cross connect update command may include a cross connect modification command, a cross connect setup command, and a cross connect delete command. In this embodiment, the rerouting node includes, for example, nodes B, E, F, and C. Among them, nodes B and C need to modify the cross-connection, and nodes E and F need to add cross-connections. If the service path A-E-F-C-D is rerouted, the cross-connection corresponding to the node B is deleted. The network controller sends a cross-connection update command to the re-routing node according to the re-routing calculation result, instructing the re-routing node to modify the cross-connection, or establish a cross-connection, or delete the cross-connection. For example, nodes B and C modify cross-connections LSP1-2 and LSP1-3, respectively, and nodes E and F establish cross-connections LSP1-5 and LSP1-6. Its In the modification, the cross-connection may be specifically to delete the original cross-connection and establish a new cross-connection. For example, Node B deletes the cross-connection established between port 1 and port 3 and establishes a cross-connection established between port 1 and port 2.

For the nodes B and C, the cross-connection update command sent by the network controller is a cross-connection modification command, which may be a PCUpd (Path Computation Update) message. The cross-connection identifier carried in the cross-connection modification command sent to the node B may be the identifier of the LSP1-2, and the outbound port identifier and/or the outbound label information of the cross-connection information of the node is changed, for example, the egress port identifier is changed to port 2. The out tag information is changed to the out tag 202. The ingress port identifier and/or inbound label information in the cross-connection information of node C is changed.

For nodes E, F, the cross-connection update command sent by the network controller to the node may be a cross-connection establishment command, such as a PCInitiate message, similar to S303.

S704: The rerouting node returns a cross connection establishment result to the network controller.

Specifically, after establishing a new cross-connection, the nodes B, E, F, and C return a message that the cross-connection establishment is successful to the network controller.

S705: The network controller re-updates network resource information.

After receiving the cross-connection establishment success message fed back by the re-routing node, the network controller re-updates the network resource information in the TED and LSPDB of the network controller.

Specifically, the released network resource is identified as idle in the TED, or the released network resource is added to the available network resource list. For example, after the cross-connection corresponding to Node B changes the cross-information, Port 3 on Node B is released, identified as idle or added to the list of available network resources. Port 2 on Node B is occupied, identified as occupied or from Delete from the list of available network resources.

In the LSPDB, the rerouted LSP information is re-associated. For example, LSP1 and LSP1-1, LSP1-2, LSP1-5, LSP1-6, LSP1-3, and LSP1-4 are associated in order.

In the embodiment of the present invention, when the service path in the network fails, the network controller performs re-routing calculation, and sends a cross-connection update command to each node that needs to be modified, deleted, or newly established after the re-routing, so that each node is modified, The corresponding cross-connection is deleted and created, and the re-routed service path is established. The rerouting service path is established through the network controller, and the efficiency of establishing the rerouting service path is improved.

FIG. 8 is an exemplary flowchart of a method for establishing a service path according to an embodiment of the present invention. The method may be performed by a network controller, where the network controller may be an SDN controller, and may be a server or a computer. Specifically, perform the following steps:

S801: The network controller calculates a service path, where the service path includes multiple nodes.

In a specific implementation process, the network controller may calculate a service path from the source node to the sink node after receiving the service path calculation request of the client device. Specifically, the service path calculation request may carry information such as a source node and a sink node. The service path calculated by the network controller can be identified as LSP1. Specifically, none of the multiple nodes that LSP1 passes may support the GMPLS protocol, or some nodes do not support the GMPLS protocol, or both support the GMPLS protocol. After the network controller calculates the service path, each node may report to the network controller whether the node supports the GMPLS protocol. Alternatively, the network controller pre-stores information about whether each node supports the GMPLS protocol.

S802: The network controller separately sends a handover to each of the multiple nodes. A fork connection establishment command, the cross connection establishment command instructing each of the plurality of nodes to establish a cross connection.

Specifically, the cross-connection establishment command sent by the network controller to each node may be implemented by a PCInitiate/PCInit message. Specifically, the PCInitiate/PCInit message may carry the LSP identifier of each node, the cross-connection identifier of the node, and the cross-connection information of the node. For example, if the LSP1 passes through the first node, the LSP identifier corresponding to the first node is LSP1, and the cross-connection identifier of the first node is LSP1-1. The cross-connection information of the first node may include an ingress port identifier and an egress port identifier on the first node, and may further include inbound label information and outbound label information on the first node. The first node can establish a cross-connection from the ingress port to the egress port according to the cross connect command. For example, LSP1 can also pass through the second node, and the LSP identifier of the second node is LSP2, and the cross-connection identifier of the second node is LSP1-2. The cross-connection information of the second node may include an ingress port identifier and an egress port identifier on the second node, and may further include inbound label information and outbound label information on the second node. The second node can establish a cross-connection from the ingress port to the egress port according to the cross connect command.

Specifically, when LSP1 further includes multiple nodes supporting the GMPLS protocol, a plurality of nodes supporting the GMPLS protocol form a sub-service path. The source node of the sub-service path is the third node, and the sink node is the fourth node. The third node and the fourth node support the GMPLS protocol. The network controller also sends a sub-service path establishment order to the third node of the source node of the sub-service path. The third node may establish a sub-service path connection between the third node and the fourth node according to the sub-service path establishment command. The sub-service path establishment command may carry the LSP identifier of the sub-service path, and may also carry the source node and the sink of the sub-service path. The node can also carry the LSP identifier of the service path. For example, the LSP identifier of the sub-service path is LSP1-3, and the LSP of the service path identifies LSP1. Optionally, the sub-service path establishing command may further include an ingress port identifier, an outbound port identifier, an inbound label information, and an outgoing label information of the third node and/or the fourth node. You can also carry the inbound port ID, outbound port ID, inbound label information, and outbound label information of any other node on the sub-service path.

S803: The network controller receives a message that a cross-connection establishment success is successful from each of the plurality of nodes, and establishes a connection of the service path by a cross-connection established by each of the plurality of nodes.

After each cross-connection on LSP1 is successfully established, the network controller can determine that the service path LSP1 is successfully established. Optionally, when the sub-service path on the LSP1 is successfully established, for example, when the sub-service path from the third node to the fourth node is successfully established, the network controller may determine that the service path LSP1 is successfully established. The network controller may save the established cross-connections and/or sub-service paths in the LSPDB, and may also perform sequential association. For example, LSP1 is composed of LSP1-1, LSP1-2, and LSP1-3.

When a physical link in a network fails, the cross-connection and/or sub-service path through which LSP1 passes may be affected. For example, when the network controller cross-connects on LSP1 is affected by the fault, the re-routing calculation is performed. After the network controller performs the rerouting calculation, the cross-connection update command is sent to the re-routing node. The rerouting node includes a node that needs to modify the cross connection, a node that newly adds a cross connection, or a node that deletes the cross connection. The cross connect update command includes a cross connect modification command, a cross connect setup command, and a cross connect delete command.

Specifically, the network controller performs re-routing calculation on LSP1, and LSP1 after re-routing The modified cross-connection corresponding to the first node is included. The network controller sends a cross-connection modification command to the first node, and the first node can establish a new cross-connection according to the cross-connection modification command. The network controller receives the message that the modified cross-connection is successfully established from the first node, and establishes the connection of the service path after the re-routing by the modified cross-connection established by the first node. The modified cross-connection may be a cross-connection between the new ingress port and the original egress port, or may be a cross-connection between the original ingress port and the new egress port, or may be a new ingress port and a new one. Cross-connection between the outgoing ports. The cross-connection modification command can be implemented by using a PCUpd message. The cross-connection modification command may carry the new cross-connection information of the first node, and may also carry the new cross-connection identifier of the first node. Optionally, the cross-connection identifier of the first node may also be unchanged, and is still LSP1-1. The ingress port identifier and/or the egress port identifier on the first node are updated, and the modified cross-connection information of the first node may include a new ingress port identifier and/or a new egress port identifier, and may also include a new entry. Tag information and/or new tag information.

After the network controller performs the re-routing calculation on the LSP1, the service path before the re-routing passes through the second node, but the re-routed service path does not pass through the second node, so the second node needs to delete the cross-connection. Specifically, the network controller sends a cross-connection deletion command to the second node to instruct the second node to delete the cross-connection. Further, the network controller receives a message that the cross-connection deletion from the second node is successful.

The rerouted LSP1 may further include a fifth cross-connection corresponding to the fifth node. The fifth cross-connection is a new cross-connection, and the establishing process is similar to establishing a cross-connection with the first node in S802.

After the cross-connection of each re-routing node is successfully established, the network controller may It is determined that LSP1 is successfully established after rerouting. The network controller may re-associate the cross-connections corresponding to the re-routing nodes in LSP1 in the LSPDB.

According to the technical solution provided by the embodiment of the present invention, the network controller calculates a service path, where the service path includes multiple nodes, and the network controller separately sends a cross-connection establishment command to each of the multiple nodes. The cross-connection establishment command instructs each of the plurality of nodes to establish a cross-connection; the network controller receives a message from each of the plurality of nodes that the cross-connection is successfully established, through the plurality of nodes A cross-connection established by each of the nodes establishes a connection of the service path. In the process of establishing a service path, the network controller directly sends a cross-connection establishment command to each node in the network, thereby establishing an end-to-end service path directly through the network controller, thereby improving the efficiency of establishing the service path.

FIG. 9 is a schematic diagram of a logical structure of a network controller according to an embodiment of the present invention. The network controller may include a computing unit 901, a transmitting unit 902, and a determining unit 903.

The computing unit 901 is configured to calculate a service path, where the service path includes multiple nodes. Specifically, the method steps performed by the computing unit 902 can be referred to S801.

In a specific implementation process, the calculating unit 901 may calculate a service path from the source node to the sink node after receiving the service path calculation request of the client device. Specifically, the service path calculation request may carry information such as a source node and a sink node. The service path calculated by the calculation unit 901 can be identified as LSP1. Specifically, none of the multiple nodes that LSP1 passes may support the GMPLS protocol, or some nodes do not support the GMPLS protocol, or both support the GMPLS protocol. The network controller may further include a determining unit, and after the network controller calculates the service path, each node may report to the determining unit whether the GMPLS protocol is supported. Alternatively, the judging unit pre-stores information on whether each node supports the GMPLS protocol.

The sending unit 902 is configured to separately send a cross-connection establishment command to each of the plurality of nodes, where the cross-connection establishment command instructs each of the plurality of nodes to establish a cross-connection. Specifically, the method step performed by the sending unit 902 can be referred to S802.

Specifically, the cross-connection establishment command sent by the sending unit 902 to each node may be implemented by using a PCInitiate/PCInit message. Specifically, the PCInitiate/PCInit message may carry the LSP identifier of each node, the cross-connection identifier of the node, and the cross-connection information of the node. For example, if the LSP1 passes through the first node, the LSP identifier corresponding to the first node is LSP1, and the cross-connection identifier of the first node is LSP1-1. The cross-connection information of the first node may include an ingress port identifier and an egress port identifier on the first node, and may further include inbound label information and outbound label information on the first node. The first node can establish a cross-connection from the ingress port to the egress port according to the cross connect command. For example, LSP1 can also pass through the second node, and the LSP identifier of the second node is LSP2, and the cross-connection identifier of the second node is LSP1-2. The cross-connection information of the second node may include an ingress port identifier and an egress port identifier on the second node, and may further include inbound label information and outbound label information on the second node. The second node can establish a cross-connection from the ingress port to the egress port according to the cross connect command.

Specifically, when LSP1 further includes multiple nodes supporting the GMPLS protocol, a plurality of nodes supporting the GMPLS protocol form a sub-service path. The source node of the sub-service path is the third node, and the sink node is the fourth node. The third node and the fourth node support the GMPLS protocol. The network controller also sends a sub-service path establishment order to the third node of the source node of the sub-service path. The third node can establish a command according to the sub-service path establishment command. A sub-service path connection between the three nodes and the fourth node. The sub-service path establishment command may carry the LSP identifier of the sub-service path, and may also carry the source node and the sink node of the sub-service path, and may also carry the LSP identifier of the service path. For example, the LSP identifier of the sub-service path is LSP1-3, and the LSP of the service path identifies LSP1. Optionally, the sub-service path establishing command may further include an ingress port identifier, an outbound port identifier, an inbound label information, and an outgoing label information of the third node and/or the fourth node. You can also carry the inbound port ID, outbound port ID, inbound label information, and outbound label information of any other node on the sub-service path.

The receiving unit 903 is configured to receive a message that the cross-connection establishment success is successful from each of the multiple nodes, and establish a connection of the service path by using a cross-connection established by each of the multiple nodes. Specifically, the method step performed by the receiving unit 902 can be referred to S803.

After each cross-connection on the LSP1 is successfully established, the receiving unit 903 may determine that the service path LSP1 is successfully established. Optionally, when the sub-service path on the LSP1 is successfully established, for example, when the sub-service path from the third node to the fourth node is successfully established, the receiving unit 903 may determine that the service path LSP1 is successfully established. The network controller can save the established cross-connections in the LSPDB, and can also perform sequential association. For example, LSP1 is composed of LSP1-1, LSP1-2, and LSP1-3.

When a physical link in a network fails, the cross-connection and/or sub-service path through which LSP1 passes may be affected. For example, when the cross-connection on LSP1 is affected by the fault, the computing unit 901 performs a re-routing calculation. After the calculation unit 901 performs the re-routing calculation, the transmitting unit 902 sends a cross-connection update command to the re-routing node. The rerouting node includes a node that needs to modify the cross connection, a node that adds a new cross connection, or deletes the cross connection. Connected nodes. The cross-connection update command includes: a cross-connection modification command, a cross-connection establishment command, and a cross-connection deletion command.

Specifically, the calculation unit 901 performs re-routing calculation on the LSP1, and the re-routed LSP1 includes the modified cross-connection corresponding to the first node. The network controller sends a cross-connection modification command to the first node, and the first node may establish a modified cross-connection according to the cross-connection modification command. The network controller receives the message that the modified cross-connection is successfully established from the first node, and establishes the connection of the service path after the re-routing by the modified cross-connection established by the first node. The modified cross-connection may be a cross-connection between the new ingress port and the original egress port, or may be a cross-connection between the original ingress port and the new egress port, or may be a new ingress port and a new one. Cross-connection between the outgoing ports. The cross-connection modification command can be implemented by using a PCUpd message. The cross-connection modification command may carry the new cross-connection information of the first node, and may also carry the new cross-connection identifier of the first node. Optionally, the cross-connection identifier of the first node may also be unchanged, and is still LSP1-1. The ingress port identifier and/or the egress port identifier on the first node are updated, and the new cross-connection information of the first node may include a new ingress port identifier and/or a new egress port identifier, and may also include a new ingress label. Information and/or new tag information.

After the calculation unit 901 performs the re-routing calculation on the LSP1, the service path before the re-routing passes through the second node, but the re-routed service path does not pass through the second node, so the second node needs to delete the cross-connection. Specifically, the network controller sends a cross-connection deletion command to the second node to instruct the second node to delete the cross-connection. Further, the network controller receives a message that the cross-connection deletion from the second node is successful.

The rerouted LSP1 may further include a fifth cross-connection corresponding to the fifth node. Its The fifth cross-connection is a new cross-connection, and the establishment process is similar to establishing a cross-connection with the first node in S802.

After the cross-connection establishment of each re-routing node is successful, the determining unit 903 may determine that the re-routed LSP1 is successfully established. The network controller may re-associate the cross-connections corresponding to the re-routing nodes in LSP1 in the LSPDB.

According to the technical solution provided by the embodiment of the present invention, the calculating unit 901 calculates a service path, where the service path includes multiple nodes, and the sending unit 902 separately sends a cross-connection establishment command to each of the plurality of nodes, where the cross a connection establishment command instructing each of the plurality of nodes to establish a cross-connection; the receiving unit 903 receives a message that a cross-connection establishment success is successful from each of the plurality of nodes, through each of the plurality of nodes The cross-connection established by the node establishes a connection of the service path. In the process of establishing a service path, the network controller directly sends a cross-connection establishment command to each node in the network, thereby establishing an end-to-end service path directly through the network controller, thereby improving the efficiency of establishing the service path.

FIG. 10 is a schematic structural diagram of a computer device 1000 according to an embodiment of the present invention. As shown in FIG. 10, the computer device 1000 includes a processor 1001, a memory 1002, an input/output interface 1003, a communication interface 1004, and a bus 1005. The processor 1001, the memory 1002, the input/output interface 1003, and the communication interface 1004 implement a communication connection with each other through the bus 1005.

The processor 1001 may be a general-purpose central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or at least one integrated circuit for executing related programs. The technical solution provided by the embodiments of the present invention.

The memory 1002 may be a read only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 1002 can store an operating system and other applications. When the technical solution provided by the embodiment of the present invention is implemented by software or firmware, the program code for implementing the technical solution provided by the embodiment of the present invention is saved in the memory 1002 and executed by the processor 1001.

The input/output interface 1003 is for receiving input data and information, and outputting data such as an operation result.

Communication interface 1004 enables communication between computer device 1000 and other devices or communication networks using transceivers such as, but not limited to, transceivers.

Bus 1005 can include a path for communicating information between various components of computer device 1000 (e.g., processor 1001, memory 1002, input/output interface 1003, and communication interface 1004).

In a specific implementation process, the network controller executes the code stored in the memory 1002 by the processor 1001 to implement a computing service path, where the service path includes multiple nodes; and the network controller sends each of the multiple nodes through the communication interface 1004. Each of the nodes sends a cross-connection establishment command, the cross-connection establishment command instructing each of the plurality of nodes to establish a cross-connection; the network controller receives from each of the plurality of nodes through the communication interface 1004 The connection establishes a successful message; the network controller executes the code stored in the memory 1002 by the processor 1001 to establish a connection of the service path through a cross-connection established by each of the plurality of nodes.

Specifically, the method steps shown in FIGS. 3, 7, and 8 can be implemented by the computer device 1000 shown in FIG. It should be noted that although the computer device 1000 shown in FIG. 10 only shows the processor 1001, the memory 1002, the input/output interface 1003, the communication interface 1004, and the bus 1005, those skilled in the art should understand in the specific implementation process. Computer device 1000 also contains other devices necessary to achieve proper operation. In the meantime, those skilled in the art will appreciate that computer device 1000 may also include hardware devices that implement other additional functions, depending on the particular needs. Moreover, those skilled in the art will appreciate that computer device 1000 may also only include the components necessary to implement embodiments of the present invention, and does not necessarily include all of the devices shown in FIG.

Those of ordinary skill in the art will appreciate that various aspects of the present invention, or possible implementations of various aspects, may be embodied as a system, method, or computer program product. Thus, aspects of the invention, or possible implementations of various aspects, may employ an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, etc.), or a combination of soft Forms of embodiments of hardware and hardware are collectively referred to herein as "circuits," "modules," or "systems." Furthermore, aspects of the invention, or possible implementations of various aspects, may take the form of a computer program product, which is a computer readable program code stored in a computer readable medium.

The computer readable medium can be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium includes, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing, such as random access memory (RAM), read only memory (ROM), Erase programmable read-only memory (EPROM or flash memory), optical fiber, portable read-only memory (CD-ROM).

The processor in the computer reads the computer readable program code stored in the computer readable medium such that the processor is capable of performing the various functional steps specified in each step of the flowchart, or a combination of steps; A device that functions as specified in each block, or combination of blocks.

The computer readable program code can execute entirely on the user's computer, partly on the user's computer, as a separate software package, partly on the user's computer and partly on the remote computer, or entirely on the remote computer or server. . It should also be noted that in some alternative implementations, the functions noted in the various steps in the flowcharts or in the blocks in the block diagrams may not occur in the order noted. For example, two steps, or two blocks, shown in succession may be executed substantially concurrently or the blocks may be executed in the reverse order.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or computer software and A combination of electronic hardware is implemented. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods for implementing the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present invention.

The above is only a few embodiments of the present invention, and various modifications and changes may be made thereto without departing from the spirit and scope of the invention.

Claims

A method for establishing a service path, the method comprising:

The network controller calculates a service path, where the service path includes multiple nodes;

The network controller separately sends a cross-connection establishment command to each of the plurality of nodes, the cross-connection establishment command instructing each of the plurality of nodes to establish a cross-connection;

The network controller receives a message that a successful cross-connection is established from each of the plurality of nodes, and establishes a connection of the service path through a cross-connection established by each of the plurality of nodes.
The method of claim 1, wherein after the network controller calculates the service path, the method further comprises:

The network controller determines that each of the plurality of nodes does not support the general multi-protocol label switching GMPLS protocol.
The method of claim 1, wherein the service path further comprises a plurality of nodes supporting the GMPLS protocol, and the plurality of nodes supporting the GMPLS protocol form a sub-service path, the method further comprising:

The network controller sends a sub-service path establishment command to the source node of the sub-service path, where the sub-service path establishment command instructs the source node to establish the sub-service path;

The network controller receives a message that the sub-service path from the source node is successfully established, and establishes a connection of the service path by using a sub-service path established by the source node.
The method of claim 1 or 2, wherein the service path is built After success, it also includes:

When the service path fails, the network controller performs re-routing calculation on the service path, and the service path after the re-routing passes through the first node, and the first node needs to modify the cross-connection;

Sending, by the network controller, a cross-connection modification command to the first node, where the cross-connection modification command instructs the first node to modify the cross-connection;

The network controller receives a message that the cross-connection modification is successful from the first node, and establishes a connection of the service path after the re-routing by the modified cross-connection of the first node.
The method according to claim 1 or 2, wherein after the service path is successfully established, the method further includes:

When the service path fails, the network controller performs re-routing calculation on the service path, and the service path after the re-routing passes through the second node, and the second node needs to establish a cross-connection;

The network controller sends a second cross-connection establishment command to the second node, where the second cross-connection establishment command instructs the second node to establish a second cross-connection;

And the network controller receives a message that the second cross-connection is successfully established from the second node, and establishes a connection of the service path after the re-routing by using the second cross-connection established by the second node.
The method according to claim 1 or 2, wherein after the service path is successfully established, the method further includes:

When the service path fails, the network controller enters the service path Row rerouting calculation, the service path before the rerouting passes through the third node, and the third node needs to delete the cross connection;

Sending, by the network controller, a cross-connection deletion command to the third node, where the third cross-connection deletion command instructs the third node to delete a cross-connection;

The network controller receives a message that the cross-connection deletion from the third node is successful.
The method of any of claims 1-6, wherein the cross-connection establishment command is implemented by a path computation unit protocol PCEP.
A network controller, wherein the network controller comprises:

a computing unit, configured to calculate a service path, where the service path includes multiple nodes;

a sending unit, configured to separately send a cross-connection establishment command to each of the plurality of nodes, where the cross-connection establishment command instructs each of the plurality of nodes to establish a cross-connection;

And a receiving unit, configured to receive a message that the cross-connection establishment success is successful from each of the plurality of nodes, and establish a connection of the service path by using a cross-connection established by each of the multiple nodes.
The network controller according to claim 8, wherein the network controller further comprises:

The determining unit is configured to determine that each of the plurality of nodes does not support the universal multi-protocol label switching GMPLS protocol.
The network controller according to claim 8, wherein the service path further comprises a plurality of nodes supporting the GMPLS protocol, and the plurality of nodes supporting the GMPLS protocol The nodes form a sub-service path.

The sending unit is further configured to send a sub-service path establishment command to the source node of the sub-service path, where the sub-service path establishment command instructs the source node to establish the sub-service path;

The receiving unit is further configured to receive a message that the sub-service path from the source node is successfully established, and establish a connection of the service path by using a sub-service path established by the source node.
A network controller according to claim 8 or 9, wherein

The computing unit is further configured to: when the service path fails, the network controller performs re-routing calculation on the service path, and the service path after the re-routing passes through the first node, where the first The node needs to modify the cross-connection;

The sending unit is further configured to send a cross-connection modification command to the first node, where the cross-connection modification command instructs the first node to modify the cross-connection;

The receiving unit is further configured to receive a message that the cross-connection modification succeeds from the first node, and establish a connection of the service path after the re-routing by using the modified cross-connection of the first node.
A network controller according to claim 8 or 9, wherein

The computing unit is further configured to: when the service path fails, the network controller performs re-routing calculation on the service path, and the service path after the re-routing passes through the second node, the second The node needs to establish a cross-connection;

The sending unit is further configured to send a second cross-connection establishment command to the second node, where the second cross-connection establishment command instructs the second node to establish a second cross-connection;

The receiving unit is further configured to receive a message that the second cross-connection is successfully established from the second node, and establish a connection of the service path after the re-routing by using the second cross-connection established by the second node.
A network controller according to claim 8 or 9, wherein

The calculating unit is further configured to: when the service path fails, the network controller performs re-routing calculation on the service path, where the service path before the re-routing passes through a third node, and the third The node needs to delete the cross-connection;

The sending unit is further configured to send a cross-connection deletion command to the third node, where the third cross-connection deletion command instructs the third node to delete the cross-connection;

The receiving unit is further configured to receive a message that the cross-connection deletion is successful from the third node.
The network controller according to any one of claims 8-13, wherein the sending unit is configured to implement the cross-connection establishment command by a path calculation unit protocol PCEP.
A network system, characterized in that the network system at least comprises: a network controller and a plurality of nodes,

The network controller is configured to calculate a service path, where the service path includes the multiple nodes;

The network controller is further configured to separately send a cross-connection establishment command to each of the plurality of nodes, where the cross-connection establishment command instructs each of the plurality of nodes to establish a cross-connection;

The network controller is further configured to receive, from each of the multiple nodes The fork connection establishes a successful message, establishing a connection of the service path through a cross-connection established by each of the plurality of nodes.
A network system according to claim 15 wherein:

The network controller is further configured to determine that each of the multiple nodes does not support the universal multi-protocol label switching GMPLS protocol.
The network system according to claim 15, wherein the service path further comprises a plurality of nodes supporting the GMPLS protocol, and the plurality of nodes supporting the GMPLS protocol form a sub-service path.

The network controller is configured to send a sub-service path establishment command to the source node of the sub-service path, where the sub-service path establishment command instructs the source node to establish the sub-service path;

The network controller is further configured to receive a message that the sub-service path from the source node is successfully established, and establish a connection of the service path by using a sub-service path established by the source node.
A network controller, comprising: a processor, a memory, a bus, and a communication interface; the memory is configured to store a computer to execute an instruction, and the processor is connected to the memory through the bus, when the computer In operation, the processor executes the computer-executable instructions stored by the memory to cause the computer to perform the method of any of claims 1-7.