Mobile location identifier for social check-in applications

• US 8,774,778 B2
• Filed: 03/21/2012
• Issued: 07/08/2014
• Est. Priority Date: 03/21/2012
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Faillaci, Anthony E., Hillary, Matthew Charles, Nogueras, Jorge Rafael, Tyshkevich, Irina
• Primary Examiner(s): Obayanju, Omoniyi
• Application Number:
  US13/425,791
• Publication Number:
  US 20130252594A1
• Time in Patent Office: 839 Days
• Field of Search: 455/414.2, 455/414.1, 455/404.2, 455/457
• US Class Current: 455/414.2
• CPC Class Codes: G06Q 50/01 Social networking
• CPC Class Codes: G06Q 90/00 Systems or methods specially adapted for administrative, commercial, financial, managerial or supervisory purposes, not involving significant data processing
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 4/023 using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds
• CPC Class Codes: H04W 4/21 for social networking applications
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Abstract

An approach is provided that receives a geographic beacon location that corresponds to a mobile entity with the mobile entity being an established entity at a social network website. A geographic user location is received with the geographic user location corresponding to a mobile user device that is associated with a user of the social networking website. A determination is made as to whether the geographic beacon location is proximate to the geographic user location. A check-in of the user at the entity is logged at the social media website in response to the geographic beacon location being proximate to the geographic user location.

Claims

1. A method implemented by an information handling system comprising:

establishing a mobile entity at a social networking website, wherein the mobile entity is associated with an event having a mobile location, and wherein the establishing comprises;

setting a user access policy that corresponds to the mobile entity;

establishing one or more mobile entity devices, wherein each mobile entity device serves as a geographic beacon of the mobile entity; and

setting a mobile entity lifetime that applies to the mobile entity;

receiving a geographic beacon location corresponding to the mobile entity;

receiving a geographic user location corresponding to a mobile user device that is associated with a user of the social networking website;

determining whether the geographic beacon location is proximate to the geographic user location;

determining whether the user is authorized to check into the mobile entity, wherein the determining comprises;

sending a user identifier corresponding to the user to the social networking website; and

receiving a response from the social networking website indicating whether the user is authorized to check into the mobile entity; and

logging, at the social networking website, a check-in of the user at the mobile entity in response to the determination being that the geographic beacon location is proximate to the geographic user location and the user is authorized to check into the mobile entity.

2. The method of claim 1 wherein the determining whether the user is authorized further comprises:

retrieving a beacon access list accessible from the social networking website;

determining whether the user is authorized to check into the mobile entity by comparing the user identifier corresponding to the user with a plurality of authorized user identifiers included in the beacon access list; and

inhibiting the logging in response to determining that the user is unauthorized to check into the mobile entity.

3. The method of claim 1 wherein the logging further comprises:

writing the check-in to a user page of the social networking website, wherein the user page corresponds to the user.

4. The method of claim 1 wherein the logging further comprises:

writing the check-in to a page of the social networking website that corresponds with the mobile entity.

5. The method of claim 1 further comprising:

receiving an entity check-in request from the mobile entity, wherein the entity check-in request includes a mobile user identifier corresponding to the mobile user device, and wherein the entity check-in request is the geographic beacon location;

receiving a user check-in request from the mobile user device, wherein the user check-in request includes a mobile entity identifier corresponding to the mobile entity, and wherein the user check-in request is the geographic beacon location; and

matching the received entity check-in request with the received user check-in request, wherein the determination that the geographic beacon location is proximate to the geographic user location is based upon the matching.

6. The method of claim 5 wherein the mobile entity and the mobile user device communicate with each other using a near field communication (NFC) wireless technology.

7. The method of claim 1 wherein establishing the mobile entity further comprises:

establishing one or more user identifiers as owners of the mobile entity.

8. An information handling system comprising:

one or more processors;

a memory coupled to at least one of the processors;

a network interface that receives signals from a network; and

a set of instructions stored in the memory and executed by at least one of the processors, wherein the set of instructions perform actions of;

establishing a mobile entity at a social networking website, wherein the mobile entity is associated with an event having a mobile location, and wherein the establishing comprises;

setting a user access policy that corresponds to the mobile entity;

establishing one or more mobile entity devices, wherein each mobile entity device serves as a geographic beacon of the mobile entity; and

setting a mobile entity lifetime that applies to the mobile entity;

receiving a geographic beacon location corresponding to the mobile entity;

receiving a geographic user location corresponding to a mobile user device that is associated with a user of the social networking website;

determining whether the geographic beacon location is proximate to the geographic user location;

determining whether the user is authorized to check into the mobile entity, wherein the determining comprises;

sending a user identifier corresponding to the user to the social networking website; and

receiving a response from the social networking website indicating whether the user is authorized to check into the mobile entity; and

logging, at the social networking website, a check-in of the user at the mobile entity in response to the determination being that the geographic beacon location is proximate to the geographic user location and the user is authorized to check into the mobile entity.

9. The information handling system of claim 8 wherein the determining whether the user is authorized comprises further actions of:

retrieving a beacon access list accessible from the social networking website;

determining whether the user is authorized to check into the mobile entity by comparing the user identifier corresponding to the user with a plurality of authorized user identifiers included in the beacon access list; and

inhibiting the logging in response to determining that the user is unauthorized to check into the mobile entity.

10. The information handling system of claim 8 wherein the logging further includes additional actions comprising:

writing the check-in to a user page of the social networking website, wherein the user page corresponds to the user.

11. The information handling system of claim 8 wherein the logging further includes additional actions comprising:

writing the check-in to a page of the social networking website that corresponds with the mobile entity.

12. The information handling system of claim 8 wherein the actions further comprise:

receiving an entity check-in request from the mobile entity, wherein the entity check-in request includes a mobile user identifier corresponding to the mobile user device, and wherein the entity check-in request is the geographic beacon location;

receiving a user check-in request from the mobile user device, wherein the user check-in request includes a mobile entity identifier corresponding to the mobile entity, and wherein the user check-in request is the geographic beacon location; and

matching the received entity check-in request with the received user check-in request, wherein the determination that the geographic beacon location is proximate to the geographic user location is based upon the matching.

13. The information handling system of claim 12 wherein the mobile entity and the mobile user device communicate with each other using a near field communication (NFC) wireless technology.

14. The information handling system of claim 8 wherein establishing the mobile entity comprises further actions of:

establishing one or more user identifiers as owners of the mobile entity.

15. A computer program product stored in a non-transitory computer readable storage medium, comprising functional descriptive material that, when executed by an information handling system, causes the information handling system to perform actions comprising:

establishing a mobile entity at a social networking website, wherein the mobile entity is associated with an event having a mobile location, and wherein the establishing comprises;

setting a user access policy that corresponds to the mobile entity;

establishing one or more mobile entity devices, wherein each mobile entity device serves as a geographic beacon of the mobile entity; and

setting a mobile entity lifetime that applies to the mobile entity;

receiving a geographic beacon location corresponding to the mobile entity;

receiving a geographic user location corresponding to a mobile user device that is associated with a user of the social networking website;

determining whether the geographic beacon location is proximate to the geographic user location;

determining whether the user is authorized to check into the mobile entity, wherein the determining comprises;

sending a user identifier corresponding to the user to the social networking website; and

receiving a response from the social networking website indicating whether the user is authorized to check into the mobile entity; and

logging, at the social networking website, a check-in of the user at the mobile entity in response to the determination being that the geographic beacon location is proximate to the geographic user location and the user is authorized to check into the mobile entity.

16. The computer program product of claim 15 wherein determining whether the user is authorized comprises further actions of:

retrieving a beacon access list accessible from the social networking website;

determining whether the user is authorized to check into the mobile entity by comparing the user identifier corresponding to the user with a plurality of authorized user identifiers included in the beacon access list; and

inhibiting the logging in response to determining that the user is unauthorized to check into the mobile entity.

17. The computer program product of claim 15 wherein the logging includes additional actions comprising:

writing the check-in to a user page of the social networking website, wherein the user page corresponds to the user.

18. The computer program product of claim 15 wherein the logging includes additional actions comprising:

writing the check-in to a page of the social networking website that corresponds with the mobile entity.

19. The computer program product of claim 15 wherein the actions further comprise:

receiving an entity check-in request from the mobile entity, wherein the entity check-in request includes a mobile user identifier corresponding to the mobile user device, and wherein the entity check-in request is the geographic beacon location;

receiving a user check-in request from the mobile user device, wherein the user check-in request includes a mobile entity identifier corresponding to the mobile entity, and wherein the user check-in request is the geographic beacon location; and

matching the received entity check-in request with the received user check-in request, wherein the determination that the geographic beacon location is proximate to the geographic user location is based upon the matching.

20. The computer program product of claim 19 wherein the mobile entity and the mobile user device communicate with each other using a near field communication (NFC) wireless technology.

21. The computer program product of claim 15 wherein the actions further comprise:

establishing one or more user identifiers as owners of the mobile entity.

22. A method implemented by a mobile information handling system comprising:

establishing the mobile information handling system at a social networking website, wherein the mobile information handling system is associated with an event having a mobile location, and wherein the establishing comprises;

setting a user access policy that corresponds to the mobile information handling system;

establishing one or more mobile entity devices, wherein each mobile entity device serves as a geographic beacon of the mobile information handling system; and

setting a mobile entity lifetime that applies to the mobile information handling system;

receiving a check-in request from a mobile user device, wherein the check-in request includes a user identifier corresponding to the mobile user device;

determining whether the mobile user device is authorized to check-in at the mobile information handling system wherein the determining comprises;

sending an authorization request to the social media website; and

receiving an authorization response back from the social media website that indicates whether the received user identifier is allowed to check-in at the mobile information handling system

in response to determining that the mobile user device is authorized to check-in, sending a check-in notification from the mobile information handling system to a social media website, wherein the check-in notification includes the user identifier and a mobile entity identifier corresponding to the mobile information handling system.

23. The method of claim 22 wherein the check-in request is received from the mobile user device using a near field communication (NFC) wireless technology.

24. The method of claim 22 wherein determining whether the mobile user device is authorized to check-in further comprises:

comparing the received user identifier with a plurality of authorized user identifiers, wherein the sending of the check-in notification is only performed in response to the received user identifier matching one of the authorized user identifiers.