Method and system for low power mode management for complex Bluetooth devices
View Patent ↗Methods and systems for controlling a personal area network access device are disclosed herein. Aspects of the method may comprise receiving an application event associated with a particular application running on a complex Bluetooth® device that is running a plurality of simultaneous applications, and determining whether a low power mode is allowed by the particular application running on the complex Bluetooth® device. If the low power mode is allowed by the particular application running on the complex Bluetooth® device, the complex Bluetooth® device running the particular application may be configured to operate utilizing the allowed low power mode. The allowed low power mode may be switched by the complex Bluetooth® device based on the application event. An active mode may be switched from a current mode prior to switching to the allowed power mode based on the application event.
1. A method for controlling a personal area network access device, the method comprising:
receiving an application event associated with a particular application running on a Bluetooth® device that is running a plurality of simultaneous applications;
determining whether a low power mode is allowed by said particular application running on said Bluetooth® device; and
if said low power mode is allowed by said particular application running on said Bluetooth® device, configuring said Bluetooth® device running said particular application to operate utilizing said allowed low power mode.
2. The method according to claim 1 , comprising switching said Bluetooth® device to said allowed low power mode based on said application event.
3. The method according to claim 1 , comprising switching said Bluetooth® device from a current mode to an active mode prior to switching to said allowed low power mode based on said application event.
4. The method according to claim 1 , wherein said application event is received by a low power manager.
5. The method according to claim 1 , comprising communicating said application event from said particular application to a low power manager.
6. The method according to claim 1 , wherein said low power mode comprises at least one of a sniff mode indicator, a hold mode indicator, and a park mode indicator.
7. The method according to claim 1 , wherein said application event comprises at least one of a “protocol connection open” event, a “protocol connection closed” event, an “application open” event, an “application closed” event, a “SCO open” event, a “SCO closed” event, a “connection idle” event, a “connection busy” event, and a “power mode changed to active” event.
8. The method according to claim 1 , comprising selecting settings for said allowed low power mode from a table.
9. The method according to claim 8 , wherein said table comprises at least one representation of said low power mode corresponding to said particular application.
10. The method according to claim 8 , wherein said table comprises a plurality of representations of simultaneous applications, at least one representation of allowed low power mode corresponding to each of said plurality of representations of simultaneous applications, and at least one representation of event associated with each of said plurality of representations of simultaneous applications.
11. The method according to claim 10 , wherein said at least one representation of allowed low power mode is associated with a time interval which defines a period of time prior to which said allowed low power mode becomes active.
12. The method according to claim 10 , wherein said allowed low power mode is active for a particular duration.
13. The method according to claim 12 , comprising, if two or more of said plurality of simultaneous applications comprises said allowed low power mode, activating a low power mode which has smallest duration.
14. The method according to claim 1 , comprising configuring said Bluetooth® device running said particular application to operate in an alternate low power mode, if switching to said allowed low power mode fails.
15. The method according to claim 14 , comprising selecting said alternate low power mode from a table based on at least said received application event.
16. The method according to claim 15 , comprising switching to an active mode from said allowed low power mode prior to switching to said alternate low power mode.
17. A machine-readable storage having stored thereon, a computer program having at least one code section for controlling a personal area network access device, the at least one code section being executable by a machine to perform steps comprising:
receiving an application event associated with a particular application running on a Bluetooth® device that is running a plurality of simultaneous applications;
determining whether a low power mode is allowed by said particular application running on said Bluetooth® device; and
if said low power mode is allowed by said particular application running on said Bluetooth® device, configuring said Bluetooth® device running said particular application to operate utilizing said allowed low power mode.
18. The machine-readable storage according to claim 17 , comprising code for switching said Bluetooth® device to said allowed low power mode based on said application event.
19. The machine-readable storage according to claim 17 , comprising code for switching said Bluetooth® device from a current mode to an active mode prior to switching to said allowed low power mode based on said application event.
20. The machine-readable storage according to claim 17 , wherein said application event is received by a low power manager.
21. The machine-readable storage according to claim 17 , comprising code for communicating said application event from said particular application to a low power manager.
22. The machine-readable storage according to claim 17 , wherein said low power mode comprises at least one of a sniff mode indicator, a hold mode indicator, and a park mode indicator.
23. The machine-readable storage according to claim 17 , wherein said application event comprises at least one of a “protocol connection open” event, a “protocol connection closed” event, an “application open” event, an “application closed” event, a “SCO open” event, a “SCO closed” event, a “connection idle” event, a “connection busy” event, and a “power mode changed to active” event.
24. The machine-readable storage according to claim 17 , comprising code for selecting settings for said allowed low power mode from a table.
25. The machine-readable storage according to claim 24 , wherein said table comprises at least one representation of said low power mode corresponding to said particular application.
26. The machine-readable storage according to claim 24 , wherein said table comprises a plurality of representations of simultaneous applications, at least one representation of allowed low power mode corresponding to each of said plurality of representations of simultaneous applications, and at least one representation of event associated with each of said plurality of representations of simultaneous applications.
27. The machine-readable storage according to claim 26 , wherein said at least one representation of allowed low power mode is associated with a time interval which defines a period of time prior to which said allowed low power mode becomes active.
28. The machine-readable storage according to claim 26 , wherein said allowed low power mode is active for a particular duration.
29. The machine-readable storage according to claim 28 , comprising code for activating a low power mode which has smallest duration, if two or more of said plurality of simultaneous applications comprises said allowed low power mode.
30. The machine-readable storage according to claim 17 , comprising code for configuring said Bluetooth® device running said particular application to operate in an alternate low power mode, if switching to said allowed low power mode fails.
31. The machine-readable storage according to claim 30 , comprising code for selecting said alternate low power mode from a table based on at least said received application event.
32. The machine-readable storage according to claim 31 , comprising code for switching to an active mode from said allowed low power mode prior to switching to said alternate low power mode.
33. A system for controlling a personal area network access device, the system comprising:
at least one processor configured to receive an application event associated with a particular application running on a Bluetooth® device that is running a plurality of simultaneous applications;
said at least one processor configured to determine whether a low power mode is allowed by said particular application running on said Bluetooth® device; and
said at least one processor configured to configure said Bluetooth® device running said particular application to operate utilizing said allowed low power mode, if said low power mode is allowed by said particular application running on said Bluetooth® device.
34. The system according to claim 33 , wherein said at least one processor is configured to switch said Bluetooth® device to said allowed low power mode based on said application event.
35. The system according to claim 33 , wherein said at least one processor is configured to switch said Bluetooth® device to an active mode from a current mode prior to switching to said allowed low power mode based on said application event.
36. The system according to claim 33 , comprising a low power manager that is configured to receive said application event.
37. The system according to claim 33 , wherein said at least one processor is configured to communicate said application event from said particular application to a low power manager.
38. The system according to claim 33 , wherein said low power mode comprises at least one of a sniff mode indicator, a hold mode indicator, and a park mode indicator.
39. The system according to claim 33 , wherein said application event comprises at least one of a “protocol connection open” event, a “protocol connection closed” event, an “application open” event, an “application closed” event, a “SCO open” event, a “SCO closed” event, a “connection idle” event, a “connection busy” event, and a “power mode changed to active” event.
40. The system according to claim 33 , wherein said at least one processor is configured to select settings for said allowed low power mode from a table.
41. The system according to claim 40 , wherein said table comprises at least one representation of said low power mode corresponding to said particular application.
42. The system according to claim 40 , wherein said table comprises a plurality of representations of simultaneous applications, at least one representation of allowed low power mode corresponding to each of said plurality of representations of simultaneous applications, and at least one representation of event associated with each of said plurality of representations of simultaneous applications.
43. The system according to claim 42 , wherein said at least one representation of allowed low power mode is associated with a time interval which defines a period of time prior to which said allowed low power mode becomes active.
44. The system according to claim 42 , wherein said allowed low power mode is configured to be active for a particular duration.
45. The system according to claim 44 , wherein said at least one processor is configured to activate a low power mode which has smallest duration, if two or more of said plurality of simultaneous applications comprises said allowed low power mode.
46. The system according to claim 33 , wherein said at least one processor is configured to configure said Bluetooth® device running said particular application to operate in an alternate low power mode, if switching to said allowed low power mode fails.
47. The system according to claim 46 , wherein said at least one processor is configured to select said alternate low power mode from a table based on at least said received application event.
48. The system according to claim 47 , wherein said at least one processor is configured to switch to an active mode from said allowed low power mode prior to switching to said alternate low power mode.