# US 2013/0252594 A1 · Mobile Location Identifier for Social Check-In Applications

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

- Number: US 2013/0252594 A1
- Document ID: US20130252594A1
- Status: Published application
- Kind: A1
- Application number: 13/425,791
- Filed: 2012-03-21
- Published: 2013-09-26
- Earliest claimed: 2012-03-21
- Assignees: International Business Machines Corporation
- Inventors: Anthony E. Faillaci; Matthew Charles Hillary; Jorge Rafael Nogueras; Irina Tyshkevich
- Web page: https://patentgrep.com/patent/US20130252594A1

## CPC

- H04W 4/023: {using mutual or relative location information between multiple location based services [LBS] targets or of distance thresholds}
- G06Q 10/40: Business processes related to social networking or social networking services
- G06Q 90/00: Systems or methods specially adapted for administrative, commercial, financial, managerial or supervisory purposes, not involving significant data processing
- H04W 4/21: for social networking applications
- H04W 12/08: Access security
- H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## 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

### Claim 1

A method implemented by an information handling system comprising:
receiving a geographic beacon location corresponding to a mobile entity, wherein the mobile entity is established at a social network website;
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; and
logging, at the social networking website, a check-in of the user at the entity in response to the determination being that the geographic beacon location is proximate to the geographic user location.

### Claim 2 (depends on 1)

The method of claim 1 further comprising:
prior to the logging:
retrieving a beacon access list accessible from the social network website;
determining whether the user is authorized to check into the mobile entity by comparing a user identifier corresponding to the user with a plurality of authorized user identifiers included in the beacon access list;
inhibiting the logging in response to determining that the user is unauthorized to check into the mobile entity; and
logging the check-in of the user at the entity in response to determining that the user is authorized to check into the mobile entity and in response to determining that the geographic beacon location is proximate to the geographic user location.

### Claim 3 (depends on 1)

The method of claim 1 wherein the logging further comprises:
writing the check-in to a user page of the social network website, wherein the user page corresponds to the user.

### Claim 4 (depends on 1)

The method of claim 1 wherein the logging further comprises:
writing the check-in to an page of the social network website that corresponds with the mobile entity.

### Claim 5 (depends on 1)

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.

### Claim 6 (depends on 5)

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.

### Claim 7 (depends on 1)

The method of claim 1 further comprising:
establishing the mobile entity prior to receiving the geographic beacon location, wherein the configuring comprises:
setting a user access policy that corresponds to the mobile entity;
establishing one or more mobile entity devices that each serve as geographic beacons of the mobile entity;
establishing one or more user identifiers as owners of the mobile entity; and
setting a mobile entity lifetime that applies to the mobile entity.

### Claim 8

An information handling system included in a financial services card, wherein the information handling system comprises:
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:
receiving a geographic beacon location corresponding to a mobile entity, wherein the mobile entity is established at a social network website;
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; and
logging, at the social networking website, a check-in of the user at the entity in response to the determination being that the geographic beacon location is proximate to the geographic user location.

### Claim 9 (depends on 8)

The information handling system of claim 8 wherein the actions further comprise:
prior to the logging:
retrieving a beacon access list accessible from the social network website;
determining whether the user is authorized to check into the mobile entity by comparing a user identifier corresponding to the user with a plurality of authorized user identifiers included in the beacon access list;
inhibiting the logging in response to determining that the user is unauthorized to check into the mobile entity; and
logging the check-in of the user at the entity in response to determining that the user is authorized to check into the mobile entity and in response to determining that the geographic beacon location is proximate to the geographic user location.

### Claim 10 (depends on 8)

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 network website, wherein the user page corresponds to the user.

### Claim 11 (depends on 8)

The information handling system of claim 8 wherein the logging further includes additional actions comprising:
writing the check-in to an page of the social network website that corresponds with the mobile entity.

### Claim 12 (depends on 8)

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.

### Claim 13 (depends on 12)

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.

### Claim 14 (depends on 8)

The information handling system of claim 8 wherein the actions further comprise:
establishing the mobile entity prior to receiving the geographic beacon location, wherein the configuring comprises:
setting a user access policy that corresponds to the mobile entity;
establishing one or more mobile entity devices that each serve as geographic beacons of the mobile entity;
establishing one or more user identifiers as owners of the mobile entity; and
setting a mobile entity lifetime that applies to the mobile entity.

### Claim 15

A computer program product stored in a 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:
receiving a geographic beacon location corresponding to a mobile entity, wherein the mobile entity is established at a social network website;
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; and
logging, at the social networking website, a check-in of the user at the entity in response to the determination being that the geographic beacon location is proximate to the geographic user location.

### Claim 16 (depends on 15)

The computer program product of claim 15 wherein the actions further comprise:
prior to the logging:
retrieving a beacon access list accessible from the social network website;
determining whether the user is authorized to check into the mobile entity by comparing a user identifier corresponding to the user with a plurality of authorized user identifiers included in the beacon access list;
inhibiting the logging in response to determining that the user is unauthorized to check into the mobile entity; and
logging the check-in of the user at the entity in response to determining that the user is authorized to check into the mobile entity and in response to determining that the geographic beacon location is proximate to the geographic user location.

### Claim 17 (depends on 15)

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 network website, wherein the user page corresponds to the user.

### Claim 18 (depends on 15)

The computer program product of claim 15 wherein the logging includes additional actions comprising:
writing the check-in to an page of the social network website that corresponds with the mobile entity.

### Claim 19 (depends on 15)

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.

### Claim 20 (depends on 19)

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.

### Claim 21 (depends on 15)

The computer program product of claim 15 wherein the actions further comprise:
establishing the mobile entity prior to receiving the geographic beacon location, wherein the configuring comprises:
setting a user access policy that corresponds to the mobile entity;
establishing one or more mobile entity devices that each serve as geographic beacons of the mobile entity;
establishing one or more user identifiers as owners of the mobile entity; and
setting a mobile entity lifetime that applies to the mobile entity.

### Claim 22

A method implemented by a mobile information handling system comprising:
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; and
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.

### Claim 23 (depends on 22)

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.

### Claim 24 (depends on 21)

The method of claim 21 further comprising:
determining whether the mobile user device is authorized to check-in at the mobile information handling system wherein the determining 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 comparing matching the received user identifier with one of the authorized user identifiers.

### Claim 25 (depends on 21)

The method of claim 21 further comprising:
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, wherein the sending of the check-in notification is only performed in response to the comparing matching the received user identifier with one of the authorized user identifiers.
