Radio coexistence in wireless networks

Radio coexistence in wireless networks

Radio coexistence in wireless networks

[Cross-reference of related applications]

This application claims US Provisional Patent Application No. 61/646,223, Volume No. P45300Z, filed on May 11, 2012, the entire specification of which is hereby incorporated by reference for all purposes in its entirety.

The present invention relates to radio coexistence in wireless networks.

Modern wireless devices, such as mobile phones, tablet computers, and other portable computing devices, often include multiple types of radios for communication. For example, a smart phone may include a 4G transceiver connected to a cell tower, a WiFi transceiver connected to a local Internet hotspot, and a Bluetooth transceiver connected to nearby devices such as earphones or keyboards. The WiFi transceiver can receive information at substantially the same time as the Bluetooth transceiver transmits information. In some examples, the 4G transceiver can transmit information at substantially the same time as the Bluetooth transceiver receives the information. Therefore, coexistence interference may occur between the WiFi transceiver and the Bluetooth transceiver operating in the smart phone, or between the 4G transceiver and the Bluetooth transceiver. Between transmitters, thereby reducing the communication utility of each of the co-located transceivers.

<p>102Packet</p><p>104Sub Frame</p><p>106Start</p><p>310Time-sharing duplex configuration</p><p>320Time-sharing duplex configuration</p><p>510Off-chain reference resources</p><p>520CSI notification subframe</p><p>700Radio Coexistence System</p><p>702Bluetooth Radio</p><p>7043GPP LTE radio</p><p>706Co-located radio</p><p>710Intermittent receiving module</p><p>720Channel status information notification module</p><p>730Reference resource sub-frame selection module</p><p>740Radio Link Monitoring Module</p>

The features and advantages of the present invention become more obvious from the previous detailed description in conjunction with the accompanying drawings. The detailed description and the accompanying drawings illustrate the features of the present invention together with examples, and in the figures:

Figure 1 shows the timing of a Bluetooth packet synchronized with the sub-frames in the third-generation partnership project (3GPP) long-term evolution (LTE) transceiver in a number of time division duplex (TDD) configurations according to an example picture.

Figure 2 is a diagram showing a long discontinuous reception (DRX) cycle according to an example.

Figures 3A and 3B show an exemplary TDD configuration supporting DRX according to an example.

FIG. 3C is a timing diagram showing LTE transmission/reception patterns and Bluetooth transmission/reception patterns according to an example.

Figure 4 shows an example of an ASN code based on an example of DRX configuration information.

Figure 5 shows channel state information (CSI) reference resources during a long DRX cycle according to an example.

Figure 6 depicts a flowchart of a method for reducing coexistence interference in multiple radio devices according to an embodiment of the present invention.

Figure 7 shows a block diagram of a radio coexistence system according to an example.

Figure 8 shows a mobile wireless device according to an example.

Reference is made to the exemplary embodiment shown, and specific terms are used in this text The exemplary embodiments are described in words. Nevertheless, it should be understood that there is no intention to limit the scope of the present invention in any way.

[Content and Implementation of the Invention]

Before disclosing and describing the present invention, it should be understood that the present invention is not limited to the specific structures, procedures, or materials disclosed herein, but extends to equivalents of these as understood by those with ordinary knowledge in the related art. It should also be understood that the terminology used herein is only used to describe specific embodiments and is not intended to be limiting.

definition

As used herein, the term "substantially" refers to the complete or almost complete range or extent of an action, characteristic, property, state, structure, object, or result. For example, an object that is "substantially" enclosed means that the object is completely enclosed or almost completely enclosed. The exact allowable degree of deviation from absolute completeness may in some cases depend on the specific context. However, in general, the closeness of completeness will be such that the overall result is as if absolute and total completeness were obtained. The use of "substantially" also applies when it is used in a negative connotation to refer to the complete or almost complete lack of an action, characteristic, property, state, structure, object, or result.

Other words can be defined elsewhere in the body of this specification.

Exemplary embodiment

A preliminary overview of technical embodiments is provided below, and then specific technical embodiments are described in more detail later. This preliminary summary is intended to help readers understand the technology more quickly, and is not intended to identify the key features or necessary features of the technology, nor is it intended to limit the scope of the subject matter of patent claims.

Bluetooth transceivers are often collocated with other types of radios and/or transceivers. For example, transceivers that use Orthogonal Frequency Division Multiple Access (OFDMA) to communicate, such as the Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) transceiver, the Institute of Electrical and Electronics Engineers (IEEE) 802.16 transceiver, often It is called WiMAX (Global Interoperability for Microwave Access), a wireless local area network (WLAN) transceiver (ie, IEEE 802.11 radio, often referred to as WiFi), and/or a global navigation satellite system (GNNS) receiver.

Each collocated radio can be used for a specific purpose. For example, a Bluetooth transceiver can be used to communicate with a wireless private area network (WPAN), a WiFi transceiver can be used to communicate with a wireless local area network (WLAN), and a 3GPP LTE or WiMAX transceiver can be used to communicate with a wireless wide area network (WWAN) communication.

Bluetooth transceivers juxtaposed with other types of transceivers that use OFDMA for communication (such as 3GPP LTE transceivers, WiMAX transceivers, and/or WiFi transceivers) operate simultaneously in wireless devices (such as smart phones or tablets) It will produce interference that reduces the data throughput of both transceivers. Throughout this specification, multiple examples of collocated Bluetooth transceivers and 3GPP LTE transceivers are proposed. This is not meant to be limiting. The same system(s) and method(s) can be applied to other types of OFDMA radios operating in Time Domain Duplex (TDD) collocated with Bluetooth transceivers.

Generally speaking, TDD refers to a duplex communication link, in which the uplink and the downlink are separated by the allocation of different time slots in the same frequency band. Since TDD allows an asymmetric flow of uplink and downlink data transmission, the time slots for uplink and downlink transmission are allocated to users. TDD is conducive to the asymmetry of the data rate on the chain and the chain.

Bluetooth reception may conflict with the transmission from the 3GPP LTE transceiver, especially when the transceivers are placed on the same device, such as smart phones, tablets, netbooks, laptops, or another type of wireless Mobile device. Bluetooth transmission can also reduce the sensitivity of reception in the 3GPP LTE transceiver.

To reduce coexistence interference, there are several possible solutions. One possible solution is to use frequency division multiplexing (FDM) to move the signal from one transceiver away in frequency from the signal of another transceiver, thereby creating more frequency separation. Another possible solution is to use time division multiplexing (TDM), where scheduling can be used so that when one transceiver is transmitting, another collocated transceiver will not receive at the same time.

An example of TDM may include discontinuous reception (DRX), which will be discussed in more detail below. The radio frequency solution involves the use of radio frequency filtering, which can be used to reduce out-of-bounds (OOB) emissions, using filters at the transmitter, or using filters at the receiver to block out-of-bounds signals. Power-based solutions can be used to reduce the transmission power, thereby potentially reducing the level of interference. There can also be mixed solutions by combining two or more of the aforementioned solutions.

For 3GPP LTE transceivers and collocated Bluetooth transceivers, the weight can be defined Complex time-domain transmission/reception (Tx/Rx) pattern to coordinate its transmitter and receiver. If the data is periodically configured in time, the Tx/Rx pattern can be repeated at known intervals. Known intervals allow continuous reservations in 3GPP LTE transceivers to reduce or avoid interference between different transceivers.

For example, the repeated Tx/Rx pattern defines a specific Bluetooth transmission time slot for each eSCO packet transmitted by the Bluetooth transceiver to prevent Bluetooth transmission from interfering with 3GPP LTE reception, and to protect 3GPP LTE transmission is not interfered by Bluetooth reception.

The ability to use persistent reservations to coordinate 3GPP LTE and Bluetooth transmitters and receivers also allows other types of transceivers to be collocated. For example, the WiFi transceiver can be coordinated to communicate in a specific period in the coordination formed between the 3GPP LTE and the Bluetooth transceiver.

Figure 1 shows the transmission and reception of eSCO formatted packet 102 for Bluetooth radio operating in Time Division Duplex (TDD) mode and Tx/Rx subframe 104 for all seven configurations of 3GPP LTE radio . Use a slot of Bluetooth eSCO packet as an example to show the figures and tables presented in this article. However, this interference avoidance technique can be applied to other Bluetooth profiles and packet lengths (such as three- or five-slot packets). Bluetooth eSCO packets can include various forms with different numbers of transmission and reception time slots. For a single slot eSCO packet, Bluetooth specifies the interval of 6, 8, 10, 12, 14, 16, and 18. The interval shown in Figure 1 is T_eSCO=8, including four transmission time slots and four reception time slots. Bluetooth also specifies the retransmission window W_eSCOIt is 0, 2, or 4. The retransmission window indicates that a Bluetooth packet is in its interval Within (T_eSCO) The number of attempts to transmit that can occur. Although this manual currently limits retransmission attempts to 0, 2, or 4, when T_eSCOWhen it is equal to or greater than 8, additional retransmission attempts may be included. Future Bluetooth standards may include additional retransmission attempts, and the embodiments disclosed herein are not limited to 0, 2, or 4 described in this standard.

The 3GPP LTE standard, as used herein, may include 3GPP LTE release 8 in the fourth quarter of 2008, 3GPP LTE advanced release 10 in the first quarter of 2011, and release 11 in the third quarter of 2012. However, the embodiments disclosed in this article are not limited to these issuances. When using the same TDD configuration and sub-frame timing, future standards may also be applicable. Transceivers that operate under at least one of these 3GPP LTE issues are also referred to herein as LTE transceivers. The use of the terms 3GPP, 3GPP LTE, or LTE is not meant to be limiting. Any of these terms can refer to anyone issued by 3GPP.

Currently, 3GPP LTE communication defines seven different LTE TDD configurations. Figure 1 provides an example of each LTE configuration, numbered from 0 to 6. Each configuration is aligned at the beginning 106 of the longer consecutive number of received subframes for each configuration. Synchronize the Bluetooth packet so that the first receiving time slot (time slot 1) is aligned with the first receiving sub-frame of the continuous receiving sub-frame in each of the seven LTE configurations.

As shown in Figure 1, the Bluetooth time slot 102 has a different time period from the LTE sub-frame. Each Bluetooth slot has a period of 0.625 milliseconds (ms), and each LTE frame has a frame period of 10ms. Each LTE frame is composed of 10 sub-frames. Therefore, each sub-frame has a period of 1 ms. Therefore, even if the Bluetooth packet is synchronized, the transmission slot is 0 Align with one of the transmission sub-frames in each LTE TDD configuration, and the receiving slot 1 is aligned with the first receiving sub-frame in the continuous receiving sub-frame of each configuration, the transmission and receiving slots will soon be It becomes misaligned, so that the transmission and reception from the Bluetooth and 3GPP transceivers will cause co-channel interference in each of the transceivers.

Co-channel interference may occur when one of the transceivers transmits in the receiving interval of the other transceiver. This is especially true when the 3GPP LTE transceiver transmits during the receiving period of the Bluetooth transceiver, because the 3GPP LTE transceiver transmits at significantly higher power and may therefore overpower (or conflict) the Bluetooth transceiver Try to receive most of the Bluetooth signal during the Bluetooth reception period.

Figure 2 is a diagram showing a long discontinuous reception (DRX) cycle according to an example. The concept of DRX was introduced in 3GPP LTE Release 8 to save power. DRX can be used to enable wireless devices, such as user equipment (UE) in the 3GPP LTE network, to monitor control channels intermittently, such as the physical downlink control channel (PDCCH) transmitted from a transmission station such as an enhanced node (eNB or eNodeB) ). Intermittent monitoring by using DRX can provide significant power savings at the UE, because the receiver at the UE can be turned off for a selected period. The schedule of 3GPP LTE transceivers using DRX will be explained more fully below.

According to an embodiment of the present invention, in addition to saving power, DRX can also be used to provide a TDM solution to reduce the coexistence interference of collocated devices. For example, using DRX can reduce the coexistence interference between co-located 3GPP LTE transceivers and low-power Bluetooth (BT) transceivers by scheduling BT transceivers Transmit when the LTE transceiver is not receiving.

In one embodiment, a transceiver in a multi-radio device (such as an LTE transceiver) can be configured to be more often configured by reducing the amount of time the transceiver monitors a control channel (such as a physical downlink control channel (PDCCH)). closure. In other words, the transceiver can communicate with a transmission station (called a network node) to negotiate the period when the transceiver will receive communication from the network node. During the negotiated period when no information is being received, the transceiver can turn off its receiver and enter a low power state. DRX is used in several different wireless communication standards, including but not limited to 3GPP LTE releases 8, 9, 10, and 11.

If the 3GPP LTE transceiver is configured for DRX and it is in RRC_CONNECTED mode, the 3GPP LTE transceiver can operate to monitor intermittently. Otherwise, 3GPP LTE transceivers that are not configured for DRX can continuously monitor the PDCCH. The radio resource control (RRC) can be used to control the DRX operation in the 3GPP LTE transceiver by configuring the parameters onDurationTimer, drx-InactivityTimer, longDRX-Cycle, drxStartOffset, and optional drxShortCycleTimer and shortDRX-Cycle. When the short DRX cycle is not configured, the 3GPP LTE transceiver monitors the PDCCH at the beginning of the longDRX-Cycle parameter (according to the length defined in onDurationTimer). If the downlink and/or uplink transmission can be completed, the 3GPP LTE transceiver can stop monitoring the PDCCH after the onDuration-Timer. In the remaining DRX cycles (such as short DR cycles), the 3GPP LTE transceiver may become inactive. During this period, the eNB does not schedule downlink transmission and the eNB does not require the 3GPP LTE transceiver to transmit uplink data. When the short DRX cycle is configured, the short DRX cycle can be regarded as The confirmation period when the packet arrives late is before the 3GPP LTE transceiver enters the long DRX cycle. When the 3GPP LTE transceiver is in a short DRX cycle and data arrives at the eNB, the data is scheduled to be transmitted at the next wake-up time, after which the 3GPP LTE transceiver continues to receive. On the other hand, if no data arrives at the eNB during the short DRX cycle, the 3GPP LTE transceiver can enter the long DRX cycle if the current packet activity ends. The DRX active time is the period when the 3GPP LTE transceiver monitors the PDCCH in the DRX cycle.

Returning to Figure 2, an exemplary long DRX cycle is shown. The long DRX cycle may include an ON period and an OFF period. During the ON period of the long DRX cycle (that is, the scheduling period), the eNB can schedule transmission with the UE. During the OFF period of the long DRX cycle (that is, the non-scheduled period), the eNB does not schedule transmission with the UE. Generally speaking, the UE can transition from an unnecessary short DRX cycle to a long DRX cycle when a timer expires.

Figures 3A and 3B show exemplary TDD configurations 310 and 320 supporting DRX patterns according to an example. One limitation of using DRX solutions to reduce coexistence interference in multiple radio devices is that the currently supported long DRX cycle values do not include several values that can be used to significantly improve in-device coexistence scenarios. For example, long DRX cycle values that can be used to reduce interference in devices in LTE and Bluetooth scenarios (for example, LTE transceiver and Bluetooth transceiver transmitting/receiving information substantially simultaneously transmitting/receiving information) are not allowed to allow long DRX cycle values. These long DRX cycle values may include 2 milliseconds (ms), 5ms, and/or 8ms. As will be discussed in more detail below, 2ms, 5ms, and 8ms long DRX cycle values can provide one or more useful hybrid automatic repeat requests (HARQ) The program keeps the pattern.

One limitation of using DRX to reduce coexistence interference in LTE and Bluetooth scenarios is that when the LTE ON period is not extended, DRX supports connected LTE downlink (DL) subframes within a single DRX cycle. Using the currently available DRX cycle value, when the DRX solution is used for LTE and Bluetooth scenarios, the DRX cycle is 10ms. In addition, a 5ms short DRX cycle can be used within a 10ms long DRX cycle. Therefore, DRX can support bit pattern patterns with LTE ON downlink sub-frames that are connected in a 10ms period or a 5ms period.

Figure 3A shows an example of a DRX pattern that can be used to reduce the cycle time of interference among devices in a multi-radio device. In particular, it shows the benefits of including a 2ms long DRX cycle for LTE and Bluetooth scenarios. The exemplary configuration 310 is TDD configuration 2. The configuration 310 includes m frames and has a loop start offset of 2 ms. The total length of configuration 310 is 10ms long, and each subframe is 1ms long. In addition, the configuration 310 can be represented by the bitmap 0111010111. In other words, "0" means that the subframe cannot be used (for example, the subframe is closed), and "1" means that the subframe can be used. Here, the closed sub-frames are 0, 4, and 6, which results in a bitmap of 0111010111. The sub-frame in the configuration 310 can be a downlink (DL) sub-frame or an uplink (UL) sub-frame. Here, the DL sub-frame is gray and the UL sub-frame is white. According to TDD configuration 2 (which is one of the seven available TDD configurations), subframes 0, 1, 3, 4, 5, 6, 8, and 9 are DL subframes and subframes 2 and 7 is the upper chain frame. In addition, for DRX types related to LTE and Bluetooth plots, the upper chain is generally ignored Frame. Therefore, sub-frames 0, 4, and 6 are closed, and sub-frames 2 and 7 are on the chain, resulting in sub-frames 1, 3, 5, 8, and 9. In other words, sub-frames 1, 3, 5, 8, and 9 are LTE ON sub-frames and are represented by checkered sub-frames.

Therefore, the 2ms long DRX cycle value is beneficial to the configuration 310, which may allow more HARQ bit patterns to be supported. The first sub-frame is included in the first 2ms cycle; the third sub-frame is included in the second 2ms cycle; the fifth sub-frame is included in the third 2ms cycle; and the eighth and Both of the ninth subframes are included in the fifth 2ms cycle. Neither sub-frame 6 or 7 is included in the fourth 2ms cycle because sub-frame 6 is OFF and sub-frame 7 is an up-chain sub-frame. Subframe 8 is regarded as onDuration, because the unit of onDurationTimer is a PDCCH subframe, which is a DL subframe in the case of TDD. Therefore, onDurationTimer starts in subframe 7, but since subframe 7 is a UL subframe, it extends to subframe 8. Therefore, the sub-frame is regarded as ON. If the 2ms long DRX cycle is not supported, another HARQ bitmap pattern will be used, which will reduce the number of sub-frames that can be used by LTE.

Figure 3B shows an example of another DRX pattern that can be used to reduce the cycle time of interference among devices in a multi-radio device. In particular, it shows the benefits of including a 5ms long DRX cycle for LTE and Bluetooth scenarios. In particular, the use of a 5ms long DRX cycle allows the use of additional HARQ bitmap patterns. If the 5ms long DRX cycle cannot be used, fewer LTE subframes can be used.

Demonstration configuration 320 is TDD configuration 2. Configuration 320 includes m messages Frame, and has a loop start offset of 5ms. In addition, the configuration 320 can be represented by the bitmap 0111101111. Here, the closed sub-frames are 0 and 5, which results in a bitmap of 0111010111. According to TDD configuration 2 (which is one of the seven available TDD configurations), subframes 0, 1, 3, 4, 5, 6, 8, and 9 are DL subframes and subframes 2 and 7 is the upper chain frame.

When considering DRX patterns related to LTE and Bluetooth scenarios, the uplink sub-frames (ie, sub-frames 2 and 7) are generally ignored, and sub-frames 0 and 5 are closed, and the result is sub-frame 1. 3, 4, 6, 8, and 9. In other words, sub-frames 1, 3, 4, 6, 8, and 9 are LTE ON downlink sub-frames received by the 3GPP LTE transceiver. Therefore, the 5ms long DRX cycle value is beneficial to the configuration 320. Subframes 1, 3, and 4 are included in the first 5ms cycle, and subframes 6, 8, and 9 are included in the second 5ms cycle. The 10ms long DRX cycle value cannot be used with TDD configuration 2 because subframe 5 is closed.

In LTE and Bluetooth scenarios, the 2ms and 5ms long DRX cycle values can provide useful HARQ program retention patterns for time-sharing duplex (TDD). Generally speaking, HARQ can be used to ensure that data is reliably sent from one node to another. HARQ use stops and waits for agreement. A transmitting entity (such as an LTE transceiver) transmits data blocks to a receiving entity (such as an eNB). The transmitting entity stops and waits until it receives an acknowledgement (ACK) or a negative acknowledgement (NACK) from the receiving entity. If the sending entity receives the ACK, it sends the next data block. If the transmitting entity receives a NACK, it can retransmit the same data block. Regardless of receiving ACK or NACK, the transmitting entity schedules and processes the next to be transmitted within a specific period of time. Data blocks. In LTE, the N procedure can be used to stop and wait, where the transmitting entity stops and waits for a specific HARQ procedure. For example, the transmission can stop and wait for a specific HARQ procedure. However, there are multiple HARQ procedures, so from the perspective of the transmitter, it will not stop its transmission.

Generally speaking, LTE uses multiple HARQ parallel procedures shifted in time. Since each program transmits a block of data, when the next transmission configuration arrives, the transmitting entity will have received an ACK or NACK from the receiving entity, and therefore generate the next data block to be transmitted or to be retransmitted. Therefore, from the perspective of the sending entity, data will be continuously sent to the receiving entity. In TDD, a configurable number of HARQ procedures are supported.

By applying 2ms and 5ms long DRX cycle values to LTE and Bluetooth plots, 2ms and 5ms patterns are created. These 2ms and 5ms patterns can be regarded as HARQ compatible patterns. A pattern if: (1) each LTE DL subframe enabled for DL or UL HARQ procedures is associated with at least one LTE UL subframe; and (2) each enabled for DL or UL HARQ procedures One LTE UL subframe is associated with at least one LTE DL subframe; and (3) At least one LTE DL HARQ procedure and one UL HARQ procedure are enabled, which is compatible with HARQ. In TDD configuration 2, there are 192 HARQ compatible patterns and 51 HARQ compatible patterns that are supported when DRX is applied to LTE and Bluetooth scenarios. Therefore, the proportion of HARQ compatible models supported when DRX is applied to LTE and Bluetooth scenarios is 27%. In addition, the 2ms and 5ms long DRX cycle values support additional HARQ bitmap patterns. If not using 2ms and 5ms long DRX cycle value, the HARQ bit pattern will use a smaller number of LTE sub-frames. In other words, the bitmap will include an extra "0" indicating that a particular subframe cannot be used.

Provide at least one HARQ process reserve pattern to ensure that each radio transceiver of the UE will not transmit/receive information while a different radio transceiver of the UE is receiving/transmitting information. Therefore, the coexistence interference between multiple radio transceivers in the UE can be reduced. In addition, each radio transceiver may include a different radio access technology (RAT). Examples of RATs include 3GPP LTE, WiMAX, Bluetooth, WLAN, GNSS, and so on.

FIG. 3C is a timing diagram 330 showing the LTE transmission/reception pattern and the Bluetooth transmission/reception pattern according to an example. The LTE Rx model and the LTE Tx model are the same. Each ON and OFF cycle lasts 2ms. Therefore, the bitmap of LTE Rx and LTE Tx is 11001100. Each number indicates whether LTE is ON (such as "1") or 0FF (such as "0") in a one-second period. Therefore, "11" indicates an ON period of two seconds, and "00" indicates an OFF period of two seconds. As shown in the timing diagram 330, there is no interference between LTE transmission and Bluetooth reception. In other words, while LTE is transmitting (that is, LTE Tx ON), Bluetooth does not receive. Similarly, while Bluetooth is receiving (ie, BT Rx ON), LTE does not transmit. Although there is some overlap between LTE reception and Bluetooth transmission, there is generally no interference caused by overlap. It is assumed that Bluetooth transmission will not interfere with LTE reception, because the LTE downlink frequency band does not overlap with the Bluetooth transmission frequency band.

Timing diagram 330 is about operating in Frequency Division Duplex (FDD) LTE. In FDD, different frequency bands are used on the transmission side and the reception side. Since FDD uses different frequency bands to send and receive information, the sending and receiving data signals will not interfere with each other.

The sequence diagram 330 is a bitmap-based TDM solution for the coexistence between LTE and Bluetooth. A bitmap with 8ms (such as 11001100) can ensure that LTE will not transmit information substantially at the same time when Bluetooth is receiving information. Therefore, having a long DRX cycle of 8ms (which corresponds to a bitmap of 8ms) can be useful for LTE FDD. In some examples, having a long DRX cycle of 4ms may be useful for LTE FDD, but unlike the long DRX cycle of 8ms, the long DRX cycle of 4ms is not utilized in the HARQ program retention pattern in LTE FDD. In other words, several LTE FDDHARQ procedures can be shielded to cope with the coexistence between LTE and Bluetooth. For FDD, there are 8 HARQ programs on the uplink, and the downlink can have up to 8 HARQ programs. The downlink HARQ program can be transmitted in any order without a fixed timing, and each uplink HARQ program is assigned to a specific sub-frame. The UE transmits every eight sub-frames in the same HARQ procedure. Therefore, the 8ms long DRX cycle is useful for reducing the coexistence interference between LTE and Bluetooth, because the 8ms long DRX cycle corresponds to 8 uplink and downlink HARQ procedures in FDD.

Figure 4 shows an example of ASN.1 code based on an example of DRX configuration information. Abstract Syntax Notation 1 (ASN.1) can be used to implement enhancements to the existing DRX configuration. DRX-Config-r11 (ie, DRX configuration 11) is used to define various characteristics of the DRX cycle. The existing DRX-Config-r11 includes ASN.1 codes to define onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimer, longDRX-CycleStartOffset, shortDRX-cycle, and drxShortCycleTimer. Currently, longDRX-CycleStartOffset includes cycle values of sf10, sf20, sf32, sf40, etc. By adding the cycle values of sf2, sf5, and sf8 to the ASN.1 code, the addition of the 2ms, 5ms, and 8ms long DRX cycle values can be included in DRX-Config-r11. Since the existing DRX-Config-r11 does not allow expansion, the new DRX-Config-r11 can be configured with 2ms, 5ms, and 8ms long DRX cycle values to provide additional DRX types that can be used to reduce interference in devices in multiple radio devices Like, as discussed in the previous paragraph.

Figure 5 shows a sub-frame used to receive the downlink reference resource 510 during a long DRX cycle according to an example. The downlink reference resource 510 may include a reference signal (RS) transmitted from the eNB. The measured power of the reference signal at the UE is used to determine the power of the eNB to transmit downlink data. The measured power of the reference signal can be transmitted to the eNB via a channel status information (CSI) report.

In wireless communication, CSI can refer to the known channel properties of a communication link. CSI describes how a signal propagates from the transmitter to the receiver. In addition, CSI can represent the combined effects of scattering, decay, and so on. CSI ensures that the transmission system is adapted to the current channel conditions, thereby leading to reliable communication with Bluetooth transceivers, LTE transceivers, and so on. The CSI is periodically transmitted from the UE to the eNB.

Generally speaking, the CSI may include at least one of a channel quality index (CQI), a precoding matrix index (PMI), and a class index (RI). CQI is information that the UE sends to the eNB to indicate the appropriate data rate for downlink transmission. CQI can be based on the received downlink signal to interference plus noise ratio (SINR) Measurements, and various known characteristics of the UE receiver. PMI is the signal fed back by the UE and corresponds to the index of the precoder, which maximizes the total number of data bits that can be received across the downlink space transport layer. The RI is sent to the eNB by the UE configured for the physical downlink shared channel (PDSCH). RI corresponds to the number of useful transport layers for spatial multiplexing (based on the UE's downlink channel estimation).

The CSI report is usually transmitted after at least four symbols of the downlink reference resource 510. In order to make the measurement of the reference signal accurate, the reference signal should be received in the downlink sub-frame with the least interference. Interference can reduce the accuracy of the reference signal measurement and impact the accuracy of the CSI report. Accordingly, it is important to select the downlink sub-frame to receive the reference signal with little interference.

Currently, the rules for selecting the chain subframes under the downlink reference resource 510 do not consider the impact of interference in the device. Therefore, when there is interference in the device (for example, the Bluetooth transceiver and the LTE transceiver are receiving the reference signal and transmitting information at the same time), the measurement of the reference signal received in the symbol of the downlink reference resource 510 may be negatively impacted.

As shown in Figure 5, the long DRX cycle of the LTE (or WWAN) transceiver can be divided into a scheduled period and a non-scheduled period. When transitioning from the LTE unscheduled period to the LTE scheduled period, the UE can be configured to send CSI (such as CQI, PMI, and RI) to the eNB. In other words, the LTE transceiver in the UE can be configured to transmit CSI to the eNB. The CSI may be based on the reference signal received in the downlink reference resource 510. Can be linked to the sub-frame nn_{CQI_ref}The downlink reference resource 510 (ie, time domain reference) is defined.

CSI notification sub-frame 520 occurs in the downstream sub-frame nn_{CQI_ref}To After four sub-frames are missing. In other words, the CSI is notified to the eNB periodically in the uplink subframe, and the uplink subframe occurs after at least four subframes of the downlink reference resource 510 are received from the eNB. Therefore, the CSI notification sub-frame 520 is located in the UE's transceiver (such as WWAN transceiver) after a long DRX cycle and is combined with the downlink reference resource 510 (that is, the downlink sub-frame nn_{CQI_ref})corresponding. In some examples, the link frame nn_{CQI_ref}If there are more than four sub-frames (such as six sub-frames), the CSI will be notified.

When using DRX as a TDM solution, CSI measurement requires special handling. Otherwise, the downlink reference resource 510 will be impacted by the interference in the device between the collocated transceivers in the multi-radio device, which will cause the UE to report inaccurate CSI. Inaccurate CSI may substantially reduce system throughput. In other words, the average rate of successful message delivery on a communication channel may be reduced due to inaccurate CSI. Therefore, the downlink reference resource 510 should not be impacted by interference in the device.

If you link the frame nn_{CQI_ref}If it is not disturbed by the interference in the device, download the sub-frame nn_{CQI_ref}Can be considered effective. Therefore, if the UE receives a reference signal or other type of downlink reference resource from the eNB in a downlink subframe during a period (which does not correspond to a different coexisting radio transceiver in the UE transmitting an uplink subframe), the The lower chain frame is not affected by the interference in the device. In other words, when interference exists in the device, the UE does not receive the downlink sub-frame nn from the eNB._{CQI_ref}. Therefore, the link frame nn_{CQI_ref}It is effective and can be used to receive the reference resources of the downlink.

In some examples, the eNB may download the link sub-frame nn_{CQI_ref}A different transceiver (such as a Bluetooth transceiver) assigned to the UE is transmitting information while being received by the UE in a sub-frame (such as the LTE transceiver in the UE). If you know this will happen, you can link the frame nn_{CQI_ref}The designation is invalid and cannot be used to receive reference symbols from the eNB. In other words, if the downlink sub-frame associated with the downlink reference resource 510 is disturbed by interference in the device, the downlink reference resource 510 can be identified as unusable.

In some examples, in order to reduce the chance of interference in the device in the downlink subframe, if the downlink subframe belongs to the unscheduled period of the long DRX cycle, as shown in Figure 5, the downlink subframe can be The box designation is invalid. The subframe designated as invalid will not be used by the eNB to transmit data to the UE. Therefore, if the DRX solution is used for coexistence in the device, the downlink reference resource 510 can be received in the downlink subframe that is not included in the unscheduled period of the long DRX cycle. In one embodiment, the downlink subframes included in the scheduling period of the long DRX cycle can be designated as valid subframes for the UE to receive downlink reference resources, such as RS. In addition, the sub-frames in the unscheduled period can be used by the UE to report the CSI based on the reference resource to the eNB.

In one embodiment, if: (1) the downlink sub-frame is configured for the UE downlink sub-frame; (2) the downlink sub-frame does not include the Multimedia Broadcast Single Frequency Network (MBSFN) sub-frame (except (Except transmission mode 9); (3) The downlink sub-frame does not contain the downlink boot time slot (DwPTS) field to prevent the length of DwPTS from being 7680. T_sOr fewer cases occur; (4) The downlink frame does not fall within the configured measurement gap of the UE (5) Downlink subframes, for periodic CSI reports, when the UE is configured with a CSI subframe group, it is an element of the CSI subframe group linked to the periodic CSI report; and (6) If the downlink sub-frame is not disturbed by interference in the device, the downlink sub-frame can be seen nn_{CQI_ref}Is effective. In addition, when DRX is used to reduce the coexistence in the device, if the link subframe is not part of the unscheduled period, the link subframe can be seen as nn_{CQI_ref}Is effective.

In some embodiments of the present invention, the radio link monitoring (RLM) is performed by the WWAN transceiver of the UE, and can use sub-frames that are substantially free from interference from multiple coexisting radio transceivers in the UE. The RLM function in the UE is used to monitor the quality of the radio link under the serving cell in the RRC_CONNECTED state. The RLM system is based on cell-specific reference signals. Therefore, the UE in the RRC_CONNECTED state can determine whether it is synchronized with the serving cell or not. In the case of a certain number of consecutive out-of-sync indications (referred to as "N310"), the UE can start the radio link failure timer "T310" of the network configuration. If several consecutive synchronization indications "N311" are notified by the physical layer of the UE, the timer is stopped. Both asynchronous and synchronous counters (N310 and N311) can be configured by the network. When the timer T310 expires, a radio link failure (RLF) occurs. The result is that the UE shuts down its transmitter to avoid interference and then requests to re-establish the RRC connection.

When the sub-frames impacted by interference in the device are used in RLM, the interference will cause errors in measuring cell-specific reference signals. For example, in the long During the unscheduled period of the DRX cycle, other RATs (such as WLAN, Bluetooth) can transmit information. Therefore, the Bluetooth transceiver in the UE can transmit information in substantially the same subframe as the LTE transceiver is receiving information (such as a cell-specific reference signal). If multiple errors are received, the UE can notify the radio link failure, close the WWAN transmitter, and re-establish the RRC link. This will result in less throughput and unnecessary management burden for the 3GPP network.

In some examples, the WWAN radio transceiver of the UE can be configured to receive RLM in the downlink subframe that occurs during the scheduling period of the long DRX cycle, thereby reducing the use of subframes affected by interference in the device to perform RLM Possibility. Therefore, while the UE is performing RLM, the UE does not use the sub-frames that are impacted by the interference in the device. In addition, in the unscheduled period of the long DRX cycle, the UE can determine which sub-frames are not interfered by interference in the device. The UE can perform RLM using subframes that are not interfered by interference in the device.

In another embodiment, a method 600 for reducing coexistence interference in multiple radio devices is disclosed, as shown in the flowchart in FIG. 6. The method includes the operation of receiving 610 a discontinuous reception (DRX) configuration from an enhanced NodeB (eNodeB) on a multi-radio device. The multi-radio device can be a user device with a plurality of radio transceivers. The method 600 further includes applying 620 the discontinuous reception (DRX) configuration to at least one of the plurality of radio transceivers in the multi-radio device. The DRX may include a long DRX cycle of the at least one of the plurality of radio transceivers. The method 600 further includes selecting 2 for the long DRX cycle One of milliseconds (ms), 5ms, and 8ms cycle start offset period to reduce the coexistence interference between the plurality of radio transceivers in the multi-radio device.

In one embodiment, the plurality of radio transceivers in the method 600 include a third-generation partnership project long-term evolution (3GPP LTE) radio transceiver and a Bluetooth radio transceiver.

In one embodiment, the 2ms cycle start offset period in the method 600 provides at least one HARQ reserved pattern to reduce the Bluetooth radio transceiver and communication in LTE-TDD This coexistence between LTE radio transceivers interferes. In addition, the 5ms cycle start offset period in the method 600 provides at least one HARQ reserved pattern to reduce the Bluetooth radio transceiver and the LTE radio transceiver communicating in LTE-TDD This coexistence interferes between. In addition, the 8ms cycle start offset period in the method 600 provides at least one HARQ reserved pattern to reduce the Bluetooth radio transceiver and the LTE radio transceiver communicating in LTE-FDD (LTE-FDD) This coexistence interferes between. In addition, the method 600 may include, by the UE, monitoring a physical downlink control channel (PDCCH) during the long DRX cycle.

In an embodiment, the operation of selecting one of the plurality of cycle start offset periods in the method 600 may include providing at least one HARQ program reserved pattern to ensure the plurality of radio transceivers of the UE Each of them does not transmit/receive information while a different radio transceiver of the UE is receiving/transmitting information, thereby reducing the complexity of the UE. Coexistence interference between several radio transceivers, where each radio transceiver includes a different radio access technology (RAT).

In another embodiment, a radio coexistence system 700 is disclosed. FIG. 7 shows an exemplary block diagram of the system 700. The system 700 includes a discontinuous reception (DRX) module 710, which is operable to apply DRX to a wireless wide area network (WWAN) transceiver in a user device (UE) with a plurality of coexisting radio transceivers. A channel status information (CSI) notification module 720 is configured to periodically notify the CSI in the CSI notification sub-frame from the UE to the eNB. The CSI notification sub-frame is located after the long DRX cycle of the WWAN transceiver in the UE. A reference resource sub-frame selection module 730 is configured to select the downlink reference resource sub-frame compared to the position of the CSI notification sub-frame, so that there is substantially no coexisting radio transceiver from the UE. The downlink reference resource sub-frame is received under interference in the device of the device. A radio link monitoring (RLM) module 740 is configured to perform radio link monitoring (RLM) by using sub-frames of WWAN receivers that are substantially free from interference from a plurality of coexisting radio transceivers in the UE. . The RLM can be performed on the WWAN radio transceiver of the UE during the scheduling period of the long DRX cycle. System 700 may include Bluetooth radio 702, 3GPP LTE radio 704, and a collocated radio 706. Although the DRX module, CSI notification module, reference resource subframe selection module, and RLM module are shown outside the radio in the mobile communication device, these modules can also be integrated in one or more of the radios Inside.

In an embodiment, the plurality of coexisting radio transceivers may include At least two radio access technologies (RATs), the RATs include: 3GPP LTE radio transceiver, wireless local area access network (WLAN) transceiver, Bluetooth transceiver, and global navigation satellite system (GNSS) receiver.

In an embodiment, the downlink reference resource subframe includes CSI reference resources.

In some embodiments of the present disclosure, the CSI notified to the eNB will not substantially reduce UE throughput due to interference from the devices of the plurality of coexisting radio transceivers in the UE. In addition, the CSI includes at least one of a channel quality index (CQI), a precoding matrix index (PMI), and a class index (RI).

In some embodiments, the CSI notification module 720 is further configured to notify the CSI during the transition period from the unscheduled period to the scheduled period from the UE to the eNB, wherein the unscheduled period and the The scheduling period occurs during the long DRX cycle of the 3GPP LTE radio transceiver. In addition, the CSI reporting module 720 is further configured to periodically report the CSI to the eNB in the uplink sub-frame, wherein the uplink sub-frame is at least four sub-frames after receiving the downlink reference resource sub-frame from the eNB. The frame occurs. In addition, the CSI notification module 720 is further configured to receive the downlink reference resource sub-information from the eNB during a period that does not correspond to a different coexisting radio transceiver that is transmitting uplink sub-frames in the UE. frame. In some examples, the CSI notification module 720 is further configured to receive the downlink reference resource subframe from the eNB during the scheduling period of the long DRX cycle.

In some embodiments of the present disclosure, the system 700 may include a radio link monitoring (RLM) module 740, which is configured to use 3GPP that is substantially free from interference from multiple coexisting radio transceivers in the UE. The link frame under the LTE radio transceiver comes to RLM. In addition, the RLM module 740 is further configured to perform the RLM on the 3GPP LTE radio transceiver of the UE during the scheduling period of the long DRX cycle of the DRX. The RLM module can determine that there is a subframe that has substantially no interference in the device during the unscheduled period of the long DRX cycle; and uses the subframe that has substantially no interference in the device during the unscheduled period of the long DRX cycle To fulfill RLM.

In some embodiments, the present disclosure may include at least one computer readable medium having instructions stored thereon to reduce coexistence interference in multiple radio devices. These instructions, when executed on a machine, will cause the machine to: impose a discontinuity Reception (DRX) is configured to a user device (UE) with multiple coexisting radio transceivers, where the DRX includes a long DRX cycle for the UE; for the long DRX cycle, one is selected from the start of the multiple cycles and the offset period is selected The cycle start offset period to reduce the coexistence interference between the plurality of coexisting radio transceivers in the UE; and from the UE to the eNB, during the long DRX cycle of the UE and when receiving from the eNB After the downlink reference resource sub-frame, channel status information (CSI) is notified, where the downlink reference resource sub-frame is received from the eNB in a period outside the unscheduled period of the long DRX cycle.

In an embodiment of the computer readable medium, the position of the downlink reference resource sub-frame is selected to be substantially free from the pluralities in the UE In-device interfering sub-frames in coexisting radio transceivers. In addition, the plurality of cycle start offset periods for the long DRX cycle include one of 2 milliseconds (ms), 5ms, and 8ms.

In an embodiment of the computer readable medium, the cycle start offset period is selected to provide at least one hybrid automatic repeat request (HARQ) program retention pattern to ensure that each radio transceiver of the UE is in the A different radio transceiver of the UE is receiving/transmitting information while not transmitting/receiving information, thereby reducing the coexistence interference between the plurality of radio transceivers in the UE, wherein each radio transceiver includes a different Radio access technology (RAT).

Figure 8 provides an exemplary drawing of a mobile communication device, such as a user device (UE), a mobile station (MS), a mobile wireless device, a tablet computer, a cell phone, or another type of mobile wireless device. The mobile device may include one or more antennas configured to communicate with a base station (BS), evolved node B (eNB), or other types of wireless wide area network (WWAN) access points. Although two antennas are shown, the mobile device may have between one and four or more antennas. The mobile device can be configured to communicate using at least one wireless communication standard including 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. Mobile devices use separate antennas for each wireless communication standard, or use shared antennas for multiple wireless communication standards. Mobile devices can communicate in wireless local area access networks (WLAN), wireless private area networks (WPAN), and/or wireless wide area networks (WWAN).

Figure 8 also provides audio input and output microphones that can be used for mobile devices A drawing of Kefun and one or more speakers. The display screen may be a liquid crystal display (LCD) screen, or other types of display screens, such as an organic light emitting diode (OLED) display. The display screen can be configured as a touch screen. Touching the screen can use capacitive, resistive, or another touch screen technology. Application processors and graphics processors can be coupled to internal memory to provide processing and display capabilities. The non-electrical memory port can also be used to provide data input/output options to the user. Non-electrical memory ports can also be used to expand the memory capacity of mobile devices. The keyboard can be integrated with the mobile device or connected wirelessly to the mobile device to provide additional user input. You can also use the touch screen to set up a virtual keyboard.

It should be understood that many functional units described in this specification have been marked as modules to more specifically emphasize their implementation independence. For example, the module can be implemented as a hardware circuit including a customized VLSI circuit or gate array, such as an off-the-shelf semiconductor such as a logic chip, a transistor, or other discrete components. Modules can also be implemented in programmable hardware devices, such as field programmable gate arrays, programmable array logic, programmable logic devices, or the like.

Modules can also be implemented in software for execution by various types of processors. An identified executable code module can, for example, include one or more physical or logical blocks of computer instructions, which can, for example, be organized as an object, program, or function. Nevertheless, the executable code of the identified module does not need to be physically together, but may include different instructions stored in different locations. When logically connected together, the executable code of the module is included and the module is implemented. The purpose.

Indeed, a module of executable code can be a single instruction or many instructions Commands, and can even be scattered on a number of different code segments, between different programs, and across a number of memory devices. Similarly, in this article, the calculation data can be identified and drawn in the module, and can be embodied in any suitable form and organized in any suitable type of data structure. The calculation data can be assembled into a single data group, or can be scattered in different locations, including different storage devices, and can only exist at least partially as electronic signals on the system or the network. Modules can be passive or active, including agents that can be operated to perform desired functions.

Reference to "an embodiment" throughout this specification means that a specific feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment of the present invention. Therefore, the appearances of the word "in an embodiment" in various places in this specification do not absolutely refer to the same embodiment.

As used herein, a plurality of items, structural elements, composition elements, and/or materials may be presented in a common list for convenience. However, these lists should be treated as if each member of the list was individually identified as a separate and independent member. Therefore, it cannot be regarded as the de facto equivalent of any other member of the same list based on the individual members of such a list being presented in a common group, unless otherwise indicated. In addition, various embodiments and examples of the present invention can be referred to herein, as well as alternatives for various components thereof. It can be understood that such embodiments, examples, and alternatives should not be regarded as de facto equivalents of the other, but should be regarded as separate and autonomous manifestations of the present invention.

In addition, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, various specific details are provided, such as examples of materials, fasteners, sizes, lengths, widths, shapes, etc., to provide a detailed understanding of the embodiments of the present invention. However, familiar Those skilled in the art will understand that the present invention can be implemented without one or more of the specific details, or with other methods, components, materials, etc. In other examples, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the present invention.

Although the foregoing examples illustrate the principles of the present invention in one or more specific applications, it is obvious that a person with ordinary knowledge in the art can make various modifications in the form, purpose, and details of the implementation without using it. Creative work without departing from the principles and concepts of the present invention. Accordingly, the present invention is not intended to be restrictive, except for the scope of the patent application filed below.