WO2019036094A1 - Code lisible par machine audible - Google Patents

Code lisible par machine audible Download PDF

Info

Publication number
WO2019036094A1
WO2019036094A1 PCT/US2018/037751 US2018037751W WO2019036094A1 WO 2019036094 A1 WO2019036094 A1 WO 2019036094A1 US 2018037751 W US2018037751 W US 2018037751W WO 2019036094 A1 WO2019036094 A1 WO 2019036094A1
Authority
WO
WIPO (PCT)
Prior art keywords
computing device
audio token
user
data
audio
Prior art date
Application number
PCT/US2018/037751
Other languages
English (en)
Other versions
WO2019036094A8 (fr
Inventor
Arjita MADAN
Sumit Gwalani
Caesar Sengupta
Original Assignee
Google Llc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Google Llc filed Critical Google Llc
Priority to CN201880053311.0A priority Critical patent/CN110998637A/zh
Publication of WO2019036094A1 publication Critical patent/WO2019036094A1/fr
Publication of WO2019036094A8 publication Critical patent/WO2019036094A8/fr

Links

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
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0241—Advertisements
    • G06Q30/0251—Targeted advertisements
    • 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/327—Short range or proximity payments by means of M-devices
    • G06Q20/3272—Short range or proximity payments by means of M-devices using an audio code
    • 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/327—Short range or proximity payments by means of M-devices
    • G06Q20/3274—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being displayed on the M-device

Definitions

  • the technology disclosed herein relates to broadcasting computing devices, and particularly to transmitting information using audio tokens broadcast via broadcasting computing devices.
  • Broadcasting computing devices having speakers that emit data via audio communication channels are located at a variety of important locations, including subway stops, bus stops, and other points of interest.
  • users may desire to perform an action such as processing a service request, viewing advertising, or viewing other useful information via user computing devices. For example, at a subway stop or a bus stop, a user may desire to obtain a ticket.
  • QR codes are displayed in many places, such as at service system locations or at points of interest.
  • there are usability issues with QR codes especially in scenarios that involve poorly lit environments, where displayed QR codes are damaged, or where user computing devices are not capable of scanning a QR code.
  • Audio communication has a much better technical and usability characteristic and can be applied in similar situations in which a QR code could be displayed.
  • Techniques herein provide a computer-implemented method to transmit audio tokens, comprising: receiving, by one or more computing devices, data and a request to generate an audio token to associate with the data from a computing system; generating, by the one or more computing devices, the audio token; associating, by the one or more computing devices, the audio token with the received data; transmitting, by the one or more computing devices, the audio token to the computing system, wherein the computing system configures a merchant computing device at a location to broadcast the audio token to a user computing device via an audio communication channel; receiving, by the one or more computing devices, the audio token from the user computing device; retrieving, by the one or more computing devices, the data associated with the audio token; and transmitting, by the one or more computing devices, at least part of the data to the user computing device.
  • Figure 1 is a block diagram depicting a system to receive, by a user computing device, audio token data associated with an audio token transmitted by a merchant computing device, in accordance with certain examples.
  • Figure 2 is a block flow diagram depicting a method to receive, by a user computing device, audio token data associated with an audio token transmitted by a merchant computing device, in accordance with certain examples.
  • Figure 3 is a block flow diagram depicting a method to register, by a merchant system, for an account with an account management system and downloading an advertising application on a merchant computing device, in accordance with certain examples.
  • Figure 4 is a block flow diagram depicting a method to register, by a user, for an account with an account management system and download an advertising application onto a user computing device, in accordance with certain examples.
  • Figure 5 is a block flow diagram depicting a method to receive, by a user computing device, an audio token and extract audio token data using a QR code library, in accordance with certain examples.
  • Figure 6 is a block diagram depicting a computing machine and module, in accordance with certain examples.
  • Examples herein provide computer-implemented techniques for receiving, by a user computing device, audio token data associated with an audio token transmitted by a merchant computing device.
  • a merchant system configures an audio token comprising audio token data with an account management system.
  • the merchant system transmits audio token data to the account management system and a request for an audio token via a network.
  • Example audio token data comprises an advertisement, transaction details, public service information, a uniform resource locator ("URL") for a website, or other relevant information to be broadcast by a merchant computing device at a merchant system location or at a point of interest.
  • a merchant computing device may comprise a broadcasting computing device.
  • Example transaction details comprise an identification of an item to be purchased, a total amount of a transaction, and payment account information associated with the account management system.
  • the account management system receives the audio token data and the request for the audio token from the merchant system via the network.
  • the audio token data comprises a uniform resource locator ("URL") for a website.
  • the account management system stores the received audio token data, generates an audio token, and associates the generated token with the stored audio token data.
  • the audio token comprises a random number comprising an alphanumeric and/or symbolic string of characters and the account management system generates the audio token via a random number generator.
  • the account management system stores the audio token and the associated audio token data in an audio token list maintained in a data storage unit accessible to the account management system, where the audio token list comprises a list that associates generated audio tokens with audio token data associated with each generated audio token.
  • a merchant system generates an audio token, associates the audio token with audio token data stored by the merchant system or generated by the merchant system, and transmits the audio token along with the audio token data to the account management system via the network.
  • the audio token comprises a random number comprising an alphanumeric and/or symbolic string of characters.
  • the merchant system generates the audio token via a random number generator.
  • the merchant system stores the audio token and the associated audio token data in an audio token list maintained in a data storage unit accessible to the merchant system.
  • the audio token list comprises a listing of generated audio tokens and associated audio token data corresponding to each audio token generated by the advertising system.
  • the account management system receives the audio token and the audio token data via the network, associates the audio token with the audio token data, and stores the audio token and the associated audio token data.
  • the advertising system maintains a list of audio tokens with associated stored audio token data.
  • the account management system stores the audio token and the associated audio token data in an audio token list maintained in a data storage unit accessible to the account management system, where the audio token list comprises a list that associates received audio tokens with received audio token data associated with each received audio token.
  • a merchant system comprises a QR code library stored on a data storage unit on the merchant computing device or accessible to the merchant computing device.
  • the QR code library comprises a database.
  • the QR code library is stored on a data storage unit on the account management system.
  • the QR code library is stored on the merchant system, one or more user computing devices, and the account management system, or is otherwise accessible to the merchant system, to the one or more user computing devices, and to the account management system.
  • the account management system, the merchant system, and/or the merchant computing device are able to communicate with the QR code library and/or a device or data storage unit comprising the QR code library.
  • the account management system, and/or the merchant computing device can otherwise read or access information in the QR code library.
  • the merchant system defines an audio token with the QR code library and associates an advertisement, a website, or other audio token data with the audio token in the QR code library.
  • the merchant system may define the audio token using an application on the merchant computing device that communicates with the QR code library.
  • the merchant system defined an audio token to associate with audio token data comprising a uniform resource locator ("URL") for a website.
  • URL uniform resource locator
  • the QR code library on the merchant computing device in response to a merchant system operator selecting an option to define the audio token via the QR code library, the QR code library on the merchant computing device generates an audio token to associate with the advertisement, website, or the other audio token data that the merchant system desires to associate with the audio token.
  • one or more user computing devices comprise advertising applications that also comprise the audio QR code library or are able to access the QR code library via the network.
  • the merchant system defines the audio token with the QR code library using an application on the merchant computing device, the merchant system communicates with an account management system via the network to update the QR code library stored on the account management system, and the account management system communicates via the network with the one or more user computing devices to synchronize the merchant QR code library with each of the QR code libraries on the respective one or more user computing devices.
  • the merchant system configures a merchant computing device to broadcast the audio token at a location.
  • the location comprises a brick and mortar store location of the merchant system or a point of interest, for example, a point of interest comprising a subway or train station where the merchant system desires to conduct an advertising campaign.
  • the merchant computing device broadcasts the audio token at a location.
  • One or more user computing devices comprising an application receive the broadcast audio token and retransmit the audio token to the account management system via a network.
  • the merchant computing device comprises an audio component capable of sound output, for example, an audio speaker capable of generating an audible sound output or ultrasound output.
  • a user computing device comprising an advertising application receives audio tokens when the user is signed in to the advertising application. For example, a user having an account with the account management system selects an advertising application on the user computing device and signs into an advertising application on the user computing device using a username and a password. The advertising application communicates with the account management system via a network when the user is signed in to the advertising application. The advertising application activates a microphone component of the user computing device to listen for data transmitted over audio communication channels. In an example, the user signs in to the advertising application and the advertising application activates the microphone component of the user computing device in response to receiving an indication that the user signed in to the advertising application. The user computing device receives, via the microphone component, the audio token broadcasted by the merchant computing device.
  • the advertising application transmits the received audio token to the account management system via the network along with a request for advertising data associated with the audio token.
  • an account management system receives the audio token from a particular user computing device over the network.
  • the particular user computing device received the audio token transmitted at the location of the merchant computing device and then transmitted the audio token to the account management system via the network.
  • the account management system receives the retransmitted audio token and the request for advertising data associated with the audio token.
  • the account management system determines that the received audio token matches a stored audio token previously configured by a merchant system, and extracts the audio token data associated with the audio token. For example, the account management system maintains a list in a data storage unit that lists the audio token data associated with each audio token. In an example, the account management system extracts the audio token data associated with the audio token.
  • Example extracted audio token data comprises a URL, advertisement data, or other audio token data.
  • the account management system transmits the extracted audio token data comprising a URL to the user computing device over the network along with instructions to the user computing device to access a website associated with the URL or instructions to prompt the user to approve the user computing device accessing the website associated with the URL.
  • Other example extracted audio token data comprises public service data.
  • public service data comprises an alert issued by a public service or other service such as a traffic alert, emergency alert, or weather alert. In this example, the account management system transmits the alert information to the user computing device to be displayed on the user computing device for the user.
  • the user computing device instead of receiving, by the user computing device, the broadcast audio token and then retransmitting the received audio token to the account management system over the network, receives the audio token and compares the audio token to multiple audio tokens stored in a QR code library on the user computing device.
  • the user computing device is logged into the advertising application, receives the audio token broadcast by the merchant computing device, and determines that the received audio token corresponds to a particular stored audio token in the QR code library stored on the user computing device or otherwise accessible to the user computing device via the network.
  • the user computing device extracts particular audio token data associated with the particular stored audio token in the QR code library.
  • the extracted particular audio token data comprises a URL, advertising data, public service data, or other audio token data.
  • the user computing device displays or otherwise executes instructions in accordance with the extracted particular audio token data.
  • the user computing device accesses and displays a website associated with audio token data comprising an extracted URL associated with the particular stored audio token.
  • data contained in a QR code may be transmitted over audio communication channels. Therefore everywhere that a QR code is shown (in marketing assets / websites / store fronts), and where the provision is available, an audio token may be broadcast as an alternative to a QR code. If a user with a user computing device, such as a smartphone, is in the vicinity of the displayed QR code, an application on the user computing device can decode the embedded information using the QR code library and take the same action as the QR code would have directed the user computing device to take. For example, redirect the user computing device to the website embedded in the audio code. The degree to which this exchange is controlled by the user can be adjusted or defined.
  • audio communication has usability benefits over scanning a QR code for a user computing device, since audio communication does not require the user to load a camera or focus on the QR code using the user computing device. Further, audio communication provides for a higher range and scope for bidirectional communication than scanning QR codes.
  • a merchant system can preconfigure an audio token by associating the audio token with audio token data, such as a URL, and transmit the preconfigured audio token to the account management system along with the audio token data over a network.
  • the merchant system then broadcasts the audio token using the merchant computing device via an audio communication channel at a merchant location.
  • a user computing device associated with a user receives the audio token broadcast at the merchant location via an audio communication channel and transmits the received audio token to the account management system via the network.
  • a QR code library is stored on an application on the merchant computing device.
  • a merchant computing device operator defines the audio token with the library and associates the audio token data with the defined audio token.
  • the QR code library on the merchant computing device communicates with the account management system via the network and multiple user computing devices, also comprising the QR code library, communicate over the network with the account management system.
  • the account management system synchronizes each of the respective user computing device QR code libraries when any particular QR code library, whether the merchant system QR code library, account management system QR library code database, or user computing device QR code library, is updated.
  • User device application also has access to the library.
  • a user computing device receives the audio token broadcast at the merchant location and then the advertising application on the user computing device uses the QR code library to identify audio token data stored on the QR code library associated with the received audio token.
  • the user device displays the stored data or otherwise executes instructions in accordance with the stored audio token data, for example, by accessing a website associated with the stored audio token data when the stored audio token data comprises a URL.
  • the user computing device communicates with the account management system via the network to request and receive the audio token data associated with the received audio token from the QR code library stored on the account management system.
  • the merchant system and the account management system provide the capability to transmit data to user computing devices via audio communication channels at points of interest by broadcasting audio tokens.
  • the systems and methods described herein enables transmitting an indication of data via audio communication channels to user computing devices at appropriate locations at which advertising systems desire user computing devices to receive data.
  • the merchant system, the user computing device, and the account management system enable a user to receive relevant information at merchant system locations or at points of interest directly on a user computing device without having to manually scan QR codes, request information from employees, or provide inputs on the user computing device to search for and access websites to receive information.
  • the methods and systems described herein reduce inputs required by users with respect to user computing devices to receive relevant information at merchant system locations or at points of interest. Further, by using and relying on the methods and systems described herein, the merchant system and the account management system enable the merchant system to increase locations at which advertising data may be transmitted by enabling transmission via any sound-emitting merchant computing device and reduce the cost of transmitting data by only having to transmit an audio token associated with data that may be exchanged by the user computing device with the account management system for the associated data.
  • FIG. 1 is a block diagram depicting a system 100 for receiving, by a user computing device, audio token data associated with an audio token transmitted by a merchant computing device, in accordance with certain examples.
  • the system 100 comprises network computing devices 110, 130, 140, and 150 that are configured to communicate with one another via one or more networks 120 or audio communication channels.
  • a user associated with a device must install an application and/or make a feature selection to obtain the benefits of the techniques described herein.
  • the network 120 can include a local area network (“LAN”), a wide area network (“WAN”), an intranet, an Internet, storage area network (“SAN”), personal area network (“PAN”), a metropolitan area network (“MAN”), a wireless local area network (“WLAN”), a virtual private network (“VPN”), a cellular or other mobile communication network, Bluetooth, Bluetooth low energy (“BLE”), near field communication (“NFC”), ultrasound communication, or any combination thereof or any other appropriate architecture or system that facilitates the communication of signals, data, and/or messages.
  • LAN local area network
  • WAN wide area network
  • MAN metropolitan area network
  • VPN virtual private network
  • Bluetooth Bluetooth low energy
  • NFC near field communication
  • ultrasound communication or any combination thereof or any other appropriate architecture or system that facilitates the communication of signals, data, and/or messages.
  • Each network computing device 110, 130, 140, and 150 includes a device having a communication module capable of transmitting and receiving data over the network 120.
  • each network computing device 110, 130, 140, and 150 can include a server, desktop computer, laptop computer, tablet computer, a television with one or more processors embedded therein and / or coupled thereto, smart phone, handheld computer, personal digital assistant ("PDA"), video game device, wearable computing device, or any other wired or wireless, processor-driven device.
  • PDA personal digital assistant
  • the network computing devices 110, 131, 140, and 150 are operated by users 101, merchant system 130 operators, account management system 140 operators, and issuer system 150 operators, respectively.
  • An example user computing device 110 comprises a user interface 111, an advertising application 113, a data storage unit 115, and a microphone component 119.
  • the user computing device 110 communicates with an account management system 140 via the network 120 and receives data over an audio communication channel from the merchant computing device 131 associated with the merchant system 130.
  • the user interface 111 enables the user 101 to interact with the user computing device 110.
  • the user interface 111 comprises a touch screen, a voice-based interface, or any other interface that allows the user 101 to provide input and receive output from an application on the user computing device 110.
  • the user 101 interacts via the user interface 111 with the advertising application 113.
  • the advertising application 113 is a program, function, routine, applet, or similar entity that exists on and performs its operations on the user computing device 110.
  • the user 101 must install the advertising application 113 and/or make a feature selection on the user computing device 110 to obtain the benefits of the techniques described herein.
  • the user 101 accesses the advertising application 113 on the user computing device 110 via the user interface 111.
  • the advertising application 113 is associated with the account management system 140 and may transmit data to the account management system 140 via the network 120 and/or receive data from the account management system 140 via the network 120.
  • the advertising application 113 comprises a payment application.
  • the advertising application 113 comprises a ticketing application.
  • the advertising system 113 comprises an email application, a mapping application, a shopping application, a social media application, or other application.
  • the data storage unit 115 comprises a local or remote data storage structure accessible to the user computing device 110 suitable for storing information.
  • the data storage unit 115 stores encrypted information, such as HTML 5 local storage.
  • the microphone component 119 comprises a microphone device that is capable of receiving audible sound inputs and/or ultrasound inputs audible sound inputs from an environment of the user computing device 110.
  • the microphone component 119 communicates with the advertising application 113 to receive an instruction to transition from a passive mode to an active mode and listen for ultrasound inputs. For example, in response to a user 101 signing in to the advertising application 113, for example, by entering a user name and a password, the advertising application 113 transmits the instruction to the microphone component 119 to transition from the passive mode to the active mode.
  • the microphone component 119 receives audible sound inputs and/or ultrasound inputs while in the active mode and transmits the received sound inputs to the payment application 113.
  • An example merchant system 130 comprises one or more merchant computing devices 131 located at locations.
  • An example merchant computing device 131 comprises an advertising application 133, a data storage unit 135 and an audio component 138.
  • the merchant computing device comprises a radio, a computer, a television, or other device comprising an audio component 138 capable of broadcasting audio tokens over an audio communication channel.
  • the merchant computing device 131 does not comprise an advertising application 133.
  • the merchant computing device 131 comprises a speaker device that is pre-configured to broadcast one or more audio tokens.
  • the merchant computing device 131 comprises a mobile computing device such as a smartphone device, tablet device, or other mobile computing device.
  • the merchant computing device 131 comprises a point of sale terminal.
  • the merchant system 130 and/or merchant computing device 131 communicate with an account management system 140 via the network 120.
  • the merchant computing device 131 communicates data to one or more user computing devices 110 via an audio communication channel by broadcasting an audio token.
  • the data storage unit 135 comprises a local or remote data storage structure accessible to the merchant computing device 131 suitable for storing information.
  • the data storage unit 135 stores encrypted information, such as HTML 5 local storage.
  • the audio component 138 comprises a speaker device or other device capable of producing an ultrasound and/or audible sound output.
  • the audio component 138 can be configured by the merchant system 130 to broadcast an audio token at a location of the merchant computing device 131.
  • the audio component 138 is a component of another device that is communicatively coupled to the merchant computing device 131 or to the advertising system 130.
  • An example account management system 140 or service processing system, comprises an account management component 141, a data storage unit 145, and a transaction processing component 149.
  • the account management system communicates with the user computing device 110 and the advertising system 130 via the network 120.
  • the account management system 140 communicates with an issuer system 150 via the network 120.
  • the account management component 141 manages user 101 accounts and merchant system 130 accounts associated with users 101 and merchant systems 130, respectively.
  • the account management component 141 receives requests to add, edit, delete, or otherwise modify payment account information for a user 101 account or a merchant system account.
  • the account management component 141 maintains a QR code library accessible to the merchant system 130, the merchant computing device 131, and/or one or more user computing devices 110 via the network 120.
  • the account management system 140 updates the QR code library in response to receiving a request for an audio token and audio token data from one or more merchant systems 130 or merchant computing devices 131.
  • the account management component 141 communicates with advertising applications 113 on one or more respective user computing devices 110 to synchronize the QR code library s on the respective user computing devices 110 to correspond to the QR code library on the account management system 140 in response to updating the QR code library on the account management system 140.
  • the data storage unit 145 comprises a local or remote data storage structure accessible to the account management system 140 suitable for storing information.
  • the data storage unit 145 stores encrypted information, such as HTML 5 local storage.
  • the server 147 provides the content that the user 101 accesses through the web browser on the user computing device 110, including but not limited to html documents, images, style sheets, and scripts.
  • the web server 141 supports the website 148 of the account management computing system 140.
  • the website 148 communicates with the web browser 118 or advertising application 113 resident on the user computing device 110 via the network 120.
  • the user 101 accesses the website 143 to download an application 113 and/or configure a user 101 account with the account management computing system 140.
  • the transaction processing component 149 receives transaction details from a merchant system 130 as part of audio token data and an audio token from a user computing device 110.
  • the transaction processing component 149 extracts the audio token data comprising the stored transaction details received from the merchant system 130 and associated with the audio token received from the user computing device 110.
  • the transaction details comprise a total amount of transaction and merchant system 130 payment account information.
  • the transaction processing system component 149 extracts payment information associated with a user 101 account associated with the user computing device 110 and transmits a payment authorization request to an issuer system 150 or other appropriate financial institution associated with the user 101 payment account information.
  • An example payment authorization request comprises advertising system payment account information, user 101 payment account information, and a total amount of the transaction.
  • the transaction processing component 149 receives an approval or denial of the payment authorization request from the issuer system 150 over the network 120. In an example, the transaction processing component 149 transmits a receipt to the merchant computing device 131 and/or the user computing device 110 comprising a summary of the payment transaction.
  • the transaction processing component 149 receives an audio token from the user computing device 110, extracts audio token data associated with the audio token, and transmits the extracted audio token data to the user computing device 110.
  • the audio token data comprises images, text, a URL, or other data associated with the received audio token.
  • the transaction processing component 149 of the account management system 140 received the data to associate with the token from the merchant system 130.
  • An example issuer system 150 approves or denies a payment authorization request received from the merchant computing system 130 or from the account management system 140.
  • the issuer system 150 communicates with the merchant computing device 131, the merchant system 130, and/or account management system 140 over the network 120.
  • the issuer system 130 communicates with an acquirer system to approve a credit authorization and to make payment to the account management system 140 and/or merchant system.
  • the acquirer system is a third party payment processing company.
  • the network computing devices and any other computing machines associated with the technology presented herein may be any type of computing machine such as, but not limited to, those discussed in more detail with respect to Figure 6.
  • any functions, applications, or components associated with any of these computing machines, such as those described herein or any others (for example, scripts, web content, software, firmware, hardware, or modules) associated with the technology presented herein may by any of the components discussed in more detail with respect to Figure 6.
  • the computing machines discussed herein may communicate with one another, as well as with other computing machines or communication systems over one or more networks, such as network 120.
  • the network 120 may include any type of data or communications network, including any of the network technology discussed with respect to Figure 6.
  • FIG. 2-5 The components of the example operating environment 100 are described hereinafter with reference to the example methods illustrated in Figures 2-5.
  • the example methods of Figures 2-5 may also be performed with other systems and in other environments.
  • the operations described with respect to any of the Figures 2-5 can be implemented as executable code stored on a computer or machine readable non-transitory tangible storage medium (e.g., floppy disk, hard disk, ROM, EEPROM, nonvolatile RAM, CD-ROM, etc.) that are completed based on execution of the code by a processor circuit implemented using one or more integrated circuits; the operations described herein also can be implemented as executable logic that is encoded in one or more non- transitory tangible media for execution (e.g., programmable logic arrays or devices, field programmable gate arrays, programmable array logic, application specific integrated circuits, etc.).
  • Figure 2 is a block flow diagram depicting a method to receive, by a user computing device 110, audio token data associated with an audio token transmitted by a merchant computing device 131, in accordance with certain examples. The method 200 is described with reference to the components illustrated in Figure 1.
  • the merchant system 130 registers with an account management system 140 and downloads an advertising application 133 onto the merchant computing device 131.
  • the method to register, by a merchant system 130, for an account with an account management system 140 and downloading an advertising application 133 onto a merchant computing device 131 is described in more detail hereinafter with reference to the methods described in Figure 3.
  • Figure 3 is a block flow diagram depicting a method 210 to register, by a merchant system 130, for an account with an account management system 140 and downloading an advertising application 133 onto a merchant computing device 131, as referenced in block 210.
  • the method 210 is described with reference to the components illustrated in Figure 1.
  • the merchant computing device 131 operator accesses the account management system 140 website 148 via the merchant computing device 131.
  • the operator accesses the account management system 140 website 148 via a web browser of the merchant computing device 131.
  • the merchant computing device 131 operator enters the website 148 address in the address bar of a web browser to access the website 148 via the network 120.
  • the merchant computing device 131 operator accesses the account management system 140 website 148 website using an application resident on the merchant computing device 131.
  • the merchant computing device 131 operator selects an application on the merchant computing device 131 that connects the user 101 to the account management system 140 website 148.
  • the merchant system 130 comprises an advertising system.
  • the merchant computing device 131 operator registers for a merchant account via the account management system 140 website 148.
  • the merchant computing device 131 operator establishes an account management system 140 account with the account management system 140.
  • the merchant computing device 131 operator registers a username and a password associated with the merchant account to use to sign in to the merchant account.
  • the merchant account is associated with a service, such as a digital wallet, an email service, a messaging service, a gaming service, or a mapping service.
  • the merchant account is associated with multiple services.
  • the merchant computing device 131 operator downloads an advertising application 133 on the merchant computing device 131.
  • the advertising application 133 communicates with the account management system 140 over the network 120.
  • the advertising application 133 is associated with the merchant system account and may be utilized by the operator or merchant system 130 to access the merchant account and/or services provided by the account management system 140 for the merchant system 130 or for the operator 102 associated with the merchant computing device 131.
  • the advertising application 133 may be a digital wallet application to which the merchant system 130 may upload financial data.
  • the advertising application 133 communicates with the account management system 140, which administers the digital wallet account.
  • the merchant computing device 131 operator may download various applications associated with the merchant system account from the account management system 140.
  • the advertising application 133 is downloaded onto the merchant computing device 131 before the merchant computing device 131 establishes the merchant account with the account management system 140. In certain examples, the merchant computing device 131 does not download the advertising application 133 onto the merchant computing device 131.
  • the merchant computing device 131 operator uploads account information to the merchant account.
  • Example account information comprises financial account information.
  • the merchant computing device 131 operator enters financial account information into the merchant account.
  • the financial account information is associated with a financial institution system.
  • the financial institution system is a bank or a credit union with which the merchant computing device 131 operator or merchant system 130 has a financial account.
  • financial account information comprises an account number, a routing number, the name associated with the financial account, the address associated with the financial account and/or any other relevant, useful, or necessary information that the merchant computing device 131 operator may enter into the broadcasting system account or that the broadcasting system account may require.
  • the merchant computing device 131 operator enters the financial account information using the advertising application 133.
  • the advertising application 133 communicates via the network 120 with a digital wallet account managed by the account management system 140.
  • the merchant computing device 131 operator enters the financial account information via a web browser, which communicates with the account management system 140 website 148 via the network 120.
  • the merchant computing device 131 operator enters credit account information into the merchant account.
  • the credit account is associated with an issuer system 150 and an acquirer system.
  • the credit account information comprises a credit card number, an expiration date, a card verification number, the name associated with the credit account, and/or any other relevant, useful, or necessary information that the merchant computing device 131 operator may enter into the merchant account or that the merchant account may require.
  • the merchant computing device 131 operator enters the credit account information using the advertising application 133, which communicates with the account management system 140 via the network 120.
  • the merchant computing device 131 operator enters the financial account information via a web browser, which communicates with the account management system 140 website 148 via the network 120.
  • the user 101 registers for a user account with the account management system 140 and downloads an advertising application 113 on the user computing device 110.
  • the method to register, by a user 101, for a user 101 account with an account management system 140 is described in more detail hereinafter with reference to the methods described in Figure 4.
  • Figure 4 is a block flow diagram depicting a method 220 to register, by a user 101, for a user 101 account with an account management system 140, in accordance with certain examples, as referenced in block 220.
  • the method 220 is described with reference to the components illustrated in Figure 1.
  • the user 101 accesses the account management system 140 website 148 via the user computing device 110.
  • the user 101 accesses the account management system 140 website 148 via a web browser of the user computing device 110.
  • the user 101 enters the website 148 address in the address bar of the web browser to access the website 148.
  • the user 101 accesses the account management system website 148 using an application resident on the user computing device 110.
  • the user 101 selects an application on the user computing device 110 that connects the user 101 to the account management system website 148 via the network 120.
  • the user 101 registers for a user account via the account management system 140 website 148.
  • the user 101 registers a username and a password associated with the user account to use to sign in to the user account.
  • the user account is associated with a service, such as a digital wallet, an email service, a messaging service, a gaming service, or a mapping service.
  • the user account is associated with multiple services.
  • Example user account information comprises user financial account information.
  • the user 101 enters financial account information into the user account.
  • the financial account information is associated with a financial institution system.
  • the financial institution system is a bank or a credit union with which the user 101 has a financial account.
  • financial account information comprises an account number, a routing number, the name associated with the financial account, the address associated with the financial account and/or any other relevant, useful, or necessary information that the user 101 may enter into the user account or that the user account may require.
  • the user 101 enters the financial account information using the application.
  • the application is a digital wallet application that communicates with a digital wallet account managed by the account management system 140.
  • the user 101 enters the financial account information via a web browser, which communicates with the account management system 140 website 148 via the network 120.
  • the user 101 enters credit account information into the user 101 account.
  • the credit account is associated with an issuer system 130 and an acquirer system 140.
  • the credit account information comprises a credit card number, an expiration date, a card verification number, the name associated with the credit account, and/or any other relevant, useful, or necessary information that the user 101 may enter into the user account or that the user account may require.
  • the user 101 enters the credit account information using the application, which communicates with the account management system 140 via the network 120.
  • the user 101 enters the financial account information via a web browser, which communicates with the account management system website 148 via the network 120.
  • the user 101 downloads an advertising application 113 on the user computing device.
  • the application 113 communicates with the account management system 140 over the network 120.
  • the advertising application 113 is associated with the user account and may be utilized by the user 101 to access the user account and/or services provided by the account management system 140 for the user 101 associated with the user account.
  • the advertising application 113 may be a digital wallet application module to which the user 101 may upload financial data.
  • the advertising application 113 communicates with the account management system 140, which administers the user digital wallet account.
  • the user 101 may download various advertising applications 113 associated with the user account from the account management system 140.
  • the advertising application 113 is downloaded onto the user computing device 110 before the user 101 establishes the user account with the account management system 140. In certain examples, the user 101 does not download the advertising application 113 onto the user computing device 110.
  • the merchant system 130 configures an audio token with a merchant computing device 131.
  • the merchant system 130 transmits audio token data to the account management system 140 and a request for an audio token via a network 120.
  • Example audio token data comprises an advertisement, transaction details, public service information, a uniform resource locator ("URL") for a website, or other relevant information to be broadcast by a merchant computing device 131 at a merchant system 130 location or at a point of interest.
  • a merchant computing device 131 may comprise a broadcasting computing device.
  • Example transaction details comprise an identification of an item to be purchased, a total amount of a transaction, and payment account information associated with the account management system.
  • the account management system 140 receives the audio token data and the request for the audio token from the merchant system 130 via the network 120.
  • the audio token data comprises a uniform resource locator ("URL") for a website.
  • the account management system stores the received audio token data, generates an audio token, and associates the generated token with the stored audio token data.
  • the audio token comprises a random number comprising an alphanumeric and/or symbolic string of characters and the account management system generates the audio token via a random number generator.
  • the account management system 140 stores the audio token and the associated audio token data in an audio token list maintained in a data storage unit accessible to the account management system 140, where the audio token list comprises a list that associates generated audio tokens with audio token data associated with each generated audio token.
  • a merchant system 130 generates an audio token, associates the audio token with audio token data stored by the merchant system 130 or generated by the merchant system 130, and transmits the audio token along with the audio token data to the account management system 140 via the network 120.
  • the audio token comprises a random number comprising an alphanumeric and/or symbolic string of characters.
  • the merchant system 130 generates the audio token via a random number generator.
  • the merchant system 130 stores the audio token and the associated audio token data in an audio token list maintained in a data storage unit 135 accessible to the merchant system 130.
  • the audio token list comprises a listing of generated audio tokens and associated audio token data corresponding to each audio token generated by the merchant system 130.
  • the account management system 140 receives the audio token and the audio token data via the network 120, associates the audio token with the audio token data, and stores the audio token and the associated audio token data.
  • the merchant system 130 maintains a list of audio tokens with associated stored audio token data.
  • the account management system stores the audio token and the associated audio token data in an audio token list maintained in a data storage unit 145 accessible to the account management system 140, where the audio token list comprises a list that associates received audio tokens with received audio token data associated with each received audio token.
  • a merchant system 130 comprises a QR code library stored on a data storage unit 135 on the merchant computing device 131 or accessible to the merchant computing device 131.
  • the QR code library comprises a database.
  • the QR code library is stored on a data storage unit 145 on the account management system 140.
  • the QR code library is stored on the merchant system 130, one or more user computing devices 110, and the account management system 140, or is otherwise accessible to the merchant system 130, to the one or more user computing devices 110, and to the account management system 140.
  • the account management system 140, the merchant system 130, and/or the merchant computing device 131 are able to communicate with the QR code library and/or a device or data storage unit comprising the QR code library.
  • the account management system 140, and/or the merchant computing device 131 can otherwise read or access information in the QR code library.
  • the merchant system 130 defines an audio token with the QR code library and associates an advertisement, a website, or other audio token data with the audio token in the QR code library.
  • the merchant system 130 may define the audio token using an advertising application 133 on the merchant computing device 131 that communicates with the QR code library.
  • the merchant system defined an audio token to associate with audio token data comprising a uniform resource locator ("URL") for a website.
  • URL uniform resource locator
  • the QR code library on the merchant computing device 131 in response to a merchant system 130 operator selecting an option to define the audio token via the QR code library, the QR code library on the merchant computing device 131 generates an audio token to associate with the advertisement, website, or the other audio token data that the merchant system 130 desires to associate with the audio token.
  • one or more user computing devices 110 comprise advertising applications 113 that also comprise the audio QR code library or are able to access the QR code library via the network 120.
  • the merchant system 130 defines the audio token with the QR code library using an advertising application 133 on the merchant computing device, the merchant system 130 communicates with an account management system via the network 120 to update the QR code library stored on the account management system 140, and the account management system 140 communicates via the network 120 with the one or more user computing devices 110 to synchronize the merchant QR code library with each of the QR code libraries on the respective one or more user computing devices 110.
  • the merchant computing device 131 broadcasts the audio token.
  • the merchant system 130 location comprises a brick and mortar store location of the merchant system 130 or a point of interest, for example, a point of interest comprising a subway or train station where the merchant system 130 desires to conduct an advertising campaign.
  • the merchant computing device 131 broadcasts the audio token at a location.
  • the merchant system 130 configures a broadcasting computing device separate from the merchant computing device 131 to broadcast the audio token and the broadcasting computing device broadcasts the audio token via an audio communication channel.
  • One or more user computing devices 110 comprising an advertising application 113 receive the broadcast audio token and retransmit the audio token to the account management system 140 via a network 120.
  • the merchant computing device 131 or broadcasting computing device comprises an audio component 138 capable of sound output, for example, an audio speaker capable of generating an audible sound output or ultrasound output.
  • the user 101 signs in to the advertising application 113 on the user computing device 110 and the user computing device 110 activates the microphone component 119 to listen for audio tokens.
  • a user computing device 110 comprising an advertising application 113 receives audio tokens via a microphone component 119 when the user 101 is signed in to the advertising application 113.
  • a user 101 having an account with the account management system 140 selects an advertising application 113 on the user computing device 110 and signs into an advertising application 113 on the user computing device 110 using a username and a password.
  • the advertising application 113 communicates with the account management system 140 via a network 120 when the user 101 is signed in to the advertising application 113.
  • the advertising application activates the microphone component 119 of the user computing device 110 to listen for data transmitted over audio communication channels.
  • the user 101 signs in to the advertising application 113 and the advertising application 113 activates the microphone component 119 of the user computing device 110 in response to receiving an indication that the user 101 signed in to the advertising application 113.
  • the user 101 arrives within an audio broadcasting proximity of the merchant computing device 131.
  • the user 101 carrying the user computing device 110, arrives at the merchant system location 130 comprising the merchant computing device 131.
  • the user 101 has signed in to the user computing device 110 and the user computing device 110 microphone component 119 has been activated and is able to receive audio tokens broadcast by the merchant computing device 131.
  • the user computing device 110 receives an audio token and extracting audio token data using a QR code library database.
  • the method to receive, by a user computing device 110, an audio token and extracting audio token data using a QR code library database is described in more detail hereinafter with reference to the methods described in Figure 5.
  • Figure 5 is a block flow diagram depicting a method 220 to receive, by a user computing device 110, an audio token and extracting audio token data using a QR code library database, in accordance with certain examples, as referenced in block 270.
  • the method 270 is described with reference to the components illustrated in Figure 1.
  • the user computing device 110 receives the broadcast audio token via an audio communication channel.
  • the user computing device 110 receives, via the microphone component 119, the audio token broadcasted by the merchant computing device 131 over an audio communication channel.
  • the user computing device 110 receives, via the microphone component 119, the audio token broadcasted by a broadcasting computing device over the audio communication channel.
  • the user computing device 110 accesses the QR code library database and identifies the audio token in the QR code library database.
  • the user computing device 110 receives the audio token and compares the audio token to multiple audio tokens stored in a QR code library on the user computing device 110.
  • the user computing device 110 is logged into the advertising application 113, receives the audio token broadcast by the merchant computing device 131, and determines that the received audio token corresponds to a particular stored audio token in the QR code library stored on the user computing device 110 or stored in a database otherwise accessible to the user computing device via the network 120.
  • the user computing device 110 extracts the stored audio token data associated with the received audio token in the QR code library database.
  • the user computing device 110 extracts particular audio token data associated with the particular stored audio token in the QR code library.
  • the extracted particular audio token data comprises a URL, advertising data, public service data, or other audio token data.
  • the user computing device displays or otherwise executes instructions in accordance with the extracted particular audio token data.
  • the user computing device 110 accesses and displays a website associated with audio token data comprising an extracted URL associated with the particular stored audio token.
  • the advertising application 113 transmits the received audio token to the account management system 140 via the network 120 along with a request for advertising data associated with the audio token.
  • an account management system 140 receives the audio token from a particular user computing device 110 over the network 120.
  • the particular user computing device 110 received the audio token transmitted at the location of the merchant computing device 131 and then transmitted the audio token to the account management system 140 via the network 120.
  • the account management system 140 receives the retransmitted audio token and the request for advertising data associated with the audio token.
  • the account management system 140 determines that the received audio token matches a stored audio token previously configured by a merchant system 130, and extracts the audio token data associated with the audio token.
  • the account management system 140 maintains a list in a data storage unit 145 that lists the audio token data associated with each audio token.
  • the account management system 140 extracts the audio token data associated with the audio token.
  • Example extracted audio token data comprises a URL, advertisement data, or other audio token data.
  • the account management system 140 transmits the extracted audio token data comprising a URL to the user computing device 110 over the network 120 along with instructions to the user computing device 110 to access a website associated with the URL or instructions to prompt the user to approve the user computing device 110 accessing the website associated with the URL.
  • Other example extracted audio token data comprises public service data.
  • public service data comprises an alert issued by a public service or other service such as a traffic alert, emergency alert, or weather alert.
  • the account management system 140 transmits the alert information to the user computing device to be displayed on the user computing device for the user 101.
  • the user computing device displays the received information via a user interface 111 of the user computing device 110.
  • a merchant system 130 can preconfigure an audio token by associating the audio token with audio token data, such as a URL, and transmit the preconfigured audio token to the account management system 140 via the network 120 along with the audio token data.
  • the merchant system 130 then broadcasts the audio token using the merchant computing device 131 via an audio communication channel at a merchant system 130 location.
  • a user computing device 110 associated with a user 101 receives the audio token broadcast at the merchant system 130 location via an audio communication channel and transmits the received audio token to the account management system 140 via the network 120.
  • a QR code library is stored on an advertising application 133 on the merchant computing device 131.
  • a merchant computing device 131 operator defines the audio token with the library and associates the audio token data with the defined audio token.
  • the QR code library on the merchant computing device 131 communicates with the account management system 140 via the network 120 and multiple user computing devices 110, also comprising the QR code library, communicate over the network 120 with the account management system 140.
  • the account management system 140 synchronizes each of the respective user computing device 110 QR code libraries when any particular QR code library, whether the merchant system 130 QR code library, account management system 140 QR library code database, or user computing device 110 QR code library, is updated.
  • the user computing device 110 advertising application 113 also has access to the library.
  • the user computing device 110 receives the audio token broadcast at the merchant system 130 location and the advertising application 113 on the user computing device 110 uses the QR code library to identify audio token data stored on the QR code library associated with the received audio token.
  • the user computing device 110 displays the stored data or otherwise executes instructions in accordance with the stored audio token data, for example, by accessing a website associated with the stored audio token data when the stored audio token data comprises a URL.
  • the user computing device 110 communicates with the account management system 140 via the network 120 to request and receive the audio token data associated with the received audio token from the QR code library stored on the account management system 140.
  • the user computing device 110 processes a transaction or executes instructions in accordance with the extracted audio token data associated with the received audio token.
  • the information associated with the audio token comprises transaction details and a user interface 111 object selectable by the user 101 to initiate a transaction.
  • the user computing device 110 forwards the transaction details to the account management system 140 along with user 110 account data and a request to process a transaction.
  • Example transaction details comprise an amount of transaction, a transaction identifier, and a description of items to be purchased.
  • the account management system 140 receives, via the network 120, a user 101 payment account identifier and extracts user 101 payment account information associated with the user 101 account identifier.
  • the account management system 140 communicates via the network 120 with the merchant system to receive transaction details associated with the transaction identifier and also receives merchant system 130 payment account information.
  • the account management computing system 140 transmits a payment authorization request to an issuer system 150 or other appropriate financial institution associated with the user 101 payment account information via the network 120.
  • An example payment authorization request comprises merchant system 130 payment account information, user 101 payment account information, and a total amount of the transaction.
  • the account management system 140 receives an approval or denial of the payment authorization request from the issuer system 150 over the network 120.
  • the account management system 140 transmits a receipt to the broadcasting computing device 130 and/or the user computing device 110 comprising a summary of the payment transaction.
  • Figure 6 depicts a computing machine 2000 and a module 2050 in accordance with certain examples.
  • the computing machine 2000 may correspond to any of the various computers, servers, mobile devices, embedded systems, or computing systems presented herein.
  • the module 2050 may comprise one or more hardware or software elements configured to facilitate the computing machine 2000 in performing the various methods and processing functions presented herein.
  • the computing machine 2000 may include various internal or attached components such as a processor 2010, system bus 2020, system memory 2030, storage media 2040, input/output interface 2060, and a network interface 2070 for communicating with a network 2080.
  • the computing machine 2000 may be implemented as a conventional computer system, an embedded controller, a laptop, a server, a mobile device, a smartphone, a set-top box, a kiosk, a router or other network node, a vehicular information system, one more processors associated with a television, a customized machine, any other hardware platform, or any combination or multiplicity thereof.
  • the computing machine 2000 may be a distributed system configured to function using multiple computing machines interconnected via a data network or bus system.
  • the processor 2010 may be configured to execute code or instructions to perform the operations and functionality described herein, manage request flow and address mappings, and to perform calculations and generate commands.
  • the processor 2010 may be configured to monitor and control the operation of the components in the computing machine 2000.
  • the processor 2010 may be a general purpose processor, a processor core, a multiprocessor, a reconfigurable processor, a microcontroller, a digital signal processor ("DSP"), an application specific integrated circuit (“ASIC”), a graphics processing unit (“GPU”), a field programmable gate array (“FPGA”), a programmable logic device (“PLD”), a controller, a state machine, gated logic, discrete hardware components, any other processing unit, or any combination or multiplicity thereof.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • GPU graphics processing unit
  • FPGA field programmable gate array
  • PLD programmable logic device
  • the processor 2010 may be a single processing unit, multiple processing units, a single processing core, multiple processing cores, special purpose processing cores, coprocessors, or any combination thereof. According to certain embodiments, the processor 2010 along with other components of the computing machine 2000 may be a virtualized computing machine executing within one or more other computing machines.
  • the system memory 2030 may include non-volatile memories such as read-only memory (“ROM”), programmable read-only memory (“PROM”), erasable programmable read-only memory (“EPROM”), flash memory, or any other device capable of storing program instructions or data with or without applied power.
  • the system memory 2030 may also include volatile memories such as random access memory (“RAM”), static random access memory (“SRAM”), dynamic random access memory (“DRAM”), and synchronous dynamic random access memory (“SDRAM”). Other types of RAM also may be used to implement the system memory 2030.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • Other types of RAM also may be used to implement the system memory 2030.
  • the system memory 2030 may be implemented using a single memory module or multiple memory modules.
  • system memory 2030 is depicted as being part of the computing machine 2000, one skilled in the art will recognize that the system memory 2030 may be separate from the computing machine 2000 without departing from the scope of the subject technology. It should also be appreciated that the system memory 2030 may include, or operate in conjunction with, a non-volatile storage device such as the storage media 2040.
  • the storage media 2040 may include a hard disk, a floppy disk, a compact disc read only memory (“CD-ROM”), a digital versatile disc (“DVD”), a Blu-ray disc, a magnetic tape, a flash memory, other non-volatile memory device, a solid state drive (“SSD”), any magnetic storage device, any optical storage device, any electrical storage device, any semiconductor storage device, any physical-based storage device, any other data storage device, or any combination or multiplicity thereof.
  • the storage media 2040 may store one or more operating systems, application programs and program modules such as module 2050, data, or any other information.
  • the storage media 2040 may be part of, or connected to, the computing machine 2000.
  • the storage media 2040 may also be part of one or more other computing machines that are in communication with the computing machine 2000 such as servers, database servers, cloud storage, network attached storage, and so forth.
  • the module 2050 may comprise one or more hardware or software elements configured to facilitate the computing machine 2000 with performing the various methods and processing functions presented herein.
  • the module 2050 may include one or more sequences of instructions stored as software or firmware in association with the system memory 2030, the storage media 2040, or both.
  • the storage media 2040 may therefore represent examples of machine or computer readable media on which instructions or code may be stored for execution by the processor 2010.
  • Machine or computer readable media may generally refer to any medium or media used to provide instructions to the processor 2010.
  • Such machine or computer readable media associated with the module 2050 may comprise a computer software product.
  • a computer software product comprising the module 2050 may also be associated with one or more processes or methods for delivering the module 2050 to the computing machine 2000 via the network 2080, any signal-bearing medium, or any other communication or delivery technology.
  • the module 2050 may also comprise hardware circuits or information for configuring hardware circuits such as microcode or configuration information for an FPGA or other PLD.
  • the input/output (“I/O”) interface 2060 may be configured to couple to one or more external devices, to receive data from the one or more external devices, and to send data to the one or more external devices. Such external devices along with the various internal devices may also be known as peripheral devices.
  • the I/O interface 2060 may include both electrical and physical connections for operably coupling the various peripheral devices to the computing machine 2000 or the processor 2010.
  • the I/O interface 2060 may be configured to communicate data, addresses, and control signals between the peripheral devices, the computing machine 2000, or the processor 2010.
  • the I/O interface 2060 may be configured to implement any standard interface, such as small computer system interface (“SCSI”), serial-attached SCSI (“SAS”), fiber channel, peripheral component interconnect (“PCI”), PCI express (PCIe), serial bus, parallel bus, advanced technology attached (“ATA”), serial ATA (“SAT A”), universal serial bus (“USB”), Thunderbolt, FireWire, various video buses, and the like.
  • SCSI small computer system interface
  • SAS serial-attached SCSI
  • PCIe peripheral component interconnect
  • PCIe PCI express
  • serial bus parallel bus
  • advanced technology attached ATA
  • serial SAT A serial ATA
  • USB universal serial bus
  • Thunderbolt FireWire
  • the I/O interface 2060 may be configured to implement only one interface or bus technology.
  • the I/O interface 2060 may be configured to implement multiple interfaces or bus technologies.
  • the I/O interface 2060 may be configured as part of, all of, or to operate in conjunction with, the system bus 2020.
  • the I/O interface 2060 may couple the computing machine 2000 to various input devices including mice, touch-screens, scanners, electronic digitizers, sensors, receivers, touchpads, trackballs, cameras, microphones, keyboards, any other pointing devices, or any combinations thereof.
  • the I/O interface 2060 may couple the computing machine 2000 to various output devices including video displays, speakers, printers, projectors, tactile feedback devices, automation control, robotic components, actuators, motors, fans, solenoids, valves, pumps, transmitters, signal emitters, lights, and so forth.
  • the computing machine 2000 may operate in a networked environment using logical connections through the network interface 2070 to one or more other systems or computing machines across the network 2080.
  • the network 2080 may include wide area networks (WAN), local area networks (LAN), intranets, the Internet, wireless access networks, wired networks, mobile networks, telephone networks, optical networks, or combinations thereof.
  • the network 2080 may be packet switched, circuit switched, of any topology, and may use any communication protocol. Communication links within the network 2080 may involve various digital or an analog communication media such as fiber optic cables, free-space optics, waveguides, electrical conductors, wireless links, antennas, radio-frequency communications, and so forth.
  • the processor 2010 may be connected to the other elements of the computing machine 2000 or the various peripherals discussed herein through the system bus 2020. It should be appreciated that the system bus 2020 may be within the processor 2010, outside the processor 2010, or both. According to certain examples, any of the processor 2010, the other elements of the computing machine 2000, or the various peripherals discussed herein may be integrated into a single device such as a system on chip (“SOC”), system on package (“SOP”), or ASIC device.
  • SOC system on chip
  • SOP system on package
  • ASIC application specific integrated circuit
  • the users may be provided with an opportunity or option to control whether programs or features collect user information (e.g., information about a user's social network, social actions or activities, profession, a user's preferences, or a user's current location), or to control whether and/or how to receive content from the content server that may be more relevant to the user.
  • user information e.g., information about a user's social network, social actions or activities, profession, a user's preferences, or a user's current location
  • certain data may be treated in one or more ways before it is stored or used, so that personally identifiable information is removed.
  • a user's identity may be treated so that no personally identifiable information can be determined for the user, or a user's geographic location may be generalized where location information is obtained (such as to a city, ZIP code, or state level), so that a particular location of a user cannot be determined.
  • location information such as to a city, ZIP code, or state level
  • the user may have control over how information is collected about the user and used by a content server.
  • Embodiments may comprise a computer program that embodies the functions described and illustrated herein, wherein the computer program is implemented in a computer system that comprises instructions stored in a machine-readable medium and a processor that executes the instructions.
  • the embodiments should not be construed as limited to any one set of computer program instructions.
  • a skilled programmer would be able to write such a computer program to implement an embodiment of the disclosed embodiments based on the appended flow charts and associated description in the application text. Therefore, disclosure of a particular set of program code instructions is not considered necessary for an adequate understanding of how to make and use embodiments.
  • the examples described herein can be used with computer hardware and software that perform the methods and processing functions described herein.
  • the systems, methods, and procedures described herein can be embodied in a programmable computer, computer-executable software, or digital circuitry.
  • the software can be stored on computer-readable media.
  • computer-readable media can include a floppy disk, RAM, ROM, hard disk, removable media, flash memory, memory stick, optical media, magneto-optical media, CD-ROM, etc.
  • Digital circuitry can include integrated circuits, gate arrays, building block logic, field programmable gate arrays (FPGA), etc.
  • Example 1 A system to transmit data using audio communication channels, comprising: a storage device;
  • a processor communicatively coupled to the storage device, wherein the processor executes application code instructions that are stored in the storage device to cause the system to:
  • the computing system configures a merchant computing device at a location to broadcast the audio token to a user computing device via an audio communication channel;
  • Example 2 The system of example 1, wherein the data comprises one or more of text and images.
  • Example 3 The system of example 1 or 2, wherein the data comprises one or more of a uniform resource locator ("URL") associated with a website, payment data, and location information.
  • URL uniform resource locator
  • Example 4 The system of example 3, wherein the data comprises a URL, and wherein the user computing device accesses the website based on the URL.
  • Example 5 The system of at least one of the preceding examples, wherein the merchant computing device broadcasts the audio token via an audio component comprising a speaker.
  • Example 6 The system of example 5, wherein audio speaker is designed to generate an audible sound output and / or ultrasound output.
  • Example 7 The system of example 3, wherein the data comprise transaction details comprising payment account information and a total amount of transaction, and wherein the processor is further configured to execute application code instructions that are stored in the storage device to cause the system to:
  • Example 8 The system of at least one of the preceding examples, wherein associating the audio token with the received data comprises storing the audio token and the received data in a quick response code library.
  • Example 9 The system of at least one of the preceding examples, wherein the data comprises a public service announcement, and wherein the user computing device displays the public service announcement.
  • Example 10 The system of at least one of the preceding examples, wherein the data comprises transaction data, and wherein the user computing device initiates a transaction using the transaction data.
  • Example 11 A computer-implemented method to transmit audio tokens, comprising: receiving, by one or more computing devices, data and a request to generate an audio token to associate with the data from a computing system;
  • the audio token transmitting, by the one or more computing devices, the audio token to the computing system, wherein the computing system configures a merchant computing device at a location to broadcast the audio token to a user computing device via an audio communication channel;
  • Example 12 The method of example 11, wherein the data comprises one or more of text and images.
  • Example 13 The method of example 11 or 12, wherein the data comprises one or more of a uniform resource locator ("URL") associated with a website, payment data, and location information.
  • URL uniform resource locator
  • Example 14 The method of example 13, wherein the data comprises a URL, and wherein the user computing device accesses the website based on the URL.
  • Example 15 The method of at least one of the examples 11 to 14, wherein the merchant computing device broadcasts the audio token via an audio component comprising a speaker.
  • Example 16 The method of example 15, wherein the audio token comprises audible sound output and / or ultrasound output.
  • Example 17 The method of example 13, wherein the data comprise transaction details comprising payment account information and a total amount of transaction, and further comprising:
  • a transaction authorization request comprising the user payment account information, the merchant system payment account information, and the total amount of transaction to an issuer system associated with the user payment account information
  • Example 18 The method of at least one of the examples 11 to 17, wherein associating the audio token with the received data comprises storing the audio token and the received data in a quick response code library.
  • Example 19 A computer program product, comprising:
  • non-transitory computer-readable medium having computer-executable program instructions embodied thereon that when executed by a processor enable transmission of audio tokens comprising indications of data to user computing devices, the computer- executable program instructions comprising:
  • computer-executable program instructions to transmit the audio token to the computing system wherein the computing system configures a merchant computing device at a location to broadcast the audio token to a user computing device via an audio communication channel; computer-executable program instructions to receive the audio token from the user computing device;
  • Example 20 The computer program product of example 19, wherein the merchant computing device broadcasts the audio token via an audio component comprising a speaker.
  • Example 21 The computer program product of example 19 or 20 wherein the data comprise transaction details comprising payment account information and a total amount of transaction, and further comprising:
  • Example 22 The computer program product of at least one of the examples 19 to 21, wherein associating the audio token with the received data comprises storing the audio token and the received data in a quick response code library.

Abstract

La présente invention concerne un système de commerçant qui préconfigure un jeton audio en associant le jeton audio avec des données de jeton audio et qui transmet le jeton audio préconfiguré à un système de gestion de compte avec les données de jeton audio sur un réseau. Le système de commerçant diffuse ensuite le jeton audio à l'aide du dispositif informatique de commerçant par l'intermédiaire d'un canal de communication audio au niveau d'un emplacement de commerçant. Un dispositif informatique d'utilisateur associé à un utilisateur utilise une bibliothèque de codes QR pour identifier des données de jeton audio stockées sur la bibliothèque de codes QR associée au jeton audio reçu. Le dispositif d'utilisateur affiche les données stockées ou exécute par ailleurs des instructions en fonction des données de jeton audio stockées. Dans un exemple, le dispositif informatique d'utilisateur communique avec le système de gestion de compte par l'intermédiaire du réseau pour demander et recevoir les données de jeton audio associées au jeton audio reçu à partir de la bibliothèque de codes QR stockée sur le système de gestion de compte.
PCT/US2018/037751 2017-08-16 2018-06-15 Code lisible par machine audible WO2019036094A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201880053311.0A CN110998637A (zh) 2017-08-16 2018-06-15 可听的机器可读代码

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201762546145P 2017-08-16 2017-08-16
US62/546,145 2017-08-16

Publications (2)

Publication Number Publication Date
WO2019036094A1 true WO2019036094A1 (fr) 2019-02-21
WO2019036094A8 WO2019036094A8 (fr) 2019-04-11

Family

ID=62842266

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2018/037751 WO2019036094A1 (fr) 2017-08-16 2018-06-15 Code lisible par machine audible

Country Status (2)

Country Link
CN (1) CN110998637A (fr)
WO (1) WO2019036094A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017029605A1 (fr) * 2015-08-19 2017-02-23 Soundpays Inc. Système et procédé pour interactions à médiation de signaux audio
US20170228720A1 (en) * 2016-02-10 2017-08-10 Aintu Inc. Method and System for Contactless Payments

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8245044B2 (en) * 2008-11-14 2012-08-14 Visa International Service Association Payment transaction processing using out of band authentication
US8463705B2 (en) * 2010-02-28 2013-06-11 International Business Machines Corporation Systems and methods for transactions on the telecom web
WO2012151590A2 (fr) * 2011-05-05 2012-11-08 Transaction Network Services, Inc. Systèmes et procédés permettant d'effectuer des paiements mobiles
US20160071094A1 (en) * 2014-09-05 2016-03-10 Ebay Inc. Systems and methods for implementing hybrid dynamic wallet tokens

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017029605A1 (fr) * 2015-08-19 2017-02-23 Soundpays Inc. Système et procédé pour interactions à médiation de signaux audio
US20170228720A1 (en) * 2016-02-10 2017-08-10 Aintu Inc. Method and System for Contactless Payments

Also Published As

Publication number Publication date
WO2019036094A8 (fr) 2019-04-11
CN110998637A (zh) 2020-04-10

Similar Documents

Publication Publication Date Title
US10769609B2 (en) Network security based on proximity with IP whitelisting
CA2998735C (fr) Securite de reseau basee sur la proximite
US10448313B2 (en) Identifying users via mobile hotspots
US20200042693A1 (en) Confirming the identity of integrator applications
US11062296B2 (en) Symmetric discovery over audio
US20170255941A1 (en) Facial Template And Token Pre-Fetching In Hands Free Service Requests
US10581814B2 (en) Re-programmable secure device
US20180053176A1 (en) Tap And Pair Via Proximity Sensing
WO2019125548A1 (fr) Interface utilisateur graphique créée par l'intermédiaire d'entrées à partir d'un document électronique
US11683104B2 (en) Audio based service set identifier
US11431426B2 (en) Mobile service requests to any sound emitting device
US20160005023A1 (en) Conducting financial transactions by telephone
WO2019036094A1 (fr) Code lisible par machine audible
EP3616392B1 (fr) Appariement de dispositifs informatiques par l'intermédiaire de canaux de communication audio
WO2019040149A1 (fr) Dispositif émetteur de sons permettant de communiquer des jetons audio

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18738108

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18738108

Country of ref document: EP

Kind code of ref document: A1