US 8,089,949 B2Grant
Distributed access point for IP based communications
Issue Date:2012-01-03
•16 Claims
•6 Drawing Sheets
Abstract
An apparatus for Internet-Protocol based communications in a wireless network includes a network interface, a controller, and memory. The interface receives a series of multicast data packets. The controller identifies one or more receiving nodes in the wireless network requesting data corresponding to the series of multicast data packets and determines that the effective unicast rate for one or more unicast data packets exceeds a minimum data rate of the series of multicast data packets using an 802.x protocol. The memory stores instructions that may be executable by a processor. Upon execution of the instructions by a processor, the received series of multicast data packets is converted into one or more unicast packets, the execution and conversion occurring in response to instructions received from the controller. A system for Internet-Protocol based communications in a wireless network implements such an apparatus in the context of an access point.
Metadata
Assignee
- Ruckus Wireless, Inc.
Inventor
- William S. Kish
Application Information
Application Number:US 12/719,006
Filing Date:2010-03-08
Priority Date:2004-11-05
Art Unit:2617
Classifications
IPC:
H04J3/24
Patent Drawings (6 sheets)
Description
Cross-Reference to Related Applications
[0001] This application is a continuation-in-part and claims the priority benefit of U.S. patent application Ser. No. 11/985,866 filed Nov. 16, 2007 now U.S. Pat. No. 7,787,436 and entitled “Improved Communications Throughput with Multiple Physical Data Rate Transmission Determinations,” which is a divisional and claims the priority benefit of U.S. patent application Ser. No. 11/232,196, now U.S. Pat. No. 7,505,447, filed Sep. 20, 2005 and entitled “Systems and Methods for Improved Data Throughput in Communications Networks,” which claims the priority benefit of U.S. provisional application No. 60/625,331 filed Nov. 5, 2004, and entitled “Systems and Methods for Improved Data Throughput in Wireless Local Area Networks.” The disclosure of each of the foregoing applications is incorporated herein by reference.
[0002] This application is related to co-pending U.S. patent application Ser. No. 11/010,076 entitled “System and Method for an Omnidirectional Planar Antenna Apparatus with Selectable Elements,” filed on Dec. 9, 2004, U.S. patent application Ser. No. 11/022,080 entitled “Circuit Board Having a Peripheral Antenna Apparatus with Selectable Antenna Elements,” filed on Dec. 23, 2004, and U.S. patent application Ser. No. 11/041,145 entitled “System and Method for a Minimized Antenna Apparatus with Selectable Elements,” filed on Jan. 21, 2005, the subject matter of which are hereby incorporated by reference.
[0003] This application is related to U.S. patent application Ser. No. 11/985,865 filed Nov. 16, 2007 and entitled “Improved Communications Throughput with Unicast Packet Transmission Alternative,” which is itself a divisional of the aforementioned U.S. patent application Ser. No. 11/232,196 and entitled “Systems and Methods for Improved Data Throughput in Communications Networks.” The disclosure of this commonly owned application is incorporated herein by reference.
Background of the Invention
[0004] 1. Field of the Invention
[0005] The present invention generally relates to communications networks and more particularly to systems and methods for increased data throughput in communications networks.
[0006] 2. Description of the Prior Art
[0007] Demand for multimedia applications, including audio and video data, is rapidly increasing. Some of the more popular uses of multimedia are real-time interactive applications, such as video and audio streaming, Internet Protocol TV (IPTV), transmission of lectures or speeches to a remote audience, and animated simulations. Even when data compression is used, multimedia applications require large amounts of bandwidth.
[0008] In an IEEE 802.11 wireless local area network (LAN), broadcast or multicast packet transmission enables bandwidth-intensive multimedia applications to transmit—simultaneously—audio and video data packets to each receiving node associated with a group of the wireless LAN. Broadcast packets are transmitted to all receiving nodes of the wireless LAN, whereas multicast packets are transmitted to two or more, but fewer than all, of the receiving nodes of the wireless LAN.
[0009] In the wireless LAN, a source node may transmit (e.g., via Ethernet) multicast packets to a multicast-enabled access point, and the access point sends the multicast packets via wireless transmission to destination receiving nodes that have identified themselves as part of the multicast group.
[0010] The access point of the wireless LAN may also support unicast packet transmission. For unicast transmission in the wireless LAN, the access point transmits one or more unicast packets to the receiving node identified by an intended destination address included in the unicast packets. After receiving the unicast packet, the receiving node transmits (approximately 9 μs later) an 802.11 acknowledgement (ACK) packet back to the access point. The 802.11 ACK mechanism provides reliable data transmission in the typically highly interfered 802.11 wireless network by confirming to the access point that the unicast packet was received.
[0011] A limitation with transmitting multicast packets in the wireless LAN is that the 802.11 ACK does not provide a reliable mechanism for ensuring that the receiving nodes actually received the multicast packets. For example, if the 802.11 access point were to transmit one or more multicast packets to a number of receiving nodes, and each of the receiving nodes were to respond essentially simultaneously with 802.11 ACK packets, the multiple ACK packets received by the access point would comprise “noise” during the period of the multiple simultaneous 802.11 ACKs. To the access point, these multiple simultaneous 802.11 ACKs are undecipherable. This condition may be referred to as a “multiple ACK problem.”
[0012] Another limitation with transmitting multicast packets is that the wireless LAN may be limited in the bandwidth used for multicast packets. Because of the multiple ACK problem, the IEEE 802.11 specification for multicast dictates that transmission of multicast packets occur at a minimum allowable physical data rate. Because the receiving nodes may be at various distances from the source of the transmission, and may experience various interference levels, transmitting at the minimum allowable physical data rate improves the probability of reception of the multicast packets by each receiving node. For example, an 802.11 access point transmits multicast packets at a minimum allowable physical data rate of 1 Mbps for 802.11b and 6 Mbps for 802.11a. The receiving nodes do not transmit 802.11 ACK packets to verify reception of the multicast packets. Thus, without the 802.11 ACK mechanism, there is no verification of reception of the multicast packets.
[0013] Further, transmitting at the minimum allowable physical data rate under-utilizes available bandwidth in the wireless LAN, which otherwise is capable of supporting much higher data rates. In addition, transmitting at the minimum allowable physical data rate may make the wireless LAN unsuitable for applications that require high rate communication, such as multimedia applications.
Summary of the Claimed Invention
[0014] A claimed embodiment of the present invention is for a distributed access point for Internet-Protocol based communications in a wireless network.
[0015] An apparatus for Internet-Protocol based communications in a wireless network is claimed. The apparatus includes a network interface, a controller, and memory. The interface receives a series of multicast data packets. The controller identifies one or more receiving nodes in the wireless network requesting data corresponding to the series of multicast data packets and determines that the effective unicast rate for one or more unicast data packets exceeds a minimum data rate of the series of multicast data packets using an 802.x protocol. The memory stores instructions that may be executable by a processor. Upon execution of the instructions by a processor, the received series of multicast data packets is converted into one or more unicast packets, the execution and conversion occurring in response to instructions received from the controller.
[0016] A second claimed embodiment is for that of a system for Internet-Protocol based communications in a wireless network. The system includes an access point, which includes a network interface to receive a series of multicast data packets, and memory storing instructions executable by a processor to convert the received series of multicast data packets into one or more unicast packets in response to instructions received from a controller. The system also includes a controller that is physically distinct from but communicatively coupled to the access point. The controller identifies one or more receiving nodes in the wireless network requesting data corresponding to the series of multicast data packets, and determines that the effective unicast rate for the one or more unicast data packets exceeds a minimum data rate of the series of multicast data packets using an 802.x protocol.
[0017] In yet another claimed embodiment of the present invention, a system for Internet-Protocol based communications in a wireless network includes a motherboard and controller. The motherboard has a network interface to receive a series of multicast data packets, and memory storing instructions executable by a processor to convert the received series of multicast data packets into one or more unicast packets in response to instructions received from a controller. The motherboard further includes a radio. A controller is communicatively coupled to the radio at the first motherboard by way of a wireless network. The controller identifies one or more receiving nodes in the wireless network requesting data corresponding to the series of multicast data packets, and determines that the effective unicast rate for the one or more unicast data packets exceeds a minimum data rate of the series of multicast data packets using an 802.x protocol.
Brief Description of the Drawings
[0018] FIG. 1 illustrates a block diagram of a system for multicast transmission in a wireless local area network;
[0019] FIG. 2 illustrates an exemplary method for multicast or unicast transmission in the wireless local area network of FIG. 1 ;
[0020] FIG. 3 illustrates an exemplary timing diagram illustrating conversion of multicast packets into unicast packets as described with respect to FIGS. 1-2 ; and
[0021] FIG. 4 illustrates an apparatus for Internet-Protocol based communications in a wireless network and that may implement multicast to unicast conversion.
[0022] FIG. 5 illustrates a system for Internet-Protocol based communications in a wireless network.
Detailed Description
[0023] The systems and methods disclosed herein enable data throughput in communication networks greater than that which is provided in the prior art. For example, the system and method disclosed herein support bandwidth-intensive multimedia applications over wireless LANs. Nodes of a communication network may be referred to as a host, a source, a destination, a node, a receiving node, an access point, and a station. These references should not be considered in a limiting sense; for example, a “receiving node” is in no way limited to the function of receiving only, but is at least capable of receiving. Additionally, the term “group packet” includes a multicast packet, a broadcast packet, and any packet whose destination address indicates one or more addresses and/or nodes of the communications network.
[0024] According to one embodiment, a wireless local area network (LAN) comprises an access point configured to receive a multicast or broadcast packet from a source. The multicast or broadcast packet is addressed to a group comprising one or more nodes of a communications network (e.g., stations associated with the access point of the wireless LAN). The access point determines whether to convert the multicast or broadcast packet into one or more unicast packets for sequential transmission to the one or more nodes or whether to transmit the multicast or broadcast packet to the group. If the access point transmits the multicast or broadcast packet without conversion, the access point may determine a lowest common denominator data rate based on data rates for transmitting multicast or broadcast packets to the one or more nodes and transmits the multicast or broadcast packet to the group at the lowest common denominator rate.
[0025] FIG. 1 illustrates a block diagram of a system 100 for multicast packet transmission in a wireless local area network, in accordance with one embodiment of the present invention. The system 100 comprises a source node 110, a network link 115, an access point 120, receiving nodes 130, 140, and 150, wireless links 135, 145, and 155, and a group 160 comprising two or more of the receiving nodes (e.g., the receiving nodes 130 and 140). The source node 110 is configured to communicate with the access point 120 over the network link 115. The access point 120 is configured to communicate with the receiving nodes 130-150 over the wireless links 135-155 that form the wireless LAN.
[0026] The source node 110 is any device capable of network communication including unicast or multicast packet transmission with the access point 120 over the network link 115. The source node 110 may comprise, for example, a personal computer, a server, a network attached storage device, or a network video distribution device. The source node 110 may support networking protocols such as Transmission Control Protocol/Internet Protocol (TCP/IP), User Datagram Protocol (UDP/IP), and/or Internet Group Management Protocol (IGMP), and may support unicast, multicast, and/or broadcast packet transmission of network data.
[0027] The source node 110 is configured to transmit one or more group packets addressed to the group 160 (e.g., one or more multicast or broadcast packets) over the network link 115. The network link 115 may be a wired or wireless network link. In one embodiment, the network link 115 comprises a UDP/IP connection. In one example, the source node 110 comprises an IPTV video server (not shown) that transmits the multicast packets, providing a remote video stream to the group 160 through the access point 120. Although discussed in regard to multicast transmission, the group packets may comprise a packet whose destination address specifies all (i.e., broadcast), or less than all (i.e., multicast) of the receiving nodes 130-150.
[0028] The receiving nodes 130-150 each comprise any device capable of receiving network communication from the source node 110 through the access point 120 over the wireless links 135-155. The receiving nodes 130-150 may comprise devices such as personal computers, PDAs, cell phones, and/or internet enabled televisions. In one example, the receiving nodes 130-140 of the group 160 may comprise TV set-top boxes configured to receive a video stream provided by the IPTV server at the source node 110 to the group 160. Although described as the source node 110 and the receiving nodes 130-150, it should be noted that the source node 110 may also be the destination node of a data packet as well as the receiving nodes 130-150 may also be the source node of a data packet.
[0029] As described further herein, the access point 120 is configured to transmit the video stream to the receiving node 130 and the receiving node 140 either simultaneously as a multicast packet, or sequentially as one or more unicast packets to each of the receiving nodes 130 and 140. The access point 120 is virtually any device capable of acting as a bridge in a peer-to-peer connection in the wireless LAN or as a bridge between the network link 115 and the wireless links 135-155. The access point 120 may be configured to convert the multicast packet into one or more unicast packets, as discussed further with respect to FIG. 2 . The access point 120 may include a processor, a memory, and additional circuitry that provides or assists in providing the bridge and/or the multicast packet conversion. The access point 120 may use the IEEE 802.11 protocol, such as 802.11a or 802.11b, to communicate with the receiving nodes 130-150. It will be appreciated that the access point 120 may incorporate other wireless protocols, such as 802.11g, 802.16, or Bluetooth.
[0030] The access point 120 may support multicast control protocols, such as IGMP, and may be configured as a multicast-enabled router. A multicast control protocol enables the access point 120 to determine from the receiving nodes (e.g., the receiving nodes 130-150) which group(s) (e.g., the group 160) the receiving nodes 130-150 are associated with. Some examples of multicast control protocols are IGMP, Protocol-Independent Multicast (PIM), Real-Time Streaming Protocol (RTSP), Multiprotocol Border Gateway Protocol (MBGP), Multicast Source Discovery Protocol (MSDP), Simple Service Discovery Protocol (SSDP), and Source Specific Multicast (SSM). For example, the receiving node 130 may send a multicast control protocol packet to the access point 120 to change the channel for an IPTV multicast stream received from the source node 110. The multicast control protocol packet informs the access point 120 that the receiving node 130 is interested in receiving group packets for the selected channel.
[0031] The access point 120 of some embodiments is further configured to maintain information about “associated nodes.” Associated nodes are devices that have negotiated a wireless communication link (e.g., the wireless link 135) with the access point 120. For example, when the receiving node 130 initially associates with the access point 120 to negotiate the wireless link 135, the receiving node 130 provides a Media Access Control (MAC) or hardware address that uniquely identifies the receiving node 130. The receiving node 130 may also provide a list of allowable physical data rates (e.g., 1 Mbps-54 Mbps) at which it may communicate with the access point 120. The access point 120 may store such information about the associated nodes in memory, for example.
[0032] As described further herein, the system 100 improves multicast data throughput in the wireless LAN because the access point 120 of one embodiment is configured to convert the multicast packet addressed to the group 160 into one or more unicast packets addressed to the receiving nodes 130-140. The access point 120 may transmit the one or more unicast packets sequentially to the receiving nodes 130-140 at a higher data rate than the minimum data rate used for 802.11 multicast transmission. Further, the access point 120 of this embodiment would ensure reliable transmission of the converted multicast packet because the access point 120 would be able to service 802.11 ACK packets generated by the receiving nodes 130-140. In some embodiments, the access point 120 may determine not to convert the multicast packet into one or more unicast packets, but instead may transmit the multicast packet to the receiving nodes of the group 160 at a relatively higher data rate than the minimum allowable physical data rate used for 802.11 multicast packet transmission.
[0033] FIG. 2 illustrates an exemplary method for multicast or unicast transmission in the wireless local area network of FIG. 1 , in accordance with one embodiment of the present invention. The steps of the exemplary method are described as occurring in particular order, but it will be appreciated that certain steps may be rearranged to provide a similar result. The method determines whether to convert a multicast packet into one or more unicast packets or whether to transmit the multicast packet. The method also determines at what rate to transmit the multicast packet and the one or more unicast packets. The method begins with the access point 120 already associated with receiving nodes 130-150.
[0034] In step 205, the access point 120 receives a first join request (e.g., a multicast control protocol packet such as an IGMP join request) from the first receiving node (e.g., the receiving node 130) containing a first address for the receiving node 130. The access point 120 uses the join request to correlate the receiving node 130 with the address of the group 160. In IGMP, a multicast client (e.g., the receiving node 130) joins a multicast group (e.g., the group 160) to enable group reception of a multicast traffic stream. When the access point 120 receives the IGMP join request from the receiving node 130, the access point 120 inspects the IGMP packet and determines the required join information.
[0035] In this embodiment, the access point 120 does not itself use the IGMP protocol. Regardless, the system 100 takes advantage of the fact that the IGMP join requests from the receiving nodes 130-140 to the source node 110 pass through the access point 120. The access point 120 “sniffs” or samples the IGMP join requests to map the hardware (MAC) address of the receiving nodes 130 and 140 with the address of the group 160. In some embodiments, the access point 120 “speaks” the IGMP protocol. The access point 120 may map the IP addresses (instead of the MAC addresses) of the receiving nodes 130 and 140 to the address of the group 160.
[0036] In the alternative to sniffing or speaking IGMP or other control protocols from the receiving nodes 130-150, the access point 120 may maintain a map that contains the hardware addresses of all or a subset of the receiving nodes 130-150 that are associated with the access point 120. The access point 120 may use the map to query the receiving nodes 130-150 to determine which of the receiving nodes 130-150 are interested in receiving multicast traffic addressed to the group 160. These maps of MAC addresses or IP addresses allow the access point 120 to convert the multicast packet received from the source node 110 and addressed to the group 160 into one or more unicast packets addressed to the receiving nodes 130-140 of the group 160.
[0037] In step 210, the access point 120 maps the first address of the receiving node 130 from the IGMP packet to the address of the group 160. In step 215, the access point 120 receives a second join request (e.g., a second IGMP join request) from a second receiving node (e.g., the receiving node 140). In step 220, the access point 120 maps a second address of the receiving node 140 to the address of the group 160.
[0038] In step 225, the access point 120 receives the multicast packet addressed to the group 160. In step 230, the access point 120 determines a first data rate (e.g., 54 Mbps) by which the access point 120 may reliably transmit (e.g., including the 802.11 ACK mechanism) one or more unicast packets to the receiving node 130. In step 235, the access point 120 determines a second data rate (e.g., 24 Mbps) by which the access point 120 may reliably transmit one or more unicast packets to the receiving node 140. Although not depicted, in some embodiments the access point 120 may determine additional (e.g., a third or more) data rates by which the access point 120 may reliably transmit one or more unicast packets to a third receiving node (e.g., the receiving node 150 which would be part of the group 160).
[0039] In step 240, the access point 120 determines an effective unicast rate. As discussed further with respect to FIG. 3 , the effective unicast rate corresponds to a combined rate for converting the multicast packet into one or more unicast packets and sending the one or more unicast packets to the receiving nodes 130 and 140 of the group 160 at the first and second (and third . . . ) data rates. The effective unicast rate depends on the total number of bits included in the unicast packets, including additional data packet overhead (e.g., additional bits in the unicast packet as compared to the multicast packet). The effective unicast rate also depends on computational time associated with converting the multicast packet into one or more unicast packets. The effective unicast rate is further based on the duration for reception and processing of ACK packets from the receiving nodes of the group 160. Further, the effective unicast rate is based on the number of receiving nodes in the group 160, because each additional receiving node in the group 160 proportionally lowers the effective unicast rate. One method for determining the effective unicast rate is presented in U.S. patent application Ser. No. 11/180,329 and entitled “System and Method for Transmission Parameter Control for an Antenna Apparatus with Selectable Elements,” the disclosure of which is incorporated by reference.
[0040] As described further, rather than converting the multicast packet to unicast packets, the access point may transmit at a “lowest common denominator rate” to the group 160. For example, the lowest common denominator rate may be higher than the effective unicast rate, particularly with a large number of receiving nodes in the group 160 each receiving at a relatively high rate. For example, the group 160 may comprise the receiving nodes 130, 140, and 150. The receiving node 130 may receive packets at a physical data rate of 54 Mbps, the receiving node 140 may receive packets at a physical data rate of 54 Mbps, and the receiving node 150 may receive packets at a physical data rate of 54 Mbps. The lowest common denominator rate for this example is 54 Mbps, which may be higher than the effective unicast rate. In step 245, the access point 120 determines the lowest common denominator rate (LCDR) for transmitting the multicast packet simultaneously to the receiving nodes of the group 160.
[0041] In steps 250-295, the access point 120 determines whether to transmit unicast or multicast packets, and at what rate to transmit the unicast or multicast packets. Specifically, in steps 250-275, the access point 120 may determine to convert the multicast packet into one or more first unicast packets addressed to the receiving node 130 and one or more second unicast packet addressed to the receiving node 140 for transmission. Alternatively, in steps 285-295, the access point 120 may determine to transmit the multicast packet simultaneously to the receiving nodes 130-140 of the group 160 and not convert the multicast packet into unicast packets. Further, in steps 285-295 the access point 120 determines whether to transmit at the lowest common denominator rate if the lowest common denominator rate is higher than the minimum allowable physical data rate.
[0042] In step 250, the access point 120 determines if the effective unicast rate exceeds the lowest common denominator rate. For example, in an 802.11a wireless LAN with the receiving nodes 130, 140, and 150 in the group 160, the first data rate may be 54 Mbps, the second data rate may be 6 Mbps, and the third data rate may be 54 Mbps. The effective unicast rate, given the number of data bits in the unicast packets, packet overhead, conversion processing time, and the like may be 11.5 Mbps, for example. Accordingly, the effective unicast rate of 11.5 Mbps exceeds the lowest common denominator rate of 6 Mbps (i.e., the minimum allowable physical data rate for 802.11a), so the access point 120 will convert the multicast packet into one or more unicast packets in steps 255-275.
[0043] In step 255, the access point 120 converts the multicast packet to a first unicast packet addressed to the receiving node 130. In step 260, the access point 120 transmits the first unicast packet to the receiving node 130 at the first data rate. After transmission of the first unicast packet, in step 265 the access point 120 may delay for a predetermined delay period before converting the multicast packet into a second unicast packet and transmitting the second unicast packet to the receiving node 140 in steps 270-275. The delay period is computed to allow the receiving node 130 sufficient time to generate an 802.11 ACK that the access point 120 may receive to verify reliable transmission and reception of the first unicast packet. The access point 120 may compute the delay period based on several factors. For example, the access point 120 may compute the delay based on computational time needed by the access point 120 to convert the multicast packet into the first unicast packet. The delay may include data packet overhead (e.g., additional bits in the first unicast packet that reduce the first data rate to a relatively lower “user” data rate). Further, the access point 120 may retransmit the first unicast packet to the receiving node 130 if the access point 120 does not receive the 802.11 ACK from the receiving node 130 for the first unicast packet, adding to the delay.
[0044] In step 270, the access point 120 converts the multicast packet from the source node 110 into a second unicast packet addressed to the receiving node 140. In step 275, the access point 120 transmits the second unicast packet at the second data rate to the receiving node 140. In similar fashion to the method described above with respect to steps 260-265 for the first unicast packet, the access point 120 awaits an 802.11 ACK from the receiving node 140 to ensure reliable transmission and reception of the second unicast packet. The access point 120 may retransmit the second unicast packet to the receiving node 140 if the access point 120 does not receive the 802.11 ACK from the receiving node 140. Although not depicted, the steps 265 to 275 may be repeated for additional (e.g., third . . . ) receiving nodes in the group 160.
[0045] Optionally, the access point 120 may determine in step 260 and step 275 whether one of the receiving nodes of the group 160 comprises a multicast data transmitter. For example, if the receiving node 130 acts as the source node 110 for sending the multicast packet through the access point 120 to the receiving nodes 140 and 150 of the group 160, the access point 120 need not retransmit the converted unicast packet back to the receiving node 130. Although sending the unicast packet back to the receiving node 130 is legitimate practice in 802.11, doing so wastes network bandwidth.
[0046] At step 250, if the effective unicast rate does not exceed the lowest common denominator rate, the access point 120 may determine not to convert the multicast packet into one or more unicast packets for sequential transmission to each receiving node in the group 160. Accordingly, in step 285, the access point 120 determines whether the LCDR exceeds the minimum allowable data rate. For example, if the receiving node 130 is capable of receiving at 54 Mbps and the receiving node 140 is capable of receiving at 24 Mbps, the LCDR of 24 Mbps exceeds the minimum allowable data rate of 6 Mbps. Accordingly, in step 290 the access point 120 will transmit the multicast packet to the group 160 at the LCDR of 24 Mbps. Alternatively, at step 285 if the receiving node 130 is capable of receiving at 54 Mbps and the receiving node 140 is capable of receiving at only 6 Mbps, for example, the LCDR does not exceed the minimum allowable data rate of 6 Mbps. Accordingly, in step 295, the access point 120 will transmit the multicast packet to the group 160 at the minimum allowable data rate of 6 Mbps.
[0047] The methods described with respect to FIG. 2 advantageously achieve higher data throughput than traditional multicast transmission, by converting multicast packets in the access point 120 into one or more unicast packets that may be transmitted sequentially to each receiving node of the group 160 at a relatively higher data rate. Further, converting the multicast packet into unicast packets affords higher data transmission reliability because the unicast packets are verified by ACK responses from each receiving node of the group 160. Additionally, if the access point 120 determines not to convert multicast packets into unicast packets, the access point 120 may transmit the multicast packet at the lowest common denominator rate, which is a higher physical data rate than the minimum allowable physical data rate defined in the IEEE 802.11 standard.
[0048] Although FIGS. 1 and 2 generally describe multicast data flow from the source node 110 to the group 160 (i.e., left to right in FIG. 1 ), the methods described with respect to FIG. 2 are applicable to multicast control protocol packets that flow in the opposite direction (e.g., from right to left in FIG. 1 ). For example, the system 100 may include a source node (e.g., the receiving node 130) configured to transmit a group packet to a destination node (e.g., the access point 120). The receiving node 130 sends a multicast control protocol packet, such as an IGMP join request, over the wireless link 135 to the access point 120 to join a group (e.g., group 160) receiving an IPTV multimedia multicast stream. To provide more effective use of the available bandwidth of the wireless link 135, and to provide reliable transmission of the multicast control protocol packet, the receiving node 135 may convert the multicast control protocol packet to one or more unicast packets for transmission to an acknowledgement by the access point 120.
[0049] In one example, the receiving node 130 determines a first data rate for transmitting the group packet and determines a second data rate based upon converting the group packet to a unicast packet addressed to the access point 120. The receiving node 130 transmits the unicast packet at the second data rate through the wireless link 135 to the access point 120 if the first data rate for transmitting the group packet is less than the second data rate for transmitting the unicast packet. As discussed herein, the receiving node 130 transmits the unicast packet at a higher physical data rate than specified for multicast transmission. Upon receipt of the unicast packet, the access point 120 sends an ACK to acknowledge receipt of the unicast packet.
[0050] If the first data rate for transmitting the group packet is greater than the second data rate for transmitting the unicast packet, the receiving node 130 may transmit the group packet through the wireless link 135. As previously discussed, the receiving node 130 may transmit the group packet at the lowest common denominator rate. The access point 120 then receives the group packet and processes the multicast control protocol packet. Therefore, in these embodiments, the receiving node 130 and the access point 120 individually determine whether transmitting the group packet or converting the group packet to one or more unicast packets allows for a more effective use of the available bandwidth and for reliable transmission.
[0051] FIG. 3 illustrates an exemplary timing diagram comparing the conversion of the multicast packet into one or more unicast packets, as described in FIGS. 1-2 , as compared to multicast packet transmission, in accordance with one embodiment of the present invention. A first time interval 310 indicates the time needed for the access point 120 to convert the multicast packet received from the source node 110 into the first unicast packet and transmit the first unicast packet to the receiving node 130, for example, at 54 Mbps. The time interval 310 may vary depending upon at least the first data rate, the number of data bits in the first unicast packet, and the conversion time needed by the access point 120 to convert the multicast packet into the first unicast packet. After the first unicast packet is transmitted to the receiving node 130, an ACK time interval 320 indicates the time needed for the receiving node 130 to return the 802.11 ACK corresponding to the first unicast packet and for the access point 120 to process the 802.11 ACK packet.
[0052] Similarly, a second time interval 330 indicates the time needed for the access point 120 to convert the multicast packet received from the source node 110 into the second unicast packet and transmit the second unicast packet to the receiving node 140 at the second data rate, for example, 18 Mbps. A second ACK time interval 340 indicates the time needed for the receiving node 140 to return an 802.11 ACK corresponding to the second unicast packet and for the access point 120 to process the 802.11 ACK packet. In comparison, a multicast time interval 350 indicates the duration for the access point 120 to receive and transmit the multicast packet simultaneously to the receiving nodes 130 and 140 at either the lowest common denominator rate or the minimum allowable physical data rate.
[0053] Because the duration of the combined time intervals 310, 320, 330, and 340 is shorter than the duration of the multicast time interval 350, the system and method described herein advantageously achieve a higher data throughput by converting the multicast packet to sequential unicast packets. Further, as the duration of the time intervals 310 and 320 increases because of interference in the wireless links 135 and 145 (FIG. 1 ) leading to lower first and second data rates, for example, the combined duration of the time intervals 310, 320, 330, and 340 may exceed the multicast time interval 350. In such case, the lowest common denominator rate may provide a higher data rate than the minimum allowable data rate. Another advantage, therefore, is graceful degradation of the overall data transmission rate with changes in the wireless LAN.
[0054] FIG. 4 illustrates an exemplary apparatus 400 for Internet-Protocol based communications in a wireless network and that may implement multicast to unicast conversion as described above. The apparatus 400 may operate in the context of an access point or any other network enabled communications node, including nodes like those previously described. The apparatus 400 of FIG. 4 includes a network interface 410 that receives a series of multicast data packets (405). The network interface 410, as illustrated in FIG. 4 , constitutes a series of selectable antenna elements receiving wirelessly transmitted data. In some implementations, however, the network interface for the receipt of multicast data packets may be a wired data connection and be separate from a network interface allowing for wireless transmission of data.
[0055] A controller 420 at apparatus 400 identifies one or more receiving nodes 440 . . . 460 in the wireless network 430 that are requesting data corresponding to the series of multicast data packets. In addition to identifying receiving nodes in the network, the controller 420 is capable of determining, as generally described above, that the effective unicast rate for one or more unicast data packets exceeds a minimum data rate of the series of multicast data packets using an 802.x protocol.
[0056] The controller 420 of FIG. 4 may be implemented as a software application. This application may be stored in memory (not shown) independent of the memory (470) storing instructions executable by processor 480. The controller software may be executable by processor 480 or an additional processor (not shown). The controller software application could alternatively be stored in the same memory 470 storing the instructions executable by processor 480 to convert the received series of multicast data packets into one or more unicast packets. The controller 420 may also operate in the context of an application specific microprocessor.
[0057] Regardless of any particular implementation, the controller 420 identifies one or more receiving nodes (440, 450, 460) to determine that the effective unicast rate for the one or more unicast data packets exceeds a minimum data rate of the series of multicast data packets as noted above. The controller 420 may further assign each of the one or more receiving nodes in the wireless network to a group of receiving nodes.
[0058] The controller 420 may operate in accordance with factory-installed instructions or a factory-configuration for control of the apparatus 400. The controller 420 may allow for updating or reconfiguration in accordance with user-defined parameters or as otherwise allowed for by controller software. Memory 470 at the apparatus 400 stores instructions executable by a processor 480 to convert the received series of multicast data packets into one or more unicast packets (485) in response to instructions received from the controller 420. Transmission of the packets 485 may occur by way of radio 490 and antenna elements (410), which may be the same selectable antenna elements (or selected configurations thereof) as described above.
[0059] Some embodiments of the apparatus 400 may include multiple radios (not shown). A group of receiving nodes may be assigned to a particular one of the multiple radios. Each of the radios may be coupled to a wireless network interface, such as an antenna element, to wireless transmit the one or more unicast data packets to the group of receiving nodes assigned to the radio using an 802.x protocol. In those embodiments utilizing a single radio, like that of FIG. 4 , a wireless network interface transmits—wirelessly—the one or more unicast data packets to a group of receiving nodes from the one or more receiving nodes requesting the data corresponding to the one or more multicast data packets.
[0060] The controller 420 and multiple radios (or single radio 490) may be embedded on a common motherboard or on separate motherboards within the apparatus 400. A controller 420 and wireless network interface 410 may likewise be on common or separate motherboards.
[0061] FIG. 5 illustrates a system 500 for Internet-Protocol based communications in a wireless network. The system 500 illustrated in FIG. 5 includes an access point 530, which may be similar to the apparatus 400 of FIG. 4 . The access point 530 of FIG. 5 includes a network interface (not shown) to receive a series of multicast data packets 520 from a multicast source 510. The access point 530 further includes memory (not shown) for storing instructions executable by a processor to convert the received series of multicast data packets into one or more unicast packets 540 in response to instructions received from a controller 550.
[0062] Controller 550 of FIG. 5 is physically distinct from but communicatively coupled to the access point 530. The communicative coupling may be via a wireless network, a direct communicative coupling (e.g., a wired connection), or a proxy arrangement. The controller 550 in FIG. 5 identifies one or more receiving nodes (560, 570, 580) in a wireless network requesting data corresponding to the series of multicast data packets 520. The controller 550 determines that the effective unicast rate for the one or more unicast data packets exceeds a minimum data rate of the series of multicast data packets using an 802.x protocol. The controller 550 may be implemented in any number of configurations, including those described in the context of FIG. 4 .
[0063] Like the controller of FIG. 4 , controller 550 may assign each of the one or more receiving nodes (560, 570, 580) in the wireless network to a group of receiving nodes. Like the apparatus of FIG. 4 , the access point 530 may include multiple radios. Each group of receiving nodes may be assigned to one or more of the multiple radios, each of those radios being coupled to a wireless network interface to wirelessly transmit the one or more unicast data packets to the group of receiving nodes assigned to the radio using an 802.x protocol. The access point 530 may includes a wireless network interface to allow for the wireless transmission of the one or more unicast data packets to a group of receiving nodes from the one or more receiving nodes (560, 570, 580) requesting the data corresponding to the one or more multicast data packets.
[0064] In a still further embodiment of the present invention, a system for Internet-Protocol based communications in a wireless network may include a motherboard and controller. The motherboard includes a network interface to receive a series of multicast data packets and memory storing instructions executable by a processor to convert the received series of multicast data packets into one or more unicast packets in response to instructions received from a controller. The motherboard further includes a radio. Such a motherboard may be installed in an apparatus 400 like that described in FIG. 4 and/or the access point 530 of FIG. 5 .
[0065] The controller, of this particular embodiment, is communicatively coupled to the radio at the motherboard over a wireless network. The controller identifies one or more receiving nodes in the wireless network requesting data corresponding to the series of multicast data packets, and determines that the effective unicast rate for the one or more unicast data packets exceeds a minimum data rate of the series of multicast data packets using an 802.x protocol.
[0066] The embodiments discussed herein are illustrative of one example of the present invention. As these embodiments of the present invention are described with reference to illustrations, various modifications or adaptations of the methods and/or specific structures described may become apparent to those skilled in the art. All such modifications, adaptations, or variations that rely upon the teachings of the present invention, and through which these teachings have advanced the art, are considered to be within the scope of the present invention. Hence, these descriptions and drawings should not be considered in a limiting sense, as it is understood that the present invention is in no way limited to only the embodiments illustrated. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the appended claims along with their full scope of equivalents.
Claims
What is claimed is:
1. An apparatus for Internet-Protocol based communications in a wireless network, the apparatus comprising:
a network interface to receive a series of multicast data packets;
a controller to:
identify one or more receiving nodes in the wireless network requesting data corresponding to the series of multicast data packets, and
determine that the effective unicast rate for one or more unicast data packets exceeds a minimum data rate of the series of multicast data packets using an 802.x protocol; and
memory storing instructions executable by a processor to convert the received series of multicast data packets into one or more unicast packets in response to instructions received from the controller.
2. The apparatus of claim 1, wherein the controller is a software application stored in memory independent of the memory storing instructions executable by a processor to convert the received series of multicast data packets into one or more unicast, the controller software application executable by a processor to identify the one or more receiving nodes and determine that the effective unicast rate for the one or more unicast data packets exceeds a minim data rate of the series of multicast data packets.
3. The apparatus of claim 1, wherein the controller is an application specific microprocessor.
4. The apparatus of claim 1, wherein the controller is a software application stored in memory with instructions executable by a processor to convert the received series of multicast data packets into one or more unicast packets.
5. The apparatus of claim 1, wherein the controller further assigns each of the one or more receiving nodes in the wireless network to a group of receiving nodes.
6. The apparatus of claim 5, further comprising a plurality of radios, and wherein each group of receiving nodes is assigned to one or more radios from the plurality of radios, and each of the plurality of radios is coupled to a wireless network interface to wirelessly transmit the one or more unicast data packets to the group of receiving nodes assigned to the radio using an 802.x protocol.
7. The apparatus of claim 6, wherein the controller and the plurality of radios are embedded on a common motherboard.
8. The apparatus of claim 6, wherein the controller and the plurality of radios are on separate motherboards.
9. The apparatus of claim 5, further comprising a wireless network interface to wirelessly transmit the one or more unicast data packets to a group of receiving nodes from the one or more receiving nodes requesting the data corresponding to the one or more multicast data packets.
10. The apparatus of claim 9, wherein the controller and the wireless network interface are on a common motherboard.
11. The apparatus of claim 9, wherein the controller and the wireless network interface are on separate motherboards.
12. A system for Internet-Protocol based communications in a wireless network, the system comprising:
an access point including:
a network interface to receive a series of multicast data packets, and
memory storing instructions executable by a processor to convert the received series of multicast data packets into one or more unicast packets in response to instructions received from a controller; and
a controller that is physically distinct from but communicatively coupled to the access point, the controller configured to:
identify one or more receiving nodes in the wireless network requesting data corresponding to the series of multicast data packets, and
determine that the effective unicast rate for the one or more unicast data packets exceeds a minimum data rate of the series of multicast data packets using an 802.x protocol.
13. The system of claim 12, wherein the controller is further configured to assign each of the one or more receiving nodes in the wireless network to a group of receiving nodes.
14. The system of claim 12, wherein the access point further includes a plurality of radios, and wherein each group of receiving nodes is assigned to one or more radios from the plurality of radios, and each of the plurality of radios is coupled to a wireless network interface to wirelessly transmit the one or more unicast data packets to the group of receiving nodes assigned to the radio using an 802.x protocol.
15. The system of claim 12, further comprising a wireless network interface to wirelessly transmit the one or more unicast data packets to a group of receiving nodes from the one or more receiving nodes requesting the data corresponding to the one or more multicast data packets.
16. A system for Internet-Protocol based communications in a wireless network, the system comprising:
a motherboard including:
a network interface to receive a series of multicast data packets, and
memory storing instructions executable by a processor to convert the received series of multicast data packets into one or more unicast packets in response to instructions received from a controller, and
a radio; and
a controller communicatively coupled to the radio at the first motherboard by way of a wireless network, the controller configured to:
identify one or more receiving nodes in the wireless network requesting data corresponding to the series of multicast data packets, and
determine that the effective unicast rate for the one or more unicast data packets exceeds a minimum data rate of the series of multicast data packets using an 802.x protocol.
Patent Citations (200)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4176356(A) | 1979-11-01 | Foster et al. | Applicant |
| US4193077(A) | 1980-03-01 | Greenberg | Applicant |
| US4253193(A) | 1981-02-01 | Kennard | Applicant |
| US4305052(A) | 1981-12-01 | Baril et al. | Applicant |
| US4513412(A) | 1985-04-01 | Cox | Applicant |
| US4814777(A) | 1989-03-01 | Monser | Applicant |
| US5097484(A) | 1992-03-01 | Akaiwa | Applicant |
| US5173711(A) | 1992-12-01 | Takeuchi et al. | Applicant |
| US5203010(A) | 1993-04-01 | Felix | Applicant |
| US5220340(A) | 1993-06-01 | Shafai | Applicant |
| US5361256(A) | 1994-11-01 | Doeringer | Applicant |
| US5373548(A) | 1994-12-01 | McCarthy | Applicant |
| US5507035(A) | 1996-04-01 | Bantz | Applicant |
| US5559800(A) | 1996-09-01 | Mousseau et al. | Applicant |
| US5570366(A) | 1996-10-01 | Baker | Applicant |
| US5608726(A) | 1997-03-01 | Virgile | Applicant |
| US5754145(A) | 1998-05-01 | Evans | Applicant |
| US5767809(A) | 1998-06-01 | Chuang | Applicant |
| US5802312(A) | 1998-09-01 | Lazaridis et al. | Applicant |
| US5930259(A) | 1999-07-01 | Katsube | Applicant |
| US5964830(A) | 1999-10-01 | Durrett | Applicant |
| US6034638(A) | 2000-03-01 | Thiel et al. | Applicant |
| US6094177(A) | 2000-07-01 | Yamamoto | Applicant |
| US6181697(B1) | 2001-01-01 | Nurenberg | Applicant |
| US6266528(B1) | 2001-07-01 | Farzaneh | Applicant |
| US6292153(B1) | 2001-09-01 | Aiello et al. | Applicant |
| US6307524(B1) | 2001-10-01 | Britain | Applicant |
| US6317599(B1) | 2001-11-01 | Rappaport et al. | Applicant |
| US6326922(B1) | 2001-12-01 | Hegendoerfer | Applicant |
| US6337628(B2) | 2002-01-01 | Campana, Jr. | Applicant |
| US6337668(B1) | 2002-01-01 | Ito et al. | Applicant |
| US6339404(B1) | 2002-01-01 | Johnson et al. | Applicant |
| US6345043(B1) | 2002-02-01 | Hsu | Applicant |
| US6356242(B1) | 2002-03-01 | Ploussios | Applicant |
| US6356243(B1) | 2002-03-01 | Schneider et al. | Applicant |
| US6356905(B1) | 2002-03-01 | Gershman et al. | Applicant |
| US6377227(B1) | 2002-04-01 | Zhu et al. | Applicant |
| US6392610(B1) | 2002-05-01 | Braun et al. | Applicant |
| US6404386(B1) | 2002-06-01 | Proctor, Jr. et al. | Applicant |
| US6407719(B1) | 2002-06-01 | Ohira et al. | Applicant |
| US6442507(B1) | 2002-08-01 | Skidmore et al. | Applicant |
| US6445688(B1) | 2002-09-01 | Garces et al. | Applicant |
| US6493679(B1) | 2002-12-01 | Rappaport et al. | Applicant |
| US6498589(B1) | 2002-12-01 | Horii | Applicant |
| US6499006(B1) | 2002-12-01 | Rappaport et al. | Applicant |
| US6505253(B1) | 2003-01-01 | Chiu | Applicant |
| US6507321(B2) | 2003-01-01 | Oberschmidt et al. | Applicant |
| US6625454(B1) | 2003-09-01 | Rappaport et al. | Applicant |
| US6674459(B2) | 2004-01-01 | Ben-Shachar et al. | Applicant |
| US6701522(B1) | 2004-03-01 | Rubin et al. | Applicant |
| US6725281(B1) | 2004-04-01 | Zintel et al. | Applicant |
| US6753814(B2) | 2004-06-01 | Killen et al. | Applicant |
| US6762723(B2) | 2004-07-01 | Nallo et al. | Applicant |
| US6779004(B1) | 2004-08-01 | Zintel | Applicant |
| US6819287(B2) | 2004-11-01 | Sullivan et al. | Applicant |
| US6836481(B1) | 2004-12-01 | Hotta | Applicant |
| US6873627(B1) | 2005-03-01 | Miller | Applicant |
| US6876280(B2) | 2005-04-01 | Nakano | Applicant |
| US6888504(B2) | 2005-05-01 | Chiang et al. | Applicant |
| US6888893(B2) | 2005-05-01 | Li et al. | Applicant |
| US6892230(B1) | 2005-05-01 | Gu et al. | Applicant |
| US6906678(B2) | 2005-06-01 | Chen | Applicant |
| US6910068(B2) | 2005-06-01 | Zintel et al. | Applicant |
| US6924768(B2) | 2005-08-01 | Wu et al. | Applicant |
| US6931429(B2) | 2005-08-01 | Gouge et al. | Applicant |
| US6941143(B2) | 2005-09-01 | Mathur | Applicant |
| US6950019(B2) | 2005-09-01 | Bellone et al. | Applicant |
| US6961028(B2) | 2005-11-01 | Joy et al. | Applicant |
| US6973622(B1) | 2005-12-01 | Rappaport et al. | Applicant |
| US6975834(B1) | 2005-12-01 | Forster | Applicant |
| US7034770(B2) | 2006-04-01 | Yang et al. | Applicant |
| US7043277(B1) | 2006-05-01 | Pfister | Applicant |
| US7050809(B2) | 2006-05-01 | Lim | Applicant |
| US7064717(B2) | 2006-06-01 | Kaluzni et al. | Applicant |
| US7085814(B1) | 2006-08-01 | Gandhi et al. | Applicant |
| US7089307(B2) | 2006-08-01 | Zintel et al. | Applicant |
| US7130895(B2) | 2006-10-01 | Zintel et al. | Applicant |
| US7161934(B2) | 2007-01-01 | Buchsbaum | Applicant |
| US7171475(B2) | 2007-01-01 | Weisman et al. | Applicant |
| US7187925(B2) | 2007-03-01 | Abhishek | Applicant |
| US7203508(B2) | 2007-04-01 | Ohkubo et al. | Applicant |
| US7269174(B2) | 2007-09-01 | Olson et al. | Applicant |
| US7289505(B2) | 2007-10-01 | Sanchez | Applicant |
| US7355997(B2) | 2008-04-01 | Qian | Applicant |
| US7369510(B1) | 2008-05-01 | Wong | Applicant |
| US7505447(B2) | 2009-03-01 | Kish et al. | Applicant |
| US2001/0047474(A1) | 2001-11-01 | Takagi et al. | Applicant |
| US2001/0055312(A1) | 2001-12-01 | Negus | Applicant |
| US2002/0001310(A1) | 2002-01-01 | Mai | Applicant |
| US2002/0031130(A1) | 2002-03-01 | Tsuchiya et al. | Applicant |
| US2002/0045435(A1) | 2002-04-01 | Fantaske | Applicant |
| US2002/0047800(A1) | 2002-04-01 | Proctor, Jr. et al. | Applicant |
| US2002/0080767(A1) | 2002-06-01 | Lee | Applicant |
| US2002/0084942(A1) | 2002-07-01 | Tsai et al. | Applicant |
| US2002/0105471(A1) | 2002-08-01 | Kojima et al. | Applicant |
| US2002/0112058(A1) | 2002-08-01 | Weisman et al. | Applicant |
| US2002/0114330(A1) | 2002-08-01 | Cheung et al. | Applicant |
| US2002/0143951(A1) | 2002-10-01 | Khan | Applicant |
| US2002/0158798(A1) | 2002-10-01 | Chiang et al. | Applicant |
| US2002/0164963(A1) | 2002-11-01 | Tehrani et al. | Applicant |
| US2002/0170064(A1) | 2002-11-01 | Monroe et al. | Applicant |
| US2003/0026240(A1) | 2003-02-01 | Eyuboglu et al. | Applicant |
| US2003/0030588(A1) | 2003-02-01 | Kalis et al. | Applicant |
| US2003/0063591(A1) | 2003-04-01 | Leung et al. | Applicant |
| US2003/0122714(A1) | 2003-07-01 | Wannagot et al. | Applicant |
| US2003/0169330(A1) | 2003-09-01 | Ben-Shachar et al. | Applicant |
| US2003/0184490(A1) | 2003-10-01 | Raiman et al. | Applicant |
| US2003/0189514(A1) | 2003-10-01 | Miyano et al. | Applicant |
| US2003/0189521(A1) | 2003-10-01 | Yamamoto et al. | Applicant |
| US2003/0189523(A1) | 2003-10-01 | Ojantakanen et al. | Applicant |
| US2003/0210207(A1) | 2003-11-01 | Suh et al. | Applicant |
| US2003/0227414(A1) | 2003-12-01 | Saliga et al. | Applicant |
| US2004/0008663(A1) | 2004-01-01 | Srikrishna | Applicant |
| US2004/0014432(A1) | 2004-01-01 | Boyle | Applicant |
| US2004/0017310(A1) | 2004-01-01 | Runkle et al. | Applicant |
| US2004/0017860(A1) | 2004-01-01 | Liu | Applicant |
| US2004/0027291(A1) | 2004-02-01 | Zhang et al. | Applicant |
| US2004/0027304(A1) | 2004-02-01 | Chiang et al. | Applicant |
| US2004/0028006(A1) | 2004-02-01 | Kayama | Applicant |
| US2004/0032378(A1) | 2004-02-01 | Volman et al. | Applicant |
| US2004/0036651(A1) | 2004-02-01 | Toda | Applicant |
| US2004/0036654(A1) | 2004-02-01 | Hsieh | Applicant |
| US2004/0041732(A1) | 2004-03-01 | Aikawa et al. | Applicant |
| US2004/0048593(A1) | 2004-03-01 | Sano | Applicant |
| US2004/0058690(A1) | 2004-03-01 | Ratzel et al. | Applicant |
| US2004/0061653(A1) | 2004-04-01 | Webb et al. | Applicant |
| US2004/0070543(A1) | 2004-04-01 | Masaki | Applicant |
| US2004/0080455(A1) | 2004-04-01 | Lee | Applicant |
| US2004/0095278(A1) | 2004-05-01 | Kanemoto et al. | Applicant |
| US2004/0114535(A1) | 2004-06-01 | Hoffmann et al. | Applicant |
| US2004/0125777(A1) | 2004-07-01 | Doyle et al. | Applicant |
| US2004/0190477(A1) | 2004-09-01 | Olson | Applicant |
| US2004/0260800(A1) | 2004-12-01 | Gu et al. | Applicant |
| US2004/0264463(A1) | 2004-12-01 | Fukushima | Applicant |
| US2005/0002395(A1) | 2005-01-01 | Kondo | Applicant |
| US2005/0009523(A1) | 2005-01-01 | Pekonen | Examiner |
| US2005/0022210(A1) | 2005-01-01 | Zintel et al. | Applicant |
| US2005/0041739(A1) | 2005-02-01 | Li et al. | Applicant |
| US2005/0042988(A1) | 2005-02-01 | Hoek et al. | Applicant |
| US2005/0074108(A1) | 2005-04-01 | Dezonno et al. | Applicant |
| US2005/0097503(A1) | 2005-05-01 | Zintel et al. | Applicant |
| US2005/0135480(A1) | 2005-06-01 | Li et al. | Applicant |
| US2005/0138137(A1) | 2005-06-01 | Encarnacion et al. | Applicant |
| US2005/0138193(A1) | 2005-06-01 | Encarnacion et al. | Applicant |
| US2005/0180381(A1) | 2005-08-01 | Retzer et al. | Applicant |
| US2005/0185666(A1) | 2005-08-01 | Raya et al. | Applicant |
| US2005/0188193(A1) | 2005-08-01 | Kuehnel et al. | Applicant |
| US2005/0226239(A1) | 2005-10-01 | Nishida et al. | Applicant |
| US2005/0240665(A1) | 2005-10-01 | Gu et al. | Applicant |
| US2005/0250544(A1) | 2005-11-01 | Grant et al. | Applicant |
| US2005/0267935(A1) | 2005-12-01 | Gandhi et al. | Applicant |
| US2006/0018335(A1) | 2006-01-01 | Koch | Applicant |
| US2006/0094371(A1) | 2006-05-01 | Nguyen | Applicant |
| US2006/0098605(A1) | 2006-05-01 | Li | Applicant |
| US2006/0098607(A1) | 2006-05-01 | Zeng et al. | Applicant |
| US2006/0098613(A1) | 2006-05-01 | Kish et al. | Applicant |
| US2006/0114881(A1) | 2006-06-01 | Chari et al. | Applicant |
| US2006/0123124(A1) | 2006-06-01 | Weisman et al. | Applicant |
| US2006/0123125(A1) | 2006-06-01 | Weisman et al. | Applicant |
| US2006/0123455(A1) | 2006-06-01 | Pai et al. | Applicant |
| US2006/0165029(A1) | 2006-07-01 | Melpignano et al. | Applicant |
| US2006/0168159(A1) | 2006-07-01 | Weisman et al. | Applicant |
| US2006/0184661(A1) | 2006-08-01 | Weisman et al. | Applicant |
| US2006/0184693(A1) | 2006-08-01 | Rao et al. | Applicant |
| US2006/0187660(A1) | 2006-08-01 | Liu | Applicant |
| US2006/0224690(A1) | 2006-10-01 | Falkenburg et al. | Applicant |
| US2006/0225107(A1) | 2006-10-01 | Seetharaman et al. | Applicant |
| US2006/0227761(A1) | 2006-10-01 | Scott, III et al. | Applicant |
| US2006/0239369(A1) | 2006-10-01 | Lee | Applicant |
| US2006/0268881(A1) | 2006-11-01 | Moreton | Applicant |
| US2006/0291434(A1) | 2006-12-01 | Gu et al. | Applicant |
| US2007/0002750(A1) | 2007-01-01 | Sang et al. | Applicant |
| US2007/0010271(A1) | 2007-01-01 | Roy | Applicant |
| US2007/0027622(A1) | 2007-02-01 | Cleron et al. | Applicant |
| US2007/0030811(A1) | 2007-02-01 | Frei et al. | Applicant |
| US2007/0109961(A1) | 2007-05-01 | Liang | Applicant |
| US2007/0135167(A1) | 2007-06-01 | Liu | Applicant |
| US2007/0189283(A1) | 2007-08-01 | Agarwal et al. | Applicant |
| US2007/0223451(A1) | 2007-09-01 | Ren et al. | Applicant |
| US2008/0043638(A1) | 2008-02-01 | Ribiere | Applicant |
| US2008/0069068(A1) | 2008-03-01 | Dean et al. | Applicant |
| US2008/0225804(A1) | 2008-09-01 | Thubert | Applicant |
| US2008/0247317(A1) | 2008-10-01 | Weil et al. | Applicant |
| US2008/0247327(A1) | 2008-10-01 | Weil et al. | Applicant |
| US2008/0267116(A1) | 2008-10-01 | Kang et al. | Applicant |
| US2009/0067369(A1) | 2009-03-01 | Stamoulis | Applicant |
| US2009/0213730(A1) | 2009-08-01 | Zeng et al. | Applicant |
| EP352787 | 1989-07-01 | Applicant | |
| EP534612 | 1993-03-01 | Applicant | |
| EP1315311 | 2003-05-01 | Applicant | |
| EP11450521 | 2004-08-01 | Applicant | |
| EP1608108 | 2005-12-01 | Applicant | |
| JP3038933 | 1989-07-01 | Applicant | |
| JP8088633 | 1996-04-01 | Applicant | |
| JP2001057560 | 2001-02-01 | Applicant | |
| JP2005354249 | 2005-12-01 | Applicant | |
| JP2006060408 | 2006-03-01 | Applicant | |
| WOW00225967 | 2002-03-01 | Applicant | |
| WOW00249360 | 2002-06-01 | Applicant | |
| WOW003079484 | 2003-09-01 | Applicant |
Non-Patent Literature (29)
- Hirayama et al., Next-Generation Mobil-Access IP Network, Hitachi Review, vol. 49 (2000), No. 4, pp. 176-179.Applicant
- Hjalmtysson et al., Overcoming Last-Hop/First-Hop Problems in IP Multicast, Reykjavik University, Dept. of Computer Science, Ofanleiti 2, 103 Reykjavik, Iceland, (The Icelandic Centre for Research under grant No. 020500002.).Applicant
- Visoottiviseth et al., Sender-Initiated Multicast Forwarding Scheme, Telecommunications, 2003, ICT 2003 10th International Conference, pp. 334-339, downloaded on Mar. 26, 2009 from IEEE Xplore, 0-7803-7661 (c) 2003 IEEE.Applicant
- Tang et al., Mac Reliable Broadcast in Ad Hoc Networks, Computer Science Dept., University of California, Los Angeles, pp. 1008-1013, 0-7803-7225 (c) 2001 IEEE.Applicant
- Tsunekawa, Kouichi, “Diversity Antennas for Portable Telephones”, 39th IEEE Vehicular Technology Conference, pp. 50-56, vol. 1, Gateway to New Concepts in Vehicular Technology, May 1-3, 1989, San Francisco, CA.Applicant
- Dell Inc., “How Much Broadcast and Multicast Traffic Should I Allow in My Network,” PowerConnect Application Note #5, Nov. 2003.Applicant
- Toskala, Antti, “Enhancement of Broadcast and Introduction of Multicast Capabilities in RAN,” Nokia Networks, Palm Springs, California, Mar. 13-16, 2001.Applicant
- Microsoft Corporation, “IEEE 802.11 Networks and Windows XP,” Windows Hardware Developer Central, Dec. 4, 2001.Applicant
- Festag, Andreas, “What is MOMBASA?” Telecommunication Networks Group (TKN), Technical University of Berlin, Mar. 7, 2002.Applicant
- Hewlett Packard, “HP ProCurve Networking: Enterprise Wireless LAN Networking and Mobility Solutions,” 2003.Applicant
- Dutta, Ashutosh et al., “MarconiNet Supporting Streaming Media Over Localized Wireless Multicast,” Proc. of the 2d Int'l Workshop on Mobile Commerce, 2002.Applicant
- Dunkels, Adam et al., “Making TCP/IP Viable for Wireless Sensor Networks,” Proc. of the 1st Euro. Workshop on Wireless Sensor Networks, Berlin, Jan. 2004.Applicant
- Dunkels, Adam et al., “Connecting Wireless Sensornets with TCP/IP Networks,” Proc. Of the 2d Int'l Conf. on Wired Networks, Frankfurt, Feb. 2004.Applicant
- Cisco Systems, “Cisco Aironet Access Point Software Configuration Guide: Configuring Filters and Quality of Service,” Aug. 2003.Applicant
- Ken Tang, et al., “MAC Layer Broadcast Support in 802.11 Wireless Networks,” Computer Science Department, University of California, Los Angeles, 2000 IEEE, pp. 544-548.Applicant
- Vincent D. Park, et al., “A Performance Comparison of the Temporally-Ordered Routing Algorithm and Ideal Link-State Routing,” IEEE, Jul. 1998, pp. 592-598.Applicant
- Ian F. Akyildiz, et al., “A Virtual Topology Based Routing Protocol for Multihop Dynamic Wireless Networks,” Broadband and Wireless Networking Lab, School of Electrical and Computer Engineering, Georgia Institute of Technology.Applicant
- Pat Calhoun et al., “802.11r strengthens wireless voice,” Technology Update, Network World, Aug. 22, 2005, http://www.networkworld.com/news/tech/2005/082208techupdate.html.Applicant
- Areg Alimian et al., “Analysis of Roaming Techniques,” doc.:IEEE 802.11-04/0377r1, Submission, Mar. 2004.Applicant
- Information Society Technologies Ultrawaves, “System Concept / Architecture Design and Communication Stack Requirement Document,” Feb. 23, 2004.Applicant
- Golmie, Nada, “Coexistence in Wireless Networks: Challenges and System-Level Solutions in the Unlicensed Bands,” Cambridge University Press, 2006.Applicant
- Mawa, Rakesh, “Power Control in 3G Systems,” Hughes Systique Corporation, Jun. 28, 2006.Applicant
- Wennstrom, Mattias et al., “Transmit Antenna Diversity in Ricean Fading MIMO Channels with Co-Channel Interference,” 2001.Applicant
- Steger, Christopher et al., “Performance of IEEE 802.11b Wireless LAN in an Emulated Mobile Channel,” 2003.Applicant
- Chang, Nicholas B. et al., “Optimal Channel Probing and Transmission Scheduling for Opportunistics Spectrum Access,” Sep. 2007.Applicant
- Gillham, Bruce et al. JUNOSe Internet Software for E-series Routing Platforms Policy and QoS Configuration Guide, Release 7.0x.Applicant
- Fair queuing, http://en.wikipedia.org/wiki/Fair—queuing.Applicant
- Weighted Fair Queuing, http://en.wikipedia.org/wiki/Weighted—fair—queuing.Applicant
- Weighted Round Robin, http://en.wikipedia.org/wiki/Weighted—round—robin.Applicant