System and method for location-based node management in a wireless charging network

Abstract

Multiple wireless charging systems can be used within a network at a location or other physical area to precisely locate the network's battery-powered nodes. When a transaction between a node and another node within the network is associated with this precise location, the node's location can then be used to manage the transaction.

Description

Background Technology

[0001] The background description provided herein is intended to generally present the context of this disclosure. To the extent described in this background section, the work of the currently identified inventors and aspects of the description that might not have otherwise qualified as prior art at the time of filing are neither explicitly nor implicitly considered as prior art to this disclosure.

[0002] Wireless communication networks are ubiquitous. The data transmitted between nodes within a wireless network ranges from personal communications to complex data transfers and manipulations between nodes. Several known techniques can be used to determine the physical location of network nodes. For example, cell identification combining round-trip time (RTT), timing advance (TA), and measured signal level (RX level), time difference of arrival (TDOA), and angle of arrival (AOA) techniques can be used with varying degrees of accuracy. Some nodes, such as smartphones and other computing devices, may include Global Positioning System (GPS) capabilities for location determination.

[0003] However, each of these technologies has its drawbacks. For example, non-GPS technologies typically rely on two network sites, such as cellular towers, which can measure and process the delay between signal arrivals, identify the direction of the signal based on path signatures, and determine the distance between the mobile station and the cellular tower. GPS positioning systems are error-prone and only achieve high accuracy after performing extensive calculations and measurements to eliminate errors. Furthermore, these methods degrade significantly when determining the location of indoor network nodes. Summary of the Invention

[0004] The following is a simplified overview of this disclosure to provide a basic understanding of some aspects of it. This overview is not an exhaustive summary and is not intended to identify key or essential elements of this disclosure or define its scope. The following overview presents some concepts in a simplified form only as an introduction to the more detailed description provided below.

[0005] Loosely coupled wireless charging systems within networks and associated data can be used to locate mobile computing devices (e.g., smartphones, tablets, and other mobile computing devices with virtual wallet applications, internet access, and / or other capabilities to communicate with e-commerce merchants and complete purchase transactions). Data facilitating the location of mobile computing devices may include: the duration it takes for a device to charge from zero to a threshold charge using several wireless charging systems; and the response time of the device in instructing multiple wireless charging systems that it has reached the threshold charge. The distance between the charger and the device can be estimated using the known location of the wireless charger and the duration it takes for the battery to charge from zero to the threshold (e.g., the battery voltage that enables the mobile computing device to respond to the wireless charger). From multiple wireless chargers (e.g., at least four in three-dimensional space), trilateration can be used to determine the three-dimensional location of the mobile computing device. Using this known location, backend payment servers or other systems can use e-wallets, browsers, or other applications on the mobile computing device to manage network nodes (e.g., mobile computing devices) to facilitate location-based transactions (e.g., seating in stadiums, theaters, and other venues, push media content to devices, etc.).

[0006] The processor-implemented method can manage transactions between nodes in a system comprising multiple wireless charging systems. For example, the method may involve a network server's processor receiving charging data corresponding to a mobile computing device. The charging data may include information corresponding to the mobile computing device's charging. The charging data may also include elapsed time for the mobile computing device's communication module to reach a threshold level and send a response to the multiple wireless charging systems in response to reaching the threshold level. The method may also involve the network server's processor determining the location of the mobile computing device based on the location of each of the multiple wireless charging systems and the relationship between the elapsed time and the threshold level. Then, the method may involve the network server's processor sending the location of the mobile computing device to the system's nodes to manage location-based transactions between the mobile computing device and the system's nodes. The mobile computing device may be coupled to multiple wireless charging systems.

[0007] The system can manage transactions between nodes in a system comprising multiple wireless charging systems. The system may include a processor and a memory communicating with the processor, the memory storing instructions that, when executed by the processor, cause the processor to manage the transactions. In some embodiments, the instructions may cause the processor to receive charging data corresponding to a mobile computing device. The charging data may include charging data corresponding to the mobile computing device. The charging data may also include the elapsed time for the mobile computing device's communication module to reach a threshold level (e.g., enabling the mobile computing device to respond to the battery voltage of the wireless charger) and for sending a response to the multiple wireless charging systems in response to reaching the threshold level. Other instructions may send the location of the mobile computing device to the nodes of the system to manage location-based transactions between the mobile computing device and the system's nodes based on the location of the mobile computing device. The mobile computing device may be coupled to multiple wireless charging systems. Attached Figure Description

[0008] For illustrative purposes only, the figures depict preferred embodiments. Those skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods shown herein may be used without departing from the principles described herein.

[0009] Figure 1 An illustration of an exemplary system for managing nodes in a wireless charging network is shown;

[0010] Figure 2A Showing the use of Figure 1 A first view of an exemplary payment device for the system;

[0011] Figure 2B Showing the use of Figure 1 A second view of an exemplary payment device for the system;

[0012] Figure 3 This is a flowchart of a method for managing nodes in a wireless charging system;

[0013] Figure 4 It is an exemplary site comprising multiple wireless charging systems for managing network nodes to facilitate the embodiments described herein; and

[0014] Figure 5 This illustrates a wireless charging system. Figure 1 An exemplary curve showing the relationship between charging time, charging power, and distance in a network;

[0015] Figure 6 It is an exemplary computing device modified to implement the embodiments described herein.

[0016] Those skilled in the art will understand that the elements shown in the figures are for simplicity and clarity, and therefore not all connections and options are shown to avoid obscuring various aspects of the invention. For example, common but well-understood elements that are useful or necessary in commercially viable embodiments are not typically depicted to facilitate viewing of these various embodiments of this disclosure with minimal hindrance. It should be further understood that certain actions and / or steps may be described or depicted in a specific order of occurrence, and those skilled in the art will understand that such specificity regarding order is not actually required. It should also be understood that the terms and expressions used herein are defined relative to their corresponding respective fields of inquiry and research, unless otherwise set forth herein with specific meaning. Detailed Implementation

[0017] The embodiments described herein provide a technical solution to the technical problem of location-based node management in wireless charging networks. The embodiments described herein address this problem by using data from multiple wireless charging systems within a venue to precisely locate mobile computing devices and then facilitating transactions associated with that precise location. For example, the embodiments can be used to facilitate seat-based pricing in theaters or other venues, as location data can be used to determine the exact seat where a mobile computing device is located. Furthermore, the precise location can be used to push media or other content associated with the same location to the device.

[0018] Battery-powered electronic devices can be wirelessly charged over a distance using several methods. For example, inductive technology uses alternating current (AC) in a coil to generate an alternating magnetic field, inducing AC in a nearby secondary coil. If the secondary coil is integrated into the device's battery, it can charge the device's battery. The separation, alignment, and size of the coils significantly affect the efficiency of energy transfer, and practical inductive systems typically achieve efficiencies of around 30-60%. The "Qi" standard is an example of wireless power transfer using inductive charging over distances up to four centimeters. Resonant charging technology can use induction to charge batteries, but can do so over much greater distances. In a resonant charging system, the coil operates at a resonant frequency. The oscillating magnetic field generated by the primary coil induces a current in the secondary coil. However, due to the strong coupling of the resonant coils, current can be induced even when separated by a meter or more. TMResonance is one example of resonant charging technology. Another embodiment uses radio frequency (RF) wireless charging technology. RF wireless charging uses electronic waves or radio frequency, rather than a magnetic field, to charge the device. In an RF charging system, an RF transmitter emits RF waves, and a receiver embedded in the device receives these RF waves. The receiver then converts the RF waves into electricity to power and charge the device. RF wireless charging technology includes far-field and near-field methods. Far-field methods emit electronic waves, and the transmitter (similar to a router network device) positions the RF receiver within a defined area. Near-field methods allow any small enclosed space, such as a drawer or box, to become a transmitter / charging station. The device is placed within the enclosed space and is charged. Of course, facilities can use a combination of various loosely coupled wireless charging technologies, and other loosely coupled wireless charging technologies may be able to charge battery-powered electronic devices at a distance.

[0019] Figure 1 This section generally illustrates one embodiment of a system 100 for location-based node management in a wireless charging network. System 100 may include a computer network 102 linking one or more systems and computer components. In some embodiments, system 100 includes a mobile computing device 104, a wireless charging system 105, a location-based merchant computer system 106, a payment network system 108, a location determination system 110, and a payment device issuer system 111.

[0020] Network 102 can be described in various ways as a communication link, computer network, Internet connection, etc. System 100 may include various software or computer-executable instructions or components stored in tangible memory and dedicated hardware components or modules, which use software and instructions in practical applications to manage network nodes for location-based transactions via wireless charging system 105, as described herein.

[0021] Various modules can be implemented as computer-readable storage devices containing computer-readable instructions (i.e., software) for execution by one or more processors of system 100 within a dedicated or unique computing device. Modules can perform various tasks, steps, methods, blocks, etc., as described herein. System 100 may also include both hardware and software application programs, as well as various data communication channels for transferring data between various dedicated and unique hardware and software components.

[0022] Networks are generally considered to encompass the interconnection and interoperability of hardware, data, and other entities. Computer networks, or data networks, are digital telecommunications networks that allow nodes to share resources. In computer networks, computing devices exchange data with each other using connections between nodes, such as data links. For example, a hardware network may include clients, servers, and intermediate nodes in a graphical topology (e.g., mobile computing device 104, wireless charging system 105, location-based merchant computer system 106, payment network system 108, location determination system 110, and payment device issuer system 111). Similarly, a data network may include data nodes in a graphical topology, where each node includes related or linked information, software methods, and other data. Nodes such as mobile computing device 104 can manage data and instructions from various other nodes in system 100 (e.g., wireless charging system 105, etc.) to facilitate location-based transactions with other nodes in the system (e.g., location-based merchant computer systems).

[0023] It should be noted that, as used throughout this application, the term "server" generally refers to a computer, other device, program, or combination thereof, including a processor and memory, for processing and responding to requests from remote users / nodes across a communication network. The server sends its information to the requesting "client." As used herein, the term "client" generally refers to a computer, program, other device, user, and / or combination thereof capable of processing and issuing requests and receiving and processing any responses from a server via a communication or data network. Computers, other devices, related datasets, programs, or combinations thereof that facilitate, process, and / or facilitate the transfer of information and requests from a source user to a destination user are generally referred to as "nodes." A network is generally considered to facilitate the transfer of information from a source point to a destination. The node specifically responsible for facilitating the transfer of information from the source to the destination is generally referred to as a "router." Networks come in many forms, such as Local Area Networks (LANs), Pico networks, Wide Area Networks (WANs), Wireless Networks (WLANs), etc. For example, the Internet is generally considered to be an interconnection of numerous networks through which remote clients and servers can access and interact with each other.

[0024] Mobile computing device 104 may include smartphone 106 or other computing devices capable of sending and receiving wireless digital communications. The mobile computing device may include processor 145, memory 146, and battery 147. Mobile computing device 106 may include RFID tag 106A or other devices, such as those from a device manufacturer, capable of transmitting radio signals including mobile computing device data, after a certain elapsed time has elapsed since the device communication module 150C has been charged to a threshold battery level sufficient to enable it to respond to the wireless battery charging system 105. The memory 146 of mobile computing device 104 may include various modules including instructions that, when executed by processor 145, substantially control the functionality of mobile computing device 104 and, more specifically, integrate the mobile computing device into system 100. For example, some modules may include operating system 150A, browser module 150B, communication module 150C, and wallet module 150D. Communication module 150C may include processor-executable instructions to send and / or receive signals from contactless components of system 100, such as the wireless charging system 105. In some embodiments, the communication module 150C may include an RFID receiver or instructions for implementing an RFID receiver. The wallet module 150D may also include payment device data 151. Payment device data 151 can securely identify the payment device 200 (FIG. 2) and the user's payment account information to facilitate transactions between the mobile computing device 104 and the location-based merchant computer system 106. In some embodiments, payment device data 151 may be tokenized, allowing only trusted partners to access it. The wallet module 105D may also include instructions for sending charging data 113.

[0025] The wallet module or other modules of mobile computing device 106 may include instructions to facilitate the management of nodes within the wireless charging network based on location and to facilitate location-based transactions. For example, module 150D may include instructions for sending and receiving charging data 113. Module 150D may include instructions for monitoring when device 104 begins charging with a loosely coupled wireless battery charging system (e.g., system 105) for a specified period of time. The instructions may also include instructing transmitting device 104 to reach a threshold battery level 107 of device communication module 150C to be fully charged, enabling it to respond to elapsed time of wireless battery charging system 105 by sending data to another component of system 100 (e.g., location determination system 110). In another embodiment, module 105D may include instructions to periodically send charging data 113 at the threshold battery level or at other times or conditions. The threshold battery level may include the voltage at which the battery 147 for the device communication module 150C is fully charged to enable it to respond to the wireless battery charging system 105, the voltage required to turn on the device 104, the battery level at which the device 104 transitions from a “low power mode” to a regular power mode, the voltage required to complete a transaction between the device 104 and a location-based merchant computer system, or simply, the battery level at a second time compared to a first time. In some embodiments, multiple wireless charging systems 105 (e.g., in a theater or other performance venue) may receive elapsed time until the threshold battery level 107 is reached. In other embodiments, the location determination system 110 may receive charging data 113 from the mobile computing device 104.

[0026] The wireless charging system 105 may also include a processor 108 and a memory 109. Although Figure 1System 100 illustrates a wireless charging system 105, but system 100 may include several systems 105, each simultaneously connected to and charging the mobile computing device 104. Additionally, a mobile computing device threshold battery power level 107 indicating that the device communication module 150C is sufficiently charged to respond to data from the wireless battery charging system 105, and the elapsed time for achieving said level, can be used to accurately locate the mobile computing device 104, as described herein. Processor 108 can execute processor-executable instructions stored in memory 109. The memory 109 of the wireless charging system 105 may include various modules comprising instructions that, when executed by processor 108, substantially control the functionality of the wireless charging system 105 and integrate the wireless charging system 106 into system 100 to particularly facilitate location-based management of network nodes (e.g., mobile computing device 104 and wallet module 150D) in the wireless charging network. For example, some modules may include a charging module 109A, a communication module 109B, and a coordination module 109C. Modules 109A, 109B, and 109C may include instructions to facilitate location-based management of nodes in a wireless charging network and to facilitate location-based transactions between nodes, as described herein. In some embodiments, the modules may include instructions to send charging data 113 of system 105 to one or more other components of system 100. Charging data 113 may include the manufacturer of mobile computing device 104 for determining a threshold battery charge level 107. For example, charging data 113 of wireless charging system 105 may include the charging output of system 105 (e.g., in milliwatts “mW”, or other power expressions), the device communication module 150C being fully charged to enable it to respond to the elapsed time of wireless battery charging system 105, the difference between the battery charge levels of nodes (e.g., mobile computing device 104) when device 104 is connected to multiple wireless charging systems 105 between a first time period and a second time period, and other data for determining the location of mobile computing device 104 or other components of system 100. The location determination system 110 can use a fully charged device communication module 150C to enable it to respond to the elapsed time of the wireless battery charging system 105 to determine the precise location of the mobile computing device 104 within an area including multiple wireless charging systems 105. In other embodiments, the charging power output of the wireless charging system 105 can be used to determine the distance to the mobile computing device 104. For example, as the distance between the wireless charging system 105 and the mobile computing device 104 increases, the power output received by the mobile computing device 105 will decrease. Therefore, the power output from the wireless charging system 105 to a particular battery-powered mobile computing device 104 can indicate the distance to the device 104.

[0027] The coordination module 109C may include instructions to communicate charging data 113 with other wireless charging systems 105 that are also charging a particular mobile computing device 104. For example, when the mobile computing device 104 is connected to two or more wireless charging systems 105, the coordination module 109C may cause the processor 108 to execute instructions to share charging data 113, a threshold battery level 107, and other data relating to the charging actions of the wireless charging systems 105 and other nodes of the system 100 (e.g., other wireless charging systems 105, location determination system 110, etc.), so that multiple wireless charging systems 105 can charge a single mobile computing device 104. The charging data 113 may also include an identifier of the mobile computing system 104, the charging power output of each of the multiple wireless charging systems 105 connected to the particular mobile computing device 104, the elapsed time of the device communication module 150C being fully charged to enable it to respond to the wireless battery charging systems 105, the location of the mobile computing device 104, etc.

[0028] Merchant computer system 106 may include computing devices, such as merchant server 129 including processor 130 and memory 132, the merchant server including components and instruction modules including processor-executable instructions to facilitate transactions between other entities of system 100 and mobile computing device 104. In some embodiments, memory 132 may include transaction communication module 134. Transaction communication module 134 may include sending merchant messages 134A to other entities of system 100 (i.e., 104, 105, 108, 110, 111) to generally indicate that a transaction with mobile computing device 104 has been initiated, and wallet module 150D includes, in particular, payment account data, location data 119, and other data as described herein. For example, nodes of system 100 (e.g., generally mobile computing device 104, and especially browser module 150B) may access location-based merchant website 144 to initiate location-based transactions. Some examples of location-based transactions include ticket sales for specific seats at a venue. Merchant computer system 106 may also include a transaction repository 142 and instructions for storing payment and other transaction data 142A within the transaction repository 142. Merchant computer system 106 may also include a product repository 143 and instructions for storing product and other data 143A within the product repository 143. In some embodiments, merchant computer system 106 may also include instructions for transmitting payment device data 151 corresponding to payment device 200 (FIG. 2), transaction data 143A, and / or product data 143B, as well as other data received during a transaction, from mobile computing device 104 to a payment network system.

[0029] Payment network system 108 may include a payment server 156, which includes a processor 158 and a memory 160. The memory 160 may include a payment network module 162, which includes instructions for facilitating payments between parties (e.g., one or more users, merchants, etc.) using system 100. Module 162 may communicatively connect to an account holder data repository 164, including payment network account data 164A. Payment network account data 164A may include any data used to facilitate payments and other fund transfers between system entities (e.g., 104, 105, 106, 110, and 111). For example, payment network account data 164A may include identification data, account history data, payment device data, etc. Module 162 may also include instructions for sending payment messages 166 to other entities and components of system 100 to complete location-based transactions between mobile computing system 104 and location-based merchant computer system 106. For example, module 162 may include an instruction to send payment message 166 to payment device issuer system 111 or other entity of system 100 to complete a location-based purchase transaction. Message 166 may include data authorizing the purchase transaction, such as an authorization number or other identifier, and may be tokenized or encrypted by system 100 before message 166 is sent to the system entity via network 102.

[0030] Payment device issuer system 111 may include payment device issuer server 170, which includes processor 172 and memory 174. The memory may include payment device issuer module 176, which includes instructions for facilitating payments from system 100 to merchant computer system 106. Module 176 may be communicatively connected to issuer transaction data repository 178, which includes issuer transaction data 178A. Issuer transaction data 178A may include data facilitating the execution by processor 172 of the instructions included in payment device issuer module 176 to facilitate payments and other fund transfers to / from location-based merchant computer system 106 and to / from payment device issuer system 111. In some embodiments, module 176 may include instructions for transferring funds corresponding to a location-based purchase transaction after receiving payment message 166 from payment network system 108. For example, module 176 may include instructions to send an issuer message 182, including data and / or further instructions, to a location-based merchant computer system 106, the instructions implementing or instructing a fund transfer corresponding to a location-based purchase transaction. Issuer transaction data 178A may include merchant identification data, user account history data, etc. Module 176 may also communicatively connect to a cardholder account data repository 180, which includes cardholder account data 180A. Module 176 may also include instructions to receive payment messages 166 from a payment network system 108 to manage nodes of system 100 and complete transactions between users and / or merchants, and to better manage user and merchant fund account balances for location-based transactions.

[0031] Location determination system 110 may include one or more instruction modules, including a positioning module 112. The positioning module typically includes instructions that enable the processor 114 of location server 116 to functionally communicate via network 102 with a plurality of other computer-executable steps or submodules and components of system 100 to facilitate data and instructions based on various other nodes of system 100 (e.g., wireless charging system 105, etc.) and location-based transactions with other nodes of system 100 (e.g., location-based merchant computer system 106, mobile computing device 104, etc.). For example, positioning module 112 may include instructions to determine the distance from wireless charging system 105 to mobile computing device 104. In some embodiments, the instructions may enable the processor of location determination system 110 to map the relationship between the elapsed time to reach a threshold battery power level 107 and the charging power received at device 104 and the time to reach the threshold battery power level 107. Figure 5The distance between the mobile computing device 104 and the wireless charging system 105 is determined by comparison. In another embodiment, the positioning module 112 may include instructions for determining the distance from the plurality of wireless charging systems 105 to the mobile computing device 104 and for using trilateration to determine the three-dimensional position 119 of the mobile computing device 104. The first data repository 122 may store payment network transaction data 122A for all entities of the system 100. In some embodiments, the additional data repository may correspond to different types of payment network transaction data 122A or sub-components of payment network transaction data 122A (e.g., location of a location-based purchase transaction, merchant, account holder, transaction area, transaction type, time of day, merchant and / or customer type, physical device identifier, payment device type, transaction amount, cardholder name, cardholder account number, and other payment network account data 164A, etc.).

[0032] Various other data 124A may be received and / or exported by the location determination system 110 and stored in the second data repository 124, and used by the system 100 as described herein. For example, the second data repository may be used to store e-wallet transaction details 124A from the e-wallet system and wallet module 150D or other methods of electronic or computer-based payment.

[0033] refer to Figure 2A and 2B The exemplary payment device 200 can take various shapes and forms. In some embodiments, the payment device 200 is a traditional card, such as a debit card or credit card. In other embodiments, the payment device 200 can be a keychain clasp, an NFC wearable device, or other devices. In other embodiments, the payment device 200 can be an electronic wallet (e.g., wallet module 150D), in which an account (e.g., payment device data 151) is selected from a plurality of accounts previously stored in the wallet and transmitted to the system 100 to perform a location-based transaction. The payment device 200 is capable of securely communicating with the system 100 and its components. Many traditional payment devices may have to be read by a magnetic stripe reader, and therefore, the size of the payment device 200 may have to be adapted to a magnetic stripe reader. In other instances, the payment device 200 may communicate via near-field communication or other contactless forms of communication. The payment device may include a radio frequency identification (RFID) tag 252 that can be read by the wireless charging system 105.

[0034] Physically, the payment device 200 may be a card, and the card may have multiple layers to include various elements constituting the payment device 200. In one embodiment, the payment device 200 may have a substantially flat front surface 202 and a substantially flat rear surface 204 opposite to the front surface 202. Logically, in some embodiments, surfaces 202, 204 may have some embossing 206 or other forms of clear writing, including a Personal Account Number (PAN) 206A and a Card Validation Number (CVN) 206B. In some embodiments, the payment device 200 may include data corresponding to the primary account holder, such as the account holder's payment network account data 164A. The memory 254 and specifically module 254A may generally be encrypted to ensure that all data related to the payment is secure to unauthorized third parties. A radio frequency identification (RFID) tag 252 may be communicatively coupled to a communication interface 256. Communication interface 256 may include instructions for facilitating the transmission of payment device data 151, payment payload, payment token, or account identifier, or other data for identifying payment device 200, to one or more components of system 100 via network 102. In another embodiment, communication interface 256 may be communicatively coupled to mobile computing device 104 and wallet module 150D to facilitate location-based node management in a wireless charging network as described herein. For example, communication interface 256 may include instructions typically interfaced with mobile computing device 104, and particularly wallet module 105D, to facilitate transactions using payment device 200.

[0035] refer to Figure 3 Method 300 can manage nodes in system 100, including network 102 with multiple wireless charging systems 105, by facilitating location-based transactions between nodes on network 102. Each step of method 300 is performed on the processor of system 100 or a corresponding system component (e.g., mobile computing device 104, wireless charging system 105, location-based merchant computer system 106, payment network system 108, location determination system 110, and payment device issuer system 111, or...). Figure 1 One or more computer-executable instructions (e.g., modules, blocks, steps, stand-alone instructions, or sequences of instructions, etc.) that execute on other computing devices (such as those shown and / or other computer systems described herein) may be physically configured to perform different aspects of the method. Each step may include executing any of the instructions described with respect to method 300 and system 100 as part of the network management system and method described herein or other components internal or external to system 100. Although presented as an ordered set in the following boxes, the various steps described may be executed in any particular order to complete the method described herein.

[0036] At block 302, method 300 can coordinate among multiple wireless charging systems 105 to charge the battery 147 of a node of system 100 (e.g., mobile computing device 104). In some embodiments, method 300 may record the connection time between device 104 and charging system 105. Method 300 can also send and / or receive charging data 113 among multiple other nodes of system 100 (e.g., multiple wireless charging systems 105, location determination system 110, etc.). Method 300 may periodically send the charging data 113 to other system nodes and / or receive the charging data from other system nodes at a threshold battery level 107, etc. In another embodiment, the charging data 113 may include an identifier of the mobile computing device 104 currently being charged by system 105, along with the corresponding charging power output of system 105 at a first time and the battery level of device 104 at a first time. Next, after a period of time has elapsed, a charging threshold has been met, or other measurements have been taken, the method can continue to coordinate among the multiple wireless charging systems 105 by sending charging data 113 at a second, later time. The elapsed time between the first and second time for sending charging data 113 can be any period during which the battery 147 increases its charge due to the connection between the mobile computing device 104 and one or more wireless charging systems 105. The charging data may also include the identification and location of the wireless charging system 105. In some embodiments, method 300 may cause the wallet module 150D of the mobile computing device 104 to send charging data 113 and other data to the location determination system 110.

[0037] refer to Figure 4 Location 400 may include multiple wireless charging systems (e.g., 105A, 105B, 105C, 105D, 105E, 105F, 105G, 105H, etc.). It should be noted that, although... Figure 4 Location 400 includes eight wireless charging systems 105, but other locations may include more or fewer systems 105 to implement the embodiments described and claimed herein. A mobile computing device 104, including a battery 147, may be connected to multiple wireless charging systems 105 (e.g., 105A, 105B, 105C, etc.). Each wireless charging system 105A, 105B, 105C may coordinate with the other described wireless charging systems at block 302.

[0038] return Figure 3At block 304, the location determination system 110 can receive charging data 113 for a single mobile computing device 104, including a response to the wireless charging system 105 indicating that the battery 147 has been fully charged to a threshold battery level 107, enabling the communication module 150C to transmit data 113 to the system 105. Block 304 may also include determining the elapsed time for the battery 147 to reach the threshold battery level 107. The charging data 113 may include an indication of the threshold battery level 107.

[0039] At box 306, method 300 determines the point-to-point distance between (multiple) wireless charging systems (e.g., 105A, 105B, 105C) and mobile computing device 104. (Brief reference) Figure 5 Graph 500 illustrates the relationship between the power output 502 of the wireless charging system 105, the time required to achieve a threshold battery power level 107 for the mobile computing device 104 connected to the wireless charging system 105, and the distance 506 between the mobile computing device 104 and the wireless charging system 105. As shown, as the distance 506 increases, the power output 502 of the wireless charging system 105 decreases, while the time 504 required to achieve the threshold battery power level 107 increases. Using this relationship, the location module 112 of the positioning system 110 can execute instructions to determine the point-to-point distance between (multiple) wireless charging systems (e.g., 105A, 105B, 105C) and the mobile computing device 104 based on charging data 113. The advantage of using the charging time 504 instead of RF communication travel time, GPS, and other positioning technologies for this location determination is that the time 504 for the connected battery 147 of the mobile computing device 104 to achieve the threshold battery power level 107 is much longer than the RF travel time (e.g., the speed of light). Therefore, compared to using other location technologies, the measurement error of the point-to-point distance between each pair of the mobile computing device 104 and its connected wireless charging system 105 will be much lower, resulting in better location accuracy.

[0040] At box 308, method 300 can determine the position 119 of mobile computing device 104. Based on charging data 113 for multiple mobile computing device / wireless charging system pairs, the method can use trilateration to determine the three-dimensional position 119 of mobile computing device 104. For example, referring to... Figure 5Given a relationship between the time 504 for achieving a threshold battery level 147 and the distance from the mobile computing device 104 to the wireless charging system 105, charging data 113 received by the location determination system 110 can indicate the location of a node (e.g., the mobile computing device 104) (e.g., the distance 506 between the mobile computing device 104 and the wireless charging system 105), wherein the charging data 113 includes at least the elapsed time 504 for reaching the threshold battery level 107. In some embodiments, trilateration can determine the absolute or relative location of a point by measuring the distance between the wireless charging system 105 and the connected mobile computing device 104 using the geometry of a circle, sphere, or triangle. For example, the intersection of three circles or spheres representing the distance from the wireless charging system 105 to the mobile computing device 104 can indicate the location 119 of the mobile computing device 104.

[0041] At block 310, method 300 may use the location determined by block 308 to manage transactions between one or more nodes of system 100. In some embodiments, a node of system 100 may transmit the location 119 of wireless computing device 104 (as determined at blocks 306 and 308 of method 300) to another node of system 100. For example, in some embodiments, wallet module 150D, location determination system 110, or other components of system 100 may transmit location 119 to browser module 150B, location-based merchant computer system 106 (e.g., transaction communication module 134), or other nodes of system 100. Location 119 may then be used to facilitate location-based transactions between nodes of system 100. In some embodiments, location 119 corresponds to product 143A of product repository 143. Location 119 may then be used to manage or facilitate transaction 142A between nodes of system 100 (e.g., mobile computing device 104 and location-based merchant computer system 106).

[0042] In another embodiment, block 310 may include, typically, a mobile computing device 104, and in particular, a browser module 150B, accessing a merchant website 144 to initiate a location-based transaction. Location-based transactions may include any communication between nodes of system 100 that requires determining the precise location 119 of the mobile computing device 104. In some embodiments, location-based transactions may include a purchase transaction for a location-based product, such as a ticket within venue 400. Figure 4The location includes multiple wireless charging systems 105 at locations indicated by location data 119. In other embodiments, location-based transactions may include pushing media (e.g., marketing data, data for location-based site browsing, etc.) to mobile computing device 104 based on the precise location 119 determined by location determination system 110. Method 300 may use location 119 to identify product 143A and may manage or facilitate purchases or other transactions between nodes of system 100.

[0043] In location-based purchasing transactions, venue 400 may use seat-based pricing instead of zone- or area-based pricing. Participants in events at venue 400 may access venue 400’s ticket purchasing application using mobile computing device 104. Box 310 may include instructions for seat selection to be purchased via the ticket purchasing application or wallet module 150D based on the location 119 of mobile computing device 104 determined by location determination system 110. Furthermore, when multiple wireless charging systems 105 are present near device 104, historical sites, tourist routes, or other location-based merchants (including location-based points of interest or other location-based items) may use location 119 to push media to mobile computing device 104.

[0044] Therefore, the embodiments described herein provide a technical solution to the technical problem of location-based node management in wireless charging networks. The embodiments described herein address this problem by using data from multiple wireless charging systems within a location to accurately locate a mobile computing device and then facilitate transactions associated with that precise location. The charging time 504 of each wireless charging system 105 connected to the mobile computing device, rather than RF communication travel time or other location technologies, can be used to determine the location. For example, the time 504 for the connected battery 147 of the mobile computing device 104 to reach a threshold charge is much longer than the RF travel time (e.g., the speed of light). Therefore, compared to using RF travel time technologies, the measurement error of the point-to-point distance between the mobile computing device 104 and each paired wireless charging system 105 will be much lower, resulting in better location accuracy. For example, the embodiments can be used to facilitate seat-based pricing in theaters or other venues, as location data can be used to determine the exact seat where the mobile computing device is located. Furthermore, the precise location can be used to push media or other content associated with the same location to the device.

[0045] Figure 6This is a high-level block diagram of an instance computing environment 900 used for system 100 and the methods described herein (e.g., method 300). The computing device 900 may include a server, mobile computing device, cellular phone, tablet computer, Wi-Fi-enabled device or other personal computing device capable of wireless or wired communication, thin client, or other known types of computing device (e.g., mobile computing device 104, wireless charging system 105, location-based merchant computer system 106, payment network system 108, location determination system 110, and payment device issuer system 111, etc.). Logically, the computing device 900 may be designed and constructed to specifically perform certain tasks.

[0046] Those skilled in the art will recognize that, in light of this disclosure and the teachings herein, other types of computing devices with different architectures can be used. Processor systems similar to or identical to the example systems and methods described herein can be used to implement and execute the example systems and methods described herein. Although example system 900 is described below as including multiple peripheral devices, interfaces, chips, memory, etc., one or more of those elements may be omitted from other example processor systems used to implement and execute the example systems and methods. Furthermore, other components may be added.

[0047] like Figure 6 As shown, computing device 901 includes processor 902 coupled to an interconnect bus. Processor 902 includes a register set or register space 904, which... Figure 6 The device is depicted as being entirely on-chip, but it may alternatively be wholly or partially off-chip and directly coupled to processor 902 via dedicated electrical connections and / or via an interconnect bus. Processor 902 can be any suitable processor, processing unit, or microprocessor. Although Figure 6 Although not shown, computing device 901 may be a multiprocessor device and may therefore include one or more additional processors that are the same as or similar to processor 902 and are communicatively coupled to an interconnect bus.

[0048] Figure 6The processor 902 is coupled to a chipset 906, which includes a memory controller 908 and a peripheral input / output (I / O) controller 910. Chipsets typically provide I / O and memory management functions, as well as multiple general-purpose and / or special-purpose registers, timers, etc., that can be accessed or used by one or more processors coupled to the chipset 906. The memory controller 908 performs functions that enable the processor 902 (or multiple processors if there are multiple processors) to access system memory 912 and mass storage 914, which may include either or both of in-memory caches (e.g., caches within memory 912) or on-disk caches (e.g., caches within mass storage 914).

[0049] System memory 912 may include any desired type of volatile and / or non-volatile memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), flash memory, read-only memory (ROM), etc. Mass storage 914 may include any desired type of mass storage device. For example, computing device 901 may be used to implement module 916 (e.g., the various modules described herein). Mass storage 914 may include hard disk drives, optical disk drives, magnetic tape storage devices, solid-state memories (e.g., flash memory, RAM, etc.), magnetic memories (e.g., hard disk drives), or any other memory suitable for mass storage. As used herein, the terms module, block, function, operation, process, routine, step, and method refer to tangible computer program logic or tangible computer-executable instructions that provide the specified function for computing device 901, system, and methods described herein. Therefore, modules, blocks, functions, operations, processes, routines, steps, and methods may be implemented in hardware, firmware, and / or software. In one embodiment, program modules and routines are stored in mass storage 914, loaded into system memory 912 and executed by processor 902, or can be provided from a computer program product stored in a tangible computer-readable storage medium (e.g., RAM, hard disk, optical / magnetic media, etc.).

[0050] The peripheral I / O controller 910 performs the function of enabling the processor 902 to communicate with the peripheral input / output (I / O) device 924, the network interface 926, and the local network transceiver 928 (via the network interface 926) via the peripheral I / O bus. The I / O device 924 can be any desired type of I / O device, such as a keyboard, a display (e.g., a liquid crystal display (LCD), a cathode ray tube (CRT) display, etc.), a navigation device (e.g., a mouse, a trackball, a capacitive touchpad, a joystick, etc.), etc. The I / O device 924 can be used, along with modules such as 916, to receive data from the transceiver 928, transmit data to components of the system 100, and perform any operations related to the methods described herein. The local network transceiver 928 may include support for Wi-Fi networks, Bluetooth, infrared, cellular, or other wireless data transmission protocols. In other embodiments, a single element may simultaneously support each of the various wireless protocols employed by the computing device 901. For example, a software-defined radio may be able to support multiple protocols via downloadable instructions. In operation, computing device 901 may be able to periodically poll visible wireless network transmitters (both cellular and local networks) on a periodic basis. This polling may be possible even when computing device 901 supports normal wireless traffic. Network interface 926 may be, for example, an Ethernet device, an Asynchronous Transfer Mode (ATM) device, an 802.11 wireless interface device, a DSL modem, a cable modem, a cellular modem, etc., enabling system 100 to communicate with another computer system having at least the elements described with respect to system 100.

[0051] Although the memory controller 908 and I / O controller 910 are in Figure 6 The module 916 is depicted as a separate functional block within chipset 906, but the functions performed by these blocks can be integrated into a single integrated circuit, or implemented using two or more separate integrated circuits. The computing environment 900 can also implement module 916 on remote computing device 930. Remote computing device 930 can communicate with computing device 901 via Ethernet link 932. In some embodiments, module 916 can be retrieved by computing device 901 from cloud computing server 934 via Internet 936. When using cloud computing server 934, the retrieved module 916 can be programmatically linked to computing device 901. Module 916 can be a collection of various software platforms, including artificial intelligence software and document creation software, or it can be a module residing in computing device 901 or remote computing device 930. Executed within a virtual machine (JVM) environment Mini-program. Module 916 may also be a "plugin" suitable for execution in a web browser located on computing devices 901 and 930. In some embodiments, module 916 may communicate with backend component 938 via Internet 936.

[0052] System 900 may include, but is not limited to, any combination of LAN, MAN, WAN, mobile network, wired or wireless network, private network or virtual private network. Furthermore, although in Figure 6 Only one remote computing device 930 is shown in the description to simplify and clarify the instructions, but it should be understood that any number of client computers are supported and can communicate within the system 900.

[0053] Additionally, certain embodiments herein are described as comprising logic or a plurality of components, modules, blocks, or mechanisms. Modules and method blocks may constitute software modules (e.g., code or instructions embodied on a machine-readable medium or embodied as transmitted signals, wherein the code is executed by a processor) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. In exemplary embodiments, one or more computer systems (e.g., standalone client or server computer systems) or one or more hardware modules (e.g., processors or groups of processors) of a computer system may be configured as hardware modules by software (e.g., an application or a portion of an application) that operate to perform certain operations as described herein.

[0054] In various embodiments, the hardware module may be implemented mechanically or electronically. For example, the hardware module may include dedicated circuitry or logic that is permanently configured (e.g., as a dedicated processor, such as a field-programmable gate array (FPGA)) or application-specific integrated circuit (ASIC) to perform certain operations. The hardware module may also include programmable logic or circuitry systems that are temporarily configured by software to perform certain operations (e.g., as encompassed within a processor or other programmable processor). It should be understood that the decision to implement the hardware module mechanically, in a dedicated and permanently configured circuitry system, or in a temporarily configured circuitry system (e.g., by software configuration) may be driven by cost and time considerations.

[0055] Therefore, the term "hardware module" should be understood to encompass tangible entities that are physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate or perform certain operations described herein. As used herein, "hardware-implemented module" refers to a hardware module. Considering embodiments in which hardware modules are temporarily configured (e.g., programmed), it is not necessary to configure or instantiate each of the hardware modules at any given time. For example, in cases where a hardware module includes a processor configured by software, the processor can be configured as a corresponding different hardware module at different times. The software can therefore configure the processor, for example, to constitute a particular hardware module at one time and a different hardware module at different times.

[0056] Hardware modules can provide information to and receive information from other hardware modules. Therefore, the described hardware modules can be considered as communicatively coupled. When multiple such hardware modules exist simultaneously, communication can be achieved through signal transmissions connecting the hardware modules (e.g., via suitable circuitry and buses). In embodiments where multiple hardware modules are configured or initialized at different times, communication between these modules can be achieved, for example, by storing and retrieving information in a memory structure accessible to the multiple hardware modules. For example, a hardware module can perform an operation and store the output of that operation in a memory device, to which it is communicatively coupled. Another hardware module can then subsequently access the memory device to retrieve and process the stored output. Hardware modules can also initiate communication with input or output devices and can operate on resources (e.g., collections of information).

[0057] The various operations of the example methods described herein can be performed at least in part by one or more processors, which may be temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, these processors may constitute processor-implemented modules that operate to perform one or more operations or functions. In some example embodiments, the modules mentioned herein may include processor-implemented modules.

[0058] Similarly, the methods or routines described herein may be implemented at least in part by a processor. For example, at least some operations of the methods may be performed by one or more processors or processor-implemented hardware modules. The performance of certain operations may be distributed across one or more processors, residing not only within a single machine but also deployed across multiple machines. In some exemplary embodiments, one or more processors may reside in a single location (e.g., in a home environment, office environment, or server cluster), while in other embodiments, processors may be distributed across multiple locations.

[0059] One or more processors may also operate performance to support “cloud computing” environments or related operations in “Software as a Service” (SaaS). For example, at least some operations may be performed by a group of computers (as instances of machines including processors) that are accessible via a network (e.g., the Internet) and through one or more appropriate interfaces (e.g., application programming interfaces (APIs)).

[0060] The performance of certain operations can be distributed across one or more processors, residing not only within a single machine but also deployed across multiple machines. In some exemplary embodiments, one or more processors or processor-implemented modules may reside in a single geographic location (e.g., within a home environment, an office environment, or a server cluster). In other exemplary embodiments, one or more processors or processor-implemented modules may be distributed across multiple geographic locations.

[0061] Parts of this specification are presented based on algorithms or symbolic representations of operations on data stored as bit or binary digital signals in machine memory (e.g., computer memory). These algorithms or symbolic representations are examples of techniques used by those skilled in the art of data processing to communicate the substance of their work to others skilled in the art. As used herein, an "algorithm" is a self-consistent sequence of operations or similar processes that produces a desired result. In this context, algorithms and operations involve the physical manipulation of physical quantities. Typically, but not necessarily, such quantities may be in the form of electrical, magnetic, or optical signals that can be stored, accessed, transmitted, combined, compared, or otherwise controlled by a machine. Primarily for common use, it is sometimes convenient to refer to such signals using terms such as "data," "content," "bit," "value," "element," "symbol," "character," "item," "number," "digit," etc. However, these terms are merely convenient labels and will be associated with appropriate physical quantities.

[0062] Unless otherwise specifically indicated, the use of terms such as “processing,” “computing,” “operation,” “determining,” “presenting,” and “displaying” in this document may refer to the actions or processes of a machine (e.g., a computer) that controls or converts data into physical (e.g., electrical, magnetic, or optical) quantities within one or more memories (e.g., volatile memory, non-volatile memory, or a combination thereof), registers, or other machine components that receive, store, transmit, or display information.

[0063] As used herein, any reference to “embodiment,” “some embodiments,” “an embodiment,” or “teaching” in connection with an embodiment describes a particular element, feature, structure, or characteristic that is included in at least one embodiment. The phrases “some embodiments” or “teaching” appearing in different places in this specification do not necessarily refer to the same embodiment.

[0064] The terms "coupling" and "connection," as well as their derivatives, can be used to describe some embodiments. For example, the term "coupling" can be used to describe some embodiments to indicate that two or more elements are in direct physical or electrical contact. However, the term "coupling" can also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other. Embodiments are not limited in this context.

[0065] Furthermore, the preferred embodiments are depicted in the figures for illustrative purposes only. Those skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods shown herein can be employed without departing from the principles described herein.

[0066] Upon reading this disclosure, those skilled in the art will understand, through the principles disclosed herein, additional alternative structural and functional designs for the systems and methods described herein. Therefore, while specific embodiments and applications have been shown and described, it should be understood that the disclosed embodiments are not limited to the precise constructions and components disclosed herein. Various modifications, alterations, and variations may be made to the arrangement, operation, and details of the systems and methods disclosed herein without departing from the spirit and scope defined by any of the appended claims, as will be apparent to those skilled in the art.

Claims

1. A processor-implemented method for managing transactions between nodes in a system comprising multiple wireless charging systems, the method comprising: The processor of the network server receives charging data corresponding to the mobile computing device, the charging data corresponding to the mobile computing device, the charging data including the elapsed time when the communication module of the mobile computing device reaches a threshold level and sends a response to the plurality of wireless charging systems in response to reaching the threshold level; The location of the mobile computing device is determined by the processor of the network server based on the location of each of the plurality of wireless charging systems and the relationship between the elapsed time and the threshold level; as well as The processor of the network server sends the location of the mobile computing device to the nodes of the system to manage location-based transactions between the mobile computing device and the nodes of the system based on the location of the mobile computing device. The mobile computing device is coupled to the plurality of wireless charging systems.

2. The method of claim 1, wherein the threshold level includes enabling the mobile computing device to respond to the battery voltage of the plurality of wireless charging systems.

3. The method of claim 2, wherein the plurality of wireless charging systems comprises at least three wireless charging systems, and the location-based transaction comprises a transaction between the mobile computing device and a location-based merchant computer system using the location of the mobile computing device.

4. The method of claim 3, wherein the elapsed time for the communication module to reach the threshold level includes the elapsed time for the battery of the mobile computing device to reach the threshold level.

5. The method of claim 4, wherein determining the location of the mobile computing device based on the elapsed time of the communication module of the mobile computing device reaching the threshold level further comprises using the elapsed time of the communication module of the mobile computing device reaching the threshold level to determine the distance between the mobile computing device and each of the plurality of wireless network systems.

6. The method of claim 5, wherein determining the location of the mobile computing device based on the elapsed time when the communication module of the mobile computing device reaches the threshold level further comprises performing a trilateration among the at least three wireless charging systems based on the location of each of the plurality of wireless charging systems and the relationship between the elapsed time when the communication module of the mobile computing device reaches the threshold level and the threshold level.

7. The method of claim 6, wherein using the location of the mobile computing device to manage the location-based transaction between the mobile computing device and the location-based merchant computer system includes transmitting the location to the location-based merchant computer system.

8. The method of claim 7, wherein the location corresponds to a product of the location-based merchant computer system.

9. The method of claim 1, further comprising coordinating the plurality of wireless charging systems by the processor of the network server.

10. The method of claim 1, wherein the charging data includes an identifier of the mobile computing device.

11. A system for managing transactions between nodes of a system comprising multiple wireless charging systems, the system comprising: A processor and a memory in communication with the processor, the memory storing instructions that, when executed by the processor, cause the processor to: Receive charging data corresponding to a mobile computing device, the charging data including the elapsed time when the communication module of the mobile computing device reaches a threshold level and sends a response to the plurality of wireless charging systems in response to reaching the threshold level. The location of the mobile computing device is determined based on the location of each of the plurality of wireless charging systems and the relationship between the elapsed time and the threshold level; The location of the mobile computing device is sent to the nodes of the system to manage location-based transactions between the mobile computing device and the nodes of the system based on the location of the mobile computing device. The mobile computing device is coupled to the plurality of wireless charging systems.

12. The system of claim 11, wherein the threshold level includes enabling the mobile computing device to respond to the battery voltage of the plurality of wireless charging systems.

13. The system of claim 12, wherein the plurality of wireless charging systems comprises at least three wireless charging systems, and the location-based transaction comprises a transaction between the mobile computing device and a location-based merchant computer system using the location of the mobile computing device.

14. The system of claim 13, wherein the elapsed time for the communication module to reach the threshold level includes the elapsed time for the battery of the mobile computing device to reach the threshold level.

15. The system of claim 14, wherein the instruction to determine the location of the mobile computing device based on the elapsed time when the communication module of the mobile computing device reaches the threshold level further includes using the elapsed time when the communication module of the mobile computing device reaches the threshold level to determine the distance between the mobile computing device and each of the plurality of wireless network systems.

16. The system of claim 15, wherein the instruction to determine the location of the mobile computing device based on the elapsed time when the communication module of the mobile computing device reaches the threshold level further comprises performing a trilateration among the at least three wireless charging systems based on the location of each of the plurality of wireless charging systems and the relationship between the elapsed time when the communication module of the mobile computing device reaches the threshold level and the threshold level.

17. The system of claim 16, wherein using the location of the mobile computing device to manage the location-based transaction between the mobile computing device and the location-based merchant computer system includes transmitting the location to the location-based merchant computer system.

18. The system of claim 17, wherein the location corresponds to a product of the location-based merchant computer system.

19. The system of claim 18, further comprising coordinating the plurality of wireless charging systems by a network server.

20. The system of claim 19, wherein the charging data includes an identifier of the mobile computing device.

Images