# US 2017/0289749 A1 · Dynamically managing a listen list of beacon aware devices

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

- Number: US 2017/0289749 A1
- Document ID: US20170289749A1
- Status: Published application
- Kind: A1
- Application number: 15/089,327
- Filed: 2016-04-01
- Published: 2017-10-05
- Earliest claimed: 2016-04-01
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: David J. Brennan; David Michael Gray; Hubert Van Hoof; Nicholas Wrem
- Web page: https://patentgrep.com/patent/US20170289749A1

## CPC

- H04W 4/023: {using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds}
- H04W 4/02: Services making use of location information
- H04W 4/30: Services specially adapted for particular environments, situations or purposes
- H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
- H04W 40/244: {using a network of reference devices, e.g. beaconing}
- H04W 64/00: Locating users or terminals {or network equipment} for network management purposes, e.g. mobility management
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The described technology provides a system and method for dynamically managing a listen list for beacon aware devices. A mobile device may be configured to listen for one or more beacon UUIDs based on a listen list. A contextual change detected by the mobile device may trigger a collection of additional contextual information and update to the listen list based on the additional contextual information. Using the described technology, the mobile device may use a limited set of beacon UUIDs to improve micro-location granularity and enhance the mobile device's resources.

## Claims

### Claim 1

A location method comprising:
storing in memory of a mobile device a listen list of one or more beacon universally unique identifiers (UUIDs) associated with an application executable on the mobile device;
monitoring wirelessly received UUIDs transmitted by one or more beacons within a wireless-reception range of the mobile device, the mobile device being configured to perform a processor-executable operation upon detection of a beacon UUID stored in the listen list, the processor-executable operation being associated with the detected beacon UUID and the application; and
updating the listen list associated with the application and stored in the memory of the mobile device with a different set of one or more beacon UUIDs, responsive to a detected change in one or more monitored user contextual parameters satisfying one or more listen list update trigger conditions.

### Claim 2 (depends on 1)

The location method of claim 1, wherein the one or more listen list update trigger conditions are based on a detected GPS location of the mobile device.

### Claim 3 (depends on 1)

The location method of claim 1, wherein the one or more listen list update trigger conditions are based on a detection of a beacon UUID.

### Claim 4 (depends on 1)

The location method of claim 1, wherein the one or more listen list update trigger conditions are based on a calendar event.

### Claim 5 (depends on 1)

The location method of claim 1, wherein updating the listen list further comprises updating the one or more listen list update trigger conditions.

### Claim 6 (depends on 1)

The location method of claim 1, wherein updating the listen list further comprises receiving the different set of one or more beacon UUIDs from a network.

### Claim 7 (depends on 1)

The location method of claim 1, wherein updating the listen list further comprises receiving the different set of one or more beacon UUIDs from the memory of the mobile device.

### Claim 8 (depends on 1)

The location method of claim 1, wherein the different set of one or more beacon UUIDs is based on one or more collected additional user contextual parameters.

### Claim 9 (depends on 8)

The location method of claim 8, wherein the one or more collected additional user contextual parameters includes at least one of a current time, a location, application policies, and a user preference.

### Claim 10 (depends on 1)

The location method of claim 1, wherein updating the listen list further comprises collecting one or more additional user contextual parameters.

### Claim 11

One or more tangible processor-readable storage media embodied with instructions for executing on one or more processors and circuits of a device a process for location, the process comprising:
storing in memory of a mobile device a listen list of one or more beacon universally unique identifiers (UUIDs);
monitoring wirelessly received UUIDs transmitted by one or more beacons within a wireless-reception range of the mobile device, the mobile device being configured to perform a processor-executable operation upon detection of a beacon UUID stored in the listen list, the processor-executable operation being associated with the detected beacon UUID; and
updating the listen list stored in the memory of the mobile device with a different set of one or more beacon UUIDs, responsive to a detected change in one or more monitored user contextual parameters satisfying one or more listen list update trigger conditions.

### Claim 12 (depends on 11)

The one or more tangible processor-readable storage media of claim 11, wherein the listen list update trigger condition is based on a detected GPS location of the mobile device.

### Claim 13 (depends on 11)

The one or more tangible processor-readable storage media of claim 11, wherein the one or more listen list update trigger conditions are based on a detection of a beacon UUID.

### Claim 14 (depends on 11)

The one or more tangible processor-readable storage media of claim 11, wherein the one or more listen list update trigger conditions are based on a calendar event.

### Claim 15 (depends on 11)

The one or more tangible processor-readable storage media of claim 11, wherein the different set of one or more beacon UUIDs is based on one or more collected additional user contextual parameters.

### Claim 16 (depends on 15)

The one or more tangible processor-readable storage media of claim 15, wherein the one or more collected additional user contextual parameters includes at least one of a current time, a location, application policies, and a user preference.

### Claim 17 (depends on 11)

The one or more tangible processor-readable storage media of claim 11, wherein updating the listen list further comprises updating the one or more listen list update trigger conditions.

### Claim 18

A system for location comprising:
one or more processors;
a memory; and
a location application stored in the memory and executable by the one or more processors, the location application is configured to:
store in the memory a listen list of one or more beacon universally unique identifiers (UUIDs) associated with the location application;
monitor wirelessly received UUIDs transmitted by one or more beacons;
perform an operation executable by the one or more processors upon detection of a beacon UUID stored in the listen list, the operation being associated with the detected beacon UUID and the location application; and
update the listen list stored in the memory with a different set of one or more beacon UUIDs, responsive to a detected change in one or more monitored user contextual parameters satisfying one or more listen list update trigger conditions.

### Claim 19 (depends on 18)

The system of claim 18, wherein the location application is further configured to update the one or more listen list update trigger conditions.

### Claim 20 (depends on 18)

The system of claim 18, wherein the location application is further configured to collect one or more additional user contextual parameters responsive to the detection of satisfaction of the one or more listen list update trigger conditions and wherein the different set of one or more beacon UUIDs is based at least on the collected one or more additional user contextual parameters.
Please add the following new claims:

### Claim 21 (depends on 1)

The method of claim 1 further comprising:
monitoring the one or more user contextual parameters to detect the satisfaction of the one or more listen list update trigger conditions by the change in the one or more user contextual parameters.

### Claim 22 (depends on 1)

The method of claim 1 further comprising:
detecting the change the one or more user contextual parameters, the one or more user contextual parameters being monitored and the change in the one or more monitored user contextual parameters satisfying a listen list update trigger condition.
