# US 2006/0050670 A1 · Method and system for low power mode management for complex bluetooth devices

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2006/0050670 A1
- Document ID: US20060050670A1
- Status: Published application
- Kind: A1
- Application number: 11/018,973
- Filed: 2004-12-21
- Published: 2006-03-09
- Earliest claimed: 2004-09-07
- Assignees: Broadcom Corporation
- Inventors: Jason Hillyard; Jaku Jose
- Web page: https://patentgrep.com/patent/US20060050670A1

## CPC

- H04W 52/0222: {in packet switched networks}
- H04M 1/72403: with means for local support of applications that increase the functionality
- H04W 52/0251: {using monitoring of local events, e.g. events related to user activity}
- H04W 52/288: {taking into account the usage mode, e.g. hands-free, data transmission or telephone}
- H04W 84/18: Self-organising networks, e.g. ad-hoc networks or sensor networks
- Y02D 30/70: in wireless communication networks
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

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.

## Claims

### Claim 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 complex 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 complex Bluetooth® device; and
if said low power mode is allowed by said particular application running on said complex Bluetooth® device, configuring said complex Bluetooth®D device running said particular application to operate utilizing said allowed low power mode.

### Claim 2 (depends on 1)

The method according to claim 1, further comprising switching said complex Bluetooth® device to said allowed low power mode based on said application event.

### Claim 3 (depends on 1)

The method according to claim 1, further comprising switching said complex Bluetooth® device from a current mode to an active mode prior to switching to said allowed power mode based on said application event.

### Claim 4 (depends on 1)

The method according to claim 1, wherein said application event is received by a low power manager.

### Claim 5 (depends on 1)

The method according to claim 1, further comprising communicating said application event from said particular application to a low power manager.

### Claim 6 (depends on 1)

The method according to claim 1, wherein said at least one low power mode comprises at least one of a sniff mode indicator, a hold mode indicator, and a park mode indicator.

### Claim 7 (depends on 1)

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.

### Claim 8 (depends on 1)

The method according to claim 1, further comprising selecting settings for said allowed low power mode from a table.

### Claim 9 (depends on 8)

The method according to claim 8, wherein said table comprises at least one representation of said low power mode corresponding to said particular application.

### Claim 10 (depends on 8)

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.

### Claim 11 (depends on 1)

The method according to claim 1, further comprising configuring said complex Bluetooth® device running said particular application to operate in an alternate low power mode, if switching to said allowed low power mode fails.

### Claim 12 (depends on 11)

The method according to claim 11, further comprising selecting said alternate low power mode from a table based on at least said received application event.

### Claim 13 (depends on 12)

The method according to claim 12, further comprising switching to an active mode from said allowed low power mode prior to switching to said alternate low power mode.

### Claim 14 (depends on 10)

The method according to claim 10, wherein said at least one allowed low power mode is associated with a time interval which defines a period of time prior to which said allowed mode becomes active.

### Claim 15 (depends on 10)

The method according to claim 10, wherein said allowed mode is active for a particular duration.

### Claim 16 (depends on 15)

The method according to claim 15, further comprising, if two or more of said plurality of simultaneous applications comprises said allowed low power mode, activating said low power mode which has smallest duration.

### Claim 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 complex 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 complex Bluetooth® device; and
if said low power mode is allowed by said particular application running on said complex Bluetooth® device, configuring said complex Bluetooth® device running said particular application to operate utilizing said allowed low power mode.

### Claim 18 (depends on 17)

The machine-readable storage according to claim 17, further comprising code for switching said complex Bluetooth® device to said allowed low power mode based on said application event.

### Claim 19 (depends on 17)

The machine-readable storage according to claim 17, further comprising code for switching said complex Bluetooth® device from a current mode to an active mode prior to switching to said allowed power mode based on said application event.

### Claim 20 (depends on 17)

The machine-readable storage according to claim 17, wherein said application event is received by a low power manager.

### Claim 21 (depends on 17)

The machine-readable storage according to claim 17, further comprising code for communicating said application event from said particular application to a low power manager.

### Claim 22 (depends on 17)

The machine-readable storage according to claim 17, wherein said at least one low power mode comprises at least one of a sniff mode indicator, a hold mode indicator, and a park mode indicator.

### Claim 23 (depends on 17)

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.

### Claim 24 (depends on 17)

The machine-readable storage according to claim 17, further comprising code for selecting settings for said allowed low power mode from a table.

### Claim 25 (depends on 24)

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.

### Claim 26 (depends on 24)

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.

### Claim 27 (depends on 17)

The machine-readable storage according to claim 17, further comprising code for configuring said complex Bluetooth® device running said particular application to operate in an alternate low power mode, if switching to said allowed low power mode fails.

### Claim 28 (depends on 27)

The machine-readable storage according to claim 27, further comprising code for selecting said alternate low power mode from a table based on at least said received application event.

### Claim 29 (depends on 28)

The machine-readable storage according to claim 28, further comprising code for switching to an active mode from said allowed low power mode prior to switching to said alternate low power mode.

### Claim 30 (depends on 26)

The machine-readable storage according to claim 26, wherein said at least one allowed low power mode is associated with a time interval which defines a period of time prior to which said allowed mode becomes active.

### Claim 31 (depends on 26)

The machine-readable storage according to claim 26, wherein said allowed mode is active for a particular duration.

### Claim 32 (depends on 31)

The machine-readable storage according to claim 31, further comprising code for activating said low power mode which has smallest duration, if two or more of said plurality of simultaneous applications comprises said allowed low power mode.

### Claim 33

A system for controlling a personal area network access device, the system comprising:
at least one processor that receives an application event associated with a particular application running on a complex Bluetooth® device that is running a plurality of simultaneous applications;
said at least one processor determines whether a low power mode is allowed by said particular application running on said complex Bluetooth® device; and
said at least one processor configures said complex 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 complex Bluetooth® device,

### Claim 34 (depends on 33)

The system according to claim 33, wherein said at least one processor switches said complex Bluetooth® device to said allowed low power mode based on said application event.

### Claim 35 (depends on 33)

The system according to claim 33, wherein said at least one processor switches said complex Bluetooth® device to an active mode from a current mode prior to switching to said allowed power mode based on said application event.

### Claim 36 (depends on 33)

The system according to claim 33, further comprising a low power manager that receives said application event.

### Claim 37 (depends on 33)

The system according to claim 33, wherein said at least one processor communicates said application event from said particular application to a low power manager.

### Claim 38 (depends on 33)

The system according to claim 33, wherein said at least one low power mode comprises at least one of a sniff mode indicator, a hold mode indicator, and a park mode indicator.

### Claim 39 (depends on 33)

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.

### Claim 40 (depends on 33)

The system according to claim 33, wherein said at least one processor selects settings for said allowed low power mode from a table.

### Claim 41 (depends on 40)

The system according to claim 40, wherein said table comprises at least one representation of said low power mode corresponding to said particular application.

### Claim 42 (depends on 40)

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.

### Claim 43 (depends on 33)

The system according to claim 33, wherein said at least one processor configures said complex Bluetooth® device running said particular application to operate in an alternate low power mode, if switching to said allowed low power mode fails.

### Claim 44 (depends on 43)

The system according to claim 43, wherein said at least one processor selects said alternate low power mode from a table based on at least said received application event.

### Claim 45 (depends on 44)

The system according to claim 44, wherein said at least one processor switches to an active mode from said allowed low power mode prior to switching to said alternate low power mode.

### Claim 46 (depends on 42)

The system according to claim 42, wherein said at least one allowed low power mode is associated with a time interval which defines a period of time prior to which said allowed mode becomes active.

### Claim 47 (depends on 42)

The system according to claim 42, wherein said allowed mode is active for a particular duration.

### Claim 48 (depends on 47)

The system according to claim 47, wherein said at least one processor activates said low power mode which has smallest duration, if two or more of said plurality of simultaneous applications comprises said allowed low power mode.
