WO2015035055A1 - Procédés et systèmes pour utiliser des codes pouvant être balayés afin d'obtenir un service - Google Patents

Procédés et systèmes pour utiliser des codes pouvant être balayés afin d'obtenir un service Download PDF

Info

Publication number
WO2015035055A1
WO2015035055A1 PCT/US2014/054103 US2014054103W WO2015035055A1 WO 2015035055 A1 WO2015035055 A1 WO 2015035055A1 US 2014054103 W US2014054103 W US 2014054103W WO 2015035055 A1 WO2015035055 A1 WO 2015035055A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
scan
information
event
code
Prior art date
Application number
PCT/US2014/054103
Other languages
English (en)
Inventor
Peter Joseph Marsico
Stuart Howard KUPINSKY
Original Assignee
Flashback Survey, Inc.
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 Flashback Survey, Inc. filed Critical Flashback Survey, Inc.
Publication of WO2015035055A1 publication Critical patent/WO2015035055A1/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
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management

Definitions

  • the subject matter described herein relates to methods and systems for using a scan-able code to initiate and facilitate the providing of a scan-triggered service to a user.
  • Information collection systems that are typically deployed to gather information from a consumer of goods and services are often intrusive and time consuming from the perspective of the consumer. While such information collection systems are capable of gathering detailed information from a consumer, these systems do not give the user an incentive to participate or an easy way to obtain high-utility services.
  • the subject matter described herein includes systems and methods for surveying a user using a scan-able information element, such as a radio frequency identification (RFID) encoded tag, a near field communication (NFC) encoded tag, or an encoded graphic image, such as a bar code or a quick response (QR) code tag.
  • a mobile communication device such as a smartphone, tablet computer, computer-integrated eyewear, wearable computer or communication devices, or other mobile computer is adapted to include a scan-enabled client module for scanning and communicating scan- triggered service code information.
  • a scan- triggered service code is associated with a seat or location in an event venue, and when scanned by a user is adapted to enable the user to place an order for a good or service, which can then be delivered to the user's seat or location.
  • a scan- triggered service code is associated with a scheduled event, and when scanned by a user is adapted to cause an electronic calendar invitation to be generated and transmitted to the user.
  • the user may also be granted a digital reward in response to scanning of the associated event scan code, and/or may be granted a digital in response to accepting the associated electronic calendar event invitation.
  • a scan- triggered service code is associated with a time sensitive or time-window based voting or rating service, that when scanned by a user within a dynamic voting/rating time-window is adapted to register and record the user's vote / rating information.
  • a scan- triggered service code is associated with a good or service identifier, and when scanned by a user is adapted to cause the associated good or service to be added to an online goods or service information repository that is associated with the user's scan-triggered service account, which the user may subsequently access and browse.
  • the subject matter described herein for facilitating scan-triggered services may be implemented in hardware, software, firmware, or any combination thereof.
  • the terms "function" or “module” as used herein refer to hardware, software, and/or firmware for implementing the feature being described.
  • the subject matter described herein may be implemented using a non-transitory computer readable medium having stored thereon computer executable instructions that when executed by the processor of a computer perform steps.
  • Exemplary computer readable media suitable for implementing the subject matter described herein include disk memory devices, programmable logic devices, application specific integrated circuits, and downloadable electrical signals.
  • a computer readable medium that implements the subject matter described herein may be located on a single device or computing platform distributed across multiple physical devices and/or computing platforms.
  • FIG. 1 is a functional block diagram which illustrates a mobile communication device that includes a scan-able code reader module, such as a quick response (QR) code scanner module and exemplary scan-enabled client module;
  • a scan-able code reader module such as a quick response (QR) code scanner module
  • QR quick response
  • Figure 2 is a functional block diagram which illustrates an application server that includes an exemplary server application module
  • Figures 3A-D generally illustrate exemplary ServeMe Square provisioning, processing and data structures associated with a first exemplary embodiment of ServeMe Square scan-triggered service
  • Figures 4A-B generally illustrate exemplary ServeMe Square provisioning, processing and data structures associated with a second exemplary embodiment of ServeMe Square scan-triggered service
  • Figures 5A-C generally illustrate exemplary ServeMe Square provisioning, processing and data structures associated with a third exemplary embodiment of ServeMe Square scan-triggered service
  • Figures 6A-B generally illustrate exemplary ServeMe Square provisioning, processing and data structures associated with a fourth exemplary embodiment of ServeMe Square scan-triggered service
  • Figures 7A-B illustrate exemplary data and data structures associated with embodiments of the ServeMe Square scan-triggered service
  • Figure 8A-8B generally illustrate exemplary ShowUp Square provisioning, processing and data structures associated with an exemplary embodiment of ShowUp Square scan-triggered service
  • Figure 8C illustrates exemplary data and data structures associated with embodiments of the ShowUp Square scan-triggered service
  • Figure 9A-9D generally illustrate exemplary Invite Square provisioning, processing and data structures associated with a first exemplary embodiment of Invite Square scan-triggered service
  • Figure 9E-9F generally illustrate exemplary Invite Square provisioning, processing and data structures associated with a second exemplary embodiment of Invite Square scan-triggered service
  • Figure 9G illustrates exemplary data and data structures associated with embodiments of the Invite Square scan-triggered service
  • Figure lOA-lOC generally illustrate exemplary Calllt Square provisioning, processing and data structures associated with an exemplary embodiment of Calllt Square scan-triggered service
  • Figures 10D-10E illustrate exemplary data and data structures associated with embodiments of the Calllt Square scan-triggered service
  • Figure 11A-11C generally illustrate exemplary Savelt Square provisioning, processing and data structures associated with an exemplary embodiment of Savelt Square scan-triggered service
  • Figure 11D illustrate exemplary data and data structures associated with embodiments of the Savelt Square scan-triggered service.
  • a scan-able code such as quick response (QR) code, a near field communication (NFC) code, radio frequency identification (RFID) code, or similar optical, magnetic or electrical scan-able codes, to provide a service to a user who scans the code.
  • a scan code-based services system of the subject matter described herein includes a scan- enabled client module, which may be implemented in hardware, software, firmware or a combination thereof and which resides on a mobile communication device, such as a smartphone, tablet computer, netbook computer, computer-integrated eyeglasses, computer-integrated wristwatch, wearable electronics or other mobile computing device that is capable of communicating with a network server.
  • the scan-enabled client module may include an executable computer program (e.g., C++, Java, etc.) that is adapted to be downloaded onto the mobile communication device, installed and executed.
  • the scan-enabled client module may also include a WEB browser that is adapted to access and execute WEB-based software (e.g., JavaScript, etc.) that provides a least a portion of the necessary scan-enabled client functionality.
  • Figure 1 is a block diagram that illustrates an exemplary architecture of a smartphone-based scan-enabled client module.
  • Smartphone 100 includes a camera module 102 that is adapted to capture and store an image in a digital format.
  • Smartphone 100 also includes a scan-enabled client module 104.
  • Scan-enabled client module 104 is comprised of scan-able code reader module 106, a user interface module 108, an administration module 110, a scan control logic module 112, a participation reward control logic module 114, a data storage module 116, a communication module 118, geo-location module 120, and at least one processor 122.
  • the extracted scan-triggered service information may comprise information that is representative, for example, of an alphanumeric text string, a numeric code.
  • the extracted scan-triggered service information may be used to identify and facilitate the providing of scan-triggered rewards based on the scanning of service scan codes.
  • the decoded scan code information is provided to an associated server application module via communication module 118.
  • scan code reader module 106 is adapted to receive digital image information from camera module 102 and to communicate the digital image information (e.g., JPEG) to an associated server application module via communication module 118 where decoding processing is performed.
  • information that identifies or can be used to identify a scan-triggered service user e.g., user name, user ID, session ID, etc. is also provided to the server application module.
  • User interface module 108 is adapted to present the mobile device user with a graphical user interface for enabling the user to generally control and operate the functionality of the scan-enabled client module 104.
  • User interface module 108 is adapted to present a menu structure to the user and enable the user to navigate this menu structure.
  • the menu structure provides a user with access to administrative functions, such as scan triggered service account settings (e.g., username, password, service preferences, personal information, etc.), account log-in. Such administrative functions are controlled within scan-capable or scan-enabled client module 104 via administration module 110.
  • the menu structure may also provide the user with the ability to control the associated smartphone camera.
  • scan-enabled client module 104 may include a native application that is adapted to execute on mobile device 100, and in such a case that native application may include QR scanning / decoding capability or alternatively scan-enabled client module 104 may simply invoke the services of a third-party QR scanner / decoder that is installed in the mobile device.
  • a third-party QR scanner / decoder may be invoked by the mobile device user to scan and decode a suitably provisioned QR, where decoding of the QR code causes a WEB browser instance to be launched and directed to a URL associated with the application server.
  • information that identifies the relevant / necessary scan-triggered service information may be passed to the application server via the URL/URL parameters.
  • information that identifies a scan-triggered service and relevant / necessary service information may be explicitly or implicitly communicated to the application server via the URL itself (e.g., the host name and/or path and/or query string components of the URL can be used by the application server to explicitly or implicitly identify the service information).
  • all communications between the user's mobile device and the application server may be addressed to a URL which points to a scan-based service provider (e.g., www.flashbacksurvey.com), and the information that identifies the scan-triggered service may be communicated to the scan-based service provider's application server via the path and/or query string parameter portions of the URL.
  • a URL address associated with the scan- triggered service platform may be encoded or otherwise incorporated into a scan code associated with a scan-triggered service platform, or which requests scan- triggered application service from a scan-triggered service platform.
  • the URL which points scan-based service provider e.g., www.flashbacksurvey.com
  • the information that identifies the scan-triggered service may be encrypted, such that only a particular code scanner, native mobile code scanning application, or mobile WEB browser with integrated code scanning capability which has access to or is provisioned with the appropriate decryption / de- obfuscation key information can decode and process the scan-triggered service URL information and thereby facilitate the providing of the associated scan-triggered service.
  • a particular scan- triggered service code may be "locked" to all code scanners but the scanner that has access to / is provided with the appropriate decrypt / de-obfuscation key information, thereby providing users with an added measure of security with respect to accessing scan-triggered services.
  • the menu structure also provides the user with the ability to access and redeem participation rewards. Participation reward access and redemption functionality is provided by reward control logic module 114.
  • Data storage module 116 is adapted to provide both long term storage of data associated with the scan- enabled client module, as well as short term, cache-type storage of scan client related data. Exemplary uses of the data storage are discussed in more detail in the disclosure that follows.
  • Communications module 118 is adapted to facilitate the communication of information between scan-enabled client module 104 and an associated server application module.
  • communication module 118 may receive information from scan control logic module 112 that is to be communicated to an associated server application module.
  • Communication module 118 may package the information according to a pre-defined message format and forward the message to a data communications interface associated with the smartphone.
  • Exemplary data communication interfaces may include, but are not limited to, a General Packet Radio Service (GPRS) interface, an Enhanced Data Rates for GSM Evolution (EDGE), High Speed Packet Access (HSPA), WiMax, WiFi, LTE, etc.
  • GPRS General Packet Radio Service
  • EDGE Enhanced Data Rates for GSM Evolution
  • HSPA High Speed Packet Access
  • WiMax Wireless Fidelity
  • communication module 118 when a user scans a service scan code associated with a scan-triggered service, communication module 118 is adapted to communicate to an associated server application module information that was encoded in the scanned service code as well as information that can be used to identify the user.
  • Information that can be used to identify the user may include a user identifier (e.g., usemame, email address, mobile IP address, session ID, etc.). It will be appreciated that the communication of such user identifying information to the server module may be triggered upon scanning of the QR code or may be triggered upon startup of software associated with scan-enabled client module 104 (e.g., auto-login, manual login, etc.).
  • the communication of user identifying information and information obtained from the scanning of a scan code may be accomplished via a single message that is communicated between scan-enabled client module 104 and an associated server module, or this information may be communicated via multiple messages to the application server module.
  • a communication channel or session is established between a scan- enabled client module (e.g., a smartphone WEB browser or native application) and a server application module (e.g., an application residing on a network-based host computer), and all subsequent communications made via the session or channel are associated with the user's login credential / identity information.
  • a user's identity information may be provided before, during, or even after the scanning of an associated service scan-able code (e.g., QR code, NFC code, RF1D code, etc.), and thereafter bound to the information derived or obtained from scanning of the code.
  • an associated service scan-able code e.g., QR code, NFC code, RF1D code, etc.
  • the scanning of a scan code by a user triggers the scan-enabled client module 104 to access previously stored login credential information (e.g., login credential information stored in a file or cookie that is resident on mobile communication device 100.
  • Scan-enabled client module 104 automatically provides the user's login credentials to the application server module, which then associates the information obtained from the scanning of the scan code with the user's account. Once the session is established, information obtained and provided to the application server module is automatically associated with the user's account.
  • Geo-location module 120 is adapted to determine geo-location information indicative of the geographic position of mobile communication device 100.
  • Geo- location information determined by module 120 may include Global Positioning System (GPS) coordinate information (e.g., latitude, longitude, elevation).
  • GPS Global Positioning System
  • Module 120 may determine this geo-location information and generally facilitate the communication of this information to an associated server application module in conjunction with the communication of scanned graphic icon (e.g., QR code) information, thereby enabling the server application module to identify and store the location at which a QR code was scanned.
  • GPS Global Positioning System
  • QR code e.g., QR code
  • mobile device 100 becomes a special purpose computing platform that improves the functionality of mobile device 100 by providing direct access to a server application in response to receiving a scanned code from camera module 102.
  • Mobile device 100 with scan-enable client module 104 also improves the technical field of network access to services because such services can be accessed automatically and quickly with a reduced likelihood of data entry errors.
  • Processor 122 is adapted to facilitate the execution of software and firmware associated with the operation of modules 106, 108, 110, 112, 114, 116, 118 and 120, which is used to provide the overall scan- enabled client module functionality described herein.
  • processor 122 includes, but are not limited to, one or more single-core microprocessors, one or more mutli-core microprocessors, one or more application specific integrated circuits, and one or more programmable logic devices (e.g., a complex programmable logic devices, a field-programmable gate arrays, etc.).
  • processor 122 includes, but are not limited to, one or more single-core microprocessors, one or more mutli-core microprocessors, one or more application specific integrated circuits, and one or more programmable logic devices (e.g., a complex programmable logic devices, a field-programmable gate arrays, etc.).
  • FIG. 2 is a block diagram that illustrates an exemplary architecture of a server application module 202, which resides and executes on a network or cloud- hosted application server 200.
  • the server application module is comprised of a provisioning, administration and billing module 204, a reporting module 206, a showup square control logic module 208, a reward control logic module 210, a data storage module 212, a communication module 214, a serveme square control logic module 216, a invite square control logic module 218, a saveit square control logic module 220, a callit square control logic module 222, and at least one processor 224.
  • the purpose and function of each of these modules is described below.
  • Server application module 202 executing on application server 200 makes application server 200 a special purpose computing platform that improves the functionality of application server 200 by configuring application server 200 to process received scanned codes and providing the indicated service in response to receiving the scanned codes. As such, server application module 202 improves the technical fields of network access to services by providing such services automatically in response to receiving the scanned codes and with a reduced likelihood of data entry error.
  • Provisioning, administration and billing module 204 is adapted to provide access for a user, such as a merchant entity, a delivery service vendor entity, an event venue entity, mobile user entity or a system administrator, to provision registration information, subscription configurations / preference information, service configuration information, and participation reward content information.
  • a user is considered to be the operator or user of a mobile communication device (e.g., smartphone, tablet computer, etc.) that includes a scan-enabled client module, and is therefore capable of scanning a QR code (or other encoded, scan-able code) and provide, trigger, initiate or facilitate the providing of a service to the user.
  • a user may be a consumer of goods and services provided by a merchant, an attendee of an event, a shopper, or an employee of a corporation.
  • a scanning user may be granted or credited with a digital reward or coupon in response to the scanning of an associated scan-triggered service code.
  • exemplary digital rewards may include, but are not limited to, a digital or electronic coupon associated with a good or a service, a credit for an online gaming service, a credit for an online video, an audio or video download.
  • the value of a granted digital reward may be determined, based at least in part, on the type / brand / manufacturer of the mobile phone that was used to scan the associated scan-triggered service scan code.
  • such rewards may be credited or placed in a digital reward wallet associated with the user, whereby the user can access and redeem a granted reward.
  • a reward granted to a user may be granted at a first value (e.g., $1 off next purchase) and subsequently modified to a second value (e.g., $2 off next purchase) at a later by Reward Control Module 210.
  • Module 210 may facilitate the sharing of a scan-triggered service platform- granted reward from one user to another user, where sharing may include the gifting, transferring, or cloning of a granted reward.
  • a first user who is the current owner of a reward selects the reward and identifies a second user to whom the reward is to be transferred.
  • the first user then communicates information that identifies both the reward and the "transferred to" user to module 210.
  • the information that identifies the "transferred to" or recipient user may be a username or user ID provided by the recipient user at the time of registration by the recipient user.
  • Module 210 receives, processes and logs the transfer request and updates the appropriate reward data so as to execute the transfer.
  • reporting module 206 enables an administrative entity or user to view, track and analyze such reward transfers.
  • restrictions / limitations / qualifications may be imposed on rewards that are to be transferred or gifted from one user to another.
  • module 210 may include reward transfer or gifting rules that specify those conditions under which a reward may be transferred and/or those conditions under which a reward may not be transferred. These rules may be stored in a database, table, or data structure that is contained within or accessible by module 210.
  • An exemplary rule may state that a reward may only be transferred or gifted to a new user (e.g., a user that has registered for service within the past 30 days, etc.).
  • this rule module 210 may access user registration data that is maintained in data storage module 212.
  • Another exemplary rule may state that a reward may only be transferred or gifted to a user who has not previously patronized the scan-triggered service client entity with which the reward is associated.
  • In order to enforce this rule module 210 may access user transaction data that is maintained in data storage module 212.
  • reward sharing functionality includes functionality where an existing user may clone/copy, transfer or gift a reward to an individual who has not yet become a registered scan-triggered service user.
  • the existing user communicates information that identifies both the reward and the "transferred to" or recipient user to module 210.
  • the existing user since the recipient user is not yet a registered user of the system / service, the existing user must specify a public contact address for the intended recipient.
  • Exemplary public contact addresses may include, but are not limited to, an email address, a mobile telephone number, a mobile subscriber ISDN (MSISDN), a Twitter address, an instant message address.
  • Module 210 receives processes and logs the transfer request.
  • module 210 is adapted to generate a message that is addressed to the specified public contact address (e.g., email address).
  • the message may include the transferred reward or information specifying how the transferred reward may be obtained and redeemed.
  • the message may include information that describes the pending reward transfer and also provides a hyperlink / URL associated with a WEB page where the intended recipient may register and thereby receive and redeem the transferred reward.
  • the existing user that transferred or gifted the reward (thereby resulting in the recruitment / registration of a new subscriber) may be issued a new reward as a result of the transfer.
  • the new reward may be the same as the transferred reward or different.
  • the new reward may be issued by reward control logic module 210.
  • Processor 224 is adapted to facilitate the execution of software and firmware associated with the operation of modules 204, 206, 208, 210, 212, 214, 216, 218, 220 and 222, which is used to provide the overall server application module functionality described herein.
  • Exemplary implementations of processor 224 include, but are not limited to, one or more single-core microprocessors, one or more mutli-core microprocessors, one or more application specific integrated circuits and one or more programmable logic devices (e.g., a complex programmable logic devices, a field-programmable gate arrays, etc.).
  • Figure 3 A is diagram that generally illustrates the provisioning of information associated with a service of a scan code-based service system according to an embodiment of the subject matter described herein.
  • This service is referred to herein as ServeMe Square service, which is a service that facilitates deliverable vending services at an event venue.
  • a deliverable service is a service that entails the delivery of an item (e.g., food, drink, gift, etc.) to the location / seat of the user who placed the order for the item. Exemplary provisioning of information associated with one embodiment of the service is shown in Figure 3A.
  • an entity associated with or acting on behalf of an event venue (e.g., football stadium, basketball arena, hockey arena, soccer stadium, baseball stadium, movie cinema, theatrical playhouse, concert venue, amphitheater, etc.) is adapted to use a computer terminal 600 to access and provide provisioning data to an application server 200, which is hosting the ServeMe Square service application.
  • the provisioning entity logs into a ServeMe Square service provisioning interface associated with server 200, as indicated in step 1.
  • the provisioning entity provides seat identifier / identification information for some or all seats associated with a particular event at the event venue, as indicated in step 2.
  • step 3 the ServeMe Square application returns or provides access to information which is to be encoded in a scan-able ServeMe Square Binding code that is placed on or associated with each ticket that is sold / distributed to the event being hosted at the event venue.
  • Figure 3B is a diagram that generally illustrates the provisioning of information by a delivery service vendor associated with the ServeMe Square service.
  • a delivery service entity e.g., administrator
  • a concession vendor e.g., food vendor, drink vendor, gift shop vendor, etc.
  • an application server 200 which is hosting the ServeMe Square service application.
  • the provisioning entity logs into a ServeMe Square service provisioning interface associated with server 200, as indicated in step 1.
  • the provisioning entity provides information that defines a list of menu item options (e.g., "Large Diet Coke - $5", “Small Diet Coke - $3", etc.), as shown in step 2.
  • the provisioning entity specifies which menu items will have an associated Item Order Request QR code generated by the ServeMe Square application, as indicated in step 3.
  • a separate ServeMe Square Item Order Request QR code is generated for each of the appropriately provisioned / specified menu items.
  • codes may then be deployed in any number of ways at the associated event / event venue, including, but not limited to, printing them in event program guides, printing them on handouts and flyers, placing them on the event tickets, placing them on stickers affixed to event seats, displaying them on a large viewing screen, TV monitor, computer monitor, scoreboard, placing them on cups or bags, etc.
  • FIGs 3C and 3D are exemplary process flow diagrams which generally illustrate use and operation of this embodiment of the ServeMe Square service.
  • a user scans a ServeMe Square binding QR code that has been previously generated and printed or placed on their event ticket.
  • This binding QR code includes information which uniquely identifies the event and the user's seat within the event venue (e.g., Section 12, seat 22).
  • the user is already a registered user of the scan-based service system, and scanning of the ServeMe Square binding QR code causes the user's login credentials to be automatically provided to the ServeMe Square application server 200 at the time of the scan along with the information that uniquely identifies the event and the user's seat within the event venue, as indicated in step 1.
  • ServeMe Square application server 200 receives this information and generates a binding record for the user, which associates, links, or binds the user to the provided event venue seat identification information.
  • This binding record is stored in data storage module 212 which is associated with ServeMe Square application server 200.
  • Exemplary binding record data is illustrated in Table 4 of Figure 7.
  • the scanning user was not a previously registered user of the system, in one embodiment, the user would be prompted to provide registration information, which might include name, email address, and other personal data. Once registered, the binding record would be generated in a manner similar to that described above.
  • the user scans an Item Order Request QR code (e.g., a code associated with a "Large Diet Coke for $5"). Scanning of the Item Order Request QR code causes the scan-enabled client module 104 to communicate user identifying / user login credentials to ServeMe Square application server 200 along with information that identifies the menu item option associated with the scanned Item Order Request QR code (i.e., "Large Diet Coke for $5"), as indicated in step 1.
  • ServeMe Square application server 200 receives the delivery order request and responds with a query to the user that is displayed on their mobile communication device, which asks for the quantity of the ordered item, as indicated in step 2.
  • step 3 the user responds by indicating that a quantity of 2 are being requested / ordered.
  • step 4 ServeMe Square application server 200 accesses credit card information for the user that has been kept on file, charges the user's credit card for the amount of the order, and responds to the user with a receipt.
  • step 5 ServeMe Square application server 200 then communicates the order information, the ordering user's seat identifying information, and payment status to a delivery service order fulfillment system 604, which is located at the event venue. Personnel working the delivery service vendor's concession can then fill the order and deliver the ordered product(s) to the specified seat of the ordering user.
  • Figures 4A and 4B illustrate an alternate embodiment that includes the use of a binding QR code similar to the previously described embodiment, but which utilizes a ServeMe Square Menu Request QR code instead of an Item Order Request QR code. Provisioning of the binding QR code is similar to that shown in Figure 3C, and as such a detailed description of binding QR code provisioning is not repeated here.
  • Figure 4A generally illustrates provisioning of a ServeMe Square Menu Request QR code.
  • the provisioning delivery service entity provides ServeMe Square application server 200 with menu selection option information (e.g., Large Diet Coke - $5, Pizza Slice - $3, etc.), as indicated in steps 1 and 2.
  • menu selection option information e.g., Large Diet Coke - $5, Pizza Slice - $3, etc.
  • a user scans a ServeMe Square binding QR code that has been previously generated and printed or placed on their event ticket, the same as in the previous embodiment example.
  • a detailed discussion of the binding code QR scan is not repeated here.
  • the user scans a Menu Request QR code (e.g., a code associated with a particular delivery service vendor, such as "Luigi's Pizza By The Slice”). Scanning of the Menu Request QR code causes the scan-enabled client module 104 to communicate user identifying / user login credentials to ServeMe Square application server 200 along with information that identifies the delivery service vendor associated with the scanned Item Order Request QR code (i.e., "Luigi's Pizza By The Slice"), as indicated in step 1.
  • a Menu Request QR code e.g., a code associated with a particular delivery service vendor, such as "Luigi's Pizza By The Slice”
  • Scanning of the Menu Request QR code causes the scan-enabled client module 104 to communicate user identifying / user login credentials to ServeMe Square application server 200 along with information that identifies the delivery service vendor associated with the scanned Item Order Request QR code (i.e., "Luigi's Pizza By The Slice"), as indicated in step 1.
  • ServeMe Square application server 200 receives the menu order request and responds with menu item option information for Luigi's Pizza By The Slice (e.g., Large Diet Coke - $5, Pizza slice - $3, etc.), as indicated in step 2.
  • the user responds by indicating the menu items and associated quantities that they would like to order.
  • ServeMe Square application server 200 accesses credit card information for the user that has been kept on file, charges the user's credit card for the amount of the order, and responds to the user with a receipt.
  • ServeMe Square application server 200 then communicates the order information, the ordering user's seat identifying information, and payment status to a delivery service order fulfillment system 604, which is located at the event venue. Personnel working the delivery service vendor's concession can then fill the order and deliver the ordered product(s) to the specified seat of the ordering user.
  • Figures 5A and 5B illustrate alternate embodiments, that include the use of a binding QR code similar to the previously described embodiment, but which utilizes a ServeMe Square Service Request QR code instead of a Menu Request QR code. Provisioning of the binding QR code is similar to that shown in Figure 3C, and as such a detailed description of binding QR code provisioning is not repeated here.
  • Figure 5A generally illustrates provisioning of a ServeMe Square Service Request QR code.
  • an event venue provisioning entity uses computer terminal 602 to communicate a list of delivery service vendors to ServeMe Square application server 200, as indicated in steps 1 and 2.
  • Service Request QR codes are generated by or with information obtained from ServeMe Square application server 200, as indicated in step 3, copies of which may be deployed around the event venue in a manner similar to that previously described.
  • the provisioning delivery service entity provides ServeMe Square application server 200 with menu selection option information (e.g., Large Diet Coke - $5, Pizza Slice - $3, etc.), as described in steps 1 and 2 of the previous example.
  • menu selection option information e.g., Large Diet Coke - $5, Pizza Slice - $3, etc.
  • a user first scans a ServeMe Square binding QR code that has been previously generated and printed or placed on their event ticket, the same as in the previous embodiment example. As this portion of the process flow is identical to the previous example, a detailed discussion of the binding code QR scan is not repeated here.
  • the user scans a Service Request QR code (e.g., a code associated with a general request for delivery service by an as yet unspecified delivery service vendor). Scanning of the Service Request QR code causes the scan- enabled client module 104 to communicate user identifying / user login credentials to ServeMe Square application server 200, as indicated in step 1.
  • ServeMe Square application server 200 receives the Service request and responds with a list of delivery service vendors, as indicated in step 2.
  • the user responds by selecting one of the delivery service vendors.
  • ServeMe Square application server 200 responds with a list of menu item options for the selected delivery service vendor.
  • the user responds with a list of selected menu item options and quantities, as well as payment information.
  • ServeMe Square application server 200 accesses credit card information for the user that has been kept on file, charges the user's credit card for the amount of the order, and responds to the user with a receipt (not shown).
  • ServeMe Square application server 200 then communicates the order information, the ordering user's seat identifying information, and payment status to a delivery service order fulfillment system 604, which is located at the event venue. Personnel working the delivery service vendor's concession can then fill the order and deliver the ordered product(s) to the specified seat of the ordering user.
  • FIG. 5C illustrates an embodiment of the subject matter described herein that requires the scanning of only a single QR code to facilitate the processing of a ServeMe Square Service request.
  • the information encoded in the QR scan code printed on the event ticket includes information that not only identifies the seat of the user, but also includes information that triggers a Service request.
  • scanning of the integrated Binding+Service Request QR code causes the scan-enabled client module 104 to communicate user identifying / user login credentials, seat identifying information, and a Service request to ServeMe Square application server 200.
  • ServeMe Square application server 200 receives the Service request and responds with a list of delivery service vendors, as indicated in step 2.
  • step 3 the user responds by selecting one of the delivery service vendors.
  • step 4 ServeMe Square application server 200 responds with a list of menu item options for the selected delivery service vendor.
  • step 5 the user responds with a list of selected menu item options and quantities, as well as payment information.
  • ServeMe Square application server 200 accesses credit card information for the user that has been kept on file, charges the user's credit card for the amount of the order, and responds to the user with a receipt (not shown).
  • step 6 ServeMe Square application server 200 then communicates the order information, the ordering user's seat identifying information, and payment status to a delivery service order fulfillment system 604, which is located at the event venue. Personnel working the delivery service vendor's concession can then fill the order and deliver the ordered product(s) to the specified seat of the ordering user.
  • Figures 6 A and 6B illustrate an embodiment of the subject matter described herein that requires the scanning of only a single QR code to facilitate the processing of a ServeMe Square Menu request.
  • the information encoded in the QR scan code printed on the event ticket includes information that not only identifies the seat of the user, but also includes information that triggers a Menu request for a particular vendor. This provisioning is similar to previous provisioning examples, and is generally illustrated in Figure 6A.
  • step 1 scanning of the integrated Binding+Menu Request QR code (e.g., printed on the user's ticket) causes the scan-enabled client module 104 to communicate user identifying / user login credentials, seat identifying information, and a Menu request for a particular delivery service vendor to ServeMe Square application server 200.
  • ServeMe Square application server 200 receives the Service request and responds with a list of menu option items for the associated delivery service vendor, as indicated in step 2.
  • step 3 the user responds with a list of selected menu item options and quantities, as well as payment information.
  • ServeMe Square application server 200 accesses credit card information for the user that has been kept on file, charges the user's credit card for the amount of the order, and responds to the user with a receipt (not shown).
  • ServeMe Square application server 200 then communicates the order information, the ordering user's seat identifying information, and payment status to a delivery service order fulfillment system 604, which is located at the event venue. Personnel working the delivery service vendor's concession can then fill the order and deliver the ordered product(s) to the specified seat of the ordering user.
  • Tables 1 - 6 illustrate exemplary data and data structures associated with the exemplary ServeMe Square embodiments discussed herein, and include user identifier information 300 (e.g., scan-triggered service usemame, email address, etc.), username information 302, address / zip code information 304, credit / debit card information 306. Such user information would typically be provisioned by a user prior to using ServeMe Square service. Shown in Table 2 is exemplary event/seat-to-ServeMeSquarelD binding information that includes a ServeMeSquarelD identifier 308, an event ticket identifier 309, an event identifier 310, and a seat identifier 312. Such binding information would typically be provisioned at the time that the event ticket was generated.
  • user identifier information 300 e.g., scan-triggered service usemame, email address, etc.
  • username information 302 e.g., address / zip code information 304
  • Such user information would typically be provision
  • Shown in Table 3 is exemplary user-to-ServerMeSquarelD binding information that includes a ServeMeSquarelD identifier 308,a user identifier 314, and binding scan timestamp information 316. Such binding information is generated at the time a user first scans the ServeMe Square code on their event ticket.
  • Shown in Table 4 is exemplary delivery service information that includes a menu option scan code identifier 319, a delivery service entity identifier 320, delivery service entity name information 322, city 324, state 326, and zipcode information 328. It will be appreciated that in some embodiments of the present invention, a delivery entities menu may be associated with a MenuScanCodelD identifier 330 that may be encoded within a scan-able service code.
  • This menu scan code is bound to the delivery entities menu, and when scanned will present the scanning user with the delivery entities provisioned menu selection options.
  • a particular order-able menu item may have an associated scan code that incorporates the appropriate MenuOptionScanCodelD 331.
  • the menu option information may be displayed to the user following the scanning of a menu scan Table 5 includes exemplary food service menu information associated with a delivery service entity, which includes menu option identifier information 332, menu option text information 334, and menu option price information 336.
  • Such information would be provisioned in order to permit a food/service vendor to provide delivery services to users / event attendees using the ServeMe Square scan- triggered system.
  • Shown in Table 6 is exemplary ServeMe Square transaction record data that includes an order identifier 338, a delivery service entity identifier 340, an "ordering" ServeMeSquarelD 342, an order scan timestamp 344, and ordered menu item information 348.
  • a single, integrated scan code version of the menu item order request embodiment of the subject matter described herein is also within the scope of this disclosure.
  • a single QR code that includes user seat information, delivery service vendor identifying information, and menu item order request information can be generated, deployed and processed.
  • Embodiments of the subject matter described herein may include a system for providing a scan-triggered product hunt list service, the system comprising:
  • a computing platform including at least one processor:
  • a server application module executable by or embodied within the at least one processor and configured to:
  • a delivery service request that includes information obtained from the scanning of a scan-able delivery service request code which can be used to identify a location to which the requested good or service should be delivered;
  • the scan-enabled client module may reside on a mobile communication device.
  • creating an order for delivery of the selected goods or service to the delivery location includes communicating an order for the requested good or service to an order fulfillment system.
  • creating an order for delivery of the selected goods or service to the delivery location includes communicating a request for payment to the scan-enabled client module.
  • creating an order for delivery of the selected goods or service to the delivery location includes communicating a request for user identification information to the scan-enabled client module.
  • the delivery service request received from the scan- enabled client module also includes information that can be used to identify a good and service vendor. In one embodiment, the delivery service request received from the scan- enabled client module also includes information that can be used to identify the person / user of the scan-enabled client module placing the order.
  • creating an order for delivery of the selected goods or service to the delivery location includes communicating an order for the requested good or service to a concession vendor at an event venue.
  • information obtained from the scanning of a scan-able delivery service request code which can be used to identify a location to which the requested good or service should be delivered includes a seat identifier at an event venue.
  • Embodiments of the subject matter described herein may include a system for facilitating the placement of a delivery service request using information obtained from the scanning of a scan-able code by a scan-enabled client module, the system comprising:
  • a computing platform including at least one processor:
  • a server application module executable by or embodied within the at least one processor and configured to:
  • a delivery service request that includes information obtained from the scanning of a scan-able delivery service request code which can be used to identify a location to which the requested good or service should be delivered and a good or service;
  • FIG 8A is diagram that generally illustrates the provisioning of information associated with one embodiment of a service of a scan code-based service system of the subject matter described herein.
  • This service is referred to herein as ShowUp Square service, which is a service that facilitates attendance or presence validation of a user via the scanning of a ShowUp Square service scan code by the user.
  • ShowUp Square service might involve an event venue, such as a baseball stadium, and a merchant.
  • the owner of the baseball stadium negotiates a marketing campaign with the merchant (e.g., pizza shop) that involves offering anyone who attends baseball game #1 a discount on the merchant's product (e.g., $1 off next pizza).
  • ShowUp Square QR codes are displayed at fixed locations within the baseball stadium complex.
  • An attendee of the game uses his or her mobile phone-based QR code scanner's to scan one of the displayed ShowUp Square QR codes.
  • the user's scan is recorded by the scan-based ShowUp Square system, and the user is given an electronic coupon or reward associated with the merchant.
  • the scan-based ShowUp Square system also tracks and logs redemption of the granted reward by the user.
  • the merchant uses computer terminal 608 to log into a provisioning interface associated with an application server 200 that is hosting the ShowUp Square application, as indicated in step 1.
  • ShowUp Square campaign information such as, event venue identifying information, event date, event start time, event stop time, attendance reward information, ShowUp Square scan acceptance time window information, feedback question and response option information, feedback rating scale information .
  • scan-triggered application server 200 generates a ShowUpSquarelD value and binds this identifier to the event and associated event information.
  • server 200 creates and stores a binding record that associates the event (and event information) with the ShowUpSquarelD.
  • ShowUpSquarelD and/or a ShowUp Square QR code 510 is generated by or with the aid of ShowUp Square application server 200 and communicated to the provisioning entity 608. Copies of the ShowUp Square QR code 510 may be deployed in any number of ways and formats in and around the event stadium 512, step 5.
  • Figure 8B illustrates a user 100 who is in attendance at the game and scans ShowUp Square code 510.
  • the scanning of the ShowUp Square code causes the scan-enabled client module 104 to communicate information which can be used to identify the user (e.g., scan-triggered service user login credentials) and information that can be used to identify an event/event location (e.g., ShowUpSquarelD) to scan- triggered ShowUp Square application server 200, as indicated in step 1.
  • information e.g., scan-triggered service user login credentials
  • an event/event location e.g., ShowUpSquarelD
  • ShowUp SquarelD may be encoded into a ShowUp Square (e.g., "1234" "6789", etc.) and subsequently read/extracted by scan- enabled client module 104, where they are then provided to server 200.
  • a single alphanumeric code e.g., 5543#@15# A , etc.
  • ShowUp Square may be encoded into a ShowUp Square, which may subsequently be provided to and used by server 200 to identify an event and an associated merchant.
  • scan-triggered ShowUp Square application server 200 receives the scan code information, which includes user identifying / user login credentials, ShowUpSquarelD and, if the ShowUp Square scan information is received during a predefined attendance / scan acceptance window, server 200 responds with an acknowledgement message, as indicated in step 2.
  • scan- triggered application server 200 creates and stores a scan transaction record (see Table 10) that effectively creates a binding between the user and the associated event / scan location (e.g., the ballpark).
  • An AttendanceScanID 370 is assigned to the scan transaction and scan timestamp information 376 maybe included in the scan binding record, along with the received ShowUpSquarelD value 372.
  • a digital reward may be granted to the user (step 4). For example, if ShowUp Square Control Logic Module 208, determines that the user has not already been granted a reward for attending this event, then an attendance reward is granted to the user by Reward Control Logic Module 210. In one embodiment, a reward that is granted to the user may be placed in a digital reward wallet associated with the user's scan-triggered service account.
  • an electronic calendar event invitation associated with an upcoming event may be generated by server 200 in response to receiving the ShowUp Square scan information, and the invitation may be communicated to a contact address (e.g., email, Twitter, text message service, etc.) associated with the scanning user, step 5.
  • a contact address e.g., email, Twitter, text message service, etc.
  • server 200 may communicate one or more questions (e.g., "how was the event?", etc.) and associated response options (e.g., "It was great”, “it was ok”, “it was out”, etc.) to the user's mobile device 100. The user may select the appropriate response option and communicate the selected response option information to server 200, where it is logged and recorded.
  • server 200 may communicate rating scale information to the user, and request that the user rate or score the event based on the provided rating scale.
  • the user can specify a rating score and communicate the rating score information to server 200, where it is logged / recorded.
  • ShowUp Square service By using ShowUp Square service, as provided by server 200, event venue operators and/or merchants may easily execute partnered marketing agreements, whereby users are selectively rewarded by a merchant / reward sponsoring entity in exchange for attending a pre-determined event.
  • scan-triggered application server 200 may simultaneously provide such ShowUp Square services for multiple events which are sponsored by multiple merchants / reward sponsoring entities, as each binding record can be identified as being associated with a particular event and/or reward sponsoring entity.
  • server 200 may be provisioned to generate and transmit an electronic calendar event invitation (e.g., Google calendar invitation) for an upcoming / future event in response to receiving ShowUp Square scan information from a user (step 5).
  • an event venue operator is provided with a unique mechanism for distributing information related to upcoming events, in conjunction with ShowUp Square reward distribution.
  • Figure 8C illustrates exemplary data and data structures associated with the exemplary ShowUp Square embodiments discussed herein, and include user identifier information 300 (e.g., scan-triggered service username, email address, etc.), username information 302, address / zip code information 304, credit / debit card information 306.
  • user identifier information 300 e.g., scan-triggered service username, email address, etc.
  • username information 302 e.g., address / zip code information 304
  • Shown in Table 8 is exemplary event- to-ShowUpSquarelD binding information that includes a ShowUpSquarelD identifier 350, an event name/identifier 352, ShowUp Square scan acceptance time window information 354, and reward identifier 356.
  • ShowUp Square scan acceptance time window information e.g., Facebook, Twitter, etc.
  • reward identifier 356 e.g., reward identifier 356
  • Shown in Table 9 is exemplary reward information that includes a RewardID identifier 360, a reward description 362, and reward expiration date information 364.
  • Shown in Table 10 is exemplary ShowUp Square attendance scan transaction information that includes an AttendanceScanID identifier 370, a scanned ShowUpSquarelD value 372, a scanning user identifier 374, ShowUp Square scan timestamp information associated with the transaction 376, a granted RewardID identifier 378, and user feedback / rating information 380.
  • Embodiments of the subject matter described herein may include a system for facilitating the granting of an attendance-conditional reward to a user using information obtained from the scanning of a scan-able code by a scan-enabled client module, the system comprising:
  • a computing platform including at least one processor:
  • a server application module executable by or embodied with the at least one processor and configured to:
  • the system may receive from the scan-enabled client module information obtained from the scanning of a scan-able attendance confirmation scan code that can be used to identify a merchant, vendor or business entity
  • the system may, in response to receiving the EPL and user identifying information, grant the user an electronic coupon or reward.
  • the scan-enabled client module resides on a mobile communication device.
  • the server application module resides on a network application server.
  • the electronic coupon or reward is communicated to the mobile communication device. In one embodiment, the electronic coupon or reward is communicated to the user via email, Twitter, text message service, short message service, instant message service. Invite Square
  • FIG. 9 A is diagram that generally illustrates the provisioning of information associated with one embodiment of a service of a scan code-based service system of the subject matter described herein.
  • This service is referred to herein as Invite Square service, which is a service that facilitates the creation of a calendar event invitation for the user that is triggered via the scanning of an Invite Square service scan code by the user.
  • Invite Square service is a service that facilitates the creation of a calendar event invitation for the user that is triggered via the scanning of an Invite Square service scan code by the user.
  • Invite Square service might involve a wine merchant that has scheduled a wine tasting event for October 24, 2013 at 7pm at the merchant's Durham, NC store.
  • a user who receives a printed flyer from the merchant in the mail that includes an Invite Square code for the wine tasting event scans the Invite Square QR code using the QR code scanner on their mobile phone.
  • the Invite Square service may also provide the user with an electronic coupon or reward for requesting an invitation or for requesting and accepting an invitation to an event that is sponsored by the merchant.
  • the Invite Square service may facilitate and track redemption of the reward by the user.
  • Invite Square campaign information such as, event location / venue identifying information, event date, event start time, and associated participation reward (e.g., a reward that is granted in response to scanning the Invite Square code and requesting that an invitation to the event be sent, or a reward associated with receiving the invitation and accepting it, etc.) information.
  • participation reward e.g., a reward that is granted in response to scanning the Invite Square code and requesting that an invitation to the event be sent, or a reward associated with receiving the invitation and accepting it, etc.
  • Exemplary data tables and data structures associated with various embodiments of Invite Square service are presented in Figure 9G.
  • an Invite SquarelD value is generated and bound to the associated Event / Event information by Invite Square hosting scan-triggered application server 200.
  • server 200 creates and stores a binding record that associates the event (and event information) with the InviteSquarelD.
  • the InviteSquarelD value or a scan code containing the InviteSquarelD value is communicated to provisioning entity 608.
  • copies of the associated Invite Square QR code may be deployed in any number of ways and formats including, but not limited to, printed flyers, direct mailing collateral, in-store displays, computer monitor display, magazine advertisements, purchase receipts, etc.
  • a user scans Invite Square code 514.
  • the scanning of the Invite Square code causes the scan-enabled client module 104 to communicate user identifying / user login credentials and InviteSquarelD information to Invite Square application server 200, as indicated in step 1.
  • Invite Square application server 200 receives the scan code information, which includes user identifying / user login credentials and InviteSquarelD information, and responds with an acknowledgement message, as indicated in step 2.
  • Invite Square Control Logic Module 218 determines that the user has not already scanned this Invite Square code, then a scan transaction / binding record is created which associates the InviteSquarelD and the scanning user identifier, step 3.
  • the user identifying information is used to access a contact address, such as an email address associated with the user.
  • Such contact address information may be stored in data storage module 212.
  • the user identifying information provided by module 104 may be the user's email address, and as such no additional email address lookup processing is necessary.
  • Invite Square Control Logic Module 218, may cause a message or prompt to be sent and displayed to the user asking for an email address to which the event invite should be sent.
  • Invite Square application server 200 generates and sends or causes to be generated and sent an email containing a calendar invitation to an email address associated with the scanning user.
  • Invite Square Control Logic Module 218 may determine (based on prior provisioned rules) whether the user should be granted a reward in exchange for scanning the Invite Square code or for scanning the Invite Square code and subsequently accepting the associated calendar invitation that was sent. If a reward is to be granted, Reward Control Logic Module 210 may facilitate the crediting of the granted reward to the user's account, as indicated in step 6 of Figure 9C. In step 7, user 100 provides feedback or rating score information to server 200, where it is logged and stored. In one embodiment, such feedback or rating score information may be collected from the user upon a subsequent scanning of InviteSquare scan code 514 after the associated event or appointment has commenced or concluded.
  • server 200 is adapted to communicate one or more questions (e.g., "How was your appointment?", etc.) and associated response options (e.g., "Great", “Ok”, “Awful") to mobile device 100 following a scan of code 514.
  • the user may select the desired response option, which is then communicated to server 200, where it is bound to the Invite SquarelD and userlD information and stored.
  • rating scale information may be communicated to mobile device 100 following a scan of code 514, and the user may specify a rating score value, which is then communicated to server 200, where it is bound to the InviteSquarelD and userlD information and stored. In this way, user feedback or rating information associated with an Event or Appointment may be quickly and easily collected, analyzed, and reported.
  • Figure 9D illustrates an embodiment of the subject matter described herein where a scan-triggered server is adapted to receive a communication from a user's electronic calendaring service server 203, which indicates that the user has accepted a previous event invitation sent by server 200, and in response, server 200 grants the user a digital reward.
  • user 100 accepts an electronic calendar event invitation that was previously generated and sent by / on behalf of server 200.
  • a server 203 associated with the user's electronic calendaring service provider in response to the user's acceptance of the event invitation, communicates an "RSVP" invitation acceptance confirmation message and communicates this message to the originator of the event invitation, scan-triggered server 200 (step 7).
  • step 8 scan- triggered service logs the message and/or updates the user's associated event transaction / binding record (step 8) to log the invitation acceptance.
  • server 200 grants the user a digital reward (step 9), which may, for example, be credited to a digital reward wallet associated with the user's scan-triggered service account.
  • scheduling coordinator's computer 609 is adapted to generate the Invite Square QR code without first contacting / communicating with the scan-triggered application server 200.
  • scheduling coordinator's computer 609 includes a software module which is adapted to generate an Invite Square QR code that includes encoded information that identifies the schedulingEntity (e.g., the dental practice), date, time and location of the appointment.
  • a scheduling administrator e.g., healthcare office appointment scheduling staff, etc. uses a local computer / computer terminal 609 to schedule an appointment for a patient / user.
  • a software module associated with terminal 609 generates an InviteSquare appointment scan code that includes unique InviteSquarelD identifier information (and optionally other identifiers), step 1.
  • a local binding of the InviteSquarelD identifier information and the appointment schedule information is stored by terminal 609.
  • scan control logic module 112 communicates the scanned information, which includes InviteSquarelD information to application server 200.
  • User identifying information may also be communicated from mobile device 100 to scan-triggered application server 200 at or near the time of the associated InviteSquare scan (step 3).
  • Exemplary user identifying information may include, but is not limited to, an email address, a username associated with the scan- triggered service, etc.
  • InviteSquare Control Logic Module 218 receives and logs the InviteSquarelD and user identifying information, and as shown in Figure 9F, server 200 uses the received InviteSquarelD information to query terminal 609 (or a computer system associated with terminal 609). It will be appreciated that in one embodiment, server 200 may be adapted to use InviteSquarelD or other information obtained from the scanning of the associated InviteSquare to determine the network address / contact address of terminal 609. In any event, using the InviteSquarelD information server 200 requests appointment detail information from terminal 609 (step 4). Terminal 609 uses the InviteSquarelD information received from the server 200 request to access local appointment-to- InviteSquarelD binding records and obtain the requested appointment schedule detail information.
  • This appointment schedule detail information is returned to server 200 (step 5).
  • server 200 uses the appointment detail information along with user identifying information (e.g., user contact address information such as an email address, Twitter handle, Facebook posting address, etc.) to generate and transmit an electronic calendar event invitation (e.g., Google Calendar invitation, etc.) associated with the scheduled appointment to / towards the user.
  • user identifying information e.g., user contact address information such as an email address, Twitter handle, Facebook posting address, etc.
  • an electronic calendar event invitation e.g., Google Calendar invitation, etc.
  • the user receives and accepts the electronic calendar invitation, and is subsequently granted a digital reward (step 8), which may be placed in a digital reward wallet associated with the user' s scan-triggered service account.
  • Invite Square service embodiments described above may also be provided via a native Invite Square application that is installed on the user's smartphone.
  • information that identifies or can be used to identify the address of an Invite Square server to which the appointment information should be communicated need not be encoded within the Invite Square QR code that is displayed to and scanned by a user.
  • the information that identifies or can be used to identify the address of an Invite Square server may be pre-configured and stored in the smartphone's memory, such as in data storage module 116.
  • the native application may dynamically determine the address of the appropriate Invite Square server at the time of the Invite Square QR code scan by a user.
  • Invite Square processing is very similar to that described above, except that the address of the Invite Square server is not obtained by a user scan of an Invite Square QR code.
  • Figure 9G illustrates exemplary data and data structures associated with the exemplary Invite Square embodiments discussed herein, and includes a user identifier 300, user name information 302, user location / zipcode information 304.
  • Shown in Table 12 is exemplary InviteSquarelD to Event/ Appointment binding information, which includes an InviteSquarelD 390, Event or Appointment identifying information 392, Event or Appointment date/time information 394, and Event or Appointment location information 396. In one embodiment, this information may be "echoed" or otherwise displayed / provided to the scanning user at or shortly after the time of the associated Invite Square service code scan.
  • Reward information Shown in Table 13 is Reward information, which includes a RewardID 400, Reward description information 402, and Reward expiration date information 404.
  • Such digital Rewards may be distributed to scanning users, and placed, for example, in a digital reward wallet associated with the user's scan-triggered service account.
  • Shown in Table 14 is Invite Square scan transaction / binding record data, which is received and stored following the scanning of an Invite Square service code by a user.
  • the exemplary scan transaction record data includes an Invite SquarelD 410, a userlD 412, Event / Appointment invitation acceptance indicator 414, Follow-up service request indicator 416 (e.g 5 .
  • server 200 does the user want to receive another reminder about the Event / Appointment, if so server 200 generates a reminder message such as an email, text or Tweet and transmits this reminder to a contact address associated with the user prior to the Event / Appointment), a granted RewardID 418, and user feedback / rating information 419.
  • a reminder message such as an email, text or Tweet
  • FIG 10A is diagram that generally illustrates the provisioning of information associated with a service of a scan code-based service system according to an embodiment of subject matter described herein.
  • This service is referred to herein as Calllt Square service, which is a service that facilitates scan-triggered, time window or time context-dependent voting by users who scan an associated Calllt Square scan code. For example, mobile phone users watching a sporting event scan a Calllt Square scan code during a short duration time window immediately following a foul / penalty call to vote on whether the game official's call was good or not.
  • a time-window associated with the call e.g., time window starts when the penalty call occurred and lasts for 10 seconds, etc.
  • no further votes for that particular penalty call are tallied by the scan-triggered Calllt Square system.
  • a user's vote is triggered and communicated via the scanning of a Calllt Square service scan code by the user.
  • Calllt Square service might involve a user who is attending a professional hockey game. A penalty is called by the official.
  • a user disagrees with the call and uses the QR code scanner on their mobile phone to scan a Calllt Square QR code that is encoded with information that is interpreted by a scan- triggered server that is providing Calllt Square service as a "bad call” vote.
  • a user may be presented with a single Calllt Square scan code. When the user scans this Calllt Square scan code (during an open voting window), the user is presented with a voting "ballot" of possible vote response options, and the user is prompted to specify or select a vote response option value.
  • server 200 provides the voting "ballot" / possible vote response value selection information to the mobile user.
  • a mobile phone user watching an event scans a Calllt Square scan code during a prescribed rating window time period following the occurrence of a ratable incident (e.g., a great show, a slam dunk, a fast-break, etc.) during the game, where the scanned Calllt Square code has been pre-associated with a rating value.
  • a ratable incident e.g., a great show, a slam dunk, a fast-break, etc.
  • a rating value e.g., a great show, a slam dunk, a fast-break, etc.
  • server 200 opens a rating window for 10 seconds, and the mobile user can scan one of the three Calllt Square scan codes, thereby providing their rating input for the shot to server 200.
  • a user may be presented with a single Calllt Square scan code. When the user scans this Calllt Square scan code (during an open rating window), the user is prompted to specify or select a rating value.
  • server 200 provides rating scale / possible rating value selection information to the mobile user.
  • the scan-triggered server that is providing Calllt Square service is adapted to randomly or through some other selection means distribute digital coupons or rewards to users as a result of Calllt Square service participation.
  • granted digital rewards are credited to or deposited in a digital reward wallet associated with the user's scan-triggered service account.
  • the Calllt Square service may facilitate and track redemption of rewards by users.
  • the event organizer uses computer terminal 600 to log into a provisioning interface associated with an application server 200 that is hosting the Calllt Square application, as indicated in step 1.
  • Calllt Square campaign information such as, event location / venue identifying information, event date, event start time, vote collection time window duration (e.g., 10 seconds per votable event, etc.) and associated participation reward (e.g., a reward that is granted in response to scanning a Calllt Square code) information.
  • server 200 creates and assigns one or more unique identifiers that can be used to identify both an Event and a call option (e.g., good call / bad call / dunk contest rating scale, etc.).
  • a single identifier may be created and assigned to provide this function, or multiple identifiers may be created and used.
  • two identifiers are created and bound to an Event/Call Option.
  • An EventID 420 and a CallOptionID 430 are used to uniquely identify an Event and possible call option.
  • some or all of the identifiers may be concatenated, mapped to a hashing function / table, or otherwise encoded and placed in an associated Calllt Square service scan code.
  • the extracted identifier information is provided to server 200 and is sufficient to enable server 200 to identify both the Event with which Calllt Square service scan code is associated and the call option with which the same scan code is associated. This association is created at provisioning time and stored by server 200 as illustrated in Tables 16 and 17. Exemplary data tables and data structures associated with various embodiments of Calllt Square service are presented in Figure IOC.
  • Calllt Square scan code information is communicated to provisioning entity 600 (step 4) and Calllt Square codes associated with, for example, "I agree with the call” and “I disagree with the call” which were generated by or with the aid of Calllt Square application server 200 may be deployed (e.g., on cups, bags, event programs, television screens, etc.), step 5.
  • Figure 10B illustrates an exemplary Calllt Square code 516 that has been associated (via provisioning) with the statement, "I disagree with the call.”
  • Another Calllt Square code (not shown) is also generated and deployed that represents the statement "I agree with the call.”
  • Copies of the Calllt Square QR code 516 (and the other code) may be deployed in any number of ways and formats including, but not limited to, printed flyers, event programs, drink cups, bags, napkins, scoreboard display, purchase receipts, etc.
  • Calllt Square QR code may be displayed on viewer television screens during a network or cable TV broadcast of a sporting event.
  • one or more Calllt Square QR scan codes may be displayed / superimposed on the televised / streamed broadcast image that is displayed on viewer's television / viewing screens for the duration of a voting/rating window time period.
  • broadcasting / streaming equipment e.g., a computer, computer server, audio/visual signal processing unit, etc.
  • scan-triggered server 200 may determine that a votable / ratable incident has occurred and open a voting / rating window without an explicit signal from an administrator or external equipment.
  • Such an implicit voting / rating window opening determination may be made by scan- triggered server 200 by analyzing the volume of received scans from users over time. For example, server 200 may determine that a votable / ratable incident has occurred if the average / mean scan receipt rate moves above a reference threshold scan receipt rate, and in response, effectively open a voting/rating window. In a similar manner, server 200 may determine, based on a reference "window closing" threshold reference value, when the voting / rating window associated with a votable / ratable incident is closed. Vote or rating scans received from users while voting/rating window is open are tallied / logged / recorded / counted by server 200.
  • a votable or ratable incident such as a penalty call or a great shot by a player occurs, which causes a voting (or rating) window to be opened.
  • a scan-triggered application service administrator who is watching the event signals server 200 to open a voting / rating window (step 1).
  • server 200 may be signaled to open a voting or rating window based on input from other sources, such as computer equipment associated with a television broadcast system or Internet broadcast / streaming system. Scanning of the Calllt Square code 516 causes the scan-enabled client module 104 to communicate user identifying / user login credentials, eventID information and CallltOptionlD information to Calllt Square application server 200, as indicated in step 2.
  • Calllt Square application server 200 receives the scan code information during the open vote collection time window, which includes user identifying / user login credentials eventID information and CallltOptionlD information.
  • the CallltOptionlD information obtained from scanning of the Calllt Square scan code 516 is used by scan-triggered server 200 to determine the scanning user's vote for the associated incident (e.g., "Good Call", "Bad Call'V'Great Shot", etc.).
  • server 200 closes the voting window associated with the incident. In one embodiment, if a user's scan "vote" is received while there is not an incident voting window open, then the vote is not tallied.
  • Calllt Square Application server 200 may communicate or relay current vote tally information to other communication systems so, for example, the current tally of votes for a penalty call can be displayed on the jumbo scoreboard screen of the event stadium.
  • Calllt Square Control Logic Module 218 may determine (based on prior provisioned rules) whether the user should be granted a reward in exchange for scanning the Calllt Square code. If a reward is to be granted, Reward Control Logic Module 210 may facilitate the crediting of the granted reward to the user's account (step 5).
  • server 200 may award a user with a vote "multiplier" reward, for example, in response to determining that the user has been an active participant / user of the scan-triggered voting / rating service. As such, a vote cast by the user will be multiplied by an amount associated with the reward. For example, if a use is awarded a "3x" multiplier, any subsequent vote that they cast will be tallied 3 times.
  • Figure IOC illustrates an example of Calllt Square according to an embodiment of the subject matter described herein, where a Calllt Square scan code 517 is associated with set of pre-defined voting "ballot" response options, which are provided to the scanning user 100 by scan-triggered server 200 in response to scanning of code 517.
  • Calllt Square scan code 517 is associated with set of pre-defined rating scale / range response options, which are provided to the scanning user 100 by scan-triggered server 200 in response to scanning of code 517.
  • step 1 a votable / ratable incident occurs and scan- triggered server 200 determines that a voting / rating window should be opened for the votable/ratable incident.
  • user 100 scans Calllt Square 517.
  • server 200 which can be used by server 200 to identify the event with which the votable/ratable incident is associated is extracted from the scan code by device 100 and communicated to server 200.
  • User identifying information e.g., scan-triggered service account UserlD information
  • server 200 communicates one or more possible vote response options (e.g., "Good call”, "Bad call”, etc.) or rating scale information (e.g., "10-Awesome ... 1- Terrible", etc.) to mobile device 100 where it is displayed onscreen to the user.
  • the user of mobile device 100 may tap to touch an onscreen button associated with one or more of the response options or rating scale options, which causes information that can be used to identify the selected response option to be communicated to server 200.
  • Server 200 may respond to the user by providing a current tally or summary of crowd-sourced vote / rating results for the associated event incident.
  • server 200 closes the incident voting / rating window.
  • Calllt Square scans received after the event incident window closes are not included in the associated incident result tally.
  • Figures 10D and 10 E illustrates exemplary data and data structures that may be used by Calllt Square application server 200 to facilitate Calllt Square services, and include user identifier information 300, user name information 302, and user location / zipcode information 304. It will be appreciated that embodiments of the present Calllt Square invention may be operated without collecting or using user identifying information. In such "anonymous" modes of operation, user identifying information is not required / is optional. Shown in Table 16 is Event information, which includes an EventID 420, event description information 422, event start and end date/time 424 and 426, respectively. Shown in Table 17 is call option information including a CallOptionID 430 and call option description information 432.
  • Table 18 Shown in Table 18 is Reward information including a RewardID 442, Reward description information 444, and Reward expiration date information 446.
  • Table 19 Shown in Table 19 is a Calllt Square scan transaction / binding record that contains / stores scan data associated with a received user Calllt Square service code scan.
  • Table 19 includes scanning UserlD information 450, EventID information 452, an IncidentID 453 which can be used to distinguish between multiple, different call-able incidents (e.g., fouls, penalties, slam dunks, touchdowns, etc.) that occur during an event, a CallOptionID value 454, a Calllt Square scan timestamp 456, and a granted RewardID 458.
  • Shown in Table 20 is exemplary rating scale information used with some embodiments.
  • Table 20 includes an EventID 452, a Rating ScalelD 460, and Rating text / label 462.
  • Table 21 additionally includes Rating Scale Lowest Score information 464 and Rating Scale Highest Score information 466.
  • Shown in Table 22 is another exemplary Calllt Square scan transaction / binding record that contains / stores scan data associated with a received user Calllt Square service code scan.
  • Table 22 includes an IncidentID 468, EventID 452, UserlD 468, User Rating Score information 470, granted RewardID 472, and scan timestamp information 474.
  • Embodiments of the subject matter described herein may include a system for providing time window-based voting and rating of event incidents via the scanning of a scan-able code by a scan-enabled client module, the system comprising:
  • a computing platform including at least one processor:
  • a server application module executable by or embodied in the at least one processor and configured to:
  • event identifying information and event incident vote or rating information from a user, where the event identifying and incident vote or rating information is obtained from the scanning of a scan-triggered service scan code by the user;
  • event identifying information and event incident vote or rating information use the event identifying information and event incident vote or rating information to update a vote or rating tally associated with the event incident;
  • Embodiments of the subject matter described herein may include a system for providing time window-based voting and rating of event incidents via the scanning of a scan-able code by a scan-enabled client module, the system comprising:
  • a computing platform including at least one processor:
  • a server application module executable by or embodied in the at least one processor and configured to: receive a signal that causes an event incident voting / rating window to be opened, during which time user vote or rating information associated with the event incident is tallied;
  • event identifying information and event incident vote or rating information from a user, where the event identifying and incident vote or rating information is obtained from the scanning of a scan-triggered service scan code by the user;
  • event identifying information and event incident vote or rating information use the event identifying information and event incident vote or rating information to update a vote or rating tally associated with the event incident;
  • FIG 11A is diagram that generally illustrates the provisioning of information associated with a service of a scan code-based service system according to an embodiment of the subject matter described herein.
  • This service is referred to herein as Savelt Square service, which is a service that facilitates the addition of an item to a list for the user that is triggered via the scanning of an Savelt Square service scan code by the user.
  • Savelt Square service is a service that facilitates the addition of an item to a list for the user that is triggered via the scanning of an Savelt Square service scan code by the user.
  • Savelt Square service might involve a wine merchant that has many different bottles of a wine in their store.
  • a user who would like to remember a particular vintner and vintage scans a Savelt Square QR code associated with the particular bottle of wine using the QR code scanner on their mobile phone.
  • Scanning of the Savelt Square causes descriptive information about that particular bottle of wine to be saved in the user's Savelt Square data vault.
  • the user can then log into his or her Savelt Square vault at any time and browse information about that bottle of wine.
  • the Savelt Square service may also provide the user with a digital coupon or reward for scanning the Savelt Square associated with a particular item in a merchant's store, or for scanning a certain number of Savelt Square codes associated with the merchant.
  • the Savelt Square service may facilitate and track redemption of the Reward by the user.
  • server 200 is adapted to credit a reward to a digital reward wallet associated with a recipient user's scan-triggered service account.
  • a merchant uses computer terminal 608 to log into a provisioning interface associated with an application server 200 that is hosting the Savelt Square application, as indicated in step 1.
  • product description information such as, product name, product stock keeping unit (SKU) information, universal product code (UPC) information, product description text, uniform resource identifier or locator information associated with the product, related product identifiers / descriptions, product price information, sale date information, in-stock quantity information, and associated participation reward (e.g., a reward that is granted in response to scanning the Savelt Square code) information.
  • SKU product stock keeping unit
  • UPC universal product code
  • step 3 server 200 creates and assigns a SaveltID identifier that can be used to identify the associated product.
  • This SaveltID value is bound to the product / product information and stored in a binding record by server 200.
  • step 4 Savelt Square scan code information is communicated to provisioning entity 608.
  • step 5 one or more copies of the Savelt Square scan code may be deployed in any number of ways and formats including, but not limited to, printed tags that are placed on the shelf that holds/displays the associated product, direct mailing collateral, in-store displays, computer monitor display, magazine advertisements, purchase receipts, etc.
  • a user scans Savelt Square code 518. Scanning of the Savelt Square code causes the scan-enabled client module 104 to communicate user identifying / user login credentials and SaveltID information to Savelt Square application server 200, as indicated in step 1.
  • Savelt Square application server 200 receives the scan code information, which includes user identifying / user login credentials and SaveltID information, and creates or updates a binding record associated with the user's scan-triggered service account so as to include the SaveltID information or information associated with the SaveltID (e.g., information related to the associated good or service), as indicated in step 2.
  • Server 200 responds with an acknowledgement message that includes information that echo's the SaveltID which was received, as indicated in step 3. For example, if the SaveltID received is associated with a bottle of wine that has a provisioned description of "Oak Hill 2005 Zin", then the echo provided back to the user may include the text "Oak Hill 2005 Zin.”
  • Savelt Square Control Logic Module 220 determines that the user has not already scanned this Savelt Square code, then the SaveltID is recorded in the user's Savelt data structure / log (step 2). Via a mobile user browsing interface, the user may log into the Savelt application server 200 and browse the contents of their Savelt data / vault.
  • Savelt Square Control Logic Module 220 may determine (based on prior provisioned rules) whether the user should be granted a reward in exchange for scanning the Savelt Square code. If a reward is to be granted, Reward Control Logic Module 210 may facilitate the crediting of the granted reward to a digital reward wallet associated with the user's account (step 4). In step 5, user 100 provides feedback or rating score information to server 200, where it is logged and stored. In one embodiment, such feedback or rating score information may be collected from the user following the scanning of Savelt Square scan code 518.
  • server 200 is adapted to communicate one or more questions (e.g., "Why did you like this product?", etc.) and associated response options (e.g., "High Quality", “Inexpensive”, “Good Design”) to mobile device 100 following a scan of code 518.
  • the user may select the desired response option, which is then communicated to server 200, where it is bound to the SaveltID and userlD information and stored.
  • rating scale information may be communicated to mobile device 100 following a scan of code 518, and the user may specify a rating score value, which is then communicated to server 200, where it is bound to the SaveltID and userlD information and stored. In this way, user feedback or rating information associated with an product or service may be quickly and easily collected, analyzed, and reported.
  • the user can log in to scan-triggered server 200 (via any computer / communication device) at a later time and access or browse their saved good / services.
  • user 100 logs into server 200, thereby providing user identifying information to server 200.
  • server 200 uses the provided / obtained user identifying information (e.g., UserlD) to access the user's associated Savelt data.
  • some or all of the user's Savelt data (e.g., saved goods / service information) is provided to user 100.
  • server 200 may provide user 100 with a digital reward, which may for example, be placed in a digital reward wallet associated with the user's scan-triggered services account.
  • step 5 user 100 provides feedback or rating score information to server 200, where it is logged and stored.
  • feedback or rating score information may be collected from the user following the scanning of Savelt Square scan code 518.
  • server 200 is adapted to communicate one or more questions (e.g., "Why did you like this product?", etc.) and associated response options (e.g., "High Quality", “Inexpensive", “Good Designl”) to mobile device 100 following a scan of code 518. The user may select the desired response option, which is then communicated to server 200, where it is bound to the SaveltID and userlD information and stored.
  • rating scale information may be communicated to mobile device 100 following a scan of code 518, and the user may specify a rating score value, which is then communicated to server 200, where it is bound to the SaveltID and userlD information and stored.
  • server 200 where it is bound to the SaveltID and userlD information and stored.
  • Figure 11D illustrates exemplary data and data structures associated with the exemplary Savelt Square embodiments discussed herein and includes user identifier information 300, user name information 302 and user location / zipcode information 304.
  • Shown in Table 24 is an exemplary SaveltID to product/service binding record.
  • Table 24 includes a SaveltID 660, a good/service name 662, a merchantID 664, a merchant storelD 666, a goods or service category 668.
  • additional information related to the associated good or service may be provisioned, such as product marketing / sales information, product / service web site URL information, product / service video or image information, etc. Such information may be communicated to or browsed by the user.
  • Shown in Table 25 is exemplary SaveltID to Reward binding data that includes a SaveltID 660, a RewardID 672, a Reward description 674, and a Reward expiration date 676.
  • Shown in Table 26 is an exemplary Savelt Square scan transaction / binding record that includes userlD information 678, SaveltID information 680, scan timestamp information 682, granted RewardID information 684, and user feedback / rating score information 686. It will be appreciated that in one embodiment, the data presented in Table 26 essentially represents or reflects the contents of a user's Savelt vault.
  • Embodiments of the subject matter described herein may include a system for storing a reference to a good or service via the scanning of a scan-able code by a scan-enabled client module, the system comprising:
  • a computing platform including at least one processor:
  • a server application module executable by or embodied within the at least one processor and configured to:

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Operations Research (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention porte sur des procédés, des systèmes et des produits programmes d'ordinateur pour surveiller un utilisateur utilisant une image graphique à informations codées pouvant être balayées, telle qu'un code à barres ou un code de réponse rapide (QR), un code/étiquette de communication en champ proche (NFC) ou un code/étiquette d'identification radiofréquence (RFID). Un dispositif de communication mobile tel qu'un téléphone intelligent, un ordinateur tablette ou autre ordinateur mobile peut comprendre un module client de balayage pour balayer et communiquer des informations de code QR. Le balayage de code QR est accomplie par un module d'appareil photo qui est associé au téléphone intelligent ou autre dispositif informatique mobile. Le module client à fonction de balayage communique les informations de code QR balayées à une application serveur associée pour collecter, traiter et rapporter des données de balayage.
PCT/US2014/054103 2013-09-04 2014-09-04 Procédés et systèmes pour utiliser des codes pouvant être balayés afin d'obtenir un service WO2015035055A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201361959862P 2013-09-04 2013-09-04
US61/959,862 2013-09-04
US201361960258P 2013-09-13 2013-09-13
US61/960,258 2013-09-13

Publications (1)

Publication Number Publication Date
WO2015035055A1 true WO2015035055A1 (fr) 2015-03-12

Family

ID=52628927

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2014/054103 WO2015035055A1 (fr) 2013-09-04 2014-09-04 Procédés et systèmes pour utiliser des codes pouvant être balayés afin d'obtenir un service

Country Status (1)

Country Link
WO (1) WO2015035055A1 (fr)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9223885B2 (en) 2011-08-24 2015-12-29 Flashback Survery, Inc. Methods and systems for surveying a user with scan-able codes
US20210174344A1 (en) * 2019-03-06 2021-06-10 Digital Seat Media, Inc. System and method for location based individualized mobile content and mobile wallet offers
US11106753B1 (en) 2020-04-27 2021-08-31 Digital Seat Media, Inc. Method and system for digital record verification
US11182768B2 (en) 2019-03-06 2021-11-23 Digital Seat Media, Inc. System and method for location-based individualized content and mobile wallet offers
US11206432B1 (en) 2017-06-07 2021-12-21 Digital Seat Media, Inc. System and method for providing synchronized interactive multimedia content to mobile devices based on geolocation of a vehicle
WO2022061339A1 (fr) 2020-09-16 2022-03-24 Digital Seat Media, Inc. Système et procédé pour fournir un contenu multimédia interactif synchronisé à des dispositifs mobiles sur la base de la géolocalisation d'un véhicule
US11475409B2 (en) 2017-06-07 2022-10-18 Digital Seat Media, Inc. Method and system for digital record verification
US11481807B2 (en) 2020-04-27 2022-10-25 Digital Seat Media, Inc. Delivery of dynamic content based upon predetermined thresholds
US11488273B2 (en) 2020-04-27 2022-11-01 Digital Seat Media, Inc. System and platform for engaging educational institutions and stakeholders
US11494737B2 (en) 2020-04-27 2022-11-08 Digital Seat Media, Inc. Interactive and dynamic digital event program
US11657337B2 (en) 2020-04-27 2023-05-23 Digital Seat Media, Inc. System and method for exchanging tickets via a machine-readable code
US11688029B2 (en) 2021-04-27 2023-06-27 Digital Seat Media, Inc. Wagering platforms and access derived from machine-readable codes
US11829834B2 (en) 2021-10-29 2023-11-28 Snap Inc. Extended QR code
WO2024037285A1 (fr) * 2022-08-16 2024-02-22 支付宝(杭州)信息技术有限公司 Procédé et appareil de traitement de service de lieu

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100185465A1 (en) * 2004-08-09 2010-07-22 Sumit Rana Electronic Appointment Scheduling For Medical Resources
US20130080262A1 (en) * 2010-02-26 2013-03-28 Research In Motion Limited Scheduling and delivering ad meetings
WO2013126886A1 (fr) * 2012-02-24 2013-08-29 Augme Technologies, Inc. Système et procédé de création de coupon virtuel

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100185465A1 (en) * 2004-08-09 2010-07-22 Sumit Rana Electronic Appointment Scheduling For Medical Resources
US20130080262A1 (en) * 2010-02-26 2013-03-28 Research In Motion Limited Scheduling and delivering ad meetings
WO2013126886A1 (fr) * 2012-02-24 2013-08-29 Augme Technologies, Inc. Système et procédé de création de coupon virtuel

Cited By (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9223885B2 (en) 2011-08-24 2015-12-29 Flashback Survery, Inc. Methods and systems for surveying a user with scan-able codes
US11475409B2 (en) 2017-06-07 2022-10-18 Digital Seat Media, Inc. Method and system for digital record verification
US11972396B2 (en) 2017-06-07 2024-04-30 Digital Seat Media, Inc. Method and system for digital record verification
US11206432B1 (en) 2017-06-07 2021-12-21 Digital Seat Media, Inc. System and method for providing synchronized interactive multimedia content to mobile devices based on geolocation of a vehicle
US11570485B2 (en) 2017-06-07 2023-01-31 Digital Seat Media, Inc. System and method for providing synchronized interactive multimedia content to mobile devices based on geolocation of a vehicle
US20210174344A1 (en) * 2019-03-06 2021-06-10 Digital Seat Media, Inc. System and method for location based individualized mobile content and mobile wallet offers
US11182768B2 (en) 2019-03-06 2021-11-23 Digital Seat Media, Inc. System and method for location-based individualized content and mobile wallet offers
US11769140B2 (en) 2019-03-06 2023-09-26 Digital Seat Media, Inc. System and method for location-based individualized content and mobile wallet offers
EP4115376A4 (fr) * 2020-03-06 2023-12-06 Digital Seat Media, Inc. Système et procédé pour des propositions de contenus individualisés et de portefeuilles mobiles basées sur la localisation
US11461426B2 (en) 2020-04-27 2022-10-04 Digital Seat Media, Inc. Method and system for digital record verification
US11816597B2 (en) 2020-04-27 2023-11-14 Digital Seat Media, Inc. Interactive and dynamic digital event program
US11481807B2 (en) 2020-04-27 2022-10-25 Digital Seat Media, Inc. Delivery of dynamic content based upon predetermined thresholds
US11488273B2 (en) 2020-04-27 2022-11-01 Digital Seat Media, Inc. System and platform for engaging educational institutions and stakeholders
US11494737B2 (en) 2020-04-27 2022-11-08 Digital Seat Media, Inc. Interactive and dynamic digital event program
US11461425B2 (en) 2020-04-27 2022-10-04 Digital Seat Media, Inc. Method and system for digital record verification
US11657337B2 (en) 2020-04-27 2023-05-23 Digital Seat Media, Inc. System and method for exchanging tickets via a machine-readable code
US11675863B2 (en) 2020-04-27 2023-06-13 Digital Seat Media, Inc. Method and system for digital record verification
US12061997B2 (en) 2020-04-27 2024-08-13 Digital Seat Media, Inc. System and method for exchanging tickets via a machine-readable code
US11106753B1 (en) 2020-04-27 2021-08-31 Digital Seat Media, Inc. Method and system for digital record verification
US11908031B2 (en) 2020-04-27 2024-02-20 Digital Seat Media, Inc. System and platform for engaging educational institutions and stakeholders
US11468138B2 (en) 2020-04-27 2022-10-11 Digital Seat Media, Inc. Method and system for digital record verification
US11853378B2 (en) 2020-04-27 2023-12-26 Digital Seat Media, Inc. Method and system for digital record verification
US11263282B2 (en) 2020-04-27 2022-03-01 Digital Seat Media, Inc. Method and system for digital record verification
US11853379B2 (en) 2020-04-27 2023-12-26 Digital Seat Media, Inc. Method and system for digital record verification
WO2022061339A1 (fr) 2020-09-16 2022-03-24 Digital Seat Media, Inc. Système et procédé pour fournir un contenu multimédia interactif synchronisé à des dispositifs mobiles sur la base de la géolocalisation d'un véhicule
US20230274382A1 (en) * 2021-04-27 2023-08-31 Digital Seat Media, Inc. Wagering platforms and access derived from machine-readable codes
US12008672B2 (en) 2021-04-27 2024-06-11 Digital Seat Media, Inc. Systems and methods for delivering augmented reality content
US11688029B2 (en) 2021-04-27 2023-06-27 Digital Seat Media, Inc. Wagering platforms and access derived from machine-readable codes
US12062108B2 (en) 2021-04-27 2024-08-13 Digital Seat Media, Inc. Wagering platforms and access derived from machine-readable codes
US11829834B2 (en) 2021-10-29 2023-11-28 Snap Inc. Extended QR code
WO2024037285A1 (fr) * 2022-08-16 2024-02-22 支付宝(杭州)信息技术有限公司 Procédé et appareil de traitement de service de lieu

Similar Documents

Publication Publication Date Title
WO2015035055A1 (fr) Procédés et systèmes pour utiliser des codes pouvant être balayés afin d'obtenir un service
US11361292B2 (en) Selected place on map or from category specific list of nearby places associated payment interface for making payment
US20160203352A1 (en) Using scanable codes to obtain a service
US20200219152A1 (en) Systems for Integrating Online Reviews with Point of Sale (POS) OR EPOS (Electronic Point of Sale) System
JP5671151B2 (ja) インスタントメッセージングサービス提供方法及びその提供システム
US8626627B2 (en) Providing online promotions through social network platforms
US20090018961A1 (en) Customer identification system and method for a personalized merchant rewards program
US20150302493A1 (en) Interactive transactions
US20150170164A1 (en) Methods and systems for using scanable codes to obtain a service
US20130013404A1 (en) System and method for distribution of digital offers
US20140231502A1 (en) Methods and systems for providing subject-specific survey content to a user with scanable codes
CA2893660C (fr) Systeme et procede de mise en d'attente d'appels video
US20100211436A1 (en) Mobile computing device network of multi-vendor, multi-interface computers
WO2012025824A2 (fr) Système de fidélisation des clients dans des chaînes de vente au détail et dans des restaurants à l'aide de serveurs web, dispositifs de communication mobiles et terminaux de point de vente
US20150302347A1 (en) System and method for managing venue concessions
US20160005012A1 (en) Consolidated platform for selling tickets
US20170308818A1 (en) Payment and ordering system and application for a mobile client
US20090119183A1 (en) Method and System For Service Provider Access
KR20170102931A (ko) 온라인 제품 예약 시스템
JP2018101388A (ja) 情報処理装置及びプログラム
WO2015039025A1 (fr) Procédés et systèmes pour utiliser des codes lisibles optiquement pour obtenir des services déclenchés par lecture optique
US20230177910A1 (en) Information processing apparatus, information processing method, beverage container, beverage server, and electronic device
US8089346B2 (en) System and method for managing restaurant customers and placing orders
WO2015005861A1 (fr) Procédé et système de passation de commande et de paiement
US20050060748A1 (en) Programming service offer presentment and instant actvation system, method, and computer program product

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: 14842119

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: 14842119

Country of ref document: EP

Kind code of ref document: A1