Wireless communication equipment and method for operating the wireless communication equipment

Abstract

A wireless device, comprising: a Bluetooth transceiver designed to transmit or receive Bluetooth signals with a peer Bluetooth transceiver; and a Bluetooth controller, trained to: Obtaining a Long-Term Evolution (LTE) signal transmit / receive pattern of an LTE transceiver; and based on the LTE signal transmit / receive pattern of the LTE transmit / receive device: based on a desensitization target, aligning the transmission of Bluetooth signals by the Bluetooth transceiver so that they occur within an uplink duration of the LTE transceiver, or based on a desensitization target, aligning the reception of Bluetooth signals by the Bluetooth transceiver so that they occur within a downlink duration of the LTE transceiver.

Description

Cross-reference to related application

[0001] This application claims the benefit of U.S. Provisional Application No. 61 / 618,906, filed April 2, 2012, the contents of which are incorporated herein by reference in their entirety for all purposes. Technical area

[0002] The present disclosure relates to wireless communication devices and methods of operating wireless communication devices. background

[0003] Mobile communications devices can support a variety of wireless access technologies, such as a cellular radio communication technology (LTE) (Long Term Evolution), a short-range radio communication technology (LTE) (e.g., Bluetooth or WLAN), or a metropolitan area system radio communication technology (WiMax). Although different frequency bands are typically allocated to different wireless access technologies, interference can still occur between them, for example, if a mobile communications device wishes to operate two different wireless technologies in parallel.

[0004] Publication EP2727430B1 shows that to mitigate of potential interference between radio access technologies (RATs) on a multi-RAT device, traffic scheduling rules may be implemented so that communications of the individual RATs are timed in a manner that reduces interference. For example, communications of a Bluetooth / WLAN RAT may be scheduled such that initial and responsive communications of the Bluetooth / WLAN RAT occur during sub-frames of an LTE RAT that are less likely to cause cross-RAT interference.

[0005] Publication EP3664318A1 shows that in a wireless communication device with multiple radio access technologies (RATs), frame timing for one RAT may be aligned with a frame timing of another RAT so as to reduce a number of communication frames of the different RATs that overlap in time with each other. PublicationWO2012099939A1 shows that, to improve performance in devices capable of communication using multiple radio access technologies (RATs), a gap pattern may be constructed in which a first RAT is quieted during certain times to allow for a second RAT to operate without interference.

[0006] Publication EP2666331A1 shows that, to improve performance in devices capable of communication using multiple radio access technologies (RATs), a gap pattern may be constructed in which a first RAT is quieted during certain times to allow for a second RAT to operate without interference. Gap patterns may be constructed based on timeline constraints, such as grant scheduling and HARQ performance, or based on desired performance levels of one or more of the RATs.

[0007] Avoiding such interference and improving coexistence between different wireless access technologies is desirable. Summary

[0008] This desire is satisfied by the subject matter defined in the independent patent claims. Further advantageous embodiments are the subject matter of the dependent claims. Short character description

[0009] In the drawings, like reference characters generally designate like parts throughout the different views. The drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention. In the following description, various embodiments of the invention are described with reference to the following drawings, in which: Fig. Figure 1 shows a communication system according to one aspect of the invention; Fig. 2 shows a frequency band diagram; Fig. 3 shows a test system; Fig. 4 shows the measurement results of the first test case; Fig. 5 modified measurement results for the first test case, for different broadband noise; Fig. 6 shows the measurement results of the second test case; Fig.7 shows modified measurement results for the second test case for different broadband noise; Fig. 8 shows the measurement results of the second test case; Fig. 9 shows modified measurement results of the second test case for different broadband noise; Fig. 10 shows a communication device according to various aspects of this disclosure; Fig. 11 shows a frame structure; Fig. 12 shows a data transfer diagram; Fig. 13 shows a transmission diagram; Fig. 14 shows a transmission diagram; Fig. 15 shows a transmission diagram; Fig. 16 and Fig. 17 show the impact of Wi-Fi and Bluetooth usage on LTE-FDD with full traffic connectivity support, relying only on LTE denial and LTE kill; Fig.18 shows a communication circuit according to one aspect of this disclosure; Fig. 19 shows a status & arbitration unit according to an aspect of this disclosure; Fig. 20 shows a transmission diagram; Fig. 21 shows a communication device; Fig. 22 shows a flow chart; Fig. 23 shows a transmission diagram; Fig. 24 shows a message flow diagram; Fig. 25 shows a frequency allocation table; Fig. 26 shows a message flow diagram; Fig. 27 shows a transmission diagram; Fig. 28 shows a transmission diagram; Fig. 29 shows a transmission diagram; Fig. 30 shows a transmission diagram; Fig. 31 shows a transmission diagram; Fig. 32 shows a transmission diagram; Fig.33 shows a transmission diagram; Fig. 34 shows a wireless communication device; Fig. 35 shows a wireless communication device; Fig. 36 shows a flow chart; Fig. 37 shows a flow chart; Fig. 38 shows a wireless communication device; Fig. 39 shows a flow chart; Fig. 40 shows a wireless communication device; Fig. 41 shows a flow chart; Fig. 42 shows a flowchart illustrating a process for BT / LTE coexistence; Fig. 43 shows a flowchart illustrating a process for BT / LTE coexistence; Fig. 44 shows a flowchart illustrating a process for WiFi / LTE coexistence; and Fig.45 shows a flowchart illustrating a process for WiFi / LTE coexistence. Description

[0010] In the following detailed description, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. These aspects of this disclosure are described in sufficient detail to enable those skilled in the art to practice the invention. It is understood that other embodiments may be utilized and structural, logical, or electrical changes may be made without departing from the scope of the present invention. The various features of this invention are not necessarily mutually exclusive, as some features of this invention may be combined with one or more other features of this invention to form new features.

[0011] 3GPP (3rd Generation Partnership Project) has introduced LTE (Long Term Evolution) as a standard in its version 8 of UMTS (Universal Mobile Telecommunication System).

[0012] The air interface of an LTE communication system is called E-UTRA (Evolved Universal Terrestrial Radio Access) and is commonly referenced as "3.9G." In December 2010, the ITU recognized that current versions of LTE and other developed 3G technologies do not meet "IMT-advanced" requirements and cannot be considered "4G," provided they represent predecessors to "IMT-advanced," with a substantial improvement in performance and capabilities relative to initial, already deployed "third-generation" systems. LTE is therefore sometimes referred to as "4G" (primarily for marketing reasons).

[0013] Compared to its predecessor, UMTS, LTE offers an air interface that has been further optimized for packet data transmission by improving system capacity and spectral efficiency. Among other improvements, the maximum net transmission rate has been significantly increased to 300 Mbps in the downlink transmission direction and 75 Mbps in the uplink transmission direction. LTE supports scalable bandwidths from 1.4 MHz to 20 MHz and is based on new multiple access methods, such as OFDMA (Orthogonal Frequency Division Multiple Access) / TDMA (Time Division Multiple Access) in the downlink direction (transmitter, e.g., base station, to handset, e.g., mobile device) and SC-FDMA (Single Carrier Frequency Division Multiple Access) / TDMA in the uplink direction (hands-free device to transmitter).OFDMA / TDMA is a multi-carrier multiple access method in which a subscriber (e.g., a mobile device) is provided with a defined number of subcarriers in a frequency spectrum and a defined transmission time for the purpose of data transmission. The RF (radio frequency) capability of a mobile device according to LTE (also referred to as user equipment (UE, e.g., a mobile phone) for transmitting and receiving has been set at 20 MHz. A physical resource block (PRB) is the basic unit for allocating the physical channels defined in LTE. It comprises a matrix of 12 subcarriers with 6 or 7 OFDMA / SC-FDMA symbols. At the physical layer, a pair of an OFDMA / SC-FDMA symbol and a subcarrier is referred to as a "resource element." A communication system used according to one aspect of this disclosure, which, for example,a communication system according to LTE is defined below with reference to . Fig. 1 described.

[0014] Fig. 1 shows a communication system 100 according to one aspect of this disclosure.

[0015] The communication system 100 is a cellular mobile communication system (hereinafter also referred to as a cellular wireless communication network) that includes a wireless access network (e.g., an E-UTRAN, Evolved UMTS (Universal Mobile Communication System) Terrestrial Radio Access Network according to LTE (Long Term Evolution)) 101 and a core network (e.g., an EBC, Evolved Packet Core, according to LTE) 102. The wireless access network 101 may include a base (transceiver) station (e.g., eNodeBs, eNBs, according to LTE) 103. Each base station 103 provides wireless coverage for one or more mobile radio cells 104 of the wireless access network 101.

[0016] A mobile device (also referred to as UE, user equipment) 105 located in a cellular radio cell 104 can communicate with the core network 102 and with other mobile devices 105 via the base station that provides coverage in the cellular cell (in other words, is in operation). In other words, the base station 103 operating the cellular cell 104 in which the mobile device 105 is located provides the E-UTRA user plane termination, including the PDCP (Package Data Convergence Protocol) layer, the RLC (Radio Link Control) layer, and the MAC (Medium Access Control) layer, and control plane termination, including the RRC (Radio Resource Control) layer, toward the mobile device 105.

[0017] Control and user data are transmitted between a base station 103 and a mobile device 105 located in the mobile radio cell 104 operated by the base station 103 via the air interface 106, based on multiple access methods.

[0018] The base stations 103 are interconnected via a first interface 107, e.g., an X2 interface. The base stations 103 are also connected via a second interface 108, e.g., an S1 interface, to the core network, e.g., an MME (Mobility Management Entity) 109 via an S1-MME interface, and to a serving gateway (S-GW) 110 via an S1-U interface. The S1 interface supports multiple-to-multiple relationships between MMEs / S-GWs 109, 110 and the base stations 103, i.e., a base station 103 can be connected to more than one MME / S-GW 109, 110, and an MME / S-GW 109, 110 can be connected to more than one base station 103. This enables network sharing in LTE.

[0019] For example, the MME 109 may be responsible for controlling the mobility of mobile devices located within the E-UTRAN coverage area, while the S-GW 110 is responsible for handling the transmission of user data between mobile devices 105 and the core network 102.

[0020] In the case of LTE, the wireless access network 101, i.e. the E-UTRAN 101 in the case of LTE, can be considered as consisting of the base station 103, i.e. the eNBs 103 in the case of LTE, which provide the E-UTRA user plane (PDCP / RLC / MAC) and control plane (RRC) protocol termination towards the UE 105.

[0021] An eNB 103 can, for example, provide the following functions: • Radio resource management functions: radio bearer control, radio access control, link mobility control, dynamic allocation of resources to UEs 105 in uplink and downlink (scheduling); • IP header compression and encryption of user data streams; • Selection of an MME 109 attachment to UE 105 if no routing to an MME 109 can be determined from the information provided by UE 105; • Routing of user-plane data towards the Serving Gateway (S-GW) 110; • Scheduling and transmission or sending of paging messages (originating from the MME); • Planning and transmission of broadcast information (originating from MME 109 or O&M (Operation and Maintenance)); • Measurement and configuration of measurement reports for mobility and planning; • Planning and transmission of PWS (Public Warning System), including ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Alert System) messages (originating from the MME 109); • CSG (Closed subscriber group) handling.

[0022] Each base station of the communication system 100 controls communication within its geographical coverage area, namely its mobile radio cell 104, which ideally has a hexagonal shape. When the mobile device 105 is located in the mobile radio cell 104 and camped in the mobile radio cell 104 (in other words, it is registered at the mobile radio cell 104), it communicates with the base station 103 that controls the mobile radio cell 104. When a call is initiated by a user of the mobile device 105 (mobile outgoing call) or a call is addressed to the mobile device 105 (mobile incoming call), radio channels are established between the mobile device 105 and the base station 103 that controls the mobile radio cell 104 and in which the mobile device is located (and in which it is camped).If the mobile device 105 moves away from the original mobile radio cell 104 in which the call was established, and the signal strength of the radio channel that has developed in the original mobile radio cell 104 decreases, the communication system can initiate a transfer of the call to radio channels of another mobile radio cell 104 to which the mobile device 105 moves.

[0023] As mobile device 105 continuously moves through the coverage area of ​​communication system 100, control of the call may be transferred between neighboring cellular cells 104. The transfer of a call from one cellular cell 104 to another is referred to as a handover or handoff.

[0024] In addition to communication via the E-UTRAN 102, the mobile device 105 may support communication via a Bluetooth (BT) communication link 111, e.g., to another mobile device 112, and communication via a WLAN communication link 113 to a WLAN access point (AP) 114. Via the access point 114, the mobile device may gain access to a communication network 115 (e.g., the Internet), which may be connected to the core network 102.

[0025] LTE operates in a newly allocated set of frequency bands. The main difference with the introduction of this new set of bands compared to those used for 2G / 3G communication systems is that two of them are in the immediate vicinity of the ISM band used by Wi-Fi and Bluetooth.

[0026] This is in Fig. 2 shown.

[0027] Fig. 2 shows a frequency band diagram 200.

[0028] In the band diagram 200 frequencies are shown from left to right.

[0029] From left to right, LTE band 40 201, ISM band 202, LTE band 7 UL (uplink) and a guard band 204, LTE band 38 205, and LTE band 7 DL (downlink) 206 are shown. The band diagram 200 thus illustrates the spectrum allocated to LTE around ISM band 202.

[0030] LTE band 40 201, used by LTE-TDD (Time Division Duplex), is immediately adjacent to the lower band of ISM band 202 without any guard band in between, and LTE band 7 204, used for LTE-FDD (Frequency Division Duplex) UL, is immediately adjacent to the higher band of ISM band 202 with the guard band 203 of 17 MHz.

[0031] To illustrate the coexistence issues (in this case between LTE), the following are results from real-world measurements conducted with current or common hardware. The three test cases for which the results are presented are: 1: Wi-Fi affects band 40; 2: LTE band 40 interferes with Wi-Fi in the ISM band; 3: LTE band 7 interferes with Wi-Fi in the ISM band.

[0032] The test system used is in Fig. 3 shown.

[0033] Fig. 3 shows a test system 300.

[0034] The test system 300 includes a first communication circuit 301, which supports (among other things) Wi-Fi and Bluetooth, and a second communication circuit 302, which supports (among other things) LTE communication. Various filters 303, 304, 305, and 306 are provided for testing.

[0035] An arrow 307 indicates the coexistence case of interest, in this example (WLAN / LTE coexistence). Note that in the measurements, the RF (radio frequency) analysis was focused on interference via antennas and not on pin-to-pin interference at the IC level.

[0036] In the first test case, LTE band 40 201 is the receiver (or interference victim) and ISM band 202 is the interferer.

[0037] Fig. 4 shows the measurement results for the first test case.

[0038] Fig. Figure 5 shows modified measurement results for the first test case for different broadband noise.

[0039] From the first test case, it can be seen that using the lower part of the ISM band desensitizes the entire band 40.

[0040] In the second test case, LTE band 40 201 is the interferer and ISM band 202 is the receiver (or interference victim).

[0041] Fig. 6 shows the measurement results for the second test case.

[0042] Fig. Figure 7 shows modified measurement results for the second test case for different broadband noise.

[0043] From the second test case, it can be seen that using the upper part of band 40 desensitizes the entire ISM band. Approximately 75% of the frequency combinations have more than 10 dB of desensitization.

[0044] In the third test case, LTE band 7 UL 204 is the interferer and ISM band 202 is the receiver (or frequency victim).

[0045] Fig. 8 shows the measurement results of the second test case.

[0046] Fig. Figure 9 shows modified measurement results of the third test case with different broadband noise.

[0047] From the third test case, it can be seen that even with a narrowband WLAN filter, there is a strong desensitization at the frequency 2510 MHz.

[0048] The test results show that severe coexistence problems occur with the existing hardware in all three test cases.

[0049] According to various aspects of this disclosure, these open points are solved or mitigated by using a mechanism applied at the PHY layer and protocol layer, and relying, for example, on a mix of software (SW) and hardware (HW) implementations.

[0050] The examples below are based on an exemplary communication device used in Fig. 10 is described.

[0051] Fig. 10 shows a communication device 1000 according to various aspects of the invention.

[0052] The communication device 1000 is, for example, a mobile radio communication device configured or designed according to LTE and / or other 3GPP mobile radio communication technologies. The communication device 1000 is also referred to as a wireless communication device.

[0053] According to various aspects of the invention, the communication device 1000 may include a processor 1002, such as a microprocessor (e.g., a central processing unit (CPU)) or another type of programmable logic device (acting, for example, as a controller). Furthermore, the communication device 1000 may include a first memory 1004, for example, a read-only memory (ROM) 1004 and / or a second memory 1006, for example, a random access memory (RAM) 1006.Furthermore, the communication device 1000 may include a display 1008, such as a touch-sensitive display, for example, a liquid crystal display (LCD) display, a light-emitting diode (LED) display, or an organic light-emitting diode (OLED) display. However, any other type of display may also be provided for the display 1008. The communication device 1000 may additionally include any other suitable output device (not shown), such as a speaker or a vibration actuator. The communication device 1000 may include one or more input devices, such as a keypad 1010 including a plurality of keys.The communication device may additionally include any other suitable input device (not shown), such as a microphone, for example, for voice control of the communication device 1000. In the event that the display 1008 is implemented as a touch-sensitive display 1008, the keypad 1010 may be implemented by the touch-sensitive display 1008. Furthermore, the communication device 1000 may optionally include a coprocessor 1012 to offload computing load from the processor 1002. Furthermore, the communication device 1000 may include a first transceiver 1014 and a second transceiver 1018. The first transceiver 1014 is, for example, an LTE transceiver that supports wireless communication according to LTE, and the second transistor 1018 is, for example, a WLAN transceiver that supports communication according to a WLAN communication standard, or a Bluetooth transceiver that supports communication according to Bluetooth.

[0054] The components described above can be connected to one another via one or more lines, e.g., implemented in the form of a bus 1016. The first memory 1004 and / or the second memory 1006 can be a volatile memory, e.g., a DRAM (Dynamic Random Access Memory), or a non-volatile memory, e.g., a PROM (Programmable Read Only Memory), an EPROM (Erasable PROM), an EEPROM (Electrically Erasable PROM), or a flash memory, e.g.,a floating gate memory, a charge trapping memory, an MRAM (magnetic resistive random access memory), a PCRAM (phase change random access memory), or a CBRAM (conductive bridging random access memory). The program code used to execute and thus control the processor 1002 (and the optional co-processor 1012) may be stored in the first memory 1004. Data (e.g., messages received or to be sent by the first transceiver 1014) processed by the processor 1002 (and optional co-processor 1012) may be stored in the second memory 1006. The first transceiver 1014 may be configured or designed to implement a Uu interface according to LTE.The communication device 1000 and the first transceiver 1014 may also be configured to provide MIMO radio transmission.

[0055] Furthermore, the communication device 1000 may have an image and / or video camera 1020 that is configured to provide a video conference via the communication device 1000.

[0056] In addition, the communication device 1000 may include a Subscriber Identity Module (SIM), e.g., a UMTS Subscriber Identity Module (USIM), for identifying a user and a subscriber of the communication device 1000. The processor 1002 may also include audio processing circuitry, such as audio decoding circuitry and / or audio coding circuitry configured to decode and / or encode audio signals according to one or more of the following audio coding or audio decoding technologies: ITU G.711, Adaptive Multi-Rate Narrowband (AMR-NB), Adaptive Multi-Rate Wideband (AMR-WB), Advanced Multi-Band Excitation (AMBE), etc.

[0057] It should be noted that although most of the examples described below are for the coexistence of LTE and WLAN or Bluetooth, the first transceiver 1014 and the second transceiver 1018 may also support other communication technologies.

[0058] For example, each of the transceivers 1014, 1018 can support one of the following communication technologies: - a short-range radio communication technology (which may include, for example, a Bluetooth wireless communication technology, an Ultra Wide Band (UWB) wireless communication technology, and / or a wireless local area network (WLAN) communication technology (e.g., according to an IEEE 802.11 (e.g., IEEE 802.11n) wireless communication standard), IrDA (Infrared Data Association), Z-Wave and ZigBee, HiperLAN / 2 (HIgh Performance Radio LAN; an alternative ATM-like 5 GHz standardized technology), IEEE 802.11a (5 GHz), IEEE 802.11g (2.4 GHz), IEEE 802.11n, IEEE 802.11VHT (VHT = Very High Throughput)), - a Metropolitan Area System wireless communication technology (which may include, for example, Worldwide Interoperability for Microwave Access (WiMax) (e.g., according to an IEEE 802.16 wireless communication standard, e.g., WiMax fixed or WiMax mobile), WiPro, HiperMAN (High Performance Radio Metropolitan Area Network) and / or IEEE 802.16m Advanced Air Interface), - a cellular wireless wide area communication technology (which may include, for example, a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology; and / or a Third Generation Partnership Project (3GPP) radio communication technology (e.g. (Universal Mobile Telecommunications System), FOMA (Freedom of Multimedia Access), 3GPP LTE (Long Term Evolution), 3GPP LTE Advance (Long Term Evolution Advance)), CDMA2000 (Code Division Multiple Access, EnglishCode Division Multiple Access 2000), CDPD (Cellular Digital Packet Data), Mobitex, 3G (3rd Generation), CSD (Circuit Switched Data), HSCSD (High-Speed ​​Circuit-Switched Data), UMTS (3G) (Universal Mobile Telecommunications System (3rd Generation)), W-CDMA (UMTS) (Wideband Code Division Multiple Access (Universal Mobile Telecommunications System)), HSPA (High Speed ​​Packet Access), HSDPA (High-Speed ​​Downlink Packet Access), HSUPA (High-Speed ​​Uplink Packet Access), HSPA+ (High-Speed ​​Packet Access Plus)High Speed ​​Packet Access Plus), UMTS-TDD (Universal Mobile Telecommunications System - Time-Division Duplex), TD-CDMA (Time Division Code Division Multiple Access), TD-CDMA (Time Division Synchronous Code Division Multiple Access), 3GPP Rel. 8 (Pre-4G) (3rd Generation Partnership Project Release 8 (Pre-4th Generation)), UTRA (UMTS Terrestrial Radio Access), E-UTRA (Evolved UMTS Terrestrial Radio Access), LTE Advanced (4G) (Long Term Evolution Advanced (4th Generation)), cdmaOne (2G), CDMA2000 (3G) (Code Division Multiple Access 2000 (Third Generation)), EV-DO (Data Optimized or Evolution-Only Data, English Evolution-Data Optimized or Evolution-Data Only), AMPS (1G) (Improved Mobile Phone System, English Advanced Mobile Phone System (First Generation, English).1st Generation)), TACS / ETACS (Total Access Communication System / Extended Total Access Communication System), D-AMPS (2G) (Digital AMPS (2nd Generation)), PTT (Push-to-talk), MTS (Mobile Telephone System), IMTS (Improved Mobile Telephone System), AMTS (Advanced Mobile Telephone System), OLT (Norwegian for Public Land Mobile Telephony), MTD (Swedish abbreviation for Mobile telephony system D), Autotel / PALM (Public Automated Land Mobile), ARP (Finnish for Autoradiopuhelin, wireless car phone “car radio phone”), NMT (Nordic Mobile Telephony), Hicap (High Performance Version, English.High capacity version of NTT (Nippon Telegraph and Telephone)), CDPD (Cellular Digital Packet Data), Mobitex, DataTAC, iDEN (Integrated Digital Enhanced Network), PDC (Personal Digital Cellular), CSD (Circuit Switched Data), PHS (Personal Handyphone System), WiDEN (Wideband Integrated Digital Enhanced Network), iBurst, Unlicensed Mobile Access (UMA, also referred to as 3GPP Generic Access Network, or GAN standard).

[0059] A short-range wireless communication technology may include the following short-range communication technology subfamilies: - personal area networks (Wireless PANs) Wireless communication subfamily which may include, for example, IrDA (Infrared Data Association), Bluetooth, UWB, Z-Wave and ZigBee; and - wireless local area networks (WLANs) Wireless communications subfamily, which may include, for example, HiperLAN / 2 (HIgh PErformance Radio LAN; an alternative ATM-like 5 GHz standardized technology), IEEE 802.11a (5 GHz), IEEE 802.11g (2.4 GHz), IEEE 802.11n, IEEE 802.11VHT (VHT = Very High Throughput).

[0060] A Wireless Metropolitan Area System communication technology family may include the following Wireless Metropolitan Area System communication technology subfamilies: - Wireless campus area networks (W-CANs) are a wireless communications subfamily that can be considered a form of metropolitan area network, specifically in academic environments, and can include WiMAX, WiPro, HiperMAN (High Performance Radio Metropolitan Area Network), or IEEE 802.16m Advanced Air Interface; and - Wireless metropolitan area networks (W-MANs) A wireless communications subfamily that may be limited to a room, building, campus, or specific metropolitan area (e.g., a city) and may include, for example, WiMAX, WiPro, HiperMAN (High Performance Radio Metropolitan Area Network), or IEEE 802.16m Advanced Air Interface.

[0061] Cellular wireless wide area communication technologies can also be considered as wireless wide area network (wireless WAN) wireless communication technology.

[0062] In the following examples, it is assumed that the first transceiver 1014 supports LTE communication and therefore operates in the LTE frequency bands 201, 204, 205, and 206. Accordingly, the first transceiver 1014 is also referred to as LTE-RF.

[0063] For the following examples, it is further assumed that the second transceiver 1018 operates in the ISM band 212 and supports WLAN communication or Bluetooth communication.

[0064] The first transceiver 1014 includes a first communication circuit 1022 that can perform various tasks related to the communication performed by the first transceiver 1014, such as controlling the timing of transmission / reception, etc. The first communication circuit 1022 can be understood as a (first) processor of the communication device 1000 and is configured, for example, to control the first transceiver 1014.

[0065] The second transceiver 1018 similarly includes a second communication circuit 1024 that can perform various tasks related to the communication performed by the second transceiver 1018, such as controlling the timing of transmission / reception, etc. The second transceiver 1018 is also referred to as a connectivity system or CWS. The second communication circuit 1024 is also referred to as a CWS chip or connectivity chip. The second communication circuit 1024 can be considered a (second) processor of the communication device 1000 and is configured, for example, to control the second transceiver 1018.

[0066] Each of the first transceivers 1014 and the second transceivers 1018 may also include front-end components (filters, amplifiers, etc.), and one or more antennas.

[0067] The first communication circuit 1022 may include a first real-time (RT) interface 1026 and a first non-real-time (NRT) interface 1028. Similarly, the second communication circuit 1024 may include a second RT interface 1030 and a second NRT interface 1032. These interfaces 1026 and 1032 are described in detail below and may be used to exchange control information related to other components of the communication device 1000. The RT interfaces 1026, 1030 may, for example, form an RT interface between the first communication circuit 1022 and the second communication circuit 1024. Similarly, the NRT interfaces 1028, 1032 may form an NRT interface between the first communication circuit 1022 and the second communication circuit 1024.

[0068] It should be noted that a "circuit" can be any type of logic-implementing unit, which can be a special-purpose circuit or a processor executing software stored in memory, firmware, or any combination thereof. Consequently, a "circuit" can be a wired logic circuit or a programmable logic circuit, such as a programmable processor, e.g., a microprocessor (e.g., a Complex Instruction Set Computer (CISC) processor or a Reduced Instruction Set Computer (RISC) processor). A circuit can also be a processor executing software, e.g., any type of computer program, e.g., a computer program executing virtual machine code such as Java.Other types of implementations of the corresponding functions, which are described in more detail below, may also be understood as circuitry according to aspects of this disclosure. RT coexistence mechanism

[0069] According to one aspect of this disclosure, a real-time coexistence architecture is provided which relies on two methods (or at least one of these methods), namely protocol synchronization and traffic arbitration.

[0070] Protocol synchronization may, for example, comprise two mechanisms: exploiting the available period in which LTE RF 1014 is idle and organizing the RF activity of the connectivity system 1018 such that RX (i.e., receive) periods occur simultaneously with LTE RX periods and TX (i.e., transmit) periods occur simultaneously with LTE TX periods. Protocol synchronization can be achieved through the use of LTE frame indication and LTE gap indication signals, which allow the second transceiver 1018 (WLAN or BT) to schedule its activities at appropriate times: ie, when the LTE RF 1014 is idle or when the corresponding activities are compatible (ie, so that the first transceiver 1014 and the second transceiver 1018 are receiving or so that the first transceiver 1018 and the second transceiver 1018 are transmitting).

[0071] Traffic arbitration may consist of receiving the advance activity indication from the CWS 1018 and the advance activity from the LTE RF 1014 and selecting the traffic to be allowed to process when a conflict is identified. Traffic arbitration may be achieved by a CWS activity indication, which is used by an RT (real-time) arbiter to generate a CWS kill and an LTE kill signal (to "delete" a frame or subframe for a communication technology, i.e., to prevent transmission in the communication technology in the subframe or frame).

[0072] The following describes an LTE frame indication in the LTE-TDD case (i.e., in the case that the LTE-RF 1014 is operated in the TDD mode of operation) used for protocol synchronization according to one aspect of this disclosure.

[0073] In a Time Division Duplex system (TD), LTE-TDD has a unique frame structure that includes both a DL and UL subframe. This is in Fig. 11 shown.

[0074] Fig. 11 shows a frame structure 1100.

[0075] The frame structure 1100 illustrates an LTE-TDD frame 1101 comprising DL subframes, ie subframes allocated for downlink transmissions (in which LTE-RF 1024 receives data), UL subframes, ie subframes allocated for uplink transmissions (in which LTE-RS 1028 sends data), and special (S) subframes, which can be used, for example, as guard time and pilot transmission.

[0076] There are a set of seven possible configurations defined in 3GPP for TDD. Whichever configuration is selected, the TDD frame structure contains a periodic DL / UL pattern that can be communicated to the CWS chip 1024 and used by the connectivity system 1018 to schedule communication traffic.

[0077] The LTE-TDD frame structure is typically static or varies very rarely. It can be indicated to the CWS chip 1028 via an NRT message over an NRT interface 1032. The required synchronization between the CWS chip 1028 and the timing alignment with the LTE-TDD frame can be performed over the RT interfaces 1026, 1030 using an LTE Frame_SYNC signal 1102, as shown in Fig. 11 shown.

[0078] The LTE frame start (ie, the beginning of each frame 1001) is indicated one millisecond in advance to the CWS chip 1024 via the pulse sent 1 ms in advance via the RT interface between the first communication circuit 1022 and the second communication circuit 1024 (ie, via the RT interfaces 1026, 1030).

[0079] By using the LTE frame SYNC signal coupled to the LTE frame structure, signaled via an NRT message, the CWS chip 1024 has full knowledge of the LTE-TDD frame and can plan its communication activities accordingly.

[0080] This LTE-TDD frame structure signaling message over the NRT (coexistence) interface between the first communication circuit 1022 and the second communication circuit 1024 (formed by NRT interfaces 1028, 1032) has, for example, the format shown in Table 1. Table 1 ID News payload Info Bits I / O Description 11 LTE BITMAP 10x2 O 0=Special subframe 1=RX LTE subframe 2= ​​TX LTE subframe

[0081] This message can be reduced to 3 bits (only 7 configurations) and an encoding of the S subframe structure can be added: • the seven UL / DL TDD frame configurations as defined in 3GPP: 3 bits • the nine special subframe configurations: 4 bits

[0082] Considering that the message is an NRT message and using an implicit LTE configuration encoding will require some LTE knowledge on the connectivity chip 1024, it may be desirable to stick with the explicit 20-bit encoding.

[0083] For LTE frame indication in the LTE FDD (Frequency Division Duplex) case, LTE Band 7 UL 204 is the most relevant band. This is an uplink band, and thus all subframes are UL subframes. Nevertheless, an LTE frame indication can also be used in this case to allow the CWS chip 1024 to properly schedule its activity at the LTE subframe boundaries. It can also be used by the CWS chip 1024 to synchronize its system clock with the LTE system clock.

[0084] If (traffic) arbitration gives a medium access to the CWS 1018, this can by definition continue until the end of the erased LTE subframe, and the CWS 1018, knowing the subframe boundaries, is able to apply scheduling to maximize the amount of traffic transmitted until the end of the erased (LTE subframe).

[0085] The following describes an LTE gap indication in case of LTE-FDD discontinuous reception (DRX) and discontinuous transmission (DTX), which is used for protocol synchronization according to one aspect of this disclosure.

[0086] LTE was designed to address the needs of mobile internet access. Internet traffic can be characterized by high bursts with high peak data rates and long signal-free periods or long periods of silence. An LTE system allows DRX (discontinuous reception) to enable battery savings. Two DRX profiles are supported, addressed by short DRX and long DRX. An LTE system allows discontinuous transmission (DTX) to increase system capacity for the reverse link, i.e., the uplink.

[0087] For example, isochronous traffic can be assumed for VoLTE (Voice over LTE). Because the speech encoder generates a packet every 20 ms, the underlying periodicity of LTE traffic can be exploited for Wi-Fi and BT transmissions during LTE idle periods and LTE signal-free periods, respectively.

[0088] For example, the UL / DL planning for an inactivity period of two (the smallest allowed value in 3GPP Release 9 for DRX inactivity times is 1) is in Fig. 12 shown.

[0089] Fig. 12 shows a data transfer diagram 1200.

[0090] In the data transmission diagram 1200, time increases from left to right. The data transmission diagram 1200 shows uplink LTE data transmission 1201, downlink LTE data transmission 1202, and a bottom timeline 1203 illustrating the time (in units of subframes) available for the CWS 1024 during the DRX periods 1207.

[0091] A first hatching 1204 shows periods available to the CWS 1024 (e.g., BT or WLAN), a second hatching 1203 shows the periods available to the CWS 1024, and a third hatching 1206 shows the periods usable by the CWS 1024.

[0092] The lowest time line 1203 marks the periods (by the first hatching 1204 and the second hatching 1205) during which no LTE-UL activity is expected and can thus be transmitted to the CWS 1024. Note that the interference-free period must be communicated to the LTE transceiver 1022 (especially in its role as a receiver) before the impending reception, for determining the AGC (Automatic Gain Control) and potentially reacquiring the signal. For short LTE-DRX periods, the period is approximately 300 µs; for long DRX periods, it is less than 1.3 ms.

[0093] The LTE standard also provides a mechanism called semi-persistent scheduling (SPS) to reduce signaling overhead in the case of isochronous transmission. In this case, UL authorization is implicitly granted by the SPS scheduling, and the DRX period can start immediately after receiving the specified or scheduled TTI (Transmission Time Interval).

[0094] The following describes an RT algorithm for LTE-FDD gap indication or LTE-FDD gap display, which is used for protocol synchronization according to one aspect of this invention.

[0095] An LTE transmission gap can be generated at any time by the communication device 1000, following the decision rules applicable in the network. According to one aspect of the present disclosure, the beginnings and ends of this transmission are indicated to the CWS 1024 so that the CWS 1024 can schedule its data traffic within the transmission gap (e.g., in the case where the CWS 1024 is performing a WLAN communication or a Bluetooth communication using an ACL (Asynchronous Connectionless Link)-based profile).

[0096] In 3 GPP version 9, there are three possible root causes to create a transmission gap: measurement gap, DRX / DTX and autonomous measurement gap.

[0097] A measurement (transmission) gap is known 34 ms or 74 ms in advance at the LTE-L1 level or LTE-L1 layer, respectively, and is 6 ms long. A DRX / DTX (transmission) gap in a subframe is known after decoding the PDCCH (Packed Data Control Channel) of the previous subframe, i.e., much less than 1 ms in advance (e.g., approximately 200 µs). However, in an ad-hoc operating mode, a transmission gap decision can be rejected up to 1.5 ms before the start of the transmission gap.

[0098] LTE gap signaling according to one aspect of this disclosure is described in Fig. 13 illustrates.

[0099] Fig. 13 shows a transmission diagram 1300.

[0100] The transmission diagram 1300 shows an uplink LTE data transmission 1301, a downlink LTE data transmission 1302, an uplink transmission gap signaling 1303, and a downlink transmission gap signaling 1304. Time increases from left to right.

[0101] In this example, there is an uplink transmission gap 1305 and a downlink transmission gap 1306. The uplink transmission gap 1305 is signaled by an uplink transmission gap signal 1307 (UL gap enveloping signal), and the downlink transmission gap 1306 is signaled by a downlink transmission gap signal 1308 (DL gap enveloping signal). The start and end of the transmission gap 1305, 1306 are indicated to the CBS chip 1204, for example, one second in advance by the uplink transmission gap signal 1307 and the downlink transmission gap signal 1308, and for example, via the RT interface between the first communication circuit 1022 and the second communication circuit 1024.

[0102] It should be noted that under 3GPP Version 11 - working title "In Device Coexistence," newly defined transmission gaps triggered specifically for coexistence purposes may be introduced. Transmission gap signaling according to one aspect of this disclosure is in accordance with these new transmission gaps.

[0103] In practice, the timing advance of the DL gap enveloping signal 1308 remains short because the decision for a transmission gap can only be made during the last DL subframe before the DL transmission gap and can only be performed when the PDCCH is decoded. For the UL transmission gap, the decision is also based on the DL subframe decoding, but there is a delay of approximately 4 ms between DL and UL subframes. Additionally, the UL transmission gap decision can be rejected before it is applied, up to 1.5 ms before the transmission gap starts. Rejection requests after this time, if any, are not applied. Thus, the UL transmission gap start can be signaled 1 ms in advance (< 1.5 ms). Similarly, a transmission gap end can be signaled a maximum of 1 ms in advance, since a higher value cannot be applied for a 1 ms UL transmission gap (1 subframe).According to one aspect of the present disclosure, a 1 ms advance signaling is maintained for the LTE transmission gap end signaling as the maximum of the advance facilitated traffic planning on the CWS 1018 side.

[0104] As in Fig. 13, the advance values ​​are, for example, 300 µs for tadv3, 1.5 ms for tadv4, and 1 ms for tadv1 and tadv2.

[0105] It should be noted that optimal signaling for a transmission gap can be achieved by displaying the transmission gap start and the transmission gap duration.

[0106] It should also be noted that protocol synchronization can also be used for LTE-TDD discontinuous reception (DRX) and discontinuous transmission (DTX).

[0107] The arbitration for the LTE-TDD case is described below.

[0108] Due to LTE resource usage and WLAN / BT protocol requirements, perfect protocol synchronization on each side and applying only concurrent RX and concurrent TX may not be sufficient to support the use case, and some colliding RX / TX events may occur.

[0109] Fig. 14 and Fig. 15 illustrate conflicts or collisions between LTE-TDD operation and WLAN / BT operation that can occur.

[0110] Fig. 14 shows a transmission diagram 1400.

[0111] The transmission diagram 1400 illustrates the occurrence of transmit and receive conflicts or collisions in the case of synchronized LTE-TDD and WLAN traffic.

[0112] For all three timelines 1401, 1402, 1403, WLAN downlink transmissions are shown above and WLAN uplink transmissions are shown below the timelines 1401, 1402, 1403, with time increasing from left to right and, for example, from top to bottom along the timelines 1401, 1402, 1403. Furthermore, LTE transmissions (or LTE subframe allocations) 1404, 1405, 1406 are shown for the timelines 1401, 1402, 1403.

[0113] A hatch 1407 shows RX / TX conflicts that can occur between WLAN transmissions and LTE transmissions.

[0114] Fig. 15 shows a transmission diagram 1500.

[0115] The transmission diagram 1500 illustrates the occurrence of UL-DL conflicts in the case of synchronized LTE-TDD and Bluetooth traffic.

[0116] For each of the three timelines 1501, 1502, 1503, Bluetooth data transmission is shown above, and Bluetooth data reception is shown below timelines 1501, 1502, 1503, with time increasing from left to right for each of timelines 1501, 1502, 1503. Also shown are LTE transmissions (or LTE subframe allocations) 1504, 1505, 1506 for timelines 1501, 1502, 1503.

[0117] A hatch 1507 shows UL / DL conflicts that can occur between Bluetooth transmissions and LTE transmissions.

[0118] RX / TX conflicts can be handled through arbitration, which potentially leads to LTE subframe losses. Arbitration can be performed between WLAN / BT and LTE to determine whether WLAN / BT traffic is allowed or denied.

[0119] For example, if a WLAN / BT transmission event (by the second transceiver 1018) conflicts with an LTE-DL subframe (i.e., a scheduled reception by the first transceiver 1014), real-time arbitration is performed. The arbitration process decides whether to either discard a WLAN / BT transmission to protect the LTE-DL subframe or allow it to proceed. In the latter case, depending on the RS interference level, the LTE-DL subframe is likely not to be decoded by the LTE-PHY, i.e., the LTE physical layer (implemented by components of the first transceiver 1014).

[0120] In the LTE-UL case, an arbitration decision may consist of allowing a WLAN / BT reception or allowing an LTE-UL subframe (i.e., an LTE transmission). Fig. 14 and Fig.Figure 15 can be viewed as illustrating the impact of a WLAN and Bluetooth use case over LTE-TDD for full connectivity traffic support (i.e., support through communication via the second transceiver 1018) that relies only on LTE denial and LTE desensitization. This determines the worst case for the LTE-TDD side and can be used as a reference to quantify the improvements provided by the coexistence mechanism for LTE-TDD.

[0121] RT arbitration may be a unit implemented by a combination of hardware and software located in the LTE subsystem (e.g., in the first transceiver 1014) that performs the synchronization of the first transceiver 1014 and the second transceiver 1018 via the real-time (coexistence) interface between the first transceiver 1014 and the second transceiver 1018 (which is formed by the RT interface 1026, 1030), for example, in the context given by an NRT arbitration decision. This results in RT arbitration, and this is applied to the first transceiver 1014 and the second transceiver 1018 (via the RT coexistence interface).

[0122] For LTE-FDD, the interfering band is a UL band. LTE-UL cannot be compromised by CWS, and thus the role of arbitration is reduced to protecting or not protecting WLAN / BT RX from LTE TX. If a conflict occurs, i.e., as a consequence of misscheduling or insufficient medium access for connectivity traffic, arbitration can be applied. This results in either the LTE-UL subframe being dropped or being executed as normal.

[0123] Fig. 16 and Fig. Figure 17 shows the impact of a Wi-Fi and Bluetooth use case over LTE-FDD for full connectivity traffic support, relying only on LTE denial and LTE kill. This determines the worst case for the LTE-FDD side and can be used as a reference to quantify the improvement provided by the coexistence mechanism for LTE-FDD.

[0124] Fig. 16 shows a transmission diagram 1600.

[0125] The transmission diagram 1600 illustrates the occurrence of transmission-reception conflicts in the case of synchronized LTE-FDD and WLAN traffic.

[0126] Wi-Fi downlink transmissions are shown above all four timelines 1601, 1602, 1603, and 1604, and Wi-Fi uplink transmissions are shown below timelines 1601, 1602, 1603, and 1604, with time increasing from left to right. Additional LTE transmissions (or LTE subframe allocations) 1605, 1606, 1607, and 1608 are shown for timelines 1601, 1602, 1603, and 1604.

[0127] A hatch 1609 indicates RX / TX conflicts that may occur between WLAN transmissions and LTE transmissions.

[0128] Fig. 17 shows a transmission diagram 1700.

[0129] The transmission diagram 1700 illustrates the occurrence of UL-DL conflicts in the case of synchronized LTE-FDD and Bluetooth traffic.

[0130] A Bluetooth data transmission is shown above each of the three timelines 1701, 1702, 1703, and a Bluetooth data reception is shown below timelines 1701, 1702, 1703, with time increasing from left to right for each of timelines 1701, 1702, 1703. Further LTE transmissions (or LTE subframe allocations) 1704, 1705, 1706 are shown for timelines 1701, 1702, 1703.

[0131] A hatch 1707 indicates UL / DL conflicts that may occur between Bluetooth transmissions and LTE transmissions.

[0132] The real-time (coexistence) interface 1026 can be implemented solely by hardware or a combination of hardware and software located in the LTE subsystem (i.e., in the first transceiver 1014). According to one aspect of this disclosure, this includes a set of eight proprietary real-time signals to support protocol synchronization and traffic arbitration. These signals can be controlled, for example, by a software driver located in the LTE subsystem. It is connected to the CBS chip RT interface 1013.

[0133] For example, the RT interface may include the traffic arbitration signals shown in Table 2. Table 2 signal Width I / O Description CWS active 1 I Medium busy, indicating CWS RF activity 0 = idle / 1 = active CWS Tx / Rx 1 I CWS traffic direction 0 = RX / 1 = Tx CWS Priority 2 I CWS Priority 0 = low priority / 1 = BT high priority / 2 = WLAN high priority (PS-POLL, ACK, BACK) / 3 = reserved LTE active 1 O CWS kill indicator

[0134] The RT interface may, for example, include protocol synchronization signals as shown in Table 3. Table 3 signal Width SRC / Dest I / O Description LTE frame sync 1 CWS O Synchronization signal indicating an LTE frame start UL - gap envelope 1 CWS O Synchronization signal indicating an LTE-UL gap. Signal envelope with edges occurring 1 ms before the air interface gap (rising and falling edges). DL gap envelope 1 CWS O Synchronization signal indicating an LTE-DL gap. Signal envelope with rising edge used only for LTE-TDD. Signal envelope with edges occurring 1 ms before the air interface gap (rising and falling edges).

[0135] The following is an example of a hardware implementation of the RT interface between the first transceiver 1014 and the second transceiver 1018.

[0136] The example describes an RT interface between the first communication chip 1022 and the connectivity chip 1024. The purpose of the RT interface is to enable fast, bidirectional communication between the two chips 1022 and 1024. Non-real-time communication can be performed, for example, using a standardized interface between the first transceiver 1014 and the second transceiver 1018.

[0137] The real-time interface can also be understood as something that basically contains a set of discrete signals, as in Fig. 18.

[0138] Fig. 18 shows a communication circuit 1800 according to one aspect of this disclosure.

[0139] The communication circuit 1800 corresponds, for example, to the first communication circuit 1022.

[0140] The communication circuit 1800 includes an LTE subsystem 1801 (L1CC), which can control all hardware interactions. The communication circuit 1800 includes an RT interface 1803, by means of which the LTE subsystem 1801 can be connected to another communication circuit, e.g., the second communication circuit 1024, which uses various IDC (In Device Coexistence) signals, which are shown on the left side of the RT interface 1803 and which are described in more detail in the following text.

[0141] According to one aspect of this disclosure, there are no specific requirements for the electrical characteristics of the RT interface 1803. For example, the IDC signals are configured during system boot. There is no need to reconfigure the IDC ports (which implement the RT interface 1803) during operation.

[0142] From a hardware perspective, the communication protocol for the interface signals can be kept simple. However, additional hardware support may be required in the Layer 1 subsystem context to support real-time handling of the interface signals (i.e., the IDC signals).

[0143] The LTE subsystem 1801 includes an RT-coex (coexistence) timer unit 1804, which is responsible for generating time-accurate events for the output signals IDC_LteDrxEnv, IDC_LteDtxEnv, and IDC_LteFrameSync when configured as output signals. When IDC_LteFrameSync is configured as an input signal, a snapshot in the form of LTE timing is performed. The signal characteristics are described in more detail below.

[0144] IDC_LteFrameSync - LTE2CWS_SYNC configuration (output signal): This signal can be used to generate periodic frame pulses for the CWS 1018. It should be noted that these pulses may not be available during LTE sleep phases.

[0145] IDC_LteDrxEnv, IDC_LteDtxEnv: These output signals are envelope signals that indicate discontinuous transmission / reception phases toward the CWS subsystem 1018. They are used to indicate discontinuous transmission / reception phases, depending on the cause: DARX, DTX measurements, or something else. Both signals can be individually programmed using a timer.

[0146] IDC_LteFrameSync - CWS2LTE_SYNC Configuration (Input Signal): This signal can be used when LTE2CWS_SYNC is also a desirable solution, while retaining it as a fallback. Using this signal, the CWS subsystem 1018 can request a snapshot of the LTE timing. Additionally, an interrupt can be generated with this event.

[0147] The LTE subsystem 1801 further includes an arbitration unit 1805, an interrupt control unit (IRQ) 1806, and an LTE transmission (Tx) path 1807. The arbitration unit 1805 is described in more detail in Fig. 19 shown.

[0148] Fig. 19 shows an arbitration unit 1900 according to one aspect of this disclosure.

[0149] The arbitration unit 1900 has an IDC status register 1901, an arbitration lookup table (LUT) 1902 and register 1903.

[0150] Arbitration unit 1900 can be used for status indication (e.g., via IDC status register 1901) and for interrupt generation. For example, the current level of signals, e.g., the IDC-related signals mentioned below, can be monitored by arbitration unit 1900. Furthermore, some of the signals can be supplied to trigger an interrupt at control unit 1806.

[0151] The arbitration unit 1900, in its role as an arbitration unit, provides hardware support for IDC real-time arbitration. The task of the arbitration unit 1900 is to control the signals IDC_LteActive and IIC_LteKill depending on the input signals IDC_CwsActive, IDC_CwsTxRx, and IDC_CwsPriority (which, due to its length, can be considered to consist of two signals, IDC_CwsPriority1 and IDC_CwdPriority2). For this purpose, a combination of the input signals can be made according to a programmable lookup table of the arbitration LUT 1902. The lookup table 1902 can be programmed on the fly using the LTE subsystem 1801.

[0152] IDC_LteActive: This signal is available on the IDC-RT interface 1803. The connectivity chip 1024 is the receiver of this signal. This signal can be composed of hardware to provide a fast response in the event of changing input parameters. For example, the reset and uncoupling level of this signal is zero.

[0153] IDC_LteKill: This signal can be used for ad-hoc termination of an LTE transmission. Within the LTE subsystem 1014, the signal can be used to generate an interrupt for the LTE subsystem 1804 and / or the LTE Tx path 1807. In principle, this signal can be used for direct manipulation of the Tx IQ data stream. For backup or emergency purposes, the LteKill signal is visible on the external IDC real-time interface 1803. If necessary, the LteKill signal from the RT interface 1803 can be connected to a GPIO (General Purpose Input / Output) to enable quick deletion of the current LTE transmission.

[0154] The arbitration LUT 1902 may include dedicated lookup tables implemented for IDC_LteActive and IDC_LteKill.

[0155] The arbitration unit 1900 may include filters 1904 for output signal filtering. In principle, an unstable state of the output signal (e.g., IDC_LteActive and IDC_LteKill) may be possible, for example, if an input signal changes and / or the lookup table 1902 is updated. If the unstable state causes a problem on the receive side, output filtering may be necessary. In this case, changes to the output signal are only applied if the input is stable for a minimal period of time (e.g., 1 microsecond). One-microsecond filtering does not imply a loss of granularity in signal processing, since it is not necessary to indicate events shorter than 1 microsecond. The filtering creates a 1-microsecond latency, which can be hidden by requiring the CWS 1118 to indicate its activity to the RT interface 1030 1 µs earlier.

[0156] LTE kill is a mechanism that can be used to stop (or terminate) the current LTE transmission (i.e., a UL communication) so that the LTE transceiver 1014 does not transmit, e.g., to free up the communication medium for WLAN / BT use. It can occur, for example, as a result of real-time arbitration to the advantage of WLAN / BT.

[0157] According to one aspect of this invention, abrupt shutdown of an LTE transmission is to be avoided because it could have various side effects such as spurious emissions and a possible influence on an eNodeB AGC power control.

[0158] To prevent spurious interference, LTE kill can be implemented using a power reduction command (e.g., sent via a digRF interface) or by zeroing IQ samples. Using a power reduction command may be preferable to a shutdown command, as it provides the ability to reduce LTE transmit power down to -40 dBm (vs. -50 dBM) while avoiding unwanted side effects (such as PLL (Phase Locked Loop) shutdown, etc.).

[0159] The use of a command sent over the digRF interface ensures that changes in the transmission power occur in a smooth or uniform manner, thus avoiding spur generation.

[0160] According to one aspect of the invention, in order to achieve optimal adaptation to WLAN / BT traffic, LTE-kill has a very short latency, e.g., approximately 10 µs for WLAN traffic and approximately 150 µs for BT traffic.

[0161] Fig. 20 shows a transmission diagram 2000.

[0162] WLAN traffic over the medium is depicted along a timeline 2001, with data reception (i.e., downlink communication) depicted above timeline 2001 and data transmission (i.e., uplink communication) depicted below timeline 2002. LTE transmission is also depicted for a first case 2002 and for a second case 2003. Furthermore, CWS Rx / Tx is depicted over the RT interface 2004.

[0163] It should be noted that WLAN activity has a timing uncertainty due to contention or contention in CSMA (Carrier Sense Multiple Access): - When a WLAN device gains access, timing uncertainty on the order of several µs occurs. - This is not known precisely in advance, but it is tied to the WLAN MAC (Medium Access Control) protocol; - When a Wi-Fi device loses access to the medium, its activity differs for several hundred microseconds and, from a coexistence perspective, can be considered a new traffic event. This is not known in advance and can repeat itself multiple times.

[0164] In contrast, BT has no timing uncertainty.

[0165] It should be noted that ensuring that LTE kill is not applied to consecutive retransmissions of the same subframe may be critical to protecting HARQ. For FDD, this means that LTE kill is prohibited for subframe n and subframe n+8. A pattern can be used to protect HARQ.

[0166] It should also be noted that full use of the remaining time in the erased LTE subframe by WLAN / BT may be desirable.

[0167] Another example of components of the communication device 1000 is given below.

[0168] Fig. 21 shows a communication device 2100.

[0169] For example, the communication device 2100 corresponds to the communication device 1000, with only some of the components shown, while other components have been omitted for simplicity.

[0170] The communication device 2100 includes an LTE subsystem 2101, which corresponds, for example, to the first transceiver 1014 and / or the LTE subsystem 1801, and a WLAN / Bluetooth communication circuit 2102, which corresponds, for example, to the second of the second communication circuit 1024. The LTE subsystem 2101 includes an LTE radio module 2103 and a communication circuit 2104, which corresponds, for example, to the first communication circuit 1022. The LTE subsystem 2101 can implement the L1 (Layer 1) LTE communication stack 2114 and the LTE protocol stack 2115 (above Layer 1).

[0171] The communication device 2100 further includes an application processor 2105, which corresponds, for example, to the processor (CPU) 1002. Connection applications or connectivity applications 2112 (including WLAN applications or applications and / or Bluetooth applications or applications) and LTE applications or applications 2113 can be executed on the application processor 2105.

[0172] The communication circuit 2104 may include an NRT-apps (application) coexistence interface 2106 for communicating with the application processor 2105 by means of an application interface 2109 of the application processor 2105, and an NRT coexistence interface 2107, corresponding, for example, to the NRT interface 1028, for communicating with the WLAN / BT communication circuit 2102 by means of an NRT coexistence interface 2110 of the WLAN / BT communication circuit 2102, corresponding, for example, to the NRT interface 1032.

[0173] The LTE subsystem 2101 includes an RT arbitration unit 2111 (which corresponds, for example, to the arbitration unit 1805).

[0174] The communication circuit 2104 further includes an (LTE connectivity) NRT arbitration unit 2108. It should be noted that the NRT arbitration unit 2108 is not necessarily located in the communication circuit 2104, but can also be located in other components of the communication device 1000, 2108. It can be implemented, for example, in the form of the CPU 1002.

[0175] The LTE subsystem 2101 includes a first RT interface 2106, which corresponds, for example, to the first RT interface 1026, and the WLAN / Bluetooth communication circuit 2102 includes a second RT interface 2107, which corresponds, for example, to the second RT interface 1030, which can be understood as forming an RT interface 2116 between the LTE subsystem 2101 and the WLAN / Bluetooth communication circuit 2102.

[0176] Table 4 shows the signals that can be exchanged, for example, via the RT interface 2116. Table 4 signal Width I / O Description Used in FDD Volume 7 Used in TDD Volume 40 CWS active 1 I Medium occupied, indicating CWS-RF activity Arbitration Arbitration 0 = idle / 1 = active CWS Tx / Rx 1 I CWS traffic direction Unused (CWS Active high only for Rx) Arbitration 0 = Rx 1 = Tx CWS Priority 2 I CWS Priority Arbitration Arbitration 0 : low priority / 1 : BT high priority / 2 : WLAN high priority (PS-POLL, ACK, BACK) / 3 : reserved LTE active 1 O CWS kill indicator Arbitration Arbitration LTE frame sync 1 O Synchronization signal indicating an LTE frame start Unused Traffic synchronization UL gap sheath 1 O Synchronization signal indicating an LTE-UL gap. Signal envelope with edges occurring 1 ms before the air interface gap (rising and falling edges). Traffic synchronization Traffic synchronization DL-split sleeve 1 O Synchronization signal indicating an LTE-DL gap. Signal envelope with rising edge used only for LTE-TDD. Signal envelope with edges that occur 1 ms before the air interface gap (rising and falling edges). Unused Traffic synchronization

[0177] It should be noted that due to its length, the CWS priority signal can also be considered as two signals, CBS priority 1 & 2.

[0178] It should further be noted that the first transceiver 1014 and the second transceiver 1018 may also be connected via the application processor 2105 (e.g., the CPU 1002) instead of a direct connection (as a direct RT interface). Furthermore, it should be noted that, in general, communication may be implemented via a serial or parallel bus instead of using dedicated signals (as shown, for example, in Table 4).

[0179] According to one aspect of the disclosure, a degraded RT mode of operation may be used. Specifically, only a subset of the RT coexistence I / F signals specified in Table 4 may be operatively connected to the WLAN / Bluetooth communication circuit 2102.

[0180] For an FDD-only platform (i.e., in the case where the first transceiver 1014 and the second transceiver 1018 use only FDD), a first option (referred to as Option 1a in Table 5 below) for a degraded RT interface is to remove the DL gap envelope signal and the CBS Tx / Rx signal, leaving six signals. Because these removed signals are useless for FDD, there is no impact on coexistence performance. As a second option (referred to as Option 1b in Table 5 below), in addition to removing the DL gap envelope signal and the CBS Tx / Rx signal, the CBS priority signal (CBS priority signals 1 & 2) can be removed, leaving four signals. In this case, there is no longer a priority indication. Alternatively, a "light" or "light" signal can be used.weak arbitration is used, where the second transceiver 1018 indicates activity only for high priority traffic, but high priority traffic from BT and WLAN can no longer be distinguished from each other.

[0181] For an FDD-TDD platform (i.e., in which the first transceiver 1014 and the second transceiver 1018 use TDD and FDD), a first option (referred to as Option 2 in Table 5 below) is to eliminate arbitration and rely solely on traffic synchronization, leaving only three signals. In this case, the second transceiver 1018 becomes a pure slave and can only use the communication resources remaining from the LTE communication (i.e., the first transceiver 1014) signaled via the DL gap envelope signal and the UL gap envelope signal, or via synchronization via the TDD frame structure based on the LTE frame sync signal. In this case, there is no way to protect LTE traffic from incorrect or late CWS scheduling.

[0182] As a second option (referred to as Option 3 in Table 5 below), traffic synchronization and light arbitration can be maintained, leaving six signals. In this case, there is no priority setting. The second transceiver can only signal or indicate above a certain priority, but cannot distinguish between BT and Wi-Fi. The same arbitration rules are used for the LTE-BT conflict and the LTE-Wi-Fi conflict.

[0183] Table 5 summarizes the options for a degraded RT interface. Table 5 Option Applicable for TDD / FDD Removed signals I / F signals Influence comment BT Wi-Fi On LTE 1a only FDD DL gap envelope None Traffic sync arbitration CWS 6 none none no - Nbr - Tx / RX r Traffic sync of LTE rejection incre ased Traffic sync arbitration - no distinction between WLAN and BT activity Arb i-tra ¬ti on None -traffic sync only -no arbitration 1b only FDD DL gap envelope Nbr of LTE rejection increases - Traffic sync arbitration - No distinction between WLAN and BT activity

[0184] As a summary, for example, the following may be provided for an RT coexistence mechanism according to various aspects of this invention: - LTE frame indicator (signal + frame structure notification) - UL gap display - DL gap display - Arbitration with a short conflict option - HARQ protection (for arbitration and LTE denial) - Degraded RT operating mode - Full use of an LTE deleted subframe - Implementation of an RT interface, such as described above General coexistence architecture

[0185] According to one aspect of this disclosure, five entities or elements perform LTE-CWS coexistence management: the MRT arbitration entity 2108, the NRT application coexistence interface 2106, the NRT coexistence interface (formed by NRT coexistence interfaces 2107, 2110), the RT arbitration entity 2111, and the RT coexistence interface (formed by RT interfaces 2106, 2107).

[0186] The (LTE connectivity) NRT arbitration unit 2108 can be implemented, for example, by software located in the communication circuit 2104. It uses, for example, a mix of application requirements (from the connectivity and LTE apps) and context information from both cores (e.g., from the first transceiver 1014 and the second transceiver 1018), e.g., the band, the bandwidth, the EARFCN (E-UTRA Absolute Radio Frequency Channel Number) to perform arbitration and displays static information, such as selected frequency bands or selected power levels, to the first transceiver 1014 and the second transceiver 1018. It also provides indications to the RT arbiter 2111 located in the LTE subsystem 2101. It should be noted that, according to one aspect of the disclosure, the NRT arbitration unit 2108 does not perform arbitration between WLAN and BT. This arbitration may, for example,in a WLAN / BT communication circuit.

[0187] The NRT-apps (applications) coexistence interface 2106 may also be an entity implemented by software executing in the communication circuit 2104. It transmits NRT messages carrying application information from connectivity applications 2112 and LTE applications 2113 executing on the application processor 2105. Table 6 provides a list of messages that can be exchanged between the application processor 2105 and the communication circuit 2104 via the NRT-apps coexistence interface 2106 (and the corresponding application interface 2109). Table 6 News about LTE-NRT Apps Coex I / F (R / W) ID Message payload In fo Bi ts I / O Description 1 IS_COEX 1 I 1 = Coexistence between at least 2 systems 0 = no coexistence 2 IS_TETHERING 1 I 1 = WLAN unit is access point 0 = WLAN unit is a STA 3 WLAN_APP_PERIOD 16 I Required service period for WLAN in ms 4 WLAN_APP_DURATI ON 6 I Required service duration for WLAN in ms 5 BT_APP_PERIOD 16 I Requested service period for BT in ms. Applies to a connection using eSCO or SCO. 6 BT_APP_DURATION 6 I Requested service duration for BT in ms. Applies to a connection using only eSCO or SCO. 7 WLAN_APP_THROUG HPUT 16 I In kbps 8 BT_PROFILE_BITM AP 32 I Bitmap of the active BT profile (HFP, HSP, A2DP...) 9 LTE_APP_THROUGH PUT 16 I In kbps 10 LTE_APP_LATENCY 16 I Application latency in ms

[0188] The NRT coexistence interface 2107 can also be a unit implemented by software located in the communication circuit 2104. It transmits NRT messages carrying context information from the WLAN / BT communication circuit and sends messages from the NRT arbiter 2108 to the WLAN / BT communication circuit (via the corresponding NRT coexistence interface 2110 of the WLAN / BT communication circuit). Table 7 provides a list of messages that can be exchanged, for example, via the interface formed by the NRT coexistence interface 2107 of the communication circuit 2104 and the NRT coexistence interface 2110 of the WLAN / BT communication circuit 2102. Table 7 News about LTE-RT Coex I / F (R / W) ID News payload Info Bits I / O Description 1 WLAN_CHAN_NBR 3 I / O WLAN channel number (applied or to be applied) 2 WLAN BW 1 I / O WLAN bandwidth (applied or applicable): 0 = 20 MHz 1 = 40 MHz 3 WLAN_MCS 4 I WLAN MCS 4 WLAN_TX_POWER 4 I / O WLAN Tx power (applied or applicable) 5 WLAN_CHANNEL_RANK 14x4 I WLAN channel plan, ranked from preferred to worst based on SINR measurements and WLAN / BT restrictions 6 BT_AFH_RANK 79x3 I full AFH plan (including channels that may be excluded for WLAN / BT Coex) with preferences encoded over 3 bits : 000 ->preferred 111 ->worst 7 BT_AFH_MAP 79 I / O BT AFH Bitmap (applied or to be applied) 8 BT_PKT_TYPE 4 I Bluetooth packet type 9 GNSS_BD 2 operated frequency band 10 GNSS_STATE 2 0 = sleep 1 = Recording 2 = Tracking 11 LTE_BITMAP 10x2 O 0 = Special subframe 1 = RX LTE subframe 2 = TX LTE subframe 13 WLAN_LTE_EN 1 O Transmission of WLAN packets shorter than wlan_short_tx while LTE RX is allowed. 14 BT_LTE_EN 1 O Transmission of WLAN packets with a power < bt_low_pwr_tx while LTE RX is allowed 15 LTE_SPS_PATTERN 24 O PLC periodicity (ms): 11 bits PLC event duration (ms): 9 bits SPS initial offset (subframe offset in the first LTE frame where SPS is applied): 4 bits

[0189] It should be noted that the LTE bitmap can be modified (limited to seven frame structures, but also allows for more configurations for the S content itself). It should also be noted that the NRT messages mentioned above can be sent partially or completely to the eNodeB 103, as some coexistence decisions are made by it.

[0190] Additionally, it should be noted that depending on the platform architecture and application stacks, the division between information located in the communication circuit 2104 and in the WLAN / BT communication circuit 2102 may be changed.

[0191] According to one aspect of this invention, the NRT coexistence algorithm and the RT coexistence algorithm are coordinated. This is Fig. 22 illustrates.

[0192] Fig. 22 shows a flowchart 2200.

[0193] When the coexistence status of the communication device 1000 changes to 2201, the NRT coexistence mechanism 2202 is activated. A message is then sent over the NRT coexistence interface to apply the NRT arbitration decision.

[0194] Subsequently, in 2203, the desensing level for the RAT connectivity achieved with the newly applied NRT arbitration is estimated using a pre-calculated RF interference table. If it is above the desensing target, the RT coexistence mechanism is activated in 2204 and is continuously executed autonomously. If the desensing level is below the desensing target, the RT coexistence mechanism is deactivated in 2205.

[0195] When updates (via SW messages) are received from either the LTE subsystem 2101 or the WLAN / BT communication circuit 2102, the NRT arbiter 2108 may detect a change in coexistence status, in the sense that, for example, if the frequencies previously used for LTE and CWS communication were not in the critical bands, this may now be the case and coexistence algorithms must be activated.

[0196] The NRT arbiter 2108 is the unit responsible for enabling or disabling any specific coexistence algorithms, and is always ready to receive input signals from LTE or CWS indicating a change of any relevant parameter.

[0197] Cases of change of coexistence status may include (among others): - a second RAT becomes active; - a handover is performed in LTE communication to another LTE band; - the LTE bandwidth is modified; - the number of active RATs drops to 1.

[0198] As described above and according to various aspects of the disclosure, a separation (e.g., in the form of interfaces) may occur between RT and NRT. RT and NRT processing may be synchronized. NRT messages may be augmented by messages between the communication devices 105 and the eNodeB 103. NRT coexistence mechanism

[0199] The NRT coexistence mechanism may include an FDM / PC (Frequency Division Multiplex / Power / Control) algorithm for Bluetooth, which is described below.

[0200] Bluetooth medium access is based on slotted traffic scheduling (slotted traffic scheduling link). Slots are scheduled or defined in a fixed time and frequency grid. The time slots are 625 µs long and mapped to 1 MHz wide BT channels. The frequency channel used for a given time slot is subject to frequency hopping patterns that alternate pseudo-randomly from slot to slot.

[0201] A Bluetooth device (e.g., in the form of a communication device 1000 using Bluetooth) can be either a (Bluetooth) master or a (Bluetooth) slave. A Bluetooth master provides reference time and controls the synchronization and activity of a piconet it manages, which is a small network of surrounding Bluetooth devices. Slave devices must periodically monitor the medium to capture any control information coming from the piconet master. A Bluetooth slave listens for all potential master transmissions (1.25 ms periods) during a slot or slot portion, and responds in the next slot if it has received a packet addressed to it in the current slot.A BT slave can use a "sniff mode" to reduce and avoid power consumption: master-slave transactions only take place in reserved slots (negotiated before entering sniff mode).

[0202] According to Bluetooth, user data and / or control data are carried over two periods and / or by asynchronous packets. The type of packets for a given data traffic depends on the corresponding traffic profile (which is standardized). Control traffic is carried by asynchronous traffic.

[0203] A BT slave can use a "sniff mode" to reduce and avoid power consumption: master-slave transactions only take place in reserved slots (negotiated before switching to sniff mode).

[0204] Target Bluetooth profiles can be A2DP for audio (e.g., music) streaming and HFP as a voice headset profile. A2DP is an asynchronous traffic profile that uses variable-length packets (single-multislot), while HFP is periodic single-slot traffic that is transferred or transmitted in fixed (reserved) slots. Devices can also be BT-paired without any traffic.

[0205] Slots can be reserved during connection setup (by the connection manager). The most common packets are HV3 packets (for synchronous connection-oriented (SCO) communication), which occupy one-third of a double slot.

[0206] An example of multi-slot Bluetooth traffic is shown in Fig. 23 illustrates.

[0207] Fig. Figure 23 shows a transmission diagram for 2003.

[0208] In the transmission diagram 2300, time increases from left to right and is divided into time slots 2301 of 625 µs. First transmissions 2302 are performed by a master device, and second transmissions 2303 are performed by a slave device.

[0209] Bluetooth communication uses frequency hopping. During communication, the frequency channels used or operated change pseudo-randomly from time slot to time slot, performing a pseudo-random migration or route through 79 available 1 MHz channels in the ISM band 202.

[0210] Adaptive Frequency Hopping (AFH) is a mechanism that allows this to be restricted to a subset of the 79 channels. However, the number N of channels used cannot be less than 20. Channel plan selection is completely flexible, but results from negotiations between master and slave, which are carried out on a static basis. AFH can be disabled for "parked" slaves.

[0211] The adaptive frequency hopping mechanism can be used to push BT traffic away from the LTE frequency bands. It is particularly effective for protecting LTE Rx from BT Tx (LTE-TDD), but less effective in the reverse direction because the BT frontend (filter / low-noise amplifier (LNA)) is a wideband.

[0212] According to one aspect of this invention, the adaptive frequency hopping mechanism is utilized in the following: - the first communication circuit 1022 sends a static request to the second communication circuit 1024 (acting as a (local) BT core) to change its channel plan; - the second communication circuit 1024 updates the channel plan and coordinates it with the paired unit (e.g., another communication device).

[0213] Bluetooth spectrum occupancy can be reduced to 1 / 3 of the ISM band 202. This provides a guard band of up to 60 MHz for the LTE band 40 201 and a guard band of up to 79 MHz for the LTE band 7 UL 204. It should be noted that the efficiency of AFH for BT / LTE coexistence may be limited due to the fact that the BT-RX frontend receives the full band even in the AFH context (nonlinearities are present anyway).

[0214] The impact of using this mechanism for BT-WLAN coexistence can be considered limited.

[0215] The following describes a procedure for protecting Bluetooth from LTE-FDD transmissions in LTE band 7 UL 204 with reference to Fig. 24 described.

[0216] Fig. Figure 24 shows a message flow diagram 2400.

[0217] An NRT algorithm corresponds to the message flow diagram 2400, which can be executed, for example, by the NRT arbitration unit 2108.

[0218] The message flow takes place between an LTE subsystem 2401 corresponding to the LTE subsystem 2101 (e.g., a software), an NRT arbiter 2402 corresponding to the NRT arbiter 2108, and a BT communication circuit 2403 corresponding to the WLAN-BT communication circuit 2102.

[0219] In 2404, the NRT arbiter 2402 loads the BT desensing target.

[0220] In 2405, the NRT arbiter 2402 sends an LTE information request (info request) message 2406 to the LTE subsystem 2401 to request information about the LTE configuration.

[0221] In 2407, the LTE subsystem 2401 generates information about the LTE configuration, e.g., an LTE information table, including the used band, the used bandwidth, the EARFCN, the path loss margin (estimated transmission power loss without trigger modulation / bandwidth switching), etc.

[0222] In 2408, the LTE subsystem 2401 sends the generated information with an LTE information acknowledgment message 2409 to the NRT arbiter 2402.

[0223] In 2410, the NRT arbiter 2042 stores the information it received with the LTE information confirmation message 2409.

[0224] In 2411, the NRT arbiter 2402 sends an AFH plan request message 2412 to the BT communication circuit 2403 to request an AFH plan.

[0225] In 2413, the BT communication circuit 2403 forms a ranked AFH plan including channels excluded from coexistence.

[0226] In 2414, the BT communication circuit 2403 sends the generated AFH plan to the NRT arbiter 2402 with an AFH plan confirmation message 2415.

[0227] In 2416, the NRT arbiter 2402 generates a new AFH plan. The default is the BT de-sensing level. The generation can include, for example, the following: 1) Calculate a Delta F for BT channels (full band, granularity to be defined) 2) Evaluate BT de-sensing versus full-band BT channel operation using isolation tables (static, pre-calculated for LTE at full power) 3) Selection N, highest number of BT channels that satisfy the BT desensing target 4) If the target cannot be reached or N < Nmin, then use Nmin 5) If the target cannot be reached, keep the exclusion that was applied for WLAN / BT coex > neglect 6) Create a new AFH plan.

[0228] In 2417, the NRT arbiter 2402 sends the new AFH plan to the BT communication circuit 2403 with an AFH set request message 2418 requesting the BT communication circuit 2403 to use the new AFH plan.

[0229] In 2419, the BT communication circuit 2403 updates the frequency hopping sequence accordingly.

[0230] In 2420, the BT communication circuit 2403 confirms the use of the new AFH plan by means of an AFH set confirmation message 2421.

[0231] In 2422, the NRT arbiter 2402 selects the highest LTE Tx (transmit) power that satisfies the BT de-sensing target and the LTE Tx path loss margin.

[0232] It should be noted that this approach can be dangerous for interoperability testing (IOT). According to one aspect of this invention, it is important to ensure that it is applied only in coexistence cases, as defined by AB.

[0233] In 2423, the NRT arbiter 2402 sends the determined LTE Tx power to the LTE subsystem 2401 with a power request message 2424, which requests the LTE subsystem 2401 to use the determined Tx power.

[0234] In 2425, the LTE subsystem 2401 uses the Tx power accordingly.

[0235] In 2426, the LTE subsystem 2401 confirms the use of the Tx power by means of a power confirmation message 2427.

[0236] In 2428 it is assumed that the NRT arbiter 2402 recognizes that there is no (any) more coexistence to be taken into account from now on.

[0237] In 2429, the NRT arbiter 2402 sends a power cancellation request message 2430 to the LTE subsystem 2401, which is confirmed in 2431 by the LTE subsystem 2401 by means of a power cancellation confirmation message 2432.

[0238] According to one aspect of this invention, the NRT coexistence mechanism comprises an FDM / PC algorithm for WLAN, which is described below.

[0239] Wi-Fi medium access is based on Carrier Sense Medium Access (CSMA), where stations listen for a medium and compete to gain access to it when it is idle. There is no resource scheduling and no traffic periodicity. Global synchronization is achieved using a beacon transmitted by the access point approximately every 102 ms, but effective beacon transmission can be delayed due to medium congestion.

[0240] WLAN MACs adapt to the radio channel conditions using link rate adaptation, which is based on a packet error rate calculated on the transmit side based on received ACKs (positive ACKs with repeated or retransmissions).

[0241] In the 2.4 GHz band (ISM band), WLAN systems operate over 14 overlapping channels, designated CH#1 to CH#14 (CH#14 is used only in Japan). Fig. 25 illustrates.

[0242] Fig. Figure 25 shows a frequency allocation diagram 2500.

[0243] In the frequency allocation diagram 2500, frequencies increase from left to right. The 14 overlapping channels allocated for Wi-Fi are represented by semicircles 2501.

[0244] Wi-Fi typically operates in BSS (Basic Service Set) mode. A peer-to-peer mode also exists, but this is rarely used so far. However, it could be useful for smartphone use.

[0245] In BSS mode, the access point (AP) has full control over the operating Wi-Fi channel selection and the mobile stations (STAs). The Wi-Fi channel is selected or set by the static access point.

[0246] According to one aspect of this disclosure, WLAN power control is used to reduce interference with LTE communication.

[0247] Wi-Fi has a peak power of approximately 20 dBm and is typically transmitted at full power to enable the highest possible PHY rate and reduce packet duration as much as possible for power consumption reasons. However, the Wi-Fi protocol stack does not prevent the use of less transmit power or define rules for selecting the power used.

[0248] If necessary, the second transceiver 1018 (operating as a WLAN transceiver in this example) integrated in the communication device 1000 can autonomously reduce its Tx power: - If the communication device 1000, via the second transceiver 1018, acts as a station connected to a home access point or hotspot, it is likely to trigger a link rate adjustment event to lower the PHY rate, which would result in a longer packet duration and thus longer interference between WLAN and LTE. According to one aspect of this disclosure, the use of power control is limited in this case. - When the communication device 1000 acts as an AB (i.e., fat herring case) via the second transceiver 1018, the distance between the communication device 1000 (e.g., a smartphone) used as an access point (router) and a connected WLAN (e.g., wiki) client (e.g., laptop) is under the user's control and can be shortened. The communication device 1000 can then significantly reduce its WLAN Tx power to compensate for the reduced BSS coverage and associated path losses.

[0249] A comparison of the estimated path losses for tethering versus hot-spot is given in Table 8. Table 8 Use case Tethering Hot spot (interior) AP-STA distance 10 30 Path losses dB 66, 1 85,2 Delta dB 19,1

[0250] The approximate estimation given in Table 8 shows a 19 dB margin between hotspot and tethering, which indicates that the WLAN Tx power can be reduced by up to 19 dB, which corresponds to 1 dBm.

[0251] According to one aspect of this disclosure, the AP Tx power is gradually reduced and the PER evolution at the AP is observed (PER statistics are generated in the WLAN anyway).

[0252] In summary, WLAN power control can achieve a 15-20 dB reduction in WLAN-to-LTE interference in the case of tethering. LTE-to-WLAN interference rejection requirements could be relaxed (WLAN de-sensing requirement). For connections with TDM (Time Division Multiplexing) solutions, this approach may not be suitable because Tx power reduction can lead to a lower PHY rate and thus to increased Tx duration. There is a trade-off between power control and using high PHY rates.

[0253] According to one aspect of this invention, WLAN channel selection is used to reduce WLAN / LTE interference.

[0254] In the use case where the communication device 1000 (as a WLAN unit) acts as an AP (e.g., tethering), it can freely select the WLAN channel for its operation. Thus, WLAN traffic can be pushed away from the LTE operating band, thus protecting both WLAN from LTE and LTE from WLAN. According to one aspect of this invention, the WLAN channel quality as perceived by the WLAN APs, e.g., reflection channel occupancy by a nearby hotspot or a home AP, is taken into account in this process.

[0255] Wi-Fi channel selection can provide 18 to 42 dB of interference reduction from Wi-Fi to LTE (LTE Band 40) when channels CH#3 to #14 are selected. This mechanism is compatible with power control solutions, which can be used in addition.

[0256] Wi-Fi channel selection can bring 27 to 77 dB reduction of LTE (LTE band 40) to Wi-Fi interference when channels CH#3 to #10 are selected.

[0257] Overall, AP channel selection can reduce: - WLAN to LTE band 40 OOB (out-of-band) rejection by 18 to 42 dB; - LTE band 40 to WLAN OOB rejection by 27 to 77 dB; - LTE Band 7 UL -> WLAN OOB rejection by 19 to 49 dB.

[0258] This mechanism does not harm Wi-Fi throughput or Wi-Fi robustness.

[0259] It should be noted that the aforementioned analysis only considers OOB noise effects, and thus assumes that nonlinear effects such as signal compression due to backmixing are avoided by the RF system design.

[0260] The following describes a procedure for protecting WLAN from LTE-FDD transmissions in LTE band 7 UL 204 with reference to Fig. 26 described.

[0261] Fig. 26 shows a message flow diagram 2600.

[0262] An NRT algorithm corresponds to the message flow diagram 2600, which can be executed, for example, by the NRT arbitration unit 2108.

[0263] The message flow takes place between an LTE subsystem 2601, which corresponds to the LTE subsystem 2101 (e.g., a software), and an NRT arbiter 2602, which corresponds to the NRT arbiter 2108, and a WLAN communication circuit 2603, which corresponds to the WLAN / BT communication circuit 2102.

[0264] In 2604, the NRT arbiter 2602 loads the WLAN desensing target.

[0265] In 2605, the NRT arbiter 2602 sends an LTE information request message 2606 to the LTE subsystem 2601 to request information about the LTE configuration.

[0266] In 2607, the LTE subsystem 2601 generates information about the LTE configuration, e.g., an LTE information table that includes the used band, the used bandwidth, EARFCN, the path loss margin (estimated transmit power degradation without trigger modulation / bandwidth changes), etc.

[0267] In 2608, the LTE subsystem 2601 sends the generated information with an LTE information acknowledgment message 2609 to the NRT arbiter 2602.

[0268] In 2610, the NRT arbiter 2602 stores the information it received with the LTE information acknowledgment message 2608.

[0269] In 2611, the NRT arbiter 2602 sends a channel plan request message 2612 to the WLAN communication circuit 2603 to request a channel plan.

[0270] In 2613, the WLAN communication circuit 2603 forms a ranked channel plan. The ranked channel plan may be based on SINR (signal-to-interference-plus-noise ratio) and WLAN / BT limitations or obstructions.

[0271] In 2614, the WLAN communication circuit 2603 sends the generated channel plan to the NRT arbiter 2602 with a channel plan confirmation message 2615.

[0272] In 2615, the NRT arbiter 2602 determines a WLAN channel to be used. The default is the WLAN desensitization level. The determination may include, for example, the following: 1) Calculate a Delta F for each WLAN channel; 2) Evaluate WLAN desensitization for each WLAN usage, using an isolation table (static, pre-calculated for LTE at full power); 3) Select the highest ranked Wi-Fi channel that meets the Wi-Fi desensitization target.

[0273] In 2617, the NRT arbiter 2602 sends an indication of the determined WLAN channel to the WLAN communication circuit 2603 with a channel set request message 2618 requesting the WLAN communication circuit 2603 to use the determined WLAN channel.

[0274] In 2619, the WLAN communication circuit 2603 moves accordingly to the specified WLAN channel.

[0275] In 2620, the WLAN communication circuit 2603 confirms the use of the specified WLAN channel by means of a channel setting confirmation message 2621.

[0276] In 2622, the NRT arbiter 2602 stores an indication of the WLAN channel.

[0277] In 2623, the NRT arbiter 2602 sends a WLAN information request message 2624 to the WLAN communication circuit 2603 to request information about the WLAN configuration.

[0278] In 2625, the WLAN communication circuit 2603 generates information about the WLAN configuration, e.g., a WLAN information table including the channel number, the MCS (Modulation and Coding Scheme), the Tx power, etc.

[0279] In 2626, the WLAN communication circuit 2603 sends the generated information with a WLAN information confirmation message 2627 to the NRT arbiter 2602.

[0280] In 2628, the NRT arbiter 2602 selects the highest LTE-Tx (transmit) power that satisfies the WLAN desensitization objective and the LTE-Tx path loss margin.

[0281] This may include: 1) Calculate a Delta F for the operating WLAN channel; 2) Calculate WLAN desensitization for the operating WLAN channel, using an isolation table (static, pre-calculated for LTE at full power); 3) Select the highest LTE Tx power that satisfies the WLAN desensitization target and the LTE Tx path loss margin.

[0282] It should be noted that this approach can be dangerous for interoperability testing (IOT). According to one aspect of this disclosure, it must be ensured that it is applied only in coexistence cases defined by AB.

[0283] In 2629, the NRT arbiter 2602 sends the specified LTE Tx power to the LTE subsystem with a power request message 2630 requesting the LTE subsystem 2601 to use the specified Tx power.

[0284] In 2631, the LTE subsystem 2601 applies the Tx power accordingly.

[0285] In 2632, the LTE subsystem 2601 confirms the use of the Tx power by means of a power confirmation message 2633.

[0286] In 2634, it is assumed that the NRT arbiter in 2602 has realized that there is no further coexistence to be taken into account from now on.

[0287] In 2635, the NRT arbiter 2602 sends a power cancellation request message 2636 to the LTE subsystem 2601, which is confirmed in 2637 by the LTE subsystem 2601 by means of a power cancellation confirmation message 2638.

[0288] Messages may be exchanged, for example, via the NRT interface formed by the NRT coexistence interface 2107 of the communication circuit 2104 and the NRT coexistence interface 2110 of the WLAN / BT communication circuit 2102 (e.g., operated as a WLAN / BT baseband circuit) in the context of an NRT coexistence, as shown in Table 7 above. Further examples are given in the following text.

[0289] According to one aspect of the invention, a measurement gap configuration is used in LTE connected operation mode for LTE-WLAN coexistence.

[0290] While in LTE connected mode of operation, measurement columns defined in 3GPP specifications allow individual wireless mobile devices (i.e., mobile devices with only one LTE transceiver that does not have the capability to transparently measure other frequencies during LTE connected mode of operation (other than those used by the serving cell)) to perform measurements of: 1. LTE neighboring cells operating on frequencies other than the serving cell (intermediate frequency measurements); 2. Other RAT (e.g. 2G or 3G) neighboring cells (inter-RAT measurements).

[0291] When LTE is the serving RAT, these measurement columns typically have a length of 6 ms and are scheduled with either a 40 ms or 80 ms periodicity.

[0292] When LTE communication is performed, which uses a frequency that overlaps with Wi-Fi communication and vice versa, the measurement gaps can be used for secure Wi-Fi reception and transmission: • if the gap is used for an LTE inter-frequency measurement, and if the LTE frequency does not overlap with the WLAN frequency • If the gap is used for 2G or 3G measurement, because there is no possible interference between 2G / 3G and the ISM frequency band, the gap can be used without restriction for WLAN / BT in parallel with the LTE measurement.

[0293] Additionally, 3GPP Release 9 introduces the concept of autonomous measurement gaps for improved closed subscriber group (CSG) cell support in LTE-connected operation mode. This is because the SIB (System Information Block) must be read for CSG cells, which requires an additional measurement gap asynchronous to those scheduled at regular intervals. If the network supports autonomous measurement gaps, it is permissible for the mobile device to ignore some / few TTIs, as long as the mobile device is capable of sending at least 60 ACKs / NAKs per 150 ms interval. HARQ and higher-layer signaling ensure that no data is lost.

[0294] To inform the second transceiver 1018 in advance of any upcoming regular gap event or occurrence during which no interference with WLAN reception or transmission will occur, the first transceiver 1014 (e.g., the LTE baseband circuitry) may send a message to the second transceiver 1018 (e.g., the CWS baseband circuitry) indicating a gap pattern together with: • the measurement slit pattern periodicity (e.g. 40 / 80 ms), • the measurement slot duration (e.g. 6 ms) • a unique method for identifying the first measurement gap occurrence for the measurement gap pattern under consideration.

[0295] This can be used for: • Intermediate frequency measurement gap, • Inter-RAT measurement gap, • autonomous measurement gap.

[0296] The message may be, for example, a Periodic_Gap_Pattern_Config (periodicity, duration, first event date) message sent from the first transceiver 1014 (e.g., LTE baseband circuitry) to the second transceiver 1018 (e.g., such as CWS baseband circuitry) indicating the periodic gap pattern, and the second transceiver 1018 may freely perform transmission and reception during each of these gaps.

[0297] A criterion and a decision in the first transceiver 1014 (e.g., the LTE baseband circuitry) to enable the sending of a gap message indication from the first transceiver 1014 (e.g., implemented by the LTE protocol stack or the LTE physical layer) controlled by the first processor to the second transceiver 1018 (e.g., the CWS baseband circuitry) may be associated with the non-real-time arbiter unit (e.g., software) 2018, which may be executed on the first transceiver 1014 (e.g., the LTE baseband circuitry), based on whether: • Frequency interference occurs; • there are sufficient or insufficient interference-free time periods during which the second transceiver 1018 (e.g., the CWS baseband circuit) could operate.

[0298] The gap message indication can be dynamically turned on or off by the non-real-time arbiter 2108 (e.g., software) when it considers that the criterion is met to start or stop the use of gaps to ensure proper functionality of the second transceiver 1018.

[0299] In summary, Wi-Fi communication can be protected from LTE band 7 UL 204, Bluetooth communication can be protected from LTE band UL 204, and also Wi-Fi communication can be protected from LTE band 40 201 and Bluetooth communication can be protected from LTE band 40 201. PHY mitigation

[0300] Pilot symbols in overlapping OFDM symbols are typically meaningless. The worst case scenario is when two consecutive OFDM symbols are lost per LTE slot. This means that one pilot is missing per antenna and per slot (e.g., less than two for antennas 0 and 1, less than one for antennas 2 and 3). It should be noted that antennas 0 and 1 are only relevant for smartphones. This leaves a worst case scenario (for 1 / 2 antennas): one pilot is missing for a given carrier.

[0301] This can have the following effects: 1) the external receiver may be affected by AGC, noise estimation, channel estimation. - these tasks are performed with a delay sufficient to provide a real-time indication of the WLAN interfering time slot (burst), - some filters already exist in an equalizer to compensate for the absence of an RS (reference signal), - the indication of the WLAN interfering time slot can be used by an external receiver to declare the corresponding RS as missing, if necessary, and an existing filter can then be applied, - This real-time display may include the RT coexistence interface. In summary, external receiver protection against WLAN short-term interference can be implemented through framework modifications (the implementation of RT coexistence and RT arbitration may be performed as a precondition). 2) Indoor receiver: • Transport block / code word / code block vulnerability can be difficult to evaluate; an impact or influence depends at least on a code block length and channel conditions: • In the best case, code blocks (coding blocks) can be restored by the turbo code in such a way that it has no impact on the LTE throughput, • In the worst case, a code block is similarly affected (periodically) by consecutive repeated HARQ transmissions. This would mean that the corresponding transport block would never make it through the transmission.

[0302] Typically, it is desirable to avoid the worst case. Furthermore, it may be desirable to prevent two consecutive interfering time slots in the same LTE subframe. This can be achieved, for example, by blocking two consecutive interfering Wi-Fi time slots separated by the HARQ period (e.g., 8 ms).

[0303] According to one aspect of this disclosure, trace nulling can be used to address the above points, which can be considered a frequency-domain solution. For example, it is assumed or presumed that the trace does not saturate the FFT (thus does not extend over the full bandwidth in the frequency domain): The WLAN / BT requirements for transmit interference or spurious emissions can be dimensioned accordingly. For example, frequency-domain trace detection and frequency-domain trace cancellation or signal trace cancellation can be applied.

[0304] In summary, RS filtering is based on an RT coexistence indicator (AGC, noise estimation and channel estimation protection) and / or trace detection and cancellation is applied for coexistence. Protocol mitigations

[0305] On the LTE side, several protocol mechanisms can be used to prevent conflicts between LTE and WLAN / BT activities on the communication medium: - In the absence of idle gaps, or if their number / duration is insufficient compared to WLAN / BT needs, some techniques can be applied at the protocol layer to reject some LTE subframes so that they can be used by WLAN / BT. This is referred to as LTE denial. Such techniques cannot rely on the current 3GPP specification and can be implemented autonomously at the mobile device level. However, they can be partially included in the 3GPP version 11 standard (IDC work item). Additionally, when the mobile device is within handover range, it can attempt to influence the eUTRAN to prioritize a handover to a cell with a more coexistence-friendly carrier frequency. It can also attempt to delay a handover to a less coexistence-friendly cell. This is also referred to as coexistence-friendly handover.

[0306] LTE denial can be implemented by ignoring UL grants or SR (Schedule Request) postponement. Coexistence-friendly handover can be implemented by smart reporting of measurement results from neighboring cells (values ​​and / or times).

[0307] The impact of Wi-Fi and Bluetooth use cases over LTE-FDD for full connectivity traffic support, which relies only on LTE ruler, is shown above in the Fig. 16 and Fig.17. This can be considered the worst case for the LTE-FDD side and can be used as a reference to quantify the improvements provided by the coexistence mechanism for LTE-FDD. The following assumptions were made: ◯ systematic LTE denial ◯ WLAN is operated with medium channel quality (29 Mbps PHY rate, worst case) ◯ WLAN STA (i.e. not valid for tethering).

[0308] Tables 9 and 10 also illustrate the worst-case impact of Bluetooth use case over LTE-FDD and the worst-case impact of WLAN use case over LTE-FDD (assuming full support, no LTE column). The use cases are the same as those in the Fig. 16 and Fig. 17 are illustrated. Table 9 BT traffic profiles (of usage cases) Worst case (w / o gap) Best case (w / o gap) HFP bi-directional - Master, SCO HV3 - 64Kbps+64Kbps 4 non-consecutive UL subframes over 11 (36%) Ident HFP bi-directional - Master, eSCO EV3 64kbps + 64kbps In the absence of repeated transmission, 1 UL subframe over 6 (16.6%) Ident A2DP SBC Stereo High Quality, SRC - Master, 2-DH5, 345Kbps, Period 30 ms 4 non-consecutive UL subframes per 30 ms (13.3%) Ident Table 10 WLAN traffic types (of usage cases) Worst case (w / o gap) Best case (w / o gap) WLAN beacon monitoring 2 subframes, negated every 300ms (2 / 300) Ident Skype Video - bidirectional 1Mbps 2 subframes every 20 ms (1 / 10) Ident YouTube - DL 600kbps 2 consecutive subframes every 20 ms (1 / 10) Ident TCP - DL 600kbps 1 subframe every 20 ms (1 / 20) Ident

[0309] According to one aspect of the invention, LTE denial consists of: - At the mobile device level, autonomous rejection of the use of UL subframes where LTE has allocated communication resources. This can be applied to both LTE-FDD (e.g., LTE Band 7 UL 204) and LTE-TDD (e.g., LTE Band 40 201). - At the mobile device level, autonomous rejection of the use of DL subframes where LTE has allocated communication resources. This can be applied for LTE-TDD (e.g., LTE band 40201).

[0310] It should be noted that for UL denial, cancellation / postponement of the scheduled LTE activity can be performed, while for DL ​​denial, allowing concurrent TX activity on the CWS side may be sufficient.

[0311] In the context of SR shifting, it should be noted that LTE was developed to address the needs for mobile Internet access. Internet traffic can be characterized by high bursts with high peak data rates and long idle periods. To enable battery savings, an LTE communication system (as in Fig.1) DRX. Two DRX profiles are introduced, which are addressed as Short-DRX and Long-DRX, respectively. For the reverse connection, i.e., the uplink, an LTE communication system allows discontinuous transmission (DTX) to increase system capacity. For uplink traffic, the mobile device 105 reports its uplink buffer status to the eNB 103, which then schedules and allocates uplink resource blocks (RBs) to the mobile device 105. In the case of an empty buffer, the eNB 103 cannot schedule uplink capacity, and in this case, the UE 105 is unable to report its uplink buffer status. In case the uplink buffer changes to one of its uplink queues, the UE 105 sends a so-called schedule request (SR) in order to be able to report its buffer status to a subsequent scheduled uplink shared channel (PUSCH).

[0312] To prevent this, the MAC layer of mobile device 105 can delay the SR if the DTX period has previously been granted WLAN activity. According to one aspect of this invention, this mechanism can be used for LTE-WLAN coexistence. This is described in Fig. 27 shown.

[0313] Fig. 27 shows a transmission diagram 2700.

[0314] LTE uplink transmissions are shown along a first timeline 2701, and LTE downlink transmissions are shown along a second timeline 2702. The transmissions occur, for example, between mobile device 105 and base station 103 serving mobile device 105. Time increases from left to right along timelines 2701, 2702.

[0315] In this example, mobile device 105 receives a UL grant in a first TTI 2703. Mobile device 105 responds to this UL grant by transmitting a UL signal in a second TTI 2704. At the same time, mobile device 105 sets its DRX inactivity counter. Assuming no further UL grants or DL ​​transport blocks (TBs) have been scheduled, which would cause the DRX inactivity counter to be reset to the DRX inactivity time, mobile device 105, after receiving the pending ACK of the last UL transport block, transmits that the DRX and DTX conditions are met (as indicated by arrow 2705). During the DRX and DTX period 2706, the mobile device 105 is not required to listen to any of the downlink control channels in the PDCCH, and the mobile device 105 will not be scheduled by the eNP 103 before the end of the DRX and DTX period 2706. The DRX and DTX period 2706 may be used for WLAN transfer or-Transmission can be used.

[0316] The mobile device 105 may send an SR if it is required to send some uplink data, which would terminate the DRX and DTX period 2706. To prevent this, the mobile device MAC may suppress the SR if the period is used for interfering WLAN activity.

[0317] In the example of Fig. 27, mobile device 105 receives a UL grant in the first TTI 2703. Mobile device 105 acknowledges this UL grant by transmitting a UL signal in the second TTI 2704 (four TTIs later). However, mobile device 105 can ignore the UL grant and thus reject the UL subframe that arrives four TTIs later, which is then enabled for WLAN / BT operation. The enabled subframe is indicated to CWS chip 1024 using RT coexistence interface 1026 (UL gap indication).

[0318] According to one aspect of the disclosure, LTE denial with HARQ protection is used. This is described below.

[0319] In LTE-WLAN / BT coexistence, the use of LTE denial may be required to release the LTE subframe for connectivity traffic (overriding the LTE subframe allocation). When applied in UL, LTE denial can be considered something similar to preventing the LTE transceiver 1014 from transmitting in a subframe in which it has some allocated communication resources. In this case, the characteristics of the LTE HARQ mechanism can also be considered: HARQ is a MAC-level retransmission mechanism that is synchronous and periodic with an 8 ms period (UL case; in DL, it is asynchronous).

[0320] In LTE-FDD UL, HARQ is synchronous and supports a maximum of eight processes. The potentially repeated transmission of a packet initially transmitted in subframe N thus occurs in subframes N + 8 * K, with K >= 1. Consequently, the impact of LTE denial over a transport channel can vary greatly depending on the interaction with LTE-HARQ. For example, a periodic LTE denial with an 8 ms period can affect every retry of a single HARQ process and can lead to connection losses. An example with a denial period of 12 ms is shown in Fig. 28 shown.

[0321] Fig. Figure 28 shows a transmission diagram 2800.

[0322] Along a first timeline 2801, UL subframe denials and the allocation of TTIs to HARQ processes (numbered 0 to 7) are shown. In this example, there are regular LTE denials, so processes 0 and 4 are rejected periodically (every other time).

[0323] A periodic LTE denial of a 9 ms period affects the same HARQ process only once every eight LTE denials.

[0324] Periodic rejections without considering HARQ behavior can have significant negative effects, even with a small number of rejections: They can lead to a weaker link (best case) or HARQ errors (worst case). A weak link can lead to eNodeB link adjustment, which reduces resource allocation, while HARQ errors can lead to data loss (RLC in an unacknowledged mode) or to repeated RLC transmissions with corresponding delay.

[0325] It is desirable to avoid the use of LTE denial periods, which have such a negative impact on HAQR. However, LTE denial requests can come from applications or applications / codecs on the connectivity (CWS) side, and many codecs have periodic requests. The following describes a mechanism for Smart LTE denial that enables periodic LTE denial to support application / codec requests while minimizing its impact on HARQ processes, or avoiding periodic LT denial where applicable.

[0326] For example, the following precautions can be taken when applying LT denial to minimize the impact on HARQ: - Bursty denial: Although there are no strict application / codec requirements for periodic medium access (e.g., in the case of HTTP traffic transmitted over WLAN), the rejected subframes are grouped together (in bursts or time slots of continuous-time subframes) to minimize the number of consecutive denials for a given HARQ process (i.e., denials of TTIs assigned to the same HARQ process). For example, rare burst time slots with a duration of less than 8 ms usually affect each HARQ process only once. Therefore, they are likely to be fully mitigated by HARQ. - Smart Denial: If bursty denial cannot be applied, a denial pattern is generated that minimizes the impact on HARQ while ensuring periodic requests. This pattern is designed to maximize the time interval between consecutive denials of subframes executing a given HARQ process: ◯ This approach is optimal with respect to LTE connection robustness maintenance (HARQ process protection) ◯ The periodicity requirements are met on average (the LTE denial is executed with the required period on average over the entire LTE denial pattern). The pattern contains variations in the period between two LTE denials. ◯ Avoid underflow / overflow for codec with periodic behavior.

[0327] The general pattern generation algorithm for Smart LTE denial can be, for example, the following: Requirements: • P: periodic requests (in ms) • N: Duration of the request (in ms) • W: HARQ window length (8 ms for UL)

[0328] Algorithm: • Find P1 <= P such that [(MOD(P1,W) >=N) or (MOD(P1,W)>=WN)] and (MOD(P1,W) + N) is even • If (P1 = P) continuous application of P otherwise application of K1 times P1 with K1 = W-abs(P-P1) application of K2 times P1+W with K2 = P-P1

[0329] A simple implementation example of this described algorithm is given below: • P1 = P-abs(mod(P,W)-N) • P2 = P1+W • K1 = W-(P-P1) • K2 = P-P1

[0330] An example is in Fig.28. Along a second timeline 2802, UL subframe denials and the allocation of TTIs to HARQ processes are shown, with the periods between LTE denials determined according to the above algorithm. In this case, the LTE denial pattern period P1 is applied K1 times and P2 is applied K2 times. As can be seen, this avoids periodically rejecting TTI allocations from the same HARQ process.

[0331] It should be noted that this pattern generation algorithm is applicable autonomously within the mobile device 105. It is also potentially applicable to 3GPP Release 11 IDC, where the possibility of LTE gap generation being decided at the eNodeB level is under discussion. In this case, a definition of an LTE denial pattern may be required, and the one described above may be optimal from a robustness perspective.

[0332] A mechanism for Smart VoLTE (Voice over LTE) BT-HFP coexistence is described below.

[0333] In this use case, it is assumed that mobile device 105 is connected to an earpiece via BT and a voice call is being received or transmitted over LTE (VoLTE). It is further assumed or presumed that mobile device 105 is acting as a master BT device (in other words, the BT unit of mobile device 105 is assumed to have a master role). If this is not the case, a BT role swap command can be issued.

[0334] Bluetooth communication is organized in piconets, with a single master controlling traffic allocation using 625 µs time slots. Fig. 29 shown.

[0335] Fig. 29 shows a transmission diagram 2900.

[0336] The transmission diagram shows transmission (TX) and reception (RX) by a master device, a first slave device (Slave 1), and a second slave device (Slave 2). The master has transmission capabilities for even slots, while the slaves can only transmit in odd slots (based on allocations from the master). The slaves listen to all potential master transmissions every 1.25 ms, unless they are in a sleep mode (sniff, park, hold mode) where these requests are relaxed.

[0337] For an earpiece connection, the BT units are typically paired in a low-power operating mode (e.g., a traffic exchange every 50-500 ms). When a call starts, the BT unit switches to an HFB (Handsfree Profile) profile with very frequent periodic eSCO (extended Synchronos Connection Oriented) or SCO (Synchronos Connection Oriented) traffic. This is Fig. 30 shown.

[0338] Fig. 30 shows a transmission diagram 3100, 3200.

[0339] The first transmission diagram 3001 shows eSCO communication between a master (M) and a slave (S) and the second transmission diagram 3002 shows SCO communication between the master and the slave.

[0340] Typically, as in Fig. 30, a configuration for HFP-eSCO has eight slot periods with two consecutive slots specifically designated for master and slave transmissions, followed by repeated transmission opportunities, and an SCO configuration has a six-slot period with two consecutive slots specifically designated for master and slave transmissions, followed by four idle slots, and no repeated transmission opportunity.

[0341] It should be noted that once BT devices are paired, a piconet is created, and thus a BT system clock and slot counter are enabled. For example, the odd and even slots are then determined. An attempt to synchronize the Bluetooth system clock with the LTE system clock may not be possible after a piconet is established, either by defining odd or even slots. It should also be noted that the notation TTI here refers to the LTE TTI (1 ms), and Ts refers to the BT timeslot duration (0.625 ms).

[0342] The following describes the protection provided by BT-eSCO. This applies when a Bluetooth device (e.g., implemented by the second transceiver 1018) uses the HFP profile to transmit voice to / from a headset with eSCO traffic.

[0343] Fig. 31 shows a transmission diagram 3100.

[0344] The top timeline 3101 represents VoLTE traffic in LTE-FDD UL over the air (1 ms grid). The HARQ process is synchronous with an 8 ms period and the voice codec has a 20 ms period.

[0345] Subframes with a T and an RTn designation correspond to the initial transmission of a VoLTE frame and its nth retransmission (in the sense of a HARQ retransmission). VoLTE original subframes are represented by a first hatch 3103, and potential retransmissions are represented by a second hatch 3104.

[0346] A lower timeline 3102 shows Bluetooth HFB traffic as seen from a master's perspective, based on eSCO packets. BT slots with a second hatch 3104 correspond to potential BT retransmissions according to the eSCO traffic definition.

[0347] Due to both traffic characteristics (periods and durations), applying MAC protocol synchronization can enable efficient coexistence between VoLTE and BT-HFP operation. Two different compromises are possible: a first where only the BT-HFP eSCO initial reception is protected from LTE-UL interference, and a second where both the BT-HFP eSCO initial reception and the retransmitted slot reception are protected.

[0348] The reception of original packets transmitted via a BT slave can be protected from LTE retransmissions under the following conditions: - Protection against T mod(D0, 5TTI) >= TTI- Ts or mod(D0, 5TTI) <= 5TTI-2 Ts - Protection against RT1 mod(D0, 5TTI) <= 3TTI-2 Ts or mod(D0, 5TTI) >= 4TTI - Ts - Protection against RT2 mod(D0, 5TTI) <= TTI-2 Ts or mod(D0, 5TTI) >= 2TTI - Ts - Protection against RT3 mod(D0, 5TTI) <= 4TTI- 2Ts or mod(D0, 5TTI) >= 5 TTI - Ts

[0349] The reception of packets retransmitted by the BT slave can be protected from LTE retransmission under the following conditions: - Protection against T mod(D0, 5TTI) >= 4TTI or mod(D0, 5TTI) <= 3TTI- Ts - Protection against RT1 mod(D0, 5TTI) <= TTI- Ts or mod(D0, 5TTI) >= 2TTI - Protection against RT2 mod(D0, 5TTI) <= 4TTI- Ts or mod(D0, 5TTI) >= 0 - Protection against RT3 mod(D0, 5TTI) <= 2TTI- Ts or mod(D0, 5TTI) >= 3 TTI

[0350] As a first approach for VoLTE and BT-eSCO coexistence, BT can be protected from LTE-TX, ReTX1, ReTX2, ReTX3 (i.e., protection of the first transmission and the first three retransmissions of the packet), without BT retransmission protection.

[0351] In this case, the initial BT packet exchange (1 TX slot + 1 RX slot) is protected from LTE transmissions as long as LTE does not repeat four consecutive times for the same HARQ process. BT repeated transmissions can be blocked by LTE-UL transmissions if necessary. This can be achieved by requesting the BT master to delay the initial packet transmission relative to the initial LTE subframe transmission by D0 with 2TTI-Ts <= mod(D0, 5TTS) <= 3TTI-2Ts, e.g., 1375 µs <= mod(D0, 5ms) <= 1750 µs. An example is shown in Fig. 32 shown.

[0352] The Fig. 32 shows a transmission diagram 3200.

[0353] A top-level timeline 3201 represents VoLTE traffic in LTE-FDD-UL. Subframe T and RTn designations correspond to the initial transmission of a VoLTE subframe and its nth retransmission (in the sense of HARQ retransmission). Original VoLTE subframes are represented by a first hatch 3103, and a potential retransmission is represented by a second hatch 3104.

[0354] A lower timeline 3102 shows Bluetooth HFP traffic as seen from a master's perspective and is based on eSCO packets. BT slots with a second hatch 3104 correspond to potential BT retransmissions, according to the eSCO traffic definition.

[0355] As a second approach for VoLTE and PT-eSCO coexistence, BT and BT retransmission (i.e., BT packet retransmission) can be protected from LTE-TX and ReTx1 (i.e., packet retransmission and the first retransmission of the packet). In this case, the initial BT packet exchange (1TX slot + 1RX slot) and its potential first retransmissions are protected from LTE-UL transmissions as long as the LTE system does not retransmit twice consecutively for the same HARQ process. If an LTE system retransmits more than twice, some BT transmissions / retransmissions may be blocked. This can be achieved by requesting the BT master to delay the initial packet transmission relative to the initial LTE subframe transmission by D1, where D1 = TTI-Ts. For example, mod(D1, 5ms) = 375 µs for eSCO and eSCO repeated protection against LTE-T and RT1. The transmission scenario corresponds to that described in Fig.31 is shown.

[0356] As a third approach for SVoLTE and BT-eSCO coexistence, BT can be protected from LTE-TI, ReTx1. BT repetition is not protected.

[0357] In this case, the initial BT packet exchange (1 TX slot + 1 RX slot) is protected from LTE-UL transmission as long as LTE does not retransmit twice consecutively for the same HARQ process. If LTE retransmits more than twice, some BT transmissions / retransmissions may be blocked.

[0358] This can be achieved by requesting the BT master to delay initial packet transmission relative to all initial LTE subframe transmissions to D0 with TTI-Ts <= mod (D3, 5TTI) <= 3 TTI-2Ts. For example, 375 µs <= mod (D3, 5ms) <= 1625 µs for eSCO protection from LTE-T, RT1. The transmission scenario corresponds to that in Fig. 31 shown.

[0359] As another approach, BT-SCO can be protected as follows. According to Bluetooth, the HFD profile can be used to transmit voice from / to a hands-free headset or microphone-headset combination with SCO traffic, which occupies 1 / 3 of the communication medium time and has no retransmission capability. An example is in Fig. 33 stated.

[0360] Fig. 33 shows a transmission diagram 3300.

[0361] An upper timeline 3301 represents VoLTE traffic in LTE-FDD UL. Subframes with T and RTn designations correspond to the initial transmission of a VoLTE subframe and its nth retransmissions (in the sense of HARQ retransmissions). Initial VoLTE subframes are represented by a first hatch 3103, and potential retransmissions are represented by a second hatch 3104.

[0362] A lower timeline 3102 shows Bluetooth HFP traffic from a master's perspective and based on SCO packets.

[0363] Two-thirds of the BT packet exchange (1 TX slot + 1 RX slot) is protected from LTE-UL transmissions. If some LTE retransmission occurs, it is likely that several BT slots will be blocked. This can be achieved by requiring that BT be delayed relative to the LTE active subframe start, between TTI - Ts and TTI and TTI - Ts <= mod (D2, 6Ts) <= TTI. For example, 375 µs <= mod (D2, 3.75 µs) <= 1 ms for minimal LTE VoLTE interference via SCO traffic. If D2 is not within this range, then two-thirds of the SCO packets may be blocked by VoLTE subframe transmissions.

[0364] In summary, the delays or range of delays between VoLTE Tx and BT Master Tx identified above (which can be considered an optimum) provide a minimal collision probability between VoLTE subframe transmissions and BT HFP packet receptions. The delay requirements are derived from an eSCO packet usage for BT HFP profiles or from an SCO packet usage, respectively.

[0365] The use of eSCO packets may be desirable because they coexist much better with the VoLTE traffic pattern. When SCO is used, one-third of the BT packets are lost due to collisions with VoLTE UL subframes, and this cannot be resolved by LTE denial for this frame because the effect on call quality would be worse (20 µs losses versus 5 µs losses).

[0366] Among eSCO solutions, the third approach may be desirable because: - it is sufficient to completely protect the initial BT reception, - its delay requirements are relatively low (2xBT T-slots); this can be evaluated in case of an LTE handover during the call.

[0367] A possible concept could be the following: A) Establish a call 1) BT pairing, which typically takes place before a VoLTE connection is established, without any concrete coexistence restrictions. 2) Once the LTE connection (LTE call) is established, information from the periodically allocated subframes (SPS-based) is passed to the BT and added to NRT messages. This is available, for example, 5-10 ms after the SPS pattern is applied. 3) The BT master then interprets the PLC indication message (period, duration, offset) and uses the LTE frame sync RT signal as a sync reference.

[0368] Once the eSCO / SCO traffic is established, the BT master allocates the BT slots that meet the delay requirements related to VoLTE transmissions (which is always possible since for the third approach the delay is 2xT-slot). B) LTE handover

[0369] When LTE performs a handover during a VoLTE call from a first cell to a second cell, the LTE system clock in the first cell may differ in phase from the LTE system clock in the second cell (or second sector). A SPS allocation may also be different. As a consequence, the delay between BT and VoLTE traffic patterns may no longer be met: 1) Handover and new PLC allocation can then be made available to BT via NRT messages. 2) The BT master can change the BT slot allocation for the eSCO traffic to meet the delay requirement again (always only possible with the third approach described above).

[0370] It should be noted that due to the lack of a timestamping mechanism, it may not yet be guaranteed that BT can directly derive VoLTE subframe positions from the indication in NRT messages. If not, the BT unit can detect them by monitoring the LTE UL gap envelope (RT interface), which uses the SPS period information. Since it can take several VoLTE cycles to achieve VoLTE sync in this way, BT can have a blind eSCO schedule at startup and reschedule it once the VoLTE subframe has been identified.

[0371] This mechanism, at 20 ms, can be considered optimized for VoLTE. However, it can be used for any SPS-based LTE traffic. Only the delay requirements may need to be adjusted.

[0372] In summary, for LTE-WLAN / BT coexistence in the context of protocol mitigation, the following can be provided / implemented: - Coexistence-friendly handover - SR shift - ignoring UL grant - LTE denial control (algorithm with packet error rate monitoring) - Minimizing the impact of LTE denial via LTE-HARQ and thus on LTE connection robustness (e.g., through an appropriate algorithm) - Minimize the impact on BT HFD traffic over VoLTE traffic

[0373] According to one aspect of the present invention, a wireless communication device as in Fig. 34, provided.

[0374] Fig. 34 shows a wireless communication device 3400.

[0375] The wireless communication device 3400 includes a first transceiver 3401 configured to transmit and receive signals in accordance with a wireless wide area communication technology and a second transceiver 3402 configured to transmit and receive signals in accordance with a wireless short range communication technology or a wireless metropolitan area system communication technology.

[0376] The wireless communication device 3400 further includes a processor 3403 configured to at least partially synchronize the reception or transmission of signals from the first transceiver 3401 with the reception or transmission of signals from the second transceiver 3402, such that at least a portion of the reception and / or transmission of signals of the first transceiver and the second transceiver is performed at the same time.

[0377] It should be noted that although a connection of the first transceiver 3401 and the second transceiver 3402 via the processor 3403 is shown, the first transceiver 3401 and the second transceiver 3402 may also be connected directly.

[0378] The processor may be configured to control the second transceiver to at least partially synchronize the receiving or transmitting of signals of the first transceiver with the receiving or transmitting of signals of the second transceiver depending on a receiving and transmitting scheduling of the first transceiver.

[0379] The processor may be configured to control the second transceiver to at least partially synchronize receiving or transmitting signals of the first transceiver with receiving or transmitting signals of the second transceiver depending on a receive and transmit (or transmit) time division duplex frame for the first transceiver.

[0380] The processor may be configured to control the second transceiver to at least partially synchronize the receiving or transmitting of signals of the first transceiver with the receiving or transmitting of signals of the second transceiver depending on a received transmit (or transmit) gap indication and / or a received receive gap indication.

[0381] For example, the received transmission gap indication includes a received measurement gap indication or a received discontinuous transmission indication.

[0382] For example, the received gap reception indication includes a received discontinuous reception indication.

[0383] The first transceiver may be configured to transmit and receive signals according to a third generation wireless partnership project communication technology.

[0384] The first transceiver may be configured to transmit and receive signals according to a 4G wireless communication technology.

[0385] For example, the first transceiver is configured to transmit and receive signals according to a wireless Long Term Evolution communication technology.

[0386] The second transceiver may be configured to transmit and receive signals according to a short-range wireless communication technology selected from a group consisting of: wireless Bluetooth communication technology; wireless Ultra Wide Band communication technology; short-range wireless network communication technology; wireless infrared data association communication technology; wireless Z-Wave communication technology; wireless ZigBee communication technology; wireless high-performance radio LAN communication technology; IEEE 802.11 wireless communication technology; and Digital Enhanced Cordless wireless Communication technology.

[0387] The second transceiver may be configured to transmit and receive signals according to a wireless metropolitan area system communication technology selected from a group consisting of: wireless Worldwide Interoperability for Microwave Access communications technology; WiPro wireless communication technology; wireless High Performance Radio Metropolitan Area System communications technology; and wireless 802.16m Advanced Air Interface Communication technology.

[0388] The processor may be configured to control the first transceiver and the second transceiver to at least partially synchronize the receiving or transmitting of signals of the first transceiver with the receiving or transmitting of signals of the second transceiver depending on a previously received activity schedule indication for the first transceiver and / or second transceiver.

[0389] The processor may be configured to detect a conflict in receiving or transmitting signals of the first transceiver and the second transceiver, and to select the first transceiver or the second transceiver to transmit a signal.

[0390] For example, the processor is configured to select the first transceiver or the second transceiver to transmit a signal, taking into account a periodicity of a provided hybrid automatic repetition request.

[0391] The processor may further be configured to determine a reception and / or transmission (or transmission) behavior of the first transceiver and / or the second transceiver, and to take the determined information into account in the at least partial synchronization of the reception or transmission of signals of the first transceiver with the reception or transmission of signals of the second transceiver.

[0392] According to one aspect of the disclosure, a wireless communication device as described in Fig. 35, provided.

[0393] Fig. 35 shows a wireless communication device 3500.

[0394] The wireless communication device 3500 includes a first transceiver 3501 configured to transmit and receive signals according to a cellular wireless wide area communication technology; and a second transceiver 3502 configured to transmit and receive signals according to a short-range wireless communication technology or a wireless metropolitan area system communication technology.

[0395] The wireless communication device 3500 further includes a processor 3503 configured to control the transmission behavior and / or the reception behavior of the second transceiver depending on periods during which the first transceiver is idle, or to control the transmission behavior and / or the reception behavior of the first transceiver depending on periods during which the second transceiver is in the idle state.

[0396] It should be noted that although a connection of the first transceiver 3501 and the second transceiver 3502 via the processor 3503 is shown, the first transceiver 3501 and the second transceiver 3502 may also be connected directly.

[0397] The processor may be configured to control the transmission behavior and / or the reception behavior of the second transceiver depending on a reception schedule or transmission schedule for the first transceiver or to control the transmission behavior and / or the reception behavior of the second transceiver depending on a reception schedule or transmission schedule for the second transceiver.

[0398] The processor may be configured to control the transmission behavior and / or the reception behavior of the second transceiver depending on a reception and transmission time-division duplex frame for the first transceiver, or to control the transmission behavior and / or the reception behavior of the first transceiver depending on a reception and transmission time-division duplex frame for the second transceiver.

[0399] For example, the processor is configured to control the transmission behavior and / or the reception behavior of the second transceiver depending on a received transmission gap indication and / or received reception gap indication.

[0400] For example, the received transmission gap indication includes a receive measurement gap indication or a received discontinuous transmission indication.

[0401] For example, the received receive gap indication includes a received discontinuous receive indication.

[0402] The first transceiver may be configured to transmit and receive signals according to a Wireless Third Generation Partnership Project communication technology.

[0403] The first transceiver may be configured to transmit and receive signals according to a 4G wireless communication technology.

[0404] For example, the first transceiver is configured to transmit and receive signals according to a wireless long-term evolution communication technology.

[0405] The second transceiver may be configured to transmit and receive signals according to a short-range wireless communication technology selected from a group consisting of: wireless Bluetooth communication technology; wireless Ultra Wide Band communication technology; short-range wireless network communication technology; wireless infrared data association communication technology; wireless Z-Wave communication technology; wireless ZigBee communication technology; wireless high-performance radio LAN communication technology; IEEE 802.11 wireless communication technology; and Digital Enhanced Cordless wireless Communication technology.

[0406] The second transceiver may be configured to transmit and receive signals according to a wireless metropolitan area system communication technology selected from a group consisting of: wireless Worldwide Interoperability for Microwave Access communications technology; WiPro wireless communication technology; wireless High Performance Radio Metropolitan Area System communications technology; and wireless 802.16m Advanced Air Interface communication technology.

[0407] The processor may be configured to control the transmission behavior and / or the reception behavior of the second transceiver depending on a previously received activity schedule indication for the first transceiver and / or second transceiver.

[0408] The processor may be configured to detect a conflict in receiving or transmitting signals of the first transceiver and the second transceiver, and to select the first transceiver or the second transceiver to transmit a signal.

[0409] For example, the processor is configured to select the first transceiver or the second transceiver to transmit a signal, taking into account a periodicity of a provided hybrid automatic repetition request.

[0410] The processor may be further configured to determine whether the first transceiver or the second transceiver is in the idle state.

[0411] According to one aspect of the invention, a method for operating the wireless communication device as described in Fig. presented, made available.

[0412] Fig. 36 shows a flowchart 3600. In 3601, a first transceiver transmits and receives signals in accordance with a wireless wide area communication technology.

[0413] In 3602, a second transceiver transmits and receives signals in accordance with a short-range wireless communication technology or a metropolitan area system wireless communication technology.

[0414] In 3603, the receiving or transmitting of signals of the first transceiver is at least partially synchronized with the receiving or transmitting of signals of the second transceiver such that at least a portion of the receiving and / or a portion of the transmitting of signals of the first transceiver and the second transceiver is performed simultaneously.

[0415] The second transceiver may be controlled to at least partially synchronize receiving or transmitting signals of the first transceiver with receiving or transmitting signals from the second transceiver depending on a receive schedule or transmit schedule for the first transceiver.

[0416] The second transceiver may be controlled to at least partially synchronize receiving or transmitting signals of the first transceiver with receiving or transmitting signals from the second transceiver in accordance with a receive and transmit time division duplex frame for the first transceiver.

[0417] The second transceiver may be controlled to at least partially synchronize receiving or transmitting signals of the first transceiver with receiving or transmitting signals from the second transceiver depending on a received transmit gap indication and / or received receive gap indication.

[0418] For example, the received transmission gap indication includes a received measurement gap indication or a received discontinuous transmission indication.

[0419] For example, the received receive gap indication includes a received discontinuous receive indication.

[0420] The first transceiver can transmit and receive signals according to a third-generation wireless partnership project communication technology.

[0421] The first transceiver can transmit and receive signals according to a 4G wireless communication technology.

[0422] For example, the first transceiver transmits and receives signals according to a wireless Long Term Evolution communication technology.

[0423] The second transceiver can transmit and receive signals according to a short-range wireless communication technology selected from a group consisting of: wireless Bluetooth communication technology; wireless ULtra Wide Band communication technology; short-range wireless network communication technology; wireless infrared data association communication technology; wireless Z-Wave communication technology; wireless ZigBee communication technology; wireless high-performance radio LAN communication technology; IEEE 802.11 wireless communication technology; and Digital Enhanced Cordless wireless Communication technology.

[0424] The second transceiver is capable of transmitting and receiving signals in accordance with a wireless metropolitan area system communication technology selected from a group consisting of: wireless Worldwide Interoperability for Microwave Access communications technology; WiPro wireless communication technology; wireless High Performance Radio Metropolitan Area System communications technology; and wireless 802.16m Advanced Air Interface communication technology.

[0425] The first transceiver and the second transceiver may be controlled to at least partially synchronize the receiving or transmitting of signals of the first transceiver with the receiving or transmitting of signals of the second transceiver depending on a previously received activity schedule indication for the first transceiver and / or second transceiver.

[0426] The method may further include determining a conflict in receiving or transmitting signals between the first transceiver and the second transceiver; and selecting the first transceiver or the second transceiver to transmit a signal.

[0427] For example, selecting the first transceiver or the second transceiver to transmit a signal may be performed taking into account a periodicity of a provided hybrid automatic repetition request.

[0428] The method may, for example, further include determining a reception and / or transmission behavior of the first transceiver and / or the second transceiver; and taking the determined information into account when at least partially synchronizing the reception or transmission of signals of the first transceiver with the reception or transmission of signals of the second transceiver.

[0429] According to one embodiment, a wireless method for operating a communication device as described in Fig. 37, provided.

[0430] In 3701, a first transceiver transmits and receives signals according to a wireless wide area communication technology.

[0431] In 3702, a second transceiver transmits and receives signals according to a short-range wireless communication technology or a metropolitan area system wireless communication technology.

[0432] In 3703, at least one reception and / or transmission behavior of the second transceiver is controlled depending on periods during which the first transceiver is in the idle state, or the transmission behavior and / or the reception behavior of the first transceiver are controlled depending on periods during which the second transceiver is idle.

[0433] The transmission behavior and / or reception behavior of the second transceiver are controlled depending on a reception schedule and transmission schedule for the first transceiver or the transmission behavior and / or reception behavior of the second transceiver are controlled depending on a reception schedule or transmission schedule for the second transceiver.

[0434] The transmission behavior and / or the reception behavior of the second transceiver are controlled depending on a reception and transmission time-division duplex frame for the first transceiver, or the transmission behavior and / or the reception behavior of the first transceiver are controlled depending on a reception and transmission time-division duplex frame for the second transceiver.

[0435] For example, the transmission behavior and / or the reception behavior of the second transceiver are controlled depending on a received transmission gap indication and / or received reception gap indication.

[0436] For example, the received transmission gap indication includes a received measurement gap indication or a received discontinuous transmission indication.

[0437] For example, the received gap reception indication includes a received discontinuous reception indication.

[0438] The first transceiver can transmit and receive signals according to a third-generation wireless partnership project communication technology.

[0439] The first transceiver can transmit and receive signals according to a 4G wireless communication technology.

[0440] For example, the first transceiver transmits and receives signals according to a wireless Long Term Evolution communication technology.

[0441] The second transceiver can transmit and receive signals according to a short-range wireless communication technology selected from a group consisting of: wireless Bluetooth communication technology; wireless Ultra Wide Band communication technology; short-range wireless network communication technology; wireless infrared data association communication technology; wireless Z-Wave communication technology; wireless ZigBee communication technology; wireless high-performance radio LAN communication technology; IEEE 802.11 wireless communication technology; and Digital Enhanced Cordless wireless Communication technology.

[0442] The second transceiver can transmit and receive signals according to a wireless metropolitan area system communication technology selected from a group consisting of: wireless Worldwide Interoperability for Microwave Access communications technology; WiPro wireless communication technology; wireless High Performance Radio Metropolitan Area System communications technology; and wireless 802.16m Advanced Air Interface Communication technology.

[0443] The transmission behavior and / or the reception behavior of the second transceiver are controlled depending on a received transmission gap indication for the first transceiver and / or the second transceiver.

[0444] The method may further include determining a conflict in receiving or transmitting signals between the first transceiver and the second transceiver and selecting the first transceiver or the second transceiver to transmit a signal.

[0445] For example, the first transceiver or the second transceiver is selected to transmit a signal taking into account a periodicity of a provided hybrid automatic repetition request.

[0446] The method may further include determining whether the first transceiver or the second transceiver is in the idle state.

[0447] According to one aspect of the disclosure, a wireless communication device is provided in Fig. 38 is provided.

[0448] Fig. 38 shows a wireless communication device 3800.

[0449] The wireless communication device 3800 includes a transceiver 3801 configured to transmit and receive signals according to a cellular wireless wide area communication technology and a receiver 3802 configured to receive signals according to a satellite positioning technology.

[0450] The wireless communication device 3800 further includes a processor 3803 configured to at least partially synchronize the receiving of signals from the transceiver with the receiving of signals from the receiver such that at least a portion of the receiving of the signals from the transceiver and the receiver is performed at the same time.

[0451] It should be noted that although a connection of the transceiver 3801 and the receiver 3802 via the processor 3803 is shown, the transceiver 3801 and the receiver 3802 may also be connected directly.

[0452] The receiver may be configured to receive signals according to a global positioning technology.

[0453] According to one aspect of the invention, a method for operating a wireless communication device as described in Fig. 39, provided.

[0454] In 3901, a transceiver transmits and receives signals in accordance with a wireless wide area communication technology.

[0455] In 3902, a receiver receives signals in accordance with a satellite positioning technology.

[0456] In 3903, a processor at least partially synchronizes receiving signals from the transceivers with receiving signals from the receiver such that at least a portion of receiving the signals from the transceivers and the receiver are performed concurrently.

[0457] The receiver can receive signals in accordance with a global positioning technology.

[0458] According to one aspect of the disclosure, a wireless communication device as described in Fig. 40 shown, provided.

[0459] Fig. 40 shows a wireless communication device 4000.

[0460] The wireless communication device 4000 includes a transceiver 4001 configured to transmit and receive signals according to a cellular wireless wide area communication technology and a receiver 4002 configured to receive signals according to a satellite positioning technology.

[0461] The wireless communication device 4000 further includes a processor 4003 configured to control the reception behavior of the receiver depending on time intervals during which the transceiver is in the idle state.

[0462] It should be noted that although a connection of the transceiver 4001 and the receiver 4002 via the processor 4003 is shown, the transceiver 4001 and the receiver 4002 may also be connected directly.

[0463] The receiver may be configured to receive signals according to a global positioning technology.

[0464] According to one aspect of the disclosure, a method for operating a wireless communication device as described in Fig. presented, made available.

[0465] Fig. 41 shows a flowchart 4100.

[0466] In 4101, a transceiver transmits and receives signals in accordance with a cellular wireless wide area communication technology.

[0467] In 4102, a receiver receives signals according to a satellite positioning technology.

[0468] In 4103, a processor controls the reception behavior of the receiver depending on time intervals during which the transceiver is in idle state.

[0469] For example, the receiver can receive signals according to a global positioning technology.

[0470] According to various aspects of the disclosure, the transmission and reception behavior of transceivers according to different wireless communication technologies can be synchronized with each other so that both transceivers transmit or receive signals at the same time. This can reduce interference from adjacent frequency bands used by transceivers of different wireless communication technologies (e.g., by a cellular wireless wide area communication technology transceiver and by a wireless short range communication technology transceiver or a wireless metropolitan area system communication technology transceiver).

[0471] Furthermore, it can be determined when a transceiver is in an idle state, and this information can be used to control the other transceivers to transmit signals during the transceivers' idle time.

[0472] In the wireless communication devices 3400, 3500, 3800, 4000, the (first) transceiver corresponds, for example, to the LTE subsystem 2101, and the second transceiver corresponds, for example, to the WLAN / Bluetooth communication circuit 2102. The processor may correspond to a corresponding controller of one of these communication modules. For example, the processor may correspond to the communication circuit 2104. The processor may, for example, correspond to (or include) the RT arbitration unit 2111. Alternatively, each of the corresponding tasks may be performed by the application processor 2105.

[0473] Further examples of LTE / BT / Wi-Fi coexistence are given below.

[0474] The NRT arbiter 2108 uses a mix of application requests (from the connectivity and LTE apps) and context information from both cores, i.e., LTE and Bluetooth or Wi-Fi (e.g., band, bandwidth, EARFCN), for arbitration and displays static information, such as selected frequency bands or selected power levels, of the LTE and connectivity (i.e., Bluetooth or Wi-Fi). It can also provide indications to the RT arbiter located in the LTE subsystem.

[0475] For example, the NRT arbiter 2108 does not arbitrate between WLAN and BT (arbitration between them is performed, for example, by the connectivity chip).

[0476] When the LTE subsystem camps in a new cell, the LTE software indicates new LTE information to the NRT arbiter 2108, and this information is stored to be reused in the NRT algorithm, e.g., according to 2407, 2408, 2410.

[0477] The NRT arbiter can then execute an NRT algorithm to protect BT from LTE-FDD.

[0478] The algorithm is executed in the NRT arbitration unit 2108. It is split into two subroutines: Subroutine 1 is activated each time the LTE subsystem 2101 is deployed in a new cell while BT is active (BT status is indicated separately via the NRT coexistence interface, for example). It determines the frequency range in which BT can safely coexist with LTE under worst-case conditions. Subroutine 1 is in Fig. 42 shown.

[0479] Fig. 42 shows a message flow diagram 4200.

[0480] The message flow takes place between an NRT arbiter 4201, which corresponds to the NRT arbiter 2108, and the BT communication circuit 4202, which corresponds to the WLAN / BT communication circuit 2102.

[0481] In 4203, the NRT arbiter 4201 loads parameters from a non-volatile memory. These can be the parameters LaNT (antenna isolation) between LTE-Tx and WLAN-BT-Rx, P_LTE_max (maximum power of LTE), Nmin, required minimum number of BT channels to apply AFH, BT_max_PSD (in dBm / MHz) (maximum BT spectral power density), BT_MAX_BLKR (BT maximum tolerable block interference), BT_MAX_LIN (BT maximum tolerable in-band noise), L_OOB () (LTE transmitter out-of-band spectrum (relative to in-band power)) and ISM RX filter waveform parameters (e.g., Band7Filter(,1) (or RxFilter(,1)).

[0482] In 4204, the NRT arbiter 4201 calculates BT_SAFE_RX_FREQ_MIN and BT_SAFE_RX_FREQ_MAX based on: - LTE band - BT max tolerable block interference - BT max tolerable in-band interference - LTE frequency - ISM-RX filter curve shape - LTE Tx OOB noise - Antenna isolation

[0483] BT_SAFE_RX_FREQ_MIN, BT_SAFE_RX_FREQ_MAX specify the ISM frequency range (1 MHz accuracy) that meets the converging (parallel) worst-case objectives (de-sense, throughput loss) (LTE max power, max bandwidth, BT-RX@sensitivity). These are static, so they can be precalculated and stored in a lookup table.

[0484] In 4205, the NRT arbiter 4201 sends or communicates BC_SAFE_RX_FREQ_MIN and BT_SAFE_RX_FREQ_MAX to the BT communication circuit 4202.

[0485] In 4206, the BT communication circuit 4202 stores BT_SAFE_RX_FREQ_MIN BT_SAFE_RX_FREQ_MAX and confirms the receipt of these parameters in 4207. Subroutine 2 is in Fig. 43 shown.

[0486] Fig. 43 shows a message flow diagram 4300.

[0487] The message flow takes place between an NRT arbiter 4301, which corresponds to the NRT arbiter 2108, and the BT communication circuit 4302, which corresponds to the WLAN / BT communication circuit 2102.

[0488] Subroutine 2 is activated each time the BT communication circuit 4302 modifies its AFH plan or AFH network plan in 4303.

[0489] This modification can, for example, be performed autonomously on the BT side, either for traffic purposes or for coexistence purposes.

[0490] In 4304, the BT communication circuit 4302 stores the minimum BT frequency and the maximum BT frequency according to the changed AFH plan.

[0491] In 4305, the BT core (i.e., the BT communication circuit 4302) checks whether its complete AFH plan is contained within the protected frequency range and indicates the result to the NRT arbiter 4301 (in this example, using a single-bit indication) in 4306. If the information is received, the NRT arbiter 4301 enables / disables the real-time interface (or a subset of the real interface, allowing a distinction between BT and WLAN) in 4307 and sends an acknowledgment to the BT communication circuit 4302 in 4308.

[0492] In case there is no way to distinguish between WiFi and BT, the parameters BT_RX_KILL and WIFI_RX_KILL (see Fig. 45) both are off, and then the real-time interface is off. Otherwise, the real-time interface is on.

[0493] In addition, the NRT arbiter can execute an NRT algorithm to protect Wi-Fi from LTE-FDD.

[0494] The algorithm is executed in the NRT arbitration unit 2108. It is divided into two subroutines: Subroutine 1 is activated each time the LTE subsystem 2101 is deployed in a new cell while WLAN is active (the WLAN status is indicated separately via the NRT coexistence interface, for example). It determines the frequency range in which WLAN can be safely operated together with LTE. Subroutine 1 is in Fig. 42 shown.

[0495] Fig. 44 shows a message flow diagram 4400.

[0496] The message flow takes place between an NRT arbiter 4401, which corresponds to the NRT arbiter 2108, and a WLAN communication circuit 4402, which corresponds to the WLAN / BT communication circuit 2102.

[0497] In 4403, the NRT arbiter 4401 loads parameters from a non-volatile memory. These can be the parameters Lant (antenna isolation) between LTE-Tx and WLAN / BT-Rx, P_LTE_max (maximum power of LTE), WLAN_max_PST (maximum WLAN power spectral density), WLAN_MAX_BLKR (WLAN maximum tolerable block interference), WLAN_MAX_LIN (WLAN maximum tolerable in-band jamming interference), L_OOB () (contains LTE transmitter out-of-band spectrum (relative to in-band power)) and ISM RX filter waveform parameters (e.g., Band7Filter)(,BW) (or Rx Filtr(,BW)). Band7Filter(,BW) is the ISM RX filter waveform integrated over the LTE cell BW. Five Band7Filter tables are stored in the NVM corresponding to BW = 1, 5, 10, 15, 20 MHz.

[0498] In 4404, the NRT arbiter 4401 calculates WLAN_SAFE_RX_FREQ_MIN and WLAN_SAFE_RX_FREQ_MAX based on: - LTE band - WLAN max tolerable block interference - WLAN max tolerable IN-band interference - LTE FREQ - ISM RX filter curve shape - LTE Tx OOB noise - Antenna isolation

[0499] WLAN_SAFE_RX_FREQ_MIN and WLAN_SAFE_RX_FREQ_MAX specify the ISM frequency range (1 MHz accuracy) that satisfies the converging (parallel) objectives (de-sense, throughput losses) in the worst case (LTE maximum power, maximum bandwidth, WLAN RX@ sensitivity). These are static, so they can be precalculated and stored in lookup tables.

[0500] In 4405, the NRT arbiter 4401 communicates or sends WLAN_SAFE_RX_FREQ_MIN and WLAN_SAFE_RX_FREQ_MAX to the WLAN communication circuit 4402.

[0501] In 4406, the WLAN communication circuit 4402 stores WLAN_SAFE_RX_FREQ_MIN WLAN_SAFE_RX_FREQ_MAX and confirms the receipt of these parameters in 4407. Subroutine 2 is in Fig. 45 shown.

[0502] Fig. 45 shows a message flow diagram 4500.

[0503] The message flow takes place between an NRT arbiter 4501, which corresponds to the NRT arbiter 2108, and a WLAN communication circuit 4502, which corresponds to the WLAN / BT communication circuit 2102.

[0504] Subroutine 2 is activated each time the WLAN communication circuit 4502 modifies its list of active WLAN channels in 4503.

[0505] This modification can be performed autonomously on the WLAN side, either for traffic purposes or for coexistence purposes.

[0506] In 4504, the WLAN communication circuit 4502 then stores the minimum WLAN frequency and the maximum WLAN frequency according to the changed list of active WLAN channels.

[0507] In 4505, the WLAN core (i.e., the WLAN communication circuit 4502) checks whether its WLAN channels are in the secure frequency range and indicates the result to the NRT arbiter 4501 (in this case by means of a single-bit indication) in 4506. If the information is received, the NRT arbiter 4501 switches the real-time interface (or a subset of the real interface if a distinction between BT and WLAN is possible) on / off in 4507 and sends an acknowledgment to the WLAN communication circuit 4502 in 4508. In case no distinction can be made between WiFi and BT in any way, the parameters BT_RX_KILL (see Fig. 45) and WiFi_RX_KILL are both disabled, and then the real-time interface is disabled. Otherwise, the real-time interface is enabled.

[0508] Further examples of the non-real-time application interface, the non-real-time coexistence interface, and parameters stored in non-volatile memory are given below.

[0509] The NRT application interface sends messages containing application information about connectivity and LTE applications. The "I / O" field has the following meaning for parameters: "I" means from AP to NRTA, "O" means from NRTA to AP. Table 11: Non-real-time application coexistence interface parameter Info Bits I / O Description PERIOD 16 I / O Required application service duration ms. Overwrite any previous usage DURATION 6 I / O Required application service duration ms. Overwrite any previous usage

[0510] The NRT coexistence interface sends notifications containing CWS information. The "I / O" field has the following meaning for the parameters: "I" means from CWS to NRTA, "O" means from NRTA to CWS. Table 12: Non-real-time coexistence interface parameter Info Bits I / O Description WLAN_ACTIVE 1 I NRT controller is switched on by this display -> Replaces IS_COEX previously in NRT Apps I / F WLAN_SAFE_RX 1 I Indicates that Wi-Fi operation is within the safe frequency range. (Used to disable the RT-I / F or the Wi-Fi portion of it) WLAN_BANDWIDTH 2 I WLAN bandwidth 0 = 20MHz, 1 = 40MHz, 2 = 80MHz, 3 = Invalid BT_ACTIVE 1 I NRT controller is switched on by this display -> Replaces IS_COEX previously in NRT Apps I / F BT_SAFE_RX 1 I Indicates that BT operation is within the safe frequency range. (Used to disable the RT-I / F or the BT portion thereof) LTE_ACTIVE 1 O Used by CWS -> Indication for CWS that the restrictions running with LTE are released WLAN_LTE_EN 1 O Transmission of WLAN packets shorter than 2 LTE-OFDM symbols For future use: LTE-TDD only LTE_SPS_PATTER N 24 O PLC periodicity (ms): 11 bits PLC event duration (ms): 9 bits SPS initial offset (subframe offset in the first LTE frame where SPS is applied): 4 bits TBC: Displays periodic LTE activity for the connectivity chip, which can then evaluate it for its own planning purposes. LTE_BITMAP 10x2 O 0 = Special subframe 1 = RX LTE subframe 2 = TX LTE subframe For future reference: Display of LTE-TDD frame structure for the connectivity cores. WLAN_SAFE_RX_F REQ MIN 12 O Lower limit of the frequency range where WLAN can receive during LTE-Tx (worst case, static approach) in MHz WLAN_SAFE_RX_F REQ MAX 12 O Upper limit of the frequency range where WLAN can receive during LTE-Tx (worst case, static approach) in MHz BT_SAFE_RX_FRE Q MIN 12 O Lower limit of the frequency range where BT can receive during LTE-Tx (worst case, static approach) in MHz BT_SAFE_RX_FRE Q_MAX 12 O Upper limit of the frequency range where BT can receive during LTE-Tx (worst case, static approach) in MHz WLAN_TX_POWER 4 I / O WLAN Tx power (applied or applicable) For future use (LTE-TDD). For use by NRT controllers to evaluate Wi-Fi interference over LTE (useful in tethering cases where Wi-Fi transmit power may be reduced).

[0511] The following table lists examples of parameters used in non-volatile memory. Table 13: NVM parameters NVM parameters NRT_capability BT_Max_PSD BT_channel_freq Nmin P_LTE_max L_OOB Band7Filter Land

[0512] While the invention has been particularly shown and described with reference to specific aspects, it should be understood by those skilled in the art that various changes in form and detail may be made without departing from the spirit and scope of the invention as defined by the appended claims. The scope of the invention is therefore indicated by the appended claims, and all changes which come within the meaning and range of equivalence of the claims are therefore intended to be embraced.

Claims

[1] A wireless device comprising: a Bluetooth transceiver configured to transmit or receive Bluetooth signals with a peer Bluetooth transceiver; and a Bluetooth controller, trained to: Obtaining a Long-Term Evolution, LTE, signal transceiver pattern of an LTE transceiver; and based on the LTE signal transceiver pattern of the LTE transceiver: based on a desensitization target, aligning the transmission of Bluetooth signals by the Bluetooth transceiver so that they occur within an uplink duration of the LTE transceiver, or based on a desensitization target, aligning the reception of Bluetooth signals by the Bluetooth transceiver so that they occur within a downlink duration of the LTE transceiver. [2] The wireless device of claim 1, wherein the LTE transceiver is an eNodeB. [3] The wireless device according to claim 1 or 2, further comprising: a second LTE transceiver; and an LTE controller configured to provide the LTE signal transceiver pattern to the second LTE transceiver. [4] The wireless device according to any one of the preceding claims, wherein the Bluetooth signal transmission by the Bluetooth transceiver occurs during the uplink duration of the LTE transceiver. [5] The wireless device according to any one of the preceding claims, wherein Bluetooth data reception by the Bluetooth transceiver occurs during the downlink duration of the LTE transceiver. [6] The wireless device according to any one of the preceding claims, wherein interference between the Bluetooth transceiver and the LTE transceiver is reduced. [7] A method for performing wireless communication by a wireless device, the method comprising: Sending or receiving, by a Bluetooth transceiver, Bluetooth signals with a peer Bluetooth transceiver; Obtaining, through a Bluetooth controller, a Long-Term Evolution, LTE, signal transceiver pattern of an LTE transceiver; and based on the LTE signal transceiver pattern of the LTE transceiver: based on a desensitization target, aligning by the Bluetooth controller, sending the Bluetooth signals so that they occur within an uplink duration of the LTE transceiver, or based on a desensitization target, aligning by the Bluetooth controller, receiving the Bluetooth signals so that they occur within a downlink duration of the LTE transceiver. [8] The method of claim 7, wherein the LTE transceiver is an eNodeB. [9] The method of claim 7 or 8, wherein the transmitting of the Bluetooth signals by the Bluetooth transceiver occurs during the uplink duration of the LTE transceiver. [10] The method according to any one of claims 7 to 9, wherein receiving the Bluetooth signals by the Bluetooth transceiver occurs during a downlink duration of the LTE transceiver. [11] The method according to any one of claims 7 to 10, wherein interference between the Bluetooth transceiver and the LTE transceiver is reduced. [12] A non-transitory computer-readable medium comprising program instructions for causing a computer to perform the method of any one of claims 7 to 11. [13] A wireless device comprising: a Bluetooth transceiver configured to transmit or receive Bluetooth signals with a peer Bluetooth transceiver; and a Bluetooth controller, trained to: Obtaining an uplink or downlink signal pattern of a Long-Term Evolution (LTE) network, and based on a desensitization target, aligning the transmission of Bluetooth signals by the Bluetooth transceiver with the uplink signal pattern of the LTE network, or aligning the reception of Bluetooth signals by the Bluetooth transceiver with the downlink signal pattern of the LTE network. [14] The wireless device of claim 13, wherein the Bluetooth signal transmission by the Bluetooth transceiver occurs within a duration of the uplink LTE signal pattern of the LTE network. [15] The wireless device of claim 13 or 14, wherein the Bluetooth signal reception by the Bluetooth transceiver occurs within a duration of the downlink LTE signal pattern of the LTE network. [16] The wireless device according to any one of claims 13 to 15, wherein interference between the Bluetooth transceiver and the LTE network is reduced. [17] A method for performing wireless communication by a wireless device, the method comprising: Sending or receiving, by a Bluetooth transceiver, Bluetooth signals with a peer Bluetooth transceiver; Obtaining, through a Bluetooth controller, an uplink or downlink signal pattern of a Long-Term Evolution (LTE) network; and based on a desensitization target, aligning, by the Bluetooth controller, the transmission of the Bluetooth signals by the Bluetooth transceiver with the uplink LTE signal pattern of the LTE network, or aligning, by the Bluetooth controller, the reception of the Bluetooth signals by the Bluetooth transceiver with the downlink LTE signal pattern of the LTE network. [18] The method of claim 17, wherein the Bluetooth signal transmission by the Bluetooth transceiver occurs within a duration of the uplink LTE signal pattern of the LTE network. [19] The method of claim 17 or 18, wherein the Bluetooth signal reception by the Bluetooth transceiver occurs within a duration of the downlink LTE signal pattern of the LTE network. [20] The method according to any one of claims 17 to 19, wherein interference between the Bluetooth transceiver and the LTE network is reduced. [21] A non-transitory computer-readable medium comprising program instructions for causing a computer to perform the method of any one of claims 17 to 20.

Images