[0001] This application claims the benefit of priority to U.S. Provisional Application Number 61/562,385, filed on November 21, 2011. This and all other extrinsic materials discussed herein are incorporated by reference in their entirety. Where a definition or use of a term in an incorporated reference is inconsistent or contrary to the definition of that term provided herein, the definition of that term provided herein applies and the definition of that term in the reference does not apply.

Field of the Invention

[0002] The field of the invention is transaction infrastructure technologies. Back2round

[0003] The background description includes information that may be useful in understanding the present invention. It is not an admission that any of the information provided herein is prior art or relevant to the presently claimed invention, or that any publication specifically or implicitly referenced is prior art.

[0004] Transaction systems provide primitive solutions for the ever growing world of on-line transactions. Typically, existing transaction systems provide a single provider the ability to conduct a transaction with a single user. However, they lack the ability to offer providers (e.g. , of service, good, etc.) or consumers a system that can reconcile aspects of a transaction among multiple providers or user accounts.

[0005] For example, Apple® EasyPay allows a user to make merchant (i.e., Apple®) specific payments in its retail stores in a closed loop system through the user's iTunes® account, thereby eliminating the need to wait in line at a physical counter; see URL:

www.javelinstrategy.com/ blog/2011/11/15/apple-iphone-easypay-mobile-payment-rollout- may-delay-nfc/. Another example includes Zoosh®, which uses ultrasound to perform certain near field transactions via two devices; see URL

venturebeat.com/2011/06/19/narattes-zoosh-enables-nfc-wit h-just-a-speaker-and- microphone/).

[0006] Unfortunately, existing transaction systems apparently fail to reconcile aspects of a transaction among multiple provider accounts or user accounts. Thus, there is still a need for transaction systems capable of reconciling aspects of a transaction among multiple provider or user accounts.

Summary of The Invention

[0007] The inventive subject matter provides apparatus, systems and methods in which one can conduct a transaction involving multiple provider accounts or user accounts that are involved with a payment (e.g. , of cash, coupon, discount, loyalty points, etc.) or any other suitable transaction associated to an item (e.g. , good, service, subscriptions, etc.). As used herein, the term "provider" is used very broadly to include providers of a service or good, whether real or virtual. One aspect of the inventive subject matter is considered to include a transaction system comprising a recognition engine, a transaction engine, and possibly one or more device engagement engines. The recognition engine can obtain a digital representation of a real- world object and derive attributes associated with the object (e.g. , time, location, color, shape, model, cost, price, available coupons, messages, metadata, etc.) based on recognizing the object. A transaction engine can communicate with the recognition engine and can reconcile a transaction among multiple provider accounts or user accounts as a function of one or more of the derived object attributes. In some preferred embodiments, the transaction involves making a payment to one or more of the provider accounts or user accounts where the payment relates to an item. In some embodiments, an engagement engine can cause a computing device (e.g. , cell phone, set- top box, kiosk, game consoles or system, etc.) to take action based on the transaction. Actions will be discussed in greater detail below.

[0008] Another aspect of the inventive subject matter includes a method of reconciling payment of a coupon. Contemplated methods include using a recognition engine, possibly deployed on a mobile cell phone or other computing device, to recognize a real-world object related to a purchasable item. The purchasable item could be the same item as the real-world object (e.g. , a product on a store shelf) or tangentially related (e.g. , a ticket of a movie displayed in on a movie poster). The method can further include creating a virtual coupon based on attributes derived from a digital representation of the real-world object where the digital representation could comprise image data, sound data, non-visible data, signals, or other modal types of data. Another step can include activating the virtual coupon upon a triggering event generated by a mobile device, a cell phone for example. The triggering event could be generated automatically, "zero touch" (e.g. , via near field communications, recognition of an object, etc.), or manually via one, two or more user interactions with a user interface. With zero touch generation of a triggering event, it is contemplated that a device can be configured to recognize objects located as far as 1, 5, 10, 20, 50, 100 or even 1000 or more feet away. Less clicks or user interface interactions can be preferable over a larger number of interactions. The mobile device, or other electronic device involved in the transaction, can reconcile the transaction among two or more electronic accounts relating to the purchase of the purchasable item. For example, a coupon vendor account can be charged according to terms of the virtual coupon, a vendor account can be credited with payment, a consumer's account can be charged according to terms of the virtual coupon, or a consumer's account can be credited according to terms of the transaction or virtual coupon. In some embodiments, the accounts can be third party accounts associated with various loyalty programs possibly participating in a loyalty exchange system where one account currency (e.g. , frequent flyer miles, free gasoline points, etc.) can be converted to another (e.g. , virtual gold in an on-line game, mobile phone minutes, etc.) according to terms of a virtual coupon.

[0009] Yet another aspect of the inventive subject matter can include a transaction apparatus (e.g. , cell phone, point of sales device, computer, server, kiosk, game console, etc.) that can include a sensor interface through which the apparatus can acquire a digital representation of a real-world object or scene having the object. Example sensor interfaces could include an actual sensor (e.g. , GPS, microphone, camera, accelerometer, bio-metric, etc.), a hardware interface to a sensor platform (e.g. , serial interface, parallel interface, network interface, USB, etc.), or even a set of application program interfaces (APIs) capable of making local or remote procedure call. The transaction apparatus can also include a recognition module communicatively coupled with the sensor interface where the recognition module derives one or more object attributes from the digital representation and uses the object attributes to identify a purchasable item (e.g. , the real- world object, a good, a product, a service, a subscription, etc.). Contemplated apparatus can further comprise a virtual coupon generator configured to generate a virtual coupon associated with the purchasable item as a function of the object attributes or other information available (e.g. , customer ID, phone number, vendor ID, merchant ID, account numbers, prior consumer transactions, prior consumer scans, prior consumer interactions, etc.). The transaction apparatus can further include a transaction interface configured to electronically engage, directly or indirectly, one or more accounts possibly over a network. The transaction interface allows the apparatus to reconcile an account based on a payment for the purchasable item and based on use or authentication of the virtual coupon. In especially preferred embodiments, a user account is credited for purchasing the item. One especially preferred embodiment includes a mobile phone operating as the transaction apparatus where the virtual coupon is specifically generated according to a location and time.

[0010] Still another aspect of the inventive subject matter includes a method of mitigating risk of transaction fraud associated with a coupon. The method includes providing a virtual coupon on a mobile device (e.g. , cell phone, vehicle, car, airplane, mobile kiosk, point of sales device, etc.) where the coupon relates to a purchasable item, possibly identified from object attributes derived from a digital representation of a scene. The virtual coupon can be provided via a text message, an email, a pop up, or any other commercially suitable method. The mobile device can further engage in an electronic transaction locally or even over a network with one or more account servers. The device can further allow the user to select at least one target account to be involved in the transaction from multiple accounts available for use with the transaction. The method can further include authenticating the transaction as a function of transaction attributes derived by the mobile device, possibly from the digital representation (e.g. , location, time, make, model, consumer ID, device ID, etc.), as a function of the user selected target account, as a function of virtual coupon properties, or other factors. In more preferred embodiments, the method includes crediting the target account according to the terms of the virtual coupon. For example, a user might purchase a television at full price and might receive a virtual coupon from the television manufacturer that allows the user an option to credit a number of miles to a frequently flyer account or to credit their cell phone account.

[0011] Various objects, features, aspects and advantages of the inventive subject matter will become more apparent from the following detailed description of preferred embodiments, along with the accompanying drawing figures in which like numerals represent like components.

Brief Description of the Drawin2S

[0012] Fig. 1 shows an overall ecosystem of a transaction system of the inventive subject matter.

[0013] Fig. 2 shows an object recognition engine deriving attributes related to a real world object. [0014] Fig. 3 shows a transaction reconciliation engine reconciling a transaction among multiple accounts.

[0015] Fig. 4 shows an embodiment of the inventive subject matter as embodied in a mobile device application.

[0016] Fig. 5 is a flowchart showing a method of reconciling a payment of a coupon. [0017] Fig. 6 shows a transaction apparatus of the inventive subject matter. [0018] Fig. 7 shows a flowchart of a method of mitigating a risk of transaction fraud. Detailed Description

[0019] The following discussion provides many example embodiments of the inventive subject matter. Although each embodiment represents a single combination of inventive elements, the inventive subject matter is considered to include all possible combinations of the disclosed elements. Thus if one embodiment comprises elements A, B, and C, and a second embodiment comprises elements B and D, then the inventive subject matter is also considered to include other remaining combinations of A, B, C, or D, even if not explicitly disclosed.

[0020] It should be noted that while the following description is drawn to a computer/server based transaction/recognition systems, various alternative configurations are also deemed suitable and may employ various computing devices including servers, interfaces, systems, databases, agents, peers, engines, controllers, or other types of computing devices operating individually or collectively. One should appreciate the computing devices comprise a processor configured to execute software instructions stored on a tangible, non-transitory computer readable storage medium (e.g. , hard drive, solid state drive, RAM, flash, ROM, etc.). The software instructions preferably configure the computing device to provide the roles, responsibilities, or other functionality as discussed below with respect to the disclosed apparatus. In especially preferred embodiments, the various servers, systems, databases, or interfaces exchange data using standardized protocols or algorithms, possibly based on HTTP, HTTPS, AES, public-private key exchanges, web service APIs, known financial transaction protocols, or other electronic information exchanging methods. Data exchanges preferably are conducted over a packet-switched network, the Internet, LAN, WAN, VPN, or other type of packet switched network. [0021] One should appreciate that the disclosed techniques provide many advantageous technical effects including providing an infrastructure capable of generating networked signals that cause remote devices to engage in reconciling accounts among one or more provider or user accounts.

[0022] As used herein, and unless the context dictates otherwise, the term "coupled to" is intended to include both direct coupling (in which two elements that are coupled to each other contact each other) and indirect coupling (in which at least one additional element is located between the two elements). Therefore, the terms "coupled to" and "coupled with" are used synonymously. Within this document, "coupled with" can also mean "communicatively coupled with", possibly over a network.

[0023] As used in the description herein and throughout the claims that follow, the meaning of "a," "an," and "the" includes plural reference unless the context clearly dictates otherwise. Also, as used in the description herein, the meaning of "in" includes "in" and "on" unless the context clearly dictates otherwise.

[0024] Unless the context dictates the contrary, all ranges set forth herein should be interpreted as being inclusive of their endpoints, and open-ended ranges should be interpreted to include commercially practical values. Similarly, all lists of values should be considered as inclusive of intermediate values unless the context indicates the contrary.

[0025] It is contemplated that the inventive subject matter described herein can leverage one or more techniques disclosed in the following co-owned pending applications: U.S.

provisional application number 60/246295 filed November 6, 2000; U.S. provisional application number 60/317521 filed September 5, 2001 ; U.S. application number 11/510009 titled "Interactivity Via Mobile Image Recognition" filed on August 25, 2006; U.S.

application number 12/505726 titled "Interactivity with a Mixed Reality" filed on July 20, 2009; U.S. application number 13/005716 titled "Data Capture and Identification System and Process" filed on January 13, 2011 ; U.S. application number 13/037317 titled "Image Capture and Identification System and Process" filed on February 28, 2011 ; and U.S.

application number 13/037330 titled "Object Information Derived from Object Images" filed on February 28, 2011. For example, the inventive subject matter can utilize one or more of the techniques for presenting information such as Internet content to a user described in U.S. application number 13/005726. [0026] Figure 1 shows an overall ecosystem of a transaction system of the inventive subject matter. Transaction system 100 (e.g. , a subscription service, etc.) comprises an object recognition engine 1 10, transaction reconciliation engine 120, engagement engine 130, and computing device 140.

[0027] Object recognition engine 110 is configured to recognize a real-world object and derive object attributes of the object. The "real-world object" can comprise any existing still or moving object, including for example, a poster, a magazine, a brochure, a billboard sign, a product, a purchasable product, a vehicle, a storefront, a food item, a logo, a trademark, an image on a screen (e.g. , television or computer screen, etc.), a person providing a service, a person, an image of a good or service (e.g. , an image in printed media, non-printed media, an image of an animated object, an image of an inanimate object, etc.), a street sign, or a service embodied in a tangible medium. The object attributes can comprise any quality or feature of an object, including for example, an absolute time, a relative time, a response time, a location, a relative position or orientation, a color, a size, a quantity, a quality, a material, an availability, a depreciation rate, an appreciation rate, a supply relative to a demand, a shape, a make, a model, a cost, an available coupon, a message, metadata, and a price. Additional details regarding object recognition engines will be provided in the description of Figure 2.

[0028] Transaction reconciliation engine 120 can be communicatively coupled to object recognition engine 1 10 and configured to reconcile a transaction amongst two or more provider accounts or user accounts as a function of the attributes derived by object recognition engine 1 10. The transaction can include, among other things, a purchase, a download, an order, a pre-order, a reservation, a down payment, a pre -payment, a partial prepayment, reconciling a coupon among at least one of a provider account associated with the transaction and a user account, or any other suitable transaction. Reconciling a coupon can include, among other things, at least one of the following steps: (1) identification of a coupon to be generated; (2) generation of a coupon; (3) providing a coupon to a user; (4) a user receiving a coupon; (5) a user presenting the coupon to a provider or point-of-sale terminal (e.g. , via a text, email, a closeness of a device to a point of sale device, a presenting of a displayed virtual coupon, a presenting of a code or password associated with the virtual coupon, etc.); and (6) reconciling at least one account (e.g. , user, provider, etc.) via a credit, debit, update, notification, etc. [0029] In some embodiments, the transaction can involve some sort of payment to at least two different accounts, for the purpose of obtaining a good, product, service, or subscription. Moreover, the transaction can be completed in no more than 10, 5, 3, or even 2 or less physical interactions. For example, it is contemplated that an end user can capture an image of a real world object via a single click of a device, and that this single click can initiate some or all of the steps of a transaction related to the object, which can include reconciliation of a coupon. It is also contemplated that the transaction can occur automatically based on a realtime automatic ambient collection of sensor data forming a digital representation of the real- world object without requiring the end user to initiate the transaction. For example, the digital representation of the real-world object can automatically be compared with objects or items within a database. This database can be located in a server located within the device collecting sensor data, a remote server, or any combination thereof. Additional details regarding transaction reconciliation engines and the process of reconciling a transaction will be provided in the description of Figure 3.

[0030] Engagement engine 130 is communicatively coupled to object recognition engine 110, transaction engine 120 and computing device 140, and is configured to cause computing device 140 to take one or more actions as a function of a transaction. All commercially suitable computing devices are contemplated, including for example, a mobile phone, a gaming console or system (including 3-D gaming consoles and systems), a local server, a remote server, a general purpose computer, a tablet, a kiosk an electronic device, a set-top box, or any other commercially suitable device. Examples of actions that can be caused by engagement engine 130 include, among other things, a credit, debit, initiation of a software process, an initiation of a transaction, posting data, reading data, logging on or off an account, registering an account, interacting with a game, or making a phone call (e.g. , to a doctor, store, etc.).

[0031] One contemplated type of transaction system can be configured to modify a subscription bill from a service or product provider (e.g. , a utility provider, a magazine subscription provider, etc.). Modifying a subscription bill can include, among other things, at least one of a deletion of a charge, a reduction of a charge, an increase of a charge, an overall percentage discount, a credit, a free offer, a reduced price offer, or a coupon for a service or a good. The system can establish a universal framework of a virtual loyalty card usable by multiple providers based on object recognition of a real world object. A recognition engine of such systems can recognize the object, derive object attributes associated with the object, and recognize an ID of a virtual coupon in the process of recognition of both the object and of the virtual coupon of the real world object. The recognition engine can then engage a transaction engine to initiate a transaction associated with the object (e.g. , a purchase of the object, etc.), and redeem the coupon by crediting the provider's monthly statement, or other provider or user account. A final reconciliation among providers can occur on a weekly basis, monthly basis, yearly basis, one-time basis, or any other recurring or non-recurring time period.

[0032] For example, a user can be assigned a single loyalty ID or account number. When the user interacts with an object such as a poster via his mobile phone, he can be provided with a link to a website selling the poster. Based on at least one of the user's clicking on the link, saving the link, or making a purchase at a website associated with the link, a credit can be made to a loyalty account associated with the link or website. If the same user interacts with an image of Disneyland, and is automatically redirected to a website where the user purchases airplane tickets to Florida, a credit can automatically be made to a loyalty account associated with the airline or a credit card used to purchase the airplane tickets (e.g. , with frequent flyer miles, etc.).

[0033] Coupon redemption by providers can occur upon confirmation of payment even before a payment is received (e.g. , during the period wherein a credit card payment has been authorized but funds have not yet been received by the provider(s)). One should appreciate the reconciliation can occur based on a recognition of the real world object, generation of virtual coupon, entering into virtual loyalty card, and a purchase or redemption being complete in less than 2 steps. These steps can each occur on a single mobile device (or multiple devices), in real or substantially real time in the real world. In some embodiments the reconciliation can occur in real or substantially real time through collection of ambient sensor data or at a point of sales. Thus, various provider and user accounts can be credited or debited based on their loyalty activity.

[0034] An additional aspect of the inventive subject matter includes a system to allow users to pay a provider to receive a service (e.g. , telephone, utility, magazine or newspaper subscription, car lease etc,) by redemption of coupons obtained via a purchase of real world objects or services different from the first service. This can be achieved by utilizing a recognition and engagement engine in at least one of a device and a server. For example, a user who purchases a telephone at AT&T™ can be sent a coupon, via text or email, which the user can redeem to receive a free month of telephone service through Verizon™.

[0035] Figure 2 shows one embodiment of an object recognition engine of the inventive subject matter that is configured to obtain a digital representation of a real- world object and derive attributes associated with the object. In this example, real world object 210 is representative of both a product and a service, and is an image of a car. Real world object 210 is representative a product insofar as an item associated with the object (e.g. , the car, a car part, etc.) can be purchased, leased, physically destroyed, enhanced or other modified, or rented. Real world object 210 further is representative of a service insofar as it is associated with a driving or other service (e.g. , a taxi service, limousine service, etc.).

[0036] Object recognition engine 200 comprises a derivation engine 220 that is configured to derive one or more object attributes (e.g. , 221 , 222, and 223) of real world object 210.

Derivation engine 220 can be configured to derive 5, 10, 15, 20, 25, 50, or even 100 or more object attributes for every real world object it scans or recognizes. As discussed above, the object attributes (e.g. , 221 , 222, and 223) can include, among other things, an absolute time, a relative time, a response time, a location, a relative position or orientation, a color, a size, a quantity, a quality, a material, an availability, a depreciation rate, an appreciation rate, a supply relative to a demand, a shape, a make, a model, a cost, an available coupon, a message, metadata, and a price.

[0037] Some or all of the derived attributes can be derived from visible data, and others derived from non- visible data. It is also contemplated that a single attribute can be derived from both visible and non- visible data. Examples of visible data include, for example, digital representations of a size, a color, a shape, a location, a brightness, a material, a shadow, a relative size, a relative color, a relative shape, a relative location, or a relative brightness. Examples of non-visible data include, for example, digital representations of a sound, texture, touch, sensed emotion, taste or smell.

[0038] Figure 3 shows a transaction reconciliation engine of the inventive subject matter that is configured to reconcile a transaction related to a real world object or an item associated with the real world object. As used herein, an "item associated with a real world object" can comprise a good, product, subscription, real coupon, virtual coupon, or a service (e.g. , a utility, reservation, game, etc.). The transaction is reconciled among a plurality of accounts as a function of one or more of the attributes derived by an object recognition engine.

[0039] Item 300 is a car associated with object 210, which was an image of a car very similar to item 300. User 310 captures a digital representation of object 210 via a camera enabled mobile phone. Object recognition engine 220 obtains the digital representation captured by user 310, recognizes object 210 as a real world object, and derives various attributes thereof, including a make, model, year of manufacture, and color of object 210. Object recognition engine 220 then causes information related to item 300 to be presented to the user, either via the mobile phone used to capture the digital representation or a remote device. The information related to item 300 can be a video showing item 300, an accident history, a repair history, miles driven, a location, a price, an availability, and a transaction link (e.g. , a link to a website where the item can be purchased).

[0040] In this example, user 310 clicks on a link to a website where the item can be purchased, and engages in a transaction 330 that comprises a payment to four accounts, 321, 322, 323 and 324, related to item 300. This payment to the four accounts can be a lump or partial payment, and can be direct or indirect. For example, a user can make a lump (i.e. complete) or partial payment indirectly via a third party collector. A lump payment can be distributed amongst the various accounts, while a partial payment can be distributed to a specific account, or two or more accounts. It is also contemplated that the user can also make lump or partial payments directly to the accounts themselves. A direct payment can be a payment between a consumer and a provider, which is limited to the inclusion of two or more of the following: entities associated with the user account; entities associated with the provider account; the use of a transaction system of the inventive subject matter; and transaction reconciliation engine of the inventive subject matter. An indirect payment can comprise any other payment and can include a third party entity.

[0041] When user 310 purchases item 300 via the website, user 310 provides user account information to transaction reconciliation engine 320, either directly or via a third party payment processor (not shown). This user account information can include, for example, at least one of a name, address, expiration date, login username, login password, consumer ID associated with an application, account number, a name of a financial establishment, a type of account (e.g. , Visa™, Mastercard™, Discover™, American Express™, etc.), or a confirmation of a payment or authorization of a payment made by a remote server or third party.

[0042] Upon at least one of the following: receipt of user account information; confirmation of correctness or completeness of user account information; processing a payment associated with user account information; authorization of a payment associated with user account information; and receipt of a payment associated with user account information, transaction reconciliation engine 320 can reconcile the transaction among accounts 321 , 322, 323, and 324.

[0043] The following use case describes a reconciliation of a payment by the embodiment in Figure 3. User 310 makes a payment to a third party payment processor (not shown) of $10,000 USD for the purchase of item 300 according to the information provided via object recognition engine 220. To make this payment, user 310 provides the third party payment processor with a credit card authorization form approving the processing of a $10,000 USD payment. The third party payment processor processes the payment and provides a confirmation of the payment to transaction reconciliation engine 320. Transaction reconciliation engine 320 then reconciles the transaction among accounts 321 , 322, 323, and 324 by distributing the payment amongst them. Account 321 is associated with the previous owner of item 300, who receives a payment of 60% ($6,000 USD). Account 322 is associated with the car dealership storing item 300, who receives a payment of 20% ($2,000 USD). Account 323 is associated with a magazine who has been advertising item 300 for sale, who receives a payment of 10% ($1 ,000 USD). Account 324 is associated with the host of transaction reconciliation engine 320 or the system it composes, who receives a payment of 10% ($1 ,000 USD). In this manner, transaction reconciliation engine 320 allows users to pay multiple entities via a single payment.

[0044] It is also contemplated that in some embodiments, the transaction reconciliation engine can perform some or all of the functions of a third party payment processor. Thus, transaction reconciliation engine 320 can also allow providers to receive their portions of a payment efficiently and immediately without having to transact directly with user 310.

[0045] In some embodiments, as shown in Figure 4, a Software Developer Kit (SDK) 465 can be provided to developers of client-side applications (e.g. , software, cell phone apps, cloud-based services, etc.). SDK allow developers to configure mobile devices (e.g. , 400) to recognize real world 3D objects (e.g. , 410, 411 and 412) in real-time based on comparing imagery captured by a device camera with a database (e.g. , 425) of images (e.g. , 435, 436, and 437) stored in the device. This can eliminate the latency involved in sending images to the server and thus can enable real-time identification of objects within the camera field of view as a user waves the device across his environment. This mode also eliminates the need for a user to "snap" an image since recognition is operating continuously in the mobile device, thus allowing a user to engage in a transaction without requiring the user to take actions via a user interface. Preferably the user can conduct a transaction via a user interface (e.g. , 445) with no more than three or two user interface interactions, more preferably no more than one user interface interaction, or yet more preferably automatically without any user interface interactions. Example techniques that can be deployed in a recognition module include vSLAM, SIFT, VIPR, or other techniques.

[0046] On the client-side, image recognition services also can provide real-time tracking and augmented reality overlays on identified objects. These augmented reality overlays can comprise 2D content (e.g. , HTML) or 3D animated models. In either case, the augmented reality overlays can be aligned with or track the recognized object, in real-time, in the mobile device screen. The overlay content can be accessed via network or can be resident in the handset to minimize latency. In some embodiments the overlay can include a virtual coupon constructed, possibly in real-time. In some embodiments the overlay can include an advertisement, informational text, link to a website, or any other commercially suitable overlay.

[0047] The client-side image recognition services or modules can also provide real-time data describing the relative position and orientation of a tracked object.

[0048] The client-side recognition technology can be optimized to produce a smooth and robust user experience. For example, on an iPhone® 4, the Applicant' s object recognition system is able to operate easily at a rate of 10 video frames per second, where post- recognition augmented reality object tracking is able to operate at 30 frames per second.

[0049] Images in the client-side database can have an average size of approximately 30KB. A typical smart-phone can therefore accommodate a database of thousands of images.

[0050] Several options are available for loading and updating the client-side database. This includes: "User Pull", wherein the user initiates a database update by performing an action such as checking in to a retail store, selecting a product category, and so forth. A client app, via the SDK 465, then downloads images related to the user's action from the SDK server 475; and "Automatic Push", wherein the SDK server 475 automatically sends database updates to the app 485, based on any set of desired conditions, e.g. the user's location, time, actions taken within an app, local deals, coupons, or other promotions. If the database is running out of storage space, the application can be configured to automatically delete images or data from the database, preferably based on a prioritized basis (discussed further below).

[0051] In addition to server-side and client-side image recognition, the platform can also support a hybrid mode in which initial image recognition is performed by a server but augmented reality processing is performed by the client. This hybrid mode enables use of a virtually unlimited database size and eliminates the need to update the client-side database, while providing for augmented reality. This hybrid mode can cause initial delay of a few seconds between capturing a digital representation of a scene and the start of the augmented reality experience. During that delay the initial image is sent to the server, analyzed, and the augmented reality content can be sent to the client.

[0052] The client-side image recognition SDK can provide direct programmatic access to all object recognition and tracking functions (e.g. , vLSAM, VIPR, SIFT, GPS information, time stamps, etc.). The SDK can include a complete detailed function library, for use by developers familiar with image recognition, and a simplified function library that is useful for those without an image recognition background.

[0053] The client SDK can also include support for the Unity® game development environment. 3D models developed in that environment are compatible with the augmented reality functionality in the SDK.

Example Use Cases

[0054] The following use cases provide various examples of some aspects of some embodiments of the inventive subject matter.

Merchant and Consumer Applications for Redeeming a Coupon

[0055] In some embodiments, a merchant or other provider can utilize a merchant application developed via an SDK. A transaction system associated with the merchant can have certain templates, which the merchant can provision with pricing and coupons or other forms of benefits. The merchant can open the merchant application, log in with his or her merchant ID (which can be set up through a third party), and scan one or more objects by capturing an image, scanning a barcode or other symbol, via near field communications, etc. The merchant can also provision the system or application (if there are templates), or simply input pricing and coupon / benefits information, which can be saved to the system.

[0056] From a user perspective, the user can walk into the merchant's store and engage the system by opening a consumer application developed via an SDK. The user can log in to the consumer application with his or her consumer ID and scan items to view coupons / savings. The consumer can select a coupon or saving, take an item associated with the coupon to a merchant checkout counter or person and redeem the coupon.

[0057] When a merchant is presented with a coupon, the merchant can open the application and log in with his or her merchant ID. The merchant can obtain a phone number or other information associated with the consumer and input it into the application. It is contemplated that the merchant will be able to view the coupons selected by the consumer in the merchant's application. The merchant can apply the coupon selected using various methods. First, the user can apply the coupon within the merchant application if POS is enabled and the consumer is set up for payment (e.g. , via ClearXchange™). The merchant can receive confirmation of payment processing and obtain an electronic receipt, including a merchant service charge, if any. Second, the merchant can apply coupons to the consumer bill manually with his or her existing payment system. Third, the merchant can enter the total charge to an existing payment system and savings associated with the coupon(s) can be applied to the consumer's mobile phone carrier phone bill (e.g. , Verizon™, AT&T™, etc.). The consumer can receive a text, app, or email notification that the coupon(s) were applied, along with what payment option was used. The merchant and consumer can have access to all transaction online, including details of coupons / savings received, and via which method(s), among other things.

Consumer Identification, Interests and Recommendations

[0058] A consumer utilizing a transaction system of the inventive subject matter (e.g. , a SDK generated application installed in his mobile device) can obtain various recommendations, coupons, etc. based on objects or items associated with the consumer. It is contemplated that systems of the inventive subject matter can achieve at least one of the following: (1) identify a consumer, (2) identify what objects with which the consumer interacts or transacts, or (3) identify what objects and items would be of interest to the consumer.

[0059] The following use case shows some of the benefits the system can provide a consumer walking through a shopping center. Prior to entering the shopping center, the user can open up the consumer application and log in using his unique consumer ID and possibly a password. The system will identify the consumer and begin to store and prioritize data associated with the consumer.

[0060] For example, when a user walks into a specific store, sensor data can automatically be acquired and an interest in the store can be identified by the system. This identification can be based on one or more of the following, among other things: a recognition that the consumer entered the store; the amount of time the consumer spent in the store, the number of items purchased in the store; or the amount of money spent in the store.

[0061] If the consumer walks by a movie advertisement in the store, the movie advertisement can automatically be scanned, and sensor data automatically obtained. The system can then identify that the movie is of the consumer's basic level of interest and prioritize the movie poster accordingly. The system can also possibly recognize an actor, director, producer, filming location, or any other feature of the movie advertised and prioritize those features accordingly. If the consumer wishes to initiate a transaction with the movie advertisement, the consumer can capture an image of the object, or simply stand in front of the

advertisement for a specified threshold time {e.g. , 2, 5, 10, 15, or even 20 or more seconds) such that the system can recognize a moderate level of interest. The consumer can then be provided with a link to a website that provides information related to the movie {e.g. , show times, location of a DVD in the store itself, etc.) or allows the consumer to purchase movie tickets, DVD, movie poster, or soundtrack. If the consumer chooses to engage in a transaction associated with the object by clicking on this link, the system can identify that a transaction related to the movie occurred and assign a higher priority to the movie than other movies of advertisements that were scanned, based on a special level of interest. If the consumer chooses to engage in a further transaction related to the object {e.g. , a purchase the movie tickets, etc.), then the movie can be given an ever higher priority based on a superior level of interest. [0062] Based on the information recognized, stored or prioritized by the system, the system could provide a recommendation, coupon, or other information related to real world objects that have not yet been scanned or captured by the consumer. Where a class of goods or services, or a specific brand or type of goods or services is purchased by the consumer with increased frequency, those classes, brands or types of goods or services can be assigned a higher priority than those where fewer transactions occurred. Moreover, the system can identify one or more common attributes of objects that were scanned, captured, or purchased by a user and provide recommendations, coupons or information based on those attributes. Identifying the common attributes can allow the system to identify the interests and intent profile of the consumer.

[0063] It is also contemplated that the system provider can charge a fee to providers whose goods or services are mentioned in a recommendation, coupon, or other information provided to the consumer.

[0064] Once the system has identified, stored or prioritized the objects or attributes of interest to the consumer in a database associated with the system, it is contemplated that a transaction can occur automatically based on real time or substantially real time automatic ambient collection of sensor data forming a digital representation of the real-world object without requiring the end user to initiate the transaction. For example, when the user passes by Dodgers™ stadium, a mobile device carried by the user can automatically open the team's official website in an Internet browser based on stored data indicating an interest in baseball team websites.

[0065] In some contemplated embodiments, a system can be configured to identify a consumer based on location data or height data (e.g., a height of the user, location of a device relative to the ground, location of a device by street, city or state, etc.) obtained via a consumer device, objects scanned, objects with which the consumer interacts or transacts in relation to, or any combination thereof. For example, a consumer carrying a consumer mobile device may open an SDK generated application at any time. Regardless of whether the consumer enters a consumer ID, the device can begin scanning the objects within its field of view and allow the consumer to interact or transact in relation to the objects scanned. If the consumer has logged in, the consumer can be authenticated based on at least one of the location data, height data, scans, interactions or transactions. If the consumer has not logged in, the consumer can be identified based on at least one of the location data, height data, scans, interactions or transactions, thereby eliminating the need to log in manually.

Additional Concepts

[0066] One should also note that the inventive subject matter is also considered to include the additional concepts presented below.

Methods of Reconcilin2 a Payment of a Coupon

[0067] Some aspects of the inventive subject matter can include a method of reconciling a payment of a coupon, as shown in Figure 5. Such methods can comprise recognizing a real world object related to a purchasable item via a recognition engine. In some embodiments a virtual coupon can be created based on attributes derived from a digital representation of the real world object recognized via a recognition engine. The virtual coupon can then be activated via an event that is triggered from a mobile device. Moreover, a transaction amongst multiple electronic accounts associated with the object can be reconciled as a function of the derived attributes and the virtual coupon.

[0068]

Table 1 : Proposed Method of Reconciling a Payment of a Coupon Claims

associated with the real world object as a function of the derived attributes and the virtual coupon by accounts (as suggested by step 540).

The method of claim 1 , wherein the attributes include a time (as suggested by step 516).

The method of claim 1 , wherein the attributes include a location (as suggested by step 516).

The method of claim 1 , wherein the attributes compose a vector of at least three dimensions of relevance (as suggested by step 515).

The method of claim 4, wherein the attributes compose a vector of at least six dimensions of relevance (as suggested by step 515).

The method of claim 5, wherein the vector comprises the following dimensions: a time, a place, and three dimensions of the real- world object.

The method of claim 5, wherein the vector is unique to the transaction.

The method of claim 1 wherein the event occurs automatically based on ambient data.

The method of claim 1 , wherein the event includes a user generated event on the mobile device.

The method of claim 1 , wherein the step of reconciling the transaction includes authenticating the transaction via the mobile device, wherein the mobile device is emitting a transaction signal (as suggested by step 545).

The method of claim 10, wherein the transaction signal is unique to the transaction.

The method of claim 10, wherein the transaction signal comprises a visual display. The method of claim 10, wherein the transaction signal comprises a non- visual signal.

The method of claim 13, wherein the transaction signal at least one of the following: an RF signal, an audible sound, an ultrasound, a dynamic RFID value, and a light-based signal outside the visual spectrum.

The method of claim 10, wherein the step of reconciling the transaction includes reconciling payment for the item and the coupon on a periodical bill (as suggested by step 546).

The method of claim 15, wherein the periodical bill is associated with at least one of the following: a user, a coupon provider, a vendor, a cell phone carrier, a subscription, a bank, and a third-party exchange.

The method of claim 15, wherein the periodical bill comprises a periodicity of on of the following: weekly, bi-weekly, monthly, quarterly, semi-annually, and annually.

The method of claim 1 , wherein the step of reconciling the transaction includes crediting a user account associated with a service provider (as suggested by step 547).

The method of claim 1 , wherein the step of reconciling the transaction includes issuing a check to a consumer (as suggested by step 548).

A method of redeeming a coupon, the method comprising:

obtaining, via a camera enabled device, a digital representation of a real- world object related to a purchasable item; transmitting the digital representation to a reconciliation

engine;

obtaining a virtual coupon generated based on attributes of the digital representation; and

triggering an activation of the virtual coupon via the mobile

Transaction Apparatus

[0069] In some embodiments of the inventive subject matter, a transaction apparatus is provided, as shown in Figure 6. The transaction apparatus can comprise a sensor interface, recognition module, and a virtual coupon generator, among other things. The sensor interface can be configured to acquire a digital representation of a real world object. The recognition module can be coupled with the sensor interface and configured to derive object attributes from the digital representation. The recognition module can then identify a purchasable item as a function of the object attributes. The virtual coupon generator can be coupled with the recognition module and configured to generate a virtual coupon associated with the purchasable item as a function of the object attributes. The transaction apparatus can further comprise a transaction interface that is configured to reconcile an account based on a payment for the purchasable item and use of the virtual coupon.

[0070]

Table 2: Proposed Transaction Apparatus Claims

(e.g. , 660, 661, or 662) based on a payment for the purchasable item and use of the virtual coupon.

The apparatus of claim 1 , wherein the digital representation comprises a digital representation 605 of a scene.

The apparatus of claim 2, wherein the recognition module is further configured to map the object attributes to an a priori known context.

The apparatus of claim 3, wherein the virtual coupon generator is further configured to generate the coupon as a function of the context.

The apparatus of claim 1 , wherein the digital representation comprises a representation of non-visible properties of the real-world object.

The apparatus of claim 5, wherein the non- visible properties of the real-world object comprises at least one of the following: a sound, a texture, a taste, a smell, light out side the visible spectrum, a radio signal, a heat signal, an emotional state, and a non-visible bio-metric.

The apparatus of claim 1 , wherein the digital representation comprises a representation of visible properties of the real-world object.

The apparatus of claim 7, wherein the visible properties of the real- world object comprises at least one of the following: a printed text, a printed image, an electronically displayed image, a reflection, a rendering, a three dimensional model or image, a time varying appearance, a projection, and an light signal from the object.

The apparatus of claim 1 , wherein the virtual coupon comprises a promotion.

The apparatus of claim 9, wherein the promotion comprises at least one of the following: an advertisement, a sale, and a subsidy.

The apparatus of claim 1 , wherein the virtual coupon is unique to a user of the transaction apparatus. The apparatus of claim 1 , further comprising a mobile device 650 comprising the sensor interface, the recognition module, and the transaction interface.

The apparatus of claim 12, wherein the mobile device comprises at least one of the following: a mobile phone, a computer, a vehicle, a mobile kiosk, and a spacecraft.

The apparatus of claim 1, wherein the object attributes include features derived according to at least one of the following: vSLAM, VIPR, GPS, or SIFT.

The apparatus of claim 1, wherein the object attributes include a location and a time.

The apparatus of claim 1, wherein the real- world object comprises a printed object.

The apparatus of claim 1, wherein the real- world object comprises a non-printed object.

The apparatus of claim 1, wherein the purchasable item comprises at least one of the following: a good, a product, and a service.

The apparatus of claim 1, further comprising an object database 660 storing target objects and coupled with the recognition module, the target objects having target object attributes.

The apparatus of claim 19, wherein the recognition module is further configured to identify the purchasable item by obtaining a target object from the target object database by comparing the object attributes to the target object attributes.

The apparatus of claim 19, wherein the recognition module is further configured to obtain at least a portion of the object database from a remote source over a communication connection as a function of the object attributes.

The apparatus of claim 21, wherein the recognition module is configured to obtain the at least a portion of the object database based on location and time attributes.

The apparatus of claim 22, wherein the location and time attributes are associated with the transaction device.

The apparatus of claim 1 , wherein the transaction device comprises at least one of the following: a cell phone, a kiosk, a point-of-sales device, and an on-line account server.

The apparatus of claim 1 , wherein the account comprises at least one of the following: a user account, a cell carrier account, a coupon provider account, a vendor, and a service provider account.

The apparatus of claim 1 , wherein the account comprises an inventory of transactions associated with a user of the transaction apparatus.

A mobile device comprising:

a sensor interface configured to acquire a digital

representation of a real-world object;

a recognition module coupled with the sensor interface and configured to derive object attributes from the digital representation, including a location and time, and to identify a purchasable item as a function of the object attributes, including the location and time; a virtual coupon generator coupled with the recognition

module and configured to generate a virtual coupon associated with the purchasable item as a function of the object attributes; and

a transaction interface configured to reconcile at least one account based on a payment for the purchasable item and use of the virtual coupon, where a user account is credited in response to payment from the purchasable item and use of the virtual coupon.

28 A method of using a virtual coupon via a transaction apparatus,

comprising:

acquiring, via a sensor interface of the apparatus, a digital

representation of a real world object;

obtaining a virtual coupon associated with a purchasable item and generated by a virtual coupon generator as a function of object attributes derived by a recognition module; and

utilizing the virtual coupon and initiating a payment for the purchasable item.

Transaction Apparatus

[0071] Some aspects of the inventive subject matter can include a method of mitigating risk of transaction fraud, as shown in Figure 7. Such methods can comprise providing a virtual coupon associated with a purchasable item on a mobile device. The mobile device can then engage in an electronic transaction related to the purchasable item and the virtual coupon. A user can select a target account from a plurality of available user accounts (e.g. , via the mobile device, etc.). the electronic transaction can be authenticated as a function of transaction attributes derived by the mobile device and the user selected target account(s). Moreover, the target account can be credited (e.g. , with rewards points, discounts, coupons, a reduction in balance, etc.) according to terms of the virtual coupon.

[0072]

Table 3: Proposed Method of Mitigating Risk of Transaction Fraud Claims

suggested by step 710);

engaging, via the mobile device, in an electronic transaction related to the purchasable item and the virtual coupon

(as suggested by step 720);

allowing a user to select a target account from a plurality of available user accounts accessible electronically (as suggested by step 730);

authenticating the transaction as a function of transaction attributes derived by the mobile device and the user selected target account (as suggested by step 740); and crediting the target account according to terms of the virtual coupon (as suggested by step 750).

The method of claim 1 , wherein the plurality of accounts comprises multiple loyalty accounts, each associated with a distinct entity.

The method of claim 2, wherein the loyalty account comprise at least one of the following: a frequent flyer account, a credit card account, a bank account, a virtual world account, a game account, and a subscription account.

The method of claim 1 , wherein the target account is managed by a third party unaffiliated with the purchasable item.

The method of claim 1 , wherein the transaction attributes comprise virtual coupon attributes associated with the virtual coupon.

The method of claim 5, wherein the virtual coupon comprises authentication criteria that depend to the virtual coupon attributes and the transaction attributes.

The method of claim 6, wherein the authentication criteria depend on at least one of the following: a location, a time, a context, a user identifier, a vendor identifier, an item identifier, and a real-world object attribute. The method of claim 1, further comprising providing access to the mobile device to the user and wherein the mobile device conducts the steps of allowing the user to select the target account, authenticating the transaction, and crediting the target account (as suggested by step 735).

The method of claim 1 , further comprising updating a coupon inventory with an amount credited to the target account (as suggested by step 770).

The method of claim 1 , further comprising completing the transaction by reconciling payment between the target account and at least one other account (as suggested by step 780).

The method of claim 10, wherein the step of reconciling the payment includes submitting less than full payment to the at least one other account according to terms of the virtual coupon.

The method of claim 10, wherein the step of reconciling the payment includes receiving full payment from a user account.

The method of claim 10, wherein the step of reconciling the payment includes crediting the selected target account, wherein the target account comprises a subscription account.

The method of claim 1 , wherein the step of providing the virtual coupon includes displaying a coupon overlay on an image of the purchasable item on a display of the mobile device (as suggested by step 715).

The method of claim 1 , further comprising using the mobile device to derive object attributes of an object with a field of view of a sensor associated with the mobile device (as suggested by step 790).

The method of claim 15, further comprising the mobile device deriving the transaction attributes from the object attributes. The method of claim 15, further comprising the mobile device identifying the purchasable item as a function of the object attributes.

The method of claim 15, further comprising constructing the field of view based on aggregating sensor data obtained while changing an orientation or position of the mobile device (as suggested by step 795).

The method of claim 18, wherein the step of aggregating the sensor data occurs in real-time as the mobile device is moved.

The method of claim 1 , wherein the steps of engaging in the transaction requires no more than two user interface actions by the user.

The method of claim 20, wherein the steps of engaging in the transaction requires no more than one user interface actions by the user.

The method of claim 21, wherein the steps of engaging in the transaction occurs automatically via the user moving the mobile device.

A method of mitigating risk of transaction fraud, comprising:

obtaining a virtual coupon on a mobile device, the virtual coupon associated with a purchasable item; engaging, via the mobile device, in an electronic transaction related to the purchasable item and the virtual coupon; and

selecting a target account from a plurality of available user accounts accessible electronically; and

providing an input that allows an authentication of the

transaction as a function of transaction attributes derived by the mobile device and the user selected target account. [0073] It should be apparent to those skilled in the art that many more modifications besides those already described are possible without departing from the inventive concepts herein. The inventive subject matter, therefore, is not to be restricted except in the scope of the appended claims. Moreover, in interpreting both the specification and the claims, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms "comprises" and "comprising" should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced. Where the specification claims refers to at least one of something selected from the group consisting of A, B, C .... and N, the text should be interpreted as requiring only one element from the group, not A plus N, or B plus N, etc.