Openflow protocol-based resource control method and system, and apparatus

Patent metadata

Field	Value
Publication number	US-11140091-B2
Application number	US-201715858815-A
Country	US
Kind code	B2
Filing date	Dec 29, 2017
Priority date	Jun 30, 2015
Publication date	Oct 5, 2021
Grant date	Oct 5, 2021

Abstract

An OpenFlow protocol-based resource control method and system, and an apparatus are provided, to resolve a problem that forwarding resources are not fully used. The method provided by the present invention may include: sending, by a controller, a resource allocation request message to a forwarder, where an OpenFlow interface is established between the controller and the forwarder; receiving, by the controller, a resource configuration message that is sent by the forwarder in response to the resource allocation request message, where the resource configuration message includes an idle forwarding resource obtained by the forwarder from total forwarding resources; and allocating, by the controller according to the idle forwarding resource, a service-accessible forwarding resource to an already created service on the controller, where the service-accessible forwarding resource is some or all resources in idle forwarding resources.

First claim

What is claimed is:

1. An OpenFlow protocol-based resource control method, comprising:
sending, by a controller, a resource allocation request message to a forwarder, wherein an OpenFlow interface is established between the controller and the forwarder, wherein forwarding services are configured on both the controller and the forwarder;
receiving, by the controller, a resource configuration message from the forwarder, wherein the resource configuration message is sent by the forwarder in response to the resource allocation request message, and the resource configuration message includes an idle forwarding resource obtained by the forwarder from total forwarding resources on the forwarder, the idle forwarding resource including a resource that is not an already occupied forwarding resource;
creating, by the controller, a resource pool configured to store the idle forwarding resource obtained by the forwarder and perform resource allocation and management for an already created service on the controller;
allocating, by the controller according to the idle forwarding resource in the resource pool, a service-accessible forwarding resource to the already created service on the controller, wherein the service-accessible forwarding resource includes some or all resources in the idle forwarding resource;
sending a resource release request message to the forwarder, where the resource release request message includes an idle forwarding resource that needs to be released by the controller; and
establishing an association relationship between the already created service on the controller and the service-accessible forwarding resource allocated to the service, so that the controller can reallocate the service-accessible forwarding resource to the already created service according to the association relationship after the controller releases the service-accessible forwarding resource.

2. The method according to claim 1 , wherein the sending, by a controller, a resource allocation request message to a forwarder comprises:
sending, by the controller to the forwarder, a resource allocation request message for requesting to obtain multiple resources when the controller establishes an initial connection to the forwarder; and
re-sending, by the controller to the forwarder, the resource allocation request message for requesting to obtain multiple resources if multiple idle forwarding resources obtained by the controller have been allocated; and
the receiving, by the controller, a resource configuration message from the forwarder includes:
receiving, by the controller, a resource configuration message that is re-sent by the forwarder in response to the resource allocation request message, wherein the resource configuration message that is re-sent by the forwarder includes multiple idle forwarding resources re-obtained by the forwarder from the total forwarding resources.

3. An OpenFlow protocol-based resource control method, comprising:
receiving, by a forwarder, a resource allocation request message sent by a controller, wherein an OpenFlow interface is established between the forwarder and the controller, wherein forwarding services are configured on both the controller and the forwarder;
obtaining, by the forwarder, an idle forwarding resource from total forwarding resources on the forwarder according to the resource allocation request message, the idle forwarding resource including a resource that is not an already occupied forwarding resource;
sending, by the forwarder, a resource configuration message to the controller, wherein the resource configuration message includes the idle forwarding resource obtained by the forwarder;
receiving a resource release request message from the forwarder, where the resource release request message includes an idle forwarding resource that needs to be released by the controller;
adding, to the total forwarding resources, the idle forwarding resource released by the controller;
sending a resource release success message to the controller; and
establishing an association relationship between an already created service on the controller and a service-accessible forwarding resource allocated to the service, so that the controller can reallocate the service-accessible forwarding resource to the already created service according to the association relationship after the controller releases the service-accessible forwarding resource.

4. The method according to claim 3 , wherein the receiving, by a forwarder, a resource allocation request message sent by a controller comprises:
receiving, by the forwarder, a resource allocation request message for requesting to obtain multiple resources when the forwarder establishes an initial connection to the controller; and
the obtaining, by the forwarder, an idle forwarding resource from total forwarding resources according to the resource allocation request message includes:
obtaining, by the forwarder, multiple idle forwarding resources from the total forwarding resources according to the resource allocation request message for requesting to obtain multiple resources.

5. A controller, comprising:
a memory; and
a processor coupled to the memory and configured to:
send a resource allocation request message to a forwarder, wherein an OpenFlow interface is established between the controller and the forwarder, wherein forwarding services are configured on both the controller and the forwarder;
receive a resource configuration message from the forwarder, wherein the resource configuration message is sent by the forwarder in response to the resource allocation request message, and the resource configuration message includes an idle forwarding resource obtained by the forwarder from total forwarding resources on the forwarder, the idle forwarding resource including a resource that is not an already occupied forwarding resource;
creating, by the controller, a resource pool configured to store the idle forwarding resource obtained by the forwarder and perform resource allocation and management for an already created service on the controller;
allocate, by the resource pool of the controller according to the idle forwarding resource, a service-accessible forwarding resource to the already created service on the controller, wherein the service-accessible forwarding resource includes some or all resources in the idle forwarding resource;
send a resource release request message to the forwarder, where the resource release request message includes an idle forwarding resource that needs to be released by the controller; and
establish an association relationship between the already created service on the controller and the service-accessible forwarding resource allocated to the service, so that the controller can reallocate the service-accessible forwarding resource to the already created service according to the association relationship after the controller releases the service-accessible forwarding resource.

6. The controller according to claim 5 , wherein the processor is further configured to:
when the controller establishes an initial connection to the forwarder, send, to the forwarder, a resource allocation request message for requesting to obtain multiple resources; and if multiple idle forwarding resources obtained by the controller have been allocated, re-send, to the forwarder, the resource allocation request message for requesting to obtain multiple resources; and
receive a resource configuration message that is re-sent by the forwarder in response to the resource allocation request message, wherein the resource configuration message that is re-sent by the forwarder includes multiple idle forwarding resources re-obtained by the forwarder from the total forwarding resources.

7. A forwarder, comprising:
a

Assignees

• Huawei Tech Co Ltd

Inventors

• Jiang Zhihua
• Ma Peng
• Ni Hui

Classifications

• H04L41/0896

  Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities (flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76) · CPC title

• H04L47/72 Primary

  using reservation actions during connection setup · CPC title

• H04L47/83

  based on usage prediction · CPC title

• H04L43/20

  the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV · CPC title

• H04L41/342

  between virtual entities, e.g. orchestrators, SDN or NFV entities · CPC title