CN111917664A - A queue management method and system - Google Patents

Abstract

The invention discloses a queue management method and system. The method includes: classifying packets entering the layer 2 network to generate different types of packets; wherein, the different types of packets include unicast packets , multicast messages and broadcast messages; set up different message queues for different types of messages in the Layer 2 network; store the different types of messages in the different message queues respectively; Different types of messages are preprocessed to generate preprocessed messages; the preprocessed messages are scheduled out of the queue according to the priority of the message and the preset weight value. By preprocessing the packets in different packet queues, the method ensures that different types of packets do not affect each other, effectively manages unicast, multicast and broadcast in the case of congestion, and effectively utilizes two The broadband on the layer network can avoid unnecessary waste of broadband, relieve network congestion, and improve the utilization of broadband.

Description

A queue management method and system

technical field

The invention relates to the technical field of QoS guarantee, in particular to a queue management method and system.

Background technique

With the development of Internet technology, various computer application systems such as e-mail, web surfing, ERP system, VoIP video conferencing have also been rapidly developed and widely used, with powerful service performance and continuously improved desktop computer processing capabilities. The demand for network bandwidth for applications is also increasing. Due to the lack of effective bandwidth management methods, various computer applications preempt broadband resources disorderly, so that some key applications on the network cannot run normally, resulting in a reduction in the efficiency of the entire network and even network congestion.

At present, in the process of computer data communication, when there is no network congestion, the packet arrives at the interface and is sent out immediately. When the speed of the packet arrival exceeds the speed at which the interface sends packets, the network congestion occurs on the interface, and the network congestion is managed. The method is to use queuing technology, that is, to classify packets, send them to different queues, and perform queue scheduling on different queues to relieve network congestion.

However, using the queuing technology needs to continuously increase the network bandwidth to meet the bandwidth requirements of various applications. The broadband upgrade measures that cost a lot of money often bring little effect, because only the network bandwidth is increased without effective management and management. As a result, it still cannot ensure which key applications the newly increased broadband resources are allocated to, and cannot provide effective QoS guarantee for the network.

Therefore, how to alleviate the network congestion, effectively manage the network bandwidth, and improve the utilization rate of the bandwidth is an urgent problem to be solved by those skilled in the art.

SUMMARY OF THE INVENTION

In view of the above problems, the purpose of the present invention is to solve the problem that only increasing the network bandwidth can not ensure which key applications the newly increased broadband resources are allocated to, and cannot provide effective QoS guarantee for the network, and the bandwidth utilization rate is low.

An embodiment of the present invention provides a queue management method, including:

classifying the packets entering the Layer 2 network according to the packet types, where the packet types include unicast packets, multicast packets and broadcast packets;

Different message queues are set for different types of messages in the Layer 2 network, and the messages are respectively stored in the message queues of the corresponding message types;

Counting the number of various types of messages stored in the different message queues, and comparing the accumulated value of the number of the various types of messages with the maximum number of messages stored, when the accumulated value of the number is greater than the maximum number of messages When storing the number, buffer the various types of messages that are out of the queue, and count the numbers of the various types of messages that are out of the queue;

Feedback on the number of the various types of packets that are sent out of the queue, and adjust the token issuing cycle according to the number of the various types of packets fed back;

Allocate the tokens to the various types of messages correspondingly based on the adjusted token issuance cycle;

respectively perform queue-level scheduling on the multicast message and the broadcast message according to the tokens allocated for the multicast message and the broadcast message;

According to the priority of the corresponding packet queue and the preset weight value, various types of packets are scheduled out of the queue.

In one embodiment, the message queue includes: a unicast queue, a multicast queue, and a broadcast queue;

The unicast queue includes a unicast high priority queue and a unicast low priority queue;

The multicast queue includes a multicast high-priority front-level queue, a multicast high-priority rear-level queue, a multicast low-priority front-level queue, and a multicast low-priority rear-level queue;

The broadcast queue includes a broadcast high-priority pre-queue, a broadcast high-priority post-queue, a broadcast low-priority pre-queue, and a broadcast low-priority post-queue.

In one embodiment, the storing of the different types of packets in the different packet queues includes:

respectively judge the priority of the unicast message, the multicast message and the broadcast message;

If the unicast packet has a high priority, store the high-priority unicast packet in the unicast high-priority queue; otherwise, store the low-priority unicast packet in the unicast low-priority queue ;

If the multicast packet has a high priority, the high-priority multicast packet is stored in the multicast high-priority front-level queue; otherwise, the low-priority multicast packet is stored in the group broadcast low-priority front-end queue;

If the broadcast message has a high priority, the high-priority broadcast message is stored in the broadcast high-priority front-level queue; otherwise, the low-priority broadcast message is stored in the broadcast low-priority front-level queue. queue.

In an embodiment, the performing queue-level scheduling on the multicast packet and the broadcast packet according to the tokens allocated for the multicast packet and the broadcast packet, respectively, includes:

respectively comparing the surplus quantity of tokens allocated to the high-priority multicast message and the high-priority broadcast message with the token surplus back pressure value;

If the surplus quantity of tokens in the high-priority multicast packet and the high-priority broadcast packet is larger than the token surplus backpressure value, respectively, increase the low-priority multicast packet and the low-priority multicast packet. The number of tokens of the priority broadcast message;

comparing the surplus number of tokens of the low-priority multicast message with the length of the first multicast message in the multicast low-priority front-level queue;

If the surplus number of tokens of the low-priority multicast packet is greater than the length of the first multicast packet in the multicast low-priority preceding queue, the low-priority multicast packet stored in the multicast low-priority rear-level queue;

comparing the surplus number of tokens of the low-priority broadcast message with the length of the first broadcast message in the broadcast low-priority front-level queue;

If the surplus number of tokens of the low-priority broadcast message is greater than the length of the first broadcast message in the broadcast low-priority preceding queue, the low-priority broadcast message is stored in the Broadcast low-priority back-level queues.

In one embodiment, the performing queue-level scheduling on the multicast packet and the broadcast packet according to the tokens allocated for the multicast packet and the broadcast packet, further includes:

If the surplus quantity of tokens in the high-priority multicast packet and the high-priority broadcast packet is smaller than the token surplus backpressure value, respectively increase the high-priority multicast packet and the high-priority broadcast packet. The number of tokens of the priority broadcast message;

comparing the surplus number of tokens of the high-priority multicast message with the length of the first multicast message in the multicast high-priority front-level queue;

If the surplus number of tokens of the high-priority multicast packet is greater than the length of the first multicast packet in the preceding queue of the multicast high-priority packet, the high-priority multicast packet Dequeue from the multicast high-priority front-level queue and enter the multicast high-priority rear-level queue;

comparing the surplus number of tokens of the high-priority broadcast message with the length of the first broadcast message in the broadcast high-priority front-level queue;

If the surplus number of tokens of the high-priority broadcast packet is greater than the length of the first broadcast packet in the broadcast high-priority preceding queue, the high-priority broadcast packet is removed from the broadcast packet. The high-priority front-level queue is dequeued and enters the broadcast high-priority rear-level queue.

In a second aspect, the present invention also provides a queue management system, comprising:

a classification module, configured to classify the packets entering the Layer 2 network according to the packet types, where the packet types include unicast packets, multicast packets and broadcast packets;

a storage module, configured to set different message queues for different types of messages in the Layer 2 network, and store the messages in message queues of corresponding message types respectively;

A comparison module, configured to count the number of various types of messages stored in the different message queues, and compare the accumulated value of the number of the various types of messages with the maximum number of stored messages, when the accumulated value of the number is greater than When the maximum number of messages is stored, buffering the various types of messages out of the queue, and counts the numbers of the various types of messages out of the queue;

an allocation module, configured to feed back the number of the various types of messages that are sent out of the queue, and adjust the token issuing cycle according to the number of the various types of messages fed back;

a queue-level scheduling module, configured to perform queue-level scheduling on the multicast message and the broadcast message respectively according to the tokens allocated for the multicast message and the broadcast message;

The out-queue scheduling module is used for out-queue scheduling of various types of messages according to the priority of the corresponding message queue and the preset weight value.

In one embodiment, the message queue in the storage module includes: a unicast queue, a multicast queue and a broadcast queue;

The unicast queue includes a unicast high priority queue and a unicast low priority queue;

The multicast queue includes a multicast high-priority front-level queue, a multicast high-priority rear-level queue, a multicast low-priority front-level queue, and a multicast low-priority rear-level queue;

The broadcast queue includes a broadcast high-priority pre-queue, a broadcast high-priority post-queue, a broadcast low-priority pre-queue, and a broadcast low-priority post-queue.

In one embodiment, the storage module includes:

a priority judging unit, configured to judge the priorities of the unicast message, the multicast message and the broadcast message respectively;

The unicast message storage unit is used to store the high-priority unicast message in the unicast high-priority queue if the unicast message is high-priority; otherwise, store the low-priority unicast message in the unicast high-priority queue. the unicast low priority queue;

A multicast message storage unit, configured to store the high-priority multicast message in the multicast high-priority front-level queue if the multicast message is of high priority, otherwise, store the low-priority multicast message The multicast message is stored in the multicast low-priority front-end queue;

A broadcast message storage unit, configured to store the high-priority broadcast message in the broadcast high-priority front-level queue if the broadcast message is of high priority, and otherwise, store the low-priority broadcast message to the broadcast low-priority front-end queue.

In one embodiment, the queue-level scheduling module includes:

a high-priority comparison unit, configured to respectively compare the surplus quantity of tokens allocated to the high-priority multicast message and the high-priority broadcast message with the token surplus back pressure value;

A low-priority token adding unit, configured to increase the low-priority token if the surplus quantity of tokens of the high-priority multicast packet and the high-priority broadcast packet is greater than the token surplus back pressure value, respectively. the number of tokens of the priority multicast message and the low-priority broadcast message;

A low-priority multicast comparison unit, configured to compare the surplus number of tokens of the low-priority multicast packet with the length of the first multicast packet in the multicast low-priority front-level queue ;

A low-priority multicast message storage unit, used for if the surplus number of tokens of the low-priority multicast message is greater than the length of the first multicast message in the multicast low-priority preceding queue , the low-priority multicast message is stored in the multicast low-priority rear-level queue;

a low-priority broadcast comparison unit, configured to compare the surplus number of tokens of the low-priority broadcast message with the length of the first broadcast message in the broadcast low-priority front-level queue;

The low-priority broadcast message storage unit is used to store the token value of the low-priority broadcast message if the surplus quantity of the token of the low-priority broadcast message is greater than the length of the first broadcast message in the broadcast low-priority front-level queue. The low-priority broadcast message is stored in the broadcast low-priority post-level queue.

In one embodiment, the queue-level scheduling module further includes:

A high-priority token adding unit, configured to increase the high-priority multicast packet and the high-priority broadcast packet respectively if the surplus quantity of tokens of the high-priority broadcast packet is smaller than the token surplus back pressure value, respectively. the number of tokens of the priority multicast message and the high-priority broadcast message;

A high-priority multicast comparison unit, configured to compare the surplus number of tokens of the high-priority multicast message with the length of the first multicast message in the multicast high-priority front-level queue ;

The high-priority multicast packet dequeue unit is used if the surplus number of tokens of the high-priority multicast packet is greater than the first multicast packet in the multicast high-priority front-level queue. length, the high-priority multicast message is dequeued from the multicast high-priority front-level queue and enters the multicast high-priority rear-level queue;

a high-priority broadcast comparison unit, configured to compare the surplus number of tokens of the high-priority broadcast message with the length of the first broadcast message in the broadcast high-priority front-level queue;

The high-priority broadcast message dequeuing unit is used to send the high-priority broadcast message to the queue if the surplus number of tokens of the high-priority broadcast message is greater than the length of the first broadcast message in the broadcast high-priority front-level queue. The high-priority broadcast packet is dequeued from the broadcast high-priority pre-queue and enters the broadcast high-priority post-queue.

The beneficial effects of the above technical solutions provided by the embodiments of the present invention include at least:

A queue management method provided by an embodiment of the present invention ensures that different types of packets do not affect each other by preprocessing packets in different packet queues, and in the case of congestion, unicast, The effective management of multicast and broadcast effectively utilizes the bandwidth on the Layer 2 network, avoids unnecessary bandwidth waste, eases network congestion, improves bandwidth utilization, and enables various types of packets to be processed under congestion. The global mastery ensures the correctness of QoS.

Other features and advantages of the present invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description, claims, and drawings.

The technical solutions of the present invention will be described in further detail below through the accompanying drawings and embodiments.

Description of drawings

The accompanying drawings are used to provide a further understanding of the present invention, and constitute a part of the specification, and are used to explain the present invention together with the embodiments of the present invention, and do not constitute a limitation to the present invention. In the attached image:

1 is a flowchart of a queue management method provided by an embodiment of the present invention;

FIG. 2 is a flowchart of step S102 provided by an embodiment of the present invention;

FIG. 3 is a flowchart of scheduling processing of the multicast packet provided by an embodiment of the present invention;

4 is a flowchart of scheduling processing of the broadcast message provided by an embodiment of the present invention;

FIG. 5 is a block diagram of a queue management system according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be more thoroughly understood, and will fully convey the scope of the present disclosure to those skilled in the art.

Referring to FIG. 1, a queue management method provided by an embodiment of the present invention includes: steps S101-S107;

S101. Classify packets entering the Layer 2 network according to packet types, where the packet types include unicast packets, multicast packets, and broadcast packets;

Specifically, the classification is performed according to the MAC addresses corresponding to the packets in the Layer 2 network.

S102, setting different message queues for different types of messages in the Layer 2 network, and storing the messages in message queues of corresponding message types respectively;

Specifically, the above-mentioned different message queues include: unicast queues, multicast queues, and broadcast queues;

The unicast queue includes a unicast high priority queue and a unicast low priority queue;

The multicast queue includes a multicast high-priority front-level queue, a multicast high-priority rear-level queue, a multicast low-priority front-level queue, and a multicast low-priority rear-level queue;

The broadcast queue includes a broadcast high-priority pre-queue, a broadcast high-priority post-queue, a broadcast low-priority pre-queue, and a broadcast low-priority post-queue.

S103. Count the number of various types of messages stored in the different message queues, and compare the accumulated value of the number of the various types of messages with the maximum number of stored messages, and when the accumulated value of the number is greater than the maximum number of messages When the number of messages is stored, buffering the various types of messages exiting the queue, and counting the numbers of the various types of messages exiting the queue.

Specifically, the above-mentioned types of messages refer to: unicast messages, multicast messages, and broadcast messages.

Further, when the cumulative value of the number of the various types of messages is less than the preset number of backpressure values, the token is issued according to the default issuing cycle.

Further, the above token is a special frame that can control the station to occupy the media, so as to distinguish the data frame from other control frames.

Further, when various types of packets are queued and entered, the accumulated value of the number of various types of packets will change. It can be set that when the accumulated value of the number of various types of packets is updated once, the accumulated value of the number will be compared once. and the maximum message storage capacity.

S104. Feedback on the quantity of the various types of packets that are out of the queue, and adjust the token issuing cycle according to the feedback quantity of the various types of packets.

Specifically, compare the packet lengths of the various types of packets out of the queue with the token size, and when the size of the outgoing packets is less than the size of one token, record the packet length and wait for subsequent All kinds of messages out of the queue will be fed back until the message length is enough for one token. The main control chip will issue a token every time it receives a token message.

S105. Based on the adjusted issuance period of the token, allocate the token to the various types of messages accordingly.

S106. Perform queue-level scheduling on the multicast packet and the broadcast packet respectively according to the tokens allocated for the multicast packet and the broadcast packet.

Specifically, the above token controls the out-queue scheduling of various types of packets through the token bucket algorithm. The above token bucket control mechanism indicates when traffic can be sent based on whether there is a token in the token bucket. Each token in the token represents a byte. If there is a token in the token bucket, traffic is allowed to be sent; if there is no token in the token bucket, traffic is not allowed.

Further, when there are packets and tokens in the high-priority pre-queue of multicast packets and the high-priority pre-queue of broadcast packets, the multicast packets and broadcast packets are put into the multicast packet high-priority queue. Priority post queue and broadcast message high-priority post-queue, otherwise, continue to temporarily store in high-priority pre-queue. Similarly, multicast packet low-priority pre-queue and broadcast message low-priority pre-queue Various types of packets in the level queue are scheduled according to the above method.

Among them, if there is a packet in the previous-level queue, it means that there is a packet that can be dequeued, but it is uncertain whether the packet is dequeued from the previous-level queue under the control of the token. Therefore, by judging whether there is a packet in the previous-level queue. and whether the packet is controlled by the token to achieve the purpose of speed limiting, and restricting the storage of the packet to the post-level queue for out-queue scheduling will cause congestion and affect the QoS effect.

S107. Perform out-queue scheduling on the various types of packets according to the priority of the corresponding packet queue and the preset weight value.

Specifically, the order of the above preset weight values from high to low is: unicast packets, multicast packets, and broadcast packets;

Further, scheduling the unicast message out of the queue is prioritized, wherein first, the high-priority unicast message in the above-mentioned unicast high-priority queue is scheduled, and then the low-priority unicast message in the unicast low-priority queue is scheduled;

Further, secondly, schedule the multicast packets out of the queue, wherein firstly schedule the high-priority multicast packets in the above-mentioned multicast high-priority queues, (for high-priority multicast packets, schedule multicast high-priority packets first. The high-priority multicast packets in the pre-priority queue, then the high-priority multicast packets in the high-priority post-queue, and then the low-priority group in the multicast low-priority queue. Broadcast packets (for low-priority multicast packets, the low-priority multicast packets in the low-priority front-level queue are scheduled first, and then the low-priority multicast packets in the low-priority rear-level queue are scheduled to be multicast. message);

Further, the broadcast message is finally scheduled to go out of the queue, wherein the high-priority broadcast message in the above-mentioned broadcast high-priority queue is first scheduled, (for high-priority broadcast messages, the broadcast high-priority front-level queue is preferentially scheduled. The high-priority broadcast packets in the high-priority queue are scheduled to broadcast secondly), and then the low-priority broadcast packets in the low-priority queue are scheduled to broadcast (for low-priority broadcast packets) The priority is to schedule and broadcast the low-priority broadcast packets in the low-priority front-level queue, and then schedule and broadcast the low-priority broadcast packets in the low-priority rear-level queue);

Further, if it is found that there is no message in the above-mentioned message queue, skip the queue and only need to transmit the message in the next message queue according to the above-mentioned order.

In this embodiment, by feeding back the outgoing packets, the token issuing cycle is adjusted, and when the number of backpressure is exceeded, the token issuing speed can be reduced, which reduces the burst of traffic and the impact on the traffic. The impact of packet buffering can cause packets to be sent out at a uniform speed. And by preprocessing the packets in different packet queues, it ensures that different types of packets do not affect each other, effectively manages unicast, multicast and broadcast in the case of congestion, and effectively utilizes Layer 2 The broadband on the network avoids unnecessary waste of bandwidth, relieves network congestion, improves the utilization rate of broadband, realizes the global control of various types of packets in the case of congestion, and ensures the correctness of QoS.

In one embodiment, referring to FIG. 2 , the storing of the different types of messages in the different message queues in the foregoing step S102 includes:

S1021. Judge the priorities of the unicast packet, the multicast packet and the broadcast packet respectively;

Specifically, according to the unicast message, the multicast message and the broadcast message, the priority is judged according to different requirements of the message; for example, the message that needs urgent transmission and has strong delay is set to high Priority, set the low priority for the packets with low transmission requirements and low latency.

S1022. If the unicast packet has a high priority, store the high-priority unicast packet in the unicast high-priority queue; otherwise, store the low-priority unicast packet in the unicast low-priority queue level queue;

S1023. If the multicast packet has a high priority, store the high-priority multicast packet in the multicast high-priority front-level queue; otherwise, store the low-priority multicast packet in the high-priority multicast packet. The multicast low-priority front-end queue described above;

S1024. If the broadcast message has a high priority, store the high-priority broadcast message in the broadcast high-priority front-level queue; otherwise, store the low-priority broadcast message in the broadcast low-priority queue front-end queue.

In one embodiment, referring to FIGS. 3-4 , in the foregoing step S106, the multicast packet and the broadcast packet are respectively evaluated according to the tokens allocated for the multicast packet and the broadcast packet. Packets are scheduled at the queue level, including:

The surplus quantity of tokens allocated to the high-priority multicast message and the high-priority broadcast message is compared with the token surplus back pressure value, respectively.

Specifically, the above-mentioned surplus quantity of tokens refers to the current quantity of tokens.

If the surplus quantity of tokens in the high-priority multicast packet and the high-priority broadcast packet is larger than the token surplus backpressure value, respectively, increase the low-priority multicast packet and the low-priority multicast packet. Number of tokens for priority broadcast packets.

The surplus number of tokens of the low-priority multicast packet is compared with the length of the first multicast packet in the multicast low-priority front-level queue.

If the surplus number of tokens of the low-priority multicast packet is greater than the length of the first multicast packet in the multicast low-priority preceding queue, the low-priority multicast packet is stored in the multicast low-priority rear-level queue;

Further, if the surplus number of tokens of the low-priority multicast packet is less than the length of the first multicast packet in the multicast low-priority preceding queue, the low-priority multicast The message is still stored in the multicast low-priority front-level queue.

The surplus number of tokens of the low-priority broadcast message is compared with the length of the first broadcast message in the broadcast low-priority preceding queue.

If the surplus number of tokens of the low-priority broadcast message is greater than the length of the first broadcast message in the broadcast low-priority preceding queue, the low-priority broadcast message is stored in the Broadcast low-priority rear-level queues;

Further, if the surplus number of tokens of the low-priority broadcast message is less than the length of the first broadcast message in the broadcast low-priority front-level queue, the low-priority broadcast message is still stored. The broadcast low-priority front-level queue.

In this embodiment, if there is a packet in the previous-level queue, it means that there is a dequeued packet, but it is uncertain whether the packet can be dequeued from the previous-level queue under the control of the token. Compare the surplus number of the previous-level queue with the length of the first broadcast message in the front-level queue to determine whether the message in the front-level queue has a token, so as to achieve the purpose of speed limit, and limit the message to the back-level queue after passing through. Cause congestion and affect the effect of QoS.

In one embodiment, referring to FIGS. 3-4 , the above step S106 further includes:

If the surplus quantity of tokens in the high-priority multicast packet and the high-priority broadcast packet is smaller than the token surplus backpressure value, respectively increase the high-priority multicast packet and the high-priority broadcast packet. Number of tokens for priority broadcast packets.

Compare the surplus number of tokens of the high-priority multicast message with the length of the first multicast message in the multicast high-priority front-level queue.

If the surplus number of tokens of the high-priority multicast packet is greater than the length of the first multicast packet in the preceding queue of the multicast high-priority packet, the high-priority multicast packet Dequeue from the multicast high-priority front-level queue and enter the multicast high-priority rear-level queue;

Further, if the surplus number of tokens of the high-priority multicast packet is less than the length of the first multicast packet in the high-priority pre-multicast queue, the high-priority multicast The message is still stored in the multicast high-priority front-level queue.

Compare the surplus number of tokens of the high-priority broadcast message with the length of the first broadcast message in the broadcast high-priority preceding queue.

If the surplus number of tokens of the high-priority broadcast packet is greater than the length of the first broadcast packet in the broadcast high-priority preceding queue, the high-priority broadcast packet is removed from the broadcast packet. The high-priority front-level queue is dequeued and enters the broadcast high-priority rear-level queue;

Further, if the surplus number of tokens of the high-priority broadcast message is less than the length of the first broadcast message in the broadcast high-priority front-level queue, the high-priority broadcast message is still stored. to the broadcast high-priority front-level queue.

In this implementation, through the scheduling processing of multicast packets and broadcast packets, that is, the number of token surpluses of multicast packets and broadcast packets and the value of token surplus back pressure are compared and determined, so as to achieve the purpose of speed limit. , that is, restricting the shortcoming of congesting the corresponding packet queue after passing the packet and affecting the communication effect, alleviating the network congestion and ensuring the QoS effect.

Based on the same inventive concept, an embodiment of the present invention also provides a queue management system. Since the principle of the problem solved by the device is similar to that of the aforementioned queue management method, the implementation of the device can refer to the implementation of the aforementioned method, and the repetitions are repeated. No longer.

A queue management system provided by an embodiment of the present invention, as shown in FIG. 5 , includes:

The classification module 51 is configured to classify the packets entering the Layer 2 network according to the packet types, where the packet types include unicast packets, multicast packets and broadcast packets;

Specifically, the classification is performed according to the MAC addresses corresponding to the packets in the Layer 2 network.

The storage module 52 is configured to set different message queues for different types of messages in the Layer 2 network, and store the messages in message queues of corresponding message types respectively.

The comparison module 53 is configured to count the number of various types of messages stored in the different message queues, and compare the accumulated value of the number of the various types of messages with the maximum number of stored messages. When the accumulated value of the number is When it is greater than the maximum number of messages stored, buffering the various types of messages out of the queue, and count the numbers of the various types of messages out of the queue;

Specifically, the above-mentioned types of messages refer to: unicast messages, multicast messages, and broadcast messages.

Further, when the cumulative value of the number of the various types of messages is less than the preset number of backpressure values, the token is issued according to the default issuing cycle;

Further, specifically, the above token may be in the form of a token, that is, a special frame that can control the station to occupy the media, so as to distinguish the data frame from other control frames.

The feedback module 54 is used for the feedback module, and is used for feeding back the quantity of the various types of messages that are out of the queue, and adjusting the token issuing cycle according to the feedback quantity of the various types of messages.

The allocation module 55 is configured to allocate the tokens to the various types of messages correspondingly based on the adjusted issuance period of the tokens.

The queue-level scheduling module 56 is configured to perform queue-level scheduling on the multicast packet and the broadcast packet according to the tokens allocated for the multicast packet and the broadcast packet, respectively.

The out-queue scheduling module 57 is configured to perform out-queue scheduling for various types of messages according to the priority of the corresponding message queue and the preset weight value;

Specifically, the order of the above preset weight values from high to low is: unicast packets, multicast packets, and broadcast packets;

Further, scheduling the unicast message out of the queue is prioritized, wherein first, the high-priority unicast message in the above-mentioned unicast high-priority queue is scheduled, and then the low-priority unicast message in the unicast low-priority queue is scheduled;

Further, secondly, schedule the multicast packets out of the queue, wherein firstly schedule the high-priority multicast packets in the above-mentioned multicast high-priority queues, (for high-priority multicast packets, schedule multicast high-priority packets first. The high-priority multicast packets in the pre-priority queue, then the high-priority multicast packets in the high-priority post-queue, and then the low-priority group in the multicast low-priority queue. Broadcast packets (for low-priority multicast packets, the low-priority multicast packets in the low-priority front-level queue are scheduled first, and then the low-priority multicast packets in the low-priority rear-level queue are scheduled to be multicast. message);

Further, the broadcast message is finally scheduled out of the queue, wherein the high-priority broadcast message in the above-mentioned broadcast high-priority queue is first scheduled, (for the high-priority broadcast message, the broadcast high-priority front-level queue is preferentially scheduled. The high-priority broadcast packets in the high-priority queue are scheduled to broadcast secondly), and then the low-priority broadcast packets in the low-priority queue are scheduled to broadcast (for low-priority broadcast packets) The priority is to schedule and broadcast the low-priority broadcast packets in the low-priority front-level queue, and then schedule and broadcast the low-priority broadcast packets in the low-priority rear-level queue);

Further, if it is found that there is no message in the above-mentioned message queue, skip the queue and only need to transmit the message in the next message queue according to the above-mentioned order.

In one embodiment, the different message queues in the storage module 52 include: a unicast queue, a multicast queue, and a broadcast queue;

The unicast queue includes a unicast high priority queue and a unicast low priority queue;

The multicast queue includes a multicast high-priority front-level queue, a multicast high-priority rear-level queue, a multicast low-priority front-level queue, and a multicast low-priority rear-level queue;

The broadcast queue includes a broadcast high-priority pre-queue, a broadcast high-priority post-queue, a broadcast low-priority pre-queue, and a broadcast low-priority post-queue.

In one embodiment, the storage module 52 includes:

a priority judging unit 521, configured to judge the priorities of the unicast message, the multicast message and the broadcast message respectively;

Specifically, the priority is determined according to the unicast packet, the multicast packet and the broadcast packet according to different requirements of the packets.

The unicast message storage unit 522 is configured to store the high-priority unicast message in the unicast high-priority queue if the unicast message is of high priority; otherwise, store the low-priority unicast message to the unicast low priority queue.

The multicast message storage unit 523 is configured to store the high-priority multicast message in the multicast high-priority front-level queue if the multicast message is of high priority, and otherwise, store the low-priority multicast message The first-level multicast packets are stored in the multicast low-priority front-level queue.

The broadcast message storage unit 524 is configured to store the high-priority broadcast message in the broadcast high-priority front-level queue if the broadcast message is of high priority; otherwise, store the low-priority broadcast message Stored in the broadcast low-priority front-end queue.

In one embodiment, the queue-level scheduling module 56 includes:

a high-priority comparison unit 561, configured to compare the surplus quantity of tokens allocated to the high-priority multicast message and the high-priority broadcast message with the token surplus back pressure value;

The low-priority token adding unit 562 is configured to increase the token surplus back pressure value of the high-priority multicast packet and the high-priority broadcast packet respectively if the surplus quantity of the token is greater than the token surplus backpressure value, respectively. the number of tokens of the low-priority multicast message and the low-priority broadcast message;

The low-priority multicast comparison unit 563 is configured to compare the surplus number of tokens of the low-priority multicast packet with the length of the first multicast packet in the multicast low-priority preceding queue. Compare;

The low-priority multicast message storage unit 564 is configured to, if the surplus number of tokens of the low-priority multicast message is greater than the first multicast message in the multicast low-priority front-level queue length, the low-priority multicast message is stored in the multicast low-priority rear-level queue;

a low-priority broadcast comparison unit 565, configured to compare the surplus number of tokens of the low-priority broadcast message with the length of the first broadcast message in the broadcast low-priority preceding queue;

The low-priority broadcast message storage unit 566 is configured to, if the surplus number of tokens of the low-priority broadcast message is greater than the length of the first broadcast message in the broadcast low-priority preceding queue, store the The low-priority broadcast message is stored in the broadcast low-priority post-level queue.

In one embodiment, the scheduling unit 56 further includes:

The high-priority token adding unit 567 is configured to increase the token surplus back pressure value of the high-priority multicast packet and the high-priority broadcast packet respectively if the surplus quantity of the tokens of the high-priority broadcast packet is smaller than the token surplus the number of tokens of the high-priority multicast message and the high-priority broadcast message;

The high-priority multicast comparison unit 568 is configured to compare the surplus number of tokens of the high-priority multicast packet and the length of the first multicast packet in the multicast high-priority front-level queue. Compare;

The high-priority multicast packet dequeue unit 569 is used for if the surplus number of tokens of the high-priority multicast packet is greater than the first multicast packet in the multicast high-priority front-level queue The length of the high-priority multicast message is dequeued from the multicast high-priority front-level queue and enters the multicast high-priority rear-level queue;

a high-priority broadcast comparison unit 570, configured to compare the surplus number of tokens of the high-priority broadcast message with the length of the first broadcast message in the broadcast high-priority preceding queue;

The high-priority broadcast message dequeue unit 571 is configured to, if the surplus number of tokens of the high-priority broadcast message is greater than the length of the first broadcast message in the broadcast high-priority front-level queue, then Dequeue the high-priority broadcast message from the broadcast high-priority pre-queue and enter the broadcast high-priority post-queue.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present invention without departing from the spirit and scope of the invention. Thus, provided that these modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include these modifications and variations.

Claims (10)

1. A method of queue management, comprising:

classifying messages entering a two-layer network according to message types, wherein the message types comprise unicast messages, multicast messages and broadcast messages;

setting different message queues aiming at different types of messages in a two-layer network, and respectively storing the messages into the message queues of corresponding message types;

counting the number of various messages stored in the different message queues, comparing the accumulated value of the number of various messages with the maximum message storage number, when the accumulated value of the number is greater than the maximum message storage number, buffering various messages which are out of the queues, and counting the number of various messages which are out of the queues;

feeding back the number of the various messages of the queue, and adjusting the issuing period of the token according to the number of the various messages fed back;

correspondingly distributing the tokens to the various messages based on the adjusted issuing period of the tokens;

respectively carrying out queue level scheduling on the multicast message and the broadcast message according to the tokens distributed to the multicast message and the broadcast message;

and performing dequeue scheduling on the various messages according to the priority of the corresponding message queue and the preset weight value.

2. The system of claim 1, wherein the message queue comprises: a unicast queue, a multicast queue and a broadcast queue;

the unicast queues comprise a unicast high-priority queue and a unicast low-priority queue;

the multicast queues comprise a multicast high-priority preceding queue, a multicast high-priority subsequent queue, a multicast low-priority preceding queue and a multicast low-priority subsequent queue;

the broadcast queues include a broadcast high priority pre-queue, a broadcast high priority post-queue, a broadcast low priority pre-queue, and a broadcast low priority post-queue.

3. The method of claim 2, wherein the storing the different types of packets into the different packet queues respectively comprises:

judging the priority of the unicast message, the multicast message and the broadcast message respectively;

if the unicast message is of high priority, storing the unicast message of high priority into the unicast high priority queue, otherwise, storing the unicast message of low priority into the unicast low priority queue;

if the multicast message is of high priority, storing the multicast message of high priority to the preceding queue of high priority of multicast, otherwise, storing the multicast message of low priority to the preceding queue of low priority of multicast;

if the broadcast message is of high priority, storing the broadcast message of high priority to the pre-queue of high priority of broadcast, otherwise, storing the broadcast message of low priority to the pre-queue of low priority of broadcast.

4. The method of claim 1, wherein the performing queue level scheduling for the multicast packets and the broadcast packets according to the tokens allocated for the multicast packets and the broadcast packets, respectively, comprises:

respectively comparing the surplus quantity of the tokens distributed to the high-priority multicast message and the high-priority broadcast message with the surplus token backpressure value;

if the surplus number of the tokens of the high-priority multicast message and the high-priority broadcast message is respectively greater than the surplus counter-pressure value of the tokens, respectively increasing the token number of the low-priority multicast message and the token number of the low-priority broadcast message;

comparing the surplus number of the tokens of the low-priority multicast message with the length of the first multicast message in the multicast low-priority preceding-stage queue;

if the surplus number of the tokens of the low-priority multicast message is larger than the length of the first multicast message in the multicast low-priority preceding-stage queue, storing the low-priority multicast message to the multicast low-priority subsequent-stage queue;

comparing the surplus number of tokens of the low-priority broadcast message with the length of the first broadcast message in the broadcast low-priority pre-stage queue;

and if the surplus number of the tokens of the low-priority broadcast message is greater than the length of the first broadcast message in the broadcast low-priority front-stage queue, storing the low-priority broadcast message to the broadcast low-priority rear-stage queue.

5. The method of claim 4, wherein the performing queue level scheduling on the multicast packets and the broadcast packets according to the tokens allocated to the multicast packets and the broadcast packets, respectively, further comprises:

if the surplus number of the tokens of the high-priority multicast message and the high-priority broadcast message is respectively smaller than the surplus counter-pressure value of the tokens, respectively increasing the token number of the high-priority multicast message and the high-priority broadcast message;

comparing the surplus number of the tokens of the high-priority multicast message with the length of the first multicast message in the multicast high-priority preceding-stage queue;

if the surplus number of the tokens of the high-priority multicast message is larger than the length of the first multicast message in the multicast high-priority preceding queue, dequeuing the high-priority multicast message from the multicast high-priority preceding queue and entering the multicast high-priority subsequent queue;

comparing the surplus number of the tokens of the high-priority broadcast message with the length of the first broadcast message in the broadcast high-priority pre-stage queue;

and if the surplus number of the tokens of the high-priority broadcast message is greater than the length of the first broadcast message in the broadcast high-priority preceding-stage queue, dequeuing the high-priority broadcast message from the broadcast high-priority preceding-stage queue and entering the broadcast high-priority subsequent-stage queue.

6. A queue management system, comprising:

the classification module is used for classifying the messages entering the two-layer network according to message types, wherein the message types comprise unicast messages, multicast messages and broadcast messages;

the storage module is used for setting different message queues aiming at different types of messages in the two-layer network and respectively storing the messages into the message queues of corresponding message types;

the comparison module is used for counting the number of various messages stored in the different message queues, comparing the accumulated value of the number of various messages with the maximum message storage number, buffering various messages going out of the queues when the accumulated value of the number is greater than the maximum message storage number, and counting the number of various messages going out of the queues;

the feedback module is used for feeding back the number of the various messages out of the queue and adjusting the issuing period of the token according to the number of the various messages fed back;

the distribution module is used for correspondingly distributing the tokens to the various messages based on the adjusted issuing period of the tokens;

a queue level scheduling module, configured to perform queue level scheduling on the multicast packet and the broadcast packet according to the tokens allocated to the multicast packet and the broadcast packet;

and the dequeue scheduling module is used for dequeuing and scheduling various messages according to the priority of the corresponding message queue and the preset weight value.

7. The system of claim 6, wherein the message queue in the storage module comprises: a unicast queue, a multicast queue and a broadcast queue;

the unicast queues comprise a unicast high-priority queue and a unicast low-priority queue;

the multicast queues comprise a multicast high-priority preceding queue, a multicast high-priority subsequent queue, a multicast low-priority preceding queue and a multicast low-priority subsequent queue;

the broadcast queues include a broadcast high priority pre-queue, a broadcast high priority post-queue, a broadcast low priority pre-queue, and a broadcast low priority post-queue.

8. The system of claim 7, wherein the storage module comprises:

a priority judging unit, configured to respectively judge priorities of the unicast packet, the multicast packet, and the broadcast packet;

a unicast message storage unit, configured to store a high-priority unicast message to the unicast high-priority queue if the unicast message is of a high priority, and store a low-priority unicast message to the unicast low-priority queue if the unicast message is of a low priority;

a multicast message storage unit, configured to store a high-priority multicast message to the multicast high-priority pre-stage queue if the multicast message is of a high priority, and store a low-priority multicast message to the multicast low-priority pre-stage queue if the multicast message is of a low priority;

and the broadcast message storage unit is used for storing the broadcast message with high priority to the broadcast high-priority pre-queue if the broadcast message is with high priority, and storing the broadcast message with low priority to the broadcast low-priority pre-queue if the broadcast message is with high priority.

9. The system of claim 6, wherein the queue level scheduling module comprises:

a high-priority comparison unit, configured to compare the surplus number of tokens allocated to the high-priority multicast packet and the high-priority broadcast packet with a token surplus backpressure value;

a low-priority token increasing unit, configured to increase the token numbers of the low-priority multicast packet and the low-priority broadcast packet, if the surplus numbers of the tokens of the high-priority multicast packet and the high-priority broadcast packet are respectively greater than a token surplus counter-pressure value;

a low priority multicast comparing unit, configured to compare the surplus number of tokens of the low priority multicast packet with the length of the first multicast packet in the multicast low priority pre-stage queue;

a low-priority multicast message storage unit, configured to store the low-priority multicast message to the multicast low-priority post-queue if the surplus number of tokens of the low-priority multicast message is greater than the length of the first multicast message in the multicast low-priority pre-queue;

a low priority broadcast comparing unit, configured to compare the surplus number of tokens of the low priority broadcast packet with the length of the first broadcast packet in the broadcast low priority pre-stage queue;

a low-priority broadcast packet storage unit, configured to store the low-priority broadcast packet in the broadcast low-priority back-stage queue if the surplus number of tokens of the low-priority broadcast packet is greater than the length of the first broadcast packet in the broadcast low-priority front-stage queue.

10. The system of claim 9, wherein the queue level scheduling module further comprises:

a high-priority token increasing unit, configured to increase the number of tokens of the high-priority multicast packet and the high-priority broadcast packet, if the surplus number of tokens of the high-priority multicast packet and the high-priority broadcast packet is smaller than a token surplus counter-pressure value, respectively;

a high-priority multicast comparing unit, configured to compare the surplus number of tokens of the high-priority multicast packet with the length of the first multicast packet in the multicast high-priority pre-stage queue;

a high-priority multicast message dequeuing unit, configured to dequeue the high-priority multicast message from the multicast high-priority pre-stage queue and enter the multicast high-priority post-stage queue if the surplus number of tokens of the high-priority multicast message is greater than the length of the first multicast message in the multicast high-priority pre-stage queue;

a high-priority broadcast comparing unit, configured to compare the surplus number of tokens of the high-priority broadcast packet with the length of the first broadcast packet in the broadcast high-priority pre-stage queue;

a high-priority broadcast message dequeuing unit, configured to dequeue the high-priority broadcast message from the broadcast high-priority pre-queue and enter the broadcast high-priority post-queue if the surplus number of tokens of the high-priority broadcast message is greater than the length of the first broadcast message in the broadcast high-priority pre-queue.

Images