Patent Application
20080147546
1. Field of the Invention
This invention relates to electronic wallet transactions using a wireless device. In particular, it relates to the use of a mobile phone for payment in an electronic wallet transaction.
2. Background of Related Art
Marketers are always trying to reach customers in new and innovative ways. To this end, certain technologies are emerging to allow not only targeted marketing and advertising to consumers based on their location, but also to allow wireless phone users to pay for goods and services using their cell phone.
An electronic wallet is typically defined as an encrypted storage medium holding credit card, phone account number, or other financial information that can be used to complete electronic transactions without re-entering the stored data at the time of the transaction. Other electronic wallets are applications that run on a personal computer to enable a consumer to securely and conveniently access information, make payments, receive and manage bills, bank, and conduct other forms of commerce.
In general, a wireless phone electronic wallet application allows a user to make a payment electronically rather than using cash, taking yet another step toward a cashless society.
Unfortunately, along with technological advances and convenience comes additional opportunities for fraud. To provide a layer of security to electronic wallet applications, communications are typically performed via secure channels.
Nevertheless, fraud opportunities exist for the persistent.
There is a need for additional security features in electronic wallet transactions.
In accordance with the principles of the present invention, a method and apparatus for providing a validation service for electronic wallet transactions comprises receiving a request to validate a given electronic wallet transaction between a wireless device and a merchant. A current position of the wireless device is obtained. The current position of the wireless device is compared to an expected location or region relating to the merchant. A validation response to the request is returned, the validation response relating to validation of the given electronic wallet transaction, if the comparison results in an appropriate match.
A method and apparatus for initiating a validated electronic wallet transaction from a wireless device in accordance with another aspect of the invention comprises establishing a session with a merchant to accomplish an electronic wallet transaction. A current location of the wireless device is provided from the wireless device in coordination with a validation request relating to the electronic wallet transaction. The validated electronic wallet transaction is accepted.
A method and apparatus for obtaining location-based validation of a given electronic wallet transaction in accordance with yet another aspect of the invention comprises establishing a session with a wireless customer relating to an electronic wallet transaction. Location-based validation of the electronic wallet transaction is requested based on a current location of the wireless customer. Location-based validation of the electronic wallet transaction is received. The electronic wallet transaction is accepted and completed based on the receipt of the location-based validation.
Features and advantages of the present invention will become apparent to those skilled in the art from the following description with reference to the drawings, in which:
In accordance with the principles of the present invention, a wireless phone electronic wallet transaction is associated with a current location of the wireless device at the time of the transaction. The current location is compared to an entry in a database of associated merchants accepting electronic wallet transactions to the locations that they handle such transactions. If a match in location is found, the wireless phone electronic wallet transaction may be validated. If the wireless phone conducting the electronic wallet transaction is not at an expected or acceptable location at the time of the transaction, then the transaction may be flagged for possible fraudulent activity.
The invention is best implemented with a network that accepts a location based service (LBS) triggered by an event at the wireless device, in this case a commercial transaction using the wireless device.
There are multiple methods for determining precise location (e.g., assisted GPS (AGPS), Time Difference of Arrival (TDOA), etc.), some of which are network centric and some of which are device centric. The recent trend in wireless devices has been driving more and more processing power into the device. This trend has been driven by a combination of Moore's Law and the desire to continue to offer more sophisticated applications to the wireless end user. The inventor herein has appreciated that the end result will be that the device is more active and in some cases the primary engine to calculate its own precise location; it is more likely to be the source or retainer of this location information; and it is more capable of using this locally maintained location information.
Location triggered information is provided, e.g., location specific advertising, blog, video, multimedia content, web page, automatically dialed phone call, pop-up, or other relevant location-based content using a triggered push when the handset itself determines that it has reached the vicinity of a previously downloaded point of interest. The pre-fetching and queuing of points of interest location information based on general location reduces the traffic on the network associated with repeatedly communicating location for comparison to network hosted location points. Increased processing capacity of a wireless device is leveraged, coupled with the increasing role of wireless devices in determining its precise location to facilitate local, autonomous triggering of location specific events at the device.
As a device traverses a wireless network, its active connection is “handed off” between radio network communications endpoints. These endpoints can be towers for PCS, satellites for LEOs or paging networks, wireless routers for WiFi, or other radio network controller components. Regardless of the network, data is typically maintained either within the network or at the device (typically both) such that the device can be located to deliver calls, messages, data, etc. Similarly, the device retains this information such that it can provide this as part of a device endpoint specific transaction. For means of simplicity, the radio connection endpoint will be generically referred to as the “gross location”. An example of this “gross location” is a cell site and sector combination for a terrestrial PCS network. An important aspect is that the device knows its location and tracks its “gross location”, not just the network. In this manner, the device is capable of having a “kernel” that tracks the gross location to trigger on the change. This enables initiating software implemented solely in the wireless device.
The term location based services (LBS) generally relates to consumer and commercial applications that utilize the knowledge of a wireless device user's geographic position. Location information such as street address can be entered directly by a user, but as referred to herein location based services (LBS) relates to location information that is automatically obtained electronically, e.g., using a global positioning system (GPS) in a user's wireless device such as a cell phone or personal digital assistant (PDA). Of course, other methods of precise location are possible, within the principles of the present invention.
In explaining validation of a wireless device electronic wallet transaction, a device-based triggering of a location update is disclosed first with reference to
In particular, as shown in
The disclosed embodiments describe use of a software LBS trigger 100 initiated by a user's wireless device 113 and passed to a network database 150. The trigger 100 may take one of two forms. The trigger 100 may request the network database 150 to provide the triggering wireless device 113 with a revised set of proximate location information points within a given region or radius R surrounding the user's wireless device 113 current location, based on the user's current location. As the user moves about, from time to time the user will download a revised set of locations of points of interest to provide a sufficient buffer around the handset's current position such that the device can move about and push triggers autonomously for a significant period of time. Alternatively, the trigger 100 may request location based information (e.g., a blog, text, pop-up, video, etc.) relating to the handset having reached a vicinity of a location information point of interest previously downloaded.
The radius R may be defined as a “bubble” or radius (or diameter in a 3D implementation) R centered on the device. The radius R is preferably changed proportionally to the velocity at which the device is moving. The faster the device is moving, the larger the radius R is. This includes more potential matches ahead of time and allows the user to react. In this way, if the user is moving slowly about (e.g., as if shopping within a mall), the radius R of the bubble is preferably defined smaller so that the user does not get spammed with alerts.
Yet another variant is also anticipated wherein the trigger requests a specific application to launch. This can be local to the device, or launched within the network. downloaded.
The location information points comprise information relevant to a particular location. They may comprise only a lat/lon of the location, and specific direction as to what to request in a location push upon reaching a vicinity of the lat/lon of the location information point. The location information point may include additional information previously downloaded to the handset, e.g., text message, video, etc. The additional information may be downloaded to the handset over time, in the background of other operations on the handset, to appear to the user to operate more smoothly.
Thus, the location information points can be abstracted to represent only the XY (latitude/longitude) of the point of interest (POI). The key is to let the handset know when it has reached a triggering location.
Location information points may be points of interest, location tagged blogs, commercial locations with advertising focused on the surrounding area serviced by that commercial location, video, multimedia, audio, a phone number to automatically dial, a web page to automatically access, a pop-up to automatically present to the user, an application to launch, etc.
The LBS trigger 100 is initiated at appropriate times by the user's wireless device 113 in response to its detection of significant movement of the user, e.g., the mover is walking, driving, etc. as detected by a locating device (e.g., GPS). The LBS trigger 100 may of course be initiated at additional other times by the user's wireless device 113, e.g., at the startup of a relevant location based services application on the user's wireless device 113, etc.
The LBS trigger 100 to request a revised set of surrounding points of interest is occasionally transmitted as necessary, but preferably is transmitted only when the ‘gross location’ changes. The ‘gross location’ represents a geographic region that could be network topology driven such as a cell site and sector. If it does not change, no triggered event has occurred.
Sufficient location based information is returned by the network database 150 to the triggering wireless device 113, such that the triggering wireless device 113 will receive and buffer location based lat/lon information (and potentially content to be presented to the user upon reaching a vicinity of that lat/lon) relating to areas that the wireless device 113 is not yet proximate to, but which the wireless device 113 may become proximate to, e.g., all of those triggered locations within the region defined as the ‘gross location’. The idea is to provide the wireless device 113 with the anticipated location based information that it immediately needs based on proximity, both to reduce network traffic over time, as well as to provide the user with a smoother, faster operating user interface.
The location based information may be maintained and presented in pre-defined fixed grids, or it may be determined to be proximate to a user's current location on a trigger-by-trigger basis.
With respect to the use of pre-defined fixed grids,
In particular, as shown in
A first range 302 shown in
The information points 310-320 each may contain location based information in any suitable electronic media form (e.g., text, photo, video, audio, short message, email, etc.), but importantly ties that information to a respective given location 310-312. The information point can be a trigger for initiating a different application on the device or in the network, as well as information such as text, photo, email, etc.
The given locations 310-312 may be an exact latitude/longitudinal point, a range of latitude/longitudinal values, or even a vectored range or geometric shape (e.g., a perimeter of a building).
In particular, as shown in
In particular, the LBS trigger 100 from the triggering wireless device 113 may include additional information relating to the user's wireless device 113 and/or location. For example, the LBS trigger 100 may include information relating to a current or recent speed of the user (e.g., a current speed, average speed, median speed, range of speed, etc.) Speed of the user information may be used to define a suitable range around the user's current location for which the triggering wireless device 113 will be presented with relevant location information. The size of the range 302 for which location information points is provided is preferably based on network topology (to minimize traffic overhead), but may also make use of additional information, as well as any relevant physical equipment limitations such as the available amount of memory in the triggering wireless device 113, network bandwidth limitations, etc.
If the user is moving slowly (e.g., walking) as depicted in
While
Importantly, the embodiments describe storage of the location-based information points 310-312 and associated location based information locally on the user's device subject to network and device limitations, and presentation of the location based information to the user when the user gets closely proximate, i.e., within the proximate area 310a-312a associated with to the respective information point 310-312. Alternatively, the downloaded and locally stored location-based information points 310-312 and associated information may comprise the location point, proximate area 310a-312a, and a reference or semaphore representing a downloaded local or network resident application to trigger based on proximity to the respective information point
Location based information may alternatively be provided in a custom fashion centered on a user's current location on a trigger-by-trigger basis. For instance,
For ease of description and explanation, the points of interest 310-320 are depicted in the same locations in
Note that more frequent transmission of the LBS trigger 100 from the wireless device 113 will ensure that the wireless device 113 will not come upon a particular location for which location information is in the location based information database 150 but for which the wireless device 113 had not received location information relating to that location. The size of the proximate range 510 should be sized to allow the wireless device 113 a significant amount of time to move about without having to send another LBS trigger 100 in a way that it won't ordinarily be in a location outside the proximate range 510 at the time of the last download of location based information.
As shown in
In
In
In
In
In
In
In
In particular, as shown in
The request preferably not only includes the current location of the wireless device 113, since this is maintained by the device 113, but it also preferably includes a unique identifier of the device 113. The format of this tuple may be defined in any appropriate manner.
The device provided information is used to pre-fetch a table of location information points based on a device/user specified profile. As described, the table of location information points includes only those precise location information points X/Y coordinates within a proximity of the current location of the wireless device 113.
As the wireless device 113 traverses the network, the device 113 updates (tracks) precise location at the device level but does not need to communicate this data to the network. (This can be said to infer that assistance data has been downloaded, that precise location is enabled, etc.) The LBS application compares the current location X/Y of the wireless device 113 to currently held location information points (e.g., 310-312) to determine if/when to trigger an event at the wireless device 113 based on a proximity calculation between the current location X/Y of the wireless device 113 and the relevant location information point X/Y 310-312. In this embodiment, a match between the current location of the wireless device 113 and a stored location information point 310-312 results in a request to the serving network with a request to download relevant location information for that location. In this way, a specific trigger for download of location relevant information occurs only when a wireless device 113 first reaches a proximity of a given location information point. The appropriate trigger action is then taken, whether it is to download a location specific application, advertisement, coupon, game trigger event, blog, etc. to the handset. In this manner, the desired location specific event has been triggered by the device and executed while minimizing the amount of communications and data required for download to the handset.
In particular, LBS triggers 100 may be generated when a significant change in location is detected by the wireless device 113. As shown in step 700 of
In step 702, upon expiration of the timer, a current location of the wireless device 113 is determined.
In step 704, the current location of the wireless device 113 is compared to the X/Y longitude/latitude, plus any relevant proximate area surrounding each location information points, of any/all location information points (e.g., 310-312).
In step 706, the current location of the wireless device 113 is compared to a proximate area around each location information point stored in a local trigger table.
In step 708, it is determined if the current location of the wireless device 113 matched a given location information point. If not, the process sits idle until the timer in step 700 again times out.
However, if so, then the process proceeds to step 710, appropriate action is taken to present the associated location information to the user. The trigger could also kick off an entirely new application within the network, e.g., a tracking software application if a person of interest moves outside of a defined perimeter.
For example, specific text, video, or audio information may be requested for download from the location information database 150 at that time to the wireless device 113. This process of obtaining the location information, or kickstarting as shown in step 712, is referred to herein as a kickstart trigger application. This process may be a semaphore, though it need not be.
Note that the timer in step 700 continues to run and check matches with other location points, regardless of whether or not previously location information is being presented to the user (i.e., the location information may overlap).
In step 714, the handset or network application that is waiting for a trigger event to occur (i.e., a match to a location information point) is started, and does its independent processing. This may include location fixes, etc. that are also used for trigger evaluation. It is preferably an independent application that terminates upon completion according to its own rules.
In step 716, the LBS application ends.
The LBS application in the wireless device 113 can take the form of an applet (j2me), a BREW extension, a symbian application, or other coded logic that could be embedded or downloaded and executed on the device. In either case, the LBS application may be made available to other application developers to take advantage of a common XY downloadable table.
The applet table, or list of location information points, can include context when downloaded to the wireless device 113. This is similar to the XY table except that the table instead is a set of “tuples” that define specific characteristics useful to other applications. This information may include privacy settings, user, device info, location, speed, etc. that can be provided as part of the trigger to the network. Alternatively, a match between current location and a previously loaded location information point can be served by the downloaded application on the wireless device 113 if the specific actionable location based information has already been provided as part of a response to the LBS trigger 100.
With respect to the focus of this particular patent application, rather than implement device-based location triggers upon detection of proximity to a predefined trigger point, instead device-based location triggers are utilized to facilitate validation of an electronic wallet transaction. In particular, an electronic wallet transaction is deemed valid if determined to be performed while the wireless device is at a proper location, e.g., within a merchant's retail store. This validation is based on a match between a current location of a wireless device attempting the transaction, and an expected or acceptable location for that device to be performing that particular transaction (e.g., within an expected retail store, etc.)
A number of companies are pushing the idea of an electronic wallet. With this in mind,
This embodiment uses location technology to validate payment transactions completed through a mobile phone 813 expected to be at a particular physical location while making the payment transaction.
In particular, as shown in
In an effort to validate the transaction initiated by the wireless device 813, a mobile commerce platform 830 authorizes a location validation application 800 to validate the transaction based on the location of the wireless device 813. To activate the request, the mobile commerce platform 830 passes a proximity validation request 2 to the location validation application 800. The location validation application 800 may be implemented within any suitable server, e.g., within the service provider's network or a third party network.
In the disclosed embodiment, a request to authorize the mobile purchase 1a, 1b may be accepted or denied by either the merchant 810 and/or even by the wireless phone 813.
The location validation application 800 facilitates a comparison between a current location of the wireless device 813 and the merchant 810 using a request 3 to the geo-referenced merchant database 840. The geo-referenced merchant database 840 provides an expected or acceptable location (X, Y), or range of locations (e.g., location and diameter) associated with a given merchant using a unique merchant code in the request.
The geo-referenced merchant database 840 associates a plurality of merchants, each uniquely identified within a unique merchant code, with one or more acceptable transaction locations or regions.
Upon receipt of a request to validate a given electronic wallet transaction, the location validation application 800 passes a request 5 for a current location (X, Y) of the wireless phone 813 that is attempting the electronic wallet transaction to a location server 860. In response, the location server 860 attempts to update its data regarding the location of the requested wireless phone 813 by passing a location request 8 to the wireless phone 813.
The particular location determination method implemented by the location server 860 can be by any suitable technique or methodology, e.g., Cell ID, Enhanced Cell ID, AFLT, Hybrid, WiFi/WiMax Based/Aided, global positioning system (GPS), Assisted GPS (A-GPS), etc.
The wireless phone 813 responds with updated location information as depicted by communication 7. Ultimately, the location server 860 returns the current location of the wireless phone 813 in an answer 6 to the location validation application 800.
Ideally, it is preferred that the current location of the wireless phone returned by the location server 860 be freshly obtained subsequent to the initiation of the electronic wallet transaction, rather than reporting a location of the wireless phone by the location validation application 800 as its last known position. This adds an additional layer of security to the device-based location validation of the electronic wallet transaction.
Thus, validation of an electronic wallet transaction in accordance with the present invention requires the subscriber's proximity to the merchant for the transaction to be deemed valid. Validation is determined based on a match of the current location of the wireless phone attempting the electronic wallet transaction, and a location relating to the merchant, providing an enhanced level of security in the transaction.
For instance, let's say you are buying a product at a store using your mobile device to complete the transaction. In most proposed electronic wallet scenarios, the transaction is communicated between the wireless phone and a merchant terminal via wireless communications, e.g., via infrared, Bluetooth, WiFi, WiMax, etc.
To complete the electronic wallet transaction, the validation request preferably requires at a minimum a unique merchant code. Additional information may relate to the specific transaction being validated, e.g., a product code of goods or service being purchased, the price associated with the transaction, etc.
The transaction validation request 1a is preferably initiated by the merchant 810, but could be initiated by the wireless phone 813.
Accordingly, in accordance with the invention, the location validation application 800 checks whether a transaction by a requesting wireless electronic wallet device 813 is legit, and if so then fires a location request 5 into the network to determine the current location of the wireless electronic device 813. With the current location, a comparison is made to an expected location (or area). A match of the current location of the wireless device 813 to within a proximity to the merchant's location ensures presence of the subscriber at the merchant when conducting the transaction, thus providing an added level of security to an electronic wallet transaction.
Additionally, transactional tracking may be implemented. For instance, electronic wallet transactions may be tracked with location information included, i.e., a location of the wireless device reported for each electronic transaction that took place. In particular, a transaction log may be maintained to provide detailed archival information relating to electronic wallet transactions, for use in appropriate purposes, e.g., investigation into a later allegation of fraud, etc. The transaction log may maintain information relating particular electronic wallet transactions with a location of the subscriber's wireless phone 813 when used to perform the given transaction. The location information maintained in the transaction log can be retrieved later in case of dispute to prove that the subscriber's device 813 was or wasn't at the merchant's location at the moment that a given electronic wallet transaction was completed.
A match between current location and an expected location of a wireless phone when performing a particular electronic wallet transaction requires a geo-referenced database of merchants 840, a location server 860, and a location validation application module 800 to verify the match. If proximity is determined between the current location of the wireless device 813 being used for the electronic wallet transaction and the location of the merchant 810, the transaction can be trusted. Otherwise, if the wireless device 813 is determined to be not proximate to the known location of the merchant 810, the electronic wallet transaction may be flagged for further investigation for trustworthiness, or blocked altogether.
The disclosed embodiments relate to appropriate locations for the merchant being fixed and stored in the geo-referenced merchant database 840. However, the principles of the present invention relate equally to not only a mobile purchaser using a mobile phone 813, but also to a mobile merchant 813. In particular, the current location of a given merchant 813 associated with a merchant code in a given transaction may be determined, along with a current location of the purchaser 813, and compared to determine if the purchaser 813 is appropriately proximate to the merchant 810 at the time of the electronic wallet transaction.
Location validation has additional uses. For instance, as an additional feature, if the wireless device 813 is reported lost or stolen, any future attempted electronic wallet transaction can be blocked. Alternatively, in such a loss or theft case, any future electronic wallet transaction can be allowed to occur invisibly to the presumably unauthorized user of the wireless device 813, but tracked or otherwise monitored by appropriate enforcement or police personnel, providing yet another security enhancement to the user's finances.
Conversely, if electronic wallet transactions were validated, and if the wireless phone 813 used to make the electronic wallet transactions was not reported as lost or stolen, it would be presumed that the subscriber was physically at a given merchant's store because there would be little chance someone else made the purchase. Presumably, if the wireless phone 813 was not there at the time of a given transaction, the transaction shouldn't have been validated (if it was), and thus the subscriber should not be held responsible for the given transaction. In this regard, it is preferable that the mobile commerce platform 830 handling a given electronic wallet transaction should not be validated, and thus should not clear, unless specifically allowed and instructed to do so by the location validation application 800.
In the event that a wireless electronic wallet device 813 is cloned or hacked, and the owner is unaware of it, a location mismatch between current position and expected location of a relevant merchant 810 can be used to trigger notification and preventive/corrective action.
Use of a device-based triggered Push eliminates the need for polling, and thus greatly minimizes traffic on the network while providing a trigger to other mobile applications. The fraud prevention feature of location validation of an electronic wallet transaction is a response to a specific transactional event. In this application, the wireless device is pinged, or asked for its current location, and establishes a session to determine its location.
As explained above, the triggered device-based Push requires a device resident application to monitor device location and to compare that to a trigger table. If a match is “close enough”, then it triggers an external application (referred to as a “Kickstart”) to complete its work. The fraud prevention embodiment described herein does not require an application to monitor the device's activity, as the location is triggered not by the device reaching a vicinity of a given location but rather by the occurrence of a mobile commerce transaction as part of a verification/fraud avoidance process. Thus, a trigger table and associated logic is not required for the specific application.
While intended for use with location based services (LBS), features of the invention are applicable beyond LBS. For instance, in a non-location based embodiment, a product code may be used to match product description and price for added security, e.g., to ensure a 50″ plasma TV is not sold for $3.00.
Moreover, in applications that utilize LBS, but may not require a triggered Push from the device, a wireless device may be tracked if flagged as being illegally used, or used by a suspect for illegal purposes (e.g., kidnapping, hacking, piracy, etc.) This ability is represented in
If a given wireless phone 813 is being used to conduct illegal activities, law enforcement can instruct the phone's carrier to enable location-based monitoring and tracking on that wireless phone 813. A triggered push application to output a triggered Push passed on to law enforcement personnel may be activated in such an instance. Such tracking may also or additionally be implemented using polling from the network, either mobile device assisted or network based, or by specific location requests for the given wireless device 813 instructing the wireless device 813 to report its current location (i.e., mobile station based embodiment) to a requesting application.
Device-based location validation for electronic wallet transactions is a security enhancement that is attractive for implementations by vendors, and compelling to carriers and merchants as well as subscribers.
While the invention has been described with reference to the exemplary embodiments thereof, those skilled in the art will be able to make various modifications to the described embodiments of the invention without departing from the true spirit and scope of the invention.
This application claims priority from U.S. Provisional Appl. No. 60/876,199, filed Dec. 21, 2006, entitled “Wireless Device Electronic Wallet Transaction Validation” to Walter Weichselbaumer, and is also a continuation-in-part of U.S. patent application Ser. No. 11/544,724, filed Oct. 10, 2006, entitled “Device Based Trigger For Location Push Event” to Drew Morin, which in turn claims priority from U.S. Provisional Patent Appl. No. 60/845,527, filed Sep. 19, 2006, entitled “Device Based Triggered Location Push Event” to Drew Morin, the entirety of all of which are expressly incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 60876199 | Dec 2006 | US | |
| 60845527 | Sep 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11544724 | Oct 2006 | US |
| Child | 12003296 | US |
