DE102013104564A1 - Wireless communication apparatus e.g. smart phone of e.g. long term evolution communication system, has processor to control one transceiver to transmit signals having transmission band width based on set filter characteristic of filter - Google Patents

Abstract

The communication apparatus (1000) has a first transceiver (1014) that transmits and receives signals according to cellular wireless wide area communication technology. A second transceiver (1018) transmits and receives signals according to short-range wireless communication technology or wireless metropolitan-area system communication technology. A filter is connected to the second transceiver. A processor (1002) is coupled to the first transceiver for controlling the first transceiver to transmit signals having transmission band width based on the set filter characteristic of filter. An independent claim is included for a method for controlling wireless communication apparatus.

Description

This application claims the benefit of US Provisional Application No. 61 / 641,967, filed May 3, 2012, the contents of which are incorporated herein by reference in their entirety for all purposes.

The present disclosure relates to wireless communication devices and methods for controlling wireless communication devices.

Mobile communication devices may include a variety of wireless access technologies, e.g. a cellular wireless communication technology, e.g. LTE (long-term evolution) and short-range radio communication technology (eg, Bluetooth or WLAN) or metropolitan area-system wireless communication technology (e.g. English metropolitan area system radio communication technology) as WiMax support. Although typically different frequency bands are associated with such different wireless access technologies, there may still be interference between them, for example when a mobile communication device wants to operate two different wireless technologies in parallel. Avoiding such interference and improving coexistence between different wireless access technologies is desirable.

According to one aspect of this disclosure, there is provided a wireless communication device, comprising: a first transceiver configured to transmit and receive at least one signal according to a cellular wireless long-distance communication technology; a second transceiver configured to transmit and receive at least one of a wireless near-range communication technology and a wireless metropolitan area-system communication technology; at least one filter connected to the second receiver (or the second transceiver), the filter having a filter characteristic; and a processor connected to the first transceiver and configured to control the first transceiver to transmit signals having a transmission bandwidth set based on the filter characteristic.

In one embodiment, the at least one filter can be set up to filter the at least one signal received by the second transceiver in accordance with the filter characteristic. In yet another embodiment, the at least one filter may be configured to filter the at least one signal received by the second transceiver according to a form of the filter. In yet another embodiment, the processor may be further configured to adjust the transmission bandwidth by assigning one or more subchannels provided by the first transceiver for signal transmission. In yet another embodiment, the processor may be further configured to adjust the transmission bandwidth according to a frequency range in which signal suppression by the filter meets a predefined criterion. In yet another embodiment, the processor may be further configured to adjust the transmission bandwidth corresponding to a frequency range at which signal suppression by the filter is greater than a predefined signal suppression threshold. In yet another embodiment, the processor may be further configured to adjust the transmission bandwidth according to a frequency range at which signal suppression by the filter is maximum. In yet another embodiment, the processor may be further configured to adjust the transmission bandwidth based on the content of an instruction message received by the wireless communication device from another wireless communication device. In yet another embodiment, the processor may be further configured to adjust the transmission bandwidth according to a transmission bandwidth control message received from a second communication device. In yet another embodiment, the second communication device may be a wireless base station. In yet another embodiment, the processor may be further configured to generate a transmission bandwidth request message indicating one or more transmission bandwidths that the processor requests to assign the signal transmission. In yet another embodiment, the processor may be further configured to generate a filter characteristic message containing information about the filter characteristic of the filter. In yet another embodiment, the first transceiver may be configured to transmit and receive signals in accordance with a wireless third generation partnership project communication technology. In yet another embodiment, the first transceiver may be configured to transmit and receive signals in accordance with wireless 4G communication technology. In yet another embodiment, the first transceiver may be configured to transmit and receive signals in accordance with wireless long-term evolution communication technology. In another embodiment, the second transceiver may be configured to transmit and receive signals in accordance with a wireless near-range communication technology selected from a group consisting of: wireless Bluetooth communication technology; wireless UL wide band communication technology; wireless wireless local area Network communication technology; wireless infrared data association communication technology; wireless Z-Wave communication technology; wireless ZigBee communication technology; wireless HIgh PErformance LAN communication technology; wireless IEEE 802.11 Communication technology; and Wireless Digital Enhanced Cordless Communication Technology. In another embodiment, the second transceiver may be configured to transmit and receive signals in accordance with a wireless metropolitan area system communication technology selected from a group consisting of: Wireless Worldwide Interoperability for Microwave Access Communication Technology; wireless WiPro communication technology; wireless high-performance radio metropolitan area system communications technology; and wireless 802.16m advanced air interface communication technology.

In various embodiments, there is provided a method of controlling a wireless communication device, the method comprising: transmitting and receiving signals in accordance with a cellular wireless wide area communication technology; Sending and receiving signals according to a wireless near-range communication technology or a wireless metropolitan area-system communication technology; Filtering, by a filter based on a filter characteristic of the filter, signals received according to a wireless near-range communication technology or a wireless metropolitan area-system communication technology; Transmitting signals according to a cellular wireless long-distance communication technology using a transmission bandwidth set based on the filter characteristic of the filter.

In one embodiment, adjusting the transmission bandwidth may include assigning one or more sub-channels of one or more channels intended for signal transmission in accordance with wireless long-distance communication technology. In yet another embodiment, the wireless communication device may further include: a first transceiver configured to transmit and receive signals according to a cellular wireless wide area communication technology; a second transceiver configured to transmit and receive signals according to a wireless near-range communication technology or a wireless metropolitan area-system communication technology; at least one filter connected to the second receiver, the filter having a filter characteristic; and a message generator configured to generate a message having a suggestion for setting a transmission bandwidth for the first transceiver, the suggestion being based on the filter characteristic. In yet another embodiment, the first transceiver can be set up to send the message to another wireless communication device.

In various embodiments, there is provided a method of controlling a wireless communication device, comprising: a first transceiver transmitting and receiving at least one signal according to a cellular wireless wide area communication technology; a second transceiver transmits and receives at least one of a wireless near-range communication technology and a wireless metropolitan area-system communication technology; Filtering signals received according to a wireless near-field communication technology or a wireless metropolitan area system communication technology by means of a filter according to a filter characteristic of the filter; and generating a message with a proposal for setting a transmission bandwidth for the first transceiver, the suggestion being based on the filter characteristic.

In one embodiment, the method may further include sending the message to another communication device.

According to another aspect of this disclosure, a method of controlling a wireless communication device according to the wireless communication device described above is provided.

Further, there is provided a wireless communication device comprising a first transceiver configured to transmit and receive signals according to a cellular wireless long-distance communication technology; a second transceiver configured to transmit and receive signals according to a wireless near-range communication technology or a wireless metropolitan area-system communication technology; at least one filter connected to the second receiver, the filter having a filter characteristic; and a message generator configured to generate a message having a suggestion for setting a transmission bandwidth for the first transceiver, the suggestion being based on the filter characteristic.

Further, a method for controlling a wireless communication device according to the above-described wireless communication device is provided.

In the drawings, like reference characters generally indicate the same parts in the different views. The drawings are not necessarily to scale, instead, in general, the emphasis is on illustrating the principles of the invention. In the following description, various embodiments of the invention will be described with reference to the following drawings, in which:

1 a communication system according to one aspect of this disclosure;

2 shows a frequency band diagram;

3 shows a test system;

4 shows the measurement results of the first test case;

5 shows modified test results for the first test case, for different broadband noise;

6 shows the results of the second test case;

7 shows modified test results for the second test case for different wideband noise;

8th shows the results of the second test case;

9 shows modified measurement results of the second test case for different wideband noise;

10 a communication device according to various aspects of this disclosure;

11 shows a frame structure;

12 shows a data transfer diagram;

13 a transmission diagram shows;

14 a transmission diagram shows;

15 a transmission diagram shows;

16 and 17 show the impact of Wi-Fi and Bluetooth use on LTE-FDD with full traffic connectivity support, relying only on LTE denial and LTE kill;

18 a communication circuit according to one aspect of this disclosure;

19 a status & arbitration unit according to one aspect of this disclosure;

20 a transmission diagram shows;

21 a communication device shows;

22 a flowchart shows;

23 a transmission diagram shows;

24 shows a message flow diagram;

25 shows a frequency allocation table;

26 shows a message flow diagram;

27 a transmission diagram shows;

28 a transmission diagram shows;

29 a transmission diagram shows;

30 a transmission diagram shows;

31 a transmission diagram shows;

32 a transmission diagram shows;

33 a transmission diagram shows;

34 shows a wireless communication device;

35 a flowchart shows;

36 a flowchart illustrating a process for BT / LTE coexistence;

37 a flowchart illustrating a process for BT / LTE coexistence;

38 a flow chart illustrating a process for WiFi / LTE coexistence;

39 a flow chart illustrating a process for WiFi / LTE coexistence;

40 shows a wireless communication device; and

41 a flow chart shows.

In the following detailed description, reference is made to the accompanying drawings which show, by way of illustration, specific details and aspects of this disclosure in which the invention may be practiced. These aspects of this disclosure will be described in sufficient detail to enable those skilled in the art to practice the invention. It will be 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 disclosure are not necessarily mutually exclusive, as some features of this disclosure may be combined with one or more other features of this disclosure to provide novel features.

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

The air interface of an LTE communication system is referred to as E-UTRA (Evolved Universal Terrestrial Radio Access) and is generally referenced as "3.9G". In December 2010, the ITU acknowledged that the current versions of LTE and other developed 3G technologies do not meet the "IMT advanced" requirements and can not be considered "4G", assuming that they predecessor "IMT". advanced ", with a substantial improvement in performance and capabilities relative to initial, already deployed" third generation systems ". That's why LTE is sometimes referred to as "4G" (mainly for marketing reasons).

Compared to its predecessor UMTS, LTE provides an air interface that has been further optimized by improving system capacity and spectral efficiency for packet data transmission. Among other improvements, the maximum net transmission rate has been significantly increased, namely 300 Mbps in the downlink transmission direction and 75 Mbps in the uplink transmission direction. LTE supports scalable bandwidths from 1.4MHz to 20MHz and is based on new multiple access techniques such as Orthogonal Frequency Division Multiple Access (OFDMA) / Time Division Multiple Access (TDMA) in downlink direction (Transmitters). eg base station, to the handset, eg mobile device) and SC-FDMA (Single Carrier Frequency Division Multiple Access) / TDMA in uplink direction (handset to the transmitter). OFDMA / TDMA is a multi-carrier multiple access method in which a subscriber (eg 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, eg a mobile phone) for transmission and reception has been set to 20 MHz.) A physical resource block (PRB) is the base unit for physical allocation Channels defined in LTE It has 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 an subcarrier is referred to as a "resource element" A communication system used according to an aspect of this disclosure, which is, for example, a communication system according to LTE, will be described below with reference to FIG 1 described.

1 shows a communication system 100 according to one aspect of this disclosure.

The communication system 100 is a cellular mobile communication system (hereinafter also referred to as a cellular wireless communication network) comprising a wireless access network (eg, an E-UTRAN, Evolved UMTS (Universal Mobile Communication System) Terrestrial Radio Access Network (Terrestrial Radio Access Network ) according to LTE (Long Term Evolution)) 101 and a core network (eg an EPC, Evolved Packet Core, according to LTE) 102 having. The wireless access network 101 can a base (transceiver) station (eg eNodeBs, eNBs, according to LTE) 103 exhibit. Every base station 103 Provides a wireless coverage for one or more cell phones 104 of the wireless access network 101 to disposal.

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

Control and user data is between a base station 103 and a mobile device 105 that is in the mobile radio cell 104 coming from the base station 103 over the air interface 106 is operated, based on multiple access methods.

The base stations 103 are interconnected by means of a first interface 107 , eg an X2 interface, connected together. The base stations 103 are also using a second interface 108 , eg an S1 interface, with the core network, e.g. B. an MME (Mobility Management Entity) 109 via a S1-MME interface and to a serving gateway (S-GW) 110 connected by a S1-U interface. The S1 interface supports multiple-to-multiple relationships between MMEs / S-GWs 109 . 110 and the base stations 103 ie a base station 103 can with more than one MME / S-GW 109 . 110 be connected, and a MME / S-GW 109 . 110 can work with more than one base station 103 be connected. This enables network sharing in LTE (a shared use of the LTE network).

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

In the case of LTE, the wireless access network 101 ie the E-UTRAN 101 in the case of LTE, than out of the base station 103 existing, ie the eNBs 103 in the case of LTE, the E-UTRA user plane (PDCP / RLC / MAC) - and the control plane (RRC) - protocol completion in the direction of the UE 105 provide.

• • Funktionen zum Funk-Ressourcen-Management: Funkträger-Steuerung, Funkzugangs-Steuerung, Verbindungsmobilitäts-Steuerung, dynamische Zuteilung von Ressourcen zu UEs 105 in Uplink und Downlink (Zeitplanung);
• • IP-Kopfkompression und Verschlüsselung von Benutzerdatenströmen;
• • Auswahl eines MME-109-Anhanges an UE 105, wenn kein Routing zu einer MME 109 aus den Informationen, die von der UE 105 zur Verfügung gestellt werden, bestimmt werden kann;
• • Routing von Benutzerebene-Daten in Richtung des Serving-Gateway (S-GW) 110;
• • Planung und Übertragung bzw. Senden von Paging-Nachrichten (die von der MME stammen);
• • Planung und Übertragung bzw. Senden von Rundruf-Informationen (die von der MME 109 oder O&M (Operation and Maintenance (Betrieb und Wartung)) stammen);
• • Messung und Konfiguration von Messberichten für Mobilität und Planung;
• • Planung und Übertragung von PWS (Public Warning System (Öffentliches Warnsystem)), einschließlich ETWS (Earthquake and Tsunami Warning System (Erdbeben und Tsunamiwarnsystem)) und CMAS (Commercial Mobile Alert System (kommerzielles mobiles Alarmsystem))-Nachrichten (die von der MME 109 stammen);
• • CSG (Closed subscriber group (geschlossene Teilnehmergruppen)-Handhabung

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 a MME 109 Annex to UE 105 if no routing to a MME 109 from the information provided by the UE 105 can be determined;
• • Routing of user-level data towards the serving gateway (S-GW) 110 ;
• • planning and transmission or sending of paging messages (originating from the MME);
• • Planning and transmission or transmission of broadcast information (which is provided by the MME 109 or O & M (Operation and Maintenance));
• • Measurement and configuration of measurement reports for mobility and planning;
• • Planning and transmission of Public Warning System (PWS) including ETWS and Commercial Mobile Alert System (CMAS) messages (issued by the MME 109 come);
• • CSG (Closed subscriber group) handling

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

When the mobile device 105 continuously through the coverage area of the communication system 100 Moving, can control the call between neighboring mobile cells 104 be transmitted. The transfer of a call or call from a mobile radio cell 104 to a mobile radio cell 104 is referred to as a hand over or a hand off.

In addition to communication via the E-UTRAN 102 can the mobile device 105 communication via a Bluetooth (BT) communication link 111 support, eg to another mobile device 112 , and communication to a WLAN communication connection 113 to a wireless access point (AP) 114 , About the access point 114 the mobile device can access a communication network 115 (eg the internet), which with the core network 102 can be connected.

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 for 2G / 3G communication systems is that two of them are in the immediate vicinity of the ISM band, in which WLAN and Bluetooth are operated.

This is in 2 shown.

2 shows a frequency band diagram 200 , In the band diagram 200 Frequencies are shown from left to right.

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

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

• 1: WLAN beeinflusst das Band 40;
• 2: LTE-Band 40 stört WLAN in dem ISM-Band;
• 3: LTE-Band 7 stört WLAN in dem ISM-Band.

In order to illustrate the coexistence problems (in this case between LTE), results of real measurements made with the current or common hardware are given below. These three test cases for which the results are given are:

• 1: WLAN affects band 40;
• 2: LTE band 40 interferes with WLAN in the ISM band;
• 3: LTE Band 7 interferes with WLAN in the ISM band.

The test system used is in 3 shown.

3 shows a test system 300 ,

The test system 300 includes a first communication circuit 301 which supports (among others) WLAN and Bluetooth, and a second communication circuit 302 which supports (among others) LTE communication. Various filters 303 . 304 . 305 . 306 are intended for testing.

An arrow 307 indicates the coexistence case of interest, in this example (WLAN / LTE coexistence). It should be noted that in the measurements, RF (Radio Frequency) analysis was directed to interference via antennas rather than pin-to-pin interference at the IC level.

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

4 shows the measurement results for the first test case.

5 shows modified measurement results for the first test case for different broadband noise.

From the first test case, it can be seen that the use of the lower portion of the ISM tape desensitizes the entire tape 40.

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

6 shows the measurement results for the second test case.

7 shows modified measurement results for the second test case for different Breibandrauschen.

From the second test case, it can be seen that the use of the top of the belt 40 desensitizes the entire ISM belt. About 75% of the frequency combinations have more than 10 dB desensitization.

In the third test case, the LTE band is 7 UL 204 the disturber and that ISM band 202 the receiver (or frequency victim).

8th shows the results of the second test case.

9 shows modified measurement results of the third test case with different broadband noise.

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

From the test results, it can be seen that the existing hardware has severe coexistence problems in all three test cases.

According to various aspects of this disclosure, these open points are exploited by using a mechanism that is applied to the PHY layer and protocol layer, and is e.g. is based on a mix of software (SW) and hardware (HW) implementations, resolved or mitigated.

The examples are described below with reference to an exemplary communication device incorporated in 10 is shown described.

10 shows a communication device 1000 according to various aspects of this disclosure.

The communication device 1000 For example, a mobile communication device configured according to LTE and / or other mobile 3GPP mobile communication technologies. The communication device 1000 is also referred to as a wireless communication device.

According to various aspects of the disclosure, the communication device 1000 a processor 1002 such as a microprocessor (e.g., a central processing unit (CPU)) or other type of programmable logic device (acting, for example, as controller / controller). Furthermore, the communication device 1000 a first memory 1004 , for example a read only memory (ROM) 1004 and / or a second memory 1006 , for example random access memory (or random access memory). 1006 , exhibit. Furthermore, the communication device 1000 an ad 1008 , such as a touch-sensitive display, for example, a liquid crystal display (LCD) display or a light emitting diode (LED) display, or an organic light emitting diode (Organic Light Emitting Diode (OLED) display. However, any other type of display can be used for the display 1008 be provided. The communication device 1000 may additionally comprise any other suitable output device (not shown), such as a loudspeaker or a vibration actuator. The communication device 1000 may include one or more input devices, such as a keypad 1010 that includes 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 , exhibit. In the event that the display 1008 as a touch-sensitive display 1008 is implemented, the keypad can 1010 through the touch-sensitive display 1008 be implemented. In addition, the communication device 1000 optionally a coprocessor 1012 have to workload from the processor 1002 to decrease. Furthermore, the communication device 1000 a first transceiver 1014 and second transceiver 1018 exhibit. The first transceiver 1014 For example, an LTE transceiver supporting wireless communication according to LTE and the second transistor 1018 is, for example, a wireless transceiver that supports communication according to a WLAN communication standard, or supports a Bluetooth transceiver Bluetooth communication.

The components described above may be connected to each other via one or more lines, eg in the form of a bus 1016 implements, be connected. The first store 1004 and / or the second memory 1006 For example, a volatile (volatile) memory such as a Dynamic Random Access Memory (DRAM) or a nonvolatile (non-volatile) memory such as a programmable read only memory (PROM) may be an EPROM. Erasable PROM), an EEPROM (Electrically Erasable PROM), or a flash memory, eg, a floating gate memory, a charge trapping memory, an MRAM (Magnetic Resistive Random Access Memory) or a Phase Change Random Access Memory (PCRAM) or Conductive Bridging Random Access Memory (CBRAM). The program code used to execute and thus control the processor 1002 (and the optional coprocessor 1012 ) can be used in the first memory 1004 be saved. Data (eg messages coming from the first transceiver 1014 have been received or are to be sent) by the processor 1002 (and optional coprocessor 1012 ) can be edited in the second memory 1006 be saved. The first transceiver 1014 may be configured 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.

Furthermore, the communication device 1000 a picture and / or video camera 1020 configured to make a videoconference via the communication device 1000 to provide.

In addition, the communication device 1000 a Subscriber Identity Module (SIM), eg, a UMTS Subscriber Identity Module (USIM), for identifying a user and a subscriber of the communication device 1000 , exhibit. The processor 1002 Also, an audio processing circuit, such as an audio decoder circuit and / or an audio coding circuit, for decoding and / or encoding audio signals according to one or more of Several of the following audio coding or audio decoding technologies are implemented: ITU G.711, Adaptive Multi-Rate Narrowband (AMR-NB), Adaptive Multi-Rate Wideband ) (AMR-WB), Advanced Multi-Band Excitation (Advanced Multi-Band Excitation) (AMBE), etc.

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

• – eine Drahtlos-Nahbereich-Kommunikationstechnologie (Short Range Radio Communication Technology) (welche z. B. eine drahtlose Bluetooth-Kommunikationstechnologie, eine Ultra Wide Band (Ultra-Breitband) (UWB) Drahtlos-Kommunikationstechnologie, und/oder eine drahtlose lokales Netzwerk (Wireless Local Area Network) Kommunikationstechnologie (z.B. gemäß zu einem IEEE 802.11 (z.B. IEEE 802.11n ) drahtlosen Kommunikationsstandard)), IrDA (Infrared Data Association – Infrarot-Daten-Vereinigung), Z-Wave und ZigBee, HiperLAN/2 ((HIgh PErformance Radio LAN; eine alternative ATM-ähnliche 5 GHz standardisierte Technologie), IEEE 802.11a (5 GHz), IEEE 802.11g (2.4 GHz), IEEE 802.11n , I EEE 802.11VHT (VHT = Very High Throughput – Sehr großer Durchsatz)), aufweisen kann,
• – eine Metropoliten-Area-System Drahtlos-Kommunikationstechnologie (welche z. B. eine Worldwide Interoperability for Microwave Access (Weltweite Interoperabilität für Mikrowellen-Zugriff) (WiMax) (z. B. gemäß zu einen IEEE 802.16 Drahtlos-Kommunikationsstandard, z.B. WiMax fixed (fest) oder WiMax mobile (mobil)), WiPro, HiperMAN (High Performance Radio Metropolitan Area Network – Hochleistungsfähiges Metropolitan Area-Netzwerk) und/oder IEEE 802.16m Advanced Air Interface (Erweiterte Luftschnittstelle) aufweisen kann),
• – eine zellulare Drahtlos-Weitverkehr-Kommunikationstechnologie (welche beispielsweise ein Globales System für Mobile Kommunikation (engl. Global System for Mobile Communications) (GSM) Funkkommunikationstechnologie, einen Allgemeiner Paket-Funkdienst (engl. General Packet Radio Service) (GPRS) Funkkommunikationstechnologie, eine Erhöhte Datenraten für GSM-Evolution (engl. Enhanced Data Rates for GSM Evolution) (EDGE) Funkkommunikationstechnologie; und/oder eine 3. Generation Partnerschaftsprojekt (engl. Third Generation Partnership Project) (3GPP) Funkkommunikationstechnologie (z. B. (universelles mobiles Telekommunikationssystem (engl. Universal Mobile Telecommunications System)), FOMA (Freiheit von Multimediazugriff (engl. Freedom of Multimedia Access)), 3GPP LTE (langfristige Weiterentwicklung, engl. Long Term Evolution), 3GPP LTE Advance (erweiterte langfristige Weiterentwicklung, engl. Long Term Evolution Advance)), CDMA2000 (Codeaufteilung-Mehrfachzugriff, engl. Code division multiple access 2000), CDPD (Zellulare Digitale Paketdaten, engl. Cellular Digital Packet Data), Mobitex, 3G (3. Generation, engl. Third Generation), CSD (Leitungsvermittelte Daten, engl. Circuit Switched Data), HSCSD (Hochgeschwindigkeit-Leitungsvermittelte Daten, engl. High-Speed Circuit-Switched Data), UMTS (3G) (universelles mobile Telekommunikationssystem, engl. Universal Mobile Telecommunications System (3. Generation, engl. Third Generation)), W-CDMA (UMTS) (Breitband-Codeaufteilung-Mehrfachzugriff, engl. Wideband Code Division Multiple Access (universelle mobile Telekommunikation, engl. Universal Mobile Telecommunications System)), HSPA (Hochgeschwindigkeits-Paketzugriff, engl. High Speed Packet Access), HSDPA (Hochgeschwindigkeits-Downlink-Paketzugriff, engl. High-Speed Downlink Packet Access), HSUPA (Hochgeschwindigkeits-Uplink-Paketzugriff, engl. High-Speed Uplink Packet Access), HSPA+ (Hochgeschwindigkeits-Paketzugriff-Plus, engl. High Speed Packet Access Plus), UMTS-TDD (Universelles Mobiles Telekommunikationssystem – Zeitaufteilung Duplex, engl. Universal Mobile Telecommunications System – Time-Division Duplex), TD-CDMA (Zeitaufteilung – Codeaufteilung-Mehrfachzugriff, engl. Time Division – Code Division Multiple Access), TD-CDMA (Zeitaufteilung – Synchroner Codeaufteilung-Mehrfachzugriff, engl. 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 (Datenoptimiert oder Evolution-Nur-Daten, engl. Evolution-Data Optimized or Evolution-Data Only), AMPS (1G) (Verbessertes Mobiles Telefonsystem, engl. Advanced Mobile Phone System (Erste Generation, engl. 1st Generation)), TACS/ETACS (Vollständiger Zugriff Kommunikationssystem/Erweiterter Vollständiger Zugriff Kommunikationssystem, engl. Total Access Communication System/Extended Total Access Communication System), D-AMPS (2G) (Digitales AMPS, engl. Digital AMPS (2. Generation, engl. 2nd Generation)), PTT (Push-to-talk), MTS (Mobiles Telefonsystem, engl. Mobile Telephone System), IMTS (Verbessertes Mobiles Telefonsystem, engl. Improved Mobile Telephone System), AMTS (erweiteres Mobiles Telefonsystem, engl. Advanced Mobile Telephone System), OLT (Norwegisch für Offentlig Landmobil Telefoni, Öffentliche Land Mobile Telefonie, engl. Public Land Mobile Telephony), MTD (Schwedische Abkürzung für Mobiltelefonisystem D, engl. Mobile telephony system D), Autotel/PALM (Öffentliche Automatisierte Land Mobil, engl. Public Automated Land Mobile), ARP (Finnisch für Autoradiopuhelin, drahtloses Autotelefon „car radio phone“), NMT (Nordic Mobile Telephony), Hicap (Große Leistung Version, engl. High capacity Version von NTT (Nippon Telegraph and Telephone)), CDPD (Cellular Digital Packet Data), Mobitex, DataTAC, iDEN (Integriertes Digitales Verbessertes Netzwerk, engl. Integrated Digital Enhanced Network), PDC (Persönliches Digitales Zellular, engl. Personal Digital Cellular), CSD (Leitungsvermittelte Daten, engl. Circuit Switched Data), PHS (Persönliches Handy-Telefonsystem, engl. Personal Handyphone System), WiDEN (Breitband Integriertes Digitales Verbessertes Netzwerk, engl. Wideband Integrated Digital Enhanced Network), iBurst, Unlizensierter Mobiler Zugriff (engl. Unlicensed Mobile Access) (UMA, auch bezeichnet als 3GPP Generic Access Network, oder GAN Standard) aufweisen kann).

For example, any of the transceivers 1014 . 1018 support one of the following communication technologies:

• A Short Range Radio Communication Technology (e.g., a Bluetooth wireless communication technology, an Ultra Wide Band (UWB) wireless communication technology, and / or a wireless local area network ( Wireless Local Area Network) communication technology (eg according to one IEEE 802.11 (eg 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 , I EEE 802.11VHT (VHT = Very High Throughput)),
• - A metropolitan area system wireless communication technology (which, for example, a Worldwide Interoperability for Microwave Access (WiMax) (for example, according to one IEEE 802.16 Wireless communication standard, eg WiMax fixed (fixed) or WiMax mobile, WiPro, HiperMAN (High Performance Radio Metropolitan Area Network) and / or IEEE 802.16m Advanced Air Interface),
• - A cellular wireless long-distance communication technology (which is, for example, a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, a Increased Data Rates for GSM Evolution (EDGE) Radio Communication Technology; and / or a 3rd Generation Third Generation Partnership Project (3GPP) Radio Communication Technology (eg (Universal Mobile Telecommunication System (Universal Mobile Telecommunications System), FOMA (Freedom of Multimedia Access), 3GPP LTE (Long Term Evolution), 3GPP LTE Advance (Extended Long Term Evolution) Evolution Advance)), CDMA2000 (Code Division Multiple Access, Code divisi on multiple access 2000), CDPD (Cellular Digital Packet Data, engl. Cellular Digital Packet Data), Mobitex, 3G (Third Generation), CSD (Circuit Switched Data), HSCSD (High Speed Circuit Switched Data), UMTS (3G) (Universal Mobile Telecommunications System (Third Generation)), W-CDMA (UMTS) (Wideband Code Division Multiple Access (Universal Mobile Universal Mobile Telecommunications System), HSPA (High Speed Packet Access), HSDPA (High Speed Downlink Packet Access), HSUPA (High Speed Uplink Packet Access) High Speed Uplink Packet Access), HSPA + (High Speed Packet Access Plus), UMTS-TDD (Universal Mobile Telecommunication System - Time Division Du plex, engl. Universal Mobile Telecommunications System - Time Division Duplex), TD-CDMA (Time Division - Code Division Multiple Access), TD-CDMA (Time Division - Synchronous Code Division Multiple Access, Time Division - Synchronous Code) Multiple Access 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, Evolution -Data Optimized or Evolution-Data Only), AMPS (1G) (Advanced Mobile Phone System (1st generation)), TACS / ETACS (Full Access Communication System / Extended Full Access Communication System) , Total Access Communication System), D-AMPS (2G) (Digital AMPS). 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 Open Landmobile Telefoni, Public Land Mobile Telephony, engl. 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 (Nippon Telegraph and Telephone), CDPD, Cellite Digital Packet Data, Mobitex, DataTAC, iDEN (Integrated Digital Enhanced Network , Integrated Digital Enhanced Network), PDC (Personal Digital Cellular), CSD (Circuit Switched Data), PHS (Personal Handyphone System), WiDEN ( Broadband Integrated Digital Enhanced Network, iBurst, Unlicensed Mobile Access (UMA) as 3GPP Generic Access Network, or GAN Standard)).

• – personal area networks (Persönliches-Gebiet-Netzwerke) (Wireless PANs – Drahtlos-PANs) Drahtlos-Kommunikations-Subfamilie welche z.B. IrDA (Infrared Data Association), Bluetooth, UWB, Z-Wave und ZigBee aufweisen kann; und
• – wireless local area networks (drahtlose lokale Netzwerke (W-LANs) Drahtlos-Kommunikations-Subfamilie, welche z.B. HiperLAN/2 (HIgh PErformance Radio LAN; eine alternative ATM-ähnliche 5 GHz standardisierte Technologie), IEEE 802.11a (5 GHz), IEEE 802.11g (2.4 GHz), IEEE 802.11n , IEEE 802.11VHT (VHT = Very High Throughput), aufweisen kann.

A wireless short-range communication technology may include the following short-range communication technology subfamilies:

• Personal area networks (Wireless PANs) Wireless communication subfamily which may include IrDA (Infrared Data Association), Bluetooth, UWB, Z-Wave and ZigBee; and
• Wireless local area networks (W-LANs) wireless communication sub-family comprising, 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).

• – Wireless campus area networks (Drahtlos-Campus-Gebiet-Netzwerke) (W-CANs) Drahtlos-Kommunikations-Subfamilie, welche als eine Form eines Metropolitian-Area-Netzwerkes, spezifisch im akademischen Umfeld, aufgefasst werden kann, und welche z. B. WiMAX, WiPro, HiperMAN (High Performance Radio Metropolitan Area Network), oder IEEE 802.16m Advanced Air Interface aufweisen kann; und
• – Wireless metropolitan area networks (Drahtlos-Metropolitan Area-Netzwerke) (W-MANs) Drahtlos-Kommunikation-Subfamilie, welche auf einen Raum, Gebäude, Campus bzw. ein spezifisches Metropolitan-Gebiet (z. B. eine Stadt) beschränkt sein kann, und welche z. B. WiMAX, WiPro, HiperMAN (High Performance Radio Metropolitan Area Network), oder IEEE 802.16m Advanced Air Interface aufweisen kann.

A wireless metropolitan area system communications technology family may include the following wireless metropolitan area system communication technology subfamilies:

• Wireless campus area networks (W-CANs) Wireless communication subfamily which can be considered as a form of metropolitan area network, specifically in the academic environment, and which e.g. WiMAX, WiPro, HiperMAN (High Performance Radio Metropolitan Area Network), or IEEE 802.16m Advanced Air Interface may have; and
• - Wireless metropolitan area networks (W-MANs) Wireless communication subfamily which may be limited to a room, building, campus, or specific metropolitan area (eg, a city) , and which z. WiMAX, WiPro, HiperMAN (High Performance Radio Metropolitan Area Network), or IEEE 802.16m Advanced Air Interface may have.

Cellular wireless long-distance communication technologies can also be understood as Wireless Wide Area Network (Wireless WAN) wireless communication technology.

In the following examples it is assumed that the first transceiver 1014 LTE communication is supported and accordingly in the LTE frequency bands 201 . 204 . 205 . 206 is operated. Accordingly, the first transceiver becomes 1014 also called LTE-RF.

For the following examples it is further assumed that the second transceiver 1018 in the ISM band 212 is operated and supports WLAN communication or Bluetooth communication.

The first transceiver 1014 has a first communication circuit 1022 which can perform different tasks, focusing on the communication coming from the first transceiver 114 such as controlling the timing of transmission / reception, etc. The first communication circuit 1022 can as a (first) processor of the communication device 1000 For example, it is designed to be the first transceiver 1014 to control.

The second transceiver 1018 similarly has a second communication circuit 1024 On, the different tasks related to the communication by the second transceiver 1018 is executed, such as controlling the timing of sending / receiving, etc. The second transceiver 1018 is also referred to as 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 as a (second) processor of the communication device 1000 be understood and is z. B. configured around the second transceiver 1018 to control.

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

The first communication circuit 1022 can be a first real-time (RT) interface 1026 and a first non-real-time (NRT) interface 1028 exhibit. Similarly, the second communication circuit 1024 a second RT interface 1030 and a second NRT interface 1032 exhibit. These interfaces 1026 and 1032 will be described in detail below and may be used to provide control information related to other components of the communication device 1000 exchange. The RT interfaces 1026 . 1030 can z. B. an RT interface between the first communication circuit 1022 and the second communication circuit 1024 form. Similarly, the NRT interfaces 1028 . 1032 an NRT interface between the first communication circuit 1022 and the second communication circuit 1024 form.

It should be noted that a "circuit" may be understood to be any type of logic implementing unit which may be a special purpose circuit or a processor executing software stored in memory, firmware, or any combination thereof , Thus, a "circuit" may 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 may also be a processor executing software, e.g. B. any type of computer program, eg. B. a computer program that contains a virtual machine code such. B. Java executes. Other types of implementations of the corresponding functions, which are described in more detail below, may also be understood as circuitry in accordance with aspects of this disclosure.

RT coexistence mechanism

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.

For example, protocol synchronization can have two mechanisms: exploit the available period in which LTE-RF 1014 is idle and organizing the RF activity of the connectivity system 1018 such that RX (ie, receive) periods occur simultaneously with LTE-RX periods and TX (ie, 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 enable the second transceiver 1018 (WLAN or BT) to plan its activities at appropriate times: ie when the LTE RF 1014 idle or if the corresponding activities are compatible (ie allowing the first transceiver 1014 and the second transceiver 1018 received or so, that the first transceiver 1018 and the second transceiver 1018 send).

Traffic arbitration may result from receiving the indication of the advance activity of the CWS 1018 and the advance activity of the LTE-RF 1014 and selecting the traffic whose processing is allowed when a conflict is identified. Traffic arbitration can be achieved by a CWS activity indication or CWS activity indicator used by an RT (real-time) arbiter to cause a CWS kill and an LTE-kill signal (from "deleting" a frame or subframe for a communication technology ie to prevent transmission in the communication technology in the subframe or frame).

Hereinafter, an LTE frame indication in the LTE TDD case (ie, in the case that the LTE RF 1014 operated in TDD mode of operation), which is used for protocol synchronization according to one aspect of this disclosure.

In a time division duplex system, an LTE TDD has a unique frame structure that has both a DL and a UL subframe 11 shown.

11 shows a frame structure 1100 ,

The frame structure 1100 illustrates an LTE TDD frame 1101 comprising DL subframes, ie subframes used for downlink transmissions (in which LTE-RF 1024 Data received), UL subframes, ie subframes used for uplink transmissions (in which the LTE-RS 1028 Data is sent), and special (S) sub-frames, which z. B. can be used as a guard time and pilot transmission.

There is a set of seven possible configurations defined in 3GPP for TDD. Whatever the configuration selected, the TDD frame structure contains a periodic DL / UL pattern corresponding to the CWS chip 1024 can be communicated and which of the connectivity system 1018 can be used to plan communication traffic.

The LTE TDD frame structure is typically static or varies very rarely. It may be the CWS chip 1028 via an NRT message via an NRT interface 1032 are displayed. The required synchronization between the CWS chip 1028 and the time alignment with the LTE TDD frame can be via the RT interfaces 1026 . 1030 be performed, which is an LTE frame_SYNC signal 1102 use as in 11 shown.

The LTE frame start (ie the beginning of each frame 1001 ) will be a millisecond ahead of the CWS chip 1024 displayed, via the pulse, via the RT interface between the first communication circuit 1022 and the second communication circuit 1024 (ie via the RT interfaces 1026 . 1030 ) Is sent 1 ms in advance.

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

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

• • die sieben UL/DL-TDD-Rahmenkonfigurationen wie in 3GPP definiert: 3Bits,
• • die neun speziellen Teilrahmenkonfigurationen: 4 Bits.

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: 3Bits,
• • the nine special subframe configurations: 4 bits.

Considering that the message is an NRT message, and using an implied LTE configuration encoding, some LTE knowledge on the connectivity chip 1024 may require it to be desirable to remain in explicit 20-bit coding.

For the LTE frame display in the LTE FDD (Frequency Division Duplex) case, the LTE band is 7 UL 204 the most relevant band. This is an uplink tape and thus all subframes are UL subframes. Nevertheless, an LTE frame display can also be used in this case to give it to the CWS chip 1024 to properly plan its activity at the LTE subframe boundaries. It can also be done by the CWS chip 1024 used to synchronize its system clock with the LTE system clock.

When (Traffic) Arbitration Medium Access (Medium Access) to the CWS 1018 By definition, this can persist until the end of the deleted LTE subframe, and the CWS 1018, knowing the subframe boundaries, is able to apply scheduling to transfer the traffic amount until the end of the erased (LTE subframe) is going to maximize.

Hereinafter, an LTE gap indication is written in the case of LTE-FDD discontinuous reception (DRX) and discontinuous transmission (DTX), which is used for protocol synchronization according to one aspect of this disclosure.

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 no-signal pauses or long silence. An LTE system allows DRX (discontinuous reception) to save battery power. Two DRX profiles are supported, which are short DRX or long DRX are addressed. An LTE system allows discontinuous transmission (DTX) to increase the system capacity for the reverse link, ie the uplink.

For example, for VoLTE (voice over LTE), isochronous traffic can be assumed. Because the speech encoder generates a packet every 20 ms, the underlying periodicity of the LTE traffic can be utilized for the WLAN and BT transmissions during the LTE quiet periods and the non-signal LTE periods, respectively.

For example, UL / DL scheduling is inactive for an inactivity period of two (the minimum allowed value in the 3GPP Release 9 for DRX inactivity times is 1) 12 shown.

12 shows a data transfer diagram 1200 ,

In the data transfer diagram 1200 the time increases from left to right. The data transfer diagram 1200 shows uplink LTE data transfer 1201 , Downlink LTE data transmission 1202 and a lowest timeline 1203 which illustrates the time (in units of subframes) used for the CWS 1024 during the DRX periods 1207 Are available.

A first hatching 1204 indicates periods available to the CWS 1024 (eg, BT or WLAN), a second hatching 1203 indicates the periods used for the CWS 1024 available, and a third hatching 1206 indicates the periods used by the CWS 1024 are usable.

In the lowest timeline 1203 the periods are marked (by the first hatching 1204 and the second hatching 1205 ) in which no LTE-UL activity is expected and thus to the CWS 1024 can be delivered. It should be noted that the interference-free time is the LTE transceiver 1022 (especially in its role as receiver) must be communicated before the upcoming reception, for determining the AGC (Automatic Gain Control) and for the potential reappropriation of the signal. For short LTE DRX periods, the period is approximately 300 μs, for long DRX periods it is less than 1.3 ms.

The LTE standard also provides a mechanism called semi-persistent scheduling (SPS) to reduce signal overhead in the case of isochronous transmission. In this case, the UL approval is implicitly given by the PLC scheduling and the DRX period can start immediately after the receipt of the scheduled TTI (Transmission Time Interval).

An RT algorithm for LTE-FDD gap indication and LTE-FDD gap indication, respectively, used for protocol synchronization according to one aspect of this invention will now be described.

An LTE transmission gap or LTE transmission gap can at any time by the communication device 1000 generated following the network decision rules. The beginnings and ends of this transmission become the CWS in accordance with one aspect of this disclosure 1024 displayed so that the CWS 1024 its traffic within the transmission gap (eg in case the CWS 1024 Perform a WLAN communication or a Bluetooth communication that uses a profile that is based on Asynchronous Connectionless Link (ACL).

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

A measurement (transmission) gap is known 34 ms or 74 ms in advance in the LTE-L1 plane or LTE-L1 layer and is 6 ms long. A DRX / DTX (transmission) gap in a subframe is known after decoding of the PDCCH (Packet Data Control Channel) of the previous subframe, i. H. much less than 1 ms in advance (for example, about 200 μs). However, a transmission gap decision in an ad hoc mode of operation can be rejected up to 1.5 ms before the start of the transmission gap.

LTE gap signaling according to one aspect of this disclosure is disclosed in U.S. Patent Nos. 3,743,731, 5,729,074 13 illustrated.

13 shows a transmission diagram 1300 ,

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.

In this example, there is an uplink transmission gap 1305 and a downlink transmission gap 1306 , The uplink transmission gap 1305 is caused by an uplink transmission gap signal 1307 (UL gap enveloping signal) and the downlink transmission gap 1306 , is caused by a downlink transmission gap signal 1308 (DL-envelope signal) signals, with the start and the end of the transmission gap 1305 . 1306 the CWS 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 ,

It should be noted that under 3GPP Version 11 working title "In Device Coexistence", newly defined transmission gaps that are triggered specifically for coexistence purposes can be introduced. The transmission gap signaling, according to one aspect of this disclosure, is compliant with these new transmission gaps.

In practice, the lead time of the DL gap-enveloping signal remains 1308 in 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 done 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 about 4 ms between the DL and UL subframes. In addition, the UL Gap Decision can be rejected before it is applied, up to 1.5ms before the transmission gap begins. Rejection requests after this time, if any, will not be 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 can not be applied for a 1 ms UL transmission gap (1 subframe). According to one aspect of this disclosure, a 1 ms advance signaling for the LTE transmission gap end signaling is maintained as the maximum of the pre-facilitated traffic planning on the CWS side 1018 ,

As in 13 For example, the predicted values are tadv ₃ : 150 μs, tadv ₄ : 1 ms, tadv ₁ and tadv ₂ : 1 ms.

It should be noted that optimum signaling for a transmission gap can be achieved by indicating the transmission gap start and transmission gap duration.

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

The following describes the arbitration for the LTE-TDD case.

Due to LTE resource usage and WLAN / BT protocol requirements, perfect synchronization of the protocol on each side and the use of only simultaneous RX and concurrent TX may not be sufficient to support the use case, and some colliding RX / TX Events can occur.

14 and 15 illustrate conflicts or collisions between LTE TDD operation and WLAN / BT operation that may occur.

14 shows a transmission diagram 1400 ,

The transmission diagram 1400 illustrates the occurrence of transmission and reception conflicts in the case of synchronized LTE-TDD and WLAN traffic.

For each of the three timelines 1401 . 1402 . 1403 WLAN downlink transmissions are shown above and WLAN uplink transmissions are below the timelines 1401 . 1402 . 1403 with time increasing from left to right and, for example, from top to bottom along the timeline 1401 . 1402 . 1403 , Furthermore, LTE transfers (or LTE sub-frame allocations) 1404 . 1405 . 1406 for the timelines 1401 . 1402 . 1403 shown.

A hatching 1407 shows RX / TX conflicts that may occur between the WLAN transmissions and LTE transmissions.

15 shows a transmission diagram 1500 ,

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

For each of the three timelines 1501 . 1502 . 1503 is shown above the Bluetooth data transmission, and the Bluetooth data reception is below the timelines 1501 . 1502 . 1503 shown, with the time from left to right for each of the timelines 1501 . 1502 . 1503 increases. In addition, LTE transfers (or LTE sub-frame allocations) 1504 . 1505 . 1506 for the timelines 1501 . 1502 . 1503 shown.

A hatching 1507 shows UL / DL conflicts that can occur between Bluetooth transmissions and LTE transmissions.

RX / TX conflicts can be handled by arbitration, which potentially leads to LTE subframe losses. Arbitration can be performed between WLAN / BT and LTE to determine if the WLAN / BT traffic is allowed or not.

For example, if a WLAN / BT transmission event (by the second transceiver 1018 ) in conflict with an LTE-DL subframe (ie, a scheduled reception by the first transceiver 1014 ), real-time arbitration is performed. The arbitration process either decides to delete a WLAN / BT transmission to protect or allow the LTE-DL subframe to occur. In the latter case, depending on the RS interference level, the LTE-DL subframe is unlikely to be affected by the LTE-PHY, ie the LTE physical layer (implemented by components of the first transceiver 1014 ), decoded.

In the LTE UL case, an arbitration decision may consist in the permission of a WLAN / BT reception or a permission of an LTE UL sub-frame (ie, an LTE transmission). 14 and 15 can be used as an illustration of the impact of a WLAN and Bluetooth use case over LTE TDD for full connectivity traffic support (ie, support by the second transceiver communication 1018 ), which relies only on LTE denial (LTE rejection) and LTE desensitization (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.

The RT arbitration may be a unit implemented by a mix of HW and SW located in the LTE subsystem (eg, in the first transceiver 1014 ), which synchronizes 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 (the one through the RT interface 1026 . 1030 trained), for example in the context given by an NRT arbitration decision. This results in an RT arbitration and this is on the first transceiver 1014 and the second transceiver 1018 (using the RT coexistence interface).

For LTE-FDD, the interfering band is a UL band. LTE-UL can not be compromised by CWS, and so the role of arbitration is reduced to protecting or not protecting WLAN / BT-RX from LTE-TX. If a conflict occurs, i. as a consequence of miss planning or insufficient media access for connectivity traffic, arbitration can be applied. This will either clear the LTE UL subframe or it will run as normal.

16 and 17 show the impact of a WLAN and Bluetooth use case over LTE FDD for full connectivity traffic support based 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.

16 shows a transmission diagram 1600 ,

The transmission diagram 1600 illustrates the occurrence of transmit-receive conflicts in the case of synchronized LTE-FDD and WLAN traffic.

For all of the four timelines 1601 . 1602 . 1603 . 1604 WLAN downlink transmissions are shown above and WLAN uplink transmissions are below the timelines 1601 . 1602 . 1603 . 1604 shown, with time increasing from left to right. Other LTE transmissions (or LTE subframe allocations) 1605 . 1606 . 1607 . 1608 are for the timelines 1601 . 1602 . 1603 . 1604 shown.

A hatching 1609 denotes RX / TX conflicts that can occur between the WLAN transmissions and LTE transmissions.

17 shows a transmission diagram 1700 ,

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

For each of the three timelines 1701 . 1702 . 1703 Bluetooth data transmission is shown above, and Bluetooth data reception is below the timelines 1701 . 1702 . 1703 shown, with the time from left to right for each of the timelines 1701 . 1702 . 1703 increases. Other LTE transmissions (or LTE subframe allocations) 1704 . 1705 . 1706 are for the timelines 1701 . 1702 . 1703 shown.

A hatching 1707 refers to UL / DL conflicts that may occur between Bluetooth transmissions and LTE transmissions.

The real-time (coexistence) interface 1026 can only be done through hardware or a mix of hardware and software that integrates into the LTE subsystem (ie in the first transceiver 1014 ) can be implemented. 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 may be controlled, for example, by means of a software driver located in the LTE subsystem. He is using the CWS chip RT interface 1013 connected.

The RT interface may include, for example, the traffic arbitration signals shown in Table 2. signal width I / O description CWS active 1 I Medium busy, displaying a 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 display Table 2

The RT interface can, for. B. Protocol synchronization signals, as shown in Table 3 have. signal width SRC / Dest I / O description LTE frame sync 1 CWS O Synchronization signal indicating a LTE frame start UL column envelopes de 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 column envelopes de 1 CWS O Synchronization signal indicating an LTE-DL gap. Signal envelope with rising edge used only for LTE-TDD. Signal envelope with Flanks that occur 1 ms before the air interface gap (rising and falling edges) Table 3

The following is an example of hardware implementation of the RT interface between the first transceiver 1014 and the second transceiver 1018 specified.

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 allow fast communication between the two chips 1022 and 1024 to allow in both directions. Non-real-time communication can be B. by means of a standardized interface between the first transceiver 1014 and the second transceiver 1018 be performed.

The real-time interface can also be understood as something that basically has a set of discrete signals, as in 18 shown, has.

18 shows a communication circuit 1800 according to one aspect of this disclosure.

The communication circuit 1800 corresponds to z. B. the first communication circuit 1022 ,

The communication circuit 1800 has an LTE subsystem 1801 (L1CC), which can control all hardware interactions. The communication circuit 1800 has an RT interface 1803 on, by means of the LTE subsystem 1801 may be connected to another communication circuit, eg the second communication circuit 1024 using various IDC signals (in device coexistence) in device coexistence), which is on the left side of the RT interface 1803 are shown, and which are described in greater detail in the following text.

According to one aspect of this disclosure, there are no specific requirements for the electrical characteristics of the RT interface 1803 , The IDC signals are configured during a system start, for example. There is no need to use the IDC ports (which is the RT interface 1803 to reconfigure) during operation.

From a hardware point of view, the communication protocol of the interface signals can be kept simple. However, additional hardware support layer 1 in sub-system context may be required to make a real-time - to assist handling of the interface signals (that is, the IDC signals).

The LTE subsystem 1801 has an RT coex (co-existence) timer unit 1804 which is responsible for generating timing accurate events for the output signals IDC_LteDrxEnv, IDC_LteDtxEnv, and IDC_LteFrameSync, if configured as output signals. If IDC_LteFrameSync is configured as an input signal, a snapshot is performed in the form of LTE timing. Hereinafter, the signal characteristics will be described in more detail.

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

IDC_LteDrxEnv, IDC_LteDtxEnv:
These output signals are envelope signals, the discontinuous transmission / reception phases in the direction of the CWS subsystem 1018 Show. They are used to indicate discontinuous transmission / reception phases, depending on what the cause is: DARX, DTX measurements or (anything else). Both signals can be programmed individually by means of a timer.

IDC_LteFrameSync-CWS2LTE_SYNC configuration (input signal):
This signal can be used even if LTE2CWS_SYNC is a desirable solution while keeping it as a fall back position. This signal can be used by the CWS subsystem 1018 Request a snapshot of the LTE timing. In addition, an interrupt can be generated with this event.

The LTE subsystem 1801 also has an arbitration unit 1805 , an Interrupt Control Unit (IRQ) 1806 and an LTE transmission (Tx) path 1807 , on. The arbitration unit 1805 is more detailed in 19 shown.

19 shows an arbitration unit 1900 according to one aspect of this disclosure.

The arbitration unit 1900 has an IDC status register 1901 , an Arbitration Lookup Table (LUT) 1902 and registers 1903 , on.

The arbitration unit 1900 can be used for status indication or status display (eg by means of the IDC status register 1901 ) and the generation of an interrupt. For example, the current level of the signals, e.g. The below-mentioned IDC-related signals, by means of the arbitration unit 1900 be monitored. In addition, some of the signals of the interrupt control unit 1806 be supplied.

The arbitration unit 1900 in its role as 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 as consisting of two signals, IDC_CwsPriority1 and IDC_CwdPriority2). For this purpose, a combination of the input signals according to a programmable look-up table of Arbitration LUT 1902 be made. The reference table 1902 can be "on-the-fly" using the LTE subsystem 1801 be programmed.

IDC_LteActive: This signal is at the IDC RT interface 1803 available. The connectivity chip 1024 is the receiver of this signal. As such, this signal may be composed of hardware to provide a fast response in the event of changing input parameters. For example, the reset and decouple level of this signal is zero.

IDC_LteKill: This signal can be used for an "ad hoc" termination of an LTE transmission. Within the LTE subsystem 1014 The signal can be used to interrupt the LTE subsystem 1804 and / or the LTE-Tx path 1807 to create. 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 on the external IDC real-time interface 1803 visible, noticeable. If necessary, the LteKill signal from the RT interface 1803 be connected to a general purpose input / output (GPIO) GPIO to enable quick clearing of the current LTE transmission.

The arbitration LUT 1902 can have dedicated lookup tables implemented for IDC_LteActive and IDC_LteKill.

The arbitration unit 1900 can filter 1904 have for output signal filtering. In principle, an unstable state of the output signal (eg IDC_LteActive and IDC_LteKill) may be possible, for example if an input signal changes and / or the reference table 1902 is updated. In the event that the unstable condition causes a problem on the receiving side, filtering of the output may be required. In this case, changes in the output signal are only applied if the input is stable for a minimum period of time (eg 1 μs). A 1-microsecond filtering does not imply a loss of granularity in signal processing since it is not necessary to display events shorter than 1 microsecond. The filtering generates a 1-microsecond latency caused by the request to the CWS 1118 , their activity of the RT interface 1030 1 μs earlier, can be hidden.

LTE kill is a mechanism that can be used to stop (or stop) the instantaneous LTE transmission (ie, a UL communication), allowing the LTE transceiver 1014 does not transmit or send, z. B. to free the communication medium for WLAN / BT use. It may, for example, occur as a result of real-time arbitration for the benefit of WLAN / BT.

According to one aspect of this disclosure, abrupt shutdown of an LTE transmission is to be avoided because it could have various side effects such as spurious emission and a potential impact on eNodeB AGC power control.

To avoid the spurious wave, LTE kill can be performed by means of a power reduction command (e.g., sent over a digRF interface) or by nulling IQ samples. The use of the 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 undesirable side effects (such as PLL (Phase Locked Loop)) are avoided. Shutdown ...) can be avoided.

The use of a command sent through the digRF interface ensures that changes in transmission power occur in a smooth, even manner, thus avoiding spur generation.

According to one aspect of this disclosure, to achieve optimal adaptation to WLAN / BT traffic, LTE-kill has a very short latency, e.g. about 10 μs for WLAN traffic and about 150 μs for BT traffic.

20 shows a transmission diagram 2000 ,

Along a timeline 2001 WLAN traffic is represented over the medium, with data reception (ie downlink communication) over the timeline 2001 and data transmission (ie uplink communication) below the timeline 2002 is shown. In addition, LTE transmissions are for a first case 2002 and for a second case 2003 shown. In addition, CWS-Rx / Tx is above the RT interface 2004 shown.

• – wenn ein WLAN-Gerät den Zugang gewinnt, tritt Timing-Unsicherheit in der Größenordnung von mehreren μs auf. Diese ist nicht im Voraus präzise bekannt, aber diese ist an das WLAN-MAC (Medium Access Control – Mediumzugriffssteuerung)-Protokoll gebunden.
• – wenn ein WLAN-Gerät den Medium Zugang verliert, unterscheidet sich seine Aktivität für mehrere 100 μs und kann, von einem Koexistenz-Standpunkt aus, als ein neues Verkehrs-Ereignis aufgefasst werden. Das ist nicht im Voraus bekannt und kann sich mehrmals wiederholen.

It should be noted that WLAN activity has a timing uncertainty due to 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 in advance, but it is tied to the Medium Access Control (MAC) WLAN MAC.
• If a WLAN device loses access to the medium, its activity differs for several 100 μs and can be considered as a new traffic event from a coexistence point of view. This is not known in advance and can be repeated several times.

By contrast, BT has no timing uncertainty.

It should be noted that it can be crucial to ensure that LTE-kill is not applied to consecutive retransmissions of the same sub-frame to protect the HARQ. For FDD this means that LTE kill is forbidden for subframes n and subframes n + 8. A pattern can be used to protect the HARQ.

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

Below is another example of components of the communication device 1000 specified.

21 shows a communication device 2100 ,

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

The communication device 2100 has an LTE subsystem 2101 on, for example, the first transceiver 1014 corresponds and / or the LTE subsystem 1801 , and a WLAN / Bluetooth communication circuit 2102 , for example, the second communication circuit 1024 equivalent. The LTE subsystem 2101 has an LTE radio module 2103 and a communication circuit 2104 on, for example, the first communication circuit 1022 equivalent. The LTE subsystem 2101 can be the L1 (Layer 1) LTE communication stack 2114 and the LTE protocol stack 2115 (above layer 1).

The communication device 2100 also has an application processor 2105 on that for example the processor (CPU) 1002 equivalent. Connection applications or connectivity applications 2012 (including WLAN applications or applications and / or Bluetooth applications or applications) and LTE applications or applications 2113 can on the application processor 2105 be executed.

The communication circuit 2104 can be an NRT apps (application) coexistence interface 2106 to communicate with the application processor 2105 by means of an application interface 2109 of the application processor 2105 , exhibit, and an NRT coexistence interface 2107 , for example, the NRT interface 1028 corresponds to communicating with the WLAN / BT communication circuit 2102 using an NRT coexistence interface 2110 the WLAN / BT communication circuit 2102 , for example, the NRT interface 1032 equivalent.

The LTE subsystem 2101 has an RT arbitration unit 2111 on (for example, the arbitration unit 1805 corresponds).

The communication circuit 2104 also has an (LTE connectivity) NRT arbitration unit 2108 on. It should be noted that the NRT arbitration unit 2108 not necessarily in the communication circuit 2104 is arranged, but also in other components of the communication device 1000 . 2108 can be arranged. It can be in the form of the CPU, for example 1002 be realized.

The LTE subsystem 2101 has a first RT interface 2106 on, for example, the first RT interface 1026 corresponds, and the WLAN / Bluetooth communication circuit 2102 has a second RT interface 2107 on which, for example, the second RT interface 1030 corresponds to what can be understood that together they have an RT interface 2116 between the LTE subsystem 2101 and the WLAN / Bluetooth communication circuit 2102 form.

Table 4 shows the signals that z. B. via the RT interface 2116 can be exchanged. signal width I / O description Used in FDD Volume 7 Used in the TDD Band 40 CWS active 1 I Medium busy, displaying CWS RF activity 0 = idle / 1 = active Arbitration Arbitration CWS Tx / Rx 1 I CWS traffic direction 0 = Rx 1 = Tx Unused (CWS Active high only for Rx) Arbitration CWS priority 2 I CWS priority 0: low prio / 1: BT high prio / 2: WLAN high prio (PS-POLL, ACK, BACK) / 3: reserved Arbitration Arbitration LTE active 1 O CWS kill display Arbitration Arbitration LTE frame sync 1 O Synchronization signal indicating LTE frame start unused Traffic synchronization UL Spalteinhüllende 1 O Synchronization signal indicating an LTE-UL gap. Signal envelope with flanks occurring 1 ms before the air gap (rising and falling edges) Traffic synchronization Traffic synchronization DL Spalteinhüllende 1 O Synchronization signal indicating an LTE-DL gap. Signal feeder with rising edge used only for LTE-TDD. Signal envelope with flanks that occur 1 ms before the air gap gap (rising and falling flanks) unused Traffic synchronization Table 4

It should be noted that the length of the CWS priority signal may also be considered as two signals, CWS Priority 1 & 2.

It should be further noted that the first transceiver 1014 and the second transceiver 1018 also by means of the application processor 2105 (ie, for example, the CPU 1002 ) instead of a direct connection (as a direct RT interface). Furthermore, it should generally be noted that communication can be implemented by means of a serial or parallel bus rather than the use of dedicated signals (as shown, for example, in Table 4).

According to one aspect of the disclosure, a degraded RT mode may be used. Concretely, only a subset of the RT coexistence I / F signals given in Table 4 can be effective with the WLAN / Bluetooth communication circuit 2102 be connected.

For a FDD-only platform (ie, in this case, the first transceiver uses 1014 and the second transceiver 1018 FDD only), it is a first option (referred to as option 1a in the lower table 5) for a degraded RT interface to remove the DL-gap envelope signal and the CWS-Tx / Rx signal so that six signals remain , Because these remote signals are useless to FDD, there is no impact on coexistence performance. As a second option (referred to as option 1b in Table 5 below), in addition to the removal of the DL-gap envelope signal and the CWS-Tx / Rx signal, the CBS priority signal (CBS priority signal 1 & 2) may be removed that four signals remain. In this case, there is no longer a priority indication. Alternatively, a "light" or weak arbitration can be used, in which the second transceiver 1018 indicates an activity only for high-priority traffic, but high-priority traffic from BT and WLAN can no longer be distinguished from each other.

For a FDD TDD platform (ie in that case use the first transceiver 1014 and the second transceiver 1018 the TDD and FDD), it is a first option (referred to as Option 2 in Table 5 below) to eliminate arbitration and rely only on traffic synchronization so that only three signals remain. In this case, the second transceiver 1018 to the pure slave and can only use the communication resources which are from the LTE communication (ie the first transceiver 1014 ) and signaled by the DL-gap envelope signal and the UL-gap envelope signal or the synchronization via the TDD frame structure based on the LTE frame sync signal become. In this case, there is no way to protect the LTE traffic from wrong or too late CWS planning.

As a second option (referred to as Option 3 in Table 5 below), one can maintain traffic synchronization and light arbitration so that six signals remain, in which case there is no priority setting The second transceiver 1018 can only signal or show above a certain priority, but can not differentiate between BT and WLAN. The same arbitration rules are used for the LTE-BT conflict and the LTE-WLAN conflict.

Table 5 summarizes the options for a degraded RT interface. option Applicable for TDD / FDD Remote signals I / F signals influence comment BT WIRELESS INTERNET ACCESS on LTE 1a only FDD DL gap envelope CWS Tx / Rx 6 none none none - Traffic sync - Arbitration 1b only FDD DL Gap envelope CWS Tx / Rx CWS Priority 1 & 2 4 none none No of LTE Denial is increasing - Traffic sync - Arbitration - no distinction between WLAN and BT activity 2 FDD & TDD CWS Active CWS Tx / Rx CWS Priority 1 & 2 LTE Active 3 - HFP not supported - A2DP supported only for low / medium LTE radio coverage - Use only supported for low / medium LTE coverage none - only traffic sync - no arbitration 3 FDD & TDD CWS priority 1 & 2 6 none none No of LTE Denial is increasing - Traffic sync - Arbitration - no distinction between WLAN and BT activity Table 5

• – LTE-Rahmenanzeige (Signal + Rahmen-Strukturnachricht)
• – UL-Lücke-Anzeige
• – DL-Lücke-Anzeige
• – Arbitration mit einer kurzen Konfliktmöglichkeit
• – HARQ-Schutz (für Arbitration und LTE-Denial)
• – Degradierter RT-Betriebsmodus
• – Volle Verwendung eines LTE-gelöschten-Teilrahmen
• – Implementierung einer RT-Schnittstelle, wie z.B. oben beschrieben

By way of summary, for an RT coexistence mechanism according to various aspects of this disclosure, for example, the following may be provided:

• - LTE frame display (signal + frame structure message)
• - UL gap display
• - DL gap display
• - Arbitration with a short chance of conflict
• - HARQ protection (for arbitration and LTE denial)
• - degraded RT operation mode
• - Full use of an LTE deleted subframe
• Implementation of an RT interface, as described above

General coexistence architecture

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

The (LTE connectivity) NRT arbitration unit 2108 For example, by a software that is in the communication circuit 2104 is implemented. It uses z. A mix of application requirements (from connectivity and LTE apps) and context information from both cores (eg from the first transceiver 1014 and the second transceiver 1018 ) z. For example, the band, the bandwidth, the EARFCN (Absolute Radio Frequency Channel Number EARFCN) for performing arbitration and displays static information, such as selected frequency bands or selected power levels, the first transceiver 1014 and the second transceiver 1018 at. It also provides indications or indications for the RT-Arbiter 2111 which is in the LTE subsystem 2101 is arranged available. It should be noted that, according to one aspect of this disclosure, the NRT arbitration unit 2108 no arbitration between WLAN and BT. This arbitration can z. B. in a WLAN / BT communication circuit.

The NRT apps (applications) coexistence interface 2106 can also be a unit that uses software in the communication circuit 2104 executed is implemented. It transmits NRT messages, which application information of connectivity applications 2112 and LTE applications 2113 pointing to the application processor 2105 be carried out. Table 6 gives a list of messages between the application processor 2105 and the communication circuit 2104 using the NRT apps coexistence interface 2106 (and the corresponding application interface 2109 ) can be exchanged. News about LTE-NRT Apps Coex I / F (R / W) ID Message payload Info bits 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 an STA 3 WLAN_APP_PERIOD 16 I Required service period for WLAN in ms 4 WLAN_APP_DURATION 6 I Required service duration for WLAN in ms 5 BT_APP_PERIOD I Required service period for BT in ms. Applies to a connection using eSCO 16 or SCO. 6 BT_APP_DURATION 6 I Required service duration for BT in ms. Applies to a connection that uses only eSCO or SCO. 7 WLAN_APP_THROUGHP UT 16 I In kbps 8th BT_PROFILE_BITMAP 32 I Bitmap of the active BT profile (HFP, HSP, A2DP ...) 9 LTE_APP_THROUGHPU T 16 I In kbps 10 LTE_APP_LATENCY 16 I Application latency in ms Table 6

The NRT coexistence interface 2107 can also be a unit by software used in the communication circuit 2104 is arranged is implemented. It transmits NRT messages carrying context information from WLAN / BT communication circuitry and sends messages from the NRT arbiter 2108 to the WLAN / BT communication circuit (by means of the corresponding NRT coexistence interface 2110 the WLAN / BT communication circuit). Table 7 gives a list of messages that can be exchanged, for example, via the interface (the interface) that is through the NRT coexistence interface 2107 the communication circuit 2104 and the NRT coexistence interface 2110 the WLAN / BT communication circuit 2102 is formed. 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 applied) 2 WLAN_BW 1 I / O WLAN bandwidth (applied or applied): 0 = 20 MHz 1 = 40 MHz 3 WLAN_MCS 4 I WLAN MCS 4 WLAN_TX_POWER 4 I / O WLAN Tx performance (applied or applied) 5 WLAN_CHANNEL_RANK 14 × 4 I WLAN channel plan, arranged by preferred according to worst on the basis of SINR measurements and WLAN / BT restrictions 6 BT_AFH_RANK 79 × 3 I full AFH plan (including channels that may be excluded for WLAN / BT Coex) with preferences encoded over 3 bits: 000 -> preferably 111 -> worst 7 BT_AFH_MAP 79 I / O BT AFH bitmap (applied or applied) 8th BT_PKT_TYPE 4 I Bluetooth Packet Type 9 GNSS_BD 2 operated frequency band 10 GNSS_STATE 2 0 = sleep 1 = detection 2 = tracking 11 LTE_BITMAP 10 × 2 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 performance <bt_low_pwr_tx, while LTE RX is allowed 15 LTE_SPS_PATTERN 24 O Bits PLC initial offset (subframe offset in the first LTE frame where PLC is applied): 4 bits PLC periodicity (ms): 11 bits PLC event duration (ms): 9 Table 7

It should be noted that the LTE bitmap can be changed (limited to seven frame structures, but also more configurations for the S-content per se). It should be further noted that the NRT messages mentioned above are partial or complete to the eNodeB 103 can be sent if some coexistence decisions are made by them.

In addition, it should be noted that, depending on the platform architecture and application stacks, the sharing between information is in the communication circuitry 2104 and in the WLAN / BT communication circuit 2102 are arranged, can be changed.

In one aspect of this disclosure, the NRT coexistence algorithm and the RT coexistence algorithm are coordinated. Is in 22 illustrated.

22 shows a flowchart 2200 ,

If the coexistence status of the communication device 1000 in 2201 changes, becomes the NRT coexistence mechanism 2202 activated. A message is then sent over the NRT coexistence interface to apply the NRT arbitration decision.

Below, in 2203 For example, the desensitization level for the connectivity RAT achieved with the newly applied NRT arbitration is estimated using a pre-computed RF interference table. If it is above the desensitization target (the desense target), the RT coexistence mechanism is activated 2204 and this is carried out continuously in an autonomous manner. When the desensitization level is below the desensitization target (desense target), in 2205 , the RT coexistence mechanism is turned off.

If updates (using SW messages) either from the LTE subsystem 2101 or the WLAN / BT communication circuit 2102 can be received, the NRT arbiter 2108 detect a change in coexistence status, in the sense of, for example, if the frequencies previously used for LTE and CWS communication were not in the critical bands, it may now have become the case and coexistence algorithms must be activated.

The NRT arbiter 2108 is the responsible entity 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.

• – eine zweite RAT wird aktiv;
• – eine Übergabe (handover) wird in der LTE-Kommunikation zu einem anderen LTE-Band durchgeführt;
• – die LTE-Bandbreite wird modifiziert;
• – die Anzahl von aktiven RATs geht auf 1 zurück.

Cases of change of the coexistence status can, for. B. (among others) have:

• - a second RAT becomes active;
• A handover is performed in the LTE communication to another LTE band;
• - the LTE bandwidth is modified;
• - the number of active RATs goes back to 1.

As described above and in accordance with various aspects of this disclosure, partitioning (eg, in the form of interfaces) between RT and NRT may occur. RT and NRT processing can be synchronized. NRT messages can be sent by messages between the communication devices 105 and the eNodeB 103 be extended.

NRT coexistence mechanism

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

Bluetooth media access is based on a slotted traffic schedule link. Slots are scheduled in a fixed grid in time and frequency. The time slots are 625 μs long and are mapped to 1 MHz wide BT channels. The frequency channel used for a given timeslot is subject to frequency hopping patterns that pseudo-randomly switch from slot to slot.

A BT unit (eg in the form of a communication device 1000 that uses Bluetooth) can either be a (Bluetooth) master or a (Bluetooth) slave. A Bluetooth master provides reference time and controls the synchronization and activity of a piconet that controls it, which is a small network of surrounding Bluetooth devices. Slave units periodically observe the medium to acquire 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 when 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 occur only in reserved slots (negotiated before switching to sniff mode of operation) ).

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

A BT slave can use a "sniff mode of operation" to reduce and avoid energy consumption: master-slave transaction takes place only in reserved slots (negotiated before switching to sniff mode of operation).

Destination Bluetooth profiles may be A2DP for audio (eg, music) streaming and HFP as a voice headset profile. A2DP is an asynchronous traffic profile that uses single-slot packets, HFB is a periodic single-slot traffic that is transferred in fixed (reserved) slots. Devices can also be BT-paired without traffic.

Slots can be reserved during connection setup (through Connection Manager). The most common packets are HV3 packets (for synchronous connection-oriented (SCO) communication) occupying one third of a double slot.

An example of a multi-slot Bluetooth traffic is in 23 illustrated.

23 shows a transmission diagram 2300 ,

In the transmission diagram 2300 , the time increases from left to right and is in timeslots 2301 divided by 625 μs. First transfers 2302 be through a master device and second transmissions 2303 are performed by a slave device.

Bluetooth communication uses frequency hopping. In a communication, the frequency channels used alternate pseudorandomly from time slot to time slot and a pseudorandom hike through 79 available 1 MHz channels in the ISM band 202 carried out.

Adaptive frequency hopping (AFH) is a mechanism that allows it to be limited to a subset of the 79 channels. The number N of channels used, however, must not go below 20. The channel plan selection is completely flexible, but results in negotiations between master and slave, which are performed on a static basis. AFH can be switched off for "parked" slaves.

The adaptive frequency hopping mechanism can be used to push the BT traffic away from the LTE frequency bands. In particular, it is efficient to protect LTE-Rx from BT-Tx (LTE-TDD) but less in the opposite direction because the BT (Low Noise Filter) (LNA) frontend is a wide band.

• – Die erste Kommunikationsschaltung 1022 führt eine statische Anfrage an die zweite Kommunikationsschaltung 1024 (die als (lokaler) BT-Kern agiert), um ihren Kanalplan zu verändern;
• – Die zweite Kommunikationsschaltung 1024 aktualisiert den Kanalplan und stimmt ihn mit der gepaarten Einheit (z. B. einen anderen Kommunikationsgerät) ab.

According to one aspect of this disclosure, the adaptive frequency hopping mechanism is exploited in the following:

• - The first communication circuit 1022 performs a static request to the second communication circuit 1024 (acting as (local) BT core) to change its channel plan;
• - The second communication circuit 1024 updates the channel plan and reconciles it with the paired device (eg another communication device).

The Bluetooth spectrum occupancy can be up to 1/3 of the ISM band 202 be reduced. 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 7 UL band 204 ready. It should be noted that the efficiency of AFH for BT / LTE coexistence may be limited due to the fact that the BT-RX front-end also receives the full band in the AFH context (non-linearities are present anyway).

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

The following is a procedure for protecting Bluetooth from LTE-FDD transmissions in LTE Volume 7 UL 204 In reference to 24 described.

24 shows a message flow diagram 2400 ,

An NRT algorithm corresponds to the message flowchart 2400 , for example, from the NRT arbitration unit 2108 can be executed.

The message flow is between an LTE subsystem 2401 that the LTE subsystem 2101 corresponds to, for example, a software), an NRT arbiter 2402 , the NRT arbiter 2108 corresponds and a BT communication circuit 2403 that of the wireless BT communication circuit 2102 correspond, instead.

In 2404 loads the NRT arbiter 2402 the BT Desensitization Target (BT Desensing Target).

In 2405 sends the NRT arbiter 2402 an LTE information request message 2406 to the LTE subsystem 2401 to request information about the LTE configuration.

In 2407 creates the LTE subsystem 2401 Information about the LTE configuration, eg. An LTE information table, including the band used, the bandwidth used, the EARFCN, the path loss margin (estimated transmission power loss without trigger modulation / bandwidth change), etc.

In 2408 sends the LTE subsystem 2401 the generated information with an LTE information confirmation message 2409 to the NRT Arbiter 2402 ,

In 2410 saves the NRT arbiter 2042 the information he provided with the LTE information confirmation message 2409 has received.

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

In 2413 forms the BT communication circuit 2403 a leaderboard AFH plan including channels excluded for coexistence.

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

• 1) Berechnen eines Delta F für BT-Kanäle (volles Band, zu definierende Granularität)
• 2) Auswerten von BT-De-Sensing versus Betrieb von BT-Kanälen (volles Band) unter Verwendung von Isolations- bzw. Trenntabellen (statisch, vorberechnet für LTE bei voller Leistung)
• 3) Auswahl N, höchste Anzahl von BT-Kanälen, welche das BT-Desensitivierungs-Ziel (BT-De-Sensing-Ziel) befriedigen bzw. erfüllen
• 4) Wenn das Ziel nicht erreicht werden kann oder N < Nmin ist, dann verwende Nmin
• 5) Wenn das Ziel nicht erreicht werden kann, Beibehalten des Ausschlusses der für WLAN/BT coex angewendet wurde -> vernachlässigen
• 6) Bilden eines neuen AFH-Plans

In 2416 generates the NRT arbiter 2402 a new AFH plan. The default is the BT Desensitization Level (BT De-Sensing Level). The generation may have the following, for example:

• 1) Calculate a delta F for BT channels (full band, granularity to be defined)
• 2) Evaluate BT de-sensing vs. BT channels (full band) using isolation tables (static, pre-calculated for LTE at full power)
• 3) Selection N, highest number of BT channels satisfying the BT desensitization target
• 4) If the goal can not be reached or N <Nmin then use Nmin
• 5) If the goal can not be achieved, maintaining the exclusion that was applied for WLAN / BT coex -> neglect
• 6) Make a new AFH plan

In 2417 sends the NRT arbiter 2402 the new AFH plan to the BT communication circuit 2403 with an AFH record request message 2418 which the BT communication circuit 2403 asks to use the new AFH plan.

In 2419 updates the BT communication circuit 2403 the frequency hopping sequence accordingly.

In 2420 confirms the BT communication circuit 2403 the use of the new AFH plan by means of an AFH sentence confirmation message 2421 ,

In 2422 chooses the NRT arbiter 2402 the highest LTE-Tx (transmission) performance satisfying the BT de-sensing target and the LTE-Tx path loss margin.

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

In 2423 sends the NRT arbiter 2402 the specified LTE Tx power to the LTE subsystem 2401 with a performance request message 2424 which the LTE subsystem 2401 prompt to use the specified Tx power.

In 2425 uses the LTE subsystem 2401 the Tx performance accordingly.

In 2426 confirms the LTE subsystem 2401 the use of Tx performance by means of a performance acknowledgment message 2427 ,

In 2428 it is assumed that the NRT arbiter 2402 Recognizes that there is not (still) more coexistence that needs to be respected from now on.

In 2429 sends the NRT arbiter 2402 a performance cancellation request message 2430 to the LTE subsystem 2401 , what a 2431 by means of a performance cancellation confirmation message 2432 from the LTE subsystem 2401 is confirmed.

According to one aspect of this disclosure, the NRT coexistence mechanism comprises an FDM / PC algorithm for WLAN, which will be described below.

WLAN Medium Access is based on Carrier Sense Medium Access (CSMA), in which stations listen to and compete for a medium to gain access to it when it is free. There is no resource planning and no traffic periodicity. Global synchronization is achieved by means of a beacon transmitted through the access point approximately every 102 ms, but effective beacon transmission may be delayed due to medium occupancy.

WLAN MAC adapts to the radio channel conditions by means of a connection rate adaptation based on a packet error rate calculated on the transmission side based on received ACKs (positive ACK with repeated transmissions).

In the 2.4 GHz band (ISM band), WLAN systems are operated over 14 overlapping channels called CH # 1 to CH # 14 (CH # 14 is used only in Japan). Is in 25 illustrated.

25 shows a frequency allocation diagram 2500 ,

In the frequency allocation diagram 2500 , the frequencies increase from left to right. The 14 overlapping channels allocated for WLAN are semicircles 2501 illustrated.

WLAN is typically operated in BSS (Basic Service Set) mode of operation. There is also a peer-to-peer operation mode, but it is rarely used yet. However, this could be useful in the smartphone use case.

In BSS mode, the access point AP has full control over the operated WLAN channel selection and mobile stations (STA). The WLAN channel is selected or set by the static access point.

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

WLAN has a peak power of about 20 dBm and is usually transmitted at full power to allow the highest possible PHY rate and to reduce the packet duration as much as possible for power consumption reasons. However, the WLAN protocol stack does not prevent the use of less Tx power or define rules to select the power used.

• – wenn das Kommunikationsgerät 1000 mittels des zweiten Transceivers 1018 als eine Station agiert, die an einen Heim-Zugangspunkt oder an einem Hot-Spot verbunden ist, diese dürfte wahrscheinlich ein Verbindungsrate-Anpassungsereignis ausgelösen, um die PHY-Rate zu erniedrigen, was zu einer längeren Paketdauer und somit zu einer längeren Interferenz von WLAN und LTE führen würde. Gemäß einem Aspekt dieser Offenbarung ist die Verwendung von Leistungsregelung in diesem Fall begrenzt.
• – wenn das Kommunikationsgerät 1000 mittels des zweiten Transceivers 1018 als ein AB (d.h. Tethering-Fall) agiert, ist die Distanz zwischen den Kommunikationsgerät 1000 (z. B. ein Smartphone), das als ein Zugangspunkt (Router) verwendet wird, und einen verbundenen WLAN (z. B. Wiki)-Client (z. B. Laptop) unter der Kontrolle des Benutzers und kann verkürzt werden. Das Kommunikationsgerät 1000 kann dann sein WLAN-Tx-Leistung signifikant reduzieren, um die geringere BSS-Abdeckung und zugehörigen Pfadverluste auszugleichen bzw. kompensieren.

If necessary, the second transceiver can 1018 (operated as a WLAN transceiver in this example) operating in the communication device 1000 integrated, autonomously reduce its Tx performance:

• - if the communication device 1000 by means of the second transceiver 1018 acting as a station connected to a home access point or to a hot spot, it is likely to trigger a link rate adaptation event to decrease the PHY rate, resulting in a longer packet duration and hence longer WLAN interference and LTE would lead. In one aspect of this disclosure, the use of power control is limited in this case.
• - if the communication device 1000 by means of the second transceiver 1018 acting as an AB (ie tethering case) is the distance between the communication device 1000 (eg a smartphone) used as an access point (router) and a connected WLAN (eg wiki) client (eg laptop) 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 lower BSS coverage and associated path losses.

A comparison of the estimated path losses for tethering versus hot spot is given in Table 8. use case tethering Hot spot (interior) AP-STA distance 10 30 Pfadverluste_dB 66.1 85.2 Delta_dB 19.1 Table 8

The approximate estimate given in Table 8 shows a 19 dB margin between hot spot and tethering, which shows that the WLAN Tx power can be reduced by 19 dB, which equals 1 dBm.

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

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 requests could be relaxed (WLAN de-sensing requirement). This approach may not be suitable for connections with TDM (Time Division Multiplex) solutions because Tx power reduction can result in a lower PHY rate and thus increased Tx duration. There is a tradeoff between power regulation and use of high PHY rates.

In one aspect of this disclosure, WLAN channel selection is used to reduce WLAN / LTE interference.

In the case of use in which 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, the WLAN Traffic from the LTE operating band are pushed away, 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, eg reflection channel occupation by a near hot spot or a home AP, is taken into account in this process.

WLAN channel selection can bring 18 to 42 dB reduction from WLAN to LTE (LTE band 40) interference when channels CH # 3 to # 14 are selected. This mechanism is compatible with power control solutions, which can be used in addition.

The WLAN channel selection can bring 27 to 77 dB reduction from LTE (LTE band 40) to WLAN interference when the CH # 3 to # 10 channels are selected.

• – WLAN zu LTE-Band 40 OOB (Out-Off-Band)-Zurückweisung um 18 bis 42 dB
• – LTE-Band 40 zu WLAN OOB-Zurückweisung um 27 bis 77 dB
• – LTE-Band 7 UL -> WLAN OOB-Zurückweisung um 19 bis 49 dB

Overall, an 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

This mechanism does not harm WLAN throughput or WLAN robustness.

It should be noted that the aforementioned analysis only takes into account OOB noise effects, thus assuming that nonlinear effects such as signal compression by backmixing by the RF system design are avoided.

The following is a procedure for protecting WLAN from LTE-FDD transmissions in LTE Volume 7 UL 204 In reference to 26 described.

26 shows a message flow diagram 2600 ,

An NRT algorithm corresponds to the message flow diagram 2600 , for example, from the NRT arbitration unit 2108 can be executed.

The message flow is between an LTE subsystem 2601 which is the LTE subsystem 2101 (eg a software equivalent) and an NRT arbiter 2602 , the NRT arbiter 2108 corresponds, and a WLAN communication circuit 2603 that of the WLAN / BT communication circuit 2102 corresponds, instead.

In 2604 loads the NRT arbiter 2602 the WLAN Desensitization Destination (WLAN Desensing Destination).

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

In 2607 creates the LTE subsystem 2601 Information about the LTE configuration, eg an LTE information table, the band used, the bandwidth used, EARFCN, the path loss margin, (estimated transmission loss without trigger modulation / bandwidth changes) etc.

In 2608 sends the LTE subsystem 2601 the generated information with an LTE information confirmation message 2609 to the NRT Arbiter 2602 ,

In 2610 saves the NRT arbiter 2602 the information he provided with the LTE information confirmation message 2608 has received.

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

In 2613 forms the WLAN communication circuit 2603 a leaderboard channel plan. The rankings may be based on signal-to-interference-plus-noise ratio (SINR) and WLAN / BT limitations or disabilities.

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

• 1) Berechnen eines Delta F für jeden WLAN-Kanal
• 2) Auswerten von WLAN-Desensitivierung für jede WLAN-Benutzung, unter Verwendung einer Isolationstabelle (statisch, vorberechnet für LTE bei voller Leistung)
• 3) Auswahl des WLAN-Kanals, der in der Rangliste am höchsten steht und der das WLAN-Desensitivierung-Ziel erfüllt.

In 2615 determines the NRT arbiter 2602 a Wi-Fi channel to use. The default is the WLAN desensitization level (WLAN de-sensing level). The determination can z. For example, the following may include:

• 1) Calculate a delta F for each WLAN channel
• 2) Evaluate WLAN desensitization for each WLAN use, using an isolation table (static, pre-calculated for LTE at full power)
• 3) Selection of the WLAN channel which is highest in the ranking and which meets the WLAN desensitization target.

In 2617 sends the NRT arbiter 2602 an indication of the particular WLAN channel to the WLAN communication circuit 2603 with a channel set request message 2618 containing the wireless communication circuit 2603 asks to use the specified WLAN channel.

In 2619 moves the WLAN communication circuit 2603 according to the specified WLAN channel.

In 2620 confirms the WLAN communication circuit 2603 the use of the specified WLAN channel by means of a channel set acknowledgment message 2621 ,

In 2622 saves the NRT arbiter 2602 a display of the Wi-Fi channel.

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

In 2625 generates the WLAN communication circuit 2603 Information about the WLAN configuration, eg. B. a WLAN information table, the channel number, the MCS (Modulation and Coding Scheme - modulation and coding scheme), the Tx performance, etc., has.

In 2626 sends the WLAN communication circuit 2603 the generated information with a WLAN information confirmation message 2627 to the NRT Arbiter 2602 ,

In 2628 , chooses the NRT arbiter 2602 the highest LTE-Tx (transmission) performance satisfying the WLAN desensitization target and the LTE-Tx path loss margin.

• 1) Berechnen eines Delta F für den betriebenen WLAN-Kanal;
• 2) Berechnen von WLAN-Desensitivierung für den betriebenen WLAN-Kanal, unter Verwendung einer Isolationstabelle (statisch, vorberechnet für LTE bei voller Leistung);
• 3) Auswahl der höchsten LTE-Tx-Leistung, welche das WLAN-Desensitivierung-Ziel und die LTE-Tx-Pfadverlustmarge erfüllt.

This may include the following:

• 1) calculating a delta F for the powered WLAN channel;
• 2) calculating WLAN desensitization for the powered WLAN channel, using an isolation table (static, pre-calculated for LTE at full power);
• 3) Selection of the highest LTE Tx power that meets the WLAN desensitization target and the LTE Tx path loss margin.

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

In 2629 sends the NRT arbiter 2602 the specified LTE Tx power to the LTE subsystem with a power request message 2630 that the LTE subsystem 2601 asks to use the specified Tx power.

In 2631 applies the LTE subsystem 2601 the Tx power accordingly.

In 2632 confirms the LTE subsystem 2601 the use of Tx performance via a performance acknowledgment message 2633 ,

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

In 2635 sends the NRT arbiter 2602 a performance cancellation request message 2636 to the LTE subsystem 2601 , in the 2637 by means of a performance cancellation confirmation message 2638 from the LTE subsystem 2601 is confirmed.

For example, messages can be transmitted through the NRT interface through the NRT coexistence interface 2107 the communication circuit 2104 and the NRT coexistence interface 2110 the WLAN / BT communication circuit 2102 (eg, operated as a WLAN / BT baseband circuit) are exchanged in the context of an NRT coexistence as shown in Table 7 above. Further examples are given in the following text.

In accordance with one aspect of this disclosure, a measurement gap configuration is used in the LTE-connected mode of operation for LTE WLAN coexistence.

• 1. LTE-Nachbarzellen, die auf anderen Frequenzen als die Serving-Zelle (Zwischenfrequenzmessungen) betrieben sind,
• 2. Andere RAT (z. B. 2G oder 3G) Nachbarzellen (Inter-RAT-Messungen), durchzuführen.

While in LTE-connected mode of operation, measurement columns defined in 3GPP specifications allow individual wireless mobile devices (ie, mobile devices with only one LTE transceiver that does not have the ability to connect other frequencies during the LTE connection). To measure operating mode transparently (as those used by the serving cell)), measurements of:

• 1. LTE neighbor cells operating at frequencies other than the serving cell (intermediate frequency measurements)
• 2. Perform other RAT (eg 2G or 3G) neighbor cells (inter-RAT measurements).

When LTE is the Serving RAT, these measurement gaps are typically 6 ms in length and are scheduled with either 40 ms or 80 ms periodicity.

• • wenn die Lücke für einen LTE-Zwischenfrequenz-Messung verwendet wird, und wenn die LTE-Frequenz nicht mit der WLAN-Frequenz überlappt,
• • wenn die Lücke für 2G- oder 3G-Messung verwendet wird, weil es dort keine mögliche Interferenz zwischen 2G/3G und dem ISM-Frequenzband gibt, kann die Lücke ohne Einschränkung für WLAN/BT parallel zu der LTE-Messung verwendet werden.

When performing LTE communication using a frequency that overlays with WLAN communication and vice versa, the measurement gap can be used for secure WLAN reception and transmission:

• • if the gap is used for an LTE IF 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 to the LTE measurement.

In addition, 3GPP Release 9 introduces the concept of the so-called autonomous measurement gap for better closed subscriber group (CSG) cell support in the LTE-connected mode of operation. The reason for this is that for CSG cells, the SIB (System Information Block) must be read, which requires an additional measurement gap, which is asynchronous to those scheduled at the regular intervals. If the network supports autonomous measurement gaps, it is permissible for the mobile device to ignore some / a few TTIs as long as the mobile device is capable of transmitting at least 60 ACK / NAKs per 150 ms interval. The HARQ and higher layer signaling ensures that no data is lost.

• • der Mess-Schlitzmuster-Periodizität (z. B. 40/80 ms),
• • der Mess-Schlitzdauer (z. B. 6 ms),
• • einer eindeutigen Methode zum Identifizieren des ersten Mess-Lücke-Auftretens für das betrachtete Mess-Lücke-Muster.

To the second transceiver 1018 informing in advance of any upcoming regular gap event during which no interference with WLAN reception or transmission will occur, the first transceiver may 1014 (eg the LTE baseband circuit) sends a message to the second transceiver 1018 send (eg the CWS baseband circuitry) indicating a slot pattern, together with:

• The measurement slot pattern periodicity (eg 40/80 ms),
• The measuring slot duration (eg 6 ms),
• A unique method for identifying the first measurement gap occurrence for the considered measurement gap pattern.

• • Zwischenfrequenz-Mess-Lücke,
• • Inter-RAT-Mess-Lücke,
• • autonome Mess-Lücke.

This can be used for:

• • intermediate frequency measurement gap,
• • Inter-RAT measurement gap,
• • autonomous measuring gap.

The message may be, for example, a Periodic_Gap_Pattern_Config (periodicity, duration, first event date) message sent by the first transceiver 1014 (eg LTE baseband circuitry) on the second transceiver 1018 (eg, as CWS baseband circuitry), which indicates the periodic column pattern, and the second transceiver 1018 can freely perform transmission and reception during each of these columns.

• • Frequenz-Interferenz auftritt;
• • es genügend oder nicht genügend interferenzfreie Zeitperioden gibt, während derer der zweite Transceiver 1018 (z.B. die CWS-Basisbandschaltung) betrieben werden könnte.

A criterion and a decision in the first transceiver 1014 (eg, the LTE baseband circuitry) to transmit a gap message indication from the first transceiver 1014 (eg, implemented by the LTE protocol stack or the LTE physical layer) controlled by the first processor to the second transceivers 1018 (for example, the CWS baseband circuit) may allow to connect to the non-real-time arbiter unit (eg software) 2018 belong on the first transceiver 1014 (eg, the LTE baseband circuitry) may be implemented based on whether:

• • Frequency interference occurs;
• • There are enough or not enough interference-free time periods during which the second transceiver 1018 (eg the CWS baseband circuit) could be operated.

The gap message indicator may be through the non-real-time arbiter 2108 (eg, software) dynamically turned on or off, if it considers that the criterion is met to start or stop the use of gaps to ensure proper functionality of the second transceiver 1018 sure.

In summary, WLAN communication before the LTE tape 7 UL 204 Protected, Bluetooth communication can be before the LTE band UL 204 can be protected, and also wireless communication can be before the LTE band 40 201 be protected and Bluetooth communication can from the LTE band 40th 201 to be protected.

PHY attenuation (PHY mitigations)

Pilot symbols in overlaid OFDM symbols are typically meaningless. As a worst case, the case where two consecutive OFDM symbols are lost per LTE slot can be considered. This means that one pilot is missing per antenna and per slot (e.g., below two for antennas 0 and 1, under one for antennas 2 and 3). It should be noted that antennas 0 and 1 are only relevant for smartphones. There remains a worst case (for 1/2 antennas): a pilot is missing for a given carrier.

• 1) der äußere Empfänger bzw. Außenempfänger kann durch AGC, Rausch-Abschätzung, Kanal-Abschätzung beeinflusst sein
• – diese Aufgaben werden mit einer Verzögerung durchgeführt, welche ausreichend ist, um eine Echtzeit-Anzeige des WLAN-interferierenden-Zeitschlitzes (Burst) zu verwerten,
• – einige Filter existieren bereits in einem Entzerrer, um die Abwesenheit eines RS (Referenzsignal) zu kompensieren,
• – die Anzeige des WLAN-interferierenden-Zeitschlitzes kann von einem äußeren Empfänger bzw. Außenempfänger verwendet werden, um das entsprechende RS gegebenenfalls als fehlend zu erklären, und ein existierender Filter kann dann angewendet werden,
• – diese Echtzeit-Anzeige kann die RT-Koexistenz-Schnittstelle aufweisen.

This can have the following effects:

• 1) the outer receiver may be influenced by AGC, noise estimation, channel estimation
• These tasks are performed with a delay sufficient to exploit a real-time display 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 display of the WLAN interfering time slot may be used by an external receiver to explain the corresponding RS as necessary, and an existing filter may then be applied,
• This real-time display can have the RT coexistence interface.

• 2) Innen-Empfänger:
• – Transportblock/Code-Wort/Code-Block-Anfälligkeit kann schwierig auszuwerten sein; eine Auswirkung bzw. Einfluss hängt zumindest von einer Code-Block-Länge und von Kanal-Bedingungen ab:
• • im besten Fall können Code-Blocks (Kodier-Blöcke) durch den Turbo-Code derart wieder hergestellt werden, dass es keine Auswirkungen auf den LTE-Durchsatz hat,
• • im schlimmsten Fall wird ein Code-Block durch aufeinanderfolgende wiederholte HARQ-Übertragungen ähnlich beeinflusst (periodisch). Das würde bedeuten, dass der entsprechende Transport-Block nie durch die Übertragung gehen würde.

In summary, outside receiver protection can be performed prior to WLAN short-term interference through framework modifications (implementation of RT coexistence and RT arbitration may be prerequisite)

• 2) Indoor receiver:
• Transport block / code word / code block vulnerability can be difficult to evaluate; An impact 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 effect on the LTE throughput,
• • In the worst case, a block of code is similarly affected (periodically) by successive HARQ repetitions. This would mean that the corresponding transport block would never go through the transmission.

Typically, it is desirable to avoid the worst case. In addition, it may be desirable to prevent two consecutive interfering time slots in the same LTE subframe. This can z. By blocking two consecutive interfering WLAN time slots separated by the HARQ period (e.g., 8 ms).

According to one aspect of this disclosure, track-zeroing may be used to address the above issues, which may be considered a frequency-domain solution. It is z. Assuming, for example, that the track does not saturate the FFT (thus does not run over the full bandwidth in the frequency domain): the WLAN / BT requirements for transmission spurious radiation or sub-wave emission can be dimensioned accordingly. For example, frequency domain lane detection and frequency domain lane departure or signal lane cancellation may be employed.

In summary, RS filtering is based on an RT coexistence indication (AGC, noise estimation and channel estimation protection) and / or trace detection and extinction is applied for coexistence.

Protocol mitigation (protocol mitigations)

• – in Abwesenheit von Leerlauf-Lücken (idle gaps) oder wenn ihre Anzahl/Dauer im Vergleich zu den WLAN/BT-Bedürfnissen ungenügend sind, können einige Techniken auf der Protokollebene angewendet werden, um einige LTE-Teilrahmen zurückzuweisen, so dass sie durch WLAN/BT verwendet werden können. Dieses wird als LTE-Denial bezeichnet. Solche Techniken können sich nicht auf die gegenwärtige 3GPP-Spezifikation verlassen und können autonom bzw. selbstständig auf der Mobilgeräte-Ebene ausgeführt sein. Allerdings können sie teilweise in den 3GPP-Standard von Version 11 (IDC-Work-Item) enthalten sein.
• – Zusätzlich kann das Mobilgerät, wenn es im Übergabe (Handover)-Bereich ist, versuchen, die eUTRAN zu beeinflussen, um eine Übergabe in Richtung einer Zelle mit einer Koexistenz-freundlicheren Trägerfrequenz zu priorisieren. Es kann auch versuchen, eine Übergabe in Richtung einer weniger Koexistenz-freundlichen Zelle zu verzögern. Dieses wird auch als Koexistenz-freundliche Übergabe bezeichnet.

On the LTE side, several protocol mechanisms can be used to prevent conflicts between the LTE and WLAN / BT activities on the communication medium:

• In the absence of idle gaps, or if their number / duration is insufficient compared to the WLAN / BT needs, some techniques can be applied at the protocol level to reject some LTE subframes so that they are wireless / BT can be used. This is called LTE Denial. Such techniques can not rely on the current 3GPP specification and can be autonomous at the mobile device level. However, some of them may be included in the 3GPP standard version 11 (IDC work item).
• In addition, if the mobile device is in the handover range, it may attempt to influence the eUTRAN to prioritize a handoff to a cell with a coexistence-friendly carrier frequency. It can also try to delay a handover towards a less coexistence-friendly cell. This is also known as coexistence-friendly handover.

LTE denial can be implemented by using UL grant or SR (Schedule Request) deferral. The coexistence-friendly handover can be implemented by means of smart reporting of measurement results from neighboring cells (values and / or times).

• – systematisches LTE-Denial,
• – WLAN wird mit mittlerer Kanalqualität (29 Mbps PHY-Rate, schlechtester Fall) betrieben,
• – WLAN STA (d. h. nicht gültig für Tethering).

The impact of WLAN and Bluetooth use cases over LTE FDD for full connectivity traffic support, which relies only on LTE ruler, is high in the 16 and 17. This can be considered as the worst case for the LTE FDD page, 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 (ie not valid for tethering).

Tables 9 and 10 also illustrate the worst case impact of Bluetooth use case over LTE FDD and worst case impact of WLAN use case over LTE FDD (assumption of full support, no LTE column.

The cases of use are the same as those illustrated in Figs. 16 and 17. BT traffic profiles (of use 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 above 6 (16.6%) Ident A2DP SBC Stereo High quality, SRC master, 2-DH5, 345Kbps, period 30ms 4 non-consecutive UL subframes per 30 ms (13.3%) Ident Table 9 WLAN traffic types (of use cases) Worst case (w / o gap) Best case (w / o gap) WLAN beacon monitoring 2 subframes, negates 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 Table 10

• – auf der Mobilgerät-Ebene autonomes Zurückweisen der Verwendung von UL-Teilrahmen, wo LTE Kommunikationsressourcen zugeteilt hat. Das kann auf beides, LTE-FDD (z. B. LTE-Band 7 UL 204) und LTE-TDD (z. B. LTE-Band 40 201) angewendet sein,
• – auf der Mobilgerät-Ebene autonomes Zurückweisen der Verwendung von DL-Teilrahmen, wo LTE Kommunikationsressourcen zugeteilt hatte. Dieses kann für LTE-TDD (z. B. LTE-Band 40 201) angewendet sein.

According to one aspect of the disclosure, LTE Denial consists of:

• Autonomously rejecting the use of UL subframes at the mobile device level where LTE has allocated communications resources. This can apply to both LTE-FDD (eg LTE Volume 7 UL 204 ) and LTE-TDD (eg LTE-band 40 201 ),
• Autonomously rejecting the use of DL subframes at the mobile device level where LTE had allocated communications resources. This can be used for LTE TDD (eg LTE band 40 201 ).

It should be noted that for UL denial, a deletion / deferral of the scheduled LTE activity may be performed while for DL denial, allowing simultaneous TX activity on the CWS side may be sufficient.

In the context of SR shift, 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 quiet periods or silence periods. To save battery life, an LTE communication system (as in 1 shown) DRX. Two DRX profiles are introduced, which are addressed as Short-DRX (Short-DRX) or Long-DRX (Long-DRX). For the reverse link, ie the uplink, an LTE communication system allows discontinuous transmission (DTX) to increase system capacity. For uplink traffic, the mobile device reports 105 its uplink buffer status to the eNB 103 which then schedules uplink resource blocks (RBs) and the mobile device 105 assigns. In the case of an empty buffer, the eNB 103 do not schedule an uplink capacity, and in this case the UE 105 unable to report its uplink buffer status. In the event that the uplink buffer changes to one of its uplink queues, the UE sends 105 a schedule request (SR) to be able to report its buffer status into a subsequent scheduled uplink shared channel (PUSCH).

To prevent this, the MAC layer of the mobile device 105 delay the SR if the DTX period was previously granted WLAN activity. In accordance with one aspect of this invention, this mechanism may be used for LTE WLAN coexistence. Is in 27 shown.

27 shows a transmission diagram 2700 ,

LTE uplink transmissions are along a first timeline 2701 and LTE downlink transmissions are along a second timeline 2702 shown. The transfers occur z. B. between the mobile device 105 and the base station 103 on which the mobile device 105 served. Time takes from left to right along the timeline 2701 . 2702 to.

In this example, the mobile device is receiving 105 a UL grant or approval in a first TTI 2703 , The mobile device 105 responds to this UL grant by sending a UL signal in a second TTI 2704 , At the same time, the mobile device continues 105 its DRX inactivity counter. Assuming no further UL schedules or DL Transport Blocks (TBs) have been scheduled that would cause the DRX Inactivity Counter to be reset to the DRX Inactivity Time, the mobile device will send 105 after receiving the pending ACK of the last UL Transport Block, that the DRX and DTX conditions are met (as indicated by the arrow 2705 displayed). During the DRX and DTX period 2706 , it is not necessary that the mobile device 105 listening to any of the downlink control channels in the PDCCH, and the mobile device 105 will not be before the end of the DRX and DTX period 2706 by the eNB 103 be planned. The DRX and DTX period 2706 can be used for Wi-Fi transfer or transfer.

The mobile device 105 can send an SR if it is necessary to send some uplink data, which is the DRX and DTX period 2706 put an end to it. To prevent this, the mobile device MAC can suppress the SR when the period for interfering WLAN activity is used.

In the example of 27 , receives the mobile device 105 a UL grant in the first TTI 2703 , The mobile device 105 agrees to this UL grant by sending a UL signal in the second TTI 2704 (four TTIs later). However, the mobile device can 105 ignore the UL grant and thus reject the UL subframe that comes later to four TTIs, which is thus enabled for WLAN / BT operation. The shared subframe becomes the CWS chip 1024 by using the RT coexistence interface 1026 (UL gap display).

In one aspect of this disclosure, LTE denial with HARQ protection is used. This is described below.

In LTE WLAN / BT coexistence, it may be necessary to use LTE denial to enable the LTE subframe for connectivity traffic (override LTE subframe arbitration). When applied in UL, LTE denial can be considered as equivalent to the LTE transceiver 1014 prevents it from being transmitted to a subframe in which it has some allocated communication resources. In this case, the characteristics of the LTE HARQ mechanism may also take into account: HARQ is a repeated transmission MAC layer mechanism that is synchronous and periodic with an 8 ms period (UL case, in DL it is asynchronous).

In LTE-FDD UL, HARQ is synchronous and supports a maximum of eight processes. The potentially repeated transmission of a packet, which was initially transmitted in a subframe N, thus occurs in subframes N + 8 · K, with K> = 1. Thus, the influence of LTE denial over a transport channel can be very different, depending on the interaction with LTE-HARQ. For example, a periodic LTE denial with an 8 ms period may affect each retry of a single HARQ process and may result in link losses. An example with a denial period of 12 ms is in 28 shown.

28 shows a transmission diagram 2800 ,

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

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

Periodic rejection without regard to HARQ behavior can have high negative effects, even with a small number of rejections: it can lead to a weaker connection (best case) or to HARQ errors (worst case). A weak connection can result in an eNodeB link adaptation which reduces resource allocation, while HARQ errors can result in data loss (RLC in an unacknowledged mode of operation) or repeated RLC transmission with a corresponding delay.

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

• – Bursthaftes-Ablehnen (Bursty-Denial): obwohl es keine strengen Anforderungen von Applikationen/Codecs für periodischen Mediumzugriff (z.B. im Falle von http-Verkehr der über WLAN übertragen wird) gibt, werden die zurückgewiesenen Teilrahmen zusammen gruppiert (in Bursts bzw. Zeitschlitzen von zeitkontinuierlichen Teilrahmen), um die Anzahl von aufeinander folgenden Zurückweisungen für einen gegebenen HARQ-Prozess (d.h. von Zurückweisungen von TTIs, die den gleichen HARQ-Prozess zugeteilt sind) zu minimieren. Zum Beispiel beeinflussen seltene Burst-Zeitschlitze mit einer Dauer, die kleiner als 8 ms ist, jeden HARQ-Prozess meistens nur einmal. Daher ist es wahrscheinlich, dass diese vollständig durch die HARQ gemindert werden.
• – Intelligent-Ablehnen (Smart-Denial): Wenn Bursty-Denial nicht angewendet werden kann, wird ein Zurückweisungs-Muster erzeugt, welches den Einfluss auf HARQ minimiert, während die periodischen Anforderungen sichergestellt sind. Dieses Muster ist entworfen, um den Zeitabstand zwischen nacheinander folgenden Denials (Ablehnungen) von Teilrahmen, die einen gegebenen HARQ-Prozess ausführen, zu maximieren:
• • Dieser Ansatz ist optimal mit Bezug zur LTE-Verbindungs-Robustheit-Erhaltung (HARQ-Prozess-Schutz),
• • die Anforderungen an die Periodizität sind im Durchschnitt erfüllt (das LTE-Denial wird mit der geforderten Periode im Durchschnitt über das vollständige LTE-Denial-Muster ausgeführt). Das Muster enthält Variationen der Periode zwischen 2 LTE-Denials,
• • Vermeidung von Unterlauf/Überlauf für Codec mit periodischen Verhalten.

For example, the following precautions can be taken when using LT denial to minimize the impact on HARQ

• Bursty denial: although there are no strict requirements of applications / codecs for periodic medium access (eg in the case of http traffic being transmitted over WLAN), the rejected subframes are grouped together (in bursts or time slots) of time-continuous subframes) to allocate the number of consecutive rejections for a given HARQ process (ie, rejections of TTIs assigned to the same HARQ process) minimize. For example, rare burst time slots with a duration less than 8 ms usually only affect each HARQ process once. Therefore, it is likely that these are completely mitigated by the HARQ.
• Intelligent denial: When bursty denial can not be applied, a rejection pattern is generated which minimizes the impact on HARQ while ensuring the periodic requirements. This pattern is designed to maximize the time interval between successive denials of subframes that perform a given HARQ process:
• • This approach is optimal with respect to LTE connection robustness preservation (HARQ process protection),
• • the periodicity requirements are met on average (the LTE denial is performed with the required period on average over the full LTE denial pattern). The pattern contains variations of the period between 2 LTE denials,
• • Avoid underflow / overflow for codec with periodic behavior.

The general smart LTE denial pattern generation algorithm may be e.g. As the following.

conditions

• • B: periodic requests (in ms)
• • N: duration of the request (in ms)
• • W: HARQ window length (8 ms for UL)

Algorithm:

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

• • P1 = P-abs(mod(P, W)-N)
• • P2 = P1 + W
• • K1 = W-(P-P1)
• • K2 = P-P1

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

An example is in 28 shown. Along a second timeline 2802 UL subframe denial and the allocation from the TTIs to HARQ processes are shown, with the periods between the 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, it is avoided that TTIs allocations of the same HARQ process are periodically rejected.

It should be noted that this pattern generation algorithm is autonomous in the mobile device 105 is applicable. It is also potentially applicable to 3GPP Release 11 IDC, where the possibility of having LTE split generation decided on an 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 the standpoint of robustness.

The following describes a mechanism for Smart VoLTE (Voice over LTE) -BT-HFP coexistence.

In this use case, it is assumed that the mobile device 105 is connected to a headset by means of BT and a voice call is received or transmitted via LTE (VoLTE). It is further assumed or assumed that the mobile device 105 as a master BT device (with others Words, it is assumed that the BT unit of the mobile device 105 has a master role). If this is not the case, a BT Roll Swap command can be issued.

Bluetooth communication is organized in pico networks or piconets, with a single master controlling the traffic allocation by means of 625 μs long time slots. Is in 29 shown.

29 shows a transmission diagram.

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 straight-slot transmission capabilities, while the slaves can only transmit in odd-numbered 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 (snoop, park, hold) where these requests are relaxed.

For an earpiece connection, the BT units are typically paired in a low-power mode of operation (eg, a traffic exchange every 50-500 ms). When a call starts, the BT unit switches to an HFB profile (Handsfree Profile) with a very frequent periodic eSCO (Extended Synchronous Connection Oriented) or SCO (Synchronous Connection Oriented). synchronous connection-oriented) traffic. Is in 30 shown.

30 shows a transmission diagram 3001 . 3002 ,

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

Typically, as in 30 As shown, a setup parameter set for HFP eSCO has eight slot periods with two consecutive slots dedicated to master and slave transmissions, followed by repeated transmission possibilities, and a SCO setup has one Six slot period with two consecutive slots dedicated to master and slave transmission, followed by four idle slots, and there is no repeated transmission.

It should be noted that once BT devices are paired, a piconet is generated and thus a BT system clock and slot counter are turned on. For example, then the odd and even slots are determined. An attempt to synchronize the Bluetooth system clock with respect to the LTE system clock may not be possible after the establishment of a piconet, either by the definition of odd or even slots. It should also be noted that the term TTI here refers to the LTE-TTI (1 ms) and Ts refers to the BT time slot duration (0.625 ms).

The following describes the protection of BT-eSCO. This is applicable in the case when a Bluetooth unit (eg realized by the second transceiver 1018 ) uses the HFP profile to transmit voice from / to a headset with eSCO traffic.

31 shows a transmission diagram 3,100 ,

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

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

A lower timeline 3102 shows the Bluetooth HFB traffic, as seen from the perspective of a master, and based on eSCO packets. BT slots with a second hatch 3104 correspond to the potential BT repeated transmissions according to the eSCO traffic definition.

Due to both traffic characteristics (periods and duration), applying MAC protocol synchronization can enable efficient coexistence between VoLTE and BT-HFP operation. Two different compromises are possible, a first in which only the BT-HFP eSCO initial reception is protected from LTE-UL interference, and a second in which both BT-HFP eSCO initial reception and repeated transmitted slot Reception are protected.

• – Schutz vor T mod(D₀, 5TTI) >= TTI-Ts oder mod(D₀, 5TTI) <= 5TTI–2Ts
• – Schutz vor RT1 mod(D0, 5TTI) <= 3TTI-2Ts oder mod(D0, 5TTI) >= 4TTI-Ts
• – Schutz vor RT2 mod(D₀, 5TTI) <= TTI-2Ts oder mod(D₀, 5TTI) >= 2TTI-Ts
• – Schutz vor RT3 mod(D₀, 5TTI) <= 4TTI-2Ts oder mod(D₀, 5TTI) >= 5TTI-Ts

The receipt of original packets transmitted by a BT slave can be protected from LTE repeated transmissions under the following conditions:

• - Protection from T mod (D ₀ , 5TTI)> = TTI-Ts or mod (D ₀ , 5TTI) <= 5TTI-2Ts
• - Protection against RT1 mod (D0, 5TTI) <= 3TTI-2Ts or mod (D0, 5TTI)> = 4TTI-Ts
• - Protection against RT2 mod (D ₀ , 5TTI) <= TTI-2Ts or mod (D ₀ , 5TTI)> = 2TTI-Ts
• - Protection against RT3 mod (D ₀ , 5TTI) <= 4TTI-2Ts or mod (D ₀ , 5TTI)> = 5TTI-Ts

• – Schutz vor T mod(D₀, 5TTI) >= 4TTI oder mod(D₀, 5TTI) <= 3TTI–Ts
• – Schutz vor RT1 mod(D₀, 5TTI) <= TTI-Ts oder mod(D₀, 5TTI) >= 2TTI
• – Schutz vor RT2 mod(D₀, 5TTI) <= 4TTI-Ts oder mod(D₀, 5TTI) >= 0
• – Schutz vor RT3 mod(D₀, 5TTI) <= 2TTI-Ts oder mod(D₀, 5TTI) >= 3TTI

Receipt of packets repeatedly transmitted by the BT slave can be protected from LTE repeated transmission under the following conditions:

• - Protection against T mod (D ₀ , 5TTI)> = 4TTI or mod (D ₀ , 5TTI) <= 3TTI-Ts
• - Protection against RT1 mod (D ₀ , 5TTI) <= TTI-Ts or mod (D ₀ , 5TTI)> = 2TTI
• - Protection against RT2 mod (D ₀ , 5TTI) <= 4TTI-Ts or mod (D ₀ , 5TTI)> = 0
• - Protection against RT3 mod (D ₀ , 5TTI) <= 2TTI-Ts or mod (D ₀ , 5TTI)> = 3TTI

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 packet retransmissions) without BT retry protection.

In this case, the initial BT packet exchange (1TX slot + 1RX slot) is protected from LTE transfers as long as the LTE does not retransmit four times consecutively for the same HARQ process. BT repeated transmission may be blocked by LTE-UL transmission if necessary. This can be realized by requesting the BT master to delay initial packet transmission versus initial LTE subframe transmission by D ₀ with 2TTI-Ts <= mod (D ₀ , 5TTS) <= 3TTI-2Ts, e.g. B. 1375 μs <= mod (D ₀ , 5 ms) <= 1750 μs. An example is in 32 shown.

The 32 shows a transmission diagram 3200 ,

A top timeline 3201 represents VoLTE traffic in LTE-FDD-UL. Subframes T and RTn designations correspond to the initial transmission from a VoLTE subframe and its nth retransmission (in the sense of HARQ retransmission). VoLTE original or original sub-frames are by a first hatching 3103 and a potential retransmission is by a second hatching 3104 shown.

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

As a second approach to VoLTE and PT eSCO coexistence, BT and BT retransmission (ie BT packet retransmission) can be protected from LTE-TX and ReTx1 (ie, before packet transmission and the first retransmitted packet transmission). In this case, the initial BT packet exchange (1TX slot + 1RX slot) and its potential first retransmissions before the LTE UL transfers are protected as long as the LTE system is not two consecutive times for the same HARQ process repeatedly transmits. If an LTE system repeatedly transmits more than twice, some BT transmission / retransmission may be blocked. This can be realized by requesting the BT master to delay initial packet transmission over initial LTE subframe transmission by D ₁ with D ₁ = TTI-Ts. For example, mod (D ₁ , 5 ms) = 375 μs for eSCO and eSCO repeated protection against LTE-T and RT1. The transmission scenario corresponds to that in 31 is shown.

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

In this case, the initial BT packet exchange (1TX slot + 1RX slot) is protected before LTE UL transfer unless LTE is consecutive to the same HARQ process repeatedly transmits. If LTE transmits more than twice repeatedly, some BT transmission / retransmission may be blocked.

This can be realized by requesting the BT master to delay initial packet transmission over all initial LTE subframe transmission to D ₀ with TTI-Ts <= mod (D ₃ , 5TTI) <= 3 TTI-2Ts. For example, 375 μs <= mod (D ₃ , 5 ms) <= 1625 μs for eSCO protection against LTE-T, RT1. The transmission scenario is the same as in 31 shown.

As another approach, BT-SCO can be protected as follows. According to Bluetooth, the HFD profile can be used to transmit voice to / from a handsfree or microphone / headset combination with SCO traffic occupying 1/3 of the communication medium time and having no repeated transmission capability. An example is in 33 specified.

33 shows a transmission diagram 3300 ,

An upper timeline 3301 represents VoLTE traffic in LTE-FDD UL. Sub-frames with T and RTn designations correspond to the initial transmission of a VoLTE subframe and its nth repeated transmissions (in the sense of HARQ repeated transmissions). Original VoLTE subframes are defined by a first hatching 3103 and potential retransmissions are represented by a second hatch 3104 shown.

A lower timeline 3102 shows the Bluetooth HFP traffic from the perspective of a master and based on SCO packets.

Two thirds of the BT packet exchange (1TX slot + 1 RX slot) are protected against LTE UL transfers. If some LTE repeated transmission occurs, it is likely that several more BT slots will be blocked. This can be realized by requiring that BT be delayed from LTE-active subframe start, between TTI-Ts and TTI, and TTI-Ts <= mod (D ₂ , 6Ts) <= TTI. For example, 375 μs <= mod (D ₂ , 3.75 ms) <= 1 ms for minimal LTE-VoLTE interference over SCO traffic. If D _{2 is} not within this range, then two-thirds of the SCO packets can be blocked by the VoLTE subframe transmissions.

In summary, the delays or range of delays between VoLTE-Tx and BT-Master-Tx identified above (which may be considered to be optimum) represent a minimal probability of collision between VoLTE subframe transmissions and BT-HFP packets. Receptions available. The delay requests are derived accordingly from eSCO packet use for BT-HFP profiles or from SCO packet usage.

Using eSCO packets may be desirable because it coexists much better with the VoLTE traffic pattern. When using SCO, one-third of the BT packets are lost due to collision with VoLTE-Ul subframes, and this can not be resolved by LTE denial for that frame because the effect on call quality would be worse (20 ms losses versus 5 ms losses).

• – er ist ausreichend um den anfänglichen BT-Empfang vollständig zu schützen
• – seine Verzögerungsanforderung sind relativ gering (2 × BT T-Schlitze); dieser kann im Fall einer LTE-Übergabe (handover) während des Anrufes ausgewertet werden.

Among the eSCO solutions, the third approach may be desirable because:

• - It is sufficient to fully protect the initial BT reception
• Its delay requirement is relatively low (2 × BT T slots); this can be evaluated in the case of an LTE handover during the call.

One possible concept can be the following:

A) Establish a call

• 1) BT pairing, which typically occurs before VoLTE connection establishment, without any specific coexistence constraint.
• 2) When the LTE connection (LTE call) is established, information of the periodically assigned subframes (PLC based) is passed to the BT and added to NRT messages. These are e.g. 5-10 ms available after the PLC pattern is applied.
• 3) The BT master then interprets the PLC message
• (Period, duration, offset) and uses the LTE frame sync RT signal as a sync reference.
• 4) When the eSCO / SCO traffic is established, the BT master allocates the BT slots which satisfy the delay requirements related to VoLTE transmissions (which is always possible because for the third approach the delay is 2xT). Slot is).

B) LTE handover

• 1) Übergabe und neue SPS-Zuteilung kann dann zu BT über NRT-Nachrichten zur Verfügung gestellt werden
• 2) Der BT-Master kann die BT-Schlitz-Zuteilung für den eSCO-Verkehr ändern, um die Verzögerungs-Anforderung wieder zu erfüllen (immer nur mit dem dritten oben beschriebenen Ansatz möglich).

When LTE performs a hand over during the VoLTE call from a first cell to a second cell, the LTE system clock in the first cell may be in phase from the LTE system clock in the second cell (or second sector). differ. A PLC allocation can also be different. As a consequence, the delay between BT and VoLTE traffic patterns may no longer be met:

• 1) Transfer and new PLC allocation can then be provided to BT via NRT messages
• 2) The BT master can change the BT slot allocation for the eSCO traffic to meet the delay request again (always possible only with the third approach described above).

It should be noted that due to the lack of a timestamping mechanism, it may not yet be possible to ensure that BT can directly derive the VoLTE subframe positions from the indication in NRT messages. If not, the BT unit can detect it by monitoring the LTE UL gap envelope (RT interface) using the PLC period information. Since it may take several VoLTE cycles to reach VoLTE-sync in this way, the BT may have a blind eSCO plan at startup and schedule it again once the VoLTE subframe has been identified.

This mechanism can be considered optimized for VoLTE with a 20 ms period, but it can be used for any PLC-based LTE traffic. Only the delay requirements may be adjusted.

• – Koexistenz-freundliche Übergabe
• – SR-Verschiebung
• – ignorieren von UL-Erteilung
• – LTE-Denial-Steuerung (Algorithmus mit Überwachung der Paketfehlerrate)
• – Minimierung der Auswirkungen von LTE-Denial über LTE-HARQ und damit auf die LTE-Verbindungs-Robustheit (z. B. durch einen entsprechenden Algorithmus)
• – Minimierung der Auswirkung auf BT-HFD-Verkehr über VoLTE-Verkehr.

In summary, for LTE WLAN / BT coexistence in the context of protocol mitigation, the following can be provided / performed:

• - Coexistence-friendly delivery
• - SR shift
• - ignore UL grant
• - LTE Denial control (packet error rate monitoring algorithm)
• Minimization of the effects of LTE denial over LTE HARQ and thus on the LTE connection robustness (eg through a corresponding algorithm)
• - Minimizing the impact on BT-HFD traffic over VoLTE traffic.

According to one aspect of the present invention, there is provided a wireless communication device as in 34 shown.

34 shows a wireless communication device 3400 ,

The wireless communication device 3400 has a first transceiver 3401 adapted for transmitting and receiving at least one signal according to a cellular wireless long-distance communication technology and a second transceiver 3401 configured to transmit and receive at least one signal according to a wireless near-range communication technology or a wireless metropolitan area-system communication technology.

The wireless communication device 3400 also has at least one filter 3403 which is connected to the second receiver, the filter having a filter characteristic, and a processor 3404 coupled to the first transceiver and configured to transmit signals having a transmission bandwidth adjusted based on the filter characteristic, for controlling the first transceiver.

The filter is for example a bandpass filter.

The at least one filter is configured, for example, to filter the at least one signal received by the second transceiver in accordance with the filter characteristic.

For example, the at least one filter is arranged to filter the at least one signal received by the second transceiver according to a form of the filter.

The processor may be further configured to adjust the transmission bandwidth by assigning one or more subchannels provided by the first transceiver for signal transmission.

The processor may be further configured to adjust the transmission bandwidth according to a frequency range at which signal suppression by the filter meets a predefined criterion.

For example, the processor is further configured to adjust the transmission bandwidth corresponding to a frequency range at which signal suppression by the filter is greater than a predefined signal suppression threshold.

For example, the processor is further configured to adjust the transmission bandwidth according to a frequency range at which signal suppression by the filter is maximum.

For example, the processor may be configured to adjust the transmission bandwidth based on the content of an instruction message received by the wireless communication device from another wireless communication device (eg, a base station).

For example, the processor may be configured to adjust the transmission bandwidth according to a transmission bandwidth control message received from a second communication device.

For example, the second communication device is a wireless base station.

For example, the processor is configured to generate a transmission bandwidth request message indicating one or more transmission bandwidths that the processor requests to assign the signal transmission.

The processor is configured, for example, to generate a filter characteristic message containing information about the filter characteristic of the filter.

For example, the first transceiver is configured to transmit and receive signals in accordance with a Third Generation Partnership Project wireless communication technology.

For example, the first transceiver is configured to transmit and receive signals in accordance with a 4G wireless communication technology.

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

• • drahtlose Bluetooth Kommunikationstechnologie,
• • drahtlose ULtra Wide Band Kommunikationstechnologie,
• • drahtlose Wireless Local Area Network Kommunikationstechnologie,
• • drahtlose Infrared Data Association Kommunikationstechnologie,
• • drahtlose Z-Wave Kommunikationstechnologie,
• • drahtlose ZigBee Kommunikationstechnologie,
• • drahtlose HIgh PErformance LAN Kommunikationstechnologie,
• • drahtlose IEEE 802.11 Kommunikationstechnologie, und
• • drahtlose Digital Enhanced Cordless Kommunikationstechnologie,

zu senden und zu empfangen.According to one aspect of this disclosure, the second transceiver is configured to receive signals according to wireless near-range communication technology selected from the group consisting of:

• • wireless Bluetooth communication technology,
• • ULtra Wide Band wireless communication technology,
• Wireless wireless local area network communication technology,
• • wireless Infrared Data Association communication technology,
• • wireless Z-Wave communication technology,
• • wireless ZigBee communication technology,
• • wireless HIgh PErformance LAN communication technology,
• • wireless IEEE 802.11 Communication technology, and
• • wireless Digital Enhanced Cordless communication technology,

to send and receive.

• • drahtlose Worldwide Interoperability for Microwave Access Kommunikationstechnologie,
• • drahtlose WiPro Kommunikationstechnologie,
• • drahtlose High PerformanceRadio Metropoliten-Area-System Kommunikationstechnologie, und
• • drahtlose 802.16m Advanced Air Interface Kommunikationstechnologie.

zu senden und zu empfangen. The second transceiver is, for example, set up signals according to a wireless metropolitan area system communication technology selected from the group consisting of:

• • Wireless Worldwide Interoperability for Microwave Access Communication Technology,
• • wireless WiPro communication technology,
• • wireless high performance radio metropolitan area system communication technology, and
• • Wireless 802.16m Advanced Air Interface communication technology.

to send and receive.

According to one aspect of this disclosure, a method for controlling (or operating) a wireless communication device, as in 35 presented, provided.

35 shows a flowchart 3500 ,

In 3501 For example, signals are transmitted and received according to a cellular wireless long-distance communication technology.

In 3502 For example, signals are transmitted and received according to wireless near-range communication technology or wireless metropolitan area-system communication technology.

In 3503 For example, signals received according to a wireless near-field communication technology or a wireless metropolitan area-system communication technology are filtered by a filter according to a filter characteristic of the filter.

In 3504 For example, signals are transmitted according to a cellular wireless long-distance communication technology using a transmission bandwidth set based on the filter characteristic of the filter.

The setting of the transmission bandwidth may include assigning one or more sub-channels of one or more channels intended for signal transmission according to the wireless wide-area communication technology.

Adjusting the transmission bandwidth may include adjusting the transmission bandwidth corresponding to a frequency range at which signal suppression by the filter meets a predefined criterion.

For example, the transmission bandwidth is set according to a frequency range at which signal suppression by the filter is greater than a predefined signal suppression threshold.

For example, the transmission bandwidth is set corresponding to a frequency range at which signal suppression by the filter is maximum.

For example, the processor may set the transmission bandwidth based on the content of an instruction message received by the wireless communication device from another wireless communication device (eg, a base station).

For example, the transmission bandwidth is set in accordance with a transmission bandwidth control message received from a second communication device.

The second communication device is, for example, a wireless base station.

The method may further include generating a transmission bandwidth request message indicating one or more transmission bandwidths that the processor requests for assigning the signal transmission.

The method may further include generating a filter characteristic message including information about the filter characteristic of the filter.

According to one aspect of this disclosure, the transmission and reception of signals according to wireless long-distance communication technology includes transmitting and receiving signals according to a third-party partnership project ("Third Generation Partnership Project") communication technology.

According to one aspect of this disclosure, the transmission and reception of signals according to wireless long-distance communication technology includes transmitting and receiving signals according to wireless 4G communication technology.

For example, the transmission and reception of signals according to wireless long-distance communication technology includes transmitting and receiving signals according to a wireless long-term evolution communication technology.

• • drahtlose Bluetooth Kommunikationstechnologie,
• • drahtlose ULtra Wide Band Kommunikationstechnologie,
• • drahtlose Wireless Local Area Network Kommunikationstechnologie,
• • drahtlose Infrared Data Association Kommunikationstechnologie,
• • drahtlose Z-Wave Kommunikationstechnologie,
• • drahtlose ZigBee Kommunikationstechnologie,
• • drahtlose HIgh PErformance LAN Kommunikationstechnologie,
• • drahtlose IEEE 802.11 Kommunikationstechnologie, und
• • drahtlose Digital Enhanced Cordless Kommunikationstechnologie,

auf.Sending and receiving signals according to wireless near-range communication technology includes, for example, transmitting and receiving signals according to a wireless near-range communication technology selected from the group consisting of:

• • wireless Bluetooth communication technology,
• • ULtra Wide Band wireless communication technology,
• Wireless wireless local area network communication technology,
• • wireless Infrared Data Association communication technology,
• • wireless Z-Wave communication technology,
• • wireless ZigBee communication technology,
• • wireless HIgh PErformance LAN communication technology,
• • wireless IEEE 802.11 Communication technology, and
• • wireless Digital Enhanced Cordless communication technology,

on.

• • drahtlose Worldwide Interoperability for Microwave Access Kommunikationstechnologie,
• • drahtlose WiPro Kommunikationstechnologie,
• • drahtlose High PerformanceRadio Metropoliten-Area-System Kommunikationstechnologie, und
• • drahtlose 802.16m Advanced Air Interface Kommunikationstechnologie,

auf.The transmission and reception of signals according to a wireless metropolitan area system communication technology includes, for example, transmitting and receiving signals according to a wireless metropolitan area system communication technology consisting of:

• • Wireless Worldwide Interoperability for Microwave Access Communication Technology,
• • wireless WiPro communication technology,
• • wireless high performance radio metropolitan area system communication technology, and
• • wireless 802.16m Advanced Air Interface communication technology,

on.

In the wireless communication device 3400 For example, the first transceiver corresponds to the LTE subsystem 2101 , the second transceiver corresponds to the WLAN / Bluetooth communication circuit 2101 , The processor may correspond to a first controller of the first transceiver. For example, the first transceiver of the communication circuit 2014 correspond. The first processor may be, for example, the RT arbitration unit 2111 correspond (or include).

Alternatively, each of the corresponding tasks may be performed by the application processor 2105 be executed.

Further examples of LTE / BT / WLAN coexistence are given below.

The NRT arbiter 2108 uses a mix of application request (from the connectivity and LTE apps) and context information from both cores, ie LTE and Bluetooth or WLAN (eg Band, Bandwidth, EARFCN) for arbitration, and displays static information like selected frequency bands or selected performance levels, LTE and connectivity (ie Bluetooth or WLAN). It can also provide indications or indications to the RT arbiter located in the LTE subsystem.

For example, the NRT arbiter arbitrates 2108 not between WLAN and BT (arbitration between these is done for example by means of the connectivity chip).

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

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

The algorithm is in the NRT arbitration unit 2108 executed. It is split into two subroutines:

Subroutine 1 is activated each time the LTE subsystem 2101 stores in a new cell while BT is active (eg, BT status is displayed separately using the NRT coexistence interface). It determines the frequency range in which BT can safely be run together with LTE under worst case conditions. Subroutine 1 is in 36 shown

36 shows a message flow diagram 3600 ,

The message flow is between an NRT arbiter 3601 , the NRT arbiter 2108 corresponds, and a BT communication circuit 3602 that of the WLAN / BT communication circuit 2102 corresponds, instead.

In 3603 loads the NRT arbiter 3601 Parameters of a non-volatile memory. These can apply 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 around 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 (eg, Band7Filter (, 1) (or Rx Filter (, 1)).

• – LTE-Band
• – BT max tolerierbare Blockinterferenz
• – BT max tolerierbare In-Band Störinterferenz
• – LTE-freq
• – ISM-RX-Filterkurvenform
• – LTE-Tx-OOB-Rauschen
• – Antennenisolation

In 3604 calculates the NRT arbiter 3601 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 interference
• - LTE freq
• - ISM-RX filter waveform
• - LTE Tx OOB noise
• - Antenna isolation

BT_SAFE_RX_FREQ_MIN, BT_SAFE_RX_FREQ_MAX specifies the ISM frequency range (1 Mhz accuracy) that will meet the converging (parallel) targets (de-sense, throughput losses) in the worst case (LTE max power, max bandwidth, BT-RX @ sensitivity). These are z. Static, so that they can be precalculated and stored in a look-up table.

In 3605 , the NRT arbiter transmits or communicates 3601 BC_SAFE_RX_FREQ_MIN and BT_SAFE_RX_FREQ_Max to the BT communication circuit 3602 ,

In 3606 stores the BT communication circuit 3602 BT_SAFE_RX_FREQ_MIN and BT_SAFE_RX_FREQ_MAX and confirm receipt of these parameters in 3607 , Subroutine 2 is shown in FIG 37 shown.

37 shows a message flow diagram 3700 ,

The message flow is between an NRT arbiter 3701 , the NRT arbiter 2108 corresponds, and a BT communication circuit 3702 that of the WLAN / BT communication circuit 2102 corresponds, instead.

Subroutine 2 is activated each time the BT communication circuit 3702 its AFH plan or AFH network plan in 3703 modified.

This modification can, for. B. autonomously on the BT side, either for transport purposes or for coexistence purposes, carried out.

In 3704 stores the BT communication circuit 3702 the minimum BT frequency and the maximum BT frequency according to the modified AFH plan.

In 3705 checks the BT core (ie the BT communication circuit 3702 ), if its complete AFH plan is contained within the protected frequency range and shows the result to the NRT arbiter 3701 (in this example by means of a single-bit display) in 3706 at. When the information is received, the NRT arbiter turns on 3701 the real-time interface (or a subset of the real interface, whereby a distinction between BT and WLAN is possible) in 3907 on / off and sends an acknowledgment to the BT communication circuit 3702 in 3708 ,

In the event that it is not possible to differentiate between WiFi and BT in any way, the parameters BT_RX_KILL and WIFI_RX_KILL (see 39 ) both are switched off and then the real-time interface is switched off. Otherwise, the real-time interface is switched on.

In addition, the NRT arbiter can execute an NRT algorithm to protect WLAN from LTE-FDD.

The algorithm is in the NRT arbitration unit 2108 executed. It is divided into two subroutines:
Subroutine 1 is activated each time the LTE subsystem 2101 stores in a new cell while WLAN is active (for example, the WLAN status is displayed separately using the NRT coexistence interface). It determines the frequency range in which WLAN can be safely executed together with LTE. Subroutine 1 is in 38 shown.

38 shows a message flow diagram 3800 ,

The message flow is between an NRT arbiter 3801 , the NRT arbiter 2108 corresponds, and a WLAN communication circuit 3802 that of the WLAN / BT communication circuit 2102 corresponds, instead.

In 3803 loads an NRT arbiter 3801 Parameters of a nonvolatile 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 spectral power density), WLAN_MAX_BLKR (WLAN maximum tolerable block interference), WLAN_MAX_LIN (WLAN maximum tolerable in-band interference interference), L_OOB () (contains LTE transmitter OUT-OFF band spectrum (relative to in-band power)) and ISM-RX filter waveform parameters (eg, Band7 filter) (FIG. BW) (or Rx Filtr (, BW)). Band7Filter (, BW) is the ISM-RX filter waveform that is integrated across the LTE cell BW. 5 Band7Filter tables are stored in the NVM corresponding to BW = 1, 5, 10, 15, 20 MHz.

• – LTE-Band
• – WLAN max tolerierbare Block-Interferenz
• – WLAN max tolerierbare IN-Band-Störinterferenz
• – LTE-FREQ
• – ISM-RX-Filterkurvenform
• – LTE-Tx-OOB-Rauschen
• – Antennenisolation.

In 3804 calculates the NRT arbiter 3801 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 interference
• - LTE FREQ
• - ISM-RX filter waveform
• - LTE Tx OOB noise
• - Antenna isolation.

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

In 3805 communicates or transmits the NRT arbiter 3801 WLAN_SAFE_RX_FREQ_MIN and WLAN_SAFE_RX_FREQ_MAX to the WLAN communication circuit 3802 ,

In 3806 saves the WLAN communication circuit 3802 WLAN_SAFE_RX_FREQ_MIN and WLAN_SAFE_RX_FREQ_MAX and confirm receipt of these parameters in 3807 , Subroutine 2 is in 39 shown.

39 shows a message flow diagram 3900 ,

The message flow is between an NRT arbiter 3901 , the NRT arbiter 2108 corresponds, and a WLAN communication circuit 3902 that of the WLAN / BT communication circuit 2102 corresponds, instead.

Subroutine 2 is activated each time the WLAN communication circuit 3902 their list of active Wi-Fi channels in 3903 modified.

This modification can, for. Autonomously on the WLAN side, either for traffic purposes or for coexistence purposes.

In 3904 saves the WLAN communication circuit 3902 then the minimum WLAN frequency and the maximum WLAN frequency according to the changed list of active WLAN channels.

In 3905 checks the WLAN core (ie the WLAN communication circuit 3902 ), if its WLAN channels are in the safe frequency range, and shows the result to the NRT arbiter 3901 (in this case by means of a single-bit display) in 3906 at. When the information is received, the NRT arbiter switches 3901 the real-time interface (or a subset of the real interface, if a distinction between BT and WLAN is possible) in 3907 on / off, and sends an acknowledgment to the WLAN communication circuit 3902 in 3908 , In the event that it is not possible to differentiate between WiFi and BT in any way, the parameters BT_RX_KILL (see 39 ) and WiFi_RX_KILL are both turned off and then the real-time interface is off. Otherwise the real-time interface is switched on.

Hereinafter, further examples of the non-real-time application interface, the non-real-time coexistence interface and parameters stored in the non-volatile memory will be given.

The NRT application interface transmits messages that carry 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. parameter Info bits I / O description PERIOD 16 I / O Required application service duration ms. Overwriting any prior use DURATION 6 I / O Required application service duration ms. Overwriting any prior use Table 11: Non-real-time application coexistence interface

The NRT coexistence interface transmits messages bearing CWS information. The "I / O" field has the following meaning for parameters: "I" means from CWS to NRTA, "O" means from NRTA to CWS. parameter Info bits I / O description WLAN_ACTIVE 1 I NRT controller is turned on by this display -> Replaces IS_COEX previously in NRT Apps I / F WLAN_SAFE_RX 1 I Indication that WLAN operation takes place in the safe frequency range. (used to turn off the RT-I / F or the Wi-Fi portion of it) WLAN_BANDWIDTH 2 I WLAN bandwidth 0 = 20 MHz, 1 = 40 MHz, 2 = 80MHz, 3 = Invalid BT_ACTIVE 1 I NRT controller is turned on by this display -> Replaces IS_COEX previously in NRT Apps I / F BT_SAFE_RX 1 I Indication that BT operation is in the safe frequency range. (used to turn off the RT-I / F or the BT portion thereof) LTE_ACTIVE 1 O Used by CWS -> Display for CWS to release the restrictions associated with LTE WLAN_LTE_EN 1 O Transmission of WLAN packets shorter than 2 LTE-OFDM symbols For future use: only LTE-TDD LTE_SPS_PATTER N 24 O PLC periodicity (ms): 11 bits PLC event duration (ms): 9 bits PLC initial offset (subframe offset in first LTE frame where PLC is applied): 4 bits TBC: Indicates LTE periodic activity for the connectivity chip. He can then evaluate these for his own planning. LTE_BITMAP 10 × 2 O 0 = Special Subframe 1 = RX LTE Subframe 2 = TX LTE Subframe For future use: 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 applied) For future use (LTE-TDD). For use by NRT controllers to evaluate WLAN interference over LTE (useful in tethering case where WLAN Tx performance can be reduced). Table 12: Non-real-time coexistence interface

The following table lists examples of parameters used in nonvolatile memory. NVM parameters NRT_capability BT_Max_PSD BT_channel_freq Nmin P_LTE_max L_OOB Band7Filter lant Table 13: NVM parameters

According to one aspect of the disclosure, a wireless communication device, as in FIG 40 presented, provided.

40 shows a wireless communication device 4000 ,

The wireless communication device 4000 has a first transceiver 4001 adapted for transmitting and receiving signals according to a cellular wireless long-distance communication technology and a second transceiver 4002 configured for transmitting and receiving signals according to a wireless near-range communication technology or a wireless metropolitan area-system communication technology.

The wireless communication device 4000 also has at least one filter 4003 connected to the second receiver, the filter having a filter characteristic.

Next, the wireless communication device 4000 a message generator 4004 , configured to generate a message with a suggestion for setting a transmission bandwidth for the first transceiver, the suggestion being based on the filter characteristic.

For example, the first transceiver is arranged to send the message to another wireless communication device (e.g., a base station).

According to one aspect of this disclosure, a method for controlling (or operating) a wireless communication device, as in 41 presented, provided.

41 shows a flowchart 4100 ,

The flowchart 4100 illustrates a method for controlling (or operating) a wireless communication device.

In 4101 A first transceiver transmits and receives at least one signal according to a wireless long-distance communication technology.

In 4102 A second transceiver transmits and receives at least one signal according to a wireless near-range communication technology or a wireless metropolitan area-system communication technology.

In 4103 The wireless communication device filters, by means of a filter, the signals received according to a wireless near-range communication technology or a wireless metropolitan area-system communication technology according to a filter characteristic of the filter.

In 4104 The wireless communication device generates a message with a suggestion for setting a transmission bandwidth for the first transceiver, which proposal is based on the filter characteristic.

The wireless communication device may further send the message to another communication device.

It should be noted that examples related to the wireless communication device 3400 and in 35 in the same way for the wireless communication device 4000 and that in 41 shown methods are valid.

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 to be considered as indicated by the appended claims and all changes which come within the meaning and range of the invention should be considered as indicated.

QUOTES INCLUDE IN THE DESCRIPTION

This list of the documents listed by the applicant has been generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Cited non-patent literature

• IEEE 802.11 [0005]
• IEEE 802.11 [0101]
• IEEE 802.11n [0101]
• IEEE 802.11a [0101]
• IEEE 802.11g [0101]
• IEEE 802.11n [0101]
• EEE 802.11VHT [0101]
• IEEE 802.16 [0101]
• IEEE 802.16m [0101]
• IEEE 802.11a [0102]
• IEEE 802.11g [0102]
• IEEE 802.11n [0102]
• IEEE 802.11VHT [0102]
• IEEE 802.16m [0103]
• IEEE 802.16m [0103]
• IEEE 802.11 [0436]
• IEEE 802.11 [0456]

Claims (23)

Wireless communication device, comprising: a first transceiver configured to transmit and receive at least one signal according to a cellular wireless wide area communication technology; a second transceiver configured to transmit and receive at least one of a wireless near-range communication technology and a wireless metropolitan area-system communication technology; at least one filter connected to the second receiver, the filter having a filter characteristic; and a processor connected to the first transceiver and configured to control the first transceiver to transmit signals having a transmission bandwidth set based on the filter characteristic. The wireless communication device of claim 1, wherein the at least one filter is configured to filter the at least one signal received from the second transceiver according to the filter characteristic. The wireless communication device of claim 2, wherein the at least one filter is configured to filter the at least one signal received by the second transceiver according to a form of the filter. The wireless communication device of one of claims 1 to 3, wherein the processor is further configured to adjust the transmission bandwidth by assigning one or more sub-channels provided by the first transceiver for signal transmission. The wireless communication device of any one of claims 1 to 4, wherein the processor is further configured to adjust the transmission bandwidth according to a frequency range at which signal suppression by the filter meets a predefined criterion. The wireless communication device of claim 5, wherein the processor is further configured to adjust the transmission bandwidth according to a frequency range at which signal suppression by the filter is greater than a predefined signal suppression threshold. The wireless communication device of claim 6, wherein the processor is further configured to adjust the transmission bandwidth according to a frequency range at which signal suppression by the filter is maximum. The wireless communication device of claim 1, wherein the processor is configured to set the transmission bandwidth based on the content of an instruction message received by the wireless communication device from another wireless communication device. The wireless communication device according to any one of claims 1 to 8, wherein the processor is configured to set the transmission bandwidth according to a transmission bandwidth control message received from a second communication device. The wireless communication device of claim 9, wherein the second communication device is a wireless base station. The wireless communication device of any one of claims 1 to 10, wherein the processor is configured to generate a transmission bandwidth request message indicating one or more transmission bandwidths that the processor requests for assigning the signal transmission. The wireless communication device of any one of claims 1 to 11, wherein the processor is arranged to generate a filter characteristic message containing information about the filter characteristic of the filter. The wireless communication device according to any one of claims 1 to 12, wherein the first transceiver is arranged to transmit and receive signals according to a wireless third generation partnership project communication technology. The wireless communication device of one of claims 1 to 13, wherein the first transceiver is configured to transmit and receive signals in accordance with a wireless 4G communication technology. The wireless communication device of claim 14, wherein the first transceiver is configured to transmit and receive signals according to a wireless long term evolution communication technology. Wireless communication device according to one of claims 1 to 15, wherein the second transceiver is configured to transmit and receive signals according to wireless near-range communication technology selected from a group consisting of: wireless Bluetooth communication technology; wireless UL wide band communication technology; Wireless Wireless Local Area Network Communication Technology; wireless infrared data association communication technology; wireless Z-Wave communication technology; wireless ZigBee communication technology; wireless HIgh PErformance LAN communication technology; wireless IEEE 802.11 communication technology; and Wireless Digital Enhanced Cordless Communication Technology. Wireless communication device according to one of claims 1 to 16, wherein the second transceiver is arranged 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 Communication Technology; wireless WiPro communication technology; wireless high-performance radio metropolitan area system communications technology; and wireless 802.16m Advanced Air Interface communication technology. A method of controlling a wireless communication device, the method comprising: transmitting and receiving signals according to a cellular wireless long-distance communication technology; Sending and receiving signals according to a wireless near-range communication technology or a wireless metropolitan area-system communication technology; Filtering, by a filter based on a filter characteristic of the filter, signals received according to a wireless near-range communication technology or a wireless metropolitan area-system communication technology; Transmitting signals according to a cellular wireless long-distance communication technology using a transmission bandwidth set based on the filter characteristic of the filter. The method of claim 18, wherein adjusting the transmission bandwidth comprises assigning one or more sub-channels of one or more channels intended for signal transmission in accordance with wireless long-distance communication technology. Wireless communication device, comprising: a first transceiver configured to transmit and receive signals according to a cellular wireless long-distance communication technology; a second transceiver configured to transmit and receive signals according to a wireless near-range communication technology or a wireless metropolitan area-system communication technology; at least one filter connected to the second receiver, the filter having a filter characteristic; and a message generator adapted to generate a message having a suggestion for setting a transmission bandwidth for the first transceiver, the suggestion being based on the filter characteristic. The wireless communication device of claim 20, wherein the first transceiver is configured to transmit the message to another wireless communication device. A method of controlling a wireless communication device, comprising: a first transceiver transmitting and receiving at least one signal according to a cellular wireless long-distance communication technology; a second transceiver transmits and receives at least one of a wireless near-range communication technology and a wireless metropolitan area-system communication technology; Filtering signals received according to a wireless near-field communication technology or a wireless metropolitan area system communication technology by means of a filter according to a filter characteristic of the filter; and generating a message with a proposal for setting a transmission bandwidth for the first transceiver, the suggestion being based on the filter characteristic. The method of claim 22, further comprising sending the message to another communication device.

Images