Method and device for implementing radio frequency coexistence management strategy in wireless devices

• US 9,172,414 B2
• Filed: 09/11/2013
• Issued: 10/27/2015
• Est. Priority Date: 01/31/2013
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Li, Wenjun, Lou, Huang, McCloud, Michael L., Mahajan, Amit, Sun, Jing, Ngai, Francis M., Hu, Jun, Akula, Prashanth, Jootar, Jittra, Dede, Erdogan, Gottimukkala, Narendra Varma, Chizgi, Nate, Makh, Vansh Pal Singh, Huang, Tsai-Chen, Li, Yingbo
• Primary Examiner(s): VO, NGUYEN THANH
• Application Number:
  US14/023,569
• Publication Number:
  US 20140213210A1
• Time in Patent Office: 776 Days
• Field of Search: 455/63.1, 455/63.3, 455/78, 455/114.2, 455/296, 455/311, 455/278.1
• US Class Current: 1/1
• CPC Class Codes: H04B 1/1027 assessing signal quality or detecting noise/interference for the received signal
• CPC Class Codes: H04B 1/12 Neutralising, balancing, or compensation arrangements
• CPC Class Codes: H04B 1/525 with means for reducing leakage of transmitter signal into the receiver
• CPC Class Codes: H04B 15/04 the interference being caused by substantially sinusoidal oscillations, e.g. in a receiver or in a tape-recorder
• CPC Class Codes: H04W 16/14 Spectrum sharing arrangements between different networks
• CPC Class Codes: H04W 88/06 adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Abstract

The various embodiments include a dual-SIM-dual-active (DSDA) device and methods for implementing robust receive (Rx) processing to resolve radio frequency coexistence interference between two subscriptions operating on the DSDA device. The DSDA device may detect when a subscription (the “aggressor”) de-senses the other subscription (the “victim”) as a result of the aggressor'"'"'s transmissions, and in response, implement robust Rx processing to mitigate the effects of de-sense on the victim while causing minimal impact to the aggressor.

Claims

1. A method for implementing a radio frequency (RF) co-existence management strategy on a wireless device between an aggressor communication activity (“

aggressor”

) and a victim communication activity (“

victim”

), comprising;

determining whether an RF interference event is detected;

creating an RF co-existence management strategy in response to determining that the RF interference event is detected;

determining whether to implement robust receive (Rx) processing as part of the RF co-existence management strategy;

configuring the victim for implementation of the robust Rx processing in response to determining to implement the robust Rx processing, comprising;

determining whether de-sense is persistent by determining whether a number of aggressor hopping frequencies that result in de-sense exceeds a minimum percentage; and

implementing the robust Rx processing on the victim in response to determining to implement the robust Rx processing as part of the RF co-existence management strategy.

2. The method of claim 1, further comprising:

determining whether the RF interference event is persisting;

returning the victim to normal operations in response to determining that the RF interference event is not persisting; and

continuing to implement the RF co-existence management strategy in response to determining that the RF interference event is persisting.

3. The method of claim 1, wherein determining whether the RF interference event is detected comprises:

monitoring one or more sources of interference;

calculating a total amount of interference power based on one or more sources of interference;

determining whether the total amount of interference power exceeds a de-sense threshold; and

determining that the RF interference event is detected when the total amount of interference power exceeds the de-sense threshold.

4. The method of claim 1, wherein creating the RF co-existence management strategy in response to determining that the RF interference event is detected comprises:

determining whether implementing the robust Rx processing would reduce a downlink channel power or improve throughput; and

determining to implement the robust Rx processing in response to determining that implementing robust Rx processing would reduce the downlink channel power or improve throughput.

5. The method of claim 1, further comprising performing the following in response to determining that the de-sense is persistent:

reducing an uplink capacity of the aggressor for every frame; and

configuring a downlink of the victim to invoke the robust Rx processing during each instance of an uplink transmission of the aggressor that results in a de-sense scenario.

6. The method of claim 1, further comprising performing the following in response to determining that the de-sense is not persistent:

revoking an uplink slot restriction of the aggressor when the aggressor is currently restricted;

reducing uplink capacity of the aggressor in each frame affected by RF coexistence; and

configuring the victim to invoke the robust Rx Processing only during an uplink transmission of the aggressor that result in a de-sense scenario.

7. The method of claim 1, wherein implementing the robust Rx processing comprises at least one of:

implementing a sample nulling strategy;

freezing loops and filters of the victim; and

maintaining a power control of the victim.

8. The method of claim 7, further comprising:

determining a transmission schedule of the aggressor; and

configuring the victim to receive signals when the aggressor is not transmitting.

9. The method of claim 7, further comprising:

determining a duration of a robust Rx processing period;

determining whether the robust Rx processing period has expired; and

configuring the victim to receive normally when the robust Rx processing period has expired.

10. The method of claim 7, wherein freezing loops and filters of the victim comprises freezing one or more of a low-noise amplifier, an automatic gain control, a pilot filter, a received signal strength indication, noise power, a time-tracking loop, a frequency-tracking loop, channel estimation, covariance, and carrier-to-interference estimation.

11. A wireless device, comprising:

a plurality of radio frequency (RF) resources; and

a processor coupled to the plurality of RF resources, wherein the processor is configured with processor-executable instructions to;

determine whether an RF interference event between an aggressor communication activity (“

aggressor”

) and a victim communication activity (“

victim”

) is detected;

create an RF co-existence management strategy in response to determining that the RF interference event is detected;

determine whether to implement robust receive (Rx) processing as part of the RF co-existence management strategy;

configure the victim for implementation of the robust Rx processing in response to determining to implement the robust Rx processing by;

determining whether de-sense is persistent by determining whether a number of aggressor hopping frequencies that result in de-sense exceeds a minimum percentage; and

implement robust Rx processing on the victim in response to determining to implement the robust Rx processing as part of the RF co-existence management strategy.

12. The wireless device of claim 11, wherein the processor is further configured with processor-executable instructions to:

determine whether the RF interference event is persisting;

return the victim to normal operations in response to determining that the RF interference event is not persisting; and

continue to implement the RF co-existence management strategy in response to determining that the RF interference event is persisting.

13. The wireless device of claim 11, wherein the processor is configured with processor-executable instructions to determine whether the RF interference event is detected by:

monitoring one or more sources of interference;

calculating a total amount of interference power based on one or more sources of interference;

determining whether the total amount of interference power exceeds a de-sense threshold; and

determining that the RF interference event is detected when the total amount of interference power exceeds the de-sense threshold.

14. The wireless device of claim 11, wherein the processor is configured with processor-executable instructions to create the RF co-existence management strategy in response to determining that the RF interference event is detected by:

determining whether implementing the robust Rx processing would reduce a downlink channel power or improve throughput; and

determining to implement the robust Rx processing in response to determining that implementing robust Rx processing would reduce the downlink channel power or improve throughput.

15. The wireless device of claim 11, wherein the processor is configured with processor-executable instructions to perform the following in response to determining that the de-sense is persistent:

reducing an uplink capacity of the aggressor for every frame; and

configuring a downlink of the victim to invoke the robust Rx processing during each instance of an uplink transmission of the aggressor that results in a de-sense scenario.

16. The wireless device of claim 11, wherein the processor is configured with processor-executable instructions to perform the following in response to determining that the de-sense is not persistent:

revoking an uplink slot restriction of the aggressor when the aggressor is currently restricted;

reducing uplink capacity of the aggressor in each frame affected by RF coexistence; and

configuring the victim to invoke the robust Rx Processing only during an uplink transmission of the aggressor that result in a de-sense scenario.

17. The wireless device of claim 11, wherein the processor is configured with processor-executable instructions to perform operations such that implementing the robust Rx processing comprises at least one of:

implementing a sample nulling strategy;

freezing loops and filters of the victim; and

maintaining a power control of the victim.

18. The wireless device of claim 17, wherein the processor is further configured with processor-executable instructions to:

determine a transmission schedule of the aggressor; and

configure the victim to receive signals when the aggressor is not transmitting.

19. The wireless device of claim 17, wherein the processor is further configured with processor-executable instructions to:

determine a duration of a robust Rx processing period;

determine whether the robust Rx processing period has expired; and

configure the victim to receive normally when the robust Rx processing period has expired.

20. The wireless device of claim 17, wherein the processor is configured with processor-executable instructions to freeze loops and filters of the victim comprises freezing one or more of a low-noise amplifier, an automatic gain control, a pilot filter, a received signal strength indication, noise power, a time-tracking loop, a frequency-tracking loop, channel estimation, covariance, and carrier-to-interference estimation.

21. A wireless device, comprising:

means for determining whether a radio frequency (RF) interference event between an aggressor communication activity (“

aggressor”

) and a victim communication activity (“

victim”

) is detected;

means for creating an RF co-existence management strategy in response to determining that the RF interference event is detected;

means for determining whether to implement robust receive (Rx) processing as part of the RF co-existence management strategy;

means for configuring the victim for implementation of the robust Rx processing in response to determining to implement the robust Rx processing, comprising;

means for determining whether de-sense is persistent further comprising means for determining whether a number of aggressor hopping frequencies that result in de-sense exceeds a minimum percentage; and

means for implementing the robust Rx processing on the victim in response to determining to implement the robust Rx processing as part of the RF co-existence management strategy.

22. The wireless device of claim 21, further comprising:

means for determining whether the RF interference event is persisting;

means for returning the victim to normal operations in response to determining that the RF interference event is not persisting; and

means for continuing to implement the RF co-existence management strategy in response to determining that the RF interference event is persisting.

23. The wireless device of claim 21, wherein means for determining whether the RF interference event is detected comprises:

means for monitoring one or more sources of interference;

means for calculating a total amount of interference power based on one or more sources of interference;

means for determining whether the total amount of interference power exceeds a de-sense threshold; and

means for determining that the RF interference event is detected when the total amount of interference power exceeds the de-sense threshold.

24. The wireless device of claim 21, wherein means for creating the RF co-existence management strategy in response to determining that the RF interference event is detected comprises:

means for determining whether implementing the robust Rx processing would reduce a downlink channel power or improve throughput; and

means for determining to implement the robust Rx processing in response to determining that implementing robust Rx processing would reduce the downlink channel power or improve throughput.

25. The wireless device of claim 21, further comprising means for performing the following in response to determining that the de-sense is persistent:

reducing an uplink capacity of the aggressor for every frame; and

configuring a downlink of the victim to invoke the robust Rx processing during each instance of an uplink transmission of the aggressor that results in a de-sense scenario.

26. The wireless device of claim 21, further comprising means for performing the following in response to determining that the de-sense is not persistent:

revoking an uplink slot restriction of the aggressor when the aggressor is currently restricted;

reducing uplink capacity of the aggressor in each frame affected by RF coexistence; and

configuring the victim to invoke the robust Rx Processing only during an uplink transmission of the aggressor that result in a de-sense scenario.

27. The wireless device of claim 21, wherein means for implementing the robust Rx processing comprises at least one of:

means for implementing a sample nulling strategy;

means for freezing loops and filters of the victim; and

means for maintaining a power control of the victim.

28. The wireless device of claim 27, further comprising:

means for determining a transmission schedule of the aggressor; and

means for configuring the victim to receive signals when the aggressor is not transmitting.

29. The wireless device of claim 27, further comprising:

means for determining a duration of a robust Rx processing period;

means for determining whether the robust Rx processing period has expired; and

means for configuring the victim to receive normally when the robust Rx processing period has expired.

30. The wireless device of claim 27, wherein means for freezing loops and filters of the victim comprises means for freezing one or more of a low-noise amplifier, an automatic gain control, a pilot filter, a received signal strength indication, noise power, a time-tracking loop, a frequency-tracking loop, channel estimation, covariance, and carrier-to-interference estimation.

31. A non-transitory processor-readable storage medium having stored thereon processor-executable software instructions configured to cause a processor of a wireless device to perform operations comprising:

determining whether a radio frequency (RF) interference event between an aggressor communication activity (“

aggressor”

) and a victim communication activity (“

victim”

) is detected;

creating an RF co-existence management strategy in response to determining that the RF interference event is detected;

determining whether to implement robust receive (Rx) processing as part of the RF co-existence management strategy;

configuring the victim for implementation of the robust Rx processing in response to determining to implement the robust Rx processing, comprising;

determining whether de-sense is persistent by determining whether a number of aggressor hopping frequencies that result in de-sense exceeds a minimum percentage; and

implementing robust Rx processing on the victim in response to determining to implement the robust Rx processing as part of the RF co-existence management strategy.

32. The non-transitory processor-readable storage medium of claim 31, wherein the stored processor-executable software instructions are configured to cause a processor of a wireless device to perform operations further comprising:

determining whether the RF interference event is persisting;

returning the victim to normal operations in response to determining that the RF interference event is not persisting; and

continuing to implement the RF co-existence management strategy in response to determining that the RF interference event is persisting.

33. The non-transitory processor-readable storage medium of claim 31, wherein the stored processor-executable software instructions are configured to cause a processor of a wireless device to perform operations such that determining whether the RF interference event is detected comprises:

monitoring one or more sources of interference;

calculating a total amount of interference power based on one or more sources of interference;

determining whether the total amount of interference power exceeds a de-sense threshold; and

determining that the RF interference event is detected when the total amount of interference power exceeds the de-sense threshold.

34. The non-transitory processor-readable storage medium of claim 31, wherein the stored processor-executable software instructions are configured to cause a processor of a wireless device to perform operations such that creating the RF co-existence management strategy in response to determining that the RF interference event is detected comprises:

determining whether implementing the robust Rx processing would reduce a downlink channel power or improve throughput; and

determining to implement the robust Rx processing in response to determining that implementing robust Rx processing would reduce the downlink channel power or improve throughput.

35. The non-transitory processor-readable storage medium of claim 31, wherein the stored processor-executable software instructions are configured to cause a processor of a wireless device to perform operations further comprising performing the following in response to determining that the de-sense is persistent:

reducing an uplink capacity of the aggressor for every frame; and

configuring a downlink of the victim to invoke the robust Rx processing during each instance of an uplink transmission of the aggressor that results in a de-sense scenario.

36. The non-transitory processor-readable storage medium of claim 31, wherein the stored processor-executable software instructions are configured to cause a processor of a wireless device to perform operations further comprising performing the following in response to determining that the de-sense is not persistent:

revoking an uplink slot restriction of the aggressor when the aggressor is currently restricted;

reducing uplink capacity of the aggressor in each frame affected by RF coexistence; and

configuring the victim to invoke the robust Rx Processing only during an uplink transmission of the aggressor that result in a de-sense scenario.

37. The non-transitory processor-readable storage medium of claim 31, wherein the stored processor-executable software instructions are configured to cause a processor of a wireless device to perform operations such that implementing the robust Rx processing comprises at least one of:

implementing a sample nulling strategy;

freezing loops and filters of the victim; and

maintaining a power control of the victim.

38. The non-transitory processor-readable storage medium of claim 37, wherein the stored processor-executable software instructions are configured to cause a processor of a wireless device to perform operations further comprising:

determining a transmission schedule of the aggressor; and

configuring the victim to receive signals when the aggressor is not transmitting.

39. The non-transitory processor-readable storage medium of claim 37, wherein the stored processor-executable software instructions are configured to cause a processor of a wireless device to perform operations further comprising:

determining a duration of a robust Rx processing period;

determining whether the robust Rx processing period has expired; and

configuring the victim to receive normally when the robust Rx processing period has expired.

40. The non-transitory processor-readable storage medium of claim 37, wherein the stored processor-executable software instructions are configured to cause a processor of a wireless device to perform operations such that freezing loops and filters of the victim comprises freezing one or more of a low-noise amplifier, an automatic gain control, a pilot filter, a received signal strength indication, noise power, a time-tracking loop, a frequency-tracking loop, channel estimation, covariance, and carrier-to-interference estimation.