Sharing beacons

• US 8,990,556 B1
• Filed: 08/13/2014
• Issued: 03/24/2015
• Est. Priority Date: 08/13/2014
• Status: Active Grant

• Current Assignee: Gimbal, Inc.
• Original Assignee: Gimbal, Inc.
• Inventors: Wurster, Charles S., Menendez, Jose R.
• Primary Examiner(s): HOFFMAN, BRANDON S
• Application Number:
  US14/459,138
• Time in Patent Office: 223 Days
• Field of Search: None
• US Class Current: 713/158
• CPC Class Codes: H04W 12/04 Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/35 Protecting application or service provisioning, e.g. securing SIM application provisioning

Abstract

Data is received that specifies at least one beacon associated with a first account and a first validity window specifying a time period during which the at least one beacon is to be associated with an additional account. Thereafter, a first key is generated which, when registered by a second account, causes the at least one beacon to be associated with the second account until expiration of the first validity window. Prior to registration of the first key and additionally outside the first validity window the at least one beacon is associated solely with the first account. After the registration of the first key, the at least one beacon is caused to be associated with the second account during the first validity window. Related apparatus, systems, techniques and articles are also described.

Claims

1. A method comprising:

receiving data specifying at least one beacon associated with a first account and a first validity window specifying a time period during which the at least one beacon is to be associated with an additional account;

generating a first key which, when registered by a second account, causes the at least one beacon to be associated with the second account during the first validity window;

causing the at least one beacon to be associated solely with the first account outside the first validity window; and

causing, after the registration of the first key, the at least one beacon to be associated with the second account during the first validity window.

2. The method of claim 1, wherein the at least one beacon is associated with the second account in addition to the first account during the first validity window.

3. The method of claim 1 further comprising:

receiving data revoking the first key; and

causing the at least one beacon to no longer be associated with the second account during the first validity window after the first key revocation.

4. The method of claim 1, wherein each key is a unique alphanumeric string that can only be registered once.

5. The method of claim 1 further comprising:

receiving data specifying restrictions on use of the at least one beacon, wherein the association of the at least one beacon with the second account prevents the at least one beacon to be used in contravention with the specified restrictions.

6. The method of claim 5, wherein the specified restrictions on use of the at least one beacon includes prevention of at least one of:

editing at least one beacon or deleting at least one beacon.

7. The method of claim 1 further comprising:

receiving data specifying permissible uses of the at least one beacon, wherein the association of the at least one beacon with the second account prevents the at least one beacon to be used for other than the specified permissible uses.

8. The method of claim 7, wherein the specified permissible uses of the at least one beacon comprise at least one of:

detection of each of a plurality of beacons, presenting a notification to an end-user on a client device, launching or changing a user interface on a client device, logging that the end-user was near a beacon at a certain time and dwelled nearby it for an amount of time.

9. The method of claim 1 further comprising:

receiving data specifying the at least one beacon associated with the first account and a second validity window specifying a time period during which the at least one beacon is to be associated with an additional account; and

generating a second key which, when registered by a third account, causes the at least one beacon to be associated with the third account until expiration of the second validity window.

10. The method of claim 9 further comprising:

causing, after the registration of the second key, the at least one beacon to be associated with the third account during the second validity window.

11. The method of claim 9, wherein the first validity window overlaps, at least in part, with the second validity window.

12. The method of claim 11, wherein the registration of the second key causes the first key to be revoked such that the at least one beacon is no longer associated with the second account during the first validity window and/or the overlap of the first validity window and the second validity window.

13. The method of claim 11, wherein the at least one beacon is associated with both the second account and the third account during the overlap of the first validity window and the second validity window.

14. The method of claim 13, wherein the at least one beacon is further associated with the first account during the overlap of the first validity window and the second validity window.

15. The method of claim 1 further comprising:

receiving data specifying exclusivity terms for the first key; and

wherein, after the registration of the first key, the at least one beacon is associated with the second account during the first validity window according to the exclusivity terms.

16. The method of claim 15, wherein the exclusivity terms specify complete exclusivity for the second account with the exception of the first account.

17. The method of claim 15, wherein the exclusivity terms specify partial exclusivity for the second account with the exception of the first account.

18. The method of claim 15 further comprising:

receiving data specifying exclusivity terms for a second key; and

wherein, after the registration of the second key, the first key is revoked such that the at least one beacon is no longer associated with the second account during the first validity window.

19. The method of claim 1, wherein the at least one beacon is solely associated with the first account during the first validity window until such time as the first key is registered by the second account.

20. A non-transitory computer program product storing instructions which, when executed by at least one data processor forming part of at least one computing system, result in operations comprising:

receiving data specifying at least one beacon associated with a first account and a first validity window specifying a time period during which the at least one beacon is to be associated with an additional account;

generating a first key which, when registered by a second account, causes the at least one beacon to be associated with the second account until expiration of the first validity window;

causing the at least one beacon to be associated solely with the first account outside the first validity window; and

causing, after the registration of the first key, the at least one beacon to be associated with the second account during the first validity window.

21. A system comprising:

at least one beacon;

at least one data processor; and

memory storing instructions which, when executed by the at least one data processor, result in operations comprising;

receiving data specifying at least one beacon associated with a first account and a first validity window specifying a time period during which the at least one beacon is to be associated with an additional account;

generating a first key which, when registered by a second account, causes the at least one beacon to be associated with the second account until expiration of the first validity window;

causing the at least one beacon to be associated solely with the first account prior to registration of the key and additionally outside the first validity window; and

causing, after the registration of the first key, the at least one beacon to be associated with the second account during the first validity window.

22. A method comprising:

receiving, by a beacon server, data specifying at least one beacon associated with a first account and a first validity window specifying a time period during which the at least one beacon is to be associated with an additional account;

generating, by a beacon server, a first key which, when registered by a second account via the beacon server, causes the at least one beacon to be associated with the second account during the first validity window;

causing, by the beacon server, the at least one beacon to be associated solely with the first account outside the first validity window; and

causing, by the beacon server after the registration of the first key, the at least one beacon to be associated with the second account during the first validity window;

wherein;

software on a client device detects transmissions from one beacon of the at least one beacon;

the software on the client device relays data characterizing the detected transmission to the beacon server;

the beacon server sends beacon information associated with the first account to the software on the client device if the software on the client device is associated with the first account and it is outside the first validity window;

the beacon server sends beacon information associated with the second account to the software on the client device if the software on the client device is associated with the second account and it is within the first validity window.