The following relates generally to a mobile operating environment, and more particularly to providing dynamic mobile coupons in such a mobile operating environment.
In recent years, a variety of advancements has occurred in cellular communication technology and cellular communication devices. Some of the advancements, such as integration of camera and video recording technology onto such devices, incorporation of e-mail and short messaging services into mobile communication, and the like, involve software and/or hardware applications. These applications have added increased flexibility, processing power, communication capabilities, and so forth, to already popular communication devices (e.g., cellular telephones). As a result, such devices have become more popular in a consumer marketplace, motivating larger numbers of consumers to purchase such devices, or to upgrade to devices that include new applications and technologies.
As larger numbers of consumers own and utilize mobile devices, business mechanisms traditionally limited to personal, radio, television or landline telephone contact are expanding into the mobile environment. For instance, as the Internet becomes increasingly accessible via mobile communication devices, e-mail and web browsing applications are utilized with mobile devices. Further, electronic commerce is conducted by way of such devices as well. For instance, secure web applications can provide an interface for conducting online commercial transactions with a web browsing device. Credit card, debit card, bank transfer and like payments can be facilitated utilizing secure web applications by way of such device.
In addition to the foregoing, other commercial mechanisms have also been incorporated into mobile devices and mobile communication environments. For instance, electronic coupons stored on mobile devices can be utilized to replace paper coupons. A commercial entity can generate coupons and distribute them to mobile devices, which can in turn facilitate redemption of coupons in conjunction with commercial transactions. As electronic files, such coupons have more flexibility than traditional paper coupons. For instance, a paper coupon is more readily misplaced as compared with an electronic coupon stored on a mobile device. Further, an electronic coupon can incorporate various security measures to mitigate duplication and other unauthorized uses. Accordingly, many benefits accrue upon introduction of electronic coupons in a mobile operating environment.
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed description that is presented later.
Disclosed herein are dynamic electronic coupons configured for a mobile device and having a variable characteristic, such as commercial value, in conjunction with a commercial transaction. Such electronic coupons, or dynamic mobile coupons (DMCs) as configured for a mobile device, can be delivered to the mobile device from a voice and/or data service provider, retail entity, third party supplier, or the like. The variable characteristic of the DMC is established based at least in part on a factor pertinent to a recipient mobile device, a user of the device, a coupon profile provided by a sponsor of the coupon, etc.
A variable characteristic of a DMC can be determined prior to transmitting the DMC to a recipient device. Alternatively, or in addition, the variable characteristic of the DMC can be determined after transmission of the DMC to the recipient device. Further, in at least some aspects, a determined characteristic can be dynamically updated based on additional circumstances and/or criteria. Upon redemption of the DMC, the characteristic is fixed and at least an aspect of the characteristic is applied to a transaction. Data pertaining to the transaction and the DMC can be sent to a clearinghouse entity that facilitates payment or reimbursement, where suitable, to a retail entity that redeems the coupon (e.g., a retail store). Therefore, the subject disclosure describes a DMC that facilitates a rich and flexible mechanism to generate purchasing incentive for consumers in a mobile environment.
In one or more aspects, disclosed is a method of providing an electronic coupon in a mobile operating environment. The method comprises associating a DMC with a target mobile device wherein the DMC has at least one variable coupon characteristic. Further, the method can comprise establishing an initial parameter for variable coupon characteristic(s) based on a determinable circumstance pertinent to the target mobile device or a user account of/associated with the device. In some aspects, the method can comprise communicatively coupling with a clearinghouse in conjunction with applying the value of the DMC to a transaction.
In some aspects, described is an apparatus that facilitates distribution, redemption, or valuation of an electronic coupon in a mobile environment. The apparatus can comprise a coupon module that associates a DMC with a target mobile device, wherein the DMC has at least one variable coupon characteristic. The apparatus can further comprise a valuation module that establishes an initial parameter of the variable coupon characteristic based on a determinable circumstance pertinent to the target mobile device or a user account of/associated with the device. The apparatus can also include memory that stores at least the coupon module and the valuation module to facilitate DMC distribution by the apparatus, and a processor that executes the modules. Optionally, the apparatus can include a wired and/or wireless interface that sends the DMC or an indication thereof to the selected mobile device.
In accordance with one or more additional aspects, disclosed is a DMC distribution device. The DMC distribution device can comprise a first module configured to associate a DMC with a target mobile device, wherein the DMC has at least one variable coupon characteristic. Further, the device can comprise a third module configured to establish an initial parameter for the variable coupon characteristic based on a determinable circumstance pertinent to the target mobile device or a user account of/associated with the device. The distribution device can optionally include a fourth module configured to communicatively couple with a clearinghouse in conjunction with applying the value of the DMC to a transaction.
According to a further aspect, described is an apparatus configured to provide an electronic coupon in a mobile operating environment. The apparatus can comprise means for associating a DMC with a target mobile device, wherein the DMC has at least one variable coupon characteristic. Further, the apparatus can comprise means for establishing an initial parameter of the variable coupon characteristic based on a determinable circumstance pertinent to the target mobile device or a user account of/associated with the device.
In at least one additional aspect, disclosed is a computer program product for communication between remote devices. The computer program product comprises a computer-readable medium containing instructions executable by at least one computer to associate a DMC with a target mobile device, wherein the DMC has at least one variable coupon characteristic. Moreover, the instructions can be executable by the at least one computer to establish an initial parameter of the variable coupon characteristic based on a determinable circumstance pertinent to the target mobile device or a user account of/associated with the device.
According to one or more other aspects, provided is a method of communication between remote devices. The method can comprise obtaining data from a device; the data comprises a DMC or an indication of the DMC and further comprises at least one variable coupon characteristic. Further, the method can comprise obtaining a factor relevant to establishing an initial parameter for the variable coupon characteristic and collecting data pertinent to the factor to facilitate establishing the initial parameter.
In additional aspects, disclosed is an apparatus that facilitates implementing a dynamic electronic coupon in a mobile environment. The apparatus comprises a transceiver that obtains a DMC having at least one variable coupon characteristic, or an indication of such DMC and characteristic, and at least one factor relevant to establishing an initial parameter for the variable coupon characteristic. The apparatus can further comprise memory that stores the DMC or factor(s) and a valuation engine that collects data pertinent to the at least one factor to facilitate establishing the initial parameter for the variable coupon characteristic.
According to a further aspect, provided is a mobile device. The mobile device can comprise a transceiver configured for wired and/or wireless data exchange with a remote device. The mobile device can further include a first module configured to obtain a DMC or an indication of the DMC from the remote device, wherein the DMC has at least one variable coupon characteristic. Further, the mobile device can comprise a second module configured to obtain at least one factor relevant to establishing an initial parameter for the variable coupon characteristic and a third module configured to collect data pertinent to the factor(s) to facilitate establishing of the initial parameter.
According to an additional aspect, provided is an apparatus configured for communication with a remote device. The apparatus can comprise means for obtaining a DMC or an indication of the DMC from a device, wherein the DMC has at least one variable coupon characteristic. Moreover, the apparatus can comprise means for obtaining at least one factor relevant to establishing an initial parameter for the variable coupon characteristic and means for collecting data pertinent to the at least one factor to facilitate establishing the initial parameter.
In accordance with still another aspect, disclosed is a computer program product configured for communication with a remote device. The computer program produce can comprise a computer-readable medium containing instructions executable to obtain a DMC or an indication of the DMC from a device, wherein the DMC has at least one variable coupon characteristic. The instructions can be further executable to obtain at least one factor relevant to establishing an initial parameter for the variable coupon characteristic and to collect data pertinent to the at least one factor to facilitate establishing the initial parameter.
To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative aspects of the one or more aspects. These aspects are indicative, however, of but a few of the various ways in which the principles of various aspects can be employed and the described aspects are intended to include all such aspects and their equivalents.
Various aspects are now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It can be evident, however, that such aspect(s) can be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing one or more aspects.
The subject disclosure provides for variable characteristic electronic coupons for a mobile environment. The electronic coupons can be distributed to a particular mobile device, selected based on predetermined criteria (e.g., location, time, identity, prior mobile device-based commercial transactions, features/capabilities of the mobile device, and so on). In addition, the electronic coupons can provide some value in conjunction with a commercial transaction. Particularly, the value is variable, in that it can be undetermined or adjustable at a given point in time. By adjusting the variable characteristic (e.g., a redeemable value) of an electronic coupon, a consumer can be given a greater or lesser incentive to conduct the transaction at a given point in time or based on a given circumstance.
In addition to the foregoing, mobile coupons (e.g., an electronic coupon configured for, distributed to, stored on and/or redeemed utilizing a mobile device) can be distributed based on information pertinent to a mobile device, user accounts maintained on such devices (e.g., mobile coupon account), interaction with users in a user ‘buddy list’, and the like. The nature of mobile devices (e.g., cell phone, smart phone, PDA, laptop, multi-mode phone, and so on) involves dynamic, yet generally determinable characteristics. For instance, a location of the mobile device can change over time as a user carries the mobile device, transports the mobile device in a vehicle, etc. Strength of signals emitted by a mobile device (e.g., radio frequency [RF] signals) can vary over time as well, as location, transmission strength, battery power, or like factors associated with the mobile device change. Accordingly, a wireless device communicatively coupled with a mobile device can determine various dynamic characteristics of such device based on signals received or transmitted to such mobile device.
Because mobile devices involve dynamic characteristics, directed marketing involving a mobile device can be conducted based on contemporaneous conditions of such device. For instance, a mobile coupon can be distributed to the mobile device based on location of the mobile device, capabilities/functions of the mobile device, or time of day, or a combination of these or like factors. It should also be appreciated that a mobile coupon can have dynamic or variable coupon characteristics as well. In some aspects, an attribute of the coupon can depend on a dynamic characteristic of the mobile device. For instance, a redeemable value of a DMC can be based on a location of the mobile device. The foregoing example describes a mobile coupon with a dynamic characteristic and provides at least one example of a dynamic mobile coupon (DMC).
As a particular example of the foregoing, a redeemable value of a DMC can provide a first monetary value if the mobile device is at a first location and a second monetary value if the mobile device is not at the first location (or, e.g., is not within a threshold distance of the first location). In some aspects, the redeemable value of the DMC can be independent of characteristics associated with the mobile device. As another example, the redeemable value could provide the first monetary value between 9 am and 12 noon, and the second monetary value between 12 noon and 5 pm, regardless of location of the mobile device. As a third example, various suitable circumstances can be combined to determine the redeemable value. For instance, the DMC can provide the first monetary value if the mobile device is at the first location between 9:00 am and 12:00 noon, and provide the second monetary value in all other circumstances. It should be appreciated that various suitable algorithms (e.g., Boolean logic) are contemplated for establishing a value, or other variable coupon characteristic, of a DMC.
By determining changing aspects of mobile devices, DMCs can be distributed to such devices based on user profile(s) or device characteristics. In addition, because mobile coupons are electronic files, such as audio and/or video media files, mobile coupons can be rich multi-dimensional media, graphical files, programs, and the like. For instance, a DMC can be displayed and presented on a graphical display in three dimensions (simulated or actual), with various layers, animations, video, audio, sections, fonts, drawings, figures, and the like. Further, additional applications can be linked to the DMC. As an example, product, manufacturer, distributor, and/or retail electronic media advertisements can be coupled to the DMC. Such media can utilize graphical animation to provide a rich and detailed user experience. In addition, characteristics of the DMC (e.g., redeemable value) can be adjusted based on value-added incentives included with the DMC, such as a video advertisement.
According to one or more other aspects, DMCs can be stored and organized on a mobile device for user convenience. The DMCs can be referenced based on suitable indicia, such as supplier, product, retail entity, and the like. DMCs can also be categorized as a function of concurrent value. In addition, rules defining changes to redeemable value can be displayed, where desired. In some aspects, rules for defining value or value adjustment can be hidden or not included with the DMC. Accordingly, some DMCs can adjust or determine redeemable value based on factors undisclosed to a consumer. As described, the disclosure presents a rich and flexible environment for distributing, valuing, and redeeming mobile coupons in a mobile communication environment.
The disclosure herein facilitates many commercial benefits, including providing variable purchasing incentive based at least in part on dynamic factors associated with a mobile device, a stored profile of a user, manufacturer, coupon distributor, etc., a dynamic commercial influence associated with a store or product (e.g., current inventory), and so on. Thus, purchasing incentive provided through coupons can be dynamically tailored to fit the desires of a coupon sponsor based on fluctuating consumer and market conditions.
Various aspects of the disclosure are described below. It should be apparent that the teaching herein can be embodied in a wide variety of forms and that any specific structure and/or function disclosed herein is merely representative. Based on the teachings herein one skilled in the art should appreciate that an aspect disclosed herein can be implemented independently of other aspects and that two or more of these aspects can be combined in various ways. For example, an apparatus can be implemented and/or a method practiced using any number of the aspects set forth herein. In addition, an apparatus can be implemented and/or a method practiced using other structure and/or functionality in addition to or other than one or more of the aspects set forth herein. As an example, many of the methods, devices, systems, and apparatuses described herein are described in the context of providing dynamic mobile coupons in a mobile communication environment. One skilled in the art should appreciate that similar techniques could apply to other communication environments as well.
As used in this disclosure, the terms “component,” “system,” “module,” and the like are intended to refer to a computer-related entity, either hardware, software, software in execution, firmware, middle ware, microcode, and/or any combination thereof. For example, a component can be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two or more computers. Further, these components can execute from various computer readable media having various data structures stored thereon. The components can communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems by way of the signal). Additionally, components of systems described herein can be rearranged and/or complemented by additional components in order to facilitate achieving the various aspects, goals, advantages, etc., described with regard thereto, and are not limited to the precise configurations set forth in a given figure, as will be appreciated by one skilled in the art.
Additionally, the various illustrative logics, logical blocks, modules, and circuits described in connection with the aspects disclosed herein can be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any suitable combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but, in the alternative, the processor can be any conventional processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other suitable configuration. Additionally, at least one processor can comprise one or more modules operable to perform one or more of the steps and/or actions described herein.
Furthermore, various aspects are described herein in connection with a mobile communication device (or, e.g., a mobile device). A mobile communication device can also be called a system, a subscriber unit, a subscriber station, mobile station, mobile, mobile device, cellular device, multi-mode device, remote station, remote terminal, access terminal, user terminal, user agent, a user device, or user equipment, or the like. A subscriber station can be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device having wireless connection capability, or other processing device connected to a wireless modem or similar mechanism facilitating wireless communication with a processing device.
Moreover, various aspects or features described herein can be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. Further, the steps and/or actions of a method or algorithm described in connection with the aspects disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. Additionally, in some aspects, the steps and/or actions of a method or algorithm can reside as at least one or any combination or set of codes and/or instructions on a machine-readable medium and/or computer readable medium, which can be incorporated into a computer program product. Further, the term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., compact disk (CD), digital versatile disk (DVD), etc.) smart cards, and flash memory devices (e.g., card, stick, key drive, etc.). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term “machine-readable medium” can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.
In addition to the foregoing, the word “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the word exemplary is intended to present concepts in a concrete fashion. Furthermore, as used in this application and the appended claims, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, in this example, X could employ A, or X could employ B, or X could employ both A and B, and thus the statement “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.
As used herein, the terms to “infer” or “inference” refer generally to the process of reasoning about or inferring states of a system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic—that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data. Such inference results in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources.
Referring now to the drawings,
As utilized herein, a DMC refers to an electronic application, program, file, or the like, that can be redeemed for economic value in conjunction with a transaction, and has at least one characteristic that varies based on a determinable circumstance. In some aspects, the DMC can be a stand-alone application transmitted to an external entity (e.g., mobile device 104). In other aspects, the DMC can be retained at a distribution device (e.g., coupon system 102), and information identifying, describing and/or pertinent to redeeming the DMC can be transmitted to the external entity (104). In still other aspects, a DMC can be copied and shared between the distributor (102) and the external entity (104).
As stated above, a DMC provides some economic value in conjunction with a transaction. The transaction can include a sale, lease, rent, or a like exchange of a product, a service, and so on. The economic value can include any suitable modification of a term or condition of the transaction. For example, the economic value can be a reduction in purchase price of a product or products (e.g., a percent discount, a flat reduction in price, a discount or reduction of a second product or service based on purchase of a first product or service, and so on). As another example, the economic value can be an extension of a benefit (e.g., a warranty, customer service, technical support, etc.) associated with the transaction. It should be appreciated that the economic value can comprise any suitable economic consumer benefit utilized in conjunction with paper coupons or radio/television coupons, in addition to values and benefits specifically described herein.
In addition to the foregoing, a DMC is dynamic, and as such involves at least one characteristic that can vary based on determinable circumstances. For instance, the economic value of the DMC can vary. In another example, an expiration date of the DMC can vary. In still other examples, a product or service, a retailer, conditions of redemption (e.g., time, location), or like characteristics associated with the DMC, or a combination thereof, can vary. The variable characteristic can have a default state that is subsequently adjusted based on the determinable circumstances, or can have no predetermined default state. In the latter case, the state of the characteristic is undefined, or zero, until data pertaining to one or more determinable circumstances is obtained and analyzed.
Variable coupon characteristics of the DMC can be evaluated utilizing various factors. For instance, data pertinent to the mobile device 104, data pertinent to a sponsor/issuer of the DMC (102), data pertinent to a retail entity (e.g., retail store, online store, and so on) such as in-stock volume, data pertinent to a state of a user account, or interactions with other user accounts of other devices (e.g., sharing or recommending a DMC with another user), or independent factors such as time can be utilized as determinable circumstances. Such data can be collected in various manners. For instance, data pertinent to the mobile device 104 or a user account can be obtained from the mobile device 104 or by way of exchanging wireless signals (e.g., RF signals) with the mobile device 104. Data pertinent to a sponsor/issuer of the DMC or to a retail entity can be obtained dynamically by way of a communication link with one or more such entities, or the data can be manually entered, or can be predefined and stored by the coupon system 102. Once collected, data can be utilized to evaluate one or more variable coupon characteristics associated with the DMC.
Variable coupon characteristics of a DMC (e.g., redeemable value, multidimensional feature(s)) can be evaluated at any suitable time after receiving information pertinent to quantifying or qualifying such characteristic(s). For instance, a value of a DMC can be generated once an identity of a mobile device or user thereof is determined, once a location of the mobile device is determined, once a time of day is determined, or once a user/manufacturer/retailer/DMC profile is determined, or a combination thereof. According to some aspects, the characteristic can be determined prior to associating the DMC with the mobile device 104, after such association, or both (e.g., an initial parameter of the characteristic can be determined prior to association and the initial value can be altered based on later conditions). According to one or more further aspects, the characteristic can be generated in response to a user input (e.g., a user input can result in collection of data, application of data to a valuation formula, and/or display of a calculated value). In another aspect, the characteristic can be determined/updated before, concurrent with, or after transmission of the DMC or an indication of the DMC to the mobile device 104. In accordance with still one or more other aspects, the characteristic can be updated at a suitable point prior to or during redemption of the coupon. An updated characteristic can be based on the determinable circumstances, a predetermined time or sequence, and/or user input. Accordingly, a DMC is a very flexible and rich entity that can provide various consumer purchasing incentives and can be updated dynamically based on changing conditions, user input, and so on.
It should be appreciated that variable characteristics of the DMC can be fixed to prevent further variation of the characteristic. For instance, an initial parameter (e.g., quantitative amount) of a variable coupon characteristic (e.g., product discount, redeemable value) can be established upon generating the DMC for a particular device/user (104), associating the DMC with the device/user (104), transmitting the DMC or an indication thereof to the device/user (104), based on a user input at the mobile device 104, upon redemption, or upon sharing/trading the DMC with another device/user, or a suitable combination thereof. In some aspects, as discussed above, the variable characteristic can continue to vary based on changes in one or more determinable circumstances after the initial parameter is established. In other aspects, the variable characteristic can be fixed based on the initial parameter and not vary further. Alternatively, or in addition, the variable characteristic can be subject to further adjustment based on a set of circumstances provided by a coupon manufacturer, based on a user input at the mobile device 104, or a suitable combination of both. As one particular example, the initial parameter of the variable coupon characteristic can be established based on a determined circumstance(s) (e.g., location of the mobile device with respect to a retail outlet, and number of previous DMCs pertaining to the retail outlet that the device has received, redeemed, shared, viewed, etc.), when the DMC is associated with the device/user (104). Thereafter, the coupon characteristic can be fixed until redemption. At redemption, additional circumstances are determined and the coupon characteristic adjusted, as suitable. It should be appreciated that various other suitable examples of when the initial parameter can be determined and when it can be adjusted exist, as well as under what circumstances the determination/adjustment can occur. Accordingly, the subject disclosure is not limited to the specific examples recited herein.
In addition to the foregoing, coupon system 102 can include a filter module 106 that can select a particular mobile device 104 for distribution of a DMC. Selection can be based on criteria associated with the mobile device 104. For instance, a location of the mobile device 104 can be utilized in determining whether to generate a DMC for such device (104). In addition, time, an ID of the mobile device (e.g., subscriber identity module, mobile device calling number, or the like), an identity of a user of the mobile device, prior transaction history, prior coupon history, a user profile, sharing/trading mobile coupons with other user accounts, a DMC profile associated with a particular DMC, a manufacturer profile, a profile associated with a coupon distribution entity (102), a retailer profile, or a combination thereof or of like factors can be utilized to determine whether to generate the DMC for mobile device 104. Criteria for selecting a mobile device can be stored at coupon system 102. In addition, such criteria can be provided by a sponsor of the DMC (not depicted). Accordingly, a sponsor can provide a DMC only to those devices (104) that meet criteria identified by the sponsor.
Coupon system 102 can also include a valuation module 108 that establishes an initial parameter for the variable coupon characteristic of the DMC. According to one or more particular aspects of the disclosure, the initial parameter can be based on a determinable circumstance pertinent to mobile device 104. In other aspects, the initial parameter can be based on generic circumstances established by a sponsor of the DMC. The determinable circumstance can be a subset of the data utilized by the filter component 106 to select the mobile device 104, or can include additional data pertinent to the mobile device 104 (e.g., information in a user profile history, such as mobile shopping history, DMC usage history, DMC redistribution information such as inter-device sharing, and so on). Valuation module 108 can collect data pertinent to the determinable circumstance, apply the data to a predetermined formula, and establish the initial parameter of the DMC variable coupon characteristic. Data can be collected at the coupon system 102, from mobile device 104 or a network component (not depicted) associated with the coupon system 102 (e.g., a back-end server, data farm, or the like), from a sponsor of the DMC (e.g., a manufacturer), and so on.
Valuation module 108 can also continue to collect data associated with one or more determinable circumstances, and update the established initial parameter, accordingly. For instance, location of mobile device 104 can be monitored (e.g., by communication with the mobile device 104 or with an associated mobile network) and the established parameter updated periodically based on location. As another example, the value can be updated based on conditions provided by a manufacturer or retail entity associated with the DMC. As a more specific example, a restaurant can offer a first discount value if the DMC is redeemed during lunch operation (e.g., at a predetermined range of time) and a second discount value if the DMC is redeemed during dinner operation (e.g., at a second predetermined range of time). Valuation module 108, therefore, can update a concurrent value of the DMC based on time of day and lunch and dinner hours of the restaurant. It should be appreciated that any suitable circumstance utilized to establish a value for a DMC, as described herein, can also be utilized to update the value of the DMC at a subsequent point in time (e.g., upon redemption).
Coupon system 102 can also include a redemption module 110. Redemption module 110 can couple to a clearinghouse (not depicted) to facilitate application of a value of the DMC (e.g., established by the valuation module 108) to a transaction. For instance, if mobile device 104 redeems the DMC in conjunction with a transaction identified by the DMC (e.g., purchase of a hamburger at a fast food restaurant), a value established by the valuation module 108 can be applied to the transaction. Results of the transaction, including an identity of the DMC, the mobile device, a retail entity redeeming the DMC, a product/service involved, and/or value provided via the DMC, can be received by redemption module 110 (e.g., from the retail entity facilitating the transaction). Redemption module 110 can then perform a check to determine that terms and conditions of the DMC are accurately reflected in the transaction (e.g., the established value is appropriately provided to a transaction). If the transaction is appropriate, redemption module 110 can then transmit information pertaining to the DMC to the clearinghouse. The clearinghouse can perform various mediation functions, including performing an additional check for compliance with DMC terms and conditions, indemnifying the retail entity for applying the established value to the transaction, and so on. As described, system 100 provides for a flexible electronic coupon in a mobile environment, to facilitate directed marketing at consumers based at least in part on concurrent and determinable information associated with a mobile device 104.
Once mobile device 204 is selected, coupon distributor 208 generates a DMC (212A, 212B, 212C) provided by manufacturer 206 and associates the DMC with the mobile device 204. The coupon distributor 208 can then forward the DMC (212A, 212B, 212C) to coupon system 202. Coupon system 202 then distributes the DMC (212A, 212B, 212C), or a message identifying and/or describing the DMC (212A, 212B, 212C) to mobile device 204 (e.g., a short message service [SMS] message, e-mail message, text message, ad-hoc wireless data exchange, and so on). The DMC (212A, 212B, 212C) can have a variable coupon characteristic, such as redeemable value, evaluated by way of a determinable circumstance associated with the mobile device 204 and/or other components of system 200 (e.g., manufacturer 206, retailer 210). Coupon distributor 208 can comprise a mobile base station, a wireless node, a stand-alone wireless device that is manually uploaded with the DMC, or any other suitable wireless communication device.
Determination of the variable coupon characteristic can be done at a network component (e.g., coupon system 202, coupon distributor 208, etc.) or at the mobile device 204, or a combination of both. For instance, the DMC (212A, 212B, 212C) can contain instructions (e.g., an executable module) directing the mobile device 204 to establish a parameter for the variable coupon characteristic and rules for doing so. In other aspects, mobile device 204 can also provide information specified by the DMC (212A, 212B, 212C) to the coupon system 202 pertinent to determining this value (e.g., a GPS location of mobile device 204). In some aspects, if mobile device 204 is unable to obtain the variable coupon characteristic or initial parameter value from the coupon system 202 (e.g., due to inability to establish a wireless link), an executable module included within the DMC (212A, 212B, 212C) can be utilized to calculate the value at mobile device 204.
The determination, as discussed above, can be conducted at various suitable times. For instance, when mobile device 204 is first selected by coupon system 202, when the DMC (212A, 212B, 212C) is generated at coupon distributor 208, when the DMC (212A, 212B, 212C), or an indication thereof, is transmitted to the mobile handset 204, at a predetermined point in time after the mobile handset 204 receives the DMC (212A, 212B, 212C), as a result of a user input (e.g., recommending the DMC, forwarding the DMC to another mobile device via ad-hoc data exchange, or utilizing a network), based on activity of a third party (e.g., a ‘buddy list’ member obtains, recommends, redeems or somehow interacts with the DMC), based on a threshold change in a determinable circumstance associated with the mobile device 204, or upon redemption, or a combination thereof. Accordingly, in such aspects, an initial parameter can be adjusted (e.g., according to rules provided manufacturer 206) up until redemption of the DMC (212A, 212B, 212C).
As depicted, a DMC (212A, 212B, 212C) is transmitted to various components of system 200 as shown by the solid line arrows of
DMC 212A is received by coupon distributor 208. Coupon distributor 208 can generate an electronic file to package the DMC (212A, 212B, 212C). For instance, the electronic file can facilitate displaying and/or playing media pertinent to a product, value, redemption information, variable coupon characteristics, or rules for evaluating/updating such characteristics, and so on, of the DMC (212A, 212B, 212C). The electronic file can be in various formats based on feedback from the mobile device 204 (e.g., a pdf-type format, a word-processing format, a spreadsheet format, etc.).
Once an electronic package for the DMC (212A, 212B, 212C) is generated, and a mobile device 204 selected, DMC 212B is sent to coupon system 202. Coupon system 202, as discussed, can establish a value (e.g., an initial value, or a fixed value, etc.) of the dynamic aspects of the DMC 212C upon transmitting the DMC 212C to mobile device 204. Alternatively, coupon system 202 can leave the dynamic aspects undefined at such time. A version of the DMC (212A, 212B, 212C) received at mobile device 204 is indicated by DMC 212C.
The dotted line of
Mobile handset 204 can utilize the DMC 212C in conjunction with a transaction at a retailer 210 identified in the DMC 212C. Retailer 210 can be any suitable store, physical or virtual (e.g., an online Internet vendor), that can provide a product or service identified in the DMC 212C. Mobile handset 204 transmits the DMC 212C, or unique ID of the DMC 212C, or the like, to the retailer 210 in conjunction with a suitable transaction. Retailer 210 forwards the transaction information to a clearinghouse 214 for mediation, authorization, and/or reimbursement.
Clearinghouse 214 can be any suitable networked entity that can provide billing and mediation for a DMC (212A, 212B, 212C). Specifically, clearinghouse 214 obtains information pertinent to a transaction from retailer 210 that involves the DMC (212A, 212B, 212C). Clearinghouse 214 can determine whether the DMC (212A, 212B, 212C) is valid, whether applying the DMC (212A, 212B, 212C) to the transaction is valid, whether the DMC (212A, 212B, 212C) is properly applied to the transaction, and so on. If the information pertinent to the transaction matches specifications for the DMC (212A, 212B, 212C), clearinghouse 214 can forward data identifying the transaction and the DMC (212A, 212B, 212C) to manufacturer 206. Manufacturer 206 can then provide reimbursement for the DCM (212A, 212B, 212C) to clearinghouse 214, which forwards at least a portion of such reimbursement to retailer 210. Accordingly, system 200 provides one example system that can generate, distribute, redeem, and indemnify various entities in conjunction with implementing a DMC (212A, 212B, 212C) in a mobile environment.
According to some aspects, system 300 can include a transaction database 306 that stores information related to a user profile, a vendor profile, a DMC profile or a retailer profiler, or a combination thereof. A user profile can provide user preferences in conjunction with a DMC (e.g., indicating a desired sponsor, a desired retailer, a desired product, whether and/or what type of DMC is to be accepted at the mobile device 304, or the like). The user profile can also include prior transaction history associated with a user of the mobile device 304, including previous DMC received, cancelled, redeemed, stored on the device 304, and so on. The user profile can also indicate prior DMC transaction history, mobile shopping history, or sharing and social network history pertinent to DMCs. In some aspects, the user profile can include feature information of the mobile device 304 (e.g., for determining what multi-media features associated with the DMC can be activated). Information contained in the user profile can be utilized, at least in part, to select a mobile device (204) as a target device for DMC distribution and/or to determine a parameter of a DMC variable coupon characteristic (e.g. set a redeemable value), or other variable coupon characteristic of the DMC (e.g., re-distribution and sharing rules, multi-media features bundled within the mobile device).
According to some aspects, system 300 can include a data mining module 310 to interface with various system components (302, 304) to extract information and update transaction database 306. For instance, data mining module 310 can interface with mobile device 304 and obtain information pertinent to user transaction history, saved DMCs, preferred DMCs, DMCs viewed on a user interface of mobile device 304, DMC advertisements played at the mobile device 304, and so on. Such information can be forwarded to transaction database 306 and added to the user's (304) profile, a DMC profile, vendor profile, manufacturer profile, distributor profile, and/or retailer profile associated with the DMC. In similar fashion, data mining module 310 can interface with vendor, retailer, or distributor entities or with coupon system 302 (including sub-components of such system 302) and generate/update appropriate profiles at transaction database 306. Accordingly, information stored at transaction database 306 can be continually updated based on data extracted by data mining module 310.
According to some aspects, a vendor profile contained within the transaction database 306 can provide various rules for generating, distributing, evaluating and/or redeeming a DMC, as specified by a sponsor of the DMC (e.g., product manufacturer). Such information will be utilized by system 300 in conjunction with distributing a DMC, in conjunction with determining a value of the DMC, and/or other dynamic aspects of the DMC. A retailer profile can also be contained within the transaction database 306. The retailer profile can include information pertinent to a product or service identified in a DMC, availability of such product/service at a particular retail location, participation of such retail location in a DMC transaction, and additional terms or conditions imposed by the retailer. For instance, a retailer profile can indicate which locations will honor a DMC, current product/service availability applicable to the DMC, hours of operation, hours of redemption, any factors pertinent to determining a value of the DMC or other provided benefit (e.g., a change in redeemable value at various times of day), and the like. In addition to the foregoing, transaction database 306 can include a DMC profile that contains particular information pertinent to each DMC or type of DMC provided by a sponsor. The DMC profile can indicate special incentives included within the DMC (e.g., a product advertisement, see
As a specific example of the foregoing, various profiles can be contained in transaction database 306 that affect a DMC. As a first example, a profile of User A could indicate that User A is interested only in DMCs related to pizza restaurants or pizza in particular. Thus, system 300 can ignore a mobile device 304 associated with User A when distributing a non pizza-related DMC. A profile of Manufacturer X can specify that a DMC is to have a variable redeemable value, depending on both proximity of the mobile device 304 to a retail location, and based on the time of day. In addition, Manufacturer X's profile can indicate that a DMC should be generated once each day and that all of Manufacturer X's DMCs are to expire within 30 days of distribution to a mobile device 304. Accordingly, system 300 can generate one DMC for Manufacturer X per day (e.g., calendar day), set and adjust a redeemable value of each Manufacturer X DMC based on location of a recipient mobile device (304) and time of day, and set an expiration date for such DMC(s) at 30 days from distribution to the recipient mobile device(s) (304). Likewise, similar information contained within a retailer or DMC profile can be integrated into terms, conditions, and variable coupon characteristics of a DMC.
System 300 can further include a learning engine 308 that employs machine learning to evaluate information contained in the transaction database 306 and make strategic determinations related to a DMC. In one aspect, learning engine 308 can employ user profile information to determine whether or what DMC is most appropriate to associate with a particular mobile device 304 (e.g., based on past DMC usage history, mobile shopping history, etc.). In another aspect, learning engine can employ such information to evaluate a determinable circumstance associated with a mobile device 304 and establish an initial parameter of a variable coupon characteristic (e.g., redeemable value, applicable media-features). Information utilized by learning engine 308 can be referenced with respect to at least one DMC distribution or valuation rule (e.g., provided by a DMC sponsor or distributor) for making the determinations (e.g., distribute a particular DMC only within 30 minutes of a time period that the DMC is most likely to be redeemed).
Information utilized by learning engine 308 can comprise any suitable information pertinent to the mobile device 304, a DMC, or a DMC sponsor, retailer, or the like (e.g., determined from an applicable profile). More specifically, such information can include time, mobile device location, distribution device location and/or retail store(s) location, user transaction or coupon history, frequent user coupon points, retailer profile information, DMC profile information, and so on. In one example, the learning engine 308 can utilize user mobile shopping history and DMC usage history to determine whether to distribute/associate the DMC with the mobile device 304, and determine an initial parameter for the variable coupon characteristic prior to such distribution/association. It should be appreciated that as data is updated at transaction database 306, the learning engine 308 can re-evaluate the information to update a state of the variable characteristic. As a particular example, if a DMC is presented for redemption, transaction module can access pertinent profile or history information to establish a final redeemable value for the DMC at time of redemption.
To make strategic determinations, learning engine 308 can utilize a set of models (e.g., user preference model, coupon sponsor model, usage/sharing history model, etc.) in connection with determining relationships between information contained in the transaction database 306 and rules for distributing and/or valuating a DMC. The models can be based on a plurality of information (e.g., a state of a user/manufacturer DMC distribution flag, frequency of past user DMC activity, user feedback pertinent to one or more DMCs, retail availability of a product/service, general mobile shopping history or preferences, location of the mobile device 304, distance between the mobile device 304 and DMC distribution device (302) and/or a retail entity, and so on). Optimization routines associated with learning engine 308 can harness a model that is trained from previously collected data, a model that is based on a prior model that is updated with new data, via model mixture or a data mixing methodology, or simply one that is trained with seed data, and thereafter tuned in real-time by training with actual field data provided by user interest vector 604.
In addition, learning engine 308 can employ learning and reasoning techniques in connection with making determinations or inferences regarding optimization decisions and the like. For example, learning engine 308 can employ a probabilistic-based or statistical-based approach in connection with modifying or updating data structures or data configurations pertinent to the mobile device 304, or drawing conclusions therefrom. The inferences can be based in part upon explicit training of classifier(s) (not shown) before employing the learning engine 308, or implicit training based at least upon manual input and the like. Data or policies used in optimizations can be collected from a specific database or from a community of databases (not depicted) of various types (e.g., obtained by data mining module 310), various applications and/or operating systems, for instance.
Learning engine 308 can also employ one of numerous methodologies for learning from data and then drawing inferences from the models so constructed (e.g., Hidden Markov Models (HMMs) and related prototypical dependency models, more general probabilistic graphical models, such as Bayesian networks, e.g., created by one or more structure searches using a Bayesian model score or approximation, linear classifiers, such as support vector machines (SVMs), non-linear classifiers, such as methods referred to as “neural network” methodologies, fuzzy logic methodologies, and other approaches that perform data fusion, etc.) in accordance with implementing various aspects described herein. As a non-limiting example, classifiers can be trained on a relationship between a user profile preference for a particular product or service identified in a DMC, and a retail entity's availability of such product or service (and, for instance, distance from a mobile device to the retail entity), or other examples described herein. As data is updated at transaction database 306, or additional data pertinent to mobile device 304, a DMC, a DMC supplier, or retail entity, etc., is identified, the classifiers can be retrained. For instance, when a DMC associated with a user profile/mobile device 304 is redeemed, data mining module 310 can update transaction database 308 with redemption information (e.g., ID of DMC redeemed, product/service, value applied to the transaction, etc.) and learning engine 308 can execute one or more classifiers to generate changes to inferences and results provided by the learning engine 308.
Methodologies employed by learning engine 308 can also include mechanisms for the capture of logical relationships such as theorem proverbs or more heuristic rule-based expert systems. Inferences derived from such learned or manually constructed models can be employed in optimization techniques, such as linear and non-linear programming, that seek to maximize some objective function. For example, manipulating data of user interest vector 604 to deconstruct such data and identify potential users associated therewith can be based on iterative interactions with the user input vector 604, common times at which particular subject matter activity occurs, common communications at which particular subject matter activity occurs, common data packets wherein particular subject matter activity occurs, and/or like factors suitable for data configuration optimization.
Accordingly, learning engine 308 serves as an interface to the profile information stored in the transaction database 306. Therefore, system 300 can continually determine and store information pertinent to a mobile device 304, a vendor or retailer of a DMC, and so on, to generate a current and accurate value for dynamic aspects of the DMC. Thus, according to some aspects, system 300 provides for expedient valuation of a DMC upon redemption.
System 400 can include a media integration module 406. Media integration module 406 can receive and store various media information (408), electronic files (408), and/or audio-visual programs, etc. Such media (408) can include advertisements, product/service descriptions, manufacturer, retailer or distributor information, or third party information, or a combination thereof or of like information. The information (408) can be pertinent to a DMC distributed to mobile device 404, tangentially related (e.g., pertaining to other products of a common manufacturer), or unrelated to the DMC 410 (e.g., provided by an unrelated sponsor).
In addition to the foregoing, media integration module 406 can integrate media 408 within a DMC 410 or bundle media with a DMC 410 that is associated with the mobile device 404. Further, the media integration module 406 can package the DMC (or, e.g., an indication of the DMC) and media into a mobile device application and transmit the application to mobile device 404. Accordingly, by accessing the DMC 410 at a user interface 412 of mobile device 404, information pertaining to the synchronized media (408) is presented or displayed. A user can then select the media 408 to view it on the mobile device 404. In some aspects, the media 408 can be automatically played on the mobile device 404 when the DMC is received, or selected, or the like.
According to at least one aspect, a particular mobile application can be utilized to package the media/DMC that provides various multidimensional functions to highlight feature richness of the DMC/media. For instance, the mobile device application can be configured to utilize an audio, visual, olfactory, gustatory (e.g., pertaining to the sense of taste) or tactile function of a target mobile device (404). Such function can be obtained from user profile information stored at the mobile device 404, a DMC application located on the mobile device, on a network transaction database (not depicted, but see
As one example of the foregoing, a mobile device 404 could comprise tactile sensory features (e.g., vibration device, tactile display) that provide tactual feedback. The tactile sensory features can be employed by a product-related application to convey tactual information to a user of the mobile device. For example, audio/video media 408 of a race car engine could be coupled with a tactile application that employs a vibration device or tactile display to give a user a representative ‘feel’ of the vibration caused by a powerful engine motor. A DMC associated with a high performance motor oil product could be bundled with the audio/visual/tactile media 408, which can serve as an advertisement of the product. It should be appreciated that the foregoing is simply one example of a sensory features (e.g., graphical display, audio controller and speakers, vibration device, tactile display, scent replicator) of a mobile device 404 that can be utilized to augment an aspect of a product or service associated with a DMC. Other examples of device sensory features (e.g., audio, visual, tactile, olfactory, gustatory, etc.) known in the art, or made known to one of skill in the art by way of the context provided herein, are included in the subject disclosure. Some examples can include employing olfactory features (e.g., pre-loaded perfume scents coupled with a scent spray or ejector) to augment media (408) pertaining to perfumes or other scented products (e.g., soaps, air fresheners). Another example can comprise media (408) employing combinations of sensory features, such as an audio/video presentation of a major league baseball World Series, coupled with device vibration coinciding with a roaring crowd and scents of buttered popcorn ‘in the air’.
According to further aspects, media integration system 406 and/or coupon system 402 can affect a variable characteristic of the DMC 410 (e.g., redeemable value) based on the media 408. According to one particular example, if the media 408 is played by mobile device 404, a redeemable value of DMC 410 can be adjusted (e.g., increased). To this purpose, DMC 410 can record information pertinent to media 408. Specifically, DMC 410 can set a flag, or like indicator, once the media 408 is presented on the user interface 412 of the mobile device. The flag or indicator can then be submitted to coupon system 402, and the coupon system 402 can adjust a dynamic value of the DMC 410 accordingly. Thus, upon redeeming the DMC 410, additional value can be provided in conjunction with a transaction. Accordingly, a user of the mobile device 404 is presented incentive to view the media (e.g., advertisement) and a sponsor of the media is presented some indication that the media 408 was viewed.
In another aspect, the media can be an advertisement of a third party (e.g., that is not a sponsor, recipient, or distributor of the DMC). If the media is played at mobile device 404, DMC 410 can update coupon system 402 as described above. Coupon system 402 can then modify, initiate or complete a transaction with the third party based on playing the advertisement at the mobile device. Thus, system 400 can provide an additional revenue stream related to distributing and/or playing third party advertisements in conjunction with distribution of a DMC and/or advertisement media to target device.
According to still further aspects, coupon system 402 can request input in response to playing media at the user interface 412. For instance, questions pertinent to played media can be presented at the user interface 412 during or after playing the media. A user can answer the questions via the user interface 412 and transmit the answers to coupon system 402 through the mobile device 404. If answers are received, it is more likely that the user viewed the media 408 and, based on the feedback or answers, the user's opinion and/or understanding of the media 408 can be ascertained. In addition, a variable characteristic of the DMC 410 can be adjusted based on the questions/feedback in response to the media 408. As an example, a redeemable value, or an additional value or benefit can be provided based on the nature of the response to the media 408. As described, system 400 provides a mechanism to integrate advertisements and other media of third party entities with a DMC, to provide benefit for consumers as well as sponsors of the media.
As described herein (e.g., see
In one aspect, representation of a DMC can include multiple dimensions, such as multiple slides or layers (506, 508, 510). Each dimension or layer (506, 508, 510) can segregate information pertinent to the DMC. For instance, a first layer 506 can provide present information pertaining to a DMC. A second layer 508 can provide prior information pertaining to previous DMCs received at the mobile device 504, for instance, that are similar to the current DMC (e.g., common product, manufacturer, retailer, or the like). In addition, a third layer 510 can provide social networking information pertaining to a DMC.
As a particular example of social networking information, the third layer 510 can indicate a user preference (e.g., contained in a user profile, generated from prior transactions, etc.) associated with the DMC. In addition, the third layer 510 can tabulate preferences contained by associates of a user of mobile device 502. For instance, opinions or usage history of other individuals specified in a friends list can be shared between mobile devices (502) and stored on memory allocated to the DMC. Such information can also be obtained from social networking websites accessed by the mobile device 502. Information from identified trendsetters, statistical information pertaining to groups of individuals, and the like can be collected, stored, and displayed at the third layer 510. Thus, a user can access others' opinions and perceptions of the DMC, such as whether it provides a good value, how they liked an associated product/service, how they maximized value associated with the DMC, opinions of advertisements or other media coupled with the DMC (e.g., see
In some aspects, a layer (506, 508, 510) can include terms and conditions, redemption information, additional manufacturer/retailer/distributor product or business information, or the like. Such information can be organized in various suitable ways on the user interface 504 of a mobile device 502. It should be appreciated that various suitable business and social network information pertaining to entities associated with a DMC, as described herein or known to one of skill in the art, or pertaining to a device (502) or user can be contained on various DMC display layers (506, 508, 510).
According to some aspects, present information associated with a DMC can be displayed on at least one layer 506. The present information can include data describing the DMC, as well as associated entities, value, incentives, and redemption information pertaining to the DMC. For instance, a first portion 512 can provide validity information, including expiration date, status, and so on. A second portion 514 can display frequent-coupon user points associated with the DMC. For instance, if a user has redeemed one or more DMCs of a particular sponsor or vendor in the past, the points can provide an indication of how many DMCs have been redeemed, and provide additional value in conjunction with future redemptions.
In addition to the foregoing, present information can also include brand information displayed in another portion 516 of the first layer 506. Brand information can identify a product, provide information pertinent to the product or a supplier, and so on. Further, an additional portion 518 of the first layer 506 can provide a concurrent value of the DMC. The concurrent value can be a percent discount, flat discount, purchase-related discount (e.g., buy one get a second half price), added benefit (e.g., free customer service, technical support, etc.), or a combination thereof, as described herein or known to one of skill in the art. In addition, the concurrent value can be based on concurrent circumstances associated with the mobile device (e.g., location), independent criteria (e.g., time of day), relative criteria (e.g., number of related DMCs redeemed by other devices 502), retailer stock, and so on. Further, according to some aspects, the value (518) can be updated in response to a user input at the user interface 504. The value (518) can be modified, if appropriate, based on a state of circumstances pertinent to the value at a time of the input. Such circumstances and modification can be conducted at the mobile device 502, at a network server (not depicted), or a combination of both.
Additional information can also be displayed at a present information layer 506. For instance, one portion 520 can provide information pertinent to added incentives, such as media or advertisements included with the DMC. Moreover, another portion 522 can indicate an ID of the DMC. The ID can be displayed as a bar code, a string of digits, or the like. Display of the ID can also be utilized in conjunction with redemption of the DMC (e.g., a bar code displayed at the user interface 504 can be scanned by an electronic scanner at a point of service device, such as a cash register).
In one or more other aspects of the subject disclosure, multi-dimensional layers (506, 508, 510) can comprise different media applications pertinent to a DMC or advertisement. For instance, a first layer 506 can comprise a graphical depiction of a product associated with a DMC (e.g., a picture of a pizza with a manufacturer's logo or trademark). A second layer 508 can comprise an audio/visual application that plays an animated advertisement on the user interface 504. A third layer 510 can employ a particular function/feature of the mobile device (e.g., an olfactory feature comprising a scent loaded onto the mobile device 502) to augment an aspect of the product (e.g., the application can cause the mobile device 502 to release a pizza scent while the audio/visual application shows a hot freshly baked pizza). Thus, the multi-dimensionality of the user interface layers is not limited to segregating information, but can be employed to display various suitable multi-dimensional media features of the DMC at the user interface of the device. It should be appreciated that various information can be included within a user interface display of a mobile coupons, and
Mobile device 604 can include a valuation engine 606 that extracts a factor relevant to establishing a value for the DMC from mobile device 604. The factor can be related to any suitable information pertinent to such device 604. For instance, the factor can be related to location of the device 604 (e.g., determined by GPS, base station triangulation or like techniques, peer-to-peer ranging, and so on), identity the device 604 or a user of the device 604, a user profile contained at the device 604, prior DMC transaction history, DMCs stored at the mobile device 604, advertisements associated with DMCs, special manufacturer incentives, or a combination of these or like factors. Valuation engine 606 can access various software, applications, and modules of the mobile device 604 to collect data pertinent to the factor(s) to facilitate establishing a value of a DMC based on such factor(s).
Data collected by valuation engine 606 is included within a data file 610 and provided to the valuation module 602 as data 608. As described above, valuation module 602 can analyze information in the data file 610 and generate a value 612 for a DMC. A relationship between data 608 and value 612 can be based on one or more algorithms or rules provided by a sponsor of the DMC. Accordingly, terms, conditions and other limitations of the sponsor can be incorporated into the value (612) for the DMC. Valuation module 602 returns the value 612 to the mobile device 604, which can associate the value 612 with a DMC.
Exchange of data 608 for value 612 can be conducted at predetermined points in time (e.g., periodically, based on device location or change in location, etc.), or based on user request. For instance, a user can press a ‘value update’ button, or the like, associated with a graphical display of a DMC at the mobile device 604. Such an input can initiate data collection by valuation engine 606, as described above, and submission of the data 608 to valuation module 602. In some aspects, exchange of data 608 for value 612 can be conducted at issuance of the DMC, at redemption of the DMC, or other suitable circumstances.
Mobile handset 702 includes at least one antenna 706 (e.g., a transmission receiver or group of such receivers comprising an input interface) that receives a signal (e.g., pertaining to voice call, data transfer, DMC value, and so on) and a receiver 708, which performs typical actions (e.g., filters, amplifies, down-converts, etc.) on the received signal. Specifically, antenna 706 can obtain a DMC from the coupon system 704 over a wireless link between such system 704 and the mobile device 702. Antenna 706 can also be involved in data exchange with coupon system 704 related to determining a value or other variable coupon characteristic of the DMC, determining a location or distance between the mobile handset 702 and coupon system 704, or the like. For instance, a valuation engine 716 can collect data pertinent to dynamic circumstances associated with the mobile device 702 (e.g., location, DMCs stored, prior transaction history, etc.). The information can be based on a query for information provided by coupon system 704, based on instructions stored at memory 714, or dynamically established at least in part by the coupon system 704 and mobile device 702, or a combination thereof.
Antenna 706 and receiver 708 can also be coupled with a demodulator 710 that can demodulate received symbols and provide them to a processor 712 for evaluation. Processor 712 can analyze information received by antenna 706 or a user input interface 720 of the mobile device 702, and/or generate information for transmission by a transmitter 726. Additionally, processor 712 can control and/or reference one or more components (706, 708, 710, 714, 716, 718, 720, 722, 724, 726, 728) of the mobile handset 702. Additionally, processor 712 can execute one or more modules, applications, engines, or the like (716, 718, 722, 724) that comprise information or controls pertinent to determining variable coupon characteristics of a DMC, factors for evaluating such characteristics, displaying such information at a user interface 720, or the like. Alternatively, or in addition, such modules (716, 718, 722, 724) can comprise information or controls pertaining to receiving and/or redeeming a DMC, as described herein.
Mobile handset 702 can additionally include memory 714 that is operatively coupled to processor 712. Memory 714 can store data to be transmitted, received, and the like. Such data can be pertinent to determining/verifying a variable coupon characteristic of a DMC. Alternatively, or in addition, the data can be pertinent to playing a media file associated with a DMC at a user interface 720 of mobile handset 702. In at least one aspect, memory 714 can store a DMC received at the mobile handset 702, as well as one or more factors, rules, etc., for determining and/or updating an initial parameter of a variable DMC characteristic.
Memory 714 can also be coupled with valuation engine 716 that can extract data from the mobile handset 702 in conjunction with determining a value of a DMC. According to some aspects, the valuation engine 716 can calculate a value (or, e.g., a state or parameter of another variable coupon characteristic) of the DMC based at least in part on the collected data. According to another aspect, the valuation engine 716 can send the collected data (e.g., via processor 712, modulator 726, and transmitter 728) to the coupon system 704 to calculate the value (or, e.g., other variable characteristic).
According to additional aspects, data collected by valuation engine 716 can include time, location of the mobile device 702, a user input provided at the mobile device 702, location of a vendor or retailer associated with a DMC, or a combination of these or like data. According to one or more other aspects, the valuation engine 716 can obtain an adjustment to a default or prior determined DMC characteristic or value based at least in part on additional data pertinent to such value. According to still other aspects, valuation engine 716 can freeze the value of the DMC based at least in part on the collected data, or a user input, or based on redemption of the DMC. According to still other aspects, valuation engine 716 can enable the value/characteristic to be re-evaluated by the mobile device 716 as data pertinent to determining such value/characteristic changes.
Memory 716 can also be coupled to a playback module 718 that can present information pertinent to the DMC at the mobile device 702. As an example, such information can include product description, supplier information, manufacturer information, retailer information, vendor information, redemption instructions, expiration information, DMC identification information, or value-added incentives (e.g., advertisements) associated with the DMC (e.g., see
Memory 716 is also connected to an update module 722 that obtains a dynamic update to an algorithm that changes a manner in which the value for the DMC is generated. For instance, a DMC supplier can provide the dynamic update as an Internet download. Alternatively, the update can be pushed to the mobile device 702 by a mobile network (not depicted), or pulled from a mobile network (not depicted).
In addition to the foregoing, memory 716 can also be coupled with a redemption module 724. Redemption module 724 can collect information pertinent to the DMC, and concurrent characteristics of the DMC established by mobile device 702 and/or coupon system 704, and present such information to a point of sale device (e.g., an electronic cash register, etc.) in conjunction with a commercial transaction. The redemption module 724 can also verify that a value of the DMC is properly applied to the commercial transaction. In addition, redemption module 724 can forward results of the transaction to coupon system 704 (or, e.g., a clearinghouse) for mediation and billing (e.g., as a verification of similar results provided by the point of sale device). The redemption module 724 can facilitate submitting a DMC to a point of sale device, for instance, in conjunction with redeeming the DMC in a transaction. As non-limiting examples, the redemption module 724 can display an ID of the DMC on a device (e.g., to be read by a retail store operator, or provided by such operator by a user of mobile device 702), display a bar code or other indicia representing an ID of the DMC that can be scanned at a point of sale device, form a wired and/or wireless link to the point of sale device and submit the DMC ID to such device, couple directly with a back-end network entity (e.g., a network clearinghouse module) via a mobile network, or a combination thereof or of the like.
It should be appreciated that redemption of a dynamic mobile coupon in conjunction with a transaction can be implemented in other ways, in addition to those recited above. For instance, where a DMC is stored in memory 716, the DMC can be accessed from memory 716 based on a UI input associated with redemption of the DMC and output to a user and/or a POS device. Where the DMC is stored at a network server (e.g., short message server, text message server, Internet data server, Intranet data server, and so forth), the DMC, or indicia identifying the DMC can be obtained from such server based on the UI input, and output to the user and/or POS device. It should also be appreciated that the DMC and/or indicia identifying the DMC can be input into the POS device in various ways disclosed herein and/or known in the art (e.g., manually by reading the identifying information from a screen and providing such information to a clerk who enters it into the POS device, by optically scanning indicia identifying the DMC displayed on a UI of the device 702 into the POS device, through wired and/or wireless data exchange between the mobile device 702 and POS device, etc.). Furthermore, the indicia identifying the DMC can include a bar code or other graphical indicia, quantitative indicia (e.g., unique or semi-unique number), qualitative indicia (e.g., manufacturer description, product description, retailer description, and an identifier, or a combination thereof), etc. Furthermore, the DMC can be identified based on association with a user account (e.g., maintained on mobile device 702). Information identifying the user account (e.g., a phone number of the mobile device 702) can be entered into the POS device as described herein, and DMCs associated with the user account and pertinent to a transaction facilitated by the POS device (e.g., where a product/service associated with the DMC is involved in the transaction) can be accessed by such device (e.g., by manual input, direct communication with the mobile device 702, access to a network server). In addition to the foregoing, user loyalty cards (e.g., commercial loyalty cards provided by an entity associated with the POS device, such as a retail store, online store, or the like) associated with the user account can be accessed and applied to the transaction, as provided by rules associated with such user loyalty cards. In at least one aspect of the subject disclosure, the user account can be accessed by providing user loyalty card information or payment card information coupled with the mobile device 702 or a user account associated with the mobile device (e.g., through near field communication [NFC] or Felica phones where payment ID is stored on mobile device 702 and transferred to the POS device, through a one-time payment code accessed by the mobile device 702 from a network server, such as short message server or the like, and provided to the POS device, where the network server receives subsequent DMC redemption requests coupled with the payment code and can identify the user account, DMC(s), and/or payment/loyalty cards associated with such payment code to facilitate verifying and/or implementing a transaction). In at least one aspect of the subject disclosure, a personal computer or other computing device (e.g., laptop, PDA, etc.) can be substituted for mobile device 702 and utilize wired and/or wireless communication with remote devices to implement aspects of the disclosure provided herein.
Mobile handset 702 still further comprises a modulator 724, and a transmitter 726 that transmits generated signals (e.g., by processor 712 and modulator 724) to, for instance, coupon system 704, a base station, an access point, another access terminal, a remote agent, a point of sale device, etc. Although depicted as being separate from the processor 712, it is to be appreciated that valuation engine 716 can be part of processor 712 or a number of processors (not shown).
The aforementioned systems have been described with respect to interaction between several components, modules, and/or electronic interface functions. It should be appreciated that such systems and components/modules/functions can include those components or sub-components specified therein, some of the specified components or sub-components, and/or additional components. For example, a system could include coupon system 102, mobile device 104, transaction database 306, transaction module 308, and valuation module 602, or a different combination of these and other components. Sub-components could also be implemented as components communicatively coupled to other components rather than included within parent components. Additionally, it should be noted that one or more components could be combined into a single component providing aggregate functionality. For instance, data mining module 310 can include transaction database 306, or vice versa, to facilitate collecting and storing data pertinent to various user or supplier profiles or histories by way of a single component. The components may also interact with one or more other components not specifically described herein but known by those of skill in the art.
Furthermore, various portions of the disclosed systems can include or consist of artificial intelligence or knowledge or rule based components, sub-components, processes, means, methodologies, or mechanisms (e.g., support vector machines, neural networks, expert systems, Bayesian belief networks, fuzzy logic, data fusion engines, classifiers . . . ). Such components, inter alia, and in addition to that already described herein, can automate certain mechanisms or processes performed thereby to make portions of the systems more adaptive as well as efficient and intelligent.
It is to be understood that the aspects described herein can be implemented in hardware, software, firmware, middleware, microcode, or any combination thereof. For a hardware implementation, the processing units can be implemented within one or more ASICs, DSPs, digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.
When the aspects are implemented in software, firmware, middleware or microcode, program code or code segments, they can be stored in a machine-readable medium, such as a storage component. A code segment can represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment can be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. can be passed, forwarded, or transmitted using any suitable means including memory sharing, message passing, token passing, network transmission, etc.
For a software implementation, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The software codes can be stored in memory units and executed by processors. The memory unit can be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.
Referring to
At 804, method 800 can associate a DMC with the mobile device, where the DMC has at least one variable coupon characteristic. The variable coupon characteristic can vary as a function of one or more determinable circumstances pertinent to the mobile device. Such circumstances can include location of the mobile device, distance to a predetermined entity (e.g., a retail store), time, user profile information, vendor profile information, DMC profile information, retailer profile information, previous DMCs distributed to/utilized by the mobile device, DMCs stored at the mobile device, prior redemption of DMCs associated with the mobile device, and so on. Information pertaining to the determinable circumstances can be obtained from the mobile device, an entity communicatively coupled with the mobile device (e.g., a base station, wireless transmitter), or a server of a network entity (e.g., a mobile network server maintained by a service provider associated with the mobile device). The variable characteristic can include a redeemable value, applicable transactions or products/services associated with such transactions, time of redemption, location of redemption (e.g., a predetermined store or online website), additional media provided with the DMC, various feature richness associated with the DMC or media, or a combination of these or like characteristics.
At 806, method 800 can establish an initial parameter of the variable coupon characteristic based at least in part on at least one determinable circumstance pertinent to the mobile device. Such circumstances and their applicability to the variable coupon characteristic and/or initial parameter can be established by rules of a sponsor of the DMC. According to some aspects, establishing the initial parameter can render the value constant, independent of additional determinable characteristics described above or changes in such characteristics. According to other aspects, establishing the initial parameter can render the value constant until a predetermined circumstance occurs, in which case the value can change again (e.g., a cancellation can occur rendering the value zero). Such predetermined circumstance can comprise associating the DMC with a target mobile device, receiving a value acceptance input from the target mobile device, identifying a threshold change in a determinable circumstance utilized to establish the initial parameter (or, e.g., a related determinable circumstance described above), and/or receiving notice that the DMC is presented for redemption, or a combination of these or like factors.
At 808, method 800 can communicatively couple with a clearinghouse server to redeem the DMC in conjunction with a transaction. Further, the clearinghouse can facilitate modifying a default characteristic of the transaction based on a state of the variable coupon characteristic (e.g., a current redeemable value). In general, the clearinghouse can provide billing, mediation, authorization, and/or security functions for the transaction. For instance, the clearinghouse can analyze information pertinent to the transaction and DMC and determine whether the DMC and transaction are appropriate. Further, the clearinghouse can update a manufacturer as to redemption status of the DMC. According to other aspects, the clearinghouse can cancel the DMC upon redemption (or, e.g., upon expiration of an active data) to mitigate unauthorized additional redemption.
According to further aspects, the clearinghouse can act as an intermediary between a sponsor of the DMC and a retail entity that redeems the DMC. Specifically, the clearinghouse can relay transaction information to the sponsor and can provide indemnification/reimbursement to the retail entity or other sponsor of the transaction a modified default characteristic of the transaction (e.g., resulting from application of the DMC to the transaction). Accordingly, methodology 800 provides for targeting a DMC based on individual characteristics of a mobile device, and providing flexible characteristics, such as redeemable value, based on predetermined sponsor criteria.
At 906, method 900 can identify a suitable device in accordance with the list of rules received at reference number 904. At 908, method 900 can generate a DMC application, playable at the identified device, according to the list of rules. At 910, method 900 determines whether an advertisement is to be coupled with the DMC. Such determination can be based on the identified device, on the rules provided by the manufacturer/sponsor, or like circumstances. If an advertisement is to be coupled with the DMC, method 900 proceeds to reference number 912, if not, method 900 can proceed to reference number 918.
At 912, method 900 can obtain an advertisement to be coupled with the DMC. The advertisement can include various information pertaining to the DMC, including sponsor information, redemption information, product or service information and/or related products or services (e.g., offered by the sponsor or a retail entity). According to some aspects, a third party can provide the advertisement instead of or in addition to the sponsor, retailer, etc. At 914, method 900 can generate an advertisement media file that can be played on a user interface of the device identified at reference number 906. At 916, the media file is combined or bundled with the DMC (or, e.g., an indication of the DMC), packaged into a suitable mobile device application playable at the identified mobile device, and transmitted to the identified device.
In some aspects, the mobile device application can be selected to utilize an audio, visual, olfactory, or tactile function of the target mobile device. Further, the application can be configured to employ such function of the identified mobile device to augment a product, service or other aspect of the DMC or advertisement. It should be appreciated that where the advertisement is of a third party (e.g., that is not a sponsor, recipient or distributor of the DMC), an indication that the third party advertisement is played at the mobile device can form the basis for modifying, initiating or completing a transaction with the third party. Accordingly, bundling advertisements of third parties can provide an additional revenue stream in conjunction with distributing a DMC.
At 918, method 900 can determine whether a redeemable value (or, e.g., other suitable variable coupon characteristic of the DMC) is determined at the identified mobile device or at a server device. If the redeemable value is determined at the server device, method 900 can proceed to 924. If, on the other hand, the redeemable value is determined at the mobile device, method 900 can proceed to 920.
At 920, valuation factors pertinent to determining the redeemable value (or other suitable variable coupon characteristic of the DMC) are obtained. Such factors can include, for instance, location of the mobile device, time of day, user, sponsor or retailer profile information, whether media, advertisements or other special incentives were viewed at a mobile device, as described herein, or a combination of these or like factors. At 922, method 900 can combine the factors and valuation data with the DMC for distribution to the identified mobile device.
At 924, method 900 can identify valuation factors pertinent to determining the variable coupon characteristic of the DMC (e.g., if not done at reference number 920). At 926, the DMC can be transmitted to the identified mobile device. Confirmation of receipt of the DMC can also be obtained and stored for reference. At 928, data pertinent to the factors determining the variable coupon characteristic can be obtained. Such data can be obtained from the mobile device, determined from data exchange with such device, or data exchange with an external entity (e.g., base station of a mobile network). At 930, the value of the DMC, or other variable coupon characteristic, can be fixed based on the data obtained at reference number 928. Fixing the value can be permanent, or can be dependent upon occurrence of some predetermined circumstance (e.g., obtaining additional data pertinent to the mobile device, redeeming the DMC, etc.).
At 932, a determination is made as to whether the DMC has been submitted for redemption. If no redemption has been determined, method 900 can proceed to 934 where additional data pertinent to the factor(s) establishing the dynamic value can be obtained and/or monitored. Method 900 can then proceed back to 930 to determine whether the value or variable coupon characteristic should again be fixed based on any additional data obtained at reference number 934. If, at reference number 932, the DMC has been submitted for redemption, method 900 can proceed to 936 where the DMC is identified and cross-referenced with rules for redemption obtained at reference number 904.
At 938, method 900 can identify a value (or, e.g., other suitable variable coupon characteristic) of the DMC. The value can be previously determined (e.g., at reference number 930) or updated based on information obtained in conjunction with redemption. At 940, method 900 can check security measures associated with the DMC. Such measures can include checking proper encryption or security information associated with the DMC, determining whether the DMC has been previously redeemed, determining whether a redeeming entity is authorized to redeem the DMC, and so on. Based on such information, method 900 can apply or authorize application of the DMC to a transaction, and modify a default characteristic of the transaction based on the value (or, e.g., other suitable variable coupon characteristic).
At 942, method 900 can submit details of the redemption and an associated transaction to a clearinghouse for mediation and billing. AT 944, method 900 can receive information from the clearinghouse. If the information approves the transaction, redemption of the DMC can be authorized. According to further aspects, indemnification/reimbursement of a sponsor of the transaction provided by the clearinghouse can be forwarded to such sponsor (e.g., an entity honoring the DMC). At reference number 946, method 900 can end.
As described, method 900 provides a flexible mechanism to distribute a DMC in a mobile environment based on criteria established by a sponsor of the DMC. In such a manner, the DMC can be targeted toward a particular mobile device, rather than limited to a general mass mailing. Further, the DMC can be associated with rich and dynamic media and advertisements presented at a graphical display of the mobile device. In addition, characteristics of the DMC can be dynamically adjusted, including a redemption value, to facilitate increasing or decreasing consumer-purchasing incentive. Accordingly, many benefits are provided by distribution of DMCs in a mobile environment as described by the aspects presented herein.
At 1004, method 1000 can receive the DMC or an indication of the DMC, where the DMC has at least one variable coupon characteristic. Receiving the DMC can be based in part on, for instance, proper response to a query at reference number 1002. The DMC can include a stand-alone file or application that can operate on a mobile device. The stand-alone file can be displayed on a user interface of the device to provide information to a user and present feature richness and/or multi-dimensional aspects of the DMC. In addition, the stand-alone file can obtain and or utilize information to determine a value of the DMC. According to further aspects, the stand-alone file can facilitate redemption of the DMC at a retail entity. For instance, the file can obtain an identity of the DMC, and pertinent security, applicability, redemption value, and like information associated with redeeming the DMC. Accordingly, dynamic functions of the DMC can be performed, at least in part, at the mobile device receiving the DMC.
At 1006, a factor can be obtained that is pertinent to establishing an initial parameter for the variable coupon characteristic. The factor can include any suitable information pertaining to the mobile device, a product, service, manufacturer/sponsor, distributor or retailer associated with the DMC, or the like, as described herein. At 1008, data associated with the factor can be collected to facilitate establishing the initial parameter of the variable coupon characteristic (e.g., redemption value of the DMC). In one aspect, the data can be analyzed and the parameter determined at the mobile device. In other aspects, the data can be forwarded to a network device (e.g., Internet server, component of a mobile operator's network) for determination of the initial parameter. The initial parameter can be fixed to mitigate change to the variable coupon characteristic based on input at the mobile device, or can be un-fixed, and thus re-evaluated to update the initial parameter. Such re-evaluation can be based on association of the DMC with the mobile device, a threshold change in the circumstance(s) utilized to determine the initial parameter or related circumstances, redemption of the DMC or an input at the mobile device (e.g., an acceptance of the value), or a combination thereof or of the like. As described, method 1000 provides for receiving and interacting with a DMC to determine variable coupon characteristics of the DMC. The variable coupon characteristics can be based on information at a receiving device, and thus can be at least partially independent of an issuing or redeeming device, providing autonomy and flexibility for the DMC.
At 1106, data pertinent to the factor identified at reference number 1104 is collected. At 1108, a determination is made as to whether the value of the DMC is calculated locally at a device or at a remote device. If the determination is made locally, method 1100 can proceed to 1112 where the value of the DMC is calculated based at least in part on the data collected at reference number 1106. After calculating the value, method 1100 can proceed to 1114.
If, at reference number 1108, the value is determined to be calculated at a remote device, method 1100 proceeds to 1110 and transmits collected data to the remote device (e.g., an Internet server) for calculation. The calculated value is received from the remote device, and method 1100 can proceed to 1114. At 1114, method 1100 can determine a value of the DMC based on remote device feedback or local calculations. At 1116, additional data pertaining to the factor is optionally monitored and/or collected. At 1118, the value is optionally updated based on additional data determined at reference number 1116.
At 1120, media associated with the DMC can be played at a recipient device. The media can describe transactions or products applicable to the DMC, retail locations participating in such transactions, redemption limitations or conditions, methods to update and/or increase the value of the DMC, and so on. At 1122, method 1100 can optionally play advertisements or incentive media included with the DMC, and update the value of the DMC as specified by the DMC. At 1124, method 1100 can submit the DMC for redemption in conjunction with a predetermined transaction at a participating retail entity. As described, method 1100 provides a process for receiving and determining value associated with a DMC based on criteria pertinent to a recipient mobile device. Accordingly, method 1100 depicts a flexible process that enables utilization and redemption of a DMC with minimal interaction with remote server devices.
In addition to the foregoing, system 1200 further includes a module 1306 for establishing an initial parameter of the variable coupon characteristic. The initial parameter can be established at least in part on one or more factors associated with a recipient mobile device, as described herein. The mobile device can collect data pertinent to the factor(s) and provide such data to the third module 1306 for further analysis. Specifically, such data can be applied to one or more algorithms or functions provided to establish the initial parameter (e.g., an initial redeemable value) of the DMC based on the one or more factors. In accordance with some aspects of the subject disclosure, system 1200 can optionally include a module 1208 for coupling with a clearinghouse. Such a clearinghouse can provide mediation and billing functions in conjunction with redeeming the DMC.
As an example of the foregoing, optional module 1208 can provide transaction, security, authorization, or ID information, or the like, associated with the DMC, to the clearinghouse upon redemption of the DMC. If the transaction complies with applicable specifications (e.g., established by a sponsor of the DMC), the clearinghouse will provide indemnification for a retail entity honoring the DMC in conjunction with a commercial transaction. Accordingly, a user of a recipient device can utilize the DMC similar to an electronic credit card transaction in a mobile environment. Although various differences can remain, such as presentation of the DMC and associated information at the recipient device, at least in some aspects redemption, authorization, and/or indemnification of value by the clearinghouse can be performed electronically, without involving the device user.
Referring now to
System 1300 includes a module 1304 for obtaining a DMC or an indication of the DMC (e.g., that identifies the DMC, or a product, service, or source of such product/service, rules for redemption, rules for determining a dynamic characteristic such as value, and so on), wherein the DMC includes at least one variable coupon characteristic. The DMC can comprise, for instance, a file or application, including applicable rules, terms and conditions for redemption, valuation formulae, associated advertisements and media, and the like as described herein. The DMC can be displayed at a user interface of the recipient device to convey applicable information. System 1300 can additionally include a module 1306 for obtaining a factor pertinent to establishing an initial parameter of the variable coupon characteristic. Such factor can be extracted from the DMC, or obtained from an entity that distributes the DMC to the recipient device. In addition to the foregoing, system 1300 can include a module 1308 for collecting data pertinent to establishing the value of the DMC. Accordingly, value can be established according to certain rules and based on certain circumstances of the recipient device. System 1300 can facilitate determination of the value at such device, reducing need for interactions with remote devices. According to some aspects, data collected by the module 1308 can be provided to a remote device for analysis, and such remote device can then distribute the value to the optional module 1302.
What has been described above includes examples of one or more aspects. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the aforementioned aspects, but one of ordinary skill in the art may recognize that many further combinations and permutations of various aspects are possible. Accordingly, the described aspects are intended to embrace all such alterations, modifications, and variations that fall within the scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.
The present Application for Patent claims priority to Provisional Application No. 60/945,098 entitled DYNAMIC COUPON SYSTEM filed Jun. 20, 2007, and assigned to the assignee hereof and hereby expressly incorporated by reference herein. The present Application for Patent is related to the co-pending U.S. patent application Ser. No. 12/124,824, entitled MOBILE COUPONS UTILIZING PEER TO PEER RANGING, filed May 21, 2008, assigned to the assignee hereof and expressly incorporated by reference herein, which in turn claimed priority to Provisional Application No. 60/945,120 entitled “METHOD AND APPARATUS FOR DELIVERING COUPONS BASED ON RANGING” filed Jun. 20, 2007; and U.S. patent application Ser. No. 12/142,597, entitled MANAGEMENT OF DYNAMIC ELECTRONIC COUPONS, filed concurrently herewith, assigned to the assignee hereof and expressly incorporated by reference herein, which in turn claimed priority to Provisional Application No. 60/945,100 entitled “COUPON WALLET SYSTEM” filed Jun. 20, 2007.
Number | Name | Date | Kind |
---|---|---|---|
4006477 | Yost, Jr. et al. | Feb 1977 | A |
5382957 | Blume | Jan 1995 | A |
5687169 | Fullerton | Nov 1997 | A |
5764696 | Barnes et al. | Jun 1998 | A |
5812081 | Fullerton | Sep 1998 | A |
5832035 | Fullerton | Nov 1998 | A |
5907427 | Scalora et al. | May 1999 | A |
5952956 | Fullerton | Sep 1999 | A |
5960031 | Fullerton et al. | Sep 1999 | A |
5963581 | Fullerton et al. | Oct 1999 | A |
5969663 | Fullerton et al. | Oct 1999 | A |
5970148 | Meier | Oct 1999 | A |
5995534 | Fullerton et al. | Nov 1999 | A |
6025795 | Hulderman et al. | Feb 2000 | A |
6031862 | Fullerton et al. | Feb 2000 | A |
6091374 | Barnes | Jul 2000 | A |
6111536 | Richards et al. | Aug 2000 | A |
6133876 | Fullerton et al. | Oct 2000 | A |
6177903 | Fullerton et al. | Jan 2001 | B1 |
6218979 | Barnes et al. | Apr 2001 | B1 |
6295019 | Richards et al. | Sep 2001 | B1 |
6297773 | Fullerton et al. | Oct 2001 | B1 |
6300903 | Richards et al. | Oct 2001 | B1 |
6304623 | Richards et al. | Oct 2001 | B1 |
6332193 | Glass et al. | Dec 2001 | B1 |
6351652 | Finn et al. | Feb 2002 | B1 |
6354946 | Finn | Mar 2002 | B1 |
6400307 | Fullerton et al. | Jun 2002 | B2 |
6400329 | Barnes | Jun 2002 | B1 |
6421389 | Jett et al. | Jul 2002 | B1 |
6430208 | Fullerton et al. | Aug 2002 | B1 |
6437756 | Schantz | Aug 2002 | B1 |
6462701 | Finn | Oct 2002 | B1 |
6466125 | Richards et al. | Oct 2002 | B1 |
6469628 | Richards et al. | Oct 2002 | B1 |
6483461 | Matheney et al. | Nov 2002 | B1 |
6489893 | Richards et al. | Dec 2002 | B1 |
6492904 | Richards | Dec 2002 | B2 |
6492906 | Richards et al. | Dec 2002 | B1 |
6501393 | Richards et al. | Dec 2002 | B1 |
6504483 | Richards et al. | Jan 2003 | B1 |
6512455 | Finn et al. | Jan 2003 | B2 |
6512488 | Schantz | Jan 2003 | B2 |
6519464 | Santhoff et al. | Feb 2003 | B1 |
6529568 | Richards et al. | Mar 2003 | B1 |
6538615 | Schantz | Mar 2003 | B1 |
6539213 | Richards et al. | Mar 2003 | B1 |
6549567 | Fullerton | Apr 2003 | B1 |
6552677 | Barnes et al. | Apr 2003 | B2 |
6556621 | Richards et al. | Apr 2003 | B1 |
6560463 | Santhoff | May 2003 | B1 |
6571089 | Richards et al. | May 2003 | B1 |
6573857 | Fullerton et al. | Jun 2003 | B2 |
6577691 | Richards et al. | Jun 2003 | B2 |
6585597 | Finn | Jul 2003 | B2 |
6593886 | Schantz | Jul 2003 | B2 |
6606051 | Fullerton et al. | Aug 2003 | B1 |
6611234 | Fullerton et al. | Aug 2003 | B2 |
6611811 | Deaton et al. | Aug 2003 | B1 |
6614384 | Hall et al. | Sep 2003 | B2 |
6614387 | Deadman | Sep 2003 | B1 |
6621462 | Barnes | Sep 2003 | B2 |
6636566 | Roberts et al. | Oct 2003 | B1 |
6636567 | Roberts et al. | Oct 2003 | B1 |
6636573 | Richards et al. | Oct 2003 | B2 |
6642903 | Schantz | Nov 2003 | B2 |
6650894 | Berstis et al. | Nov 2003 | B1 |
6661342 | Hall et al. | Dec 2003 | B2 |
6667724 | Barnes et al. | Dec 2003 | B2 |
6670909 | Kim | Dec 2003 | B2 |
6671310 | Richards et al. | Dec 2003 | B1 |
6674396 | Richards et al. | Jan 2004 | B2 |
6677796 | Brethour et al. | Jan 2004 | B2 |
6700538 | Richards | Mar 2004 | B1 |
6710736 | Fullerton et al. | Mar 2004 | B2 |
6717992 | Cowie et al. | Apr 2004 | B2 |
6748040 | Johnson et al. | Jun 2004 | B1 |
6750757 | Gabig, Jr. et al. | Jun 2004 | B1 |
6759948 | Grisham et al. | Jul 2004 | B2 |
6760387 | Langford et al. | Jul 2004 | B2 |
6762712 | Kim | Jul 2004 | B2 |
6763057 | Fullerton et al. | Jul 2004 | B1 |
6763282 | Glenn et al. | Jul 2004 | B2 |
6774764 | Ghosh et al. | Aug 2004 | B2 |
6774846 | Fullerton et al. | Aug 2004 | B2 |
6774859 | Schantz et al. | Aug 2004 | B2 |
6778603 | Fullerton et al. | Aug 2004 | B1 |
6781530 | Moore | Aug 2004 | B2 |
6782048 | Santhoff | Aug 2004 | B2 |
6788730 | Richards et al. | Sep 2004 | B1 |
6822604 | Hall et al. | Nov 2004 | B2 |
6823022 | Fullerton et al. | Nov 2004 | B1 |
6836223 | Moore | Dec 2004 | B2 |
6836226 | Moore | Dec 2004 | B2 |
6844816 | Melton et al. | Jan 2005 | B1 |
6845253 | Schantz | Jan 2005 | B1 |
6847675 | Fullerton et al. | Jan 2005 | B2 |
6862575 | Anttila et al. | Mar 2005 | B1 |
6879878 | Glenn et al. | Apr 2005 | B2 |
6882301 | Fullerton | Apr 2005 | B2 |
6895034 | Nunally et al. | May 2005 | B2 |
6895236 | Shuster | May 2005 | B2 |
6898434 | Pradhan et al. | May 2005 | B2 |
6900732 | Richards | May 2005 | B2 |
6906625 | Taylor et al. | Jun 2005 | B1 |
6907244 | Santhoff et al. | Jun 2005 | B2 |
6907270 | Blanz | Jun 2005 | B1 |
6912240 | Kumar et al. | Jun 2005 | B2 |
6914949 | Richards et al. | Jul 2005 | B2 |
6917280 | Griffith et al. | Jul 2005 | B1 |
6919838 | Santhoff | Jul 2005 | B2 |
6922166 | Richards et al. | Jul 2005 | B2 |
6922177 | Barnes et al. | Jul 2005 | B2 |
6925109 | Richards et al. | Aug 2005 | B2 |
6933882 | Fullerton | Aug 2005 | B2 |
6937639 | Pendergrass et al. | Aug 2005 | B2 |
6937663 | Jett et al. | Aug 2005 | B2 |
6937667 | Fullerton et al. | Aug 2005 | B1 |
6937674 | Santhoff et al. | Aug 2005 | B2 |
6947492 | Santhoff et al. | Sep 2005 | B2 |
6950485 | Richards et al. | Sep 2005 | B2 |
6954480 | Richards et al. | Oct 2005 | B2 |
6959031 | Haynes et al. | Oct 2005 | B2 |
6959032 | Richards et al. | Oct 2005 | B1 |
6961285 | Niemiec et al. | Nov 2005 | B2 |
6963727 | Shreve | Nov 2005 | B2 |
6980613 | Krivokapic | Dec 2005 | B2 |
6989751 | Richards | Jan 2006 | B2 |
7002473 | Glick et al. | Feb 2006 | B2 |
7003289 | Kolls | Feb 2006 | B1 |
7015793 | Gabig, Jr. et al. | Mar 2006 | B2 |
7020224 | Krivokapic | Mar 2006 | B2 |
7026983 | Spratt | Apr 2006 | B2 |
7027425 | Fullerton et al. | Apr 2006 | B1 |
7027483 | Santhoff et al. | Apr 2006 | B2 |
7027493 | Richards | Apr 2006 | B2 |
7030806 | Fullerton | Apr 2006 | B2 |
7042417 | Santhoff et al. | May 2006 | B2 |
7046187 | Fullerton et al. | May 2006 | B2 |
7046618 | Santhoff et al. | May 2006 | B2 |
7058414 | Rofheart et al. | Jun 2006 | B1 |
7069111 | Glenn et al. | Jun 2006 | B2 |
7075476 | Kim | Jul 2006 | B2 |
7079827 | Richards et al. | Jul 2006 | B2 |
7099367 | Richards et al. | Aug 2006 | B2 |
7099368 | Santhoff et al. | Aug 2006 | B2 |
7116266 | Vesel et al. | Oct 2006 | B1 |
7129886 | Hall et al. | Oct 2006 | B2 |
7132975 | Fullerton et al. | Nov 2006 | B2 |
7139647 | Larsen | Nov 2006 | B2 |
7145954 | Pendergrass et al. | Dec 2006 | B1 |
7148791 | Grisham et al. | Dec 2006 | B2 |
7149533 | Laird et al. | Dec 2006 | B2 |
7167525 | Santhoff et al. | Jan 2007 | B2 |
7170408 | Taylor et al. | Jan 2007 | B2 |
7178719 | Silverbrook et al. | Feb 2007 | B2 |
7184938 | Lansford et al. | Feb 2007 | B1 |
7190722 | Lakkis et al. | Mar 2007 | B2 |
7190729 | Siwiak | Mar 2007 | B2 |
7206334 | Siwiak | Apr 2007 | B2 |
7206559 | Meade et al. | Apr 2007 | B2 |
7209724 | Richards et al. | Apr 2007 | B2 |
7230980 | Langford et al. | Jun 2007 | B2 |
7239277 | Fullerton et al. | Jul 2007 | B2 |
7245900 | Lamb et al. | Jul 2007 | B1 |
RE39759 | Fullerton | Aug 2007 | E |
7256727 | Fullerton et al. | Aug 2007 | B2 |
7271779 | Hertel | Sep 2007 | B2 |
7277715 | Starr et al. | Oct 2007 | B2 |
7308356 | Melaku et al. | Dec 2007 | B2 |
7310532 | Knauerhase et al. | Dec 2007 | B2 |
7363494 | Brainard et al. | Apr 2008 | B2 |
7366509 | Akgun et al. | Apr 2008 | B2 |
7383984 | Silverbrook et al. | Jun 2008 | B2 |
7505443 | McNew et al. | Mar 2009 | B2 |
7554979 | Ikeda | Jun 2009 | B2 |
7581113 | Smith et al. | Aug 2009 | B2 |
7739157 | Bonner et al. | Jun 2010 | B2 |
7783532 | Hsu et al. | Aug 2010 | B2 |
7818762 | Liu et al. | Oct 2010 | B2 |
7870021 | Mankoff | Jan 2011 | B2 |
7870229 | Spector | Jan 2011 | B2 |
8332270 | Sprigg et al. | Dec 2012 | B2 |
8595070 | Barnes et al. | Nov 2013 | B1 |
20010014870 | Saito et al. | Aug 2001 | A1 |
20010042010 | Hassell | Nov 2001 | A1 |
20020002504 | Engel et al. | Jan 2002 | A1 |
20020004783 | Paltenghe et al. | Jan 2002 | A1 |
20020010627 | Lerat | Jan 2002 | A1 |
20020046084 | Steele et al. | Apr 2002 | A1 |
20020065713 | Awada et al. | May 2002 | A1 |
20020091569 | Kitaura et al. | Jul 2002 | A1 |
20020091571 | Thomas et al. | Jul 2002 | A1 |
20020107738 | Beach et al. | Aug 2002 | A1 |
20020111140 | Kim | Aug 2002 | A1 |
20020111907 | Ling | Aug 2002 | A1 |
20020116271 | Mankoff | Aug 2002 | A1 |
20020117544 | Wolf et al. | Aug 2002 | A1 |
20020128903 | Kernahan | Sep 2002 | A1 |
20020138345 | Dickson et al. | Sep 2002 | A1 |
20020138346 | Kodaka et al. | Sep 2002 | A1 |
20020161631 | Banerjee et al. | Oct 2002 | A1 |
20020169665 | Hughes et al. | Nov 2002 | A1 |
20020169668 | Bank et al. | Nov 2002 | A1 |
20020169892 | Miyaoku et al. | Nov 2002 | A1 |
20020178060 | Sheehan | Nov 2002 | A1 |
20020194303 | Suila et al. | Dec 2002 | A1 |
20030004808 | Elhaoussine et al. | Jan 2003 | A1 |
20030004821 | Dutta et al. | Jan 2003 | A1 |
20030014306 | Marko | Jan 2003 | A1 |
20030055726 | Sohya et al. | Mar 2003 | A1 |
20030074259 | Slyman, Jr. et al. | Apr 2003 | A1 |
20030093283 | Morsa | May 2003 | A1 |
20030093314 | Leung et al. | May 2003 | A1 |
20030108009 | Petersen | Jun 2003 | A1 |
20030115152 | Flaherty | Jun 2003 | A1 |
20030117635 | Roberts | Jun 2003 | A1 |
20030158796 | Balent | Aug 2003 | A1 |
20030195806 | Willman et al. | Oct 2003 | A1 |
20030217153 | Rao et al. | Nov 2003 | A1 |
20030233190 | Jones | Dec 2003 | A1 |
20040054575 | Marshall | Mar 2004 | A1 |
20040054592 | Hernblad | Mar 2004 | A1 |
20040054732 | Carter et al. | Mar 2004 | A1 |
20040064351 | Mikurak | Apr 2004 | A1 |
20040117250 | Lubow et al. | Jun 2004 | A1 |
20040137886 | Ross et al. | Jul 2004 | A1 |
20040143500 | Lopez et al. | Jul 2004 | A1 |
20040156326 | Chithambaram | Aug 2004 | A1 |
20040158490 | Sakamura et al. | Aug 2004 | A1 |
20040158492 | Lopez et al. | Aug 2004 | A1 |
20040177003 | Liao et al. | Sep 2004 | A1 |
20040203963 | Shivaram et al. | Oct 2004 | A1 |
20040218574 | Sata et al. | Nov 2004 | A1 |
20040222302 | Matsumori | Nov 2004 | A1 |
20040233621 | Maeoka et al. | Nov 2004 | A1 |
20040240565 | Santhoff et al. | Dec 2004 | A1 |
20040243519 | Perttila et al. | Dec 2004 | A1 |
20040254836 | Emoke Barabas et al. | Dec 2004 | A1 |
20050004840 | Wanninger | Jan 2005 | A1 |
20050027984 | Saito et al. | Feb 2005 | A1 |
20050038574 | Gila et al. | Feb 2005 | A1 |
20050040230 | Swartz et al. | Feb 2005 | A1 |
20050045718 | Bortolin et al. | Mar 2005 | A1 |
20050114213 | Smith et al. | May 2005 | A1 |
20050131761 | Trika et al. | Jun 2005 | A1 |
20050132234 | Dawson | Jun 2005 | A1 |
20050135304 | Wentink et al. | Jun 2005 | A1 |
20050138576 | Baumert et al. | Jun 2005 | A1 |
20050184145 | Law et al. | Aug 2005 | A1 |
20050200671 | Mistry et al. | Sep 2005 | A1 |
20050204152 | Breitbach | Sep 2005 | A1 |
20050230473 | Fajkowski | Oct 2005 | A1 |
20050237270 | Adams et al. | Oct 2005 | A1 |
20060003776 | Natori et al. | Jan 2006 | A1 |
20060014532 | Seligmann et al. | Jan 2006 | A1 |
20060015404 | Tran | Jan 2006 | A1 |
20060015405 | Bala et al. | Jan 2006 | A1 |
20060026070 | Sun | Feb 2006 | A1 |
20060030341 | Pham | Feb 2006 | A1 |
20060068822 | Kalhan | Mar 2006 | A1 |
20060073851 | Colando et al. | Apr 2006 | A1 |
20060074784 | Brown | Apr 2006 | A1 |
20060111967 | Forbes | May 2006 | A1 |
20060130100 | Pentland | Jun 2006 | A1 |
20060143080 | Garg et al. | Jun 2006 | A1 |
20060177030 | Rajagopalan et al. | Aug 2006 | A1 |
20060178932 | Lang | Aug 2006 | A1 |
20060180664 | Barrett et al. | Aug 2006 | A1 |
20060190331 | Tollinger et al. | Aug 2006 | A1 |
20060194569 | Hsueh | Aug 2006 | A1 |
20060293968 | Brice et al. | Dec 2006 | A1 |
20070017259 | Cho et al. | Jan 2007 | A1 |
20070043626 | Duvall et al. | Feb 2007 | A1 |
20070057051 | Bortolin et al. | Mar 2007 | A1 |
20070061208 | Goldman et al. | Mar 2007 | A1 |
20070061302 | Ramer et al. | Mar 2007 | A1 |
20070087732 | Hsueh | Apr 2007 | A1 |
20070112951 | Fung et al. | May 2007 | A1 |
20070124209 | Walker et al. | May 2007 | A1 |
20070131759 | Cox et al. | Jun 2007 | A1 |
20070136657 | Blumenthal et al. | Jun 2007 | A1 |
20070136775 | MacKay et al. | Jun 2007 | A1 |
20070138270 | Reblin | Jun 2007 | A1 |
20070150339 | Retter et al. | Jun 2007 | A1 |
20070156513 | Mastrianni et al. | Jul 2007 | A1 |
20070173266 | Barnes, Jr. | Jul 2007 | A1 |
20070174116 | Keith et al. | Jul 2007 | A1 |
20070174259 | Amjadi | Jul 2007 | A1 |
20070182546 | Virk et al. | Aug 2007 | A1 |
20070200671 | Kelley et al. | Aug 2007 | A1 |
20070203792 | Rao | Aug 2007 | A1 |
20070241189 | Slavin et al. | Oct 2007 | A1 |
20070249288 | Moallemi et al. | Oct 2007 | A1 |
20070259690 | Julian et al. | Nov 2007 | A1 |
20070270129 | Luo | Nov 2007 | A1 |
20070276537 | Walker et al. | Nov 2007 | A1 |
20070285306 | Julian et al. | Dec 2007 | A1 |
20070287386 | Agrawal et al. | Dec 2007 | A1 |
20080040229 | Gholston | Feb 2008 | A1 |
20080052169 | O'Shea et al. | Feb 2008 | A1 |
20080065488 | Schwagmann et al. | Mar 2008 | A1 |
20080072066 | Vogler et al. | Mar 2008 | A1 |
20080074264 | Sharpe et al. | Mar 2008 | A1 |
20080077484 | Main et al. | Mar 2008 | A1 |
20080120186 | Jokinen et al. | May 2008 | A1 |
20080133349 | Nazer et al. | Jun 2008 | A1 |
20080133366 | Evans et al. | Jun 2008 | A1 |
20080154714 | Liu et al. | Jun 2008 | A1 |
20080154827 | Connors | Jun 2008 | A1 |
20080167991 | Carlson et al. | Jul 2008 | A1 |
20080189170 | Ramachandra | Aug 2008 | A1 |
20080207327 | Van Luchene et al. | Aug 2008 | A1 |
20080208688 | Byerley et al. | Aug 2008 | A1 |
20080215430 | Ellis et al. | Sep 2008 | A1 |
20080221984 | Abhyanker | Sep 2008 | A1 |
20080238615 | Carpenter | Oct 2008 | A1 |
20080240440 | Rose et al. | Oct 2008 | A1 |
20080262928 | Michaelis | Oct 2008 | A1 |
20080270231 | Li et al. | Oct 2008 | A1 |
20080300970 | Scheibe | Dec 2008 | A1 |
20080300984 | Li | Dec 2008 | A1 |
20090030779 | Tollinger et al. | Jan 2009 | A1 |
20090076911 | Vo et al. | Mar 2009 | A1 |
20090076912 | Rajan et al. | Mar 2009 | A1 |
20090088182 | Piersol et al. | Apr 2009 | A1 |
20090098903 | Donaldson et al. | Apr 2009 | A1 |
20090108064 | Fernandes et al. | Apr 2009 | A1 |
20090164309 | Mgrdechian et al. | Jun 2009 | A1 |
20090178144 | Redlich et al. | Jul 2009 | A1 |
20090233575 | Morrison | Sep 2009 | A1 |
20100066498 | Fenton | Mar 2010 | A1 |
20100138303 | Preston et al. | Jun 2010 | A1 |
20100153205 | Retter et al. | Jun 2010 | A1 |
20100174615 | Weaver | Jul 2010 | A1 |
20100185504 | Rajan et al. | Jul 2010 | A1 |
20100205043 | Edwards | Aug 2010 | A1 |
20100241574 | Salazar | Sep 2010 | A1 |
20100257020 | Bryant et al. | Oct 2010 | A1 |
20100280960 | Ziotopoulos et al. | Nov 2010 | A1 |
20100289640 | Annamalai | Nov 2010 | A1 |
20100299224 | Borom et al. | Nov 2010 | A1 |
20110028160 | Roeding et al. | Feb 2011 | A1 |
20110119132 | Morton et al. | May 2011 | A1 |
20110215138 | Crum | Sep 2011 | A1 |
20110250901 | Grainger et al. | Oct 2011 | A1 |
20110276385 | Keller | Nov 2011 | A1 |
20130006773 | Lutnick et al. | Jan 2013 | A1 |
20130085827 | Jenkins | Apr 2013 | A1 |
20130144703 | VanNoller | Jun 2013 | A1 |
20150017951 | Agrawal et al. | Jan 2015 | A1 |
20150024689 | Agrawal et al. | Jan 2015 | A1 |
20160012489 | Rajan et al. | Jan 2016 | A1 |
Number | Date | Country |
---|---|---|
1432949 | Jul 2003 | CN |
1633660 | Jun 2005 | CN |
1672382 | Sep 2005 | CN |
1694122 | Nov 2005 | CN |
1716223 | Jan 2006 | CN |
1799061 | Jul 2006 | CN |
1879121 | Dec 2006 | CN |
1968167 | May 2007 | CN |
101384031 | Mar 2009 | CN |
101731017 | Jun 2010 | CN |
1758308 | Feb 2007 | EP |
1926335 | May 2008 | EP |
2184927 | May 2010 | EP |
11353555 | Dec 1999 | JP |
2000275328 | Oct 2000 | JP |
2001034658 | Feb 2001 | JP |
2001145785 | May 2001 | JP |
2001216449 | Aug 2001 | JP |
2001223712 | Aug 2001 | JP |
2001325507 | Nov 2001 | JP |
2002073666 | Mar 2002 | JP |
2002074131 | Mar 2002 | JP |
2002109237 | Apr 2002 | JP |
2002132886 | May 2002 | JP |
2002149945 | May 2002 | JP |
2002150102 | May 2002 | JP |
2002525641 | Aug 2002 | JP |
2002251555 | Sep 2002 | JP |
2002279274 | Sep 2002 | JP |
2002291047 | Oct 2002 | JP |
2002374261 | Dec 2002 | JP |
2003006543 | Jan 2003 | JP |
2003023367 | Jan 2003 | JP |
2003051771 | Feb 2003 | JP |
2003067606 | Mar 2003 | JP |
2003115001 | Apr 2003 | JP |
2003187140 | Jul 2003 | JP |
2003208381 | Jul 2003 | JP |
2003256705 | Sep 2003 | JP |
2003263582 | Sep 2003 | JP |
2004094543 | Mar 2004 | JP |
2004516989 | Jun 2004 | JP |
2004220522 | Aug 2004 | JP |
2004236166 | Aug 2004 | JP |
2004248215 | Sep 2004 | JP |
2004272463 | Sep 2004 | JP |
2004326303 | Nov 2004 | JP |
2004328542 | Nov 2004 | JP |
2004334885 | Nov 2004 | JP |
2004362470 | Dec 2004 | JP |
2005011318 | Jan 2005 | JP |
2005020350 | Jan 2005 | JP |
2005045756 | Feb 2005 | JP |
2005078173 | Mar 2005 | JP |
2005128903 | May 2005 | JP |
2005128965 | May 2005 | JP |
2005141686 | Jun 2005 | JP |
2005209114 | Aug 2005 | JP |
2005528016 | Sep 2005 | JP |
2005533316 | Nov 2005 | JP |
2005534260 | Nov 2005 | JP |
2006011806 | Jan 2006 | JP |
2006018511 | Jan 2006 | JP |
2006018824 | Jan 2006 | JP |
2006020004 | Jan 2006 | JP |
2006059219 | Mar 2006 | JP |
2006091355 | Apr 2006 | JP |
2006129000 | May 2006 | JP |
2006139431 | Jun 2006 | JP |
2006197458 | Jul 2006 | JP |
2006227901 | Aug 2006 | JP |
2006246433 | Sep 2006 | JP |
2006295249 | Oct 2006 | JP |
2006318125 | Nov 2006 | JP |
2007025854 | Feb 2007 | JP |
2007502087 | Feb 2007 | JP |
2007072906 | Mar 2007 | JP |
2007133461 | May 2007 | JP |
2007201851 | Aug 2007 | JP |
2007213276 | Aug 2007 | JP |
2008225540 | Sep 2008 | JP |
2008293123 | Dec 2008 | JP |
2009104350 | May 2009 | JP |
2009188922 | Aug 2009 | JP |
2010515168 | May 2010 | JP |
2013500538 | Jan 2013 | JP |
1020020068945 | Aug 2002 | KR |
20020096946 | Dec 2002 | KR |
20030011744 | Feb 2003 | KR |
20030018741 | Mar 2003 | KR |
20040020309 | Mar 2004 | KR |
20040069122 | Aug 2004 | KR |
100512362 | Sep 2005 | KR |
20060014942 | Feb 2006 | KR |
20060018235 | Feb 2006 | KR |
20060064222 | Jun 2006 | KR |
20060124430 | Dec 2006 | KR |
20070016301 | Feb 2007 | KR |
2150790 | Jun 2000 | RU |
2267156 | Dec 2005 | RU |
20050100782 | Feb 2006 | RU |
2301450 | Jun 2007 | RU |
I228364 | Feb 2005 | TW |
I252324 | Apr 2006 | TW |
I252628 | Apr 2006 | TW |
I252639 | Apr 2006 | TW |
I252671 | Apr 2006 | TW |
WO9613920 | May 1996 | WO |
0178423 | Oct 2001 | WO |
WO-0175710 | Oct 2001 | WO |
0221478 | Mar 2002 | WO |
WO0225823 | Mar 2002 | WO |
0250732 | Jun 2002 | WO |
WO02054353 | Jul 2002 | WO |
WO03107289 | Dec 2003 | WO |
2004008276 | Jan 2004 | WO |
2004014037 | Feb 2004 | WO |
2004027662 | Apr 2004 | WO |
WO-2004107230 | Dec 2004 | WO |
2005045455 | May 2005 | WO |
2005064515 | Jul 2005 | WO |
2005110208 | Nov 2005 | WO |
2005122483 | Dec 2005 | WO |
WO2006030341 | Mar 2006 | WO |
WO2006092772 | Sep 2006 | WO |
2007026745 | Mar 2007 | WO |
WO2008027965 | Mar 2008 | WO |
2008146576 | Dec 2008 | WO |
2008157804 | Dec 2008 | WO |
WO2008157806 | Dec 2008 | WO |
2009140438 | Nov 2009 | WO |
2010096617 | Aug 2010 | WO |
2011014292 | Feb 2011 | WO |
Entry |
---|
Lester, J et al., ““Are You With Me ?”—Using Accelerometers to Determine if Two Devices are Carried by the Same Person”, LNCS, Pervasive Computing, Apr. 2004,vol. 3001, pp. 33-50. |
Bardia Alavi, et al., “Indoor Geolocat ion Distance Error Modeling using UWB Channel Measurements” ,2005 IEEE 16th International Symposium on Personal, Indoor and Mobile Radio Communications, Sep. 11-14, 2005. |
Blundo, C. et al.: “Secure E-Coupons,” Electronic Commerce Research, vol. 5, No. 1, pp. 117-139, Kluwer, Dordrecth, NL, (Jan. 1, 2005), XP002380651, ISSN: 1389-5753, Section 8.4. |
Co-pending U.S. Appl. No. 13/048,060, filed Mar. 15, 2011. |
Co-pending U.S. Appl. No. 13/363,580, filed Feb. 1, 2012. |
International Search Report and Written Opinion—PCT/US2008/067765, International Search Authority—European Patent Office—Oct. 14, 2008. |
Okazaki, “Eight Methods for Capitalizing on Access Log Analysis, which are Essential to SEO, Marketing and Redesign”, Web Creators, NdN Corporation, Japan, Mar. 1, 2005, vol. 39, pp. 148-155. |
Roumeliotis, T., “Five geofencing ideas for mobile marketing from brands and retailers,” Mobile Commerce Daily, Jul. 16, 2010, 2 pages, Retrieved from http://www.mobilecommercedaily.com/five-geofencing-ideas-for-mobile-marketing-from-brands-and-retailers. |
“Digital Watermarking Alliance”, Oct. 19, 2006, 8 Pages, Retrieved from the Internet: URL: http://www.digitalwatermarkingalliance.org/faqs.asp [retrieved on Jul. 21, 2014]. |
Itao T., “Relationship Mechanism for Dynamic and User Preference-Aware Service Creation”, Journal of the Information Processing Society of Japan, Japan, IPSJ, Mar. 15, 2003, vol. 44, No. 3, pp. 812-825. |
Kirovski D., et al., “Spread Spectrum Watermarking of Audio Signals”, IEEE Transactions on Signal Processing, vol. 51, No. 4, pp. 1020-1033, Apr. 2003. |
Number | Date | Country | |
---|---|---|---|
20090061884 A1 | Mar 2009 | US |
Number | Date | Country | |
---|---|---|---|
60945098 | Jun 2007 | US |