IP Library › Granted Patent US 9,100,927
Granted Patent B2
US 9,100,927 · App. 13/919,279 · Granted Aug 4, 2015

Software feed forward strategy to avoid hand-shaking delays between software and firmware

Inventors: Narendra Varma Gottimukkala (San Diego, CA); Erdogan Dede (San Diego, CA)
Assignee: QUALCOMM Incorporated
H04W60/005G06F9/48H04W72/1215
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,100,927
App. No.
13/919,279
Granted
Aug 4, 2015
Kind
B2
Abstract

Methods for enabling a mobile device to efficiently resolve coexistence issues in a DSDA configuration by utilizing a feed forward strategy to avoid hand-shaking between software-implemented operations and firmware. The mobile device may employ a dual subscription, dual active (or “DSDA”) configuration in which two or more subscriptions may be associated with concurrently active communications, such as voice or data calls. The mobile device may be configured to predict activity associated with the concurrently active subscriptions, such as determining operations likely to be performed in a future time period. Such predicted activity information, as well as predefined actions and priority information, may be provided to a library common to both subscriptions. Firmware of the subscriptions may use the common library to detect current conflicts, such as desense, as well as actions to perform to resolve coexistence issues, such as blanking operations.

Claims (93)

1. A method for a dual-subscriber identity module (SIM), dual-active (DSDA) mobile device to efficiently resolve coexistence issues by utilizing a feed forward strategy, comprising:

initializing a coexistence manager configured to schedule at least a first subscription and a second subscription;

storing, in the coexistence manager, information provided in advance by software-implemented operations of the first subscription and the second subscription;

detecting whether a coexistence issue will exist for an activity interval within a current time period using firmware of the first subscription and the second subscription and the information provided to the coexistence manager in advance; and

scheduling operations with the firmware of the first subscription and the second subscription using the information provided to the coexistence manager in advance of when the coexistence issue will exist.

2. The method of claim 1 , wherein storing, in the coexistence manager, information provided in advance by the software-implemented operations of the first subscription and the second subscription comprises:

generating actions with the software-implemented operations of the first subscription and the second subscription;

registering the actions and information related to the first subscription and the second subscription with the coexistence manager, wherein the information related to the first subscription and the second subscription includes priority information; and

registering in advance predicted activity information for the first subscription and the second subscription for a future time period with the coexistence manager.

3. The method of claim 2 , wherein detecting whether a coexistence issue will exist for an activity interval within a current time period using firmware of the first subscription and the second subscription and the information provided to the coexistence manager in advance comprises:

determining, with the firmware associated with the first subscription and the second subscription, whether the coexistence issue exists for the activity interval within the current time period based on the registered predicted activity information.

4. The method of claim 3 , further comprising:

identifying priorities of the first subscription and the second subscription with the firmware based on registered activity information of the current time period when the coexistence issue exists; and

performing the first subscription and the second subscription with the firmware based on the identified priorities and the registered actions.

5. The method of claim 4 , wherein performing the first subscription and the second subscription with the firmware based on the identified priorities and the registered actions comprises:

identifying a subscription that has a lower priority based on the identified priorities;

performing normal operations of a subscription that has a higher priority during a first period;

performing the registered actions associated with the subscription that has the lower priority during the first period; and

performing normal operations of the subscription that has the lower priority during a second period in response to performing the registered actions during the first period.

6. The method of claim 1 , wherein the scheduled operations include at least blanking and back-off operations.

7. The method of claim 1 , wherein the coexistence issue is one of an unacceptable specific absorption rate, suboptimal battery current use, and a desense condition of either the first subscription or the second subscription.

8. The method of claim 1 , further comprising generating predicted activity information for a future time period with the software-implemented operations of the first subscription and the second subscription.

9. The method of claim 8 , wherein the future time period is from one to two milliseconds after the current time period.

10. A mobile device configured to efficiently resolve coexistence issues by utilizing a feed forward strategy, comprising:

a processor configured with processor-executable instructions to:

initialize a coexistence manager configured to schedule at least a first subscription and a second subscription;

store, in the coexistence manager, information provided in advance by software-implemented operations of the first subscription and the second subscription;

detect whether a coexistence issue will exist for an activity interval within a current time period using firmware of the first subscription and the second subscription and the information provided to the coexistence manager in advance; and

schedule operations with the firmware of the first subscription and the second subscription using the information provided to the coexistence manager in advance of when the coexistence issue will exist.

11. The mobile device of claim 10 , wherein the processor is configured with processor-executable instructions to perform operations such that storing, in the coexistence manager, information provided in advance by software-implemented operations of the first subscription and the second subscription comprises:

generating actions with the software-implemented operations of the first subscription and the second subscription;

registering the actions and information related to the first subscription and the second subscription with the coexistence manager, wherein the information related to the first subscription and the second subscription includes priority information; and

registering in advance predicted activity information for the first subscription and the second subscription for a future time period with the coexistence manager.

12. The mobile device of claim 11 , wherein the processor is configured with processor-executable instructions to perform operations such that detecting whether a coexistence issue will exist for an activity interval within a current time period using firmware of the first subscription and the second subscription and the information provided to the coexistence manager in advance comprises:

determining, with the firmware associated with the first subscription and the second subscription, whether the coexistence issue exists for the activity interval within the current time period based on the registered predicted activity information.

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

identify priorities of the first subscription and the second subscription with the firmware based on registered activity information of the current time period when the coexistence issue exists; and

perform the first subscription and the second subscription with the firmware based on the identified priorities and the registered actions.

14. The mobile device of claim 13 , wherein the processor is configured with processor-executable instructions to perform operations such that performing the first subscription and the second subscription with the firmware based on the identified priorities and the registered actions comprises:

identifying a subscription that has a lower priority based on the identified priorities;

performing normal operations of a subscription that has a higher priority during a first period;

performing the registered actions associated with the subscription that has the lower priority during the first period; and

performing normal operations of the subscription that has the lower priority during a second period in response to performing the registered actions during the first period.

15. The mobile device of claim 10 , wherein the scheduled operations include at least blanking and back-off operations.

16. The mobile device of claim 10 , wherein the coexistence issue is one of an unacceptable specific absorption rate, suboptimal battery current use, and a desense condition of either the first subscription or the second subscription.

17. The mobile device of claim 10 , wherein the processor is configured with processor-executable instructions to perform operations further comprising generating predicted activity information for a future time period with the software-implemented operations of the first subscription and the second subscription.

18. The mobile device of claim 17 , wherein the future time period is from one to two milliseconds after the current time period.

19. A mobile device configured to efficiently resolve coexistence issues by utilizing a feed forward strategy, comprising:

means for initializing a coexistence manager configured to schedule at least a first subscription and a second subscription;

means for storing, in the coexistence manager, information provided in advance by software-implemented operations of the first subscription and the second subscription;

means for detecting whether a coexistence issue will exist for an activity interval within a current time period using firmware of the first subscription and the second subscription and the information provided to the coexistence manager in advance; and

means for scheduling operations with the firmware of the first subscription and the second subscription using the information provided to the coexistence manager in advance of when the coexistence issue will exist.

20. The mobile device of claim 19 , wherein means for storing, in the coexistence manager, information provided in advance by software-implemented operations of the first subscription and the second subscription comprises:

means for generating actions with the software-implemented operations of the first subscription and the second subscription;

means for registering the actions and information related to the first subscription and the second subscription with the coexistence manager, wherein the information related to the first subscription and the second subscription includes priority information; and

means for registering in advance predicted activity information for the first subscription and the second subscription for a future time period with the coexistence manager.

21. The mobile device of claim 20 , wherein means for detecting whether a coexistence issue will exist for an activity interval within a current time period using firmware of the first subscription and the second subscription and the information provided to the coexistence manager in advance comprises:

means for determining, with the firmware associated with the first subscription and the second subscription, whether the coexistence issue exists for the activity interval within the current time period based on the registered predicted activity information.

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

means for identifying priorities of the first subscription and the second subscription with the firmware based on registered activity information of the current time period when the coexistence issue exists; and

means for performing the first subscription and the second subscription with the firmware based on the identified priorities and the registered actions.

23. The mobile device of claim 22 , wherein means for performing the first subscription and the second subscription with the firmware based on the identified priorities and the registered actions comprises:

means for identifying a subscription that has a lower priority based on the identified priorities;

means for performing normal operations of a subscription that has a higher priority during a first period;

means for performing the registered actions associated with the subscription that has the lower priority during the first period; and

means for performing normal operations of the subscription that has the lower priority during a second period in response to performing the registered actions during the first period.

24. The mobile device of claim 19 , wherein the scheduled operations include at least blanking and back-off operations.

25. The mobile device of claim 19 , wherein the coexistence issue is one of an unacceptable specific absorption rate, suboptimal battery current use, and a desense condition of either the first subscription or the second subscription.

26. The mobile device of claim 19 , further comprising means for generating predicted activity information for a future time period with the software-implemented operations of the first subscription and the second subscription.

27. The mobile device of claim 26 , wherein the future time period is from one to two milliseconds after the current time period.

28. A non-transitory processor-readable storage medium having stored thereon processor-executable software instructions configured to cause a processor to perform operations for a mobile device to efficiently resolve coexistence issues by utilizing a feed forward strategy, comprising:

initializing a coexistence manager configured to schedule at least a first subscription and a second subscription;

storing, in the coexistence manager, information provided in advance by software-implemented operations of the first subscription and the second subscription;

detecting whether a coexistence issue will exist for an activity interval within a current time period using firmware of the first subscription and the second subscription and the information provided to the coexistence manager in advance; and

scheduling operations with the firmware of the first subscription and the second subscription using the information provided to the coexistence manager in advance of when the coexistence issue will exist.

29. The non-transitory processor-readable storage medium of claim 28 , wherein the stored processor-executable software instructions are configured to cause the processor to perform operations such that storing, in the coexistence manager, information provided in advance by software-implemented operations of the first subscription and the second subscription comprises:

generating actions with the software-implemented operations of the first subscription and the second subscription;

registering the actions and information related to the first subscription and the second subscription with the coexistence manager, wherein the information related to the first subscription and the second subscription includes priority information; and

registering in advance predicted activity information for the first subscription and the second subscription for a future time period with the coexistence manager.

30. The non-transitory processor-readable storage medium of claim 29 , wherein the stored processor-executable software instructions are configured to cause the processor to perform operations such that detecting whether a coexistence issue will exist for an activity interval within a current time period using firmware of the first subscription and the second subscription and the information provided to the coexistence manager in advance comprises:

determining, with the firmware associated with the first subscription and the second subscription, whether the coexistence issue exists for the activity interval within the current time period based on the registered predicted activity information.

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

identifying priorities of the first subscription and the second subscription with the firmware based on registered activity information of the current time period when the coexistence issue exists; and

performing the first subscription and the second subscription with the firmware based on the identified priorities and the registered actions.

32. The non-transitory processor-readable storage medium of claim 31 , wherein the stored processor-executable software instructions are configured to cause the processor to perform operations such that performing the first subscription and the second subscription with the firmware based on the identified priorities and the registered actions comprises:

identifying a subscription that has a lower priority based on the identified priorities;

performing normal operations of a subscription that has a higher priority during a first period;

performing the registered actions associated with the subscription that has the lower priority during the first period; and

performing normal operations of the subscription that has the lower priority during a second period in response to performing the registered actions during the first period.

33. The non-transitory processor-readable storage medium of claim 28 , wherein the scheduled operations include at least blanking and back-off operations.

34. The non-transitory processor-readable storage medium of claim 28 , wherein the coexistence issue is one of an unacceptable specific absorption rate, suboptimal battery current use, and a desense condition of either the first subscription or the second subscription.

35. The non-transitory processor-readable storage medium of claim 28 , wherein the stored processor-executable software instructions are configured to cause the processor to perform operations further comprising generating predicted activity information for a future time period with the software-implemented operations of the first subscription and the second subscription.

36. The non-transitory processor-readable storage medium of claim 35 , wherein the future time period is from one to two milliseconds after the current time period.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 17, 2013
From: GOTTIMUKKALA, NARENDRA VARMA; DEDE, ERDOGAN
To: QUALCOMM INCORPORATED
Reel/Frame 030624/0233 →
Continuity (1)
Related Publication 20140370892A1 · Dec 18, 2014