CN103384158A - Wireless communication apparatus and method for controlling same - Google Patents

Abstract

The invention relates to a radio communication device and a method for controlling a radio communication device. According to an aspect of this disclosure, there is provided a radio communication device, comprising: a first transceiver configured to transmit and receive at least one signal according to cellular wide area radio communication technology; a second transceiver configured to transmit and receive at least one signal according to short-range radio communication technology or metro system radio communication technology transmits and receives at least one signal; at least one filter coupled to a second receiver, said filter having filtering characteristics; and a processor coupled to said first transceiver and said The processor is configured to control the first transceiver to transmit a signal having a transmission bandwidth set based on the filtering characteristic.

Description

Radio communication device and method for controlling radio communication device

Cross References to Related Applications

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

technical field

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

Background technique

A mobile communication terminal may support multiple radio access technologies such as cellular radio communication technologies such as LTE (Long Term Evolution) and short-range radio communication technologies such as Bluetooth or WLAN or metro system radio communication technologies such as WiMax. Although typically different frequency bands are allocated to such different radio access technologies, for example when a mobile communication terminal wants to operate two different radio access technologies in parallel there may still be interference between them. It is desirable to avoid such interference and improve coexistence between different radio access technologies.

Contents of the invention

According to an aspect of the present disclosure, there is provided a radio communication device, the radio communication device comprising: a first transceiver configured to transmit and receive at least one signal according to cellular wide area radio communication technology; a second transceiver configured to for transmitting and receiving at least one signal according to a short-range radio communication technique or a metropolitan area system radio communication technique; at least one filter coupled to a second receiver, said filter having filtering characteristics; and a filter coupled to said first transceiver a processor and the processor is configured to control the first transceiver to transmit a signal having a transmission bandwidth set based on the filter characteristic.

According to another aspect of the present disclosure, a method for controlling a radio communication device corresponding to the above-mentioned radio communication device is provided.

Furthermore, a radio communication device is provided, the radio communication device comprises a first transceiver configured to transmit and receive at least one signal according to a cellular wide area radio communication technique; a second transceiver, Configured to transmit and receive at least one signal according to a short-range radio communication technique or a metropolitan area system radio communication technique; at least one filter coupled to a second receiver, the filter having filtering characteristics; and a message generator configured to have A proposal message to set a transmission bandwidth for the first transceiver, wherein the proposal is based on the filtering characteristic.

There is also provided a method for controlling a radio communication device corresponding to the above radio communication device.

Description of drawings

In the drawings, like reference characters generally refer to the same parts throughout the different views. The drawings are not necessarily to scale, emphasis instead generally being placed upon illustrating the principles of the invention. In the following description, various aspects are described with reference to the following drawings, in which:

Figure 1 illustrates a communication system according to one aspect of the present disclosure.

Figure 2 shows a frequency band diagram.

Figure 3 shows the test system.

Figure 4 shows the measurement results for the first test case.

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

Figure 6 shows the measurement results for the second test case.

Fig. 7 shows modified measurement results for a second test case of different broadband noise.

Figure 8 shows the measurement results for the second test case.

Fig. 9 shows modified measurement results for a second test case of different broadband noise.

FIG. 10 illustrates a communication terminal according to various aspects of the present disclosure.

Fig. 11 shows the frame structure.

Figure 12 shows a data transfer diagram.

Figure 13 shows the transmission diagram.

Figure 14 shows a transmission diagram.

Figure 15 shows a transmission diagram.

Figures 16 and 17 depict WLAN and Bluetooth usage cases over LTE-FDD for full connectivity traffic support relying only on the impact of LTE reject and LTE deny.

FIG. 18 illustrates communication circuitry according to one aspect of the disclosure.

FIG. 19 illustrates a state and arbitration unit according to an aspect of the disclosure.

Figure 20 shows a transmission diagram.

Fig. 21 shows a communication terminal.

Fig. 22 shows a flowchart.

Figure 23 shows a transmission diagram.

Figure 24 shows a message flow diagram.

Fig. 25 shows a frequency allocation diagram.

Figure 26 shows a message flow diagram.

Figure 27 shows a transmission diagram.

Figure 28 shows a transmission diagram.

Figure 29 shows a transmission diagram.

Figure 30 shows a transmission diagram.

Figure 31 shows a transmission diagram.

Figure 32 shows a transmission diagram.

Figure 33 shows a transmission diagram.

Fig. 34 shows a radio communication device.

Fig. 35 shows a flowchart.

Figure 36 shows a message flow diagram illustrating a procedure for BT/LTE coexistence.

Figure 37 shows a message flow diagram illustrating a procedure for BT/LTE coexistence.

Figure 38 shows a message flow diagram illustrating a procedure for WiFi/LTE coexistence.

Figure 39 shows a message flow diagram illustrating a procedure for WiFi/LTE coexistence.

Fig. 40 shows a radio communication device.

Fig. 41 shows a flowchart.

Detailed ways

The following detailed description refers to the accompanying drawings that show, by way of illustration, specific details and aspects of the disclosure in which the invention may be practiced. These aspects of the disclosure are described in sufficient detail to enable those skilled in the art to practice the invention. Other aspects of this disclosure may be utilized and structural, logical, and electrical changes may be made without departing from the scope of the present invention. The various aspects of this disclosure are not necessarily mutually exclusive, as certain aspects of this disclosure can be combined with one or more other aspects of this disclosure to form new aspects.

3GPP (3rd Generation Partnership Project) has introduced LTE (Long Term Evolution) into Release 8 of the UMTS (Universal Mobile Telecommunications System) standard.

The air interface of the LTE communication system is known as E-UTRA (Evolved Universal Terrestrial Radio Access) and is commonly referred to as '3.9G'. In December 2010, the ITU acknowledged that current versions of LTE and other evolved 3G technologies that do not meet the requirements of "IMT-Advanced" represent precursors to IMT-Advanced and relative to the performance and capabilities of the initial third-generation systems already deployed Current versions of LTE and other evolved 3G technologies that do not meet the requirements of 'IMT-Advanced' may still be considered '4G' if there is a significant level of improvement in this area. For this reason, LTE is also sometimes referred to as '4G' (mainly for marketing reasons).

Compared to its predecessor UMTS, LTE provides an air interface that is further optimized for packet data transmission by improving system capacity and spectral efficiency. Among other enhancements, the maximum net transfer rate has been significantly increased to 300 Mbps in the downlink transfer direction and to 75 Mbps in the uplink transfer direction. LTE supports scalable bandwidth from 1.4 MHz to 20 MHz and is based on new multiple access methods such as OFDMA (Orthogonal Frequency Division Multiple Access)/TDMA (Time Division Multiple Access) and SC-FDMA (Single Carrier-Frequency Division Multiple Access)/TDMA in the uplink direction (handset to tower). OFDMA/TDMA is a multicarrier multiple access method in which a subscriber (ie a mobile terminal) is provided with a defined number of subcarriers on the frequency spectrum and a defined transmission time for the purpose of data transmission. The RF (Radio Frequency) capability for transmission and reception of mobile terminals (also called User Equipment (UE), such as cellular phones) according to LTE has been set at 20 MHz. A physical resource block (PRB) is a baseline allocation unit of a physical channel defined in LTE. It consists of a matrix of 12 subcarriers x 6 or 7 OFDMA/SC-FDMA symbols. At the physical layer, a pair of one OFDMA/SC-FDMA symbol and one subcarrier is represented as a 'resource element'. A communication system used according to an aspect of the present disclosure and which is, for example, a communication system according to LTE is described below with reference to FIG. 1 .

FIG. 1 illustrates a communication system 100 according to one aspect of the present disclosure.

The communication system 100 is a cellular mobile communication system (hereinafter also referred to as a cellular radio communication network), comprising a radio access network (according to LTE (Long Term Evolution), e.g. E-UTRAN, Evolved UMTS (Universal Mobile Telecommunications System) terrestrial radio Access Network) 101 and Core Network (Evolved Packet Core according to LTE, eg EPC) 102. The radio access network 101 may comprise base (transceiver) stations (eg eNodeBs, eNBs according to LTE) 103 . Each base station 103 provides radio coverage for one or more mobile radio cells 104 of the radio access network 101 .

A mobile terminal (also called UE, User Equipment) 105 located in a mobile radio cell 104 can communicate with the core network 102 and with other mobile terminals via a base station providing coverage in the mobile radio cell (in other words operating the mobile radio cell). 105 communications. In other words, the base station 103 operating the mobile radio cell 104 in which the mobile terminal 105 is located provides: E-UTRA user plane termination including PDCP (Packet Data Convergence Protocol) layer, RLC (Radio Link Control) layer and MAC (Media Access Control ) layer; and a control plane termination including the RRC (Radio Resource Control) layer towards the mobile terminal 105 .

Control and user data are transmitted on the basis of a multiple access method via an air interface 106 between a base station 103 and a mobile terminal 105 located in a mobile radio cell 104 operated by the base station 103 .

The base stations 103 are interconnected with each other by means of a first interface 107, eg an X2 interface. The base station 103 is also connected to the core network by means of a second interface 108, e.g. an S1 interface, e.g. to an MME (Mobility Management Entity) 109 via an S1-MME interface and to a Serving Gateway (S-GW) by means of an S1-U interface. ) 110. The S1 interface supports a many-to-many relationship between the MME/S-GW 109, 110 and the base station 103, i.e. the base station 103 can be connected to more than one MME/S-GW 109, 110 and the MME/S-GW 109, 110 may be connected to more than one base station 103 . This enables network sharing in LTE.

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

In case of LTE, the radio access network 101, i.e. E-UTRAN 101 in case of LTE, can be seen to comprise a base station 103, i.e. eNB 103 in case of LTE, which provides E-UTRA towards UE 105 User plane (PDCP/RLC/MAC) and control plane (RRC) protocol termination.

The eNB 103 may for example host the following functions:

■ Radio resource management functions: radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UE 105 in both uplink and downlink (scheduling);

■ IP header compression and user data flow encryption;

■ select the MME 109 at UE 105 attach when it can be determined from the information provided by the UE 105 that there is no route to the MME 109;

■ routing of user plane data towards the Serving Gateway (S-GW) 110;

■ Scheduling and transmission of paging messages (from MME);

■ Scheduling and transmission of broadcast information (from MME 109 or O&M (operation and maintenance);

■ Measurement and measurement reporting configuration for mobility and scheduling;

■ (from MME 109) dispatch and transmission of PWS (Public Warning System, which includes ETWS (Earthquake and Tsunami Warning System) and CMAS (Commercial Mobile Warning System)) messages;

■ CSG (Closed Subscriber Group) processing.

Each base station of the communication system 100 controls communication within its geographical coverage area, ie its mobile radio cell 104 (ideally represented by a hexagonal shape). When a mobile terminal 105 is located within a mobile radio cell 104 and is camping on said mobile radio cell 104 (in other words, registering with this mobile radio cell 104), it communicates with the base station 103 controlling this mobile radio cell 104 communication. When a call is initiated by the user of the mobile terminal 105 (mobile-originated call) or is addressed to the mobile terminal 105 (mobile-terminated call), the ) A radio channel is established between the base stations 103 of the mobile radio cell 104 . If the mobile terminal 105 moves away from the original mobile radio cell 104 in which the call was established and the signal strength of the radio channel set up in the original mobile radio cell 104 weakens, the communication system can initiate a call to the mobile radio cell 104 to which the mobile terminal 105 has moved. Transfer of the radio channel of another mobile radio cell 104 .

As the mobile terminal 105 continues to move throughout the coverage area of the communication system 100 , control of the call may be transferred between adjacent mobile radio cells 104 . The transfer of a call from the mobile radio cell 104 to the mobile radio cell 104 is called handover (or handover).

In addition to communication via the E-UTRAN 102, the mobile terminal 105 may support communication via a Bluetooth (BT) communication connection 111, e.g., with another mobile terminal 112 and communication via a WLAN communication connection 113 with a WLAN access point (AP) 114 . Via the access point 114 , the mobile terminal can access a communication network 115 , such as the Internet, which can be connected to the core network 102 .

LTE operates in the newly allocated frequency band set. The main difference introduced by this new set of frequency bands compared to those used for 2G/3G communication systems is that two of them are next to the ISM bands in which WLAN and Bluetooth operate.

This is illustrated graphically in FIG. 2 .

FIG. 2 shows a frequency band diagram 200 .

In frequency band diagram 200, frequencies are included from left to right.

From left to right, LTE band 40 201, ISM band 202, LTE band 7 UL (uplink), guard band 204, LTE band 38 205 and LTE band 7 DL (downlink) 206 are shown. Accordingly, frequency band diagram 200 illustrates spectrum allocated to LTE around ISM band 202 .

The LTE band 40 201 used by LTE-TDD (Time Division Duplex) is the lower frequency band next to the ISM band 202 without any guard bands in between, while the LTE band 7 204 used for LTE-FDD (Frequency Division Duplex) UL starts with The guard band 203 of 17 MHz is adjacent to the higher frequency band of the ISM band 202 .

In the following, in order to illustrate the coexistence problem (between LTE in this example), the results of actual measurements made with current hardware are given. The three test cases for which results are given are:

1: WLAN affects frequency 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 illustrated schematically in Figure 3.

FIG. 3 shows a test system 300 .

The test system 300 includes: a first communication circuit 301 supporting WLAN and Bluetooth (etc.); and a second communication circuit 302 supporting LTE communication (etc.). Various filters 303, 304, 305, 306 are provided for testing.

Arrow 307 indicates the coexistence case of interest in this example (WLAN/LTE coexistence). It should be noted that in the measurements, the RF (radio frequency) analysis focuses on the interference via the antenna and not on the IC level via pin-to-pin.

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

Figure 4 shows the measurement results for the first test case.

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

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

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

Figure 6 shows the measurement results for the second test case.

Fig. 7 shows modified measurement results for a second test case of different broadband noise.

From the second test case, it can be seen that using the higher part of the band 40 desensitizes the entire ISM band. About 75% of the frequency combinations had a desensitization greater than 10 dB.

In a third test case, the LTE band 7 UL 204 is the interferer and the ISM band 202 is the receiver (or interference victim).

Figure 8 shows the measurement results for the second test case.

Fig. 9 shows modified measurement results for a second test case of different broadband noise.

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

As can be seen from the test results, with the existing hardware, severe coexistence problems arise in all three test cases.

According to various aspects of the present disclosure, these problems are solved or mitigated using mechanisms applied at the PHY layer and protocol layer and relying, for example, on a mix of software (SW) and hardware (HW) implementations.

Examples are described hereinafter with reference to an exemplary communication terminal as illustrated in FIG. 10 .

FIG. 10 illustrates a communication terminal 1000 according to various aspects of the present disclosure.

For example, communication terminal 1000 is a mobile radio communication device configured in accordance with LTE and/or other 3GPP mobile radio communication technologies. Communication terminal 1000 is also called a radio communication device.

In various aspects of the present disclosure, the communication terminal 1000 may include a processor 1002 such as, for example, a microprocessor (eg, a central processing unit (CPU)) or any other type of programmable logic device (which may, for example, act as a controller). Furthermore, the communication terminal 1000 may comprise a first memory 1004 such as a read only memory (ROM) 1004 and/or a second memory 1006 such as a random access memory (RAM) 1006 . Furthermore, the communication terminal 1000 may comprise a display 1008, such as for example a touch-sensitive display, eg a Liquid Crystal Display (LCD) display or a Light Emitting Diode (LED) display, or an Organic Light Emitting Diode (OLED) display. However, any other type of display may be provided as display 1008 . The communication terminal 1000 may additionally comprise any other suitable output means (not shown), such as eg a speaker or a vibration actuator. Communication terminal 1000 may include one or more input devices, such as keypad 1010 including a plurality of keys. The communication terminal 1000 may additionally comprise any other suitable input means (not shown), such as eg a microphone, eg for voice control of the communication terminal 1000 . Where display 1008 is implemented as a touch-sensitive display 1008 , keypad 1010 may be implemented by touch-sensitive display 1008 . Furthermore, optionally, the communication terminal 1000 may include a coprocessor 1012 to take processing load from the processor 1002 . Furthermore, the communication terminal 1000 may include a first transceiver 1014 and a second transceiver 1018 . The first transceiver 1014 is eg an LTE transceiver supporting radio communication according to LTE and the second transceiver 1018 is eg a WLAN transceiver supporting communication according to the WLAN communication standard or a Bluetooth transceiver supporting communication according to Bluetooth.

The components described above may be coupled to each other via one or more lines (eg, implemented as bus 1016 ). The first memory 1004 and/or the second memory 1006 may be a volatile memory such as DRAM (Dynamic Random Access Memory) or a non-volatile memory such as PROM (Programmable Read Only Memory), EPROM (Erasable PROM), EEPROM (Electrically Erasable PROM) or Flash memory such as Floating Gate Memory, Charge Trap Memory, MRAM (Magnetoresistive Random Access Memory) or PCRAM (Phase Change Random Access Memory) or CBRAM (Conductive Bridge Random Access Memory) ). Program code to be executed and thereby control processor 1002 (and optionally coprocessor 1012 ) may be stored in first memory 1004 . Data to be processed by processor 1002 (and optionally coprocessor 1012 ), eg messages received or to be transmitted via first transceiver 1014 , may be stored in second memory 1006 . The first transceiver 1014 may be configured such that it implements a Uu interface according to LTE. The communication terminal 1000 and the first transceiver 1014 may also be configured to provide MIMO radio transmission.

In addition, the communication terminal 1000 may include a still image and/or video camera 1020 configured to provide video conferencing via the communication terminal 1000 .

Furthermore, the communication terminal 1000 may include a Subscriber Identity Module (SIM), such as a UMTS Subscriber Identity Module (USIM) that identifies a user of the communication terminal 1000 and a subscriber. Processor 1002 may include: audio processing circuitry, such as for example audio decoding circuitry and/or audio encoding circuitry, configured to decode and/or encode audio signals in accordance with one or more of the following audio encoding/decoding techniques: ITU G.711 , Adaptive Multi-Rate Narrowband (AMR-NB), Adaptive Multi-Rate Wideband (AMR-WB), Advanced Multi-Band Excitation (AMBE), etc.

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

For example, each transceiver 1014, 1018 may support one of the following communication technologies:

- short-range radio communication technologies (which may include radio communication technologies such as Bluetooth radio technologies, ultra-wideband (UWB) radio communication technologies, and/or wireless local area network radio communication technologies (such as radio communication standards according to IEEE 802.11 (e.g. IEEE 802.11n))), IrDA (Infrared Data Association), Z-Wave and ZigBee, HiperLAN/2 ((High Performance Radio LAN; 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),

- Metro system radio communication technologies (which may include e.g. Worldwide Interoperability for Microwave Access (WiMAX) (e.g. radio communication standards according to IEEE 802.16, e.g. WiMAX fixed WiMax mobile), WiPro, HiperMAN (High Performance Radio Metropolitan Area Network) and/or or IEEE 802.16m Advanced Air Interface,

- cellular wide area radio communication technologies (which may include, for example, Global System for Mobile Communications (GSM) radio communication technologies, General Packet Radio Service (GPRS) radio communication technologies, Enhanced Data Rates for GSM Evolution (EDGE) radio communication technologies, and/or 3rd Generation Partnership Project (3GPP) radio communication technologies (such as UMTS (Universal Mobile Telecommunications System), FOMA (Free Multimedia Access), 3GPP LTE (Long Term Evolution), 3GPP LTE-Advanced (Long Term Evolution)), CDMA2000 (code Division Multiple Access 2000), CDPD (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) Generation)), W-CDMA (UMTS) (Wideband Code Division Multiple Access (Universal Mobile Telecommunications System)), HSPA (High Speed Packet Access), HSDPA (High Speed Downlink Packet Access), HSUPA (High Speed Uplink Packet Access) Access), HSPA+ (High Speed Packet Access+), UMTS-TDD (Universal Mobile Telecommunications System-Time Division Duplex), TD-CDMA (Time Division-Code Division Multiple Access), TD-CDMA (Time Division-Synchronous Code Division Multiple Access ), 3GPP Rel 8 (pre-4G) (3rd Generation Partnership Project Release 8 (pre-4th generation)), UTRA (UMTS Terrestrial Radio Access), E-UTRA (Evolved UMTS Terrestrial Radio Access), Advanced LTE (4G) (Long Term Evolution Advanced (4th Generation)), cdmaOne (2G), CDMA2000 (3G) (Code Division Multiple Access 2000 (3rd Generation)), EV-DO (Evolution Data Optimized or Evolution-Just Data) , AMPS (1G) (Advanced Mobile Phone System (First Generation)), TACS/ETACS (Total Access Communication System/Extended Total Access Communication System), D-AMPS (2G) (Digital AMPS (Second Generation)) , PTT (Push to Talk), MTS (Mobile Telephone System), IMTS (Improved Mobile Telephone System), AMTS (Advanced Mobile Telephone System), OLT (Norwegian Offentlig Landmobil Telefoni, Public Land Mobile Telephone), MTD (for Mobiletelefonisystem Swedish abbreviation for D, or mobile phone system D), Autotel/PALM (Automatic Public Land Mobile), ARP (Finnish for Autoradiopuhelin, "Car Radio Telephone"), NMT (Nordic Mobile Telephone), Hicap (a high-capacity version of NTT (Nippon Telegraph and Telephone Corporation)), CDPD (Cellular Digital Packet Data), Mobitex, Data TAC, iDEN (Integrated Digital Enhanced Network), PDC (Personal Digital Cellular), CSD (Circuit Switched Data), PHS (Personal Handyphone System ), WiDEN (Wideband Integrated Digital Enhancement Network), iBurst, Unlicensed Mobile Access (UMA, also known also as 3GPP Universal Access Network, or GAN standard)).

Short-range radiocommunication technologies may include the following subfamilies of short-range radiocommunication technologies:

- Personal Area Network (Wireless PAN) radio communication subfamily, which may include eg IrDA (Infrared Data Association), Bluetooth, UWB, Z-Wave and ZigBee; and

- Wireless Local Area Network (W-LAN) radiocommunication subfamily, which may include for example HiperLAN/2 (High Performance Radio LAN; 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).

The metro system radiocommunication technology family may include the following metro system radiocommunication technology subfamilies:

- The Wireless Campus Area Network (W-CAN) radiocommunication subfamily, which can be considered a form of metropolitan area network specific to academic settings and may include, for example, WiMAX, WiPro, HiperMAN (High Performance Radio Metropolitan Area Network) or IEEE 802.16m Advanced Air Interface; and

- Wireless Metropolitan Area Network (W-MAN) radiocommunication subfamily which may be respectively restricted to rooms, buildings, campuses or specific metropolitan areas (e.g. cities) and may include e.g. WiMAX, Wipro, HiperMAN (high-performance Radio Metropolitan Area Network) or advanced air interface of IEEE 802.16m.

Cellular wide area radio communication technology may also be considered as Wireless Wide Area Network (Wireless WAN) radio communication technology.

In the following example it is assumed that the first transceiver 1014 supports LTE communication and thus operates in the LTE frequency bands 201 , 204 , 205 , 206 . Therefore, the first transceiver 1014 is also referred to as LTE RF.

It is further assumed for the following examples that the second transceiver 1018 operates in the ISM band 202 and supports WLAN communication or Bluetooth communication.

The first transceiver 1014 includes a first communication circuit 1022 that can perform various tasks related to communications performed by the first transceiver 1014, such as controlling transmission/reception timing, and the like. The first communication circuit 1022 may be regarded as a (first) processor of the communication terminal 1000 and is eg configured to control the first transceiver 1014 .

The second transceiver 1018 similarly includes a second communication circuit 1024 that may perform various tasks related to communications by the second transceiver 1018, such as controlling transmission/reception timing, and the like. The second transceiver 1018 is also referred to as connectivity (system) or CWS. The second communication circuit 1024 is also called a CWS chip or a connectivity chip. The second communication circuit 1024 may be regarded as a (second) processor of the communication terminal 1000 and is eg configured to control said second transceiver 1018 .

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

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

It should be noted that a "circuit" may be understood as any kind of logic implementing entity, which may be a dedicated circuit or a processor executing software stored in memory, firmware, or any combination thereof. Thus, a "circuit" may be a hardwired logic circuit or a programmable logic circuit, such as a programmable processor, eg a microprocessor (eg a Complex Instruction Set Computer (CISC) processor or a Reduced Instruction Set Computer (RISC) processor). A circuit may also be a processor executing software, such as any kind of computer program, such as a computer program using virtual machine code, such as Java for example. In accordance with aspects of the present disclosure, any other kind of implementation of the corresponding functions which will be described in more detail below may also be understood as a circuit.

RT coexistence mechanism

According to one aspect of the present disclosure, a real-time coexistence architecture is provided that relies on two approaches (or at least one of these approaches), namely protocol synchronization and traffic arbitration.

For example, protocol synchronization may include two mechanisms: utilizing available periods where the LTE RF 1014 is idle and organizing the RF activity of the connectivity system 1018 such that RX (i.e. receive) periods occur concurrently with LTE RX periods and TX (i.e. transmit) The period coincides with the LTE TX period. Protocol synchronization can be achieved via the use of LTE frame indication and LTE gap indication signals that allow the second transceiver 1018 (WLAN or BT) to schedule its activity at appropriate times: i.e. when the LTE RF 1014 is idle, Or when the corresponding activities are compatible (ie, cause both the first transceiver 1014 and the second transceiver 1018 to be receiving or cause both the first transceiver 1014 and the second transceiver 1018 to be transmitting).

Traffic arbitration may include receiving indications of first CWS 1018 activity and first LTE RF 1014 activity and selecting traffic to allow when a conflict is identified. CWS that can be used via RT (real-time) arbiter to derive CWS-kill and LTE-kill signals ("kill" a frame or subframe for a communication technology, i.e. prohibit transmission via a communication technology in a subframe or frame) Activity instructions to achieve business arbitration.

In the following, LTE frame indication for protocol synchronization according to an aspect of the present disclosure in the case of LTE-TDD (ie, in case the LTE RF 1014 is operating in TDD mode) is described.

As a time division duplex system, LTE-TDD has a unique frame structure that includes both DL and UL subframes. This is illustrated graphically in FIG. 11 .

FIG. 11 shows a frame structure 1100 .

Frame structure 1100 illustrates an LTE-TDD frame 1101 comprising: DL subframes, i.e. subframes allocated for downlink transmission (in which LTE RF 1024 receives data); UL subframes, i.e. subframes allocated for uplink transmissions (where the LTE RF 1028 transmits data); and special (S) subframes, which can be used, for example, as guard time and pilot transmissions.

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

The LTE TDD frame structure is typically static or changes little. It may be indicated to the CWS chip 1028 via NRT messaging via the NRT interface 1032 . The required synchronization between the CWS chip 1028 and the LTE-TDD frame timing can be performed via the RT interface 1026, 1030 using the LTE-frame_sync signal 1102 as illustrated in FIG.

The start of the LTE frame (i.e. the beginning of each frame 1001) is sent 1 ms earlier to the CWS via a pulse sent 1 ms earlier through the RT interface between the first communication circuit 1022 and the second communication circuit 1024 (i.e. via the RT interfaces 1026, 1030). Chip 1024 indicates.

Using the LTE frame sync signal coupled with the LTE frame structure signaled via NRT messages, the CWS chip 1024 has full knowledge of the LTE-TDD frame and thus it can schedule its communication activities.

This LTE-TDD frame structure signaling message via the NRT (coexistence) interface between said first communication circuit 1022 and second communication circuit 1024 (formed by NRT interfaces 1028, 1032) has for example as illustrated in Table 1 Format.

The message may be reduced to 3 bits (only 7 configurations) and encoding of the S subframe structure may be added:

Seven UL/DL TDD frame configurations as defined in 3GPP: 3 bits

• Nine special subframe configurations: 4 bits.

Considering that this message is an NRT message and using an implicit LTE configuration encoding would require some LTE knowledge about the connectivity chip 1024, it may be desirable to stick to an explicit 20-bit encoding.

For LTE frame indication in case of LTE-FDD (Frequency Division Duplex), LTE band 7 UL 204 is the most relevant frequency band. This is the uplink frequency band, so all subframes are UL subframes. However, LTE frame indication can also be used in this case to allow the CWS chip 1024 to properly schedule its activities on LTE UL subframe boundaries. It can also be used by the CWS chip 1024 to synchronize its system clock with the LTE system clock.

When (traffic) arbitration gives medium access to the CWS 1018, which may by definition apply until the end of the denied LTE subframe, knowing the subframe boundaries of the CWS 1018 enables scheduling to be applied in order to maximize until the denied ( LTE) The amount of traffic transferred until the end of the subframe.

In the following, LTE gap indication for protocol synchronization according to an aspect of the present disclosure in case of LTE-FDD discontinuous reception (DRX) and discontinuous transmission (DTX) is described.

LTE has been designed to address the need for mobile Internet access. Internet traffic can be characterized by high burstiness with high peak data rates and long periods of silence. To allow for battery saving, the LTE system allows DRX (Discontinuous Reception). Two DRX profiles addressed by Short DRX and Long DRX respectively are supported. For the reverse link, that is, the uplink, in order to increase the system capacity, the LTE system allows discontinuous transmission (DTX).

For example, for VoLTE (Voice over LTE), isochronous traffic may be assumed. Since the vocoder generates a packet every 20 ms, the basic periodicity of LTE traffic can be exploited for WLAN and BT transmissions during LTE silence periods.

As an example, for an inactivity period of 2 (the minimum allowed value of DRX inactivity time is 1 in 3GPP Release 9), the UL/DL schedule is shown in FIG. 12 .

FIG. 12 shows a data transfer diagram 1200 .

In data transfer diagram 1200, time increases from left to right. Data transmission diagram 1200 illustrates uplink LTE data transmission 1201, downlink LTE data transmission 1202 and on timeline 1203 at the bottom illustrates time (in terms of subframes) available for CWS 1024 due to DRX period 1207 .

A first hatch 1204 indicates a time period available for CWS 1024 (such as BT or WLAN), a second hatch 1205 indicates a time period that may be available for CWS 1024 and a third hatch 1206 indicates a time period that may be utilized by CWS 1024.

In the timeline 1203 at the bottom, these periods are marked (by first hatching 1204 and second hatching 1205) during which no LTE-UL activity is expected and therefore the CWS 1024 may be given. It should be noted that the LTE transceiver 1022 (especially in its role as a receiver) needs to be given interference-free time before the upcoming reception to allow the AGC (Automatic Gain Control) to stabilize and potentially reacquire the signal. For a short LTE DRX period, this period is about 300 μs; for a long DRX cycle, it is less than 1.3 ms.

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

In the following, an RT algorithm that can be used for protocol-synchronized LTE-FDD gap indication according to an aspect of the present disclosure is described.

The LTE transmission gap can be created by the communication terminal 1000 at any time according to the decision rules deployed by the network. The start and end of these transmissions are indicated to CWS 1024 in accordance with one aspect of this disclosure so that CWS 1024 can schedule its data traffic within transmission gaps (e.g., performed at CWS 1024 using an ACL (Asynchronous Connectionless Link) based profile) in the case of WLAN communication or Bluetooth communication).

In 3GPP Release 9, there are three possible root causes for creating transmission gaps: measurement gaps, DRX/DTX and autonomous measurement gaps.

Measurement (transmission) gaps are known 34 ms or 74 ms in advance at LTE L1 level and are 6 ms long. The DRX/DTX (transmission) gap in a subframe is known ahead of time by much less than 1 ms (eg approximately 200 μs) after decoding the PDCCH (Packet Data Control Channel) in the previous subframe. However, the transmission gap decision can be overruled in ad-hoc (point-to-point) mode up to 1.5 ms before the start of the transmission gap.

LTE gap signaling according to one aspect of the present disclosure is illustrated in FIG. 13 .

FIG. 13 shows a transmission diagram 1300 .

Transmission diagram 1300 illustrates uplink LTE data transmission 1301 , downlink LTE data transmission 1302 , uplink transmission gap signaling 1303 and 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 . An uplink transmission gap 1305 is signaled by an uplink transmission gap signal 1307 (UL gap envelope signal), and a downlink transmission gap 1306 is signaled by a downlink transmission gap signal 1308 (DL gap envelope signal), where The start and termination (end) of the transmission gaps 1305, 1306 are advanced, for example, by an uplink transmission gap signal 1307 and a downlink transmission gap signal 1308, for example via the RT interface between the first communication circuit 1022 and the second communication circuit 1024 1 ms is indicated to the CWS chip 1204 .

It should be noted that according to 3GPP Rel11 - Work item "In Device Coexistence" (3GPP Release 11 - Work Item "In Device Coexistence"), newly defined transmission gaps triggered especially for coexistence purposes can be introduced. Transmission gap signaling according to an aspect of the present disclosure is compliant with these new transmission gaps.

In practice, the timing advance of the DL gap envelope signal 1308 is kept short because the decision to claim a transmission gap can be taken during the last DL subframe before the DL transmission gap and can only be done when the PDCCH is decoded. For UL transmission gaps, the decision is also based on DL subframe decoding, but there is a delay of about 4 ms between DL and UL subframes. Additionally, a UL transmission gap decision can be vetoed before it is applied, up to 1.5 ms before transmission gap initiation. Veto requests (if any) later than this time are not applied. Therefore, UL transmission gap start may be signaled 1 ms (<1.5 ms) in advance. Similarly, transmission gap termination may be signaled a maximum of 1 ms earlier, since higher values cannot be applied for 1 ms UL transmission gaps (1 subframe). According to an aspect of this disclosure, 1 ms advance signaling is reserved for LTE transmission gap termination signaling, since maximizing the advance facilitates traffic scheduling at the CWS 1018 side.

As indicated in FIG. 13 , the advance values are eg tadv ₃ : 150 μs, tadv ₄ : 1 ms, tadv ₁ and tadv ₂ : 1 ms.

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

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

In the following, arbitration for the LTE-TDD case is described.

Due to LTE resource usage and due to WLAN/BT protocol requirements, having the protocol fully synchronized on each side and only applying concurrent RX and concurrent TX may not be sufficient to support the use case and some conflicting RX/TX events may occur.

Figures 14 and 15 illustrate possible conflicts between LTE-TDD operation and WLAN/BT operation.

FIG. 14 shows a transmission graph 1400 .

Transmission diagram 1400 illustrates the occurrence of transmission-reception collisions in the case of simultaneous LTE-TDD and WLAN traffic.

For each of the three timelines 1401, 1402, 1403, WLAN downlink transmissions are illustrated above the timelines 1401, 1402, 1403 and WLAN uplink transmissions are illustrated on the timelines 1401, 1402, 1403 Below, where time increases along the timelines 1401 , 1402 , 1403 from left to right and eg from top to bottom. Additionally, LTE transmissions (or LTE subframe allocations) 1404 , 1405 , 1406 are illustrated with respect to timelines 1401 , 1402 , 1403 .

Hatching 1407 indicates possible RX/TX collisions between WLAN transmissions and LTE transmissions.

FIG. 15 shows a transmission diagram 1500 .

Transmission diagram 1500 illustrates the occurrence of UL-DL collisions in the case of simultaneous LTE-TDD and Bluetooth traffic.

For each of the three timelines 1501, 1502, 1503, Bluetooth data transmissions are illustrated above the timelines 1501, 1502, 1503 and Bluetooth data receptions are illustrated below the timelines 1501, 1502, 1503, where For each of the timelines 1501, 1502, 1503, time increases from left to right. Additionally, LTE transmissions (or LTE subframe allocations) 1504 , 1505 , 1506 are illustrated with respect to timelines 1501 , 1502 , 1503 .

Hatching 1507 indicates possible UL/DL collisions between Bluetooth transmissions and LTE transmissions.

RX/TX collisions may be handled via arbitration, potentially resulting in LTE subframe loss. Arbitration may be performed between WLAN/BT and LTE to determine if WLAN/BT traffic is allowed.

Real-time arbitration is performed, for example, when a WLAN/BT transmission event (by the second transceiver 1018 ) collides with an LTE-DL subframe (ie, scheduled reception by the first transceiver 1014 ). The arbitration process decides or rejects the WLAN/BT transmission to protect the LTE-DL subframe or let it happen. In the latter case, depending on the RF interference level, the LTE-DL subframe may not be decoded by the LTE PHY, i.e. the LTE physical layer (implemented by components of the first transceiver 1014).

In the case of LTE-UL, the arbitration decision may consist in allowing the WLAN/BT to receive or allowing the LTE-UL subframe (ie LTE transmission). It can be seen that Figures 14 and 15 illustrate WLAN and Bluetooth usage over LTE-TDD for full connectivity traffic support (i.e. support of communication by the second transceiver 1018) relying solely on LTE rejection and LTE desensitization (desense) influence. This sets the worst case for the LTE-TDD side and can be used as a reference for quantifying the enhancement provided by the coexistence mechanism of LTE-TDD.

For example in the context given by the NRT arbiter decision, the RT arbitrator may be a hybrid implemented entity of the HW and SW located in the LTE subsystem (e.g., in the first transceiver 1014), via the first transceiver 1014 and the second The real-time (coexistence) interface between the two transceivers 1018 (formed by the RT interface 1026 , 1030 ) handles the synchronization of the first transceiver 1014 and the second transceiver 1018 . It derives the RT arbitration and applies it to the first transceiver 1014 and the second transceiver 1018 (via the RT coexistence interface).

For LTE-FDD, the interfering frequency band is the UL frequency band. LTE UL cannot be compromised by CWS, so the role of arbitration is reduced to protect or not protect WLAN/BT RX from LTE TX. Arbitration may be applied when collisions occur, ie as a result of incorrect scheduling of connectivity traffic or insufficient medium access. This results in vetoing the LTE UL subframe or letting it happen normally.

Figures 16 and 17 illustrate the WLAN and Bluetooth use cases over LTE-FDD for full connectivity traffic support depending only on the impact of LTE reject and LTE deny. This sets the worst case for the LTE-FDD side and can be used as a reference for quantifying the enhancement provided by the coexistence mechanism of LTE-FDD.

FIG. 16 shows a transmission diagram 1600 .

Transmission diagram 1600 illustrates the occurrence of transmission-reception collisions in the case of simultaneous LTE-TDD and WLAN traffic.

For each of the four timelines 1601, 1602, 1603, 1604, WLAN downlink transmissions are illustrated above timelines 1601, 1602, 1603, 1604 and WLAN uplink transmissions are illustrated on timeline 1601 , 1602, 1603, 1604, where time increases from left to right. Additionally, LTE transmissions (or LTE subframe allocations) 1605 , 1606 , 1607 , 1608 are illustrated with respect to timelines 1601 , 1602 , 1603 , 1604 .

Hatching 1609 indicates possible RX/TX collisions between WLAN transmissions and LTE transmissions.

FIG. 17 shows a transmission diagram 1700 .

Transmission diagram 1700 illustrates the occurrence of UL-DL collisions in the case of simultaneous LTE-FDD and Bluetooth traffic.

For each of the three timelines 1701, 1702, 1703, Bluetooth data transmissions are illustrated above the timelines 1701, 1702, 1703 and Bluetooth data receptions are illustrated below the timelines 1701, 1702, 1703, where For each of the timelines 1701, 1702, 1703, time increases from left to right. Additionally, LTE transmissions (or LTE subframe allocations) 1704 , 1705 , 1706 are illustrated with respect to timelines 1701 , 1702 , 1703 .

Hatching 1707 indicates possible UL/DL collisions between Bluetooth transmissions and LTE transmissions.

The real-time (coexistence) interface 1026 can be implemented by hardware only or by a mix of hardware and software located in the LTE subsystem (ie the first transceiver 1014). According to one aspect of this disclosure, it includes a set of eight proprietary real-time signals to support protocol synchronization and traffic arbitration. For example, these signals can be controlled via a software driver located in the LTE subsystem. It is connected to the CWS chip RT interface 1030 .

The RT interface may include traffic arbitration signals as shown in Table 2, for example.

The RT interface may include protocol synchronization signals as shown in Table 3, for example.

In the following, an example of hardware implementation of the RT interface between the first transceiver 1014 and the second transceiver 1018 is given.

This example describes the 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, 1024 in both directions. Non-real-time communication may be handled eg via a standardized interface between the first transceiver 1014 and the second transceiver 1018 .

The real-time interface can be seen as basically consisting of a set of discrete signals as shown in FIG. 18 .

FIG. 18 illustrates a communication circuit 1800 according to one aspect of the disclosure.

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

Communication circuit 1800 includes LTE subsystem 1801 (L1CC), which can control all hardware interactions. The communication circuit 1800 includes an RT interface 1803, via which the LTE subsystem 1801 can be connected to another communication circuit such as the second communication circuit 1024 using various IDC (In-Device Coexistence) signals, which are transmitted on the RT interface 1803 The left hand side is indicated and described in more detail in the text below.

According to one aspect of the present disclosure, there are specific requirements on the electrical characteristics of the RT interface 1803 . The IDC signal is configured, for example, during system startup. There is no need to reconfigure the IDC port (implementing the RT interface 1803) during operation.

From a hardware point of view, the communication protocol regarding interface signals can be kept simple. However, additional hardware support may be required in the context of layer 1 subsystems to support real-time processing of interface signals (ie IDC signals).

The LTE subsystem 1801 includes an RT coexistence (coexistence) timer unit 1804 responsible for generating time-accurate events on 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 of LTE timing is taken. Signal characteristics are described in more detail below.

IDC_LteFrameSync-LTE2CWS_SYNC configuration (output signal):

This signal can be used to generate frame periodic pulses for the CWS 1018. It should be noted that this burst signal may not be available during the LTE sleep phase.

IDC_LteDrxEnv, IDC_LteDtxEnv:

These output signals are envelope signals used to indicate discontinuous transmission/reception phases towards the CWS subsystem 1018 . Regardless of the root cause: DRX, DTX, measurement or any other, they are used to indicate a discontinuous transmission/reception phase. These two signals can be programmed individually via timers.

IDC_LteFrameSync-CWS2LTE_SYNC configuration (input signal):

This signal may be used, LTE2CWS_SYNC may be desired as a solution, while this one is kept as a backup. Via this signal, the CWS subsystem 1018 can request a snapshot of the LTE timing. Also, an interrupt can be generated in this case.

The LTE subsystem 1801 also includes an arbitration unit 1805 , an interrupt control unit (IRQ) 1806 and an LTE transmission (Tx) path 1807 . The arbitration unit 1805 is shown in more detail in FIG. 19 .

FIG. 19 shows an arbitration unit 1900 according to an aspect of the present disclosure.

The arbitration unit 1900 includes an IDC status register 1901 , an arbitration lookup table (LUT) 1902 and a register 1903 .

The arbitration unit 1900 may be used for status indication (eg, by means of the IDC status register 1901 ) and for interrupt generation. For example, the current level of a signal (such as an IDC-related signal mentioned below) can be monitored via the arbitration unit 1900 . Additionally, some signals may be provided to the interrupt control unit 1806 .

Arbitration unit 1900 provides hardware support for IDC real-time arbitration in its role as an arbitration unit. The task of the arbitration unit 1900 is to control the signals IDC_LteActive and IDC_LteKill, which depends on the input signals IDC_CwsActive, IDC_CwsTxRx and IDC_CwsPriority (because its width can be seen as consisting of two signals IDC_CwsPriority1 and IDC_CwdPriority2). For this purpose, the combination of the input signals is done according to a programmable look-up table, arbitration LUT 1902. The lookup table 1902 can be programmed on-the-fly via the LTE subsystem 1801 .

IDC_LteActive: This signal is available on the IDC RT interface 1803. The connectivity chip 1024 is the receiver of this signal. This signal can be configured in hardware to provide a fast response in case of changing input parameters. For example, the reset and isolation levels of this signal are zero.

IDC_LteKill: This signal can be used for "ad-hoc (point-to-point)" termination of LTE transmissions. Within the LTE subsystem 1014, this signal may be used to generate an interruption of the LTE subsystem 1804 and/or LTE Tx path 1807. In principle this signal could be used to directly manipulate the Tx IQ data flow. The LteKill signal is visible at the external IDC real-time interface 1803 for backup purposes. If desired, the LteKill signal can be connected from the RT interface 1803 to a GPIO (General Purpose Input/Output) for fast vetoing of the current LTE transmission.

Arbitration LUT 1902 may include dedicated lookup tables implemented for IDC_LteActive and IDC_LteKill.

The arbitration unit 1900 may include a filter 1904 for output signal filtering. In principle, transients on the output signals (eg IDC_LteActive and IDC_LteKill) are possible if eg the input signal changes and/or the look-up table 1902 is updated. Filtering at the output may be required in case transients cause problems on the receive side. In this case, changes at the output only apply if the input is stable for a minimum time (eg 1 μs). 1 μs filtering does not imply any loss of granularity in the signaling process, since events shorter than 1 μs need not be indicated. This filtering results in a 1 μs latency that can be hidden in requiring the CWS 1018 to indicate its activity on the RT interface 1030 1 μs earlier.

LTE veto is a mechanism for stopping (or terminating) current LTE transmission (ie UL communication) such that the LTE transceiver 1014 does not transmit, for example in order to free up the communication medium for WLAN/BT use. It may eg occur as a result of real-time arbitration in support of WLAN/BT.

According to an aspect of the present disclosure, sudden shutdown of LTE transmission is avoided as this would have several side effects like spurious emissions and possible impact on eNodeB AGC, power control.

To avoid these spurs, LTE rejection can be performed via a power down command (eg sent over the digRF interface) or via zeroing of IQ samples. The use of the power down command can be selected with the power down command, as it provides the ability to reduce the LTE transmit power down to -40 dBm (vs -50 dBm) while avoiding undesired side effects (such as PLL (Phase Locked Loop) off.. .) possibility.

Using commands sent over the digRF interface ensures that changes in transmit power are applied in a smooth manner, thus avoiding glitches.

According to an aspect of the present disclosure, LTE denial has a very short latency, for example about 10 μs for WLAN traffic and about 150 μs for BT traffic, in order to be optimally adapted to WLAN/BT traffic.

FIG. 20 shows a transmission diagram 2000 .

Along timeline 2001, WLAN traffic on the medium is shown, where data reception (i.e. downlink communication) is shown above timeline 2001 and data transmission (i.e. uplink communication) is shown at time Below line 2002. Furthermore, LTE transmissions for a first case 2002 and a second case 2003 are shown. Also, CWS Rx/Tx on RT interface 2004 is shown.

It should be noted that WLAN activities have timing uncertainty due to contention in CSMA (Carrier Sense Multiple Access):

- If the WLAN device wins access, the timing uncertainty is on the order of a few μs. It cannot be known precisely in advance, but it is constrained by the WLAN MAC (Media Access Control) protocol;

- If a WLAN device loses medium access, its activity differs by a few hundred µs and can be considered a new traffic event from a coexistence perspective. This cannot be known in advance and can be repeated several times.

In contrast, BT has no timing uncertainty.

It should be noted that it may be crucial to ensure that LTE vetoing does not apply to consecutive retransmissions of the same subframe to protect HARQ. For FDD, this means that LTE vetoes for subframes n and n+8 are disabled. For this, a mode for protecting HARQ channels can be used.

It should be further noted that full use by WLAN/BT of the remaining time in overridden LTE subframes may be desired.

Hereinafter, another example of components of communication terminal 1000 is given.

FIG. 21 shows a communication terminal 2100 .

Communication terminal 2100 corresponds to, for example, communication terminal 1000 in which only some components are shown and others are omitted for simplicity.

The communication terminal 2100 includes: an LTE subsystem 2101 , for example corresponding to the first transceiver 1014 and/or the LTE subsystem 1801 ; and a WLAN/Bluetooth communication circuit 2102 , for example corresponding to the second communication circuit 1024 . The LTE subsystem 2101 includes an LTE radio module 2103 and a communication circuit 2104 eg corresponding to said first communication circuit 1022 . The LTE subsystem 2101 may implement a L1 (layer 1) LTE communication stack 2114 and an LTE protocol stack 2115 (above layer 1).

Communication terminal 2100 also includes, for example, an application processor 2105 corresponding to processor (CPU) 1002 . Connectivity applications 2112 (including WLAN applications and/or Bluetooth applications) and LTE applications 2113 may run on the applications processor 2105 .

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

The LTE subsystem 2101 includes an RT arbitration entity 2111 (eg, corresponding to the arbitration unit 1805).

The communication circuit 2104 also includes a (LTE-connectivity) NRT mediation entity 2108 . It should be noted that the NRT mediation entity 2108 is not necessarily located in the communication circuit 2104 , but may also be located in other components of the communication terminal 1000 , 2108 . For example, it can be realized by CPU 1002.

The LTE subsystem 2101 includes, for example, a first RT interface 2106 corresponding to the first RT interface 1026, and the WLAN/Bluetooth communication circuit 2102 includes, for example, a second RT interface 2107 corresponding to said second RT interface 1030, which can be viewed as Together form the RT interface 2116 between the LTE subsystem 2101 and the WLAN/Bluetooth communication circuit 2102 .

Table 4 shows, for example, signals that may be exchanged on the RT interface 2116 .

It should be noted that the CWS priority signal can be seen as two signals CWS priority 1 and 2 because of its width.

It should also be noted that the first transceiver 1014 and the second transceiver 1018 may also be connected via the application processor 2105 (ie, for example, the CPU 1002) rather than directly (as a direct RT interface). Furthermore, it should be noted that, in general, communication can also be achieved via a serial or parallel bus instead of using dedicated signals (eg as shown in Table 4).

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

For FDD-only platforms (i.e. where the first transceiver 1014 and the second transceiver 1018 use only FDD), the first option for downgrading the RT interface (referred to as option 1a in Table 5 below) is to move Except the DL gap envelope signal and the CWS Tx/Rx signal, so that six signals remain. Since these removed signals are useless for FDD, there is no impact on coexistence performance. As a second option (referred to as option 1b in Table 5 below), in addition to removing the DL gap envelope signal and the CWS Tx/Rx signal, the CWS priority signal (CWS priority 1 and 2) can be removed such that the four signal. In this case, there is no priority indication anymore. Alternatively, light arbitration may be used, where the second transceiver 1018 may only indicate the activity of high priority traffic, but high priority traffic from BT and WLAN cannot be distinguished from each other.

For an FDD-TDD platform (i.e. where the first transceiver 1014 and the second transceiver 1018 use both TDD and FDD), the first option (referred to as option 2 in Table 5 below) is to get rid of arbitration and separate Relying on traffic synchronization, only three signals remain. In this case, the second transceiver 1018 becomes a pure slave and can only use the remaining communication resources available by LTE communication (i.e. the first transceiver 1014) via the DL gap The envelope signal and the UL gap envelope signal are signaled based on the synchronization of the LTE frame sync signal on the TDD frame structure. In this case, there is no way to protect LTE traffic from wrong or late CWS scheduling.

As a second option (referred to as option 3 in Table 5 below), traffic synchronization and light arbitration may be maintained such that six signals remain. In this case, there is no priority setting. The second transceiver 1018 may only signal above a certain priority, but cannot differentiate between BT and WLAN. The same arbitration rules are used for LTE-BT collisions and LTE-WLAN collisions.

Table 5 summarizes the options for downgrading the RT interface.

As a summary, the following may, for example, be provided for RT coexistence mechanisms according to various aspects of this disclosure:

- LTE frame indication (signal + frame structure message)

- UL gap indication

- DL gap indication

- Arbitration including short collision possibility

- HARQ protection (for arbitration and LTE rejection)

- Downgraded RT mode

- Full use of subframes rejected by LTE

- For example the implementation of the RT interface as above.

General Coexistence Architecture

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

(LTE-Connectivity) NRT arbitration entity 2108 may eg be implemented by software located in said communication circuit 2104 . For example, it uses a mix of application requirements (from connectivity and LTE applications) with contextual information from both cores (eg from both the first transceiver 1014 and the second transceiver 1018), such as frequency band, bandwidth, EARFCN ( E-UTRA Absolute Radio Frequency Channel Number) to arbitrate and indicate static information such as a selected frequency band or a selected power level to the first transceiver 1014 and the second transceiver 1018. It also provides an indication to the RT Arbiter 2111 located in the LTE Subsystem 2101 . It should be noted that according to one aspect of this disclosure, the NRT arbitration entity 2108 does not arbitrate between WLAN and BT. This arbitration can eg be performed in the WLAN/BT communication circuit.

The NRT application (application) coexistence interface 2106 may also be an entity realized by means of software running on the communication circuit 2104 . It transfers NRT messages carrying application information from the connectivity application 2112 and the LTE application 2113 running on the application processor 2105 . Table 6 gives a list of messages that can be exchanged between the application processor 2105 and the communication circuit 2104 by means of the NRT application coexistence interface 2106 (and the corresponding application interface 2109).

The NRT coexistence interface 2107 may also be a SW-implemented entity located in the communication circuit 2104 . It transfers NRT messages carrying context information from the WLAN/BT communication circuit and sends notifications from the NRT arbiter 2108 to the WLAN/BT communication circuit (by means of the corresponding NRT coexistence interface 2110 of the WLAN/BT communication circuit). Table 7 presents a list of messages that may be exchanged eg via the interface formed by the NRT coexistence interface 2107 of the communication circuit 2104 and the NRT coexistence interface 2110 interface of the WLAN/BT communication circuit 2102 .

It should be noted that the LTE bitmap can be changed (limited to seven frame structures but there are many more configurations for the S content itself). It should be further pointed out that the above mentioned NRT messages may also be partially or fully sent to the eNodeB 103 if the eNodeB 103 takes some decisions about coexistence.

Furthermore, it should be noted that the split between the information located in the communication circuit 2104 and the information located in the WLAN/BT communication circuit 2102 may vary depending on the platform architecture and application stack.

According to one aspect of the present disclosure, the NRT coexistence algorithm and the RT coexistence algorithm are coordinated. This is illustrated in Figure 22.

FIG. 22 shows a flowchart 2200 .

When the coexistence state changes in the communication terminal 1000 in 2201, the NRT coexistence mechanism is activated in 2202. Messages are then sent over the NRT coexistence interface to apply the NRT arbitration decision.

Continuing, at 2203, the pre-computed RF interference table is used to estimate the level of desensitization of the connectivity RAT achieved by the newly applied NRT arbitration. If it is above the desensitization target, the RT coexistence mechanisms are enabled 2204 and they continue to run in an autonomous manner. If the desensitization level is below the desensitization target, then in 2205 the RT coexistence mechanism is disabled.

When receiving an update (via SW message) either from the LTE subsystem 2101 or from the WLAN/BT communication circuit 2102, the NRT arbiter 2108 can detect a change in the coexistence state in the sense that, for example, if the frequency used for LTE and CWS communication Not being in the critical band so far, it may now have become the case and the coexistence algorithm needs to be activated.

The NRT arbiter 2108 is the entity responsible for activating or deactivating any particular coexistence algorithm and is always ready to receive input messages from LTE or CWS indicating changes of any relevant parameters.

Situations of a coexistence state change may for example include (among others):

- the second RAT becomes active;

- Perform handover to another LTE frequency band during LTE communication;

- Modify LTE bandwidth;

- The number of active RATs is reduced to 1.

As noted above, according to various aspects of this disclosure, there may be a split between RT and NRT (eg, in terms of interface). RT and NRT processing can be synchronized. NRT messaging can be extended by messaging between the communication terminal 105 and the eNodeB 103.

NRT coexistence mechanism

The NRT coexistence mechanism may include Bluetooth's FDM/PC (Frequency Division Multiplexing/Power Control) algorithm described below.

Bluetooth medium access is based on time slot (slot) business scheduling. Slots are scheduled at fixed times and frequencies. The time slots are 625µs long and are mapped onto 1MHz wide BT channels. The frequency channels used in a given time slot are imposed by a frequency hopping pattern, which varies pseudo-randomly from time slot to time slot.

A BT entity (for example in the form of a communication terminal 1000 using Bluetooth) may be either a (Bluetooth) master or a (Bluetooth) slave. The Bluetooth master provides the reference time and controls the synchronization and activity of the piconet (this is the control) which is a small network of Bluetooth devices around it. The slave entity must periodically monitor the medium to capture any control information from the piconet master. A Bluetooth slave listens during a slot or part of a slot for all potential master transmissions (1,25 ms period) and replies in the next slot whether it has received a packet addressed to it in the current slot. BT slaves can use "power-saving (Sniff) mode" to reduce power consumption and avoid: master-slave transactions only on reserved time slots (negotiated before entering power-saving mode).

According to Bluetooth, useful data and/or control data are carried on two periodic and/or asynchronous packets. The kind of packet used for a given data service depends on the corresponding service profile (which is standardized). Control services are carried by asynchronous services.

BT slaves can use "power saving mode" to reduce power consumption and avoid: master-slave transactions only on reserved time slots (negotiated before entering power saving mode).

Target Bluetooth profiles might be A2DP for audio (eg music) streaming and HFP as a voice headset profile. A2DP is an asynchronous traffic profile using variable length packets (single-multi-slot), HFP is a periodic single-slot traffic transferred in scheduled (reserved) slots. Devices can also be paired via Bluetooth while out of service.

Slots can be reserved (by the link manager) during link establishment. The most common packet is the HV3 packet (used for Synchronous Connection-Oriented (SCO) communications), which occupies one-third of a double slot.

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

FIG. 23 shows a transmission diagram 2300 .

In transmission diagram 2300, time increases from left to right and is divided into time slots 2301 of 625 μs. The first transfer 2302 is performed by the master device and the second transfer 2303 is performed by the slave device.

Bluetooth communication is suitable for frequency hopping. In communication, the operating frequency channel varies pseudo-randomly from time slot to time slot and performs a pseudo-random walk through the 79 available 1 Mhz channels in the ISM band 202 .

Adaptive Frequency Hopping (AFH) is a mechanism that allows limiting this to a subset of 79 channels. However, the number N of channels used must not be lower than 20. The choice of channel mapping is completely flexible, but results from a negotiation between the master and slave performed on a static basis. AFH can be disabled for sleeping slaves.

An adaptive frequency hopping mechanism can be used to exclude BT traffic from the LTE band. This is particularly efficient for protecting LTE Rx from BT Tx (LTE-TDD case), less efficient in the opposite direction since the BT front end (filter/Low Noise Amplifier (LNA)) is wideband.

According to one aspect of the present disclosure, an adaptive frequency hopping mechanism is utilized by:

- the first communication circuit 1022 performs a static request to the second communication circuit 1024 (acting as a (local) BT core) to modify its channel mapping;

- the second communication circuit 1024 updates the channel map and aligns it with the peer entity (e.g. another communication terminal);

Bluetooth spectrum occupancy can be reduced down to one-third of the ISM band 202 . This provides a guardband of up to 60 Mhz for LTE band 40 201 and a guardband of up to 79 Mhz for LTE-7 UL band 204. It should be noted that the efficiency of AFH for BT/LTE coexistence may be limited due to the fact that the BT RX front-end receives the full frequency band even in the context of AFH (non-linear anyway).

It can be seen that the use of this mechanism has limited impact on BT/WLAN coexistence.

In the following, a procedure for protecting Bluetooth from LTE-FDD transmissions in LTE Band 7 UL 204 is described with reference to FIG. 24 .

FIG. 24 shows a message flow diagram 2400 .

The NRT algorithm corresponding to the message flow diagram 2400 may be performed by the NRT arbitration unit 2108, for example.

The message flow occurs between the LTE subsystem 2401 corresponding to the LTE subsystem 2101 (for example, corresponding software), the NRT arbiter 2402 corresponding to the NRT arbiter 2108, and the BT communication circuit 2403 corresponding to the WLAN/BT communication circuit 2102 between.

At 2404, the NRT arbiter 2402 loads the BT desensitization target.

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

In 2407, the LTE subsystem 2401 generates information about LTE configuration, such as LTE information including used frequency band, used bandwidth, EARFCN, path loss margin (estimated transmission power drop without triggering modulation/bandwidth change), etc. surface.

In 2408, the LTE subsystem 2401 sends the generated information to the NRT arbiter 2402 in an LTE information confirm message 2409.

At 2410 , the NRT arbiter 2042 stores the information received in the LTE Information Ack message 2409 .

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

In 2413, the BT communication circuit 2403 constructs an AFH map including permutations of channels excluded for coexistence.

In 2414 , the BT communication circuit 2403 sends the generated AFH map to the NRT arbiter 2402 in an AFH map confirm message 2415 .

At 2416, the NRT arbiter 2402 generates a new AFH map. The target here is the level of BT sensitivity reduction. This generation can include, for example, the following:

1) Calculate the ΔF of the BT channel (full frequency band, granularity to be defined)

2) Using the isolation table (precomputed for LTE at full power, static), evaluate BT desensitization vs. operating BT channel (full band)

3) Select the highest number N of BT channels that meet the BT sensitivity reduction goal

4) If the goal cannot be achieved or N < Nmin, then use Nmin

5) If the target cannot be achieved, keep the exclusions applied to WLAN/BT coexistence -> ignore

6) Construct a new AFH map.

In 2417, the NRT arbiter 2402 sends the new AFH map to the BT communication circuit 2403 with an AFH setup request message 2418 requesting the BT communication circuit 2403 to use the new AFH map.

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

In 2420 , the BT communication circuit 2403 confirms the use of the new AFH mapping by means of an AFH Setup Confirm message 2421 .

In 2422, the NRT arbiter 2402 selects the highest LTE TX (transmit) power that meets the BT sensitivity reduction target and the LTE Tx path loss margin.

It should be noted that this practice can be dangerous for interoperability testing (IOT). According to an aspect of this disclosure, it is ensured that it is only applied to coexistence cases defined by the AP.

In 2423, the NRT arbiter 2402 sends the determined LTE Tx power to the LTE subsystem 2401 with a power request message 2424 requesting the LTE subsystem 2401 to use the determined Tx power.

In 2425, the LTE subsystem 2401 thus applies Tx power.

In 2426 the LTE subsystem 2401 confirms the use of Tx power by means of a power confirm message 2427 .

Assume, in 2428, that the NRT arbiter 2402 realizes that there is no more coexistence to care about from now on.

In 2429 the NRT arbiter 2402 sends a Power Down Request message 2430 to the LTE Subsystem 2401 , which is acknowledged in 2431 by means of a Power Off Ack message 2432 from the LTE Subsystem 2401 .

According to one aspect of the present disclosure, the NRT coexistence mechanism includes the FDM/PC algorithm for WLAN described below.

WLAN medium access is based on Carrier Sense Medium Access (CSMA), where stations listen to the medium and compete to gain access to it when it is idle. There is no resource scheduling and no business periodicity. Global synchronization is achieved via beacons transmitted by access points every approximately 102 ms, but effective beacon transmissions may be delayed due to medium occupation.

The WLAN MAC adapts to the radio channel conditions via link rate adaptation based on the packet error rate calculated at the transmitter side based on received ACKs (positive ACKs for retransmissions).

In the 2.4GHz band (ISM band), WLAN systems operate on 14 overlapping channels called CH#1 to CH#14 (CH#14 is only used in Japan). This is illustrated in Figure 25.

FIG. 25 shows a frequency allocation diagram 2500 .

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

WLANs typically operate in BSS (Basic Service Set) mode. Peer-to-peer mode also exists, but is still rarely used. However, it may become useful in smartphone usage situations.

In BSS mode, the access point (AP) has full control over the WLAN channel selection and mobile station (STA) of operation. Select the WLAN channel in the static access point.

According to one aspect of the present disclosure, WLAN power control is used to reduce interference to LTE communications.

WLAN has a peak power of about 20 dBm, and for power consumption reasons, is usually transmitted at full power to achieve the highest possible PHY rate and keep the packet duration as short as possible. However, the WLAN protocol stack does not prevent the use of lower Tx power, nor does it define rules for selecting the power used.

The second transceiver 1018 embedded in the communication terminal 1000 (in this example operating as a WLAN transceiver) can autonomously reduce its Tx power if required:

- If the communication terminal 1000 acts as a station connected to a home access point or hotspot by means of the second transceiver 1018, this could trigger a link rate adaptation event to downgrade the PHY rate, which would result in a higher packet duration and Thus resulting in longer interference from WLAN to LTE. According to one aspect of the present disclosure, the use of power control is limited in this case.

- If the communication terminal 1000 acts as an AP by means of the second transceiver 1018 (i.e. tethering case), the communication terminal 1000 (e.g. smartphone) acting as an access point (router) and the connected WLAN (e.g. Wifi) The distance between clients (eg laptops) is under the user's control and can be brought closer together. The communication terminal 1000 can then significantly reduce its WLAN Tx power to balance the lower BSS coverage and associated path loss.

In Table 8 a comparison of estimated path losses for network sharing to hotspots is given.

A rough estimate as given in Table 8 gives a 19 dB margin between hotspot and tethering, showing that the WLAN Tx power can be reduced by up to 19 dB, which corresponds to 1 dBm.

According to one aspect of this disclosure, the AP Tx power is gradually reduced and the PER evolution at the AP is monitored (PER statistics are always established in WLAN).

In summary, WLAN power control can cause a 15-20 dB reduction in WLAN-to-LTE interference in the case of network sharing. LTE to WLAN interference suppression requirements can be relaxed (WLAN sensitivity reduction requirements). This approach may not be suitable in case of coupling with TDM (Time Division Multiplexing) solutions, as Tx power reduction may result in lower PHY rate and thus increased Tx duration. There may be a tradeoff between power control and high PHY rate usage.

According to one aspect of the present disclosure, WLAN channel selection is used to reduce WLAN/LTE interference.

In the use case where the communication terminal 1000 (as a WLAN entity) acts as an AP (eg for tethering), it can freely select a WLAN channel for its operation. Therefore, WLAN traffic can be excluded from the LTE operating frequency band, thus protecting WLAN from LTE and protecting LTE from WLAN. According to an aspect of the present disclosure, the WLAN channel quality perceived by the WLAN AP, eg reflecting channel occupation by nearby hotspots or home APs, is taken into account in this process.

WLAN channel selection can cause 18 to 42 dB suppression of WLAN to LTE (LTE band 40) interference when channels CH#3 to #14 are selected. This mechanism is compatible with power control solutions that can be used on top.

WLAN channel selection can cause 27 to 77 dB suppression of LTE (LTE band 40) to WLAN interference when channels CH#3 to #10 are selected.

In summary, AP channel selection can

- 18 to 42 dB reduction in WLAN to LTE band 40 OOB (out-of-band) rejection

- Reduced LTE band 40 to WLAN OOB suppression by 27 to 77 dB

- Reduced LTE channel 7 UL -> WLAN OOB suppression by 19 to 49 dB.

This mechanism does not compromise the throughput or robustness of the WLAN.

It should be noted that the above analysis only considers OOB noise effects, thus assuming that nonlinear effects, such as signal compression by reciprocal mixing, are avoided through RF system design.

In the following, a procedure for protecting a WLAN from LTE-FDD transmissions in LTE Band 7 UL 204 is described with reference to FIG. 26 .

FIG. 26 shows an information flow diagram 2600 .

The NRT algorithm corresponding to the message flow diagram 2600 may be performed by the NRT arbitration unit 2108, for example.

The message flow occurs between the LTE subsystem 2601 corresponding to the LTE subsystem 2101 (for example, corresponding software), the NRT arbiter 2602 corresponding to the NRT arbiter 2108, and the WLAN communication circuit 2603 corresponding to the WLAN/BT communication circuit 2102 between.

At 2604, the NRT arbiter 2602 loads the WLAN desensitization target.

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

In 2607, the LTE subsystem 2601 generates information about LTE configuration, such as LTE information including used frequency band, used bandwidth, EARFCN, path loss margin (estimated transmit power drop without triggering modulation/bandwidth change), etc. surface.

In 2608, the LTE subsystem 2601 sends the generated information to the NRT arbiter 2602 with an LTE information confirm message 2609.

At 2610 , the NRT arbiter 2602 stores the information received in the LTE Info Ack message 2608 .

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

In 2613, the WLAN communication circuit 2603 builds a permuted channel map. The ranking can be based on SINR (Signal to Noise Ratio) and WLAN/BT constraints.

In 2614 , the WLAN communication circuit 2603 sends the generated channel map to the NRT arbiter 2602 in a channel map confirmation message 2615 .

At 2615, the NRT arbiter 2602 determines the WLAN channel to use. The target here is the WLAN sensitivity reduction level. This determination may, for example, include the following:

1) Calculate ΔF for each WLAN channel

2) Estimate WLAN desensitization per WLAN channel using isolation table (precomputed for LTE at full power, static)

3) Select the highest ranked WLAN channel that satisfies the WLAN sensitivity reduction objective.

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

In 2619, the WLAN communication circuit 2603 thus moves to the determined WLAN channel.

In 2620, the WLAN communication circuit 2603 confirms the use of the determined WLAN channel by means of the set channel confirmation message 2621.

At 2622, the NRT arbiter 2602 stores an indication of the WLAN channel.

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

In 2625, the WLAN communication circuit 2603 generates information about the WLAN configuration, such as a WLAN information table including the number of channels, MCS (modulation and coding scheme), Tx power, and the like.

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

In 2628, the NRT arbiter 2602 selects the highest LTE TX (transmit) power that meets the WLAN sensitivity reduction target and the LTE Tx path loss margin.

This may include the following:

1) Calculate the ΔF of the WLAN channel of operation

2) Using isolation table (precomputed for LTE at full power, static), evaluate WLAN desensitization for WLAN channel of operation

3) Select the highest LTE TX power that meets the WLAN desensitization target and LTE TX path loss margin.

It should be noted that this practice can be dangerous for interoperability testing (IOT). According to an aspect of this disclosure, it is ensured that it is only applied to coexistence cases defined by the AP.

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

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

In 2632 the LTE subsystem 2601 confirms the use of Tx power by means of a power confirm message 2633 .

Assume, in 2634, that the NRT arbiter 2602 realizes that there is no more coexistence to care about from now on.

In 2635 the NRT arbiter 2602 sends a Power Down Request message 2636 to the LTE Subsystem 2601 , which is acknowledged in 2637 by means of a Power Off Ack message 2638 from the LTE Subsystem 2601 .

It has been shown above in Table 7 that in the context of NRT coexistence may for example be formed by the NRT coexistence interface 2107 of the communication circuit 2104 and the NRT coexistence interface 2110 of the WLAN/BT communication circuit 2102 (operating for example as a WLAN/BT baseband circuit) messages exchanged on the NRT interface. Additional examples are given in the text below.

According to an aspect of the present disclosure, measurement gap configuration in LTE connected mode is used for LTE-WLAN coexistence.

Although in LTE connected mode, measurement gaps are defined in the 3GPP specification so that single radio mobile terminals (i.e. mobile terminals with only one LTE transceiver, cannot transparently measure other frequencies (except by the serving cell used frequencies)) to be able to perform the following measurements:

1. Operating an LTE neighbor cell on a different frequency than the serving cell (inter-frequency measurements)

2. Neighboring cells of other RATs (e.g. 2G or 3G) (inter-RAT measurements).

Typically, these measurement gaps have a duration of 6 ms and are scheduled with a periodicity of 40 ms or 80 ms when LTE is the serving RAT.

If LTE communication is performed using frequencies that interfere with WLAN communication and vice versa, measurement gaps can be used for safe WLAN reception and transmission:

· If the gap is used for LTE inter-frequency measurements, and if the LTE frequency does not overlap with the WLAN frequency

• If a gap is used for 2G or 3G measurements, then this gap can be used for WLAN/BT in parallel with LTE measurements without limitation since there is no possible interference between 2G/3G and ISM bands.

Furthermore, for better Closed Subscriber Group (CSG) cell support in LTE connected mode, 3GPP Release 9 introduces the concept of so-called autonomous measurement gaps. The reason here is that for CSG cells the SIB (System Information Block) needs to be read which may require additional measurement gaps asynchronous to those scheduled at regular intervals. If the network supports autonomous measurement gaps, the mobile terminal is allowed to ignore some TTIs, as long as the mobile terminal is able to send at least 60 ACK/NAKs every 150 ms interval. HARQ and higher layer signaling ensures that data is not lost.

In order to notify the second transceiver 1018 in advance of any upcoming regular gap occurrence during which no interference with WLAN reception or transmission will occur, the first transceiver 1014 (e.g., LTE baseband circuitry) may send a signal to the second transceiver 1014 1018 (eg CWS baseband circuit) sends a message indicating the gap pattern along with the following information:

· Measure gap pattern periodicity (e.g. 40/80 ms),

· Measuring gap duration (eg 6ms)

• An unambiguous method for identifying the first measurement gap occurrence of the considered measurement gap pattern.

This can be used for:

Inter-frequency measurement gaps,

inter-RAT measurement gap,

·Automatic gap measurement.

For example, the message may be a Periodic_Gap_Pattern_Config (Periodic, Duration, No. Occurrence date) message, and the second transceiver 1018 is free to perform transmission and reception during each of these gaps.

The first transceiver 1014 (for example, LTE baseband circuit) used to implement gap message indication from the first processor-controlled first transceiver 1014 (for example, implementing the LTE protocol stack or LTE physical layer) to the second transceiver 1018 Criteria and decisions for transmission (eg CWS baseband circuitry) may belong to a non-real-time (eg software) arbiter 2108 entity that may run on the first transceiver 1014 (eg LTE baseband circuitry) based on:

Whether frequency interference occurs;

• Is there enough or not enough interference free period of time during which the second transceiver 1018 (eg CWS baseband circuit) can operate.

The gap message indication may be dynamically enabled or disabled by the non-real-time (e.g. software) arbiter 2108 whenever the non-real-time (e.g. software) arbiter 2108 considers that the criteria for enabling or disabling the use of gaps is met to ensure proper second transceiver 1018 functionality .

In summary, WLAN communication can be protected from LTE band 7 UL 204, Bluetooth communication can be protected from LTE band 7 UL 204, and WLAN communication can also be protected from LTE band 40 201 and Bluetooth communication can be protected from LTE band 40 201 impact.

PHY mitigation

Pilot symbols in interfering OFDM symbols are typically meaningless. As the worst case, a situation where two consecutive OFDM symbols are lost per LTE slot can be seen. This means that each antenna lacks one pilot per slot (eg between two for antennas 0 and 1 and one for antennas 2 and 3). It should be noted that antennas 0 and 1 are only relevant for smartphones. It reserves (for 1/2 antenna) a worst case: one pilot missing for a given carrier.

This may have the following effects:

1) Outer receivers can be affected on AGC, noise estimation, channel estimation. the

- These tasks are processed with a delay sufficient to take advantage of the real-time indication of WLAN interference bursts,

- Some filters are already present in the equalizer to compensate for the absence of RS (reference signal),

- An indication of a burst of WLAN interference can be used by an outer receiver to declare the corresponding RS (if any) as absent, and then existing filters can be applied,

- This real-time indication can be included in the RT coexistence interface

In summary, outer receiver protection from WLAN short interference can be done by framework modification (as a prerequisite, the implementation of RT coexistence and RT arbitration can be done).

2) Inner Receiver:

- Transmission block/codeword/codeblock vulnerability can be difficult to assess; impact depends at least on codeblock length and channel conditions:

oIn the best case, the code block is recovered by the Turbo code, so that there is no impact on the LTE throughput

o In the worst case, code blocks are similarly affected (periodically) in consecutive HARQ retransmissions. This would mean that the corresponding transport block never undergoes transmission.

Typically, it is desirable to avoid the worst case. Furthermore, it may be desirable to prevent two consecutive bursts of interference in the same LTE subframe. For example, this can be done by suppressing two consecutive interfering WLAN bursts separated by a HARQ period (eg 8 ms).

According to one aspect of the present disclosure, spur nulling can be used to solve the above problem, which can be viewed as a frequency domain solution. Assume, for example, that the glitch does not saturate the FFT (and thus spreads over the full bandwidth in the frequency domain): WLAN/BT requirements for transmission spurious emissions can thus be dimensioned. For example, frequency domain glitch detection and frequency domain glitch nulling or signal glitch nulling may be applied.

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

protocol mitigation

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

- Some techniques can be used at the protocol level to reject some LTE subframes so that they can be used by WLAN/BT when there are no free gaps or when their number/duration is insufficient compared to WLAN/BT needs. This is known as LTE rejection. This technique may not depend on current 3GPP specifications and can be done autonomously at the mobile terminal level. However, they may be partially included in the 3GPP Release 11 standard (IDC work item).

- Furthermore, when a mobile terminal is within handover range, it can try to influence the eUTRAN to preferentially handover towards cells with coexistence-friendly carrier frequencies. It may also try to delay handover towards less coexistence-friendly cells. This is also known as a coexistence-friendly handover.

LTE rejection can be implemented using UL grant ignore or SR (scheduling request) deferral. Coexistence-friendly handover can be achieved via intelligent reporting of neighbor cell measurements (values and/or timelines).

WLAN and Bluetooth usage over LTE-FDD for full connectivity traffic support is illustrated above in Figures 16 and 17 depending only on the impact of LTE rejection. This can be seen as the worst case on the LTE-FDD side and can be used as a reference for quantifying the enhancement provided by the coexistence mechanism of LTE-FDD. Make the following assumptions:

- Systematic LTE denial

- WLAN operates with medium channel quality (29Mbps PHY rate worst case)

- WLAN STA (i.e. not valid for tethering).

Tables 9 and 10 further illustrate the worst case impact of Bluetooth usage over LTE-FDD and worst case impact of WLAN usage over LTE-FDD (assuming full support, no LTE gaps), respectively. The use case is the same as illustrated in FIGS. 16 and 17 .

According to an aspect of the present disclosure, the LTE rejection consists in:

- Autonomous rejection of the use of UL subframes in which LTE has allocated communication resources at the mobile terminal level. This can be applied to LTE-FDD (e.g. LTE Band 7 UL 204) and LTE-TDD (e.g. LTE Band 40 201),

- Autonomous rejection at the mobile terminal level of the use of DL subframes in which LTE has allocated communication resources. This may apply to LTE-TDD (eg LTE band 40 201).

It should be noted that for UL rejection, cancellation/postponement of scheduled LTE activity may be done; while for DL rejection, it may be sufficient to allow simultaneous TX activity on the CWS side.

In the context of the postponement of SR, it should be noted that LTE has been designed to address the need for mobile Internet access. Internet traffic can be characterized by high burstiness with high peak data rates and long periods of silence. To allow battery saving, the LTE communication system (as shown in Figure 1) allows DRX. Two DRX profiles are introduced which are addressed respectively by Short DRX and Long DRX. For the reverse link, that is, the uplink, in order to increase the system capacity, the LTE communication system allows discontinuous transmission (DTX). For uplink traffic, the mobile terminal 105 reports its uplink buffer status to the eNB 103, which then schedules and assigns uplink resource blocks (RBs) to the mobile terminal 105. In the case of an empty buffer, the eNB 103 may not schedule any uplink capacity, in which case the UE 105 cannot report its uplink buffer status. In case the uplink buffer changes in one of its uplink queues, the UE 105 sends a so-called scheduling request (SR) to be able to report its buffering in the subsequent scheduled uplink shared channel (PUSCH) device status.

To prevent this from happening, the mobile terminal 105 MAC layer may delay the SR if the DTX period has previously been granted to WLAN activity. According to one aspect of this disclosure, this mechanism can be used for LTE/WLAN coexistence. It is illustrated in Figure 27.

FIG. 27 shows a transmission diagram 2700 .

LTE uplink transmissions are illustrated along a first timeline 2701 , while LTE downlink transmissions are illustrated along a second timeline 2702 . The transmission takes place, for example, between the mobile terminal 105 and the base station 103 serving the mobile terminal 105 . Time increases from left to right along the timelines 2701,2702.

In this example, the mobile terminal 105 receives the UL grant in the first TTI 2703. The mobile terminal 105 responds to this UL grant by sending an UL signal in the second TTI 2704. At the same time, the mobile terminal 105 sets its DRX inactivity timer. Assuming no further UL grants or DL transport blocks (TBs) have been scheduled (this will cause the DRX inactivity timer to be reset to the DRX inactivity time), after the mobile terminal 105 receives a pending ACK for the last UL transport block it sent (As illustrated by arrow 2705 ) Afterwards, the DRX and DTX conditions are met. During the DRX and DTX period 2706, the mobile terminal 105 does not need to listen to any downlink control channel in the PDCCH and the eNB 103 does not schedule the mobile terminal 105 until the end of the DRX and DTX period 2706. DRX and DTX periods 2706 may be used for WLAN transmissions.

The mobile terminal 105 may send an SR if it requests to send some uplink data which will end the DRX and DTX period 2706 . To prevent this from happening, the mobile terminal MAC may suppress SR if that period is used to interfere with WLAN activity.

In the example of FIG. 27, the mobile terminal 105 receives a UL grant in the first TTI 2703. The mobile terminal 105 complies with the UL grant by sending the UL signal in the second TTI 2704 (4 TTIs later). However, the mobile terminal 105 may ignore the UL grant and thus reject UL subframes coming four TTIs later, which are thus freed for WLAN/BT operation. This released subframe is indicated to the CWS chip 1024 using the RT coexistence interface 1026 (UL gap indication).

According to one aspect of this disclosure, LTE rejection with HARQ protection is used. This is described below.

In LTE-WLAN/BT coexistence, the use of LTE reject may be required to release LTE subframes for connectivity traffic (vetoing LTE subframe allocation). When applied in the UL, LTE denial can be viewed as corresponding to preventing the LTE transceiver 1014 from transmitting in subframes in which it has some allocated communication resources. In this case, the characteristics of the LTE HARQ mechanism can be considered: HARQ is a MAC layer retransmission mechanism, which is synchronous and has a period of 8 ms period (UL case, in DL it is asynchronous).

In LTE-FDD UL, HARQ is synchronous and supports up to eight processes. A potential retransmission of a packet originally transmitted in subframe N thus occurs in subframe N + 8 * K, where K >= 1. Therefore, the impact of LTE rejection on the transport channel can vary greatly depending on the interaction with LTE HARQ. For example, a periodic LTE rejection with an 8ms period may affect every repetition attempt of a single HARQ process and may result in link loss. An example of a rejection period of 12 ms is illustrated in FIG. 28 .

FIG. 28 shows a transmission diagram 2800 .

Along a first timeline 2801 , UL subframe rejection and allocation of TTIs to HARQ processes (numbered 0 to 7) are indicated. In this example, there is a regular LTE rejection such that Process 0 and Process 4 are rejected periodically (every second time).

A periodic LTE rejection of period 9 ms affects the same HARQ process only once every eight LTE rejections.

Periodic rejections without considering the HARQ behavior can have a highly negative impact even for low amounts of rejections: this can lead to weaker links (best case) or HARQ failures (worst case). Weaker links may result in eNodeB link adaptation, reduced resource allocation, while HARQ failures may result in either data loss (RLC in unacknowledged mode) or RLC retransmissions with corresponding delays.

It is desirable to avoid applying LTE reject periods which have such a negative impact on HARQ. However, LTE rejection requirements may come from applications/codecs on the connectivity (CWS) side, and many codecs have periodic requirements. In the following, mechanisms for intelligent LTE rejection, enabling periodic LTE rejection to support application/decoder requirements while minimizing its impact on the HARQ process, or avoiding periodic LTE rejection when applied.

For example, the following provisions can be taken in applying LTE rejection to minimize the impact on HARQ

- Burst rejection: When the application/codec has no strict requirements for periodic medium access (e.g. in the case of HTTP traffic over WLAN), rejected subframes are grouped together (in order of time consecutive subframes). frame) to minimize the number of consecutive rejections (i.e. TTI rejections assigned to the same HARQ process) for a given HARQ process. For example, rare bursts with a duration below 8ms affect each HARQ process at most once. Therefore, it has the potential to be fully mitigated by HARQ. the

- Smart Rejection: When burst rejection cannot be applied, a rejection pattern is generated which minimizes the impact on HARQ while ensuring periodicity requirements. This pattern is designed to maximize the time interval between successive rejections (cancellations) of subframes carrying a given HARQ process:

o This method is optimal in terms of LTE link robustness protection (HARQ process protection)

o The requirement for periodicity is met on average (LTE rejection is performed with the average required period over the entire LTE rejection pattern). The pattern consists of varying the period between two LTE denials. the

o Avoid underflow/overflow for codecs with periodic behavior.

A general pattern generation algorithm for intelligent LTE rejection may for example be as follows:

Require:

o P: Time period requirement (in ms)

o N: duration requirement (in ms)

o W: HARQ window length (8 ms for UL)

algorithm:

o Find P1 <= P such that

[(MOD(P1,W)>=N) or (MOD(P1,W)>=W-N)]

and

(MOD(P1,W)+N) is an even number

o if (P1 = P)

Continuously apply P

otherwise

Apply K1 times P1, where K1 = W-abs(P-P1)

Apply K2 to multiply P1 + W, where K2 = P-P1.

Here, a simple implementation example of the algorithm is described below:

o P1 = P-abs(MOD(P,W)-N)

o P2 = P1 + W

o K1 = W-(P-P1)

o K2 = P-P1.

An example is illustrated in Figure 28. Along the second timeline 2802, UL subframe rejections and allocation of TTIs to HARQ processes are indicated, where the period between LTE rejections has been determined according to the above algorithm. In this case, the LTE reject pattern period P1 is applied K1 times and P2 is applied K2 times. As can be seen, periodic rejection of TTIs allocated to the same HARQ process is avoided.

It should be noted that this pattern generation algorithm is autonomously adapted in the mobile terminal 105 . It may also apply to 3GPP Release 11 IDC, where the possibility of deciding LTE gap creation at eNodeB level is being discussed. In this case, the definition of LTE reject patterns may be required and those described above may be optimal from a robustness point of view.

In the following, a mechanism for Smart VoLTE (Voice over LTE)-BT HFP coexistence is described.

In this use case, the mobile terminal 105 is assumed to be connected to the headset via BT and voice calls are received or placed over LTE (VoLTE). It is further assumed that the mobile terminal 105 acts as a master BT device (in other words, the BT entity in the mobile terminal 105 is assumed to have a master role). If this is not the case, a BT role switch command can be issued.

Bluetooth communications are organized in piconets, where a single master device controls traffic distribution over 625 μs long time slots. This is illustrated in Figure 29.

Figure 29 shows a transmission diagram.

The transmission diagram illustrates transmission (TX) and reception (RX) by a master, a first slave (slave 1 ) and a second slave (slave 2 ). Masters have transmission opportunities on even slots, while slaves can only transmit on odd slots (based on allocation from the master). Slaves listen for all potential master transmissions every 1.25ms unless they are in a sleep mode (listen, suspend, hold mode) where this constraint is relaxed.

For headset connections, BT entities are typically paired and in low power mode (eg, exchange a transaction every 50 to 500 ms). When a call starts, the BT entity switches to the HFP profile (Hands Free Profile) with very frequent periodic eSCO (Extended Simultaneous Connection Oriented) or SCO (Synchronous Connection Oriented) traffic. This is illustrated in Figure 30.

FIG. 30 shows transmission diagrams 3001 , 3002 .

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

Typically, as illustrated in Figure 30, for HFP, an eSCO setup has eight slot periods, where two consecutive time slots are dedicated to master and slave transmissions followed by retransmission opportunities; while an SCO setup has A period of six slots in which two consecutive time slots are dedicated to master and slave transmissions followed by four idle slots with no opportunity for retransmission.

It should be noted that once the BT devices are paired, the piconet is created and thus the BT system clock and slot counter are turned on. For example, odd and even time slots are then determined. Therefore, attempts to synchronize the Bluetooth system clock with respect to the LTE system clock after piconet establishment may not be possible, nor are odd and even time slots defined. It should also be noted that the term TTI in this paper refers to the LTE TTI (1 ms) and Ts refers to the BT time slot duration (0.625 ms).

In the following, the protection of BT eSCO is described. This applies to the case where the Bluetooth entity (eg implemented by the second transceiver 1018) is using the HFP profile to carry voice from/to the headset with eSCO traffic.

FIG. 31 shows a transmission diagram 3100 .

Top timeline 3101 represents VoLTE traffic (1ms grid) in LTE-FDD UL over the air. The HARQ process is synchronized with an 8ms period and the sound codec has a 20ms period.

A subframe with T and RTn labels corresponds to the initial transmission of a VoLTE subframe and to its nth retransmission (in the sense of a HARQ retransmission). A VoLTE original subframe is illustrated by a first hatch 3103 and a potential retransmission is illustrated by a second hatch 3104 .

The bottom timeline 3102 shows Bluetooth HFP traffic from the perspective of the master device and based on eSCO packets. BT slots with second hatching 3104 correspond to potential BT retransmissions as defined by the eSCO service.

Applying MAC protocol synchronization can allow efficient coexistence between VoLTE and BT HFP operation due to traffic characteristics (period and duration). Two different trade-offs are possible: a first trade-off where only BT-HFP-eSCO initial reception is protected from LTE UL interference, and a second trade-off where both BT-HFP-eSCO initial reception and retransmitted slot reception are protected. Two trade-offs.

Reception of original packets transmitted by a BT slave device can be protected from LTE retransmissions under the following conditions:

- Protection from T

mod(D ₀ ,5TTI) >= TTI– Ts or mod(D ₀ ,5TTI) <= 5TTI–2 Ts

- Protection from RT1

mod(D ₀ ,5TTI) <= 3TTI–2 Ts or mod(D ₀ ,5TTI) >= 4TTI – Ts

- Protection from RT2

mod(D ₀ ,5TTI) <= TTI–2 Ts or mod(D ₀ ,5TTI) >= 2TTI – Ts

- Protection from RT3

mod(D ₀ ,5TTI) <= 4TTI– 2Ts or mod(D ₀ ,5TTI) >= 5 TTI – Ts.

Reception of packets retransmitted by BT slave devices can be protected from LTE retransmissions under the following conditions:

- Protection from T

mod(D ₀ ,5TTI) >= 4TTI or mod(D ₀ ,5TTI) <= 3TTI– Ts

- Protection from RT1

mod(D ₀ ,5TTI) <= TTI– Ts or mod(D ₀ ,5TTI) >= 2TTI

- Protection from RT2

mod(D ₀ ,5TTI) <= 4TTI– Ts or mod(D ₀ ,5TTI) >= 0

- Protection from RT3

mod(D ₀ ,5TTI) <= 2TTI– Ts or mod(D ₀ ,5TTI) >= 3 TTI.

As the first method for coexistence of VoLTE and BT eSCO, BT can be protected from LTE TX, ReTx1, ReTx2, ReTX3 (i.e. protect the first transmission and first three retransmissions of packets) without BT retry protection .

In this case, the BT initial packet exchange (1TX slot + 1 RX slot) is protected from LTE UL transmission, as long as LTE does not retransmit four consecutive times for the same HARQ process. BT retransmissions (if any) may be interfered by LTE UL transmissions. This may be achieved by requiring the BT master initial packet transmission to be delayed by D ₀ relative to the LTE initial subframe transmission, where 2TTI-Ts <= mod(D ₀ , 5TTI) <= 3 TTI – 2 Ts, e.g. 1375μs <= mod (D ₀ ,5ms) <= 1750 μs. An example is shown in FIG. 32 .

FIG. 32 shows a transmission diagram 3200 .

Top timeline 3201 represents VoLTE traffic in LTE-FDD UL. A subframe with T and RTn labels corresponds to the initial transmission of a VoLTE subframe and to its nth retransmission (in the sense of a HARQ retransmission). A VoLTE original subframe is illustrated by a first hatch 3103 and a potential retransmission is illustrated by a second hatch 3104 .

The bottom timeline 3102 shows Bluetooth HFP traffic from the perspective of the master device and based on eSCO packets. BT slots with second hatching 3104 correspond to potential BT retransmissions as defined by the eSCO service.

As a second method for VoLTE and BT eSCO coexistence, BT and BT repetition (i.e. BT packet retransmission) can be protected from LTE TX and ReTx1 (i.e. from packet transmission and packet first packet retransmission). In this case, the BT initial packet exchange (1TX slot + 1 RX slot) and its potential first retransmission are protected from LTE UL transmission, as long as the LTE system does not retransmit twice consecutively for the same HARQ process . If the LTE system retransmits more than two times, some BT transmissions/retransmissions may be disturbed. This may be achieved by requiring the BT master's initial packet transmission to be delayed by D ₁ relative to the LTE initial subframe transmission, where D ₁ = TTI - Ts. For example, mod(D ₁ ,5ms) = 375 us for eSCO and eSCO duplication protection from LTE T and RT1. This transmission scheme corresponds to the transmission scheme shown in FIG. 31 .

As a third method for coexistence of VoLTE and BT eSCO, BT can be protected from LTE TX, ReTx1. BT retries are not protected.

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

This is possible by requiring the BT master initial packet transmission to be delayed by D ₀ relative to the LTE initial subframe transmission, where TTI-Ts <= mod(D ₃ ,5 TTI) <= 3 TTI – 2 Ts. For example, 375 μs <= mod(D ₃ ,5ms) <= 1625 us for eSCO protection from LTE T and RT1. This transmission scheme corresponds to the transmission scheme shown in FIG. 31 .

As another method, BT SCO can be secured as follows. According to Bluetooth, the HFP profile may be used to carry voice from/to the headset via SCO traffic, which occupies 1/3 of the communication medium time and has no retransmission capability. An example is given in Figure 33.

FIG. 33 shows a transmission diagram 3300 .

Top timeline 3301 represents VoLTE traffic in LTE-FDD UL. A subframe with T and RTn labels corresponds to the initial transmission of a VoLTE subframe and to its nth retransmission (in the sense of a HARQ retransmission). A VoLTE original subframe is illustrated by a first hatch 3103 and a potential retransmission is illustrated by a second hatch 3104 .

The bottom timeline 3102 shows Bluetooth HFP traffic from the perspective of the master device and based on SCO packets.

Protects two-thirds of BT packet exchanges (1TX slot + 1 RX slot) from LTE UL transmissions. If some LTE retransmissions happen, it has the potential to interfere with some more BT slots. This can be achieved by requiring the BT to be delayed between TTI-Ts and TTI with respect to the start of the LTE active subframe and TTI - Ts <= mod(D ₂ ,6 Ts) <= TTI. For example, 375 μs <= mod(D ₂ , 3.75ms) <= 1ms for minimum LTE VoLTE interference on SCO service. If _D2 is not in this range, two-thirds of the SCO packets may be interfered by VoLTE subframe transmissions.

In conclusion, the above identified delay or range of delays between VoLTE Tx and BT master Tx (which may be considered optimal) provides the minimum possibility of collision between VoLTE subframe transmission and BT HFP packet reception. Deriving the delay requirement corresponding to eSCO packet usage or SCO packet usage for the BT HFP profile.

The use of eSCO packets may be desirable as it is much better for VoLTE traffic pattern coexistence. If SCO is used, one-third of BT packets are lost due to collision with VoLTE UL subframe, and it cannot be resolved by LTE rejection of this frame, because its impact on call quality will be worse (20 ms loss than 5 ms loss).

Also in eSCO solutions, the third approach may be desirable because:

- It is enough to fully protect BT initial reception

- Its latency requirements are quite relaxed (2 x BT T slots); this can be exploited in case of LTE handover during a call.

Possible concepts could be as follows:

A) Call Settings

1) Complete BT pairing that typically occurs before VoLTE call setup without any specific coexistence constraints. the

2) When an LTE call is established, periodically allocated subframe (SPS based) information is transmitted to the BT added in NRT messaging. For example, it may be available 5 to 10 ms after the SPS pattern is applied. the

3) The BT master then parses the SPS indication message (period, duration, offset) and uses the LTE frame sync RT signal as a synchronization reference. the

4) When eSCO/SCO service is established, the BT master allocates BT slots which meet the delay requirements regarding VoLTE transmission (this is always possible, the delay is 2xT slots as far as the third method is concerned) . the

B) LTE handover.

When LTE performs a handover from a first cell to a second cell during a VoLTE call, the LTE system clock in the first cell may be in a different phase than the LTE in the second cell (or second sector) system clock. SPS assignments can also be different. Therefore, the delay between BT and VoLTE traffic patterns may no longer be met:

1) Handover and new SPS allocation can then be provided to BT via NRT messaging

2) The BT master can change the BT time slot allocation for eSCO traffic in order to meet the delay requirement again (always possible only for the third method above).

It should be noted that there may still be no guarantee that the BT can directly derive the VoLTE subframe position from the SPS indication in the NRT messaging since there is no timestamp mechanism. If not, the BT entity can detect them via monitoring the LTE UL gap envelope (RT interface) using the SPS period information. Because it may take several VoLTE cycles to get VoLTE synchronization in this way, BT may do blind eSCO scheduling at startup and reschedule the VoLTE subframe once it is identified.

It can be seen that this mechanism is optimized for VoLTE with a 20ms period, but it can be used for any SPS based LTE traffic. Only latency requirements may be adapted.

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

- Coexistence friendly toggle

- SR postponed

- Ignore UL authorization

- LTE Denial Control (algorithm utilizing packet error rate monitoring)

- Minimize the impact of LTE rejection on LTE HARQ and thus on LTE link robustness (e.g. by corresponding algorithms)

- Minimize the impact of BT HFP service on VoLTE service.

According to an aspect of the present disclosure, there is provided a radio communication device, as illustrated in FIG. 34 .

FIG. 34 shows a radio communication device 3400 .

The communication device 3400 includes: a first transceiver 3401 configured to transmit and receive at least one signal according to a cellular wide area radio communication technology; and a second transceiver 3402 configured to transmit and receive at least one signal according to a short-range radio communication technology or a metro system radio communication technology Receive at least one signal.

The communication device 3400 further comprises at least one filter 3403 coupled to the second receiver, the filter having filtering characteristics and a processor 3404 coupled to the first transceiver and configured to control the first transceiver to transmit A signal having a transmission bandwidth that is set based on filter characteristics.

The filter is, for example, a bandpass filter.

The at least one filter is for example configured to filter at least one signal received by the second transceiver according to a filter characteristic.

For example, the at least one filter is configured to filter at least one signal received by the second transceiver according to the shape of the filter.

The processor may be further configured to set the transmission bandwidth by allocating, by the first transceiver, one or more sub-channels of the one or more channels provided for signal transmission.

The processor may be further configured to set the transmission bandwidth according to the frequency region where signal rejection by the filter satisfies a predetermined criterion.

For example, the processor is further configured to set the transmission bandwidth according to the frequency region where signal rejection by the filter is higher than a signal rejection threshold.

For example, the processor is further configured to set the transmission bandwidth according to the frequency region where signal rejection by the filter is a maximum.

The processor may eg be configured to set the transmission bandwidth based on the content of an instruction message received by the radio communication device from the further radio communication device (eg base station).

The processor is configured, for example, to set the transmission bandwidth according to the transmission bandwidth control message received by the second communication device.

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

The processor is configured, for example, to generate a transmission bandwidth request message instructing the processor to request one or more transmission bandwidths allocated for signal transmission.

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

The first transceiver is configured, for example, to transmit and receive signals according to a 3rd Generation Partnership Project radio communication technology.

The first transceiver is for example configured to transmit and receive signals according to 4G radio communication technology.

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

According to an aspect of the present disclosure, the second transceiver may transmit and receive signals according to a short-range radio communication technology selected from the group consisting of:

Bluetooth radio communication technology;

UWB radio communication technology;

wireless local area network radio communication technology;

Infrared Data Association Radio Communication Technology;

Z-Wave radio communication technology;

ZigBee radio communication technology;

Radio communication technology for high-performance radio LAN;

IEEE 802.11 radio communication technology; and

Digitally enhanced cordless radio communication technology.

The second transceiver is for example configured to transmit and receive signals according to a metro system radio communication technology selected from the group consisting of:

Global interoperability microwave access radio communication technology;

Wipro radio communication technology;

High performance radio metropolitan area network radio communication technology; and

802.16m advanced air interface radio communication technology.

As illustrated in FIG. 35, according to one aspect of this disclosure, there is provided a method for controlling a radio communication device.

FIG. 35 shows a flowchart 3500 .

At 3501, signals are transmitted and received according to cellular wide area radio communication techniques.

At 3502, signals are transmitted and received according to a short-range radio communication technique or a metro system radio communication technique.

In 3503, the signal received according to the short-range radio communication technology or the metro system radio communication technology is filtered by means of a filter according to the filter characteristic of said filter.

At 3504, the signal is transmitted according to the cellular wide area radio communication technology using the transmission bandwidth set based on the filter characteristic of the filter.

Setting the transmission bandwidth may include allocating one or more subchannels of the one or more channels provided for signal transmission according to cellular wide area radio communication technology.

Setting the transmission bandwidth may include setting the transmission bandwidth according to a frequency region in which signal rejection by the filter satisfies a predetermined standard.

The transmission bandwidth is set, for example, according to the frequency region in which the signal suppression by the filter is above a predetermined signal suppression threshold.

For example, the transmission bandwidth is set according to the frequency region where the signal rejection by the filter is the maximum.

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

For example, the transmission bandwidth is set according to the transmission bandwidth control message received by the second communication device.

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

The method may further include generating a transmission bandwidth request message requesting allocation of one or more transmission bandwidths for signal transmission according to a cellular wide area radio communication technology.

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

According to one aspect of the present disclosure, transmitting and receiving signals according to cellular wide area radio communication technology includes transmitting and receiving signals according to 3rd Generation Partnership Project radio communication technology.

According to an aspect of the present disclosure, transmitting and receiving signals according to cellular wide area radio communication technology includes transmitting and receiving signals according to 4G radio communication technology.

Transmitting and receiving signals according to cellular wide area radio communication technology includes, for example, transmitting and receiving signals according to long term evolution radio communication technology.

Transmitting and receiving signals according to short-range radio communication techniques includes, for example, transmitting and receiving signals according to short-range radio communication techniques selected from the group consisting of:

Bluetooth radio communication technology;

UWB radio communication technology;

wireless local area network radio communication technology;

Infrared Data Association Radio Communication Technology;

Z-Wave radio communication technology;

ZigBee radio communication technology;

Radio communication technology for high-performance radio LAN;

IEEE 802.11 radio communication technology; and

Digitally enhanced cordless radio communication technology.

Transmitting and receiving signals according to a metro system radio communication technique includes, for example, transmitting and receiving signals according to a metro system radio communication technique selected from the group consisting of:

Global interoperability microwave access radio communication technology;

Wipro radio communication technology;

High performance radio metropolitan area network radio communication technology; and

802.16m advanced air interface radio communication technology.

In the radio communication device 3400 , for example, the first transceiver corresponds to the LTE subsystem 2101 , and the second transceiver corresponds to the WLAN/Bluetooth communication circuit 2102 . The processor may correspond to a controller of the first transceiver. For example, the first processor may correspond to communication circuitry 2104 . For example, the first processor may correspond to (or include) the RT arbitration entity 2111 . Alternatively, any corresponding tasks may be performed by the applications processor 2105 .

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

The NRT arbiter 2108 arbitrates and indicates static information (such as select frequency band or power level of choice) to LTE and connectivity (i.e. Bluetooth or WLAN). It can also provide indication to the RT arbiter located in the LTE subsystem.

For example, the NRT arbiter 2108 does not arbitrate between WLAN and BT (arbitration between these is done eg in the connectivity chip).

When the LTE subsystem camps on a new cell, the LTE SW indicates the new LTE information to the NRT 2108 arbiter and this information is stored for reuse in NRT algorithms, e.g. according to 2407, 2408, 2410.

The NRT arbiter then runs the NRT algorithm to protect BT from LTE-FDD.

This algorithm runs in the NRT arbitration unit 2108 . It is split into two subroutines:

Whenever the LTE subsystem 2101 camps on a new cell, subroutine 1 is activated while BT is active (eg BT status is indicated separately via NRT coexistence interface). It identifies the frequency range in which BT can safely co-operate with LTE under worst-case conditions. Subroutine 1 is illustrated in FIG. 36 .

FIG. 36 shows a message flow diagram 3600.

Message flow occurs between the NRT arbiter 3601 corresponding to the NRT arbiter 2108 and the BT communication circuit 3602 corresponding to the WLAN/BT communication circuit 2102 .

At 3603, the NRT arbiter 3601 loads parameters from non-volatile memory. These may include parameters such as: Lant (antenna isolation) between LTE Tx and WLAN/BT Rx, P_LTE_max (maximum power of LTE), minimum number of BT channels Nmin required to apply AFH, BT_max_PSD (in dBm/Mhz unit) (maximum BT power spectral density), BT_MAX_BLKR (BT maximum tolerable blocker interference), BT_MAX_LIN (BT maximum tolerable in-band noise interference), L_OOB() (contains LTE transmitter out-of-band spectrum (relative to in-band power )) and ISM RX filter shape parameters (e.g. Band7Filter(,1) (or RxFilter(,1)).

In 3604, the NRT arbiter 3601 calculates BT_SAFE_RX_FREQ_MIN and BT_SAFE_RX_FREQ_MAX based on the following parameters:

- LTE frequency band

- BT maximum tolerable blocker interference

- BT maximum tolerable in-band noise interference

- LTE frequency

- ISM RX filter shape

- LTE Tx OOB noise

- Antenna isolation

BT_SAFE_RX_FREQ_MIN, BT_SAFE_RX_FREQ_MAX give the ISM frequency range (1Mhz accuracy) that meets the goals of common operation (sensitivity reduction, throughput loss) in worst case (LTE maximum power, maximum bandwidth, BT Rx sensitivity level). These are eg static such that they can be precomputed and stored in a lookup table.

In 3605 , the NRT arbiter 3601 transmits BT_SAFE_RX_FREQ_MIN and BT_SAFE_RX_FREQ_MAX to the BT communication circuit 3602 .

At 3606 , the BT communication circuit 3602 stores BT_SAFE_RX_FREQ_MIN and BT_SAFE_RX_FREQ_MAX and confirms receipt of these parameters at 3607 . Subroutine 2 is illustrated in FIG. 37 .

FIG. 37 shows a message flow diagram 3700 .

Message flow occurs between the NRT arbiter 3701 corresponding to the NRT arbiter 2108 and the BT communication circuit 3702 corresponding to the WLAN/BT communication circuit 2102 .

Whenever the BT communication circuit 3702 modifies its AFH mapping in 3703, subroutine 2 is activated.

This modification is done eg autonomously on the BT side, for business purposes or for coexistence purposes.

In 3704, the BT communication circuit 3702 then stores the minimum BT frequency and the maximum BT frequency according to the changed AFH map.

In 3705, the BT core (ie BT communication circuit 3702) evaluates whether its entire AFH map is contained within a safe frequency range and indicates the result to the NRT arbiter 3701 in 3706 (in this example, by means of a single bit indication). When the information is received, the NRT arbiter 3701 enables/disables the real-time interface (or a subset of the real-time interface if the distinction between BT and WLAN is possible) in 3707 and sends to the BT communication circuit 3702 in 3708 confirm.

In cases where there is no way to distinguish between WiFi and BT, if both parameters BT_RX_KILL and WIFI_RX_KILL (see Figure 39) are disabled, the real-time interface is disabled. Otherwise, the real-time interface is enabled.

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

This algorithm runs in the NRT arbitration unit 2108 . It is split into two subroutines:

Subroutine 1 is activated whenever the LTE subsystem 2101 camps on a new cell while the WLAN is active (eg WLAN status is indicated separately via the NRT coexistence interface). It identifies the frequency range in which WLAN can safely co-operate with LTE. Subroutine 1 is illustrated in FIG. 38 .

FIG. 38 shows a message flow diagram 3800 .

Message flow occurs between the NRT arbiter 3801 corresponding to the NRT arbiter 2108 and the WLAN communication circuit 3802 corresponding to the WLAN/BT communication circuit 2102 .

At 3803, the NRT arbiter 3801 loads parameters from non-volatile memory. These may include parameters: Lant (antenna isolation) between LTE Tx and WLAN/BT Rx, P_LTE_max (maximum power for LTE), WLAN_max_PSD (maximum WLAN power spectral density), WLAN_MAX_BLKR (maximum tolerable blocker interference for WLAN), WLAN_MAX_LIN (WLAN maximum tolerable in-band noise interference), L_OOB() (contains LTE transmitter out-of-band spectrum (relative to in-band power)) and ISM RX filter shape parameters (such as Band7Filter(, BW) (or RxFilter(, BW)). Band7Filter (, BW) is the ISM RX filter shape integrated on the LTE cell BW. 5 Band7Filter tables are stored in NVM, corresponding to BW = 1, 5, 10, 15, 20 Mhz).

In 3804, the NRT arbiter 3801 calculates WLAN_SAFE_RX_FREQ_MIN and WLAN_SAFE_RX_FREQ_MAX based on the following parameters:

- LTE frequency band

- WLAN maximum tolerable blocker interference

- WLAN maximum tolerable in-band noise interference

- LTE frequency

- ISM RX filter shape

- LTE Tx OOB noise

- Antenna isolation

WLAN_SAFE_RX_FREQ_MIN, WLAN_SAFE_RX_FREQ_MAX gives the ISM band range (1Mhz accuracy) that meets the goals of common operation (sensitivity reduction, throughput loss) in worst case (LTE maximum power, maximum bandwidth, WLAN Rx sensitivity level). These are eg static such that they can be precomputed and stored in a lookup table.

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

In 3806 the WLAN communication circuit 3802 stores WLAN_SAFE_RX_FREQ_MIN and WLAN_SAFE_RX_FREQ_MAX and in 3807 confirms receipt of these parameters. Subroutine 2 is illustrated in FIG. 39 .

FIG. 39 shows a message flow diagram 3900.

Message flow occurs between the NRT arbiter 3901 corresponding to the NRT arbiter 2108 and the WLAN communication circuit 3902 corresponding to the WLAN/BT communication circuit 2102 .

Subroutine 2 is activated whenever the WLAN communication circuit 3902 modifies its list of active WLAN channels in 3903 .

This modification is done eg autonomously on the WLAN side, for business purposes or for coexistence purposes.

In 3904, the WLAN communication circuit 3902 then stores the minimum WLAN frequency and the maximum WLAN frequency according to the change list of active WLAN channels.

In 3905, the WLAN core (ie WLAN communication circuit 3902) evaluates whether its WLAN channel is within a safe frequency range and indicates the result to the NRT arbiter 3901 in 3906 (in this example, by means of a single bit indication). When the information is received, the NRT arbiter 3901 enables/disables the real-time interface (or a subset of the real-time interface if the distinction between BT and WLAN is possible) in 3907 and sends to the WLAN communication circuit 3902 in 3908 confirm. In cases where there is no way to differentiate between WiFi and BT, if both parameters BT_RX_KILL (see Figure 39) and WIFI_RX_KILL are disabled, the real-time interface is disabled. Otherwise, the real-time interface is enabled.

In the following, further examples of non-real-time application interfaces, non-real-time coexistence interfaces and parameters stored in non-volatile memory are given.

The NRT application interface transports messages carrying information about connectivity and LTE applications. The "I/O" field has the following parameter meanings: "I" means from AP to NRTA, and "O" means from NRTA to AP.

The NRT coexistence interface transmits messages carrying CWS information. The "I/O" field has the following parameter meanings: "I" means from CWS to NRTA, and "O" means from NRTA to CWS.

The table below lists the parameters stored in the non-volatile memory used.

According to one aspect of this disclosure, a radio communication device is provided as illustrated in FIG. 40 .

FIG. 40 shows a radio communication device 4000 .

The radio communication device 4000 includes a first transceiver 4001 configured to transmit and receive at least one signal according to a cellular wide area radio communication technology; and a second transceiver 4002 configured to transmit and receive at least one signal according to a short-range radio communication technology or a metro system radio communication technology Transmit and receive at least one signal.

The radio communication device 4000 further comprises at least one filter 4003 coupled to the second receiver, said filter having filtering characteristics.

Furthermore, the radio communication device 4000 comprises a message generator 4004 configured to generate a message with a suggestion to set the transmission bandwidth for the first transceiver, wherein the suggestion is based on the filter characteristic.

For example, the first transceiver is configured to transmit a message to a further communication device (eg a base station).

According to one aspect of this disclosure, as illustrated in Figure 41, there is provided a method for controlling a radio communication device.

FIG. 41 shows a flowchart 4100 .

Flowchart 4100 illustrates a method for operating a radio communication device.

In 4101, the first transceiver transmits and receives at least one signal according to cellular wide area radio communication technology.

In 4102, the second transceiver transmits and receives at least one signal according to a short-range radio communication technique or a metro system radio communication technique.

In 4103, the radio communication device performs filtering by means of the filter signal received according to the short-range radio communication technology or the metro system radio communication technology according to the filter characteristic of the filter.

In 4104, the radio communication device generates a message with a recommendation to set a transmission bandwidth for the first transceiver, wherein the recommendation is based on the filtering characteristic.

The radio communication device may further transmit the message to a further communication device.

It should be noted that in the context of radio communication device 3400 and the method illustrated in FIG. 35 , the examples are approximately valid for radio communication device 4000 and the method illustrated in FIG. 41 .

While the invention has been shown and described with particular reference to particular aspects, it will be understood by those skilled in the art that changes may be made in form and in the present invention without departing from the spirit and scope of the invention as defined by the appended claims. Various changes in details. The scope of the invention is thus indicated by the appended claims and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced. the

Claims (23)

1. A radio communication device comprising: a first transceiver configured to transmit and receive at least one signal according to a cellular wide area radio communication technique; a second transceiver configured to transmit and receive at least one signal according to a short-range radio communication technique or a metro system radio communication technique; at least one filter coupled to the second receiver, the filter having filter characteristics; having A processor coupled to the first transceiver and configured to control the first transceiver to transmit a signal having a transmission bandwidth set based on the filtering characteristic. 2. The radio communication device according to claim 1, Wherein the at least one filter is configured to filter the at least one signal received by the second transceiver according to the filtering characteristic. 3. The radio communication device according to claim 2, Wherein the at least one filter is configured to filter at least one signal received by the second transceiver according to the shape of the filter. 4. The radio communication device according to claim 1, Wherein the processor is further configured to set the transmission bandwidth by allocating, by the first transceiver, one or more sub-channels of the one or more channels provided for signal transmission. 5. The radio communication device according to claim 1, Wherein the ] processor is further configured to set the transmission bandwidth according to the frequency region, wherein the signal rejection by the filter satisfies a predetermined criterion. 6. The radio communication device according to claim 5, Wherein, the processor is further configured to set the transmission bandwidth according to a frequency region, wherein the signal rejection by the filter is higher than a predetermined signal rejection threshold. 7. The radio communication device according to claim 6, Wherein, the processor is further configured to set the transmission bandwidth according to a frequency region in which signal suppression by the filter is a maximum value. 8. The radio communication device according to claim 1, Wherein the processor is configured to set the transmission bandwidth based on the content of an instruction message received by the radio communication device from another radio communication device. 9. The radio communication device according to claim 1, Wherein the processor is configured to set the transmission bandwidth according to a transmission bandwidth control message received by the second communication device. 10. The radio communication device according to claim 9, Wherein said second communication device is a radio base station. 11. The radio communication device according to claim 1, Wherein the processor is configured to generate a transmission bandwidth request message indicating that the processor requests one or more transmission bandwidths allocated for signal transmission. 12. The radio communication device according to claim 1, Wherein the processor is configured to generate a filter characteristic message comprising information about the filter characteristic of the filter. 13. The radio communication device of claim 1, Wherein the first transceiver is configured to transmit and receive signals according to the 3rd Generation Partnership Project radio communication technology. 14. The radio communication device according to claim 1, Wherein said first transceiver is configured to transmit and receive signals according to 4G radio communication technology. 15. The radio communication device according to claim 14, Wherein the first transceiver is configured to transmit and receive signals according to the long term evolution radio communication technology. 16. The radio communication device of claim 1, wherein the second transceiver is configured to transmit and receive signals according to a short-range radio communication technology selected from the group consisting of: Bluetooth radio communication technology; UWB radio communication technology; wireless local area network radio communication technology; Infrared Data Association Radio Communication Technology; Z-Wave radio communication technology; ZigBee radio communication technology; Radio communication technology for high-performance radio LAN; IEEE 802.11 radio communication technology; and Digitally enhanced cordless radio communication technology. 17. The radio communication device of claim 1, wherein said second transceiver is configured to transmit and receive signals according to a metro system radio communication technology selected from the group consisting of: Global interoperability microwave access radio communication technology; Wipro radio communication technology; High performance radio metropolitan area network radio communication technology; and 802.16m advanced air interface radio communication technology. 18. A method for controlling a radio communication device, the method comprising: transmit and receive signals based on cellular wide area radio communication technology; Transmission and reception of signals according to short-range radiocommunication technology or metropolitan area system radiocommunication technology; filtering by means of a filter signal received according to short-range radio communication technology or metro system radio communication technology according to the filter characteristics of said filter; A signal is transmitted according to a cellular wide area radio communication technique using a transmission bandwidth set based on the filter characteristic of the filter. 19. The method of claim 18, Wherein setting the transmission bandwidth includes allocating one or more subchannels of one or more channels provided for signal transmission according to cellular wide area radio communication technology. 20. A radio communication device comprising: a first transceiver configured to transmit and receive at least one signal according to a cellular wide area radio communication technique; a second transceiver configured to transmit and receive at least one signal according to a short-range radio communication technique or a metro system radio communication technique; at least one filter coupled to the second receiver, the filter having filtering characteristics; and A message generator configured to generate a message with a recommendation to set a transmission bandwidth for the first transceiver, wherein the recommendation is based on the filtering characteristic. 21. The radio communication device of claim 20, Wherein the first transceiver is configured to transmit the message to another communication device. 22. A method for operating a radio communication device, comprising: the first transceiver transmits and receives at least one signal according to a cellular wide area radio communication technique; the second transceiver transmits and receives at least one signal according to a short-range radio communication technique or a metro system radio communication technique; by means of filtering the filter signal received according to the short-range radio communication technology or the metro system radio communication technology according to the filtering characteristics of said filter, A message is generated with a recommendation to set a transmission bandwidth for the first transceiver, wherein the recommendation is based on the filtering characteristic. 23. The method of claim 22, Further comprising transmitting the message to another communication device.

Images