Service management
US-2024334169-A1 · Oct 3, 2024 · US
US9231828B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9231828-B2 |
| Application number | US-201313916476-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 12, 2013 |
| Priority date | Jan 9, 2009 |
| Publication date | Jan 5, 2016 |
| Grant date | Jan 5, 2016 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
One embodiment provides a system that facilitates bandwidth-profile enforcement. During operation, the system indicates a packet's compliance with a bandwidth profile based at least on available high-compliance tokens and medium-compliance tokens. The system further accounts for overflow tokens from a respective class of service (CoS) and distribute an overflow token to another CoS priority level based on the overflow token's CoS information.
Opening claim text (preview).
What is claimed is: 1. A non-transitory storage medium storing instructions, which when executed by a processor cause the processor to perform a method, the method comprising: indicating a packet's compliance with a bandwidth profile based at least on available high-compliance tokens and medium-compliance tokens; and distributing an overflow token from one class of service (CoS) priority level to another CoS priority level; and precluding an overflow token from being used by a CoS priority level higher than the CoS priority level to which the overflow token originally belongs. 2. The non-transitory storage medium of claim 1 , wherein whether a respective CoS priority level is allowed or precluded from sharing tokens with another CoS priority level is determined by a CoS-specific sharing flag. 3. The non-transitory storage medium of claim 1 , wherein the overflow tokens are high-compliance tokens, and wherein the number of overflow high-compliance tokens distributed to a respective CoS priority level is limited by an upper rate limit for high-compliance tokens for that CoS priority level. 4. The non-transitory storage medium of claim 1 , wherein the overflow tokens are medium-compliance tokens, and wherein the number of overflow medium-compliance tokens distributed to a respective CoS priority level is limited by an upper rate limit for medium-compliance tokens for that CoS priority level. 5. The non-transitory storage medium of claim 1 , wherein distributing overflow tokens to other CoS priority levels comprises distributing the overflow tokens in a strict-priority order. 6. The non-transitory storage medium of claim 1 , wherein distributing overflow tokens to other CoS priority levels comprises distributing the overflow tokens based at least on a relative weight assigned to a respective CoS priority level. 7. The non-transitory storage medium of claim 1 , wherein indicating the packet's compliance with the bandwidth profile comprises marking the packet green when the packet is in high compliance, yellow when the packet is in medium compliance, and red when the packet is in low compliance. 8. The non-transitory storage medium of claim 1 , further comprising converting an overflow high-compliance token to a medium-compliance token. 9. A method comprising: indicating a packet's compliance with a bandwidth profile based at least on available high-compliance tokens and medium-compliance tokens; distributing an overflow token from one CoS priority level to another CoS priority level; and precluding an overflow token from being used by a CoS priority level higher than the CoS priority level to which the overflow token originally belongs. 10. The method of claim 9 , further comprising determining wherein whether a respective CoS priority level is allowed or precluded from sharing tokens with another CoS priority level based at least on a CoS-specific sharing flag. 11. The method of claim 9 , wherein the overflow tokens are high-compliance tokens, and wherein the method further comprises limiting the number of overflow high-compliance tokens distributed to a respective CoS level to an upper limit for high-compliance tokens for that CoS level. 12. The method of claim 9 , wherein the overflow tokens are medium-compliance tokens, and wherein the method further comprises limiting the number of overflow medium-compliance tokens distributed to a respective CoS level to an upper limit for medium-compliance tokens for that CoS level. 13. The method of claim 9 , wherein distributing the overflow tokens to other CoS levels comprises distributing the overflow tokens in a strict-priority order. 14. The method of claim 9 , wherein distributing the overflow tokens to other CoS levels comprises distributing the overflow tokens based at least on a relative weight assigned to a respective CoS level. 15. The method of claim 9 , wherein indicating the packet's compliance with the bandwidth profile comprises marking the packet green when the packet is in high compliance, yellow when the packet is in medium compliance, and red when the packet is in low compliance. 16. The method of claim 11 , further comprising converting an overflow high-compliance token to a medium-compliance token. 17. A system, comprising: a processor; and a non-transitory computer-readable storage devices storing instructions which when executed by the processor causes the processor to perform a method, the method comprising: indicating a packet's compliance with a bandwidth profile based at least on available high-compliance tokens and medium-compliance tokens; distributing an overflow token from one CoS priority level to another CoS priority level; and precluding an overflow token from being used by a CoS priority level higher than the CoS priority level to which the overflow token originally belongs. 18. The system of claim 17 , wherein the method further comprises determining wherein whether a respective CoS priority level is allowed or precluded from sharing tokens with another CoS priority level based at least on a CoS-specific sharing flag. 19. The system of claim 17 , wherein the overflow tokens are high-compliance tokens, and wherein the method further comprises limiting the number of overflow high-compliance tokens distributed to a respective CoS priority level to an upper limit for high-compliance tokens for that CoS priority level. 20. The system of claim 17 , wherein the overflow tokens are medium-compliance tokens, and wherein the method further comprises limiting the number of overflow medium-compliance tokens distributed to a respective CoS priority level to an upper limit for medium-compliance tokens for that CoS priority level. 21. The system of claim 17 , wherein distributing the overflow tokens to other CoS priority levels comprises distributing the overflow tokens in a strict-priority order. 22. The system of claim 17 , wherein distributing the overflow tokens to other CoS priority levels comprises distributing the overflow tokens based at least on a relative weight assigned to a respective CoS priority level. 23. The system of claim 17 , wherein indicating the packet's compliance with the bandwidth profile comprises marking the packet green when the packet is in high compliance, yellow when the packet is in medium compliance, and red when the packet is in low compliance. 24. The system of claim 21 , wherein the method further comprises converting an overflow high-compliance token to a medium- compliance token.
Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities (flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76) · CPC title
by redistribution of residual bandwidth · CPC title
Individual queue per QOS, rate or priority · CPC title
for supporting services specification, e.g. SLA · CPC title
using token-bucket · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.