WO2012116540A1 - Procédé de gestion de trafic et dispositif de gestion - Google Patents

Procédé de gestion de trafic et dispositif de gestion Download PDF

Info

Publication number
WO2012116540A1
WO2012116540A1 PCT/CN2011/079173 CN2011079173W WO2012116540A1 WO 2012116540 A1 WO2012116540 A1 WO 2012116540A1 CN 2011079173 W CN2011079173 W CN 2011079173W WO 2012116540 A1 WO2012116540 A1 WO 2012116540A1
Authority
WO
WIPO (PCT)
Prior art keywords
token
scheduled
board
tokens
queue
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.)
Ceased
Application number
PCT/CN2011/079173
Other languages
English (en)
Chinese (zh)
Inventor
卢胜文
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2012116540A1 publication Critical patent/WO2012116540A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

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/50—Queue scheduling
    • H04L47/52—Queue scheduling by attributing bandwidth to queues
    • H04L47/527—Quantum based scheduling, e.g. credit or deficit based scheduling or token bank

Definitions

  • the present invention relates to the field of communications, and more particularly to a method and a management apparatus for traffic management in the field of communications. Background technique
  • IP Internet Protocol
  • data services gradually replaced traditional voice services, and gradually became the main body of communication services.
  • traffic management needs to be performed on network devices (Traffic Management,
  • a service board is a board in a network device. Each board can perform various types of service processing, such as data stream access, forwarding, multiplexing, routing, labeling, flow control, traffic shaping, and so on. Multi-level traffic management enables the traffic to pass through the board in a single-level management manner, which meets the requirements of the total output of the board.
  • traffic management can only be performed independently within each board. For example, in order to control the ingress traffic of a card, you can perform traffic management on the data stream input from the inbound interface of the card, discard excessive packets, prevent impact on the device, affect device performance, and perform traffic management on the ingress traffic. After that, the business process of the business board is performed. In order to control the egress traffic of the service board, traffic management is performed after the service processing of the service board. In this case, the data stream after the service processing needs to be cached before traffic management can be performed, so a large amount of storage space is consumed.
  • traffic management independently within each board cannot meet the needs of traffic management. For example, when traffic of the same service enters a network device from different inbound interfaces and enters different boards, or when the same service When the traffic is distributed to the boards that are output from different outbound interfaces, the traffic that is originally associated with traffic management is no longer able to manage traffic. The management of the boards can be performed separately. The traffic of the service output from the network device does not meet predetermined requirements such as bandwidth and delay requirements, which affects the effectiveness of traffic management. Summary of the invention
  • the embodiment of the invention provides a method and a management device for the traffic management, which can solve the problem that the data traffic distributed to multiple boards cannot be uniformly managed, so that the data streams distributed to different boards can be effectively managed to meet the requirements of traffic management.
  • the embodiment of the present invention provides a method for traffic management, including: receiving a notification of a request token sent by at least two boards, the number of tokens requested by each board, and the to-be-scheduled message in the board.
  • the number of packets to be transmitted in the queue corresponds to each other; according to the number of requested tokens, the packets to be scheduled are transmitted.
  • an embodiment of the present invention provides a management apparatus for traffic management, including: a receiving module, configured to receive a notification of a request token sent by at least two boards, and the number of tokens requested by each board is An allocation module is configured to allocate a token to the to-be-scheduled message queue according to the number of requested tokens, so that the card root is according to the present invention.
  • the management device allocates the token according to the notification of the plurality of board request tokens, so as to control the packet transmission of the board through the allocation of the token, so that the traffic in the board that is originally independent of the traffic management is performed.
  • Unified, centralized scheduling can be achieved, unlike the prior art, the traffic in each board is managed separately, independently, and isolated. Therefore, the centralized traffic management performed by the management device can uniformly and effectively manage data streams that may be associated with each other on different boards, thereby satisfying the requirements of traffic management.
  • FIG. 1 is a flow chart showing a method of traffic management according to an embodiment of the present invention
  • FIG. 2 is a flow chart showing another method of traffic management according to an embodiment of the present invention
  • FIG. 3 is a schematic diagram showing an example of traffic management according to an embodiment of the present invention
  • FIG. 4 is a schematic diagram of a board using a method of traffic management according to an embodiment of the present invention
  • FIG. 5 is a schematic diagram showing another example of traffic management according to an embodiment of the present invention
  • FIG. 7 is a block diagram showing the structure of another management apparatus for traffic management according to an embodiment of the present invention.
  • the method 100 includes: in S110, receiving a notification of a request token sent by at least two boards, and the number of tokens requested by each board and the queue to be scheduled in the board need to be transmitted.
  • the token is allocated to the to-be-scheduled message queue according to the number of the requested tokens, so that the board transmits the packet in the message queue to be scheduled according to the allocated token.
  • a management device that performs centralized traffic management on at least two boards receives notifications from the boards.
  • the card requests a token from the management device by using the notification.
  • the number of the requested tokens can correspond to the number of packets to be transmitted in the queue to be scheduled in the card.
  • the management device allocates a token to the queue to be scheduled in the board according to the number of tokens requested by the board. After receiving the token, the board transmits the packet in the queue to be scheduled according to the token assigned by the management device.
  • the management device allocates a token according to the notification of the plurality of board request tokens, so as to control the transmission of the packet by using the token allocation, so that the traffic management is originally performed independently.
  • the traffic in the board can be uniformly and centralizedly scheduled. Unlike the prior art, the traffic in each board is managed separately, independently, and isolated. Therefore, by using centralized traffic management, data flows that may be associated with each other on different boards can be managed uniformly and efficiently, thereby meeting the requirements of traffic management.
  • S110 and S120 according to an embodiment of the present invention will be specifically described.
  • the notification of the request token sent by the at least two boards is received, and the number of tokens requested by each board corresponds to the number of packets to be transmitted in the queue of the to-be-scheduled message in the board.
  • the management device manages at least two boards and performs centralized unified scheduling of traffic in at least two boards.
  • the board can cache the packets to be transmitted in different queues to be scheduled according to a predetermined policy, for example, based on the packet type, the user who sent the packet, the destination address of the packet, and the output port of the packet.
  • the packet to be transmitted may be a packet received from another board or a packet generated by the board itself.
  • the board can cache the packet according to the type of the packet, and store the packet carrying the voice information in the queue of the message to be scheduled dedicated to the voice information, and store the message carrying the video information in the video dedicated to the video.
  • the message queue to be scheduled is medium.
  • the number of the requested tokens can be represented by the number of packets to be transmitted, the number of bytes of the packets, the number of packets, or the increment of the number of bytes in the queue.
  • the number of tokens requested by the notification is determined based on the packets to be transmitted in the queue to be scheduled, the number of tokens requested can be considered to correspond to the number of packets to be transmitted.
  • each report is assumed.
  • the packet has 100 bytes, and the board carries the first to-be-scheduled message queue with 300 bytes to be transmitted in the notification, and the second to-be-scheduled message queue has 500 bytes of information to be transmitted, to the management device.
  • Request a total of 800 tokens (assuming 1 token corresponds to 1 byte).
  • the number of 800 tokens requested corresponds to the number of packets to be transmitted in the queue of scheduled packets in the card.
  • the board in the S110 can be the service board of the network device. Those skilled in the art may think that the board in the S110 may also be other devices that may process data in the network device and transmit data in the future, and the traffic needs to be uniformly scheduled and managed.
  • the notification received by the management device from the board may be a notification that the board sends independently.
  • the notification may also be a notification that the management device itself determines based on the information carried by the traffic transmitted by the board.
  • the notification determined by the management device itself can also be regarded as a notification that the management device receives from the board, because this still needs to be determined by means of information from the board. For example, the management device determines that there are a large number of video packets that need to be transmitted on the board according to the traffic transmitted by the board, and the maximum size that the board is allowed to send according to the board. Bandwidth allocates tokens to the board.
  • a token is allocated to the to-be-scheduled message queue according to the number of the requested tokens, so that the board transmits the packet in the message queue to be scheduled according to the allocated token.
  • the management device allocates a token according to the number of tokens requested by the board. For example, based on the above example, the management device may allocate 300 tokens to the first to-be-scheduled message queue of the board, and allocate 500 tokens to the second to-be-scheduled message queue of the board.
  • the board transmits the packets in the queue to be scheduled according to the token allocated by the management device. For example, after the board acquisition management device allocates 300 tokens to the first to-be-scheduled message queue, the three packets in the first to-be-scheduled message queue are transmitted, and the acquisition management device allocates the second to-be-scheduled report. After the 500 tokens of the text queue, the five texts in the second queue of the scheduled message are transmitted.
  • the management device may assign a token to the queue of messages to be scheduled in the board based on a plurality of predetermined policies.
  • the predetermined policy can be set in the management device in advance, or can be dynamically adjusted according to the statistics of the data traffic in each board.
  • the traffic management policy known in the prior art may be used, or the traffic management policy may be adopted in the future, as long as it can send packets and send packets in different queues to be scheduled. Just wait for control.
  • the management device may assign a token to the queue to be scheduled based on the priority scheduling policy or the load balancing policy.
  • the management device schedules the packets according to the priority of the queues to be scheduled, so that the important packets are stored in the queue with the highest priority of the packets to be scheduled, and the packets are preferentially scheduled. For example, if a packet is cached according to the packet type, there is a voice to-be-scheduled message queue for storing voice packets, a video to-be-scheduled message queue for storing video packets, and data for storing data packets such as pictures, emails, and texts. Schedule message queues. The priorities of the voice to-be-scheduled message queue, the video to-be-scheduled message queue, and the data to-be-scheduled message queue are sequentially decreased.
  • the message When a message indicating that the message to be scheduled in the queue is to be transmitted, the message is preferentially assigned to the voice to-be-scheduled message queue. If there are remaining tokens, the message waiting to be transmitted in the queue to be scheduled is further satisfied. The packet finally meets the packet to be transmitted in the data queue to be scheduled.
  • the management device allocates a token to the to-be-scheduled message queue of the requesting token, so that the to-be-scheduled message queue can be uniformly scheduled, so that the traffic of each board can be uniformly balanced, and one board is avoided.
  • the traffic in the middle is always in a waiting state and the phenomenon of transmission is not obtained.
  • the management device determines that there are packets in the boards to be transmitted at a certain token allocation time, the tokens can be evenly distributed to the boards.
  • the traffic in the board can be treated equally.
  • the management device can allocate more tokens to the specific board when the traffic of other boards is balanced. More traffic can be transferred to avoid load buildup.
  • the management device may periodically assign a token to the message queue to be scheduled.
  • the number of tokens requested by the board may not be met by the management device at one time.
  • the management device can only allocate a fixed number of tokens to a to-be-scheduled message queue in the board at a time, or the total number of tokens that can be allocated by the management device each time is less than the total number of tokens requested.
  • the management device may not be able to satisfy the number of tokens requested by the board at one time. In this way, the management device needs to periodically assign a token to the queue to be scheduled, and flexibly allocate the token by sending the token multiple times to satisfy the predetermined scheduling policy.
  • the time interval between periodically assigning tokens may be equal or unequal.
  • the first to-be-scheduled message queue requires 300 tokens as an example.
  • the management device may assign 300 tokens to the first to-be-scheduled message queue at a time, or may assign tokens to it multiple times periodically.
  • the token may be allocated in such a manner that 100 tokens are allocated each time, three times in total, or the available tokens may be allocated multiple times according to the current token usage until the demand of 300 tokens is satisfied.
  • those skilled in the art can also easily think of determining how to assign a token based on a predetermined policy, and if the token requirement cannot be met at one time, the token requirement is satisfied by multiple allocations.
  • the board may transmit the message in the message queue to be scheduled according to the allocated token based on the token bucket technology.
  • the board can store the token received from the management device in the token bucket.
  • each token in the token bucket can correspond to one byte, or multiple bytes, and can directly correspond to one packet. If there is a token in the token bucket, then Traffic is allowed to be sent, otherwise, traffic is not allowed to be sent. If the number of tokens in the token bucket satisfies the transmission of a complete packet, the packet is transmitted and the corresponding number of tokens are deleted. If the number of tokens in the token bucket is insufficient to satisfy a complete packet.
  • the tokens in the token bucket can also be the tokens shared by the queues to be scheduled.
  • the tokens are used according to the rules for using the tokens in the queues to be scheduled. For example, the voice to-be-scheduled message queue in the board preferentially uses the token. If there are remaining tokens in the token bucket, it is used by the video to-be-scheduled message queue, and then used by the data to-be-scheduled message queue.
  • the management device allocates the token according to the notification of the plurality of board request tokens, so as to control the packet transmission of the board through the allocation of the token, so that the traffic management is originally performed independently.
  • the traffic in the board can be uniformly and centralizedly scheduled. Unlike the prior art, the traffic in each board is managed separately, independently, and isolated. Therefore, by using centralized traffic management, it is possible to uniformly and effectively manage data flows that may be associated with each other on different boards, thereby meeting the needs of traffic management.
  • FIG. 2 a flow diagram of another method 200 of traffic management in accordance with an embodiment of the present invention is shown.
  • S210 and S220 in FIG. 2 are substantially the same as S110 and S120 in FIG. 1, and therefore will not be described again.
  • the method 200 may further include, after S220, S230, when the number of allocated tokens is equal to the number of requested tokens, stopping the allocation of the queues to be scheduled to be scheduled for the board in the management device.
  • Two counters are set for the queue to be scheduled. The first counter is used to record the number of tokens requested by the board for the queue of the message to be scheduled, and the other counter is used to record the number of tokens allocated by the management device to the queue of messages to be scheduled. When the count values of the two counters are equal, it indicates that the assigned token can satisfy the packet to be transmitted in the queue of the message to be scheduled, and therefore, the token is stopped.
  • the initial value of the counter is the number of tokens that the board requests for the queue of the message to be scheduled.
  • the counter is subtracted from the assigned number of tokens, when the management device When the board receives a new notification for the queue to be scheduled, it adds the counter to the requested number of tokens.
  • the counter's count value is zero, the assignment token is stopped.
  • the method 200 may further include S240 after S220. If the board determines that the number of assigned tokens is less than the requested number of tokens, the notification of the request token is sent again.
  • the board After the management device assigns a token to the queue to be scheduled in the board, the board needs to determine whether the token allocation is over. In the case that the management device receives the notification and performs the token allocation only once, if the board receives the token, it determines that the token allocation ends. If the board does not receive the token and waits for the token to expire, Determine the end of the token assignment. The management device may send the specific information to indicate the end of the token allocation when the management device receives the notification, and may periodically allocate the tokens multiple times. If the board receives the specific information, Then, it is determined that the token allocation ends. If the board does not receive the specific message and the time of waiting for the token expires, it is determined that the token allocation ends.
  • the board determines that the token allocation is over, if the number of tokens that the management device allocates to the board cannot be full, the number of tokens that are requested cannot be transmitted, and the board requests the management device again. Token.
  • the number of tokens that are requested at this time may be the number of tokens corresponding to the packet that has not been acquired by the previous one, or the number of tokens corresponding to the number of packets that need to be transmitted in the queue to be scheduled.
  • the message that needs to be transmitted currently includes the packet that has not yet obtained the token, and also includes the newly buffered packet that needs to be transmitted.
  • the board sends a notification again by actively discovering that the number of assigned tokens cannot satisfy the requested number of tokens, and can timely request re-scheduling of the unscheduled packets, and can also reduce errors caused by the token allocation process.
  • the packets scheduled to be scheduled are not scheduled in time, and thus have an impact on traffic management performance.
  • S240 is executed after S230 in Fig. 2, S240 may be executed before S230, and S230 and S240 may be simultaneously executed.
  • the traffic management method when the traffic of the same service enters the network device from different inbound interfaces and enters different boards, or when the traffic of the same service is distributed differently
  • centralized traffic management is performed by the management device, and unified traffic management can be performed on these originally associated data flows that are desired to be uniformly managed.
  • the board is managed separately. Therefore, the requirements of traffic management can be met, and the effectiveness of traffic management can be improved.
  • the traffic management can be performed on the board in the process of data processing (such as forwarding, labeling, etc.), and the packet buffer can be shared with the service processing of the board, and the packet is directly transmitted according to the token bucket technology. Therefore, it is no longer necessary to open up new storage space and then cache the message, thereby saving storage space and improving performance.
  • 3 and 5 respectively show schematic diagrams of examples of traffic management according to an embodiment of the present invention.
  • the management device 340 performs centralized traffic management of the traffic of the boards 310, 320, and 330.
  • Each board can have multiple queues to be scheduled and cache the corresponding packets in the queue to be scheduled.
  • the management device 340 records the scheduling characteristics of each queue to be scheduled to be scheduled, and the characteristics may include at least one of the following: scheduling priority, queue scheduling mode, number of packets owned by the queue, and traffic shaping of the total egress traffic of the queue. parameter.
  • the management device 340 can manage the queues of the to-be-scheduled messages to be scheduled in the boards 310, 320, and 330 according to the set. These to-be-scheduled message queues can be divided into different sets by a predetermined policy.
  • the voice to be scheduled packet queues of the buffered voice packets in the boards 310, 320, and 330 are divided into voice sets, and the video packets of the video packets are buffered in the boards 310, 320, and 330.
  • the scheduling message queue is divided into a video set, and the data to-be-scheduled message queues of the data packets such as pictures, mails, and texts in the boards 310, 320, and 330 are divided into data sets, and the like.
  • different sets may be scheduled according to a predetermined policy, for example, based on a priority scheduling policy or a load balancing policy, the voice to-be-scheduled message queues in the voice set are preferentially scheduled, or an equal order is assigned to each set. Cards are dispatched.
  • different queue scheduling and traffic shaping strategies can also be implemented independently. For example, for the voice collection, different queues of the to-be-scheduled message can be set according to the user, and the packets in the queue of the to-be-scheduled message of the specific user are preferentially scheduled.
  • different to-be-scheduled reports can be set according to the destination address. The text queue, and allocates a specific transmission bandwidth for the queue of messages to be scheduled for a specific destination address, and so on.
  • the packets are cached in the queues of the to-be-scheduled packets of the board.
  • the real-time queue-to-queue or egress scheduling is performed by the board.
  • the management device 340 manages and controls the packets to be scheduled. The scheduling of messages in the queue. Between the boards 310, 320, and 330 and the management device 340 Message links are connected, and messages are not transmitted by means of data packets.
  • the message link can require small delay and high link reliability, which enables fast and efficient centralized management.
  • the board can be configured with the to-be-scheduled message queues to be managed by the management device 340, and the set of the to-be-scheduled message queues to be centrally managed by the management device 340 can be configured to facilitate the management device 340 according to the predetermined policy. Perform centralized scheduling.
  • Each board can periodically notify the management device 340 of the number of bytes of the message to be transmitted in the respective queues to be scheduled.
  • the advertising unit can be advertised in bytes or in byte blocks (for example, 128 bytes is a byte block). Notifying the management device 340 of the number of bytes of text can be considered as requesting scheduling control from the management device 340.
  • the number of advertised message bytes is mainly used by the management device 340 to determine whether the queue of the message to be scheduled is empty and whether the token needs to be allocated, regardless of the number of specific tokens allocated each time.
  • the board can be advertised.
  • the board can advertise the number of packets to be transmitted in the queues of the packets to be scheduled at one time, or the number of packets to be transmitted in the queue of the packets to be scheduled.
  • the board can adjust the frequency of sending notifications according to the ratio of the number of bytes of packets in the queue to be scheduled that do not acquire tokens to the total number of bytes. The higher the ratio, the faster the transmission.
  • the management device 340 After receiving the notification sent by the board, the management device 340 allocates the token based on the number of tokens requested.
  • the management device 340 can control the number of messages to be transmitted by the board according to a predetermined policy by assigning tokens.
  • the number of tokens allocated by the management device 340 may be determined by an egress flow parameter of the set to which the to-be-scheduled message queue belongs (for example, a committed burst size CBS, an excess burst size EBS, a committed information rate CIR, a peak information rate PIR, etc.). determine.
  • the traffic shaping can be performed based on the token.
  • the token bucket technology can be used to schedule a packet that acquires a token from a token bucket to a subordinate queue or an egress.
  • the single board 400 may be any one of the boards 310, 320, and 330 of FIG.
  • the board 400 includes a queue management module 410, a to-be-scheduled message queue 420, a token bucket 430, and a lower-level queue or outlet 440.
  • the queue management module 410 can advertise the unscheduled message bytes to the management device to request the acquisition of a corresponding number of tokens and receive the token assigned by the management device. After receiving the token, the queue management module 410 also delivers the assigned token to the token bucket 430. When the token in the token bucket 430 is full, Discard the newly issued token. In addition, the queue management module 410 also manages the message queue 420 to be scheduled, in which the message to be transmitted is buffered. The packets buffered in the to-be-scheduled message queue 420 are sent to the lower-level queue or the egress 440 after the tokens in the token bucket 430 are acquired, and the corresponding number of tokens are deleted from the token bucket 430. The queue management module 410 controls the transmission of the packets in the to-be-scheduled message queue 420 based on the tokens in the token bucket 430, thereby completing traffic shaping in the board 400.
  • the board 310 has a queue A to be scheduled
  • the board 320 has a queue B to be scheduled
  • the board 330 has a queue to be scheduled (:. from A, B, and C)
  • the packets output by the inbound interface are respectively cached in the queues of the to-be-scheduled packets (called "queues") A, B, and C of the three access boards of the access device (that is, the example of the board).
  • the load balancing policy is scheduled in a polling manner.
  • the total number of bytes is 15000, and 30 packets are input from the access point C, and the total number of bytes is 20000.
  • the unit is allocated with 1000 bytes as the token, that is, one token is allocated corresponding to 1000 bytes.
  • the boards 310, 320, and 330 can advertise the number of message bytes waiting to be scheduled to the management device 340 in units of byte blocks. In this example, assuming that 1 byte block also has 1000 bytes, the boards 310, 320, and 330 respectively advertise to the management device 340 that the packets in the respective queues A, B, and C that do not acquire the token have 8 , 15 and 20 byte blocks. At this time, one byte block corresponds to one token allocation unit.
  • the management device 340 assigns a token to the eight queues of eight, B, and C at a rate of 5M total outlet bandwidth, and assumes that a total of 12 token blocks can be assigned a token within the time interval in which the token is allocated.
  • the management device 340 simulates three queues for polling scheduling, and assigns four tokens to each of the three queues A, B, and C. After obtaining four tokens, the three queues A, B, and C can respectively send 4000 bytes of packets.
  • the management device 340 On the second poll, the management device 340 still allocates four tokens to each of the three queues A, B, and C. After obtaining four tokens, the three queues A, B, and C respectively send 4,000-byte packets.
  • the A queue since the A queue has no packets to send, it is no longer assigned to the A queue. New token. At this point, there are 7 byte blocks in the B queue that need to be sent, and there are 12 byte blocks in the C queue that need to be sent.
  • the management device 340 allocates six tokens to the C queue based on the load balancing policy. In this way, the B and C queues can respectively send 6,000-byte packets.
  • the management device 340 receives the notifications from the boards 310, 320, and 330, the traffic in each board can be centrally managed, and the tokens are allocated multiple times based on the load balancing policy to meet the requirements of the traffic management, and the A is guaranteed.
  • the total bandwidth transmitted by the three queues, B, and C matches the scheduling bandwidth (ie, 5M) configured for the set to which the three queues belong.
  • FIG. 5 shows another example of traffic management in accordance with an embodiment of the present invention.
  • the notification sent by the board to the management device can carry the number of packets.
  • the token is assigned to the board that sent the notification independently and periodically.
  • the management device assigns a token to the board to carry the token allocation information by confirming the ACK message, and the ACK message can also respond to the receipt of the notification. If the board finds the loss of the ACK message (for example, timeout, error correction, etc.), it waits for the specific information indicating the end of the token allocation to be received, and then recalculates the report waiting to be transmitted in the queue of the to-be-scheduled message in the board. The number of texts, the notification of the request token is sent again.
  • the management device 520 that performs centralized traffic management sequentially receives notifications of sequence numbers 1, 2, and 3 from the board 510, and the notifications carry " ⁇ bytes increments of 2000, 500, and 500, respectively. 520 sends an ACK message in response to each sequence number to the board 510 multiple times according to the predetermined scheduling policy.
  • Each ACK message carries token allocation information indicating that 500 tokens are allocated (1 token corresponds to 1 byte).
  • the board 510 expires when the timer expires.
  • the loss of the ACK message is found, and continues to wait for the management device 520 to assign the token.
  • the ACK message 3 in response to the notification of sequence number 3 is correctly transmitted, and an ACK message 3 carrying the specific information indicating the end of the token allocation is transmitted.
  • the board 510 When receiving the ACK message with the specific information from the management device 520, the board 510 recalculates the number of bytes of the message waiting to be transmitted in the queue of the to-be-scheduled message of the board 510, and The number of bytes of the message is carried in the notification with sequence number 4 and sent to management device 520.
  • FIG. 6 shows a block diagram of a structure of a management apparatus 600 for traffic management according to an embodiment of the present invention.
  • the management device 600 includes a receiving module 610 and an allocation module 620.
  • the receiving module 610 is configured to receive the notification of the request token sent by the at least two boards, and the number of tokens requested by each board corresponds to the number of packets to be transmitted in the queue of the to-be-scheduled message in the board.
  • the allocating module 620 can be configured to allocate a token to the to-be-scheduled message queue according to the number of requested tokens, so that the board transmits the packet in the message queue to be scheduled according to the allocated token.
  • the management apparatus may allocate a token based on the notification of the plurality of board request tokens, so as to control the packet transmission of the board through the allocation of the token, so that the traffic in the board that originally performs traffic management independently Unified, centralized scheduling can be achieved, unlike the prior art, the traffic in each board is managed separately, independently, and isolated. Therefore, by using the management device for centralized traffic management, it is possible to uniformly and efficiently manage data streams that may be associated with each other on different boards, thereby satisfying the requirements of traffic management.
  • Fig. 7 is a block diagram showing the structure of a management apparatus 700 for traffic management according to an embodiment of the present invention.
  • the receiving module 710 and the assigning module 720 in the management device 700 are substantially the same as the receiving module 610 and the assigning module 620 in the managing device 600 of FIG.
  • the allocating module 720 can be configured to allocate a token to the to-be-scheduled message queue based on a priority scheduling policy or a load balancing policy.
  • the allocation module 720 can be configured to periodically assign tokens to the queue of messages to be scheduled.
  • Management device 700 may also include a stop module 730, in accordance with an embodiment of the present invention.
  • the stop module 730 can be configured to stop assigning tokens to the queue of pending messages when the number of assigned tokens is equal to the number of tokens requested.
  • the scheduling module performs the scheduling based on the priority scheduling policy, so that the important packets, that is, the packets stored in the queue with the highest priority, are preferentially scheduled.
  • the load balancing policy is used for scheduling, so that the queues of the packets to be scheduled can be uniformly scheduled, so that the traffic of each board can be uniformly balanced, and the traffic in one board is always in a waiting state and cannot be transmitted.
  • the token is periodically allocated by the distribution module, so that when the management device cannot satisfy the requested number of tokens at one time, the token can be flexibly allocated by sending the token multiple times to satisfy the predetermined scheduling policy. By stopping the module, it is possible to determine when to stop the assignment of the token.
  • RAM random access memory
  • ROM read only memory
  • EEPROM electrically programmable ROM
  • EEPROM electrically erasable programmable ROM
  • registers hard disk, removable disk, CD-ROM or technology Any other form of storage medium known.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Des modes de réalisation de l'invention portent sur un procédé de gestion de trafic et sur un dispositif de gestion. Le procédé comprend : la réception de notifications transmises par au moins deux cartes uniques demandant un jeton, le nombre de jetons correspondant au nombre de paquets demandant une transmission dans une file d'attente de paquets à programmer de la carte unique ; sur la base du nombre de jetons demandés, la distribution de jetons à la file d'attente de paquets à programmer, permettant ainsi à la carte unique de transmettre, sur la base du jeton distribué, les paquets dans la file d'attente de paquets à programmer. Le dispositif de gestion comprend un module de réception et un module de distribution. Dans le procédé et le dispositif de gestion fournis dans les modes de réalisation de la présente invention, par utilisation du dispositif de gestion pour centraliser une gestion de trafic, une programmation collective et centralisée est autorisée pour un trafic précédemment géré indépendamment de cartes uniques, permettant ainsi une gestion collective et efficace de flux de données ayant une possible association les uns avec les autres et distribués sur différentes cartes uniques, et satisfaisant les besoins de gestion de trafic.
PCT/CN2011/079173 2011-02-28 2011-08-31 Procédé de gestion de trafic et dispositif de gestion Ceased WO2012116540A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN 201110047631 CN102118314A (zh) 2011-02-28 2011-02-28 流量管理的方法和管理装置
CN201110047631.5 2011-02-28

Publications (1)

Publication Number Publication Date
WO2012116540A1 true WO2012116540A1 (fr) 2012-09-07

Family

ID=44216916

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/079173 Ceased WO2012116540A1 (fr) 2011-02-28 2011-08-31 Procédé de gestion de trafic et dispositif de gestion

Country Status (2)

Country Link
CN (1) CN102118314A (fr)
WO (1) WO2012116540A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110365580A (zh) * 2019-07-26 2019-10-22 新华三大数据技术有限公司 服务质量调度方法、装置、电子设备及计算机可读存储介质
CN116366564A (zh) * 2023-03-23 2023-06-30 苏州雄立科技有限公司 流量监管方法及其装置

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102118314A (zh) * 2011-02-28 2011-07-06 华为技术有限公司 流量管理的方法和管理装置
CN103581056A (zh) * 2013-10-25 2014-02-12 盛科网络（苏州）有限公司 网络通信中通过分层队列调度实现拥塞管理的方法
US9479610B2 (en) * 2014-04-14 2016-10-25 Microsoft Technology Licensing, Llc Battery efficient synchronization of communications using a token bucket
EP3429125A4 (fr) * 2016-04-06 2019-02-20 Huawei Technologies Co., Ltd. Procédé et appareil de régulation de trafic dans un réseau défini par un logiciel
CN108768873B (zh) * 2018-05-29 2021-09-28 腾讯科技（深圳）有限公司 一种流量控制方法及相关设备
CN109672627A (zh) * 2018-09-26 2019-04-23 深圳壹账通智能科技有限公司 基于集群服务器的业务处理方法、平台、设备及存储介质
CN112104568B (zh) * 2020-11-17 2021-07-23 北京达佳互联信息技术有限公司 一种数据传输控制方法及网关

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1646192A2 (fr) * 2000-03-22 2006-04-12 Fujitsu Ltd. Commutateur de paquets, dispositif de plannification, circuit de contrôle de renvoyement, circuit de contrôle multidestinataire et dispositif de contrôle de qualité de service
CN101272345A (zh) * 2008-04-29 2008-09-24 杭州华三通信技术有限公司 一种流量控制的方法、系统和装置
CN101282305A (zh) * 2008-05-22 2008-10-08 杭州华三通信技术有限公司 分布式系统中的带宽控制方法及业务板
CN101808037A (zh) * 2010-03-15 2010-08-18 中兴通讯股份有限公司 交换网中流量管理的方法和装置
CN102118314A (zh) * 2011-02-28 2011-07-06 华为技术有限公司 流量管理的方法和管理装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100466593C (zh) * 2003-01-13 2009-03-04 华为技术有限公司 一种支持多业务的综合队列调度的实现方法
DE10306293B4 (de) * 2003-02-14 2006-08-31 Siemens Ag Verfahren zur Übertragungsbandbreitenzuteilung in einer paketorientierten Kommunikationseinrichtung
CN101789895B (zh) * 2009-01-24 2012-12-12 华为技术有限公司 一种发送/接收数据报文的方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1646192A2 (fr) * 2000-03-22 2006-04-12 Fujitsu Ltd. Commutateur de paquets, dispositif de plannification, circuit de contrôle de renvoyement, circuit de contrôle multidestinataire et dispositif de contrôle de qualité de service
CN101272345A (zh) * 2008-04-29 2008-09-24 杭州华三通信技术有限公司 一种流量控制的方法、系统和装置
CN101282305A (zh) * 2008-05-22 2008-10-08 杭州华三通信技术有限公司 分布式系统中的带宽控制方法及业务板
CN101808037A (zh) * 2010-03-15 2010-08-18 中兴通讯股份有限公司 交换网中流量管理的方法和装置
CN102118314A (zh) * 2011-02-28 2011-07-06 华为技术有限公司 流量管理的方法和管理装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110365580A (zh) * 2019-07-26 2019-10-22 新华三大数据技术有限公司 服务质量调度方法、装置、电子设备及计算机可读存储介质
CN110365580B (zh) * 2019-07-26 2022-02-22 新华三大数据技术有限公司 服务质量调度方法、装置、电子设备及计算机可读存储介质
CN116366564A (zh) * 2023-03-23 2023-06-30 苏州雄立科技有限公司 流量监管方法及其装置

Also Published As

Publication number Publication date
CN102118314A (zh) 2011-07-06

Similar Documents

Publication Publication Date Title
WO2012116540A1 (fr) Procédé de gestion de trafic et dispositif de gestion
CN111201757B (zh) 在底层网络上动态配置的网络接入节点虚拟结构
US9800513B2 (en) Mapped FIFO buffering
JP5205519B2 (ja) 帯域幅割り当て方法及びルーティング装置
CN103379038B (zh) 一种流量调度的装置及方法
CN101127686B (zh) 一种网络数据处理方法及设备
CN112041826B (zh) 用于网络接口卡的细粒度业务整形分流
CN102223306B (zh) 一种报文传输方法及装置
CN101729386A (zh) 一种基于令牌调度的流量控制方法及装置
CN108984280B (zh) 一种片外存储器的管理方法和装置、计算机可读存储介质
CN109922003B (zh) 一种数据发送方法、系统及相关组件
CN105871751A (zh) 一种数据中心网络带宽保证方法及系统
CN111181873A (zh) 数据发送方法、装置、存储介质和电子设备
CN102957626B (zh) 一种报文转发方法和装置
CN111416776A (zh) 传输数据的方法和网络设备
CN113726690B (zh) 一种协议报文的上传方法、系统、电子设备及存储介质
CN102223311A (zh) 一种队列调度方法及装置
CN115695578A (zh) 一种数据中心网络tcp和rdma混合流调度方法、系统及装置
CN101789895A (zh) 一种发送/接收数据报文的方法及装置
CN102594654B (zh) 一种队列调度的方法和装置
WO2011113264A1 (fr) Procédé et appareil de gestion du trafic dans un réseau de commutation
US9083617B2 (en) Reducing latency of at least one stream that is associated with at least one bandwidth reservation
CN114666281A (zh) 基于智能网卡卸载的数据中心多应用QoS保障系统及方法
WO2021254475A1 (fr) Procédé et appareil de planification de file d'attente
CN103888366A (zh) 一种实时企业服务总线系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11859757

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11859757

Country of ref document: EP

Kind code of ref document: A1