IP Library Granted Patent US 10,554,570
Granted Patent B2
US 10,554,570 · App. 14/909,199 · Granted Feb 4, 2020

Method and device for implementing QoS in OpenFlow network

Inventors: Min Xiao (Shenzhen, CN); Bo Wu (Shenzhen, CN); Junhui Zhang (Shenzen, CN)
Assignee: XI'AN Zhongxing New Software Co., LTD.
H04L47/622H04L45/38H04L45/745H04L47/2441
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,554,570
App. No.
14/909,199
Granted
Feb 4, 2020
Kind
B2
Abstract

Provided are a method and device for implementing QoS in an OpenFlow network. The method includes that: for a packet entering an OpenFlow switch, when a flow table is successfully matched, an instruction which is used for calling a scheduler and adding the packet into a specified queue in the scheduler is executed; and under the triggering of the instruction, queue scheduling is managed by using the scheduler. By using the technical means provided by the disclosure, the technical problem in related art that the OpenFlow switch cannot implement Hierarchical QoS (HQoS) is solved, so that the OpenFlow switch may implement both single-layer QoS and HQoS.

Claims (30)

1. A method for implementing Quality of Service (QoS) in an OpenFlow network, comprising:

for a packet entering an OpenFlow switch, when a flow table is successfully matched, executing an instruction which is used for calling a scheduler and adding the packet into a specified queue in the scheduler; and

under the triggering of the instruction, managing queue scheduling by using the scheduler;

wherein the scheduler further comprises: a next level scheduler ID, wherein the next level scheduler ID is used for a queue in the scheduler to call a next level scheduler.

2. The method according to claim 1 , wherein executing the instruction which is used for calling the scheduler and adding the packet into the specified queue in the scheduler comprises:

executing the instruction in a flow entry, matching the packet, of the flow table.

3. The method according to claim 1 , wherein executing the instruction which is used for calling the scheduler and adding the packet into the specified queue in the scheduler comprises:

according to a scheduler Identity (ID) carried in the instruction, calling the specified scheduler, in a scheduler table, corresponding to the scheduler ID; and

according to a queue ID carried in the instruction, adding the packet into a queue, in the specified scheduler, corresponding to the queue ID.

4. A method for implementing Quality of Service (QoS) in an OpenFlow network, comprising:

adding management information into a first message which is sent to an OpenFlow switch by an OpenFlow controller, wherein the management information is used for performing at least one of the following managements to a specified instruction: adding, modifying and deleting, and the specified instruction is used for calling a scheduler and adding a packet into a specified queue in the scheduler; and

sending the first message to the OpenFlow switch;

wherein the scheduler further comprises: a next level scheduler ID, wherein the next level scheduler ID is used for a queue in the scheduler to call a next level scheduler.

5. The method according to claim 4 , wherein the first message comprises: a flow table configuring message.

6. The method according to claim 4 , further comprising:

sending, by the OpenFlow controller, at least one of the following messages to the OpenFlow switch: a configuring message and a reading message aiming at the scheduler table to which the scheduler belongs; wherein the configuring message is used for performing at least one of the following managements to the scheduler table and entries in the scheduler table: adding, modifying and deleting; the reading message is used for reading the scheduler table and the entries in the scheduler table.

7. The method according to claim 6 , further comprising:

adding scheduler table error reporting information into a second message which is sent to the OpenFlow controller by the OpenFlow switch, wherein the scheduler table error reporting information is used for reporting an exception to the OpenFlow controller when the exception occurs in configuring the scheduler table according to the configuring message or when the exception occurs in reading the scheduler table according to the reading message.

8. The method according to claim 7 , wherein the second message comprises: an error reporting message.

9. A device for implementing Quality of Service (QoS) in an OpenFlow network, comprising:

an executing component configured to, for a packet entering an OpenFlow switch, when a flow table is successfully matched, execute an instruction which is used for calling a scheduler and adding the packet into a specified queue in the scheduler; and

a managing component configured to, under the triggering of the instruction, manage queue scheduling by using the scheduler;

wherein the executing component is further configured to execute the instruction when the scheduler comprises the following content: a next level scheduler Identity (ID), wherein the next level scheduler ID is used for the queue in the scheduler to call a next level scheduler.

10. The device according to claim 9 , wherein the executing component is configured to execute the instruction, in a flow entry, matching the packet, of the flow table.

11. A device for implementing Quality of Service (QoS) in an OpenFlow network, comprising:

a first adding component configured to add management information into a first message which is sent to an OpenFlow switch by an OpenFlow controller, wherein the management information is used for performing at least one of the following managements to a specified instruction: adding, modifying and deleting; and the specified instruction is used for calling a scheduler and adding a packet into a specified queue in the scheduler; and

a sending component, configured to send the first message to the OpenFlow switch;

wherein the scheduler further comprises: a next level scheduler ID, wherein the next level scheduler ID is used for a queue in the scheduler to call a next level scheduler.

12. The device according to claim 11 , further comprising:

a second adding component configured to add scheduler table error reporting information into a second message which is sent to the OpenFlow controller by the OpenFlow switch, wherein the scheduler table error reporting information is used for reporting an exception to the OpenFlow controller when the exception occurs in configuring the scheduler table according to the configuring message or when the exception occurs in reading the scheduler table according to the reading message.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 20, 2019
From: ZTE CORPORATION
To: XI'AN ZHONGXING NEW SOFTWARE CO., LTD.
Reel/Frame 051060/0643 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 1, 2016
From: XIAO, MIN; WU, BO; ZHANG, JUNHUI
To: ZTE CORPORATION
Reel/Frame 037631/0528 →
Priority Claims (1)
CN 2013 1 0330279 · Jul 31, 2013 · national
Continuity (1)
Related Publication 20160191406A1 · Jun 30, 2016
Cited By (1)
US 12,375,419