Source: http://www.google.com/patents/US20030223430?dq=6,631,400
Timestamp: 2014-10-26 04:49:35
Document Index: 563526474

Matched Legal Cases: ['art 300', 'art 300', 'art 300', 'art 300', 'art 300', 'art 300', 'art 300', 'art 300', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400', 'art 400']

Patent US20030223430 - Distributing unused allocated bandwidth using a borrow vector - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA packet-based traffic forwarding system with a plurality of contending queues. Each queue has an allocated bandwidth and an associated borrow vector. When a first queue does not consume all of its allocated bandwidth, the borrow vector associated with a second queue is checked to determine whether the...http://www.google.com/patents/US20030223430?utm_source=gb-gplus-sharePatent US20030223430 - Distributing unused allocated bandwidth using a borrow vectorAdvanced Patent SearchPublication numberUS20030223430 A1Publication typeApplicationApplication numberUS 10/370,669Publication dateDec 4, 2003Filing dateFeb 18, 2003Priority dateJun 4, 2002Also published asUS7352761Publication number10370669, 370669, US 2003/0223430 A1, US 2003/223430 A1, US 20030223430 A1, US 20030223430A1, US 2003223430 A1, US 2003223430A1, US-A1-20030223430, US-A1-2003223430, US2003/0223430A1, US2003/223430A1, US20030223430 A1, US20030223430A1, US2003223430 A1, US2003223430A1InventorsSandeep Lodha, Deepak Aatresh, Rajesh Narayanan, Raymond Vaughan-WilliamsOriginal AssigneeSandeep Lodha, Deepak Aatresh, Rajesh Narayanan, Raymond Vaughan-WilliamsExport CitationBiBTeX, EndNote, RefManReferenced by (15), Classifications (6), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetDistributing unused allocated bandwidth using a borrow vectorUS 20030223430 A1Abstract A packet-based traffic forwarding system with a plurality of contending queues. Each queue has an allocated bandwidth and an associated borrow vector. When a first queue does not consume all of its allocated bandwidth, the borrow vector associated with a second queue is checked to determine whether the second queue is permitted to use the unconsumed allocated bandwidth of the first queue. If the second queue has packets to forward, the second queue forwards the packets using the unconsumed allocated bandwidth of the first queue. Images(6) Claims(19)
What is claimed is: 1. A method of allocating bandwidth between a plurality of queues, comprising: allocating bandwidth between a plurality of queues; and setting a borrow vector for a queue of said plurality of queues that indicates a subset of said plurality of queues from which borrowing unused allocated bandwidth is permitted. 2. The method of claim 1, further comprising: consuming bandwidth according to said allocated bandwidth; and allowing unused allocated bandwidth of a first queue to be used by a second queue if a borrow vector of said second queue indicates that borrowing from said first queue is permitted. 3. The method of claim 1, further comprising: running a scheduling algorithm to identify a queue, Qi; allowing Qi to consume up to the allocated bandwidth of Qi; determining whether Qi has unused allocated bandwidth; identifying a next queue, Qnext; and checking a borrow vector associated with Qnext to determine whether Qnext is permitted to borrow unused allocated bandwidth from Qi. 4. The method of claim 3, further comprising: consuming said unused allocated bandwidth if Qnext is permitted to borrow unused allocated bandwidth from Qi. 5. The method of claim 1, wherein said borrow vector indicates whether a queue, Qnext, of said plurality of queues is permitted to borrow unused bandwidth from said plurality of queues other than Qnext. 6. A method for forwarding packet-based traffic from a plurality of contending queues to an output having a finite bandwidth, comprising: consuming a portion of bandwidth of an output with packets from a plurality of queues according to respective bandwidths allocated to said plurality of queues, leaving unused allocated bandwidth of a first queue of said plurality of queues when said first queue does not exhaust the bandwidth that is allocated to said first queue; and allowing a second queue to forward packets using said unused allocated bandwidth if a borrow vector associated with said second queue indicates that said second queue is permitted to use bandwidth allocated to said first queue. 7. The method of claim 6, wherein said borrow vector indicates whether said second queue is permitted to borrow unused bandwidth from said plurality of queues other than said second queue. 8. The method of claim 6, further comprising: determining that said first queue has unused allocated bandwidth. 9. The method of claim 6, further comprising: determining from said borrow vector that said second queue is permitted to use said unused allocated bandwidth; and determining that said second queue has packets to forward. 10. The method of claim 6, further comprising: identifying said second queue using a routine for identifying a next queue. 11. The method of claim 10, further comprising: identifying a third queue using said routine for identifying a next queue; and allowing said third queue to forward packets using a portion of said unused allocated bandwidth if a borrow vector associated with said third queue indicates said third queue is permitted to borrow from said first queue and said second queue consumes less than said unused allocated bandwidth, leaving said portion. 12. A system for forwarding packet-based traffic from a plurality of contending queues to an output having a finite bandwidth, comprising: a plurality of queues for forwarding packets, wherein a first queue of said plurality of queues has a first allocated bandwidth; a borrow vector, associated with a second queue, configured to indicate a subset of said plurality of queues from which said second queue is permitted to borrow unused allocated bandwidth; a scheduler for forwarding packets from said second queue using a portion of said first allocated bandwidth when said first queue does not consume all of said first allocated bandwidth, if said borrow vector associated with said second queue indicates that said second queue is permitted to borrow unused allocated bandwidth from said first queue. 13. The system of claim 12, wherein said borrow vector indicates whether said second queue is permitted to use bandwidth allocated to each of said plurality of queues other than said second queue. 14. The system of claim 12, further comprising: a plurality of borrow vectors respectively associated with each of said plurality of queues other than said second queue. 15. The system of claim 12, further comprising: a register configured to contain said borrow vector, wherein said borrow vector includes an array of bits, and wherein each bit of said array of bits corresponds to a queue of said subset. 16. The system of claim 12, wherein said scheduler allows packets to be forwarded according to a scheduling algorithm. 17. The system of claim 12, wherein said scheduler allows packets to be forwarded according to allocated bandwidth. 18. The system of claim 12, further comprising: an and gate for enabling said second second queue when said second queue is not empty and said borrow vector indicates said second queue may borrow unused allocated bandwidth from said first queue. 19. The system of claim 12, wherein said scheduler implements a first scheduling algorithm for identifying the queues from which packet forwarding is allowed and a second scheduling algorithm for identifying a next queue that is permitted to used unused allocated bandwidth.
CROSS REFERENCE TO RELATED APPLICATION [0001] This application is entitled to the benefit of provisional Patent Application Serial No. 60/385,982, filed Jun. 4, 2002.
BACKGROUND OF THE INVENTION [0002] Weighted Fair Queuing (WFQ) and credit token schemes are two ways to schedule packets out of a multi-queue system. With a WFQ scheme, each queue gets a transmission window and may forward packets only during its transmission window. The size of the transmission window given to each queue corresponds to the amount of bandwidth that has been allocated to the respective queues. With a credit token scheme, each queue gets tokens and may forward packets so long as the respective queue has tokens. The amount of tokens given to each queue corresponds to the amount of bandwidth that has been allocated to the respective queues. [0003] With a WFQ scheme, time slots are allocated to each queue. The size of the time slots may be different. The bandwidth allocated to each queue can be weighted by setting the time slots to different sizes. An idle time slot allocation may be used to control the total bandwidth utilized. [0004] With a credit token scheme, tokens are replenished for each queue at the start of a time period. The queues may forward packets as long as they have tokens. When more than one queue has tokens, packets from the queue with the highest priority are typically forwarded first. The length of the time periods between token replenishment may be adjusted to control the profile of bandwidth utilization. [0005] With both the WFQ and credit token schemes, during a given time period a queue may not use all of its allocated bandwidth. Accordingly, it would be desirable to identify which queues can borrow unused allocated bandwidth from a queue that does not utilize its allocated share, such as when the queue has no more packets. It would also be desirable to determine at what rate those queues are entitled to forward packets. [0006] In view of the desire to borrow unused allocated bandwidth from a queue that does not utilize its allocated share of bandwidth, what is needed is a new unused bandwidth allocation scheme that allows determination of which queues can borrow unused allocated bandwidth. In addition, it would be advantageous to establish a rate at which those queues are entitled to forward packets. SUMMARY OF THE INVENTION [0007] A technique for allocating bandwidth between a plurality of queues includes allocating bandwidth between queues and setting a borrow vector for one of the queues that indicates a subset of queues from which borrowing unused allocated bandwidth is permitted. This technique enables the sharing of unused bandwidth according to an allocation scheme that allows determination of which queues can borrow the unused bandwidth. The technique can be easily implemented in hardware. [0008] In an embodiment, a method for forwarding packet-based traffic from a plurality of contending queues to an output having a finite bandwidth includes consuming a portion of bandwidth of an output with packets from queues according to respective bandwidths allocated to the queues, leaving unused allocated bandwidth of a first queue when the first queue does not exhaust the bandwidth that is allocated to the first queue and allowing a second queue to forward packets using the unused allocated bandwidth if a borrow vector associated with the second queue indicates that the second queue is permitted to use bandwidth allocated to the first queue. [0009] In another embodiment, a system for forwarding packet-based traffic from a plurality of contending queues to an output having a finite bandwidth includes queues for forwarding packets, wherein a first queue of the queues has a first allocated bandwidth, a borrow vector, associated with a second queue, configured to indicate a subset of the queues from which the second queue is permitted to borrow unused allocated bandwidth, a scheduler for forwarding packets from the second queue using a portion of the first allocated bandwidth when the first queue does not consume all of the first allocated bandwidth, if the borrow vector associated with the second queue indicates that the second queue is permitted to borrow unused allocated bandwidth from the first queue. [0010] Other aspects and advantages will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrating by way of example the principles of the invention.
BRIEF DESCRIPTION OF THE DRAWINGS [0011]FIG. 1 is a block diagram of a system for distributing unused allocated bandwidth in accordance with an embodiment of the invention. [0012]FIG. 2 depicts exemplary bandwidth allocations and borrow vector configurations in accordance with an embodiment of the invention. [0013]FIG. 3 is a flowchart of a method for distributing unused allocated bandwidth in accordance with an embodiment of the invention, to be implemented by the system of FIG. 1. [0014]FIGS. 4A and 4B depict flowcharts of methods for distributing unused allocated bandwidth in accordance with embodiments of the invention. [0015]FIG. 5 is a block diagram of a subsystem for distributing unused allocated bandwidth in accordance with an embodiment of the invention.
DETAILED DESCRIPTION OF THE INVENTION [0016] As shown in the drawings for the purposes of illustration, an embodiment of the invention is a traffic forwarding system configured for use in a network with packetbased traffic. The system includes a scheduler and a plurality of queues with associated borrow vectors. In an embodiment, a scheduling algorithm identifies the queue from which packets should be forwarded. If the identified queue has consumed its allocated bandwidth, then the scheduling algorithm (or some other scheduling algorithm) identifies at least one other queue (a borrowing queue) to consume the unused allocated bandwidth. The borrow vector of the borrowing queue is checked to determine if the borrowing queue is permitted to consume the unused allocated bandwidth. [0017]FIG. 1 is a block diagram of a system 100 for distributing unused allocated bandwidth in accordance with an embodiment of the invention. System 100 includes a scheduler 102, four queues 110, 120, 130, and 140, and four registers 112, 122, 132, and 142 respectively associated with the four queues. The queues 110, 120, 130, and 140 are preferably first-in-first-out (FIFO) queues that identify packets for forwarding. When packets are forwarded, bandwidth is consumed. The amount of bandwidth a queue may consume depends upon the share of bandwidth allocated to the queue. [0018] In the embodiment of FIG. 1, the registers 112, 122, 132, and 142 contain borrow vectors that indicate from which queues, if any, borrowing is permitted. In an embodiment, the registers 112, 122, 132, and 142 are n−1 bit registers where n is the number of queues. Since n=4 in this embodiment, the registers 112, 122, 132, and 142 are preferably 3-bit registers. Each bit of the registers corresponds to one of the queues other than the queue with which the register is associated. For example, the register 112, which is associated with the queue 110, includes a first bit that corresponds to the queue 120, a second bit that corresponds to the queue 130, and a third bit that corresponds to the queue 140. These bits are referred to herein collectively as the borrow vector. [0019] The scheduler 102 preferably runs a first scheduling algorithm that identifies a first queue that is allowed to forward packets. If the first queue consumes all of its allocated bandwidth, then the first scheduling also is used to identify another queue that is permitted to forward packets. If the first queue does not consume its allocated bandwidth, the scheduler 102 is preferably configured to run a second scheduling algorithm for identifying at least one second queue that is permitted to consume the unused allocated bandwidth of the first queue. The scheduler 102 uses the appropriate borrow vectors to identify the second queue in a manner that is described below with reference to FIGS. 2 and 3. [0020]FIG. 2 depicts exemplary bandwidth allocations and borrow vector configurations in accordance with an embodiment of the invention. FIG. 2 serves to illustrate the maximum per queue bandwidths that result from allocating bandwidth to the queues 110, 120, 130, and 140 (FIG. 1) and setting the borrow vectors of registers 112, 122, 132, and 142 (FIG. 1), respectively. FIG. 2 includes three example bandwidth allocations and borrow vector configurations, wherein the queues are represented as A1 . . . A4, B1 . . . B4, and C1 . . . C4 for examples A, B, and C, respectively. For illustrative purposes, each queue includes an allocated bandwidth, a borrow vector (represented in square brackets), and a resulting maximum bandwidth. In the embodiment of FIG. 2, the allocated bandwidth and resulting maximum bandwidth are represented as a percentage of the total available bandwidth. The calculation of the resulting maximum bandwidth is explained below. [0021] In the first example (example A) of FIG. 2, queue A1 has an allocated bandwidth of 5% and an associated borrow vector of [0 0 0]. Since the borrow vector contains only 0's, A1 may not borrow unused allocated bandwidth from any of the other queues A2, A3, or A4. Since A1 may not borrow unused allocated bandwidth from any of the other queues, the resulting maximum bandwidth of A1 is the same as the allocated bandwidth of A1, which is 5%. A2, on the other hand, has an allocated bandwidth of 10% and an associated borrow vector of [1 0 0]. The associated borrow vector value of 1 in the first position indicates A2 may borrow unused allocated bandwidth from A1 and the values of 0 in the second and third positions indicated that A2 may not borrow unused allocated bandwidth from A3 or A4. Accordingly, the resulting maximum bandwidth for A2 is higher than the allocated bandwidth for A2. If A1 does not consume any of its allocated bandwidth, then A2 may be permitted to borrow all of A1's bandwidth. If A1 consumes part of its allocated bandwidth, A2 may be permitted to borrow some of the remaining unused bandwidth. Since A1 has 5% allocated bandwidth and A2 has 10% allocated bandwidth, the resulting maximum bandwidth for A2 is 5%+10%=15%. Whether A2 is actually permitted to borrow unused allocated bandwidth from A1 depends on whether A1 consumes all of its allocated bandwidth and on the results of a scheduling algorithm, as explained below. A3 has an allocated bandwidth of 20% and an associated borrow vector of [1 1 0]. The borrow vector indicates A3 may borrow unused allocated bandwidth from both A1 and A2. Since A1 has 5% allocated bandwidth, A2 has 10% allocated bandwidth, and A3 has 20% allocated bandwidth, the resulting maximum bandwidth for A3 is 5%+10%+20%=35%. A3 would be able to achieve this resulting maximum bandwidth if A1 and A2 did not consume any of their allocated bandwidth and no other queue uses this unconsumed bandwidth of A1 and A2. A4 has an allocated bandwidth of 65% and an associated borrow vector of [1 1 1]. The borrow vector indicates A4 may borrow unused allocated bandwidth from any of the other queues A1, A2, and A3. Accordingly, the resulting maximum bandwidth for A4 is the sum of allocated bandwidths of all of the queues, which is 100% of the allocated bandwidth in this example. [0022] In the second example (example B) of FIG. 2, queues B1, B2, B3, and B4 have the same allocated bandwidth as A1, A2, A3, and A4, respectively, but the associated borrow vectors of B1, B2, B3, and B4 are each [1 1 1]. Accordingly, the resulting maximum bandwidth for each B1, B2, B3, and B4 is the sum of all of their respective allocated bandwidths, which is 100% in this example. [0023] In the third example (example C) of FIG. 2, queues C1, C2, C3, and C4 have respective allocated bandwidths of 10%, 20%, 30%, and 40%. C1 has an associated borrow vector of [0 0 0], which means the resulting maximum bandwidth of C1 is the same as its allocated bandwidth, which is 10%. C2 has an associated borrow vector of [1 0 0], which means the resulting maximum bandwidth of C2 equals the allocated bandwidths of both C1 and C2, which is 10%+20%=30%. C3 has an associated borrow vector of [0 1 0], which means the resulting maximum bandwidth of C3 equals the allocated bandwidths of both C2 and C3, which is 20%+30%=50%. C4 has an associated borrow vector of [0 1 1], which means the resulting maximum bandwidth of C4 equals the allocated bandwidths of C2, C3, and C4, which is 20%+30%+40%=90%. [0024] Thus, a resulting maximum bandwidth is determined by setting the allocated bandwidth and borrow vector of each queue. Moreover, rate shaping is possible by selecting borrow vector values for a given queue based on the allocated bandwidths of the other queues. [0025]FIG. 3 is a flowchart 300 of a method for distributing unused allocated bandwidth in accordance with an embodiment of the invention. FIG. 3 serves to illustrate the steps that are taken for one or more queues to borrow unused allocated bandwidth from a first queue. In an embodiment, a scheduling algorithm first identifies the queue from which packets should be forwarded. If the identified queue has consumed its allocated bandwidth, then the scheduling algorithm (or a second scheduling algorithm) identifies at least one other queue (a borrowing queue) to consume the unused allocated bandwidth. The borrow vector of the borrowing queue is checked to determine if the borrowing queue is permitted to consume the unused allocated bandwidth. It should be noted that prior to the start of the flowchart 300, the queues have been allocated bandwidth and the borrow vectors associated with each queue have been set. [0026] The flowchart 300 starts with a scheduling algorithm running to identify a queue, Qi, that is allowed to forward packets at step 302. The identification of Qi may be by round robin selection, strict priority (where each of the queues have a relative priority), or some other scheme. At decision point 304, it is determined whether Qi has packets. If so, Qi is allowed to consume up to the allocated bandwidth of Qi by forwarding packets at step 306 and the flowchart 300 continues to decision point 308. If not, at decision point 308, it is determined whether Qi has unused allocated bandwidth. At decision point 308, if Qi does not have unused allocate bandwidth, the scheduling algorithm is run to identify a new Qi. If Qi does have unused allocated bandwidth (308-Y), then at step 310 a next queue, Qnext, is identified. The technique used to identify Qnext may be by round robin, strict priority, using information associated with Qi, or some other scheme. At decision point 312, a determination is made as to whether Qnext has packets to forward. If Qnext has packets to forward, then at step 314 the borrow vector of Qnext is checked to determine whether borrowing unused allocated bandwidth from Qi is permitted. If Qnext does not have packets to forward (312-N), then at decision point 316 it is determined whether Qnext is the last queue. If Qnext is the last queue, then any new Qnext that would be identified at step 310 would have been previously identified and given the opportunity to consume the unused allocated bandwidth of Qi. Accordingly, at step 322 it is determined whether Qi has unused allocated bandwidth. If not, the scheduling algorithm is run to identify a new Qi at step 302 and the flowchart 300 continues as described previously. Otherwise, if Qi has unused allocated bandwidth, at decision point 304, a determination is made as to whether Qi has packets and the flowchart 300 continues as described previously. If Qnext is not the last queue, then a new Qnext is identified at step 310. At decision point 318, a determination is made as to whether Qnext is permitted to borrow the unused allocated bandwidth of Qi. If borrowing is not permitted, then at step 316 it is determined whether Qnext is the last queue and the flowchart 300 continues as described previously. Otherwise, if borrowing is permitted, then at step 320 Qnext is allowed to forward a packet. At decision point 322, a determination is made as to whether Qnext has consumed all of the unused allocated bandwidth and the flowchart 300 continues as described previously. [0027]FIG. 4 depicts a flowchart 400A and a flowchart 400B of methods for distributing unused allocated bandwidth in accordance with embodiments of the invention. The flowchart 400A starts at step 402 with allocating bandwidth between a plurality of queues. This allocation may be accomplished using weighted fair queuing (WFQ), credit token, or some other method of allocating bandwidth between contending queues. This allocation may also include designating some bandwidth as idle, which has the effect of limiting the amount of bandwidth allocated to the queues to some amount of available bandwidth that is less than the total amount of bandwidth that could be utilized for an output. The flowchart 400A continues at step 404 with setting a borrow vector for a queue of the plurality of queues that indicates a subset of the plurality of queues from which borrowing unused allocated bandwidth is permitted. The subset could include every queue of the plurality of queues or no queue of the plurality of queues (e.g., the subset could be an empty set). Some examples of borrow vectors are illustrated in FIG. 2 for a system with four queues. [0028] The flowchart 400B starts at step 406 with consuming a portion of bandwidth of an output with packets from a plurality of queues according to respective bandwidths allocated to the queues, leaving unused allocated bandwidth of a first queue when the first queue does not exhaust its allocated bandwidth. A determination as to whether the first queue has consumed substantially all of its allocated bandwidth may be made. The flowchart 400B continues at step 408 with allowing a second queue to forward packets using the unused allocated bandwidth if a borrow vector associated with the second queue indicates that the second queue is permitted to use bandwidth allocated to the first queue. The second queue may be identified using a scheduling algorithm. Preferably, the borrow vector indicates whether the second queue is permitted to use bandwidth allocated to each of the plurality of queues other than the second queue. By checking the position of the borrow vector that corresponds to the first queue, it may be determined that the second queue is permitted to use unused allocated bandwidth. In some cases, the second queue does not use up the unused allocated bandwidth. Accordingly, a scheduling algorithm may identify a third queue and let the third queue forward packets using the unused allocated bandwidth if the borrow vector associated with the third queue indicates the third queue is permitted to borrow from the first queue. [0029]FIG. 5 is a block diagram of a system 500 for distributing unused allocated bandwidth in accordance with an embodiment of the invention. System 500 includes a queue 502, a borrow vector 504, and an AND gate 506. A �Qnext has packets to forward� flag is an output of the queue 502. When it has been determined that Qi has not used all of its allocated bandwidth and unused bandwidth is therefore available, and queue 502 has been selected as the queue that may forward packets using the unused allocated bandwidth, such as by using the methods described above, the AND gate 506 ANDs the �Qnext has packets to forward� flag and the bit associated with Qi. The output of the AND gate is a �Qnext may forward packets� flag, which enables Qnext. In an embodiment, Qnext has packets to forward means Qnext is not empty. [0030] Allocated bandwidth is expressed herein as a percentage of the total available bandwidth, but it could be expressed in some other terms. In addition, allocating the bandwidth in the designated percentages could be accomplished with, for example, WFQ, credit bucket, token bucket, or any other bandwidth allocation technique. [0031] In one embodiment, the method steps described above are embodied in a computer-readable media as computer instruction code. It shall be appreciated that not all methods steps described must be performed, nor must they be performed in the order stated. [0032] Although specific embodiments of the invention have been described and illustrated, the invention is not to be limited to the specific forms or arrangements of parts as described and illustrated herein. The invention is limited only by the claims. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7489690 *Nov 16, 2005Feb 10, 2009Cellco PartnershipIntegrated packet latency aware QoS scheduling algorithm using proportional fairness and weighted fair queuing for wireless integrated multimedia packet servicesUS7856501Nov 7, 2008Dec 21, 2010Sony Computer Entertainment Inc.Network traffic prioritizationUS7908393Nov 7, 2008Mar 15, 2011Sony Computer Entertainment Inc.Network bandwidth detection, distribution and traffic prioritizationUS8085781Dec 23, 2005Dec 27, 2011Aspera, Inc.Bulk data transferUS8156534Feb 24, 2009Apr 10, 2012Microsoft CorporationSeamless digital channel changingUS8214707Jun 26, 2007Jul 3, 2012Aspera, Inc.Method and system for reliable data transferUS8397269 *Aug 13, 2002Mar 12, 2013Microsoft CorporationFast digital channel changingUS8583977 *Jul 2, 2012Nov 12, 2013Aspera, Inc.Method and system for reliable data transferUS8824483Dec 7, 2012Sep 2, 2014International Business Machines CorporationDelivering multicast frames to aggregated link trunks in a distributed switchUS20120272115 *Jul 2, 2012Oct 25, 2012Michelle Christine MunsonBulk data transferUS20130242985 *Mar 14, 2012Sep 19, 2013International Business Machines CorporationMulticast bandwidth multiplication for a unified distributed switchUS20130242993 *Dec 7, 2012Sep 19, 2013International Business Machines CorporationMulticast bandwidth multiplication for a unified distributed switchUS20140181610 *Nov 11, 2013Jun 26, 2014Aspera, Inc.Bulk data transferWO2006071866A2 *Dec 23, 2005Jul 6, 2006Aspera IncBulk data transferWO2009073312A2 *Nov 10, 2008Jun 11, 2009Sony Comp Entertainment IncNetwork bandwidth detection, distribution and traffic prioritization* Cited by examinerClassifications U.S. Classification370/395.41International ClassificationH04L12/56Cooperative ClassificationH04L47/525, H04L12/5693European ClassificationH04L12/56K, H04L47/52CLegal EventsDateCodeEventDescriptionMar 7, 2013ASAssignmentFree format text: SECURITY INTEREST;ASSIGNOR:ALCATEL-LUCENT USA INC.;REEL/FRAME:030510/0627Owner name: CREDIT SUISSE AG, NEW YORKEffective date: 20130130Sep 19, 2011FPAYFee paymentYear of fee payment: 4Feb 1, 2008ASAssignmentOwner name: LUCENT TECHNLOGIES, INC., NEW JERSEYFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:RIVERSTONE NETWORKS, INC.;REEL/FRAME:020445/0114Effective date: 20060427Mar 20, 2003ASAssignmentOwner name: RIVERSTONE NETWORKS, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LODHA, SANDEEP;ASTRESH, DEEPAK;NARAYANAN, RAJESH;AND OTHERS;REEL/FRAME:013855/0979Effective date: 20030212RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google