METHOD AND SYSTEM FOR GEOLOCATION MAPPING OF INDOOR LOCATIONS USING PAYMENT DATA

• US 20150051953A1
• Filed: 08/19/2013
• Published: 02/19/2015
• Est. Priority Date: 08/19/2013
• Status: Abandoned Application

• Current Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Original Assignee: Mastercard International Incorporated (MasterCard Incorporated)
• Inventors: HOWE, Justin X.
• Application Number:
  US13/969,839
• Publication Number:
  US 20150051953A1
• Time in Patent Office: Days
• US Class Current: 705/7.34
• CPC Class Codes: G06Q 30/0205 Location or geographical consideration

Abstract

A method for mapping merchant boundaries includes: storing, in a transaction database, a plurality of transaction data entries, wherein each transaction data entry includes data related to a payment transaction including at least a merchant identifier, a consumer identifier, and a transaction time and/or date; identifying, in the transaction database, a subset of transaction data entries, wherein each transaction data entry in the subset of transaction data entries includes a common merchant identifier; receiving, for each transaction data entry in the identified subset of transaction data entries, a geographic location of a mobile communication device associated with the respective included consumer identifier temporally proximal to the respective included transaction time and/or date; and generating, by a processing device, a boundary map for a merchant associated with the common merchant identifier based on the geographic locations received for each transaction data entry in the identified subset of transaction data entries.

Claims

1. A method for mapping merchant boundaries, comprising:

storing, in a transaction database, a plurality of transaction data entries, wherein each transaction data entry includes data related to a payment transaction including at least a merchant identifier, a consumer identifier, and a transaction time and/or date;

identifying, in the transaction database, a subset of transaction data entries, wherein each transaction data entry in the subset of transaction data entries includes a common merchant identifier;

receiving, for each transaction data entry in the identified subset of transaction data entries, a geographic location of a mobile communication device associated with the respective included consumer identifier temporally proximal to the respective included transaction time and/or date; and

generating, by a processing device, a boundary map for a merchant associated with the common merchant identifier based on the geographic locations received for each transaction data entry in the identified subset of transaction data entries.

2. The method of claim 1, further comprising:

identifying, in the transaction database, a second subset of transaction data entries, wherein each transaction data entry in the second subset of transaction data entries includes a second common merchant identifier;

receiving, for each transaction data entry in the identified second subset of transaction data entries, a geographic location of a mobile communication device associated with the respective included consumer identifier temporally proximal to the respective included transaction time and/or date; and

generating, by the processing device, a second boundary map for a merchant associated with the second common merchant identifier based on the geographic locations received for each transaction data entry in the identified second subset of transaction data entries and the generated boundary map for the merchant associated with the common merchant identifier.

3. The method of claim 2, further comprising:

generating, by the processing device, a combined boundary map based on the generated boundary map for the merchant associated with the common merchant identifier and the generated second boundary map for the merchant associated with the second common merchant identifier.

4. The method of claim 3, wherein generating the combined boundary map includes trimming overlapping boundaries for the merchant associated with the common merchant identifier and the merchant associated with the second common merchant identifier.

5. The method of claim 1, further comprising:

receiving, by the receiving device, a new transaction data entry including the common merchant identifier, a specific consumer identifier, and a specific transaction time and/or date;

receiving, by the receiving device, a new geographic location of a mobile communication device associated with the specific consumer identifier temporally proximal to the specific transaction time and/or date; and

updating, by the processing device, the generated boundary map for the merchant associated with the common merchant identifier based on the received new geographic location.

6. The method of claim 1, wherein receiving a geographic location of a mobile communication device associated with the respective included consumer identifier for each transaction data entry in the identified subset of transaction data entries further includes

receiving a plurality of geographic locations of the mobile communication device during a predetermined period of time prior to the respective included transaction time and/or date, and

generating, by the processing device, a movement path for the mobile communication device for use in the generating step.

7. The method of claim 6, wherein the predetermined period of time is based on a merchant category associated with the merchant associated with the common merchant identifier.

8. The method of claim 1, further comprising:

identifying, by the processing device, a geo-fence for the merchant associated with the common merchant identifier based on the generated boundary map.

9. The method of claim 1, wherein the received geographic location of each mobile communication device is identified using at least one of:

a global positioning system, an application program executed by the respective mobile communication device, cellular network triangulation of the respective mobile communication device, and Bluetooth, radio frequency identification, Wi-Fi, and audio location determination.

10. The method of claim 9, wherein the application program is part of an electronic wallet program.

11. The method of claim 1, wherein the geographic location is represented using latitude, longitude, and altitude.

12. The method of claim 1, wherein the generated boundary map for the merchant associated with the common merchant identifier is a three-dimensional boundary map.

13. The method of claim 1, further comprising:

associating, by the processing device, the generated boundary map for the merchant with a name of the merchant.

14. The method of claim 13, wherein the name of the merchant is included in at least one of the transaction data entries included in the subset of transaction data entries.

15. A system for mapping merchant boundaries, comprising:

a transaction database configured to store a plurality of transaction data entries, wherein each transaction data entry includes data related to a payment transaction including at least a merchant identifier, a consumer identifier, and a transaction time and/or date;

a processing device configured to identify, in the transaction database, a subset of transaction data entries, wherein each transaction data entry in the subset of transaction data entries includes a common merchant identifier; and

a receiving device configured to receive, for each transaction data entry in the identified subset of transaction data entries, a geographic location of a mobile communication device associated with the respective included consumer identifier temporally proximal to the respective included transaction time and/or date, wherein

the processing device is further configured to generate a boundary map for a merchant associated with the common merchant identifier based on the geographic locations received for each transaction data entry in the identified subset of transaction data entries.

16. The system of claim 15, wherein

the processing device is further configured to identify, in the transaction database, a second subset of transaction data entries, wherein each transaction data entry in the second subset of transaction data entries includes a second common merchant identifier,

the receiving device is further configured to receive, for each transaction data entry in the identified second subset of transaction data entries, a geographic location of a mobile communication device associated with the respective included consumer identifier temporally proximal to the respective included transaction time and/or date, and

the processing device is further configured to generate a second boundary map for a merchant associated with the second common merchant identifier based on the geographic locations received for each transaction data entry in the identified second subset of transaction data entries and the generated boundary map for the merchant associated with the common merchant identifier.

17. The system of claim 16, wherein the processing device is further configured to generate a combined boundary map based on the generated boundary map for the merchant associated with the common merchant identifier and the generated second boundary map for the merchant associated with the second common merchant identifier.

18. The system of claim 17, wherein generating the combined boundary map includes trimming overlapping boundaries for the merchant associated with the common merchant identifier and the merchant associated with the second common merchant identifier.

19. The system of claim 15, wherein

the receiving device is further configured to

receive a new transaction data entry including the common merchant identifier, a specific consumer identifier, and a specific transaction time and/or date, and

receive a new geographic location of a mobile communication device associated with the specific consumer identifier temporally proximal to the specific transaction time and/or date, and

the processing device is further configured to update the generated boundary map for the merchant associated with the common merchant identifier based on the received new geographic location.

20. The system of claim 15, wherein receiving a geographic location of a mobile communication device associated with the respective included consumer identifier for each transaction data entry in the identified subset of transaction data entries further includes

receiving a plurality of geographic locations of the mobile communication device during a predetermined period of time prior to the respective included transaction time and/or date, and

generating, by the processing device, a movement path for the mobile communication device for use in the generating step.

21. The system of claim 20, wherein the predetermined period of time is based on a merchant category associated with the merchant associated with the common merchant identifier.

22. The system of claim 15, wherein the processing device is further configured to identify a geo-fence for the merchant associated with the common merchant identifier based on the generated boundary map.

23. The system of claim 15, wherein the received geographic location of each mobile communication device is identified using at least one of:

a global positioning system, an application program executed by the respective mobile communication device, cellular network triangulation of the respective mobile communication device, and Bluetooth, radio frequency identification, Wi-Fi, and audio location determination.

24. The system of claim 23, wherein the application program is an electronic wallet program.

25. The system of claim 15, wherein the geographic location is represented using latitude, longitude, and altitude.

26. The system of claim 15, wherein the generated boundary map for the merchant associated with the common merchant identifier is a three-dimensional boundary map.

27. The system of claim 15, wherein the processing device is further configured to associate the generated boundary map for the merchant with a name of the merchant.

28. The system of claim 27, wherein the name of the merchant is included in at least one of the transaction data entries included in the subset of transaction data entries.