US20110202416A1 - Method and system for authorizing transactions based on device location - Google Patents
Method and system for authorizing transactions based on device location Download PDFInfo
- Publication number
- US20110202416A1 US20110202416A1 US12/748,106 US74810610A US2011202416A1 US 20110202416 A1 US20110202416 A1 US 20110202416A1 US 74810610 A US74810610 A US 74810610A US 2011202416 A1 US2011202416 A1 US 2011202416A1
- Authority
- US
- United States
- Prior art keywords
- communication device
- location
- transaction
- server
- account
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/108—Remote banking, e.g. home banking
- G06Q20/1085—Remote banking, e.g. home banking involving automatic teller machines [ATMs]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/20—Point-of-sale [POS] network systems
- G06Q20/206—Point-of-sale [POS] network systems comprising security or operator identification provisions, e.g. password entry
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
- G06Q20/3224—Transactions dependent on location of M-devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- A—HUMAN NECESSITIES
- A63—SPORTS; GAMES; AMUSEMENTS
- A63B—APPARATUS FOR PHYSICAL TRAINING, GYMNASTICS, SWIMMING, CLIMBING, OR FENCING; BALL GAMES; TRAINING EQUIPMENT
- A63B71/00—Games or sports accessories not covered in groups A63B1/00 - A63B69/00
- A63B71/06—Indicating or scoring devices for games or players, or for other sports activities
- A63B71/0619—Displays, user interfaces and indicating devices, specially adapted for sport equipment, e.g. display mounted on treadmills
- A63B71/0669—Score-keepers or score display devices
- A63B71/0672—Score-keepers or score display devices using non-electronic means
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/04—Payment circuits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
Definitions
- Certain embodiments of the invention relate to networking. More specifically, certain embodiments of the invention relate to a method and system for authorizing transactions based on device location.
- a system and/or method for authorizing network transactions based on device location, substantially as illustrated by and/or described in connection with at least one of the figures, as set forth more completely in the claims.
- FIG. 1 is a block diagram illustrating an exemplary communication system that enables authorization of transactions based on device location, in accordance with an embodiment of the invention.
- FIG. 2 is a block diagram illustrating an exemplary communication device that may enable and/or utilize location based services, in accordance with an embodiment of the invention.
- FIG. 3 is a block diagram illustrating an exemplary location server, in accordance with an embodiment of the invention.
- FIG. 4 is a flow chart illustrating exemplary steps for authorizing transactions based on device location, in accordance with an embodiment of the invention.
- a request may be received to approve a transaction that was initiated from a first communication device and comprises a need to access an account.
- a second communication device that is associated with the account may be determined, and it may be determined whether to approve the transaction based on received data relating to the identity and location of the second communication device.
- the transaction may be associated with the second communication device via a database stored on the location server.
- the transaction may be approved in instances that the first communication device is in a location associated, via the database, with the second communication device.
- the transaction may be approved in instances that the first communication device is in substantially the same location as the second communication device.
- the first communication device may be an automated teller machine or point-of-sale terminal.
- the transaction may comprise an electronic payment or funds transfer from a financial account. Whether to approve the transaction may be determined based on rules and/or preferences established by a provider of the financial account. Whether to approve the transaction may be determined based on rules and/or preferences established for a location based services account associated with the second communication device.
- the request may be received from a server that is processing the transaction. A result of the determination may be communicated to the server that is processing the transaction.
- FIG. 1 is a block diagram illustrating an exemplary communication system that enables authorizing transactions based on device location, in accordance with an embodiment of the invention.
- a communication system 100 comprising a communication device 104 , a point-of-sale (POS) terminal 102 , a mobile core network 110 , wireless access points (APs) 112 a and 112 b , a cellular basestation (BS) 114 , a Worldwide Interoperability for Microwave Access (WiMAX) BS 116 , a broadcast tower 118 , a Global Navigation Satellite Systems (GNSS) network 120 , a plurality of GNSS satellites 122 a - 122 n , the Internet 130 , a location server 140 , and a satellite reference network (SRN) 150 .
- the communication device 104 may be at a location 106 and the POS terminal 102 may be at a location 108 .
- the GNSS network 120 may comprise suitable logic, circuitry, interfaces, and/or code that may provide navigation information to land-based devices via satellite links.
- the GNSS network 120 may provide positioning information via downlink satellite links transmitted to land-based devices, such as the mobile communication device 104 , to enable determining their locations.
- the GNSS network 120 may comprise, for example, the plurality of GNSS satellites 122 a - 122 n , each of which is operable to provide satellite transmissions based on a global navigation satellite system (GNSS).
- Exemplary GNSS systems may comprise, for example, the Global Positioning System (GPS), GLONASS and/or Galileo based satellite system.
- the plurality of GNSS satellites 122 a - 122 n may directly provide positioning information and/or a land-based device may utilize satellite transmissions from different satellite to determine its location using, for example, triangulation based techniques.
- the Internet 130 may comprise a system of interconnected networks and/or devices that enable exchange of information and/or data among a plurality of nodes, based on one or more networking standards, including, for example, Internet Protocols (IP).
- IP Internet Protocols
- the Internet 130 may enable, for example, connectivity among a plurality of private and public, academic, business, and/or government nodes and/or networks, wherein the physical connectivity may be provided via the Public Switched Telephone Network (PSTN), utilizing copper wires, fiber-optic cables, wireless interfaces, and/or other standards-based interfaces.
- PSTN Public Switched Telephone Network
- the mobile core network 110 may comprise suitable logic, circuitry, interfaces, and/or code that are operable to provide interfacing and/or connectivity servicing among one or more access networks, which may be provide network accessibility to mobile communication devices, and external data networks such as packet data networks (PDNs) and/or the Internet 130 .
- the mobile communication device 104 may access the mobile core network 110 , for example, via the wireless AP 112 a , the cellular BS 114 , and/or the WiMAX BS 116 .
- the mobile core network 110 may be configured to communicate various data services, which are provided by external data networks, to associated users.
- the wireless APs 112 a and 112 b may each comprise suitable logic, circuitry, interfaces, and/or code that are operable to provide data services to communication devices, such the mobile communication device 104 , in adherence with one or more wireless LAN (WLAN) standards such as, for example, IEEE 802.11, 802.11a, 802.11b, 802.11d, 802.11e, 802.11n, 802.11v, and/or 802.11u.
- the wireless AP 112 a may communicate with the mobile core network 110 , via one or more links and/or associated devices, for example.
- the wireless AP 112 b may communicate with the Internet 110 , via one or more links and/or associated devices, for example. In this manner, the wireless APs 112 a and 112 b may provide network access to the mobile communication device 104 .
- the cellular BS 114 may comprise suitable logic, circuitry, interfaces, and/or code that are operable to provide voice and/or data services to communication devices, such as the mobile communication device 104 , in adherence with one or more cellular communication standards.
- Exemplary cellular communication standards may comprise Global System for Mobile communications (GSM), General Packet Radio Services (GPRS), Universal Mobile Telecommunications System (UMTS), Enhanced Data rates for GSM Evolution (EDGE), Enhanced GPRS (EGPRS), and/or 3GPP Long Term Evolution (LTE).
- GSM Global System for Mobile communications
- GPRS General Packet Radio Services
- UMTS Universal Mobile Telecommunications System
- EDGE Enhanced Data rates for GSM Evolution
- EGPRS Enhanced GPRS
- LTE 3GPP Long Term Evolution
- the cellular BS 114 may communicate with the mobile core network 110 and/or the Internet 130 , via one or more backhaul links and/or associated devices for example. In this manner, the cellular BS 114 may provide
- the WiMAX BS 116 may comprise suitable logic, circuitry, interfaces, and/or code that are operable to provide WiMAX based data services to communication devices, such as the mobile communication devices 104 .
- the WiMAX BS 116 may communicate with the mobile core network 110 and/or the Internet 130 , via one or more backhaul links and/or associated devices for example. In this manner, the WiMAX BS 116 may provide network access to the mobile communication device 104 .
- the broadcast tower 118 may comprise, for example, a terrestrial radio and/or terrestrial television transmitter.
- the broadcast tower 118 may transmit television and/or radio in accordance with one or more broadcast standards such as, for example, AM radio, FM radio, Radio Data Services (RDS or RBDS), the Digital Video Broadcasting (DVB) family of standards, the Advanced Television Systems Committee (ATSC) family of standards, the Integrated Services Digital Broadcasting (ISDB) family of standards, the Digital Terrestrial Multimedia Broadcast (DTMB) family of standards, and the Digital Multimedia Broadcasting (DMB) family of standards.
- AM radio AM radio
- FM radio Radio Data Services
- RATSC Advanced Television Systems Committee
- ISDB Integrated Services Digital Broadcasting
- DTMB Digital Terrestrial Multimedia Broadcast
- DMB Digital Multimedia Broadcasting
- the server 132 may store private and/or secure information, such as financial information, which may be accessed during a transaction such as an electronic funds transfer or online log-in.
- the server 132 may store information for credit card holders and may process debits and/or credits to card-holders' accounts. Accordingly, for purposes of this application, the server 132 may be referred to as a “transaction hosting server.”
- the location server 140 may comprise suitable logic, circuitry, interfaces, and/or code that are operable to provide and/or support location based services (LBS).
- LBS location bases services
- the location server 140 may store and/or process location related data associated with communication devices and/or users thereof.
- users may register or otherwise establish a location bases services (LBS) account (also referred to as a profile) with the owner and/or operator of the location server 140 and the location server 140 may store information associated with the LBS accounts.
- LBS accounts or profiles may, for example, be associated with one or more users, one or more communications devices, or a combination thereof.
- the location related data may be stored in a reference database 142 in the location server 140 .
- the location server 140 may be operable to collect and/or retrieve location related data for the LBS accounts.
- the location related data may be retrieved from and/or relate to communication devices and/or owners thereof and/or users thereof.
- the location related data may be updated in a variety of ways. For example, users may be enabled to log in and manually update preferences, rules, and/or other location related data. As another example, the location related data may be updated automatically based on attempted transactions, completed transactions, and/or the age of the data.
- the location server 140 may also be operable to access and/or communicate with the SRN 150 , for example, to collect and/or update location related data independently and/or autonomously.
- the SRN 150 may comprise suitable logic, circuitry, interfaces, and/or code that are operable to collect and/or distribute data from GNSS satellites, on a continuous basis.
- the SRN 150 may comprise a plurality of GNSS reference tracking stations located around the world to provide A-GNSS coverage all the time in both a home network and/or any visited network.
- the SRN 150 may utilize satellite signal received from various GNSS constellations, such as, for example, the plurality of GNSS satellites 122 a - 122 n of the GNSS network 120 .
- the location server 140 may provide location related data when requested to do so.
- the location server 140 may be operable to provide location based services (LBS) in the system 100 .
- the location server 140 may be operable to maintain, for example, the reference database 142 , which may comprise profile elements corresponding to the mobile communication device 104 , and/or users thereof, for example.
- the location server 140 may be operable to access the SRN 150 to collect GNSS satellite data, and may utilize the collected GNSS satellite data to generate GNSS assistance data (A-GNSS data) pertaining to, and/or associated with the mobile communication device 104 .
- A-GNSS data GNSS assistance data
- the location server 140 may also be operable to collect and/or retrieve location related data directly from the mobile communication device 104 , and/or from other entities that interact with the mobile communication device 104 in the system 100 , such as, for example, the wireless AP 112 a and/or 112 b , the cellular BS 114 , and/or the WiMAX 116 .
- the location related data may be stored in the reference database 142 .
- the location server 140 may be operable to communicate the stored location related data when requested to do so.
- the reference database 142 maintained in the location server 140 may be modified, refined, and/or updated.
- the modification may be performed, for example, based on location related data received from the SNR 150 , location related data received from the mobile communication device 104 and/or other communication devices in the system 100 , and/or based on uses of and/or actions performed in the communication devices.
- the location related data maintained by the location server 140 may be utilized to augment and/or substitute for location related data received and/or generated based on communication with the GNSS network 120 , for example, when communication with the GNSS network 120 is disturbed.
- various security protocols and/or procedures may be used and/or implemented within the system 100 to ensure secure exchange of location related data among, for example, devices, such as the communication device 104 , associated with LBS accounts and/or devices, such as the transaction processing server 132 , seeking to authenticate devices and/or users associated with an LBS account.
- the communication device 104 may comprise suitable logic, circuitry, interfaces and/or code to communicate via one or more wired and/or wireless connections.
- the communication device 104 may be operable to transmit and/or receive signals to and/or from one or more of the APs 112 a and 112 b , the cellular BS 114 , the WiMAX BS 116 , the GNSS network 120 , and the broadcast tower 118 .
- the communication device 104 may comprise, for example, a phone, a laptop, or a personal media player.
- the POS terminal 102 may be a means to enable a seller to accept credit card payments, for example.
- the POS terminal 102 may accept financial information, communicate the financial information to the server 132 , and provide an indication of whether the transaction is approved or denied based on feedback from the server 132 .
- the communication device 104 and/or an owner thereof may have an LBS account (or “profile”) with the owner and/or operator of the location server 140 , and the location server 140 may thus provide location based services (LBS) for the communication device 104 and/or user thereof and/or owner thereof.
- LBS location based services
- a credit card associated with an LBS account may be swiped or entered on the POS terminal 102 .
- the POS terminal 102 may send the credit card information to the transaction hosting server 132 .
- the server 132 may then attempt to process the payment by checking the card's balance, etc.
- the server 132 may determine that the credit card account is associated with an LBS account. For example, the credit card holder has enrolled in location based authentication in exchange for a better interest rate or other incentive from the credit card company.
- the server 132 may send a request to the location server 140 to have the location server 140 authenticate the transaction.
- the request may include information identifying the location 108 as being the place where the credit card was swiped.
- the location server 140 may access an LBS account associated with the credit card account and determine that the communication device 104 is associated with the LBS account. The LBS server 140 may then determine the location of the communication device 104 .
- the location of the communication device 104 may be determined in a variety of ways. In an exemplary embodiment of the invention, the location of the communication device 104 may be determined based on GPS coordinates of the communication device 104 which may be received via the cellular BS 114 and the mobile core network 110 .
- the location of the communication device 104 may be determined based on whether the communication device 104 is in range of one or more transceivers such as the APs 112 a and/or 112 b , the cellular BS 114 , and the WiMax BS 116 . Also, the location of the communication device 104 may be determined based on a most recent location determination and/or based on a location determination performed upon receiving the request from the server 132 .
- the location server 140 may send, via any available means such as the APs 112 a and/or 112 b , cellular BS, WiMAX BS 116 , or the Internet 130 , a request to the communication device 104 for the communication device 104 to provide location related data.
- the communication device 104 may send, via any available means such as the APs 112 a and/or 112 b , cellular BS 114 , WiMAX BS 116 , or the Internet 130 , its location to the location server 140 .
- the request and/or response may be communicated securely utilizing authentication and/or encryption mechanisms that may prevent spoofing or otherwise tampering with the request and/or response.
- the communication device 104 may comprise a security subsystem that may be operable to communicate reliable and secure location information to the location server 140 .
- the security subsystem may comprise, for example, dedicated hardware and/or one or more secure applications running on the communication device 104 .
- the location server 140 may determine whether the communication device 104 being at location 106 is sufficient to authenticate the credit card transaction occurring at location 108 . Such a determination may be based on a variety of factors including, for example, preferences and/or rules associated with the account. Such preferences and/or rules may be established, for example, by the LBS account holder (that is, the owner and/or user of the communication device 104 ) and/or the credit card company.
- the preferences and/or rules may, for example, be based on the type of transaction.
- the transaction may be, as in this case, an electronic funds transfer.
- Another exemplary transaction is attempting to access Internet-accessible secure and/or private information, such as a financial account, an email account, a social networking account.
- the preferences and/or rules may, for example, be based on the location and/or device from which the transaction is being attempted. For example, a rule or preference may be established that all transactions being attempted from the account holder's home and/or home personal computer (PC) may be approved regardless of the location of the communication device 104 . Conversely, a rule or preference may be established that, for all transactions initiated from a POS terminal, such as the POS terminal 102 , the communication device 104 must be in substantially the same location as the POS terminal. In this regard, substantially the same location may be determined in a variety of ways. For example, location 106 may be substantially the same as location 108 if the GNSS coordinates are sufficiently similar. As another example, the location 106 may be substantially similar to the location 108 if they are within the same building, on the same campus, or within a certain distance or proximity such as X feet of each other.
- a rule or preference may be established that all transactions being attempted from the account holder's home and/or home personal computer (PC)
- the preferences and/or rules may, for example, be based on the particular location from which the transaction is being attempted. For example, a rule or preference may be established that particular transaction may only be approved when the device from which the transaction is initiated and the communication device 104 are in a particular location, such as the LBS account holder's home.
- the preferences and/or rules may, for example, be based on an amount of money involved in the transaction. For example, all online purchases that are initiated from the account holder's home PC and involve amounts less than $X.XX may be approved regardless of the location of the communication device 104 . Conversely, a rule or preference may be established that, for all transactions involving more than $X.XX, the communication device 104 must in substantially the same location as the device initiating the transaction.
- the preferences and/or rules may, for example, be based on the time at which the transaction is being attempted. For example, a rule or preference may be established that all transactions being attempted between the hours of X:XX and Y:YY, and/or on certain days, may be automatically denied or may automatically trigger additional authentication measures such as a notification call or message to the communication device 104 ,
- the location server 140 may communicate the result of the determination to the server 132 , which may proceed accordingly.
- FIG. 2 is a block diagram illustrating an exemplary multi-radio device that may enable and/or utilize location based services, in accordance with an embodiment of the invention.
- a communication device 104 a processor 202 , a system memory 204 , a system bus 206 , a communication subsystem 210 , a plurality of interface processing blocks 212 a - 212 n , a security subsystem 220 , and a transaction management processing block 230 .
- the communication device 104 may comprise the host processer 202 , the system memory 204 , the system bus 206 , the communication subsystem 210 , the security subsystem 220 , and the transaction management processing block 230 .
- the device 104 may be as described in FIG. 1 .
- the communication device 104 may enable reception and/or transmission of signals during communication via one or more wired and/or wireless connections.
- the communication device 104 may also be operable to support and/or utilize location based services.
- the processor 202 may comprise suitable logic, circuitry, interfaces, and/or code that may be operable to process data and/or control operations of the communication device 104 .
- the host processor 202 may be operable to configure and/or control operations of various components and/or systems of the communication device 104 , by for example, providing control signals, controlling data transfers within the communication device 104 , and enabling execution of applications, programs and/or code, which may be stored in the system memory 204 .
- Such operations of the communication device 104 may comprise detection and/or identification of the location of the communication device 104 .
- the processor 202 may enable the communication device 104 to support and/or utilize location based services.
- the memory 206 may comprise suitable logic, circuitry, and/or code that may be operable to store information such as executable instructions and data that may be utilized for operations of the communication device 104 , including utilizing and/or supporting location based services.
- the memory 206 may comprise RAM, ROM, low latency nonvolatile memory such as flash memory and/or other suitable electronic data storage.
- One or more portions of the memory 206 may be secured, e.g., via the security subsystem 220 , and the security may be implanted and/or enforced in hardware.
- At least a portion of the memory may be a one-time-programmable and may comprise information that may be utilized in authenticating the device 104 , its user, and/or its location.
- the system memory 204 may store, for example, information comprising configuration data used during LBS operations in the device 104 .
- the configuration data may comprise parameters and/or code, which may comprise software and/or firmware, but the configuration data need not be limited in this regard.
- the system bus 206 may comprise suitable logic, circuitry, interfaces, and/or code that may enable exchange of data and/or information between various components and/or systems in the communication device 104 .
- the system bus may comprise parallel or serial, and/or internal or external based bus technologies, and/or any combinations thereof.
- Exemplary system bus interfaces may comprise Inter-Integrated Circuit (I 2 C), Universal Serial Bus (USB), Advanced Technology Attachment (ATA), Small Computer System Interface (SCSI), Peripheral Component Interconnect (PCI), and/or Peripheral Component Interconnect Express (PCI-e) based interfaces.
- the communication subsystem 210 may comprise suitable logic, circuitry, code, and/or interfaces that may enable communication of data, content, and/or messaging from and/or to the communication device 104 , based on one or more wired and/or wireless protocols.
- the communication subsystem 210 may comprise, for example, the plurality of processing blocks 212 a - 212 n that may be operable to perform communication based on wired or wireless standards supported in the communication device 104 .
- each of the plurality of processing blocks 212 a - 212 n may comprise suitable logic, circuitry, interfaces, and/or code that are operable to detect, receive, and/or transmit signals based on specific frequency bands and/or modulation schemes.
- the processing blocks 212 a - 212 n may also be operable to perform necessary processing operations, which may comprise, for example, buffering, filtering, modulation/demodulation, up-conversion/down-conversion, and/or digital-to-analog/analog-to-digital conversion.
- the plurality of processing blocks 212 a - 212 n may be configured to support, for example, transmission and/or reception of RF signals during communication based on Ethernet, Bluetooth, WLAN, cellular, WiMAX, GNSS, FM interfaces and/or protocols.
- the security subsystem 220 may comprise suitable logic, circuitry, interfaces, and/or code that may operable to perform security related operations in the communication device 104 .
- the security subsystem 220 may perform device and/or user authentication, certificate usage, and/or cryptographic operations in the communication device 104 .
- Various security functions may be implemented in hardware to prevent security from being circumvented via software and/or firmware modifications.
- the security subsystem 220 may comprise dedicated hardware and/or one or more applications.
- the communication device 104 may be utilized to perform network access and/or communication via one or more wired or wireless interfaces.
- the communication device 104 may, via the communication subsystem 210 , receive signals from and/or transmit signals to the wireless AP 112 a , wireless AP 112 b , the cellular BS 114 , the WiMAX BS 116 , the broadcast tower 118 , and/or the Internet 130 (e.g., via Ethernet, DSL, and/or cable infrastructure).
- the host processor 202 may manage and/or control operations of, for example, communication subsystem 210 and/or security subsystem 220 .
- the communication device 104 may be operable to support LBS application.
- the communication device 104 may be associated with an LBS account managed via the location server 140 .
- the communication device 104 may communicate, via the communication subsystem 210 , with the location server 140 .
- Information, such as identifying information and/or information relating to a location of the communication device 104 communicated between the location server 140 and the communication device 104 may be stored in the database 142 indexed by, or otherwise associated with, the LBS account that is associated with the communication device 104 and/or an owner or user thereof.
- the communication device 104 may interact with the location server 140 via one or more of the wireless AP 112 a , wireless AP 112 b , the cellular BS 114 , the WiMAX BS 116 , and/or the Internet 130 .
- the communication device 104 may provide, and/or enable the location server 140 to determine, the location of the communication device 104 .
- the security subsystem 220 may support various authentication and/or confidentiality related operations performed via the communication device 104 .
- the security subsystem 220 may prevent a user, via software or firmware, from spoofing the location of the communication device 104 . In this manner, the security subsystem 220 may be trusted by the location server 140 such that location information received from the communication device 104 may be trusted and/or relied upon by the location server 140 .
- the communication device 104 may determine its current location, which may be done using, for example, GNSS signals received via one or more of the plurality of processing blocks 212 a - 212 n , and/or based on LBS data and/or applications provided by, for example, the location server 140 .
- the security subsystem 220 may then perform, in conjunction with a location server such as the location server 140 , user authentication based on, for example, LBS based data and/or applications.
- a location server such as the location server 140
- user authentication based on, for example, LBS based data and/or applications.
- FIG. 3 is a block diagram illustrating an exemplary location server, in accordance with an embodiment of the invention. Referring to FIG. 3 there is shown a server 140 , a processor 302 , a memory 304 , a reference database 142 , and an interfacing subsystem 310 .
- the server 140 may comprise the processor 302 , the memory 304 , the reference database 142 , and the interfacing subsystem 310 .
- the server 140 may be operable to provide and/or support location based services (LBS).
- LBS location based services
- the server 140 may maintain location related data, via the reference database 142 , for example.
- the location related data may be associated with communication devices that have an account with, or are otherwise associated with, the location based services provider that owns and/or operates the location server 140 .
- Location related data may, for example, comprise information associated with a location that the communication device 104 is at and/or locations to which the communication device 104 has been.
- the processor 302 may comprise suitable logic, circuitry, interfaces, and/or code that may be operable to manage and/or control operations of the location server 140 .
- the processor 302 may be operable to configure and/or control operations of various components and/or systems of the location server 140 , by providing, for example, control signals.
- the processor 302 may also control data transfers within the location server 140 , including data storage and/or retrieval from memory 304 and/or generating, storing, and/or updating elements in the reference database 142 .
- the processor 302 may enable execution of applications, programs and/or code, which may be stored in the memory 304 for example, to enable performing various services and/or application requested from the location server 140 , including location based services (LBS) applications for example.
- LBS location based services
- the memory 304 may comprise suitable logic, circuitry, interfaces, and/or code that enable permanent and/or non-permanent storage and/or fetch of data, code and/or other information used in the location server 140 .
- the memory 304 may comprise different memory technologies, including, for example, read-only memory (ROM), random access memory (RAM), and/or Flash memory.
- the memory 304 may be operable to store, for example, data and/or code used during LBS operations in the location server 140 .
- the data and/or code may comprise configuration data or parameters, and the code may comprise operational code such as software and/or firmware, but the information need not be limited in this regard.
- the reference database 142 may comprise suitable logic, circuitry, interfaces, and/or code that may be operable to store location related data for one or more LBS accounts, wherein each LBS account may be associated with one or more communication devices and/or owners thereof and/or users thereof.
- the reference database 142 may be internally or externally coupled to the location server 140 .
- the stored location related data may be collected from and/or provided to associated devices and/or users to support LBS applications.
- the reference database 142 may be operable to manage and update the stored location related data when requested, dynamically whenever any change is detected, and/or periodically.
- the reference database 142 may comprise data which may be utilized to approve or deny transactions.
- the reference database 142 may be updated and/or modified based on data communicated to the server 140 by the communication device 104 and/or other devices associated with an LBS account.
- the interfacing subsystem 310 may comprise suitable logic, circuitry, interfaces, and/or code that may enable communication of data, content, and/or messaging from and/or to the location server 140 .
- the interfacing system 310 may support, for example, a plurality of physical and/or logical connections, based on one or more wired and/or wireless interfaces in the location server 140 .
- the interfacing system 330 may comprise, for example, one or more network interface cards (NIC) and/or wireless network interface cards (WNIC).
- the server 140 may be utilized to provide location based services (LBS).
- LBS location based services
- the processor 302 may be operable to communicate, via the interfacing subsystem 310 , with the SRN 150 , the mobile core network 110 , and/or the Internet 130 to collect location related data.
- the processor 302 may utilize the collected location related data to build and/or update the reference database 142 , which may be coupled internally or externally to the server 140 .
- the processor 302 may retrieve or collect location related data from associated users, such as the communication device 104 .
- the server 140 may provide location related data by retrieving it from the reference database 142 .
- the server 140 may store the location related data in the reference database 142 as elements that may be indexed using identifiers that are specific to serviced devices and/or users and/or owners thereof.
- identifiers comprise LBS account numbers, LBS account usernames, phone number of a communication devices associated with LBS accounts, and MAC addresses of a communication devices associated with LBS accounts.
- the reference database 142 may store and/or maintain, via the reference database 142 for example, data and/or information which may be utilized to approve or deny transactions, substantially as described with regard to FIG. 1 .
- the transaction related data may be stored into, for example, LBS accounts (also referred to as profiles) maintained via the reference database 142 .
- the server 140 may perform device and/or user authentication procedures with the serviced devices, such as the device 104 , and/or with devices requesting the approval, such as the server 132 .
- the location server 140 may enable, via the interfacing subsystem 310 , access to LBS accounts such that information associated with an account, such as account rules and/or preferences, may be modified.
- persons and/or entities which may access an LBS account may comprise an owner and/or user of a communication device associated with the LBS account, a credit card company, bank, or other financial institution associated with the LBS account, a wireless provider associated the LBS account, an Internet service provider associated with the LBS account, and/or any other person and/or entity which has been associated with the LBS account through secure and authenticated mechanisms,
- FIG. 4 is a flow chart illustrating exemplary steps for authorizing transactions based on device location, in accordance with an embodiment of the invention.
- the exemplary steps may begin with step 404 when a transaction, such as a credit card purchase, is initiated from the location 108 , where the credit card is associated with an LBS account that is also associated with the communication device 104 .
- the attempted purchase may be submitted to the server 132 .
- the exemplary steps may advance to step 406 .
- step 406 the server 132 may send a request to the location server 140 for the location server 140 to determine whether to approve the transaction. Subsequent to step 406 , the exemplary steps may advance to step 408 .
- the location server 140 may access the LBS account associated with the credit card. Based on rules, preference, and/or other information in the LBS account or profile, the location server 140 may determine whether the transaction should be automatically approved. That is, determine whether the transaction should be approved or denied regardless of the location of the communication device 104 . In instances that the transaction cannot be automatically approved or denied, the exemplary steps may advance to step 408 . In instances that the transaction is to be automatically approved or denied, the exemplary steps may advance to step 412 .
- the location server 140 may determine the current location of the communication device 104 .
- the location server 140 may send a request to the communication device 104 via one or more of the wireless AP 112 a , wireless AP 112 b , the cellular BS 114 , and the WiMAX BS 116 , and the communication device 104 may respond with its current location.
- the communication device 104 may respond with, for example, the GNSS coordinates of its current location, an RF characterization of its current location, information about distance to the other one of communication devices 102 and 104 , and/or information about a distance to or communications with such as one or more of the wireless APs 112 , the cellular BS 114 , the WiMAX BS 116 , and/or the broadcast tower 118 .
- the response may be generated by and/or communicated via a trusted subsystem, such as the security subsystem 220 , in the communication device 104 .
- the exemplary steps may advance to step 410 .
- the location server 140 may determine whether to approve the transaction based on the location of the communication device 104 . How the location of the communication device 104 factors into the determination may depend on the rules and/or preferences of the LBS account. For example, the transaction may be approved in instances that the communication device 104 is in substantially the same location as the device from which the transaction was initiated. In instances that the transaction is approved based on the location of the communication device 104 , the exemplary steps may advance to step 412 . In step 412 , the location server 140 may notify the server 132 that the transaction is approved. In step 414 , the transaction may be completed.
- the location server 140 may attempt to authenticate the communication device 104 , its user, and/or its location via an out-of-band channel. For example, the location server 140 may call or send a message to the communication device 104 requesting manual approval from the user of the communication device 104 . The user may reply to the message and send his or her approval or denial. For example, to approve the transaction, the user may have to provide a password. In instances that the user denies the transaction, the exemplary steps may advance to step 422 . In step 422 , the location server 140 may notify the server 132 of the denial and the server 132 may, in turn, deny the transaction.
- step 418 in instances that the user allows the transaction, the exemplary steps may advance to step 414 and the transaction may be completed.
- the location server 140 may provide location related data to another server or device and such steps and/or functions may be performed in that server or device.
- the location server 140 may receive a request may to approve a transaction that was initiated from a first communication device 102 and comprises a need to access an account, such as a financial account or an Internet-accessible account.
- a second communication device 104 that is associated with the account may be determined, and it may be determined whether to approve the transaction based on received data relating to the identity and location of the second communication device 104 .
- the transaction may be associated with the second communication device 104 via a database 142 stored on the location server 140 .
- the transaction may be approved in instances that the first communication device 102 is in a location associated, via the database, with the second communication device 104 .
- the transaction may be approved in instances that the first communication device 102 is in substantially the same location as the second communication device 104 .
- the first communication device 102 may be an automated teller machine or point-of-sale terminal.
- the transaction may comprise an electronic payment or funds transfer from a financial account. Whether to approve the transaction may be determined based on rules and/or preferences established by a provider of the financial account. Whether to approve the transaction may be determined based on rules and/or preferences established for a location based services account associated with the second communication device 104 .
- the request may be received from a server 132 that is processing the transaction. A result of the determination may be communicated to the server 132 that is processing the transaction.
- inventions may provide a non-transitory computer readable medium and/or storage medium, and/or a non-transitory machine readable medium and/or storage medium, having stored thereon, a machine code and/or a computer program having at least one code section executable by a machine and/or a computer, thereby causing the machine and/or computer to perform the steps as described herein for authorizing network transactions based on device location.
- the present invention may be realized in hardware, software, or a combination of hardware and software.
- the present invention may be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited.
- a typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.
- the present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods.
- Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Engineering & Computer Science (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Computer Security & Cryptography (AREA)
- Technology Law (AREA)
- Entrepreneurship & Innovation (AREA)
- Game Theory and Decision Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
- This patent application makes reference to, claims priority to and claims benefit from:
- U.S. Provisional Patent Application Ser. No. 61/304,947 (Attorney Docket No. 20997US01) filed on Feb. 16, 2010;
- U.S. Provisional Patent Application Ser. No. 61/312979 (Attorney Docket No. 21007US01) filed on Mar. 11, 2010;
- U.S. Provisional Patent Application Ser. No. 61/312,994 (Attorney Docket No. 21008US01) filed on Mar. 11, 2010;
- U.S. Provisional Patent Application Ser. No. 61/303,794 (Attorney Docket No. 21009US01) filed on Feb. 12, 2010; and
- U.S. Provisional Patent Application Ser. No. 61/309260 (Attorney Docket No. 21024US01) filed on Mar. 1, 2010.
- This Application also makes reference to:
- U.S. patent application Ser. No. ______ (Attorney Docket No. 20997US02) filed on even date herewith;
- U.S. patent application Ser. No. ______ (Attorney Docket No. 21008US02) filed on even date herewith;
- U.S. patent application Ser. No. ______ (Attorney Docket No. 21009US02) filed on even date herewith; and
- U.S. patent application Ser. No. ______ (Attorney Docket No. 21024US02) filed on even date herewith.
- Each of the above stated applications is hereby incorporated herein by reference in its entirety.
- Certain embodiments of the invention relate to networking. More specifically, certain embodiments of the invention relate to a method and system for authorizing transactions based on device location.
- The security of electronic networks continues to grow in importance as more and more sensitive information is stored electronically communicated via such electronic networks. Businesses seeking to protect trade secrets and individuals seeking to protect their credit and identity are two primary forces driving the need for stronger network security. In this regard, the fact that such problems are prevalent today illustrates may be an indication that traditional security techniques such as username/password requirements and various encryption techniques are insufficient in many instances.
- Further limitations and disadvantages of conventional and traditional approaches will become apparent to one of skill in the art, through comparison of such systems with some aspects of the present invention as set forth in the remainder of the present application with reference to the drawings.
- A system and/or method is provided for authorizing network transactions based on device location, substantially as illustrated by and/or described in connection with at least one of the figures, as set forth more completely in the claims.
- These and other advantages, aspects and novel features of the present invention, as well as details of an illustrated embodiment thereof, will be more fully understood from the following description and drawings.
-
FIG. 1 is a block diagram illustrating an exemplary communication system that enables authorization of transactions based on device location, in accordance with an embodiment of the invention. -
FIG. 2 is a block diagram illustrating an exemplary communication device that may enable and/or utilize location based services, in accordance with an embodiment of the invention. -
FIG. 3 is a block diagram illustrating an exemplary location server, in accordance with an embodiment of the invention. -
FIG. 4 is a flow chart illustrating exemplary steps for authorizing transactions based on device location, in accordance with an embodiment of the invention. - Certain embodiments of the invention may be found in a method and system authorizing network transactions based on device location. In various embodiments of the invention, a request may be received to approve a transaction that was initiated from a first communication device and comprises a need to access an account. In response to the request, a second communication device that is associated with the account may be determined, and it may be determined whether to approve the transaction based on received data relating to the identity and location of the second communication device. The transaction may be associated with the second communication device via a database stored on the location server. The transaction may be approved in instances that the first communication device is in a location associated, via the database, with the second communication device. The transaction may be approved in instances that the first communication device is in substantially the same location as the second communication device. The first communication device may be an automated teller machine or point-of-sale terminal. The transaction may comprise an electronic payment or funds transfer from a financial account. Whether to approve the transaction may be determined based on rules and/or preferences established by a provider of the financial account. Whether to approve the transaction may be determined based on rules and/or preferences established for a location based services account associated with the second communication device. The request may be received from a server that is processing the transaction. A result of the determination may be communicated to the server that is processing the transaction.
-
FIG. 1 is a block diagram illustrating an exemplary communication system that enables authorizing transactions based on device location, in accordance with an embodiment of the invention. Referring toFIG. 1 , there is shown acommunication system 100 comprising acommunication device 104, a point-of-sale (POS)terminal 102, amobile core network 110, wireless access points (APs) 112 a and 112 b, a cellular basestation (BS) 114, a Worldwide Interoperability for Microwave Access (WiMAX) BS 116, abroadcast tower 118, a Global Navigation Satellite Systems (GNSS)network 120, a plurality of GNSS satellites 122 a-122 n, the Internet 130, alocation server 140, and a satellite reference network (SRN) 150. Thecommunication device 104 may be at alocation 106 and thePOS terminal 102 may be at alocation 108. - The GNSS
network 120 may comprise suitable logic, circuitry, interfaces, and/or code that may provide navigation information to land-based devices via satellite links. The GNSSnetwork 120 may provide positioning information via downlink satellite links transmitted to land-based devices, such as themobile communication device 104, to enable determining their locations. In this regard, the GNSSnetwork 120 may comprise, for example, the plurality of GNSS satellites 122 a-122 n, each of which is operable to provide satellite transmissions based on a global navigation satellite system (GNSS). Exemplary GNSS systems may comprise, for example, the Global Positioning System (GPS), GLONASS and/or Galileo based satellite system. The plurality of GNSS satellites 122 a-122 n may directly provide positioning information and/or a land-based device may utilize satellite transmissions from different satellite to determine its location using, for example, triangulation based techniques. - The Internet 130 may comprise a system of interconnected networks and/or devices that enable exchange of information and/or data among a plurality of nodes, based on one or more networking standards, including, for example, Internet Protocols (IP). The Internet 130 may enable, for example, connectivity among a plurality of private and public, academic, business, and/or government nodes and/or networks, wherein the physical connectivity may be provided via the Public Switched Telephone Network (PSTN), utilizing copper wires, fiber-optic cables, wireless interfaces, and/or other standards-based interfaces.
- The
mobile core network 110 may comprise suitable logic, circuitry, interfaces, and/or code that are operable to provide interfacing and/or connectivity servicing among one or more access networks, which may be provide network accessibility to mobile communication devices, and external data networks such as packet data networks (PDNs) and/or theInternet 130. Themobile communication device 104 may access themobile core network 110, for example, via thewireless AP 112 a, thecellular BS 114, and/or theWiMAX BS 116. Themobile core network 110 may be configured to communicate various data services, which are provided by external data networks, to associated users. - The
wireless APs mobile communication device 104, in adherence with one or more wireless LAN (WLAN) standards such as, for example, IEEE 802.11, 802.11a, 802.11b, 802.11d, 802.11e, 802.11n, 802.11v, and/or 802.11u. Thewireless AP 112 a may communicate with themobile core network 110, via one or more links and/or associated devices, for example. Thewireless AP 112 b may communicate with theInternet 110, via one or more links and/or associated devices, for example. In this manner, thewireless APs mobile communication device 104. - The
cellular BS 114 may comprise suitable logic, circuitry, interfaces, and/or code that are operable to provide voice and/or data services to communication devices, such as themobile communication device 104, in adherence with one or more cellular communication standards. Exemplary cellular communication standards may comprise Global System for Mobile communications (GSM), General Packet Radio Services (GPRS), Universal Mobile Telecommunications System (UMTS), Enhanced Data rates for GSM Evolution (EDGE), Enhanced GPRS (EGPRS), and/or 3GPP Long Term Evolution (LTE). Thecellular BS 114 may communicate with themobile core network 110 and/or theInternet 130, via one or more backhaul links and/or associated devices for example. In this manner, thecellular BS 114 may provide network access to themobile communication device 104. - The
WiMAX BS 116 may comprise suitable logic, circuitry, interfaces, and/or code that are operable to provide WiMAX based data services to communication devices, such as themobile communication devices 104. TheWiMAX BS 116 may communicate with themobile core network 110 and/or theInternet 130, via one or more backhaul links and/or associated devices for example. In this manner, theWiMAX BS 116 may provide network access to themobile communication device 104. - The
broadcast tower 118 may comprise, for example, a terrestrial radio and/or terrestrial television transmitter. In this regard, thebroadcast tower 118 may transmit television and/or radio in accordance with one or more broadcast standards such as, for example, AM radio, FM radio, Radio Data Services (RDS or RBDS), the Digital Video Broadcasting (DVB) family of standards, the Advanced Television Systems Committee (ATSC) family of standards, the Integrated Services Digital Broadcasting (ISDB) family of standards, the Digital Terrestrial Multimedia Broadcast (DTMB) family of standards, and the Digital Multimedia Broadcasting (DMB) family of standards. - The
server 132 may store private and/or secure information, such as financial information, which may be accessed during a transaction such as an electronic funds transfer or online log-in. For example, theserver 132 may store information for credit card holders and may process debits and/or credits to card-holders' accounts. Accordingly, for purposes of this application, theserver 132 may be referred to as a “transaction hosting server.” - The
location server 140 may comprise suitable logic, circuitry, interfaces, and/or code that are operable to provide and/or support location based services (LBS). In this regard, thelocation server 140 may store and/or process location related data associated with communication devices and/or users thereof. In this regard, users may register or otherwise establish a location bases services (LBS) account (also referred to as a profile) with the owner and/or operator of thelocation server 140 and thelocation server 140 may store information associated with the LBS accounts. LBS accounts or profiles may, for example, be associated with one or more users, one or more communications devices, or a combination thereof. The location related data may be stored in areference database 142 in thelocation server 140. Thelocation server 140 may be operable to collect and/or retrieve location related data for the LBS accounts. The location related data may be retrieved from and/or relate to communication devices and/or owners thereof and/or users thereof. The location related data may be updated in a variety of ways. For example, users may be enabled to log in and manually update preferences, rules, and/or other location related data. As another example, the location related data may be updated automatically based on attempted transactions, completed transactions, and/or the age of the data. - The
location server 140 may also be operable to access and/or communicate with theSRN 150, for example, to collect and/or update location related data independently and/or autonomously. TheSRN 150 may comprise suitable logic, circuitry, interfaces, and/or code that are operable to collect and/or distribute data from GNSS satellites, on a continuous basis. In this regard, theSRN 150 may comprise a plurality of GNSS reference tracking stations located around the world to provide A-GNSS coverage all the time in both a home network and/or any visited network. TheSRN 150 may utilize satellite signal received from various GNSS constellations, such as, for example, the plurality of GNSS satellites 122 a-122 n of theGNSS network 120. Thelocation server 140 may provide location related data when requested to do so. - The
location server 140 may be operable to provide location based services (LBS) in thesystem 100. Thelocation server 140 may be operable to maintain, for example, thereference database 142, which may comprise profile elements corresponding to themobile communication device 104, and/or users thereof, for example. Thelocation server 140 may be operable to access theSRN 150 to collect GNSS satellite data, and may utilize the collected GNSS satellite data to generate GNSS assistance data (A-GNSS data) pertaining to, and/or associated with themobile communication device 104. Thelocation server 140 may also be operable to collect and/or retrieve location related data directly from themobile communication device 104, and/or from other entities that interact with themobile communication device 104 in thesystem 100, such as, for example, thewireless AP 112 a and/or 112 b, thecellular BS 114, and/or theWiMAX 116. The location related data may be stored in thereference database 142. Thelocation server 140 may be operable to communicate the stored location related data when requested to do so. In addition, thereference database 142 maintained in thelocation server 140 may be modified, refined, and/or updated. The modification may be performed, for example, based on location related data received from theSNR 150, location related data received from themobile communication device 104 and/or other communication devices in thesystem 100, and/or based on uses of and/or actions performed in the communication devices. The location related data maintained by thelocation server 140 may be utilized to augment and/or substitute for location related data received and/or generated based on communication with theGNSS network 120, for example, when communication with theGNSS network 120 is disturbed. - Furthermore, various security protocols and/or procedures may be used and/or implemented within the
system 100 to ensure secure exchange of location related data among, for example, devices, such as thecommunication device 104, associated with LBS accounts and/or devices, such as thetransaction processing server 132, seeking to authenticate devices and/or users associated with an LBS account. - The
communication device 104 may comprise suitable logic, circuitry, interfaces and/or code to communicate via one or more wired and/or wireless connections. In this regard, thecommunication device 104 may be operable to transmit and/or receive signals to and/or from one or more of theAPs cellular BS 114, theWiMAX BS 116, theGNSS network 120, and thebroadcast tower 118. Thecommunication device 104 may comprise, for example, a phone, a laptop, or a personal media player. - The
POS terminal 102 may be a means to enable a seller to accept credit card payments, for example. In this regard, thePOS terminal 102 may accept financial information, communicate the financial information to theserver 132, and provide an indication of whether the transaction is approved or denied based on feedback from theserver 132. - In operation, there may be location related data associated with the
communication device 104 stored in thedatabase 142 of thelocation server 140. In this regard, thecommunication device 104 and/or an owner thereof may have an LBS account (or “profile”) with the owner and/or operator of thelocation server 140, and thelocation server 140 may thus provide location based services (LBS) for thecommunication device 104 and/or user thereof and/or owner thereof. - In an exemplary embodiment of the invention, a credit card associated with an LBS account may be swiped or entered on the
POS terminal 102. ThePOS terminal 102 may send the credit card information to thetransaction hosting server 132. In this regard, theserver 132 may then attempt to process the payment by checking the card's balance, etc. Upon accessing the credit card account, theserver 132 may determine that the credit card account is associated with an LBS account. For example, the credit card holder has enrolled in location based authentication in exchange for a better interest rate or other incentive from the credit card company. Accordingly, theserver 132 may send a request to thelocation server 140 to have thelocation server 140 authenticate the transaction. The request may include information identifying thelocation 108 as being the place where the credit card was swiped. - The
location server 140 may access an LBS account associated with the credit card account and determine that thecommunication device 104 is associated with the LBS account. TheLBS server 140 may then determine the location of thecommunication device 104. The location of thecommunication device 104 may be determined in a variety of ways. In an exemplary embodiment of the invention, the location of thecommunication device 104 may be determined based on GPS coordinates of thecommunication device 104 which may be received via thecellular BS 114 and themobile core network 110. In another exemplary embodiment of the invention, the location of thecommunication device 104 may be determined based on whether thecommunication device 104 is in range of one or more transceivers such as theAPs 112 a and/or 112 b, thecellular BS 114, and theWiMax BS 116. Also, the location of thecommunication device 104 may be determined based on a most recent location determination and/or based on a location determination performed upon receiving the request from theserver 132. In the latter situation, thelocation server 140 may send, via any available means such as theAPs 112 a and/or 112 b, cellular BS,WiMAX BS 116, or theInternet 130, a request to thecommunication device 104 for thecommunication device 104 to provide location related data. In response, thecommunication device 104 may send, via any available means such as theAPs 112 a and/or 112 b,cellular BS 114,WiMAX BS 116, or theInternet 130, its location to thelocation server 140. The request and/or response may be communicated securely utilizing authentication and/or encryption mechanisms that may prevent spoofing or otherwise tampering with the request and/or response. In this regard, thecommunication device 104 may comprise a security subsystem that may be operable to communicate reliable and secure location information to thelocation server 140. The security subsystem may comprise, for example, dedicated hardware and/or one or more secure applications running on thecommunication device 104. - Upon determining that the
communication device 104 is atlocation 106, thelocation server 140 may determine whether thecommunication device 104 being atlocation 106 is sufficient to authenticate the credit card transaction occurring atlocation 108. Such a determination may be based on a variety of factors including, for example, preferences and/or rules associated with the account. Such preferences and/or rules may be established, for example, by the LBS account holder (that is, the owner and/or user of the communication device 104) and/or the credit card company. - The preferences and/or rules may, for example, be based on the type of transaction. For example, the transaction may be, as in this case, an electronic funds transfer. Another exemplary transaction is attempting to access Internet-accessible secure and/or private information, such as a financial account, an email account, a social networking account.
- The preferences and/or rules may, for example, be based on the location and/or device from which the transaction is being attempted. For example, a rule or preference may be established that all transactions being attempted from the account holder's home and/or home personal computer (PC) may be approved regardless of the location of the
communication device 104. Conversely, a rule or preference may be established that, for all transactions initiated from a POS terminal, such as thePOS terminal 102, thecommunication device 104 must be in substantially the same location as the POS terminal. In this regard, substantially the same location may be determined in a variety of ways. For example,location 106 may be substantially the same aslocation 108 if the GNSS coordinates are sufficiently similar. As another example, thelocation 106 may be substantially similar to thelocation 108 if they are within the same building, on the same campus, or within a certain distance or proximity such as X feet of each other. - The preferences and/or rules may, for example, be based on the particular location from which the transaction is being attempted. For example, a rule or preference may be established that particular transaction may only be approved when the device from which the transaction is initiated and the
communication device 104 are in a particular location, such as the LBS account holder's home. - The preferences and/or rules may, for example, be based on an amount of money involved in the transaction. For example, all online purchases that are initiated from the account holder's home PC and involve amounts less than $X.XX may be approved regardless of the location of the
communication device 104. Conversely, a rule or preference may be established that, for all transactions involving more than $X.XX, thecommunication device 104 must in substantially the same location as the device initiating the transaction. - The preferences and/or rules may, for example, be based on the time at which the transaction is being attempted. For example, a rule or preference may be established that all transactions being attempted between the hours of X:XX and Y:YY, and/or on certain days, may be automatically denied or may automatically trigger additional authentication measures such as a notification call or message to the
communication device 104, - The above rules, preferences, and transactions are just for illustration and the invention is not so limited.
- Upon determining whether the transaction should be approved or denied, the
location server 140 may communicate the result of the determination to theserver 132, which may proceed accordingly. -
FIG. 2 is a block diagram illustrating an exemplary multi-radio device that may enable and/or utilize location based services, in accordance with an embodiment of the invention. Referring toFIG. 2 there is shown acommunication device 104, aprocessor 202, asystem memory 204, asystem bus 206, acommunication subsystem 210, a plurality of interface processing blocks 212 a-212 n, asecurity subsystem 220, and a transaction management processing block 230. - The
communication device 104 may comprise thehost processer 202, thesystem memory 204, thesystem bus 206, thecommunication subsystem 210, thesecurity subsystem 220, and the transaction management processing block 230. Thedevice 104 may be as described inFIG. 1 . In this regard, thecommunication device 104 may enable reception and/or transmission of signals during communication via one or more wired and/or wireless connections. Thecommunication device 104 may also be operable to support and/or utilize location based services. - The
processor 202 may comprise suitable logic, circuitry, interfaces, and/or code that may be operable to process data and/or control operations of thecommunication device 104. In this regard, thehost processor 202 may be operable to configure and/or control operations of various components and/or systems of thecommunication device 104, by for example, providing control signals, controlling data transfers within thecommunication device 104, and enabling execution of applications, programs and/or code, which may be stored in thesystem memory 204. Such operations of thecommunication device 104 may comprise detection and/or identification of the location of thecommunication device 104. In this manner, theprocessor 202 may enable thecommunication device 104 to support and/or utilize location based services. - The
memory 206 may comprise suitable logic, circuitry, and/or code that may be operable to store information such as executable instructions and data that may be utilized for operations of thecommunication device 104, including utilizing and/or supporting location based services. Thememory 206 may comprise RAM, ROM, low latency nonvolatile memory such as flash memory and/or other suitable electronic data storage. One or more portions of thememory 206 may be secured, e.g., via thesecurity subsystem 220, and the security may be implanted and/or enforced in hardware. At least a portion of the memory may be a one-time-programmable and may comprise information that may be utilized in authenticating thedevice 104, its user, and/or its location. Thesystem memory 204 may store, for example, information comprising configuration data used during LBS operations in thedevice 104. The configuration data may comprise parameters and/or code, which may comprise software and/or firmware, but the configuration data need not be limited in this regard. - The
system bus 206 may comprise suitable logic, circuitry, interfaces, and/or code that may enable exchange of data and/or information between various components and/or systems in thecommunication device 104. In this regard, the system bus may comprise parallel or serial, and/or internal or external based bus technologies, and/or any combinations thereof. Exemplary system bus interfaces may comprise Inter-Integrated Circuit (I2C), Universal Serial Bus (USB), Advanced Technology Attachment (ATA), Small Computer System Interface (SCSI), Peripheral Component Interconnect (PCI), and/or Peripheral Component Interconnect Express (PCI-e) based interfaces. - The
communication subsystem 210 may comprise suitable logic, circuitry, code, and/or interfaces that may enable communication of data, content, and/or messaging from and/or to thecommunication device 104, based on one or more wired and/or wireless protocols. Thecommunication subsystem 210 may comprise, for example, the plurality of processing blocks 212 a-212 n that may be operable to perform communication based on wired or wireless standards supported in thecommunication device 104. In this regard, each of the plurality of processing blocks 212 a-212 n may comprise suitable logic, circuitry, interfaces, and/or code that are operable to detect, receive, and/or transmit signals based on specific frequency bands and/or modulation schemes. The processing blocks 212 a-212 n may also be operable to perform necessary processing operations, which may comprise, for example, buffering, filtering, modulation/demodulation, up-conversion/down-conversion, and/or digital-to-analog/analog-to-digital conversion. The plurality of processing blocks 212 a-212 n may be configured to support, for example, transmission and/or reception of RF signals during communication based on Ethernet, Bluetooth, WLAN, cellular, WiMAX, GNSS, FM interfaces and/or protocols. - The
security subsystem 220 may comprise suitable logic, circuitry, interfaces, and/or code that may operable to perform security related operations in thecommunication device 104. In this regard, thesecurity subsystem 220 may perform device and/or user authentication, certificate usage, and/or cryptographic operations in thecommunication device 104. Various security functions may be implemented in hardware to prevent security from being circumvented via software and/or firmware modifications. In various embodiments of the invention, thesecurity subsystem 220 may comprise dedicated hardware and/or one or more applications. - In operation, the
communication device 104 may be utilized to perform network access and/or communication via one or more wired or wireless interfaces. In this regard, thecommunication device 104 may, via thecommunication subsystem 210, receive signals from and/or transmit signals to thewireless AP 112 a,wireless AP 112 b, thecellular BS 114, theWiMAX BS 116, thebroadcast tower 118, and/or the Internet 130 (e.g., via Ethernet, DSL, and/or cable infrastructure). During operations in thecommunication device 104, thehost processor 202 may manage and/or control operations of, for example,communication subsystem 210 and/orsecurity subsystem 220. In an exemplary aspect of the invention, thecommunication device 104 may be operable to support LBS application. In this regard, thecommunication device 104 may be associated with an LBS account managed via thelocation server 140. Accordingly, thecommunication device 104 may communicate, via thecommunication subsystem 210, with thelocation server 140. Information, such as identifying information and/or information relating to a location of thecommunication device 104 communicated between thelocation server 140 and thecommunication device 104 may be stored in thedatabase 142 indexed by, or otherwise associated with, the LBS account that is associated with thecommunication device 104 and/or an owner or user thereof. Thecommunication device 104 may interact with thelocation server 140 via one or more of thewireless AP 112 a,wireless AP 112 b, thecellular BS 114, theWiMAX BS 116, and/or theInternet 130. During LBS related operations, thecommunication device 104 may provide, and/or enable thelocation server 140 to determine, the location of thecommunication device 104. During LBS related operations, thesecurity subsystem 220 may support various authentication and/or confidentiality related operations performed via thecommunication device 104. For example, thesecurity subsystem 220 may prevent a user, via software or firmware, from spoofing the location of thecommunication device 104. In this manner, thesecurity subsystem 220 may be trusted by thelocation server 140 such that location information received from thecommunication device 104 may be trusted and/or relied upon by thelocation server 140. - In various embodiments of the invention, the
communication device 104 may determine its current location, which may be done using, for example, GNSS signals received via one or more of the plurality of processing blocks 212 a-212 n, and/or based on LBS data and/or applications provided by, for example, thelocation server 140. Thesecurity subsystem 220 may then perform, in conjunction with a location server such as thelocation server 140, user authentication based on, for example, LBS based data and/or applications. Once the location of thedevice 104 is determined, and/or device and/or user authentication is performed, transactions, such as described with respect toFIG. 1 , may be initiated and/or completed. -
FIG. 3 is a block diagram illustrating an exemplary location server, in accordance with an embodiment of the invention. Referring toFIG. 3 there is shown aserver 140, aprocessor 302, amemory 304, areference database 142, and aninterfacing subsystem 310. - The
server 140 may comprise theprocessor 302, thememory 304, thereference database 142, and theinterfacing subsystem 310. In this regard, theserver 140 may be operable to provide and/or support location based services (LBS). In an exemplary aspect of the invention, theserver 140 may maintain location related data, via thereference database 142, for example. The location related data may be associated with communication devices that have an account with, or are otherwise associated with, the location based services provider that owns and/or operates thelocation server 140. Location related data may, for example, comprise information associated with a location that thecommunication device 104 is at and/or locations to which thecommunication device 104 has been. - The
processor 302 may comprise suitable logic, circuitry, interfaces, and/or code that may be operable to manage and/or control operations of thelocation server 140. In this regard, theprocessor 302 may be operable to configure and/or control operations of various components and/or systems of thelocation server 140, by providing, for example, control signals. Theprocessor 302 may also control data transfers within thelocation server 140, including data storage and/or retrieval frommemory 304 and/or generating, storing, and/or updating elements in thereference database 142. Theprocessor 302 may enable execution of applications, programs and/or code, which may be stored in thememory 304 for example, to enable performing various services and/or application requested from thelocation server 140, including location based services (LBS) applications for example. - The
memory 304 may comprise suitable logic, circuitry, interfaces, and/or code that enable permanent and/or non-permanent storage and/or fetch of data, code and/or other information used in thelocation server 140. In this regard, thememory 304 may comprise different memory technologies, including, for example, read-only memory (ROM), random access memory (RAM), and/or Flash memory. Thememory 304 may be operable to store, for example, data and/or code used during LBS operations in thelocation server 140. The data and/or code may comprise configuration data or parameters, and the code may comprise operational code such as software and/or firmware, but the information need not be limited in this regard. - The
reference database 142 may comprise suitable logic, circuitry, interfaces, and/or code that may be operable to store location related data for one or more LBS accounts, wherein each LBS account may be associated with one or more communication devices and/or owners thereof and/or users thereof. Thereference database 142 may be internally or externally coupled to thelocation server 140. The stored location related data may be collected from and/or provided to associated devices and/or users to support LBS applications. Thereference database 142 may be operable to manage and update the stored location related data when requested, dynamically whenever any change is detected, and/or periodically. In an exemplary aspect of the invention, thereference database 142 may comprise data which may be utilized to approve or deny transactions. Furthermore, thereference database 142 may be updated and/or modified based on data communicated to theserver 140 by thecommunication device 104 and/or other devices associated with an LBS account. - The
interfacing subsystem 310 may comprise suitable logic, circuitry, interfaces, and/or code that may enable communication of data, content, and/or messaging from and/or to thelocation server 140. Theinterfacing system 310 may support, for example, a plurality of physical and/or logical connections, based on one or more wired and/or wireless interfaces in thelocation server 140. In this regard, the interfacing system 330 may comprise, for example, one or more network interface cards (NIC) and/or wireless network interface cards (WNIC). - In operation, the
server 140 may be utilized to provide location based services (LBS). To facilitate LBS operations and/or servicing via theserver 140, theprocessor 302 may be operable to communicate, via theinterfacing subsystem 310, with theSRN 150, themobile core network 110, and/or theInternet 130 to collect location related data. Theprocessor 302 may utilize the collected location related data to build and/or update thereference database 142, which may be coupled internally or externally to theserver 140. Theprocessor 302 may retrieve or collect location related data from associated users, such as thecommunication device 104. Theserver 140 may provide location related data by retrieving it from thereference database 142. In this regard, theserver 140 may store the location related data in thereference database 142 as elements that may be indexed using identifiers that are specific to serviced devices and/or users and/or owners thereof. Exemplary identifiers comprise LBS account numbers, LBS account usernames, phone number of a communication devices associated with LBS accounts, and MAC addresses of a communication devices associated with LBS accounts. - In an exemplary aspect of the invention, the
reference database 142 may store and/or maintain, via thereference database 142 for example, data and/or information which may be utilized to approve or deny transactions, substantially as described with regard toFIG. 1 . The transaction related data may be stored into, for example, LBS accounts (also referred to as profiles) maintained via thereference database 142. In this regard, when determining whether to approve a transaction, theserver 140 may perform device and/or user authentication procedures with the serviced devices, such as thedevice 104, and/or with devices requesting the approval, such as theserver 132. - The
location server 140 may enable, via theinterfacing subsystem 310, access to LBS accounts such that information associated with an account, such as account rules and/or preferences, may be modified. In this regard, persons and/or entities which may access an LBS account may comprise an owner and/or user of a communication device associated with the LBS account, a credit card company, bank, or other financial institution associated with the LBS account, a wireless provider associated the LBS account, an Internet service provider associated with the LBS account, and/or any other person and/or entity which has been associated with the LBS account through secure and authenticated mechanisms, -
FIG. 4 is a flow chart illustrating exemplary steps for authorizing transactions based on device location, in accordance with an embodiment of the invention. Referring toFIG. 4 , the exemplary steps may begin withstep 404 when a transaction, such as a credit card purchase, is initiated from thelocation 108, where the credit card is associated with an LBS account that is also associated with thecommunication device 104. The attempted purchase may be submitted to theserver 132. Subsequent to step 404, the exemplary steps may advance to step 406. - In
step 406, theserver 132 may send a request to thelocation server 140 for thelocation server 140 to determine whether to approve the transaction. Subsequent to step 406, the exemplary steps may advance to step 408. - In
step 407, thelocation server 140 may access the LBS account associated with the credit card. Based on rules, preference, and/or other information in the LBS account or profile, thelocation server 140 may determine whether the transaction should be automatically approved. That is, determine whether the transaction should be approved or denied regardless of the location of thecommunication device 104. In instances that the transaction cannot be automatically approved or denied, the exemplary steps may advance to step 408. In instances that the transaction is to be automatically approved or denied, the exemplary steps may advance to step 412. - In
step 408, thelocation server 140 may determine the current location of thecommunication device 104. In this regard, thelocation server 140 may send a request to thecommunication device 104 via one or more of thewireless AP 112 a,wireless AP 112 b, thecellular BS 114, and theWiMAX BS 116, and thecommunication device 104 may respond with its current location. In this regard, thecommunication device 104 may respond with, for example, the GNSS coordinates of its current location, an RF characterization of its current location, information about distance to the other one ofcommunication devices 102 and104, and/or information about a distance to or communications with such as one or more of the wireless APs 112, thecellular BS 114, theWiMAX BS 116, and/or thebroadcast tower 118. The response may be generated by and/or communicated via a trusted subsystem, such as thesecurity subsystem 220, in thecommunication device 104. Subsequent to step 408, the exemplary steps may advance to step 410. - In
step 410, thelocation server 140 may determine whether to approve the transaction based on the location of thecommunication device 104. How the location of thecommunication device 104 factors into the determination may depend on the rules and/or preferences of the LBS account. For example, the transaction may be approved in instances that thecommunication device 104 is in substantially the same location as the device from which the transaction was initiated. In instances that the transaction is approved based on the location of thecommunication device 104, the exemplary steps may advance to step 412. Instep 412, thelocation server 140 may notify theserver 132 that the transaction is approved. Instep 414, the transaction may be completed. - Returning to step 410, in instances that the transaction is denied, the
location server 140 may attempt to authenticate thecommunication device 104, its user, and/or its location via an out-of-band channel. For example, thelocation server 140 may call or send a message to thecommunication device 104 requesting manual approval from the user of thecommunication device 104. The user may reply to the message and send his or her approval or denial. For example, to approve the transaction, the user may have to provide a password. In instances that the user denies the transaction, the exemplary steps may advance to step 422. Instep 422, thelocation server 140 may notify theserver 132 of the denial and theserver 132 may, in turn, deny the transaction. - Returning to step 418, in instances that the user allows the transaction, the exemplary steps may advance to step 414 and the transaction may be completed.
- Although various steps and/or functions described with respect to
FIG. 4 are described as being performed in thelocation server 140, the invention need not be so limited. For example, thelocation server 140 may provide location related data to another server or device and such steps and/or functions may be performed in that server or device. - Various aspects of a method and system for authorizing network transactions based on device location are provided. In an exemplary embodiment of the invention, the
location server 140 may receive a request may to approve a transaction that was initiated from afirst communication device 102 and comprises a need to access an account, such as a financial account or an Internet-accessible account. In response to the request, asecond communication device 104 that is associated with the account may be determined, and it may be determined whether to approve the transaction based on received data relating to the identity and location of thesecond communication device 104. The transaction may be associated with thesecond communication device 104 via adatabase 142 stored on thelocation server 140. The transaction may be approved in instances that thefirst communication device 102 is in a location associated, via the database, with thesecond communication device 104. The transaction may be approved in instances that thefirst communication device 102 is in substantially the same location as thesecond communication device 104. Thefirst communication device 102 may be an automated teller machine or point-of-sale terminal. The transaction may comprise an electronic payment or funds transfer from a financial account. Whether to approve the transaction may be determined based on rules and/or preferences established by a provider of the financial account. Whether to approve the transaction may be determined based on rules and/or preferences established for a location based services account associated with thesecond communication device 104. The request may be received from aserver 132 that is processing the transaction. A result of the determination may be communicated to theserver 132 that is processing the transaction. - Other embodiments of the invention may provide a non-transitory computer readable medium and/or storage medium, and/or a non-transitory machine readable medium and/or storage medium, having stored thereon, a machine code and/or a computer program having at least one code section executable by a machine and/or a computer, thereby causing the machine and/or computer to perform the steps as described herein for authorizing network transactions based on device location.
- Accordingly, the present invention may be realized in hardware, software, or a combination of hardware and software. The present invention may be realized in a centralized fashion in at least one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited. A typical combination of hardware and software may be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.
- The present invention may also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which when loaded in a computer system is able to carry out these methods. Computer program in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: a) conversion to another language, code or notation; b) reproduction in a different material form.
- While the present invention has been described with reference to certain embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted without departing from the scope of the present invention. In addition, many modifications may be made to adapt a particular situation or material to the teachings of the present invention without departing from its scope. Therefore, it is intended that the present invention not be limited to the particular embodiment disclosed, but that the present invention will include all embodiments falling within the scope of the appended claims.
Claims (22)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/748,106 US20110202416A1 (en) | 2010-02-12 | 2010-03-26 | Method and system for authorizing transactions based on device location |
US12/732,922 US8958815B2 (en) | 2010-02-12 | 2010-03-26 | Method and system for characterizing location and/or range based on transmit power |
US14/589,753 US9351273B2 (en) | 2010-02-12 | 2015-01-05 | Method and system for characterizing location and/or range based on transmit power |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US30379410P | 2010-02-12 | 2010-02-12 | |
US30494710P | 2010-02-16 | 2010-02-16 | |
US30926010P | 2010-03-01 | 2010-03-01 | |
US31299410P | 2010-03-11 | 2010-03-11 | |
US31297910P | 2010-03-11 | 2010-03-11 | |
US12/748,106 US20110202416A1 (en) | 2010-02-12 | 2010-03-26 | Method and system for authorizing transactions based on device location |
Publications (1)
Publication Number | Publication Date |
---|---|
US20110202416A1 true US20110202416A1 (en) | 2011-08-18 |
Family
ID=44370298
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/748,197 Active 2034-08-30 US9449345B2 (en) | 2010-02-12 | 2010-03-26 | Method and system for authorizing network transactions based on radio frequency (RF) characterization of a device's location |
US12/748,106 Abandoned US20110202416A1 (en) | 2010-02-12 | 2010-03-26 | Method and system for authorizing transactions based on device location |
US12/748,175 Abandoned US20110202460A1 (en) | 2010-02-12 | 2010-03-26 | Method and system for authorizing transactions based on relative location of devices |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/748,197 Active 2034-08-30 US9449345B2 (en) | 2010-02-12 | 2010-03-26 | Method and system for authorizing network transactions based on radio frequency (RF) characterization of a device's location |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/748,175 Abandoned US20110202460A1 (en) | 2010-02-12 | 2010-03-26 | Method and system for authorizing transactions based on relative location of devices |
Country Status (1)
Country | Link |
---|---|
US (3) | US9449345B2 (en) |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090187492A1 (en) * | 2007-10-25 | 2009-07-23 | Ayman Hammad | Location based authentication |
US20110238476A1 (en) * | 2010-03-23 | 2011-09-29 | Michael Carr | Location-based Coupons and Mobile Devices |
US20110238514A1 (en) * | 2010-03-23 | 2011-09-29 | Harsha Ramalingam | Transaction Completion Based on Geolocation Arrival |
US8484133B1 (en) * | 2012-05-18 | 2013-07-09 | MoviePass Inc. | Secure targeted personal buying/selling method and system |
WO2014081847A1 (en) * | 2012-11-21 | 2014-05-30 | Sara Benson | Method and system for private association rating system |
US8740067B1 (en) * | 2012-02-29 | 2014-06-03 | Amazon Technologies, Inc. | Secondary verification |
US20140379504A1 (en) * | 2013-05-24 | 2014-12-25 | Marc George | System for managing personal identifiers and financial instrument use |
EP2836970A4 (en) * | 2012-04-11 | 2015-09-23 | Mastercard International Inc | Method and system for two stage authentication with geolocation |
US9351273B2 (en) | 2010-02-12 | 2016-05-24 | Broadcom Corporation | Method and system for characterizing location and/or range based on transmit power |
US9654503B1 (en) * | 2015-03-11 | 2017-05-16 | Symantec Corporation | Systems and methods for evaluating networks |
US9965768B1 (en) | 2011-05-19 | 2018-05-08 | Amazon Technologies, Inc. | Location-based mobile advertising |
US10284538B2 (en) | 2016-10-26 | 2019-05-07 | Bank Of America Corporation | System for processing an even request by determining a matching user profile based on user identifying information |
US10311423B2 (en) | 2015-06-09 | 2019-06-04 | Zumigo, Inc. | System and method for transaction approval based on confirmation of proximity of mobile subscriber device to a particular location |
US20210279735A1 (en) * | 2016-10-27 | 2021-09-09 | Sony Corporation | Information processing device, information processing system, information processing method, and program |
US11620628B2 (en) | 2015-06-30 | 2023-04-04 | Mastercard International Incorporated | Method and system for fraud control based on geolocation |
Families Citing this family (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9177313B1 (en) * | 2007-10-18 | 2015-11-03 | Jpmorgan Chase Bank, N.A. | System and method for issuing, circulating and trading financial instruments with smart features |
US9317835B2 (en) | 2011-03-08 | 2016-04-19 | Bank Of America Corporation | Populating budgets and/or wish lists using real-time video image analysis |
US8718612B2 (en) | 2011-03-08 | 2014-05-06 | Bank Of American Corporation | Real-time analysis involving real estate listings |
US8688559B2 (en) * | 2011-03-08 | 2014-04-01 | Bank Of America Corporation | Presenting investment-related information on a mobile communication device |
US8922657B2 (en) | 2011-03-08 | 2014-12-30 | Bank Of America Corporation | Real-time video image analysis for providing security |
US9317860B2 (en) | 2011-03-08 | 2016-04-19 | Bank Of America Corporation | Collective network of augmented reality users |
US9773285B2 (en) | 2011-03-08 | 2017-09-26 | Bank Of America Corporation | Providing data associated with relationships between individuals and images |
US9224166B2 (en) | 2011-03-08 | 2015-12-29 | Bank Of America Corporation | Retrieving product information from embedded sensors via mobile device video analysis |
US8721337B2 (en) | 2011-03-08 | 2014-05-13 | Bank Of America Corporation | Real-time video image analysis for providing virtual landscaping |
US8873807B2 (en) | 2011-03-08 | 2014-10-28 | Bank Of America Corporation | Vehicle recognition |
US8810598B2 (en) | 2011-04-08 | 2014-08-19 | Nant Holdings Ip, Llc | Interference based augmented reality hosting platforms |
WO2013155628A1 (en) | 2012-04-17 | 2013-10-24 | Zighra Inc. | Fraud detection system, method, and device |
JP6004752B2 (en) * | 2012-06-04 | 2016-10-12 | キヤノン株式会社 | COMMUNICATION DEVICE, ITS CONTROL METHOD, PROGRAM |
US9813905B2 (en) * | 2013-10-14 | 2017-11-07 | U.S. Bank, National Association | DTMF token for automated out-of-band authentication |
US9582516B2 (en) | 2013-10-17 | 2017-02-28 | Nant Holdings Ip, Llc | Wide area augmented reality location-based services |
US20150339638A1 (en) * | 2014-05-20 | 2015-11-26 | Capital One Financial Corporation | System and method for providing social cash |
JP6230435B2 (en) * | 2014-02-03 | 2017-11-15 | キヤノン株式会社 | Data processing apparatus, control method thereof, and program |
KR20150104700A (en) * | 2014-03-06 | 2015-09-16 | 삼성전자주식회사 | Method and apparatus for conducting mobile payment service |
US10187799B2 (en) | 2014-08-19 | 2019-01-22 | Zighra Inc. | System and method for implicit authentication |
US20160162900A1 (en) | 2014-12-09 | 2016-06-09 | Zighra Inc. | Fraud detection system, method, and device |
US10554676B2 (en) | 2015-03-03 | 2020-02-04 | Zighra Inc. | System and method for behavioural biometric authentication using program modelling |
EP3335440B1 (en) | 2015-08-14 | 2020-06-24 | Visa International Service Association | System and method for location determination using mesh routing |
US9935961B2 (en) * | 2015-09-11 | 2018-04-03 | Bank Of America Corporation | Controlling access to data |
US10581988B2 (en) | 2016-06-08 | 2020-03-03 | Bank Of America Corporation | System for predictive use of resources |
US10129126B2 (en) | 2016-06-08 | 2018-11-13 | Bank Of America Corporation | System for predictive usage of resources |
US10178101B2 (en) | 2016-06-08 | 2019-01-08 | Bank Of America Corporation | System for creation of alternative path to resource acquisition |
US10433196B2 (en) | 2016-06-08 | 2019-10-01 | Bank Of America Corporation | System for tracking resource allocation/usage |
US10291487B2 (en) | 2016-06-08 | 2019-05-14 | Bank Of America Corporation | System for predictive acquisition and use of resources |
US10565589B2 (en) * | 2016-06-14 | 2020-02-18 | Mastercard International Incorporated | Methods and system for real-time fraud decisioning based upon user-defined valid activity location data |
US11238148B2 (en) * | 2019-02-12 | 2022-02-01 | Cisco Technology, Inc. | Location-based, context-aware challenge-response authentication |
US11343259B2 (en) | 2020-07-09 | 2022-05-24 | Bank Of America Corporation | Electronic system for dynamic stepped multi-level authentication |
US11392684B2 (en) | 2020-07-09 | 2022-07-19 | Bank Of America Corporation | Authentication of user activities based on establishing communication links between network devices |
Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030225893A1 (en) * | 2002-03-01 | 2003-12-04 | Roese John J. | Locating devices in a data network |
US20040185842A1 (en) * | 2003-01-28 | 2004-09-23 | Spaur Charles W. | Secure telematics |
US20040254868A1 (en) * | 2003-06-12 | 2004-12-16 | International Business Machines Corporation | System and method for early detection and prevention of identity theft |
US20060194592A1 (en) * | 2005-02-28 | 2006-08-31 | Research In Motion Limited | Method and system for enhanced security using location-based wireless authentication |
US20070055785A1 (en) * | 2005-09-02 | 2007-03-08 | Qwest Communications International Inc. | Location based authorization of financial card transactions systems and methods |
US20080222038A1 (en) * | 2005-07-05 | 2008-09-11 | Tomer Eden | Location Based Authentication System |
US20090098825A1 (en) * | 2005-03-07 | 2009-04-16 | Heikki Huomo | Method and mobile terminal device including smartcard module and near field communications |
US20090187492A1 (en) * | 2007-10-25 | 2009-07-23 | Ayman Hammad | Location based authentication |
US20090192903A1 (en) * | 2008-01-30 | 2009-07-30 | Intuit Inc. | Method and apparatus for authorizing a financial transaction |
US20090254975A1 (en) * | 2005-03-31 | 2009-10-08 | Turnbull Rory S | Location Based Authentication |
US20100022254A1 (en) * | 2008-07-22 | 2010-01-28 | Bank Of America Corporation | Location-Based Authentication of Mobile Device Transactions |
US20100049615A1 (en) * | 2008-01-24 | 2010-02-25 | Qualcomm Incorporated | Mobile commerce authentication and authorization system |
US20100100486A1 (en) * | 2008-10-17 | 2010-04-22 | At&T Mobility Ii Llc | User terminal and wireless item-based credit card authorization servers, systems, methods and computer program products |
US7857212B1 (en) * | 2008-02-14 | 2010-12-28 | Capital One Financial Corporation | Method and system for authorizing card account transactions by geographic region |
US8090351B2 (en) * | 2009-09-01 | 2012-01-03 | Elliot Klein | Geographical location authentication method |
Family Cites Families (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7319986B2 (en) * | 1999-09-28 | 2008-01-15 | Bank Of America Corporation | Dynamic payment cards and related management systems and associated methods |
US8275704B2 (en) * | 1999-11-05 | 2012-09-25 | Lead Core Fund, L.L.C. | Systems and methods for authorizing an allocation of an amount between transaction accounts |
WO2002001376A1 (en) * | 2000-06-28 | 2002-01-03 | Yozan Inc. | Host computer, mobile communication device, program, and recording medium |
IL149960A0 (en) * | 2000-09-21 | 2001-11-10 | Hal Tech Corp | System and method for network infrastructure management |
US7103576B2 (en) * | 2001-09-21 | 2006-09-05 | First Usa Bank, Na | System for providing cardless payment |
US7647422B2 (en) * | 2001-11-06 | 2010-01-12 | Enterasys Networks, Inc. | VPN failure recovery |
US7761703B2 (en) * | 2002-03-20 | 2010-07-20 | Research In Motion Limited | System and method for checking digital certificate status |
WO2003079627A2 (en) * | 2002-03-20 | 2003-09-25 | Research In Motion Limited | System and method for supporting multiple certificate status providers on a mobile communication device |
DE602004009596T2 (en) * | 2003-09-12 | 2008-07-24 | Ntt Docomo Inc. | SAFE HANDOVER WITHIN A TERRITORY AND TERRITORY |
US7643443B2 (en) * | 2003-10-03 | 2010-01-05 | Nvidia Corporation | Systems and methods for autonomously and dynamically optimizing transmission power in a wireless network |
US7373109B2 (en) * | 2003-11-04 | 2008-05-13 | Nokia Corporation | System and method for registering attendance of entities associated with content creation |
US9191215B2 (en) * | 2003-12-30 | 2015-11-17 | Entrust, Inc. | Method and apparatus for providing authentication using policy-controlled authentication articles and techniques |
US20050242177A1 (en) * | 2004-04-28 | 2005-11-03 | Dexit Inc. | RFID-based system and method of conducting financial transactions |
WO2005107144A1 (en) * | 2004-04-30 | 2005-11-10 | Research In Motion Limited | System and method for handling data transfers |
EP1782569B1 (en) * | 2004-07-07 | 2013-09-25 | Nariste Networks Pty Ltd | Location-enabled security services in wireless network |
US7945945B2 (en) * | 2004-08-06 | 2011-05-17 | Enterasys Networks, Inc. | System and method for address block enhanced dynamic network policy management |
US20060176152A1 (en) * | 2005-02-10 | 2006-08-10 | Psc Scanning, Inc. | RFID power ramping for tag singulation |
US20070036353A1 (en) * | 2005-05-31 | 2007-02-15 | Interdigital Technology Corporation | Authentication and encryption methods using shared secret randomness in a joint channel |
US20070084913A1 (en) * | 2005-10-18 | 2007-04-19 | Capital One Financial Corporation | Systems and methods for authorizing a transaction for a financial account |
CA2640261A1 (en) * | 2006-01-26 | 2007-08-09 | Imprivata, Inc. | Systems and methods for multi-factor authentication |
US20080085727A1 (en) * | 2006-06-14 | 2008-04-10 | Kratz Tyler M | System and method for determining mobile device position information |
US7600676B1 (en) * | 2006-12-26 | 2009-10-13 | Cellco Partnership | Two factor authentications for financial transactions |
WO2008089538A1 (en) * | 2007-01-23 | 2008-07-31 | Sxip Identity Corp. | Intermediate data generation for transaction processing |
US8695074B2 (en) * | 2007-04-26 | 2014-04-08 | Microsoft Corporation | Pre-authenticated calling for voice applications |
US8036658B2 (en) * | 2007-05-17 | 2011-10-11 | Arumugam Govindswamy | Method and apparatus to improve network acquisition |
US20090012898A1 (en) * | 2007-07-02 | 2009-01-08 | Lucent Technologies Inc. | Location based credit card fraud prevention |
EA016321B1 (en) * | 2007-12-11 | 2012-04-30 | Трэнволл Холдингз Лтд. | Account risk management and authorization system for preventing unauthorized usage of accounts |
JP5211797B2 (en) * | 2008-03-26 | 2013-06-12 | 日本電気株式会社 | Authentication system, authentication method, and authentication program |
US20090326998A1 (en) * | 2008-06-27 | 2009-12-31 | Wachovia Corporation | Transaction risk management |
US20100274698A1 (en) * | 2009-04-27 | 2010-10-28 | International Business Machines Corporation | Soft Limits for Credit Card Transactions |
US20100293093A1 (en) * | 2009-05-13 | 2010-11-18 | Igor Karpenko | Alterable Security Value |
US20100332351A1 (en) * | 2009-06-30 | 2010-12-30 | Ebay Inc. | Same screen quick pay button |
US8335519B2 (en) * | 2009-12-03 | 2012-12-18 | Osocad Remote Limited Liability Company | System and method for providing a community of mobile devices |
US20110154014A1 (en) * | 2009-12-18 | 2011-06-23 | Sony Ericsson Mobile Communications Ab | Data exchange for mobile devices |
US8560722B2 (en) * | 2011-03-18 | 2013-10-15 | International Business Machines Corporation | System and method to govern sensitive data exchange with mobile devices based on threshold sensitivity values |
-
2010
- 2010-03-26 US US12/748,197 patent/US9449345B2/en active Active
- 2010-03-26 US US12/748,106 patent/US20110202416A1/en not_active Abandoned
- 2010-03-26 US US12/748,175 patent/US20110202460A1/en not_active Abandoned
Patent Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030225893A1 (en) * | 2002-03-01 | 2003-12-04 | Roese John J. | Locating devices in a data network |
US20040185842A1 (en) * | 2003-01-28 | 2004-09-23 | Spaur Charles W. | Secure telematics |
US20040254868A1 (en) * | 2003-06-12 | 2004-12-16 | International Business Machines Corporation | System and method for early detection and prevention of identity theft |
US20060194592A1 (en) * | 2005-02-28 | 2006-08-31 | Research In Motion Limited | Method and system for enhanced security using location-based wireless authentication |
US20070184818A1 (en) * | 2005-02-28 | 2007-08-09 | Research In Motion Limited | Method and system for enhanced security using location based wireless authentication |
US20090098825A1 (en) * | 2005-03-07 | 2009-04-16 | Heikki Huomo | Method and mobile terminal device including smartcard module and near field communications |
US20090254975A1 (en) * | 2005-03-31 | 2009-10-08 | Turnbull Rory S | Location Based Authentication |
US20080222038A1 (en) * | 2005-07-05 | 2008-09-11 | Tomer Eden | Location Based Authentication System |
US20070055785A1 (en) * | 2005-09-02 | 2007-03-08 | Qwest Communications International Inc. | Location based authorization of financial card transactions systems and methods |
US20090187492A1 (en) * | 2007-10-25 | 2009-07-23 | Ayman Hammad | Location based authentication |
US20100049615A1 (en) * | 2008-01-24 | 2010-02-25 | Qualcomm Incorporated | Mobile commerce authentication and authorization system |
US20090192903A1 (en) * | 2008-01-30 | 2009-07-30 | Intuit Inc. | Method and apparatus for authorizing a financial transaction |
US7857212B1 (en) * | 2008-02-14 | 2010-12-28 | Capital One Financial Corporation | Method and system for authorizing card account transactions by geographic region |
US20100022254A1 (en) * | 2008-07-22 | 2010-01-28 | Bank Of America Corporation | Location-Based Authentication of Mobile Device Transactions |
US20100100486A1 (en) * | 2008-10-17 | 2010-04-22 | At&T Mobility Ii Llc | User terminal and wireless item-based credit card authorization servers, systems, methods and computer program products |
US8090351B2 (en) * | 2009-09-01 | 2012-01-03 | Elliot Klein | Geographical location authentication method |
Cited By (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090187492A1 (en) * | 2007-10-25 | 2009-07-23 | Ayman Hammad | Location based authentication |
US10755271B2 (en) | 2007-10-25 | 2020-08-25 | Visa U.S.A. Inc. | Location based authentication |
US10163100B2 (en) | 2007-10-25 | 2018-12-25 | Visa International Service Association | Location based authentication |
US9721250B2 (en) | 2007-10-25 | 2017-08-01 | Visa U.S.A. Inc. | Location based authentication |
US9351273B2 (en) | 2010-02-12 | 2016-05-24 | Broadcom Corporation | Method and system for characterizing location and/or range based on transmit power |
US9760885B1 (en) | 2010-03-23 | 2017-09-12 | Amazon Technologies, Inc. | Hierarchical device relationships for geolocation-based transactions |
US12086786B2 (en) | 2010-03-23 | 2024-09-10 | Amazon Technologies, Inc. | Transaction completion based on geolocation arrival |
US10339549B1 (en) | 2010-03-23 | 2019-07-02 | Amazon Technologies, Inc. | Transaction bootstrapping to create relationships |
US10438242B1 (en) | 2010-03-23 | 2019-10-08 | Amazon Technologies, Inc. | Converged web-identity and mobile device based shopping |
US20110238476A1 (en) * | 2010-03-23 | 2011-09-29 | Michael Carr | Location-based Coupons and Mobile Devices |
US9058604B2 (en) | 2010-03-23 | 2015-06-16 | Amazon Technologies, Inc. | Converged web-identity and mobile device based shopping |
US9107064B1 (en) | 2010-03-23 | 2015-08-11 | Amazon Technologies, Inc. | Mobile device security |
US20110238514A1 (en) * | 2010-03-23 | 2011-09-29 | Harsha Ramalingam | Transaction Completion Based on Geolocation Arrival |
US8341029B1 (en) | 2010-03-23 | 2012-12-25 | Amazon Technologies, Inc. | User profile and geolocation for efficient transactions |
US9386507B1 (en) | 2010-03-23 | 2016-07-05 | Amazon Technologies, Inc. | Mobile device security |
US9609577B1 (en) | 2010-03-23 | 2017-03-28 | Amazon Technologies, Inc. | Mobile device security |
US8521131B1 (en) | 2010-03-23 | 2013-08-27 | Amazon Technologies, Inc. | Mobile device security |
US9681359B2 (en) | 2010-03-23 | 2017-06-13 | Amazon Technologies, Inc. | Transaction completion based on geolocation arrival |
US9697508B1 (en) | 2010-03-23 | 2017-07-04 | Amazon Technologies, Inc. | Mobile payments using point-of-sale infrastructure |
US8255284B1 (en) | 2010-03-23 | 2012-08-28 | Amazon Technologies, Inc. | User profile and geolocation for efficient transactions |
US9723131B1 (en) | 2010-03-23 | 2017-08-01 | Amazon Technologies, Inc. | Mobile device security |
US10366385B1 (en) | 2010-03-23 | 2019-07-30 | Amazon Technologies, Inc. | Mobile payments using point-of-sale infrastructure |
US9767474B1 (en) | 2010-03-23 | 2017-09-19 | Amazon Technologies, Inc. | Transaction tracking and incentives |
US9916608B1 (en) | 2010-03-23 | 2018-03-13 | Amazon Technologies, Inc. | User profile and geolocation for efficient transactions |
US9965768B1 (en) | 2011-05-19 | 2018-05-08 | Amazon Technologies, Inc. | Location-based mobile advertising |
US8740067B1 (en) * | 2012-02-29 | 2014-06-03 | Amazon Technologies, Inc. | Secondary verification |
EP2836970A4 (en) * | 2012-04-11 | 2015-09-23 | Mastercard International Inc | Method and system for two stage authentication with geolocation |
US8484133B1 (en) * | 2012-05-18 | 2013-07-09 | MoviePass Inc. | Secure targeted personal buying/selling method and system |
WO2014081847A1 (en) * | 2012-11-21 | 2014-05-30 | Sara Benson | Method and system for private association rating system |
US20140379504A1 (en) * | 2013-05-24 | 2014-12-25 | Marc George | System for managing personal identifiers and financial instrument use |
US10373166B2 (en) * | 2013-05-24 | 2019-08-06 | Marc George | System for managing personal identifiers and financial instrument use |
US9654503B1 (en) * | 2015-03-11 | 2017-05-16 | Symantec Corporation | Systems and methods for evaluating networks |
US10311423B2 (en) | 2015-06-09 | 2019-06-04 | Zumigo, Inc. | System and method for transaction approval based on confirmation of proximity of mobile subscriber device to a particular location |
US11620628B2 (en) | 2015-06-30 | 2023-04-04 | Mastercard International Incorporated | Method and system for fraud control based on geolocation |
US10284538B2 (en) | 2016-10-26 | 2019-05-07 | Bank Of America Corporation | System for processing an even request by determining a matching user profile based on user identifying information |
US20210279735A1 (en) * | 2016-10-27 | 2021-09-09 | Sony Corporation | Information processing device, information processing system, information processing method, and program |
Also Published As
Publication number | Publication date |
---|---|
US20110202461A1 (en) | 2011-08-18 |
US20110202460A1 (en) | 2011-08-18 |
US9449345B2 (en) | 2016-09-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20110202416A1 (en) | Method and system for authorizing transactions based on device location | |
US9852416B2 (en) | System and method for authorizing a payment transaction | |
US20190287110A1 (en) | Method and apparatus for facilitating multi-element bidding for influencing a position on a payment list generated by an automated authentication engine | |
KR102070132B1 (en) | System and method for providing network access to electronic devices using bandwidth provisioning | |
US11240220B2 (en) | Systems and methods for user authentication based on multiple devices | |
US20130268378A1 (en) | Transaction validation between a mobile communication device and a terminal using location data | |
US20130110715A1 (en) | Use of Velocity in Fraud Detection or Prevention | |
US10699273B2 (en) | System and method for authorizing payment transaction based on device locations | |
AU2015323425A1 (en) | Systems and methods for identifying mobile devices | |
US11575671B2 (en) | Network ID device history and mobile account attributes used as a risk indicator in mobile network-based authentication | |
US20180232740A1 (en) | Method and apparatus for facilitating payment option aggregation and without additional user input, payment option selection, utilizing an automated authentication engine | |
US20150365827A1 (en) | Methods and systems for authentication of a communication device | |
US20180232718A1 (en) | Method and apparatus for facilitating payment option aggregation to complete a transaction initiated at a third party payment apparatus, utilizing an automated authentication engine | |
US20180268476A1 (en) | Method and apparatus for facilitating multi-element bidding for influencing a position on a payment list generated by an automated authentication engine | |
US11570620B2 (en) | Network profile anti-spoofing on wireless gateways | |
US20190026704A1 (en) | Method of registering a membership for an electronic payment, system for same, and apparatus and terminal thereof | |
US20190281053A1 (en) | Method and apparatus for facilitating frictionless two-factor authentication | |
US20240296449A1 (en) | Mobile authentification method via peer mobiles | |
EP3678352A1 (en) | Quick enabling method and apparatus for service in application program and electronic device | |
US20110212735A1 (en) | Method and system for seamless consummation of an electronic transaction based on location related data | |
US20220377065A1 (en) | Single-exchange authentication of a communications device | |
WO2019191365A1 (en) | Method and apparatus for facilitating performing payment option aggregation utilizing an automated authentication engine | |
US20180165667A1 (en) | Control of permissions for making transactions | |
US11978052B2 (en) | Method for validating electronic transactions | |
US12034863B2 (en) | Methods of authenticating the identity of a computer |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BROADCOM CORPORATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BUER, MARK;ABRAHAM, CHARLES;GARRETT, DAVID;AND OTHERS;SIGNING DATES FROM 20100322 TO 20100325;REEL/FRAME:024293/0094 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:037806/0001 Effective date: 20160201 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: PATENT SECURITY AGREEMENT;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:037806/0001 Effective date: 20160201 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD., SINGAPORE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:041706/0001 Effective date: 20170120 Owner name: AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BROADCOM CORPORATION;REEL/FRAME:041706/0001 Effective date: 20170120 |
|
AS | Assignment |
Owner name: BROADCOM CORPORATION, CALIFORNIA Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:041712/0001 Effective date: 20170119 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED, SINGAPORE Free format text: MERGER;ASSIGNOR:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;REEL/FRAME:047231/0369 Effective date: 20180509 Owner name: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITE Free format text: MERGER;ASSIGNOR:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;REEL/FRAME:047231/0369 Effective date: 20180509 |
|
AS | Assignment |
Owner name: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITE Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE EXECUTION DATE OF THE MERGER AND APPLICATION NOS. 13/237,550 AND 16/103,107 FROM THE MERGER PREVIOUSLY RECORDED ON REEL 047231 FRAME 0369. ASSIGNOR(S) HEREBY CONFIRMS THE MERGER;ASSIGNOR:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;REEL/FRAME:048549/0113 Effective date: 20180905 Owner name: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED, SINGAPORE Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE EXECUTION DATE OF THE MERGER AND APPLICATION NOS. 13/237,550 AND 16/103,107 FROM THE MERGER PREVIOUSLY RECORDED ON REEL 047231 FRAME 0369. ASSIGNOR(S) HEREBY CONFIRMS THE MERGER;ASSIGNOR:AVAGO TECHNOLOGIES GENERAL IP (SINGAPORE) PTE. LTD.;REEL/FRAME:048549/0113 Effective date: 20180905 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: NOTICE OF APPEAL FILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |