|Publication number||US6999414 B2|
|Application number||US 09/783,311|
|Publication date||Feb 14, 2006|
|Filing date||Feb 15, 2001|
|Priority date||Oct 27, 1999|
|Also published as||US7573816, US7697426, US20020154655, US20060088057, US20070030807, US20100020683|
|Publication number||09783311, 783311, US 6999414 B2, US 6999414B2, US-B2-6999414, US6999414 B2, US6999414B2|
|Inventors||Ajay Chandra V. Gummalla, Dolors Sala|
|Original Assignee||Broadcom Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (37), Non-Patent Citations (8), Referenced by (40), Classifications (92), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application claims the benefit of the following provisional applications:
U.S. Provisional Application Ser. No. 60/182,470, entitled “Intelligent Silence Suppression,” filed Feb. 15, 2000, by Gummalla et al., (incorporated by reference in its entirety herein).
U.S. Provisional Application Ser. No. 60/247,188, entitled “A Local Scheduling Mechanism for Cable Modems,” filed Nov. 9, 2000, by Sala et al., (incorporated by reference in its entirety herein).
U.S. Provisional Application Ser. No. 60/254,415, entitled “A Local Scheduling Mechanism for Cable Modems,” filed Dec. 8, 2000, by Sala et al., (incorporated by reference in its entirety herein).
U.S. Provisional Application Ser. No. 60/262,201, entitled “Voice Scheduling Algorithms,” filed Jan. 17, 2001, by Sala et al., (incorporated by reference in its entirety herein).
U.S. Provisional Application Ser. No. 60/262,203, entitled “Concatenation of Requests at CMTS,” filed Jan. 17, 2001, by Sala et al., (incorporated by reference in its entirety herein).
This application is a continuation-in-part of U.S. patent Ser. No. 09/427,792, entitled “System and Method for Multiplexing Data from Multiple Sources,” filed Oct. 27, 1999, by Limb et al., now U.S. Pat. No. 6,804,251 (incorporated by reference in its entirety herein).
This application is related to the following non-provisional applications, all having the same filing date as the present application:
“Method, System and Computer Program Product for Scheduling Upstream Communications”, U.S. patent Ser. No. 09/783,404, by Gummalla et al. (incorporated by reference in its entirety herein).
“Voice Architecture For Transmission Over A Shared, Contention Based Medium,” U.S. patent Ser. No. 09/785,020, by Gummalla et al. (incorporated by reference in its entirety herein).
“System and Method for Suppressing Silence in Voice Traffic over an Asynchronous Communication Medium,” U.S. patent Ser. No. 09/783,405, by Gummalla et al. (incorporated by reference in its entirety herein).
“Cable Modem System and Method for Specialized Data Transfer,” U.S. patent Ser. No. 09/783,403, by Bunn et al., (incorporated by reference in its entirety herein).
1. Field of the Invention
The present invention is generally related to increasing the efficiency of providing requested bandwidth to a data provider via asynchronous communication mediums.
2. Background Art
The importance to the modern economy of rapid data access and exchange cannot be overstated. This explains the exponentially increasing popularity of the data access and exchange via cable networks (including coaxial cable or Hybrid fiber coaxial cable), the Internet, intranets, wireless networks, satellites and so forth (i.e., communication mediums). Rapid data access and exchange is partly dependent upon how efficiently bandwidth is allocated to a data provider in order for the data provider to transfer the requested data to a user via one of the communication mediums mentioned above.
One very desirable solution for rapid data access and exchange is via cable networks and cable modems. Cable modems provide asynchronous communications on cable networks. In general, a user connects a cable modem to the TV outlet for his or her cable TV, and the cable TV operator connects a cable modem termination system (“CMTS”) in the operator's headend. The CMTS is a central device for connecting the cable network to a data network like the Internet. The CMTS is a central distribution point for a cable system. Data flows “downstream” from the CMTS to the cable modem (i.e., downstream communication). Alternatively, data flows “upstream” from the cable modem to the CMTS (i.e., upstream communication).
A common cable modem standard today is the Data Over Cable Service Interface Specification (“DOCSIS”). DOCSIS defines technical specifications for both cable modems and CMTS. DOCSIS downstream communication is quite restrictive in the way the control information is conveyed to the data provider (e.g., cable modem) via a DOCSIS CMTS scheduler. What is needed is to override the CMTS scheduler of DOCSIS and provide a CMTS scheduler that reduces the overhead of bandwidth grants via downstream communication by providing flexibility in the allocation of the bandwidth.
The present invention is a system and method for combining requests for bandwidth by a data provider for transmission of data over an asynchronous communication medium. An embodiment of the method comprises the first step of receiving bandwidth requests from one or more data providers, each bandwidth request having a data provider identifier, a priority identifier, and the amount of required bandwidth. The next step is storing each of the bandwidth requests in a data structure so as to maintain the order in which the bandwidth requests were received. The third step is, based on the priority identifier and the order of each bandwidth request, scheduling each the bandwidth request in an order to be serviced. The next step is combining each of the bandwidth requests having the same the data provider identifier into a data burst bandwidth. The final step is granting the data burst bandwidth to the data provider over the asynchronous communication medium.
In another embodiment of the method of the present invention, the first step involves receiving bandwidth requests from one or more data providers, each bandwidth request having a data provider identifier, a priority identifier, and the amount of required bandwidth. The second step is combining, by data provider identifier and priority identifier, the amount of bandwidth required to represent a data burst bandwidth. The fourth step is, based on one or more quality of service parameters (which varies from priority to priority), scheduling each the data burst bandwidth in an order to be serviced. The final step involves granting the data burst bandwidth to the data provider over the asynchronous communication medium.
An embodiment of the system comprises a headend and a scheduler that are coupled together. The scheduler receives bandwidth requests from one or more data providers, each bandwidth request having a data provider identifier, a priority identifier, and the amount of required bandwidth. The scheduler then stores each of the bandwidth requests in a data structure so as to maintain the order in which the bandwidth requests were received. Then the scheduler schedules each the bandwidth request in an order to be serviced based on the priority identifier and the order of each bandwidth request. Next, the scheduler combines each of the bandwidth requests having the same the data provider identifier into a data burst bandwidth. Finally, the headend grants the data burst bandwidth to the data provider over the asynchronous communication medium.
Another embodiment of the system also includes a headend and a scheduler coupled together. Here, the scheduler receives bandwidth requests from one or more data providers, each bandwidth request having a data provider identifier, a priority identifier, and the amount of required bandwidth. The scheduler then combines, by data provider identifier and priority identifier, the amount of bandwidth required to represent a data burst bandwidth. The scheduler, based on one or more quality of service parameters (which varies from priority to priority), schedules each the data burst bandwidth in an order to be serviced. Finally, headend grants the data burst bandwidth to the data provider over the asynchronous communication medium.
The present invention will be described with reference to the accompanying drawings, wherein:
A. Overview of the Invention
For illustration purposes, the present invention is described in terms of being utilized with a cable network. It should be understood that the present invention is not limited to use with a cable network. In fact, the present invention may be used with any communication medium, including but not limited to, the Internet, intranets, fiber optic networks, wireless networks and satellites.
Data in the present invention includes any type of information. This includes, but is not limited to, digital, voice, video, audio, etc.
B. System Architecture Overview
In general, cable modem 104 forwards or provides data via asynchronous communications on cable networks. Cable modem 104 receives data from a user that needs to be transferred via a cable network. In order to do this, cable modem 104 requests that CMTS 102 grant to it the necessary bandwidth.
As mentioned, cable modem 104 receives data from a user to be transferred via a cable network. Different types of data require different modes of transfer since the importance of timing is different with different types of data. For example, voice data cannot tolerate delays in its transfer. Alternatively, the type of data involved in web surfing can tolerate delays in its transfer.
In order to ensure the importance of timing is maintained, cable modem 104 assigns different priority identifiers to different types of data. The higher the priority a data has, the less of a delay that type of data will experience in its transfer via the cable network. Thus, voice data would be assigned a priority identifier with a higher priority than data involved in web surfing.
Cable modem scheduler 116 is coupled to cable modem 104. Cable modem scheduler 116 is described in detail in related non-provisional application, entitled “Method, System and Computer Program Product for Scheduling Upstream Communications”, (Ser. No. 09/783,404), filed concurrently with the present invention (incorporated herein by reference in its entirety). In general, cable modem scheduler 116 is responsible for multiplexing the internal traffic, (i.e., requesting the necessary bandwidth that cable modem 116 needs to transfer its current types of data). Cable modem scheduler 116 must take into consideration the different priorities given to the current data to be transferred and to request bandwidth from CMTS 102 accordingly.
As stated above, DOCSIS is a common cable modem standard used today. DOCSIS provides standard centralized scheduling decisions that do not allow for flexibility in terms of deciding when cable modem 104 requests bandwidth from CMTS 102 in order to transfer its current data. Cable modem scheduler 116 defines an architecture that overrules this DOCSIS standard in a seamless manner. Some of the main differences between the DOCSIS standard and cable modem scheduler 116 are described next.
One main difference between the DOCSIS standard and cable modem scheduler 116 includes the decoupling of the request phase with the grant phase (i.e., grants of bandwidth received from CMTS 102). Here, cable modem scheduler 116 uses granted bandwidth as they are received regardless of their size and priority specification, thereby ignoring the DOCSIS standard. Cable modem scheduler 116 ignores the priority id of the granted bandwidth. This means that cable modem scheduler 116 does not have to use the granted bandwidth in the same order in which it was requested. It addition, piggyback requests may be separate requests for bandwidth instead of extended header as done in the DOCSIS standard. How piggyback requests are handled by the present invention are described in detail in related non-provisional application, entitled “Method, System and Computer Program Product for Scheduling Upstream Communications”, (Ser. No. 09/783,404). Here, it is important to note that piggybacks requests are treated as separate requests for bandwidth and may or may not be given a priority identifier. In an embodiment, the present designs voice data the highest priority, piggyback requests have the second highest priority and other types of data (including data required for web surfing) is given the lowest priority.
Therefore, cable modem scheduler 116 sends bandwidth requests to CMTS 102 via upstream communication 108. At a high level, each bandwidth request may include three fields. The three fields are a data provider identifier, a priority identifier, and the amount of required bandwidth. In an embodiment of the present invention, the bandwidth request does not include the data provider identifier as a field. Here, the data provider identifier is implicit (e.g. piggyback request. These three fields will be briefly described next.
Each cable modem 104 has a unique data provider identifier. CMTS 102 uses this identifier to grant the requested bandwidth to cable modem 104. Priority identifiers indicate the priority given to the data and thus indicating the type of data that will be transferred over the cable network via the granted bandwidth. Finally, the last field is value indicating the amount of required bandwidth needed to transfer the data, CMTS 102. CMTS scheduler 110 and data structure 112 will not be described.
CMTS 102 is a central device for connecting the cable network to a data network. CMTS scheduler 102 is a bandwidth manager. CMTS scheduler 102, as a bandwidth manager, decides how to grant available bandwidth according to the current bandwidth requests. This grant is done via downstream communication 106 in such as way as to reduce overhead. This ability to decide how to grant available bandwidth provides flexibility. This flexibility allows the present invention to reduce the overhead involved in granting bandwidth to cable modem 104 via downstream communication. Data structure 112 is used to organized the received bandwidth requests in such as way as to take into consideration the type of data (via the priority identifiers) and the order in which the requests were received.
As described above, the way in which the DOCSIS CMTS scheduler grants bandwidth is quite restrictive, thus creating unnecessary overhead in downstream communication. The details of how CMTS scheduler 110 grants bandwidth to cable modem 104 so that to decrease overhead will be described in detail below. The overhead in each granted bandwidth will be described next with reference to
C. Granted Bandwidth Overhead
Overhead 204 may be referred to as the physical layer overhead. Regardless of the size of granted bandwidth 202, overhead 204 uses approximately the same amount of bytes. Where the preamble and guard band are typically fixed in size, the FEC is a variable size that depends on the amount of bandwidth. Therefore, the larger the granted bandwidth, the greater the efficiency. However, larger granted bandwidths mean greater end-to-end delay experienced by a voice call, for example. Thus, when granting bandwidth, end-to-end delay versus gained efficiency must be taken into consideration.
Different systems may reserve different amount of bytes for overhead 204. How the present invention combines bandwidth requests from the same cable modem 104 to create a single data burst bandwidth is described next.
D. Combination of Bandwidth Grants
As mentioned above, cable modem scheduler 116 may send different bandwidth requests to CMTS 102, including but not limited to, voice, piggyback and data for activities such as web surfing. Thus, at any given time, CMTS 102 may have more than one request for the same cable modem. This is especially true since cable modem scheduler 104 piggybacks requests as often as possible. These requests may have different priority identifiers values or the same priority identifier value for data that has arrived at CMTS 102 at different times.
A goal of the present invention is to combine all pending bandwidth requests from the same cable modem into one data burst bandwidth request. Here, instead of individual requests being granted which would require physical overhead for each grant, the present invention reduces the physical over to one for all of the individual requests by combining them. This can be accomplished by the present invention partly because there is a decoupling of the request phase (i.e., bandwidth requests from cable modem 104) with the grant phase (i.e., grants of bandwidth received from CMTS 102), as mentioned above. CMTS scheduler 110 needs to take into consideration end-to-end delay verses the gained efficiency.
In step 304, CMTS scheduler 110 combines one or more bandwidths requests from the same cable modem 104 to create a single data burst bandwidth. Control then passes to step 306.
In step 306, CMTS 102 grants the data burst bandwidth to the appropriate cable modem 104 via downstream communication 106. The flowchart in
As illustrated in
Each bandwidth request is indicated as (n,m), where n is the data provider identifier and m is the amount of required bandwidth. As described above, each bandwidth request includes at least three fields, including the data provider identifier, the priority identifier, and the amount of required bandwidth. For example, bandwidth request 510 has a priority identifier value of 0, the cable modem 104 who sent the request has the data provider identifier of 1 and it is requesting 5 units of bandwidth. In addition, bandwidth request 510 arrived at CMTS 102 before bandwidth request 512, which in turn arrived before bandwidth request 514, as indicated by their positions in queue 502. It is important to note that bandwidth request 516 may arrive at CMTS 102 before bandwidth request 514, but bandwidth request 514 is still likely to be granted bandwidth first due to it having a higher priority identifier.
Also illustrated by
In step 404, CMTS scheduler 110 schedules each bandwidth request stored in data structure 112 in an order to be serviced by the present invention. Here, bandwidth requests are scheduled to be serviced based on priority identifiers (i.e., type of data) and the order in which the requests for bandwidth were received. An example scheduling that is based on the example data structure shown in
In step 406, CMTS scheduler 110 utilizes schedule 602 to combine bandwidth requests from the same cable modem 104 to create a single data burst bandwidth for each cable modem 104 (i.e., data provider identifier). This is illustrated in
At this point, data burst bandwidths 702–706 are ready to be granted to their appropriate cable modems as accomplished in step 306 (
As mentioned above, bandwidth requests in this embodiment are scheduled to be serviced based on various quality of service parameters.
In step 804, CMTS scheduler 110 schedules each data burst bandwidth based on quality of service parameters. Quality of service parameters include efficiency of transmission and transfer delay tolerance. As stated above, different types of data require different modes of transfer since the importance of timing is different with different types of data. For example, voice data cannot tolerate delays in its transfer. Alternatively, the type of data involved in web surfing can tolerate delays in its transfer.
The priority identifier specified in the request is not significantly important since the cable modem scheduler does not use it 104 when transferring data via the bandwidth. For consistency in all cases is desired, the present invention may specify that the priority identifier of the data burst bandwidth gets the lowest priority that contributes to the accumulated sum. Also note that this embodiment may choice to incorporate scheduling, as shown in
E. Example Environment of the Present Invention
CMTS 102, CMTS scheduler 110 and cable modem scheduler 116 may be implemented using computer 1000 as shown in
The present invention may be implemented using hardware, software or a combination thereof and may be implemented in a computer system or other processing system. In fact, in one embodiment, the invention is directed toward one or more computer systems capable of carrying out the functionality described herein. The computer system 1000 includes one or more processors, such as processor 1004. The processor 1004 is connected to a communication bus 1006. Various software embodiments are described in terms of this example computer system. After reading this description, it will become apparent to a person skilled in the relevant art how to implement the invention using other computer systems and/or computer architectures.
Computer system 1000 also includes a main memory 1008, preferably random access memory (RAM), and can also include a secondary memory 1010. The secondary memory 1010 can include, for example, a hard disk drive 1012 and/or a removable storage drive 1014, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. The removable storage drive 1014 reads from and/or writes to a removable storage unit 1018 in a well known manner. Removable storage unit 1018, represents a floppy disk, magnetic tape, optical disk, etc. which is read by and written to by removable storage drive 1014. As will be appreciated, the removable storage unit 1018 includes a computer usable storage medium having stored therein computer software and/or data.
In alternative embodiments, secondary memory 1010 may include other similar means for allowing computer programs or other instructions to be loaded into computer system 1000. Such means can include, for example, a removable storage unit 1022 and an interface 1020. Examples of such can include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM, or PROM) and associated socket, and other removable storage units 1022 and interfaces 1020 which allow software and data to be transferred from the removable storage unit 1018 to computer system 1000.
Computer system 1000 can also include a communications interface 1024. Communications interface 1024 allows software and data to be transferred between computer system 1000 and external devices. Examples of communications interface 1024 can include a modem, a network interface (such as an Ethernet card), a communications port, a PCMCIA slot and card, etc. Software and data transferred via communications interface 1024 are in the form of signals which can be electronic, electromagnetic, optical or other signals capable of being received by communications interface 1024. These signals 1026 are provided to communications interface via a channel 1028. This channel 1028 carries signals 1026 and can be implemented using wire or cable, fiber optics, a phone line, a cellular phone link, an RF link and other communications channels.
In this document, the terms “computer program medium” and “computer usable medium” are used to generally refer to media such as removable storage device 1018, a hard disk installed in hard disk drive 1012, and signals 1026. These computer program products are means for providing software to computer system 1000.
Computer programs (also called computer control logic) are stored in main memory and/or secondary memory 1010. Computer programs can also be received via communications interface 1024. Such computer programs, when executed, enable the computer system 1000 to perform the features of the present invention as discussed herein. In particular, the computer programs, when executed, enable the processor 1004 to perform the features of the present invention. Accordingly, such computer programs represent controllers of the computer system 1000.
In an embodiment where the invention is implemented using software, the software may be stored in a computer program product and loaded into computer system 1000 using removable storage drive 1014, hard drive 1012 or communications interface 1024. The control logic (software), when executed by the processor 1004, causes the processor 1004 to perform the functions of the invention as described herein.
In another embodiment, the invention is implemented primarily in hardware using, for example, hardware components such as application specific integrated circuits (ASICs). Implementation of the hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant art(s). In yet another embodiment, the invention is implemented using a combination of both hardware and software.
While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail may be made therein without departing from the spirit and scope of the invention. This is especially true in light of technology and terms within the relevant art(s) that may be later developed. Thus, the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4534024||Dec 2, 1982||Aug 6, 1985||At&T Bell Laboratories||System and method for controlling a multiple access data communications system including both data packets and voice packets being communicated over a cable television system|
|US4712210||Sep 7, 1984||Dec 8, 1987||Lee Data Corporation||Signal conversion circuit for interconnecting coaxial cable and a twisted pair|
|US5341374||Mar 1, 1991||Aug 23, 1994||Trilan Systems Corporation||Communication network integrating voice data and video with distributed call processing|
|US5421030||Sep 17, 1991||May 30, 1995||Com21, Inc.||Communications system and method for bi-directional communications between an upstream control facility and downstream user terminals|
|US5425027||Jan 4, 1993||Jun 13, 1995||Com21, Inc.||Wide area fiber and TV cable fast packet cell network|
|US5469495||Dec 16, 1994||Nov 21, 1995||U S West Advanced Technologies, Inc.||Method and apparatus for delivering secured telephone service in hybrid coaxial cable network|
|US5515379||Oct 18, 1993||May 7, 1996||Motorola, Inc.||Time slot allocation method|
|US5539449||May 3, 1993||Jul 23, 1996||At&T Corp.||Integrated television services system|
|US5570355||Nov 17, 1994||Oct 29, 1996||Lucent Technologies Inc.||Method and apparatus enabling synchronous transfer mode and packet mode access for multiple services on a broadband communication network|
|US5606561||Jul 28, 1995||Feb 25, 1997||Motorola, Inc.||Method, device/microprocessor, and computer software for providing packet fragmentation for fair, efficient downlink transmission with low packet delay|
|US5631908||Mar 28, 1995||May 20, 1997||Digital Equipment Corporation||Method and apparatus for generating and implementing smooth schedules for forwarding data flows across cell-based switches|
|US5742592||Sep 1, 1995||Apr 21, 1998||Motorola, Inc.||Method for communicating data in a wireless communication system|
|US5756280||Oct 3, 1995||May 26, 1998||International Business Machines Corporation||Multimedia distribution network including video switch|
|US5850400||Apr 27, 1995||Dec 15, 1998||Next Level Communications||System, method, and apparatus for bidirectional transport of digital data between a digital network and a plurality of devices|
|US5926478||Apr 3, 1997||Jul 20, 1999||Ericsson, Inc.||Data transmission over a point-to-multipoint optical network|
|US5963557||Apr 11, 1997||Oct 5, 1999||Eng; John W.||High capacity reservation multiple access network with multiple shared unidirectional paths|
|US5982780||Dec 26, 1996||Nov 9, 1999||Dynarc Ab||Resource management scheme and arrangement|
|US6055268||Jun 20, 1996||Apr 25, 2000||Texas Instruments Incorporated||Multimode digital modem|
|US6185224||Jan 12, 1999||Feb 6, 2001||Georgia Tech Research Corporation||System and method for communicating data in a cable network|
|US6259695||Jul 28, 1999||Jul 10, 2001||Synchrodyne Networks, Inc.||Packet telephone scheduling with common time reference|
|US6359901 *||Sep 2, 1998||Mar 19, 2002||General Dynamics Decision Systems, Inc.||Method and apparatus for asynchronous adaptive protocol layer tuning|
|US6421355 *||Jun 29, 1998||Jul 16, 2002||Texas Instruments Incorporated||Methods and linecard device for allocating multiple timeslots over digital backplane|
|US6438630 *||Oct 6, 1999||Aug 20, 2002||Sun Microsystems, Inc.||Scheduling storage accesses for multiple continuous media streams|
|US6463484 *||Jul 9, 1999||Oct 8, 2002||C-Sierra, Inc.||Egress port scheduling using memory efficient request storage|
|US6546017 *||Mar 5, 1999||Apr 8, 2003||Cisco Technology, Inc.||Technique for supporting tiers of traffic priority levels in a packet-switched network|
|US6580730||Jul 24, 2000||Jun 17, 2003||Intel Corporation||Versatile time division multiple access slot assignment unit|
|US6628609 *||Apr 30, 1998||Sep 30, 2003||Nortel Networks Limited||Method and apparatus for simple IP-layer bandwidth allocation using ingress control of egress bandwidth|
|US6724772 *||Sep 4, 1998||Apr 20, 2004||Advanced Micro Devices, Inc.||System-on-a-chip with variable bandwidth|
|US6804251||Oct 27, 1999||Oct 12, 2004||Broadcom Corporation||System and method for multiplexing data from multiple sources|
|US6917614 *||Sep 17, 1999||Jul 12, 2005||Arris International, Inc.||Multi-channel support for virtual private networks in a packet to ATM cell cable system|
|EP0573739A2 *||Mar 12, 1993||Dec 15, 1993||Roke Manor Research Limited||Improvements to data transmission systems|
|EP0774848A2||Nov 14, 1996||May 21, 1997||Xerox Corporation||Method for providing integrated packet services over a shared-media network|
|EP0829986A1||Aug 19, 1997||Mar 18, 1998||Lucent Technologies Inc.||System for improving data throughput of a TCP/IP Network connection with slow return channel|
|EP0844803A2||Oct 29, 1997||May 27, 1998||AT&T Corp.||Asynchronous transfer mode integrated access service|
|EP0912016A2||Oct 13, 1998||Apr 28, 1999||Lucent Technologies Inc.||Method for access control in a multiple access system for communications networks|
|WO1999018718A1||Sep 29, 1998||Apr 15, 1999||Thomson Consumer Electronics||Multimedia decoder and bi-directional broadcast communication system|
|WO1999030449A1||Sep 30, 1998||Jun 17, 1999||Com21 Inc||An apparatus for upstream signal selection|
|1||"Radio Frequency Interface Specification SP-RFlv1.1-l02-990731," Data-Over-Cable Service Interface Specifications, Jul. 31, 1999, retrieved from the Internet on Oct. 23, 2001:<URL:http://www.tconl.com/ikleens/DOCSIS.pdf>, pp. i-iv, 132-139 and 291-296.|
|2||Copy of International Search Report for Appl. No. PCT/US01/04820 issued Sep. 27, 2001, 8 pages.|
|3||Copy of International Search Report issued Nov. 8, 2001, for Appln. No. PCT/US01/04841, 5 pages.|
|4||Copy of International Search Report issued Nov. 8, 2001, for Appln. No. PCT/US01/04904,4 pages.|
|5||Copy of International Search Report issued Sep. 28, 2001, for Appln. No. PCT/US01/04819, 7 pages.|
|6||John O. Limb and Dolors Sala, A Protocol for Efficient Transfer of Data over Hybrid Fiber/Coax Systems, article in IEEE/ACM Transactions on Networking, vol. 5, No. 6, pp. 872-881, Dec. 1997.|
|7||Limb, J. et al, "An Access Protocol to Support Multimedia Traffic Over Hybrid Fiber/Coax Systems", Proceedings of the International Workshop on Community Networking Integrated Multimedia Services to the Home, Jun. 20, 1995, pp. 35-40.|
|8||Sala, D. et al., "Adaptive Control Mechanism for Cable Modem MAC Protocols," Proceedings of the IEEE INFOCOM, IEEE, vol. 3, Mar. 29, 1988, pp. 1392-1399.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7272141 *||Feb 28, 2002||Sep 18, 2007||At&T Bls Intellectual Property, Inc.||System and method for serializing bulk virtual circuit connection requests|
|US7571250 *||Jan 14, 2005||Aug 4, 2009||Microsoft Corporation||Method and apparatus for distributing messages|
|US7583897 *||Mar 27, 2006||Sep 1, 2009||Enablence Usa Fttx Networks Inc.||Optical network system and method for supporting upstream signals propagated according to a cable modem protocol|
|US7613161||Oct 20, 2006||Nov 3, 2009||Broadcom Corporation||System for suppressing silence in voice traffic over a wireless communication medium|
|US7613167||Sep 27, 2001||Nov 3, 2009||Broadcom Corporation||Method and system for upstream priority lookup at physical interface|
|US7616620||Nov 18, 2005||Nov 10, 2009||Broadcom Corporation||Method for suppressing silence in voice traffic over a wireless communication medium|
|US7697543||Aug 4, 2004||Apr 13, 2010||Broadcom Corporation||System and method for multiplexing data from multiple sources|
|US7733912||Jun 12, 2007||Jun 8, 2010||Broadcom Corporation||Allocation of packets in a wireless communication system|
|US7739393 *||Jan 28, 2002||Jun 15, 2010||Cisco Technology, Inc.||Apparatus and method for restoring traffic during failover in a cable head end|
|US7769047||Jul 20, 2007||Aug 3, 2010||Broadcom Corporation||Methods for specialized data transfer in a wireless communication system|
|US7773631||Jul 20, 2007||Aug 10, 2010||Broadcom Corporation||Specialized data transfer in a wireless communication system|
|US7873067 *||Dec 29, 2006||Jan 18, 2011||Alcatel-Lucent Usa Inc.||Adaptive method of floor control with fast response time and fairness in communication network|
|US7912066||Jun 12, 2007||Mar 22, 2011||Broadcom Corporation||Methods of allocating packets in a wireless communication system|
|US7940774||Aug 28, 2007||May 10, 2011||Broadcom Corporation||Method for scheduling wireless communications|
|US7953063||Oct 5, 2009||May 31, 2011||Broadcom Corporation||System and method for suppressing silence in voice traffic over a wireless communication medium|
|US7990952||Aug 17, 2007||Aug 2, 2011||Broadcom Corporation||Method for upstream priority lookup at physical interface within a wireless device|
|US8488629||Aug 6, 2010||Jul 16, 2013||Broadcom Corporation||Specialized data transfer in a wireless communication system|
|US8654775||Mar 21, 2011||Feb 18, 2014||Broadcom Corporation||Methods of allocating packets in a wireless communication system|
|US8654776||May 5, 2011||Feb 18, 2014||Broadcom Corporation||Scheduling wireless communications|
|US20020157101 *||Jul 12, 2001||Oct 24, 2002||Schrader Joseph A.||System for creating and delivering enhanced television services|
|US20030058837 *||Sep 27, 2001||Mar 27, 2003||Lisa Denney||Method and system for upstream priority lookup at physical interface|
|US20040034871 *||Jan 28, 2002||Feb 19, 2004||Cisco Technology, Inc.||Apparatus and methods for restoring traffic during failover in a cable head end|
|US20040081108 *||Oct 2, 2002||Apr 29, 2004||Andiamo Systems||Arbitration system|
|US20050008027 *||Aug 4, 2004||Jan 13, 2005||Broadcom Corporation||System and method for multiplexing data from multiple sources|
|US20060067253 *||Nov 18, 2005||Mar 30, 2006||Broadcom Corporation||System and method for suppressing silence in voice traffic over an asynchronous communication medium|
|US20060161679 *||Jan 14, 2005||Jul 20, 2006||Microsoft Corporation||Method and apparatus for distributing messages|
|US20060269285 *||Mar 27, 2006||Nov 30, 2006||Wave7 Optics, Inc.||Optical network system and method for supporting upstream signals propagated according to a cable modem protocol|
|US20070076856 *||Oct 20, 2006||Apr 5, 2007||Broadcom Corporation||System and method for suppressing silence in voice traffic over a wireless communication medium|
|US20070242673 *||Jun 12, 2007||Oct 18, 2007||Broadcom Corporation||Methods of allocating packets in a wireless communication system|
|US20070242693 *||Jun 12, 2007||Oct 18, 2007||Broadcom Corporation||Allocation of packets in a wireless communication system|
|US20070263624 *||Jul 20, 2007||Nov 15, 2007||Broadcom Corporation||Methods for specialized data transfer in a wireless communication system|
|US20070263663 *||Jul 20, 2007||Nov 15, 2007||Broadcom Corporation||Specialized data transfer in a wireless communication system|
|US20070297436 *||Aug 28, 2007||Dec 27, 2007||Broadcom Corporation||Method for scheduling wireless communications|
|US20080037556 *||Aug 17, 2007||Feb 14, 2008||Broadcom Corporation||Method for upstream priority lookup at physical interface within a wireless device|
|US20080159177 *||Dec 29, 2006||Jul 3, 2008||Krishna Balachandran||Adaptive method of floor control with fast response time and fairness in communication network|
|US20100023988 *||Jan 28, 2010||Broadcom Corporation||System And Method For Suppressing Silence In Voice Traffic Over A Wireless Communication Medium|
|US20100303018 *||Aug 6, 2010||Dec 2, 2010||Broadcom Corporation||Specialized Data Transfer in a Wireless Communication System|
|US20110164616 *||Jul 7, 2011||Andiamo Systems||Methods and apparatus for processing superframes|
|US20110170507 *||Jul 14, 2011||Broadcom Corporation||Methods of Allocating Packets in a Wireless Communication System|
|US20110211479 *||Sep 1, 2011||Broadcom Corporation||Scheduling wireless communications|
|U.S. Classification||370/230, 725/97, 370/395.41, 370/395.21, 725/111, 348/E07.069, 725/95, 348/E07.07, 370/468|
|International Classification||H04L29/06, H04L12/24, H04M7/00, H04L12/64, H04N7/173, H04J3/16, H04L12/28, H04L12/56, H04N7/10|
|Cooperative Classification||H04L12/6418, H04W28/20, H04L41/0896, H04N7/173, H04N21/2385, H04L12/2876, H04L12/5693, H04L47/788, H04N21/4788, H04N7/17309, H04L65/80, H04L47/824, H04L41/5022, H04L12/5695, H04L47/827, H04N21/44209, H04L29/06, H04L41/5003, H04L2012/6494, H04N21/64707, H04L47/15, H04N21/437, H04L47/2416, H04M7/006, H04L41/5087, H04L47/35, H04N21/6118, H04L41/509, H04L29/06027, H04L47/6215, H04L47/521, H04N21/6168, H04N21/42676, H04L12/2861, H04L2012/6481, H04L12/2801, H04N21/4396, H04L47/2433, H04L47/805, H04N21/6377, H04L12/2856|
|European Classification||H04L12/56K, H04L12/56R, H04N21/439M, H04N21/6377, H04N21/426M, H04N21/437, H04N21/647B, H04N21/61D2, H04N21/2385, H04N21/4788, H04N21/442D, H04N21/61U2, H04L65/80, H04W28/20, H04L47/82G, H04L47/78D, H04L47/52A, H04L47/15, H04L47/80C, H04L47/35, H04L47/82D, H04L47/24B, H04L47/24C1, H04L47/62C, H04M7/00M, H04N7/173B, H04L29/06, H04L12/28P1, H04L12/64B, H04L12/28B, H04L29/06C2, H04L12/28P1D1C, H04L12/28P1B2|
|Feb 15, 2001||AS||Assignment|
Owner name: BROADCOM CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GAMMALLA, AJAY CHANDRA V.;SALA, DOLORS;REEL/FRAME:011560/0471
Effective date: 20010215
|Aug 13, 2009||FPAY||Fee payment|
Year of fee payment: 4
|Mar 14, 2013||FPAY||Fee payment|
Year of fee payment: 8