Multi-communication mode packet routing mechanism

Related Applications This application claims the priority benefit of US Patent Application No. 13 / 026,580 filed on February 14, 2011.

Embodiments of the subject of the invention generally relate to the field of wireless communication networks, and more specifically to multi-communication mode packet routing mechanisms for wireless communication systems.

Wireless communication systems can use one or more communication channels to transfer data between transmitters and receivers. These communication systems can operate according to a set of standards defined by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 Commission for Wireless Local Area Network (WLAN) communications. 802.11b is part of the IEEE 802.11 specification and is a legacy wireless communication standard that enables data transfer between transmitters and receivers at speeds of 1Mbps to 2Mbps.

In some embodiments, the method is to receive a packet in legacy packet format from a host device via a legacy network interface for transmission to a destination network device in a network communication device, and via a legacy network interface. Packets received on a network communication device should be sent using a legacy communication protocol, at least in part based on the operating mode of the host device, or a non-legacy communication protocol out of multiple non-legacy communication protocols. For transmission using a non-legacy communication protocol in response to determining whether the packet should be transmitted using a non-legacy communication protocol To determine the processing path within a network communication device to follow to process a packet, and to reformat a packet in the legacy packet format to generate a target packet in the non-legacy packet format, at least in part based on the non-legacy communication protocol. And to give the target packet to the destination network device according to the non-legacy communication protocol.

In some embodiments, the method intercepts a packet received from a host device in legacy packet format via a legacy network interface and to a packet in legacy packet format received from the host device in a network communication device. It further comprises determining the operating mode of the host device, at least in part.

In some embodiments, the method determines in a network communication device that a packet should not be transmitted using a non-legacy communication protocol, at least in part based on the operating mode of the host device. It further comprises sending packets directly to the destination network device according to the legacy communication protocol.

In some embodiments, the legacy communication protocol comprises the American Association of Electrical and Electronic Engineers (IEEE) 802.11b communication protocol, and the non-legacy communication protocol is the IEEE802.11n communication protocol, the IEEE802.11g communication protocol, and wireless wide. It has one of the Area Network (WWAN) communication protocols.

In some embodiments, determining the processing path to follow to process a packet for transmission using a non-legacy communication protocol results in a target packet in a non-legacy packet format corresponding to the non-legacy communication protocol. To determine which of the multiple non-legacy communication protocols to follow in order to perform the reformatting of packets in the legacy packet format, and the non-legacy communication protocol related to the mode of operation of the host device. It further comprises determining the processing path within the network communication device based on at least one of the address of the destination network device and at least partially.

In some embodiments, the method further comprises converting a packet received through a legacy network interface from a legacy packet format to an intermediate packet format associated with a network communication device.

In some embodiments, reformatting a packet in a legacy packet format to yield a target packet in a non-legacy packet format follows non-legacy to process the packet for transmission using a non-legacy communication protocol. It further comprises identifying the communication protocol and converting the packet from the intermediate packet format associated with the network communication device to the non-legacy packet format corresponding to the non-legacy communication protocol in order to generate the target packet.

In some embodiments, the method receives a second packet in a network communication device in a non-legacy packet format corresponding to a non-legacy communication protocol for transmission to a host device over a legacy network interface. And reformatting the second packet in the non-legacy packet format to generate the second target packet in the legacy packet format, and sending the second target packet in the legacy packet format to the host device through the legacy network interface. Further prepare for giving.

In some embodiments, it is said that determining whether a packet received over a legacy network interface should be transmitted using a legacy communication protocol or a non-legacy communication protocol. For subsequent communication between the network communication device and the destination network device, in response to determining that packets received over the legacy network interface should be transmitted using the legacy communication protocol. In response to choosing a legacy communication protocol and determining that packets received over the legacy network interface should be sent using the non-legacy communication protocol of multiple non-legacy communication protocols. Determining one or more of the multiple non-legacy communication protocols supported by a destination network device, at least in part, based on the address of the destination network device, and between the network communication device and the destination network device. It further comprises selecting one or more of a plurality of non-legacy communication protocols for subsequent communication.

In some embodiments, the network communication device is capable of operating to receive packets in legacy packet format from the host device over the legacy network interface for transmission to the destination network device, with a translation bridge. Packets received by a network communication device over a legacy network interface should be sent using a legacy communication protocol, at least in part based on the operating mode of the host device, or of multiple non-legacy communication protocols. A routing unit that can operate to determine if it should be sent using our non-legacy communication protocol, and a routing unit that says that the packet should be sent using a non-legacy communication protocol. In response to the decision, determine the processing path within the network communication device to follow to process the packet for transmission using the non-legacy communication protocol, and at least partially based on the non-legacy communication protocol. It has a data processing unit that can operate to reformat a packet in legacy packet format to generate a target packet in legacy packet format and to feed the target packet to a destination network device according to a non-legacy communication protocol. ..

In some embodiments, the routing unit intercepts packets received in legacy packet format from the host device through the legacy network interface and is at least partially based on packets in legacy packet format received from the host device. It can be further operated to determine the operating mode of the host device.

In some embodiments, the routing unit determines that a packet should not be sent using a non-legacy communication protocol, at least in part based on the mode of operation of the host device, and according to the legacy communication protocol. It can be further actuated to deliver packets directly to the destination network device.

In some embodiments, a data processing unit that can act to determine the processing path to follow to process a packet for transmission using a non-legacy communication protocol is a non-legacy packet format that corresponds to the non-legacy communication protocol. To determine the non-legacy communication protocol among multiple non-legacy communication protocols that follow to reformat packets in the legacy packet format to generate the target packet in, and the non-legacy communication related to the operating mode of the host device. It further comprises a data processing unit capable of operating to determine a processing path within a network communication device based on at least one of the protocol and the address of the destination network device, at least in part.

In some embodiments, the translation bridge can further operate to translate packets received over the legacy network interface from the legacy packet format to the intermediate packet format associated with the communication device.

In some embodiments, a data processing unit capable of reformatting a packet in a legacy packet format to produce a target packet in a non-legacy packet format sends the packet for transmission using a non-legacy communication protocol. Identify the non-legacy communication protocol to follow for processing and translate the packet from the intermediate packet format associated with the communication device to the non-legacy packet format corresponding to the non-legacy communication protocol to generate the target packet. It also has a data processing unit that can operate in this way.

In some embodiments, the translation bridge receives a second packet in a non-legacy packet format that supports a non-legacy communication protocol for transmission to the host device over the legacy network interface, and the legacy packet format. Reformats a second packet in non-legacy packet format to generate a second target packet in, and feeds the host device a second target packet in legacy packet format over a legacy network interface. It is possible to operate further.

In some embodiments, it acts to determine whether a packet received over a legacy network interface should be sent using a legacy communication protocol or a non-legacy communication protocol. A possible routing unit follows between a network communication device and a destination network device in response to determining that a packet received over a legacy network interface should be sent using a legacy communication protocol. Select a legacy communication protocol for communication and determine that packets received over the legacy network interface should be sent using the non-legacy communication protocol of multiple non-legacy communication protocols. In response, determining one or more of the multiple non-legacy communication protocols supported by the destination network device, at least in part, based on the address of the destination network device, and the network communication device and destination network. It further comprises a routing unit capable of operating to select one or more of a plurality of non-legacy communication protocols for subsequent communication with the device.

In some embodiments, the system comprises a host device configured to operate in one of a plurality of modes of operation for communicating over a communication network and a communication unit coupled to the host device. Be prepared. The communication unit has a translation bridge that can operate to receive packets in legacy packet format from the host device through the legacy network interface for transmission to the destination network device, and the host device through the legacy network interface. Lee packets received by the legacy packet format from the packet via the method comprising intercept, received from the host device, and to determine the operation mode of the host device based at least in part on the packet of the legacy packet format, the legacy network interface Should be transmitted using the legacy communication protocol, or should be transmitted using the non-legacy communication protocol of multiple non-legacy communication protocols, at least in part based on the operating mode of the host device. A routing unit that can act to determine if, and a non-legacy communication protocol in response to the routing unit's determination that the packet should be sent using a non-legacy communication protocol. Legacy packet format to determine the processing path within the communication unit to follow to process the packet for transmission used and to generate a target packet in non-legacy packet format based at least in part on the non-legacy communication protocol. It includes a data processing unit capable of reformatting packets and feeding target packets to destination network devices according to non-legacy communication protocols.

In some embodiments, the routing unit determines that a packet should not be sent using a non-legacy communication protocol, at least in part based on the mode of operation of the host device, and according to the legacy communication protocol. It can be further actuated to deliver packets directly to the destination network device.

In some embodiments, a data processing unit that can act to determine the processing path to follow to process a packet for transmission using a non-legacy communication protocol is a non-legacy packet format that corresponds to the non-legacy communication protocol. To determine the non-legacy communication protocol among multiple non-legacy communication protocols that follow to reformat packets in the legacy packet format to generate the target packet in, and the non-legacy communication related to the operating mode of the host device. It further comprises a data processing unit that can operate to determine a processing path within the communication unit based on at least one of the protocol and the address of the destination network device.

In some embodiments, the translation bridge can further operate to translate packets received through the legacy network interface from the legacy packet format to the intermediate packet format associated with the communication unit.

In some embodiments, a data processing unit capable of reformatting a packet in a legacy packet format to produce a target packet in a non-legacy packet format sends the packet for transmission using a non-legacy communication protocol. Identify the non-legacy communication protocol to follow for processing and translate the packet from the intermediate packet format associated with the communication unit to the non-legacy packet format corresponding to the non-legacy communication protocol to generate the target packet. It is further equipped with a data processing unit that can operate in the same manner.

By referring to the accompanying drawings, this embodiment will be better understood and a number of purposes, features and advantages will be apparent to those skilled in the art.

<figref num="1">An exemplary block diagram showing an operation for exchanging data between communication interfaces using different data rates.</figref><figref num="2">A block diagram showing an exemplary architecture of a transformation bridge.</figref><figref num="3">An exemplary block diagram showing an exemplary legacy PLCP header format and an exemplary intermediate PLCP header format.</figref><figref num="4">A flow diagram illustrating exemplary behavior for formatting packets received from a legacy network interface for transmission using a non-legacy communication protocol.</figref><figref num="5">A flow diagram demonstrating an exemplary operation for transmitting a packet received from a legacy network interface using a non-legacy communication protocol.</figref><figref num="6">Schematic showing exemplary behavior for formatting non-legacy network packets for transmission to a legacy network interface</figref><figref num="7">A diagram illustrating an electronic device including a mechanism for multi-communication mode packet routing for a wireless communication system.</figref>

The following description includes exemplary systems, methods, techniques, instruction sequences, and computer program products that implement the techniques of the subject matter of the invention. However, it should be understood that the embodiments described may be implemented without these specific details. For example, the example refers to routing and processing a packet from a legacy network interface and sending the packet using an 802.11g / n communication protocol or a wireless wide area network (WWAN) communication protocol, but embodiments are made. Not limited to that. In other embodiments, packets from legacy network interfaces can be translated into any suitable non-legacy format and transmitted using any suitable non-legacy communication technology (eg, long-range Wi-Fi). , Any suitable non-legacy communication protocol (eg Worldwide Interoperability for Microwave) Can be sent using Access (WiMAX), etc.). Other examples do not illustrate well-known instruction instances, protocols, structures, and techniques in detail to avoid obscuring the description.

Legacy wireless local area network (WLAN) devices (for example, 802.11 or 802.11b devices) can generally transmit at a data rate of 54 Mbps for 802.11g devices and 65 Mbps for 802.11n devices. (Can) Send packets at slower data rates (eg 1Mbps-2Mbps) compared to "advanced" or "modern" non-legacy WLAN devices. Therefore, legacy WLAN devices may be able to transmit (ie, be "on the air") over longer time intervals and may not make efficient use of available bandwidth and network capacity. , Can consume more power.

The intermediate conversion unit can guarantee a seamless transition between legacy and non-legacy communication protocols in order to extend the transmission range of the legacy network interface supported by the host device. In some embodiments, packets from the host device may be delivered to the non-legacy network device through the legacy network interface for routing and translation and transmission using non-legacy communication protocols. Intermediate conversion units (for example, or non-legacy network devices) use a common WLAN infrastructure mode connectivity model and are properly supported non-legacy communication protocols (for example, WWAN communication protocols, WLANs). Packets can be sent from legacy network interfaces using 802.11g / n communication protocols, etc.). The intermediate conversion unit can intercept packets sent from the legacy network interface and can identify the route to follow to send the packet to the destination network device and the non-legacy communication protocol. The intermediate conversion unit can transform / reformate the packet from the legacy packet format to the appropriate non-legacy packet format according to the identified non-legacy communication protocol. The intermediate conversion unit can intercept and route packets from legacy network interfaces using non-legacy communication protocols at faster transmission rates (without the knowledge of the host device). Such techniques for conversion between legacy and non-legacy communication protocols implement packets from legacy network interfaces at higher speeds (eg, at higher data rates and / or advanced modulation schemes). It is possible to transmit (by doing so) and therefore the rate-over-range can be improved. This can increase the capacity of the communication network, reduce the transmission time, and free the communication medium. Therefore, this can reduce power consumption, save battery power, and extend the transmission range. In addition, advanced security protocols may be implemented to improve data security and encryption when sending packets from legacy network interfaces using non-legacy communication protocols. This allows network agnostic applications, software, and communications (eg, Internet access services) to be delivered to host devices via legacy network interfaces.

FIG. 1 is an exemplary block diagram showing an operation for exchanging data between communication interfaces using different data rates. FIG. 1 shows the communication unit 100. The communication unit 100 includes a secure digital input / output (SDIO) interface 102, a data processing unit 108, a wireless wide area network (WWAN) interface 114, a routing unit 104, a conversion bridge 106, and a wireless local. It includes an area network (WLAN) medium access control (MAC) unit 110 and a baseband / RF unit 112. The SDIO interface 102, the data processing unit 108, the WWAN interface 114, the routing unit 104, and the WLAN MAC 110 are connected to the bus 116. The conversion bridge 106 is coupled to the routing unit 104 and to the baseband unit 112. WLAN The MAC 110 is coupled to the baseband unit 112. In the WWAN interface 114, the communication unit 100 has a WWAN communication protocol (for example, General packet radio service (GPRS), Global System for Mobile. Enables communication using Communications (GSM)®, 3G, etc.). The baseband / RF unit 112 allows the communication unit 100 to communicate over a WLAN communication protocol (eg, 802.11b / g / n communication protocol). As shown in FIG. 1, the communication unit 100 implements two network interfaces, an SDIO interface 102 and a legacy network interface 118, on the host device 116. When host device 106 is in non-legacy operating mode, host device 116 may use SDIO interface 102 for applications that require high throughput, strong security, and other advanced features. When the host device 106 is in one of a plurality of legacy operating modes, the communication unit 100 receives 802.11b (or other legacy WLAN communication) depending on the operating mode and / or the packets received by the communication unit 100. Protocol), 802.11. To send packets received over legacy network interface 118 using 11g / n (or other non-legacy WLAN communication protocols) or WWAN communication protocols (eg GPRS, GSM, 3G, 4G) Can be used. In some embodiments, the communication unit 100 implements the ability to intercept or inject packets (eg, MAC frames) received from legacy network interface 118 to determine how packets should be routed and processed. can do. As described in Stages A through C below, the communication unit 100 routes and processes the data received through the legacy network interface 118 and processes the data at a higher data rate using a non-legacy communication protocol. And / or by implementing advanced modulation schemes, it can be made possible to transmit over a communication network.

In stage A, the translation bridge 106 receives a packet from the host device via the legacy network interface 118. The transformation bridge 106 can be a bridge between the legacy network interface 118 and other processing components of the communication unit 100. In one example, the legacy network interface 118 can be an interface coupled to a host device 116 that supports the 802.11b legacy communication protocol (and / or other suitable legacy communication protocol). As shown in FIG. 1, the legacy network interface 118 is coupled to the communication unit 100. Communication unit 100 can process and route packets using the appropriate non-legacy communication protocols (eg 802.11g / n, WWAN, long range Wi-Fi, WiMAX, etc.). The translation bridge 106 can work with the routing unit 104 to determine whether packets received from the legacy network interface 118 should be translated into a suitable format for transmission using the non-legacy communication protocol.

In some implementations, as soon as the host device determines that it is scheduled to communicate over the legacy network interface, the conversion bridge 106 is a baseband processing unit 112 for transmission using the legacy communication protocol. Packets can be routed directly to. Alternatively, as soon as it determines that a packet received from the host device can be transmitted using a non-legacy communication protocol, as described further below, the translation bridge 106 (routing unit 104 and data processing unit 108) And in conjunction with WLAN MAC110), the packet can be converted to a non-legacy format for transmission using one of the non-legacy communication protocols and then fed to the baseband processing unit 112. ..

In stage B, routing unit 104 determines whether packets should be fed for transmission using a non-legacy communication protocol (eg, WWAN, 802.11g / n network, etc.). The routing unit 104 can sniff a packet received from the legacy network interface 118 and determine if the packet can be transmitted using a non-legacy communication protocol. In one implementation, the routing unit 104 can determine whether a packet can be sent using a non-legacy communication protocol based on the mode of operation of the host device 116. For example, the routing unit 104 may determine that packets received from legacy network interface 118 should be sent using a non-legacy communication protocol while the host device is in voice communication mode. As another example, for gaming devices, as described further below, the routing unit 104 uses a non-legacy communication protocol for packets received from legacy network interface 118 when the gaming device is in legacy game mode. Should not be sent, instead of legacy communication protocols (eg 802. It can be determined that it should be transmitted using 11b). In another implementation, routing unit 104 sends packets received from legacy network interface 118 using a non-legacy communication protocol based on the instructions of the destination network device (eg, network address or supported communication protocol). You can determine if it can be done. For example, the routing unit 104 can snoop MAC frames sent by legacy network interface 118 to identify destination network devices that host device 116 is scheduled to communicate with. As soon as it determines that a packet can be sent to the destination network device using a non-legacy communication protocol, the routing unit 104 intermediates the packet from the legacy packet format to the translation bridge 106, as described in Stage C below. It can be converted to packet format. Routing unit 104 can also intercept subsequent packets from legacy network interface 118 and provide them for subsequent processing and transmission using non-legacy communication protocols (eg, by data processing unit 108).

After determining in stage C that the packet should be sent using a non-legacy communication protocol, the translation bridge 106 transforms the packet from the legacy packet format into an intermediate packet format recognized by the communication unit 100. As described with reference to FIGS. 2 to 3, the legacy network interface 118 and the communication unit 100 transmit packets at different data rates, use different signaling techniques, and transmit data in different packet formats. There may be a need. The translation bridge 106 allows packets received from legacy network interface 118 to be sent at a faster rate rather than being sent at a slower rate (for example, at a slower data rate using a slower legacy communication protocol such as 802.11b). Will be able to send (at higher data rates using faster non-legacy communication protocols such as 802.11g / n). In some implementations, packets received through legacy network interface 118 are sent using non-legacy communication protocols to allow access to a more secure WLAN network, and / or Can be translated for access to the WWAN network (for example, if the WLAN network is not available). The translation bridge 106 can convert packets received from the legacy network interface 118 in the legacy packet format into an intermediate packet format recognized by the communication unit 100 (eg, routing unit 104, data processing unit 108, etc.). In one example, the transformation bridge 106 is a physical layer convergence procedure (PLCP:). Physical Layer Convergence Procedure) Headers can be converted from the legacy PLCP header format to the intermediate PLCP header format. In another example, the translation bridge 106 can translate other headers and data fields of a packet from legacy format to intermediate non-legacy format. The routing unit 104 can then feed packets in intermediate packet format to the data processing unit 108. As described below for Stage D, the data processing unit 108 then decides how to route the packet and which non-legacy communication protocol (eg 802.11n, WWAN) to send the packet to the destination network device. Etc.) can be determined if it should be used. The data processing unit 108 can then convert the packet from the intermediate packet format to the non-legacy packet format corresponding to the selected non-legacy communication protocol.

Convert to 11g / n packet format). The data processing unit 108 can analyze the packet and determine the destination network device to which the packet should be given. Data processing unit 108 is the route on which packets should be sent from the host device (ie, communication unit 100) to the destination network device based on the address of the destination network device (or based on the communication protocols supported by the destination network device). Can be judged. The data processing unit 108 can also determine the preferred non-legacy communication protocol to follow for sending packets to the destination network device based on the operating mode of the host device. In one example, processing unit 108 should send packets given from legacy network interface 118 using the non-legacy WLAN communication protocol or using the WWAN communication protocol. Can be judged. When the data processing unit 108 selects a non-legacy communication protocol, the data processing unit 108 can convert the packet to the appropriate non-legacy packet format for transmission using the selected non-legacy communication protocol. For example, processing unit 108 transfers packets from an intermediate packet format to a non-legacy WLAN packet format (or WWAN), depending on whether the packet will be sent using a non-legacy WLAN communication protocol (or WWAN communication protocol). Can be converted to packet format). For example, the data processing unit 108 encapsulates a packet given by the legacy network interface 118 in an Ethernet header, a sub-network access protocol (SNAP) header, or any other suitable non-legacy communication protocol header. be able to.

Although not shown in FIG. 1, the communication unit 100 can also receive data from legacy and non-legacy devices, process the data, and feed the data to the host device 116. For example, WWAN interface 114 or baseband / RF unit 112 can receive data, process that data (along with other components of communication unit 100), and feed that data to host device 116. Further, if the routing unit 104 determines that the packet received through the legacy network interface 118 should not be transmitted using the non-legacy communication protocol, the routing unit 104 determines that the translation bridge 106 intermediate packets the packet. Note that conversion to format can be prevented. Routing unit 104 may not intercept subsequent packets and is legacy to translation bridge 106 for transmission at legacy data rates (eg 1Mbps to 2Mbps) using legacy communication protocols (eg 802.11b). Packets received via network interface 118 can be fed to baseband unit 112 (without translation).

FIG. 2 is a block diagram showing an exemplary architecture of the transformation bridge 106. The conversion bridge 106 includes a non-legacy mode conversion unit 202 and a legacy mode conversion unit 210. Non-legacy mode conversion unit 202 can translate packets received from legacy network interface 118 for transmission to routing unit 104 and other components of communication unit 100 (and finally, non-legacy communication). Translated packets can be given (for transmission over a communication network using a protocol). The non-legacy mode conversion unit 202 includes a non-legacy mode processing unit 204, a series-parallel converter 206, and a transmitter unit 208. The legacy mode conversion unit 210 can translate the packet received from the routing unit 104 (via other components of the communication unit 100) and can feed the translated packet to the legacy network interface 118. The legacy mode conversion unit 210 includes a legacy mode processing unit 214, a serializer 212, a buffer 216, and a transmitter unit 218.

The translation bridge 106 receives packets in the legacy packet format from the legacy network interface 118. In one example, the translation bridge 106 can receive an instruction (eg, a control signal) that a packet in legacy packet format is available for transmission. In response to the control signal, the non-legacy mode processing unit 204 of the non-legacy mode conversion unit 202 can begin receiving the PLCP header of the packet from the legacy network interface 118. PLCP header format 300 in FIG. 3 shows an exemplary legacy PLCP header format for packets received from legacy network interface 118. As shown in FIG. 3, the legacy PLCP header 300 can include a signal field 302, a service field 304, a length field 306, and a control bit 308. The signal field 302 can exhibit one or more characteristics of the data received from the legacy network interface 118. For example, signal field 302 can indicate a modulation scheme for data received from legacy network interface 118. In one implementation, the signal field 302 can have a value of 0x0A to indicate a data transmission rate of 1 Mbps (ie, differential binary phase shift keying (DBPSK) modulation scheme). The signal field 302 has a data transmission rate of 2 Mbps (ie, differential 4-phase shift keying (DQPSK:)). It can have a value of 0x0B to indicate the differential quadrature phase shift keying) modulation scheme). The length field 306 can indicate the transmission length (in microseconds) of the packet received from the legacy network device 118. In one example, the transmit length can be calculated to exclude the length of the legacy PLCP header. In another example, the transmit length can be calculated to include the length of the legacy PLCP header. The control bit 308 can indicate preamble information (eg, whether the packet has a short preamble or a long preamble), RF attenuator settings, AGC settings, signal quality information, and so on. In one example, the signal field 302 can be allocated 1 byte (ie, 8 bits), the service field 304 can be allocated 1 byte, the length field 306 can be allocated 2 bytes (ie 16 bits), and control. Two bytes can be allocated for bit 308. Note that in other implementations, the legacy PLCP header format 300 can have any suitable number of fields, and each field can be assigned any suitable number of bits. It can have a value of 0x0B to indicate keying) modulation scheme). The length field 306 can indicate the transmission length (in microseconds) of the packet received from the legacy network device 118. In one example, the transmit length can be calculated to exclude the length of the legacy PLCP header. In another example, the transmit length can be calculated to include the length of the legacy PLCP header. The control bit 308 can indicate preamble information (eg, whether the packet has a short preamble or a long preamble), RF attenuator settings, AGC settings, signal quality information, and so on. In one example, the signal field 302 can be allocated 1 byte (ie, 8 bits), the service field 304 can be allocated 1 byte, the length field 306 can be allocated 2 bytes (ie 16 bits), and control. Two bytes can be allocated for bit 308. Note that in other implementations, the legacy PLCP header format 300 can have any suitable number of fields, and each field can be assigned any suitable number of bits. It can have a value of 0x0B to indicate keying) modulation scheme). The length field 306 can indicate the transmission length (in microseconds) of the packet received from the legacy network device 118. In one example, the transmit length can be calculated to exclude the length of the legacy PLCP header. In another example, the transmit length can be calculated to include the length of the legacy PLCP header. The control bit 308 can indicate preamble information (eg, whether the packet has a short preamble or a long preamble), RF attenuator settings, AGC settings, signal quality information, and so on. In one example, the signal field 302 can be allocated 1 byte (ie, 8 bits), the service field 304 can be allocated 1 byte, the length field 306 can be allocated 2 bytes (ie 16 bits), and control. Two bytes can be allocated for bit 308. Note that in other implementations, the legacy PLCP header format 300 can have any suitable number of fields, and each field can be assigned any suitable number of bits.

The non-legacy mode processing unit 204 converts the received legacy PLCP header 300 into the intermediate PLCP header format 350 of FIG. 3 recognized by the components of the communication unit 100 (eg, routing unit 104 and data processing unit 108). Can be done. The intermediate PLCP header format 350 can include a power control field 352, a rate field 354, a length field 356, and other control bits 358. The power control field 352 is an implemented transmitter power control (TPC: transmitter power). It can indicate the type of control) and the corresponding transmit power at which the packet is being transmitted. The rate field 354 can indicate the transmit rate of the legacy network interface 118. For example, the rate field 354 can include a value of 0x1A to indicate a data transmission rate of 2 Mbps, a value of 0x1B to indicate a data transmission rate of 1 Mbps, and so on. The length field 356 can indicate the transmission length (in bytes) of the packet being transmitted. In one example, the power control field 352 can be allocated 8 bits, the rate field 354 can be allocated 5 bits, and the length field 356 can be allocated 12 bits. Note that in other implementations, the intermediate PLCP header format 350 may include any suitable number of fields, and each field may be allocated any suitable number of bits.

Referencing Figure 2 again, as soon as the legacy network interface 118 determines that it is ready to send data, the non-legacy mode processing unit 204 can start the PLCP clock, on the falling edge of the clock. You can start latching the data with. In one example, the PLCP clock can be a 1 MHz clock with a duty cycle of 1/3. The non-legacy mode processing unit 204 can receive the PLCP header from the legacy network interface 118 in the legacy PLCP header format 300. The non-legacy mode processing unit 204 can convert the legacy PLCP header format 300 to the intermediate PLCP header format 350. The non-legacy mode processing unit 204 causes the transmitter unit 208 to transmit the PLCP header of the intermediate PLCP header format 350 to the data processing unit 108 (via the routing unit 104) (in parallel format, that is, in bytes). Can be done.

After the non-legacy mode processing unit 204 receives, translates, and sends the PLCP header, the non-legacy mode processing unit 204 can receive subsequent fields of the packet (eg, preamble, payload, and so on). In one example, the non-legacy mode processing unit 204 has the PLCP header sent and the non-legacy mode processing unit 204 is ready to receive subsequent fields in the packet (eg, preamble, payload, etc.). (For example, a control signal) can be sent to the legacy network interface 118. To receive subsequent fields in the packet, the non-legacy mode processing unit 204 can update the clock frequency (if necessary) based on the value received in the signal field 302 of the legacy PLCP header 300. .. For example, if signal field 302 indicates that subsequent fields of the packet will be transmitted at 2 Mbps, the non-legacy mode processing unit 204 can guarantee that the clock frequency is 2 Mbps. The non-legacy mode processing unit 204 can initiate data latching on the falling edge of the clock. The data received from the legacy network interface 118 can be in serial data format (ie, the transformation bridge 106 can receive data from the legacy network interface 118 bit by bit). Therefore, the non-legacy mode processing unit 204 can give the series-parallel converter 206 the series data received from the legacy network interface 118. The series-parallel converter 206 can convert the data received from the legacy network interface 118 (eg, payload and non-PLCP data fields) to parallel format (eg, in bytes). The transmitter unit 208 can send these data bytes to the routing unit 104.

Note that in one implementation, the non-legacy mode processing unit 204 may only change the PLCP header (without changing the payload or other non-PLCP fields) of the packet received from the legacy network interface 118. In one implementation, the non-legacy mode processing unit 204 gives the series-parallel converter 206 the series data received from the legacy network interface 118, and the parallel-parallel converter 206 generated (generated from the series data). It can receive data, add an intermediate PLCP header 350, and generate packets in an intermediate packet format recognized by the components of the communication unit 100. The transmitter unit 208 can transmit a packet in the intermediate packet format to the routing unit 104 of FIG.

The legacy mode conversion unit 210 can convert packets received from the routing unit 104 (and data processing unit 108) into a legacy packet format recognized by the legacy network interface 118 (and / or host device 116). When data is available for legacy network interface 118 in routing unit 104, legacy mode processing unit 214 begins receiving PLCP headers of intermediate PLCP header format 350 from routing unit 104 (or data processing unit 108). Can be done. The legacy mode processing unit 214 can convert the PLCP header from the intermediate PLCP header format 350 to the legacy PLCP header format 300. The transmitter unit 218 can transmit the PLCP header of the legacy PLCP header format 300 to the legacy network interface 118. In one example, the legacy mode processing unit 214 can start the clock and the transmitter unit 218 can send the PLCP header on the falling edge of the clock.

After the PLCP header is sent, the legacy mode processing unit 214 can receive the rest of the packet from the routing unit 104 (eg, preamble, payload and other non-PLCP fields) and the rest of the packet on the legacy network interface 118. Can start sending. As described above, the legacy mode processing unit 214 may change the frequency of the clock depending on the preamble length and data rate expected by the legacy network interface 118. In one example, the legacy network interface 118 can be expected to receive serial data (eg, in bits), while the routing unit 104 feeds the legacy mode processing unit 214 in parallel data (eg, in bytes). be able to. Therefore, the legacy mode processing unit 214 can store parallel data received from the routing unit 104 in the buffer 216 (eg, first-in first-out method (FIFO) queue). The serializer 212 can access parallel data from buffer 216 and serialize the data so that the least significant bit (LSB) is sent to the legacy network interface 118 as the first bit. .. Transmitter unit 218 can therefore transmit serial data to legacy network interface 118.

FIG. 4 is a flow diagram (flow) 400 showing an exemplary operation for formatting packets received from a legacy network interface for transmission using a non-legacy communication protocol. Flow 400 starts at block 402.

At block 402, a packet is received from the host device via the legacy network interface. For example, referring to FIG. 2, the translation bridge 106 can receive packets from the host device through the legacy network interface 118. As soon as a packet is received from the legacy network interface 118, the translation bridge 106 can work with the routing unit 104 to determine if the packet should be sent using a non-legacy communication protocol. In one implementation, the host device may support multiple modes of communication. Packets may or may not be sent using non-legacy communication protocols, depending on the mode of communication in which the host device is operating. For example, the routing unit 104 may determine that packets received from legacy network interface 118 should be sent using a preferred non-legacy communication protocol when the host device is in voice communication mode. As another example, if the host device is operating in legacy mode, the translation bridge 106 should not work with routing unit 104 to send packets using non-legacy communication protocols (and instead legacy). It can be determined that the communication protocol should be used). The flow proceeds to block 404.

At block 404, read the header of the received packet. For example, the non-legacy mode conversion unit 202 of the conversion bridge 106 can read the PLCP header of the packet received in block 402. In one example, the PLCP header of the packet received from the legacy network interface 118 can be in the legacy PLCP header format 300 of FIG. PLCP headers can also be received from legacy network interface 118 in serial format. In one implementation, based on the PLCP header, the non-legacy mode conversion unit 202 feeds the PLCP header and subsequent data received from the legacy network interface 118 to another legacy network device using the legacy communication protocol. You can decide if it should be. If given, the non-legacy mode conversion unit 202 can directly provide the baseband unit 112 with a PLCP header and subsequent data for transmission using the legacy communication protocol. If not given, the PLCP header received from legacy network interface 118 and subsequent data are reformatted for transmission using non-legacy communication protocols, as shown in FIGS. 4 and 5. The flow proceeds to block 406.

At block 406, the header is converted from the legacy header format to the intermediate header format. For example, the non-legacy mode conversion unit 202 can convert the PLCP header from the legacy PLCP header format 300 to the intermediate PLCP header format 350. In one implementation, the intermediate PLCP header format 350 may be a predetermined PLCP header format recognized by the components of the communication unit 100 (eg, conversion bridge 106, routing unit 104, data processing unit 108, etc.). In another implementation, other non-legacy network devices (eg WLAN devices, WWAN devices, etc.) may also recognize the intermediate PLCP header format 350. Further, in some implementations, the non-legacy mode conversion unit 202 can also convert the serial data received from the legacy network interface 118 to the corresponding parallel data. The flow proceeds to block 408.

In block 408, headers in intermediate header format and corresponding data are provided for subsequent processing prior to transmission using the non-legacy communication protocol. For example, the non-legacy mode conversion unit 202 can send the PLCP header of intermediate PLCP header format 350 (as determined in block 406) and the corresponding data to the routing unit 104. In one implementation, the non-legacy mode conversion unit 202 can initially provide the routing unit 104 with a PLCP header of intermediate PLCP header format 350. In another implementation, the non-legacy mode conversion unit 202 can simultaneously provide the routing unit 104 with the PLCP header of intermediate PLCP header format 350 and the corresponding data. As described above with reference to FIGS. 1 and 2, the routing unit 104 can provide the data processing unit 108 with a PLCP header of intermediate PLCP header format 350 and corresponding data. As described with reference to FIG. 5, the data processing unit 108 can determine how (and according to which non-legacy communication protocol) the data should be sent to the destination network device, as well as the appropriate non-legacy. Data can be modified for transmission using legacy communication protocols. Block 408 ends the flow.

FIG. 5 is a flow diagram 500 showing an exemplary operation for transmitting a packet received from a legacy network interface using a non-legacy communication protocol. Flow 500 starts at block 502.

At block 502, it receives a request to connect to a legacy network interface. For example, referring to FIG. 1, the data processing unit 108 of the communication unit 100 may receive a request to connect to the host device 116 via the legacy network interface 118. In some implementations, the data processing unit 108 can present itself to the legacy network interface 118 as an access point to which client devices (and other access points) can connect. The data processing unit 108 can act as a virtual access point that periodically broadcasts beacon frames (or other periodic synchronization / monitoring messages) to signal its presence. In one example, the data processing unit 108 may generate beacon frames and the routing unit 104 may inject and feed beacon frames to the host device 116 for processing via the legacy network interface 118. Host device 116 can receive beacon frames and can send exploration request frames over legacy network interface 118 to connect to data processing unit 108 acting as a virtual access point. The flow proceeds to block 504.

At block 504, it is determined whether a connection with a legacy network interface should be established for communication using a non-legacy communication protocol. For example, routing unit 104 works with translation bridge 106 to connect with legacy network interface 118 to send data (received from legacy network interface 118) using one of the non-legacy communication protocols. Can be determined if should be established. In some implementations, routing unit 104 may determine the mode of operation of host device 116 (with legacy network interface 118) before giving exploration request frames from legacy network interface 118 to data processing unit 108. It can determine if subsequent packets received from legacy network interface 118 should be sent using one of the non-legacy communication protocols. In another implementation, the routing unit 104 receives a packet from legacy network interface 118 based on the address of the destination network device, the communication protocols supported by the destination network device, or other information contained within the received packet. Can determine if it should be sent using one of the non-legacy communication protocols. If it is determined that a connection with the legacy network interface 118 should be established for communication using the non-legacy communication protocol, the routing unit 104 will make subsequent packets from the legacy network interface 118 the non-legacy communication protocol. Can be used to determine that it can be transmitted. The flow proceeds to block 506, where routing unit 104 can establish a connection between legacy network interface 118 and data processing unit 108. .. If it is determined that a connection with the legacy network interface 118 should not be established, the flow proceeds to block 518.

At block 506, establish a connection with the legacy network interface. If the routing unit 104 determines that a connection with the legacy network interface 118 should be established for communication using the non-legacy communication protocol, the flow 500 moves from block 504 to block 506. For example, the data processing unit 108 can establish a connection with the host device 116 through the legacy network interface 118. The data processing unit 108 and the host device 116 communicate with the exploration request / response frame, association request / response frame, and authentication to establish a communication link between the communication unit 100 and the host device 116 via the legacy network interface 118. Request / response frames can be exchanged. In one implementation, the host device 116 can detect a beacon frame from the communication unit 100 and has an appropriate service set identifier (SSID). A broadcast exploration request can be sent with the identifier). The data processing unit 108 can receive the broadcast exploration request, determine that the host device 116 is transmitting through the legacy network interface 118, and can transmit the exploration response frame. In one example, routing unit 104 can provide exploration request frames received from legacy network interface 118 for subsequent processing by communication unit 100. After the connection with the legacy network interface 118 is established, the routing unit 104 can intercept packets sent by the host device through the legacy network interface 118, as described below, and is a non-legacy communication protocol. Packets can be fed to the data processing unit 108 for transmission using. The flow proceeds to block 508.

At block 508, receive a packet from the legacy network interface. For example, the data processing unit 108 can receive packets from the legacy network interface 118 that should be sent using a non-legacy communication protocol. As described above with reference to FIGS. 1 to 4, the conversion bridge 106 of the communication unit 100 can receive the PLCP header of the legacy PLCP header format 300 and convert the PLCP header to the intermediate PLCP header format 350. It can be converted and the data processing unit 108 (via the routing unit 104) can be given a PLCP header of intermediate PLCP header format 350. In one implementation, the transform bridge 106 also receives serial data from legacy network interface 118, transforms the serial data into parallel data, and feeds the parallel data to data processing unit 108 (via routing unit 104). be able to. As described below, the data processing unit 108 can further format parallel data for transmission using non-legacy communication protocols. The flow proceeds to block 510.

At block 510, determine the route on which the packet should be sent to the destination network device. For example, the data processing unit 108 can determine the route on which a packet should be sent to the destination network device based on the destination network device. The data processing unit 108 can determine the destination network device to which packets from the legacy network interface 118 (eg, including PLCP headers and parallel data) should be sent. The destination network device can be a remote / physical access point, an 802.11g / n client device, a WWAN device, and so on. The data processing unit 108 can read the packet preamble (eg, the destination address field) to determine the destination network device to which the packet should be sent. The data processing unit 108 may implement any suitable routing algorithm to determine which route and non-legacy communication protocol the packet should be sent to the destination network device. The data processing unit 108 can determine the route to which the packet should be sent and the non-legacy communication protocol based on the destination network device, the operating mode of the host device, and so on. Depending on the non-legacy communication protocol selected for packet transmission, the data processing unit 108 can format the packet according to the corresponding non-legacy packet format, as described below for blocks 512 through 516. The flow proceeds to block 512.

At block 512, determine if the packet should be sent using the non-legacy WLAN communication protocol. For example, based on the route determined in block 510, the data processing unit 108 may determine if a packet should be sent using a non-legacy WLAN (eg 802.11g / n) communication protocol. Can be done. As another example, the data processing unit 108 uses a non-legacy WLAN communication protocol based on the address of the destination network device, the communication protocol supported by the destination network device, or other information contained within the received packet. Can determine if the packet should be sent. As another example, the data processing unit 108 may determine whether a packet should be sent using a non-legacy WLAN communication protocol based on the operating mode of the host device. If it determines that the packet should be sent using the non-legacy WLAN communication protocol, the flow proceeds to block 514. Otherwise, the data processing unit 108 determines that the packet should be sent using the WWAN communication protocol and the flow proceeds to block 516.

At block 514, the packet is converted to a non-legacy WLAN packet and given a non-legacy WLAN packet for transmission to the destination network device. For example, the data processing unit 108 can convert packets from intermediate packet format 350 to non-legacy WLAN packet format in order to generate non-legacy WLAN packets. The data processing unit 108 is a WLAN The MAC110 and baseband / RF unit 112 can be made to send non-legacy WLAN packets using the non-legacy WLAN communication protocol. In one example, the data processing unit 108 can read the payload of the packet (received in block 508) and can encapsulate the payload of the packet with a WLAN header suitable for producing non-legacy WLAN packets. .. In another example, the data processing unit 108 puts the PLCP header (of intermediate PLCP header format 350) and the corresponding data (eg, parallel data) into a suitable non-legacy WLAN header to generate non-legacy WLAN packets. Can be encapsulated. The data processing unit 108 can also implement non-legacy security protocols, encryption techniques, retransmission techniques, etc. to ensure the reliability of the data transmitted from the communication unit 100. In some implementations, the behavior for generating non-legacy WLAN packets is WLAN It can be performed by MAC110 and / or baseband / RF unit 112. Block 514 ends the flow.

At block 516, the packet is converted to a WWAN packet and given for transmission to the destination network device. For example, the data processing unit 108 can convert a packet from an intermediate packet format to a WWAN packet format in order to generate a WWAN packet. The data processing unit 108 can send WWAN packets through the WWAN interface 114 using the WWAN communication protocol. In one example, the data processing unit 108 can read the payload of the packet and can encapsulate the payload of the packet with a WWAN header suitable for generating the WWAN packet. In another example, the data processing unit 108 encapsulates the PLCP header (of intermediate PLCP header format 350) and the corresponding data (eg, parallel data) in a suitable WWAN header to generate WWAN packets. Can be done. The data processing unit 108 can also implement non-legacy security protocols, encryption techniques, retransmission techniques, etc. to ensure the reliability of the data transmitted from the communication unit 100.

In some implementations, the operation for converting a packet into a WWAN packet can be performed by a separate WWAN processing module (or by WWAN interface 114). The WWAN interface 114 allows the communication unit 100 to communicate using the WWAN communication protocol. In one implementation, WWAN packets can be sent using a communication network that supports Internet Protocol version 4 (IPv4). WWAN interface 114 has the ability to control the WWAN setup (for example, to establish and tear down WWAN communication links) to send or receive data according to the WWAN communication protocol. be able to. In one implementation, the WWAN interface 114 is a point-to-point protocol (PPP) over a physical WWAN communication link. Protocol) Can provide PPP functionality to establish and negotiate connections. In other embodiments, the WWAN interface can implement any suitable communication protocol for WWAN link control and data transfer. In addition, in some embodiments, the data processing unit 108 translates Internet Protocol Network Address Translation (IP-) to allow the packet given by the legacy network interface 118 to be sent using the WWAN communication protocol. Functions for NAT: internet protocol network address translation) can be implemented. In another implementation, the data processing unit 108 can feed WWAN packets to WWAN interface 114, where WWAN packets undergo IP-NAT translation before being sent using the WWAN communication protocol. Can receive. Block 516 ends the flow.

At block 518, the legacy communication protocol is used to transmit subsequent packets received from the legacy network interface. If the routing unit 104 determines that a connection with the legacy network interface 118 should not be established for communication using the non-legacy communication protocol, the flow 500 moves from block 504 to block 518. The routing unit 104 may determine that a connection with the legacy network interface 118 should not be established based on the operating mode of the host device. For example, routing unit 104 should have a host game device in legacy game mode, packets received from that host game device should be sent using the legacy communication protocol, and a connection with legacy network interface 118 is established. You can decide that it shouldn't be. Block 518 ends the flow.

FIG. 6 is a flow diagram 600 showing an exemplary operation for formatting non-legacy network packets for transmission to a legacy network interface. Flow 600 starts at block 602.

At block 602, it receives a packet to be given to the host device via the legacy network interface. The data processing unit 108 can receive packets in non-legacy packet format using a non-legacy communication protocol for transmission to legacy network interface 118. For example, the data processing unit 108 can receive 802.11g packets at high data rates (eg 54Mbps). To provide 802.11g packets to legacy network interface 118, the data processing unit 108 can re-encode the received 802.11g packets. In other words, the data processing unit 108 can convert some / all of the received 802.11g packets into an intermediate packet format recognized by the components of the communication unit 100. For example, the data processing unit 108 can convert the PLCP header of the received 802.11g packet to the intermediate PLCP header format 350 of FIG. As described below, the translation bridge 106 can then translate the packet from the intermediate packet format to the legacy packet format, which is the legacy network interface 118 at a slower legacy data rate (eg 1-2 Mbps). Can be sent to. In one implementation, as soon as a WWAN packet is received, the WWAN interface 114 (or data processing unit 108) before routing the translated packet (eg, through the translation bridge 106) to the legacy network interface 118. IP-NAT conversion can be performed on received WWAN packets. The flow proceeds to block 604.

At block 604, read the header of the received packet. For example, the legacy mode conversion unit 210 of the conversion bridge 106 can read the PLCP header of the packet received in block 602. The PLCP header of the packet received from the routing unit 104 can be in the intermediate PLCP header format 350 of FIG. The PLCP header may also be received from the routing unit 104 in parallel format. The legacy mode conversion unit 210 can convert the PLCP header received from the routing unit 104 and subsequent data into the legacy format, as described below. The flow proceeds to block 606.

In block 606, the header is converted from the intermediate header format to the legacy header format. For example, the legacy mode conversion unit 210 can convert the PLCP header read in block 604 from the intermediate PLCP header format 350 to the legacy PLCP header format 300. In some implementations, the legacy mode conversion unit 210 also corresponds to the parallel data received from the routing unit 104 (and processing unit 108) for transmission to the host device 116 over the legacy network interface 118. Can be converted to data. The flow proceeds to block 608.

At block 608, the host device is given the header in legacy header format and the corresponding data via the legacy network interface. For example, the legacy mode conversion unit 210 can send the PLCP header of legacy PLCP header format 300 (as determined in block 606) and the corresponding data to the host device via the legacy network interface 118. In one example, the legacy mode conversion unit 210 can first provide the legacy network interface 118 with a header of legacy header format 300. In another implementation, the legacy mode conversion unit 210 can simultaneously provide the legacy network interface 118 with the PLCP header of legacy PLCP header format 300 and the corresponding data. Block 608 ends the flow.

The illustrated figures (FIGS. 1-6) are examples to aid in understanding the embodiments and should not be used to limit the embodiments or the claims. I want you to understand. Embodiments may perform additional actions, perform fewer actions, perform actions in different orders, perform actions in parallel, and perform some actions differently. For example, FIG. 5 illustrates that the data processing unit 108 translates a packet to be transmitted into either a non-legacy WLAN packet or a WWAN packet, but the embodiment is not so limited. In some embodiments, the operation of converting a packet to be transmitted into a WLAN or WWAN packet may be performed by a separate processing unit. For example, in block 512, as soon as it decides to send a packet using the non-legacy WLAN communication protocol, the data processing unit 108 decides to send a WLAN module (eg WLAN). Packets can be sent to MAC110 and / or baseband unit 112). The WLAN module can generate WLAN packets and can send WLAN packets according to the route determined in block 510. Similarly, at block 512, as soon as it decides to send a packet using the WWAN communication protocol, the data processing unit 108 (for example, part of the WWAN device coupled to the WWAN interface 114 and / or USB). Packets can be given to the WWAN module (implemented as). The WWAN module can generate WWAN packets and can send WWAN packets according to the route determined in block 510. In another embodiment, it can be determined that the packet received from the data processing unit 108, the legacy network interface 118 is transmitted using another suitable non-legacy communication protocol, and therefore the appropriate protocol, packet format. Note that the packet can be reformatted according to, etc.

Also note that in some implementations the WWAN interface 114 can allow communication over a universal serial bus (USB) connection and WWAN communication protocol. For example, WWAN interface 114 can act as a bridge between the communication unit 100 and the USB WWAN transceiver. The WWAN transceiver can then send / receive WWAN packets over the WWAN communication network. In another implementation, a WWAN circuit (eg, a WWAN transceiver) can be incorporated within the communication unit 100 (or host device 116). The WWAN interface 114 can act as a bridge between the communication unit 100 and the integrated WWAN circuit.

In addition to reformatting packets received from legacy network interface 118 according to the non-legacy communication protocol on which the packet should be sent, the data processing unit 108 can also implement advanced security protocols. After the non-legacy communication protocol is selected, the data processing unit 108 can negotiate the security protocol to be implemented, exchange authentication messages, coordinate shared secrets, and so on. For example, legacy network interface 118 may implement a legacy security protocol (eg Wired Equivalent Privacy (WEP)). The data processing unit 108 also has advanced security protocols (eg, Wi-Fi Protected) to improve the security of data transmission, in addition to legacy security protocols. Access (WPA), WPA2, etc.) can be implemented. In some implementations, the data processing unit 108 can act as a virtual access point and act as a proxy to remote and physical access points. A data processing unit 108 that acts as a proxy allows legacy network interfaces 118 to communicate at higher data rates (for example, with non-legacy (or newer) access points) using advanced security protocols. Can be done. In one example, legacy network interface 118 may pass security settings to a proxy virtual access point so that a connection with a remote, physical access point can be established first. The proxy virtual access point can then create an open access point connection with the legacy network interface 118 (eg, non-secure connection, connection with minimal / negligible security) and secure with remote, physical access points. Can maintain a good connection. The virtual proxy access point is remote with the legacy network interface 118, even though the legacy network interface 118 may be unaware of the remote and physical access points and the advanced security protocols implemented by the remote and physical access points. , Can enable communication with physical access points.

Finally, note that in some implementations the data processing unit 108 may not function as a virtual access point. Instead, the communication unit 100 may receive all packets sent by the host device 116 over the legacy network interface 118. As described above, the routing unit 104 may determine if the received packet should be transmitted using a non-legacy communication protocol. Therefore, the data processing unit 108 may route packets received from legacy network interface 118 using a non-legacy WLAN protocol, WWAN protocol, or other suitable non-legacy communication protocol.

An embodiment is a fully hardware embodiment, a fully software embodiment (including firmware, resident software, microcode, etc.), or all generally referred to herein as a "circuit," "module," or "system." There may be an embodiment in which a software aspect and a hardware aspect are combined. Further, embodiments of the subject matter of the present invention may take the form of computer program products implemented in any tangible representation medium having computer-usable program code implemented in the medium. As this specification does not list all possible variants, the embodiments described will be computer systems (or (one or) to perform processes according to the embodiments, whether or not they are currently described. It may be given as a computer program product or software that may include a machine-readable medium that stores instructions that can be used to program (plural) other electronic devices). A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (eg, a computer) (eg, software, processing application). The machine-readable medium can be a machine-readable storage medium or a machine-readable signal medium. Machine-readable storage media include, but are not limited to, magnetic storage media (eg, floppy® diskettes), optical storage media (eg, CD-ROM), optical magnetic storage media, read-only memory (ROM), etc. It may include random access memory (RAM), erasable programmable memory (eg EPROM and EEPROM), flash memory, or other types of tangible media suitable for storing electronic instructions. Machine-readable signal media include propagating data signals in which computer-readable program code is implemented, such as electrical, optical, acoustic, or other forms of propagating signals (eg, carrier waves, infrared signals, digital signals, etc.). obtain. Program code implemented on a machine-readable signal medium is, but is not limited to, wireline.

Computer program code for performing the operations of this embodiment includes object-oriented programming languages such as Java®, Smalltalk, C ++, and traditional procedural programming languages such as the "C" programming language or similar programming languages. It can be written in any combination of one or more programming languages. The program code runs entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on the remote computer. , Or it can run entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN), personal area network (PAN), or wide area network (WAN), or the connection is It can be done to an external computer (eg, through the internet using an internet service provider).

FIG. 7 is a block diagram of an embodiment of an electronic device 700 that includes a mechanism for multi-communication mode packet routing for a wireless communication system. In some implementations, the electronic device 700 can be a laptop, personal computer (PC), netbook, mobile phone, gaming device, or other suitable electronic system with wireless communication capabilities. The electronic device 700 can be a network device that supports both legacy and non-legacy communication protocols. The communication unit 708 of the electronic device 700 can receive data via the legacy network interface, process the data, and transmit it at a faster data transmission rate using a non-legacy communication protocol. The electronic device 700 includes a processor unit 702 (possibly including multiple processors, multiple cores, multiple nodes, and / or implementing multithreading). The electronic device 700 includes a memory unit 706. The memory unit 706 is a system memory (eg cache, SRAM, DRAM, zero capacitor RAM, twin transistor RAM, eDRAM, EDO RAM, DDR. It can be one or more of RAM, EEPROM, NRAM, RRAM®, SONOS, PRAM, etc.) or one or more of the possible machine-readable media implementations already described above. The electronic device 700 also has a bus 710 (eg PCI, ISA, PCI-Express, HyperTransport®, InfiniBand®, NuBus, AHB, AXI, etc.) and a wireless network interface (eg WLAN interface, Bluetooth). Includes at least one of (registered trademark) interface, WiMAX interface, ZigBee® interface, wireless USB interface, etc.) and wired network interface (eg, Ethernet interface, ATM interface, frame relay interface, SONET interface, etc.) Includes network interface 704.

The communication unit 708 of the electronic device 700 includes a conversion bridge 712, a routing unit 714, and a data processing unit 716. As described herein with reference to FIGS. 1-6, the communication unit 708 can implement a function based on which it identifies a non-legacy communication protocol in which packets from a legacy network interface can be sent. .. The communication unit 708 can translate the packet from the legacy packet format to the preferred non-legacy packet format and can transmit the packet using the selected non-legacy communication protocol. Any one of these features may be implemented in hardware and / or partially (or completely) on processor unit 702. For example, the function may be implemented using a purpose-built integrated circuit and logically implemented within a processor unit 702, a peripheral device, or a coprocessor on a card. In addition, the implementation may include fewer or additional components not shown in Figure 7, such as video cards, audio cards, additional network interfaces, peripheral devices, storage devices, and so on. The processor unit 702, memory unit 706, and network interface 706 are coupled to bus 710. Although shown as being coupled to bus 710, memory unit 706 can be coupled to processor unit 702.

Although the present embodiments have been described with reference to various embodiments and uses, it will be appreciated that these embodiments are exemplary and the scope of the subject matter of the present invention is not limited thereto. In general, the multi-communication mode packet routing mechanism for wireless communication systems described herein can be implemented with features that match any hardware system or multiple hardware systems. Many modifications, modifications, additions, and improvements are possible.

Multiple cases may be given for the components, behaviors, or structures described herein as a single case. Finally, the boundaries between the various components, behaviors, and datastores are somewhat arbitrary, and certain behaviors have been described in the context of certain exemplary configurations. Other allocations of function are envisioned and may fall within the scope of the subject matter of the present invention. In general, structures and functions presented as separate components in an exemplary configuration can be implemented as combined structures or components. Similarly, structures and functions presented as a single component can be implemented as separate components. These and other modifications, modifications, additions, and improvements may fall within the scope of the subject matter of the present invention.