CN115051951A - Service flow scheduling method, centralized controller and storage medium - Google Patents
Service flow scheduling method, centralized controller and storage medium Download PDFInfo
- Publication number
- CN115051951A CN115051951A CN202110216640.6A CN202110216640A CN115051951A CN 115051951 A CN115051951 A CN 115051951A CN 202110216640 A CN202110216640 A CN 202110216640A CN 115051951 A CN115051951 A CN 115051951A
- Authority
- CN
- China
- Prior art keywords
- queue
- information
- flowspec
- flow
- extended community
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- HRULVFRXEOZUMJ-UHFFFAOYSA-K potassium;disodium;2-(4-chloro-2-methylphenoxy)propanoate;methyl-dioxido-oxo-$l^{5}-arsane Chemical compound [Na+].[Na+].[K+].C[As]([O-])([O-])=O.[O-]C(=O)C(C)OC1=CC=C(Cl)C=C1C HRULVFRXEOZUMJ-UHFFFAOYSA-K 0.000 claims description 11
- 230000000670 limiting effect Effects 0.000 claims description 9
- 238000012545 processing Methods 0.000 abstract description 13
- 238000001914 filtration Methods 0.000 abstract description 11
- 238000007726 management method Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 7
- 238000004891 communication Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 101100042631 Saccharomyces cerevisiae (strain ATCC 204508 / S288c) SIN3 gene Proteins 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 239000012634 fragment Substances 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 230000003111 delayed effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005111 flow chemistry technique Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/46—Interconnection of networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The disclosure provides a service flow scheduling method, a centralized controller and a storage medium, wherein the method comprises the following steps: the centralized controller configures a flow specification queue field based on the information of a main queue or a sub-queue of a service flow, and sets an extended community attribute value; the centralized controller generates FlowSpec routing information, and adds flow matching information, flow specification queue fields and extended community attribute values in the FlowSpec routing information; and the centralized controller sends the FlowSpec routing information to the network routing equipment. According to the method, the centralized controller and the storage medium, the field of the BGP FlowSpec protocol and the action corresponding to the newly-increased community value are expanded, the centralized controller can complete hierarchical QoS scheduling aiming at the flow, the practicability is higher, rich filtering conditions and processing actions can be provided, and the flow can be controlled in a more targeted manner.
Description
Technical Field
The present invention relates to the field of communications technologies, and in particular, to a service flow scheduling method, an integrated controller, and a storage medium.
Background
With the development of the internet, the Service flow increases rapidly, the problem of network congestion becomes serious gradually, which causes the phenomena of data packet loss, time delay increase, transmission sequence disorder, data packet error and the like, and affects the whole internet, thereby the Quality of Service (QoS) technology appears. However, the existing QoS technology can only be applied to the actually existing ports (or their sub-interfaces), and has certain limitations.
Disclosure of Invention
In view of this, a technical problem to be solved by the present invention is to provide a traffic flow scheduling method, a centralized controller, and a storage medium.
According to a first aspect of the present disclosure, a method for scheduling a traffic flow is provided, including: the method comprises the steps that a centralized controller configures a flow specification queue field based on main queue or sub-queue information of a service flow, and an extended community attribute value is set according to an execution action corresponding to a main queue or a sub-queue; the centralized controller generates FlowSpec routing information, and adds flow matching information, the flow specification queue field and the extended community attribute value in the FlowSpec routing information; and the centralized controller sends the FlowSpec routing information to network routing equipment so that a routing controller of the network routing equipment performs flow regulation and control processing according to the FlowSpec routing information.
Optionally, the information carried by the flow specification queue field includes: queue type information and queue ID information; the queue type information is used for representing that the queue is a main queue or a sub-queue, and the main queue and the sub-queue bound by the main queue have the same queue ID information.
Optionally, the performing act includes: minimum bandwidth guarantee and congestion management; under the condition that the execution action represented by the type of the extended community attribute is minimum bandwidth guarantee, the extended community attribute value is a bandwidth guarantee value; and in the case that the execution action characterized by the type of the extended community attribute is congestion management, the extended community attribute value is a queue type.
Optionally, the performing act further comprises: limiting the bandwidth; and under the condition that the execution action represented by the type of the extended community attribute is bandwidth speed limit, the value of the extended community attribute is the speed limit bandwidth.
Optionally, the centralized controller establishes a BGP FlowSpec neighbor relationship with the network routing device; the centralized controller sends first FlowSpec routing information to the network routing equipment; wherein the information carried by the first FlowSpec routing information includes: the flow matching information used for matching with the destination IP address, the flow specification queue field corresponding to the main queue and the extended community attribute value, wherein the extended community attribute value is the first speed limit bandwidth.
Optionally, the centralized controller sends second FlowSpec routing information to the network routing device; wherein the information carried by the second FlowSpec routing information includes: the flow matching information used for matching with the source IP address or the DSCP value, the flow specification queue field corresponding to the subqueue and the extended community attribute value, wherein the extended community attribute value is the second speed limit bandwidth, the bandwidth guarantee value or the queue type.
Optionally, a routing controller of the network routing device performs traffic scheduling operation based on an instruction set; and if the extended community attribute value corresponding to the sub-queue is the second speed limit bandwidth, the routing controller controls the sum of the bandwidths of the sub-queues to be less than or equal to the first speed limit bandwidth of the main queue.
According to a second aspect of the present disclosure, there is provided a centralized controller, comprising: the information configuration module is used for configuring a flow specification queue field based on the information of a main queue or a sub-queue of a service flow and setting an extended community attribute value according to an execution action corresponding to the main queue or the sub-queue; the route generation module is used for generating FlowSpec route information and adding flow matching information, the flow specification queue field and the extended community attribute value into the FlowSpec route information; and the routing sending module is used for sending the FlowSpec routing information to network routing equipment so as to enable a routing controller of the network routing equipment to carry out flow regulation and control processing according to the FlowSpec routing information.
Optionally, the information carried by the flow specification queue field includes: queue type information and queue ID information; the queue type information is used for representing that the queue is a main queue or a sub-queue, and the main queue and the sub-queue bound by the main queue have the same queue ID information.
Optionally, the performing act includes: minimum bandwidth guarantee and congestion management; under the condition that the execution action represented by the type of the extended community attribute is minimum bandwidth guarantee, the extended community attribute value is a bandwidth guarantee value; and in the case that the execution action characterized by the type of the extended community attribute is congestion management, the extended community attribute value is a queue type.
Optionally, the performing act further comprises: limiting the bandwidth; and under the condition that the execution action represented by the type of the extended community attribute is bandwidth speed limit, the value of the extended community attribute is the speed limit bandwidth.
Optionally, the route sending module is configured to establish a BGP FlowSpec neighbor relationship with the network routing device, and send first FlowSpec routing information to the network routing device; wherein the information carried by the first FlowSpec routing information includes: the flow matching information used for matching with the destination IP address, the flow specification queue field corresponding to the main queue and the extended community attribute value, wherein the extended community attribute value is the first speed limit bandwidth.
Optionally, the route sending module is configured to send second FlowSpec routing information to the network routing device; wherein the information carried by the second FlowSpec routing information includes: the flow matching information used for matching with the source IP address or the DSCP value, the flow specification queue field corresponding to the subqueue and the extended community attribute value, wherein the extended community attribute value is the second speed limit bandwidth, the bandwidth guarantee value or the queue type.
Optionally, a routing controller of the network routing device performs traffic scheduling operation based on an instruction set; and if the extended community attribute value corresponding to the sub-queue is the second speed limit bandwidth, the routing controller controls the sum of the bandwidths of the sub-queues to be less than or equal to the first speed limit bandwidth of the main queue.
According to a third aspect of the present disclosure, there is provided a centralized controller, comprising: a memory; and a processor coupled to the memory, the processor configured to perform the method as described above based on instructions stored in the memory.
According to a fourth aspect of the present disclosure, there is provided a computer readable storage medium storing computer instructions for execution by a processor to perform the method as described above.
According to the service flow scheduling method, the centralized controller and the storage medium, the integrated controller can complete hierarchical QoS scheduling aiming at the flows by expanding the fields of the BGP FlowSpec protocol and adding the actions corresponding to the extended community values, and the practicability is higher; the stream filtering information is transmitted by using the reachable information type of the BGP network layer, so that the maintainability is good; and abundant filtering conditions and processing actions are provided, and the flow can be controlled more pertinently.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without inventive exercise.
Fig. 1 is a flow diagram of one embodiment of a traffic flow scheduling method according to the present disclosure;
FIG. 2A is a schematic format diagram of a Flow-Spec NLRI; FIG. 2B is a schematic format diagram of FlowSpec-Queue;
fig. 3 is a schematic diagram of another embodiment of a traffic flow scheduling method according to the present disclosure;
FIG. 4 is a block diagram of one embodiment of a centralized controller according to the present disclosure;
fig. 5 is a block diagram of another embodiment of a centralized controller according to the present disclosure.
Detailed Description
The present disclosure now will be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments of the disclosure are shown. The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
The terms "first", "second", and the like, hereinafter, are used for descriptive purposes only and have no other special meanings.
Fig. 1 is a flowchart illustrating a traffic flow scheduling method according to an embodiment of the present disclosure, as shown in fig. 1:
And 102, generating FlowSpec routing information by the centralized controller, and adding flow matching information, a flow specification queue field and an extended community attribute value in the FlowSpec routing information.
In one embodiment, the flow matching information includes a plurality of attributes of destination IP, destination port, DSCP, fragment type, ICMP code, ICMP type, packet length, source destination port number, protocol number, source IP, source port number, TCP flag, and the like.
And 103, the centralized controller sends the FlowSpec routing information to the network routing equipment so that the routing controller of the network routing equipment performs flow regulation and control processing according to the FlowSpec routing information.
The centralized controller may use a variety of existing methods to send the FlowSpec routing information to the network routing device. And the routing controller of the network routing equipment performs corresponding configuration processing according to the FlowSpec routing information, and performs hierarchical flow regulation and control processing on the service flow packet and the queue by using various existing methods based on the configuration information.
In one embodiment, QoS refers to the ability of a network to provide better service for a given network communication. For example, when a network is overloaded or congested, QoS can ensure that important traffic is not delayed or dropped while ensuring efficient operation of the network. The Flow specification message is used to instruct the network element to match the traffic and control the matched traffic. BGP FlowSpec (BGP Flow Specifications, BGP Flow specification, BGP, Border Gateway Protocol) messages are NLRI (network layer accessibility Information) defined by BGP, and BGP FlowSpec messages may communicate Flow specification Information via NLRI.
The service flow scheduling method improves a BGP FlowSpec protocol, expands a new BGP FlowSpec field, enables the field to be matched with the original twelve-tuple (destination IP, destination port, DSCP, fragment type, ICMP code, ICMP type, message length, source port number, protocol number, source IP, source port number and TCP zone bit), can also define a main queue/sub-queue relationship, and increases a new action of an extended community value, wherein the new action comprises minimum bandwidth guarantee, congestion management and the like.
A corresponding QoS queue may be generated for traffic flows, which may be implemented as a stack, Map, List, or the like. For example, there may be a plurality of main queues for a client, and a plurality of sub queues may be associated under each main queue, and each sub queue may correspond to an item group of the client, and each item group has its own sub queue. The centralized controller transmits corresponding flow actions through BGP FlowSpec flow classification definition of a main queue or a sub-queue based on service flow and through an extended community value mode, and completes the scheduling method for realizing the QOS of the complex service flow.
In one embodiment, the information carried by the flow specification queue field includes: queue type information and queue ID information; the queue type information is used for representing that the queue is a main queue or a sub-queue, and the main queue and the sub-queue bound by the main queue have the same queue ID information.
The actions include minimum bandwidth guarantees, congestion management, etc. Under the condition that the execution action represented by the type of the extended community attribute is minimum bandwidth guarantee, the value of the extended community attribute is a bandwidth guarantee value; in case the performed action characterized by the type of extended community attribute is congestion management, the extended community attribute value is a queue type. The action further includes bandwidth speed limiting; and under the condition that the execution action represented by the type of the extended community attribute is the bandwidth speed limit, the value of the extended community attribute is the speed limit bandwidth.
In one embodiment, the BGP FlowSpec extension header is newly defined:
1. the flow-spec NLRI structure is newly defined: based on the existing flow-spec NLRI structure, a new FlowSpec-queue field (flow canonical queue field) is added at the header of the message to match 12 tuples and distinguish the main queue and the sub-queue, as shown in fig. 2A.
The format of the FlowSpec-Queue field is shown in FIG. 2B: FlowSpec-Queue takes one byte to indicate the type and ID of the Queue, and the specific meaning is as follows:
queue-type: occupying one bit. When the value is 0, the queue is represented as a sub-queue; when the value is 1, it indicates that the queue is the main queue.
Queue-ID: seven bits are occupied. And distributing values by the centralized controller, wherein the values range from 1 to 127.
The main Queue and the sub-queues bound by the main Queue can be allocated with the same Queue-ID, namely the Queue with the same Queue-ID, the main Queue is represented by the Queue-type value of 1, and the sub-Queue is represented by the Queue-type value of 0. The main Queue and the sub-Queue with the same Queue-ID have a binding relationship.
2. Newly defined extended community values: the newly added type values are 0x800A and 0x800B, which respectively represent minimum bandwidth guarantee and congestion management. The type and coding of Extended community is shown in table 1 below:
TABLE 1 type and encoding Table for Extended community
As shown in table 1, extended community attributes having types of 0x8006 to 0x8009 have been defined in RFC 5575. type 0x 800A: the minimum bandwidth guarantee allows setting traffic to fast forward in order to get the minimum bandwidth guarantee, coded as a bandwidth guarantee value of 6 bytes (unit: Kbit/s). Type 0x 800B: congestion management allows traffic to BE set to a corresponding queue for message forwarding through a queue scheduling algorithm, and the encoded queue type is 1 byte (five upper bits are not used, and three lower bits have values from 0 to 7, which respectively indicate that the queues are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS 7).
In one embodiment, the centralized controller establishes a BGP FlowSpec neighbor relation with the network routing equipment, and the centralized controller sends first FlowSpec routing information to the network routing equipment; wherein, the information carried by the first FlowSpec routing information comprises: the flow matching information used for matching with the destination IP address, the flow specification queue field corresponding to the main queue and the extended community attribute value, wherein the extended community attribute value is the first speed limit bandwidth.
The centralized controller sends second FlowSpec routing information to the network routing equipment; wherein, the information carried by the second FlowSpec routing information comprises: the flow matching information used for matching with the source IP address or DSCP value, the flow specification queue field corresponding to the subqueue and the extended community attribute value, the extended community attribute value is the second speed limit bandwidth, the bandwidth guarantee value or the queue type.
A routing controller of the network routing equipment carries out flow scheduling operation based on the instruction set; and if the extended community attribute value corresponding to the sub-queue is the second speed limit bandwidth, the routing controller controls the sum of the bandwidths of the sub-queues to be less than or equal to the first speed limit bandwidth of the main queue.
In one embodiment, a centralized controller establishes BGP FlowSpec neighbors with a network core/aggregation device. For the primary queue: and the centralized controller issues a newly defined FlowSpec route to the neighbor for matching a source or destination IP address, and the newly defined FlowSpec route simultaneously carries the attribute of an extended group to limit the flow rate of the main queue. For the sub-queue: and the centralized controller issues a newly defined FlowSpec route to the neighbor for matching a DSCP value or a user part IP address, and the newly defined FlowSpec route simultaneously carries an extended group attribute for carrying out sub-queue flow rate limit, minimum bandwidth guarantee or congestion control.
BGP FlowSpec flow classification definition and processing based on the service flow main/sub queue: the main queue matches the user's total traffic, may be based on source or destination IP address matching (and may also be based on any combination of FlowSpec 12 tuples), and performs rate-limit. The sub-queue matches the user partial traffic scheduling, can perform recognition matching classification based on the DSCP value or the partial IP address of the user, and can perform the following actions: minimum bandwidth guarantee, congestion control, rate-limit.
Hierarchical QoS scheduling aiming at the flows is completed through the FlowSpec and the centralized controller, the routing controller analyzes a hierarchical QOS processing instruction issued by the centralized controller, corresponding flow processing operation is completed, and the scheduling condition of corresponding QOS main and sub queue parameters is described.
As shown in fig. 3, provider edge PE1 needs to access customer premises equipment CPE1, CPE2 and CPE 3. The centralized controller establishes a BGP FlowSpec neighbor relationship with PE 1. The centralized controller issues FlowSpec routing information (main queue) to PE1 according to requirements, the FlowSpec routing information respectively matches destination addresses of CPE1, CPE2 and CPE3, meanwhile, the type of the FlowSpec routing information carrying the extended community attribute is 0X8006, the main queue bandwidth speed limiting action is executed, and the speed limiting bandwidth is X at most.
The centralized controller issues the FlowSpec routing information (sub-queues) to the PE1 again according to the requirement, the FlowSpec routing information matches the source IP address (or DSCP value, etc.) respectively, and meanwhile, the type of the FlowSpec routing information carrying the extended community attribute is 0x8006, performs sub-queue traffic speed limiting (or minimum bandwidth guarantee, congestion control, etc.), and sets the highest bandwidth of the speed limiting of the multiple sub-queues to Y1, Y2, Y3 …, etc., respectively.
After PE1 receives the FlowSpec route sent by the centralized controller, the router traffic management chip (routing controller) in PE1 executes a corresponding instruction set according to the route content, and completes the corresponding traffic operation: the sum of the sub-queue bandwidths is less than or equal to the speed limit bandwidth of the main queue, namely Y1+ Y2+ Y3+ … < ═ X.
In the service flow scheduling method in the prior art, the flow is classified by means of simple flow classification or complex flow classification, the classified flow is associated with certain flow control or resource allocation action by equipment, service is provided differently, and finally a defined HQoS strategy is applied to a specific interface to achieve the purpose of flow regulation; the information for controlling the flow filtration and the routing information for forwarding the flow are mixed together, the maintenance work difficulty is high, the flow filtration strategy is frequently required to be manually modified, the strategy can be effective only by being applied to a specific interface, and certain limitations are realized.
According to the service flow scheduling method, the BGP FlowSpec TLV field and the extended community value are newly added, hierarchical classification is carried out on flow according to the FlowSpec 12 tuple, and flow actions are defined through the extended community value, so that the purpose of flow regulation and control is achieved; the BGP network layer reachable information type is used for transmitting the flow filtering information, and the routing information and the flow filtering information exist independently and have good maintainability. And abundant filtering conditions and processing actions are provided, and the flow can be controlled more pertinently.
In one embodiment, there is provided a centralized controller 40 according to the present disclosure, including: an information configuration module 41, a route generation module 42 and a route transmission module 43. The information configuration module 41 configures a flow specification queue field based on the main queue or sub-queue information of the traffic flow and sets an extended community attribute value according to an execution action corresponding to the main queue or sub-queue. The route generation module 42 generates FlowSpec routing information and adds flow matching information, flow specification queue fields, and extended community attribute values to the FlowSpec routing information. The routing sending module 43 sends the FlowSpec routing information to the network routing device, so that the routing controller of the network routing device performs flow regulation and control processing according to the FlowSpec routing information.
In one embodiment, the route sending module 43 establishes a BGP FlowSpec neighbor relationship with the network routing device, and sends the first FlowSpec routing information to the network routing device; wherein, the information carried by the first FlowSpec routing information comprises: the flow matching information used for matching with the destination IP address, the flow specification queue field corresponding to the main queue and the extended community attribute value, wherein the extended community attribute value is the first speed limit bandwidth.
The route sending module 43 sends the second FlowSpec route information to the network routing device; wherein, the information carried by the second FlowSpec routing information comprises: the flow matching information used for matching with the source IP address or the DSCP value, the flow specification queue field corresponding to the subqueue and the extended community attribute value, wherein the extended community attribute value is the second speed limit bandwidth, the bandwidth guarantee value or the queue type.
A routing controller of the network routing equipment carries out flow scheduling operation based on the instruction set; if the extended community attribute value corresponding to the sub-queue is the second speed-limiting bandwidth, the routing controller controls the sum of the bandwidths of the sub-queues to be less than or equal to the first speed-limiting bandwidth of the main queue.
Fig. 5 is a block schematic diagram of yet another embodiment of a centralized controller according to the present disclosure. As shown in fig. 5, the apparatus may include a memory 51, a processor 52, a communication interface 53, and a bus 54. The memory 51 is used for storing instructions, the processor 52 is coupled to the memory 51, and the processor 52 is configured to implement the traffic flow scheduling method described above based on the instructions stored in the memory 51.
The memory 51 may be a high-speed RAM memory, a non-volatile memory (non-volatile memory), or the like, and the memory 51 may be a memory array. The storage 51 may also be partitioned and the blocks may be combined into virtual volumes according to certain rules. Processor 52 may be a central processing unit CPU, or an application Specific Integrated circuit asic, or one or more Integrated circuits configured to implement the traffic scheduling methods of the present disclosure.
In one embodiment, the present disclosure provides a computer-readable storage medium storing computer instructions that, when executed by a processor, implement a method as in any one of the above embodiments.
In the service flow scheduling method, the centralized controller and the storage medium in the embodiments, by expanding the field of the BGP FlowSpec protocol and adding an action corresponding to an extended community value, the centralized controller can complete hierarchical QoS scheduling for a flow, and the practicability is higher; the BGP network layer reachable information type is used for transmitting the flow filtering information, and the routing information and the flow filtering information exist independently, so that the maintainability is good; and abundant filtering conditions and processing actions are provided, and the flow can be controlled more pertinently.
The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.
The description of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to practitioners skilled in this art. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.
Claims (16)
1. A method for scheduling service flow comprises the following steps:
the method comprises the steps that a centralized controller configures a flow specification queue field based on main queue or sub-queue information of a service flow, and an extended community attribute value is set according to an execution action corresponding to a main queue or a sub-queue;
the centralized controller generates FlowSpec routing information, and adds flow matching information, the flow specification queue field and the extended community attribute value in the FlowSpec routing information;
and the centralized controller sends the FlowSpec routing information to network routing equipment so that a routing controller of the network routing equipment performs flow regulation and control treatment according to the FlowSpec routing information.
2. The method of claim 1, wherein,
the information carried by the flow specification queue field includes: queue type information and queue ID information;
the queue type information is used for representing that the queue is a main queue or a sub-queue, and the main queue and the sub-queue bound by the main queue have the same queue ID information.
3. The method of claim 2, wherein the performing act comprises: minimum bandwidth guarantee and congestion management;
under the condition that the execution action represented by the type of the extended community attribute is minimum bandwidth guarantee, the extended community attribute value is a bandwidth guarantee value;
and in the case that the execution action characterized by the type of the extended community attribute is congestion management, the extended community attribute value is a queue type.
4. The method of claim 2 or 3, wherein the performing act further comprises: limiting the bandwidth;
and under the condition that the execution action represented by the type of the extended community attribute is bandwidth speed limit, the value of the extended community attribute is the speed limit bandwidth.
5. The method of claim 4, further comprising:
the centralized controller establishes a BGP FlowSpec neighbor relation with the network routing equipment;
the centralized controller sends first FlowSpec routing information to the network routing equipment;
wherein the information carried by the first FlowSpec routing information comprises: the flow matching information used for matching with the destination IP address, the flow specification queue field corresponding to the main queue and the extended community attribute value, wherein the extended community attribute value is the first speed limit bandwidth.
6. The method of claim 5, further comprising:
the centralized controller sends second FlowSpec routing information to the network routing equipment;
wherein the information carried by the second FlowSpec routing information comprises: the flow matching information used for matching with the source IP address or DSCP value, the flow specification queue field corresponding to the subqueue and the extended community attribute value, the extended community attribute value is the second speed limit bandwidth, the bandwidth guarantee value or the queue type.
7. The method of claim 6, wherein,
the routing controller of the network routing equipment carries out flow scheduling operation based on an instruction set;
and if the extended community attribute value corresponding to the sub-queue is the second speed limit bandwidth, the routing controller controls the sum of the bandwidths of the sub-queues to be less than or equal to the first speed limit bandwidth of the main queue.
8. A centralized controller, comprising:
the information configuration module is used for configuring a flow specification queue field based on the information of a main queue or a sub-queue of service flow and setting an extended community attribute value according to an execution action corresponding to the main queue or the sub-queue;
the route generation module is used for generating FlowSpec route information and adding flow matching information, the flow specification queue field and the extended community attribute value into the FlowSpec route information;
and the routing sending module is used for sending the FlowSpec routing information to network routing equipment so that a routing controller of the network routing equipment performs flow regulation and control treatment according to the FlowSpec routing information.
9. The centralized controller of claim 8, wherein,
the information carried by the flow specification queue field includes: queue type information and queue ID information;
the queue type information is used for representing that the queue is a main queue or a sub-queue, and the main queue and the sub-queue bound by the main queue have the same queue ID information.
10. The centralized controller of claim 9, wherein the performing act comprises: minimum bandwidth guarantee and congestion management;
under the condition that the execution action represented by the type of the extended community attribute is minimum bandwidth guarantee, the extended community attribute value is a bandwidth guarantee value;
and in the case that the execution action characterized by the type of the extended community attribute is congestion management, the extended community attribute value is a queue type.
11. The centralized controller of claim 9 or 10, wherein the performing act further comprises: limiting the bandwidth;
and under the condition that the execution action represented by the type of the extended community attribute is bandwidth speed limit, the value of the extended community attribute is the speed limit bandwidth.
12. The centralized controller of claim 11, wherein,
the route sending module is used for establishing a BGP FlowSpec neighbor relation with the network routing equipment and sending first FlowSpec route information to the network routing equipment;
wherein the information carried by the first FlowSpec routing information comprises: the flow matching information used for matching with the destination IP address, the flow specification queue field corresponding to the main queue and the extended community attribute value, wherein the extended community attribute value is the first speed limit bandwidth.
13. The centralized controller of claim 12, wherein,
the routing sending module is used for sending second FlowSpec routing information to the network routing equipment; wherein the information carried by the second FlowSpec routing information includes: the flow matching information used for matching with the source IP address or the DSCP value, the flow specification queue field corresponding to the subqueue and the extended community attribute value, wherein the extended community attribute value is the second speed limit bandwidth, the bandwidth guarantee value or the queue type.
14. The centralized controller of claim 13, wherein,
the routing controller of the network routing equipment carries out flow scheduling operation based on an instruction set; and if the extended community attribute value corresponding to the sub-queue is the second speed limit bandwidth, the routing controller controls the sum of the bandwidths of the sub-queues to be less than or equal to the first speed limit bandwidth of the main queue.
15. A centralized controller, comprising:
a memory; and a processor coupled to the memory, the processor configured to perform the method of any of claims 1-7 based on instructions stored in the memory.
16. A computer-readable storage medium having stored thereon computer instructions for execution by a processor of the method of any one of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110216640.6A CN115051951B (en) | 2021-02-26 | 2021-02-26 | Service flow scheduling method, centralized controller and storage medium |
| PCT/CN2021/133449 WO2022179224A1 (en) | 2021-02-26 | 2021-11-26 | Service flow scheduling method, centralized controller and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110216640.6A CN115051951B (en) | 2021-02-26 | 2021-02-26 | Service flow scheduling method, centralized controller and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115051951A true CN115051951A (en) | 2022-09-13 |
| CN115051951B CN115051951B (en) | 2024-04-19 |
Family
ID=83047774
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110216640.6A Active CN115051951B (en) | 2021-02-26 | 2021-02-26 | Service flow scheduling method, centralized controller and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN115051951B (en) |
| WO (1) | WO2022179224A1 (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106921572A (en) * | 2015-12-24 | 2017-07-04 | 华为技术有限公司 | A kind of method, apparatus and system for propagating qos policy |
| CN107222449A (en) * | 2016-03-21 | 2017-09-29 | 华为技术有限公司 | Communication means, equipment and system based on the regular agreement of stream |
| US20180191515A1 (en) * | 2016-12-30 | 2018-07-05 | Juniper Networks, Inc. | Multicast flow prioritization |
| CN108270690A (en) * | 2016-12-30 | 2018-07-10 | 北京华为数字技术有限公司 | The method and apparatus for controlling message flow |
-
2021
- 2021-02-26 CN CN202110216640.6A patent/CN115051951B/en active Active
- 2021-11-26 WO PCT/CN2021/133449 patent/WO2022179224A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106921572A (en) * | 2015-12-24 | 2017-07-04 | 华为技术有限公司 | A kind of method, apparatus and system for propagating qos policy |
| CN107222449A (en) * | 2016-03-21 | 2017-09-29 | 华为技术有限公司 | Communication means, equipment and system based on the regular agreement of stream |
| US20180191515A1 (en) * | 2016-12-30 | 2018-07-05 | Juniper Networks, Inc. | Multicast flow prioritization |
| CN108270690A (en) * | 2016-12-30 | 2018-07-10 | 北京华为数字技术有限公司 | The method and apparatus for controlling message flow |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115051951B (en) | 2024-04-19 |
| WO2022179224A1 (en) | 2022-09-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6466976B1 (en) | System and method for providing desired service policies to subscribers accessing the internet | |
| US7639674B2 (en) | Internal load balancing in a data switch using distributed network processing | |
| US7327675B1 (en) | Fairness of capacity allocation for an MPLS-based VPN | |
| EP1739914B1 (en) | Method, apparatus, edge router and system for providing a guarantee of the quality of service (qos) | |
| US6973102B2 (en) | Jitter reduction in differentiated services (DiffServ) networks | |
| CN108880904B (en) | 64-level service quality guarantee method with user and service attribute fusion | |
| JP2001358772A (en) | Random early demotion and promotion marker | |
| CN101127691A (en) | A method for implementing stream-based policy routing on network processor | |
| US6839327B1 (en) | Method and apparatus for maintaining consistent per-hop forwarding behavior in a network using network-wide per-hop behavior definitions | |
| CA2317460C (en) | Providing desired service policies to subscribers accessing internet | |
| Ghanwani et al. | A framework for integrated services over shared and switched IEEE 802 LAN technologies | |
| WO2023279818A1 (en) | Deterministic flow forwarding method and apparatus, storage medium and electronic apparatus | |
| CN115051951B (en) | Service flow scheduling method, centralized controller and storage medium | |
| Cisco | Quality of Service Solutions Configuration Guide Cisco IOS Release 12.0 | |
| Cisco | Configuring Quality of Service | |
| Cisco | QC: Quality of Service Overview | |
| Cisco | Cisco IOS Quality of Service Solutions Configuration Guide Release 12.1 | |
| Cisco | Maintaining SNA Response Times | |
| JP2002305538A (en) | Communication quality control method, server and network system | |
| Wood et al. | Network quality of service for the enterprise: A broad overview | |
| Kushwaha et al. | IPv6 flow-label based application aware routing in SDNs | |
| WO2024139547A1 (en) | Path finding method, packet transmission method, device, and medium | |
| CN113079111B (en) | Device and method for rate management and bandwidth control | |
| Cisco Systems, Inc | Cisco IOS 12.0 Quality of Service | |
| Smith et al. | Internet Engineering Task Force Anoop Ghanwani INTERNET DRAFT J. Wayne Pace Vijay Srinivasan (IBM) |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |