[go: up one dir, main page]

WO2013000116A1 - 一种漏桶限速方法及装置 - Google Patents

一种漏桶限速方法及装置 Download PDF

Info

Publication number
WO2013000116A1
WO2013000116A1 PCT/CN2011/076465 CN2011076465W WO2013000116A1 WO 2013000116 A1 WO2013000116 A1 WO 2013000116A1 CN 2011076465 W CN2011076465 W CN 2011076465W WO 2013000116 A1 WO2013000116 A1 WO 2013000116A1
Authority
WO
WIPO (PCT)
Prior art keywords
bucket
sub
tokens
packet
leak
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/076465
Other languages
English (en)
French (fr)
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.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to EP11868792.0A priority Critical patent/EP2728812B1/en
Priority to PCT/CN2011/076465 priority patent/WO2013000116A1/zh
Priority to US14/127,862 priority patent/US9160669B2/en
Publication of WO2013000116A1 publication Critical patent/WO2013000116A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/215Flow control; Congestion control using token-bucket
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00Traffic control in data switching networks
    • H04L47/10Flow control; Congestion control
    • H04L47/21Flow control; Congestion control using leaky-bucket

Definitions

  • the present invention relates to the field of data networks, and in particular, to a method and an apparatus for speed limit of a leaky bucket. Background technique
  • the packet In existing data networks, network congestion is often caused by the burstiness of packet traffic. In order to avoid network congestion and improve the quality of service (QoS) of the data network, the packet needs to be rate-limited at the receiving end. If the rate of the packet is lower than the specified rate, the packet is received normally. If the rate exceeds the specified rate, the packet is discarded or the packet is marked.
  • QoS quality of service
  • the commonly used method is to use the leaky bucket to limit the rate of packets.
  • the commonly used standards based on the leaky bucket algorithm are RFC2697 and RFC2698, namely single-rate three-color double-barrel and dual-rate three-color double-barrel, RFC standard leaky bucket.
  • the speed limit principle is shown in Figure 1. Specifically, the token is continuously filled into the leaky bucket at a specified rate until the leaky bucket is full. When the packet arrives, the packet length of the packet is compared with the number of tokens in the leaky bucket. If there are enough tokens in the leaky bucket, the packet is allowed to pass, and the packet of the packet is subtracted from the leaky bucket. The number of tokens corresponding to the long one; if the tokens in the leaky bucket are not enough, the text will be discarded, or the text will be marked.
  • the main purpose of the present invention is to provide a method and a device for rate limiting of a leaky bucket, which can flexibly limit the rate of packets according to the weight priority, thereby improving the quality of the data network and the user.
  • a leaky bucket which can flexibly limit the rate of packets according to the weight priority, thereby improving the quality of the data network and the user.
  • a method for limiting the speed of a leaky bucket when a rate limit is set for a group of packets that share the same weighted priority, the total leaky bucket is divided into multiple sub-leak buckets according to the number of weight priorities and the proportional parameter.
  • the ratio parameter must be determined according to the requirement of the weight absorption jitter of each weight priority flow, and the capacity of each sub-leakage bucket is equal to the total leaky bucket capacity, and the packet weight priority corresponds to the sub-drain bucket weight priority.
  • the parameter related to the rate limit of the leaking bucket is obtained, and the related information of the packet includes at least: a packet length of the packet and a priority parameter of the packet;
  • the total number of tokens calculated is added to the total leaky bucket. If the total leaky bucket is full, the total number of tokens of the leaky bucket is the total leaky bucket capacity, otherwise the total number of tokens added is added; If the total leaky bucket is full, the weighted priority sub-leak buckets are full. Otherwise, the total number of tokens to be added is divided according to the proportional relationship of the weight priority factors, and the sub-leak buckets provided for each weight priority are added. Number of tokens;
  • the method further includes: updating a parameter related to the rate limit of the leaky bucket, including the number of tokens after each sub-leak rate limit.
  • the parameters related to the rate limit of the leaky bucket include: the capacity of the total leaky bucket, the weight priority factor, the total token addition rate, the time when the last speed limit occurs, and the total leaky bucket and the number of tokens in each sub-leak bucket.
  • the parameters related to the rate limit of the leaking bucket are: updating the current time when the last speed limit occurs as the current time, and updating the total leaked bucket and the number of tokens in each sub-leaked bucket as the number of tokens after the speed limit operation .
  • the parameter related to the speed limit of the leaky bucket further includes one or more of the following: a capacity of each sub-leaked bucket, a proportion of a sub-leaked bucket capacity, an allocation ratio parameter additionally set by an overflow operation, and a preset mutual overflow increment number.
  • the token that overflows the leaky bucket is allocated to the other sub-leak buckets by the overflow operation: the overflow token is allocated to other sub-subjects according to the weight priority factor proportional relationship or a preset proportional relationship. Leaking the bucket, after the second addition is over, there is also an overflow token, and the third sub-leakage that is not yet full is continued to be added for the third time, ... until all sub-leaked buckets have no overflow token, Or the preset number of overflows is reached, and the token that overflows the sub-leak after the preset number of overflows is added is discarded, and the total number of tokens is also reduced.
  • a leaky bucket speed limiting device includes: a total leaking bucket, a message receiving module, a token adding module, a parameter storage module, and a message processing module;
  • the total leaky bucket divides the total leaky bucket into multiple sub-leaked buckets according to the number of priority weights of the packet and the proportional parameter, and the packet weight priority corresponds to the sub-drain bucket weight priority;
  • the packet information receiving module is configured to receive related information of the packet, where the information about the packet includes at least: a packet length of the packet and a priority parameter of the packet;
  • the token adding module is configured to: after the packet information receiving module receives the related information of the packet, acquire a parameter related to the rate limit of the leaked bucket from the parameter storage module; and obtain a parameter related to the rate limit of the leaked bucket according to the acquired parameter Calculate the total number of tokens to be added; and add tokens to the sub-leak buckets based on the calculated total number of tokens and the weight priority of the sub-leak buckets;
  • the parameter storage module is configured to maintain a parameter related to a leak rate limit of the leaky bucket
  • the packet processing module is configured to forward, discard, or mark the packet according to the packet length of the packet and the number of tokens in the sub-leak bucket corresponding to the weight priority of the packet.
  • the total number of tokens calculated is added to the total leaky bucket. If the total leaky bucket is full, the total number of tokens of the leaky bucket is the total leaky bucket capacity, otherwise the total number of tokens added is added; If the total leaky bucket is full, the weighted priority sub-leak buckets are full. Otherwise, the total number of tokens to be added is divided according to the proportional relationship of the weight priority factors, and the sub-leak buckets provided for each weight priority are added. Number of tokens;
  • the parameter storage module is further configured to update a parameter related to a leak rate limit of the leaky bucket after the packet processing module forwards, or discards, or marks the message.
  • the parameter related to the leak rate limit of the leaked bucket stored by the parameter storage module includes: a total leaky bucket capacity, a weight priority factor, a total token addition rate, a time when the last speed limit occurs, a total leaky bucket, and each sub-leak bucket Number of tokens in ,
  • the parameters related to the parameter storage module update and the leak rate limit are: update the last speed limit The moment of birth is the current time, and the number of tokens in the total leaky bucket and each sub-leak bucket is the number of tokens after the speed limit operation.
  • the parameter related to the leak rate limit of the leaked bucket stored by the parameter storage module further includes one or more of the following: a capacity of each sub-leaked bucket, a ratio of sub-leakage bucket capacity division, an overlap ratio operation, an additional set ratio parameter, and a preset The number of overflows added.
  • the token adding module allocates the overflowed token to other sub-leaked buckets that are not full: the expired token is allocated to other sub-leaked buckets according to a weight priority factor proportional relationship or a preset proportional relationship. After the second addition is completed, there is also an overflow token, and the third sub-leakage that is not yet full is continued to be added for the third time, ... until all sub-leaked buckets have no overflow token, or reach the pre- Set the number of overflows added.
  • the packet processing module forwards, discards, or marks the packet according to the packet length of the packet and the number of tokens in the sub-leak bucket corresponding to the weight priority of the packet:
  • the method and the device for limiting the rate of the leaking buckets of the present invention treat the packets with different weight priorities differently, and divide the total leaking bucket into multiple sub-leaked buckets according to the requirements of the weighting jitter of each weight priority traffic, where each weight priority corresponds to the A sub-leak bucket, when the token is added, the tokens added to the sub-leak bucket are different according to the corresponding weight priorities.
  • the tokens added to the high-weight priority sub-leak bucket are more than provided.
  • Sub-leaked bucket after that, for the received message, according to The token in the sub-leak bucket corresponding to the weight priority of the packet performs a forwarding, discarding or marking operation.
  • the present invention compensates for the insufficiency of the packet loss rate of the traditional buckets, and the packets with different weight priorities have a fixed proportion of pass and drop probabilities under the same rate limit, that is, high-weight priority packets.
  • the present invention can flexibly limit the rate of packets according to the weight priority, thereby improving the data network.
  • the present invention shares the remaining tokens with other weight priority sub-leak buckets, and can implement each weight priority service limit.
  • the dynamic allocation of the fast bandwidth improves the resource utilization.
  • the present invention organically combines the rate limit of the data packet with the scheduling idea, thereby eliminating the hardware design of the scheduling function, thereby saving network hardware resources.
  • Figure 1 is a schematic diagram of the principle of the leaky bucket speed limit of the existing RFC standard
  • FIG. 2 is a schematic flow chart of a method for speed limit of a leaky bucket according to the present invention
  • FIG. 3 is a schematic diagram of a principle of a speed limit of a leaky bucket according to the present invention.
  • FIG. 4 is a schematic flow chart of a method for speed limit of a leaky bucket according to the present invention. detailed description
  • each weight priority corresponds to a sub-leak bucket in the total leaky bucket, and is added to the sub-leak bucket when the token is added.
  • the tokens are different according to the corresponding weight priorities.
  • the tokens added to the high-weight priority sub-leak bucket are added more than the tokens added to the low-weight priority sub-leak bucket, and are added in the token adding process.
  • the remaining tokens may be shared with other weight-priority sub-leak buckets, and then, for the received packets, according to the packet weight priority
  • the token in the corresponding sub-leak bucket performs a forwarding, discarding or marking operation.
  • the packet for the rate limit of the leaky bucket can be performed according to at least two weight priorities.
  • the division for example, according to the packet type
  • the leaked bucket capacity is divided into at least two sub-leaked buckets according to different weight priorities
  • the packet weight priority corresponds to the sub-drain bucket weight priority.
  • each sub-leak bucket can be divided according to the proportional relationship of the weight priority factor (such as the weight priority factors respectively, wl, w2, w3 wn ), or can be divided according to actual needs, in general,
  • Step 201 After receiving the related information of the packet, obtain parameters related to the rate limit of the leaky bucket.
  • the information related to the packet includes: a packet length of the packet and a priority parameter of the packet, where the parameter related to the leak rate limit may include, but is not limited to:
  • the capacity of each sub-leakage can be further obtained according to the capacity of the total leaked bucket and the weight priority factor; if the sub-leakage capacity is divided according to the actual demand, the leaky bucket is
  • the speed-related parameters also need to include the capacity of each sub-leaked bucket or the proportion of the sub-leaked bucket capacity.
  • each sub-leaked bucket can be obtained according to the total leaky bucket capacity and the proportion of each sub-leaked bucket capacity, but in any case, each The sub-leakage bucket capacity must meet the requirements of each weight priority traffic absorption jitter; in addition, the parameter related to the leaky bucket speed limit may further include an allocation ratio parameter and/or a preset mutual overflow addition frequency set by the mutual overflow operation. In practical applications, regardless of hardware Or the software implementation needs to maintain the above parameter configuration.
  • Step 202 Calculate the total number of tokens to be added according to the obtained parameters related to the rate limit of the leaky bucket.
  • the time difference between the time when the current rate limit occurs and the time when the last rate limit occurs is calculated, and the product of the time difference and the total token addition rate is calculated, and the total number of tokens to be added is obtained.
  • Step 203 Add a token to the total leak bucket and each sub-leak bucket according to the calculated total number of tokens and the weight priority of the sub-leak bucket.
  • the total number of tokens calculated is added to the total leaky bucket. If the total leaky bucket is full, the total number of tokens of the leaky bucket is the total leaky bucket capacity, otherwise, the total number of tokens added;
  • the weighted priority sub-leak buckets are full, otherwise the total number of tokens to be added is divided according to the proportional relationship of the weight priority factors, and the sub-leakage provided to each weight priority is obtained.
  • the bucket adds the number of tokens, and then adds a token to the sub-leak bucket according to the number of tokens added to each weight priority sub-leak bucket. If the sub-leak token has overflow, a sub-leak is required. The overflow operation between the buckets, thereby obtaining the number of tokens of the current ownership heavy priority sub-leak bucket.
  • Delta-token 1 delta-token *wl
  • Delta_token2 delta-token *w2
  • Delta—token delta—token 1+ delta_token2 + ... + delta—tokenn.
  • the process of overflow is: The process of adding a token, if the sub-leak is full, the number of tokens of the sub-leak is the corresponding sub-leakage capacity, and the corresponding added token is obtained in all sub-leaked buckets. After that, if one or several sub-leaked buckets are full, but the tokens provided for the sub-leaked buckets are still left, the overflowed tokens may be according to a weight priority factor ratio relationship or a preset proportional relationship. Assigned to other sub-leaked buckets that are not full.
  • the number of tokens of the sub-leaked bucket is the corresponding sub-leaked bucket capacity, the second addition After the end, if there is still an overflow token, the third sub-leakage that is not yet full will continue to be added for the third time, and so on until all the sub-buckets have no overflow token, or the preset number of mutual overflows is reached ( Also known as the number of iterations, the number of tokens for all child leaky buckets is obtained.
  • the overflow calculation of the overflow sub-bucket tokens is up to N-1, and if the preset mutual overflow addition times are reached, the sub-leakage overflows. The token will be discarded, and the total number of leaky tokens will also be reduced by the corresponding number of drops.
  • Step 204 Forward, or discard, or mark the packet according to the packet length of the packet and the number of tokens in the sub-leak bucket corresponding to the weight priority of the packet.
  • the corresponding sub-leak bucket is selected according to the packet weight priority, and then the number of tokens in the sub-leak bucket is compared with the packet length of the packet to determine whether to forward the packet. If the number of tokens in the leaky bucket is greater than or equal to the packet length of the packet, the packet is forwarded, and the number of tokens in the total leaky bucket and the sub-leaked bucket is decreased and the packet length is long. Corresponding number; if the number of tokens in the sub-leaked bucket is smaller than the packet length of the packet, discarding the packet or marking the packet, the total leaking bucket and all the sub-leaked buckets The number of tokens does not change.
  • the principle of the rate limit of the leaky buckets in the present invention is as shown in FIG. 3. It can be seen that the present invention can enable the different weight priority services to dynamically allocate redundant tokens when the rate limit is leaked, thereby realizing the priority of each weight.
  • the dynamic allocation of the rate-limiting bandwidth improves the utilization of the rate-limiting bandwidth and improves the network service quality.
  • Step 205 Update the parameters related to the leak rate limit of the leaky bucket.
  • the present invention also provides a leaky bucket speed limiting device, which includes: a total leaking bucket, a message information receiving module, a token adding module, a parameter storage module, and a message processing module;
  • the total leaky bucket divides the total leaky bucket into multiple sub-leaked buckets according to the number of priority weights of the packet and the proportional parameter, and the packet weight priority corresponds to the sub-drain bucket weight priority;
  • the packet information receiving module is configured to receive information about the packet, where the information about the packet includes at least: a packet length of the packet and a priority parameter of the packet;
  • the token adding module is configured to: after the packet information receiving module receives the related information of the packet, acquire a parameter related to the rate limit of the leaked bucket from the parameter storage module; and obtain a parameter related to the rate limit of the leaked bucket according to the acquired parameter Calculate the total number of tokens to be added; and add tokens to the sub-leak buckets based on the calculated total number of tokens and the weight priority of the sub-leak buckets;
  • the parameter storage module is configured to maintain a parameter related to a leak rate limit of the leaky bucket
  • the packet processing module is configured to forward, discard, or mark the packet according to the packet length of the packet and the number of tokens in the sub-leak bucket corresponding to the weight priority of the packet.
  • the total number of tokens calculated is added to the total leaky bucket. If the total leaky bucket is full, the total number of tokens of the leaky bucket is the total leaky bucket capacity, otherwise the total number of tokens added is added; If the total leaky bucket is full, the weighted priority sub-leak buckets are full. Otherwise, the total number of tokens to be added is divided according to the proportional relationship of the weight priority factors, and the sub-leak buckets provided for each weight priority are added. Number of tokens;
  • the parameter storage module is further configured to update a parameter related to a leak rate limit of the leaky bucket after the packet processing module forwards, or discards, or marks the message.
  • the parameter related to the leak rate limit of the leaked bucket stored by the parameter storage module includes: a total leaky bucket capacity, a weight priority factor, a total token addition rate, a time when the last speed limit occurs, a total leaky bucket, and each sub-leak bucket Number of tokens in ,
  • the parameters related to the parameter limit of the leaking bucket are: updating the current time when the last speed limit occurs to the current time, and updating the total leaky bucket and the number of tokens in each sub-leaked bucket as the speed limit operation Number of cards.
  • the parameter related to the leak rate limit of the leaked bucket stored by the parameter storage module further includes one or more of the following: a capacity of each sub-leaked bucket, a ratio of sub-leakage bucket capacity division, an overlap ratio operation, an additional set ratio parameter, and a preset The number of overflows added.
  • the token adding module allocates the overflowed token to other sub-leaked buckets that are not full: the expired token is allocated to other sub-leaked buckets according to a weight priority factor proportional relationship or a preset proportional relationship. After the second addition is completed, there is also an overflow token, and the third sub-leakage that is not yet full is continued to be added for the third time, ... until all sub-leaked buckets have no overflow token, or reach the pre- Set the number of overflows added.
  • the packet processing module forwards, discards, or marks the packet according to the packet length of the received packet and the number of tokens in the sub-leak bucket corresponding to the weight priority of the packet:
  • the present invention adds tokens to the weighted priority sub-leak buckets according to the proportional relationship of the weight priority factors, so that the packets of the respective weight priorities can be basically passed according to the proportional relationship of the weight priority factors, and the present invention
  • the sub-leak bucket token overflow operation is added, so that the tokens overflowed by each sub-leak bucket can be allocated to other sub-leak buckets, thereby avoiding waste of the speed limit bandwidth.

Landscapes

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

Abstract

本发明公开了一种漏桶限速方法,对于共用同一漏桶但具有不同权重优先级的一组报文进行限速时,将总漏桶按照权重优先级的个数及比例参数分割为多个子漏桶,收到报文相关信息后,获取与漏桶限速相关的参数;计算需要添加的总令牌数;根据总漏桶在接受添加总令牌后的状态以及子漏桶的权重优先级对子漏桶进行令牌添加;根据报文的包长及权重优先级对应的子漏桶中的令牌数,转发、或丢弃、或标记所述报文,对子漏桶进行令牌添加时,所有子漏桶获取相应的添加令牌后,将溢出的令牌分配给其它未满的子漏桶。本发明还相应地公开了一种漏桶限速装置。本发明能按照权重优先级对报文进行灵活限速,且能提高资源利用率。

Description

一种漏桶 P½方法及装置 技术领域
本发明涉及数据网络领域, 尤其涉及一种漏桶限速方法及装置。 背景技术
在现有的数据网络中, 由于报文流量的突发性, 常常会导致网络拥塞。 为了避免网络拥塞, 提高数据网络的服务质量(Quality of service, QoS ), 需要在接收端对报文进行限速, 如果报文的速率低于规定的速率, 则正常 接收报文; 如果报文的速率超过规定的速率, 则将报文丟弃, 或对报文进 行标记。
目前普遍釆用的方法是利用漏桶对报文进行限速, 常用的基于漏桶算 法的标准有 RFC2697和 RFC2698 , 即单速率三色双桶和双速率三色双桶 , RFC标准的漏桶限速原理如图 1所示, 具体为: 按规定的速率不断地向漏 桶中填充令牌, 直到漏桶装满为止。 当报文到来时, 将报文的包长跟漏桶 中的令牌数进行比较, 如果漏桶中有足够的令牌, 则报文允许通过, 同时 从漏桶中减去报文的包长所对应的令牌数; 如果漏桶中的令牌不够, 则将 才艮文丟弃, 或对艮文进行标记。
可以看出, RFC2697和 RFC2698虽然能够对报文进行限速, 但是在限 速的过程中无法区别优先级高低不同的报文的服务质量, 所以, 现有报文 限速方法不够灵活, 不利于提高数据网络服务质量及用户体验。 发明内容
有鉴于此, 本发明的主要目的在于提供一种漏桶限速方法及装置, 能 按照权重优先级对报文进行灵活限速, 从而提高数据网络服务质量及用户 体验。
为达到上述目的, 本发明的技术方案是这样实现的:
一种漏桶限速方法, 对于共用同一漏桶但具有不同权重优先级的一组 报文进行限速的时候, 将总漏桶按照权重优先级的个数及比例参数分割为 多个子漏桶, 所述比例参数必须根据各权重优先级流量吸收抖动的要求而 定, 且各子漏桶的容量和等于总漏桶容量, 报文权重优先级与子漏桶权重 优先级相对应, 该方法包括:
收到报文的相关信息后, 获取与漏桶限速相关的参数, 所述报文的相 关信息至少包括: 报文的包长和报文的优先级参数;
根据获取的与漏桶限速相关的参数计算需要添加的总令牌数; 根据计算的总令牌数及子漏桶的权重优先级对子漏桶进行令牌添加; 根据所述报文的包长及所述报文的权重优先级对应的子漏桶中的令牌 数, 转发、 或丟弃、 或标记所述报文,
所述根据计算的总令牌数及子漏桶的权重优先级对总漏桶及子漏桶进 行令牌添加为:
第一步, 将计算的总令牌数添加至总漏桶, 如果总漏桶满, 则总漏桶 的令牌数为总漏桶容量, 否则为总令牌添加后的数量; 第二步, 如果总漏 桶满, 则各权重优先级子漏桶均满, 否则将需要添加的总令牌数按照权重 优先级因子的比例关系划分, 得出提供给各个权重优先级子漏桶进行添加 的令牌数;
按照所述提供给各个权重优先级子漏桶进行添加的令牌数对子漏桶进 行令牌添加, 所有子漏桶获取相应的添加令牌后, 如果有子漏桶满, 则将 溢出的所有令牌经过互溢运算分配给其它未满的子漏桶。
所述转发、 或丟弃、 或标记报文之后, 该方法还包括: 更新与漏桶限 速相关的参数其中包括各子漏桶限速后的令牌数。 所述与漏桶限速相关的参数包括: 总漏桶的容量、 权重优先级因子、 总令牌添加速率、 上一次限速发生的时刻和总漏桶及各子漏桶中的令牌数, 所述更新与漏桶限速相关的参数为: 更新上一次限速发生的时刻为当 前时刻, 以及更新总漏桶及各子漏桶中的令牌数为限速运算后的令牌数。
所述与漏桶限速相关的参数还包括以下一项或多项: 各子漏桶的容量、 子漏桶容量划分比例、 互溢运算另外设置的分配比例参数、 预设互溢添加 次数。
所述将溢出子漏桶的令牌经过互溢运算分配给其它未满的子漏桶为: 将溢出的令牌按照权重优先级因子比例关系或者预先设置的比例关系 分配给其它未满的子漏桶, 第二次添加结束后, 还有溢出令牌, 则对另外 还未满的子漏桶继续进行第三次添加, ... ..., 直至所有子漏桶无溢出令牌、 或达到预设的互溢添加次数, 且达到预设互溢添加次数后子漏桶溢出的令 牌将丟弃, 同时总漏桶令牌数也减少相应丟弃令牌的数量。
所述根据报文的包长及报文的权重优先级对应的子漏桶中的令牌数, 转发、 或丟弃、 或标记所述 文为:
根据所述报文的权重优先级选择对应的子漏桶, 将所述子漏桶中的令 牌数与所述报文的包长进行比较, 所述子漏桶中的令牌数大于或等于所述 报文的包长, 则转发所述报文, 同时总漏桶及所述子漏桶中的令牌数减少 与所述报文包长相应的数目; 所述子漏桶中的令牌数小于所述报文的包长, 则丟弃所述报文或者对所述报文进行标记, 总漏桶及所有子漏桶中的令牌 数不变。
一种漏桶限速装置, 包括: 总漏桶、 报文信息接收模块、 令牌添加模 块、 参数存储模块、 报文处理模块; 其中,
所述总漏桶, 按照报文权重优先级的个数及比例参数将总漏桶分割为 多个子漏桶, 报文权重优先级与子漏桶权重优先级相对应; 所述报文信息接收模块, 用于接收报文的相关信息, 所述报文的相关 信息至少包括: 报文的包长和报文的优先级参数;
所述令牌添加模块, 用于在报文信息接收模块接收到报文的相关信息 后, 从参数存储模块获取与漏桶限速相关的参数; 以及根据获取的与漏桶 限速相关的参数计算需要添加的总令牌数; 以及根据计算的总令牌数及子 漏桶的权重优先级对子漏桶进行令牌添加;
所述参数存储模块, 用于维护与漏桶限速相关的参数;
所述报文处理模块, 用于根据报文的包长及报文的权重优先级对应的 子漏桶中的令牌数, 转发、 或丟弃、 或标记所述报文,
所述令牌添加模块根据计算的总令牌数及子漏桶的权重优先级对总漏 桶及各子漏桶进行令牌添加为:
第一步, 将计算的总令牌数添加至总漏桶, 如果总漏桶满, 则总漏桶 的令牌数为总漏桶容量, 否则为总令牌添加后的数量; 第二步, 如果总漏 桶满, 则各权重优先级子漏桶均满, 否则将需要添加的总令牌数按照权重 优先级因子的比例关系划分, 得出提供给各个权重优先级子漏桶进行添加 的令牌数;
按照所述提供给各个权重优先级子漏桶进行添加的令牌数对子漏桶进 行令牌添加, 所有子漏桶获取相应的添加令牌后, 将溢出的令牌经过互溢 运算分配给其它未满的子漏桶。
所述参数存储模块, 还用于在报文处理模块转发、 或丟弃、 或标记报 文之后, 更新与漏桶限速相关的参数。
所述参数存储模块存储的与漏桶限速相关的参数包括: 总漏桶的容量、 权重优先级因子、 总令牌添加速率、 上一次限速发生的时刻和总漏桶及各 子漏桶中的令牌数,
所述参数存储模块更新与漏桶限速相关的参数为: 更新上一次限速发 生的时刻为当前时刻, 以及更新总漏桶及各子漏桶中的令牌数为限速运算 后的令牌数。
所述参数存储模块存储的与漏桶限速相关的参数还包括以下一项或多 项: 各子漏桶的容量、 子漏桶容量划分比例、 互溢运算另外设置的分配比 例参数、 预设互溢添加次数。
所述令牌添加模块将溢出的令牌分配给其它未满的子漏桶为: 将溢出 的令牌按照权重优先级因子比例关系或者预先设置的比例关系分配给其它 未满的子漏桶, 第二次添加结束后, 还有溢出令牌, 则对另外还未满的子 漏桶继续进行第三次添加, ... ..., 直至所有子漏桶无溢出令牌、 或达到预 设的互溢添加次数。
所述报文处理模块根据报文的包长及报文的权重优先级对应的子漏桶 中的令牌数, 转发、 或丟弃、 或标记所述报文为:
根据所述报文的权重优先级选择对应的子漏桶, 将所述子漏桶中的令 牌数与所述报文的包长进行比较, 所述子漏桶中的令牌数大于或等于所述 报文的包长, 则转发所述报文, 同时总漏桶及所述子漏桶中的令牌数减少 与所述报文包长相应的数目; 所述子漏桶中的令牌数小于所述报文的包长, 则丟弃所述报文或者对所述报文进行标记, 总漏桶及所有子漏桶中的令牌 数不变。
本发明漏桶限速方法及装置, 对不同权重优先级的报文区别对待, 将 总漏桶根据各权重优先级流量吸收抖动的要求分割成多个子漏桶, 每一权 重优先级对应其中的一个子漏桶, 在进行令牌添加时, 提供给子漏桶进行 添加的令牌按照相应权重优先级的不同而不同, 一般提供给高权重优先级 子漏桶添加的令牌多于提供给低权重优先级子漏桶添加的令牌, 并且, 在 令牌添加过程中, 某些权重优先级子漏桶令牌冗余的情况下, 可以将其剩 余的令牌分享给其他权重优先级子漏桶, 之后, 对于接收到的报文, 根据 该报文权重优先级对应的子漏桶中的令牌执行转发、 丟弃或标记操作。 本 发明弥补了传统漏桶限速不能体现报文优先级区别的不足, 使得不同权重 优先级的报文在同一限速条件下有着固定比例的通过与丟弃概率, 即高权 重优先级报文在网络拥塞情况下有相对高的通过概率, 而低权重优先级的 报文则有相对高的丟弃概率, 所以, 本发明能按照权重优先级对报文进行 灵活限速, 从而提高数据网络服务质量及用户体验; 并且, 本发明在某些 权重优先级子漏桶令牌冗余的情况下, 将剩余的令牌分享给其他权重优先 级子漏桶, 能够实现各权重优先级业务限速带宽的动态分配, 提高资源利 用率; 此外, 本发明由于将数据报文的限速与调度思想进行了有机的结合, 可以省去调度功能的硬件设计, 从而可节省网络的硬件资源。 附图说明
图 1为现有 RFC标准的漏桶限速原理示意图;
图 2为本发明漏桶限速方法流程示意图;
图 3为本发明涉及的漏桶限速原理示意图;
图 4为本发明漏桶限速方法详细流程示意图。 具体实施方式
本发明的基本思想是: 对一组具有不同权重优先级的报文, 每一权重 优先级对应总漏桶中的一个子漏桶, 在进行令牌添加时, 提供给子漏桶进 行添加的令牌按照相应权重优先级的不同而不同, 一般提供给高权重优先 级子漏桶添加的令牌多于提供给低权重优先级子漏桶添加的令牌, 并且, 在令牌添加过程中, 某些权重优先级子漏桶令牌冗余的情况下, 可以将其 剩余的令牌分享给其他权重优先级子漏桶, 之后, 对于接收到的报文, 根 据该报文权重优先级对应的子漏桶中的令牌执行转发、 丟弃或标记操作。
本发明中, 漏桶限速所针对的报文可以按照至少两个权重优先级进行 划分(例如按照报文类型划分), 相应的, 将漏桶容量按照不同的权重优先 级划分为至少两个子漏桶, 报文权重优先级与子漏桶权重优先级相对应。
需要说明的是, 各子漏桶的容量可以按照权重优先级因子 (如各权重 优先级因子分别为 wl、 w2、 w3 wn ) 的比例关系进行划分, 也可根 据实际需求进行划分, 一般的, 高权重优先级子漏桶的容量较大, 低权重 优先级子漏桶的容量较小, 所有子漏桶容量之和等于总的漏桶的容量, 即 将总的漏桶容量表示为 BS ( bucket size ),将子漏桶的容量分别表示为 BS1、 BS2、 BS3... BSn, 则它们满足如下关系: BS = BS1+BS2 + BS3 + ... + BSn。
图 2为本发明漏桶限速方法流程示意图, 如图 2所示, 该方法包括: 步骤 201 : 收到报文的相关信息后, 获取与漏桶限速相关的参数。
这里, 报文的相关信息至少包括: 报文的包长和报文的优先级参数, 所述与漏桶限速相关的参数可以但不限于包括:
( 1 ) 总漏桶的容量;
( 2 )权重优先级因子;
( 3 ) 总令牌添加速率;
( 4 )上一次限速发生的时刻;
( 5 )总漏桶及各子漏桶中的令牌数, 如果之前发生了限速运算, 指上 一次同组报文发生限速运算后的令牌数。
如果按照权重优先级因子进行子漏桶容量划分, 则可以进一步根据总 漏桶的容量和权重优先级因子获取各子漏桶的容量; 如果根据实际需求进 行子漏桶容量划分, 则与漏桶限速相关的参数还需要包括各子漏桶的容量 或子漏桶容量划分比例, 根据总漏桶的容量和各子漏桶容量划分比例可以 获取各子漏桶的容量, 但无论如何, 各子漏桶容量均须满足各权重优先级 流量吸收抖动的要求; 此外, 与漏桶限速相关的参数还可以包括互溢运算 另外设置的分配比例参数和 /或预设互溢添加次数。 实际应用中, 无论硬件 还是软件实现都需要维护以上参数配置。
步骤 202: 根据获取的与漏桶限速相关的参数计算需要添加的总令牌 数。
具体的, 计算当前限速发生的时刻与上一次限速发生的时刻的时间差, 再计算该时间差与总令牌添加速率的乘积, 得到需要添加的总令牌数。
步骤 203:根据计算的总令牌数及子漏桶的权重优先级对总漏桶及各子 漏桶进行令牌添加。
具体的, 第一步, 将计算的总令牌数添加至总漏桶, 如果总漏桶满, 则总漏桶的令牌数为总漏桶容量, 否则为总令牌添加后的数量; 第二步, 如果总漏桶满, 则各权重优先级子漏桶均满, 否则将需要添加的总令牌数 按照权重优先级因子的比例关系划分, 得出提供给各个权重优先级子漏桶 进行添加的令牌数, 然后按照所述提供给各个权重优先级子漏桶进行添加 的令牌数对子漏桶进行令牌添加, 如果子漏桶令牌有溢出, 则须进行子漏 桶之间的互溢运算, 从而得到当前所有权重优先级子漏桶的令牌数。
例如, 如果子漏桶的令牌添加数目严格按照权重优先级因子
( wl,w2,w3,...,wn )的比例关系来获取总令牌添加数目,将需要添加的总令 牌数表示为 delta_token,将各子漏桶的令牌添加量分别表示为 delta_tokenl, delta_token2, delta_token3 , ... , delta_tokenn , 则它门满足 ^口下关系:
delta—token 1 = delta—token *wl;
delta_token2 = delta—token *w2;
delta_token3 = delta—token *w3; delta_tokenn = delta—token*舊;
delta—token = delta—token 1+ delta_token2 + ... + delta—tokenn.
互溢运算的是过程是这样的: 进行令牌添加时, 如果子漏桶满, 则该 子漏桶的令牌数为对应的子漏桶容量, 在所有子漏桶获取相应的添加令牌 后, 如果某一个或几个子漏桶已满, 但提供给该子漏桶进行添加的令牌还 有剩余, 则溢出的令牌可以按照权重优先级因子比例关系或者预先设置的 另外的比例关系分配给其它未满的子漏桶, 若其它未满子漏桶在第二次添 加溢出令牌后变满, 则该子漏桶的令牌数为对应的子漏桶容量, 第二次添 加结束后, 如果还有溢出令牌, 将再对另外还未满的子漏桶继续进行第三 次添加, 如此类推直至所有子漏桶无溢出令牌、 或达到预设的互溢添加次 数(也可称为迭代次数), 得到所有子漏桶的令牌数。
需要说明的是, 若子漏桶的数目为 N, 则溢出子漏桶令牌的互溢运算 迭代计算的次数最多为 N-1 ,且如果达到预设互溢添加次数, 则子漏桶的溢 出令牌将丟弃, 同时总漏桶令牌数也减少相应丟弃的数量。
步骤 204:根据报文的包长及所述报文的权重优先级对应的子漏桶中的 令牌数, 转发、 或丟弃、 或标记所述报文。
具体的, 先根据报文权重优先级选择对应的子漏桶, 然后将所述子漏 桶中的令牌数与所述报文的包长进行比较, 决定是否转发所述报文, 如果 所述子漏桶中的令牌数大于或等于所述报文的包长, 则转发所述报文, 同 时总漏桶及所述子漏桶中的令牌数减少与所述报文包长相应的数目; 如果 所述子漏桶中的令牌数小于所述报文的包长, 则丟弃所述报文或者对所述 报文进行标记, 总漏桶及所有子漏桶中的令牌数不变。
本发明涉及的漏桶限速原理如图 3 所示, 可以看出, 本发明能够使不 同权重优先级业务在漏桶限速的时候将冗余的令牌相互动态分配, 从而实 现各权重优先级限速带宽的动态分配, 提高了限速带宽的利用率, 提高了 网络服务质量。
步骤 205: 更新与漏桶限速相关的参数。
这里, 主要指更新上一次限速发生的时刻为当前时刻, 以及更新总漏 桶及各子漏桶中的令牌数为限速运算后的令牌数。 需要说明的是, 如果釆用硬件实现本发明, 则限速计算的逻辑及参数 存储资源将随子漏桶的数目的增多而线性的增多, 需要根据实际的需求进 行综合评估。 本发明漏桶限速方法详细流程如图 4所示。
本发明还相应地提出一种漏桶限速装置, 包括: 总漏桶、 报文信息接 收模块、 令牌添加模块、 参数存储模块、 报文处理模块; 其中,
所述总漏桶, 按照报文权重优先级的个数及比例参数将总漏桶分割为 多个子漏桶, 报文权重优先级与子漏桶权重优先级相对应;
所述报文信息接收模块, 用于接收报文的相关信息, 所述报文的相关 信息至少包括: 报文的包长和报文的优先级参数;
所述令牌添加模块, 用于在报文信息接收模块接收到报文的相关信息 后, 从参数存储模块获取与漏桶限速相关的参数; 以及根据获取的与漏桶 限速相关的参数计算需要添加的总令牌数; 以及根据计算的总令牌数及子 漏桶的权重优先级对子漏桶进行令牌添加;
所述参数存储模块, 用于维护与漏桶限速相关的参数;
所述报文处理模块, 用于根据报文的包长及报文的权重优先级对应的 子漏桶中的令牌数, 转发、 或丟弃、 或标记所述报文,
所述令牌添加模块根据计算的总令牌数及子漏桶的权重优先级对总漏 桶及子漏桶进行令牌添加为:
第一步, 将计算的总令牌数添加至总漏桶, 如果总漏桶满, 则总漏桶 的令牌数为总漏桶容量, 否则为总令牌添加后的数量; 第二步, 如果总漏 桶满, 则各权重优先级子漏桶均满, 否则将需要添加的总令牌数按照权重 优先级因子的比例关系划分, 得出提供给各个权重优先级子漏桶进行添加 的令牌数;
按照所述提供给各个权重优先级子漏桶进行添加的令牌数对子漏桶进 行令牌添加, 所有子漏桶获取相应的添加令牌后, 将溢出的令牌经过互溢 运算分配给其它未满的子漏桶。
所述参数存储模块, 还用于在报文处理模块转发、 或丟弃、 或标记报 文之后, 更新与漏桶限速相关的参数。
所述参数存储模块存储的与漏桶限速相关的参数包括: 总漏桶的容量、 权重优先级因子、 总令牌添加速率、 上一次限速发生的时刻和总漏桶及各 子漏桶中的令牌数,
所述参数存储模块更新与漏桶限速相关的参数为: 更新上一次限速发 生的时刻为当前时刻, 以及更新总漏桶及各子漏桶中的令牌数为限速运算 后的令牌数。
所述参数存储模块存储的与漏桶限速相关的参数还包括以下一项或多 项: 各子漏桶的容量、 子漏桶容量划分比例、 互溢运算另外设置的分配比 例参数、 预设互溢添加次数。
所述令牌添加模块将溢出的令牌分配给其它未满的子漏桶为: 将溢出 的令牌按照权重优先级因子比例关系或者预先设置的比例关系分配给其它 未满的子漏桶, 第二次添加结束后, 还有溢出令牌, 则对另外还未满的子 漏桶继续进行第三次添加, ... ..., 直至所有子漏桶无溢出令牌、 或达到预 设的互溢添加次数。
所述报文处理模块根据所收到报文的包长及所述报文的权重优先级对 应的子漏桶中的令牌数, 转发、 或丟弃、 或标记所述报文为:
根据所述报文的权重优先级选择对应的子漏桶, 将所述子漏桶中的令 牌数与所述报文的包长进行比较, 所述子漏桶中的令牌数大于或等于所述 报文的包长, 则转发所述报文, 同时总漏桶及所述子漏桶中的令牌数减少 与所述报文包长相应的数目; 所述子漏桶中的令牌数小于所述报文的包长, 则丟弃所述报文或者对所述报文进行标记, 总漏桶及所有子漏桶中的令牌 数不变。 本发明对不同权重优先级子漏桶优先按照权重优先级因子的比例关系 进行令牌添加, 使各个权重优先级的报文便能基本按照权重优先级因子的 比例关系来通过, 同时, 本发明增加了子漏桶令牌互溢运算, 从而可以将 各子漏桶溢出的令牌分配给其它子漏桶, 避免了限速带宽的浪费。
以上所述, 仅为本发明的较佳实施例而已, 并非用于限定本发明的保 护范围。

Claims

权利要求书
1、 一种漏桶限速方法, 其特征在于, 对于共用同一漏桶但具有不同权 重优先级的一组报文进行限速的时候, 将总漏桶按照权重优先级的个数及 比例参数分割为多个子漏桶, 所述比例参数必须根据各权重优先级流量吸 收抖动的要求而定, 且各子漏桶的容量和等于总漏桶容量, 报文权重优先 级与子漏桶权重优先级相对应, 该方法包括:
收到报文的相关信息后, 获取与漏桶限速相关的参数, 所述报文的相 关信息至少包括: 报文的包长和报文的优先级参数;
根据获取的与漏桶限速相关的参数计算需要添加的总令牌数; 根据计算的总令牌数及子漏桶的权重优先级对子漏桶进行令牌添加; 根据所述报文的包长及所述报文的权重优先级对应的子漏桶中的令牌 数, 转发、 或丟弃、 或标记所述报文,
所述根据计算的总令牌数及子漏桶的权重优先级对总漏桶及子漏桶进 行令牌添加为:
第一步, 将计算的总令牌数添加至总漏桶, 如果总漏桶满, 则总漏桶 的令牌数为总漏桶容量, 否则为总令牌添加后的数量; 第二步, 如果总漏 桶满, 则各权重优先级子漏桶均满, 否则将需要添加的总令牌数按照权重 优先级因子的比例关系划分, 得出提供给各个权重优先级子漏桶进行添加 的令牌数;
按照所述提供给各个权重优先级子漏桶进行添加的令牌数对子漏桶进 行令牌添加, 所有子漏桶获取相应的添加令牌后, 如果有子漏桶满, 则将 溢出的所有令牌经过互溢运算分配给其它未满的子漏桶。
2、 根据权利要求 1所述的漏桶限速方法, 其特征在于, 所述转发、 或 丟弃、 或标记报文之后, 该方法还包括: 更新与漏桶限速相关的参数其中 包括各子漏桶限速后的令牌数。
3、 根据权利要求 2所述的漏桶限速方法, 其特征在于,
所述与漏桶限速相关的参数包括: 总漏桶的容量、 权重优先级因子、 总令牌添加速率、 上一次限速发生的时刻和总漏桶及各子漏桶中的令牌数, 所述更新与漏桶限速相关的参数为: 更新上一次限速发生的时刻为当 前时刻, 以及更新总漏桶及各子漏桶中的令牌数为限速运算后的令牌数。
4、 根据权利要求 3所述的漏桶限速方法, 其特征在于, 所述与漏桶限 速相关的参数还包括以下一项或多项: 各子漏桶的容量、 子漏桶容量划分 比例、 互溢运算另外设置的分配比例参数、 预设互溢添加次数。
5、 根据权利要求 1至 4任一项所述的漏桶限速方法, 其特征在于, 所 述将溢出子漏桶的令牌经过互溢运算分配给其它未满的子漏桶为:
将溢出的令牌按照权重优先级因子比例关系或者预先设置的比例关系 分配给其它未满的子漏桶, 第二次添加结束后, 还有溢出令牌, 则对另外 还未满的子漏桶继续进行第三次添加, ... ..., 直至所有子漏桶无溢出令牌、 或达到预设的互溢添加次数, 且达到预设互溢添加次数后子漏桶溢出的令 牌将丟弃, 同时总漏桶令牌数也减少相应丟弃令牌的数量。
6、 根据权利要求 5所述的漏桶限速方法, 其特征在于, 所述根据报文 的包长及报文的权重优先级对应的子漏桶中的令牌数, 转发、 或丟弃、 或 标记所述>¾文为:
根据所述报文的权重优先级选择对应的子漏桶, 将所述子漏桶中的令牌 数与所述报文的包长进行比较, 所述子漏桶中的令牌数大于或等于所述报文 的包长, 则转发所述 4艮文, 同时总漏桶及所述子漏桶中的令牌数减少与所述 报文包长相应的数目; 所述子漏桶中的令牌数小于所述报文的包长, 则丟弃 所述报文或者对所述报文进行标记, 总漏桶及所有子漏桶中的令牌数不变。
7、 一种漏桶限速装置, 其特征在于, 该装置包括: 总漏桶、 报文信息 接收模块、 令牌添加模块、 参数存储模块、 报文处理模块; 其中, 所述总漏桶, 按照报文权重优先级的个数及比例参数将总漏桶分割为 多个子漏桶, 报文权重优先级与子漏桶权重优先级相对应;
所述报文信息接收模块, 用于接收报文的相关信息, 所述报文的相关 信息至少包括: 报文的包长和报文的优先级参数;
所述令牌添加模块, 用于在报文信息接收模块接收到报文的相关信息 后, 从参数存储模块获取与漏桶限速相关的参数; 以及根据获取的与漏桶 限速相关的参数计算需要添加的总令牌数; 以及根据计算的总令牌数及子 漏桶的权重优先级对子漏桶进行令牌添加;
所述参数存储模块, 用于维护与漏桶限速相关的参数;
所述报文处理模块, 用于根据报文的包长及报文的权重优先级对应的 子漏桶中的令牌数, 转发、 或丟弃、 或标记所述报文,
所述令牌添加模块根据计算的总令牌数及子漏桶的权重优先级对总漏 桶及各子漏桶进行令牌添加为:
第一步, 将计算的总令牌数添加至总漏桶, 如果总漏桶满, 则总漏桶 的令牌数为总漏桶容量, 否则为总令牌添加后的数量; 第二步, 如果总漏 桶满, 则各权重优先级子漏桶均满, 否则将需要添加的总令牌数按照权重 优先级因子的比例关系划分, 得出提供给各个权重优先级子漏桶进行添加 的令牌数;
按照所述提供给各个权重优先级子漏桶进行添加的令牌数对子漏桶进 行令牌添加, 所有子漏桶获取相应的添加令牌后, 将溢出的令牌经过互溢 运算分配给其它未满的子漏桶。
8、 根据权利要求 7所述的漏桶限速装置, 其特征在于,
所述参数存储模块, 还用于在报文处理模块转发、 或丟弃、 或标记报 文之后, 更新与漏桶限速相关的参数。
9、 根据权利要求 8所述的漏桶限速装置, 其特征在于, 所述参数存储模块存储的与漏桶限速相关的参数包括: 总漏桶的容量、 权重优先级因子、 总令牌添加速率、 上一次限速发生的时刻和总漏桶及各 子漏桶中的令牌数,
所述参数存储模块更新与漏桶限速相关的参数为: 更新上一次限速发 生的时刻为当前时刻, 以及更新总漏桶及各子漏桶中的令牌数为限速运算 后的令牌数。
10、 根据权利要求 9所述的漏桶限速装置, 其特征在于, 所述参数存 储模块存储的与漏桶限速相关的参数还包括以下一项或多项: 各子漏桶的 容量、 子漏桶容量划分比例、 互溢运算另外设置的分配比例参数、 预设互 溢添加次数。
11、 根据权利要求 7至 9任一项所述的漏桶限速装置, 其特征在于, 所述令牌添加模块将溢出的令牌分配给其它未满的子漏桶为: 将溢出 的令牌按照权重优先级因子比例关系或者预先设置的比例关系分配给其它 未满的子漏桶, 第二次添加结束后, 还有溢出令牌, 则对另外还未满的子 漏桶继续进行第三次添加, ... ..., 直至所有子漏桶无溢出令牌、 或达到预 设的互溢添加次数。
12、 根据权利要求 11所述的漏桶限速装置, 其特征在于,
所述报文处理模块根据报文的包长及报文的权重优先级对应的子漏桶 中的令牌数, 转发、 或丟弃、 或标记所述报文为:
根据所述报文的权重优先级选择对应的子漏桶, 将所述子漏桶中的令 牌数与所述报文的包长进行比较, 所述子漏桶中的令牌数大于或等于所述 报文的包长, 则转发所述报文, 同时总漏桶及所述子漏桶中的令牌数减少 与所述报文包长相应的数目; 所述子漏桶中的令牌数小于所述报文的包长, 则丟弃所述报文或者对所述报文进行标记, 总漏桶及所有子漏桶中的令牌 数不变。
PCT/CN2011/076465 2011-06-28 2011-06-28 一种漏桶限速方法及装置 Ceased WO2013000116A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP11868792.0A EP2728812B1 (en) 2011-06-28 2011-06-28 Method and device for leaky bucket speed-limitation
PCT/CN2011/076465 WO2013000116A1 (zh) 2011-06-28 2011-06-28 一种漏桶限速方法及装置
US14/127,862 US9160669B2 (en) 2011-06-28 2011-06-28 Method and device for leaky bucket speed-limitation

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/076465 WO2013000116A1 (zh) 2011-06-28 2011-06-28 一种漏桶限速方法及装置

Publications (1)

Publication Number Publication Date
WO2013000116A1 true WO2013000116A1 (zh) 2013-01-03

Family

ID=47423356

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/076465 Ceased WO2013000116A1 (zh) 2011-06-28 2011-06-28 一种漏桶限速方法及装置

Country Status (3)

Country Link
US (1) US9160669B2 (zh)
EP (1) EP2728812B1 (zh)
WO (1) WO2013000116A1 (zh)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9525635B2 (en) * 2011-11-15 2016-12-20 Nec Corporation Network communication apparatus and method of preferential band limitation of transfer frame
US10291472B2 (en) * 2015-07-29 2019-05-14 AppFormix, Inc. Assessment of operational states of a computing environment
US10581687B2 (en) 2013-09-26 2020-03-03 Appformix Inc. Real-time cloud-infrastructure policy implementation and management
KR101796372B1 (ko) * 2016-02-12 2017-11-10 경희대학교 산학협력단 콘텐츠 중심 네트워킹에서 멀티패스를 이용한 인터레스트 병렬 포워딩 장치 및 방법
US10868742B2 (en) 2017-03-29 2020-12-15 Juniper Networks, Inc. Multi-cluster dashboard for distributed virtualization infrastructure element monitoring and policy control
US11323327B1 (en) 2017-04-19 2022-05-03 Juniper Networks, Inc. Virtualization infrastructure element monitoring and policy control in a cloud environment using profiles
US10761919B2 (en) 2018-02-23 2020-09-01 Dell Products, L.P. System and method to control memory failure handling on double-data rate dual in-line memory modules
US10705901B2 (en) 2018-02-23 2020-07-07 Dell Products, L.P. System and method to control memory failure handling on double-data rate dual in-line memory modules via suspension of the collection of correctable read errors
US11483241B2 (en) 2020-09-30 2022-10-25 Fortinet, Inc. Network traffic metering credit distribution in network device having multiple processing units

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859206A (zh) * 2006-03-24 2006-11-08 华为技术有限公司 一种剩余带宽复用的方法及网络设备
WO2008082599A1 (en) * 2006-12-29 2008-07-10 Ellacoya Networks, Inc. Hierarchical virtual queuing
CN101425974A (zh) * 2008-12-05 2009-05-06 中兴通讯股份有限公司 一种通过分级漏桶实现h-qos的方法
CN101478491A (zh) * 2009-02-10 2009-07-08 中兴通讯股份有限公司 一种实现分组业务区分服务的方法及装置
CN101848167A (zh) * 2010-06-01 2010-09-29 北京星网锐捷网络技术有限公司 基于类的加权公平队列调度方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7173908B2 (en) * 2002-07-08 2007-02-06 Alcatel Canada Inc. Flexible policing technique for telecommunications traffic
US7529191B2 (en) 2005-02-18 2009-05-05 Broadcom Corporation Programmable metering behavior based on table lookup
US7440405B2 (en) * 2005-03-11 2008-10-21 Reti Corporation Apparatus and method for packet forwarding with quality of service and rate control
US7719968B2 (en) * 2005-12-30 2010-05-18 Extreme Networks, Inc. Multi-priority multi-color markers for traffic metering
US8467296B2 (en) * 2009-01-09 2013-06-18 Foundry Networks, Llc Hierarchical rate color marker

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1859206A (zh) * 2006-03-24 2006-11-08 华为技术有限公司 一种剩余带宽复用的方法及网络设备
WO2008082599A1 (en) * 2006-12-29 2008-07-10 Ellacoya Networks, Inc. Hierarchical virtual queuing
CN101425974A (zh) * 2008-12-05 2009-05-06 中兴通讯股份有限公司 一种通过分级漏桶实现h-qos的方法
CN101478491A (zh) * 2009-02-10 2009-07-08 中兴通讯股份有限公司 一种实现分组业务区分服务的方法及装置
CN101848167A (zh) * 2010-06-01 2010-09-29 北京星网锐捷网络技术有限公司 基于类的加权公平队列调度方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2728812A4 *

Also Published As

Publication number Publication date
EP2728812B1 (en) 2016-05-25
EP2728812A1 (en) 2014-05-07
US20140119190A1 (en) 2014-05-01
EP2728812A4 (en) 2015-03-18
US9160669B2 (en) 2015-10-13

Similar Documents

Publication Publication Date Title
WO2013000116A1 (zh) 一种漏桶限速方法及装置
CN102238068B (zh) 一种报文的传输方法和系统
US10063478B2 (en) Switching device and control method of switching device
CN110121213B (zh) 一种多业务资源调度方法及装置
US7636316B2 (en) Resource allocation plan in a network
RU2643666C2 (ru) Способ и устройство для управления авторизацией виртуальной очереди вывода, а также компьютерный носитель информации
CN102447623A (zh) 光网络频谱资源碎片级联方法及装置
WO2022121079A1 (zh) 一种流量转发设备的链路聚合方法及流量转发设备
Panno et al. An enhanced joint scheduling scheme for GBR and non-GBR services in 5G RAN
Ren et al. A sdn-based dynamic traffic scheduling algorithm
US12199876B2 (en) Transmission control method and apparatus
JP2016032210A (ja) 仮想ネットワーク割当方法および装置
EP3063969B1 (en) System and method for traffic engineering using link buffer status
WO2019167859A1 (ja) 見積り装置および見積り方法
CN104301255B (zh) 一种光网络多用户带宽公平分配的方法
WO2013000113A1 (zh) 一种漏桶限速方法及装置
WO2021114930A1 (zh) 一种网络切片报文传输方法、电子设备及存储介质
CN110190988A (zh) 一种业务部署方法及装置
WO2013000112A1 (zh) 一种漏桶限速方法及装置
Tan et al. An optimal solution to resource allocation among soft QoS traffic in wireless network
WO2013000114A1 (zh) 一种漏桶限速方法及装置
Zeng et al. A Survivable Routing Algorithm with Hybrid Protection in Elastic Optical Networks
CN103428774B (zh) 资源调度方法及装置
Huang et al. Nonuniform bandwidth reservation for tunnels in MPLS network using meter tables of OpenFlow
CN111182379B (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: 11868792

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 14127862

Country of ref document: US

Ref document number: 2011868792

Country of ref document: EP