Distributed access point for IP based communications

Information

  • Patent Grant
  • 9661475
  • Patent Number
    9,661,475
  • Date Filed
    Tuesday, June 23, 2015
    9 years ago
  • Date Issued
    Tuesday, May 23, 2017
    7 years ago
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.
Description
BACKGROUND OF THE INVENTION

Field of the Invention


The present invention generally relates to communications networks and more particularly to systems and methods for increased data throughput in communications networks.


Description of the Related Art


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.


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.


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.


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.


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.”


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.


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 PRESENTLY CLAIMED INVENTION

A claimed embodiment of the present invention is for a distributed access point for Internet-Protocol based communications in a wireless network.


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.


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.


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


FIG. 1 illustrates a block diagram of a system for multicast transmission in a wireless local area network;



FIG. 2 illustrates an exemplary method for multicast or unicast transmission in the wireless local area network of FIG. 1;



FIG. 3 illustrates an exemplary timing diagram illustrating conversion of multicast packets into unicast packets as described with respect to FIGS. 1-2; and



FIG. 4 illustrates an apparatus for Internet-Protocol based communications in a wireless network and that may implement multicast to unicast conversion.



FIG. 5 illustrates a system for Internet-Protocol based communications in a wireless network.





DETAILED DESCRIPTION

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.


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.



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.


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.


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.


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.


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.


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.


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.


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.



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.


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.


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.


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.


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.


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).


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.


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.



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.


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.


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.



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.


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.


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.


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.


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.


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.


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.



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.


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.


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 include 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.


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.


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.


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
  • 1. An apparatus for Internet-Protocol based communications in a wireless network, the apparatus comprising: a network interface to receive a plurality of multicast data packets, from a wireless access point;a memory; anda processor, the processor executing instructions stored in the memory to: identify one or more receiving nodes in the wireless network requesting data corresponding to the plurality of multicast data packets,determine that an effective unicast rate for one or more unicast data packets exceeds a minimum data rate of the plurality of multicast data packets using a wireless protocol, andconvert the received plurality of multicast data packets into one or more unicast packets, in response to instructions received by the processor.
  • 2. The apparatus of claim 1, wherein the processor executes a software application stored in memory, independent of the instructions stored in the memory, to convert the received plurality of multicast data packets into one or more unicast packets, to identify the one or more receiving nodes and to determine that the effective unicast rate for the one or more unicast data packets exceeds a minimum data rate of the plurality of multicast data packets.
  • 3. The apparatus of claim 1, wherein the processor further executes instructions stored in the memory to assign each of the one or more receiving nodes in the wireless network to a group of receiving nodes.
  • 4. The apparatus of claim 3, further comprising a plurality of radios, wherein each group of receiving nodes is assigned to one or more radios from the plurality of radios, and wherein 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.
  • 5. The apparatus of claim 1, wherein the network interface is a wired computer network interface.
  • 6. The apparatus of claim 4, wherein each group of receiving nodes is assigned to one or more radios from a plurality of radios at the wireless access point, the processor sends the one or more unicast data packets over the network interface to the wireless access point and the wireless access point transmits the one or more unicast packets over the one or more radios to each group of receiving nodes.
  • 7. The apparatus of claim 1, 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.
  • 8. The apparatus of claim 7, wherein the processor, the memory, and the wireless network interface are on a common motherboard.
  • 9. The apparatus of claim 7, wherein the processor and the wireless network interface are on separate boards.
CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent application Ser. No. 14/160,402 filed Jan. 21, 2014, which is a continuation of U.S. patent application Ser. No. 13/298,927 filed Nov. 17, 2011, now U.S. Pat. No. 8,634,402, which is a continuation of U.S. patent application Ser. No. 12/719,006 filed Mar. 8, 2010, now U.S. Pat. No. 8,089,949, which is a continuation-in-part of U.S. patent application Ser. No. 11/985,866 filed Nov. 16, 2007, now U.S. Pat. No. 7,787,436, which is a divisional of U.S. patent application Ser. No. 11/232,196 filed Sep. 20, 2005, now U.S. Pat. No. 7,505,447, which claims the priority benefit of U.S. provisional application 60/625,331 filed Nov. 5, 2004, the disclosures of which are incorporated herein by reference. U.S. patent application Ser. No. 13/298,927 is related to U.S. patent application Ser. No. 11/010,076 filed Dec. 9, 2004, now U.S. Pat. No. 7,292,198; U.S. patent application Ser. No. 11/022,080 filed Dec. 23, 2004, now U.S. Pat. No. 7,193,562; and U.S. patent application Ser. No. 11/041,145 filed Jan. 21, 2005, now U.S. Pat. No. 7,362,280, the disclosures of which are incorporated herein by reference. U.S. patent application Ser. No. 13/298,927 is related to U.S. patent application Ser. No. 11/985,865 filed Nov. 16, 2007, now U.S. Pat. No. 8,125,975, which is a divisional of U.S. patent application Ser. No. 11/232,196 filed Sep. 20, 2005, now U.S. Pat. No. 7,505,447, the disclosures of which are incorporated herein by reference.

US Referenced Citations (324)
Number Name Date Kind
1653664 Kirkup Dec 1927 A
4176356 Foster et al. Nov 1979 A
4193077 Greenberg et al. Mar 1980 A
4253193 Kennard Feb 1981 A
4305052 Baril et al. Dec 1981 A
4513412 Cox Apr 1985 A
4814777 Monser Mar 1989 A
5097484 Akaiwa Mar 1992 A
5117430 Berglund May 1992 A
5173711 Takeuchi et al. Dec 1992 A
5203010 Felix Apr 1993 A
5220340 Shafai Jun 1993 A
5220678 Feei Jun 1993 A
5361256 Doeringer Nov 1994 A
5373548 McCarthy Dec 1994 A
5408465 Gusella et al. Apr 1995 A
5507035 Bantz Apr 1996 A
5559800 Mousseau et al. Sep 1996 A
5570366 Baker Oct 1996 A
5608726 Virgile Mar 1997 A
5636213 Eastmond et al. Jun 1997 A
5754145 Evans May 1998 A
5767809 Chuang et al. Jun 1998 A
5802312 Lazaridis et al. Sep 1998 A
5867109 Wiedeman Feb 1999 A
5930259 Katsube Jul 1999 A
5940771 Gollnick et al. Aug 1999 A
5960344 Mahany Sep 1999 A
5964830 Durrett Oct 1999 A
5970410 Carney et al. Oct 1999 A
5974034 Chin et al. Oct 1999 A
6018659 Ayyagari et al. Jan 2000 A
6034638 Thiel et al. Mar 2000 A
6044062 Brownrigg et al. Mar 2000 A
6088570 Komara et al. Jul 2000 A
6094177 Yamamoto Jul 2000 A
6132306 Trompower Oct 2000 A
6181697 Nurenbreg Jan 2001 B1
6249516 Brownrigg et al. Jun 2001 B1
6266528 Farzaneh Jul 2001 B1
6266537 Kashitani et al. Jul 2001 B1
6292153 Aiello et al. Sep 2001 B1
6307524 Britain Oct 2001 B1
6317599 Rappaport et al. Nov 2001 B1
6326922 Hegendoerfer Dec 2001 B1
6337628 Campana et al. Jan 2002 B2
6337668 Ito et al. Jan 2002 B1
6339404 Johnson et al. Jan 2002 B1
6345043 Hsu Feb 2002 B1
6356242 Ploussios Mar 2002 B1
6356243 Schneider et al. Mar 2002 B1
6356553 Nagami et al. Mar 2002 B1
6356905 Gershman et al. Mar 2002 B1
6377227 Zhu et al. Apr 2002 B1
6392610 Braun et al. May 2002 B1
6393261 Lewis May 2002 B1
6404386 Proctor, Jr. et al. Jun 2002 B1
6404775 Leslie et al. Jun 2002 B1
6407719 Ohira et al. Jun 2002 B1
6414955 Clare et al. Jul 2002 B1
6418138 Cerf et al. Jul 2002 B1
6442507 Skidmore et al. Aug 2002 B1
6445688 Garces et al. Sep 2002 B1
6493679 Rappapport et al. Dec 2002 B1
6498589 Horii Dec 2002 B1
6499006 Rappaport et al. Dec 2002 B1
6505253 Chiu Jan 2003 B1
6507321 Oberschmidt et al. Jan 2003 B2
6570883 Wong May 2003 B1
6584080 Ganz et al. Jun 2003 B1
6625454 Rappaport et al. Sep 2003 B1
6674459 Ben-Shachar et al. Jan 2004 B2
6701522 Rubin et al. Mar 2004 B1
6704301 Chari et al. Mar 2004 B2
6714551 Le-Ngoc Mar 2004 B1
6725281 Zintel et al. Apr 2004 B1
6728514 Bandeira et al. Apr 2004 B2
6753814 Killen et al. Jun 2004 B2
6762723 Nallo et al. Jul 2004 B2
6778517 Lou et al. Aug 2004 B1
6779004 Zintel Aug 2004 B1
6819287 Sullivan et al. Nov 2004 B2
6836481 Hotta Dec 2004 B1
6873627 Miller Mar 2005 B1
6876280 Nakano Apr 2005 B2
6888504 Chiang et al. May 2005 B2
6888893 Li et al. May 2005 B2
6892230 Gu et al. May 2005 B1
6906678 Chen Jun 2005 B2
6910068 Zintel et al. Jun 2005 B2
6924768 Wu et al. Aug 2005 B2
6931429 Gouge et al. Aug 2005 B2
6941143 Mathur Sep 2005 B2
6950019 Bellone et al. Sep 2005 B2
6957042 Williams Oct 2005 B2
6957277 Yagyu et al. Oct 2005 B2
6961028 Joy et al. Nov 2005 B2
6973622 Rappaport et al. Dec 2005 B1
6975834 Forster Dec 2005 B1
6996086 Wolfe et al. Feb 2006 B2
7034770 Yang et al. Apr 2006 B2
7043277 Pfister May 2006 B1
7050809 Lim May 2006 B2
7053853 Merenda et al. May 2006 B2
7064717 Kaluzni et al. Jun 2006 B2
7076274 Jollota et al. Jul 2006 B2
7085814 Ghandhi et al. Aug 2006 B1
7089307 Zintel et al. Aug 2006 B2
7113519 Hammel et al. Sep 2006 B2
7130895 Zintel et al. Oct 2006 B2
7136655 Skafidas et al. Nov 2006 B2
7149197 Garahi et al. Dec 2006 B2
7157757 Parekh et al. Jan 2007 B2
7161934 Buchsbaum Jan 2007 B2
7164667 Rayment et al. Jan 2007 B2
7171223 Herscovich et al. Jan 2007 B2
7171475 Weisman et al. Jan 2007 B2
7187925 Abhishek Mar 2007 B2
7203508 Ohkubo et al. Apr 2007 B2
7269174 Olson et al. Sep 2007 B2
7283494 Hammel et al. Oct 2007 B2
7289505 Sanchez Oct 2007 B2
7292617 Beasley et al. Nov 2007 B2
7321571 Schnack et al. Jan 2008 B2
7336642 Rich et al. Feb 2008 B2
7355997 Qian Apr 2008 B2
7362737 Behroozi Apr 2008 B2
7369510 Wong May 2008 B1
7489932 Chari et al. Feb 2009 B2
7496680 Canright Feb 2009 B2
7505426 Srikrishna et al. Mar 2009 B2
7505447 Kish et al. Mar 2009 B2
7515589 Bacher et al. Apr 2009 B2
7522731 Kiemba et al. Apr 2009 B2
7546126 Beasley et al. Jun 2009 B2
7551562 Srikrishna et al. Jun 2009 B2
7586879 Chari et al. Sep 2009 B2
7672274 Bims Mar 2010 B2
7697504 Chari et al. Apr 2010 B2
7715395 Ginchereau et al. May 2010 B2
7733833 Kalika et al. Jun 2010 B2
7787436 Kish et al. Aug 2010 B2
7852837 Au et al. Dec 2010 B1
7853829 Younger et al. Dec 2010 B2
7916684 Henderson et al. Mar 2011 B2
7974223 Zelig et al. Jul 2011 B2
8089869 Kisela et al. Jan 2012 B2
8089949 Kish et al. Jan 2012 B2
8125975 Kish et al. Feb 2012 B2
8355343 Kish et al. Jan 2013 B2
8547899 Kish Oct 2013 B2
8619662 Kish Dec 2013 B2
8634402 Kish Jan 2014 B2
8638708 Kish Jan 2014 B2
8688834 Fujimoto et al. Apr 2014 B2
8780760 Kish Jul 2014 B2
8824357 Kish et al. Sep 2014 B2
9019886 Kish Apr 2015 B2
9066152 Kish Jun 2015 B2
9071942 Kish Jun 2015 B2
9240868 Kish Jan 2016 B2
20010047474 Takagi et al. Nov 2001 A1
20010055312 Negus Dec 2001 A1
20020001310 Mai Jan 2002 A1
20020031130 Tsuchiya et al. Mar 2002 A1
20020036996 Ozluturk et al. Mar 2002 A1
20020045435 Fantaske Apr 2002 A1
20020047800 Proctor, Jr. et al. Apr 2002 A1
20020080767 Lee Jun 2002 A1
20020084942 Tsai et al. Jul 2002 A1
20020105471 Kojima et al. Aug 2002 A1
20020112058 Weisman et al. Aug 2002 A1
20020114330 Cheung Aug 2002 A1
20020143951 Khan Oct 2002 A1
20020158798 Chiang et al. Oct 2002 A1
20020158801 Crilly, Jr. et al. Oct 2002 A1
20020164963 Tehrani et al. Nov 2002 A1
20020170064 Monroe et al. Nov 2002 A1
20020194367 Nakamura et al. Dec 2002 A1
20030003917 Copley et al. Jan 2003 A1
20030026240 Eyuboglu et al. Feb 2003 A1
20030026268 Nava Feb 2003 A1
20030030588 Kalis et al. Feb 2003 A1
20030043786 Kall et al. Mar 2003 A1
20030063591 Leung et al. Apr 2003 A1
20030122714 Wannagot et al. Jul 2003 A1
20030128711 Olariu et al. Jul 2003 A1
20030129978 Akiyama et al. Jul 2003 A1
20030133458 Sato et al. Jul 2003 A1
20030169330 Ben-Shachar et al. Sep 2003 A1
20030184490 Raiman et al. Oct 2003 A1
20030189514 Miyano et al. Oct 2003 A1
20030189521 Yamamoto et al. Oct 2003 A1
20030189523 Ojantakanen et al. Oct 2003 A1
20030210207 Suh et al. Nov 2003 A1
20030227414 Saliga et al. Dec 2003 A1
20030228857 Maeki Dec 2003 A1
20030231593 Bauman et al. Dec 2003 A1
20040008663 Srikrishna Jan 2004 A1
20040014432 Boyle Jan 2004 A1
20040017310 Vargas-Hurlston et al. Jan 2004 A1
20040017860 Liu Jan 2004 A1
20040027291 Zhang et al. Feb 2004 A1
20040027304 Chiang et al. Feb 2004 A1
20040028006 Kayama Feb 2004 A1
20040032378 Volman et al. Feb 2004 A1
20040036651 Toda Feb 2004 A1
20040036654 Hsieh Feb 2004 A1
20040041732 Aikawa et al. Mar 2004 A1
20040048593 Sano Mar 2004 A1
20040058690 Ratzel et al. Mar 2004 A1
20040061653 Webb et al. Apr 2004 A1
20040070543 Masaki Apr 2004 A1
20040080455 Lee Apr 2004 A1
20040085993 Wentink May 2004 A1
20040095278 Kanemoto et al. May 2004 A1
20040114535 Hoffmann et al. Jun 2004 A1
20040125777 Doyle et al. Jul 2004 A1
20040190477 Olson et al. Sep 2004 A1
20040194143 Hirose Sep 2004 A1
20040260800 Gu et al. Dec 2004 A1
20040264463 Fukushima Dec 2004 A1
20050002395 Kondo Jan 2005 A1
20050009523 Pekonen Jan 2005 A1
20050022210 Zintel et al. Jan 2005 A1
20050032531 Gong et al. Feb 2005 A1
20050041739 Li et al. Feb 2005 A1
20050042988 Hoek et al. Feb 2005 A1
20050074018 Zintel et al. Apr 2005 A1
20050074019 Handforth et al. Apr 2005 A1
20050074108 Dezonno et al. Apr 2005 A1
20050097503 Zintel et al. May 2005 A1
20050100016 Miller May 2005 A1
20050135480 Li et al. Jun 2005 A1
20050138137 Encarnacion et al. Jun 2005 A1
20050138193 Encarnacion et al. Jun 2005 A1
20050153720 White et al. Jul 2005 A1
20050180381 Retzer et al. Aug 2005 A1
20050185666 Raya Aug 2005 A1
20050188193 Kuehnel et al. Aug 2005 A1
20050226239 Nishida et al. Oct 2005 A1
20050232179 Da Costa et al. Oct 2005 A1
20050240665 Gu et al. Oct 2005 A1
20050250544 Grant et al. Nov 2005 A1
20050259682 Yosef Nov 2005 A1
20050267935 Ghandhi et al. Dec 2005 A1
20050271070 Mikami et al. Dec 2005 A1
20060018335 Koch Jan 2006 A1
20060045089 Bacher et al. Mar 2006 A1
20060092864 Gupta et al. May 2006 A1
20060094371 Nguyen May 2006 A1
20060098605 Li May 2006 A1
20060098607 Zeng et al. May 2006 A1
20060098613 Kish et al. May 2006 A1
20060098616 Kish et al. May 2006 A1
20060114881 Chari Jun 2006 A1
20060123124 Weisman et al. Jun 2006 A1
20060123125 Weisman et al. Jun 2006 A1
20060123455 Pai et al. Jun 2006 A1
20060133341 Chari et al. Jun 2006 A1
20060165029 Melpignano et al. Jul 2006 A1
20060168159 Weisman et al. Jul 2006 A1
20060184660 Rao et al. Aug 2006 A1
20060184661 Weisman et al. Aug 2006 A1
20060184693 Rao et al. Aug 2006 A1
20060224690 Falkenburg et al. Oct 2006 A1
20060225107 Seetharaman et al. Oct 2006 A1
20060227761 Scott, III et al. Oct 2006 A1
20060239369 Lee Oct 2006 A1
20060268881 Moreton Nov 2006 A1
20060280131 Rahman et al. Dec 2006 A1
20060291434 Gu et al. Dec 2006 A1
20070002750 Sang et al. Jan 2007 A1
20070002858 Bichot Jan 2007 A1
20070010271 Roy Jan 2007 A1
20070027622 Cleron et al. Feb 2007 A1
20070030811 Frei et al. Feb 2007 A1
20070072612 Haraguchi et al. Mar 2007 A1
20070101020 Lin et al. May 2007 A1
20070109961 Liang May 2007 A1
20070135167 Liu Jun 2007 A1
20070189283 Agarwal et al. Aug 2007 A1
20070223451 Ren et al. Sep 2007 A1
20070242602 Pang et al. Oct 2007 A1
20070280168 Shibata Dec 2007 A1
20080043638 Ribiere Feb 2008 A1
20080063002 Zheng et al. Mar 2008 A1
20080069068 Dean et al. Mar 2008 A1
20080137681 Kish et al. Jun 2008 A1
20080137682 Kish et al. Jun 2008 A1
20080159207 Levine et al. Jul 2008 A1
20080225804 Thubert Sep 2008 A1
20080247317 Weil et al. Oct 2008 A1
20080247327 Weil et al. Oct 2008 A1
20080267116 Kang et al. Oct 2008 A1
20080305743 Aithal et al. Dec 2008 A1
20090019314 Younger et al. Jan 2009 A1
20090028095 Kish et al. Jan 2009 A1
20090040989 Da Costa et al. Feb 2009 A1
20090067369 Stamoulis Mar 2009 A1
20090073921 Ji et al. Mar 2009 A1
20090080333 Ozer et al. Mar 2009 A1
20090154359 Strutt et al. Jun 2009 A1
20090180396 Kish et al. Jul 2009 A1
20090207730 Stamoulis et al. Aug 2009 A1
20090213730 Zeng et al. Aug 2009 A1
20090225676 Kisela et al. Sep 2009 A1
20090262677 Banerjea et al. Oct 2009 A1
20100040056 Kobayashi Feb 2010 A1
20100085916 Yu et al. Apr 2010 A1
20100182944 Kish et al. Jul 2010 A1
20110019653 Seok Jan 2011 A1
20110096712 Kish et al. Apr 2011 A1
20110119360 Miu et al. May 2011 A1
20110119401 Miu et al. May 2011 A1
20110158233 Namgung Jun 2011 A1
20110216685 Kish et al. Sep 2011 A1
20120063379 Kish et al. Mar 2012 A1
20130010775 Kish et al. Jan 2013 A1
20130194969 Kish Aug 2013 A1
20140016563 Kish Jan 2014 A1
20140071879 Kish Mar 2014 A1
20140133385 Kish May 2014 A1
20140177511 Kish Jun 2014 A1
Foreign Referenced Citations (26)
Number Date Country
1 965 598 May 2007 CN
102763378 Oct 2012 CN
0 352 787 Jul 1989 EP
0 534 612 Mar 1993 EP
1 315 311 May 2003 EP
1 450 521 Aug 2004 EP
1 608 108 Dec 2005 EP
1 653 664 May 2006 EP
2 350 863 Aug 2015 EP
2306278 Apr 1997 GB
2003-038933 Jul 1989 JP
2008-088633 Feb 1996 JP
2001-057560 Feb 2002 JP
2005-354249 Dec 2005 JP
2006-060408 Mar 2006 JP
31159 Oct 2012 VN
WO 0225967 Mar 2002 WO
WO 0249360 Jun 2002 WO
WO 03079484 Sep 2003 WO
WO 2004057817 Jul 2004 WO
WO 2005008938 Jan 2005 WO
WO 2006052639 May 2006 WO
WO 2007016326 Feb 2007 WO
WO 2009088488 Jul 2009 WO
WO 2011060454 May 2011 WO
WO 2012061531 May 2012 WO
Non-Patent Literature Citations (85)
Entry
U.S. Appl. No. 14/979,018, William S. Kish, Increasing Reliable Data Throughput in a Wireless Network, filed Dec. 22, 2015.
Akyildiz et al., “Wireless mesh networks: a survey,” Computer Networks, 2005.
Areg Alimian et al., “Analysis of Roaming Techniques,” doc.:IEEE 802.11-04/0377r1, Submission, Mar. 2004.
Cato et al., “Method for Easier, Better, and Faster Site Surveys for Wireless Networks,” IBM Technical Disclosure Bulletin, vol. 40, No. 1, 1997.
Chang, Nicholas B. et al., “Optimal Channel Probing and Transmission Scheduling for Opportunistics Spectrum Access,” Sep. 2007.
Chawla, “Design of a Wireless Backhaul Network for Microcells,” 1999.
Cisco Systems, “Cisco Aironet Access Point Software Configuration Guide: Configuring Filters and Quality of Service,” Aug. 2003.
Dell Inc., “How Much Broadcast and Multicast Traffic Should I Allow in My Network,” PowerConnect Application Note #5, Nov. 2003.
Dunkels, Adam et al., “Connecting Wireless Sensornets with TCP/IP Networks,” Proc. of the 2d Int'l Conf. on Wired Networks, Frankfurt, Feb. 2004.
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.
Dutta, Ashutosh et al., “MarconiNet Supporting Streaming Media Over Localized Wireless Multicast,” Proc. of the 2d Int'l Workshop on Mobile Commerce, 2002.
Fair queuing, http://en.wikipedia.org/wiki/fair—queuing. Aug. 11, 2008.
Festag, Andreas, “What is MOMBASA?” Telecommunication Networks Group (TKN), Technical University of Berlin, Mar. 7, 2002.
Gillham, Burce et al. JUNOSe Internet Software for E-Series Routing Platforms Policy and QoS Configuration Guide, Release 7.0x, Sep. 7, 2005.
Golmie, Nada, “Coexistence in Wireless Networks: Challenges and System-Level Solutions in the Unlicensed Bands,” Cambridge University Press, 2006.
Hewlett Packard, “HP ProCurve Networking: Enterprise Wireless LAN Networking and Mobility Solutions,” 2003.
Hirayama, Koji et al., “Next-Generation Mobile-Access IP Network,” Hitachi Review vol. 49, No. 4, 2000.
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 Center for Research under grant No. 020500002.). Sep. 16-19, 2003.
Ian R. 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, Jul. 1, 2001.
Information Society Technologies Ultrawaves, “System Concept / Architecture Design and Communication Stack Requirement Document,” Feb. 23, 2004.
Johansson et al., “Relaying Access Points and Related Business Models for Low Cost Mobile Systems,” 2004.
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.
Ken Tang, et al., “MAC Reliable Broadcast in Ad Hoc Networks,” Computer Science Department, University of California, Los Angeles, 2001 IEEE, pp. 1008-1013.
Mawa, Rakesh, “Power Control in 3G Systems,” Hughes Systique Corporation, Jun. 28, 2006.
Microsoft Corporation, “IEEE 802.11 Networks and Windows XP,” Windows Hardware Developer Central, Dec. 4, 2001.
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.
Steger, Christopher et al., “Performance of IEEE 802.11b Wireless LAN in an Emulated Mobile Channel,” 2003.
Toskala, Antti, “Enhancement of Broadcast and Introduction of Multicast Capabilities in RAN,” Nokia Networks, Palm Springs, California, Mar. 13-16, 2001.
Tsunekawa, Kouichi “Diversity Antennas for Portable Telephones,” 39th IEEE Vehicular Technology, May 1-3, 1989, San Francisco, CA.
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.
Visoottiviseth et al., Sender-Initiated Mulitcast 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.
Weighted Fair Queuing, http://en.wikipedia.org/wiki/Weighted—fair—queuing. Aug. 11, 2008.
Weighted Round Robin, http:en.wikipedia.org/wiki/Weighted—round—robin Aug. 8, 2008.
Wennstrom, Mattias et al., “Transmit Antenna Diversity in Ricean Fading MIMO Channels with Co-Channel Interference,” 2001.
Yanikomeroglu, “Cellular Multihop Communications: Infrastructure-Based Relay Network Architecture for 4G Wireless Systems,” 2004.
PCT Search Report and Written Opinion for PCT/US08/014148 mailed Mar. 30, 2009.
PCT Search Report and Written Opinion for PCT/US11/059019 mailed Feb. 21, 2012.
PCT Search Report and Written Opinion for PCT/US05/039760 mailed Sep. 14, 2006.
PCT Search Report and Written Opinion for PCT/US10/56908 mailed May 3, 2011.
Chinese Application No. 201080002467.X, Second Office Action dated Jan. 26, 2015.
Chinese Application No. 201080002467.X, Office Action dated Jul. 3, 2014.
Chinese Application No. 20058001629.7, Office Action dated Aug. 6, 2014.
Chinese Application No. 20058001629.7, Office Action dated Jan. 21, 2014.
Chinese Application No. 20058001629.7, Office Action dated Feb. 21, 2012.
European Application No. 10813061.8. Supplementary European Search Report dated Jul. 23, 2012.
European Application No. 10813061.8. Extended European Search Report dated Oct. 21, 2011.
Taiwan Application No. 103106913, Office Action dated May 28, 2015.
Taiwan Application No. 094138837, Office Action dated Apr. 25, 2013.
Taiwan Application No. 094138837, Office Action dated Nov. 28, 2011.
U.S. Appl. No. 12/008,715, Office Action mailed Sep. 2, 2011.
U.S. Appl. No. 12/008,715, Final Office Action mailed Nov. 23, 2010.
U.S. Appl. No. 12/008,715, Office Action mailed Jun. 7, 2010.
U.S. Appl. No. 12/008,715, Office Action mailed Oct. 16, 2009.
U.S. Appl. No. 13/736,017 Office Action mailed Nov. 21, 2013.
U.S. Appl. No. 14/160,402 Office Action mailed Oct. 22, 2014.
U.S. Appl. No. 11/232,196, Office Action mailed May 15, 2008.
U.S. Appl. No. 11/232,196, Final Office Action mailed Dec. 26, 2007.
U.S. Appl. No. 11/232,196, Office Action mailed Apr. 5, 2007.
U.S. Appl. No. 14/080,488, Office Action mailed Oct. 21, 2014.
U.S. Appl. No. 11/985,865, Office Action mailed Dec. 20, 2010.
U.S. Appl. No. 11/985,866, Office Action mailed Dec. 16, 2009.
U.S. Appl. No. 11/985,866, Office Action mailed May 29, 2009.
U.S. Appl. No. 11/267,477, Office Action mailed Apr. 8, 2015.
U.S. Appl. No. 11/267,477, Decision on Appeal mailed Nov. 14, 2014.
U.S. Appl. No. 11/267,477, Final Office Action mailed Oct. 6, 2010.
U.S. Appl. No. 11/267,477, Office Action mailed Jun. 16, 2010.
U.S. Appl. No. 11/267,477, Final Office Action mailed Jun. 10, 2009.
U.S. Appl. No. 11/267,477, Office Action mailed Sep. 25, 2008.
U.S. Appl. No. 12/181,274, Final Office Action mailed Jun. 19, 2013.
U.S. Appl. No. 12/181,274, Office Action mailed Nov. 15, 2012.
U.S. Appl. No. 12/181,274, Final Office Action mailed Jan. 18, 2012.
U.S. Appl. No. 12/181,274, Office Action mailed Jun. 10, 2011.
U.S. Appl. No. 14/028,323, Final Office Action mailed Jun. 12, 2015.
U.S. Appl. No. 14/028,323, Office Action mailed Oct. 14, 2014.
U.S. Appl. No. 12/947,800, Office Action mailed Mar. 19, 2015.
U.S. Appl. No. 12/947,800, Final Office Action mailed Jul. 17, 2013.
U.S. Appl. No. 12/947,800, Office Action mailed Sep. 26, 2012.
U.S. Appl. No. 12/947,803, Office Action mailed Mar. 12, 2015.
U.S. Appl. No. 12/947,803, Final Office Action mailed Jul. 17, 2013.
U.S. Appl. No. 12/947,803, Office Action mailed Aug. 27, 2012.
U.S. Appl. No. 12/938,316, Office Action mailed Nov. 20, 2012.
U.S. Appl. No. 14/106,514, Office Action mailed Sep. 22, 2014.
Final Office Action for co-pending U.S. Appl. No. 12/947,800, dated May 18, 2016 (26 sheets).
Final Office Action for co-pending U.S. Appl. No. 12/947,803, dated May 18, 2016 (31 sheets).
Office Action for co-pending U.S. Appl. No. 14/979,018, dated Nov. 4, 2016 (14 sheets).
Related Publications (1)
Number Date Country
20150312727 A1 Oct 2015 US
Provisional Applications (1)
Number Date Country
60625331 Nov 2004 US
Divisions (1)
Number Date Country
Parent 11232196 Sep 2005 US
Child 11985866 US
Continuations (3)
Number Date Country
Parent 14160402 Jan 2014 US
Child 14748141 US
Parent 13298927 Nov 2011 US
Child 14160402 US
Parent 12719006 Mar 2010 US
Child 13298927 US
Continuation in Parts (1)
Number Date Country
Parent 11985866 Nov 2007 US
Child 12719006 US