US20200008213A1 - Traffic coexistence for collocated transceivers including bluetooth transceivers - Google Patents
Traffic coexistence for collocated transceivers including bluetooth transceivers Download PDFInfo
- Publication number
- US20200008213A1 US20200008213A1 US16/144,870 US201816144870A US2020008213A1 US 20200008213 A1 US20200008213 A1 US 20200008213A1 US 201816144870 A US201816144870 A US 201816144870A US 2020008213 A1 US2020008213 A1 US 2020008213A1
- Authority
- US
- United States
- Prior art keywords
- transceiver
- schedule
- quietie
- transmission
- bluetooth
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/001—Synchronization between nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W16/00—Network planning, e.g. coverage or traffic planning tools; Network deployment, e.g. resource partitioning or cells structures
- H04W16/14—Spectrum sharing arrangements between different networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1215—Wireless traffic scheduling for collaboration of different radio technologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/50—Allocation or scheduling criteria for wireless resources
- H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
Abstract
Description
- This application claims the benefit under 35 U.S.C. § 119(e) of U.S. Provisional Patent Application No. 62/690,714, filed on Jun. 27, 2018, which is incorporated by reference herein in its entirety for all purposes.
- This disclosure generally relates to collocated transceivers, and more specifically, to implementation of coexistence of traffic associated with such collocated transceivers.
- Various devices may include transceivers configured to transmit data in accordance with various wireless communications protocols. For example, transceivers may utilize Wi-Fi communications protocols, or may use Bluetooth communications protocols. In some cases, multiple transceivers may be implemented within a single device, and may share other system resources, such as transmission media, and components associated with such transmission media such as antenna. Accordingly, multiple transceivers may share a single antenna. However, such transceivers remain limited in their ability to share such transmission medium resources efficiently and effectively.
-
FIG. 1 illustrates an example of a system that includes collocated transceivers, configured in accordance with some embodiments. -
FIG. 2 illustrates an example of a device that includes collocated transceivers, configured in accordance with some embodiments. -
FIG. 3 illustrates an example of a first timing diagram, configured in accordance with some embodiments. -
FIG. 4 illustrates an example of a second timing diagram, configured in accordance with some embodiments. -
FIG. 5 illustrates flow chart of an example of a method for implementing coexistence of traffic for collocated transceivers in accordance with some embodiments. -
FIG. 6 illustrates flow chart of another example of a method for implementing coexistence of traffic for collocated transceivers in accordance with some embodiments. - In the following description, numerous specific details are set forth in order to provide a thorough understanding of the presented concepts. The presented concepts may be practiced without some or all of these specific details. In other instances, well known process operations have not been described in detail so as to not unnecessarily obscure the described concepts. While some concepts will be described in conjunction with the specific examples, it will be understood that these examples are not intended to be limiting.
- Various devices may include one or more transceivers that share transmission media. For example, a single device may include a Bluetooth transceiver as well as a wireless local area network transceiver (WLAN) transceiver. Such transceivers may share, at least in part, a common wireless medium of a 2.4 GHz band. Moreover, such transceivers may also share hardware associated with such a transmission medium, such as an antenna. Accordingly, coexistence techniques may be implemented so that the different transceivers sharing the same transmission medium may both utilize the transmission medium without interfering with each other's communications. Some coexistence techniques utilize the transmission of CTS-to-Self frame or management frame with every period of a transmission. In such techniques, such a frame is sent with each duty cycle and occupies a large amount of the available transmission traffic and might not be entirely effective in protecting transmitted traffic.
- Various embodiments are disclosed herein that provide collocated transceivers within a collocated device to share a transmission medium in an efficient and effective manner. As will be discussed in greater detail below, collocated devices may include different transceivers that share a transmission medium. As will be discussed in greater detail below, embodiments disclosed herein utilize the generation and transmission of a medium access schedule, that may be a QuietIE based schedule, to facilitate coexistence between different transceivers that share a transmission medium by, for example utilizing the same transmission band. Accordingly, the activity of downstream devices and the first transceiver may be configured and synchronized based on transmission characteristics of the second transceiver, and this may be accomplished using a single initial beacon frame. In this way, the number of frames utilized for protection and coexistence of collocated transceivers is reduced, and the amount of transmitted data utilized to ensure such protection and coexistence is reduced. Moreover, the efficacy of such protection and coexistence is increase as well. Various embodiments are now discussed in greater detail.
-
FIG. 1 illustrates an example of a system that includes collocated transceivers, configured in accordance with some embodiments. As will be discussed in greater detail below, devices disclosed herein may include multiple transmission devices, such as transceivers, that may share a transmission medium. Accordingly, devices as disclosed herein are configured to implement coexistence of such transceivers in an efficient manner that greatly reduces the amount of transmission overhead utilized to implement such coexistence and sharing of the transmission medium. - In various embodiments,
system 100 includes collocateddevice 102. As discussed above, collocateddevice 102 is a device that is configured to include multiple collocated transmission devices that may share a common transmission medium. For example, collocateddevice 102 may includefirst transceiver 104 andsecond transceiver 106. In various embodiments,first transceiver 104 andsecond transceiver 106 each include a transmitter and a receiver. As will be discussed in greater detail below,first transceiver 104 may include a first transmitter and receiver compatible with a first communications protocol, andsecond transceiver 106 may include a second transmitter and receiver compatible with a second communications protocol. Bothfirst transceiver 104 andsecond transceiver 106 are configured to transmit and receive data viaantenna 109 which is configured to transmit and receive wireless communications signals. Accordingly, collocateddevice 102 is configured such that network traffic associated withfirst transceiver 104 andsecond transceiver 106 shares the utilization ofantenna 109. - As will be discussed in greater detail below with reference to
FIG. 2 ,first transceiver 104 may include a processing device, such asprocessing device 108, that is configured to schedule network traffic to implement coexistence of data traffic forfirst transceiver 104 andsecond transceiver 106. More specifically,processing device 108 may be configured to determine and generate a schedule utilized send traffic associated withfirst transceiver 104. Such a schedule may be determined and generated based on a protocol utilized bysecond transceiver 106, and the schedule may be implemented utilizing a QuietIE parameter of a transmitted frame. Accordingly, coexistence may be implemented by generating a QuietIE schedule that is transmitted in a beacon frame, and is synchronized to periodic activity ofsecond transceiver 106. Additional details of the scheduling of such traffic are discussed in greater detail below with reference toFIG. 2 . - As will also be discussed in greater detail below with reference to
FIG. 2 ,first transceiver 104 may be a WLAN device, andsecond transceiver 106 may be a Bluetooth device. Accordingly, in some embodiments, collocateddevice 102 includes a WLAN transceiver and a Bluetooth transceiver that share a particular transmission medium that utilizes shared hardware components, such asantenna 109. Moreover, the schedule generated byprocessing device 108 for the WLAN transceiver is determined based, at least in part, on the Bluetooth protocol utilized by the Bluetooth transceiver. While various embodiments disclosed herein describesecond transceiver 106 as being compatible with a Bluetooth protocol, it will be appreciated that other implementations ofsecond transceiver 106 are contemplated and disclosed herein. For example,second transceiver 106 may be compatible with other protocols such as Bluetooth Low Energy (BLE) or cellular protocols such as a Global System for Mobile Communications (GSM) protocol. - In various embodiments, collocated
device 102 is configured as a software enabled access point (SoftAP). Accordingly, in some embodiments, collocateddevice 102 is configured to function as a wireless access point that handles wireless communication and routing of network traffic with one or more other wireless devices, such as first plurality ofdevices 110 and second plurality ofdevices 120 discussed in greater detail below and also with reference to, for example,FIG. 3 . In some embodiments, collocateddevice 102 is configured as a client device, or a station (STA), as will also be discussed in greater detail below with reference to, for example,FIG. 4 . - In some embodiments,
system 100 includes first plurality ofdevices 110 which may be devices configured to transmit and receive wireless network traffic utilizing a transmission modality similar to that offirst transceiver 104. For example, iffirst transceiver 104 is a WLAN transceiver, first plurality ofdevices 110 may be WLAN devices. In a particular example, first plurality ofdevices 110 may include devices such as mobile phones and mobile devices, laptops and computing devices, as well as any other suitable wireless-enabled device such as smart home devices. Accordingly, first plurality ofdevices 110 is configured to communicate withfirst transceiver 104. -
System 100 also includes second plurality ofdevices 120 which may be devices configured to transmit and receive wireless network traffic utilizing a transmission modality similar to that ofsecond transceiver 106. For example, ifsecond transceiver 106 is a Bluetooth transceiver, second plurality ofdevices 120 may be Bluetooth devices. In a particular example, second plurality ofdevices 120 may also include devices such as mobile phones and mobile devices, as well as laptops and computing devices. Moreover, second plurality ofdevices 120 may include various smart devices, such as wearable devices. Accordingly, second plurality ofdevices 120 is configured to communicate withsecond transceiver 106. - In various embodiments,
first transceiver 104 andsecond transceiver 106 may be located on a same chip. Accordingly, the transceivers may be implemented as integrated circuits on a same die or substrate. In some embodiments,first transceiver 104 andsecond transceiver 106 may be implemented on different dies or chips. Accordingly,first transceiver 104 andsecond transceiver 106 may be implemented in different in different integrated circuits or processing devices. Accordingly, whileFIG. 1 illustrates one example, of howfirst transceiver 104 andsecond transceiver 106 may be implemented, it will be appreciated that collocateddevice 102 as well asfirst transceiver 104 andsecond transceiver 106 may be configured in any of the ways described above and disclosed herein. - Moreover, while
FIG. 1 andFIG. 2 discussed in greater detail below describe the operation offirst transceiver 104 andsecond transceiver 106 with reference toantenna 109, it will be appreciated that collocateddevice 102 may include multiple antennas. Accordingly,first transceiver 104 may be coupled to a first antenna, andsecond transceiver 106 may be coupled to a second antenna, and the access to and utilization of such antennas may be configured as disclosed herein. In this way, access to the transmission medium may be controlled despite the use of multiple antennas. -
FIG. 2 illustrates an example of a device that includes collocated transceivers, configured in accordance with some embodiments. As discussed above, devices disclosed herein may include multiple transmission devices, such as transceivers, that may share a transmission medium. As also discussed above, a collocated device, such as collocateddevice 102, may include one or more transceivers, such asfirst transceiver 104 andsecond transceiver 106 that share access to a transmission medium and share hardware components, such asantenna 109. - As noted above,
first transceiver 104 andsecond transceiver 106 may be different types of transceivers that utilize different transmission protocols. For example,first transceiver 104 may be a WLAN transceiver that is configured to utilize a Wi-Fi transmission protocol in accordance with a suitable 802.11 specification. Moreover,second transceiver 106 may be a Bluetooth transceiver that is configured to utilize Bluetooth transmission protocols. Accordingly,second transceiver 106 may be configured to have a specific protocol issuing particular requests, such as Bluetooth sync events or requests, at particular times as designated by the Bluetooth transmission protocol. - In various embodiments,
processing device 108, may include a packet traffic arbiter configured to manage data packets associated withfirst transceiver 104, andprocessing device 108 is configured to generate the schedule. More specifically,processing device 108 is configured to generate a QuietIE schedule based on a transmission parameter ofsecond transceiver 106. In various embodiments, a transmission parameter may refer to particular feature or characteristic of a transmission protocol, such as a period, frequency, amplitude, duty cycle, sequence of data values, or any other suitable unique characteristic or identifier associated with the transmission protocol. - Thus, according to some embodiments,
processing device 108 may identify periods of activity ofsecond transceiver 106 based on the transmission protocol ofsecond transceiver 106. In this example,second transceiver 106 is a Bluetooth transceiver that utilizes an enhanced synchronous connection-oriented (eSCO) Bluetooth protocol. Such a protocol may have specific times at which sync requests are made, and at which Bluetooth traffic begins and ends. Accordingly,processing device 108 is configured to querysecond transceiver 106 to determine when such traffic is expected.Processing device 108 is further configured to generate a QuietIE schedule based on the results of such a query. The generated QuietIE schedule may be generated based on an identification or estimation of times at which traffic ofsecond transceiver 106 is expected and not expected, such as when there is Bluetooth traffic, and when there is no Bluetooth traffic. In various embodiments, such parameters or properties may be queried, observed, or inferred. For example, Bluetooth traffic may have a particular carrier frequency with a particular duty cycle within that frequency. Based on such parameters,processing device 108 may determine whensecond transceiver 106 is not active and when there is no Bluetooth traffic. Accordingly, the generated QuietIE schedule is configured based on an indication of when transmission is possible byfirst transceiver 104, such as when second transceiver is not transmitting. More specifically, the Quite IE schedule may be synced to particular features ofsecond transceiver 106, such as Bluetooth sync events. Thus, the generated QuietIE schedule may be generated based on times at which the transmission medium is available forfirst transceiver 104, as identified based on the transmission parameter ofsecond transceiver 106. - In various embodiments, the QuietIE schedule may identify periods when the transmission medium is quiet and absent, or periods when it is available and present. Accordingly, an access point generating the Quite IE schedule may include the Quite IE schedule in a beacon frame that is transmitted to downstream client devices, and the QuietIE schedule may identify when the access point is quiet and when the access point is available. In various embodiments, such downstream client devices may also be referred to herein as stations. In this way, operation of
first transceiver 104 as well as downstream devices in communication withfirst transceiver 104 are configured to implement traffic in accordance with quiet and available times that are determined based on the estimated Bluetooth traffic activity ofsecond transceiver 106. - Furthermore,
processing device 108 is configured to generate the first and second control signals in accordance with the generated QuietIE schedule. For example, during an enabled time in which there is no expected Bluetooth traffic, and traffic is allowed forfirst transceiver 104, which may be a WLAN transceiver which appears as present when enabled, first control signal may enable coupling betweenantenna 109 andfirst transceiver 104, and second control signal may disable coupling betweenantenna 109 andsecond transceiver 106. Moreover, during a quiet time or disabled time in which there is expected Bluetooth traffic and traffic is not allowed forfirst transceiver 104, first control signal may disable coupling betweenantenna 109 andfirst transceiver 104, and second control signal may enable coupling betweenantenna 109 andsecond transceiver 106. Additional details regarding such signals will be discussed in greater detail below with reference toFIGS. 3 and 4 . - In various embodiments, collocated
device 102 further includesRF switch 202 which is coupled toantenna 109, and is configured to enable and disable coupling between the transceivers andantenna 109. For example, a first control signal may control coupling/decoupling betweenfirst transceiver 104 andantenna 109. Moreover, a second control signal may control coupling/decoupling betweensecond transceiver 106 andantenna 109. In various embodiments, such control signals are generated by processingdevice 108. - In some embodiments, collocated
device 102 further includesinterface 204 which provides a direct communicative interface betweenfirst transceiver 104 andsecond transceiver 106. In various embodiments, collocateddevice 102 also includesprocessor 206 andmemory 208 which are configured to handle one or more processing operations associated withfirst transceiver 104,second transceiver 106,interface 204, andRF switch 202, and store data such as state data and backup data. Moreover, communications between components of collocateddevice 102 may be facilitated bybus 210. -
FIG. 3 illustrates an example of a first timing diagram, implemented in accordance with some embodiments. As discussed above, various control signals may be generated by processingdevice 108. Moreover, such control signals may be grant signals that are configured to grant or deny access of a transceiver to a shared transmission medium. For example,first control signal 302 may be configured to grant or deny transmission medium access tofirst transceiver 104 based, at least in part, on the QuietIE schedule, and may be generated by processingdevice 108. Moreover,second control signal 304 may be configured to grant or deny transmission medium access tosecond transceiver 106 based, at least in part, on the QuietIE schedule, and may be provided fromprocessing device 108 tosecond transceiver 106. - In another example, such control signals may be utilized to enable and disable coupling between
first transceiver 104 andantenna 109. In this way,first control signal 302 may be utilized as a transmission medium grant signal forfirst transceiver 104. Similarly,second control signal 304 may be utilized to enable and disable coupling betweensecond transceiver 106 andantenna 109. In this way,second control signal 304 may be utilized as a transmission medium grant signal forsecond transceiver 106. -
First timeline 306 illustrates an example of states associated withfirst transceiver 104. For example, whenfirst transceiver 104 is not granted access to the transmission medium,first transceiver 104 may be absent or quiet. Moreover, whenfirst transceiver 104 is granted access to the transmission medium,first transceiver 104 is present or available.First timeline 306 also illustrates the initial transmission of a beacon frame that includes the QuietIE schedule. In various embodiments, the collocated device includingfirst transceiver 104 andsecond transceiver 106 is configured as an access point that is managing the coexistence offirst transceiver 104 andsecond transceiver 106 in the transmission medium. In such an example, as shown infirst timeline 306, the coexistence betweenfirst transceiver 104 andsecond transceiver 106 is implemented using a single beacon frame. Furthermore, as shown insecond timeline 308, a downstream client device may implement the transmitted QuietIE schedule to synchronize its quiet and active times to the generated schedule. Accordingly, the downstream client device may be quiet whenfirst transceiver 104 is not granted access to the transmission medium, and the downstream client device may be in active whenfirst transceiver 104 is granted access to the transmission medium. -
FIG. 4 illustrates an example of a second timing diagram, implemented in accordance with some embodiments. As similarly discussed above, control signals, such asfirst control signal 302 andsecond control signal 304 may be generated by processingdevice 108 and utilized to enable and disable coupling betweenfirst transceiver 104 andantenna 109 as well as to enable and disable coupling betweensecond transceiver 106 andantenna 109. - As also shown in
FIG. 4 ,first timeline 306 illustrates an example of states associated withfirst transceiver 104, andsecond timeline 308 illustrates how a downstream client device may implement the transmitted QuietIE schedule to synchronize its quiet and active times to the generated schedule.FIG. 4 further illustrates how a request frame may be issued by the downstream device to initiate the generation of the QuietIE schedule. More specifically, collocateddevice 102 may be a downstream device, such as a client device or station, that is managing the coexistence offirst transceiver 104 andsecond transceiver 106 in the transmission medium. Accordingly, when configured in this way collocateddevice 102 may transmit a QuietIE request frame to an access point. In this example, the access point may generate a QuietIE response action which may include the generation of the QuietIE schedule as described above. The QuietIE schedule may then be distributed in a beacon frame to all downstream client devices. In this way, the generation of a QuietIE schedule may be responsive to a request from a client device when a client device is managing the coexistence offirst transceiver 104 andsecond transceiver 106 in the transmission medium. -
FIG. 5 illustrates flow chart of an example of a method for implementing coexistence of traffic for collocated transceivers in accordance with some embodiments. As discussed above, the implementation of coexistence of traffic as disclosed herein may utilize the transmission of far fewer frames, and result in reduction of transmission overhead associated with such coexistence of traffic. - Accordingly,
method 500 may being withoperation 502 during which a QuietIE request action may be issued. As discussed above, the QuietIE request may be generated by a downstream client device which may be a station. As noted above, such a downstream client device may, for example, be a WLAN device that is in communication withfirst transceiver 104. -
Method 500 may proceed tooperation 504 during which a QuietIE response action may be performed. In various embodiments, the QuietIE response action may include the transmission of a QuietIE response frame. -
Method 500 may proceed tooperation 506 during which a QuietIE schedule may be generated. As discussed above, the QuietIE schedule may be generated based on the transmission parameter of another collocated transceiver, such assecond transceiver 106. In this way, the QuietIE schedule may be generated based on one or more characteristics of the transmission protocol ofsecond transceiver 106. For example, the QuietIE schedule may be generated for a collocated WLAN transceiver and downstream STAs, and such QuietIE schedule may be generated based, at least in part, on a Bluetooth protocol implemented by a collocated Bluetooth transceiver. -
Method 500 may proceed tooperation 508 during which the QuietIE schedule may be transmitted. As noted above, the QuietIE schedule may be included in a beacon frame that is transmitted to all downstream devices. In this way, the downstream devices may receive the QuietIE schedule, and synchronize their quiet and active times based on the expected activity ofsecond transceiver 106. Moreover, as similarly discussed above, the transmission and implementation of the QuietIE schedule enables the implementation of coexistence of the collocated transceivers utilizing the single beacon frame, and request frame if utilized, as opposed to a CTS-to-Self frame or management frame with every transmission. -
Method 500 may proceed tooperation 510 during which one or more control signals may be generated. As also described above, control signals, such as the first and second control signals may be generated and implemented based on the identified times underlying the QuietIE schedule. Accordingly, the first and second control signals may be generated and implemented to enable utilization of the transmission medium and associated hardware that may include, for example,antenna 109, in a manner that in consistent with the generated QuietIE schedule. -
FIG. 6 illustrates flow chart of another example of a method for implementing coexistence of traffic for collocated transceivers in accordance with some embodiments. As will be discussed in greater detail below, the implementation of coexistence of traffic as disclosed herein may utilize the transmission of far fewer frames, and may also implement legacy techniques when the implementation of a QuietIE schedule is not feasible. - Accordingly,
method 600 may being withoperation 602 during which it may be determined if a QuietIE schedule is available. Such a determination may be made based on whether or not a QuietIE schedule is stored in a memory of a collocated device, or based on one or more indicators or identifiers that are configured to identify the availability of a QuietIE schedule. In various embodiments, if a QuietIE schedule is available,method 600 may proceed tooperation 604. - During
operation 604, it may be determined if a transceiver, such as a second transceiver, may be aligned with the QuietIE schedule. In various embodiments, such a determination may be made based on a comparison of the QuietIE schedule with parameters or characteristics of the transmission protocol of the second transceiver. For example, available periods and quiet periods may be compared against parameters, such as duty cycle and period, of the transmission protocol of the second transceiver, and it may be determined if it is possible to align the second transceiver with the available periods and quiet periods given those parameters or characteristics. If it is determined that alignment is possible,method 600 may proceed tooperation 606 during which the second transceiver may be granted access to the transmission medium based on requests issued by the second transceiver and based on the transmission protocol of the second transceiver. For example, the second transceiver may be a Bluetooth transceiver, and may be granted access to the transmission medium based on Bluetooth transmission requests. - Returning to
operation 604, if it is determined that a transceiver cannot be aligned with the QuietIE schedule,method 600 may proceed tooperation 608 during which it may be determined if the QuietIE schedule may be aligned with a period of the transmission protocol of the second transceiver. For example, it may be determined if the QuietIE schedule may be aligned with a period of the second transceiver utilizing a Bluetooth protocol. Such a determination may be made based on one or more features or characteristics of the QuietIE schedule, such as a period or frequency, and a period of the transmission protocol of the second transceiver. If it is determined that the QuietIE schedule may be aligned with a period of the transmission protocol of the second transceiver,method 600 may proceed tooperation 610. - During
operation 610, the QuietIE schedule may be adjusted and implemented based on requests issued by the second transceiver. For example, the QuietIE schedule may be moved or adjusted based on requests issued by the second transceiver, which may be Bluetooth requests. In this way, adjustments may be made to the implementation of the QuietIE schedule to align the QuietIE schedule with such Bluetooth requests. As shown inFIG. 6 , if such alignment is successful, as may be determined atoperation 612, the second transceiver may be granted access to the transmission medium in accordance with such requests. - If such alignment is not successful,
method 600 may proceed tooperation 614 during which the second transceiver may be switched to a legacy coexistence technique. For example, the second transceiver may use CTS-to-Self frames or management frames to implement such coexistence, and such frames may be included with every transmission. - Returning to
operation 608, if it is determined that the QuietIE schedule cannot be aligned with a period of the transmission protocol of the second transceiver,method 600 may proceed tooperation 616 during which new QuietIE schedule may be generated. In various embodiments, this may include the generation of a QuietIE schedule request and/or the generation and distribution of a QuietIE schedule. In various embodiments, the QuietIE schedule may be generated based, at least in part, on features or characteristics of a transmission protocol of the second transceiver, such as a timing of requests issued in accordance with the transmission protocol of the second transceiver, such as Bluetooth requests. - If a QuietIE schedule is successfully generated, as determined in
operation 618,method 600 may proceed tooperation 606 during which the second transceiver may be granted access to the transmission medium based on requests issued by the second transceiver and based on the transmission protocol of the second transceiver. If a QuietIE schedule is not successfully generated, as determined inoperation 618,method 600 may proceed tooperation 614 during which the second transceiver may be switched to a legacy coexistence technique. - Returning to
operation 602, if a QuietIE schedule is not available,method 600 may proceed tooperation 616 as discussed above, and it may be determined if a QuietIE schedule may be generated. - Although the foregoing concepts have been described in some detail for purposes of clarity of understanding, it will be apparent that certain changes and modifications may be practiced within the scope of the appended claims. It should be noted that there are many alternative ways of implementing the processes, systems, and devices. Accordingly, the present examples are to be considered as illustrative and not restrictive.
Claims (20)
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/144,870 US10506622B1 (en) | 2018-06-27 | 2018-09-27 | Traffic coexistence for collocated transceivers including bluetooth transceivers |
CN201980040582.7A CN112335314B (en) | 2018-06-27 | 2019-05-08 | Method, device and system for realizing flow coexistence of collocated transceivers |
DE112019003241.0T DE112019003241T9 (en) | 2018-06-27 | 2019-05-08 | TRAFFIC COEXISTENCE FOR LOCAL COMBINED TRANSCEIVERS INCLUDING BLUETOOTH TRANSCEIVERS |
PCT/US2019/031376 WO2020005397A1 (en) | 2018-06-27 | 2019-05-08 | Traffic coexistence for collocated transceivers including bluetooth transceivers |
US16/675,748 US11039457B2 (en) | 2018-06-27 | 2019-11-06 | Traffic coexistence for collocated transceivers including bluetooth transceivers |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201862690714P | 2018-06-27 | 2018-06-27 | |
US16/144,870 US10506622B1 (en) | 2018-06-27 | 2018-09-27 | Traffic coexistence for collocated transceivers including bluetooth transceivers |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/675,748 Continuation US11039457B2 (en) | 2018-06-27 | 2019-11-06 | Traffic coexistence for collocated transceivers including bluetooth transceivers |
Publications (2)
Publication Number | Publication Date |
---|---|
US10506622B1 US10506622B1 (en) | 2019-12-10 |
US20200008213A1 true US20200008213A1 (en) | 2020-01-02 |
Family
ID=68766087
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/144,870 Active US10506622B1 (en) | 2018-06-27 | 2018-09-27 | Traffic coexistence for collocated transceivers including bluetooth transceivers |
US16/675,748 Active US11039457B2 (en) | 2018-06-27 | 2019-11-06 | Traffic coexistence for collocated transceivers including bluetooth transceivers |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/675,748 Active US11039457B2 (en) | 2018-06-27 | 2019-11-06 | Traffic coexistence for collocated transceivers including bluetooth transceivers |
Country Status (4)
Country | Link |
---|---|
US (2) | US10506622B1 (en) |
CN (1) | CN112335314B (en) |
DE (1) | DE112019003241T9 (en) |
WO (1) | WO2020005397A1 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN117375656A (en) * | 2022-06-27 | 2024-01-09 | 瑞昱半导体股份有限公司 | Electronic device, antenna control method and communication chip |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009543404A (en) * | 2006-06-27 | 2009-12-03 | エヌエックスピー ビー ヴィ | Scheduled coexistence environment |
ATE518391T1 (en) * | 2006-12-21 | 2011-08-15 | Nxp Bv | QUALITY OF SERVICE FOR WIFI AND BLUETOOTH COMBINATIONS |
PT2103042E (en) | 2007-01-11 | 2010-11-18 | Nds Ltd | Wireless networking system and method |
WO2008090509A2 (en) | 2007-01-26 | 2008-07-31 | Koninklijke Philips Electronics N.V. | Quiet period management in wirelses networks |
GB2490834B (en) * | 2008-02-06 | 2013-05-29 | Hmicro Inc | Wireless communications systems using multiple radios |
US8542620B2 (en) | 2009-05-05 | 2013-09-24 | Qualcomm Incorporated | Dynamic energy saving mechanism for access points |
GB2465650B (en) | 2009-07-27 | 2010-10-13 | Cambridge Silicon Radio Ltd | Wireless network protocol coexistence |
FR2949928A1 (en) | 2009-09-08 | 2011-03-11 | Thomson Licensing | TRANSMITTING METHOD IMPLEMENTED BY A NODE AND CORRESPONDING RECEIVING METHOD |
EP2636266B1 (en) | 2010-11-05 | 2021-09-15 | InterDigital Patent Holdings, Inc. | Silent period method and apparatus for dynamic spectrum management |
US8730990B2 (en) | 2011-09-15 | 2014-05-20 | Nokia Corporation | Method, apparatus, and computer program product for quiet period management in wireless networks for coexistence |
US20130225068A1 (en) | 2012-02-24 | 2013-08-29 | Nokia Corporation | Method, apparatus, and computer program product for coexistence-aware communication mechanism for multi-radios |
US9167622B2 (en) | 2012-05-23 | 2015-10-20 | Qualcomm Incorporated | Methods and a system of multiplexing multiple concurrent operational modes on a single physical transceiver by opportunistic time stealing |
KR20160009530A (en) | 2013-03-10 | 2016-01-26 | 엘지전자 주식회사 | Method for performing channel switch in network converging plurality of communication systems and apparatus for same |
GB2537553B (en) | 2014-01-28 | 2018-09-12 | Imagination Tech Ltd | Proximity detection |
US10555328B2 (en) * | 2017-02-17 | 2020-02-04 | Avago Technologies International Sales Pte. Limited | Scalable coexistence scheme for WLAN operation with multiple periodic BT connections |
-
2018
- 2018-09-27 US US16/144,870 patent/US10506622B1/en active Active
-
2019
- 2019-05-08 CN CN201980040582.7A patent/CN112335314B/en active Active
- 2019-05-08 WO PCT/US2019/031376 patent/WO2020005397A1/en active Application Filing
- 2019-05-08 DE DE112019003241.0T patent/DE112019003241T9/en not_active Ceased
- 2019-11-06 US US16/675,748 patent/US11039457B2/en active Active
Also Published As
Publication number | Publication date |
---|---|
DE112019003241T9 (en) | 2021-05-20 |
US10506622B1 (en) | 2019-12-10 |
DE112019003241T5 (en) | 2021-03-18 |
US11039457B2 (en) | 2021-06-15 |
US20200100266A1 (en) | 2020-03-26 |
CN112335314A (en) | 2021-02-05 |
CN112335314B (en) | 2022-02-08 |
WO2020005397A1 (en) | 2020-01-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11671918B2 (en) | Implementation of traffic coexistence for collocated transceivers including Bluetooth transceivers | |
JP5795023B2 (en) | Clustering management in millimeter-wave wireless systems | |
US10517071B2 (en) | Wireless communication device, wireless communication system, wireless communication method and program | |
US8886203B2 (en) | Dynamic channel reuse in multi-access communication systems | |
GB2501898A (en) | Simultaneous transmission of uplink and downlink data in a wireless network | |
EP3751936A1 (en) | Carrier set determination method and device, storage medium and electronic device | |
TW201032656A (en) | Method and apparatus of dynamic bandwidth management | |
US9661652B2 (en) | Efficient receiver yielding for distributed D2D communications | |
WO2018176324A1 (en) | Data exchange method, terminal device, and network device | |
US11039457B2 (en) | Traffic coexistence for collocated transceivers including bluetooth transceivers | |
JP5584209B2 (en) | Apparatus and method for transmitting / receiving a bicon signal | |
US20160036705A1 (en) | Method and device for configuring link in wireless lan system | |
US20110085505A1 (en) | Method for producing communication frame of body area network and communication network of body area network using the same | |
CN104066198A (en) | Method and system for selecting signal channel in wireless local area network | |
US20170289097A1 (en) | Multi-Radio Single Internet Protocol Address Wireless Local Area Network Apparatus and Method | |
US11617204B2 (en) | Channel scheduling for spatial reuse | |
US9907106B2 (en) | Device for multiple pan access | |
US11418222B2 (en) | Data transmission method and device for multi-radio frequency system, storage medium and terminal | |
US9277415B2 (en) | Resource sharing priority | |
US20040196817A1 (en) | Method and device for prefetching frames | |
US20230061086A1 (en) | Systems, methods, and devices for supplemental scanning in wireless networks | |
US20070104159A1 (en) | WLAN data reception method and WLAN device | |
US20230389074A1 (en) | Ultra-Wide Band Channel Access-Periodic Reservation | |
EP4287762A1 (en) | Ultra-wide band channel access-opportunistic reservation | |
KR20110040682A (en) | Method of producing a communication frame for body area network and method of communication for body area network by using the same |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: CYPRESS SEMICONDUCTOR CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KENCHARLA, RAGHAVENDRA;GUNDU RAO, RAJENDRA KUMAR;THOTA, SRI RAMYA;REEL/FRAME:047425/0688 Effective date: 20180926 |
|
AS | Assignment |
Owner name: MUFG UNION BANK, N.A., CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNOR:CYPRESS SEMICONDUCTOR CORPORATION;REEL/FRAME:049917/0093 Effective date: 20190731 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: SPANSION LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MUFG UNION BANK, N.A.;REEL/FRAME:059410/0438 Effective date: 20200416 Owner name: CYPRESS SEMICONDUCTOR CORPORATION, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:MUFG UNION BANK, N.A.;REEL/FRAME:059410/0438 Effective date: 20200416 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |