# Patent

## Title
Method and system for auto coexistence priority selection for a SCO link

## Abstract

Methods and systems for auto coexistence priority selection for a SCO link are disclosed. Aspects of one method may include a first Bluetooth device communicating with a collocated WLAN device via a coexistence method. The first Bluetooth device, prior to executing a non-SCO task, which may comprise tasks that do not involve SCO packet transfer, may communicate low priority via the coexistence method if a Bluetooth SCO link is present between the first Bluetooth device and a second Bluetooth device, and if a current task being handled by the first Bluetooth device is a high priority task. If a SCO link is not present between the first and second Bluetooth devices, and if the current non-SCO task is a high priority task, the first Bluetooth device may communicate high priority via the coexistence method prior to executing the non-SCO task.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS/INCORPORATION BY REFERENCE
This application makes reference to U.S. patent application Ser. No. 11/439,776 filed on May 24, 2006.
The above stated application is hereby incorporated herein by reference in its entirety.
FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
Not Applicable
MICROFICHE/COPYRIGHT REFERENCE
Not Applicable
FIELD OF THE INVENTION
Certain embodiments of the invention relate to wireless communication. More specifically, certain embodiments of the invention relate to a method and system for auto coexistence priority selection for a SCO link.
BACKGROUND OF THE INVENTION
Some conventional communication systems are known to support wireless and wireline communication between wireless and/or wireline communication devices. Such communication systems range from national and/or international cellular telephone systems to the Internet, and to point-to-point in-home wireless networks. Each type of communication system is designed, and hence operates, in accordance with relevant communication standards. For instance, wireless communication systems may operate in accordance with one or more standards including, but not limited to, IEEE 802.11, Bluetooth, advanced mobile phone services (AMPS), digital AMPS, global system for mobile communications (GSM), code division multiple access (CDMA), local multi-point distribution systems (LMDS), multi-channel-multi-point distribution systems (MMDS), and/or variations thereof.
Depending on the type of wireless communication system, a wireless communication device, for example, a cellular telephone, two-way radio, personal digital assistant (PDA), personal computer (PC), laptop computer, or home entertainment equipment, communicates directly or indirectly with other wireless communication devices. For direct communications, also known as point-to-point communications, the participating wireless communication devices tune their receivers and transmitters to the same channel, or channels, and communicate via those channel(s). Each channel may utilize one or more of the plurality of radio frequency (RF) carriers of the wireless communication system. For indirect wireless communication, each wireless communication device communicates directly with an associated base station, for example, for cellular services, and/or an associated access point, for example, for an in-home or in-building wireless network, via an assigned channel or channels.
In order for each wireless communication device to participate in wireless communication session, it utilizes a built-in radio transceiver, which comprises a receiver and a transmitter, or it is coupled to an associated radio transceiver, for example, a station for in-home and/or in-building wireless communication networks, or a RF modem. The transmitter converts data into RF signals by modulating the data in accordance with the particular wireless communication standard. However, different communication systems may use different standards, for example, the IEEE 802.11 standard and the Bluetooth standard, which may share the same RF spectrum.
In order to alleviate signal interference from sharing an RF spectrum with other communication systems, the Bluetooth standard allows frequency hopping where information is transmitted at various frequencies. In this manner, the energy of the transmitted signal is spread across a RF spectrum from 2.402 GHz to 2.480 GHz in 79 channels with each channel separated by 1 MHz. The Bluetooth standard allows 1600 frequency hops per second. The advantage of the frequency hopping system is that it spreads information across a wide band of frequencies. Therefore, signals transmitted by other systems using a portion of the same frequency spectrum may appear as noise to only some of the frequencies used by Bluetooth in frequency hopping. Similarly, only a portion of Bluetooth transmission may interfere with signals transmitted by other systems.
Two or more Bluetooth devices, up to a total of eight devices, may comprise a piconet with one master device and up to seven slave devices. The piconet may share a common communication data channel with present capacity of 1 megabits per second (Mbps) up to a theoretical maximum of 3 Mbps. This data channel is divided in to time slots of 625 microseconds. Although a master device may initiate contact with any slave device, a slave device may only respond to a master device. A piconet link between a master device and a slave device may be either synchronous connection oriented (SCO) link or asynchronous connectionless (ACL) link. The piconet may support up to three SCO links, and any remaining bandwidth may be utilized by ACL links.
In some current systems, a Bluetooth device may share a platform with a WLAN device, and this may be referred to as coexistence. For example, a device such as a cellular telephone may have integrated thereon a Bluetooth radio and a Wireless LAN radio. There are times when the Bluetooth radio and the WLAN radio may need to operate simultaneously. For example, since the Bluetooth radio and the WLAN radio are close to each other in distance, and both operate in the same frequency band, transmission by one radio may interfere with transmission from the other radio. Transmission by one radio may also interfere with reception on another radio, or reception by the Bluetooth radio and/or the WLAN radio may be interfered with by transmission by other Bluetooth radios and/or WLAN radios.
A coexistence method may be used to communicate when a Bluetooth device is collocated with a WLAN device. Accordingly, the Bluetooth device may signal when the Bluetooth device may be receiving and/or transmitting, and the WLAN device may signal when the WLAN device may be transmitting. The Bluetooth device may indicate whether high priority is desired for subsequent transmissions. The high priority may allow Bluetooth transmission without interference from a simultaneous WLAN transmission. However, the indication typically may need to be made before the start of a frame.
A coexistence method may make use of a packet traffic arbitration (PTA) unit. The PTA unit may receive the priority indications from the WLAN device and the Bluetooth device, and may determine whether the Bluetooth device or the WLAN device may have priority by signaling appropriately to the Bluetooth device and/or the WLAN device. The PTA unit may be located, for example, with the WLAN circuitry. Accordingly, the signaling from the Bluetooth device may be to the WLAN circuitry.
In certain instances, the Bluetooth device may continuously transmit at a high priority, and thereby drastically reduce operating efficiency of the WLAN device. For example, if a HV2 SCO link is established with the Bluetooth device, every other frame may be a high priority frame for the duration of the SCO link. Additionally, if the Bluetooth device also executes a page scan while the SCO link is established, the frames not used for SCO link may be used for a high priority page scan. This may effectively prevent the collocated WLAN device from transmitting until either the SCO link is finished or the page scan is finished.
Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present invention as set forth in the remainder of the present application with reference to the drawings.
BRIEF SUMMARY OF THE INVENTION
A system and/or method for auto coexistence priority selection for a SCO link, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.
Various advantages, aspects and novel features of the present invention, as well as details of an illustrated embodiment thereof, will be more fully understood from the following description and drawings.



BRIEF DESCRIPTION OF SEVERAL VIEWS OF THE DRAWINGS
FIG. 1 illustrates a Bluetooth piconet, which may be utilized in connection with an embodiment of the invention.
FIG. 2 is a block diagram illustrating a host device with a Bluetooth device collocated with a WLAN device, which may be utilized in accordance with an embodiment of the invention.
FIG. 3a is a diagram illustrating SCO frames in Bluetooth transmission, in connection with an embodiment of the invention.
FIG. 3b is a graph illustrating exemplary HV2 SCO link in Bluetooth transmission, in connection with an embodiment of the invention.
FIG. 3c is a graph illustrating exemplary HV2 SCO link in Bluetooth transmission, in accordance with an embodiment of the invention.
FIG. 4 is a flow chart illustrating exemplary steps for auto coexistence priority selection for a SCO link, in accordance with an embodiment of the invention.



DETAILED DESCRIPTION OF THE INVENTION
Certain embodiments of the invention may be found in a method and system for auto coexistence priority selection for a SCO link. Aspects of the method may comprise a first Bluetooth device communicating with a collocated WLAN device via a coexistence method. The first Bluetooth device may communicate a low priority via the coexistence method prior to the first Bluetooth device executing a non-SCO task if a SCO link is present between the first Bluetooth device and a second Bluetooth device, and if the current non-SCO task being handled by the first Bluetooth device is a high priority task. The non-SCO task may be a task that does not involve a transfer of an SCO packet between two Bluetooth devices. The non-SCO tasks may be, for example, tasks such as Bluetooth inquiry scan and page scan. The SCO link may be a HV2 SCO link or a HV3 SCO link.
Execution of the non-SCO task may comprise transmitting and/or receiving at least one Bluetooth packet in at least one Bluetooth frame. The first Bluetooth device may operate as a master and the second Bluetooth device may operate as a slave. Alternatively, the first Bluetooth device may operate as a slave and the second Bluetooth device may operate as a master. If the Bluetooth SCO link is not present between the first Bluetooth device and the second Bluetooth device, and if the current non-SCO task being handled by the first Bluetooth device is a high priority task, a high priority may be communicated via the coexistence method prior to the first Bluetooth device executing the non-SCO task.
FIG. 1 illustrates a Bluetooth piconet that may be utilized in connection with an embodiment of the invention. Referring to FIG. 1, there is shown a personal computer (PC) 100, a laptop 110, and a personal digital assistant (PDA) 120. These three host devices, or host platforms, may each be Bluetooth enabled. Each host device may have a Bluetooth application and a Bluetooth communication device for transmitting and receiving signals. Each host device may then be considered to be a Bluetooth device. Up to eight Bluetooth devices may communicate with each other in a local network called a piconet. In a given piconet, only one Bluetooth device may be a master, while the others may be slaves.
The process for designating a master may be a dynamic process each time a piconet is set up. A Bluetooth device may be a member of multiple piconets, where it may be designated as a master device for one piconet, and a slave device for another piconet. Each Bluetooth device may use an algorithm that takes into account different variables, for example, performance and power requirements, in deciding whether it may want to be a master device. For example, since transmitting signals to locate other Bluetooth devices to form a piconet may utilize and transmission bandwidth, a Bluetooth device may wait passively for other Bluetooth devices to try to establish a piconet. A Bluetooth device that finds other Bluetooth devices, and establishes a connection with one or more Bluetooth devices, may be designated as the master Bluetooth device for that piconet. Multiple piconets that may have connection with each other, for example, where a Bluetooth device may be a member of more than one piconet, may be referred to as a scatternet.
Although only a single piconet is illustrated, in a system comprising a plurality of piconets, it may be possible for a Bluetooth device to operate as a master device in one piconet and as a slave device in an adjacent piconet. For example, a Bluetooth device A may operate as a master device in a first piconet P1 and as a slave device in a second piconet P2. In another example, the Bluetooth device A may operate as a slave device in a first piconet P1 and as a master device in a second piconet P2. A master device, for example, the PC 100, may communicate with each of the slave devices, for example, the laptop 110 and the PDA 120. However, the slave devices may not communicate directly with each other. When the master device moves out of range of communication, the piconet may be destroyed until another Bluetooth device establishes a piconet.
FIG. 2 is a block diagram illustrating a host device with a Bluetooth device and a WLAN device, which may be utilized in accordance with an embodiment of the invention. Referring to FIG. 2, there is shown a host device 200. The host device 200 may comprise a Bluetooth communication device 210, a WLAN communication device 212, a processor 220, and memory 230. The Bluetooth communication device 210 may be a Bluetooth radio, which may comprise suitable logic, circuitry and/or code that may enable communication of data, command and/or status with other Bluetooth devices.
The Bluetooth communication device 210 may comprise a handshaking block 210a and a processor 211. The handshaking block 210a may comprise suitable logic, circuitry and/or code that may enable communication with the WLAN communication device 212 using a coexistence method. The coexistence method may comprise using a plurality of signals, which may include a Priority signal from the Bluetooth device.
The handshaking block 210a may assert and deassert signals according to a particular coexistence method used to indicate whether the Bluetooth device may be executing a task that may be high priority. The coexistence method used may be design and/or implementation dependent. The processor 211 or the processor 220 may control the handshaking block 210a, for example. Some Bluetooth tasks, for example, tasks associated with an SCO link between two Bluetooth devices, may assert a high priority for frames used for SCO packet transfer. FIG. 2 may show that the Priority signal may be communicated to the WLAN communication device 212 for simplicity. The Priority signal, and other signals that may be associated with a coexistence method used, may be communicated to and from, for example, a packet traffic arbitration (PTA) unit 212a. 
The WLAN communication device 212 may be a WLAN radio, which may comprise suitable logic, circuitry and/or code that may enable communication of data, command and/or status with other WLAN devices. The processor 220 may comprise suitable logic, circuitry and/or code that may enable communication of data, command and/or status with the Bluetooth communication device 210 and the WLAN communication device 212. The memory 230 may comprise suitable logic and/or circuitry that may enable storage of information, such as, for example, data and/or code, that may be used by other devices.
In operation, the host device 200 may be, for example, the laptop 110 that may be enabled for Bluetooth via the Bluetooth communication device 210, and connected to a LAN via the WLAN communication device 212. The processor 220 may be the main processor for the host device 200. An application that uses the Bluetooth communication device 210 may be a different application than the application that is accessing the LAN via the WLAN communication device 212. Accordingly, the communication devices 210 and 212 may not be coordinated with respect to when each may transmit and/or receive.
A multiwire signaling protocol for a coexistence method, for example, may be used by a Bluetooth communication device 210 and a WLAN communication device 212 to better coordinate RF tasks in order to alleviate interference between the Bluetooth communication device 210 and the WLAN communication device 212. The signaling on the Bluetooth side may be accomplished by, for example, the handshaking block 210a, which may be controlled by, for example, the processor 211 and/or by hardware circuitry in the Bluetooth communication device 210.
For example, the PTA unit 212a may receive signals from the Bluetooth communication device 210 and from the WLAN communication device 212, and may arbitrate which device may have priority for transmission and/or reception during a specific period of time. The PTA unit 212a may communicate to the Bluetooth communication device 210 to indicate whether the Bluetooth communication device 210 may have priority. The PTA unit 212a may also communicate to the WLAN communication device 212 whether it may have priority.
FIG. 3a is a diagram illustrating SCO frames in Bluetooth transmission, in connection with an embodiment of the invention. Referring to FIG. 3a, there is shown a diagram 300 of SCO frames when HV1 method is used, a diagram 302 of SCO frames when HV2 method is used, and a diagram 304 of SCO frames when HV3 method is used. The HV1, HV2, and HV3 methods for a SCO link may be used for a variety of conditions that may have different interfering noise. For example, the HV3 method may be used when there is relatively little RF interference, and thus no forward error correction overhead may be needed for the voice data. Accordingly, 30 bytes of information may be transmitted in a packet, and a HV3 packet may be sent every 3 frames.
As RF interference increases, the HV2 method may be used. This method may transmit 20 information bytes per packet, and each packet may be sent every other frame. The HV2 method may also be protected by a 2⁄3 forward error correction code. As RF interference increases still more, the HV1 method may be used. This method may transmit 10 bytes of information per packet that may be protected by 1⁄3 forward error correction code. Accordingly, the forward error correction code for the HV1 and the HV2 methods may allow some errors to be corrected, but the throughput may be less. This may be because more frames may be dedicated to transmitting the same number of information bytes. The escalation scheme described for using the HV3, HV2, and HV1 may be exemplary only. For example, the host device 200 may use the HV1 SCO link as a default link.
In the diagram 300, there is shown the SCO frames 300a, 300b, 300c, and 300d. Since every frame may be dedicated to one SCO link, a Bluetooth master device may not be able to communicate with any other Bluetooth slave devices. In the diagram 302, there is shown the SCO frames 302a and 302c, which may be representative of the SCO frames in the HV2 method. Accordingly, every other frame may be used for the SCO link, and the other frames may be used for other purposes. This may include communicating with other Bluetooth devices by the Bluetooth master device during, for example, the frames 302b and 302d. 
In the diagram 304, there is shown the SCO frames 302a and 302d, which may be representative of the SCO frames in the HV3 method. Accordingly, every third frame may be used for the SCO link, and the other frames may be used for other purposes. For example, the other frames such as the frames 302b and 302c may be used to communicate with other Bluetooth devices by the Bluetooth master device. Accordingly, it may be seen that various percentage of the frames available may be used for an SCO link. The more frames used for an SCO link, the less a collocated WLAN device may be able to transmit.
FIG. 3b is a graph illustrating exemplary HV2 SCO link in Bluetooth transmission, in connection with an embodiment of the invention. Referring to FIG. 3b, there is shown frames 310, . . . , 316 that may be used for a HV2 method SCO link. Accordingly, every other frame may be allocated to an SCO link. These frames may be, for example, the frames 310, 312, 314, and 316. The Bluetooth communication device 210 may indicate to the collocated WLAN device that these frames may be high priority frames. Accordingly, the WLAN device may decide not to transmit at these times.
A Bluetooth communication device may also have other tasks that may be deemed to be a high priority task, and hence indicate a high priority to the collocated WLAN device. The tasks deemed to be a high priority task may be implementation dependent, but some may be, for example, inquiry scan and page scan. During an inquiry scan, a Bluetooth master device may locate other Bluetooth devices that may be available to connect to its piconet. During a page scan, those Bluetooth devices may be connected to a piconet by the Bluetooth master device for that piconet.
If a page scan task is set for high priority, then the Bluetooth master device may indicate a high priority for the other frames not used for the SCO link in order to use them for page scan. The frames used for page scan may be, for example, the frames 311, 313, and 315. Accordingly, the Bluetooth master device may continuously indicate high priority frames, and thereby keep the collocated WLAN device from transmitting. Therefore, the WLAN device may not be able to transmit until either the SCO link is removed, the Bluetooth master device times out on its page scan, or the Bluetooth device that is searched for during the page scan is located and connected on to the piconet. This may adversely affect the throughput of the WLAN device.
A Bluetooth slave device may also assert the transmission portion of a frame as high priority. This may be described by the U.S. application Ser. No. 11/439,776, which is hereby incorporated herein by reference in its entirety. A Bluetooth slave device may allow a collocated WLAN device to transmit more than a Bluetooth master device since the Bluetooth slave device may only assert high priority for one slot of a non-SCO frame as high priority, rather than assert high priority for both slots of a frame, as a Bluetooth master device might.
FIG. 3c is a graph illustrating exemplary HV2 SCO link in Bluetooth transmission, in accordance with an embodiment of the invention. Referring to FIG. 3c, there is shown frames 320, . . . , 326. The frames 320, 322, 324, and 326 may be allocated for a HV2 method SCO link. However, in order to allow the collocated WLAN communication device, for example, the WLAN communication device 212, to transmit during the SCO link, the Bluetooth communication device 210 may assign a low priority to the other tasks, such as for example, page scan or inquiry scan.
Accordingly, a Bluetooth device may not indicate to the collocated WLAN device that the frames not used for the SCO link may be high priority frames. In this manner, the alternate frames, such as for example, the frames 321, 323, and 325, may be used by, for example, the WLAN communication device 212 to transmit to other WLAN devices. When the SCO link is no longer active, then the Bluetooth device may assign a high priority to those tasks whose priority may have been lowered when the SCO link was active.
FIG. 4 is a flow chart illustrating exemplary steps for auto coexistence priority selection for a SCO link, in accordance with an embodiment of the invention. Referring to FIG. 4, in step 400, the Bluetooth communication device 210 may determine whether a SCO link with another Bluetooth device is present. If so, the next step may be step 402. If not, the next step may be step 400.
In step 402, the Bluetooth communication device 210 may determine the non-SCO tasks that may be lowered from a high priority to a low priority, where the priority may be communicated to a collocated WLAN device, for example, via the PTA 212a, prior to a packet being transmitted or received by the Bluetooth communication device 210. This may allow, for example, a collocated WLAN device to transmit during the frames that are not used to transmit voice data for the SCO link. In step 404, the Bluetooth communication device 210 may indicate a low priority, for example, via the PTA 212a, to the WLAN device, for example, the WLAN communication device 212, for the frames that are not used to transmit voice data for the SCO link. Accordingly, the collocated WLAN device may be able to transmit during at least a portion of each of the frames that are not used to transmit voice data for the SCO link.
In step 406, the Bluetooth communication device 210 may determine whether there are any SCO links present. If so, the next step may be step 406 again. Otherwise the next step may be step 408. In step 408, the Bluetooth communication device 210 may determine the non-SCO tasks whose priority communicated to the collocated WLAN communication device 212 may be raised from a low priority to a high priority. These tasks may be, for example, the non-SCO tasks determined in step 402. Generally, these tasks may be those that may have a high priority communicated to the WLAN communication device 212 prior to transmitting a packet in a frame. In step 410, the Bluetooth communication device 210 may indicate a high priority to the collocated WLAN device for the frames that may be used for those tasks. Accordingly, when there is no SCO link between, for example, the Bluetooth communication device 210 and another Bluetooth communication device, the Bluetooth communication device 210 may be able to transmit packets at a high priority.
Another embodiment of the invention may provide a machine-readable storage, having stored thereon, a computer program having at least one code section executable by a machine, thereby causing the machine to perform the steps as described above for auto coexistence priority selection for a SCO link.
In accordance with an embodiment of the invention, aspects of an exemplary system may comprise handshaking circuitry, for example, the handshaking block 210a, within a Bluetooth communication device 210. The handshaking block 210a may enable communication of priority with a collocated WLAN communication device 212. The communication of the priority may be made prior to the Bluetooth communication device 210 transmitting and/or receiving a packet in a Bluetooth frame. If a Bluetooth SCO link is present between the Bluetooth communication device 210 and another Bluetooth device, and if a current non-SCO task being handled by the Bluetooth communication device 210 is a high priority task, then the priority communicated by the handshaking block 210a for packets associated with the current non-SCO task may be low priority. A non-SCO task may be a task that does not comprise transfer of SCO packets. The SCO link may be a HV2 SCO link or a HV3 SCO link.
Execution of the non-SCO task may comprise transmitting and/or receiving at least one Bluetooth packet in at least one Bluetooth frame. The Bluetooth communication device 210 may operate as a master and the other Bluetooth device may operate as a slave. Alternatively, the Bluetooth communication device 210 may operate as a slave and the other Bluetooth device may operate as a master.
If a Bluetooth SCO link is not present between the Bluetooth communication device 210 and the other Bluetooth device, and if the current non-SCO task being handled by the Bluetooth communication device 210 is a high priority task, the handshaking block 210a may communicate a high priority using the coexistence interface prior to the Bluetooth communication device 210 executing the non-SCO task.
Accordingly, the present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.
The present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.
While the present invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the present invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present invention without departing from its scope. Therefore, it is intended that the present invention not be limited to the particular embodiment disclosed, but that the present invention will comprise all embodiments falling within the scope of the appended claims.

## Claims

1. A method for wireless communication, the method comprising:
responsive to (1) a Bluetooth SCO link being present between a first Bluetooth device communicating via a coexistence method with a collocated WLAN device and a second Bluetooth device and (2) a non-SCO task, which does not comprise transfer of an SCO packet, being handled by said first Bluetooth device and being a high priority non-SCO task, communicating a low priority with regard to said non-SCO task via said coexistence method prior to said first Bluetooth device executing said non-SCO task, said communicating of said low priority enabling transmission of said collocated WLAN device within one or more frames not allocated for said Bluetooth SCO link during said Bluetooth SCO link,
wherein a high priority is communicated with regard to said non-SCO task via said coexistence method prior to said first Bluetooth device executing said non-SCO task when said Bluetooth SCO link is not present between said first Bluetooth device and said second Bluetooth device.

2. The method according to claim 1, wherein said executing said non-SCO task comprises one or both of transmitting at least one Bluetooth packet in at least one Bluetooth frame and receiving at least one Bluetooth packet in at least one Bluetooth frame.

3. The method according to claim 1, wherein said first Bluetooth device operates as a master and said second Bluetooth device operates as a slave.

4. The method according to claim 1, wherein said first Bluetooth device operates as a slave and said second Bluetooth device operates as a master.

5. The method according to claim 1, comprising, if said Bluetooth SCO link is not present between said first Bluetooth device and said second Bluetooth device, and if said current non-SCO task being handled by said first Bluetooth device is a high priority task, communicating said high priority via said coexistence method prior to said first Bluetooth device executing said task.

6. The method according to claim 1, wherein said SCO link is an HV2 SCO link.

7. The method according to claim 1, wherein said SCO link is an HV3 SCO link.

8. A non-transitory machine-readable storage having stored thereon, a computer program having at least one code section for wireless communication, the at least one code section being executable by a machine for causing the machine to perform steps comprising:
responsive to (1) a Bluetooth SCO link being present between a first Bluetooth device communicating via a coexistence method with a collocated WLAN device and a second Bluetooth device and (2) a non-SCO task, which does not comprise transfer of an SCO packet, being handled by said first Bluetooth device and being a high priority non-SCO task, communicating a low priority with regard to said non-SCO task via said coexistence method prior to said first Bluetooth device executing said non-SCO task, said communicating of said low priority enabling transmission of said collocated WLAN device within one or more frames not allocated for said Bluetooth SCO link during said Bluetooth SCO link,
wherein a high priority is communicated with regard to said non-SCO task via said coexistence method prior to said first Bluetooth device executing said non-SCO task when said Bluetooth SCO link is not present between said first Bluetooth device and said second Bluetooth device.

9. The non-transitory machine-readable storage according to claim 8, wherein said executing said non-SCO task comprises one or both of transmitting at least one Bluetooth packet in at least one Bluetooth frame and receiving at least one Bluetooth packet in at least one Bluetooth frame.

10. The non-transitory machine-readable storage according to claim 8, wherein said first Bluetooth device operates as a master and said second Bluetooth device operates as a slave.

11. The non-transitory machine-readable storage according to claim 8, wherein said first Bluetooth device operates as a slave and said second Bluetooth device operates as a master.

12. The non-transitory machine-readable storage according to claim 8, wherein said at least one code section comprises code that allows, if said Bluetooth SCO link is not present between said first Bluetooth device and said second Bluetooth device, and if said current non-SCO task being handled by said first Bluetooth device is a high priority task, communicating said high priority via said coexistence method prior to said first Bluetooth device executing said task.

13. The non-transitory machine-readable storage according to claim 8, wherein said SCO link is an HV2 SCO link.

14. The non-transitory machine-readable storage according to claim 8, wherein said SCO link is an HV3 SCO link.

15. A system for wireless communication, the system comprising:
handshaking circuitry for a coexistence interface that is operable to enable communication of a low priority with regard to a non-SCO task, with a WLAN device collocated with a first Bluetooth device prior to said first Bluetooth device executing said non-SCO task, said communication of said low priority being responsive to (1) a Bluetooth SCO link being present between said first Bluetooth device and a second Bluetooth device and (2) if said current task being handled by said first Bluetooth device being a high priority non-SCO task, wherein said non-SCO task does not comprise transfer of an SCO packet and wherein said communication of said low priority enables transmission of said collocated WLAN device within one or more frames not allocated for said Bluetooth SCO link during said Bluetooth SCO link; and wherein said non-SCO task comprises one or both of a Bluetooth page scan and a Bluetooth inquiry scan,
wherein a high priority is communicated with regard to said non-SCO task prior to said first Bluetooth device executing said non-SCO task when said Bluetooth SCO link is not present between said first Bluetooth device and said second Bluetooth device.

16. The system according to claim 15, wherein said executing said non-SCO task comprises one or both of transmitting at least one Bluetooth packet in at least one Bluetooth frame and receiving at least one Bluetooth packet in at least one Bluetooth frame.

17. The system according to claim 15, wherein said first Bluetooth device is operable as a master and said second Bluetooth device is operable as a slave.

18. The system according to claim 15, wherein said first Bluetooth device is operable as a slave and said second Bluetooth device is operable as a master.

19. The system according to claim 15, wherein said handshaking circuitry is operable to enable communication of said high priority via a coexistence interface prior to said first Bluetooth device said executing said task if said Bluetooth SCO link is not present between said first Bluetooth device and said second Bluetooth device, and if said current non-SCO task being handled by said first Bluetooth device is a high priority task.

20. The system according to claim 15, wherein said SCO link is an HV2 SCO link.