WO2015101169A1

WO2015101169A1 - Method for deploying service by sdn and sdn controller

Info

Publication number: WO2015101169A1
Application number: PCT/CN2014/093846
Authority: WO
Inventors: 董杰; 陈国义
Original assignee: 华为技术有限公司
Priority date: 2013-12-31
Filing date: 2014-12-15
Publication date: 2015-07-09
Also published as: CN104753713A; CN104753713B

Abstract

Disclosed are a method for deploying a service by an SDN and an SDN controller. The SDN controller receives a service request from an upper-layer application, the service request comprising a service type and service parameters, and the service type being a tunnel or a VPN service; and the SDN controller obtains path information of the tunnel or information of at least one PE device corresponding to the VPN service, and notifies the obtained information to an ingress network node of the tunnel or the at least one PE device, so as to complete deployment of the tunnel or the VPN service. The problems in the prior art that the deployment of the VPN service by manual configuration requires a lot of time, is error prone, complex in tunnel establishment, and poor in service expansion can be solved.

Description

Method and SDN controller for SDN deployment service

This application claims the priority of the Chinese patent application filed on December 31, 2013, the Chinese Patent Office, the application number is CN201310753129.5, and the invention is entitled "A method and SDN controller for SDN deployment service". The citations are incorporated herein by reference.

Technical field

The present invention relates to the field of network communications, and in particular, to a software defined network (SDN) deployment service method and an SDN controller.

Background technique

The Virtual Private Network (VPN) service is an important service provided by network operators to customers. Currently, the main way to establish a VPN in the network is to manually configure the provider edge (PE) device and establish a VPN connection between the PEs.

Network operators provide VPN services to users, which are usually carried by tunnels. A commonly used tunnel is a Traffic Engineering (TE) tunnel. The advantage of a TE tunnel is that the operator can control the tunnel path and implement bandwidth guarantee. At present, the establishment of a TE tunnel in the network is mainly performed by manually configuring the router on the router, and the shortest path first (SPF)/Constrained Shortest Path First (CSPF) calculation is performed by the head node router of the TE tunnel. The tunnel path is obtained. Alternatively, the head node router of the TE tunnel is used as a path Computation Client (PCC) to initiate a route calculation request to the Path Computation Element (PCE). The PCE returns the path calculation result. The head node router of the TE tunnel, and the head node router of the TE tunnel, uses the Resource Reservation Protocol-Traffic Engineering (RSVP-TE) to establish the TE tunnel.

However, existing VPN deployments require manual configuration and are prone to configuration errors.

Summary of the invention

The embodiment of the invention provides a method, a system and an SDN controller for the SDN deployment service, which can solve the problem that the VPN service deployment needs manual configuration and is prone to configuration errors.

The first aspect provides a method for deploying a service by using an SDN, including:

The SDN controller receives a service request from an upper layer application, where the service request includes a service type and a service parameter, where the service type is a tunnel, and the service parameter includes information of an ingress network node and information of an egress network node;

The SDN controller sends a path calculation request to the path calculation unit PCE, where the path calculation request includes the service type and the service parameter;

Receiving a path calculation response returned by the PCE, where the path calculation response includes path information of the tunnel;

Notifying the path information of the tunnel to the ingress network node.

In a first possible implementation manner of the first aspect, the notifying the path information of the tunnel to the ingress network node includes:

And transmitting, by the SDN controller, a control session established by the ingress network node to the ingress network node.

In a second possible implementation manner of the first aspect, the notifying the path information of the tunnel to the ingress network node includes:

Transmitting the path information of the tunnel to the network management system NMS, and advertising the path information of the tunnel to the ingress network node by using the NMS.

According to the first aspect and any one of the first and second possible implementations of the first aspect, in a third possible implementation of the first aspect, the tunnel is advertised to the ingress network node After the path information, the method further includes: receiving a service deployment result fed back by the ingress network node.

According to a third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the service deployment result that is received by the ingress network node feedback includes:

And receiving, by the SDN controller, a control session established with the ingress network node, a service deployment result fed back by the ingress network node.

According to a third possible implementation manner of the first aspect, in a fifth possible implementation manner of the first aspect, the service deployment result that is received by the ingress network node feedback includes:

The service deployment result fed back by the ingress network node is received by the network management system NMS.

In a second aspect, a method for deploying a SDN service is provided, including:

The SDN controller receives the service request from the upper layer application, where the service request includes a service type and a service parameter, and the service type is a virtual private network VPN service;

Obtaining, according to the service request, information about at least one carrier edge PE device corresponding to the VPN service;

Determining service deployment information corresponding to the VPN service according to the information of the at least one PE device and the service parameter;

And advertise the service deployment information to the at least one PE device.

In a first possible implementation manner of the second aspect, the service parameter includes information of at least one user edge CE device;

And the obtaining, by the service request, the information of the at least one PE device corresponding to the VPN service, including:

Sending a policy query request to the policy module, where the policy query request includes information about the VPN service and the at least one CE device;

And receiving, by the policy module, a query response that is allowed to establish the VPN service, where the query response includes information about the at least one PE device.

In a second possible implementation manner of the second aspect, the service parameter includes the information of the at least one PE device, and the acquiring, by the service request, the information of the at least one PE device corresponding to the VPN service, including: Obtaining the at least one PE device from the service parameter Information.

According to the second aspect and any one of the first and second possible implementations of the second aspect, in a third possible implementation of the second aspect, the advertised to the at least one PE device Business deployment information includes:

And transmitting, by the SDN controller, the service deployment information to the at least one PE device by using a control session established by the SDN controller and the at least one PE device.

According to the second aspect and any one of the first to third possible implementations of the second aspect, in a fourth possible implementation of the second aspect, the advertised to the at least one PE device Business deployment information includes:

The service deployment information is sent to the network management system (NMS), and the service deployment information is sent to the at least one PE device by using the NMS.

According to the second aspect and any one of the first to fourth possible implementations of the second aspect, in a fifth possible implementation of the second aspect, the service is advertised to the at least one PE device After the information is deployed, the method further includes: receiving a service deployment result fed back by the at least one PE device.

According to a fifth possible implementation manner of the second aspect, in a sixth possible implementation manner of the second aspect, the receiving, by the SDN controller, the service deployment result that is received by the at least one PE device The control session established by the at least one PE device receives the service deployment result fed back by the at least one PE device.

According to a fifth possible implementation manner of the second aspect, in a seventh possible implementation manner of the second aspect, the receiving, by the network management system, the NMS, the service deployment result The result of the service deployment fed back by a PE device.

According to the second aspect and any one of the first to seventh possible implementation manners of the second aspect, in an eighth possible implementation manner of the second aspect, the method further includes: deploying information according to the service , associating or establishing a tunnel for the VPN service.

Any of the first to eighth possible implementations according to the second aspect and the second aspect The ninth possible implementation manner of the second aspect, the service parameter further includes any one or more of the following combinations: delay, bandwidth, protection condition, and service priority;

Determining the service deployment information corresponding to the VPN service according to the information of the at least one PE device and the service parameter, including:

Generating a logical topology corresponding to the VPN service according to the information of the at least one PE device and the service parameter;

Determining service deployment information of the at least one PE device according to the logical topology.

According to the second aspect and any one of the first to ninth possible implementations of the second aspect, in a tenth possible implementation of the second aspect,

The VPN service type is a virtual circuit VC; correspondingly, the at least one PE includes a first PE device and a second PE device;

Or the VPN service type is a virtual network VN; correspondingly, the at least one PE device includes a first PE device, a second PE device, and a third PE device;

Alternatively, the VPN service type is a virtual tree VT; correspondingly, the at least one PE device includes a root PE device and at least one leaf PE device.

In a third aspect, an SDN controller is provided, including:

a service request receiving module, configured to receive a service request from an upper layer application, where the service request includes a service type and a service parameter, where the service type is a tunnel, and the service parameter includes information of an ingress network node and information of an egress network node. ;

a path calculation client PCC, configured to send a path calculation request to the path calculation unit PCE, where the path calculation request includes the service type and the service parameter; and receive a path calculation response returned by the PCE, where the path calculation The path information of the tunnel is included in the response;

And a sending module, configured to advertise the path information of the tunnel to the ingress network node.

In a first possible implementation manner of the third aspect, the SDN controller further includes:

The result receiving module is configured to receive a service deployment result fed back by the ingress network node.

According to a first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, the sending module is specifically configured to use a control session between the SDN controller and the ingress network node, Sending path information of the tunnel to the ingress network node;

Correspondingly, the result receiving module is configured to receive, by using the control session, a service deployment result fed back by the ingress network node.

According to a first possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the sending module is configured to send path information of the tunnel to a network management system (NMS), by using the NMS Notifying the ingress network node of path information of the tunnel;

Correspondingly, the result receiving module is specifically configured to receive, by using the NMS, a service deployment result fed back by the ingress network node.

In a fourth aspect, an SDN controller is provided, including:

a service request receiving module, configured to receive a service request from an upper layer application, where the service request includes a service type and a service parameter, where the service type is a virtual private network VPN service;

a device information acquiring module, configured to acquire information of at least one carrier edge PE device corresponding to the VPN service according to the service request;

a deployment determining module, configured to determine service deployment information corresponding to the VPN service according to the information of the at least one PE device and the service parameter;

And a sending module, configured to notify the at least one PE device of the service deployment information.

In a first possible implementation manner of the fourth aspect, the service parameter includes information of at least one user edge CE device;

The device information obtaining module is specifically configured to send a policy query request to the policy module, where the policy query request includes information of the application requester, the VPN service, and information of the at least one CE device; The query response returned by the policy module is allowed to establish the VPN service, and the query response includes information of the at least one PE device.

According to a first possible implementation of the fourth aspect, the second possible implementation in the fourth aspect In the mode, the service parameter includes information of the at least one PE device, and the device information acquiring module is specifically configured to obtain information of the at least one PE device from the service parameter.

According to the fourth aspect and any one of the first and second possible implementation manners of the fourth aspect, in a third possible implementation manner of the fourth aspect, the SDN controller further includes: a result receiving module, A service deployment result for receiving feedback from the at least one PE device.

According to a third possible implementation manner of the fourth aspect, in a fourth possible implementation manner of the fourth aspect, the sending module is specifically configured to be used by the SDN controller to establish a control session with the at least one PE device. Sending the service deployment information to the at least one PE device;

Correspondingly, the result receiving module is configured to receive, by using the control session, a service deployment result fed back by the at least one PE device.

According to a third possible implementation manner of the fourth aspect, in a fifth possible implementation manner of the fourth aspect, the sending module is configured to send the service deployment information to a network management system (NMS), by using the NMS Transmitting, by the at least one PE device, the service deployment information;

Correspondingly, the result receiving module is configured to receive, by using the NMS, a service deployment result fed back by the at least one PE device.

According to the fourth aspect, the any one of the first to fifth possible implementation manners of the fourth aspect, in a sixth possible implementation manner of the fourth aspect, the SDN controller further includes: a tunnel determining module, And configured to associate or establish a tunnel for the VPN service according to the service deployment information.

According to the fourth aspect and any one of the first to sixth possible implementation manners of the fourth aspect, in the seventh possible implementation manner of the fourth aspect, the service parameter further includes any one or more of the following Combination of: delay, bandwidth, protection conditions, and service priority;

The deployment determining module is configured to generate a logical topology corresponding to the VPN service according to the information of the at least one PE device and the service parameter, and determine service deployment information of the at least one PE device according to the logical topology. .

Any of the first to seventh possible implementations according to the fourth aspect and the fourth aspect The eighth possible implementation manner of the fourth aspect, the VPN service type is a virtual circuit VC; correspondingly, the several PE devices include a first PE device and a second PE device;

Or the VPN service type is a virtual network VN; correspondingly, the plurality of PE devices include a first PE device, a second PE device, and a third PE device;

Alternatively, the VPN service type is a virtual tree VT; correspondingly, the several PE nodes include a root PE device and at least one leaf PE device.

A fifth aspect provides a system for SDN deployment services, including an SDN controller and an upper layer application;

The SDN controller is configured to receive a service request of the upper layer application, where the service request includes a service type and a service parameter, and the service corresponding to the service type is deployed for the upper layer application according to the service request.

In a first possible implementation manner of the fifth aspect, the service type is a tunnel; the service parameter includes information about an ingress network node and an egress network node of the tunnel; and the SDN controller is the third aspect or the third Any possible implementation of the aspect; the system further comprising the ingress network node, the egress network node, and a path computation unit PCE.

In a second possible implementation manner of the fifth aspect, the service type is a VPN service, where the service parameter includes information of at least one CE device, or information of at least one PE device corresponding to the VPN service; A controller, as in any one of the foregoing fourth or fourth aspect, wherein the system further comprises the at least one PE device.

In the SDN deployment service method provided by the embodiment of the present invention, the SDN controller receives the service request from the upper layer application, and the service request of the service type is a tunnel, and the device information is obtained through the interaction with the PCE to obtain the path information of the tunnel and advertised to the ingress network node of the tunnel. The establishment of the tunnel is completed; the service request of the VPN service is obtained, the information of the multiple PE nodes corresponding to the VPN service is obtained, and the service deployment information is advertised to the multiple PE devices to complete the establishment of the VPN service. For service requests from upper-layer applications, tunnels or VPNs can be completed quickly without manual configuration. The establishment of the service solves the problem that the tunnel or the VPN service is manually configured to be error-prone in the prior art.

DRAWINGS

FIG. 1 is a schematic diagram of a system for an SDN deployment service according to an embodiment of the present invention;

2 is a flowchart of a method for deploying an SDN according to an embodiment of the present invention;

FIG. 3 is a flowchart of another method for deploying an SDN according to an embodiment of the present invention;

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

FIG. 5 is a schematic structural diagram of another SDN controller according to an embodiment of the present disclosure;

6 is a schematic structural diagram of another SDN controller according to an embodiment of the present invention.

FIG. 7 is a schematic structural diagram of still another SDN controller according to an embodiment of the present invention.

detailed description

The above described objects, features, and advantages of the embodiments of the present invention will become more apparent and understood.

Software defined network (SDN) is a new type of network architecture. It provides easy application layer by defining the interface between SDN layer, SDN layer and upper application, and the interface between SDN layer and lower layer network. Deployed and extended network services.

Referring to FIG. 1 , a system for an SDN deployment service according to an embodiment of the present invention includes an SDN controller and an upper layer application. The SDN controller receives a service request from an upper-layer application, where the service request includes a service parameter and a service type, such as a VPN, a tunnel, and the like, and deploys a service corresponding to the service type according to the service request.

As shown in FIG. 1, the system further includes a PE device; optionally, a PCE and a policy module. Further optionally, a network management system (NMS) is also included.

The PCE is configured to provide a path calculation service for the SDN controller.

The policy module is configured to provide a policy service, such as a service authority control, for the SDN controller. The policy module may be located on a different network device from the SDN controller, for example, the policy module is implemented by a dedicated server; the policy module may also be located on the same network device as the SDN controller. The method of the SDN deployment service provided by the embodiment of the present invention and the SDN controller are described in detail.

FIG. 2 is a schematic diagram of a method for deploying an SDN according to an embodiment of the present invention, including:

201. The SDN controller receives a service request from an upper layer application.

The service request includes a service type and a service parameter, where the service type is a tunnel, and the service parameter includes information of an ingress network node and an egress network node of the tunnel, for example, an internet protocol of an ingress network node of the tunnel (Internet Protocol, Referred to as IP) address, the IP address of the egress node.

The tunnel can be a TE tunnel.

202. The SDN controller sends a path calculation request to the path calculation unit PCE, where the path calculation request includes the service type and the service parameter.

The service parameters may further include: path constraint information; for example, the hop count of the path, the value of the path, the network node that must pass, the network node that cannot pass, and the like.

Further, the service parameter may further include one or more of a delay, a bandwidth, and a protection condition.

203. Receive a path calculation response returned by the PCE, where the path calculation response includes path information of the tunnel.

After receiving the path calculation request of the SDN, the PCE may further calculate, according to the path constraint information, the delay, the bandwidth, the protection condition, etc., according to the information of the ingress node and the information of the egress node. path.

The path calculation response includes path information of the tunnel; path information of the tunnel The complete path information or partial path information of the tunnel is included, for example, the IP address of all or part of the network nodes through which the tunnel passes; optionally, the path information of the tunnel may further include reserved bandwidth, and the path generation Value and so on.

A PCE Communication Protocol (PCEP) communication between the PCE and the PCC may be used between the SDN controller and the PCE.

204. Notifying the ingress network node of path information of the tunnel.

The SDN controller advertises the path information of the tunnel to the ingress network node of the tunnel, and optionally also controls the ingress network node to establish a tunnel according to the path information of the tunnel.

Specifically, the ingress network node may carry the tunnel path information by using RSVP-TE signaling to complete establishment of the tunnel.

Further, after the path information of the tunnel is advertised to the ingress network node, the method may further include: receiving a service deployment result fed back by the ingress network node. Specifically, the ingress network node feeds back information about the establishment result and status of the tunnel to the SDN controller.

Optionally, the advertise the tunnel path information to the ingress network node, including: transmitting, by using a control session established between the SDN controller and the ingress network node, path information of the tunnel to the Initiating a network node and controlling the ingress network node to establish the tunnel according to path information of the tunnel. Correspondingly, the receiving the service deployment result fed back by the ingress network node comprises: receiving, by using the control session, a service deployment result fed back by the ingress network node.

Optionally, the advertise the path information of the tunnel to the ingress network node, including: sending the tunnel path information to a network management system (NMS), to the ingress network by using the NMS Sending, by the node, path information of the tunnel; specifically, the NMS may configure the ingress network node, send path information of the tunnel to the ingress network node, and instruct the ingress network node to establish the tunnel . Correspondingly, the receiving the service deployment result fed back by the ingress network node includes: The NMS receives the service deployment result fed back by the ingress network node. Specifically, the NMS can communicate with the ingress network node by using a network management and configuration mechanism, such as a simple network management protocol (SNMP), and a network configuration protocol (netconf) to manage the ingress network node. Control: transmitting path information of the tunnel to the ingress network node, and instructing the ingress network node to establish the tunnel.

In the SDN deployment service method provided by the embodiment of the present invention, the SDN controller receives the service request for establishing a tunnel from the upper layer application, and obtains the path information of the tunnel by interacting with the PCE, and advertises the path information of the tunnel to the ingress network node of the tunnel to complete the establishment of the tunnel. Without manual configuration, it can quickly respond to the service request for establishing a tunnel, improve the scalability of the tunnel service, and avoid the problem of manual configuration being error-prone.

FIG. 3 is a schematic diagram of another SDN deployment service method according to an embodiment of the present invention, including:

301. The SDN controller receives a service request from an upper layer application.

The service request includes a service type and a service parameter, where the service type is a VPN service.

The VPN service includes a virtual circuit (VC), a virtual network (VN), and a virtual tree (VT).

302. Acquire, according to the service request, information about at least one PE device corresponding to the VPN service.

Optionally, the service parameter includes information of at least one customer edge (CE) device, such as an IP address of the CE device, and the at least one PE device corresponding to the VPN service is obtained according to the service request. Information, including:

And receiving, by the policy module, a query response that is allowed to establish the VPN service, where the query response includes information about the at least one PE device. Further optionally, the strategy The query request includes the user information of the upper layer application, such as a user name, an identity, and the like; the policy module determines, according to the user information, whether to allow the VPN service to be established; specifically, the policy module is based on the user. The information is obtained by the user to determine whether the VPN service is allowed to be established. If the policy module determines that the VPN service is allowed to be established, the policy module acquires information about the at least one PE device corresponding to the VPN service; if the policy module determines that the VPN service is not allowed to be established, the policy The module returns a query response to the SDN controller that does not allow establishment of a VPN service.

Optionally, the service parameter includes the information of the at least one PE device, and the acquiring the information of the at least one PE device corresponding to the VPN service according to the service request, including: obtaining the Information about at least one PE device.

If the VPN service is a VC, the at least one PE device includes a first PE device and a second PE device;

If the VPN service is a VN, the at least one PE node includes a first PE device, a second PE device, and a third PE device; and of course, the fourth PE device, the fifth PE device, and the like.

If the VPN service is a VT, the at least one PE device includes a root PE device and at least one leaf PE device.

The policy module may be located on a different network device than the SDN controller, or may be located on the same network device.

303. Determine service deployment information corresponding to the VPN service according to the information of the at least one PE device and the service parameter.

Optionally, the service parameter further includes any one or more of the following: a delay, a bandwidth, a protection condition, and a service priority; the SDN controller is configured according to the information of the at least one PE device The service parameter determines the service deployment information corresponding to the VPN service; specifically, the SDN controller may form a logical topology corresponding to the VPN service according to the information of the at least one PE device and the service parameter, according to the Logical topology determination The service deployment information corresponding to the VPN service. Specifically, the deployment information of each of the at least one PE device is obtained according to the logical topology, so that the service deployment information corresponding to the VPN service is determined.

304. The service deployment information is advertised to the at least one PE device to complete VPN service deployment.

Further, the SDN controller may associate, according to the service deployment information corresponding to the VPN service, the established tunnel that meets the requirements of the VPN service, or may be deployed according to the service corresponding to the VPN service. The information is used to establish a tunnel for the VPN service by using the method shown in FIG. 2 of the present invention.

Further, after the service deployment information is advertised to the at least one PE device, the method may further include: receiving a service deployment result fed back by the at least one PE device. Specifically, each of the at least one PE device feeds back information such as a VPN service establishment result and a status to the SDN controller.

Optionally, the advertising the service deployment information to the at least one PE device comprises: sending the service to the at least one PE device by using a control session established by the SDN controller and the at least one PE device Deployment information. Correspondingly, the service deployment result that is received by the at least one PE device comprises: receiving, by the control session established with the at least one PE device, a service deployment result fed back by the at least one PE device.

Optionally, the advertise the service deployment information to the at least one PE device, including: sending the service deployment information to a network management system (NMS), and sending the service deployment to the at least one PE device by using the NMS information. Correspondingly, the service deployment result that is received by the at least one PE device is received by the NMS, and the service deployment result fed back by the at least one PE device is received by the NMS. Specifically, the NMS can communicate with the at least one PE device through a network management configuration mechanism, such as SNMP, netconf, and the like.

The SDN deployment service method provided by the embodiment of the present invention, the SDN controller receives a service request for establishing a VPN from an upper layer application, and obtains a letter of multiple PE devices corresponding to the VPN service. And the service deployment information is advertised to the plurality of PE devices to complete the establishment of the VPN service; without manual configuration, the VPN service can be quickly established, the scalability of the VPN service is improved, and the manual configuration can be avoided. An error-prone problem.

As shown in FIG. 4, an embodiment of the present invention provides an SDN controller, which is used to implement the SDN deployment service shown in FIG. 2 of the present invention. The SDN controller includes:

The service request receiving module 401 is configured to receive a service request from an upper layer application, where the service request includes a service type and a service parameter, where the service type is a tunnel, and the service parameter includes an ingress network node and an egress network of the tunnel. Information about the node, for example, the IP address of the ingress network node of the tunnel and the IP address of the egress network node;

a path calculation client PCC 402, configured to send a path calculation request to the path calculation unit PCE, where the path calculation request includes the service type and the service parameter; and receive a path calculation response returned by the PCE, the path Calculating path information including the tunnel in the response;

a sending module 403, configured to notify the ingress network node of path information of the tunnel;

Optionally, the SDN controller further controls the ingress network node to establish a tunnel according to the path information of the tunnel. Specifically, the ingress network node may carry the tunnel path information by using RSVP-TE signaling to complete establishment of the tunnel.

The tunnel can be a TE tunnel.

Between the SDN controller and the PCE, PCEP communication may be employed.

Further, the service parameter may further include a delay, a bandwidth, a protection condition, and the like.

After receiving the path calculation request of the SDN, the PCE may further perform the path constraint information, the delay, the bandwidth, the protection condition, etc. according to the information of the ingress network node and the information of the egress network node. The tunnel calculates the path.

The path information of the tunnel includes the complete path information or the partial path information of the tunnel, for example, the IP address of all or part of the network nodes through which the tunnel passes; optionally, the path information of the tunnel may further include a reservation. Bandwidth, the value of the path, etc.

Further, the SDN controller further includes: a result receiving module, configured to receive a service deployment result fed back by the ingress network node.

The sending module is specifically configured to send the path information of the tunnel to the ingress network node by using a control session with the ingress network node; correspondingly, the result receiving module is specifically configured to pass the Controlling a session, receiving a service deployment result fed back by the ingress network node.

Or the sending module is specifically configured to send the path information of the tunnel to the network management system NMS, and send the path information of the tunnel to the ingress network node by using the NMS; correspondingly, the result receiving module, Specifically, the service deployment result fed back by the ingress network node is received by the NMS.

The SDN controller provided by the embodiment of the present invention receives the service request for establishing a tunnel from the upper layer application, and obtains the path information of the tunnel by interacting with the PCE, and advertises the path information of the tunnel to the ingress network node of the tunnel to complete the establishment of the tunnel; no manual configuration is required. The tunnel can be established quickly, and the way to establish a tunnel is simple and fast, which improves the scalability of the tunnel service and avoids the problem of manual configuration being error-prone.

As shown in FIG. 5, an embodiment of the present invention provides another SDN controller, which is used to implement the SDN deployment service shown in FIG. 3 of the present invention. The SDN controller includes:

The service request receiving module 501 is configured to receive a service request from an upper layer application, where the service request includes a service type and a service parameter; and the service type is a virtual private network VPN service;

The device information obtaining module 502 is configured to obtain, according to the service request, information about at least one carrier edge PE device corresponding to the VPN service;

The deployment determining module 503 is configured to determine service deployment information corresponding to the VPN service according to the information of the at least one PE device and the service parameter.

The sending module 504 is configured to advertise the service deployment information to the at least one PE device.

The VPN service includes VC, VN, and VT. The service parameters may also include delay, bandwidth, protection conditions, service priority, and the like.

If the VPN service is a VN, the number of the PE devices includes the first PE device, the second PE device, and the third PE device; of course, the fourth PE device, the fifth PE device, and the like;

If the VPN service is a VT, the number of the PE devices includes a root PE device and at least one leaf PE device.

Optionally, the service parameter includes information of at least one CE device, for example, an IP address of the CE device, and the device information obtaining module 502 is specifically configured to send a policy query request to the policy module, where the policy query request includes The information about the VPN service and the at least one CE device is received; and the query response returned by the policy module is allowed to be established, and the query response includes the information of the at least one PE device.

Further, optionally, the policy query request further includes user information of the upper layer application, such as a user name, an identity identifier, and the like; and the policy module determines, according to the user information, whether to allow the VPN service to be established; specifically, The policy module acquires the rights of the user according to the user information, to determine whether to allow the VPN service to be established. If the policy module determines that the VPN service is allowed to be established, the policy module acquires information about the at least one PE device corresponding to the VPN service; if the policy module determines that the VPN service is not allowed to be established, the policy The module returns a query response to the SDN controller that does not allow establishment of a VPN service.

Optionally, the SDN controller further includes the policy module.

Optionally, the service parameter includes information about the at least one PE device, and the device information obtaining module 502 is configured to obtain information about the at least one PE device from the service parameter.

Further, the SDN controller further includes: a result receiving module, configured to receive a service deployment result fed back by the at least one PE device.

The sending module is configured to send the service deployment information to the at least one PE device by using a control session established with the at least one PE device. Correspondingly, the result receiving module is configured to receive the service deployment result fed back by the at least one PE device by using the control session established with the at least one PE device.

Or the sending module is configured to send the service deployment information to the network network system (NMS), and send the service deployment information to the at least one PE device by using the NMS. Correspondingly, the result receiving module is configured to receive, by using the NMS, a service deployment result fed back by the at least one PE device.

Further, the SDN controller further includes: a tunnel determining module, configured to associate, according to the service deployment information corresponding to the VPN service, an established tunnel that meets the VPN service requirement; or The service deployment information corresponding to the VPN service is used to establish a tunnel for the VPN service according to the method shown in FIG. 1 of the present invention.

The SDN controller provided by the embodiment of the present invention receives the service request for establishing a VPN from the upper-layer application, obtains the information of the multiple PE devices corresponding to the VPN service, and advertises the service deployment information to the multiple PE devices to complete the VPN service. The establishment of the VPN service can be completed quickly without manual configuration, the scalability of the VPN service is improved, and the problem of poor real-time configuration and error-prone can be avoided.

FIG. 6 is a schematic structural diagram of another SDN controller according to an embodiment of the present invention, for implementing the method shown in FIG. 2 of the present invention, where the SDN controller includes: a processor 601, a memory 602, and a communication. An interface 603; wherein the processor 601, the memory 602, and the communication interface 603 are connected by a bus or The other methods are connected to each other, and the connection is made by the bus 604 in FIG. 6 as an example.

The memory 602 is configured to store a program. In particular, the program can include program code, the program code including computer operating instructions. The memory 502 may include a random access memory (RAM), and may also include a non-volatile memory, such as at least one disk storage.

The processor 601 executes the program stored in the memory 602, and the method for performing the SDN deployment service provided by the embodiment of the present invention includes:

Receiving a service request from an upper layer application, where the service request includes a service type and a service parameter, where the service type is a tunnel, and the service parameter includes information of an ingress network node and information of an egress network node;

Notifying the path information of the tunnel to the ingress network node.

The communication interface 603 is configured to communicate with an upper layer application; and is further configured to communicate with a PCE; and is further configured to communicate with an ingress network node of the tunnel.

The method also includes receiving a service deployment result fed back by the ingress network node.

Specifically, the advertise the path information of the tunnel to the ingress network node, including: transmitting, by using the control session established by the SDN controller and the ingress network node, path information of the tunnel to the ingress network node. Correspondingly, the receiving the service deployment result fed back by the ingress network node comprises: receiving, by using the control session, a service deployment result fed back by the ingress network node.

Or the advertise the path information of the tunnel to the ingress node, and send the path information of the tunnel to the network management system (NMS), and send the path information of the tunnel to the ingress network node by using the NMS. . Correspondingly, the receiving the portal network node is reversed The service deployment result of the feed includes: receiving, by the NMS, a service deployment result fed back by the portal network node.

Optionally, the communication interface 603 is further configured to communicate with the NMS.

The SDN controller provided by the embodiment of the present invention receives the service request for establishing a tunnel from the upper layer application, and obtains the path information of the tunnel by interacting with the PCE, and advertises the path information of the tunnel to the ingress network node of the tunnel to complete the establishment of the tunnel; no manual configuration is required. It can quickly respond to the service request for establishing a tunnel, improve the scalability of the tunnel service, and avoid the problem of manual configuration being error-prone.

FIG. 7 is a schematic structural diagram of still another SDN controller according to an embodiment of the present invention, for implementing the method shown in FIG. 3 of the present invention, where the SDN controller includes: a processor 701, a memory 702, and a communication. The interface 703; wherein the processor 701, the memory 702, and the communication interface 703 are connected to each other by a bus or the like, and are connected by a bus 704 in FIG. 7 as an example.

The memory 702 is configured to store a program. In particular, the program can include program code, the program code including computer operating instructions. Memory 702 may include RAM and may also include non-volatile memory, such as at least one disk storage.

The processor 701 executes the program stored in the memory 702, and the method for performing the SDN deployment service provided by the embodiment of the present invention includes:

Receiving a service request from an upper layer application, where the service request includes a service type and a service parameter, where the service type is a virtual private network VPN service;

And advertise the service deployment information to the at least one PE device.

The communication interface 703 is configured to communicate with an upper layer application, and is further configured to communicate with the at least one PE node.

The VPN service includes VC, VN, and VT;

If the VPN service is a VC, the number of the PE nodes includes a first PE node and a second PE node;

If the VPN service is a VN, the number of the PE nodes includes a first PE node, a second PE node, and a third PE node; of course, the fourth PE node, the fifth PE node, and the like;

If the VPN service is a VT, the number of the PE nodes includes a root PE node and at least one leaf PE node.

Optionally, the service parameter includes the information of the at least one user edge CE device, and the acquiring, by the service request, the information of the at least one PE device corresponding to the VPN service, including:

The communication interface 703 is further configured to communicate with the policy module.

The method further includes receiving a service deployment result fed back by the at least one PE device.

Specifically, the advertising the service deployment information to the at least one PE device comprises: sending the service deployment information to the at least one PE device by using a control session established with the at least one PE device. Correspondingly, the service deployment result that is received by the at least one PE device comprises: receiving, by the control session established with the at least one PE device, a service deployment result fed back by the at least one PE device.

Or the advertising the service deployment information to the at least one PE device includes: The service deployment information is sent to the network management system (NMS), and the service deployment information is sent to the at least one PE device by using the NMS. Correspondingly, the service deployment result that is received by the at least one PE device is received by the NMS, and the service deployment result fed back by the at least one PE device is received by the NMS.

Further, the method further includes: associating the established VPN service that meets the VPN service requirement with the VPN service according to the service deployment information; or, according to the service deployment information, adopting the present invention as shown in FIG. The method establishes a tunnel for the VPN service.

Further, the embodiment of the present invention further provides a system for SDN deployment services, including an SDN controller and an upper layer application.

The SDN controller receives a service request from the upper-layer application, where the service request includes a service parameter and a service type, and deploys a service corresponding to the service type according to the service request.

Optionally, the service type is a tunnel; the service parameter includes information of an ingress network node and an egress network node of the tunnel; the SDN controller is as described in the embodiment of FIG. 4 or FIG. 6 of the present invention; The ingress network node and the egress network node; further comprising a path calculation unit PCE for providing a path calculation service for the SDN controller. The service parameters may further include: path constraint information; for example, the hop count of the path, the value of the path, the network node that must pass, the network node that cannot pass, and the like.

Optionally, the service type is a VPN service; the service parameter includes information of at least one CE device, or information of at least one PE device corresponding to the VPN service; The SDN controller is as described in the embodiment of FIG. 5 or 7 of the present invention; the system further includes the at least one PE device. Optionally, the system further includes at least one CE device and a policy module, where the policy module is configured to provide a policy service, such as a service authority control, for the SDN controller. The policy module may be located on a different network device from the SDN controller, for example, the policy module is implemented by a dedicated server; the policy module may also be located on the same network device as the SDN controller.

Optionally, the system further comprises a network management system NMS.

One of ordinary skill in the art can understand that all or part of the steps of implementing the above embodiments may be performed by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, which may be a ROM. /RAM, disk or CD, etc.

The above is only a preferred embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or within the technical scope disclosed by the present invention. Alternatives are intended to be covered by the scope of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

A method for software-defined network SDN deployment service, comprising:

The SDN controller receives a service request from an upper layer application, where the service request includes a service type and a service parameter, where the service type is a tunnel, and the service parameter includes information of an ingress network node and information of an egress network node;

The SDN controller sends a path calculation request to the path calculation unit PCE, where the path calculation request includes the service type and the service parameter;

Receiving a path calculation response returned by the PCE, where the path calculation response includes path information of the tunnel;

Notifying the path information of the tunnel to the ingress network node.
The method according to claim 1, wherein the notifying the path information of the tunnel to the ingress network node comprises:

And transmitting, by the SDN controller, a control session established by the ingress network node to the ingress network node.
The method according to claim 1, wherein the notifying the path information of the tunnel to the ingress network node comprises:

Transmitting the path information of the tunnel to the network management system NMS, and sending, by the NMS, the path information of the tunnel to the ingress network node.
The method according to any one of claims 1 to 3, further comprising: after advertise the path information of the tunnel to the ingress network node, further comprising:

Receiving a service deployment result fed back by the ingress network node.
The method according to claim 4, wherein the receiving the service deployment result fed back by the ingress network node comprises:

And receiving, by the SDN controller, a control session established by the ingress network node, the service deployment result fed back by the ingress network node.
The method of claim 4 wherein said receiving said portal network The service deployment results fed back by the network node include:

Receiving, by the network management system NMS, the service deployment result fed back by the ingress network node.
A method for software-defined network SDN deployment service, comprising:

The SDN controller receives the service request from the upper layer application, where the service request includes a service type and a service parameter, and the service type is a virtual private network VPN service;

Obtaining, according to the service request, information about at least one carrier edge PE device corresponding to the VPN service;

Determining service deployment information corresponding to the VPN service according to the information of the at least one PE device and the service parameter;

And advertise the service deployment information to the at least one PE device.
The method according to claim 7, wherein the service parameter comprises information of at least one user edge CE device;

And the obtaining, by the service request, the information of the at least one PE device corresponding to the VPN service, including:

Sending a policy query request to the policy module, where the policy query request includes information about the VPN service and the at least one CE device;

And receiving, by the policy module, a query response that is allowed to establish the VPN service, where the query response includes information about the at least one PE device.
The method according to claim 7, wherein the service parameter includes information of the at least one PE device, and the obtaining, by the service request, the information of the at least one PE device corresponding to the VPN service, including:

Obtaining information of the at least one PE device from the service parameters.
The method according to any one of claims 7 to 9, wherein the advertising the service deployment information to the at least one PE device comprises:

Controlling a session established by the SDN controller with the at least one PE device The at least one PE device sends the service deployment information.
The method according to any one of claims 7 to 9, wherein the advertising the service deployment information to the at least one PE device comprises:

Sending the service deployment information to the network management system (NMS), and sending the service deployment information to the at least one PE device by using the NMS.
The method according to any one of claims 7 to 11, further comprising: after advertising the service deployment information to the at least one PE device,

Receiving a service deployment result fed back by the at least one PE device.
The method according to claim 12, wherein the receiving the service deployment result fed back by the at least one PE device comprises:

Receiving, by the control session established by the SDN controller and the at least one PE device, the service deployment result fed back by the at least one PE device.
The method according to claim 12, wherein the receiving the service deployment result fed back by the at least one PE device comprises:

Receiving, by the network management system NMS, the service deployment result fed back by the at least one PE device.
The method according to any one of claims 7 to 14, further comprising: associating or establishing a tunnel for the VPN service according to the service deployment information.
The method according to any one of claims 7 to 15, wherein the service parameter further comprises a combination of any one or more of the following: delay, bandwidth, protection condition, and service priority;

Determining the service deployment information corresponding to the VPN service according to the information of the at least one PE device and the service parameter, including:

Generating a logical topology corresponding to the VPN service according to the information of the at least one PE device and the service parameter;

Determining service deployment information of the at least one PE device according to the logical topology.
A method according to any one of claims 7 to 16, wherein

The VPN service type is a virtual circuit VC; correspondingly, the at least one PE includes a first PE device and a second PE device;

Or the VPN service type is a virtual network VN; correspondingly, the at least one PE device includes a first PE device, a second PE device, and a third PE device;

Alternatively, the VPN service type is a virtual tree VT; correspondingly, the at least one PE device includes a root PE device and at least one leaf PE device.
A software defined network SDN controller, comprising:

a service request receiving module, configured to receive a service request from an upper layer application, where the service request includes a service type and a service parameter, where the service type is a tunnel, and the service parameter includes information of an ingress network node and information of an egress network node. ;

a path calculation client PCC, configured to send a path calculation request to the path calculation unit PCE, where the path calculation request includes the service type and the service parameter; and receive a path calculation response returned by the PCE, where the path calculation The path information of the tunnel is included in the response;

And a sending module, configured to advertise the path information of the tunnel to the ingress network node.
The SDN controller according to claim 18, further comprising:

The result receiving module is configured to receive a service deployment result fed back by the ingress network node.
The SDN controller according to claim 19, wherein the sending module is configured to send, by using a control session between the SDN controller and the ingress network node, path information of the tunnel to the Said portal network node;

Correspondingly, the result receiving module is configured to receive, by using the control session, the service deployment result fed back by the ingress network node.
The SDN controller according to claim 19, wherein the sending module is configured to send path information of the tunnel to a network management system NMS, and send the tunnel to the ingress network node by using the NMS. Path information;

Correspondingly, the result receiving module is specifically configured to receive the portal by using the NMS The service deployment result fed back by the network node.
A software defined network SDN controller, comprising:

a service request receiving module, configured to receive a service request from an upper layer application, where the service request includes a service type and a service parameter, where the service type is a virtual private network VPN service;

a device information acquiring module, configured to acquire information of at least one carrier edge PE device corresponding to the VPN service according to the service request;

a deployment determining module, configured to determine service deployment information corresponding to the VPN service according to the information of the at least one PE device and the service parameter;

And a sending module, configured to notify the at least one PE device of the service deployment information.
The SDN controller according to claim 22, wherein the service parameter comprises information of at least one user edge CE device;

The device information obtaining module is configured to send a policy query request to the policy module, where the policy query request includes information about the VPN service and the at least one CE device, and receiving the permission returned by the policy module to establish the The query response of the VPN service, where the query response includes information of the at least one PE device.
The SDN controller according to claim 23, wherein the service parameter includes information of the at least one PE device, and the device information obtaining module is configured to acquire the at least one of the service parameters. Information about the PE device.
The SDN controller according to any one of claims 22 to 24, further comprising:

The result receiving module is configured to receive a service deployment result fed back by the at least one PE device.
The SDN controller according to claim 25, characterized in that

The sending module is configured to send the service deployment information to the at least one PE device by using a control session established by the SDN controller and the at least one PE device;

Correspondingly, the result receiving module is configured to receive, by using the control session, the service deployment result fed back by the at least one PE device.
The SDN controller according to claim 25, characterized in that

The sending module is configured to send the service deployment information to the network management system (NMS), and send the service deployment information to the at least one PE device by using the NMS;

Correspondingly, the result receiving module is configured to receive, by using the NMS, the service deployment result fed back by the at least one PE device.
The SDN controller according to any one of claims 22 to 27, further comprising: a tunnel determining module, configured to associate or establish a tunnel for the VPN service according to the service deployment information.
The SDN controller according to any one of claims 22 to 28, wherein the service parameter further comprises any one or more of the following combinations: delay, bandwidth, protection condition, and service priority;

The deployment determining module is configured to generate a logical topology corresponding to the VPN service according to the information of the at least one PE device and the service parameter, and determine service deployment information of the at least one PE device according to the logical topology. .
The SDN controller according to any one of claims 22 to 29, wherein the VPN service type is a virtual circuit VC; correspondingly, the plurality of PE devices comprise a first PE device and a second PE device;

Or the VPN service type is a virtual network VN; correspondingly, the plurality of PE devices include a first PE device, a second PE device, and a third PE device;

Alternatively, the VPN service type is a virtual tree VT; correspondingly, the several PE nodes include a root PE device and at least one leaf PE device.
A system for software-defined network SDN deployment service, characterized in that it comprises an SDN controller and an upper layer application;

The SDN controller is configured to receive a service request from the upper-layer application, where the service request includes a service type and a service parameter, and deploy, according to the service request, a service corresponding to the service type for the upper-layer application.
The system according to claim 31, wherein the service type is a tunnel; and the service parameters include information of an ingress network node and an egress network node of the tunnel;

The SDN controller includes the SDN controller according to any one of claims 18 to 21;

The system also includes the ingress network node, the egress network node, and a path computation unit PCE.
The system according to claim 31, wherein the service type is a VPN service; the service parameter includes information of at least one CE device, or information of at least one PE device corresponding to the VPN service;

The SDN controller includes the SDN controller according to any one of claims 22 to 30;

The system also includes the at least one PE device.